| Age | Commit message (Collapse) | Author | Files | Lines | 
|---|
|  | Closes: #721244 | 
|  | /etc/systemd/system/<service> already exists (but is not a symlink).
Closes: #739090 | 
|  |  | 
|  | We cannot just unconditionally unmask services on installation time,
otherwise “systemctl mask” executed by the user will be reversed.
To that end, files in /var/lib/systemd/deb-systemd-helper-masked/ signal
that d-s-h masked the service and is allowed to unmask it. | 
|  | This particular test was written under the (wrong) assumption that
masking a service is pointing its install (!) symlink to /dev/null,
while in reality it’s a different symlink. | 
|  | Turns out that I mistakenly linked the same symlinks to /dev/null that
one would normally link to the service file, but mask links are
orthogonal to that. As an example, for rsyslog.service, the mask link is
/etc/systemd/system/rsyslog.service -> /dev/null, not
/etc/systemd/system/mult-user.targe.wants/rsyslog.service
fixes #714903 | 
|  |  | 
|  |  | 
|  |  | 
|  | Updates that add new service files or remove existing ones are now also
tested (using update-state).
Furthermore, the Also= and Alias= statements in unit files are now
tested, too. | 
|  |  | 
|  |  | 
|  |  |