Le lundi 15 mai 2006 à 19:11 -0400, Roberto C. Sanchez a écrit : > I was working on a solution to #359996 and it occurred to me that there > was no easy way let dh_python do its thing *and* still get a versioned > dependency of the form: > > Package: python-foo > Depends: python2.3-foo (= source_version) > > Now, it seems to me that it is relatively important to have that, > otherwise you end up with bugs like #359996. I know that all it would > take would be for someone to have python2.3-eyed3 installed because some > other package depends on it, follwed by an apt-get update (where the > eyed3 packages have new versions), followed again by the user installing > the eyed3 package to get the CLI tools. If the dependency is not > versioned, then you end up with a version mismatch, which could cause > the package to cease functioning. > > That said, I think it would be a good thing in the sense of long term QA > to have this in dh_python. What I don't understand is why the arch all > packages will not be available until the packages have been rebuilt.
They will be uninstallable if they depend from a package that hasn't been rebuilt. You should be aware that we're going to change the way python modules are packaged. This work should hopefully be finished at the end of Debconf. It will solve your issue in a more elegant way. If you cannot wait for a week or two, there is a workaround that would work: we could make dh_python add this strict dependency only if python-foo is Architecture: any. This avoids doing it for packages not needing it, and won't render packages uninstallable. -- .''`. Josselin Mouette /\./\ : :' : [EMAIL PROTECTED] `. `' [EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
signature.asc
Description: Ceci est une partie de message numériquement signée
