block 621460 by 621366 thank you 2011/4/7 Peter Samuelson <pe...@p12n.org>: > > [Ondrej Surı] >> Your package currently still uses Berkeley DB version 4.8 (libdb4.8). > > Indeed. > > subversion Build-Depends: libaprutil1-dev > libaprutil1-dev Depends: libdb4.8-dev > libdb*-dev Conflicts: libdb*-dev > > Some time ago I suggested that apr-util should drop this -dev > dependency, and I believe Stefan Fritsch agreed to do so in his next > upload.
I believe so (php5 was involved in those mails). > Then Subversion will be free to _not_ track the DB version of > apr-util. At that time, I will have a look at whether Subversion can > be migrated to DB 5.x. Thank you, I would be happy to help. >> Please port your package to libdb5.1 as soon as possible. In most cases >> only change required is to update build depends from libdb4.8-dev >> to libdb-dev, or just recompile the package. > > 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. You may Suggest: db-util from the db-defaults 5.1.1 release ;-). > 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?). Even though the upgrade path should be fairly straightforward - the only thing you need to take care of is backuping your database before running dbX.Y_upgrade (where X.Y is the new version) on the database file. O. -- Ondřej Surý <ond...@sury.org> http://blog.rfc1925.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
