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 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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: