Your message dated Thu, 25 Dec 2014 10:25:38 -0600
with message-id <[email protected]>
and subject line Re: [Pkg-sysvinit-devel] Bug#773895: sysvinit: package to pin
sysvinit during upgrades
has caused the Debian Bug report #773895,
regarding sysvinit: package to pin sysvinit during upgrades
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.)
--
773895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773895
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: src:sysvinit
severity: important
tags: patch
Hi,
In order to provide an option for users to control the init system
outcome during an upgrade, I propose the attached update to
src:sysvinit. This adds a new package, which the user can elect to
install prior to their upgrade. It will prevent systemd installation
and retain sysvinit.
Please let me know if you have any feedback.
Best wishes,
Mike
--- End Message ---
--- Begin Message ---
On Wed, Dec 24, 2014 at 11:30:01PM -0500, Michael Gilbert wrote:
> Proposed patch included this time.
> diff -Nru sysvinit-2.88dsf/debian/block-systemd
> sysvinit-2.88dsf/debian/block-systemd
> --- sysvinit-2.88dsf/debian/block-systemd 1970-01-01 00:00:00.000000000
> +0000
> +++ sysvinit-2.88dsf/debian/block-systemd 2014-12-25 03:47:23.000000000
> +0000
> @@ -0,0 +1,3 @@
> +Package: systemd systemd-sysv libsystemd-daemon0 libsystemd-login0
> libsystemd-journal0
> +Pin: release o=Debian
> +Pin-Priority: -1
This is not a reasonable thing to ship in any package in the archive.
Pinning should be managed directly by the admin; wrapping this in a package
is an unnecessary indirection.
The actual contents of your pin are also highly harmful to the user, and
will prevent upgradability of large numbers of packages that take advantage
of systemd facilities. The way to express that you want to retain sysvinit
as the init system would be to pin the systemd-sysv package *only*, not any
of the other packages built from systemd source.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[email protected] [email protected]
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel