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!
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!
FS#28650 - [systemd-sysvcompat] Shouldn't it provide 'sysvinit'?
Attached to Project:
Arch Linux
Opened by Marcos Mello (marcosfrm) - Saturday, 25 February 2012, 15:42 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 25 February 2012, 19:34 GMT
Opened by Marcos Mello (marcosfrm) - Saturday, 25 February 2012, 15:42 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 25 February 2012, 19:34 GMT
|
DetailsWhen I try to install systemd-sysvcompat 2-1 pacman say it will remove sysvinit, but the install stops because broken deps since 'initscripts' depends on 'sysvinit'.
For what I could understand systemd-sysvcompat installs systemd and set-up symlinks to keep the current initscripts working. Or not? Arch's systemd wiki doesn't mention systemd-sysvcompat... |
This task depends upon
Closed by Dave Reisner (falconindy)
Saturday, 25 February 2012, 19:34 GMT
Reason for closing: Not a bug
Additional comments about closing: working as intended
Saturday, 25 February 2012, 19:34 GMT
Reason for closing: Not a bug
Additional comments about closing: working as intended
Comment by Dave Reisner (falconindy) -
Saturday, 25 February 2012, 19:34 GMT
No, it shouldn't provide sysvinit. If you're installing this package, you're stating that you _arent_ using Arch's initscripts.