]] Ansgar Burchardt
> Tollef Fog Heen writes:
> > So we are proposing the following scheme:
> >
> > a/ Upload a new "init" package. This is a new, essential package that
> > will replace sysvinit as the package that ensures your system has an
> > init system. We want to build this binary package
Am 17.07.2014 02:31, schrieb Ben Hutchings:
> On Wed, 2014-07-16 at 23:22 +0200, Tollef Fog Heen wrote:
> [...]
>> New installations
>> =
>> The new "init" package will ensure that systemd-sysv is installed as
>> default init on Linux and by demoting the priority of sysvinit and
>>
On Wed, 2014-07-16 at 23:22 +0200, Tollef Fog Heen wrote:
[...]
> New installations
> =
> The new "init" package will ensure that systemd-sysv is installed as
> default init on Linux and by demoting the priority of sysvinit and
> sysvinit-core to optional those packages will not be
Processing commands for cont...@bugs.debian.org:
> severity 754824 wishlist
Bug #754824 [systemd] systemd not user-friendly in case of a problem at boot
time
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
754824: http://b
libpam-systemd on unstable (208-6) is now uninstallable with sysvinit:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754984
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939
The systemd maintainers decided to go ahead and release 208-6 into
unstable without waiting for a compatible sy
Am 15.07.2014 18:17, schrieb Michal Suchanek:
> Excerpts from Michael Biebl's message of Tue Jul 15 15:44:24 +0200 2014:
>> Please also mention which version of systemd and systemd-sysv you have
>> installed.
>>
>
> ii systemd 204-14 amd64
> system and service m
Your message dated Thu, 17 Jul 2014 00:51:40 +0200
with message-id <53c701fc.7010...@debian.org>
and subject line systemd: loginctl kill-session does not work
has caused the Debian Bug report #748309,
regarding systemd: loginctl kill-session does not work
to be marked as done.
This means that you
Am 16.07.2014 23:42, schrieb Ansgar Burchardt:
>> c/ Upload a new version of the init package which does the actual switch
>> and changes the order via Pre-Depends: systemd-sysv |
>> sysvinit-core. Diff[4]
>
> Why do a, and c, in two steps?
We want to have the safety measures in place before mak
Hi,
Tollef Fog Heen writes:
> So we are proposing the following scheme:
>
> a/ Upload a new "init" package. This is a new, essential package that
> will replace sysvinit as the package that ensures your system has an
> init system. We want to build this binary package from a package which
> is no
Hi all,
We're now at the point where we want to flip the default init system for
Jessie on Linux. A lot of systems have already switched over to systemd
as their init system [0] and the package received a fair amount of
testing and integration work over the last couple of months. This makes
us pr
Am 16.07.2014 17:22, schrieb Michael Biebl:
> See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752428
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752430
sorry, meant
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752425
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752428
B
Processing commands for cont...@bugs.debian.org:
> severity 754984 normal
Bug #754984 [libpam-systemd] libpam-systemd 208-6 conflicts with sysvinit-core
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
754984: http://bugs.d
Your message dated Wed, 16 Jul 2014 17:20:01 +0200
with message-id <53c69821.4070...@debian.org>
and subject line Re: Bug#754984: libpam-systemd 208-6 conflicts with
sysvinit-core
has caused the Debian Bug report #754984,
regarding libpam-systemd 208-6 conflicts with sysvinit-core
to be marked as
Am 16.07.2014 16:38, schrieb Norbert Preining:
> Hi Michael,
>
>>> Update to 208-6 broke xfce suspend-to-ram. Option greyed out.
>>> Worked all the way till this update.
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939
>
> Why? I am not running systemd-shim?
>
> un systemd-shim
Package: libpam-systemd
Version: 204-14
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
libpam-systemd 204-14 lived in peaceful coexistence with sysvinit-core by
depending on systemd-sysv | systemd-shim.
libpam-systemd 208-6 amd64 now depends on systemd-sysv alone, and
Hi Michael,
> > Update to 208-6 broke xfce suspend-to-ram. Option greyed out.
> > Worked all the way till this update.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939
Why? I am not running systemd-shim?
un systemd-shim (no description available)
ii systemd-sysv
Am 16.07.2014 08:45, schrieb Norbert Preining:
> Package: systemd
> Version: 208-6
> Severity: important
>
> Update to 208-6 broke xfce suspend-to-ram. Option greyed out.
> Worked all the way till this update.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939
--
Why is it that all of th
Your message dated Wed, 16 Jul 2014 15:46:33 +0200
with message-id <53c68239.3020...@debian.org>
and subject line Re: Bug#746279: systemd: wrong permissions on non-persistent
/run/log/journal
has caused the Debian Bug report #746279,
regarding systemd: wrong permissions on non-persistent /run/log/
On Mon, Apr 28, 2014 at 11:58:46PM +0200, Michael Biebl wrote:
> Am 28.04.2014 20:12, schrieb Alessandro Ghedini:
> > On Mon, Apr 28, 2014 at 08:01:55PM +0200, Alessandro Ghedini wrote:
> >> On Mon, Apr 28, 2014 at 07:39:10PM +0200, Michael Biebl wrote:
> >>> Am 28.04.2014 19:19, schrieb Alessandro
19 matches
Mail list logo
