Zypper warns about some files not being symoblic links

English Install/Boot/Login
#1

During the installation of updates, zypper gives the following information:

/sbin/ldconfig: /usr/lib64/libv4lconvert.so.0 is not a symbolic link

/sbin/ldconfig: /usr/lib64/libv4l2.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib64/libv4l1.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib/libv4l1.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib/libv4l2.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib/libv4lconvert.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib64/libv4lconvert.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib64/libv4l2.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib64/libv4l1.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib/libv4l1.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib/libv4l2.so.0 is not a symbolic link


/sbin/ldconfig: /usr/lib/libv4lconvert.so.0 is not a symbolic link

I use opensuse factory. Are these messages a problem? Can I ignore them?

#2

I’m using factory. I am seeing:


% ls -ld libv4l*
drwxr-xr-x 3 croot root   4096 Oct  2 07:17 libv4l
lrwxrwxrwx 1 croot root     16 Sep 29 00:14 libv4l1.so.0 -> libv4l1.so.0.0.0
-rwxr-xr-x 1 croot root  24472 Sep 29 00:14 libv4l1.so.0.0.0
lrwxrwxrwx 1 croot root     16 Sep 29 00:14 libv4l2.so.0 -> libv4l2.so.0.0.0
-rwxr-xr-x 1 croot root  55552 Sep 29 00:14 libv4l2.so.0.0.0
lrwxrwxrwx 1 croot root     22 Sep 29 00:14 libv4lconvert.so.0 -> libv4lconvert.so.0.0.0
-rwxr-xr-x 1 croot root 158736 Sep 29 00:14 libv4lconvert.so.0.0.0

You possibly copied these, in a manner such that copy followed symlinks.

As far as I know, what you have still works. But you have broken some of the versioning support for dynamic libraries, which expects symlinks.

#3

That should have gone in Pre-release/Beta.

#4

Sorry, I thought that Factory was a distribution of its own now.

#5

No not really Factory is to replace tumbleweed I guess. But Factory is still factory ie cutting edge/beta But I guess a little more stable then in the past

#6

Actually, Factory (the new, tested, more “stable” Factory) is going to be renamed to “Tumbleweed” and therefore replace it, yes.
“Factory” will be the unstable/untested “Factory-to-test” then again, AIUI .

See also:
https://news.opensuse.org/2014/10/24/tumbleweed-factory-rolling-releases-to-merge/

#7

Ok I guess LOL I suppose it is just an internal shuffling of resources.

#8

Well, as I understand it it’s just a rename now. The changes are already in place for months.

TBH though, IMHO they should have settled on calling the new Factory “Tumbleweed” already before they announced the new “Factory” rolling distribution.
The way it has been done (i.e. announce a more stable Factory as the new rolling distribution, then decide three months later to call the unstable one Factory again instead) just creates unnecessary confusion I think. But well, it’s too late now…:\

Anyway, when Factory was announced as the new rolling release, there were also talks about a new forum for Factory specifically.
I suppose that will be the Tumbleweed forum now… :wink:

Btw, you should really follow the opensuse-factory mailnglist when you use Factory. Especially now:

After Nov 4 Factory users should change their repositories, but they wont have to do anything until May 4th, when the old Factory repositories will be retired

More details will be discussed on the opensuse-factory mailinglist, with clear published advice closer to Nov 4th.

http://lists.opensuse.org/opensuse-factory/

#9

The folk who want a rolling release are looking for “the state of the art.”

And what could be more “state of the art” than confusion?

#10

True… rotfl!

#11

On 2014-11-01 17:06, nrickert wrote:
>
> wolfi323;2672239 Wrote:
>> The way it has been done (i.e. announce a more stable Factory as the new
>> rolling distribution, then decide three months later to call the
>> unstable one Factory again instead) just creates unnecessary confusion
>> I think. But well, it’s too late now…:\

Because they thought about it later. First they thought that Tumbleweed
might be redundant, as its single maintainer considered what to do:
continue it or not.

In the end, they decided to “take over” Tumbleweed, replacing it with
what was “factory tested”. Good.

And they thought that the original, untested factory, should also be
available.

So perhaps the forums should have both, factory-tumbleweed, and
factory-untested. Or something like that, and make it clear to users.

Perhaps the forum software should parse the messages, and when they
mention 13.2 or factory, suggest change location? If this is at all
possible.

> The folk who want a rolling release are looking for “the state of the
> art.”
>
> And what could be more “state of the art” than confusion?

LOL. Yep.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)