Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ordering issue when updating #137

Open
0-wiz-0 opened this issue Sep 15, 2024 · 3 comments
Open

ordering issue when updating #137

0-wiz-0 opened this issue Sep 15, 2024 · 3 comments
Assignees

Comments

@0-wiz-0
Copy link

0-wiz-0 commented Sep 15, 2024

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

@jperkin jperkin self-assigned this Sep 16, 2024
@jperkin
Copy link
Contributor

jperkin commented Sep 16, 2024

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.

@0-wiz-0
Copy link
Author

0-wiz-0 commented Sep 16, 2024

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.

@0-wiz-0
Copy link
Author

0-wiz-0 commented Sep 16, 2024

I'll run pkgin with -t by default from now on, let's see if/when it happens again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants