On Tue, Aug 18, 2009 at 08:11:52PM +0200, Frank Küster <fr...@debian.org> was heard to say: > I'm not sure whether this is actually a bug in the dependency handling, > or rather just a strange way to tell me something.
I think the latter. > Why does it think those packages are broken, when simply doing what I > requested (upgrade everything that can be upgraded) solves the problem? It means that "after I applied your changes, there were broken packages. This fixes them." > Note that in the following script, it does actually not what I expect > (as a maintainer). While it says it will remove texlive-base-bin and > texlive-base-bin-doc, it first starts to unpack lots of other (upgraded) > packages. This results in a couple of file conflicts (not shown > below). We intended to force the removal by some conflicts, but it seems > we did it wrong. I'm not sure what you're talking about here -- you mean what happens when dpkg actually runs? That's all done by the apt library, based on the dependencies of the package. Probably you need to tweak your metadata a little. Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
