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#25469 - [systemd] install script has wrong `if` tests

Attached to Project: Community Packages
Opened by Damjan Georgievski (damjan) - Tuesday, 09 August 2011, 01:18 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 09 August 2011, 02:06 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Name : systemd
Version : 33-1

I'm maybe tired and blind, but it seems to me that there's a problem with the install script in the systemd package.
The tests it does in `if`s are oposite of what they need to be, for ex:

if usr/bin/getent group lock >/dev/null; then
usr/sbin/groupadd -g 54 lock
fi

`if getent group lock` will only create the group if the group already exists (i.e getent returns success). but when the group doesn't exist, getent returns failure, and the block after then IS NOT executed.

The same thing in this case:

if [ -f etc/machine-id ]; then
bin/systemd-machine-id-setup
fi

if the file exists, try to create it (???). it should be, if it doesn't exists, the create it.
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 09 August 2011, 02:06 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd 33-2
Comment by Dave Reisner (falconindy) - Tuesday, 09 August 2011, 02:01 GMT
I'll tell you who's tired and blind... it's me. Must have slipped when I refactored this. Thanks. I'll tag a new pkgrel.

Loading...