Am 11.07.2016 um 15:02 schrieb Jan Engelhardt:
>
> On Monday 2016-07-11 14:18, Michael Biebl wrote:
>> Am 09.07.2016 um 18:33 schrieb Jan Engelhardt:
>>> Package: systemd-container
>>> Version: 230-5
>>>
>>> nspawn fails to start the selected p
Hi Christian,
thanks for working on this
On Sat, Jul 02, 2016 at 03:46:00PM +0200, z...@debian.org wrote:
> +[Install]
> +WantedBy=multi-user.target
> +WantedBy=mail-transport-agent.target
I noticed this while looking over the debdiff.
mail-transport-agent.target is or rather was a Debian specif
Am 26.04.2016 um 11:24 schrieb Raphaël Hertzog:
> Package: dh-systemd,debhelper
> Severity: wishlist
>
> Hello dh-systemd maintainers and debhelper maintainers,
>
> with the adoption of systemd as default init system for quite a while now,
> it does not make sense that we have to Build-Depend on
Am 12.07.2016 um 01:46 schrieb Tianon Gravi:
> On 11 July 2016 at 15:37, Raphael Hertzog wrote:
>> A lintian check helps people to not introduce the mistake in new packages
>> as well whereas a bug report only helps already existing packages (but
>> will greatly help the conversion while lintian w
Package: ftp.debian.org
Severity: normal
Hi,
on a Debian stretch/unstable system using systemd as init system, the
initscripts package is no longer required. We asked all packages with
explicit dependencies to remove it and it is now possible to uninstall
initscripts without any ill side-effects.
Package: ftp.debian.org
Severity: normal
Hi,
please consider lowering the priority of sysv-rc from required to
optional. It's no longer needed on a system with systemd as init system.
The sysvinit-core package has explicit dependencies on initscripts and
sysv-rc, making sure that those packages
Package: ftp.debian.org
Severity: normal
Hi,
startpar is used by sysv-rc to boot a system when using sysvinit.
With systemd as our default init system, having startpar installed by
default is no longer necessary. I would therefor like to see its
priority demoted to optional.
On a system which us
Control: reassign -1 init-system-helpers
Control: found -1 1.35
On Wed, 13 Jul 2016 16:15:56 +0200 Michael Biebl wrote:
> Package: rpcbind
> Version: 0.2.3-0.5
> Severity: serious
>
> During a dist-upgrade from jessie to stretch, the rpcbind package failed
> to upgrade cleanly
Am 13.07.2016 um 18:24 schrieb Michael Biebl:
> Turns out the problem is in init-system-helpers.
> In 1.35, invoke-rc.d was changed to use systemctl is-enabled.
> This doesn't work for sysv init scripts with v215.
> As init-system-helpers is unpacked before systemd has
Am 13.07.2016 um 18:28 schrieb Michael Biebl:
> Am 13.07.2016 um 18:24 schrieb Michael Biebl:
>> Turns out the problem is in init-system-helpers.
>> In 1.35, invoke-rc.d was changed to use systemctl is-enabled.
>> This doesn't work for sysv init scripts with v215.
&g
ibsystemd0 230-7
ii libtirpc10.2.5-1
ii libwrap0 7.6.q-25
ii lsb-base 9.20160629
rpcbind recommends no packages.
rpcbind suggests no packages.
-- no debconf information
>From 7c8264a9eac62c2bd3b7d66bed3eaff63749c721 Mon Sep 17 00:00:00 2001
Fr
On Sun, 10 Jul 2016 18:20:53 +0200 Michael Biebl wrote:
> Am 10.07.2016 um 16:19 schrieb Askar Safin:
> > root@debian:~# systemd-nspawn -D /str
> > Spawning container str on /str.
> > Press ^] three times within 1s to kill container.
> > Failed to create directory /st
Control: tags -1 + moreinfo
Am 07.07.2016 um 15:23 schrieb Norbert Schulz:
> after an upgrade from wheezy to jessie wake-on-lan does not work anymore.
>
> The output from ethtool shows, that wake-on-lan is enabled, but after a
> shutdown and sending a wake-on-lan
> signal from an other computer
Control: tags -1 + moreinfo
Hi Daniel
Am 01.07.2016 um 10:35 schrieb Daniel Pocock:
> Severity: important
> Package: systemd
> Version: 215-17+deb8u2
>
> Since upgrading to jessie/systemd, one particular system frequently
> stops in the single-user mode password prompt during booting.
>
> Looki
Hi
Am 07.07.2016 um 14:30 schrieb Arturo Borrero Gonzalez:
> On 29 June 2016 at 11:31, Arturo Borrero Gonzalez
>> Hi, just uploaded the update package to mentors.d.n.
>> You can also find the sources in the git repo.
>>
>> Would you please review and sponsor?
Small nit: Please use consistent id
Am 14.07.2016 um 15:04 schrieb Norbert Schulz:
>> #!/bin/sh
>> ethtool
>>
>> Mark it as executable and the run systemctl halt
>>
>> What's the output of the script?
>>
> There is no output of the script. No messages will be written to
> /var/log/syslog
> or /var/log/messages
Try that instead
#
Am 14.07.2016 um 16:44 schrieb Norbert Schulz:
>
> Michael Biebl schrieb:
>> Am 14.07.2016 um 15:04 schrieb Norbert Schulz:
>
>> Try that instead
>
>> #!/bin/sh
>> mount -oremount,rw /
>> ethtool $iface > /ethtool.txt
>> mount -oremount,ro /
&
Package: init-system-helpers
Version: 1.35
Severity: important
File: /usr/sbin/invoke-rc.d
Since commit 6dd9d53f4fcc0f64fa2aa9d60452ea90ee9a30d0
invoke-rc.d foo status fails for disabled services:
# update-rc.d networking disable
# invoke-rc.d networking status
invoke-rc.d: emulating initscript
On Fri, 21 Nov 2014 13:31:21 +1100 Dmitry Smirnov
wrote:
> Package: systemd
> Version: 215-5+b1
> Severity: normal
>
> Switching to systemd with Wheezy to Jessie upgrade broke a particular
> Btrfs mount in fstab. Btrfs consists of three devices:
>
> $ sudo btrfs fi show
> Label: 'tmp_area'
Control: retitle -1 Drop transitional sysvinit package in stretch
Am 05.05.2015 um 17:57 schrieb Josh Triplett:
> On Tue, May 05, 2015 at 02:08:56PM +0200, Michael Biebl wrote:
>> Hi,
>>
>> On Thu, 02 Apr 2015 11:24:53 -0700 Josh Triplett
>> wrote:
>>> sysvi
On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt wrote:
> Control: tag -1 pending
>
> Wang Jian [2016-05-19 23:59 +0800]:
> > getty-static.service starts getty on tty2-6, but container has only 4
> > ttys (1-4) at default. getty will exit and be respawned for tty5-tty6.
> > This leads to high cpu u
Am 17.07.2016 um 18:55 schrieb Michael Biebl:
> On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt wrote:
>> Control: tag -1 pending
>>
>> Wang Jian [2016-05-19 23:59 +0800]:
>>> getty-static.service starts getty on tty2-6, but container has only 4
>>> ttys (
Am 17.07.2016 um 22:12 schrieb Josh Triplett:
> This change would break the mechanism that allowed switching between
> init systems via init= (or the generated options in GRUB). That makes
> it more difficult for someone who needs to test sysvinit for whatever
> reason. (The reverse works fine: h
Am 17.07.2016 um 23:05 schrieb Michael Biebl:
> Am 17.07.2016 um 22:12 schrieb Josh Triplett:
>> This change would break the mechanism that allowed switching between
>> init systems via init= (or the generated options in GRUB). That makes
>> it more difficult for some
Am 17.07.2016 um 23:17 schrieb Josh Triplett:
> On Sun, Jul 17, 2016 at 11:05:09PM +0200, Michael Biebl wrote:
>> If you have systemd-sysv installed and you want to try sysvinit-core,
>> you install the package and you get a fallback grub menu entry for
>> systemd (unle
Am 18.07.2016 um 00:07 schrieb Josh Triplett:
> On Sun, Jul 17, 2016 at 11:30:26PM +0200, Michael Biebl wrote:
>> Am 17.07.2016 um 23:17 schrieb Josh Triplett:
>>> On Sun, Jul 17, 2016 at 11:05:09PM +0200, Michael Biebl wrote:
>>>> If you have systemd-sysv installe
Am 16.07.2016 um 15:34 schrieb Martin Pitt:
> Control: tag -1 pending
>
> Wang Jian [2016-05-19 23:59 +0800]:
>> getty-static.service starts getty on tty2-6, but container has only 4
>> ttys (1-4) at default. getty will exit and be respawned for tty5-tty6.
>> This leads to high cpu usage on host's
Am 18.07.2016 um 00:17 schrieb Michael Biebl:
> Am 16.07.2016 um 15:34 schrieb Martin Pitt:
>> Control: tag -1 pending
>>
>> Wang Jian [2016-05-19 23:59 +0800]:
>>> getty-static.service starts getty on tty2-6, but container has only 4
>>> ttys (1-4) at defaul
Am 18.07.2016 um 07:56 schrieb Evgeni Golov:
> Hi again,
>
> On Mon, Jul 18, 2016 at 12:30:34AM +0200, Michael Biebl wrote:
>>> I assume this file was created by lxc.
>>> Apparently the lxc maintainers decided it is useful to have a getty on
>>> tty1-tty4? lxc
Am 18.07.2016 um 09:05 schrieb Evgeni Golov:
> On Mon, Jul 18, 2016 at 07:56:40AM +0200, Martin Pitt wrote:
>> Hello Michael, Evgeni,
>>
>> Evgeni Golov [2016-07-18 7:25 +0200]:
> There is no point in even wasting four getty processes on tty1-4 in
> LXC -- containers are not meant to have
Package: lxc
Version: 1:2.0.3-1
Severity: normal
Hi,
he had an interesting discussion today on #pkg-systemd IRC about what
modifications are currently done for LXC containers to work properly
with systemd. Ideally we'd like to make a default systemd installation work
ootb.
Atm, the Debian templa
Am 14.07.2016 um 19:31 schrieb 0x2a:
> you will see this in the log:
>
> Jul 14 17:11:40 systemd-test systemd[1]: Starting Halt...
> Jul 14 17:11:40 systemd-test systemd[1]: Assertion
> 'sd_id128_randomize(&id) >= 0' failed at ../src/core/dbus.c:688,
> function bus_on_connection(). Aborting.
> Ju
Am 18.07.2016 um 19:01 schrieb Martin von Wittich:
> So as far as I'm concerned, this update can be released.
Thanks a lot Martin for the very thorough testing.
Very much appreciated.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed
Am 19.07.2016 um 02:52 schrieb Laurent Bonnaud:
> This file belongs to package root-system-proofd that has been removed from
> Debian. I purged this package from my system, and now the error message is
> not displayed any more.
Do you still have a copy of the /etc/init.d/root-system-proofd sys
On Mon, 18 Jul 2016 11:05:12 +0200 Michael Biebl wrote:
> Am 18.07.2016 um 07:56 schrieb Evgeni Golov:
> > Hi again,
> >
> > On Mon, Jul 18, 2016 at 12:30:34AM +0200, Michael Biebl wrote:
> > wrt SIGPWR: iirc lxc-stop will issue SIGPWR to the container to stop it,
On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt wrote:
> Control: tag -1 pending
>
> Wang Jian [2016-05-19 23:59 +0800]:
> > getty-static.service starts getty on tty2-6, but container has only 4
> > ttys (1-4) at default. getty will exit and be respawned for tty5-tty6.
> > This leads to high cpu u
On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt wrote:
> Control: tag -1 pending
>
> Wang Jian [2016-05-19 23:59 +0800]:
> > getty-static.service starts getty on tty2-6, but container has only 4
> > ttys (1-4) at default. getty will exit and be respawned for tty5-tty6.
> > This leads to high cpu u
Am 19.07.2016 um 14:12 schrieb Michael Biebl:
> On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt wrote:
> Given Lennarts explanation at [1], I would suggest that we replace that
> condition with ConditionPathExists=/dev/tty0
There is an interesting follow-up by Lennart regarding LXC
Hi
Am 19.07.2016 um 19:28 schrieb Niels Thykier:
> Thanks for the report - at first glance it sounds like #830208 (Cc'ed
> accordingly).
>
> Peter's message quoted in full (for those not subscribed to
> debhelper-devel):
>
>> Hi,
>>
>> Now that dh_systemd_start and dh_systemd_enable are part of
Am 20.07.2016 um 12:22 schrieb Peter Pentchev:
> So... right now, it seems to me that the proper thing to do as a
> maintainer of a package that has both a SysV init script and a systemd
> service file would be to disable the systemd sequence and let
> dh_installinit do its job. This would mean th
Am 20.07.2016 um 17:37 schrieb Wang Jian:
> # diff -u /lib/systemd/system/getty@.service
> /etc/systemd/system/getty@.service
> --- /lib/systemd/system/getty@.service 2016-04-25 17:32:15.0 +0800
> +++ /etc/systemd/system/getty@.service 2015-05-17 20:28:50.253964583 +0800
> @@ -21,7 +21,
Am 21.07.2016 um 18:32 schrieb Felipe Sateler:
> On 21 July 2016 at 06:28, Yuri D'Elia wrote:
>> Package: systemd-coredump
>> Version: 230-7
>> Severity: wishlist
>>
>> LZ4 compression makes a huge difference in terms of performance impact when
>> compressing core files, but it's currently not ena
Am 21.07.2016 um 18:46 schrieb Michael Biebl:
> Am 21.07.2016 um 18:32 schrieb Felipe Sateler:
>> On 21 July 2016 at 06:28, Yuri D'Elia wrote:
>>> Package: systemd-coredump
>>> Version: 230-7
>>> Severity: wishlist
>>>
>>> LZ4 compres
Control: tags -1 + moreinfo
Am 21.07.2016 um 19:03 schrieb Yuri D'Elia:
> On Thu, Jul 21 2016, Michael Biebl wrote:
>>>> LZ4 is the default compression method according to upstream since systemd
>> If we build against liblz4, what happens with existing journal file
stly helps LXC containers, which don't
have a real VC subsystem but start some pseudo-ttys on tty1-tty4. So the
check for /dev/tty2 was wrong. We had a discussion with systemd upstream
who recommends to test for /dev/tty0 as indicator for a working VC
subsystem.
-- Michael Biebl Sun, 2
Source: glibc
Version: 2.19-18+deb8u4
Severity: normal
Tags: patch
Hi,
while working on a backport of systemd v230 for jessie, we ran into
issues. Our test-suite was failing on i386, specifically test-tmpfiles.
It turns out, the files created wit O_TMPFILE had broken permissions and
were unreadab
Control: tags -1 + moreinfo
Am 27.07.2016 um 01:37 schrieb John Pearson:
> This appears to be fundamentally similar to Debian bug #767468i, assigned to
> cgmanager.
Do you have cgmanager installed? Is it running?
Please attach your fstab and autofs configuration files.
A journalctl -alb log migh
Package: init-system-helpers
Version: 1.40
Severity: serious
In the latest upload, we dropped the insserv dependency and added some
fallback code for SysV init scripts for the case where insserv is not
installed [1].
Unfortunately, the disable case is not handled correctly. It removes all
symlink
Am 27.07.2016 um 11:17 schrieb Arturo Borrero Gonzalez:
> Thanks Michael,
>
> just uploaded to mentors a new version with all of this changes.
>
> Would you please review and sponsor?
I've uploaded the package as-is. It will have to go through NEW, so
might take a while.
Something which you mi
control: tags -1 + moreinfo
Am 28.07.2016 um 12:08 schrieb Rick Thomas:
> Main PID: 477 (code=exited, status=228/SECCOMP)
...
> Kernel: Linux 4.6.0-1-marvell
That looks like you are using a custom kernel. Is the problem
reproducible with the default Debian Linux kernel?
--
Why is it that all o
Hi Guido
Am 22.07.2016 um 10:50 schrieb Guido Günther:
> On Mon, Jun 27, 2016 at 08:41:18PM +0200, Michael Biebl wrote:
>> as discussed offline, in pkg-systemd we typically have two type of
>> patches: upstream cherrry-picks and Debian specific patches. Upstream
>> cherry-p
Am 28.07.2016 um 16:39 schrieb Michael Biebl:
> Maybe Felipe's helper could be generalized and added to gbp pq, like
> gbp pq cherry-pick
Or more generally gbp pq cherry-pick --before|after
This will cherry-pick a given commit after (or before) all patches with
the give topi
Am 28.07.2016 um 22:01 schrieb Rick Thomas:
> No. This is a stock kernel. It’s available from both testing and unstable
> repos. The machine itself is a SheevaPlug. Nothing custom about it.
>
> What makes you think it’s custom?
This was more of a question then a statement.
I wanted to rule o
Am 29.07.2016 um 09:17 schrieb Michael Biebl:
> That's not a bug in systemd but in your service file.
> If you want to run in early boot, you'll need to use
> DefaultDependencies=yes and specify your dependencies/orderings carefully.
I've filed an upstream RFE bug at [1].
Am 29.07.2016 um 14:08 schrieb Marc Haber:
> systemd 231-1 on Banana Pi fails with a bunch of "Failed at step
> SECCOMP spawning systemd-food: Invalid Argument". This at least
> applies to logind and networkd. Here is the output of trying to restart
> systemd-networkd:
>
> [ 113.060755] systemd[1
Am 29.07.2016 um 14:42 schrieb Michael Biebl:
> Am 29.07.2016 um 14:08 schrieb Marc Haber:
>> [ 113.379297] systemd[1]: Failed to start Network Service.
>> [ 113.444174] systemd[1565]: systemd-networkd.service: Failed at step
>> SECCOMP spawning /lib/systemd/systemd-netwo
Package: init-system-helpers
Version: 1.41
Severity: serious
Running
update-rc.d foo disable
update-rc.d foo defaults
will create start symlinks although this should not happen for a
disabled service.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (
Am 29.07.2016 um 22:44 schrieb Michael Biebl:
> Package: init-system-helpers
> Version: 1.41
> Severity: serious
>
> Running
> update-rc.d foo disable
> update-rc.d foo defaults
> will create start symlinks although this should not happen for a
> disabled service.
T
Am 29.07.2016 um 23:10 schrieb Felipe Sateler:
> I was going to ask this. I think we should register interest in
> insserv in the reportbug configuration.
Good idea. Added a bug-control script and pushed to master.
--
Why is it that all of the instruments seeking intelligent life in the
universe
Am 29.07.2016 um 23:29 schrieb Rick Thomas:
> Hmmm… Curiouser and curiouser!
>
> I upgraded a VM (amd64) to latest Sid (with systemd version 231-1). The
> problem is *not* present there.
>
> The problem may be specific to arm hardware? I’ll try it on a PowerPC G4
> (Apple Mac PPC) machine la
Am 30.07.2016 um 19:52 schrieb Felipe Sateler:
> On 29 July 2016 at 17:05, Michael Biebl wrote:
>> Am 29.07.2016 um 22:44 schrieb Michael Biebl:
>>> Package: init-system-helpers
>>> Version: 1.41
>>> Severity: serious
>>>
>>> Running
&g
Am 30.07.2016 um 20:47 schrieb Michael Biebl:
> Am 30.07.2016 um 19:52 schrieb Felipe Sateler:
>> On 29 July 2016 at 17:05, Michael Biebl wrote:
>>> Am 29.07.2016 um 22:44 schrieb Michael Biebl:
>>>> Package: init-system-helpers
>>>> Version: 1.4
Am 01.08.2016 um 23:40 schrieb Felipe Sateler:
> So I think the kernel should enable SECCOMP.
I agree, unless SECCOMP on arm has some unwanted side-effects.
Felipe, can you file a bug report against the linux package accordingly?
> However, I think systemd should also simply (warn and) ignore sec
Am 03.08.2016 um 17:26 schrieb Felipe Sateler:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/3882
> Control: severity -1 serious
> Yes, I'd like upstream's opinion on this first. However, I think this
> bug should be bumped to RC to prevent migration to testing, as this
> makes
Control: tags -1 + confirmed
Am 05.08.2016 um 04:33 schrieb Matthias Urlichs:
> Package: systemd
> Version: 230-1
> Severity: serious
> Justification: Missing Replaces:
>
> Unpacking systemd (231-1) over (230-1) ...
> dpkg: error processing archive
> /var/cache/apt/archives/systemd_231-1_amd64.d
Control: found -1 231-2
Am 15.08.2016 um 00:17 schrieb Rick Thomas:
> Sorry, it’s not fixed in 231-2… Please see attached boot log.
Yeah, the revert was incomplete.
The service files in systemd use
MemoryDenyWriteExecute=yes
which is implemented using seccomp. So we need to revert
40652ca4791fc3
Hi
On Mon, 10 Aug 2015 09:15:58 -0400 Jon DeVree wrote:
> As far as the shutdown problem is concerned, just putting udevd's pid
> into /run/sendsigs.omit.d/udevd fixes the problem without causing any
> new ones.
>
> Thats probably a good fix for debian rather than trying to patch udevd
> itself
Package: watchdog
Version: 5.15-1
Severity: normal
Hi,
thanks for shipping a service file for wd_keepalive [1]
There are some changes I think should be done:
1/ the sendsigs.omit.d interface is not supported under systemd, so
please drop
ExecStartPost=/bin/sh -c 'ln -s /var/run/wd_keepalive.pi
Am 28.08.2016 um 17:24 schrieb Tero Marttila:
> The fstab entry for this specific mount:
>
>> nfs.test.pvl:mail /srv/mail nfs4
>> defaults,auto,nodev,nosuid,noatime,x-systemd.automount 0 0
I think you really want "noauto" instead of "auto" here, so the share is
only mounted
Control: tags -1 - moreinfo
Am 28.08.2016 um 17:51 schrieb Michael Biebl:
> It is odd though indeed, that systemd marks your nfs share as mounted
> when it actually isn't. It seems I can reproduce that issue with v231 as
> well. I've created a test share on a server, stopped the
Control: forwarded -1 https://github.com/systemd/systemd/issues/2913
Hi
Am 05.09.2016 um 12:23 schrieb Tomas Crhonek:
> But journalctl -u add.service (or journalctl -f -u add.service) shows
> only some records, not complete output from program. In journalctl
> (without -u) are all messages.
This
Control: tags -1 + pending
Am 09.09.2016 um 13:37 schrieb Dimitri John Ledkov:
> Package: systemd
> Version: 231-5
> Severity: wishlist
>
> Hello,
>
> I'm looking to modify debian/rules and I've noticed that some common
> variables are re-invented, instead using things that are provided by a
> s
Am 09.09.2016 um 22:47 schrieb Brian Kroth:
> Package: systemd
> Version: 230-7~bpo8+2
> Severity: normal
> Tags: security
>
> Dear Maintainer,
>
> systemd appears to start systemd-resolved, even when it's been masked,
> in the background even when an unprivileged user calls systemd-resolve.
>
>
Thanks for the hint, Michal.
Seems like someone else already came to the same conclusion:
https://gist.github.com/ebautistabar/82811d492231700ab2471dd9048502b7
Am 07.09.2016 um 18:31 schrieb Michal Schmidt:
> systemd-fsckd's event loop terminates if nothing happens for 30 seconds
> (IDLE_TIME_SEC
Am 10.09.2016 um 00:20 schrieb Brian Kroth:
> Michael Biebl 2016-09-09 23:33:
>> Am 09.09.2016 um 22:47 schrieb Brian Kroth:
>>> Package: systemd
>>> Version: 230-7~bpo8+2
>>> Severity: normal
>>> Tags: security
>>>
>>> Dear Maintaine
Am 10.09.2016 um 00:26 schrieb Michael Biebl:
> So, you'll also need to mask that name, i.e
> dbus-org.freedesktop.resolve1.service
https://github.com/systemd/systemd/issues/1873
is somewhat related.
Upstream's position on this is, that masks apply only on that particular
name
Am 10.09.2016 um 02:27 schrieb Andreas Kloeckner:
> Package: systemd
> Version: 231-4
> Severity: normal
>
> Dear Maintainer,
>
> on my system, the following happens (from journalctl -e) on trying to start
> the
> services in the subject.
>
> --
> Sep 09 19:0
On Wed, 7 Sep 2016 18:31:12 +0200 Michal Schmidt
wrote:
> 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 exit
> by itself while
Am 10.09.2016 um 15:16 schrieb Michael Biebl:
> On Wed, 7 Sep 2016 18:31:12 +0200 Michal Schmidt
> wrote:
>> systemd-fsckd's event loop terminates if nothing happens for 30 seconds
>> (IDLE_TIME_SECONDS). Usually fsck writes progress updates more frequently
>> than
Am 10.09.2016 um 17:45 schrieb Felipe Sateler:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/4122
>
> On 9 September 2016 at 19:36, Michael Biebl wrote:
>> Upstream's position on this is, that masks apply only on that particular
>> name and no
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
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 exit
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
>
Am 15.09.2016 um 06:25 schrieb 積丹尼 Dan Jacobson:
> Maybe instead test if the group exists via other means, and then only if
> it doesn't, use addgroup to add it.
No, as said this is a bug in adduser/addgroup.
The root cause should be fixed and not worked around in individual packages.
Michael
Hi Jon,
thanks for your efforts.
Am 20.09.2016 um 03:26 schrieb Jon DeVree:
> The attached patches are about as clean as I can make it. The first one
> fixes the initial problem I found during git-bisect. The second one
> fixes the part of the problem that upstream pointed out in the issue/PR.
G
Control: tags -1 moreinfo unreproducible
Control: severity -1 important
Am 21.09.2016 um 05:31 schrieb Grond:
> Setting up systemd (215-17+deb8u5) ...
> addgroup: The group `systemd-journal' already exists as a system group.
> Exiting.
> dpkg: error processing package systemd (-
Am 21.09.2016 um 06:29 schrieb Michael Biebl:
> Control: tags -1 moreinfo unreproducible
> Control: severity -1 important
>
> Am 21.09.2016 um 05:31 schrieb Grond:
>> Setting up systemd (215-17+deb8u5) ...
>> addgroup: The group `systemd-journal' alr
Am 21.09.2016 um 14:10 schrieb Martin Pitt:
> Hello Dmitry,
>
> Dmitry Bogatov [2016-09-21 14:47 +0300]:
>> Since 'runit-init' package, which provides /sbin/init is in testing, I
>> ask include 'runit-init' into Pre-Depends: of this metapackage.
>
> Does that need any adjustment in invoke-rc.d, s
Am 21.09.2016 um 15:06 schrieb Michael Biebl:
> Am 21.09.2016 um 14:10 schrieb Martin Pitt:
>> Hello Dmitry,
>>
>> Dmitry Bogatov [2016-09-21 14:47 +0300]:
>>> Since 'runit-init' package, which provides /sbin/init is in testing, I
>>> ask include &
Control: fixed -1 230-3
Am 22.09.2016 um 15:04 schrieb Felipe Sateler:
> Control: user pkg-systemd-maintainers@lists.alioth.debian.org
> Control: usertags -1 jessie-backport
>
>
> On 20 September 2016 at 19:27, Paul Tagliamonte wrote:
>> found 774153 215-17+deb8u5
>
>
>
>> FWIW, this seems l
Control: fixed -1 229-4
Am 22.09.2016 um 16:18 schrieb Michael Biebl:
> There is a related followup change from 230-3 [1]:
>
>> * debian/extra/init-functions.d/40-systemd: Do not call systemctl
>> daemon-reload if the script is called as user (like reportbug does). Als
Am 18.09.2016 um 11:16 schrieb Antonio Ospite:
> After a precious suggestion by Mantas Mikulėnas (grawity in
> #debian-systemd) I verified that this is happening because
> /etc/pam.d/systemd-user does not load pam_limits.so.
>
> The following change fixes the issue:
> -
Control: tags -1 + pending
Am 27.09.2016 um 16:29 schrieb Antonio Ospite:
> Package: systemd
> Version: 231-7
> Followup-For: Bug #838191
>
> Dear Maintainer,
>
> I am attaching the patch to
> debian/patches/debian/Adjust-systemd-user-pam-config-file-for-Debian.patch
Committed as 9709b3
Thanks
Am 29.09.2016 um 20:43 schrieb Dietz Proepper:
> Package: systemd
> Version: 215-17+deb8u5
> Severity: important
>
> Dear Maintainer,
>
> see the details of the problem at
> https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet
>
> I can reproduce it without any problems. And it is
Version: 231-8
Am 29.09.2016 um 23:18 schrieb Michael Biebl:
> Am 29.09.2016 um 20:43 schrieb Dietz Proepper:
>> Package: systemd
>> Version: 215-17+deb8u5
>> Severity: important
>>
>> Dear Maintainer,
>>
>> see the details of the p
Package: init-system-helpers
Version: 1.45
Severity: important
debian/copyright currently lists Michael Stapelberg as the sole
copyright holder and the license as BSD-3-Clause.
dh_systemd_* moved to debhelper. The remaining bits from Michael S are
script/deb-systemd-* and t/.
invoke-rc.d, update
Package: systemd
Version: 215-17+deb8u5
Severity: important
User: pkg-systemd-maintainers@lists.alioth.debian.org
Usertags: jessie-backport
The news about systemd crashing when getting a zero sized message on the
notification socket made the rounds recently.
While v215 is not directly affected by
Control: fixed -1 231-9
Am 02.10.2016 um 22:36 schrieb Michael Biebl:
> Package: systemd
> Version: 215-17+deb8u5
> Severity: important
> User: pkg-systemd-maintainers@lists.alioth.debian.org
> Usertags: jessie-backport
>
> The news about systemd crashing when getting a zero
Am 03.10.2016 um 08:22 schrieb Wolfgang Karall:
> Hello Michael,
>
> On 16-10-02 22:36:00, Michael Biebl wrote:
>> The news about systemd crashing when getting a zero sized message
>> on the notification socket made the rounds recently. While v215 is
>> not directly
Am 03.10.2016 um 12:11 schrieb Michael Biebl:
> Am 03.10.2016 um 08:22 schrieb Wolfgang Karall:
>> Hello Michael,
>>
>> On 16-10-02 22:36:00, Michael Biebl wrote:
>>> The news about systemd crashing when getting a zero sized message
>>> on the notification
1301 - 1400 of 2654 matches
Mail list logo
