Re: pkg/32790 ("pkg_chk" uses binary packages when it shouldn't)

[Matthias Scheler <tron%zhadum.org.uk@localhost>]

The following reply was made to PR pkg/32790; it has been noted by GNATS.

From: Matthias Scheler <tron%zhadum.org.uk@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/32790 ("pkg_chk" uses binary packages when it shouldn't)
Date: Wed, 15 Feb 2006 13:55:17 +0000

 On Wed, Feb 15, 2006 at 01:31:15PM +0000, abs%netbsd.org@localhost wrote:
 > would it be possible that there are multiple Mesa binary packages in the
 > package dir?
 
 No of the package which it was about to build because I remove old binary
 packages with a script after updating my packages.
 
 It is however very likely that there were two binary packages of one of
 the package which just had been update: the old one and the one which
 just has been created.
 
 > 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.
 
 I know about that behaviour and that's not what I complaining about. In my
 case it definitely reinstalled an outdated version from a binary package.
 
 Can it perhaps like this:
 1.) "a" depends on "b" and "c".
 2.) "b" and "c" are outdated.
 3.) "pkg_chk -u" removes "b" and "c".
 4.) "pkg_chk -u" builds and install "b".
 5.) "pkg_chk -u" tries to install "a", find the binary package for it and
      runs "pkg_add a.tgz".
 6.) "pkg_add a.tgz" detects that "b" is missing and install the outdated
      "b" binary package.
 
        Kind regards
 
 -- 
 Matthias Scheler                                  http://scheler.de/~matthias/