[Debian-med-packaging] Bug#449440: severity is important

Charles Plessy charles-listes-med-packaging at plessy.org
Tue Nov 6 00:50:12 UTC 2007

Le Tue, Nov 06, 2007 at 12:26:40AM +0100, Steffen Moeller a écrit :
> The dependency is not hard-coded:
> http://svn.debian.org/wsvn/debian-med/trunk/packages/gnumed-client/trunk/
> Package: gnumed-common
> Architecture: all
> Depends: ${python:Depends}, ${misc:Depends}, python-psycopg2
> Pre-Depends: adduser

Dear all, dear Karsten,

indeed, Debian packages are not meant to be compiled and installed on
different branches. What happens with gnumed-common classically happens
with any binary program which depends on a library that has a higher
version number in Testing/Unstable than in Stable. For instance, when
there is a major upgrade of the libc, most binary packages containing C
programs just do not install anymore on Stable.

It is precisely for solving that problem that backports.org has been
invented. But backports.org is not meant to be used for every updates
made in Unstable, only for the ones which we estimate high quality
enough to be targetted to Stable users.

So in conclusion, as Steffen said, rebuilding for Etch in Etch is the
way. We could also think about distributing such rebuild packages
somewhere if gnumed-client is still in a fast development cycle, and
cherry-pick the best ones for backports.org (which can only accept
packages signed by official DDs).

Have a nice day,

Charles Plessy
Wako, Saitama, Japan

More information about the Debian-med-packaging mailing list