Bug#827755: transition: kdepim-16.04
On Monday, 20 June 2016 18:48:29 CEST Emilio Pozuelo Monfort wrote:
> On 20/06/16 16:44, Maximiliano Curia wrote:
> > 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.
Sorry for not being clear enough. After rethinking this, I realize that the
kdepimlibs part of the transition is not really needed as the binaries and the
source package names are different.
I'll just remove the kdepimlibs part from this transition request.
> > The following ben file is intended to block all the new kdepim packages
> > (that
> > > block them?
What I meant is keep them in unstable while the transition is ongoing.
> > 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.
The auto transitions only cover some of the kdepim packages, most of the
packages are now in new source packages, either because they were split/
renamed upstream or because we needed the co-installability (kdepimlibs and
kf5-kdepimlibs).
Reviewing the list of packages, I've just realized that we will need an new
akonadi4 upload to provide the old akonadi libraries.
Running the tracker against unstable and experimental gives the full list of
the affected packages, as many of them are only in experimental.
The important part here is that this transition is centered in migrating
kdepim, given the amount of packages involved in the transition, it is very
hard to know which combinations of new and old versions will work well
together, and thus I would prefer to hold the whole suite in unstable until is
ready.
Revised Ben file:
title = "kdepim-16.04";
is_affected = .source ~ /akonadi/
| .source ~ /akonadi4/
| .build-depends ~ /libkf5akonadi-dev/
| .build-depends ~ /libkf5akonadiserver-dev/
| .build-depends ~ /libkf5libkleo-dev/
| .build-depends ~ /libakonadi-dev/
| .source ~ /libkgapi/
| .build-depends ~ /libkf5gapi-dev/
| .build-depends ~ /libkgapi-dev/
;
is_good = .build-depends ~ /libkf5akonadi-dev/
| .build-depends ~ /libkf5akonadiserver-dev/
| .build-depends ~ /libkf5libkleo-dev/
| .build-depends ~ /libkf5gapi-dev/
;
is_bad = .build-depends ~ /libakonadi-dev/
| .build-depends ~ /libkgapi-dev/
| .depends ~ /\b(akonadi\-dbg|libakonadi\-dev|
libakonadiprotocolinternals1)\b/
| .depends ~ /\b(libkgapi2\-2)\b/
| .depends ~ /\b(libkolab0v5)\b/
;
--
"Nothing ever goes away." -- Commoner's Law of Ecology
Saludos /\/\ /\ >< `/
Reply to: