-queuebot:#ubuntu-release- New sync: onetbb (jammy-proposed/primary) [2021.5.0-7]06:56
-queuebot:#ubuntu-release- New: accepted onetbb [sync] (jammy-proposed) [2021.5.0-7]06:58
-queuebot:#ubuntu-release- New: accepted sdl12-compat [amd64] (jammy-proposed) [1.2.52-3]06:58
-queuebot:#ubuntu-release- New: accepted sdl12-compat [armhf] (jammy-proposed) [1.2.52-3]06:58
-queuebot:#ubuntu-release- New: accepted sdl12-compat [riscv64] (jammy-proposed) [1.2.52-3]06:58
-queuebot:#ubuntu-release- New: accepted sdl12-compat [arm64] (jammy-proposed) [1.2.52-3]06:59
-queuebot:#ubuntu-release- New: accepted sdl12-compat [s390x] (jammy-proposed) [1.2.52-3]06:59
-queuebot:#ubuntu-release- New: accepted sdl12-compat [ppc64el] (jammy-proposed) [1.2.52-3]06:59
seb128doko, hey, why did you rename the tbb binaries, there is no explanation nor bug reference in the upload. It makes other things in the archive like gtk no build anymore because they use the old naming, should we at least have a provides?07:39
dokoseb128: no libtbb-dev is built by onetbb. I'll go through the r-dependencies, and change those to libtbb2-dev which still require the old tbb. work in progress, waiting for the builds07:52
dokohmm, where exactly is gtk affected?07:53
seb128doko, https://launchpadlibrarian.net/589580643/buildlog_ubuntu-jammy-amd64.gtk4_4.6.1+ds-1ubuntu2_BUILDING.txt.gz07:53
seb128 libtbb12 : Breaks: libtbb2 (< 2021) but 2020.3-1ubuntu1 is to be installed07:53
seb128doko, also onettb fails to build on riscv64 so gtk isn't going to be able to build there07:54
seb128which in on the path to have the new GNOME migrating07:54
dokothe fix is uploaded07:55
dokook, I'll look at the breaks07:55
dokoohh crap, libtbb12 ships multiple shared libs, with unrenamed sonames. bad packaging ... ok, I'll remove that again, until I have a solution for that one08:01
seb128we are past feature freeze, new packages should require a ffe anyway at this point08:02
dokothis package was there, and only was removed yesterday.08:04
-queuebot:#ubuntu-release- Packageset: Removed mozjs78 from i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Removed shtool from i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Added gcc-12-cross-ports to i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Added onetbb to i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Added postgresql-common to i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Added racc to i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Added rubocop to i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Added ruby-ast to i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Added ruby-mini-portile2 to i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Added ruby-parallel to i386-whitelist in jammy08:06
-queuebot:#ubuntu-release- Packageset: Added ruby-rainbow to i386-whitelist in jammy08:07
-queuebot:#ubuntu-release- Packageset: Added ruby-regexp-parser to i386-whitelist in jammy08:07
-queuebot:#ubuntu-release- Packageset: Added ruby-rubocop-ast to i386-whitelist in jammy08:07
-queuebot:#ubuntu-release- Packageset: Added ruby-unicode-display-width to i386-whitelist in jammy08:07
-queuebot:#ubuntu-release- Packageset: Added ruby-whitequark-parser to i386-whitelist in jammy08:07
-queuebot:#ubuntu-release- Packageset: Added ssl-cert to i386-whitelist in jammy08:07
=== michagogo is now known as micha_
-queuebot:#ubuntu-release- New binary: tbb [i386] (jammy-proposed/universe) [2020.3-1ubuntu2] (i386-whitelist, kubuntu)09:06
-queuebot:#ubuntu-release- New binary: tbb [amd64] (jammy-proposed/universe) [2020.3-1ubuntu2] (i386-whitelist, kubuntu)09:07
-queuebot:#ubuntu-release- New binary: tbb [s390x] (jammy-proposed/universe) [2020.3-1ubuntu2] (i386-whitelist, kubuntu)09:10
-queuebot:#ubuntu-release- New binary: tbb [ppc64el] (jammy-proposed/universe) [2020.3-1ubuntu2] (i386-whitelist, kubuntu)09:14
-queuebot:#ubuntu-release- New binary: tbb [riscv64] (jammy-proposed/universe) [2020.3-1ubuntu2] (i386-whitelist, kubuntu)09:21
seb128sil2100, hey, any chance you could retry https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/jammy/ubuntu-canary ? it failed again on that09:26
seb128! Could not open (any of):09:26
seb128!   http://people.canonical.com/~ubuntu-archive/seeds/ubuntu.jammy/STRUCTURE09:26
ubottuseb128: I am only a bot, please don't think I'm intelligent :)09:26
seb128but the ubuntu iso built today so that seems a flaky error09:26
seb128sil2100, also if you retry you might need to tweak your cmd, the retry you did yesterday didn't include the canary ppa archive according to the log09:27
sil2100seb128: oh, crap, right - forgot about that. Let me do that via ancientminister then09:27
seb128sil2100, thx09:27
sil2100seb128: btw. how are you guys using the canary PPA? Is that like a staging fast-development thing before landing in the archive?09:28
seb128sil2100, yes, it's either for testing candidate fixes, or in this case I added debug code in an hacked version of livecd-rootfs to try to debug https://bugs.launchpad.net/launchpad-buildd/+bug/196370609:29
ubottuLaunchpad bug 1963706 in launchpad-buildd "Ubuntu Desktop Canary ISO failing to build since builders update" [High, New]09:29
seb128sil2100, but most of the time the ppa is empty09:30
sil2100seb128: ok, good, thanks!09:30
-queuebot:#ubuntu-release- New binary: tbb [arm64] (jammy-proposed/universe) [2020.3-1ubuntu2] (i386-whitelist, kubuntu)09:38
-queuebot:#ubuntu-release- New binary: tbb [armhf] (jammy-proposed/universe) [2020.3-1ubuntu2] (i386-whitelist, kubuntu)09:39
julianksil2100: Let's force-skiptest netcat-openbsd/1.218-4ubuntu1 then I guess, my retry with new gsocket did not help britney either, let's migrate it, and hope britney doesn't crap out again09:40
-queuebot:#ubuntu-release- New: accepted tbb [amd64] (jammy-proposed) [2020.3-1ubuntu2]09:41
-queuebot:#ubuntu-release- New: accepted tbb [armhf] (jammy-proposed) [2020.3-1ubuntu2]09:41
-queuebot:#ubuntu-release- New: accepted tbb [ppc64el] (jammy-proposed) [2020.3-1ubuntu2]09:41
-queuebot:#ubuntu-release- New: accepted tbb [s390x] (jammy-proposed) [2020.3-1ubuntu2]09:41
-queuebot:#ubuntu-release- New: accepted tbb [arm64] (jammy-proposed) [2020.3-1ubuntu2]09:41
-queuebot:#ubuntu-release- New: accepted tbb [riscv64] (jammy-proposed) [2020.3-1ubuntu2]09:41
-queuebot:#ubuntu-release- New: accepted tbb [i386] (jammy-proposed) [2020.3-1ubuntu2]09:41
-queuebot:#ubuntu-release- New: accepted python-unicodedata2 [sync] (jammy-proposed) [14.0.0+ds-8]09:41
-queuebot:#ubuntu-release- New binary: python-unicodedata2 [amd64] (jammy-proposed/none) [14.0.0+ds-8] (no packageset)09:44
-queuebot:#ubuntu-release- New binary: python-unicodedata2 [s390x] (jammy-proposed/none) [14.0.0+ds-8] (no packageset)09:44
-queuebot:#ubuntu-release- New binary: python-unicodedata2 [ppc64el] (jammy-proposed/none) [14.0.0+ds-8] (no packageset)09:44
-queuebot:#ubuntu-release- New binary: python-unicodedata2 [arm64] (jammy-proposed/universe) [14.0.0+ds-8] (no packageset)09:46
-queuebot:#ubuntu-release- New binary: python-unicodedata2 [armhf] (jammy-proposed/universe) [14.0.0+ds-8] (no packageset)09:46
juliankrestarting lxd-armhf2, it has a broken lxd10:01
sil2100seb128: hm, this one failed even weirder? https://launchpadlibrarian.net/589592686/buildlog_ubuntu_jammy_amd64_ubuntu-canary_BUILDING.txt.gz10:02
julianksigh @ " A stop job is running for Service f?tion lxd.daemon (4min 48s / 10min)"10:02
seb128sil2100, no, that one is expected, that's https://bugs.launchpad.net/launchpad-buildd/+bug/1963706 I mentioned10:03
ubottuLaunchpad bug 1963706 in launchpad-buildd "Ubuntu Desktop Canary ISO failing to build since builders update" [High, New]10:03
seb128sil2100, the snap preseeding is failing since the buildd have been updated to focal, the snapd team think we might get out of loop devices, I was trying to get more info by making it call journalctl on the failure10:03
juliankgrub having a 30s timeout on cloud images is hilarious too10:03
sil2100juliank: ACK, let me skiptest it in this case. It's weird to me that it's still having problems...10:03
seb128sil2100, the ls /dev in the log also shows it has only 8 loop devices which I think helps10:04
seb128I'm going to go back to the launchpad team with that10:04
seb128sil2100, by 'helps' I mean to show that it has only that number, that's probably why snapd is failing10:04
juliankseb128: I think it's unable to run a migration-reference/0 and hence does not know the baseline10:07
sil2100Hint pushed10:10
-queuebot:#ubuntu-release- New binary: python-unicodedata2 [riscv64] (jammy-proposed/universe) [14.0.0+ds-8] (no packageset)10:10
juliankrabbitmq restarting, britney may lose some test requests10:26
juliankrather it thinks it queued them but didn't10:26
juliankIt was supposed to restart a while ago, but the restart service was running as wrong user :(10:26
juliankMär 08 10:25:54 juju-4d1272-prod-proposed-migration-8 maybe-restart-rabbitmq[751346]: connection_other: 1.6861 gb (57.04%)10:27
juliankwho doesn't love that10:27
julianknot sure what ` maybe-restart-rabbitmq[751346]: other_system: 18446744073.7914 gb (624023093593.84%)` is all about ...10:28
coreycbdoko: I maybe be hitting an issue with the new gcc-9-cross in focal. https://paste.ubuntu.com/p/7gqYM7QtKp/ it seems to be missing a closing bracket for one of the extern "C" {13:17
coreycbcontents of /usr/lib/gcc-cross/aarch64-linux-gnu/9/include/arm_acle.h: https://paste.ubuntu.com/p/W5PmcNqJY5/13:24
-queuebot:#ubuntu-release- New binary: webkit2gtk [amd64] (jammy-proposed/main) [2.35.90-1ubuntu1] (desktop-core, i386-whitelist)15:24
-queuebot:#ubuntu-release- New binary: webkit2gtk [ppc64el] (jammy-proposed/main) [2.35.90-1ubuntu1] (desktop-core, i386-whitelist)15:39
-queuebot:#ubuntu-release- New binary: webkit2gtk [s390x] (jammy-proposed/main) [2.35.90-1ubuntu1] (desktop-core, i386-whitelist)15:39
jochenspwith open3d working in proposed (thx mwhudson), can someone drop the old ppc64el binary so it can transition? (still no idea about the build failure)15:48
bdmurray^ AA ping15:54
seb128that's not how things work, there is a valid build on that arch in the release pocket, the way you get it to migrate is by fixing the build failure in the candidate15:57
seb128or if it can't be built there you remove the arch from the control and ask to remove the binary from release in a bug that documents why15:57
jochensp(in Debian I would just fill a removal bug for ftp..)15:58
jochenspalso it builds fine in Debian ppc64el so if someone can help with doing the necessary dance for Ubuntu I would appreciate15:59
bdmurrayThe build failure looks lto related16:01
jochenspyeah it seems to use custom CXXFLAGS (like -O3) I don't know where they come from16:02
jbichaUbuntu's ppc64el uses -O3; it's the only Ubuntu release architecture to do that16:04
vorlonseb128: fyi the "flaky error" is whenever the build lands on the unlucky cloud region (lcy02)16:05
seb128vorlon, ah, thanks16:05
jochenspjbicha: good to know, are there any other flags (LTO?) custom for ppc64el?16:06
jbicha-O3 is the only thing special about ppc64el I know of16:07
vorlonright, LTO is used across all our 64-bit archs, but there can be arch-specific implementation bugs16:08
jochenspyeah, we worked around LTO in build2 but it still FTBFS on ppc64el, that's why I wonder (and I don't think anyone uses open3d on ppc64el and there are no rdeps so dropping it seams easy)16:09
jochenspseb128: where should the bug go? (given that open3d builds fine in Debian)16:23
seb128jochensp, Ubuntu uses launchpad so on https://bugs.launchpad.net/ubuntu/+source/open3d/+filebug16:24
seb128jochensp, there is https://bugs.launchpad.net/ubuntu/+source/open3d/+bug/1963556 but I don't know if that's the same issue16:24
ubottuLaunchpad bug 1963556 in open3d (Ubuntu) "Open3D segfaults when compiled with LTO" [Undecided, Confirmed]16:24
jochensp(that's by me) no, that one is fixed with build216:25
jochenspfilled: https://bugs.launchpad.net/ubuntu/+source/open3d/+bug/196415416:25
ubottuLaunchpad bug 1964154 in open3d (Ubuntu) "Fails to build on ppc64el due custom compiler flags" [Undecided, New]16:25
jochenspcan someone upload a build2 with ppc64el removed from the archs? (not sure I'm allowed to upload to the queue)16:26
vorlonthat's not what we would do here; we would remove the previous open3d binaries from the archive, no source changes or reupload required16:28
jochenspthat would be great (and was my initial request)16:30
vorlonas open3d has no reverse-depends, that's probably fine, though on the Canonical side we are generally trying to maintain coverage equal to Debian so I'll at least have a cursory look16:30
vorlonthis looks like a candidate for a source upload that just sets DEB_BUILD_MAINT_OPTIONS=optimize=-lto on ppc64el16:31
jochenspvorlon: it is in the lto-disabled-list already (but maybe still worth a try)16:31
vorlonah true, I don't see any of the lto commandline args passed to the compiler16:32
vorlonok so the toolchain is broken, has any bug been opened on gcc for this?16:33
jochenspI'm not aware of a bug for that (I assumed different compiler flags till now)16:33
vorlonanyway, binary removal here seems entirely appropriate16:33
coreycbbdmurray: hello, if you get a chance I'd like to see if we can get the impish changes reviewed for #1960636. also I have a python-glance-store upload that needs rejecting in the impish queue.16:35
-queuebot:#ubuntu-release- Unapproved: rejected python-glance-store [source] (impish-proposed) [3.0.0-0ubuntu1]16:37
bdmurrayvorlon: Do you need anything more for bug 1964152?16:37
ubottuBug 1964152 in tasksel (Ubuntu Jammy) "removal request for tasksel" [Undecided, Confirmed] https://launchpad.net/bugs/196415216:37
-queuebot:#ubuntu-release- Unapproved: accepted vitrage [source] (impish-proposed) [7.5.0-0ubuntu2]17:21
-queuebot:#ubuntu-release- Unapproved: accepted networking-baremetal [source] (impish-proposed) [5.0.0-0ubuntu2]17:24
-queuebot:#ubuntu-release- Unapproved: accepted glance [source] (impish-proposed) [2:23.0.0-0ubuntu2]17:26
-queuebot:#ubuntu-release- Unapproved: accepted aodh [source] (impish-proposed) [1:13.0.0-0ubuntu2]17:28
-queuebot:#ubuntu-release- Unapproved: accepted barbican [source] (impish-proposed) [2:13.0.0-0ubuntu1.1]17:31
vorlonbdmurray: you should output of reverse-depends -a source but not reverse-depends without -a source?17:43
-queuebot:#ubuntu-release- Unapproved: accepted cinder [source] (impish-proposed) [2:19.0.0-0ubuntu3]17:43
vorlonbdmurray: also given that it's tasksel, worth checking if it's seeded anywhere... which it is (ubuntustudio)17:43
* Eickmeyer looks17:44
bdmurrayvorlon: ack17:45
Eickmeyervorlon, bdmurray: That means something is pulling it in. Any clue which package, or do I need to investigate?17:46
bdmurrayEickmeyer: ubiquity used to depend on it17:46
Eickmeyerbdmurray: We don't use ubiquity as of 20.10.17:46
vorlonEickmeyer: multimedia-tasks depends on it17:47
-queuebot:#ubuntu-release- Unapproved: accepted designate [source] (impish-proposed) [1:13.0.0-0ubuntu2]17:47
vorlonwhich is a dep of multimedia-puredata17:47
vorlonanyway, it appears there is definitely some revdep work to be done on tasksel before it's fit for removal17:48
bdmurrayvorlon: yeah, I see that now thanks. It can move to universe in the meantime though.17:48
EickmeyerWhich is a dep of puredata.17:49
EickmeyerActually, it's a suggests, not a dep.17:50
-queuebot:#ubuntu-release- New source: onetbb (jammy-proposed/primary) [2021.5.0-7ubuntu2]17:52
-queuebot:#ubuntu-release- New: accepted onetbb [source] (jammy-proposed) [2021.5.0-7ubuntu2]17:54
-queuebot:#ubuntu-release- New: accepted python-unicodedata2 [arm64] (jammy-proposed) [14.0.0+ds-8]17:54
-queuebot:#ubuntu-release- New: accepted python-unicodedata2 [ppc64el] (jammy-proposed) [14.0.0+ds-8]17:54
-queuebot:#ubuntu-release- New: accepted python-unicodedata2 [s390x] (jammy-proposed) [14.0.0+ds-8]17:54
-queuebot:#ubuntu-release- New: accepted webkit2gtk [ppc64el] (jammy-proposed) [2.35.90-1ubuntu1]17:54
-queuebot:#ubuntu-release- New: accepted python-unicodedata2 [amd64] (jammy-proposed) [14.0.0+ds-8]17:54
-queuebot:#ubuntu-release- New: accepted python-unicodedata2 [riscv64] (jammy-proposed) [14.0.0+ds-8]17:54
-queuebot:#ubuntu-release- New: accepted webkit2gtk [s390x] (jammy-proposed) [2.35.90-1ubuntu1]17:54
-queuebot:#ubuntu-release- New: accepted python-unicodedata2 [armhf] (jammy-proposed) [14.0.0+ds-8]17:54
-queuebot:#ubuntu-release- New: accepted webkit2gtk [amd64] (jammy-proposed) [2.35.90-1ubuntu1]17:54
-queuebot:#ubuntu-release- New binary: onetbb [i386] (jammy-proposed/universe) [2021.5.0-7ubuntu2] (i386-whitelist)18:09
-queuebot:#ubuntu-release- New: accepted onetbb [i386] (jammy-proposed) [2021.5.0-7ubuntu2]18:09
ahasenackhi release team, is this the live jammy release notes document? https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/2466818:29
ahasenacki.e., can I start adding stuff there without fear of it being lost once the real release notes are published?18:29
ahasenackI wanted to highlight a change from focal, which is udp nfs mounts are disabled (since groovy), and that caught me (and one other person at least) by surprise: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964093/comments/518:30
ubottuLaunchpad bug 1964093 in linux (Ubuntu) "nfsver=3,udp not working anymore" [Undecided, Confirmed]18:30
ahasenack(and for a moment I thought it was my nfs-utils version bump that caused it)18:31
bdmurrayahasenack: It is18:31
bdmurrayahasenack: and thank you for thinking about the release notes!18:31
ahasenackcheers :)18:32
Eickmeyerubuntu-archive: Still looking for a review for show-in-file-manager to resolve a Python 3.10 compatibility issue with rapid-photo-downloader.18:35
EickmeyerConvoluted, I know, but it's related to a new version of r-p-d.18:35
ahasenackok, noted down, maybe someone can make the text better, but the most important bit is there18:35
=== chiluk_ is now known as chiluk
-queuebot:#ubuntu-release- Unapproved: accepted postgresql-13 [source] (impish-proposed) [13.6-0ubuntu0.21.10.1]19:18
vorlonso why has a no-change rebuild of python-leidenalg incorrectly dropped the dependency on python3-igraph?20:13
-queuebot:#ubuntu-release- Unapproved: rejected glibc [source] (focal-proposed) [2.31-0ubuntu9.6]20:29
LocutusOfBorgI: dh_python3 pydist:292: Cannot find package that provides python_igraph. Please add package that provides it to Build-Depends or add "python_igraph python3-igraph" line to debian/py3dist-overrides or add proper dependency to Depends by hand and ignore this info.20:33
vorlonLocutusOfBorg: ok but python3-igraph is a build-dep, so what is the actual fix here?20:36
-queuebot:#ubuntu-release- Unapproved: accepted ovn [source] (focal-proposed) [20.03.2-0ubuntu0.20.04.3]20:37
LocutusOfBorgI blame dh_python20:39
LocutusOfBorgbut I'm checking debian build with newer python3-igraph20:40
LocutusOfBorgtest build might give some hint20:40
LocutusOfBorgyeah, it fails in Debian too20:42
seb128vorlon, since when deleting binaries on $arch is an appropriate solution to let things migrated that started failing to build? :/20:46
vorlonseb128: in reference to open3d?20:52
seb128vorlon, yes20:52
LocutusOfBorgits science team, do we care? :)20:52
vorlonseb128: reverse-depends says it's a leaf package; and the arch-specific regression is a toolchain bug.  I don't see a reason to hold it in -proposed, am I missing something?20:52
vorlonseb128: in *most* cases where we see a per-arch Ubuntu build failure but not a Debian failure I would hold it because we don't want to regress in Debian, but I think this case is special because it's a toolchain issue20:53
seb128vorlon, release team in the past always pushed on overwritting test results or $stack issues as it removes the visibility on the issue and lower the pressure to get it fixed at the right place20:53
vorlonseb128: I opened a bug task on gcc-11 which is the right place for thi20:54
seb128vorlon, also it seems highly inconsistent with your position on wanting to kick adsys out of the release pocket because tests were failing on one arch when the package is also Ubuntu specific and a leaf package20:54
vorlonseb128: adsys needed to get out of the way so the major language transitions could go through.  It was not clear to me at the time that adsys had a pending MIR (that's not one of the things I would ordinarily check) and that as a result it was a package of core interest20:55
vorlonso my policy there is to not regress test coverage, and the way to do that without holding up python3+perl indefinitely (since the longer it's blocked the more tangled it gets) was to demote the leaf package20:56
seb128vorlon, I was not speaking about kicking it out for letting python-default migrate, but after the migration was done when I removed the block tag you asked why we were letting a package with a failing test back in release20:56
seb128I mean I can understand the position than we don't want package broken in the release pocket20:57
seb128but then I struggle to understand why it's ok for one universe package and not another20:57
vorlonseb128: in general I think non-existent packages are better than broken packages20:57
vorlonseb128: but I also found your argument about adsys sufficiently persuasive that I didn't chase it further :)20:58
seb128sorry I didn't mean to make an argument around adsys20:58
seb128I was just genuinely surprised that we considered ok to delete the build on one arch to let a package update migrate when the new version is failing to build20:59
vorlonyes; in most cases I look for whether Debian ftpmasters have also agreed to remove the architecture support before I do so20:59
seb128maybe I was dealing more with L_aney for such things in the past and his position is slightly different from yours and just never noticed20:59
vorlonin fact I took that position over the weekend21:00
seb128vorlon, going back to the earlier topic of the ISO build failing when landing on lcy02, do you know if that is tracked by a RT or something? the desktop ISO has been failing for 3 days in a row on amd64, we might be unlucky but still sounds like it's happening often enough at this point that it would be worth getting resolved21:06
vorlonseb128: I'm afraid I don't know whether it's in an RT; cjwatson has been tracking it from the LP side, and jchittum was the first victim with the cloud images21:07
seb128cjwatson, jchittum, is that worth reporting a bug or filing a RT is that actively being worked on at this point?21:08
seb128vorlon, thx21:08
jchittumseb128: Is it failing early from trying to reach "people.canonical.com"?21:14
jchittumor is it failing from something related to loop devices?21:14
jchittumi'm reading back, sorry, bit distracted21:14
jchittumthere is an RT related to failed metadata services related to lcy0221:15
vorlonjchittum: that's the one21:17
vorlonit breaks ISO builds also21:17
jchittumah, we have an RT and an SF case now21:18
jchittumso it's escalated to "production" stuff but still no resolution due to the metadate issue21:19
cjwatsonRight, it's in RT and has also been escalated to Bootstack who are the team who can actually do something about it21:31
cjwatsonvorlon,seb128: https://portal.admin.canonical.com/C136237 and https://canonical.my.salesforce.com/5004K00000E8Ncg (with varying degrees of visibility on both of those)21:32
cjwatson(I can't even see the latter although I'm CCed on it)21:32
cjwatsonIt's not necessary to report more bugs/RTs21:33
jchittumI will say that this is going to cause releasing images for the current set of CVEs to be painful21:43
jchittumGonna be a lot of retrying builds21:43
seb128cjwatson, thanks22:35
* RAOF idly wishes that upstreams would produce deliberate tarballs didn't include .github detritus.23:50

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