Summary: | media-sound/jack-audio-connection-kit-0.124.1 : file collision with media-sound/jack2-1.9.10 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Professional Audio Applications Maintainers <proaudio> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | Adrian.Bassett, bearcatsandor, dev, suhr |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-history.txt
media-sound:jack-audio-connection-kit-0.124.1:20160523-050102.log jack-audio-connection-kit-9999-depend-on-Jack2-instead |
Description
Toralf Förster
2016-05-23 07:49:32 UTC
Created attachment 435014 [details]
emerge-history.txt
Created attachment 435016 [details]
media-sound:jack-audio-connection-kit-0.124.1:20160523-050102.log
I don't think it's a good idea to make that jack2 ebuild since many files are the same and there is even a patch to get jackdebus with media-sound/jack-audio-connection-kit:0/1. Why not simply sub-slot with a 0/2 to ease selection? Well, if somebody wants to maintain that jack2 variant... Well, I guess a patch to move the files and setup libs/[lc]flags for pkgconfig will not be that hard? Kind of an unpleasant work. I hope nobody hard code include path, libs and [cl]flags? Pf course it's common. Good luck then! Just my cent, nothing more, nothing less. (In reply to tokiclover from comment #3) > I don't think it's a good idea to make that jack2 ebuild since many files > are the same and there is even a patch to get jackdebus with > media-sound/jack-audio-connection-kit:0/1. Why not simply sub-slot with a > 0/2 to ease selection? Well, if somebody wants to maintain that jack2 > variant... Well, I guess a patch to move the files and setup libs/[lc]flags > for pkgconfig will not be that hard? Kind of an unpleasant work. I hope > nobody hard code include path, libs and [cl]flags? Pf course it's common. > Good luck then! > > Just my cent, nothing more, nothing less. This seems like a prime candidate for depending on a virtual/jack that is satisfied by either media-sound/jack-audio-connection-kit or media-sound/jack2 (In reply to Adrian.Bassett from comment #4) > (In reply to tokiclover from comment #3) > > I don't think it's a good idea to make that jack2 ebuild since many files > > are the same and there is even a patch to get jackdebus with > > media-sound/jack-audio-connection-kit:0/1. Why not simply sub-slot with a > > 0/2 to ease selection? Well, if somebody wants to maintain that jack2 > > variant... Well, I guess a patch to move the files and setup libs/[lc]flags > > for pkgconfig will not be that hard? Kind of an unpleasant work. I hope > > nobody hard code include path, libs and [cl]flags? Pf course it's common. > > Good luck then! > > > > Just my cent, nothing more, nothing less. > > This seems like a prime candidate for depending on a virtual/jack that is > satisfied by either media-sound/jack-audio-connection-kit or > media-sound/jack2 And, indeed, there is one ... A quick check suggests that jack2 blocks jack-audio-connection-kit but that the latter doesn't block jack2 So far, the ebuilds that i've changed "jack? ( >=media-sound/jack-audio-connection-kit-0.121.3-r1[${MULTILIB_USEDEP}] )" to "jack? ( >=virtual/jack-0[${MULTILIB_USEDEP}] )" have worked. Why can't someone just do a sed on this and replace the former with the latter? I ran into this problem. I had jack-audio-connection kit installed and needed to install jack2 due to a BitWig Studio dependency. It can't be done. Had to remove jack-audio-connection-kit entirely (and the flag, which meant recompiling every related package) so I could have BitWig running. Maybe the virtual should let you decide if you want jack1 or jack2, right? OK, it seems that some packages are not using virtual/jack properly: # emerge -ajuDN @world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] media-sound/jack-audio-connection-kit-0.125.0 USE="alsa pam (-altivec) (-coreaudio) -debug -doc -examples -oss" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="3dnow sse" [ebuild R ] media-libs/aubio-0.4.3 USE="jack*" [ebuild N ] media-plugins/gst-plugins-jack-1.8.3 ABI_X86="32 (64) (-x32)" [ebuild R ] media-libs/slv2-0.6.6-r1 USE="jack*" [ebuild R ] media-plugins/libvisual-plugins-0.4.0-r3 USE="jack*" [ebuild R ] media-sound/ardour-5.3 USE="jack*" [ebuild R ] media-sound/pulseaudio-9.0 USE="jack*" [ebuild R ] media-libs/openal-1.17.2 USE="jack*" [ebuild R ] media-video/ffmpeg-2.8.8 USE="jack*" [ebuild R ] media-sound/timidity++-2.14.0-r2 USE="jack*" [ebuild R ] media-plugins/alsa-plugins-1.1.1 USE="jack*" [ebuild R ] media-video/mpv-0.22.0 USE="jack*" [ebuild R ] media-sound/audacity-2.0.5-r1 USE="jack*" [ebuild R ] media-video/vlc-2.2.4 USE="jack*" [ebuild R ] media-plugins/gst-plugins-meta-1.8.3 USE="jack*" Also, on IRC, infirit said: 14:04 < infirit> Renich, ok, I see now. At least media-libs/aubio does not properly use the virtual 14:10 < infirit> Renich, you will want to do you own ebuild and update the deps 14:13 < infirit> Renich, no. You need to replace all references to "media-sound/jack-audio-connection-kit" with "virtual/jack" Now, my question is... how do I contact all package owners to deal with this? I am having the same issue. Even with the minimal USE flag set to mailutils. Ah, disregard my comment. Wrong issue ID. Created attachment 460246 [details]
jack-audio-connection-kit-9999-depend-on-Jack2-instead
Work-around ebuild to allow Jack1 depending ebuilds install, even though Jack2 is really being installed.
Work-around for applications which depend on Jack1, but wanting Jack2 installed. Fake ebuild of jack-audio-connection-kit-9999 that depends on Jack2. Local Repository: 1. Add to /etc/portage/make.conf PORTDIR_OVERLAY="/usr/local/portage/ ${PORTDIR_OVERLAY}" 2. Make directory /usr/local/portage/metadata 3. echo "masters = gentoo" >> /usr/local/portage/metadata/layout.conf 4. chown -R portage:portage /usr/local/portage/ Add Fake Ebuild to Local Repository: 1. Download jack-audio-connection-kit-9999-depend-on-Jack2-instead 2. Make directory /usr/local/portage/media-sound/jack-audio-connection-kit 3. cd ~/Downloads or wherever jack-audio-connection-kit-9999-depend-on-Jack2-instead was downloaded to 3. cp ./jack-audio-connection-kit-9999-depend-on-Jack2-instead /usr/local/portage/media-sound/jack-audio-connection-kit/jack-audio-connection-kit-9999 4. echo "=media-sound/jack-audio-connection-kit-9999 ~amd64" >> /etc/portage/package.keywords/jack2 5. chown -R portage:portage /usr/local/portage/ 6. emerge =media-sound/jack-audio-connection-kit-9999 You should now be able to install any ebuild which has a dependency on jack1 while having jack2 installed. I have another ebuild which fixes the problem of only being able to install jackd audio server or jackdbus. The ebuild can install both with an additional use flag. I will post a link to that bug here (as a reply) once I submit it. NOTE: THIS IS TEMPORARY! Use at your own risk. step 7: ebuild media-sound/jack-audio-connection-kit-9999.ebuild metadata Ebuild Enhancement - dbus-and-jackd flag to install both: https://bugs.gentoo.org/show_bug.cgi?id=605834 irc is not a tool that I use. It would be nice if there were an online forum or even a website irc shim. I will let someone else hold the torch if this needs discussed on irc. Renich Bon Ciric - Thank you for the hard work! When virtual/jack is being depended upon by the apps you have listed, the hack above won't be useful. WTF is this mess with Jack? Why are these changes in the main tree with no mask before the packages are fixed? I think this has effectively become a duplicate of https://bugs.gentoo.org/show_bug.cgi?id=602898 ? The only thing left to do regarding this issue is that jack-audio-connection-kit should block jack2, correct? $summary fixed by commit 23b43634f4e6670b3fa15e0393cc3992b4a2e27b, if there is anything else of value in this bug not related to file collisions, please report in a separate bug. |