On Sat, Jan 14, 2017 at 06:40:49PM +0100, Jarek Kamiński wrote:
> Hello,
>
> #771122 explains that journald can't be restarted, as all stdout and
> stderr fds used by daemons to log would be lost. If I understand
> correctly, that was fixed in v219[1] though:
> > * systemd now provides a
Processing commands for cont...@bugs.debian.org:
> affects 851412 + src:neovim
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Added indication
Am 16.01.2017 um 15:33 schrieb Alexander Kurtz:
> Hi!
>
> On Mon, 2017-01-16 at 00:51 +0100, Michael Biebl wrote:
>> The commit for #859 is part of a massive pull request. A simple
>> cherry-pick of 01af8c019a33eb3882f17e3b65e30c4a924fed2a on top of v232
>> does produce merge conflicts
>>
>> If
Processing commands for cont...@bugs.debian.org:
> fixed 840816 215-17+deb8u6
Bug #840816 [systemd] systemd: Fails to boot normally after installing NIS.
Failed to start Login Service (logind)
Marked as fixed in versions systemd/215-17+deb8u6.
>
End of message, stopping processing here.
Please
I tested this morning with Jessie 8.6, boot problem persisted still and
I had to boot via rescue mode and there stop and start networking,
network-manager and nis.
After upgrade to jessie 8.7 I have booted twice, and normal boot starts
this host. The boot does seem to take a longish time,
#
# bts-link upstream status pull for source package systemd-cron
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #829438 (http://bugs.debian.org/829438)
# Bug title: systemd-cron: cron-{daily,
Processing commands for cont...@bugs.debian.org:
> affects 851412 + gnome-online-accounts xrdp
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Hi!
On Mon, 2017-01-16 at 00:51 +0100, Michael Biebl wrote:
> The commit for #859 is part of a massive pull request. A simple
> cherry-pick of 01af8c019a33eb3882f17e3b65e30c4a924fed2a on top of v232
> does produce merge conflicts
>
> If you want to see this in stretch, you should probably
