![](https://seccdn.libravatar.org/avatar/e76779f0629280df6d2dfce07e4e1600.jpg?s=120&d=mm&r=g)
Hello, Am Dienstag, 2. April 2013 schrieb Frederic Crozat:
Le mardi 02 avril 2013 à 10:27 +0200, Andreas Jaeger a écrit :
On Tuesday, April 02, 2013 10:06:46 Michal Kubecek wrote:
On Fri, Mar 29, 2013 Cristian Rodríguez wrote:
Does anyone have access to a full unpacked tree of factory and can post what packages contain init scripts but not service files so can take look at them ? there is no rpmlint check for that :-|
grepping ARCHIVES.gz might be helpful ;-) (and it might be helpful to have an ARCHIVES.gz for factory)
The only case where it should be an error is "early boot" initscripts (the one named boot.*). Support for that has been removed in upstream systemd
Nice[tm]. What's the reason for this? (I assume "let's break some initscripts from stone age" was not the reason - I seriously hope Lennart is not evil enough for that ;-)
and I'd prefer to not backport the support in our systemd, if we can avoid it..
At the moment you'll break lots of packages and, more important, break lots of basic features like RAID and LVM. I'll give you a short overview from my system (Factory, last updated about 3 weeks ago): # cd /etc/init.d && for file in boot.* ; do echo === $file ===; pac=$(rpm -qf $file); echo Package: $pac; rpm -ql $pac |grep '\.service$'; echo; done === boot.apparmor === Package: apparmor-parser-2.8.1-130.1.x86_64 === boot.cycle === Package: bootcycle-0.3-244.1.x86_64 === boot.d === Package: filesystem-12.3-11.1.x86_64 === boot.device-mapper === Package: device-mapper-1.02.77-22.1.x86_64 === boot.dmraid === Package: dmraid-1.0.0.rc16-23.1.x86_64 === boot.kdump === Package: kdump-0.8.1-21.1.x86_64 === boot.loadmodules === Package: mkinitrd-2.7.2-5.7.x86_64 /usr/lib/systemd/system/purge-kernels.service # doesn't count ;-) === boot.local === Package: file /etc/init.d/boot.local is not owned by any package # but should continue to work ;-) === boot.localnet === Package: aaa_base-12.3-17.1.x86_64 === boot.lvm === Package: lvm2-2.02.98-22.1.x86_64 === boot.md === Package: mdadm-3.2.6-0.x86_64 === boot.scpm === Package: scpm-1.1.7-21.1.x86_64 === boot.sysstat === Package: sysstat-10.0.5-7.1.x86_64 /usr/lib/systemd/system/sysstat.service === boot.udev === Package: udev-195-24.1.x86_64 /usr/lib/systemd/system/basic.target.wants/systemd-udev-root-symlink.service /usr/lib/systemd/system/sysinit.target.wants/systemd-udev-trigger.service /usr/lib/systemd/system/sysinit.target.wants/systemd-udevd.service /usr/lib/systemd/system/systemd-udev-root-symlink.service /usr/lib/systemd/system/systemd-udev-settle.service /usr/lib/systemd/system/systemd-udev-trigger.service /usr/lib/systemd/system/systemd-udevd.service /usr/lib/systemd/system/udev.service In other words: from the 14 packages owning boot.* initscripts on my system, only 2 have service files. I'm sure the maintainers of the other 12 will happily accept submit requests that add the service file and do the migration in %post ;-) Note that I didn't write anything about "remove the initscript" - for AppArmor, I'd like to keep it for backwards compability with older openSUSE releases. Other maintainers might or might not have similar wishes. BTW: is ExecStatus supported in the meantime? (Needless to say that updating systemd is a no-go until all affected packages have a service file.) Regards, Christian Boltz -- Doh, bad Steve, no donut! [...] That's what I got for copy&wasting from a diff. [Steve Beattie in apparmor] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org