Your message dated Tue, 27 Jan 2015 21:40:27 +0100 with message-id <[email protected]> and subject line Re: release-notes: systemd switch: customised init scripts has caused the Debian Bug report #760897, regarding release-notes: systemd switch: customised init scripts to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 760897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760897 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: release-notes Severity: normal Exactly how the init system is to be handled for wheezy->jessie upgrades is still being argued about (and probably still will be in a few months...). What is clear, however, is that some sort of "migration to systemd" documentation would be appropriate to include in the release notes. Interested admins will want to know how to go about changing irrespective of whether the migration is done by default or not. There is a starting point on the wiki (although that is probably overly verbose to include in the release notes as it is) https://wiki.debian.org/systemd One point for migration that came up on debian-devel [1] is that local modifications to init scripts may well need to be ported over to the systemd units. This can't be done automatically and it's not even going to be easy to work out if there is a systemd unit for any given local modification. What we can do, however, is help the admin prepare a list of init scripts that have been modified so they can add them to their own TODO list for checking. One of the following is a good starting point for this: # debsums -c -e | grep ^/etc/init.d Using debsums is the simplest but requires installation of that package (personally, I'd have it installed anyway and run it as part of the upgrade procedure for some housekeeping). # dpkg-query --show -f'${Conffiles}' | sed 's, /,\n/,g' | grep /etc/init.d | awk 'NF,OFS=" " {print $2, $1}' | md5sum --quiet -c This shell monstrosity is general enough... Presumably the sed+grep+awk can be tidied at the expense of legibilility. # dpkg --verify This is only available in jessie's dpkg. If a multi-step upgrade procedure is recommended then relying on jessie's dpkg would be feasible but it would mix the preparation and upgrade steps. [1] http://lists.debian.org/<[email protected]>
--- End Message ---
--- Begin Message ---On 2015-01-15 10:02, Stuart Prescott wrote: > Hi Niels, > > looks good to me! > > thanks > Stuart > Excellent, thanks for the review - I will close this bug then. :) ~Niels
--- End Message ---
