Greg Troxel <gdt%ir.bbn.com@localhost> writes: > I ran a pkg_rr and got this (after updating base from 5.0_STABLE to > 5.1_RC2, which is hardly an update different from along 5.0_STABLE): > > ===> Updating using binary package of osabi-NetBSD-5.1_RC2 > /usr/pkg/sbin/pkg_add -K /var/db/pkg -U > /n0/gdt/NetBSD-current/pkgsrc/packages/All/osabi-NetBSD-5.1_RC2.tgz > pkg_add: Dependency of libgtop-2.28.0 fulfilled by osabi-NetBSD-5.0_STABLE, > but not by osabi-NetBSD-5.1_RC2 > pkg_add: 1 package addition failed > > > This is wrong; the point of make replace and pkg_rr is that you can > bring packges one by one to an unsafe state and then updates are needed. > By having libgtop depend on osabi, and then get marked unsafe_depends, > pkg_rr will rebuild it, and that part is great. I have tested and committed a fix. pkg_rolling-replace (and make replace in general) should not be able to update osabi and clean up the resulting dirty packages.
Description: PGP signature