=== guiverc2 is now known as guiverc [06:02] sergiodj, btw, the debian maintainer is asking to patch Ubuntu.pm, not Debian.pm === justReddy is now known as justache [09:45] Is anyone working on the gnat-related issues? I'm currently looking into it (more specifically the ahven FTBFS) [15:53] LocutusOfBorg: I talked to him yesterday; I will work on it this week. thanks [17:09] ddstreet: mapreri: backport request #2002211 needs someone to look at it, Bastian asked me to sponsor it so I did, but I'd like an extra set of eyes before approving. === ahasenack_ is now known as ahasenack [18:16] vorlon: would you be opposed at me trying to enable apparmor by default on rsyslog? [18:17] I see it also needs a merge from debian, which I would also do, unless it's in your todo already (you are TIL in the package) [18:18] ahasenack: I don't have any objections [20:07] How do i disable LTO? i have tried optimize=-lto but does not do anything [20:24] mariogrip, https://wiki.ubuntu.com/ToolChain/LTO , that should work so maybe something more specific? [20:25] seb128: Does it matter where i put it in the rules file? [20:25] i have it at the top [20:27] top should fine [20:28] i building this on ppa [20:29] the source does not set lto [20:31] maybe share the build log url? [20:32] or ppa rather so people can check the source [20:32] https://launchpadlibrarian.net/645325791/buildlog_ubuntu-lunar-arm64.biometryd_0.0.3~git20230105.872dfab-1.7_BUILDING.txt.gz [20:32] https://launchpad.net/~mariogrip/+archive/ubuntu/lomiri-bleeding/+packages [20:32] biometryd is the one [20:44] https://launchpad.net/ubuntu/+source/lxc/1:5.0.1-0ubuntu1 hi - that pkg has been there awhile. what's needed to promote it out of -proposed? [21:01] huh fun, it works when building the package locally but not ppa [21:01] so somethings up with ppa and lto bulding [21:12] hallyn: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#lxc says that there are some autopkgtest regressions, quick look at the logs and golang-gopkg-lxc-go-lxc.v2 might be missing a build-dependency, and lxc a build failure? Would need deeper analysis. [21:15] dbungert: thanks. bookmarked that link [21:17] looks like the autopkg tests for it need to be updated for autoconf->meson :( [21:44] hallyn: the autopkgtst tests for which need to updated? [21:48] bdmurray: lxc [21:48] i forget where those are defined, haven't had a chance to look yet [21:48] In the debian/tests directory [21:50] oh i was thinking there was some external tree [21:51] can i easily run those tests locally? [21:51] i'll try with https://wiki.debian.org/ContinuousIntegration/autopkgtest [22:12] mariogrip: Without being able to explain why LTO was enabled in your PPA, I want to mention that I have successfully applied the opposite stragegy for C++ packages in order to make the symbols file work in both Debian and Ubuntu: Enable LTO in Debian. Example: https://bugs.debian.org/1024999 [22:12] -ubottu:#ubuntu-devel- Debian bug 1024999 in src:maliit-framework "Please consider to build with LTO enabled" [Wishlist, Open] [22:18] GunnarHj to enable LTO worked fine for me also, i have done this on some debian uploads, but for this specific package i need it off (due to some dlopen issue) [22:18] it builds fine on debian, but i want to fix package so it syncs fine with ubuntu [22:20] Anyway, lomiri with mir 2.11 now start fine on ubuntu lunar :D just missing some packages and it will fully be in lunar https://usercontent.irccloud-cdn.com/file/YvevSlDR/image.png [22:21] mariogrip: That was precisely the situation in the example I mentioned. It built fine on Debian, but we had to tweak the symbols file in Ubuntu. After having changed it on Debian, the package can now be sync'ed without changes. [22:22] GunnarHj yeah, but this package need lto off, else it segfaults :) [22:22] mariogrip: Sorry, I didn't read all your comments carefully enough. :/ [22:23] No problem :) [22:24] For symbols i use (optional=lto)c++::sym::blah but i should maybe enable lto on debian, but iirc it should be enabled by default after bookworm [22:27] mariogrip: Yeah, I think that's the plan. [22:29] I guess i'll just upload the package to debian with -lto since it has too be disabled anyway, lets see if it syncs fine the. Maybe it needs to be added to the lto exclusion file if that does not work? [22:31] May be worth a try. [22:34] mariogrip: Or wait.. If you just add "optimize=-lto" in Debian, the symbols file will reamin unchanged and the sync thus fail. Or am I missing something? [22:35] GunnarHj: Then the symbol file should be the same as debian [22:37] mariogrip: Ok, right, assuming that "optimize=-lto" is effective in universe as opposed to your PPA. ;) [22:38] I hope, since this package will not work with lto anyway tests will fail before it reach the symbols [22:38] Ack. [22:40] how often do the debian sync happen btw? [22:42] mariogrip: It happens always as long as autosync is on. [22:42] once a day? [22:43] More often than that, I think. I.e. as soon as it has been published in unstable. [22:48] autosync runs 4x per day https://people.canonical.com/~ubuntu-archive/auto-sync/2023-01-10/