clone 35 -1
reassign -1 qemu-system-x86
retile -1 setting unsupported timeout for i6300esb watchdog causes reset
thanks
Am 13.02.2015 um 08:55 schrieb Peter Colberg:
On Fri, Feb 13, 2015 at 08:02:09AM +0100, Michael Biebl wrote:
Am 13.02.2015 um 07:44 schrieb Michael Biebl:
I went on and
Processing commands for cont...@bugs.debian.org:
fixed 768577 218-1
Bug #768577 [systemd] systemd-cryptsetup handles keyfile differently from
cryptsetup on plain mode
Marked as fixed in versions systemd/218-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
On Fri, 13 Feb 2015, Martin Pitt wrote:
Control: reassign -1 util-linux 2.25.2-5
Control: severity -1 normal
I still disagree with critical:
I also disagree this should be done in the first place. But I don't
want to put myself into eternal wars and who shouds the loudest
wins, so I'll
On 13/02/2015 06:54, Martin Pitt wrote:
Control: severity -1 normal
I still disagree with critical:
- If the hardware clock is so broken that at the next boot it has an
earlier time than on the previous boot/ntpdate, then writing it
once more at shutdown isn't going to entirely fix
Control: tag -1 fixed 218-1
Quentin Lefebvre [2014-11-24 15:35 +0100]:
For your information, a patch has been applied upstream.
Here is the link:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=8a52210c93
This was part of 218, thus is fixed in experimental.
I realize that this might
Processing control commands:
tag -1 fixed 218-1
Unknown tag/s: 218-1.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid
help security upstream pending sarge sarge-ignore experimental d-i confirmed
ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch
Am 13.02.2015 um 08:55 schrieb Peter Colberg:
In the linux-3.16.7-ckt4 source the range of the timeout value for
the i6300esb is 1s timeout 2*1023s. In theory it should work
with the default shutdown timeout of 10min.
This again might suggest, that his is a hardware, i.e. qemu bug?
For the
systemd_215-12_amd64.changes uploaded successfully to localhost
along with the files:
systemd_215-12.dsc
systemd_215-12.debian.tar.xz
systemd_215-12_amd64.deb
systemd-sysv_215-12_amd64.deb
libpam-systemd_215-12_amd64.deb
libsystemd0_215-12_amd64.deb
libsystemd-dev_215-12_amd64.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 13 Feb 2015 12:08:31 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev
Your message dated Fri, 13 Feb 2015 11:34:11 +
with message-id e1ymevf-0001em...@franck.debian.org
and subject line Bug#767267: fixed in systemd 215-12
has caused the Debian Bug report #767267,
regarding systemctl --failed not documented
to be marked as done.
This means that you claim that
Your message dated Fri, 13 Feb 2015 11:34:11 +
with message-id e1ymevf-0001es...@franck.debian.org
and subject line Bug#772700: fixed in systemd 215-12
has caused the Debian Bug report #772700,
regarding systemd-logind is installed on minimal install, but dbus which is
required is not.
to be
Your message dated Fri, 13 Feb 2015 11:34:11 +
with message-id e1ymevf-0001es...@franck.debian.org
and subject line Bug#772700: fixed in systemd 215-12
has caused the Debian Bug report #772700,
regarding Failed to start Login Service. after upgrade to 215-5+b1
to be marked as done.
This means
Your message dated Fri, 13 Feb 2015 11:34:11 +
with message-id e1ymevf-0001es...@franck.debian.org
and subject line Bug#772700: fixed in systemd 215-12
has caused the Debian Bug report #772700,
regarding Logind does not start properly on freshly installed minimal systems
to be marked as done.
Your message dated Fri, 13 Feb 2015 11:34:11 +
with message-id e1ymevf-0001es...@franck.debian.org
and subject line Bug#772700: fixed in systemd 215-12
has caused the Debian Bug report #772700,
regarding systemd-logind.service fails to start if dbus is missing
to be marked as done.
This means
systemd_218-10_amd64.changes uploaded successfully to localhost
along with the files:
systemd_218-10.dsc
systemd_218-10.debian.tar.xz
systemd_218-10_amd64.deb
systemd-sysv_218-10_amd64.deb
libpam-systemd_218-10_amd64.deb
libsystemd0_218-10_amd64.deb
libsystemd-dev_218-10_amd64.deb
On Mon, 9 Feb 2015, Christoph Berg wrote:
Re: Tomas Pospisek 2015-02-08 alpine.DEB.2.11.1502081748110.2557@hier
Hello all,
there's more fallout from the change of the default that makes bind mounts
share submounts (as introduced by systemd) instead of the previous default
that kept them
(resubmitting/forwarding since on first attempt this bug was already
archived and this my comment wouldn't get included therein)
-- Forwarded message --
Date: Sun, 8 Feb 2015 18:19:06 +0100 (CET)
From: Tomas Pospisek
To: 739593@b.d.o
Cc: Christoph Berg
Michael Stapelberg
Processing commands for cont...@bugs.debian.org:
unarchive 739593
Bug #739593 {Done: Michael Stapelberg stapelb...@debian.org} [systemd]
systemd makes / shared by default
Unarchived Bug 739593
thanks
Stopping processing here.
Please contact me if you need assistance.
--
739593:
Package: systemd
Version: 215-10
Platform -- Dell M3800 (XPS-15 alike) laptop, dm-crypt rootfs, jessie
with main/contrib/non-free, nVidia binary drivers (dkms). *Mostly* a
vanilla Jessie install (dm-crypt'd / is the obvious out of the
ordinary config item). Note - NOT an upgraded Debian
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 13 Feb 2015 12:25:06 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev
libsystemd-id128-dev udev
Your message dated Fri, 13 Feb 2015 12:04:47 +
with message-id e1ymezh-0005ez...@franck.debian.org
and subject line Bug#767267: fixed in systemd 218-10
has caused the Debian Bug report #767267,
regarding systemctl --failed not documented
to be marked as done.
This means that you claim that
control: tags -1 moreinfo
Am 14.02.2015 um 02:22 schrieb Jedd Rashbrooke:
Package: systemd
Version: 215-10
Platform -- Dell M3800 (XPS-15 alike) laptop, dm-crypt rootfs, jessie
with main/contrib/non-free, nVidia binary drivers (dkms). *Mostly* a
vanilla Jessie install (dm-crypt'd / is
Processing control commands:
tags -1 moreinfo
Bug #778362 [systemd] Periodic (90s) restart of KDM by systemd on jessie
Added tag(s) moreinfo.
--
778362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
You should consider removing the console-kit-daemon package.
It's not really useful anymore nowadays.
I have now removed the consolekit package - thanks for the suggestion.
I noted that it resulted in the removal of the mdadm package (along
with a bunch of init.d/*mdadm scripts) even though
24 matches
Mail list logo
