On Tue, 14 Jun 2005, Jeroen van Wolffelaar wrote: > On Mon, Jun 13, 2005 at 01:18:51PM -0500, Micah Anderson wrote: > > Package: ftp.debian.org > > Severity: normal > > > > lkcdutils/lkcdutils-dev is currently a dummy transitional package > > package to facilitate upgrades in sarge. It has been superseded and > > should be completely removed for etch/sid. Please remove it from the > > archive. > > lkcdutils and -dev are built from dumputils. Removing those packages > from the archive makes no sense as on next upload you'd reintroduce > them.
We put lkcdutils/-dev in dumputils for transitional purposes and intended to remove them once we knew that they'd be removed from the archive. I'm uploading a new dumputils now that removes lkcdutils and lkcdutils-dev, should I close this bug in the changelog when I do? > Please instead simply stop building those packages from the dumputils > source package, and lkcdutils and -dev will disapprear > semi-automagically. Is there some automatic culling process that will remove packages that don't exist anymore or something? We are puzzled by this because we aren't really sure we understand how this can work as at any moment the package could be uploaded from some other place, so how can it be known that it should be removed from the archive, except by filing a bug to have it removed?
signature.asc
Description: Digital signature
