Re: Advice for release critical bug (WAS: Bug#22942: libpaper depends on libpaperg)
Roman Hodek <Roman.Hodek@informatik.uni-erlangen.de> writes:
> > SOLUTION 3
> > ----------
> > Well, we can also decide that to leave the situation as it is. In this
> > way, however, users would not be able to install the new version of the
> > library without also installing libpaperg (and libc6...)
> That isn't the real problem, but the upgrade from an old system (e.g.
> bo). The libc6 version libpaperg surely conflicts with older versions
> of libpaper, where the libs weren't installed to /usr/lib/libc5-compat
> yet. So to upgrade, the user has to:
> - Install a new libpaper before libpaperg (due to conflict)
> - Install libpaperg before libpaper (due to dependency)
> Obviously, this is Catch-22 :-)
> The only remedy is to remove the old libpaper, and then to install
> libpaper and libpaperg.
Where *did* you get this idea from? It's 200% bogus.
| 14:19:44@hades| ~/temp $dpkg -l libpaper | tail +6
| ii libpaper 1.0.3-3 Library for handling paper characteristics
[ ^^ This is bo's ]
| 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) ...
| 14:20:22@hades| ~/temp $
[ You can even do it the other way round, albeit with two dpkg runs ]
[ We've had this discussion before about xview ]
> Additionally, you loose your paper config in the process.
Additionally, you so *don't*. The config file is a config file enough
that it's only removed on purge not remove (not that the remove is
necessary as you claim).
~Yawn And Walk North~
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com