On Thu, 18 Oct 2001 reed@reedmedia.net wrote:

> binary package of xv-3.10anb1 built against different libpng than
> pkgsrc xv-3.10anb1.

It should have been bumped to "nb2" when the dependency on png was
bumped. Same for many other packages. Although the png/buildlink.mk
permits the dependency to be bumped automatically, it doesn't increment
the version number of the package (nor could it -- it should all be done
manually). It's too late now, because there surely are binary packages
that depend on libpng.so.2 floating around already.

> pkgsrc tree is "10 Sep 2001" (which I assume is "stable" for 1.5.2).
> (Please feel free to tell me other tags or other ways to fetch "stable" pkgsrc.)

Sorry, there is no "stable" pkgsrc -- there's no branching at all. Even
rolling back to the netbsd-1-5-PATCH001 tag, the last released "pkgsrc",
won't necessarily help you if you've already installed packages built
from newer pkgsrc, although that would otherwise be your "stable" tag.

> Remove bad package from ftp server(s)?

Sure, but that won't help folks who have CD's burned within the last
year or so.

The best we can do is to resolve not to do it again. Maybe for 1.6* we
should consider going back to separate collections for 1.6, 1.6.1, and
so on, so at least we have a chance to gloss over certain mistakes, and
still produce one single consistent collection of binary packages.