Your message dated Tue, 6 Nov 2007 09:55:01 +0100 (CET)
with message-id <[EMAIL PROTECTED]>
and subject line [Debian-med-packaging] Bug#449440: severity is important (fwd)
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: gnumed-common
Version: 0.2.7.0-1
Severity: important


gnumed-common requires python-support > 0.7.1 which makes it
uninstallable on Debian/Etch which has python-support 0.5.6.

This makes it impossible to run GNUmed from testing on a Debian/Stable
system. Please fix if possible. gnumed-client may suffer the same
problem.

Thanks,
Karsten

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable'), (200, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages gnumed-common depends on:
ii  adduser                       3.102      Add and remove users and groups
ii  debconf [debconf-2.0]         1.5.11     Debian configuration management sy
ii  python                        2.4.4-2    An interactive high-level object-o
ii  python-pgsql                  2.5.1-2    A Python DB-API 2.0 interface to P
ii  python-support                0.5.6      automated rebuilding support for p

gnumed-common recommends no packages.

-- debconf information:
  gnumed/group:



--- End Message ---
--- Begin Message ---
Hi,

I hereby close this bug report because the issuer of the bug
agreed that the problem can not be resolved in unstable/testing
and he has to either use snapshot.debian.net or to try a
backport.

Andreas.

--
http://fam-tille.de

---------- Forwarded message ----------
Date: Tue, 6 Nov 2007 09:21:23 +0100
From: Karsten Hilbert <[EMAIL PROTECTED]>
To: Debian-Med Packaging Team <[EMAIL PROTECTED]>
Subject: Re: [Debian-med-packaging] Bug#449440: severity is important

On Tue, Nov 06, 2007 at 07:17:35AM +0100, RKI Andreas wrote:

If that's so I would like to withdraw 0.2.7.1 from Testing.

Even this would not help.  Reuploading 0.2.7.0 to unstable and then
testing would lead to the consequence that you have to rebuild the
package with the current building tools.  The effect would be that
even 0.2.7.0 would stop working on Etch.
I see.

What you can do is to pick
a package from

   http://snapshot.debian.net/package/gnumed-client
Good to know.

I don't in the least ask for a new version of GNUmed in
Debian/Stable. First of all I ask for a consistent
explanation of why gnumed-client 0.2.7.1 cannot be installed
into a Stable system while 0.2.7.0 can.

Because a package depends from the python-support version it was
compiled against.
And apparently python-support changed versions. I see.

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

_______________________________________________
Debian-med-packaging mailing list
[EMAIL PROTECTED]
http://lists.alioth.debian.org/mailman/listinfo/debian-med-packaging



--- End Message ---

Reply via email to