PDA

View Full Version : SLES 12 SUSEConnect not found since SUSEConnect-0.2.14.42-9.3.1.x8



jmroth
02-Dec-2015, 21:04
Hello forum,

Is there anything known about messed up SUSEConnect packages in SLES12 since SUSEConnect-0.2.14.42-9.3.1.x86_64?


:~ # SUSEConnect
If 'SUSEConnect' is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf SUSEConnect
:~ # rpm -qa | grep -i connect
SUSEConnect-0.2.14.42-9.3.1.x86_64
ruby2.1-rubygem-suse-connect-0.2.14.42-9.3.1.x86_64
:~ # ls -l /usr/sbin/SUSEConnect
lrwxrwxrwx 1 root root 18 Nov 6 19:58 /usr/sbin/SUSEConnect -> ../bin/SUSEConnect
:~ # ls -l /usr/bin/SUSEConnect
lrwxrwxrwx 1 root root 29 May 11 2015 /usr/bin/SUSEConnect -> /etc/alternatives/SUSEConnect
:~ # ls -l /etc/alternatives/SUSEConnect
lrwxrwxrwx 1 root root 35 May 11 2015 /etc/alternatives/SUSEConnect -> /usr/bin/SUSEConnect.ruby2.1-0.2.14
:~ # ls -l /usr/bin/SUSEConnect.ruby2.1-0.2.14
ls: cannot access /usr/bin/SUSEConnect.ruby2.1-0.2.14: No such file or directory
:~ # rpm -V SUSEConnect-0.2.14.42-9.3.1.x86_64 ruby2.1-rubygem-suse-connect-0.2.14.42-9.3.1.x86_64
:~ # ls -l /usr/bin/SUSEConnect.ruby2.1-0.2.14
ls: cannot access /usr/bin/SUSEConnect.ruby2.1-0.2.14: No such file or directory


Thanks.

jmozdzen
03-Dec-2015, 14:10
Hi jmroth,

> Is there anything known about messed up SUSEConnect packages in SLES12 since SUSEConnect-0.2.14.42-9.3.1.x86_64?

Seems to be a problem with update-alternatives - from what I can see, the definitions look fine, but aren't applied properly. Are you in a position to open a service request?

Regards,
Jens

jmroth
03-Dec-2015, 14:51
Hi jmroth,

> Is there anything known about messed up SUSEConnect packages in SLES12 since SUSEConnect-0.2.14.42-9.3.1.x86_64?

Seems to be a problem with update-alternatives - from what I can see, the definitions look fine, but aren't applied properly. Are you in a position to open a service request?


I tried. But sometimes they take a while before ultimate comprehension. Instead they make you run diagnostic commands even if you tell them how to reproduce :)

jmozdzen
03-Dec-2015, 15:14
Hi jmroth,

> Instead they make you run diagnostic commands even if you tell them how to reproduce :)

do be to hard on 1st level ;) - they're the ones pushed by both the users and developers. The latter, by experience, insist on a supportconfig file to have all the environmental details at hand in a standardized way.

Regards,
Jens

jmroth
03-Dec-2015, 19:25
Feedback from support, they got it:


This is a known issue and a bug has been created, you can fix the suseconnect witht he following commad:

zypper install --force ruby2.1-rubygem-suse-connect

Now that's ok for me.