On Sat, Mar 20, 2004 at 01:34:23PM +0100, Adrian Bunk wrote: > > On 2004-03-17 16:08 +0100, Martin Pitt wrote: > > > Hi Steve, hi Oliver! > > > On 2004-03-17 0:43 -0600, Steve Langasek wrote: > > > > I question whether this bug should really be considered RC. The binary > > > > that fails comes from the old version of the package, which did have > > > > correct dependencies on libkrb5-17-heimdal; and the database > > > > dump/restore is normally done as part of the upgrade, AIUI; so this > > > > really ought to only fail if something else forced the removal of the > > > > already-installed libkrb5-17-heimdal package at the time of upgrade, and > > > > I can't see any conflicts in the archive that would do this. > > > > IMHO, this bug ought to be considered "important", not "serious". > > > Oliver planned to upload a new version into woody-proposed-updates > > > which will also save all depended-on libraries. This will ensure a > > > clean upgrade to Sarge and help the situation a litte. However, the > >... > > This bug affects only a small fraction of testing users (it does not > > really affect the sid version) and Oliver will prepare an updated > > woody version (which will prevent missing libraries, thus > > straightening the upgrade path from woody). According to the > > discussion partly quoted above I'm downgrading this bug to important > > now. > This will ensure _nothing_. > It's supported that users upgrade from Debian 3.0r0 to 3.1. > > I'm CC'ing this to -release for some feedback. If somebody objects to > > this downgrade, then please upgrade the bug to RC again; you have time > > for this until libxml2 enters testing. > > Thank you for considering and for any comments, and have a nice weekend! > I don't know much about the PostgreSQL packaging, but a working upgrade > from Debian 3.0r0 to Debian 3.1 is definitely a must, and a non-working > database upgrade is without question RC. This bug only occurs when there are libraries needed by the old version of pg_dump which are not needed by the new version, *and* the packages providing those libraries have been removed, prior to upgrading the database. This is a bigger deal when upgrading from testing, because there are a large number of Kerberos-related library dependencies that have changed recently. Between 7.1.2-2woody4 and 7.4.2-1, however, the only library dependencies that have been dropped are libssl0.9.6 and libpgsql2. Since the only package that conflicts meaningfully with these libraries is harden-remoteflaws, if the user allows the maintainer scripts to upgrade the database at package upgrade time, this should be a non-issue. Even if the user doesn't upgrade the database when the package is upgraded, the needed libraries are likely to still be installed unless something like deborphan is in use on the system. My impression is that, with all of these factors taken together, the bug is not RC in scope. One improvement I do think the maintainers could make to the postgresql packages would be to not *ask* the user whether the database should be upgraded. I should never have to answer the question "do you want your system to remain usable?" when upgrading. ;) -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature