hello, i got the following bugreport, and i'm not sure about the best way to fix it. the problem is obvious: python-mysqldb depends on python2.3-mysqldb (= 1.2.1c3-6), but after a binNMU of python2.3-mysqldb it is version 1.2.1c3-6+b1. so three solutions spring into my mind: - relax the dependency to python2.3-mysqldb (= 1.2.1c3) - relax the dependency to python2.3-mysqldb (>= 1.2.1c3-6) - drop pythonX.Y-mysqldb packages, provide one python-mysqldb package for all python versions. i'm not sure whether this is possible at all. the first solution would negate the intension of the python-mysqldb transitional package. but that's somehow true for the second solution as well. so what do you suggest? ... jonas ----- Forwarded message from Steve Langasek <vorlon@debian.org> ----- Date: Tue, 11 Apr 2006 03:17:50 -0700 From: Steve Langasek <vorlon@debian.org> Subject: Bug#361940: python-mysqldb: can't be binNMUed due to arch: all -> arch: any dep To: submit@bugs.debian.org Reply-To: Steve Langasek <vorlon@debian.org>, 361940@bugs.debian.org Package: python-mysqldb Version: 1.2.1c3-6 Severity: grave The python-mysqldb package is uninstallable in unstable because python-mysqldb was binNMUed for the mysqlclient ABI change, and python-mysqldb, an arch: all package, has a dependency on python2.3-mysqldb (= 1.2.1c3-6) which no longer exists. Arch: all -> Arch: any strict versioned dependencies are fundamentally incompatible with binNMUs. Please either make a single arch: any python-mysqldb package that Provides: python2.3-mysqldb, or relax the dependency so it can be satisfied by +b1 ... +bN versions of the package. Either way, python-mysqldb currently needs a sourceful upload for the libmysqlclient transition. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/ ----- End forwarded message -----
Attachment:
signature.asc
Description: Digital signature