Re: Advice for release critical bug (WAS: Bug#22942: libpaper depends on libpaperg)
>>"James" == James Troup <J.J.Troup@scm.brad.ac.uk> writes:
>> The only remedy is to remove the old libpaper, and then to install
>> libpaper and libpaperg.
James> Where *did* you get this idea from? It's 200% bogus.
>> 14:20:02@hades| ~/temp $sudo dpkg -iEG libpaper_1.0.3-9.deb libpaperg_1.0.3-9.deb
>> (Reading database ... 34403 files and directories currently installed.)
>> Preparing to replace libpaper 1.0.3-3 (using libpaper_1.0.3-9.deb) ...
>> Unpacking replacement libpaper ...
>> Selecting previously deselected package libpaperg.
>> Unpacking libpaperg (from libpaperg_1.0.3-9.deb) ...
>> Setting up libpaperg (1.0.3-9) ...
>> Setting up libpaper (1.0.3-9) ...
Well, in cases like this the order in which the deb files are
presented to dpkg is relevant. So if a novice is upgrading a large
set of packages, and the packages are not presented in the corect
order, the upgrade process issues ominous sounding threats.
This situation is better avoided.
"Open the pod bay doors, HAL." Dave Bowman, 2001
Manoj Srivastava <email@example.com> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com