On Sat 20 Oct 2012 17:50:31 Andreas Beckmann escribió: > On 2012-10-20 22:24, Lisandro Damián Nicanor Pérez Meyer wrote: > > Believe it or not, this is trigerred by a loop dependency between two > > packages and apt gets confused. So far we could not find another way of > > solving it (and > > I really like the analysis and you have my full support for solving the > dependency loop by splitting the package (instead of adding the > transitional package I proposed). > > > So, marking all KDE packages as "found" doesn't really helps. > > It helps piuparts to automatically classify the failed logs and move > them to the affected list. For this to work, the bug needs to have an > Affects: for the package where the bug is observed - and piuparts wants > to have a bug marked as found in the exact version the logfile is about. > Therefore you'll see from time to time a few new found/affects on that > bug ... and with all the about 40 packages failing with > immediate-configure *phonon* problems being moved aside, I can > concentrate on analyzing the "more interesting" failures (and piuparts > will keep checking the affected packages frequently to see if some > dependency got fixed). > > Setting the affects is the right thing to do anyway to have the bug show > up in the bug lists of packages where it is observed. Setting the found > on some foreign package is a little abuse of the BTS and if you know a > better solution ... we can change things. key-value usertags in the BTS > would be nice :-) (or even better key-multivalue usertags) Ah, thank you very much Andreas for taking the time to explain this to me. So please ignore my comment and keep up the good work :-) Kinds regards, Lisandro. -- ~/ sweet ~/ Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.