Your message dated Thu, 30 Jul 2009 09:40:15 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-sysvinit-devel] Bug#509449: initscripts
Conflicts/Replaces old sysvinit
has caused the Debian Bug report #509449,
regarding initscripts Conflicts/Replaces old sysvinit
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.)
--
509449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509449
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 2.86.ds1-38
The control file here says:
Replaces: ... sysvinit (<< 2.85-12) ...
Conflicts: ... sysvinit (<< 2.86.ds1-12) ...
The effect of this is that when you say
dpkg -i initscripts.deb
on a system with older sysvinit, dpkg will deinstall sysvinit in
favour of initscripts. This is the effect of the Conflicts/Replaces
combination (and is documented in the policy manual).
If the administrator does not notice this obviously renders the system
unbootable !
Perhaps what was meant was:
* This package replaces some files from old sysvinit
and
* This package must not be installed at the same time as old
sysvinit
But of course this is not a sensible combination. If the package must
not be installed at the same time, then there is no need to worry
about file conflicts.
Since the Conflicts covers all of the version range that the Replaces
does, it suffices to remove the Replaces entry.
If this affected upgrades from sarge I would have set the severity to
`grave' for obvious reasons. However it only causes problems for
upgrades from woody (and earlier). People are still doing that, but I
understand that this isn't a well-supported operation.
Nevertheless I think that this very small fix should be considered for
a stable point release in etch. It is easy to see that the change is
safe because it only affects systems with sysvinit versions older than
oldstable.
Ian.
--- End Message ---
--- Begin Message ---
Version: 2.86.ds1-66
[Ian Jackson]
> Package: initscripts
> Version: 2.86.ds1-38
>
> The control file here says:
> Replaces: ... sysvinit (<< 2.85-12) ...
> Conflicts: ... sysvinit (<< 2.86.ds1-12) ...
>
> The effect of this is that when you say
> dpkg -i initscripts.deb
> on a system with older sysvinit, dpkg will deinstall sysvinit in
> favour of initscripts. This is the effect of the Conflicts/Replaces
> combination (and is documented in the policy manual).
This was fixed in version 2.86.ds1-66, when I removed these
replaces/conflicts with versions before oldstable.
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
