Hi Tobias,
Tobias Hansen <tobias.han@gmx.de> (08/05/2012):
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
thanks for the very detailed bug report, that's very much appreciated.
> These are the affected packages in Debian unstable:
[…]
I'll set up a tracker and check everyone's mentioned there. We'll give you
a green light once the current mess is sorted out.
> They all were tested to build fine with allegro4.4, if liballegro4.4-dev
> gets a 'Provides: liballegro4.2-dev', except […]
Beware, between your test rebuilds and when the transition is going to happen,
a switch to gcc 4.7 as default compiler happened (for some architectures), so
one has to make sure those new FTBFS are known, reported, and have a fix
ready. A first row of bug reports was filed, and an archive-wide rebuild was
apparently performed a few hours ago, so bug reports should exist now.
And well, versions in -dev packages are harmful. If you want to rename it right
now (still providing the old liballegro4.2-dev), I'd rather suggest picking up
liballegro-dev.
But what you could do instead, making sure the transition runs fine is:
1. stick to the current liballegro4.2-dev package for now; it mismatches
with the current SONAME, but let's say nobody cares about that.
2. perform the transition.
3. later on, when nobody is stuck in this or that transition, you could
replace liballegro4.2-dev with liballegro-dev (with a Provides until
everyone's build dependencies are updated; making sure nobody has a
versioned build-dep since versioned Provides don't work).
Of course, 3. would be totally optional.
See you later for that transition.
Mraw,
KiBi.
Attachment:
signature.asc
Description: Digital signature