Synopsis: "pkg_chk" uses binary packages when it shouldn't

State-Changed-From-To: open->feedback
State-Changed-By: abs@netbsd.org
State-Changed-When: Wed, 15 Feb 2006 13:31:14 +0000
State-Changed-Why:
I believe this could happen, but cannot reproduce it this end. For reference:

-- With out of date package for which newer binary available:
# pkg_info
tnef-1.3.2nb1       Decode MS-TNEF MIME attachments
pkg_chk-1.67        Check installed package versions against pkgsrc
# pkg_chk -u
tnef-1.3.4: version mismatch - tnef-1.3.2nb1 (binary package available)
13:14 /usr/bin/env /usr/sbin/pkg_delete -K /var/db/pkg -r tnef-1.3.2nb1
[ Rechecking packages after deletions ]
tnef-1.3.4: missing (binary package available)
[ Install ]
13:14 /usr/bin/env /usr/sbin/pkg_add -K /var/db/pkg /files/netbsd/pkgsrc/packages/NetBSD-3.0-i386/All/tnef-1.3.4.tgz
13:14 rm -f /pkgsrc/pkgchk_update-forsaken.conf
Installed: tnef-1.3.4

-- With out of date package for which binary is also out of date:
# pkg_info                                       rzip-2.0nb1         Create or extract .rz files, like gzip but smaller
pkg_chk-1.67        Check installed package versions against pkgsrc
# pkg_chk -u                                     rzip-2.1: version mismatch - rzip-2.0nb1
Merging in previous /pkgsrc/pkgchk_update-forsaken.conf
13:17 /usr/bin/env /usr/sbin/pkg_delete -K /var/db/pkg -r rzip-2.0nb1
[ Rechecking packages after deletions ]
rzip-2.1: missing
[ Install ]
13:17 cd /pkgsrc/archivers/rzip && /usr/bin/make update CLEANDEPENDS=yes
[...]

would it be possible that there are multiple Mesa binary packages in the
package dir?

Alternatively, what could happen:

pkg-a depends on pkg-b
pkg-b version is changed, but not pkg-a
pkg_chk removes outdated pkg-b and (automatically) pkg-a
pkg_chk.conf contains pkg-a
pkg_chk finds correct binary package for pkg-a, so installs it. This pulls in
the outdated pkg-b.


Could this be happening in your case?