Peter,
I understand your dismay and I thing it is reasonable that in your
case it's probably better to either depend directly on libdb5.1-dev +
db5.1-util (and db4.8-util) or on libdb-dev (= 5.1), libdb-dev (
5.2), db-util (= 5.1), db-util ( 5.2).
Anyway Stefan has uploaded the needed changes to
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:
* Ondřej Surý:
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?).
Does db_upgrade deal with environment updates these days?
AFAIK,
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,
Package: subversion
Version: 1.6.16dfsg-1
Severity: normal
User: pkg-db-de...@lists.alioth.debian.org
Usertags: db5.1
Your package currently still uses Berkeley DB version 4.8 (libdb4.8).
However, there is a newer Berkeley DB version in the archive (libdb5.1),
with a compatible API. Berkeley DB
[Ondrej Surý]
Your package currently still uses Berkeley DB version 4.8 (libdb4.8).
Indeed.
subversionBuild-Depends: libaprutil1-dev
libaprutil1-dev Depends: libdb4.8-dev
libdb*-devConflicts: libdb*-dev
Some time ago I suggested that apr-util should drop this -dev
6 matches
Mail list logo
