[Portaudio] Packages conflicts in Ubuntu Trusty

[Daniel Schürmann]

Hi

we have some issues with portaudio and jack 1/2 on Ubuntu Trusty,
setting up a development environment.
A solution involves uninstalling the default libjack-jackd2-0

The error:

The following packages have unmet dependencies:
libjack-dev : Depends: libjack0 (=
1:0.121.3+20120418git75e3e20b-2.1ubuntu1) but it is not going to be
installed

The final build result (Mixxx) runs fine with libjack-jackd2-0
in place.

Is there a way to setup a dev environmen without removing libjack-jackd2-0?

We track the issue here:
https://bugs.launchpad.net/mixxx/+bug/1326653

Thank you for your help.

Kind regards,

Daniel

[Alan Horstmann]

Hi Daniel,

Post by Daniel Schürmann
we have some issues with portaudio and jack 1/2 on Ubuntu Trusty,
setting up a development environment.
A solution involves uninstalling the default libjack-jackd2-0
libjack-dev : Depends: libjack0 (=
1:0.121.3+20120418git75e3e20b-2.1ubuntu1) but it is not going to be
installed
The final build result (Mixxx) runs fine with libjack-jackd2-0
in place.
Is there a way to setup a dev environmen without removing libjack-jackd2-0?
https://bugs.launchpad.net/mixxx/+bug/1326653

My *guess* would be that the package 'libjack-jackd2-dev' should be installed
instead of 'libjack-dev', from looking through:
'http://packages.ubuntu.com/search?keywords=jack'
but I don't really have a handle on the jack0/1/2 thing yet! Then Portaudio
should build against the correct headers for the installed jack version. Let
us know if that helps.

Regards

Alan

[Daniel Schürmann]

Hi Alan,

cool, that was simple!
Installing libjack-jackd2-dev after portaudio19-dev works.

However if you try to install
portaudio19-dev on a plain Ubuntu with libjack-jackd2-dev, install it
fails, because
it complains about a missing libjack-dev

Once you do the downgrade, you can install
portaudio19-dev
and after that you can upgrade to jack2 again.

libjack-dev is listed in the portaudio19-dev dependency.
I do not know how libjack-jackd2-dev can satisfy this dependency,
but this state should be somehow swapped.

Kind regards,

Daniel

Post by Alan Horstmann
Hi Daniel,

Post by Daniel Schürmann
we have some issues with portaudio and jack 1/2 on Ubuntu Trusty,
setting up a development environment.
A solution involves uninstalling the default libjack-jackd2-0
libjack-dev : Depends: libjack0 (=
1:0.121.3+20120418git75e3e20b-2.1ubuntu1) but it is not going to be
installed
The final build result (Mixxx) runs fine with libjack-jackd2-0
in place.
Is there a way to setup a dev environmen without removing libjack-jackd2-0?
https://bugs.launchpad.net/mixxx/+bug/1326653

My *guess* would be that the package 'libjack-jackd2-dev' should be installed
'http://packages.ubuntu.com/search?keywords=jack'
but I don't really have a handle on the jack0/1/2 thing yet! Then Portaudio
should build against the correct headers for the installed jack version. Let
us know if that helps.
Regards
Alan

[Alan Horstmann]

Post by Daniel Schürmann
cool, that was simple!
Installing libjack-jackd2-dev after portaudio19-dev works.
However if you try to install
portaudio19-dev on a plain Ubuntu with libjack-jackd2-dev, install it
fails, because
it complains about a missing libjack-dev
Once you do the downgrade, you can install
portaudio19-dev
and after that you can upgrade to jack2 again.
libjack-dev is listed in the portaudio19-dev dependency.
I do not know how libjack-jackd2-dev can satisfy this dependency,
but this state should be somehow swapped.

So this would appear to be a Ubuntu/Debian packaging issue? Could you raise
this with them? What seems to be happening is that the Portaudio19 package
lists 'libjack-dev' as a dependancy:
https://packages.debian.org/jessie/portaudio19-dev
and the text mentions that this is provided also by 'libjack-jackd2-dev'.
However the packaging system is not picking up the fact that you have
libjackd2 installed and using the correct dev package, but instead forces the
wrong dev package.

I've no idea how these package managers work 'under-the-hood' but there is
probably a way it can be sorted?

Regards

Alan

[John Clements]

Post by Alan Horstmann

Post by Daniel Schürmann
cool, that was simple!
Installing libjack-jackd2-dev after portaudio19-dev works.
However if you try to install
portaudio19-dev on a plain Ubuntu with libjack-jackd2-dev, install it
fails, because
it complains about a missing libjack-dev
Once you do the downgrade, you can install
portaudio19-dev
and after that you can upgrade to jack2 again.
libjack-dev is listed in the portaudio19-dev dependency.
I do not know how libjack-jackd2-dev can satisfy this dependency,
but this state should be somehow swapped.

So this would appear to be a Ubuntu/Debian packaging issue? Could you raise
this with them? What seems to be happening is that the Portaudio19 package
https://packages.debian.org/jessie/portaudio19-dev
and the text mentions that this is provided also by 'libjack-jackd2-dev'.
However the packaging system is not picking up the fact that you have
libjackd2 installed and using the correct dev package, but instead forces the
wrong dev package.
I've no idea how these package managers work 'under-the-hood' but there is
probably a way it can be sorted?

You (or rather, someone) should probably get in touch with one of the portaudio package maintainers at debian. The url you listed also lists the maintainers of the package. The first human on the list is Kilian Krause (https://qa.debian.org/developer.php?login=kilian%40debian.org) .

Apologies if this was already obvious!

John Clements

[Alan Horstmann]

Post by Alan Horstmann

Post by Daniel Schürmann
However if you try to install
portaudio19-dev on a plain Ubuntu with libjack-jackd2-dev, install it
fails, because
it complains about a missing libjack-dev
Once you do the downgrade, you can install
portaudio19-dev
and after that you can upgrade to jack2 again.
libjack-dev is listed in the portaudio19-dev dependency.
I do not know how libjack-jackd2-dev can satisfy this dependency,
but this state should be somehow swapped.

So this would appear to be a Ubuntu/Debian packaging issue? Could you
raise this with them?

Daniel has raised:
https://bugs.launchpad.net/ubuntu/+source/portaudio19/+bug/1464913

Regards

Alan

[Alan Horstmann]

Post by Alan Horstmann
https://bugs.launchpad.net/ubuntu/+source/portaudio19/+bug/1464913

And it seems there is already a similar Debian bug (from 2013):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718221

Regards

Alan

[Daniel Schürmann]

Hi Alan,

we have still no solution for the packaging issue.
Is there anyone known who is able to solve this?

Thank you,

Daniel

Post by Alan Horstmann

Post by Alan Horstmann
https://bugs.launchpad.net/ubuntu/+source/portaudio19/+bug/1464913

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718221
Regards
Alan
_______________________________________________
Portaudio mailing list
http://music.columbia.edu/mailman/listinfo/portaudio

[Alan Horstmann]

Hi Daniel,

Post by Daniel Schürmann
we have still no solution for the packaging issue.
Is there anyone known who is able to solve this?

This is a frustrating situation - I hadn't realised there was no progress.
Unfortunately, it is essentially outside of Portaudio control, as it is down
to the distro packaging having got things wrong. I'm not sure what is the
best way to push things along, or if there is a maintainer there who will
pick it up.

Regards

Alan