On 20/06/16 16:44, Maximiliano Curia wrote: > Package: release.debian.org > Severity: normal > User: release.debian....@packages.debian.org > Usertags: transition > > Hi, > > Now that the qt transition is over, we would like to start pushing kdepim to > unstable. This should address the auto transitions: > https://release.debian.org/transitions/html/auto-akonadi.html > https://release.debian.org/transitions/html/auto-kdepimlibs.html > https://release.debian.org/transitions/html/auto-libkolab.html > https://release.debian.org/transitions/html/auto-libkgapi.html > > Sadly, the last one was inadvertently started which is currently keeping some > "cruft" packages in testing as they are still depended on, we would upload a > +really version if this causes any problems.
That won't be necessary. > The kdepimlibs binary components were all renamed in the new source package > (kf5-kdepimlibs), so it doesn't really need to be addressed in this > transition, but packages depending on the old kdepimlibs won't be able to use > any of the new kdepim components, so if possible, it would be better to > disable the dependency and remove the kdepimlibs packages. What dependency? I don't follow here, sorry. > The following ben file is intended to block all the new kdepim packages (that block them? > build depend on libkf5akonadi-dev, libkf5libkleo-dev and/or > libkf5akonadiserver-dev, as well as to cover the packages affected by the > mentioned auto-transitions. I'm sure there is a more elegant way to express > this, but this seems to "work". What is the purpose of this tracker? Is it an aggregation of the four auto-* ones, or does it have any additional value? I guess you explained it above, but I didn't quite understand that, possibly because I'm not familiar with these kde stuff. Cheers, Emilio
