Package Details: sysvinit 2.99-2

Git Clone URL: (read-only, click to copy)
Package Base: sysvinit
Description: Linux System V Init
Upstream URL:
Licenses: GPL
Conflicts: systemd-sysvcompat
Provides: sysvinit
Submitter: maandree
Maintainer: eatmyvenom
Last Packager: eatmyvenom
Votes: 29
Popularity: 0.004187
First Submitted: 2013-05-16 16:45
Last Updated: 2021-03-03 00:18

Latest Comments

1 2 Next › Last »

wrath commented on 2021-01-08 09:00

I get an error with the checksum of the archive

eatmyvenom commented on 2021-01-07 00:07

The e2fsprogs conflict was fixed on the git version of this package. I will fix it here as well shortly.

michabuntu commented on 2021-01-04 05:09

error: failed to commit transaction (conflicting files)

sysvinit: /usr/bin/logsave exists in filesystem (owned by e2fsprogs)

sysvinit: /usr/share/man/man8/logsave.8.gz exists in filesystem (owned by e2fsprogs)

aaditya commented on 2014-06-15 07:00

Leads to errors in installation as it does not conflict with systemd-sysvcompat.

artoo commented on 2014-05-22 17:11

Should only depend on glibc

artoo commented on 2014-05-22 14:36

namcap tells in clean chroot build that procps-ng is not needed as dep.

r08 commented on 2014-04-03 02:06

Thanks for the update. killall5 works and bootlogd is present

mdevaev commented on 2013-12-24 15:59

It's very strange, I did not have the desired.

maandree commented on 2013-12-18 16:37

procps-ng=3.3.9 added the command `pidof` which as
alreadly provided by sysvinit-tools, therefore procps-ng
as marked as providing (even it was only partially
providing) and conflicting with sysvinit-tools.

sysvinit=2.88-13 required sysvinit-tools, (installed from the
same source as sysvinit) so sysvinit now instead requires
procps-ng>=3.3.9 to get `pidof` and the split of sysvinit
and sysvinit-tools have been removed; without marking
sysvinit as providing sysvinit-tools because that would case
an unresolvable conflict.

x33a commented on 2013-12-18 12:51

@ mdevaev

This package provides all the utilities present in your package, as well, without conflicting with procps-ng.