On Mon, Dec 30, 2013 at 09:52:37PM +0100, Tollef Fog Heen wrote:
]] Ian Jackson
Steve Langasek writes (Bug#727708: systemd-shim uploaded to NEW):
So I repeat here my request that the systemd maintainers make a suitable
split of the systemd binary package, so that systemd-shim
Steve Langasek wrote:
Looking more closely, I find that one of the conflicting files is a conffile
(/etc/dbus-1/system.d/org.freedesktop.systemd1.conf). diversions and
conffiles still don't mix, AFAIK (and according to current policy). So that
seems to still leave us without a proper
* Raphael Hertzog hert...@debian.org, 2013-12-30, 19:42:
dpkg-divert is the usual answer when you need/want to replace something
without the consent of the other side.
FWIW, Policy §3.9 reads:
“You should not use ‘dpkg-divert’ on a file belonging to another package
without consulting the
Steve Langasek writes (Bug#727708: systemd-shim uploaded to NEW):
On Mon, Dec 30, 2013 at 06:29:10PM +, Ian Jackson wrote:
This would be quite wrong; Replaces is not supposed to be used like
that (but you apparently know that).
Yes. Raphaël rightly points out that dpkg-divert can
On Tue, Dec 31, 2013 at 01:16:32AM -0800, Josh Triplett wrote:
Steve Langasek wrote:
Looking more closely, I find that one of the conflicting files is a conffile
(/etc/dbus-1/system.d/org.freedesktop.systemd1.conf). diversions and
conffiles still don't mix, AFAIK (and according to current
Hello,
On Tue, 31 Dec 2013 13:07:22 -0800
Steve Langasek vor...@debian.org wrote:
For the record, logind is not the only issue here. It's logind,
timedated, hostnamed, localed which are needed by GNOME. This
doesn't actually change the work involved in forking the package; but
I think it
Steve Langasek writes (Bug#727708: systemd-shim uploaded to NEW):
So I repeat here my request that the systemd maintainers make a suitable
split of the systemd binary package, so that systemd-shim will be
coinstallable with the systemd-provided implementations of the other dbus
services
On Mon, 30 Dec 2013, Ian Jackson wrote:
The only alternative I see is for systemd-shim to declare a
Replaces: against systemd without a Conflicts,
This would be quite wrong; Replaces is not supposed to be used like
that (but you apparently know that).
How do the systemd maintainers
]] Ian Jackson
Steve Langasek writes (Bug#727708: systemd-shim uploaded to NEW):
So I repeat here my request that the systemd maintainers make a suitable
split of the systemd binary package, so that systemd-shim will be
coinstallable with the systemd-provided implementations of the other
On Mon, Dec 30, 2013 at 06:29:10PM +, Ian Jackson wrote:
Steve Langasek writes (Bug#727708: systemd-shim uploaded to NEW):
So I repeat here my request that the systemd maintainers make a suitable
split of the systemd binary package, so that systemd-shim will be
coinstallable
Tollef Fog Heen wrote:
Initially, by waiting for the ctte to come to a conclusion. If that is
that systemd should be the default init system I think we should solve
the problem by not solving it. If the decision is that another init
system should be solved, I'm probably going to solve it by
On Mon, Dec 30, 2013 at 01:03:48PM -0800, Steve Langasek wrote:
This would be quite wrong; Replaces is not supposed to be used like
that (but you apparently know that).
Yes. Raphaël rightly points out that dpkg-divert can be used for this; if
necessary, that's what I'll do.
But I still
On Sat, Dec 28, 2013 at 07:50:11PM -0800, Steve Langasek wrote:
I've just uploaded the systemd-shim package to the NEW queue.
This package has been marked for ACCEPT. Please feel free to test it
once dinstall runs and it gets sync'd to your local friendly mirror.
Cheers,
Paul
--
.''`.
13 matches
Mail list logo
