Bug#837871: no need for addgroup: The group `input' already exists as a system group. Exiting. messages

2016-09-14 Thread 積丹尼 Dan Jacobson
Maybe instead test if the group exists via other means, and then only if it doesn't, use addgroup to add it. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Processed: Re: Bug#837871: no need for addgroup: The group `input' already exists as a system group. Exiting. messages

2016-09-14 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 763055 Bug #837871 [udev] no need for addgroup: The group `input' already exists as a system group. Exiting. messages 837871 was not blocked by any bugs. 837871 was not blocking any bugs. Added blocking bug(s) of 837871: 763055 -- 837871:

Bug#837871: no need for addgroup: The group `input' already exists as a system group. Exiting. messages

2016-09-14 Thread Michael Biebl
Control: block -1 by 763055 Am 15.09.2016 um 01:56 schrieb 積丹尼 Dan Jacobson: > Package: udev > Version: 231-6 > Severity: wishlist > > Perhaps on upgrade instead of saying > addgroup: The group `input' already exists as a system group. Exiting. > say nothing, and instead just say >

Bug#837871: no need for addgroup: The group `input' already exists as a system group. Exiting. messages

2016-09-14 Thread 積丹尼 Dan Jacobson
Package: udev Version: 231-6 Severity: wishlist Perhaps on upgrade instead of saying addgroup: The group `input' already exists as a system group. Exiting. say nothing, and instead just say Adding group `input'. if adding. That way you need only make one message once, instead of

systemd-bootchart_231-1_source.changes ACCEPTED into unstable

2016-09-14 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Sep 2016 22:36:25 +0200 Source: systemd-bootchart Binary: systemd-bootchart Architecture: source Version: 231-1 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers

Bug#788050: systemd-fsck : Check disks at each reboot

2016-09-14 Thread Michael Biebl
Control: tags -1 + pending Am 07.09.2016 um 18:31 schrieb Michal Schmidt: > systemd-fsckd's event loop terminates if nothing happens for 30 seconds > (IDLE_TIME_SECONDS). Usually fsck writes progress updates more frequently > than that, but the interval is not guaranteed. So systemd-fsckd may

Processed: Re: Bug#788050: systemd-fsck : Check disks at each reboot

2016-09-14 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #788050 [systemd] systemd-fsck : Check disks at each reboot Added tag(s) pending. -- 788050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#837759: network configuration stops working reliably

2016-09-14 Thread Wolfgang Walter
On Wednesday, 14 September 2016 10:00:28 CEST Felipe Sateler wrote: > Control: tags -1 moreinfo > > On 14 September 2016 at 06:59, Wolfgang Walter > wrote: > > Package: systemd > > Version: 231-6 > > Severity: grave > > > > Starting with version 231-6 the configuration

Bug#837811: initramfs-tools integration

2016-09-14 Thread Michael Biebl
Package: systemd-bootchart Version: 231-1 Severity: wishlist It would be nice if systemd-bootchart would also be able to profile the initramfs stage. We should investigate if this is doable via initramfs-tools hooks or if this needs direkt support from initramfs-tools. dracut seems to be covered

Processing of systemd-bootchart_231-1_source.changes

2016-09-14 Thread Debian FTP Masters
systemd-bootchart_231-1_source.changes uploaded successfully to localhost along with the files: systemd-bootchart_231-1.dsc systemd-bootchart_231.orig.tar.gz systemd-bootchart_231-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)

Bug#837759: network configuration stops working reliably

2016-09-14 Thread Wolfgang Walter
Am Mittwoch, 14. September 2016, 10:00:28 schrieben Sie: > Control: tags -1 moreinfo > > On 14 September 2016 at 06:59, Wolfgang Walter wrote: > > Package: systemd > > Version: 231-6 > > Severity: grave > > > > Starting with version 231-6 the configuration of network

Bug#837759: network configuration stops working reliably

2016-09-14 Thread Felipe Sateler
Control: tags -1 moreinfo On 14 September 2016 at 06:59, Wolfgang Walter wrote: > Package: systemd > Version: 231-6 > Severity: grave > > Starting with version 231-6 the configuration of network interfaces stops > working reliably when rebooting a system. Downgrading to

Processed: Re: Bug#837759: network configuration stops working reliably

2016-09-14 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #837759 [systemd] network configuration stops working reliably Added tag(s) moreinfo. -- 837759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#837759: network configuration stops working reliably

2016-09-14 Thread Wolfgang Walter
Package: systemd Version: 231-6 Severity: grave Starting with version 231-6 the configuration of network interfaces stops working reliably when rebooting a system. Downgrading to 231-5 fixes the problem. Symptoms: If a network interface is configured using /etc/network/interfaces it seems

Bug#837642: Error appears only an close-to-full filesystems

2016-09-14 Thread v
Hello, increasing the partition size fixes this error: $ df -h DateisystemGröße Benutzt Verf. Verw% Eingehängt auf /dev/sda112G3,9G 7,3G 35% / $ systemctl status systemd-journald systemd-journal[950]: Permanent journal is using 504.1M (max allowed 750.0M, trying to leave