Package: systemd
Version: 208-1
Severity: normal
When running "systemctl is-enabled" for SysV-only services I get the
following error message:
sudo systemctl is-enabled mysql.service
Failed to issue method call: No such file or directory
I thought we had fixed that in the past, so this might be
On Sat, Jun 14, 2014 at 18:50:02 -0400, Michael Gold wrote:
> On Sat, Jun 14, 2014 at 23:44:42 +0200, Michael Biebl wrote:
> > Am 14.06.2014 22:41, schrieb Michael Gold:
> > > * after printing "Welcome to emergency mode!", it took a minute or two
> > >before a password prompt was shown; but th
On Sat, Jun 14, 2014 at 23:44:42 +0200, Michael Biebl wrote:
> Am 14.06.2014 22:41, schrieb Michael Gold:
> > * after printing "Welcome to emergency mode!", it took a minute or two
> >before a password prompt was shown; but that prompt died (I guess)
> >without accepting any keyboard input
Am 15.06.2014 00:02, schrieb Michael Biebl:
> tags 751623 + fixed-upstream
> thanks
>
> Am 14.06.2014 22:51, schrieb Debian Bug Tracking System:
>>> retitle -2 systemd: should print reason for starting emergency shell
>> Bug #751623 [systemd] systemd: opens emergency shell after prompting for
>>
tags 751623 + fixed-upstream
thanks
Am 14.06.2014 22:51, schrieb Debian Bug Tracking System:
>> retitle -2 systemd: should print reason for starting emergency shell
> Bug #751623 [systemd] systemd: opens emergency shell after prompting for
> unnecessary dm-crypt passwords
> Changed Bug title to '
Am 14.06.2014 22:41, schrieb Michael Gold:
> * after printing "Welcome to emergency mode!", it took a minute or two
>before a password prompt was shown; but that prompt died (I guess)
>without accepting any keyboard input, and after another few minutes I
>got another welcome message an
Processing commands for cont...@bugs.debian.org:
> severity 751585 normal
Bug #751585 [systemd] systemd: opens emergency shell after prompting for
unnecessary dm-crypt passwords
Severity set to 'normal' from 'important'
> clone 751585 -1 -2 -3
Bug #751585 [systemd] systemd: opens emergency shell
severity 751585 normal
clone 751585 -1 -2 -3
retitle -1 systemd: shows unnecessary password prompts for encrypted disks
severity -1 normal
retitle -2 systemd: should print reason for starting emergency shell
severity -2 wishlist
retitle -3 systemd: emergency shell takes several minutes to start
sev
Processing commands for cont...@bugs.debian.org:
> reassign 751589 sysvinit-core,systemd-sysv
Bug #751589 [sysvinit-core] sysvinit-core: /sbin/init missing after switching
from systemd to sysvinit
Bug reassigned from package 'sysvinit-core' to 'sysvinit-core,systemd-sysv'.
No longer marked as fou
Processing control commands:
> tags -1 - unreproducible
Bug #751589 [systemd-sysv] sysvinit-core: /sbin/init missing after switching
from systemd to sysvinit
Removed tag(s) unreproducible.
> reassign -1 sysvinit-core systemd-sysv
Bug #751589 [systemd-sysv] sysvinit-core: /sbin/init missing after
Control: tags -1 - unreproducible
Control: reassign -1 sysvinit-core systemd-sysv
Control: found -1 sysvinit/2.88dsf-53
Control: found -1 systemd/204-6
> You can't remove the systemd package while systemd is still the active init.
> How did you force the removal?
> That said, even with that seque
On 2014-06-14 19:37 +0200, Michael Biebl wrote:
> [Hit the send button a bit too early]
>
> Am 14.06.2014 19:34, schrieb Michael Biebl:
>> As I'm not able to reproduce the issue, I'm unable to test if replacing
>> Breaks with Conflicts actually fixes this particular bug you are seeing.
>
> Michael
[Hit the send button a bit too early]
Am 14.06.2014 19:34, schrieb Michael Biebl:
> As I'm not able to reproduce the issue, I'm unable to test if replacing
> Breaks with Conflicts actually fixes this particular bug you are seeing.
Michael, could you test if you can reliably reproduce the issue?
I
Am 14.06.2014 18:31, schrieb Michael Biebl:
> That said, even with that sequence of events /sbin/init is available here.
> I'm marking the bug as unreproducible until we have steps how we can
> reproduce the issue.
>
> root@pluto:/# apt-get remove systemd
> Reading package lists... Done
> Buildin
Am 14.06.2014 18:30, schrieb Michael Gold:
> Perhaps the options I want are "quiet" in crypttab and "nofail" in
> fstab, so they'll be mounted if available. With sysvinit most of them
> actually are automounted during startup--I have a udev script that runs
> cryptdisks_start when the disks are de
On Sat, Jun 14, 2014 at 17:30:30 +0200, Michael Biebl wrote:
> I noticed that you don't have those crypt devices marked as noauto (or
> nofail) in /etc/fstab.
> This means, if they fail to show up during boot systemd will drop you in
> an emergency shell (which is what happened in your case).
>
>
Processing commands for cont...@bugs.debian.org:
> tags 751589 + unreproducible
Bug #751589 [systemd-sysv] sysvinit-core: /sbin/init missing after switching
from systemd to sysvinit
Added tag(s) unreproducible.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
7515
tags 751589 + unreproducible
thanks
Am 14.06.2014 18:22, schrieb Michael Gold:
> On Sat, Jun 14, 2014 at 17:34:21 +0200, Michael Biebl wrote:
>> That said, I can not reproduce the sequence of events which make
>> /sbin/init dissappear.
>>
>> I've installed systemd-sysv in a VM, then ran apt-get in
On Sat, Jun 14, 2014 at 17:34:21 +0200, Michael Biebl wrote:
> That said, I can not reproduce the sequence of events which make
> /sbin/init dissappear.
>
> I've installed systemd-sysv in a VM, then ran apt-get install
> sysvinit-core and /sbin/init was available afterwards.
>
> So something else
Am 14.06.2014 17:15, schrieb Sven Joachim:
>> This is not going to happen as this conflicts with #748355.
>
> #748355 is about the conflict with sysvinit, not with sysvinit-core.
Fair enough. Using Conflicts: sysvinit-core in systemd-sysv would have
been the correct thing to do anyway, i.e. the f
Am 14.06.2014 16:59, schrieb Michael Gold:
> On Sat, Jun 14, 2014 at 16:27:36 +0200, Michael Biebl wrote:
>> Am 14.06.2014 16:04, schrieb Michael Gold:
>>> Package: systemd
>>> Version: 204-10
>>> Severity: critical
>>>
>>> After installing systemd today and rebooting, I saw a few lines (not
>>> er
On Sat, Jun 14, 2014 at 16:47:45 +0200, Petter Reinholdtsen wrote:
> [Michael Gold]
> > /sbin was available in the emergency shell and contained some files,
> > but 'init' wasn't there. 'dpkg -L sysvinit-core' ended at the line
> > '/sbin' (i.e., it was missing /sbin/shutdown, /sbin/init, etc.).
On Sat, Jun 14, 2014 at 17:14:35 +0200, Michael Biebl wrote:
> Just install the systemd package (but not systemd-sysv) and keep
> sysvinit-core installed.
>
> Then you can easily boot with systemd by specifying the kernel command
> line parameter
> init=/lib/systemd/systemd
>
> This allows you to
Control: reopen -1
Closing bugs which render the system unbootable seems a bit premature to me.
On 2014-06-14 17:03 +0200, Michael Biebl wrote:
> Am 14.06.2014 16:55, schrieb Sven Joachim:
>> Control: reassign -1 systemd-sysv 204-6
>>
>> On 2014-06-14 16:18 +0200, Michael Gold wrote:
>>
>>> Pa
Processing control commands:
> reopen -1
Bug #751589 {Done: Michael Biebl } [systemd-sysv]
sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
Bug reopened
Ignoring request to alter fixed versions of bug #751589 to the same values
previously set
--
751589: http://bugs.de
Am 14.06.2014 16:59, schrieb Michael Gold:
> I didn't retry, and since I had some difficulty recovering (see bug
> #751589) I'd rather not do it on this system. I was thinking of trying
> in a VM but that might take a while.
Just install the systemd package (but not systemd-sysv) and keep
sysvi
On Sat, Jun 14, 2014 at 16:27:36 +0200, Michael Biebl wrote:
> Am 14.06.2014 16:04, schrieb Michael Gold:
> > Package: systemd
> > Version: 204-10
> > Severity: critical
> >
> > After installing systemd today and rebooting, I saw a few lines (not
> > errors) about systemd-fsck on xfs filesystems,
Your message dated Sat, 14 Jun 2014 17:03:03 +0200
with message-id <539c6427.7080...@debian.org>
and subject line Re: Bug#751589: sysvinit-core: /sbin/init missing after
switching from systemd to sysvinit
has caused the Debian Bug report #751589,
regarding sysvinit-core: /sbin/init missing after s
Am 14.06.2014 16:55, schrieb Sven Joachim:
> Control: reassign -1 systemd-sysv 204-6
>
> On 2014-06-14 16:18 +0200, Michael Gold wrote:
>
>> Package: sysvinit-core
>> Version: 2.88dsf-53.2
>> Severity: critical
>>
>> After a failed switch to systemd today (Debian bug #751585), I tried to
>> switc
Processing control commands:
> reassign -1 systemd-sysv 204-6
Bug #751589 [sysvinit-core] sysvinit-core: /sbin/init missing after switching
from systemd to sysvinit
Bug reassigned from package 'sysvinit-core' to 'systemd-sysv'.
No longer marked as found in versions sysvinit/2.88dsf-53.2.
Ignoring
Control: reassign -1 systemd-sysv 204-6
On 2014-06-14 16:18 +0200, Michael Gold wrote:
> Package: sysvinit-core
> Version: 2.88dsf-53.2
> Severity: critical
>
> After a failed switch to systemd today (Debian bug #751585), I tried to
> switch back to sysvinit but found /sbin/init missing after a r
Processing commands for cont...@bugs.debian.org:
> severity 751585 important
Bug #751585 [systemd] systemd: opens emergency shell after prompting for
unnecessary dm-crypt passwords
Severity set to 'important' from 'critical'
> tags 751585 + moreinfo
Bug #751585 [systemd] systemd: opens emergency
Am 14.06.2014 16:04, schrieb Michael Gold:
> Package: systemd
> Version: 204-10
> Severity: critical
>
> After installing systemd today and rebooting, I saw a few lines (not
> errors) about systemd-fsck on xfs filesystems, and then I was prompted
> for dm-crypt passwords for 4 disks that are not n
Package: systemd
Version: 204-10
Severity: critical
After installing systemd today and rebooting, I saw a few lines (not
errors) about systemd-fsck on xfs filesystems, and then I was prompted
for dm-crypt passwords for 4 disks that are not necessary to boot the
system. I pressed enter to bypass e
Your message dated Sat, 14 Jun 2014 11:34:05 +
with message-id
and subject line Bug#750992: fixed in init-system-helpers 1.19
has caused the Debian Bug report #750992,
regarding position in build process not clear
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 14 Jun 2014 11:34:05 +
with message-id
and subject line Bug#750986: fixed in init-system-helpers 1.19
has caused the Debian Bug report #750986,
regarding Typos in error message
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Sat, 14 Jun 2014 11:34:05 +
with message-id
and subject line Bug#750404: fixed in init-system-helpers 1.19
has caused the Debian Bug report #750404,
regarding dh_systemd_start --restart-after-upgrade fails to start services on
initial installation
to be marked as done.
Thi
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 14 Jun 2014 13:17:57 +0200
Source: init-system-helpers
Binary: init-system-helpers dh-systemd
Architecture: source all
Version: 1.19
Distribution: unstable
Urgency: medium
Maintainer: pkg-systemd-maintainers
Chan
init-system-helpers_1.19_amd64.changes uploaded successfully to localhost
along with the files:
init-system-helpers_1.19_all.deb
dh-systemd_1.19_all.deb
init-system-helpers_1.19.dsc
init-system-helpers_1.19.tar.xz
Greetings,
Your Debian queue daemon (running on host franck.debian.
On 14/06/14 06:32, Michael Biebl wrote:
Am 08.06.2014 00:37, schrieb Jason Alavaliant:
I've just tested the latest initscripts package (2.88dsf-53.1)
Jason, could you please test again with 2.88dsf-53.2?
53.1 had an embarrasing formatting error.
I've retested with 2.88dsf-53.2 and confirmed t
Hi,
Am 12.06.2014 21:53, schrieb Michael Stapelberg:
> Hi Michael,
>
> Sorry for the late response.
>
> Michael Biebl writes:
>> I.e., it has a special case for the initial installation and uses
>> start if ! -n "$2".
>>
>> We should do the same for dh_systemd_start
> Agreed. I addressed this w
41 matches
Mail list logo
