Processed: severity of 792173 is important

2015-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: severity 792173 important Bug #792173 [udev] udev - missing ID and block information for dasd Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 792173:

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread Michael Biebl
Control: tags -1 + upstream Am 12.07.2015 um 15:30 schrieb nfb: After a quick jump on the #tor IRC channel we concluded that this may be an issue on the systemd side, and after reading something around the web we tried to tweak the Hardening section of the unit file. And indeed we found that

Processed: Re: Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread Debian Bug Tracking System
Processing control commands: tags -1 + upstream Bug #792187 [systemd] systemd: systemctl start not working when ReadWriteDirectories is a symlink Added tag(s) upstream. -- 792187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792187 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread nfb
Including the complete .service file would be helpful. Oh yes i didn't specify i installed the tor package in the debian testing repos, so the unit file is the one included in the package: --- [Unit] Description=Anonymizing overlay network for TCP After=network.target nss-lookup.target

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread intrigeri
nfb wrote (12 Jul 2015 21:41:39 GMT) : Oh yes i didn't specify i installed the tor package in the debian testing repos, so the unit file is the one included in the package: FWIW, I'm using the same unit file (from sid) and it has been working flawlessly here since it was introduced in the tor

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread Michael Biebl
Hi, Am 12.07.2015 um 23:41 schrieb nfb: That said, this sounds like an upstream issue, so please report that at https://github.com/systemd/systemd/issues/ and report bug with the bug number. Sorry, do i have to file an upstream bug referring to this bug number in its body, or do i have

Bug#723198: marked as done (unbootable initrd due to custom config files in /etc/initramfs-tools/)

2015-07-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jul 2015 22:41:36 +0200 with message-id 55a2d100.60...@debian.org and subject line Re: Bug#723198: marked as done (unbootable initrd due to custom config files in /etc/initramfs-tools/) has caused the Debian Bug report #723198, regarding unbootable initrd due to custom

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread nfb
Once you file the bug upstream, reply to *this* bug report with the upstream bug report number. This way I can link the two bug reports and we can track the upstream process automatically. here it is: https://github.com/systemd/systemd/issues/567 @Intrigeri So you cannot confirm... maybe

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread Michael Biebl
Control: forwarded -1 https://github.com/systemd/systemd/issues/567 Am 13.07.2015 um 01:04 schrieb nfb: Once you file the bug upstream, reply to *this* bug report with the upstream bug report number. This way I can link the two bug reports and we can track the upstream process automatically.

Processed: Re: Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread Debian Bug Tracking System
Processing control commands: forwarded -1 https://github.com/systemd/systemd/issues/567 Bug #792187 [systemd] systemd: systemctl start not working when ReadWriteDirectories is a symlink Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/567'. -- 792187:

Processed: wrong bug number, sorry

2015-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: reopen 723198 Bug #723198 {Done: Tomas Pospisek t...@sourcepole.ch} [udev] unbootable initrd due to custom config files in /etc/initramfs-tools/ 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Bug#792030: systemd does not reliably mount nfs shares

2015-07-12 Thread Bodo Eggert
On Fri, 10 Jul 2015, Michael Biebl wrote: Am 10.07.2015 um 14:05 schrieb Bodo Eggert: Package: systemd Version: 215-17+deb8u1 Severity: normal Dear Maintainer, when I boot my system, some of the NFS shares don't get mounted reliably. At first I blamed it on the RPC race

Bug#723198: marked as done (unbootable initrd due to custom config files in /etc/initramfs-tools/)

2015-07-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jul 2015 14:35:54 +0200 (CEST) with message-id alpine.DEB.2.11.1507121432470.30184@hier and subject line this is fixed in gnote 3.16.1-1 has caused the Debian Bug report #723198, regarding unbootable initrd due to custom config files in /etc/initramfs-tools/ to be marked

Processed: this is fixed in gnote 3.16.1-1

2015-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: fixed 723198 3.16.1-1 Bug #723198 [udev] unbootable initrd due to custom config files in /etc/initramfs-tools/ There is no source info for the package 'udev' at version '3.16.1-1' with architecture '' Unable to make a source version for version

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread nfb
Package: systemd Version: 221-1 Severity: normal Dear Maintainer, I installed tor (The onion router) the other day and when i started it (either via /usr/sbin/service or systemctl) i went through this: $ sudo systemctl start tor.service Job for tor.service failed because the control process

Bug#776171: Same problem

2015-07-12 Thread M.
I'm running Debian Sid and have exactly the same problem: issuing a sudo shutdown -r now gives me the error Failed to start reboot.target: Transaction is destructive. The system is going down for reboot NOW! ___ Pkg-systemd-maintainers mailing list