Hi! On 2004-03-07 9:28 +0100, Matthias Klose wrote: > As Colin said, an update of postgresql, which fixes the RC report, > maybe with priority medium, and then migrates to testing in five days > is the preferred solution. Okay, I will do that. > OTOH, if the upload doesn't fix the RC report and it was already > broken in sarge, then maybe downgrade the severity and let it go to > testing as it is now? No, the current RC bug in particular is fixed (we just got another one today, I will see what we can do about it). The automatic upgrading is flawed in general; this affects both the testing and the Sid version. postgresql tries to keep binaries from a previous version to be able to dump the database and then restores it in the new format; however, as the newest RC BR (and many many others) show, there may be libraries which changed or disappeared which make the automatic upgrade break. Before you ask: there were already versions which tried to dump in the preinst (with the old binaries still present), but that was flawed as well since other packages may already be replaced. Oliver is working at a new architecture which will allow several major versions be installed in parallel; this will eventually solve all troubles, but it is not finished yet. In this sense the current is no better or worse than the one in Sarge. But the current version fixes many other bugs that are still in testing, so I think it is worth uploading. I don't have time to do it today, but I will care for that tomorrow. Have a nice day! Martin -- Martin Pitt Debian GNU/Linux Developer martin@piware.de mpitt@debian.org http://www.piware.de http://www.debian.org
Attachment:
signature.asc
Description: Digital signature