15 Dec
2008
15 Dec
'08
12:12 p.m.
Hi :)
I added what I did below chronologically arranged. The first try failed
because of Packman libs. The second try failed because of less Packman
libs too.
I don't know what to install and then how to use ldconfig. When I last
tried to remove the whole studio in the box, by removing or first
install and then removing jack by zypper it failed.
I installed jack by YaST2 from repo-oss.
I don't know what to do. I can't install or remove jack, all because I
upgraded from the repo-oss version 0.109 to the Packman's version 0.116.
Cheers,
Ralf
------------------------------------------------------------------------
------------------------------------------------------------------------
FIRST TRY
PACKMAN PROBLEM
spinymouse@suse11:/usr/src/packages/RPMS/x86_64> wget
http://www.sonarnerd.net/suse11/jack-0.116.1-16.jl.suse.x86_64.rpm
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # rpm -iv
jack-0.116.1-16.jl.suse.x86_64.rpm
error: Failed dependencies:
libcap is needed by jack-0.116.1-16.jl.suse.x86_64
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # zypper install libcap
Downloading repository 'Packman Repository' metadata [done]
Building repository 'Packman Repository' cache [done]
Reading installed packages...
The following NEW package is going to be installed:
libcap1
Overall download size: 8.0 K. After the operation, additional 16.0 K
will be used.
Continue? [YES/no]: y
Downloading package libcap1-1.10-10.1.x86_64 (1/1), 8.0 K (16.0 K unpacked)
Downloading: libcap1-1.10-10.1.x86_64.rpm [done]
Installing: libcap1-1.10-10.1 [done]
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # rpm -iv
jack-0.116.1-16.jl.suse.x86_64.rpm
Preparing packages for installation...
file /usr/lib64/libjackserver.so.0 from install of
jack-0.116.1-16.jl.suse conflicts with file from package
libjackserver2-0-1.9.0-0.pm.4
file /usr/lib64/libjack.so.0 from install of
jack-0.116.1-16.jl.suse conflicts with file from package
libjack2-0-1.9.0-0.pm.4
file /usr/bin/jack_freewheel from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_load from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_transport from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_unload from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jackd from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/inprocess.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_alsa.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_dummy.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_net.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/alsa_in from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/alsa_out from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_freewheel from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_load from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_netsource from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_transport from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jack_unload from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/bin/jackd from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/inprocess.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/intime.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/jack_alsa.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/jack_dummy.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/jack_net.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
file /usr/lib64/jack/jack_oss.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack-0.116.1-0.pm.1
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # zypper rm jack
Reading installed packages...
The following packages are going to be downgraded:
lash jaaa hydrogen gstreamer-0_10-plugins-bad-lang
gstreamer-0_10-plugins-bad
The following packages are going to be REMOVED:
tuneit tap-reverbed soundtank snd-ls san-dysth rtsynth rezound
qtractor qsampler
qjacklam python-lash phasex perl-Audio-Ardour-Control mx44 lash-devel klick
kde4-kdenlive jconv jamin jacktube jackmixdesk-gui jackmixdesk jackmix
jackmeter
jackmaster jackbeat jack_snapshot jack_mixer jack_capture jackEQ jack2
jack-rack jack
guitarix gmidimonitor gigedit-linuxsampler-plugin fmit mhwaveedit
linuxsampler
ecasound ecamegapedal dssi-calf didgeridoo calf bristol-debugsource
bristol-debuginfo
bristol audicle ardour2 alsa-patch-bay LiVES
The following packages are going to change vendor:
lash jaaa hydrogen gstreamer-0_10-plugins-bad-lang
gstreamer-0_10-plugins-bad
Overall download size: 3.5 M. After the operation, 91.1 M will be freed.
Continue? [YES/no]: n
------------------------------------------------------------------------
------------------------------------------------------------------------
SECOND TRY
PACKMAN DISABLED & jack & libcap1 REMOVED BY YAST2
suse11:/usr/src/packages/RPMS/x86_64 # zypper install libcap1
Reading installed packages...
The following NEW package is going to be installed:
libcap1
Overall download size: 8.0 K. After the operation, additional 16.0 K
will be used.
Continue? [YES/no]: y
Downloading package libcap1-1.10-10.1.x86_64 (1/1), 8.0 K (16.0 K unpacked)
Downloading: libcap1-1.10-10.1.x86_64.rpm [done]
Installing: libcap1-1.10-10.1 [done]
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # rpm -iv
jack-0.116.1-16.jl.suse.x86_64.rpm
Preparing packages for installation...
file /usr/lib64/libjackserver.so.0 from install of
jack-0.116.1-16.jl.suse conflicts with file from package
libjackserver2-0-1.9.0-0.pm.4
file /usr/lib64/libjack.so.0 from install of
jack-0.116.1-16.jl.suse conflicts with file from package
libjack2-0-1.9.0-0.pm.4
file /usr/bin/jack_freewheel from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_load from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_transport from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jack_unload from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/bin/jackd from install of jack-0.116.1-16.jl.suse
conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/inprocess.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_alsa.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_dummy.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
file /usr/lib64/jack/jack_net.so from install of
jack-0.116.1-16.jl.suse conflicts with file from package jack2-1.9.0-0.pm.4
------------------------------------------------------------------------
------------------------------------------------------------------------
HOW DO I HAVE TO USE ldconfig?
suse11:/usr/src/packages/RPMS/x86_64 # ldconfig
suse11:/usr/src/packages/RPMS/x86_64 # ldconfig --help
Usage: ldconfig [OPTION...]
Configure Dynamic Linker Run Time Bindings.
-c, --format=FORMAT Format to use: new, old or compat (default)
-C CACHE Use CACHE as cache file
-f CONF Use CONF as configuration file
-i, --ignore-aux-cache Ignore auxiliary cache file
-l Manually link individual libraries.
-n Only process directories specified on the
command
line. Don't build cache.
-N Don't build cache
-p, --print-cache Print cache
-r ROOT Change to and use ROOT as root directory
-v, --verbose Generate verbose messages
-X Don't generate links
-?, --help Give this help list
--usage Give a short usage message
-V, --version Print program version
Mandatory or optional arguments to long options are also mandatory or
optional
for any corresponding short options.
------------------------------------------------------------------------
------------------------------------------------------------------------
REMOVING THE STUDIO IN THE BOX, EXCEPTED qjackctl THAT IS A NON-RPM
INSTALL, BY REMOVING jack BY zypper
suse11:/usr/src/packages/RPMS/x86_64 # zypper rm jack
Reading installed packages...
'jack' is not installed.
Nothing to do.
suse11:/usr/src/packages/RPMS/x86_64 # zypper install jack
Reading installed packages...
Nothing to do.
------------------------------------------------------------------------
AFTER I INSTALLED jack BY YAST2 FROM THE REPO-OSS
suse11:/usr/src/packages/RPMS/x86_64 # jackd --help
jackd: error while loading shared libraries: libjack.so.0: cannot open
shared object file: No such file or directory
------------------------------------------------------------------------
suse11:/usr/src/packages/RPMS/x86_64 # zypper rm jackd
Reading installed packages...
'jackd' not found.
Nothing to do.
suse11:/usr/src/packages/RPMS/x86_64 # ldconfig
suse11:/usr/src/packages/RPMS/x86_64 # zypper rm jackd
Reading installed packages...
'jackd' not found.
Nothing to do.
15 Dec
15 Dec
12:58 p.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
Am Montag, 15. Dezember 2008 schrieb Ralf Mardorf:
Hi :)
I added what I did below chronologically arranged. The first try failed
because of Packman libs. The second try failed because of less Packman
libs too.
I don't know what to install and then how to use ldconfig. When I last
tried to remove the whole studio in the box, by removing or first
install and then removing jack by zypper it failed.
you can't do it this way ...
first note: rpm -i is totally wrong here., you don't want to install you want
to do a upgrade or downgrade.
second note: you need a package-manager to resolve this problem :)
explantation:
jack and jack2 are providing the same "functionality", so you have to make a
choice which package-family you want to use.
possibility a) install jack, libjack0 and libjackserver0 ==> 0.116.x
possibility b) install jack2, libjack2-0 and libjackserver2-0 ==> 1.9.x
Those two package-families are mutual exclusive.
According the openSuSE shared library policy all shared libs are splitted out
in seperate packages with the so-name in the package name.
if you pull in the mentioned package from http://www.sonarnerd.net/suse11/
you need additional steps, as these package doesn't follow the original SuSE
packages. It contains the binaries and the libs without obsoleting/requiring
other packages. And it need libcapX as it is configured to use libcap. The
SuSE packages and the packman packages don't use this option.
This package can only be installed with a
rpm -e --nodeps <all installed jack-packages> (get a list with rpm -qa | grep
jack) and the install this special jack package with rpm -Uhv ...
I installed jack by YaST2 from repo-oss.
I don't know what to do. I can't install or remove jack, all because I
upgraded from the repo-oss version 0.109 to the Packman's version 0.116.
btw,
you are the only person with install problems with the packman packages.
I think I know the reason know, please use your package-manager to
install/deinstall/upgrade your packages. And always refresh your
package-cache before doing such operations.
If you still have problems to install the packman packages, post your problems
to our mailing list and or cc me (I've packaged those packages for packman)
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Cheers,
Ralf
<snip>
have fun
oc2pus
1:26 p.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de wrote:
He? If you will ignore the links to Ardour and google search,than I'm
the only one. Will you go on with the Linux-Club bashes?
you can't do it this way ...
first note: rpm -i is totally wrong here., you don't want to install you want
to do a upgrade or downgrade.
second note: you need a package-manager to resolve this problem :)
explantation:
jack and jack2 are providing the same "functionality", so you have to make a
choice which package-family you want to use.
possibility a) install jack, libjack0 and libjackserver0 ==> 0.116.x
possibility b) install jack2, libjack2-0 and libjackserver2-0 ==> 1.9.x
Those two package-families are mutual exclusive.
According the openSuSE shared library policy all shared libs are splitted out
in seperate packages with the so-name in the package name.
if you pull in the mentioned package from http://www.sonarnerd.net/suse11/
you need additional steps, as these package doesn't follow the original SuSE
packages.
I first had a 0.109 install from the repo-oss. I upgraded by YaST2 to
0.116 from the Packman Repo and got the same as a lot of people got, see
http://ardour.org/node/2271.
Some steps followed, see
* [LAD] JACK for openSUSE 11.0 x86_64
<http://lalists.stanford.edu/lad/2008/12/0047.html> /Ralf
Mardorf/ /(Sun Dec 14 2008 - 21:29:57 EET)/
o Re: [LAD] JACK for openSUSE 11.0 x86_64
<http://lalists.stanford.edu/lad/2008/12/0048.html>
/torbenh@email-addr-hidden/ /(Sun
Dec 14 2008 - 21:37:10 EET)/
+ Re: [LAD] [Jack-Devel] JACK for openSUSE 11.0 x86_64
<http://lalists.stanford.edu/lad/2008/12/0049.html> /Ralf
Mardorf/ /(Mon Dec 15 2008 - 02:23:07 EET)/
There seems to be a bug for the jack Packman's package since my last
upgrade, that was done with OSS, NON-OSS, UPDATES, PACKMAN and yes, also
VIDEOLAN. I did the upgrade, resp. "update all packeges if newer version
is available" (I'm writing from Lenny, but I guess you know which option
I'm talking about, I don't know the exact words by heard) at 12-14-2008
18:36.
After I've done some installs and deinstalls, I tried to install the
RPM, it might be, that 0.116 was installed again, when I run RPM the
first time, to install Jussi's version, anyway, Suse was broken before.
It contains the binaries and the libs without
obsoleting/requiring
other packages. And it need libcapX as it is configured to use libcap. The
SuSE packages and the packman packages don't use this option.
This package can only be installed with a
rpm -e --nodeps <all installed jack-packages> (get a list with rpm -qa | grep
jack) and the install this special jack package with rpm -Uhv ...
To avoid a misunderstanding. This is for Jussi's package, am I right?
What wrong with the Packman's package? Is there a way to use this?
I installed
jack by YaST2 from repo-oss.
I don't know what to do. I can't install or remove jack, all because I
upgraded from the repo-oss version 0.109 to the Packman's version 0.116.
btw, you are the only person with install problems with the packman packages.
I think I know the reason know, please use your
package-manager to
install/deinstall/upgrade your packages. And always refresh your
package-cache before doing such operations.
That has broken Suse, read the mails.
If you still have problems to install the packman
packages, post your problems
to our mailing list and or cc me (I've packaged those packages for packman)
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Why, you always ignored what I was writing. You can read all messages
here in the LAD mailing list archive.
Cheers,
Ralf
1:35 p.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
9:47 p.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
On Mon, Dec 15, 2008 at 06:26:49PM +0100, Ralf Mardorf wrote:
oc2pus(a)arcor.de wrote:
just install a self built source OVER the stuff from the package.
and then run ldconfig as root.
there is no "i dont know how to use ldconfig"
it just does its thing. you dont need to give it options,
or interact with it. you just need to start it.
after it ran you can use the installed jackd.
i am really sorry, but you are making it very hard to help you.
you can't do it this way ...
first note: rpm -i is totally wrong here., you don't want to install you want
to do a upgrade or downgrade.
second note: you need a package-manager to resolve this problem :)
explantation:
jack and jack2 are providing the same "functionality", so you have to make a
choice which package-family you want to use.
possibility a) install jack, libjack0 and libjackserver0 ==> 0.116.x
possibility b) install jack2, libjack2-0 and libjackserver2-0 ==> 1.9.x
Those two package-families are mutual exclusive.
According the openSuSE shared library policy all shared libs are splitted out
in seperate packages with the so-name in the package name.
if you pull in the mentioned package from http://www.sonarnerd.net/suse11/
you need additional steps, as these package doesn't follow the original SuSE
packages.
I first had a 0.109 install from the repo-oss. I upgraded by YaST2 to
0.116 from the Packman Repo and got the same as a lot of people got, see
http://ardour.org/node/2271.
Some steps followed, see
* [LAD] JACK for openSUSE 11.0 x86_64
<http://lalists.stanford.edu/lad/2008/12/0047.html> /Ralf
Mardorf/ /(Sun Dec 14 2008 - 21:29:57 EET)/
o Re: [LAD] JACK for openSUSE 11.0 x86_64
<http://lalists.stanford.edu/lad/2008/12/0048.html>
/torbenh@email-addr-hidden/ /(Sun
Dec 14 2008 - 21:37:10 EET)/
+ Re: [LAD] [Jack-Devel] JACK for openSUSE 11.0 x86_64
<http://lalists.stanford.edu/lad/2008/12/0049.html> /Ralf
Mardorf/ /(Mon Dec 15 2008 - 02:23:07 EET)/
Why, you always ignored what I was writing. You can read all messages
here in the LAD mailing list archive.
random up and downgrading, and mixing several repos is very likely
to break your system.
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
10:02 p.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
torbenh(a)gmx.de wrote:
just install a self built source OVER the stuff from
the package.
and then run ldconfig as root.
there is no "i dont know how to use ldconfig"
it just does its thing. you dont need to give it options,
or interact with it. you just need to start it.
after it ran you can use the installed jackd.
i am really sorry, but you are making it very hard to help you.
Thank You :)
I hope this will help.
random up and downgrading, and mixing several repos is
very likely
to break your system.
It broke by an upgrade from repo-oss 0.109 to Packman 0.116, when it was
broken I tried to downgrade and then I removed libs like it was written
on the Ardour homepage and after that I tried to install Jussi's RPM,
but at the beginning I didn't mix anything. It's a pure OSS, NON-OSS,
UPDATES, PACKMAN and VIDEOLAN Suse with 3 or 4 self compiled
applications, I'm not mixing anything randomly for this install. Okay, I
might not use VIDEOLAN, but that is the only critical repository.
Cheers,
Ralf
16 Dec
16 Dec
2:58 a.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
Am Dienstag, 16. Dezember 2008 schrieb torbenh(a)gmx.de:
<snip>
just install a self built source OVER the stuff from
the package.
and then run ldconfig as root.
but use ./configure --prefix=/usr in the configure
step !
otherwise your installation will be installed in /usr/local instead of /usr
and a new round of problems will start.
<snip>
have fun
oc2pus
10:39 a.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
Hi Oc2pus :)
I'm sorry that I boiled over.
Am Dienstag, 16. Dezember 2008 schrieb
torbenh(a)gmx.de:
<snip>
The Release date for openSUSE 11.1 still is the 12-18-2008. If I will
have the time, I'll try to fix my 11.0, just to learn what to do, if
something like that happens, but I decided to delete my 11.0, the 11.0
backup the and the 11.1 RC and to install the 11.1. I only will keep the
/homes of 11.0 and 11.1 RC. I guess I can use he /home of 11.1 RC for my
11.1 without trouble.
I'm not sure if I'll use the 64bit version again. There is a kernel vs
hardware issue for 64bit hardware (for any distro). Probably it won't
help to run 32bit on 64bit hardware, but nobody seems to know this.
It seems to be that (what for some people means really) stable for 64bit
hardware needs realtime kernels 2.6.21 and 2.6.22, while for 32bit
hardware even kernel 2.6.26 now might be fine.
Cheers,
Ralf
just install a self built source OVER the stuff
from the package.
and then run ldconfig as root.
but use ./configure --prefix=/usr in the configure step !
otherwise your installation will be installed in /usr/local instead of /usr
and a new round of problems will start.
15 Dec
15 Dec
1:58 p.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
If you are interested in solving what's going wrong Oc2pus, here is the
calumet.
A resume:
I booted Suse 11.0
Launched YaST2, Install Software and upgraded all packages
jackd 0.109 from OSS was replaced by jackd 0.116 from a PACKMAN-mirror
Right after this, jackd was broken. Suse 11.0 is a clean install, there
might be some LADSPA self compiled and definitive QjackCtl is self
compiled, nothing else should be from any other source, but OSS,
NON-OSS, UPDATES, PACKMAN and VIDEOLAN.
YaST2 says that all dependencies are fine.
2:16 p.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
Am Montag, 15. Dezember 2008 schrieb Ralf Mardorf:
If you are interested in solving what's going
wrong Oc2pus, here is the
calumet.
A resume:
I booted Suse 11.0
Launched YaST2, Install Software and upgraded all packages
jackd 0.109 from OSS was replaced by jackd 0.116 from a PACKMAN-mirror
Right after this, jackd was broken. Suse 11.0 is a clean install, there
might be some LADSPA self compiled and definitive QjackCtl is self
compiled, nothing else should be from any other source, but OSS,
NON-OSS, UPDATES, PACKMAN and VIDEOLAN.
YaST2 says that all dependencies are fine.
please post the output of
rpm -qa | grep jack
have fun
oc2pus
2:48 p.m.
New subject: [Jack-Devel] JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de wrote:
Am Montag, 15. Dezember 2008 schrieb Ralf Mardorf:
I guess one archives mailing list at this point is enough for this, we
should it sent only to LAD or jack-dev or go on off-list.
Oops, I just rebooted from Lenny to Suse and back to Lenny.
Now I have to go shopping, I'll boot Suse and run rpm -qa | grep jack
when I'm back, this might take one hour or more.
Just to rule out I did this stupid check:
This is the mirror YaST2 used: http://ftp.skynet.be/pub/packman/suse/11.0/
Today it's equal to another server, maybe it was also equal, when I run
the upgrade.
spinymouse@suse11:~> mkdir diff
spinymouse@suse11:~> wget
http://ftp.skynet.be/pub/packman/suse/11.0/x86_64/jack-0.116.1-0.pm.1.x86_6…
--2008-12-15 19:26:13--
http://ftp.skynet.be/pub/packman/suse/11.0/x86_64/jack-0.116.1-0.pm.1.x86_6…
Resolving ftp.skynet.be... 195.238.1.7
Connecting to ftp.skynet.be|195.238.1.7|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 112723 (110K) [application/x-redhat-package-manager]
Saving to: `jack-0.116.1-0.pm.1.x86_64.rpm'
100%[=================================================================================>]
112,723 428K/s in 0.3s
2008-12-15 19:26:13 (428 KB/s) - `jack-0.116.1-0.pm.1.x86_64.rpm' saved
[112723/112723]
spinymouse@suse11:~> cd diff
spinymouse@suse11:~/diff> wget
http://packman.jacobs-university.de/suse/11.0/x86_64/jack-0.116.1-0.pm.1.x8…
--2008-12-15 19:26:44--
http://packman.jacobs-university.de/suse/11.0/x86_64/jack-0.116.1-0.pm.1.x8…
Resolving packman.jacobs-university.de... 212.201.44.24
Connecting to packman.jacobs-university.de|212.201.44.24|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 112723 (110K) [application/x-rpm]
Saving to: `jack-0.116.1-0.pm.1.x86_64.rpm'
100%[=================================================================================>]
112,723 128K/s in 0.9s
2008-12-15 19:26:45 (128 KB/s) - `jack-0.116.1-0.pm.1.x86_64.rpm' saved
[112723/112723]
spinymouse@suse11:~/diff> diff jack-0.116.1-0.pm.1.x86_64.rpm
~/jack-0.116.1-0.pm.1.x86_64.rpm
spinymouse@suse11:~/diff> ce ..
bash: ce: command not found
spinymouse@suse11:~/diff> cd..
spinymouse@suse11:~> rm -r diff jack-0.116.1-0.pm.1.x86_64.rpm
spinymouse@suse11:~>
If you are interested in solving what's going
wrong Oc2pus, here is the
calumet.
A resume:
I booted Suse 11.0
Launched YaST2, Install Software and upgraded all packages
jackd 0.109 from OSS was replaced by jackd 0.116 from a PACKMAN-mirror
Right after this, jackd was broken. Suse 11.0 is a clean install, there
might be some LADSPA self compiled and definitive QjackCtl is self
compiled, nothing else should be from any other source, but OSS,
NON-OSS, UPDATES, PACKMAN and VIDEOLAN.
YaST2 says that all dependencies are fine.
please post the output of
rpm -qa | grep jack
have fun
oc2pus
6:05 p.m.
New subject: JACK for openSUSE 11.0 x86_64
Hi Oc2pus :)
here is the information I got by rpm, I also checked jack only and
dependencies by YaST2 and added the stuff that's unknown by the package
management and including jack in it's name.
oc2pus(a)arcor.de wrote:
please post the output of
rpm -qa | grep jack
suse11:/home/spymo # yast2 --install
System dependencies verify OK.
All package dependencies are OK.
jack 0.109.2-36.1-x86_64 is isntalled
jack-32bit isn't installed
jack2 1.9.0-0.pm.4-x86_64 is installed
suse11:/home/spymo # exit
spinymouse@suse11:~> rpm -qa | grep jack
jack_mixer-6-0.pm.3
jackmeter-0.3-0.pm.1
libjack2-0-1.9.0-0.pm.4
jack_snapshot-0.0.3-0.pm.1
jackbeat-0.6.3-0.pm.1
jacktube-0.20-0.pm.1
libjackserver2-0-1.9.0-0.pm.4
jackEQ-0.4.1-0.pm.2
jackmixdesk-0.3-112.pm.svn20070530
jack_capture-0.9.31-0.pm.1
jack-scope-20080627-0.pm.1
libjack-devel-0.116.1-0.pm.1
jackmix-0.4-0.pm.1
qjacklam-0.3-0.pm.2
jack-0.109.2-36.1
jackmixdesk-gui-0.3-112.pm.svn20070530
jackmaster-0.0.1-0.pm.1
jack-rack-1.4.7-68.1
libjack0-32bit-0.109.2-36.1
jack2-1.9.0-0.pm.4
spinymouse@suse11:~> ls -l /usr/local/bin
total 1496
-rwxr-xr-x 1 root root 246832 2008-10-13 22:55 non-daw
-rwxr-xr-x 1 root root 191408 2008-10-13 22:59 non-sequencer
-rwxr-xr-x 1 root root 1074368 2008-10-12 02:05 qjackctl
Self compiled and make install instead of checkinstall, because
checkinstall doesn't work, since I have 64-bit hardware. Qjackctl seems
to be cvs version 0.3.3.6 and because of the make install, it's not
known by the packet management.
The latest rsync of Suse 11.0 is from ...
spinymouse@suse11:~> ls -l /mnt/backup_space_i
[snip]
drwxr-xr-x 21 spinymouse 1000 4096 2008-08-19 10:27 tmp_suse11.0-19-08-2008
... so I would prefer to get it repaired, instead of restoring it from
that backup.
Cheers,
Ralf
7:09 p.m.
New subject: JACK for openSUSE 11.0 x86_64
Am Montag, 15. Dezember 2008 schrieb Ralf Mardorf:
Hi Oc2pus :)
here is the information I got by rpm, I also checked jack only and
dependencies by YaST2 and added the stuff that's unknown by the package
management and including jack in it's name.
oc2pus(a)arcor.de wrote:
> please post the output of
> rpm -qa | grep jack
spinymouse@suse11:~> rpm -qa | grep jack
jackmeter-0.3-0.pm.1
libjack2-0-1.9.0-0.pm.4 <================
jack_snapshot-0.0.3-0.pm.1
jackbeat-0.6.3-0.pm.1
jacktube-0.20-0.pm.1
libjackserver2-0-1.9.0-0.pm.4 <=============
jackEQ-0.4.1-0.pm.2
jackmixdesk-0.3-112.pm.svn20070530
jack_capture-0.9.31-0.pm.1
jack-scope-20080627-0.pm.1
libjack-devel-0.116.1-0.pm.1 <======
jackmix-0.4-0.pm.1
qjacklam-0.3-0.pm.2
jack-0.109.2-36.1 <======= NOT A PACKMAN PACKAGE
jackmixdesk-gui-0.3-112.pm.svn20070530
jackmaster-0.0.1-0.pm.1
jack-rack-1.4.7-68.1
libjack0-32bit-0.109.2-36.1 <=========
jack2-1.9.0-0.pm.4 <=======
I marked them with <====
your system is borked, yo have a total mixture of jack2 and jack
even 32bit variants in your system...
this can't work,never ever :)
you need
jack2, libjackserver2-0 libjack2-0
OR
jack, libjackserver0, libjackserver0
don't know how you managed to reach this installation mixture.
But if it helps you, you can continue to write in all your known
communities:
<sarkasm mode on>
its ALWAYS the packager's mistake! and those packages are totally borked...
</sarkasm mode off>
A tip from me: simply try gentoo, than YOU are the master of installing and
compiling things. And if things won't work as expected, grab your own nose
and yell around :)
Cheers,
Ralf
9:16 p.m.
New subject: JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de wrote:
Am Montag, 15. Dezember 2008 schrieb Ralf Mardorf:
I just wrote about a bug, I never said that it's a sin to produce bugs,
I produce bugs myself, but here I just installed and removed jack
packages by YaST and at a later point by zypper. Because you guess that
you are god, I won't report it to you. Sorry, my mental disorders
differs to the once you have got. Please, don't care about my mails and
postings. It's wasting time, we don't have enough in common to
correspond about those things. I never installed jack2 by myself, it was
installed as a dependency to jack. I can try to force, to remove jack2,
libjackserver2-0, libjack2-0 and to install jack, libjackserver0, but
the problem seems to be, that YaST and zypper aren't able to do this any
more. I'm fine with Suse and Debian, but I'm not fine with people like
you. I don't understand what's the problem with this. You don't need to
write me your opinions, if you think that I'm faking bugs, let the
people know that I'm a liar. I distinctly declared that I won't report
bugs to some people. I like to help people that are using Suse and I
like to get help. Maybe you should engage the services of Gentoo, if you
don't like Suse users. It all started with 2 bugs I reported by details
at Linux-Club, than I had to declare what my needs about a tool like
Linux are. I stoped this conversation at Linux-Club and you are
stalking. YOU DON'T NEED TO WRITE TO ME! I don't wish to have a
discussion about different Linux-World-Views. And if you answer people,
not only here, please read what they have written. Yes, as I've written,
jack-0.109.2-36.1 is from repo-oss, maybe because I tried to downgrade
to this package, perhaps I have written that. Will it be fine for you if
I declare, that I'm totally wrong and you are god?
I JUST NEED HELP, BECAUSE I DON'T KNOW SOME THINGS, I DON'T NEED
ACIDNESS! You are a stalker, don't follow me.
Hi Oc2pus :)
here is the information I got by rpm, I also checked jack only and
dependencies by YaST2 and added the stuff that's unknown by the package
management and including jack in it's name.
oc2pus(a)arcor.de wrote:
> please post the output of
> rpm -qa | grep jack
>
spinymouse@suse11:~> rpm -qa | grep jack
jackmeter-0.3-0.pm.1
libjack2-0-1.9.0-0.pm.4 <================
jack_snapshot-0.0.3-0.pm.1
jackbeat-0.6.3-0.pm.1
jacktube-0.20-0.pm.1
libjackserver2-0-1.9.0-0.pm.4 <=============
jackEQ-0.4.1-0.pm.2
jackmixdesk-0.3-112.pm.svn20070530
jack_capture-0.9.31-0.pm.1
jack-scope-20080627-0.pm.1
libjack-devel-0.116.1-0.pm.1 <======
jackmix-0.4-0.pm.1
qjacklam-0.3-0.pm.2
jack-0.109.2-36.1 <======= NOT A PACKMAN PACKAGE
jackmixdesk-gui-0.3-112.pm.svn20070530
jackmaster-0.0.1-0.pm.1
jack-rack-1.4.7-68.1
libjack0-32bit-0.109.2-36.1 <=========
jack2-1.9.0-0.pm.4 <=======
I marked them with <====
your system is borked, yo have a total mixture of jack2 and jack
even 32bit variants in your system...
this can't work,never ever :)
you need
jack2, libjackserver2-0 libjack2-0
OR
jack, libjackserver0, libjackserver0
don't know how you managed to reach this installation mixture.
But if it helps you, you can continue to write in all your known
communities:
<sarkasm mode on>
its ALWAYS the packager's mistake! and those packages are totally borked...
</sarkasm mode off>
A tip from me: simply try gentoo, than YOU are the master of installing and
compiling things. And if things won't work as expected, grab your own nose
and yell around :)
> Cheers,
> Ralf
>
9:57 p.m.
New subject: JACK for openSUSE 11.0 x86_64
On Tue, Dec 16, 2008 at 02:15:59AM +0100, Ralf Mardorf wrote:
oc2pus(a)arcor.de wrote:
i dont understand you.
he pointed out the errors.
and told you how you should fix your system.
he is a bit annoyed, because your saying the packages are broken.
the packages are fine. YOU broke your system.
now fix it.
just remove the offending packages.
read the man page of rpm and remove them.
i guess you need the force option, because you got yourself into
dependency hell.
yast wont help you here.
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
Am Montag, 15. Dezember 2008 schrieb Ralf
Mardorf:
I just wrote about a bug, I never said that it's a sin to produce bugs,
I produce bugs myself, but here I just installed and removed jack
packages by YaST and at a later point by zypper. Because you guess that
you are god, I won't report it to you. Sorry, my mental disorders
differs to the once you have got. Please, don't care about my mails and
postings. It's wasting time, we don't have enough in common to
correspond about those things. I never installed jack2 by myself, it was
installed as a dependency to jack. I can try to force, to remove jack2,
libjackserver2-0, libjack2-0 and to install jack, libjackserver0, but
the problem seems to be, that YaST and zypper aren't able to do this any
more. I'm fine with Suse and Debian, but I'm not fine with people like
you. I don't understand what's the problem with this. You don't need to
write me your opinions, if you think that I'm faking bugs, let the
people know that I'm a liar. I distinctly declared that I won't report
bugs to some people. I like to help people that are using Suse and I
like to get help. Maybe you should engage the services of Gentoo, if you
don't like Suse users. It all started with 2 bugs I reported by details
at Linux-Club, than I had to declare what my needs about a tool like
Linux are. I stoped this conversation at Linux-Club and you are
stalking. YOU DON'T NEED TO WRITE TO ME! I don't wish to have a
discussion about different Linux-World-Views. And if you answer people,
not only here, please read what they have written. Yes, as I've written,
jack-0.109.2-36.1 is from repo-oss, maybe because I tried to downgrade
to this package, perhaps I have written that. Will it be fine for you if
I declare, that I'm totally wrong and you are god?
I JUST NEED HELP, BECAUSE I DON'T KNOW SOME THINGS, I DON'T NEED
ACIDNESS! You are a stalker, don't follow me. Hi Oc2pus :)
here is the information I got by rpm, I also checked jack only and
dependencies by YaST2 and added the stuff that's unknown by the package
management and including jack in it's name.
oc2pus(a)arcor.de wrote:
> please post the output of
> rpm -qa | grep jack
>
spinymouse@suse11:~> rpm -qa | grep jack
jackmeter-0.3-0.pm.1
libjack2-0-1.9.0-0.pm.4 <================
jack_snapshot-0.0.3-0.pm.1
jackbeat-0.6.3-0.pm.1
jacktube-0.20-0.pm.1
libjackserver2-0-1.9.0-0.pm.4 <=============
jackEQ-0.4.1-0.pm.2
jackmixdesk-0.3-112.pm.svn20070530
jack_capture-0.9.31-0.pm.1
jack-scope-20080627-0.pm.1
libjack-devel-0.116.1-0.pm.1 <======
jackmix-0.4-0.pm.1
qjacklam-0.3-0.pm.2
jack-0.109.2-36.1 <======= NOT A PACKMAN PACKAGE
jackmixdesk-gui-0.3-112.pm.svn20070530
jackmaster-0.0.1-0.pm.1
jack-rack-1.4.7-68.1
libjack0-32bit-0.109.2-36.1 <=========
jack2-1.9.0-0.pm.4 <=======
I marked them with <====
your system is borked, yo have a total mixture of jack2 and jack
even 32bit variants in your system...
this can't work,never ever :)
you need
jack2, libjackserver2-0 libjack2-0
OR
jack, libjackserver0, libjackserver0
don't know how you managed to reach this installation mixture.
But if it helps you, you can continue to write in all your known
communities:
<sarkasm mode on>
its ALWAYS the packager's mistake! and those packages are totally borked...
</sarkasm mode off>
A tip from me: simply try gentoo, than YOU are the master of installing and
compiling things. And if things won't work as expected, grab your own nose
and yell around :)
> Cheers,
> Ralf
>
10:12 p.m.
New subject: JACK for openSUSE 11.0 x86_64
torbenh(a)gmx.de wrote:
YOU broke your system.
By doing what? I did an upgrade from 0.109 to 0.116 by YaST, maybe it
wasn't the package, but it also wasn't me. I just clicked to upgrade it
from the repo-oss to the Packman version, from that point on it was
broken. I might have done wrong things after that, because I read stuff
from the web, e.g. the Ardour link. If I don't have knowledge I have to
read and to ask, I just reported and asked, and get acidness.
just remove the offending packages.
read the man page of rpm and remove them.
i guess you need the force option
Okay, I'll resume:
1. RPM force option to remove the offending Packages
2. install from the source (or try Packman again or try Jussi's RPM +
dependency, all should work)
3. run ldconfig
16 Dec
16 Dec
1:01 a.m.
New subject: JACK for openSUSE 11.0 x86_64
Ralf Mardorf wrote:
While I was tired, I tried to install jack, okay, --force seems to be
the wrong option and I've forgotten to run ldconfig, see terminal_1.txt.
Then I tried to erase the jack2 stuff, but everything depends to it, I
removed the jack stuff instead, because there were no dependency
conflicts. Than I --replaced jack2, run ldconfig, but nothing changed,
see terminal_2.txt and ignore the OT statements, they are remarks for me.
Today I might not be able to spend time in Suse Linux. I've to work.
I'll take look at man rpm and will search the net ASAP.
suse11:~ # rpm -qa | grep jack
jack_mixer-6-0.pm.3
jackmeter-0.3-0.pm.1
libjack2-0-1.9.0-0.pm.4
jack_snapshot-0.0.3-0.pm.1
jackbeat-0.6.3-0.pm.1
jacktube-0.20-0.pm.1
libjackserver2-0-1.9.0-0.pm.4
jackEQ-0.4.1-0.pm.2
jackmixdesk-0.3-112.pm.svn20070530
jack_capture-0.9.31-0.pm.1
jack-scope-20080627-0.pm.1
libjack-devel-0.116.1-0.pm.1
jackmix-0.4-0.pm.1
qjacklam-0.3-0.pm.2
jack-0.109.2-36.1
jackmixdesk-gui-0.3-112.pm.svn20070530
jackmaster-0.0.1-0.pm.1
jack-rack-1.4.7-68.1
libjack0-32bit-0.109.2-36.1
jack2-1.9.0-0.pm.4
suse11:~ # rpm --test -ivh --force
http://download.opensuse.org/distribution/11.0/repo/oss/suse/x86_64/jack-0.…
Retrieving
http://download.opensuse.org/distribution/11.0/repo/oss/suse/x86_64/jack-0.…
Preparing... ########################################### [100%]
suse11:~ # jackd --help
jackd: error while loading shared libraries: libjack.so.0: cannot open shared object file:
No such file or directory
suse11:~ # rpm -ivh --force
http://download.opensuse.org/distribution/11.0/repo/oss/suse/x86_64/jack-0.…
Retrieving
http://download.opensuse.org/distribution/11.0/repo/oss/suse/x86_64/jack-0.…
Preparing... ########################################### [100%]
1:jack ########################################### [100%]
suse11:~ # jackd --help
jackd: error while loading shared libraries: libjack.so.0: cannot open shared object file:
No such file or directory
suse11:~ # rpm -qa | grep jack
jack_mixer-6-0.pm.3
jackmeter-0.3-0.pm.1
libjack2-0-1.9.0-0.pm.4
jack_snapshot-0.0.3-0.pm.1
jackbeat-0.6.3-0.pm.1
jacktube-0.20-0.pm.1
libjackserver2-0-1.9.0-0.pm.4
jack-0.109.2-36.1
jackEQ-0.4.1-0.pm.2
jackmixdesk-0.3-112.pm.svn20070530
jack_capture-0.9.31-0.pm.1
jack-scope-20080627-0.pm.1
libjack-devel-0.116.1-0.pm.1
jackmix-0.4-0.pm.1
qjacklam-0.3-0.pm.2
jackmixdesk-gui-0.3-112.pm.svn20070530
jackmaster-0.0.1-0.pm.1
jack-rack-1.4.7-68.1
libjack0-32bit-0.109.2-36.1
jack2-1.9.0-0.pm.4
I guess checkinstall sometimes worked for my 64bit hardware too, resp. I can't
remember how I build this package, maybe there was another automation, that build the RPM:
/usr/src/packages/RPMS/x86_64/wineasio-x-1.x86_64.rpm
wineasio - wineasio-x suse11.0 spinymouse 5 Aug 2008
Version: x-1
Project Page:
wineasio-x suse11.0 spinymouse 5 Aug 2008
Anyway, there are some more applications I compiled, but I don't need them and they
shouldn't be part of the problem.
suse11:~ # rpm --test -ev jack-0.109.2-36.1 libjack0-32bit-0.109.2-36.1
libjack-devel-0.116.1-0.pm.1
error: Failed dependencies:
jack-devel is needed by (installed) arts-devel-1.5.9-33.1.x86_64
suse11:~ # rpm --test -ev jack-0.109.2-36.1 libjack0-32bit-0.109.2-36.1
libjack-devel-0.116.1-0.pm.1 arts-devel-1.5.9-33.1.x86_64
error: Failed dependencies:
arts-devel is needed by (installed) kdelibs3-devel-3.5.9-49.1.x86_64
suse11:~ # rpm --test -ev jack-0.109.2-36.1 libjack0-32bit-0.109.2-36.1
libjack-devel-0.116.1-0.pm.1 arts-devel-1.5.9-33.1.x86_64
kdelibs3-devel-3.5.9-49.1.x86_64
suse11:~ # rpm -ev jack-0.109.2-36.1 libjack0-32bit-0.109.2-36.1
libjack-devel-0.116.1-0.pm.1 arts-devel-1.5.9-33.1.x86_64
kdelibs3-devel-3.5.9-49.1.x86_64
I don't need the devel packages, but I need jack. I first will try to force to get
jack2 by the replace options.
suse11:~ # rpm --test --replacefiles --replacepkgs -ivh
http://ftp.skynet.be/pub/packman/suse/11.0/x86_64/jack2-1.9.0-0.pm.4.x86_64…
Retrieving
http://ftp.skynet.be/pub/packman/suse/11.0/x86_64/jack2-1.9.0-0.pm.4.x86_64…
warning: /var/tmp/rpm-xfer.wajmN8: Header V3 DSA signature: NOKEY, key ID 9a795806
Preparing... ########################################### [100%]
suse11:~ # rpm --replacefiles --replacepkgs -ivh
http://ftp.skynet.be/pub/packman/suse/11.0/x86_64/jack2-1.9.0-0.pm.4.x86_64…
Retrieving
http://ftp.skynet.be/pub/packman/suse/11.0/x86_64/jack2-1.9.0-0.pm.4.x86_64…
warning: /var/tmp/rpm-xfer.Bp1RLi: Header V3 DSA signature: NOKEY, key ID 9a795806
Preparing... ########################################### [100%]
1:jack2 ########################################### [100%]
suse11:~ # jackd --help
jackd: error while loading shared libraries: libjackserver.so.0: cannot open shared object
file: No such file or directory
suse11:~ # ldconfig
suse11:~ # jackd --help
jackd: error while loading shared libraries: libjackserver.so.0: cannot open shared object
file: No such file or directory
just remove
the offending packages.
read the man page of rpm and remove them.
i guess you need the force option
Okay, I'll resume:
1. RPM force option to remove the offending Packages
2. install from the source (or try Packman again or try Jussi's RPM +
dependency, all should work)
3. run ldconfig
1:12 a.m.
New subject: JACK for openSUSE 11.0 x86_64
What I'm thinking of, isn't to erase any package, but I hope I used the
replace option not correct and that it will be possible to replace jack2
libs by jack libs, or if I like to get jack2 installed correctly, this
hopefully will also be fine, if I know how to use the replace options in
the right way. And I won't forget to run ldconfig.
6:43 a.m.
New subject: JACK for openSUSE 11.0 x86_64
On Di, 16.12.08 06:12 Ralf Mardorf <ralf.mardorf(a)alice-dsl.net> wrote:
What I'm thinking of, isn't to erase any
package, but I hope I used
the replace option not correct and that it will be possible to
replace jack2 libs by jack libs, or if I like to get jack2 installed
correctly, this hopefully will also be fine, if I know how to use the
replace options in the right way. And I won't forget to run ldconfig.
I would definately clean it up. So, to sum up the "how to do this"..
1) Get rid of jack2 (that's jackdmp I guess)
# rpm -e --nodeps jack2 libjack2-0 libjackserver2-0
2) Just to be sure, also remove jack(1)
# rpm -e --nodeps jack libjack0 libjackserver0 libjack-devel
libjack0-32bit
(I agree with paul that this naming scheme is absolutely ridiculous,
on Gentoo it's called like upstream calls it: jack-audio-connection-kit)
3) Now make sure that there are no leftovers of
libjack* in /usr/lib and /usr/lib64 and /usr/local/lib (who knows)
4) Then fire up YaST2, and make sure that you unset all ignored
conflicts! "Extras -> Ignorierte Abhängigkeitskonflikte zurücksetzen"
5) Reinstall jack by using either the suse-oss, or Jessi's rpm.
If you choose to use packman, use _only_ zypper, and never touch YaST
again afterwards! See below.
Hope that helps.
------------------------------------------------------
@ oc2pus, jack in packman is broken, or YaST is. I set up a fresh
install in a virtual machine using 11.1RC1 and only added packman.
Currently there is:
* pulseaudio-module-jack-0.9.12-8.5
* libjack0-0.116.1-0.pm.1
Now if I tick the box in YaST to install "jack" it pulls in
libjackserver2-0 and jack, which of course breaks things, as it keeps
libjack0. zypper on the other side gets it right. See the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
If I would let YaST go on with that, I would end up with a broken jack
install too :)
I you, Ralf, used YaST, it really wasn't your fault at all.
Regards,
Thomas
6:49 a.m.
New subject: JACK for openSUSE 11.0 x86_64
On Di, 16.12.08 11:42 Thomas Kuther <gimpel(a)sonnenkinder.org> wrote:
libjack0. zypper on the other side gets it right. See
the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
Did I really write that zypper gets it right?
It would pull in jack2 even I tell it to install "jack", but at least
it wouldn't break the box.
7:33 a.m.
New subject: JACK for openSUSE 11.0 x86_64
Am Dienstag, 16. Dezember 2008 schrieb Thomas Kuther:
@ oc2pus, jack in packman is broken, or YaST is. I set
up a fresh
install in a virtual machine using 11.1RC1 and only added packman.
Currently there is:
* pulseaudio-module-jack-0.9.12-8.5
* libjack0-0.116.1-0.pm.1
Now if I tick the box in YaST to install "jack" it pulls in
libjackserver2-0 and jack, which of course breaks things, as it keeps
libjack0. zypper on the other side gets it right. See the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
nor the packman package or yast is broken...
pulseaudio-module-jack has a (wrong ?) requires to jack instead libjack.so.1
(or a other program in your system) . And as there are more than one provider
for jack, yast pulls in the first provider for jack it finds.
So the bad packages in this dependency hell are the ones who has a "Requires:
jack"
Regards,
Thomas
have fun
Toni
8:18 a.m.
New subject: JACK for openSUSE 11.0 x86_64
On Di, 16.12.08 12:31 oc2pus(a)arcor.de wrote:
nor the packman package or yast is broken...
pulseaudio-module-jack has a (wrong ?) requires to jack instead
libjack.so.1 (or a other program in your system) . And as there are
more than one provider for jack, yast pulls in the first provider for
jack it finds.
So the bad packages in this dependency hell are the ones who has a
"Requires: jack"
That system is a plain fresh install of 11.1RC1 with KDE 4.1 payload,
packman added, "zypper up" run. Nothing else. I didn't even install
anything additionally yet. An absolutely untouched system, beside
the fact that I added packman :)
Actually I installed it only to see if this problem is reproducible.
So as long the final iso's aren't on the mirrors, I'd go out and fix
whatever causes that, otherwhise packman will break lots of audio boxen.
(In the suse OSS repo there is only one version of jack, so why
the heck should they care about different versions. Only a packman can
ask them to fix the pulseaudio-module-jack dependency ;) - you can
reproduce it quite easily thanks to virtual machines, not?)
Go for it!
Thomas
9:10 a.m.
New subject: JACK for openSUSE 11.0 x86_64
On Tue, Dec 16, 2008 at 12:31:22PM +0100, oc2pus(a)arcor.de wrote:
Am Dienstag, 16. Dezember 2008 schrieb Thomas Kuther:
and this is only possible because, there are 2 packages, for libjack and
jack. Why do you think we distibute them in one package ?
They make no sense without each other.
STOP SPLITTING JACK UP.
@ oc2pus, jack in packman is broken, or YaST is.
I set up a fresh
install in a virtual machine using 11.1RC1 and only added packman.
Currently there is:
* pulseaudio-module-jack-0.9.12-8.5
* libjack0-0.116.1-0.pm.1
Now if I tick the box in YaST to install "jack" it pulls in
libjackserver2-0 and jack, which of course breaks things, as it keeps
libjack0. zypper on the other side gets it right. See the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
nor the packman package or yast is broken...
pulseaudio-module-jack has a (wrong ?) requires to jack instead libjack.so.1
(or a other program in your system) . And as there are more than one provider
for jack, yast pulls in the first provider for jack it finds. So the bad packages in this dependency hell are the
ones who has a "Requires:
jack"
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
Regards,
Thomas
have fun
Toni
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
9:33 a.m.
New subject: JACK for openSUSE 11.0 x86_64
Am Dienstag, 16. Dezember 2008 schrieb torbenh(a)gmx.de:
On Tue, Dec 16, 2008 at 12:31:22PM +0100,
oc2pus(a)arcor.de wrote:
This "fetaure" was not packman's idea ...
see openSuSE-shared-library policy:
http://en.opensuse.org/Shared_Library_Packaging_Policy
and even jack2 is providing this scheme:
http://trac.jackaudio.org/wiki/SuggestedPackagingApproach
* "jack server frontend" - virtual package provided by "jackd" and
"jackdbus"
packages
* "jack server (library)" - package containing libjackserver.so at least.
Maybe also: essential tools, drivers, inprocess clients.
* "jackd" - package containing jackd binary. This package depends on "jack
server (library)"
* "jackdbus" - package containing jackdbus binary and jack_control script.
This package depends on "jack server (library)"
* "jack client library" - package containing libjack.so
* "jack client library dev" - package containging headers and pkgconfig file
for libjack.so
* "jack server library dev" - package containging headers and pkgconfig file
for libjackserver.so
This shared library policy needs a lot of extra-work but it allows also to
update library packages without breaking existing packages and or
mass-rebuilds if a so-name of a library is changed (ffmpeg-libs, x264 are
well known candidates for changing often API).
And if we don't follow the naming-scheme of the base distribution we were lost
and have much more troubles.
have fun
Toni
Am Dienstag, 16. Dezember 2008 schrieb Thomas
Kuther:
and this is only possible because, there are 2 packages, for libjack and
jack. Why do you think we distibute them in one package ?
They make no sense without each other.
STOP SPLITTING JACK UP. @ oc2pus, jack in packman is broken, or YaST is.
I set up a fresh
install in a virtual machine using 11.1RC1 and only added packman.
Currently there is:
* pulseaudio-module-jack-0.9.12-8.5
* libjack0-0.116.1-0.pm.1
Now if I tick the box in YaST to install "jack" it pulls in
libjackserver2-0 and jack, which of course breaks things, as it keeps
libjack0. zypper on the other side gets it right. See the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
nor the packman package or yast is broken...
pulseaudio-module-jack has a (wrong ?) requires to jack instead
libjack.so.1 (or a other program in your system) . And as there are more
than one provider for jack, yast pulls in the first provider for jack it
finds. 
1:22 p.m.
New subject: JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de writes:
and even jack2 is providing this scheme:
http://trac.jackaudio.org/wiki/SuggestedPackagingApproach
I've changed the page and it now contains this paragraph:
All different releases of JACK should be considered internally
incompatible - that is, it should never be considered possible to mix
versions of the JACK server with other versions of the JACK library/ies,
drivers or internal clients. Packaging should ensure that no packages
associated with different releases of JACK are ever installed
simultaneously. Especially, having two versions of libjack.so installed
simultaneously, often causes JACK programs using one libjack version not
being able to operate with JACK server of other version.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
2:16 p.m.
New subject: JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de wrote:
This is one of the "bright" ideas adopted from Debian-based systems, but
I'm not at all convinced that it's a good idea especially in jack case.
Normally the reason for this is that older applications which depend on
older shared libraries can co-exist and work with newer applications
depending on newer shared libraries. However, for jack this creates a
conflict situation which might be hard for the end user to solve.
Reason is that the jack server and the shared library for clients are
tied to each other by specific version/layout of shared memory block
used to communicate. Even if dynamic linking dependency for older
applications wouldn't break and the application would continue to load,
they will stop actually functioning! For this particular reason there's
a specific way to handle also shared library versions. This is not done
for binaries, however!
Now this "bright" idea of "let's not break old binaries, let's
just
install bunch of different versions of the same library" is doomed for
jack (and for many other non-self-contained apps too). It doesn't take
into account the dependency between the server version and certain
client library version. And even more confusing for the user would be to
have two different server versions with applications for two different
library versions and the user would start wondering why he cannot route
audio between different applications, etc...
STOP SPLITTING
JACK UP.
This "fetaure" was not packman's idea ...
see openSuSE-shared-library policy:
http://en.opensuse.org/Shared_Library_Packaging_Policy This shared library policy needs a lot of extra-work
but it allows also to
update library packages without breaking existing packages and or
mass-rebuilds if a so-name of a library is changed (ffmpeg-libs, x264 are
well known candidates for changing often API).
That's especially what it doesn't achieve with jack. It specifically
breaks things, badly...
BR,
- Jussi
3:12 p.m.
New subject: JACK for openSUSE 11.0 x86_64
Am Dienstag, 16. Dezember 2008 schrieb Jussi Laako:
oc2pus(a)arcor.de wrote:
This is one of the "bright" ideas adopted from Debian-based systems, but
I'm not at all convinced that it's a good idea especially in jack case.
Normally the reason for this is that older applications which depend on
older shared libraries can co-exist and work with newer applications
depending on newer shared libraries. However, for jack this creates a
conflict situation which might be hard for the end user to solve.
Reason is that the jack server and the shared library for clients are
tied to each other by specific version/layout of shared memory block
used to communicate. Even if dynamic linking dependency for older
applications wouldn't break and the application would continue to load,
they will stop actually functioning! For this particular reason there's
a specific way to handle also shared library versions. This is not done
for binaries, however!
Now this "bright" idea of "let's not break old binaries, let's
just
install bunch of different versions of the same library" is doomed for
jack (and for many other non-self-contained apps too). It doesn't take
into account the dependency between the server version and certain
client library version. And even more confusing for the user would be to
have two different server versions with applications for two different
library versions and the user would start wondering why he cannot route
audio between different applications, etc...
Ok, I uploaded new packages for jack and jack2.
They are now mutually exclusive and the user must change wich one to use.
Formerly jack2 was handled as a update to jack.
The "Requires" to the underlying library packages where already part of the
packman packages.
STOP
SPLITTING JACK UP.
This "fetaure" was not packman's idea ...
see openSuSE-shared-library policy:
http://en.opensuse.org/Shared_Library_Packaging_Policy This shared library policy needs a lot of
extra-work but it allows also
to update library packages without breaking existing packages and or
mass-rebuilds if a so-name of a library is changed (ffmpeg-libs, x264 are
well known candidates for changing often API).
That's especially what it doesn't achieve with jack. It specifically
breaks things, badly... BR,
- Jussi
3:54 p.m.
New subject: JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de wrote:
Ok, I uploaded new packages for jack and jack2.
They are now mutually exclusive and the user must change wich one to use.
Formerly jack2 was handled as a update to jack.
The "Requires" to the underlying library packages where already part of the
packman packages.
Most common problem users encounter is multiple library versions
installed. It might be a good idea to make the jack library package to
conflict with any other version of the library package. But it's a bit
of a packaging problem if the name part contains a version number...
libjack*0 should never ever coexist with libjack*1, or libjack*2 etc.
- Jussi
9:54 a.m.
New subject: JACK for openSUSE 11.0 x86_64
On Tue, Dec 16, 2008 at 02:05:05PM +0100, torbenh(a)gmx.de wrote:
and this is only possible because, there are 2 packages, for libjack and
jack. Why do you think we distibute them in one package ?
They make no sense without each other.
STOP SPLITTING JACK UP.
Sorry, this might have sounded a little bit harsh.
But this is a message to ALL packagers.
not only packman, but also debian packagers.
It looks like we will stop supporting people with distros/repos
which split up the libraries from jackd. And just tell them
their distro is broken.
STOP SPLITTING JACK UP.
There is NO reason to do that.
So at least fix it with HARD Require of a matching jackd/libjack
version in both packages.
--
torben Hohn
11:50 a.m.
New subject: JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de wrote:
nor the packman package or yast is broken...
pulseaudio-module-jack has a (wrong ?) requires to jack instead libjack.so.1
(or a other program in your system) . And as there are more than one provider
for jack, yast pulls in the first provider for jack it finds.
So the bad packages in this dependency hell are the ones who has a "Requires:
jack"
I don't wish to have stuff like arts and pulseaudio on my machine, I
always disable system sounds, because my Linux are audio Workstations,
resp. they should be audio workstations.
That's why I compile and set up a lot myself. I won't read what I have
to do, if I use package managements all the time.
How should a user know about that? "I will upgrade jack, but shall know,
that I have to google for problems with pulseaudio"?!
I hate it, that I'm forced to have bull shit like arts, because I'm
using KDE. I don't know anything about pulseaudio.
12:35 p.m.
New subject: JACK for openSUSE 11.0 x86_64
On Tue, Dec 16, 2008 at 12:31:22PM +0100, oc2pus(a)arcor.de wrote:
Am Dienstag, 16. Dezember 2008 schrieb Thomas Kuther:
hmm... ok. it looks like libjack0-0.109.2 is not requiring
jack-0.109.2.
and jack-0.109.2 only requires libjack0.so
which can be provided by libjack2 and libjack1.
i consider this broken.
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
@ oc2pus, jack in packman is broken, or YaST is.
I set up a fresh
install in a virtual machine using 11.1RC1 and only added packman.
Currently there is:
* pulseaudio-module-jack-0.9.12-8.5
* libjack0-0.116.1-0.pm.1
Now if I tick the box in YaST to install "jack" it pulls in
libjackserver2-0 and jack, which of course breaks things, as it keeps
libjack0. zypper on the other side gets it right. See the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
nor the packman package or yast is broken...
2:37 p.m.
New subject: JACK for openSUSE 11.0 x86_64
Am Dienstag, 16. Dezember 2008 schrieb torbenh(a)gmx.de:
On Tue, Dec 16, 2008 at 12:31:22PM +0100,
oc2pus(a)arcor.de wrote:
just for the records:
these are not packman packages.
the packman packages contains a X.pm.Y in the release tag, the actual version
is 0.116.1.
A lib-package normally doesn't contain a requirement to a program-package.
For my packages in the packman repository:
As a reaction of this thread, I uploaded new packages for jack and jack2.
They are now mutually exclusive and the user must change wich one to use.
Formerly jack2 was handled as a update to jack.I followed also the idea from
Torben to handle the jack-daemon like a library.
The "Requires" to the underlying library packages where already part of the
packman packages. So I hope the problems of upgrading/changing the
jack-versions are solved.
And a last note to Mr. Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
your posting in the linux-club community is very astonishing. You grab
sentences from Paul and others from here and put them in a very very special
context to fit your argumentation against SuSE distribution and especially
the packman repository.
http://www.linux-club.de/viewtopic.php?f=18&t=99521&p=605724#p605724
And words like "überhebliche Schwätzer" are very motivating.
have fun
oc2pus
Am Dienstag, 16. Dezember 2008 schrieb Thomas
Kuther:
hmm... ok. it looks like libjack0-0.109.2 is not requiring
jack-0.109.2.
and jack-0.109.2 only requires libjack0.so
which can be provided by libjack2 and libjack1.
i consider this broken. @ oc2pus, jack in packman is broken, or YaST is.
I set up a fresh
install in a virtual machine using 11.1RC1 and only added packman.
Currently there is:
* pulseaudio-module-jack-0.9.12-8.5
* libjack0-0.116.1-0.pm.1
Now if I tick the box in YaST to install "jack" it pulls in
libjackserver2-0 and jack, which of course breaks things, as it keeps
libjack0. zypper on the other side gets it right. See the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
nor the packman package or yast is broken...
2:52 p.m.
New subject: JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de wrote:
Am Dienstag, 16. Dezember 2008 schrieb
torbenh(a)gmx.de:
THAT'S the evilness? You don't know what time it is! Yes, a Suse install
comes with default packages @ repo-oss. Is Packman incompatible to Suse
repositories? Ican't read anything in the Linux Club howtos, stupid
people like me should read.
YOU ARE WRONG and tries to blame me, even if I came with the calumet and
was sorry that I boiled over.
NOW YOU are again twisting the truth. YOU LOSER!
On Tue, Dec 16, 2008 at 12:31:22PM +0100,
oc2pus(a)arcor.de wrote:
just for the records:
these are not packman packages.
the packman packages contains a X.pm.Y in the release tag, the actual version
is 0.116.1.
Am Dienstag, 16. Dezember 2008 schrieb Thomas
Kuther:
hmm... ok. it looks like libjack0-0.109.2 is not requiring
jack-0.109.2.
and jack-0.109.2 only requires libjack0.so
which can be provided by libjack2 and libjack1.
i consider this broken.
@ oc2pus, jack in packman is broken, or YaST is.
I set up a fresh
install in a virtual machine using 11.1RC1 and only added packman.
Currently there is:
* pulseaudio-module-jack-0.9.12-8.5
* libjack0-0.116.1-0.pm.1
Now if I tick the box in YaST to install "jack" it pulls in
libjackserver2-0 and jack, which of course breaks things, as it keeps
libjack0. zypper on the other side gets it right. See the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
nor the packman package or yast is broken...
A lib-package normally doesn't contain a
requirement to a program-package.
For my packages in the packman repository:
As a reaction of this thread, I uploaded new packages for jack and jack2.
They are now mutually exclusive and the user must change wich one to use.
Formerly jack2 was handled as a update to jack.I followed also the idea from
Torben to handle the jack-daemon like a library.
The "Requires" to the underlying library packages where already part of the
packman packages. So I hope the problems of upgrading/changing the
jack-versions are solved.
And a last note to Mr. Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
your posting in the linux-club community is very astonishing. You grab
sentences from Paul and others from here and put them in a very very special
context to fit your argumentation against SuSE distribution and especially
the packman repository.
http://www.linux-club.de/viewtopic.php?f=18&t=99521&p=605724#p605724
And words like "überhebliche Schwätzer" are very motivating.
have fun
oc2pus
No I'm Pro-Suse, I was going to write an howto and you always quoted me
wrong, BECAUSE I mentioned that if you have knowledge about pro-audio
and you are really making music, you need to have different kernels than
those from the packages, you need to compile stuff yourself, because you
always will get troubles and the moderators made jokes about me, even
you MOTHERFUCKER made jokes here.
You said IN THIS LIST, NOBODY will have any conflicts, it's only me.
You twisting the truth even now, I would like to make Suse a audio and
MIDI workstation, that's why I do what I do.
IGNORANT PEOPLE like you make it impossible, you are AGAINST SUSE, it's
not me.
YOU ARE A LIAR and everybody can read it here.
2:55 p.m.
New subject: JACK for openSUSE 11.0 x86_64
oc2pus IF YOU are making music by using the Packman repositories and
nobody, but me run into trouble with your package, why has anybody but
you problems? I guess you don't make music using your own packages!
3:09 p.m.
New subject: JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de wrote:
You grab
sentences from Paul and others from here and put them in a very very special
context to fit your argumentation against SuSE distribution and especially
the packman repository.
http://www.linux-club.de/viewtopic.php?f=18&t=99521&p=605724#p605724
And words like "überhebliche Schwätzer" are very motivating.
That's not true! Yes, I quoted Paul Davis. In which context that isn't
true? Where have I ever given a statement against Suse? I'm using Suse
since 9.0 constantly and I'm compiling for Debian that also has the
jack, libjack issue. I argued against your ignorance and your twisting
of the truth.
I was going to write a howto for Suse and needed help and I said the
truth and you said that's not true, I have no knowledge.
3:16 p.m.
New subject: JACK for openSUSE 11.0 x86_64
A last statement!
I started with 11.1 RC to avoid that Suse again will be bad for
pro-audio and in two days there again will be a new stable release
that's totally invalid. All because I get bashes at Linux Club. I boiled
over here, yes and I'm still boiling ...
Have you ever made music with your YaST Suse? I guess you will have set
limits.conf manually? Some pro-audio folks need to do more and I was
interested in solving this.
Please translate the threads at Linux Club and quote them here. I'm not
lying, but you do so.
3:17 p.m.
New subject: JACK for openSUSE 11.0 x86_64
Ralf Mardorf wrote:
A last statement!
I started with 11.1 RC to avoid that Suse again will be bad for
pro-audio and in two days there again will be a new stable release
that's totally invalid. All because I get bashes at Linux Club. I boiled
over here, yes and I'm still boiling ...
Have you ever made music with your YaST Suse? I guess you will have set
limits.conf manually? Some pro-audio folks need to do more and I was
interested in solving this.
Please translate the threads at Linux Club and quote them here. I'm not
lying, but you do so.
I go away from Linux Club, because I don't want this flame war! Why must
it go on here?
Was I'm wrong or was the package wrong?
3:32 p.m.
New subject: JACK for openSUSE 11.0 x86_64
On Di, 16.12.08 20:17 Ralf Mardorf <ralf.mardorf(a)alice-dsl.net> wrote:
I go away from Linux Club, because I don't want
this flame war! Why
must it go on here?
Good, because you will be banned inbetween the next minutes anyway
after your last mails here, and that post there.
A lot of people here and there tried to find out what the heck your
problem is, tried to help you, did actually find the problem, and there
is even a solution for you and new jack packages for all.
And if you call someone a loser and a motherf**** for absolutely no
obvious reason, on a public list read by thousands of people, you do not
deserve any further help. Not here, not in any forum, not on any other
list.
Jeees...
3:48 p.m.
New subject: JACK for openSUSE 11.0 x86_64
Thomas Kuther wrote:
On Di, 16.12.08 20:17 Ralf Mardorf
<ralf.mardorf(a)alice-dsl.net> wrote:
You can ban me for my words here, but what have I written at Linux Club,
that you ban me from Linux Club? And especially you don't have the might
to ban me from the Linux community, but anyway, I will go myself.
I go away from Linux Club, because I don't
want this flame war! Why
must it go on here?
Good, because you will be banned inbetween the next minutes anyway
after your last mails here, and that post there.
A lot of people here and there tried to find out what the heck your
problem is, tried to help you, did actually find the problem, and there
is even a solution for you and new jack packages for all.
And if you call someone a loser and a motherf**** for absolutely no
obvious reason, on a public list read by thousands of people, you do not
deserve any further help. Not here, not in any forum, not on any other
list.
Jeees...
3:51 p.m.
New subject: JACK for openSUSE 11.0 x86_64
hmm... ok. it
looks like libjack0-0.109.2 is not requiring
jack-0.109.2.
and jack-0.109.2 only requires libjack0.so
which can be provided by libjack2 and libjack1.
i consider this broken.
just for the records:
these are not packman packages.
the packman packages contains a X.pm.Y in the release tag, the actual version
is 0.116.1.
A lib-package normally doesn't contain a requirement to a program-package.
For my packages in the packman repository:
As a reaction of this thread, I uploaded new packages for jack and jack2.
They are now mutually exclusive and the user must change wich one to use.
Formerly jack2 was handled as a update to jack.I followed also the idea from
Torben to handle the jack-daemon like a library.
The "Requires" to the underlying library packages where already part of the
packman packages. So I hope the problems of upgrading/changing the
jack-versions are solved.
ok. i will have a look, when your package database has synched.
nedko also updated:
http://trac.jackaudio.org/wiki/SuggestedPackagingApproach
to make the fact more clear, that there MUST NOT be two versions,
of libjack.so on the system.
perhaps you can communicate this fact upstream to suse.
i dont know how these things works, and who builds the
"official" opesuse packages. or if they just copy a working package,
from the alternative repos.
trying to :)
oc2pus
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
4:08 p.m.
New subject: JACK for openSUSE 11.0 x86_64
torbenh(a)gmx.de wrote:
so lets drink some "virtual" beer together,
and let this stuff
rest. And Ralf, i hope that, you see that apart from pointing out
the problem you did not help in solving this problem.
I'll drink some alcohol free real beer and maybe one with alcohol too.
A lot of people have troubles with Linux, they report about their
troubles, people laugh about them and say that there will be not such
troubles and the troubles stay.
It ends in a flame war, because I asked and again I was the one who made
everything wrong. I go away from Linux Club to get help here, but oc2pus
started here again that I'm wrong, but I wasn't wrong.
Okay, now I'm banned here and at Linux Club.
If I had relented instead of boiling over, there will be still a bad
package.
But okay, I'm evil. I'm a musician and I have emotions, oc2pus might be
cool, he seems to be not a musician, he didn't noticed that the package
was broken, after I reported it. Everything is my failure.
I don't see a future for multimedia production on Linux, if people
ignore the truth, e.g. you can tell a 100 times that some people need
special kernel versions, nobody is interested.
4:15 p.m.
New subject: JACK for openSUSE 11.0 x86_64
torbenh(a)gmx.de wrote:
And Ralf, i hope that, you see that apart from
pointing out
the problem you did not help in solving this problem.
And I even wasn't the one who pointed out the problem, there were people
doing it before me, but nobody take care about them, because they didn't
boiled over.
4:20 p.m.
New subject: JACK for openSUSE 11.0 x86_64
Am Dienstag, 16. Dezember 2008 schrieb torbenh(a)gmx.de:
nedko also updated:
http://trac.jackaudio.org/wiki/SuggestedPackagingApproach
to make the fact more clear, that there MUST NOT be two versions,
of libjack.so on the system.
perhaps you can communicate this fact upstream to suse.
i dont know how these things works, and who builds the
"official" opesuse packages. or if they just copy a working package,
from the alternative repos.
openSuSE has a bugzilla and you need to register etc
etc etc (IMHO makes error
reporting very very hard, but this is only my opinion)
https://bugzilla.novell.com/index.cgi
From my experiences and as openSuSE 11.1 is ready for roll-out, I think its to
late for this SuSE version to change the jack-package layout and the "error"
will be in state "next-release" or "won't be fixed".
So this should be done for the next SuSE release. And one of the authors of
jack should trigger this.
You can get the email adress of a packager with
rpm -qi jack | grep Packager
But in 99,9% o all SuSE packages this results in
Packager : http://bugs.opensuse.org <== bugzilla
have fun
oc2pus
11:40 a.m.
New subject: JACK for openSUSE 11.0 x86_64
Thomas Kuther wrote:
On Di, 16.12.08 06:12 Ralf Mardorf
<ralf.mardorf(a)alice-dsl.net> wrote:
Yes, jackdmp now is called jack2 (from the sight of a user like me).
Perhaps I should test jack2 too (one day).
What I'm thinking of, isn't to erase any
package, but I hope I used
the replace option not correct and that it will be possible to
replace jack2 libs by jack libs, or if I like to get jack2 installed
correctly, this hopefully will also be fine, if I know how to use the
replace options in the right way. And I won't forget to run ldconfig.
I would definately clean it up. So, to sum up the "how to do this"..
1) Get rid of jack2 (that's jackdmp I guess)
# rpm -e --nodeps jack2 libjack2-0 libjackserver2-0
2) Just to be sure, also remove jack(1)
# rpm -e --nodeps jack libjack0 libjackserver0 libjack-devel
libjack0-32bit
(I agree with paul that this naming scheme is absolutely ridiculous,
on Gentoo it's called like upstream calls it: jack-audio-connection-kit)
3) Now make sure that there are no leftovers of
libjack* in /usr/lib and /usr/lib64 and /usr/local/lib (who knows)
4) Then fire up YaST2, and make sure that you unset all ignored
conflicts! "Extras -> Ignorierte Abhängigkeitskonflikte zurücksetzen"
:D my Linux all are on English, because I need to use lists on English.
But I understand what I have to take care about.
5) Reinstall jack by using either the suse-oss, or
Jessi's rpm.
This is ...
If you choose to use packman, use _only_ zypper, and
never touch YaST
again afterwards! See below.
... the ultimate amends :).
So it wasn't because I'm stupid? There is a bug?
Hope that helps.
------------------------------------------------------
@ oc2pus, jack in packman is broken, or YaST is. I set up a fresh
install in a virtual machine using 11.1RC1 and only added packman.
Currently there is:
* pulseaudio-module-jack-0.9.12-8.5
* libjack0-0.116.1-0.pm.1
Now if I tick the box in YaST to install "jack" it pulls in
libjackserver2-0 and jack, which of course breaks things, as it keeps
libjack0. zypper on the other side gets it right. See the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
If I would let YaST go on with that, I would end up with a broken jack
install too :)
I you, Ralf, used YaST, it really wasn't your fault at all.
Regards,
Thomas
But I have to say, that I was doing this for 11.0,I have a 11.1 RC too,
but this comes without JACK at the moment.
Thank you very much :)
Ralf
4:25 a.m.
New subject: JACK for openSUSE 11.0 x86_64
On Tue, 2008-12-16 at 03:12 +0100, Ralf Mardorf wrote:
. If I don't have knowledge I have to
read and to ask, I just reported and asked, and get acidness.
no, thats not the issue. i think you don't understand that we (JACK)
developers see these issues reported day after day after day, not just
by you but by other people. they are all issues that, for the most part,
we are powerless to affect. the issues are caused/created/affected by
the actions of distribution packagers and can only be solved by them.
it is incredibly frustrating watching user after user after user grapple
with stupid system configuration problems that we did not create just to
try to get JACK to run. whether its the complete lack of any way to get
real time scheduling to work, or the wrong version of PAM or the wrong
kernel or no version of limits.conf to edit, or no pre-existing user
group, or an ancient version of JACK, or a version of JACK with a
totally broken and utterly ridiculous library dependency name, or
versions of JACK built with the wrong assembler options ... watching
users struggle with this stuff is just incredibly frustrating and
sometimes that spills over to our interactions with users.
i for one am close to abandoning all efforts to provide support &
assistance to people using JACK on anything other than a small handful
of Linux distributions, because i am sick and tired of this ridiculous
situation. its been nearly 4 years since we got mainstream kernels that
were capable of supporting JACK and pro-audio/music apps out of the box.
the fact that users today are still dealing with the total crapfest that
we see every day on IRC and on the mailing lists is just totally
unacceptable. i don't know whose fault it is (maybe its mine, i'm not
ruling it out), but its a totally waste of everyone's time.
distros: people want creativity apps on linux. for audio this means that
you users will run JACK. with realtime scheduling priviledges. and they
will possibly upgrade JACK before you do. fix it! please!
11:20 a.m.
New subject: JACK for openSUSE 11.0 x86_64
Paul Davis wrote:
On Tue, 2008-12-16 at 03:12 +0100, Ralf Mardorf
wrote:
I never got acidness by jack developers. I'm a JACK user and for some
issues there is the need to report this to the developer list, e.g. bugs
like the JACK transport delay or things about the handling, like the
issue about name aliases.
A package problem or what ever the cause is, might be wrong at a
developers list, but audio users (and I guess developers sometimes too),
won't be in the right place with questions about audio, if they use
distro forums. I first googled and was linked to ...
"Hello
I made an upgrade of a Suse11-System with packman enabeled and jackd was
upgraded to 0.116.1. No jackd refuses to start with undefined symbol:
clock_source.
My next move was to install the official release from source. Yet to
noavail: the problem stays the same.
What could this be? (http://ardour.org/node/2271)"
The Packman package should not be the cause, said someone from Packman,
also it was declared that I don't have knowledge.
For 64 Studio there's a user list, but 64 Studio 2.1 stable is still
using JACK 0.103.
Users need a please were it's allowed to be stupid and because I have
some knowledge about versions (not about Linux in general) that the Suse
people don't have, I wished to have a forum on a board for users, but
there are such issues unwanted, that's why I asked were such issues are
wanted.
The answer is, that they are wanted at mailing lists, only on English,
like the 64 Studio one. But if users will have issues that are
interesting for developers too, than they need latest versions.
E.g. Tommi and I have 64bit hardware, Envy24 cards and jackd timeouts,
we never had with 32bit hardware before. My jackd are 0.103 and 0.109
and when I upgraded from 0.109 to 0.116, by using mouse-clicks for the
YaST2 GUI, my Suse was broken. All because I don't have the knowledge
to click right?!
The 1. place to asked should be a forum for users, but what to do, if
you don't get help?
Which distro is the right distro for audio and MIDI users to use?
. If I don't have knowledge I have to
read and to ask, I just reported and asked, and get acidness.
no, thats not the issue. i think you don't understand that we (JACK)
developers see these issues reported day after day after day, not just
by you but by other people. they are all issues that, for the most part,
we are powerless to affect. the issues are caused/created/affected by
the actions of distribution packagers and can only be solved by them.
it is incredibly frustrating watching user after user after user grapple
with stupid system configuration problems that we did not create just to
try to get JACK to run. whether its the complete lack of any way to get
real time scheduling to work, or the wrong version of PAM or the wrong
kernel or no version of limits.conf to edit, or no pre-existing user
group, or an ancient version of JACK, or a version of JACK with a
totally broken and utterly ridiculous library dependency name, or
versions of JACK built with the wrong assembler options ... watching
users struggle with this stuff is just incredibly frustrating and
sometimes that spills over to our interactions with users.
i for one am close to abandoning all efforts to provide support &
assistance to people using JACK on anything other than a small handful
of Linux distributions, because i am sick and tired of this ridiculous
situation. its been nearly 4 years since we got mainstream kernels that
were capable of supporting JACK and pro-audio/music apps out of the box.
the fact that users today are still dealing with the total crapfest that
we see every day on IRC and on the mailing lists is just totally
unacceptable. i don't know whose fault it is (maybe its mine, i'm not
ruling it out), but its a totally waste of everyone's time.
distros: people want creativity apps on linux. for audio this means that
you users will run JACK. with realtime scheduling priviledges. and they
will possibly upgrade JACK before you do. fix it! please!
3:24 a.m.
New subject: JACK for openSUSE 11.0 x86_64
Am Dienstag, 16. Dezember 2008 schrieb torbenh(a)gmx.de:
just remove the offending packages.
read the man page of rpm and remove them.
i guess you need the force option, because you got yourself into
dependency hell.
yast wont help you here.
you need rpm -e --nodeps <packagename> perhaps
additionally the
option --allmatches if packages are installed twice.
than a package is removed and you have a temporary inconsitent system, but if
you install immediately the other packages all will be fine
10:49 a.m.
New subject: JACK for openSUSE 11.0 x86_64
oc2pus(a)arcor.de wrote:
you need rpm -e --nodeps <packagename> perhaps
additionally the
option --allmatches if packages are installed twice.
than a package is removed and you have a temporary inconsitent system, but if
you install immediately the other packages all will be fine
Thanx, I got this information from Toni too, this should do the trick.
15 Dec
15 Dec
9:21 p.m.
New subject: JACK for openSUSE 11.0 x86_64
Oc2pus, I don't will write any thing more about this issue, you are free
to write books about it, but I won't reply to stuff that has nothing to
do with my request, if it's in that German forum style.
9:29 p.m.
New subject: JACK for openSUSE 11.0 x86_64
On Tuesday 16 December 2008 02:21:03 Ralf Mardorf wrote:
Oc2pus, I don't will write any thing more about
this issue, you are free
to write books about it, but I won't reply to stuff that has nothing to
do with my request, if it's in that German forum style.
Apart from the fact that your other mails are really long, this is the kind of
attitude to _not_ get you any help. What oc2pus wrote are actually very valid
points (apart from the tip that your situation will get better with gentoo,
you don't know enough about linux to install/manage gentoo). You do have two
different versions installed. This _is_ a messed up system. Why don't you try
to clean that up instead of writing long and angry mails?
Have fun,
Arnold
9:51 p.m.
New subject: JACK for openSUSE 11.0 x86_64
Arnold Krille wrote:
You do have two different versions installed. This
_is_ a messed up system. Why don't you try
to clean that up
I need to find out how to do this. After I upgraded my Suse 11.0 from
jackd 0.109 to jackd 0.116 by using YaST2, it was broken. Maybe not the
way it's broken now, but jackd started with an error, then I downgraded
to 0.109, the version that was fine before, but it didn't repair the
system, jackd still was broken.
When I'm writing of downgrading, I mean first to remove by YaST2 and
then to install, but YaST seems to keep some libs. I tried what was
posted at the Ardour page, rm some libs* using a terminal, but until now
it's still broken. I can restore a backup by rsync, but I would like to
repair it.
The discussion about knowledge is invalid, because it doesn't has to do
with the problem and just is guessed and it's a typical German problem.
5619
days inactive
5620
days old
linux-audio-dev@lists.linuxaudio.org
50 comments
8 participants
participants (8)
-
Arnold Krille -
Jussi Laako -
Nedko Arnaudov -
oc2pus＠arcor.de -
Paul Davis -
Ralf Mardorf -
Thomas Kuther -
torbenh＠gmx.de