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#36423 - [gconf] .INSTALL relies on pidof without a dep on the package providing it
Attached to Project:
Arch Linux
Opened by Evan Callicoat (Apsu) - Monday, 05 August 2013, 17:00 GMT
Last edited by Jan de Groot (JGC) - Monday, 05 August 2013, 21:10 GMT
Opened by Evan Callicoat (Apsu) - Monday, 05 August 2013, 17:00 GMT
Last edited by Jan de Groot (JGC) - Monday, 05 August 2013, 21:10 GMT
|
DetailsThe extra/gconf package's install script uses the "pidof" binary provided (only) in sysvinit-tools, which is installed as a dep of systemd-sysvcompat, itself part of the "base" group. However neither package is a hard dependency of gconf, leading to this error:
(272/536) reinstalling gconf [########################################################################################] 100% /tmp/alpm_UrZcRr/.INSTALL: line 12: pidof: command not found I see this has been fixed in the package svn here nearly a month ago: https://projects.archlinux.org/svntogit/packages.git/commit/?h=packages/gconf&id=4f702adac425b0e82be4cbaf528ca2d7fa6a7dc6 Maybe the maintainer will see this and get it packaged up :) |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 05 August 2013, 21:10 GMT
Reason for closing: Won't fix
Additional comments about closing: It will be in a next version. Not killing gconf daemons after upgrade is not a big issue, esp given the fact that we're on the same upstream version for a long while now.
Monday, 05 August 2013, 21:10 GMT
Reason for closing: Won't fix
Additional comments about closing: It will be in a next version. Not killing gconf daemons after upgrade is not a big issue, esp given the fact that we're on the same upstream version for a long while now.