Installation of upgrade "openSUSE-2015-289 - Security update for subversion" fails

Hello,
this update is shown in the update list. When I try to use it the following error message shows:

Subprocess failed. Error: RPM fehlgeschlagen: error: unpacking of archive failed on file /srv/svn: cpio: mkdir

error: subversion-1.8.13-2.36.1.x86_64: install failed

error: subversion-1.8.11-2.33.1.x86_64: erase skipped

And actually since today the same errormessage is shown for the updates of “libssh” and “libdnsmasq”.

Can anybody help?

Thanks,
Johannes

Well, for some reason, rpm seems to be unable to create the directory /srv/svn.

What does “ls -l /srv” say?
And please also post the output of “dmesg|tail” afterwards, it might be caused by a filesystem corruption… (in particular as libssh and dnsmasq are affected as well)
Maybe run fsck.

Thanks!

After seeing the output of “ls -l /srv” I realized it was an old NTFS partitions (that I only kept for backup purposes after switching to Linux). I hadn’t mounted this partition during the installation. But for some reasons I needed data on this partition and mounted it…

Now I have permanently unmounted this partition and now everything works fine.

I am only surprised it was mounted in /srv. Maybe I used a default value without knowing the consequences…

Thanks,
Johannes

Oh. So it was indeed a “filesystem issue”… :wink:

I am only surprised it was mounted in /srv. Maybe I used a default value without knowing the consequences…

Did you use YaST->System->Partitioner?
One of the default mountpoint options is “/srv” there, but I don’t know what would be the default.
You can enter any mount point you like though, you don’t have to choose one from the list.

For temporary mounts, I wouldn’t use YaST though. You can just mount it with “mount”, would be much faster and, temporary.
In a GUI environment (KDE, GNOME, …) you can also temporarily mount partitions in your file manager.

On 2015-05-15 21:26, wolfi323 wrote:

> Did you use YaST->System->Partitioner?
> One of the default mountpoint options is “/srv” there, but I don’t know
> what would be the default.

There is no default. It is a droplist, which probably shows the next
unused entry in the list.

> You can enter any mount point you like though, you don’t have to choose
> one from the list.

Exactly.

It is curious how many people don’t notice this, and end by mounting on
strange places, or on top of system directories (say /var). :-? :-o


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

What I meant was that I don’t know whether an entry of the drop list would be preselected by default, or which one if any.

I checked now, and the field is empty by default, with a blinking cursor. So it actually should be obvious that you can type in something…
To get the drop list, you have to click on the down-arrow, /srv is 2nd in the list here after /home (I don’t have a separate /home partition, if you have one, /srv would probably be the first).

And you cannot continue without entering/selecting something either. YaST will display an error message that you have to specify a mount point in that case.

On 2015-05-16 03:36, wolfi323 wrote:
> robin_listas;2710114 Wrote:

>> There is no default. It is a droplist, which probably shows the next
>> unused entry in the list.
> What I meant was that I don’t know whether an entry of the drop list
> would be preselected by default, or which one if any.
>
> I checked now, and the field is empty by default, with a blinking
> cursor. So it actually should be obvious that you can type in
> something…
> To get the drop list, you have to click on the down-arrow, /srv is 2nd
> in the list here after /home (I don’t have a separate /home partition,
> if you have one, /srv would probably be the first).

I don’t have a disk to try now, and it would have to be an installation,
not on a running system. But I seem to recall that when you install a
system, the box is already filled: the first time with “/”, the second
with “/home”, etc. The third I don’t remember, likely “/srv” as you say.

> And you cannot continue without entering/selecting something either.
> YaST will display an error message that you have to specify a mount
> point in that case.

Yes, of course.

But it will not complain if you select /usr or /var, either, and of
course, doing that on an installed system will crash it. :slight_smile:


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Why?
The OP explicitely stated:

So he did it in the running system, not during installation.

> And you cannot continue without entering/selecting something either.
> YaST will display an error message that you have to specify a mount
> point in that case.

Yes, of course.

But it will not complain if you select /usr or /var, either, and of
course, doing that on an installed system will crash it. :slight_smile:

But my point was that you cannot just press OK without selecting a mount point, and thus accepting some default by mistake.

Yes, YaST will mount it immediately, so you’d definitely have problems in the running system if you choose /usr or /var… :wink:
But /var and /usr are not in the list anyway. It’s only /home, /srv, /tmp, and /usr/local here on this system (one partition for the whole openSUSE, including /home). If some of them are already used as mount points, they will not appear in the list (I tested this now as well).

On 2015-05-16 11:36, wolfi323 wrote:
>
> robin_listas;2710124 Wrote:
>>
>> I don’t have a disk to try now, and it would have to be an installation,
>> not on a running system.
> Why?
> The OP explicitely stated:
> jkegmxde;2710078 Wrote:
>> I hadn’t mounted this partition during the installation. But for some
>> reasons I needed data on this partition and mounted it…
> So he did it in the running system, not during installation.

Oh, right, I forgot.

>> Yes, of course.
>>
>> But it will not complain if you select /usr or /var, either, and of
>> course, doing that on an installed system will crash it. :slight_smile:
>>
> But my point was that you cannot just press OK without selecting a mount
> point, and thus accepting some default by mistake.

Ok.

Maybe sometimes there is something on the box, sometimes not. Dunno.

> Yes, YaST will mount it immediately, so you’d definitely have problems
> in the running system if you choose /usr or /var… :wink:
> But /var and /usr are not in the list anyway. It’s only /home, /srv,
> /tmp, and /usr/local here on this system (one partition for the whole
> openSUSE, including /home). If some of them are already used as mount
> points, they will not appear in the list (I tested this now as well).

Maybe they (usr and such) were there years ago, and I recall that :slight_smile:


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

There only is something in the text field if the partition is already mounted, or at least in the fstab (I’m not sure about the latter).

> Yes, YaST will mount it immediately, so you’d definitely have problems
> in the running system if you choose /usr or /var… :wink:
> But /var and /usr are not in the list anyway. It’s only /home, /srv,
> /tmp, and /usr/local here on this system (one partition for the whole
> openSUSE, including /home). If some of them are already used as mount
> points, they will not appear in the list (I tested this now as well).

Maybe they (usr and such) were there years ago, and I recall that :slight_smile:

Maybe. I have no idea.