You are not logged in.

#1 2019-09-14 16:11:45

reflets de vert
Member
Registered: 2010-03-20
Posts: 70
Website

[Solved] wayland-protocols already present

When I try to update, I have this message, "already present in the filesystem".

I searched about this, and there is many ways to solve it (pacman --overwrite - don't understand how to use it, I read man pacman and tried the command). What is the best way, I don't understand well what is better.

Here is my error message:

:: Proceed with installation? [Y/n] y
(383/383) checking keys in keyring                                                                           [----------------------------------------------------------------] 100%
(383/383) checking package integrity                                                                         [----------------------------------------------------------------] 100%
(383/383) loading package files                                                                              [----------------------------------------------------------------] 100%
(383/383) checking for file conflicts                                                                        [----------------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
wayland-protocols: /usr/share/licenses/wayland-protocols/COPYING exists in filesystem
wayland-protocols: /usr/share/pkgconfig/wayland-protocols.pc exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/stable/presentation-time/presentation-time.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/stable/viewporter/viewporter.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/stable/xdg-shell/xdg-shell.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/idle-inhibit/idle-inhibit-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/input-method/input-method-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/input-timestamps/input-timestamps-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/pointer-gestures/pointer-gestures-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/primary-selection/primary-selection-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/relative-pointer/relative-pointer-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v2.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v3.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-decoration/xdg-decoration-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v2.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-output/xdg-output-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v5.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v6.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml exists in filesystem
Errors occurred, no packages were upgraded.

I tried to remove wayland-protocols, but there are so many dependancies, it's too much.

Last edited by reflets de vert (2019-09-15 18:00:26)


I'm against internet totalitarians of any kind.
And like cheese's humor.

Offline

#2 2019-09-14 16:28:55

Swiggles
Member
Registered: 2014-08-02
Posts: 260

Re: [Solved] wayland-protocols already present

Offline

#3 2019-09-14 22:54:33

reflets de vert
Member
Registered: 2010-03-20
Posts: 70
Website

Re: [Solved] wayland-protocols already present

it's not so clear

When I do pacman -Qo, I have:

sudo pacman -Qo /usr/share/pkgconfig/wayland-protocols.pc
error: No package owns /usr/share/pkgconfig/wayland-protocols.pc

No package contains /usr/share/pkgconfig/wayland-protocols.pc

when doing overwrite, I have:

sudo pacman -S --overwrite glob wayland-protocols
resolving dependencies...
looking for conflicting packages...

Packages (1) wayland-protocols-1.18-1

Total Installed Size:  0.40 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                                                               [----------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                             [----------------------------------------------------------------] 100%
(1/1) loading package files                                                                                  [----------------------------------------------------------------] 100%
(1/1) checking for file conflicts                                                                            [----------------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
wayland-protocols: /usr/share/licenses/wayland-protocols/COPYING exists in filesystem
wayland-protocols: /usr/share/pkgconfig/wayland-protocols.pc exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/stable/presentation-time/presentation-time.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/stable/viewporter/viewporter.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/stable/xdg-shell/xdg-shell.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/idle-inhibit/idle-inhibit-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/input-method/input-method-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/input-timestamps/input-timestamps-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/pointer-gestures/pointer-gestures-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/primary-selection/primary-selection-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/relative-pointer/relative-pointer-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v2.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v3.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-decoration/xdg-decoration-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v2.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-output/xdg-output-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v5.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v6.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml exists in filesystem
Errors occurred, no packages were upgraded.

Last edited by reflets de vert (2019-09-15 13:41:38)


I'm against internet totalitarians of any kind.
And like cheese's humor.

Offline

#4 2019-09-14 23:15:34

loqs
Member
Registered: 2014-03-06
Posts: 8,798

Re: [Solved] wayland-protocols already present

You placed glob literally in the command.  You need to generate a glob that will match all the entries you want to overwrite.
Possibly

/usr/share/licenses/wayland-protocols/COPYING,/usr/share/pkgconfig/wayland-protocols.pc,/usr/share/wayland-protocols*

Offline

#5 2019-09-14 23:15:59

Swiggles
Member
Registered: 2014-08-02
Posts: 260

Re: [Solved] wayland-protocols already present

I don't want to sound rude, but you know what a glob is? If not search for it and read the directions very carefully.

And please prefix your commands with LANG=C so people who don't speak french can still understand it. smile

Offline

#6 2019-09-14 23:21:23

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 28,061
Website

Re: [Solved] wayland-protocols already present

Pleaae read the Code of Conduct, notably https://wiki.archlinux.org/index.php/Co … ow_to_post and update your thread title to remove the redundant [update] decriptor and past output in English


Moving to NC...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#7 2019-09-15 13:35:34

reflets de vert
Member
Registered: 2010-03-20
Posts: 70
Website

Re: [Solved] wayland-protocols already present

Ok, sorry, I translated all the terminal output

No, I don't know what it is, but when I do man pacman, I read this (sorry to be rude against people who write man pages, but I don't find even three words to say what can be glob!):

       --overwrite <glob>
           Bypass file conflict checks and overwrite conflicting files. If the package that is about to be installed contains files that are already installed and match glob,
           this option will cause all those files to be overwritten. Using --overwrite will not allow overwriting a directory with a file or installing packages with
           conflicting files and directories. Multiple patterns can be specified by separating them with a comma. May be specified multiple times. Patterns can be negated,
           such that files matching them will not be overwritten, by prefixing them with an exclamation mark. Subsequent matches will override previous ones. A leading literal
           exclamation mark or backslash needs to be escaped.

The wiki pages says:

Every installed package provides a /var/lib/pacman/local/package-version/files file that contains metadata about this package. If this file gets corrupted, is empty or goes missing, it results in file exists in filesystem errors when trying to update the package. Such an error usually concerns only one package. Instead of manually renaming and later removing all the files that belong to the package in question, you may explicitly run pacman -S --overwrite glob package to force pacman to overwrite files that match glob.

Warning: Generally avoid using the --overwrite switch. See System maintenance#Avoid certain pacman commands.

And:

Generally avoid using the --overwrite option with pacman. The --overwrite option takes an argument containing a glob. When used pacman will bypass file conflict checks for files that match the glob. In a properly maintained system, it should only be used when explicitly recommended by the Arch developers. See the #Read before upgrading the system section.

For me it's unclear, and it's not easy to find good explanations about pacman --overwrite… to securely doing things… and what glob is…!

https://bbs.archlinux.org/viewtopic.php?id=237616
https://bbs.archlinux.org/viewtopic.php?id=237614

(here it's a little bit more clear… https://github.com/BlackArch/blackarch/issues/2046 and I see other people have tested randomly the overwrite command because of they didn't find explanations)

Last edited by reflets de vert (2019-09-15 14:03:59)


I'm against internet totalitarians of any kind.
And like cheese's humor.

Offline

#8 2019-09-15 14:03:51

progandy
Member
Registered: 2012-05-17
Posts: 3,546

Re: [Solved] wayland-protocols already present

The pacman manpage should probably refer to the glob(7) manpage. You could create a feature request/bug report. At the moment I'm not really sure which subset of the glob features is followed. At the minimum it undestands star and question mark.

man 7 glob

Last edited by progandy (2019-09-15 14:07:39)


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

#9 2019-09-15 14:07:13

Swiggles
Member
Registered: 2014-08-02
Posts: 260

Re: [Solved] wayland-protocols already present

Please help yourself by reading all the answers in this thread. The full solution including what a glob is are already here. Additionally it is also answered in your first link.

Last edited by Swiggles (2019-09-15 14:08:06)

Offline

#10 2019-09-15 14:07:26

reflets de vert
Member
Registered: 2010-03-20
Posts: 70
Website

Re: [Solved] wayland-protocols already present

No

man pacman | grep glob
       --overwrite <glob>                                                                                                                                                           
           Bypass file conflict checks and overwrite conflicting files. If the package that is about to be installed contains files that are already installed and match glob,  

I didn't find any reference for glob:

SEE ALSO
       alpm-hooks(5), libalpm(3), makepkg(8), pacman.conf(5)

       See the pacman website at https://www.archlinux.org/pacman/ for current information on pacman and its related tools.

For me, it's not about helping only myself to understand, but other people too.

They say overwrite must be used with care. I can think I must really be sure before overwriting, and then do further researchs to avoid system crash.
In the wiki they write overwrite must be used only when explicitly recommanded by developpers.

Last edited by reflets de vert (2019-09-15 14:19:29)


I'm against internet totalitarians of any kind.
And like cheese's humor.

Offline

#11 2019-09-15 14:47:44

reflets de vert
Member
Registered: 2010-03-20
Posts: 70
Website

Re: [Solved] wayland-protocols already present

I tried a command, here's the result:

# pacman -S --overwrite /usr/share/licences/wayland-protocols/COPYING,/usr/share/pkgconfig/wayland-protocols.pc,/usr/share/wayland-protocols* wayland-protocols 
looking for conflicting packages...

Packages (1) wayland-protocols-1.18-1

Total Installed Size:  0.40 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                                                               [----------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                             [----------------------------------------------------------------] 100%
(1/1) loading package files                                                                                  [----------------------------------------------------------------] 100%
(1/1) checking for file conflicts                                                                            [----------------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
wayland-protocols: /usr/share/licenses/wayland-protocols/COPYING exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/stable/presentation-time/presentation-time.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/stable/viewporter/viewporter.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/stable/xdg-shell/xdg-shell.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/idle-inhibit/idle-inhibit-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/input-method/input-method-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/input-timestamps/input-timestamps-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/pointer-gestures/pointer-gestures-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/primary-selection/primary-selection-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/relative-pointer/relative-pointer-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v2.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v3.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-decoration/xdg-decoration-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v2.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-output/xdg-output-unstable-v1.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v5.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v6.xml exists in filesystem
wayland-protocols: /usr/share/wayland-protocols/unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml exists in filesystem
Errors occurred, no packages were upgraded.

I'm against internet totalitarians of any kind.
And like cheese's humor.

Offline

#12 2019-09-15 15:02:36

ayekat
Member
Registered: 2011-01-17
Posts: 1,348
Website

Re: [Solved] wayland-protocols already present

The first pattern's got a typo, it should be /usr/share/licenses.

And you probably want to put the glob between quotes, otherwise the * is likely going to be evaluated by the shell.

--edit: what the hell…

Last edited by ayekat (2019-09-15 17:10:15)


{,META,RE}PKGBUILDSpacman-hacks (includes makemetapkg and remakepkg) │ dotfiles

Offline

#13 2019-09-15 15:11:53

Swiggles
Member
Registered: 2014-08-02
Posts: 260

Re: [Solved] wayland-protocols already present

I am not sure whether it has been fixed or not, but in the past the leading slash mustn't be there, because it was looking at the package structure. Let's do the full command without wildcards instead:

pacman -Syu --overwrite=usr/share/licenses/wayland-protocols/COPYING,usr/share/wayland-protocols/stable/presentation-time/presentation-time.xml,usr/share/wayland-protocols/stable/viewporter/viewporter.xml,usr/share/wayland-protocols/stable/xdg-shell/xdg-shell.xml,usr/share/wayland-protocols/unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml,usr/share/wayland-protocols/unstable/idle-inhibit/idle-inhibit-unstable-v1.xml,usr/share/wayland-protocols/unstable/input-method/input-method-unstable-v1.xml,usr/share/wayland-protocols/unstable/input-timestamps/input-timestamps-unstable-v1.xml,usr/share/wayland-protocols/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml,usr/share/wayland-protocols/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml,usr/share/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml,usr/share/wayland-protocols/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml,usr/share/wayland-protocols/unstable/pointer-gestures/pointer-gestures-unstable-v1.xml,usr/share/wayland-protocols/unstable/primary-selection/primary-selection-unstable-v1.xml,usr/share/wayland-protocols/unstable/relative-pointer/relative-pointer-unstable-v1.xml,usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v1.xml,usr/share/wayland-protocols/unstable/tablet/tablet-unstable-v2.xml,usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v1.xml,usr/share/wayland-protocols/unstable/text-input/text-input-unstable-v3.xml,usr/share/wayland-protocols/unstable/xdg-decoration/xdg-decoration-unstable-v1.xml,usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v1.xml,usr/share/wayland-protocols/unstable/xdg-foreign/xdg-foreign-unstable-v2.xml,usr/share/wayland-protocols/unstable/xdg-output/xdg-output-unstable-v1.xml,usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v5.xml,usr/share/wayland-protocols/unstable/xdg-shell/xdg-shell-unstable-v6.xml,usr/share/wayland-protocols/unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml

Offline

#14 2019-09-15 15:20:59

reflets de vert
Member
Registered: 2010-03-20
Posts: 70
Website

Re: [Solved] wayland-protocols already present

I did this without the quotes, and without your advice : (

I was too fast trying commands.

Hope it's ok.

$ sudo pacman -S --overwrite /usr/share/licenses/wayland-protocols/COPYING,/usr/share/pkgconfig/wayland-protocols.pc,/usr/share/wayland-protocols* wayland-protocols[sudo] password for daniel: 
resolving dependencies...
looking for conflicting packages...

Packages (1) wayland-protocols-1.18-1

Total Download Size:   0.06 MiB
Total Installed Size:  0.40 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 wayland-protocols-1.18-1-any                                                        59.5 KiB   184K/s 00:00 [----------------------------------------------------------------] 100%
(1/1) checking keys in keyring                                                                               [----------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                             [----------------------------------------------------------------] 100%
(1/1) loading package files                                                                                  [----------------------------------------------------------------] 100%
(1/1) checking for file conflicts                                                                            [----------------------------------------------------------------] 100%
(1/1) checking available disk space                                                                          [----------------------------------------------------------------] 100%
:: Processing package changes...
(1/1) upgrading wayland-protocols                                                                            [----------------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

Last edited by reflets de vert (2019-09-15 15:23:12)


I'm against internet totalitarians of any kind.
And like cheese's humor.

Offline

Board footer

Powered by FluxBB