[Pkg-telepathy-maintainers] Bug#721356: transition: telepathy-logger
Simon McVittie
smcv at debian.org
Wed Sep 4 11:15:49 UTC 2013
On 04/09/13 02:29, Diane Trout wrote:
> I've been trying to maintain kde-telepathy, and am still fairly new to
> official debian package development.
>
> Any suggestions for handling the transition?
Step 0 (optional, but would be useful) is to do local rebuilds of the
KDE stuff against telepathy-logger/experimental, and make sure they
work, in the same way that empathy and gnome-shell in experimental have
already been built against telepathy-logger/experimental (because they
specifically need the newer version). If you need source changes to make
these work, please upload those to experimental; if you only need a
rebuild, there's no need.
Step 1 is to wait for the release team to say "OK to do this transition
now", at which point someone (probably Laurent?) will upload the new
telepathy-logger to unstable and ask the release team to do binNMUs
(automated rebuilds) of all the affected packages.
If a simple rebuild is enough, then you don't need to do anything
further at this stage. If source changes to the KDE stuff do turn out to
be needed, step 2 is to do those uploads - it's probably best if KDE
people build and test those. However, not a lot seems to have changed in
telepathy-logger, and I'm not sure it really needed to break ABI at all,
so I suspect this transition will just need simple rebuilds.
Step 3 is to wait for the rebuilt packages to reach testing, and watch
out for any RC bugs that would impede that.
S
More information about the Pkg-telepathy-maintainers
mailing list