Open 0-wiz-0 opened 3 days ago
Thanks. The problem with this is that I can never reproduce it, let alone create a test case for it, and by the time you've done the upgrade there's no way to go back and re-run your pkgin with -t
to see what it calculated for everything.
I'll keep trying to write a test case that can trigger such issues, but in the meantime if you're able to always run pkgin
with -t
and then send me the trace log should you see issues again that'd be really helpful.
Is there anything you're doing that might cause some inconsistencies in pkg_summary
? My only guess for now is that there is something not quite right there, whereas I and most other users always use packages that were produced by pbulk so everything is in sync.
I only use pkgin to upgrade from pbulk-produced binary packages.
I sometimes run pkgin up
& pkgin ug
before finding out that one or two packages didn't build, but I don't think this happened here.
I'll run pkgin
with -t
by default from now on, let's see if/when it happens again.
When updating my pkgsrc installation from binary packages produced by a limited pbulk, I got the message that there were 4 errors. Looking at the logs I see that some packages that depend on x265 where 'refreshed' before x265 was upgraded, which lead to errors about missing shared libraries.
zip archive of log: pkg_install-err.zip