Control: severity -1 important
Am 24.07.2015 um 14:22 schrieb Michael Biebl:
On Fri, 10 Jul 2015 09:38:56 -0700 Josh Triplett j...@joshtriplett.org
wrote:
For a short-term fix, how about quickly re-introducing the gdm3
workaround? Then, we can experiment with possible ways to drop it and
On Fri, 10 Jul 2015 09:38:56 -0700 Josh Triplett j...@joshtriplett.org
wrote:
For a short-term fix, how about quickly re-introducing the gdm3
workaround? Then, we can experiment with possible ways to drop it and
(more) carefully test the upgrade paths with packages that haven't been
uploaded
Processing control commands:
severity -1 important
Bug #791964 [gdm3] gdm3: upgrade causes X session to be terminated
Severity set to 'important' from 'serious'
--
791964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791964
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
severity -1 serious
Bug #791964 [gdm3] gdm3: upgrade causes X session to be terminated
Severity set to 'serious' from 'normal'
--
791964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
[keeping pkg-systemd into the loop here]
Am 10.07.2015 um 14:37 schrieb Michael Biebl:
I suggest we follow up on this bug report.
I'm not yet quite sure, if this is a gdm or systemd bug and whether the
best course of action is to simply re-introduce the workaround patch and
drop that in
On 2015-07-10 10:46, Michael Biebl wrote:
Am 10.07.2015 um 18:38 schrieb Josh Triplett:
On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote:
* Systemd has been fixed in v222 to no longer kill services on
reload
if BusName is set, so drop that part from 92_systemd_unit.patch.
Am 10.07.2015 um 19:11 schrieb Josh Triplett:
On Fri, Jul 10, 2015 at 06:46:18PM +0200, Michael Biebl wrote:
Am 10.07.2015 um 18:38 schrieb Josh Triplett:
Note, though, that it doesn't help for systemd to be upgraded first.
Even if running the new systemd 222, upgrading gdm3 kills the active
On Fri, Jul 10, 2015 at 06:46:18PM +0200, Michael Biebl wrote:
Am 10.07.2015 um 18:38 schrieb Josh Triplett:
On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote:
Control: severity -1 serious
Am 09.07.2015 um 20:14 schrieb David Mohr:
Package: gdm3
Version: 3.14.2-1
On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote:
Control: severity -1 serious
Am 09.07.2015 um 20:14 schrieb David Mohr:
Package: gdm3
Version: 3.14.2-1
Severity: normal
Dear Maintainer,
the changelog reads:
* Systemd has been fixed in v222 to no longer kill
Am 10.07.2015 um 18:38 schrieb Josh Triplett:
On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote:
Control: severity -1 serious
Am 09.07.2015 um 20:14 schrieb David Mohr:
Package: gdm3
Version: 3.14.2-1
Severity: normal
Dear Maintainer,
the changelog reads:
* Systemd has
Am 10.07.2015 um 18:38 schrieb Josh Triplett:
On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote:
I'm not yet quite sure, if this is a gdm or systemd bug and whether the
best course of action is to simply re-introduce the workaround patch and
drop that in stretch+1 or if we drop the
11 matches
Mail list logo
