Hi Andreas, On Wed, Mar 14, 2012 at 07:29, Andreas Beckmann <deb...@abeckmann.de> wrote: > Package: cyrus-common-2.2 > Version: 2.4.13-1 > Severity: normal > User: debian...@lists.debian.org > Usertags: piuparts > > > Hi, > > while doing upgrade tests squeeze -> wheezy with piuparts I noticed that > upgrading the cyrus packages failed because the database upgrade could > not be performed as dbX.Y-util were missing. Even after enabling > installation of Recommends (which is disabled by default in piuparts), > db4.7-util was missing.
It shouldn't fail even with missing tools. Do you have a installation log file for the failure? > Since the transitional cyrus-*-2.2 packages are most likely > installed/upgraded on old installations only that will need to perform a > database upgrade during the dist-upgrade step, adding Depends for the > extra tools needed in that case seems sensible to me. Yes, but they depend on cyrus-common-2.4, which depend on cyrus-common, so only cyrus-common is needed. > What about adding an extra package like 'cyrus-upgrade' that depends on > the tools needed to perform a database upgrade? This could be installed > by the admin to ensure that there are always the right tools available > in case of a dist-upgrade. How does that differ from having the packages to depend on the right tools? I have changed cyrus-common to Depend on db-util which should always pull up-to-date libdb package utilities and I think that should be enough. Ondrej -- Ondřej Surý <ond...@sury.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
