Previously Wichert Akkerman wrote: > dpkg (1.4.1.15) unstable; urgency=low > > * non-maintainer release. > * Move dselect into its own package Oops, I forgot to remove this from the changelog. I reverted this change since there is no good upgrade strategy for moving dselect to another package. The problem is that when you upgrade the dpkg package it will remove dselect. dselect will only return when the new dselect package is installed. This means there is a timeframe in which you might be doing an install using dselect during which dselect removes itself. This can produce quite nasty problems; imagine what would happen if the install fails before the dselect package gets installed... The only way I can see to prevent this is to rename the dpkg package, and make dpkg a dummy-package that Pre-Depends on dselect and the new dpkg package. That will enforce that both dpkg and dselect will be installed when you upgrade your system. Wichert. -- _________________________________________________________________ / Generally uninteresting signature - ignore at your convenience \ | wichert@liacs.nl http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Attachment:
pgpf4D7s6A867.pgp
Description: PGP signature