Comment 12 for bug 316858

On Tue, Jan 27, 2009 at 11:39 PM, Celso Providelo
<email address hidden> wrote:
> Note that we are working with the hypothesis that apt will behave
> slightly better if we have multiple binary versions available in the
> repository index when there is an unstable transition. For instance, in
> the bzr PPA case:
>
> * bzr_1.2 (requires bzrtools == 1.2) is published
> * bzr_1.1 (requires bzrtools == 1.1) is published
> * bzrtools_1.1 is published
>
> In this scenario apt will install (of keep) bzr_1.1 and bzrtools_1.1
> installed with a discreet warning about the fact that bzr_1.2 exist but
> cannot be installed without removing bzrtools_1.1. However, if bzr_1.1
> gets superseded and thus removed from the repository index (current
> approach), apt will automatically remove bzrtools and install bzr_1.2.
>
> For standalone binaries (inkscape case) it will indeed allow user to
> jump back and forward through the available versions.
>
> Before digging into implementation details, I'd like to confirm if apt
> actually behaves as I described or am I dreaming.

Synaptic's 'Mark all Updates' function will remove bzrtools and
install bzr 1.2 even when the bzr 1.1 package still exists (provided
you haven't locked the bzr version).
Update manager will not remove the 1.1 package.

Different tools will behave differently, even if they are just front
ends to apt.

--
Stuart Bishop <email address hidden>
http://www.stuartbishop.net/