-queuebot:#ubuntu-release- New binary: fenics-ffcx [amd64] (jammy-proposed/universe) [1:0.3.0-3] (no packageset)00:40
bdmurraymwhudson: can you get the smooth_updates conversation restarted?08:40
-queuebot:#ubuntu-release- Unapproved: gst-plugins-bad1.0 (focal-proposed/universe) [1.16.2-2.1ubuntu1 => 1.16.3-0ubuntu1] (i386-whitelist, kubuntu)09:00
-queuebot:#ubuntu-release- Unapproved: simplestreams (bionic-backports/main) [0.1.0~bzr460-0ubuntu1.1 => 0.1.0-48-gb936edd4-0ubuntu1~bpo18.04.1] (ubuntu-cloud, ubuntu-server)09:03
-queuebot:#ubuntu-release- New: accepted fenics-ffcx [amd64] (jammy-proposed) [1:0.3.0-3]09:59
rbasaksil2100: have you seen this failing oem-meta-packageset-sync cronjob on snakefruit spamming devel-permissions@?11:00
rbasaksil2100: could you disable it for now please?11:00
bdmurrayrbasak: I'll let him know when I see him11:21
holmanbnot sure if there is time in SRU vanguard today or not. cloud-init has a queued for -proposed (22.1-14-g2e17a0d6) that we'd like to request review for upload  into (bionic|focal|impish)-proposed  per https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/196144611:26
ubottuLaunchpad bug 1961446 in cloud-init (Ubuntu Impish) "sru cloud-init (22.1 update) Bionic, Focal, Impish" [Undecided, In Progress]11:26
holmanbPlease also reject the prior unaccepted cloud-init 22.1-1 uploads that are queued for bionic, focal and impish.11:26
bdmurrayholmanb: Is it a priority to get it done this week? A couple of SRU team members are at a sprint.11:29
bdmurrayholmanb: If it is a priority you might try pinging RA_OF11:31
holmanbbdmurray: it will push back the start of our aging to Monday if it doesn't go in today. It wouldn't be the worst thing, but sooner is better.11:38
-queuebot:#ubuntu-release- New binary: fenics-dolfinx [ppc64el] (jammy-proposed/universe) [1:0.3.0-13] (no packageset)11:50
laneyrbasak: can you fix the owner of https://people.canonical.com/~ubuntu-archive/packagesets/jammy/canonical-oem-metapackages to be ~ubuntu-archive? I wonder why it got created with a different owner - does the initialisation process need to be fixed?12:11
laneyah, I see you already noticed the spam12:12
-queuebot:#ubuntu-release- New binary: fenics-dolfinx [s390x] (jammy-proposed/universe) [1:0.3.0-13] (no packageset)12:39
sil2100rbasak: hey! You were pinging about the oem-meta-packageset-sync, right?12:51
rbasakYes, but laney suggests what's wrong above. I'm just looking into fixing that now.12:52
sil2100I'll take a look, I think the creds might have expired. Will check up soon12:52
-queuebot:#ubuntu-release- New binary: fenics-dolfinx [armhf] (jammy-proposed/universe) [1:0.3.0-13] (no packageset)12:52
sil2100Oh, ok o/12:52
sil2100No backlog here!12:52
sil2100If you need any help or anything, just give me a poke. I'll get back to sprinting madness then12:55
rbasakOK owner changed to ~ubuntu-archive12:55
rbasakThanks laney!12:56
rbasakLet's see if that fixes it.12:56
rbasakpkgset = lp.packagesets.getByName(name='canonical-oem-metapackages', distroseries=lp.distributions['ubuntu'].getSeries(name_or_version='jammy'))12:58
rbasakpkgset.owner = lp.people['ubuntu-archive']12:58
laneymerci rbasak12:59
laneyyou should find out in 45 seconds I guess :-)12:59
rbasakAh just in time :)12:59
laneyWorked 👍13:00
laneyhow come that all only just happened?13:01
laneyI'd have expected the packageset to have existed all along13:01
rbasakThanks laney. I couldn't determine the problem from the backtrace13:01
laneyno worries, the 401 unauthorized gave it away to me13:02
laneyprobably an 'if you know, you know' thing13:02
-queuebot:#ubuntu-release- New binary: fenics-dolfinx [arm64] (jammy-proposed/universe) [1:0.3.0-13] (no packageset)13:04
rbasakLooks like the jammy packageset was created on 2021-10-1513:08
rbasakBut since then the emails suggest that the script never tried to add any entries to the jammy packageset13:09
rbasakSo this is the first time it got triggered to actually use the packageset perhaps?13:09
laneyit must be that this function wasn't returning jammy up until now https://git.launchpad.net/~developer-membership-board/+git/oem-meta-packageset-sync/tree/oem-meta-packageset-sync#n7713:11
laneyperhaps snakefruit only just got an update to distro-info-data13:11
RikMillskubuntu daily ISO build is not getting copied to cdimage13:13
rbasakJust updating the DMB docs on this.13:13
rbasakThe archive admin team runs/manages the script, right? Not the release team?13:14
laneyyes, but the DMB owns it in that they're supposed to gatekeep all code changes - that's why it is under that team on LP13:15
rbasakThanks. I updated https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Canonical_OEM_metapackage_packageset - I noticed that while the packageset was documented the automation was not.13:17
rbasakI've glossed over packageset/per-series packagesets13:17
laneylooks great13:17
-queuebot:#ubuntu-release- Packageset: 97 entries have been added or removed13:21
dokoEickmeyer: you uploaded onetbb, do you continue with the transition?13:48
-queuebot:#ubuntu-release- New: accepted fenics-dolfinx [arm64] (jammy-proposed) [1:0.3.0-13]13:50
-queuebot:#ubuntu-release- New: accepted fenics-dolfinx [ppc64el] (jammy-proposed) [1:0.3.0-13]13:50
-queuebot:#ubuntu-release- New: accepted fenics-dolfinx [armhf] (jammy-proposed) [1:0.3.0-13]13:50
-queuebot:#ubuntu-release- New: accepted fenics-dolfinx [s390x] (jammy-proposed) [1:0.3.0-13]13:50
sil2100rbasak, laney: thanks!14:01
Eickmeyerdoko: I'm not sure. It seems to me that the old tbb needs to be removed first (I did file a bug report about that), but the new onetbb seems to introduce some regressions according to britney. I was going to leave it up to ubuntu-archive.15:49
ginggsEickmeyer: these packages need rebuilding before the old tbb can be removed16:48
Eickmeyerginggs: I see. I also see that some of them are incompatible with a newer libtbb?16:49
ginggsbut at least half of those in level 2 will FTBFS16:50
ginggsso I think we should revert onetbb for now16:50
ginggsdoko: ^16:50
Eickmeyerginggs: If that's the case, we lose numba, which will cause all sorts of issues.16:50
ginggsEickmeyer: we already removed numba, what kind of issues will removing it again cause?16:51
Eickmeyerginggs: I uploaded a newer version, and part of the reason python3-defaults wouldn't migrate was the lack of numba, and a bunch of packages depended on it.16:51
dokoEickmeyer: then repackage tbb to have non-conflicting packages?16:51
ginggsEickmeyer: numba was not a reason why python3-defaults would not migrate16:52
dokono, migration of python3-defaults was independent of that16:52
EickmeyerOK, let's remove numba and revert tbb.16:52
EickmeyerThis is what I get for trying to help.16:52
dokohelp is appreciated if it's complete =)16:53
EickmeyerWell, I had no idea this was going to happen.16:53
mwhudsonbdmurray: ack19:49
LocutusOfBorgubuntu-archive: can we please kick myspell out from jammy? removed in sid, bug: #100613420:26
ubottuBug 1006134 in Stellarium "Ocular plugin: minor issue when adding a telescope" [Low, Fix Released] https://launchpad.net/bugs/100613420:26
LocutusOfBorgifrench-gut mighe20:27
LocutusOfBorg*might need to migrate first, others are false positives20:27
jochenspHi, could someone help with getting the latest open3d into jammy? Maybe by simply dropping the old ppc64el build?20:54
RikMillsjochensp: looks like a LTO related build error, and when trying the proposed amd64 build in a VM it segfaults on launch21:11
jochenspRikMills: interestingly it build in Debian, will try to run it21:12
RikMillsjochensp: debian does not build with LTO enabled by default yet21:12
jochenspbut open3d is build with -flto in Debian: https://buildd.debian.org/status/fetch.php?pkg=open3d&arch=amd64&ver=0.14.1%2Bdfsg-7&stamp=1645372419&raw=021:14
jochensp(though I guess the incompatible compiler options are from Ubuntu: ‘-mrelocatable’ and ‘-mcall-linux’ are incompatible)21:16
jochenspsmall correction: only the Python plugin is build with -flto and Ubuntu building everything with it is probably the reason for the segfault21:27
jochenspwould you still accept a patch to disable LTO for Ubuntu?21:27
mwhudsonjochensp: we've certainly disabled lto on other packages for this sort of reason21:35
jochenspI guess DEB_CFLAGS_MAINT_APPEND=-fno-lto should do it, should we push that through Debian or do you want to do a +ubuntu1 version? (I would really like to have the new version in jammy)21:36
mwhudsonjochensp: there is the lto-disabled-list package too21:37
mwhudsoni assume open3d is in universe21:37
sarnoldhopefully helpful https://wiki.ubuntu.com/ToolChain/LTO21:38
jochenspuniverse, yes21:38
jochenspcan I do something to have it fixed in jammy?21:43
mwhudsonjochensp: file a bug in launchpad?21:46
jochenspagainst which package?21:46
mwhudsonjochensp: open3d pls21:47
mwhudsoni can do the archive bits, they're trivial enough21:47
jochenspmwhudson: https://bugs.launchpad.net/ubuntu/+source/open3d/+bug/1963556 (thanks :) )21:50
ubottuLaunchpad bug 1963556 in open3d (Ubuntu) "Open3D segfaults when compiled with LTO" [Undecided, New]21:50
mwhudsontil https://en.cppreference.com/w/cpp/language/siof21:51
mwhudsonjochensp: uhhh open3d is already in here21:55
mwhudsonand has been since march 202121:56
jochenspbut I see a lot of -flto here: https://launchpadlibrarian.net/587715572/buildlog_ubuntu-jammy-amd64.open3d_0.14.1+dfsg-7build1_BUILDING.txt.gz21:56
mwhudsonwhere is this coming from then21:57
jochenspI don't see them in the Debian build21:57
mwhudsontime to do some debugging i guess21:58
mwhudsonwhy does open3d have its own copy of dpkg-buildflags??22:00
mwhudsonah wait no22:00
mwhudsonjochensp: the lto build flags are not the ones ubuntu uses though hm,m22:05
mwhudsonthis is going to be cmake somehow isn't it22:07
mwhudsonah, pybind22:09
jochensppybind uses LTO in Debian as well, but not the rest22:09
mwhudsonjochensp: all the hits for flto in https://launchpadlibrarian.net/587715572/buildlog_ubuntu-jammy-amd64.open3d_0.14.1+dfsg-7build1_BUILDING.txt.gz are for python bits afaics22:10
jochenspseems like, yeah22:12
mwhudsonin particular the link of libOpen3D.so.0.14.1 doesn't use anything exotic, so maybe this isn't https://github.com/isl-org/Open3D/issues/4747 after all22:13
ubottuIssue 4747 in isl-org/Open3D "Link Time Optimization (-flto) triggers static initialization bug in Open3D" [Open]22:13
jochenspmaybe.. do you have an idea where ‘-mrelocatable’ and ‘-mcall-linux’ are incompatible is coming from in the ppc64el build? (maybe that gives us a hint)22:16
jochensphere: https://launchpadlibrarian.net/588854642/buildlog_ubuntu-jammy-ppc64el.open3d_0.14.1+dfsg-7build1_BUILDING.txt.gz22:17
mwhudsonjochensp: no22:26
mwhudsonbut i can try a ppc64el build and see what i can find i guess22:26
mwhudson-Bsymbolic-functions is always a good bet for "things go wrong in strange ways"22:27
mwhudsonwhat is *this* person doing https://stackoverflow.com/questions/50746045/how-to-disable-mcall-linux-in-gcc22:29
mwhudson"It is not a full OS. We do not use RAM. All the executables are loaded in the processor cache."22:30
sarnoldmwhudson: *wild*22:30
jochenspthe unstable open3d packages work in jammy so seems to be something in the Ubuntu build22:33
mwhudsonjochensp: what is the default gcc / g++ in debian currently?23:19
mwhudsonbut that's interesting, means it's not glibc 2.35 i guess23:19
jochenspand libc6 is 2.33-723:20
mwhudsonUbuntu 11.2.0-16ubuntu123:20
mwhudsonclose enough, you'd have thought23:20

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