Re: why is apt 0.8.16~exp12 still in experimental ?
(Daniel answered most of it, but as i had typed most of my answer
already before i left for carnival organization, let me answer it, too)
2012/2/18 shirish शिरीष <shirishag75@gmail.com>:
> At this point it seems it just is breaking lot of things.Am I reading
> it right or doing something wrong ?
The reason for APT being in experimental currently is that it breaks
the ABI which means that packages depending on libapt-* need to
be recompiled against the new version. (So point 1 from Daniel,
it's not so much point 2 - but more testing would hurt obviously).
Uploads of such ABI breaks need to be coordinated with the release
team as such uploads otherwise might possibly interfere with other
uploads and ongoing transitions of groups of packages to testing.
Now, what stops us from asking the release team for a spot in the
transition query?
Easy. Transitions are a bit painful as they require time and block others
to some extend. So you naturally want to have few of them.
Multiarch is currently in flux. As dpkg hasn't published it's final
interface yet and d-devel@ is still discussing if/how or why (not)
certain design decisions are okay.
Its very easy to walk on water - if it is frozen. The same is true for
implementing specifications. We can't push an ABI break to unstable
and create therefore quiet a bit of work to push it to testing just to
notice a few days later that we need another ABI break to cope with
whatever ends up to be Multiarch and therefore obsoletes the work
done in the transition (Okay, we can do it, it would just not be nice).
Best regards and "Helau",
David Kalnischkies
Reply to: