I have my home project, indeed, but I confess it only has served for experimentation with the openSUSE build service yet. I'll look forward to it and do try to make up a repository as you ask.
Thanks for the link. I see there's no JACK2 in there yet :(
I tried building JACK2 in my home project a while back and had no success. Just now I tried using your rpms and sadly had no success there either. There seems to be some conflict with the default installed libjack.109. I'm getting the following error on trying to start jack with qjackctl
/usr/bin/jackd: error while loading shared libraries: libjackserver.so.0: cannot open shared object file: No such file or directory
Is there a particular process you follow for installing JACK2?
I guess you can have only one, either libjack or libjack2. I'll have to uninstall (rpm -e --nodeps) all your current jack and libjack packages and then replace them with jack2 and libjack2 ones.
hmm. if I uninstall libjack, yast complains everytime i try to install or upgrade any jack enabled app. so i just went back to installing jack 0.116 rpms, deleting the files and then compiling JACK2 from source. messy, but at least it works. So I can't use your rpms for now. thanks for providing though!
The way to go is uninstalling libjack via rpm -e with --nodeps and possibly --force options and then install libjack2 immediately after. That will shut up the complaints from installed jack apps. OTOH, having more than one version of libjack lying around (eg. one under /usr and the other under /usr/local) is prone to a plenty of nasty problems, the least of it is having a broken jack ecosystem. Make yourself a favor and don't.
I'm setting up another machine soon so I'll try that route. On this machine there's no trace of the 0.116 JACK left as I used the YAST file list to find and delete everything from those rpms, just leaving the rpms there to satisfy dependencies and then locking them to ensure the files don't get reinstalled. But, as you say, if I can have the correct rpms installed it would be much better. I'll let you know how it goes. Thanks again.
Re: openSUSE build service
I have my home project, indeed, but I confess it only has served for experimentation with the openSUSE build service yet. I'll look forward to it and do try to make up a repository as you ask.
Thanks for the heads up.
Cheers
Thanks for the link. I see
Thanks for the link. I see there's no JACK2 in there yet :(
I tried building JACK2 in my home project a while back and had no success. Just now I tried using your rpms and sadly had no success there either. There seems to be some conflict with the default installed libjack.109. I'm getting the following error on trying to start jack with qjackctl
/usr/bin/jackd: error while loading shared libraries: libjackserver.so.0: cannot open shared object file: No such file or directoryIs there a particular process you follow for installing JACK2?
Re: JACK2 rpms
I guess you can have only one, either libjack or libjack2. I'll have to uninstall (rpm -e --nodeps) all your current jack and libjack packages and then replace them with jack2 and libjack2 ones.
Cheers
hmm. if I uninstall libjack,
hmm. if I uninstall libjack, yast complains everytime i try to install or upgrade any jack enabled app. so i just went back to installing jack 0.116 rpms, deleting the files and then compiling JACK2 from source. messy, but at least it works. So I can't use your rpms for now. thanks for providing though!
Re: if I uninstall libjack...
The way to go is uninstalling libjack via rpm -e with --nodeps and possibly --force options and then install libjack2 immediately after. That will shut up the complaints from installed jack apps. OTOH, having more than one version of libjack lying around (eg. one under
/usrand the other under/usr/local) is prone to a plenty of nasty problems, the least of it is having a broken jack ecosystem. Make yourself a favor and don't.Cheers
I'm setting up another
I'm setting up another machine soon so I'll try that route. On this machine there's no trace of the 0.116 JACK left as I used the YAST file list to find and delete everything from those rpms, just leaving the rpms there to satisfy dependencies and then locking them to ensure the files don't get reinstalled. But, as you say, if I can have the correct rpms installed it would be much better. I'll let you know how it goes. Thanks again.
Post new comment