[Touch-packages] [Bug 760140] Re: HOME environmental variable no long preserved with sudo by default

2015-04-29 Thread Zhang Youfu
I'm expecting the documented behavior. Please refer Bug #889936 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/760140 Title: HOME environmental variable no long preserved

[Touch-packages] [Bug 1692353] Re: systemd-fsckd : useless CR displayed on console

2019-03-20 Thread Zhang Youfu
This bug still exists in 19.04 Disco. Please fix it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1692353 Title: systemd-fsckd : useless CR displayed on console Status

[Touch-packages] [Bug 1845909] [NEW] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-09-30 Thread Zhang Youfu
Public bug reported: upstream issue: https://github.com/systemd/systemd/issues/12886 upstream patch: https://github.com/systemd/systemd/pull/13565 The upstream fix will be available in systemd 244. Backport please. Thanks. ** Affects: systemd (Ubuntu) Importance: Undecided Status:

[Touch-packages] [Bug 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-09-30 Thread Zhang Youfu
Emm, I think the issue I referenced above is an incorrect one. https://github.com/systemd/systemd/issues/9890 & https://github.com/systemd/systemd/pull/11423 I think `debian/patches/networkd-honour-LinkLocalAddressing.patch` might be an incorrect backport of this upstream bug. ** Bug watch

[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-10-30 Thread Zhang Youfu
filed an upstream issue ** Bug watch added: github.com/systemd/systemd/issues #13882 https://github.com/systemd/systemd/issues/13882 ** Changed in: systemd Status: Fix Released => Unknown ** Changed in: systemd Remote watch: github.com/systemd/systemd/issues #12886 =>

[Touch-packages] [Bug 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-10-04 Thread Zhang Youfu
I'm running Ubuntu 19.04 with systemd 240-6ubuntu5.7 systemd-networkd configuration: ``` # eno1.network [Match] Name=eno1 [Link] Multicast=no [Network] LinkLocalAddressing=no Address=192.168.50.249/24 Gateway=192.168.50.1 DNS=192.168.50.1 VLAN=pppoe # pppoe.netdev [NetDev] Name=pppoe Kind=vlan

[Touch-packages] [Bug 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-10-04 Thread Zhang Youfu
After upgraded to Ubuntu 19.10 with systemd 242-6ubuntu1, the issue I encountered disappeared. ``` # ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever

[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-10-05 Thread Zhang Youfu
This issue also affects 18.04 LTS with systemd 237-3ubuntu10.29 A VLAN interface with LinkLocalAddressing=no configured is not honored -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet

2019-10-12 Thread Zhang Youfu
For my installation, I found that dnsmasq is running with -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new arguments. /etc/dnsmasq.d/libvirt-daemon specified bind-interfaces, causing dnsmasq trying to bind to each interface on startup, which was unfortunately not available yet. Comment out the

[Touch-packages] [Bug 1897365] Re: RoutingPolicyRule not applied on reconfigure

2020-10-11 Thread Zhang Youfu
And https://github.com/systemd/systemd/pull/16881 Not available in systemd-stable v246 yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1897365 Title:

[Touch-packages] [Bug 1897365] [NEW] RoutingPolicyRule not applied on reconfigure

2020-09-26 Thread Zhang Youfu
Public bug reported: I noticed some error message from systemd-networkd in log journal. systemd-networkd[4343]: Failed to parse RPDB rule family, ignoring: AF_INETpriority=28fwmark=28/0 This appears to be a known issue at https://github.com/systemd/systemd/issues/16784 Fix is available at

[Touch-packages] [Bug 1925827] Re: [v247] backport routing policy rule fix

2021-05-22 Thread Zhang Youfu
> I'm able to reproduce this on hirsute, but not groovy, so this seems to > affect only hirsute; please correct me if that's wrong. That’s correct. > only 'networkctl reload' doesn't work, normal systemd-networkd startup works `systemctl restart systemd-networkd` doesn’t work either. -- You

[Touch-packages] [Bug 1925827] Re: [v247] backport routing policy rule fix

2021-07-12 Thread Zhang Youfu
Tested systemd 247.3-3ubuntu3.2 on hirsute, without problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925827 Title: [v247] backport routing policy rule fix Status

[Touch-packages] [Bug 1925827] Re: [v247] backport routing policy rule fix

2021-07-12 Thread Zhang Youfu
Tested systemd 247.3-3ubuntu3.2 on hirsute, without problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925827 Title: [v247] backport routing policy rule fix Status

[Touch-packages] [Bug 1897365] Re: RoutingPolicyRule not applied on reconfigure

2021-06-29 Thread Zhang Youfu
Per my testing, restart systemd-networkd is also affected. Debian maintainer refused to apply my backport due to patch size. https://github.com/systemd/systemd-stable/pull/96 That’s fair. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1925827] [NEW] [v247] backport routing policy rule fix

2021-04-23 Thread Zhang Youfu
Public bug reported: The original issue can be found at https://github.com/systemd/systemd/issues/18107. I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) against v247-stable branch, which got merged and released in v247.4. However due to the freezing state of Debian