Community Packages

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!
Tasklist

FS#28028 - [pacmatic] Non-root use of 'pacmatic -Ss'

Attached to Project: Community Packages
Opened by Karol Błażewicz (karol) - Saturday, 21 January 2012, 14:38 GMT
Last edited by Kyle Keen (keenerd) - Saturday, 21 January 2012, 16:50 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I've read https://bbs.archlinux.org/viewtopic.php?pid=943396#p943396 that
Pacmatic needs root permissions to update the log files (arch-news.log and pacman.log) and run pacman and edit the files in /etc. So Pacmatic will be running as root and your diff program needs to be exported in root's bashrc.

but I'm not sure if it needs to be run as root for searching. If it does, it would be nice to have this in the man page.

[karol@black ~]$ pacmatic -Ssq zlib
find: `/etc/sudoers.d': Permission denied
perl
zlib
haskell-zlib
lua-zlib
/usr/bin/pacmatic: line 207: /var/log/pacman.log: Permission denied
find: `/etc/sudoers.d': Permission denied
No pacnew files to update.

This task depends upon

Closed by  Kyle Keen (keenerd)
Saturday, 21 January 2012, 16:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in pacmatic-20120121
Comment by Karol Błażewicz (karol) - Saturday, 21 January 2012, 14:40 GMT
It seems to need root even for

[karol@black ~]$ pacmatic -Qq zlib
find: `/etc/sudoers.d': Permission denied
zlib
/usr/bin/pacmatic: line 207: /var/log/pacman.log: Permission denied
find: `/etc/sudoers.d': Permission denied
No pacnew files to update.
Comment by Kyle Keen (keenerd) - Saturday, 21 January 2012, 16:17 GMT
This is a feature of Pacmatic. It logs the calling args* and exit status of every invocation.

* Well, it used to. This feature was merged into Pacman, so Pacmatic does not do it any more.

I'll make this logging fail silently.

Loading...