Processed: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

2014-11-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 732209 libpam-systemd 215-6 Bug #732209 [gnome-control-center] (gnome-control-center:11187): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. Bug reassigned from package 'gnome-control-center' to '

unblock: systemd/215-7

2014-11-26 Thread Martin Pitt
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock systemd 215-6 made it into testing today, so I'd like to ask for landing another set of small fixes. Note that I did *not* upload -7 to unstable yet, I'd like to get the release team's pre-

Bug#762101: Should be fixed now

2014-11-26 Thread Kitty Box
Hi, This bug should be fixed now as I commented on in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766771#25 Kitty ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mail

Bug#762101: Should be fixed now

2014-11-26 Thread Martin Pitt
Hey Kitty, Kitty Box [2014-11-27 3:28 +1100]: > This bug should be fixed now as I commented on in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766771#25 I don't understand what the constant reloading of udev rules (#766771) has to do with this bug? Maybe some bug number confusion, or did

systemd 215-6 MIGRATED to testing

2014-11-26 Thread Debian testing watch
FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 215-5 Current version: 215-6 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive lat

Bug#762101: Should be fixed now

2014-11-26 Thread Kitty Box
Hi Martin, The bug in (#766771) is the cause of this bug the only reason I went looking for it was because of this, I presume the reloading of udev rules triggers all of them including the ones you should only see at boot and that's why this message was spammed every udev event. I am "pretty" sure

Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

2014-11-26 Thread Crowley, Stephen
Curious, why am I being CC'ed on ths? Not that I am upset about anything... also, hi Linas, long time no chat, is this some attempt to get me back as an active member of the Debian project? :) --Stephen From: Vlad Orlov [mon...@inbox.ru] Sent: Wednesday,

Bug#771118: Acknowledgement (sysv-generator creates bogus orderings)

2014-11-26 Thread Michael Biebl
Forgot to attach the patch -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff --git a/src/sysv-generator/sysv-generator.c b/src/sysv-generator/sysv-generator.c index 677fac4..da6b4f6 100644 --- a/src/sysv-generator/sysv-generator.c

Bug#771118: Acknowledgement (sysv-generator creates bogus orderings)

2014-11-26 Thread Michael Biebl
Am 26.11.2014 um 23:39 schrieb Michael Biebl: > diff --git a/src/sysv-generator/sysv-generator.c > b/src/sysv-generator/sysv-generator.c > index 677fac4..da6b4f6 100644 > --- a/src/sysv-generator/sysv-generator.c > +++ b/src/sysv-generator/sysv-generator.c > @@ -768,6 +768,10 @@ static int enumera

Bug#771122: restarting the journal breaks other services

2014-11-26 Thread Michael Biebl
Package: systemd Version: 215-6 Severity: serious We restart systemd-journald in postinst on upgrades [0]. Unfortunately, this breaks other services like network-manager [1]. There was a recent discussion on #systemd, where Lennart mentioned in a related context (full IRC log is attached), that r

Bug#771122: restarting the journal breaks other services

2014-11-26 Thread Michael Biebl
Am 27.11.2014 um 00:17 schrieb Michael Biebl: > There was a recent discussion on #systemd, where Lennart mentioned in a > related > context (full IRC log is attached), that restarting journald is a bad idea, > as it is not properly supported atm: For completeness sake, find attached the IRC log.

Bug#762101: Should be fixed now

2014-11-26 Thread Michael Biebl
Am 26.11.2014 um 17:36 schrieb Martin Pitt: > Hey Kitty, > > Kitty Box [2014-11-27 3:28 +1100]: >> This bug should be fixed now as I commented on in >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766771#25 > > I don't understand what the constant reloading of udev rules (#766771) > has to

Re: Starting a service when stopping a different one

2014-11-26 Thread Michael Biebl
Am 21.11.2014 um 15:53 schrieb Michael Meskes: > Hi, > > is this possible? Let's say I have services foo and bar. I can declare a > conflict which results in bar being stopped automatically when foo is started. > But what I'd need is the opposite, I'd like foo to be started automatically > when ba

Re: Bug#766943: reassign 766943 to systemd

2014-11-26 Thread Michael Biebl
Am 23.11.2014 um 00:35 schrieb Christoph Anton Mitterer: > On Tue, 2014-11-11 at 20:01 +0100, Michael Biebl wrote: >> First, it would be great if you Christop could test this patch. Both >> using allow-hotplug and auto. > Done (with the v2 patch, of course). I did about 5-7 boots for each of > th

Bug#761951: systemd: Did not start network in default

2014-11-26 Thread Michael Biebl
Am 23.11.2014 um 01:29 schrieb Simon McVittie: > On Mon, 22 Sep 2014 at 15:30:00 +0900, K.Ohta wrote: >> 007_dump_network.txt.lz : systemd-analyze dump (lzipped). > > I tried using my script from > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763315 to find the > dependency cycles, but its an

Bug#762101: Should be fixed now

2014-11-26 Thread Kitty Box
Hi, You're both correct I had a slight oversight because somewhere down the comments of this bug the discussion about the spamming of the message came up and I forgot that originally it was just about the message itself. I checked the journald log and this message is still there (but thankfully on

Processed: severity of 770160 is normal

2014-11-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 770160 normal Bug #770160 [systemd] systemd: some messages are printed to multiple consoles, other to only one console Severity set to 'normal' from 'important' > thanks Stopping processing here. Please contact me if you need assistance

Bug#770090: systemd: systemctl poweroff doesn't poweroff

2014-11-26 Thread Michael Biebl
control: tags -1 moreinfo Am 18.11.2014 um 21:22 schrieb Robert Latest: > Package: systemd > Version: 215-5+b1 > Severity: important > > Dear Maintainer, > > > Since the latest aptitude update/upgrade, I can't shut down my computer any > more. Whether I do /sbin/poweroff, or /bin/systemctl powe

Processed: Re: Bug#770090: systemd: systemctl poweroff doesn't poweroff

2014-11-26 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #770090 [systemd] systemd: systemctl poweroff doesn't poweroff Added tag(s) moreinfo. -- 770090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___

Processed: forcibly merging 771118 770160

2014-11-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 771118 770160 Bug #771118 [systemd] sysv-generator creates bogus orderings Bug #770160 [systemd] systemd: some messages are printed to multiple consoles, other to only one console Severity set to 'serious' from 'normal' Marked as found

Bug#765400: networking.service started too early - PCMCIA NIC not brought up

2014-11-26 Thread Michael Biebl
control: reassign -1 ifupdown Am 14.10.2014 um 20:54 schrieb Charles-François Natali: >> Please attach /etc/network/interfaces. > > Attached. > Note that eth0 doesn't have cable plugged in and should probably be > commented out. > This is ultimately a limitation/design choice of ifupdown, speci

Processed: Re: Bug#765400: networking.service started too early - PCMCIA NIC not brought up

2014-11-26 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 ifupdown Bug #765400 [systemd] networking.service started too early - PCMCIA NIC not brought up Bug reassigned from package 'systemd' to 'ifupdown'. No longer marked as found in versions systemd/215-5. Ignoring request to alter fixed versions of bug #765

Processed (with 1 errors): Re: Bug#771101: wheezy -> jessie dist-upgrade failure when systemd is the active PID1

2014-11-26 Thread Debian Bug Tracking System
Processing control commands: > forcemerge -1 761306 Bug #771101 [udev] wheezy -> jessie dist-upgrade failure when systemd is the active PID1 Unable to merge bugs because: package of #761306 is 'systemd' not 'udev' Failed to forcibly merge 771101: Did not alter merged bugs -- 761306: http://bug

Bug#761306: Bug#771101: wheezy -> jessie dist-upgrade failure when systemd is the active PID1

2014-11-26 Thread Michael Biebl
control: forcemerge -1 761306 Am 26.11.2014 um 23:06 schrieb Michael Biebl: > I think, that's the relevant part from the journal, specifically: > >> Nov 26 19:36:57 debian systemd[1]: bind(@run/systemd/notify) failed: Address >> already in use >> Nov 26 19:36:57 debian systemd[1]: Failed to rel

Processed: Re: Bug#771101: wheezy -> jessie dist-upgrade failure when systemd is the active PID1

2014-11-26 Thread Debian Bug Tracking System
Processing control commands: > forcemerge -1 761306 Bug #761306 [systemd] v208 -> v215 upgrade fails to re-open notification socket Merged 761306 -- 761306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___

Processed: forcibly merging 771118 764408

2014-11-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 771118 764408 Bug #771118 [systemd] sysv-generator creates bogus orderings Bug #764408 [systemd] systemd-sysv-generator incorrectly considers sysvinit priorities when LSB headers are present Severity set to 'serious' from 'important' M

Processed: unmerging 771118, severity of 770160 is normal

2014-11-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unmerge 771118 Bug #771118 [systemd] sysv-generator creates bogus orderings Bug #770160 [systemd] systemd: some messages are printed to multiple consoles, other to only one console Disconnected #771118 from all other report(s). > severity 770160

Bug#771153: init-system-helpers: Please do not depend on new perl

2014-11-26 Thread Stepan Golosunov
Package: init-system-helpers Version: 1.22 init-system-helpers 1.22 introduced a versioned Depends: on perl-base. This needlessly complicates upgrades and backports by forcing perl and its reverse dependencies to be upgraded when installing init-system-helpers and its reverse dependencies. Pleas

Re: Bug#766943: reassign 766943 to systemd

2014-11-26 Thread Andrew Shadura
Hello, On Thu, 27 Nov 2014 01:13:23 +0100 Michael Biebl wrote: > Christoph, thanks for testing and confirming that it works. > Andrew, do you have any input/further questions on patch v2? > If not, would you be willing to add it to ifupdown and upload it so it > get's into jessie? I will uploa