[Aptitude-devel] apt, ABI breakages, etc -- was: Bug#764506: Processed: severity of 764506 is normal

[Manuel A. Fernandez Montecelo]

2014-11-27 14:08 David Kalnischkies:
>On Tue, Nov 25, 2014 at 10:42:10AM +0100, Axel Beckert wrote:
>> Anyway: Reason why I consider this not even important is that nobody
>> so far checked if rebuilding aptitude against apt from experimental
>> would already solve the issue -- which IMHO is not that unlikely. (I
>> though could imagine that it may FTBFS on that occassion.)
>
>JFTR: we did quite a few times before being denied the abibreak for
>jessie, so I am pretty sure a rebuild against the new abi is all what is
>needed (modulo any breakage we introduced since then, but well) to fix
>this, but this is something we will continue to work on after jessie.

Would it be useful to use different package names to avoid these
issues?

It's a bit of a hassle to do this in Debian, since the packages
changing names have to go through the NEW queue, but well...


>That said, there will be some work in the form of various deprecated
>methods and members to make use of all the good stuff (and get right of
>the bad things) so the compiler will be quite chatty, but it is
>hopefully clear what to do about them and in any case: It would be
>a "stretch" to call this an important todo-list item at the moment…

Is it possible to fix this in advance (before changes in apt happen)
by changing aptitude (and other deps) to stop using some
methods/whatever that will be deprecated, or cannot be done in advance
because the "good-stuff" is not developed/ready yet, and will be done
simultaneously with the deprecation?


>So feel free to bug me (or deity@) about this after jessie, but not
>a minute earlier. ;) (assuming apt is actually part of the jessie
>release… lets say it this way: I have some mixed signals here…)

I don't know if I am getting this right... but do you really think
that it's a possibility that Jessie ships without apt!?!


Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>