You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever an upstream maintainer decides to change the released tarball of a module and the user updated the module before, they will eventually end up with a "download skipped. File already present. Checksum failed." error during the next lin.
I'd like to propose to automatically try to download the module once in this situation.
Otherwise, if this happens in the middle of lunar renew, the module will not be updated but the update process just continues with the next module.
Comments?
The text was updated successfully, but these errors were encountered:
Has the package manager a "pin to version package" implementation? If I understand the challenge correctly, I'm assuming that the user has set their own module in place, which is not easily perceived by the manager? Pinning may give it a mechanism to trust that everything is gravy(should there be no pinning is my current assumption).
Whenever an upstream maintainer decides to change the released tarball of a module and the user updated the module before, they will eventually end up with a "download skipped. File already present. Checksum failed." error during the next
lin
.I'd like to propose to automatically try to download the module once in this situation.
Otherwise, if this happens in the middle of
lunar renew
, the module will not be updated but the update process just continues with the next module.Comments?
The text was updated successfully, but these errors were encountered: