| === bdrung_ is now known as bdrung | ||
| === tsimonq2_ is now known as tsimonq2 | ||
| === tsimonq2_ is now known as tsimonq2 | ||
| tsimonq2 | lvoytek: I retried mysql-8.4/plucky-proposed/ppc64el, it looks like ppc64el is slightly sad. | 04:10 |
|---|---|---|
| === guiverc2 is now known as guiverc | ||
| KeiOkada | Hi, I am a maintainer of euslisp/jskeus package and they are included in 23.10, but removed for 24.04. How can we re-include these packages in release? They are already released under debian sid/testing, see https://bugs.launchpad.net/ubuntu/+source/euslisp/+bug/2096808 for mor info | 10:02 |
| -ubottu:#ubuntu-devel- Launchpad bug 2096808 in euslisp (Ubuntu) "[SRU] Merge euslisp/jskeus from Debian unstable" [Undecided, New] | 10:02 | |
| mitya57 | tjaalton: Hi! Regarding your mesa merge: Debian #1092890 is still not fixed (I reopened it), maybe it's better to put it on hold until we find the fix? | 10:08 |
| -ubottu:#ubuntu-devel- Debian bug 1092890 in libglx-mesa0 "mesa: regression in 24.3: software rendering crashes on ppc64el with segmentation fault" [Serious, Open] https://bugs.debian.org/1092890 | 10:08 | |
| mitya57 | I tried building with different compiler (clang) and different linkers (gold, lld) but it didn't help much. | 10:09 |
| tjaalton | mitya57: bah, too late | 10:11 |
| tjaalton | it'll probably get stuck in proposed then | 10:12 |
| mitya57 | Well, we can ask for removal from -proposed | 10:12 |
| tjaalton | hm, yeah I can remove it | 10:12 |
| mitya57 | For now it didn't even build on ppc64el but there is no log so it's probably a LP issue. | 10:13 |
| sudip | KeiOkada: lp: #2096808 should not be marked as [SRU], but its in the sponsors list now at http://sponsoring-reports.ubuntu.com/ | 10:49 |
| -ubottu:#ubuntu-devel- Launchpad bug 2096808 in euslisp (Ubuntu) "[SRU] Merge euslisp/jskeus from Debian unstable" [Undecided, New] https://launchpad.net/bugs/2096808 | 10:49 | |
| Skia | utkarsh2102: https://code.launchpad.net/~hyask/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/480231 in case you missed it :D | 10:50 |
| utkarsh2102 | Skia: thanky! i'll get to it as soon as the test run is successful! | 10:51 |
| Skia | thanks | 10:51 |
| KeiOkada | suidip: thank you ! should i remove [SRU] from bug title? | 10:55 |
| sudip | KeiOkada: yes please. SRU is not for the current development branch | 11:08 |
| KeiOkada | ok, done | 11:15 |
| enr0n | Eickmeyer: that didn't solve it for me :/ | 14:31 |
| Skia | utkarsh2102: https://code.launchpad.net/~hyask/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/480231 CI is green | 14:37 |
| Skia | utkarsh2102: unrelated to release, but I had this MP too: https://code.launchpad.net/~hyask/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/480070 | 14:40 |
| sudip | ginggs: do you know if the autopkgtest for cl-ppcre were ignored in Debian for clisp migration? It fails in Debian too but for a different reason. | 14:49 |
| ginggs | sudip: clisp migrated on 2024-12-10 | 16:00 |
| ginggs | https://ci.debian.net/packages/c/cl-ppcre/testing/amd64/ | 16:00 |
| ginggs | shows a pass on 2024-12-04 21:30:25 UTC | 16:00 |
| ginggs | where do you see failures? | 16:01 |
| sudip | https://ci.debian.net/packages/c/cl-ppcre/unstable/amd64/ the test with clisp from unstable and https://ci.debian.net/data/autopkgtest/unstable/armhf/c/cl-ppcre/57071272/log.gz is for cl-ppcre on unstable. | 16:03 |
| sudip | s/the test with clisp from unstable/the test with clisp from experimental/ | 16:03 |
| utkarsh2102 | Skia: thanks, I'll merge those cdimage changes once I hear back from Michael about the debian-cd bits. | 16:09 |
| utkarsh2102 | so that we can pull Graham's cdimage and debian-cd changes together with yours. | 16:09 |
| utkarsh2102 | as for the u-a-t changes, they look good, thank you, but I'm not an AA yet so I'll leave that for an actual AA to review & merge? | 16:10 |
| sudip | ginggs: https://ci.debian.net/data/autopkgtest/testing/armhf/c/cl-ppcre/57072361/log.gz is cl-ppcre and only testing, no unstable | 16:15 |
| ginggs | sudip: https://ci.debian.net/packages/c/cl-ppcre/testing/armhf/ | 16:19 |
| ginggs | it looks like cl-ppcre regressed in testing on armhf sometime around 2024-09-09 03:08:12 UTC | 16:19 |
| Skia | hehe, ok, thought you'd have the rights. Maybe someone from ubuntu-archive could help merge this? https://code.launchpad.net/~hyask/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/480070 | 16:19 |
| ginggs | so it wouldn't have blocked the migration of clisp | 16:20 |
| sudip | ginggs: yeah, thats why I was asking if some hint was added to skip the test for clisp migration | 16:20 |
| sudip | ohh | 16:20 |
| sudip | ohhh. yeah.. migration-reference passes | 16:21 |
| sudip | s/passes/fails/ | 16:21 |
| * sudip cant type today | 16:21 | |
| sudip | but the migration-reference is passing in Ubuntu :) | 16:21 |
| sudip | https://autopkgtest.ubuntu.com/packages/cl-ppcre/plucky/armhf | 16:22 |
| seb128 | Skia, merged | 17:03 |
| tsimonq2 | Mornin' :) | 17:13 |
| tsimonq2 | The packaging guide lives! Last night, two PRs were merged WRT SRU docs + sponsorship: https://github.com/canonical/ubuntu-packaging-guide/pull/74 https://github.com/canonical/ubuntu-packaging-guide/pull/75 | 17:14 |
| -ubottu:#ubuntu-devel- Pull 74 in canonical/ubuntu-packaging-guide "Integrate external sru docs" [Merged] | 17:14 | |
| -ubottu:#ubuntu-devel- Pull 75 in canonical/ubuntu-packaging-guide "Documentation: Add explanation about sponsorship" [Merged] | 17:14 | |
| * tsimonq2 will circle back re: sponsorship | 17:14 | |
| tsimonq2 | I also fixed up https://ubuntu.com/community/contribute/ubuntu-development a bit last night | 17:14 |
| tsimonq2 | Lubuntu CI also lives, although I'm in the continuous process of dealing with it with a large hammer. I expect all of that to settle down completely by US EOD (and in reality the only thing it blocks is test builds.) | 17:20 |
| tsimonq2 | https://ci.lubuntu.tsimonq2.net/ is accessible to anyone in ~ubuntu-qt-code (which include MOTU IIRC) but it's very nascent. The bounty for finding security bugs is one coffee or beer at the Ubuntu Summit. ;P | 17:21 |
| Eickmeyer | enr0n: I'm at a total loss. Afaict pulseaudio keeps trying to reassert itself. | 18:44 |
| === nibbon_5 is now known as nibbon_ | ||
| sudip | mwhudson: did you manage to reproduce the problem? I now have very simple steps to reproduce the problem | 19:57 |
| === amurray_ is now known as amurray | ||
| juliank | rbasak: re the just concluded meeting, I'd like to suggest waiting for the move until the IRC rooms are plumbed, then IRC just keeps working (and lol yes you could talk to meetingology over it :D) | 20:42 |
| juliank | I don't know how far along it is | 20:42 |
| juliank | This will allow the natural move and we can decide later if the plumbing is bad | 20:44 |
| juliank | Also the server still has to move to a bigger instance | 20:45 |
| RikMills | arraybolt3_: ^^ how long for room plumbing? | 20:47 |
| === guiverc2 is now known as guiverc | ||
| Eickmeyer | juliank: Any chance you have a spare moment to help enr0n and I out with https://code.launchpad.net/~eeickmeyer/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/480208? | 21:12 |
| Eickmeyer | Mostly just need some log analysis. | 21:12 |
| juliank | Eickmeyer: I already talked to enr0n | 21:38 |
| juliank | It's about as dumb as you'd expect, apt has been told to remove pulseaudio:amd64 and hence tries to install pulseaudio:i386 to satisfy pulseaudio reverse dependencies | 21:40 |
| Eickmeyer | Yeah, kinda had the feeling that's what was happening. Can we also block pipewire:i386 or is that totally moot? | 21:43 |
| Eickmeyer | juliank: Aha! Ok, so removing/protecting `pipewire:i386` allowed it to calculate the upgrade. | 21:49 |
| Eickmeyer | Appears to be working. | 21:49 |
| Eickmeyer | s/pipewire:i386/pulseaudio:i386/ | 21:49 |
| ahasenack | does anybody know if there is some sort of "movement" or pattern to get rid of /etc/default/<pkg> files? | 22:12 |
| ahasenack | I see the pattern in systemd units to set EnvironmentFile=-/etc/default/<name> (notice the "-" prefix), | 22:12 |
| === bandali is now known as mab | ||
| ahasenack | and later the start command reference some variable which *may* be defined in that /etc/default/<name> file | 22:13 |
| ahasenack | but if it's not, or if the /etc/default/<name> file does not exist, systemd emits a warning | 22:13 |
| ahasenack | Referenced but unset environment variable evaluates to an empty string: <var-name> | 22:13 |
| ahasenack | which can be annoying | 22:13 |
| ahasenack | this pattern of /etc/default/<name> came from the sysv days, and migrated to systemd via the EnvironmentFile option | 22:14 |
| ahasenack | some argue that the "correct" way to customize startup options is to just override the systemd unit | 22:15 |
| Eickmeyer | ahasenack: Not to my knowledge? I know that grub still very much uses it and the `grub.d` directory. | 22:16 |
| ahasenack | maybe systemd didn't emit that warning before | 22:17 |
| ahasenack | but now I'm seeing more and more packages which do this and do not ship the /etc/default file | 22:17 |
| ahasenack | I might be exaggerating a bit, but I did see this quite a few times, and just now was pointed at a bug even: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2091977 | 22:17 |
| -ubottu:#ubuntu-devel- Launchpad bug 2091977 in unbound (Ubuntu) "missing file /etc/default/unbound" [Undecided, New] | 22:17 | |
| sudip | mwhudson: if you still looking for a simple reproducer for the patchelf problem then this is what I have for you - https://pastebin.ubuntu.com/p/9yYbdQ3dvV/ | 22:30 |
| mwhudson | sudip: which architecture are you running that on? | 23:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!