Le Sat, 26 Jan 2013 22:59:55 +1100, Dmitry Smirnov <only...@member.fsf.org> a écrit :
> On Sat, 26 Jan 2013 22:29:07 Laurent Bigonville wrote: > > I think you are getting an warning/error when python-pyodbc is not > > present instead of a simple crash. I guess recommending the package > > would be enough, but then you cannot enforce version. IMHO it would > > depends on the number of extra packages that are getting installed. > > > > I don't this it's working with the version in wheezy. In the code I > > see: > > > > "Could not import the pyodbc python module. You need pyodbc 2.1.8 or > > newer for migrations from RDBMSes other than MySQL." > > > > So I guess that the version should be (>= 2.1.8) instead of (>= > > 3.0.6). > > I see, we only have 2.1.7 in "testing"... > > Recently I've learned that versioned Recommends are considered by > aptitude but ignored by apt-get. > What do you think about combination of > > Recommends: python-pyodbc (>= 3.0.6) > Breaks: python-pyodbc (< 3.0.6) > > as alternative to > > Depends: python-pyodbc (>= 3.0.6) > > ? > > Depends is a good way to enforce version and I reckon we can ignore > the negative effect on backportability for now... Well I would probably just reflect what the software really needs (so 2.1.7) even if it's not available. I don't think the breaks is needed, the error message will show the needed version if it's not available. I would personally just do: Depends: python-pyodbc (>= 2.1.8) or Recommends: python-pyodbc (>= 2.1.8) Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
