Bug#695550: libjack-dev: does not automatically transition to libjack-jackd2-dev

[The Wanderer]

On 12/10/2012 11:21 AM, Jonas Smedegaard wrote:

> Quoting The Wanderer (2012-12-10 16:30:19)
> 
>> On 12/10/2012 10:08 AM, Jonas Smedegaard wrote:
>> 
>>> There are multiple implementations of JACK, and one of those
>>> implementations happen to have a "2" in its name.
> 
>> In that case (and based on a few other things which I've snipped), the
>> question becomes why the dist-upgrade is trying to remove libjack0.

> Ohhh: Most likely cause is that libjack-jackd2-dev provides libjack-dev!
> 
> Why does it do that - it seems plain wrong to me!

In combination with what Felipe pointed out about ia32-libs and jackd1, that
looks like a plausible reason to me. (The ia32-libs factor also probably means
that part of the culprit is the holds I have in place on a few other packages,
which are also interfering with parts of the ia32-libs dummy-package transition.
As such, this is at least partly my own fault, and may not manifest for
everyone.)

I'd guess that whoever set that up was operating on the same mistaken
assumptions about the relation of the jack implementations to one another as I
was.

>> I thought the purpose of dist-upgrade, as opposed to upgrade, was simply to
>> allow upgrades across scenarios where dependency changes require
>> installation of different packages rather than simply of new versions of
>> the same packages.
> 
> Check the meanings with "aptitude --help".

On my system, the text output from that command does not include the string
'dist':

wanderer at apologia$ aptitude --help | grep -i dist
wanderer at apologia$

This is with aptitude 0.6.8.2-1.

The aptitude man page does give a hint about what you might be talking about,
but I wouldn't have interpreted the section on the 'full-upgrade' option to mean
what you said. For what little that's worth.

> Oh, and if you used apt-get, then don't. Use aptitude!

I'd rather not, thanks. I'm told that it's not a good idea to mix-and-match
between aptitude and apt-get, and I find the aptitude UI to be palpably less
friendly and manageable in most circumstances than that of apt-get.

I'm aware that I'm a minority in this, but that doesn't change anything.

(Though now that I look, I see an option in aptitude which I think wasn't there
last time I looked, and which looks quite a bit like something I've been wanting
in apt-get for some time now...)

-- 
    The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Every time you let somebody set a limit they start moving it.
   - LiveJournal user antonia_tiger