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

excessive complaints and corrupted db with an i386 pkg on amd64 #71

Open
gdt opened this issue Jul 30, 2016 · 0 comments
Open

excessive complaints and corrupted db with an i386 pkg on amd64 #71

gdt opened this issue Jul 30, 2016 · 0 comments

Comments

@gdt
Copy link

gdt commented Jul 30, 2016

I have an amd64 NetBSD machine that I just upgraded from i386. For various reasons I have one package that is i386 still (not rebuilt). I generate a local pkg_summary file for my local packages, plus point pkgin at the normal repo. When doing "pkgin up" I get a warning about i386 vs amd64. Then I can run "pkgin -n ar" to see what I might prune. After doing that a few times, I get "pkgin: no packages have been installed with pkgin".

What I'd like to see is pkgin up to give a warning only on the first reading of the i386 pkg, and when the package data has not changed from the db, not warn again. And, have nothing worse than a warning; it's not really 100% broken to have an i386 package installed on an amd64 machine, as it runs fine. In some ways it is not so different than having a package built for NetBSD 4 on a NetBSD 6 machine.

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

1 participant