> > I have to control the version more explicitly. For one thing, I have
> > some "Suggests: dbX.Y-util" that would be pointless if they did not
> > match the dependency.
[Ondrej Surý]
> You may Suggest: db-util from the db-defaults 5.1.1 release ;-).
No, I want the db*-util matching the package build, not the db*-util
matching whatever is in the archive when the user does the install.
> > More importantly, in the past, it has been important to explicitly
> > test and document the procedure for upgrading user data between DB
> > formats.
> Does subversion use transactions (aka does it need db_upgrade?).
It uses transactions and an "environment", whatever that is. (I never
did really understand it.) Please have a look at the README I wrote
some years ago for the db4.2 -> db4.3 transition:
http://svn.debian.org/wsvn/pkg-subversion/trunk/debian/README.db4.3?rev=642
Fortunately, this procedure has not been needed after db4.3, but
perhaps you can see why I don't like to trust the nice people who say
things like "Don't worry! Just let the db-defaults package take care
of which DB version you get! No problem!"
--
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
