Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#66668 - [gstreamer] errors out on upgrade
Attached to Project:
Arch Linux
Opened by T.J. Townsend (blakkheim) - Friday, 15 May 2020, 23:41 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 14 July 2020, 22:47 GMT
Opened by T.J. Townsend (blakkheim) - Friday, 15 May 2020, 23:41 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 14 July 2020, 22:47 GMT
|
DetailsDescription:
When upgrading the gstreamer package to 1.16.2-2, the following error is produced: :: Processing package changes... (1/6) upgrading gstreamer [#####################################] 100% Failed to set capabilities on file `usr/lib/gstreamer-1.0/gst-ptp-helper' (No such file or directory) usage: setcap [-q] [-v] [-n <rootid>] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ] Note <filename> must be a regular (non-symlink) file. error: command failed to execute correctly |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Tuesday, 14 July 2020, 22:47 GMT
Reason for closing: Not a bug
Additional comments about closing: Configuration issue.
Tuesday, 14 July 2020, 22:47 GMT
Reason for closing: Not a bug
Additional comments about closing: Configuration issue.
The file /usr/lib/gstreamer-1.0/gst-ptp-helper does exist after removing the package and reinstalling it, but that doesn't explain the error.
Noob question, but should usr be /usr there? I assumed it ran from / but the error message lacks the initial / too.
Do you use a wrapper for pacman?
For some reason pacman is running post_upgrade() from /root instead of / as it should.
Running it as root (not with sudo) prints /
So sudo is resetting the directory somehow. Any ideas?
Running "env" in post_upgrade() gives the following:
SHELL=/bin/bash
SUDO_GID=1000
HISTSIZE=1
SUDO_COMMAND=/sbin/pacman -Syu
SUDO_USER=myuser
PWD=/root
LOGNAME=root
HOME=/root
LANG=en_US.UTF-8
TERM=screen
USER=root
HTTP_USER_AGENT=pacman/5.2.1 (Linux x86_64) libalpm/12.0.1
SHLVL=1
PATH=/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin
SUDO_UID=1000
MAIL=/var/mail/root
OLDPWD=/
_=/sbin/env
...
So, with sudo:
PWD is /root and OLDPWD is /.
And with su -:
PWD is / and OLDPWD is /root.