Daniel Burrows <dburr...@debian.org> wrote: > 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."
I still don't understand. I didn't make any specific changes, I just asked to do a full-upgrade. So these upgrade actions should have been considered anyway, as part of my requested changes, not later as a solution to something. > I'm not sure what you're talking about here -- you mean what happens > when dpkg actually runs? Yes; it was only meant as a comment clarifying that the situation might indeed be hard to understand for aptitude, since dpkg also doesn't "understand me". > That's all done by the apt library, based on > the dependencies of the package. Probably you need to tweak your > metadata a little. I guess so... Regards, Frank -- Dr. Frank Küster Debian Developer (TeXLive) VCD Aschaffenburg-Miltenberg, ADFC Miltenberg B90/Grüne KV Miltenberg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
