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#64219 - [pacman-contrib] use a different exit code when checkupdates doesn't find updates

Attached to Project: Community Packages
Opened by nl6720 (nl6720) - Tuesday, 22 October 2019, 16:26 GMT
Last edited by Daniel M. Capella (polyzen) - Wednesday, 23 October 2019, 13:16 GMT
Task Type Feature Request
Category Packages: Testing
Status Closed
Assigned To Johannes Löthberg (demize)
Daniel M. Capella (polyzen)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Currently it's not possible, by looking at the exit code, to distinguish if checkupdates didn't find any updates or it failed in a different manner.

This complicates creating a systemd timer that runs `checkupdates --download`, since the service would be marked as "failed" if checkupdates doesn't find updates. If checkupdates would return e.g. "2" instead of "1" then It would be possible to use "SuccessExitStatus=" in the unit file. Currently I'm using "ExecStart=-/usr/bin/checkupdates --download", but that's not ideal since it ignores real errors.


Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any
pacman-contrib 1.2.0-3


Steps to reproduce:
On a fully updated system run:
checkupdates ; echo $?
This task depends upon

Closed by  Daniel M. Capella (polyzen)
Wednesday, 23 October 2019, 13:16 GMT
Reason for closing:  Implemented
Additional comments about closing:  https://git.archlinux.org/pacman-contrib .git/commit/?id=3da550ef93ae0b9998361810 44d33a8147a00088

Loading...