mohaIn an Ubuntu server 22.04, I have some interfaces. If I comment one of them (in order to deactivate it) and then `netplan apply`, `ip -br a`--> the one that has been commented is still up and can ping its gateway! What could be wrong? I should reboot the OS, then that interface will be in 'Down' state.09:26
mohaNote: I'm using 'bridges' in the netplan config file09:27
mohaIndeed it can not down/up a bridge that has been changed in the config file. Deos it need to restart any other services?09:27
schopinmoha: unless you use the --state option to netplan apply, the code won't know that your old interface used to be managed by netplan, and so will simply ignore it, as we figure it's better not to break stuff we're not sure we're owning ;)09:28
Eighth_Doctorslyon: I'm trying to package 0.106 in Fedora, but the meson install step always throws this error:10:40
Eighth_DoctorERROR: Tried to install symlink to missing file /builddir/build/BUILDROOT/netplan-0.106-1.fc39.x86_64/usr/lib/systemd/system-generators/../../../usr/libexec/netplan/generate10:40
schopinEighth_Doctor: do you have a link to the full build?10:41
Eighth_Doctorwell it's on my computer, but give me a sec and I'll give you one10:42
schopinbuild logs, of course :)10:42
Eighth_Doctorhere's a scratch build that you can get logs from once it finishes failing: https://koji.fedoraproject.org/koji/taskinfo?taskID=9747325810:43
Eighth_Doctoralso, netplan requiring meson 0.61 means I can't upgrade it for RHEL 8 anymore10:43
Eighth_Doctorthey only have meson 0.5810:43
schopinEighth_Doctor: that's weird. The install step for `generate` seems to be fine, and the target is apparently the right directory (if I count my ../ correctly ;) ). Do you have access to the build root? If so, can you try and find where the `generate` executable actually ended up?10:53
Eighth_Doctorgive me a sec, I need to re-run it without cleanup :)10:54
Eighth_Doctorthen I can look10:54
Eighth_Doctorschopin: the generate binary seems to be in usr/libexec/netplan10:57
Eighth_Doctorwhich is where it's supposed to be10:58
slyonEighth_Doctor: thanks for working on the 0.106 RPMs!11:02
Eighth_Doctoryeah, once I have this working, I'll update the spec upstream too11:03
Eighth_DoctorI think this really is an argument for having CentOS/Fedora CI for netplan11:03
slyonWe need some meson 0.61 features, so there was no way to avoid that. But you could still use the legacy "Makefile" build on RHEL8 if needed.11:03
Eighth_Doctoryou deleted it, didn't you?11:03
slyonYes, I agree. I want CentOS/Fedora and Debian CI11:04
Eighth_Doctoryeah, the Makefile only wraps Meson11:04
Eighth_Doctorso that doesn't help at all 😅11:04
slyonEighth_Doctor: I kept it for the 0.106 release, it's still in the tarball11:04
slyonI only dropped the legacy Makefile after release11:04
slyonas we don't want to support that any longer11:04
Eighth_DoctorI kind of wish cmake had been chosen because of how much more stable it is, but ehh11:05
Eighth_DoctorI should at least send up the one patch I have locally11:05
slyonbut meson is the new fancy! :D (and they have a 1.0 now!)11:05
Eighth_Doctoryeah, but does that mean they'll keep to some kind of stability promise?11:06
Eighth_Doctorand we don't have that in RHEL 8 or RHEL 9 :(11:06
Eighth_Doctorit was hell getting RHEL 9 upgraded to meson 0.6311:07
slyonright. We'll try to keep the requirement at 0.61 for now11:08
Eighth_DoctorI guess this will be the end of the line for RHEL 811:09
Eighth_Doctorat least this means that compat patch you don't like doesn't have to be upstreamed :P11:10
Eighth_DoctorI don't want this again11:12
Eighth_Doctorbut I think I'm going to basically force us to have CentOS and Fedora CI now11:12
slyonwrt you symlink issue.. I think it could be related to the /usr prefix on a merged-usr vs split-usr system (not sure what RHEL8/9 are using?) https://wiki.debian.org/UsrMerge https://wiki.gentoo.org/wiki/Merge-usr11:12
schopinEighth_Doctor: sorry, that's now officially the end of my intuitions for this issue. I'll leave it in slyon 's capable hands ;)11:12
Eighth_Doctorslyon: we're a mergedusr distro (the first even!)11:13
slyonEighth_Doctor: OK so it should be very similar11:13
Eighth_Doctorback then it was just called UsrMove11:13
slyon"ERROR: Tried to install symlink to missing file /builddir/build/BUILDROOT/netplan-0.106-1.fc39.x86_64/usr/lib/systemd/system-generators/../../../usr/libexec/netplan/generate" -> I think this is related to the systemd_generator_dir variable in meson, which is consumed from pkgconfig 'systemdsystemgeneratordir'11:20
slyonsee https://launchpadlibrarian.net/650576320/buildlog_ubuntu-lunar-amd64.netplan.io_0.106-0ubuntu1_BUILDING.txt.gz for how the layout on the Ubuntu build is looking like, e.g.:11:20
slyonlrwxrwxrwx root/root         0 2023-02-09 11:10 ./lib/systemd/system-generators/netplan -> /usr/libexec/netplan/generate11:20
slyon(instead of /usr/lib/systemd/systemd-generators)11:20
Eighth_Doctoroh, you guys haven't switched to merged /usr for systemd itself yet?11:31
slyonI'm not as involved in systemd maintenance anymore. Can't recall the details11:39
Eighth_Doctorlooks like adding one more traversal made the symlink generation work properly11:56
Eighth_Doctorslyon: https://github.com/canonical/netplan/pull/32313:55
slyonEighth_Doctor: thank you! I need to double check the systemd usrmerge situation in Debian/Ubuntu wrt to that meson.build change. Otherwise this LGTM!13:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!