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
I had a partially successful bulk build and decided to use the result anyway for updating (yes, my fault. But when you're using someone else's bulk build you don't know if it's complete or what did not build).
In particular, this upgraded libicu with a shlib major bump.
After the upgrade (pkgin fug) which went without obvious errors or non-standard questions, many packages that had failed in the last bulk would not run any longer, because they depended on the old libicu shared library which was replaced by the new one during the upgrade.
This could have been prevented if pkgin had notified me that packages foo, bar, baz would not resolve their library dependencies any longer after the upgrade and asked for confirmation (then I would have cancelled it).
Please add a check and confirmation dialog for that case. Thanks!
The text was updated successfully, but these errors were encountered:
I'll take a look. This may end up being a little expensive to check, and needs to be done carefully to ensure we still retain checks for files that are not managed by the current target pkgsrc installation.
Obviously not using broken repositories is preferable ;) But I can see that this would be useful in any case.
I had a partially successful bulk build and decided to use the result anyway for updating (yes, my fault. But when you're using someone else's bulk build you don't know if it's complete or what did not build).
In particular, this upgraded libicu with a shlib major bump.
After the upgrade (
pkgin fug
) which went without obvious errors or non-standard questions, many packages that had failed in the last bulk would not run any longer, because they depended on the old libicu shared library which was replaced by the new one during the upgrade.This could have been prevented if pkgin had notified me that packages foo, bar, baz would not resolve their library dependencies any longer after the upgrade and asked for confirmation (then I would have cancelled it).
Please add a check and confirmation dialog for that case. Thanks!
The text was updated successfully, but these errors were encountered: