You are not logged in.

Pages: 1

#1 2018-01-09 11:05:11

karcher
Member
Registered: 2018-01-09
Posts: 140

error: file owned by 'zfs-utils' and 'zfs-utils-common'

Hi all,

since a while I'm getting errors about zfs every time I try to update with yaourt:
$ yaourt -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
archlinuxfr is up to date
archzfs is up to date
error: file owned by 'zfs-utils' and 'zfs-utils-common': 'etc/default/zfs'
error: file owned by 'zfs-utils' and 'zfs-utils-common': 'etc/sudoers.d/zfs'
...
error: file owned by 'zfs-utils' and 'zfs-utils-common': 'usr/share/zfs/zpool-create.sh'

Any ideas?

Offline

#2 2018-01-09 12:22:44

lo1
Member
Registered: 2017-09-25
Posts: 584

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

What if you update with pacman -Syu instead?

How To Ask Questions The Smart Way && Tacts Filters && K.I.S.S. &&
Rootless Root

Offline

#3 2018-01-09 13:04:17

karcher
Member
Registered: 2018-01-09
Posts: 140

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

Thanks for your response!
I don't get any errors when I run pacman -Syu. So it seems to be an issue with yaourt and zfs permissions.

Offline

#4 2018-01-09 13:26:25

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,882
Website

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

It looks like you have two packages providing the same files. Do you know how that happened? Please post your pacman.log.

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#5 2018-01-09 13:46:58

karcher
Member
Registered: 2018-01-09
Posts: 140

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

@WorMzy: Thanks for your response!
No, I don't know how that happened. Maybe I did something wrong without knowing it.
The pacman.log has around 9'500 lines in it. Can I post it directly here or upload it as a text file?

Offline

#6 2018-01-09 13:51:15

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,882
Website

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

A pastebin service would be preferable for a file of that size. See https://wiki.archlinux.org/index.php/Li … in_clients for recommendations.

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#7 2018-01-09 13:56:14

Lone_Wolf
Forum Moderator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,948

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

Maybe I did something wrong without knowing it.

archlinuxfr is up to date

Please remove archlinuxfr repo from pacman.conf, it can cause many problems.

Last edited by Lone_Wolf (2018-01-09 13:56:45)

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#8 2018-01-09 14:30:13

karcher
Member
Registered: 2018-01-09
Posts: 140

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

@WorMzy: I've uploaded the pacman.log here:
https://ptpb.pw/N9w7

@Lone_Wolf: Thanks for your response!
But archlinuxfr is necessary for yaourt and AUR, or not?

Offline

#9 2018-01-09 14:46:52

seth
Member
Registered: 2012-09-03
Posts: 51,468

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

No.

Edit: looking at the packages, zsf-utils and zfs-utils-common are in conflict w/o being marked as such. Both provide the same stuff.
How did you install which of them originally?

Last edited by seth (2018-01-09 14:50:07)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2018-01-09 15:28:59

karcher
Member
Registered: 2018-01-09
Posts: 140

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

@seth: Thanks for your response!

I have removed zsf-utils and spl-utils. Now when I run yaourt -Syu I don't see any errors!
But I see in my notices that these packages were installed as dependencies when I installed zfs-dkms.

Offline

#11 2018-01-09 15:37:08

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,882
Website

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

Your problem is this:

[2017-10-21 19:56] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-21 20:55] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-22 10:42] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-23 10:21] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-23 11:10] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-24 00:37] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-24 10:38] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-25 08:35] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-25 19:11] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-26 08:52] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-30 00:21] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-31 23:27] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-10-31 23:38] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-01 00:48] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-04 01:42] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-04 10:51] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-06 10:33] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-07 00:00] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-07 10:32] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-08 01:18] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-08 23:45] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-10 02:04] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-11 01:04] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-11 09:55] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-11 16:52] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-12 02:38] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-12 11:25] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-12 15:27] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-13 01:25] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-13 08:56] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-14 00:46] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-15 01:53] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-15 10:17] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-16 11:39] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-17 01:54] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-17 12:28] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-18 01:05] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-19 03:43] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-20 02:06] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-20 23:32] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-21 00:33] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-21 12:22] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-22 03:47] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-22 23:59] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-23 10:40] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-24 00:58] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-25 01:12] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-25 12:21] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-27 10:01] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-27 11:24] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-27 23:17] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-28 11:44] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-29 00:33] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-29 08:47] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-29 11:47] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-29 23:59] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-30 08:30] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-30 08:46] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-11-30 23:16] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-01 23:40] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-02 08:06] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-04 10:45] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-05 11:12] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-05 12:24] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-05 20:08] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-05 21:03] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-05 21:27] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-06 10:02] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-07 11:04] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-07 14:48] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-07 22:01] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-08 01:42] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-09 11:34] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-09 15:55] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-09 21:15] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-10 02:20] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-10 11:16] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-10 11:49] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-11 00:05] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-11 10:19] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-11 12:08] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-11 23:11] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-12 05:28] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-12 09:38] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-12 13:18] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-12 21:44] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-12 22:32] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-13 10:20] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-13 11:08] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-14 00:30] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-14 09:22] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-14 22:13] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-15 10:59] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-15 13:36] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-15 14:00] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-15 17:02] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-16 01:52] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-16 11:51] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-16 14:02] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-16 18:47] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-16 21:24] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-16 23:15] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-17 22:58] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-17 23:26] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-18 08:54] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-18 13:05] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-18 23:21] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-19 15:17] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-19 21:35] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-19 23:33] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-19 23:38] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-19 23:41] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-20 08:46] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-20 23:06] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-21 09:36] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-22 00:50] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-22 08:07] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-23 00:11] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-23 00:14] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-23 10:56] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-23 23:28] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-24 11:27] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-24 23:29] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-25 04:32] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-25 12:14] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-25 17:40] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-25 23:30] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-25 23:30] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-26 12:04] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-26 23:38] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-27 10:34] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-27 23:34] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-28 00:02] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-28 11:33] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2017-12-29 11:03] [PACMAN] Running 'pacman -Syu --noconfirm --force'
[2018-01-09 10:43] [PACMAN] Running 'pacman -Syu --noconfirm --force'

Why on earth are you using --force?

man pacman wrote:
       --force
           Bypass file conflict checks and overwrite conflicting files. If the
           package that is about to be installed contains files that are
           already installed, this option will cause all those files to be
           overwritten. Using --force will not allow overwriting a directory
           with a file or installing packages with conflicting files and
           directories. This option should be used with care, ideally not at
           all.

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#12 2018-01-09 15:49:33

karcher
Member
Registered: 2018-01-09
Posts: 140

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

@WorMzy: I didn't initiate such a command in the terminal, at least today. I have used the graphical package manager to update the system.

Offline

#13 2018-01-09 15:50:41

loqs
Member
Registered: 2014-03-06
Posts: 17,411

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

karcher wrote:

@Lone_Wolf: Thanks for your response!
But archlinuxfr is necessary for yaourt and AUR, or not?

No archlinuxfr is not necessary for yaourt and neither archlinuxfr or yaourt are necessary for AUR.
Edit:
Did you look at the dates on the output Wormzy highlighted?
What graphical package manager?
Edit2:

[2017-09-28 19:59] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-nick/PKGDEST.P0E/pamac-aur-6.0.2-1-any.pkg.tar.xz'
[2017-09-28 19:59] [ALPM] transaction started
[2017-09-28 19:59] [ALPM] installed pamac-aur (6.0.2-1)

pamac?

Last edited by loqs (2018-01-09 16:07:16)

Offline

#14 2018-01-09 15:57:51

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

The only thing that [archlinuxfr] is good at is breaking things.

How did you install Arch?

Last edited by Slithery (2018-01-09 15:58:36)

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#15 2018-01-09 16:38:26

karcher
Member
Registered: 2018-01-09
Posts: 140

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

@loqs: Thanks for your response!
pamac-aur

@slithery: Thanks for your response!
What do you mean? If you mean if it's vanilla Arch, I can assure you it is.

Offline

#16 2018-01-09 17:29:33

loqs
Member
Registered: 2014-03-06
Posts: 17,411

Re: error: file owned by 'zfs-utils' and 'zfs-utils-common'

If pamac is using the force option every time it performs a system update I suggest you stop using pamac.  For the requirements for using AUR see Arch_User_Repository.

Offline

Pages: 1

Board footer

Powered by FluxBB