Hi
Am 20.06.19 um 09:57 schrieb Trent W. Buck:
> Package: systemd
> Version: 241-5
> Severity: minor
> File: /usr/bin/systemd-analyze
>
> Below are two units which both block @debug syscalls (confirmed by strace
> crashing).
> systemd-analyze incorrectly claims @debug is allowed in one of them.
Control: tags -1 + moreinfo
Am 21.06.19 um 15:00 schrieb Seba Kerckhof:
> Package: udev
> Version: 241-5
> Severity: normal
>
> Dear Maintainer,
>
> Under Debian 10 rc1, when I plug in my USB camera (the very common logitech
> c930e), 2 devices are added (e.g. /dev/video0 and /dev/video1).
>
>
Control: tags -1 + moreinfo
Am 23.06.19 um 11:05 schrieb Corcodel Marian:
> Package: systemd
> Version: 232-25+deb9u11
> Severity: normal
>
> On etc/dbus-1/system.d/org.freedesktop.systemd1.conf expect to see
>
> policy context for org.freedesktop.systemd1.Agent interface, used on rfkill
> servi
Am 23.06.19 um 11:51 schrieb Michael Biebl:
> Control: tags -1 + moreinfo
>
> Am 23.06.19 um 11:05 schrieb Corcodel Marian:
>> Package: systemd
>> Version: 232-25+deb9u11
>> Severity: normal
>>
>> On etc/dbus-1/system.d/org.freedesktop.systemd1.conf
On Wed, 5 Jun 2019 13:04:50 +0200 Michael Biebl wrote:
> Am 29.05.19 um 18:49 schrieb Dan Streetman:
> > On Wed, May 29, 2019 at 12:35 PM Michael Biebl wrote:
> >>
> >> Am 29.05.19 um 18:19 schrieb Dan Streetman:
> >>> Package: systemd
> >>&g
Control: reassign -1 ifupdown
Am 25.06.19 um 22:47 schrieb Joshua Hudson:
> I have attached a copy of /etc/network/interfaces. We're now waiting
> for another recurrence.
>
/etc/network/interfaces is not a systemd config file, so it seems your
network interface is managed by ifupdown.
So I'm rea
Am 25.06.19 um 22:51 schrieb Michael Biebl:
> Dan, could you submit your patch as merge request?
Btw, we use gbp-dch style commit messages.
E.g. Debian bugs are closed by adding a
Closes: #929730
line to the git commit message.
http://honk.sigxcpu.org/projects/git-buildpackage/manual-h
Control: severity -1 important
Hi Raphael
On Wed, 19 Jun 2019 22:33:21 +0200 Michael Biebl wrote:
> Hi Raphael,
>
> On Tue, 11 Jun 2019 15:51:14 +0200 Raphael Hertzog
> wrote:
> > Hi,
> >
> > On Wed, 05 Jun 2019, Michael Biebl wrote:
> > > systemd-netwo
Am 26.06.19 um 14:17 schrieb Felipe Sateler:
> Honestly, I don't think networkd should keep quiet about ipv6 being
> disabled when you explicitly set up an ipv6 address.
I agree. While setting up an IPv6 address and at the same time disabling
IPv6 on the kernel side could be seen as a misconfigura
Am 26.06.19 um 21:39 schrieb andreimpope...@gmail.com:
> Control: tags -1 moreinfo
>
> On Mi, 26 iun 19, 20:23:59, Baptiste BEAUPLAT wrote:
>> Package: release-notes
>>
>> Dear maintainers,
>>
>> Systemd, in buster, will ship the file /lib/modprobe.d/systemd.conf,
>> which contains the following:
Am 26.06.19 um 21:39 schrieb andreimpope...@gmail.com:
>
> On Mi, 26 iun 19, 20:23:59, Baptiste BEAUPLAT wrote:
>> The only way to force modprobe to use local configuration is to rename
>> the /etc/modprobe.d/dummy.conf file to /etc/modprobe.d/systemd.conf.
>
> Is this documented anywhere else?
Am 27.06.19 um 20:02 schrieb Justin B Rye:
> Justin B Rye wrote:
>> Okay, so here's a first rough idea of what the release-notes might
>> say.
>
> Properly formatted patch attached.
>
Afaiu, the kernel default is to create one dummy device by default when
the module is loaded.
I assume there mig
Am 28.06.19 um 12:58 schrieb Justin B Rye:
> Michael Biebl wrote:
>> Afaiu, the kernel default is to create one dummy device by default when
>> the module is loaded.
.. or bond device, for that matter.
>> I assume there might be cases where users rely on that default behavi
Am 27.06.19 um 09:09 schrieb Raphael Hertzog:
> The net result of this problem is a server that is not reachable after a
> reboot so it can certainly be argued that it's worth documenting. It could
> be a debconf prompt that happens only when systemd-networkd is active
> and when ipv6 is disabled,
Am 29.06.19 um 15:09 schrieb Justin B Rye:
> + configure a machine as a router, may encounter problems upgrading to
> buster.
> + New versions of udev install a
That modprobe config file is shipped by the systemd package, not by udev.
> A file in
> + /lib/modprobe.d can be overrid
Am 29.06.2019 um 19:52 schrieb Justin B Rye:
> diff --git a/en/issues.dbk b/en/issues.dbk
> index 2edb9838..bf007277 100644
> --- a/en/issues.dbk
> +++ b/en/issues.dbk
> @@ -203,33 +203,28 @@ $ sudo update-initramfs -u
>
> Module configuration for bonding and dummy interfaces
>
> -
Control: tags -1 + moreinfo
Hi Steve!
Am 30.06.19 um 01:46 schrieb Steve McIntyre:
> [ Ignore the system info etc. below - I'm running reportbug on a
> different system. ]
>
> I've just dist-upgraded my headless home firewall/server from Stretch
> to Buster. I did the usual task of config fil
Am 30.06.2019 um 07:12 schrieb Michael Biebl:
> As you can see, after 30s the eye-of-cylon animation kicks in and after
> 300s the boot proceeds and successfully completes.
sorry for the typo, meant 200s here
> This is even a more elaborate setup with LVM and stuff.
To be sure, I al
Hi Steve,
with your additional information about the faulty fstab entry,
I had another look.
a/
I first tried with a non-existing device. I also made sure the
concurrently running fsck takes longer then 90s.
The result is:
https://people.debian.org/~biebl/bug931267/boot-missing-device.mp4
system
Am 03.07.19 um 15:50 schrieb andreimpope...@gmail.com:
> Please kindly confirm this Release Notes entry is needed/correct/etc.
> https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#migrate-interface-names
>
> #919390 appears to contradict /usr/share/doc/udev/README.De
Am 03.07.19 um 16:12 schrieb Michael Biebl:
> Am 03.07.19 um 15:50 schrieb andreimpope...@gmail.com:
>> Please kindly confirm this Release Notes entry is needed/correct/etc.
>> https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#migrate-interface-name
Am 03.07.19 um 16:12 schrieb Michael Biebl:
> Am 03.07.19 um 15:50 schrieb andreimpope...@gmail.com:
>> Please kindly confirm this Release Notes entry is needed/correct/etc.
>> https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#migrate-interface-name
Am 03.07.19 um 17:53 schrieb andreimpope...@gmail.com:
> On Mi, 03 iul 19, 16:47:36, Michael Biebl wrote:
>> Am 03.07.19 um 16:12 schrieb Michael Biebl:
>>> Am 03.07.19 um 15:50 schrieb andreimpope...@gmail.com:
>>>> Please kindly confirm this Release Notes entry is
Am 03.07.19 um 18:52 schrieb andreimpope...@gmail.com:
> On Mi, 03 iul 19, 18:22:30, Michael Biebl wrote:
>> Am 03.07.19 um 17:53 schrieb andreimpope...@gmail.com:
>>>
>>> diff --git a/en/issues.dbk b/en/issues.dbk
>>> index 4769f9d6..c7634151 100644
>>>
Am 03.07.19 um 18:48 schrieb Justin B Rye:
>> As said, net.ifnames=0 does not enforce the old naming scheme, it means
>> use the kernel provided names.
> I don't follow. Surely the old naming scheme *is* to use the
> kernel-provided names? Where did names like "eth0" come from if not
> the kernel
Am 08.07.19 um 16:41 schrieb Marc Haber:
> Package: systemd
> Version: 241-5
> Severity: wishlist
> File: systemd-networkd
>
> Hi,
>
> my buster (and sid) test systems don't bring up the virtio network
> interface in systemd-networkd. systemd-networkd sends a command to a
> netlink socket and get
Am 09.07.19 um 17:48 schrieb Marc Haber:
> On Mon, Jul 08, 2019 at 04:41:00PM +0200, Marc Haber wrote:
>> I will attach straces of a working and a non-working case once the bug
>> number is known. If you need additional information, I will help.
>
> Here are the straces. .prelink is an invocation
Am 09.07.19 um 18:44 schrieb Marc Haber:
> https://bugzilla.kernel.org/show_bug.cgi?id=204099
> https://bugzilla.kernel.org/show_bug.cgi?id=203769
>
> identify the kernel commit that broke things,
See also
https://lore.kernel.org/netdev/58ac6ec1-9255-0e51-981a-195c2b1ac...@mellanox.com/T/
but p
Am 09.07.19 um 21:41 schrieb Marc Haber:
> On Tue, Jul 09, 2019 at 07:16:07PM +0200, Michael Biebl wrote:
>> Can you test those patches to verify that they fix your issue?
>
> Even an unpatched systemd 241-6 fails building in my sid build chroot:
>
> 433/51
Am 10.07.19 um 07:12 schrieb Trent W. Buck:
> "systemd-analyze security systemd-resolved" claims for that
> PrivateTmp= "does not apply", though it clearly does.
I guess this is the essence of the bug report then and the bug report
should be retitled something like this:
systemd-analyze security
Am 09.07.19 um 17:11 schrieb Thomas Baetzler:
> Package: systemd
> Version: 241-5
> Severity: normal
> Tags: patch
>
> Dear Maintainer,
>
> After upgrading to Debian 10 we noticed a slightly different behaviour
> in /lib/lsb/init-functions.d/40-systemd which caused one of our scripts
> to break
Control: tags -1 + help
On Wed, 03 Jul 2019 02:12:59 +0200 Lorenzo Puliti
wrote:
> Could you please provide some fix?
I'm happy to review a patch if provided, but I won't investigate this
issue myself.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointe
Am 10.07.19 um 08:50 schrieb Marc Haber:
> I therefore can now confirm that the attached patch fixes the issue for
> me in system_241-6.
Thanks for testing. The attached patch is the combination of
9f6e82e6eb3b6e73d66d00d1d6eee60691fb702f and
4eb086a38712ea98faf41e075b84555b11b54362
This doesn't
On Thu, 11 Jul 2019 18:41:01 +0300 Mert Dirik wrote:
> On 7/11/19, Thomas Bätzler wrote:
> >
> > To wit:
> >
> > root@kvm1:~# /etc/init.d/rsync
> > Usage: /etc/init.d/rsync {start|stop|reload|force-reload|restart|status}
> >
> > vs.
> >
> > root@kvm1:~# /etc/init.d/mysql
> > /lib/lsb/init
Am 11.07.19 um 17:41 schrieb Mert Dirik:
> On 7/11/19, Thomas Bätzler wrote:
>>
>> To wit:
>>
>> root@kvm1:~# /etc/init.d/rsync
>> Usage: /etc/init.d/rsync {start|stop|reload|force-reload|restart|status}
>>
>> vs.
>>
>> root@kvm1:~# /etc/init.d/mysql
>> /lib/lsb/init-functions.d/40-systemd
Am 18.07.19 um 13:55 schrieb Michael Biebl:
> Am 11.07.19 um 17:41 schrieb Mert Dirik:
>> On 7/11/19, Thomas Bätzler wrote:
>>>
>>> To wit:
>>>
>>> root@kvm1:~# /etc/init.d/rsync
>>> Usage: /etc/init.d/rsync {start|stop|reload|force-
Hi everyone,
the first buster point release is not that far away.
I've pushed the changes I think are appropriate for buster to master and
just released 241-7 to unstable so we have some more wide spread test
coverage.
I basically want to release 241-7 as-is to buster (as either
241-7~deb10u1 or 2
reassign 932421 release.debian.org
severity 932421 normal
retitle 932421 nmu: systemd_242-2
user release.debian@packages.debian.org
usertag 932421 + binnmu
thanks
Am 19.07.19 um 04:43 schrieb 積丹尼 Dan Jacobson:
> Package: systemd
> Version: 242-2
> Severity: minor
>
> # aptitude search ~o
> i
Hi Kevin,
could you give the packages at
https://people.debian.org/~biebl/systemd/stretch/
a try and report back if they fix your issue?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital si
Control: tags -1 moreinfo unreproducible
Am 26.07.19 um 07:04 schrieb WHR:
> Package: systemd
> Version: 241-5
> Severity: normal
>
> Hello.
> I found the systemctl(1) command outputs are garbled in my terminal, if auto
> terminal paging is disabled.
> A screenshot is attached, or it is also avai
Am 26.07.19 um 11:21 schrieb 王昊然:
> OK, now I understands that was a feature, but how should I tell
> systemd to disable this feature so I can get a normal terminal output
> in terminals that doesn't support this feature?
man systemd
$SYSTEMD_URLIFY
The value must be a boolean.
n, not /sbin.
+(Closes: #931850)
+
+ [ Mert Dirik ]
+ * 40-systemd: Don't fail if SysV init script uses set -u and $1 is unset
+(Closes: #931719)
+
+ -- Michael Biebl Fri, 26 Jul 2019 21:32:04 +0200
+
systemd (241-5) unstable; urgency=medium
* Revert "Add check to switc
Am 03.08.19 um 19:32 schrieb Marc Lehmann:
> Package: udev
> Version: 241-5
> Severity: normal
>
> Dear Maintainer,
>
> udev apparently installs a seccomp filter that is incompatible with
> debians multi-arch.
>
> I found out because after installing dash:i386 on my amd64 system, my
> system was
On Mon, 27 May 2019 21:03:03 + Simon Beirnaert
wrote:
> Package: systemd
> Version: 232-25+deb9u11
> Severity: normal
>
> Dear Maintainer,
>
>
> Systemd does not seem to consistently put sshd processes under the
> relevant user's slice. I have a user with 10925 sshd processes related
> to i
On Mon, 5 Aug 2019 05:32:51 -0700 Felix Lechner
wrote:
> Hi,
>
> On Thu, May 2, 2019 at 9:27 AM Chris Lamb wrote:
> >
> > This begs the question; why cannot the systemd packaging remove the
> > executable bits from these files?
>
> On my testing system post-buster, the executable bits are still
Control: tags -1 + moreinfo
Am 05.08.19 um 17:32 schrieb Kathryn Tolsen:
> package: systemd
Which version is this?
> I had first observed this issue with Stretch and my Netgear WG111v3
> (RTL8168B chipset) using the rtl8168 driver over a year ago, and had a
> rough time running down the culprit
Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
> rpcbind (1.2.5-5) unstable; urgency=medium
> .
>* debian/rules: Add --no-restart-after-upgrade option to
> dh_installsystemd to avoid race condition at rpcbind.socket
> initialization (Closes: #933268)
https://salsa.debian.
Am 06.08.19 um 09:15 schrieb Michael Biebl:
> Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
>> rpcbind (1.2.5-5) unstable; urgency=medium
>> .
>>* debian/rules: Add --no-restart-after-upgrade option to
>> dh_installsystemd to avoid race
Am 06.08.19 um 15:35 schrieb Felipe Sateler:>
>
> On Tue, Aug 6, 2019 at 3:15 AM Michael Biebl # systemctl restart rpcbind.service rpcbind.socket
>
> Job for rpcbind.socket failed.
> See "systemctl status rpcbind.socket" and "journalctl -xe" f
Source: haveged
Version: 1.9.1-8
Severity: normal
Hi,
I noticed that debian/haveged.service uses
[Install]
WantedBy=default.target
default.target is an alias and should not be used directly.
Instead you should either hook into multi-user.target or
graphical.target.
In this particular case, multi
Package: lintian
Version: 2.17.0
Severity: wishlist
Hi,
I noticed a couple of systemd system services
(files that match /lib/systemd/system/*.{service,socket,...})
that use
[Install]
Alias=default.target
default.target is only an alias and should not be used for that.
Instead services should e
Control: tags -1 + moreinfo
Am 07.08.19 um 20:14 schrieb Daniel Baumann:
> Package: systemd
> Severity: important
> Version: 241-7 242-2
>
> Hi,
>
> when using systemd-nspawn containers, systemd 241 and 242 do not bring
> up the interfaces when using kernel 5.2. with kernel 4.9 it works.
>
> up
Am 07.08.19 um 18:22 schrieb Michael Biebl:
> Package: lintian
> Version: 2.17.0
> Severity: wishlist
>
> Hi,
>
> I noticed a couple of systemd system services
> (files that match /lib/systemd/system/*.{service,socket,...})
> that use
>
> [Install]
> Alias=d
Control: tags -1 + moreinfo unreproducible
Am 09.08.19 um 08:15 schrieb Marc Haber:
>
> I have not fully understood what happens here. I am monitoring my
> filesystems with aide, and sometimes get the following report:
>
> ---
> Changed entries:
>
Am 09.08.19 um 16:16 schrieb Michael Biebl:
> Control: tags -1 + moreinfo unreproducible
>
> Am 09.08.19 um 08:15 schrieb Marc Haber:
>>
>> I have not fully understood what happens here. I am monitoring my
>> filesystems with aide, and sometim
Am 10.08.19 um 12:37 schrieb Marc Haber:
> Hi Michael,
>
> thanks for your answer.
>
> On Fri, Aug 09, 2019 at 04:16:06PM +0200, Michael Biebl wrote:
>> I have never seen this behaviour myself on the multitude of systems I
>> run (laptop, servers, VM, containers) so I
Control: tags -1 + moreinfo unreproducible
Am 12.08.19 um 12:56 schrieb quidame:
> udevadm info --query property --export --name /dev/dm-2
I don't use LVM, but running that e.g. on /dev/sda5, I get
$ udevadm info --query property --export --name /dev/sda5
DEVPATH='/devices/pci:00/:00:1f.
Am 12.08.19 um 10:52 schrieb Trent W. Buck:
> Package: systemd
> Version: 241-5
> Severity: normal
> File: /lib/systemd/network/80-container-ve.network
>
> Debian 10 defaults to nftables:
>
>
> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#nftables
>
> ...b
Am 12.08.19 um 13:50 schrieb Arturo Borrero Gonzalez:
> On 8/12/19 1:26 PM, Michael Biebl wrote:
>> src/shared/firewall-util.* uses libiptc (which in turn uses iptables)
>>
>> ttbomk, mixing nftables and iptables is supported, otherwise we'd have
>> huge proble
Am 12.08.19 um 12:56 schrieb quidame:
> Package: udev
> Version: 241-7
> Severity: normal
>
> Dear Maintainer,
>
> When running a command such as:
>
> udevadm info --query property --export --name /dev/dm-2
>
> I expect to get a list of properties of the device (/dev/dm-2) in a
> shell-pars
Am 13.08.19 um 17:44 schrieb Michael Biebl:
> It doesn't claim that this is a shell parseable format which can be run
> through eval, so I don't think you can rely on that.
That aside, setting net.ifnames only for network interfaces does
probably make sense, so something along
Am 13.08.19 um 17:50 schrieb Michael Biebl:
> Am 13.08.19 um 17:44 schrieb Michael Biebl:
>> It doesn't claim that this is a shell parseable format which can be run
>> through eval, so I don't think you can rely on that.
>
> That aside, setting net.ifnames o
Am 13.08.19 um 18:07 schrieb quidame:
>
>
> On 13/08/2019 17:44, Michael Biebl wrote:
>>
>> --export says
>>
>> -x, --export
>>Print output as key/value pairs. Values are enclosed in
>> single quotes. This takes effects only when --
Am 17.08.19 um 21:23 schrieb Paul Gevers:
> Source: network-manager, systemd
> Control: found -1 network-manager/1.20.0-1
> Control: found -1 network-manager/1.19.90-2
> Control: found -1 systemd/241-7
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
Am 18.08.19 um 17:18 schrieb Michael Biebl:
> Am 17.08.19 um 21:23 schrieb Paul Gevers:
>> Source: network-manager, systemd
>> Control: found -1 network-manager/1.20.0-1
>> Control: found -1 network-manager/1.19.90-2
>> Control: found -1 systemd/241-7
>> Severity
Am 18.08.19 um 13:01 schrieb Andreas Henriksson:
> So apparently polkitd is not running after the first reboot attempt. I
> have no clue why or how to investigate why so I guess I'll leave that to
> the professionals.
>
> Maybe it would be useful to change the test to do
> "pidof polkitd || fail"
Control: reassign -1 systemd 241-7
Am 18.08.19 um 18:39 schrieb Michael Biebl:
> Am 18.08.19 um 17:18 schrieb Michael Biebl:
>> I've created an LXC container via
>> autopkgtest-build-lxc debian bullseye
>> and got the same autopkgtest failure using this containe
Am 19.08.19 um 21:04 schrieb Daniel Kahn Gillmor:
> Package: systemd
> Version: 241-6
> Severity: normal
> Tags: upstream patch
> Control: forwarded -1 https://github.com/systemd/systemd/issues/12784
>
> from the journal:
>
> -- Reboot --
> Aug 19 10:55:17 tyr systemd[1]: Starting Network Service
Hi
Am 23.08.19 um 01:06 schrieb Marc Lehmann:
> Package: systemd
> Version: 241-5
> Severity: minor
>
> Dear Maintainer,
>
> on one of my systems, debian runs from a filesystem image loop-mounted
> from an ntfs volume using ntfs-3g, and thus, the ntfs-3g process must be
> running at all times, b
Control: tags -1 + moreinfo
Am 26.08.19 um 19:39 schrieb Bill Seremetis:
> Package: systemd
> Version: 242-4
> Severity: normal
>
> Dear Maintainer,
>
>* What led up to the situation?
> In debian bullseye (for several months) with all disks encrypted with dmcrypt
> (except from /boot and swa
Ok, let's look at the log:
Am 28.08.19 um 09:08 schrieb Bill Seremetis:
> Aug 28 09:57:51 dwarf systemd[1]: Condition check resulted in File System
> Check on Root Device being skipped.
> Aug 28 09:57:51 dwarf systemd[1]: Condition check resulted in Kernel
> Configuration File System being skipp
Am 28.08.19 um 13:11 schrieb Trent W. Buck:
> If this is an unavoidable limitation due to Linux, please at least
> warn about it in the systemd-nspawn manpage.
I've forwarded this upstream to
https://github.com/systemd/systemd/issues/13417 where it was mentioned
that this topic had already come u
Am 29.08.19 um 11:40 schrieb Nikos Kormpakis:
> I think that it is possible to include this fix in Buster.
Make's sense on a cursory glance. Thanks for the detailed bug report.
It's probably too late to do it for 10.1, as this release is just around
the door. But I'll try to get it into the next
Am 30.08.19 um 15:09 schrieb Stefan Haller:
>> Source: systemd
>> Source-Version: 242-5
>>
>> We believe that the bug you reported is fixed in the latest version of
>> systemd, which is due to be installed in the Debian FTP archive.
>
> Thank you very much for addressing this problem!
>
> Do you
On Wed, 2 Jan 2019 21:17:43 +0100 Michael Biebl wrote:
> Hi Simon
>
> On Tue, 4 Dec 2018 21:18:07 + Simon McVittie wrote:
> > Package: libsystemd-dev
> > Version: 239-14
> > Severity: wishlist
> >
> > libsystemd-dev doesn't provide a static li
On Thu, 29 Aug 2019 11:21:37 +1000 "Trent W. Buck"
wrote:
> Michael Biebl wrote:
> > Am 28.08.19 um 13:11 schrieb Trent W. Buck:
> >
> > > If this is an unavoidable limitation due to Linux, please at least
> > > warn about it in the systemd-nspawn manpa
On Tue, 6 Aug 2019 09:42:15 -0400 Kathryn Tolsen
wrote:
> > Which version is this?
>
> > Is the problem still reproducible?
>
> root@t440:/home/user# dpkg -l systemd udev linux-image-amd64;cat
> /etc/systemd/network/70-wifi.link;dmesg|tail -n 31
> Desired=Unknown/Install/Remove/Purge/Hold
> |
>
Hi Ansgar
On Tue, 06 Nov 2018 15:24:18 +0100 Ansgar Burchardt
wrote:
> Package: systemd
> Version: 239-11
> Severity: minor
> File: /bin/systemd
>
> Running `systemd` in an interactive shell is not a good idea. To
> avoid this happening by accident, the /bin/systemd ->
> /lib/systemd/systemd sy
[somehow messed up the CC list, s/pkg-gnome/pkg-systemd/]
Am 01.09.19 um 14:44 schrieb Alan Jenkins:
> On 01/09/2019 12:52, Michael Biebl wrote:
>> On 01.09.19 13:24, Alan Jenkins wrote:
>>> Package: gnustep-base-runtime
>>> Version: 1.26.0-4
>>>
Control: reassign -1 lxc
Am 01.09.2019 um 23:31 schrieb Sergey Aleynikov:
> Source: systemd
> Version: 241-5
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
> I'm running LXC con
On Wed, 10 Jan 2018 10:08:26 +0100 Christoph Pleger
wrote:
> Hello,
>
> > Fwiw, this behaviour makes sense to me.
> > If you start a scheduled login 2 days in advance, sending a shutdown
> > message every minute would not be helpful. Restricting that to the last
> > ten minutes seems reasonable.
Am 03.09.19 um 01:07 schrieb David Anderson:
> If possible, could this fix be released as a Buster update as well?
> This bug prevents the use of networkd to set up Wireguard VPN servers
> on Buster, and it's hard to workaround without resorting to racey
> shell scripts.
According to the upstream
Control: tags -1 + moreinfo
Hi Christian
On Sun, 5 Feb 2017 00:05:03 +0100 Christian Seiler
wrote:
> while helping out on debian-mentors@ with #854192 I noticed that systemd
> doesn't appear to handle the case very well when dbus is installed but not
> configured properly (this was due to a bug
Control: tags -1 + moreinfo
On Thu, 4 May 2017 17:47:17 +0200 Christian Hofstaedtler
wrote:
> How will a database.target solve anything in those not so uncommon
> setups:
>
> - database is remote
>
> or
>
> - one database needs another to start?
>
> Please consider: if you end up with a solut
On Wed, 01 Oct 2014 05:30:09 +0200 intrig...@debian.org wrote:
> Package: systemd
> Version: 215-5
> Severity: normal
>
> Hi,
>
> ProtectSystem was adjusted (#759689) to be better suitable for Debian,
> but the corresponding manpage wasn't updated accordingly.
I wonder if it wouldn't be a better
Am 03.09.19 um 14:05 schrieb Michael Biebl:
> On Wed, 01 Oct 2014 05:30:09 +0200 intrig...@debian.org wrote:
>> Package: systemd
>> Version: 215-5
>> Severity: normal
>>
>> Hi,
>>
>> ProtectSystem was adjusted (#759689) to be better suitable for De
Am 04.09.19 um 14:09 schrieb Stefan Priebe - Profihost AG:
> Hello,
>
> currently systemd is broken in buster regarding RootDirectory and User.
>
> The issue was fixed in systemd 243 and the relevant commits are
> referenced in the specific bug report:
> https://github.com/systemd/systemd/issues/
Package: systemd
Version: 241-5
Submitter: s.pri...@profihost.ag
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: buster-backport
Am 04.09.19 um 14:09 schrieb Stefan Priebe - Profihost AG:
> Hello,
>
> currently systemd is broken in buster regarding RootDirectory and User.
>
> The
On Thu, 27 Nov 2014 14:43:33 -0800 Nikolaus Rath wrote:
> On Sat, 15 Nov 2014 00:17:59 +0100 Szymon Weihs wrote:
> >
> > When I'm doing reboot or shutdown from graphical environment (systemctl
> > reboot/poweroff), my screen turns off immediately so I can't see any
> > messages
> > provided wit
Hi Joel
On Tue, 26 Jun 2018 11:54:36 +0100 Joel Cross
wrote:
> Package: systemd
> Version: 239-1
> Severity: normal
>
> Dear Maintainer,
>
> Over the last few days (since my last system upgrade) I am unable to
> successfully hibernate/resume using the `systemctl hibernate` command. This is
> wh
Am 04.09.19 um 14:57 schrieb Michael Biebl:
> Am 04.09.19 um 14:09 schrieb Stefan Priebe - Profihost AG:
>> Hello,
>>
>> currently systemd is broken in buster regarding RootDirectory and User.
>>
>> The issue was fixed in systemd 243 and the relevant commits are
Thanks for testing
Am 05.09.19 um 07:52 schrieb Stefan Priebe - Profihost AG:
> Yes, that works fine! Thanks a lot. Is there any ETA for a release?
As I tried to explain (see below), since I don't knwo when 10.2 will be,
the answer is no.
> Am 04.09.19 um 22:32 schrieb Michael B
Am 06.09.19 um 10:35 schrieb Michael Biebl:
> Am 06.09.19 um 10:25 schrieb Harald Dunkel:
>> Package: systemd
>> Version: 241-5
>>
>> systemd in Buster and older fails to handle MountFlags correctly,
>> see
>>
>> https://github.com/systemd/systemd/co
Am 06.09.19 um 10:25 schrieb Harald Dunkel:
> Package: systemd
> Version: 241-5
>
> systemd in Buster and older fails to handle MountFlags correctly,
> see
>
> https://github.com/systemd/systemd/commit/37ed15d7edaf59a1fc7c9e3552cd93a83f3814ef
>
>
> This seriously affects the "containerd" versio
Am 06.09.19 um 10:07 schrieb Martins Pukitis:
> Package: systemd
> Version: 241-5
> Severity: important
> File: systemd-networkd
>
> Dear Maintainer, bridge interface setup status stays "configuring" (not
> "configured").
> My systemd-networkd configuration:
> lieta@lieta:~$ sudo brctl show
> bri
Am 06.09.19 um 10:42 schrieb Michael Biebl:
> Am 06.09.19 um 10:35 schrieb Michael Biebl:
>> Am 06.09.19 um 10:25 schrieb Harald Dunkel:
>>> Would it be possible to cherrypick this fix for Buster and
>>> Stretch?
>>
>> Why stretch? According to the ups
Am 06.09.19 um 10:07 schrieb Martins Pukitis:
> Package: systemd
> Version: 241-5
> Severity: important
> File: systemd-networkd
>
> Dear Maintainer, bridge interface setup status stays "configuring" (not
> "configured").
> My systemd-networkd configuration:
> lieta@lieta:~$ sudo brctl show
> bri
Hi,
https://github.com/systemd/systemd/pull/13357 has just been merged into
systemd.
With this available in udev, I wonder if lib2f-udev and its static rules
becomes obsolete or if there is still value to keep that package?
Regards,
Michael
--
Why is it that all of the instruments seeking intel
Am 07.09.19 um 12:44 schrieb Michael Biebl:
> Control: tags -1 moreinfo
>
> Am 07.09.19 um 11:36 schrieb Nikolaus Rath:
>> Package: systemd-container
>> Version: 241-5
>> Severity: normal
>> File: /usr/bin/systemd-nspawn
>>
>> Not sure what to make of
Control: tags -1 moreinfo
Am 07.09.19 um 11:36 schrieb Nikolaus Rath:
> Package: systemd-container
> Version: 241-5
> Severity: normal
> File: /usr/bin/systemd-nspawn
>
> Not sure what to make of this:
>
> # systemd-nspawn -M resuce --boot --private-users -D /mnt/usbdrive
> Spawning container re
501 - 600 of 2021 matches
Mail list logo
