Re: Why doesn't libsidplay enter testing?
On Thursday, Jul 3, 2003, at 07:21 US/Eastern, Gerfried Fuchs wrote:
Uhm, that is somehow nonsense. How can an update of a package make
itself uninstallable? What's the reasoning behind it?
Depends: libc6 >= 2.2.0
Depends: libc6 >= 2.4.0
Replacing foo-1.0.6-4 with 1.0.7-1 would make foo uninstallable
(becasue there is no glibc-2.4.0 in testing)
What nudge by a maintainer are you talking about? Especially, which
"ftp master" would be a better term. Probably Anthony Towns.
Thanks, that explains a lot. But it still doesn't explain why the
package holds back itself... Is this a bug in the testing script?
what I understand the testing script should be able to see such
dependencies -- but a dependency that breaks itself seems to be weird.
Circular dependencies are not handled well. I suppose the "feel free to
submit patches" thing applies here.