Am 14.09.2014 um 20:53 schrieb Thorsten Glaser:
> Michael Biebl dixit:
>> Also a debug log from the (failed) shutdown would be really helpful [1].
>
>> [1] http://freedesktop.org/wiki/Software/systemd/Debugging/
>> (/usr/lib/systemd/system-shutdown/debug.sh would be
>> /lib/systemd/system-shutdown
Michael Biebl dixit:
>This is not necessary. sysvinit's shutdown/reboot etc utility are able
>to talk to systemd and vice versa.
Hm okay.
>No, this seems wrong. Besides, we first need to know what went wrong.
Agreed.
>Please provide at least the versions that were installed.
Right; the system
Your message dated Sun, 14 Sep 2014 18:49:54 +
with message-id
and subject line Bug#756248: fixed in systemd 215-3
has caused the Debian Bug report #756248,
regarding systemd: reportbug config creates extremely large mails and sends
this info wihtout asking
to be marked as done.
This means t
Your message dated Sun, 14 Sep 2014 18:49:54 +
with message-id
and subject line Bug#717491: fixed in systemd 215-3
has caused the Debian Bug report #717491,
regarding [udev] man page bug - wrong system rules path
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 14 Sep 2014 18:49:54 +
with message-id
and subject line Bug#717491: fixed in systemd 215-3
has caused the Debian Bug report #717491,
regarding systemd: wrong path in man systemd-suspend.service(8)
to be marked as done.
This means that you claim that the problem has bee
Your message dated Sun, 14 Sep 2014 18:49:54 +
with message-id
and subject line Bug#758111: fixed in systemd 215-3
has caused the Debian Bug report #758111,
regarding installation-reports: Missing dbus; logind service fails
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 14 Sep 2014 18:49:54 +
with message-id
and subject line Bug#758111: fixed in systemd 215-3
has caused the Debian Bug report #758111,
regarding installation-reports: Please consider dbus for the core files
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 14 Sep 2014 18:49:54 +
with message-id
and subject line Bug#761340: fixed in systemd 215-3
has caused the Debian Bug report #761340,
regarding syslog stop working after v208 -> v215 upgrade (until next reboot)
to be marked as done.
This means that you claim that the pr
Your message dated Sun, 14 Sep 2014 18:49:54 +
with message-id
and subject line Bug#717491: fixed in systemd 215-3
has caused the Debian Bug report #717491,
regarding systemd-suspend.service(8) mentions wrong path for system-sleep
directory
to be marked as done.
This means that you claim tha
Your message dated Sun, 14 Sep 2014 18:49:54 +
with message-id
and subject line Bug#717491: fixed in systemd 215-3
has caused the Debian Bug report #717491,
regarding documentation: file references all point to /usr/lib
to be marked as done.
This means that you claim that the problem has been
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 14 Sep 2014 20:14:49 +0200
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev
libsystemd-journal0
systemd_215-3_amd64.changes uploaded successfully to localhost
along with the files:
systemd_215-3_amd64.deb
systemd-sysv_215-3_amd64.deb
libpam-systemd_215-3_amd64.deb
libsystemd0_215-3_amd64.deb
libsystemd-dev_215-3_amd64.deb
libsystemd-login0_215-3_amd64.deb
libsystemd-login-dev_21
Processing commands for cont...@bugs.debian.org:
> clone 760879 -1
Bug #760879 [src:systemd] FTBFS on sparc: recipe for target
'src/gudev/GUdev-1.0.gir' failed
Bug 760879 cloned as bug 761579
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
760879: http://bugs.deb
System uses gold as a linker by default, when using bfd the issue goes away.
(note that this is only an issue on sparc all other architectures build fine)
On Mon, Sep 08, 2014 at 10:11:37PM +0200, Michael Biebl wrote:
> g-ir-scanner: link: /bin/bash ./libtool --mode=link --tag=CC cc -o
> /«PKGBUI
Processing commands for cont...@bugs.debian.org:
> tags 761576 + moreinfo
Bug #761576 [systemd] systemd: fails to shutdown after changing to sysvinit
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
761576: http://bugs.debian.org/cgi-bin/bugr
tags 761576 + moreinfo
thanks
Am 14.09.2014 um 19:09 schrieb Thorsten Glaser:
> Package: systemd
>
> Someone I know has just installed sysvinit-core on their system,
> to switch there from systemd. This is currently the recommended
> way of switching to sysvinit after installing a wheezy/sid syst
Package: systemd
Someone I know has just installed sysvinit-core on their system,
to switch there from systemd. This is currently the recommended
way of switching to sysvinit after installing a wheezy/sid system.
The installation was not done with --purge and did pull sysvinit-shim.
However, the
Am 10.09.2014 um 02:32 schrieb Jean-Philippe MENGUAL:
> Subject: systemd: Not helpful bug to fix a minor problem
> Package: systemd
> Version: 208-8
> Severity: normal
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to
Michael Biebl writes:
> Am 13.09.2014 um 15:53 schrieb Michael Biebl:
>> Looking at v215, it seems as if starting cgmanager as part of the
>> installation messes up the running systemd state. When triggering
>> reboot, (i.e. poking /dev/initctl), I get the following:
>
> Actually this issue can be
19 matches
Mail list logo
