Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#22558 - Trigger to inform administrater when selected packages are updated

Attached to Project: Pacman
Opened by Erik Ridderby (Paddlaren) - Saturday, 22 January 2011, 20:08 GMT
Last edited by Dan McGee (toofishes) - Monday, 24 January 2011, 14:35 GMT
Task Type Feature Request
Category Packages: Core
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

Description:
Please add the possibility to trigger a notification to root when selected packages is updated through pacman.

Propsal:
Add a file in /etc where packages to monitor is entered (one package at a line).

When packman -Sy or perhaps when packamn -Su is executed, the proposed changes is checked towards the file in /etc and if a package listed in the file is about to be upgraded the user shall be notified.
If this is taken as a mere notification, there shall be no need to keep a cache; package about to be installed is in list -> notify.

The rationale:
There are sometimes a dependency between packages in pacman and packages in AUR or in source fetched elsewhere. A concrete example is VirtualBox 4 where some packages are located in pacman and one (extensions that where earlier in non-OSE version) is located in AUR.

Also, I have an own kernel as I have had strangeularities in the defualt one (it is a pain to gather information enought to write a relevant bug-request). Thus I will need to manually trace some of the modules I know will need to be compiled towards my own kernel (nvidia for example).



Additional info:


Steps to reproduce:
This task depends upon

Closed by  Dan McGee (toofishes)
Monday, 24 January 2011, 14:35 GMT
Reason for closing:  Won't implement
Additional comments about closing:  KISS, use another less intrusive way to implement this to fit your needs.
Comment by Gaetan Bisson (vesath) - Saturday, 22 January 2011, 20:45 GMT
You should not update your system blindly: you must read pacman's output.
Other than that, I note that the feature you want is easily scripted:
pacman -Syu &> pacman.log; egrep -q '(package1|package2|...)' pacman.log && mail root@localhost < pacman.log
Comment by Erik Ridderby (Paddlaren) - Saturday, 22 January 2011, 21:07 GMT
Well,
I was rather thinking of just a "The following monitored packaged will be modified" along with everything else. Sometimes an update contains a load of packages and it is easy to miss a package. Start making wrappers around pacman is an alternative but it just seems like the start of a endless journey of scripting.

BR
Erik
Comment by Dan McGee (toofishes) - Saturday, 22 January 2011, 23:01 GMT
1) Pacman can only be run by an administrator, so they should know what they are doing.
2) Turn on UseSyslog and write something with logwatch to do what you ask. Much easier than changing how you invoke pacman.

Won't be implementing this.

Loading...