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.
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.
FS#55206 - [pacman-contrib] checkupdates sets wrong exit status when network is down
Attached to Project:
Pacman
Opened by Andrew Barchuk (raindev) - Sunday, 20 August 2017, 12:12 GMT
Last edited by Allan McRae (Allan) - Wednesday, 13 September 2017, 03:26 GMT
Opened by Andrew Barchuk (raindev) - Sunday, 20 August 2017, 12:12 GMT
Last edited by Allan McRae (Allan) - Wednesday, 13 September 2017, 03:26 GMT
|
DetailsDescription:
checkupdates do not set error exit status when updates can't be fetched. When pacman -Sy command fails, its result is ignored and the script exits with status code of 0. Would be nice to let the user know when updates can't be fetched vs when no updates are available. Attached a diff with a possible fix. Additional info: $ pacman -Q pacman pacman 5.0.2-2 Example: $ checkupdates $ echo $? 0 $ ping -c4 example.com ping: example.com: Name or service not known 
checkupdates.diff
(0.2 KiB)
|
This task depends upon
Closed by Allan McRae (Allan)
Wednesday, 13 September 2017, 03:26 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in pacman-contrib project
Wednesday, 13 September 2017, 03:26 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in pacman-contrib project
You're going to want to send that to the pacman-contrib mailing list BTW: https://lists.archlinux.org/listinfo/pacman-contrib