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-networkd.service in v241 is locked down more
Processing control commands:
> severity -1 important
Bug #929469 [systemd] systemd-networkd: fails with "could not set address:
Permission denied"
Severity set to 'important' from 'serious'
--
929469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929469
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> tags 929726 + fixed-upstream
Bug #929726 [systemd] ask-password: prevent buffer overrow when reading from
keyring
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
929726:
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.
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
Processing control commands:
> reassign -1 ifupdown
Bug #930652 [systemd] systemd removes static ipv4 address from ethernet
sporadically
Bug reassigned from package 'systemd' to 'ifupdown'.
No longer marked as found in versions systemd/241-5.
Ignoring request to alter fixed versions of bug
I have attached a copy of /etc/network/interfaces. We're now waiting
for another recurrence.
interfaces
Description: Binary data
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
Package: systemd
Version: 240-6ubuntu5.1
Severity: normal
Dear Maintainer,
Upstream systemd CI is broken on Ubuntu due to a recent upstream change. The
d/t/boot-and-services test needs to be fixed to account for the new upstream
change.
This is reported upstream at: