[00:35] -queuebot:#ubuntu-release- New binary: rails [amd64] (groovy-proposed/universe) [2:6.0.3.2+dfsg-3] (no packageset) === s8321414_ is now known as s8321414 === s8321414_ is now known as s8321414 [05:16] -queuebot:#ubuntu-release- New binary: rails [amd64] (groovy-proposed/universe) [2:6.0.3.2+dfsg-4] (no packageset) [05:20] -queuebot:#ubuntu-release- New binary: haskell-blogliterately [amd64] (groovy-proposed/universe) [0.8.7-1] (no packageset) [05:34] -queuebot:#ubuntu-release- New binary: haskell-blogliterately [ppc64el] (groovy-proposed/universe) [0.8.7-1] (no packageset) [05:58] -queuebot:#ubuntu-release- New binary: haskell-blogliterately [arm64] (groovy-proposed/universe) [0.8.7-1] (no packageset) [06:04] -queuebot:#ubuntu-release- New binary: haskell-blogliterately [armhf] (groovy-proposed/universe) [0.8.7-1] (no packageset) [06:51] -queuebot:#ubuntu-release- New binary: haskell-blogliterately [s390x] (groovy-proposed/universe) [0.8.7-1] (no packageset) [07:23] enyc, likely #ubuntu-x [07:46] jibel: hey! On the isotracker I see reports for Ubuntu Desktop .1 regarding the font viewer crashing on the live session [07:46] Did you see anything like that? [07:52] sil2100, I'm currently looking at the issue [07:53] it's old crashes though [07:53] without much info [07:56] indeed it crashes [07:56] in live session only [07:57] Ok, if we had that before then I'm not as worried [07:57] Can't think of a strong usecase for checking fonts on the live session [07:58] I get bug https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1861961 [07:58] Ubuntu bug 1861961 in gnome-font-viewer (Ubuntu) "gnome-font-viewer crashed with SIGTRAP in _XEventsQueued() from XPending() from gdk_event_source_check() from g_main_context_check() from g_main_context_iterate() from g_main_context_iteration()" [Undecided,Confirmed] [07:59] could someone kill the frameworkintegration ppa autotests currently running? I can now see where they are hanging, which was the point [08:00] sil2100, and not a regression since the release [08:04] -queuebot:#ubuntu-release- New binary: haskell-blogliterately [riscv64] (groovy-proposed/universe) [0.8.7-1] (no packageset) [08:25] xnox: argh, d-i on s390x for bionic FTBFS [08:31] apw: thakyou for pointer, put note thete too [08:32] apw: its ' bit of a pain when unclear what issue(s) may be or even what packages to report [08:32] apw: i guess i could test 19.10 live iso [08:32] but still, if not xorg, not xorg video drivers, not radeon-firmware, not kernel ............ [08:33] gtk/associated? etc [08:33] enyc, yep these are tricky to diagnose [08:33] apw: I was hoping somebody would joump on or at least give me a $clue [08:34] apw: i've ended up pci-extending and physically moving cards and making space to put in an actual video-card and bypass problem that way.................... [08:34] enyc, the right place for screen corruption is ubuntu-x, they will be able to split kernel/mesa/X [08:34] apw: but STILL i'd be happy to help testing changes that might make ati RS480 work [08:34] ok! === pieq__ is now known as pieq [08:40] xnox: ok, I see you have noticed and pushed the fix for it, duh [08:40] * sil2100 could have checked the queue before digging into this [08:40] * sil2100 throws away his change and accepts xnox's [08:40] xnox: thanks! ;) [08:43] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (bionic-proposed) [20101020ubuntu543.17] [08:51] what is britney complaining about wrt the udebs here? https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#multipath-tools [08:52] afaict the udebs it's talking about exist [08:52] those messages suck [08:53] but, component-mismatches? [08:53] i don't think so? [08:54] but maybe [08:54] oh yes [08:54] https://launchpad.net/ubuntu/groovy/amd64/liburcu6-udeb/0.12.1-1 is in universe [08:54] how did that happen [08:56] and why did it not happen to the multipath-tools udebs? [08:56] why doesn't rmadison work on multpath-udeb [08:56] such knowledge being expressed here [08:58] https://launchpad.net/ubuntu/groovy/amd64/multipath-udeb/0.8.4-1ubuntu1 <- sez "main" [08:59] nod [08:59] doko: ^- what made you demote liburcu6-udeb? component-mismatches or? [09:00] http://archive.ubuntu.com/ubuntu/dists/groovy-proposed/main/debian-installer/binary-amd64/Packages.gz is pretty small now but not quite empty [09:00] er s/-proposed// [09:00] Laney: how can you tell it was doko? :) [09:01] mwhudson: if you back up one component from the URL you gave, the smoking gun is there [09:02] Laney: ah! [09:03] that's one of the nice little hidden corners of LP it's good to know about sometimes [09:04] Laney: yes, compomnent mismatches in both proposed and release [09:04] yeah i think i may have seen that page and then failed to find it again [09:05] so why did these appear in component mismatches? [09:05] I still have the list of demoted packages... so I could revert those [09:06] yeah that's a bit strange [09:06] I guess if you do that, and it comes back on c-m we can debug the report [09:06] i don't know what the long term plan is, we don't care about udebs at all for groovy afaik [09:07] but what Laney suggests makes sense [09:07] maybe all d-i stuff should be in universe, I dunno [09:07] whatever it is should be done in a considered way rather than in response here imo [09:07] yep [09:08] now does anyone want to talk about udisks2's autopkgtests or should i just bounce on retry until it works [09:09] file an rls-gg-incoming bug about that, I think desktop should schedule some work on thoes [09:09] * mwhudson goes for the latter [09:09] ok [09:10] ah there was https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1888062 already, i tagged it [09:10] Ubuntu bug 1888062 in udisks2 (Ubuntu) "autopkgtest became very flaky in Groovy" [High,Confirmed] [09:10] 🕶 [09:11] looks like there is an upstream patch and everything, i guess i could try applying it [09:19] doko: so will you revert your demotions? [09:19] migrating s390-tools/2.12.0-0ubuntu6/s390x to testing makes ubuntu-server/1.452/s390x uninstallable [09:19] * mwhudson squints [09:21] mwhudson, there is no much point tagging that bug [09:21] seb128: yeah i guess not [09:21] it's already handled with a fix commited upstream [09:21] seb128: i'm testing the upstream patch now [09:21] thx [09:22] disagree, that tagging was like 2 weeks ago, it would have made us look at it tomorrow in the meeting [09:22] s/tagging/comment/ [09:23] mwhudson: promoted again [09:23] Doing some Bionic->Focal upgrades I found https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640 is still relevant. Workaround seems to purge timidity-daemon. That might be something to mention in release notes. [09:23] Ubuntu bug 1793640 in timidity (Ubuntu) "Pulseaudio fails to detect sound card, while timidity is installed" [High,Triaged] [09:26] doko: thanks [09:29] Laney, well it's tagged so we are going to look at it :-) But I've a feeling that it will end up in us agreeing to nominate and me taking assignment since I handle udisk and I upstreamed the report that did lead to the commit that needs backporting, which is basically a no change from where we are today (I was just waiting for an upstream release to get it uploaded) [09:33] seb128: okey dokey, just take the assignment now :p [09:33] Laney, done, I should have done that when I triaged it :-) [09:39] * Laney eyes proposed-migration/xenial [09:39] why crasheth you [09:42] seb128: oh, i just uploaded the patch... [09:43] mwhudson, ah, even better [09:43] thanks! [09:43] seb128: np, +1 maint ftw [09:43] :-) [09:43] * mwhudson stops for now, let's see what britney thinks of the re-componented udebs in the morning [10:24] still puzzled why gcc-9 tries to promote ... [10:26] mwhudson: s390-tools-signed needs an upload [10:28] xnox: ah [10:28] xnox: does that require special skills? [10:46] vorlon, do you have a log about how retry-autopkgtest-regressions failing with snap-triggered tests? [10:50] mwhudson: just carefully running debian/rules clean, and ensuring version numbers match. [10:52] xnox: as i'm sure you know that was an attempt to trick you into doing it :) [10:52] i will go to bed and see if i need to do it in the morning :-) [10:53] ahahhahahahhahahhahaa [10:53] Laney: hey! Could you again re-run the snapshotting command for focal as you did last week on snakefruit? ;) [10:53] Laney: since I remembered now that we just re-spun the images, so the snapshot needs to be re-run [10:54] Laney: you can just re-run it as is, no need to delete anything [10:54] sil2100: ok! [10:54] lies [10:54] Laney: huge thanks! :) [10:54] I do need to delete it [10:54] You do? [10:54] Ouchy [10:54] OSError File exists [10:54] feel free to fix the tool to avoid that ;-) [10:54] Oh well, I guess I wouldn't know since I have no access there! [10:55] ;) [11:09] sil2100, if there will be a new respin u-u is ready for release [11:11] sil2100, i have a not too special lxc container where u-u is running for 45 minutes due to not upgradable packages and fixing LP: #1877769 helps with that [11:11] Launchpad bug 1877769 in unattended-upgrades (Ubuntu Focal) "[SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU" [Undecided,Fix committed] https://launchpad.net/bugs/1877769 [11:17] -queuebot:#ubuntu-release- New binary: fvwm-crystal [amd64] (groovy-proposed/universe) [3.4.1+dfsg-2] (no packageset) [11:22] rbalint_: I hope no respin will be required [11:25] vorlon: hey! Regarding shim-signed for bionic - I guess I'd be okay with accepting the new one if we'd be able to verify it in the nearest days [11:28] vorlon: I see that the new upload includes a fix on top of the existing changes, so for clarity I'd like it to include all the bugs so far in .changes [11:28] Let me re-push [11:30] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.5 => 1.37~18.04.6] (core) [11:40] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (bionic-proposed) [1.37~18.04.6] [11:42] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (bionic-proposed) [1.37~18.04.6] === alan_g_ is now known as alan_g [13:36] Laney: FYI, for pkg-kde-tools & lintian, looks like it just needs the fixed lintian now in proposed to avoid the hangs [14:22] sil2100, hello, would you have time to process libreoffice 1:6.4.5-0ubuntu0.20.04.1 waiting in the focal/queue? [14:23] RikMills: cool [14:27] Laney: PS. Nearly all the KDE build-needed tests should now be gone/going away, anyway \o/ [14:28] yesssssss [14:28] sorry that took so long.... [14:34] apw, could you put your generous AA hat on and let me know whether bug 1843742 looks to be reasonably set up? [14:34] bug 1843742 in irda-utils (Ubuntu) "irda-utils ftbfs in eoan" [High,Confirmed] https://launchpad.net/bugs/1843742 [14:41] rbalint_: backtrace: https://paste.ubuntu.com/p/Kcdj9j7vBm/ [14:42] sil2100: shim-signed should be a pretty quick verification. .changes, yes - do you need me to do anything there or can you reupload it with the correct -v? [14:46] rbalint_: vorlon: I think I fixed that one earlier, sorry for stealing the work (didn't notice the previous ping) [14:47] Laney: ah cheer [14:47] s [14:47] hello ubuntu-archive, could someone please take a look at this? https://code.launchpad.net/~ahasenack/ubuntu-seeds/+git/ubuntu-seeds/+merge/388428 It's to promote realmd and adcli to main in focal, after it was approved in groovy. The versions are identical in focal and groovy, and security gave a +1 already [14:47] ahasenack: seed changes don't require ubuntu-archive signoff [14:48] so don't block on us :) [14:48] correct, but I wouldn't want to change a focal seed befora an AA agrees to promote the package there [14:48] ahasenack: ah right, wasn't obvious from the url, sorry [14:48] and isn't there also an imminent .1 release for focal? I also wouldn't want to break that [14:49] ahasenack: it's only a supported seed so no point release impact. +1 for the change, go for it and I can promote [14:49] thank you! [14:52] sil2100: ah, you already did that hours ago, cheers ;) [15:03] Laney, thanks! vorlon thanks, i have not seen this failure yet [15:09] ricotz: let me take a look after the meetings! [15:09] jibel: hey! So I see you have looked at LP: #1890137, did you check if this affects only Kubuntu or other flavors? [15:10] Launchpad bug 1890137 in ubiquity (Ubuntu) "ubiquity crashes when "release notes" selected" [Medium,Confirmed] https://launchpad.net/bugs/1890137 [15:11] sil2100, ty [15:12] sil2100, hey, chromium-browser/focal sounds like another SRU worth accepting now if possible (and trivial only changelog update), it's to make sure focal_version > bionic_security, otherwise .1 upgraders might not get the snap [15:15] seb128: thanks for the info, on it as well o/ [15:16] thanks! [15:16] bdmurray: hey! Did you test that better fix for the meta package removal in u-r-u? Is it ready for releasing? [15:16] s/releasing/reviewing [15:21] vorlon: merged [15:22] sil2100: I did test it and uploaded it to groovy, haven't done it for Focal yet. [15:23] bdmurray: if you could prep a focal upload that would be sweet, since I guess it'd be nice to fast-track it before we enable upgrades [15:24] sil2100: I was also working on this on Friday and thought it'd be good to bundle with the linux meta package removal fix [15:24] https://code.launchpad.net/~brian-murray/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/388513 [15:25] sil2100, it doesn't happen on Ubuntu [15:28] Let me take a look then [15:28] sil2100, I'm downloading kubuntu [15:29] sil2100: I haven't found many duplicates of the python-dbg issue so it may be able to wait [15:36] sil2100, so on kubuntu, the link does nothing because xdg-open uses kde-open which doesn't exist but the installer doesn't crash [15:53] jibel: that's good news then [15:55] i'll file a bug for the wrong association [16:34] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (focal-proposed/main) [1:20.04.23 => 1:20.04.24] (core) [16:35] ^sil2100 [16:36] I'm writing the test case now [16:56] sil2100, bug 1890173 it's specific to kubuntu [16:56] bug 1890173 in ubiquity (Ubuntu) "[kubuntu] "Release notes" link doesn't open" [Undecided,New] https://launchpad.net/bugs/1890173 [16:57] bdmurray: \o/ [17:11] ahasenack: and packages promoted in -updates [17:15] -queuebot:#ubuntu-release- New binary: aseba-plugin-blockly [amd64] (groovy-proposed/multiverse) [20180211+git-3] (no packageset) [17:15] vorlon: thank you [17:20] -queuebot:#ubuntu-release- New binary: galax [s390x] (groovy-proposed/universe) [1.1-16] (no packageset) [17:26] hopefully fixed p-m/xenial without breaking anything else ... [17:26] quite a delicate area of the code though [17:28] -queuebot:#ubuntu-release- New binary: galax [ppc64el] (groovy-proposed/universe) [1.1-16] (no packageset) [17:28] why does c-m want to promote gcc-9? nothing in https://people.canonical.com/~ubuntu-archive/component-mismatches.svg or https://people.canonical.com/~ubuntu-archive/component-mismatches.html explains [17:31] -queuebot:#ubuntu-release- New binary: galax [amd64] (groovy-proposed/universe) [1.1-16] (no packageset) [17:42] -queuebot:#ubuntu-release- New binary: galax [armhf] (groovy-proposed/universe) [1.1-16] (no packageset) [17:44] -queuebot:#ubuntu-release- New binary: galax [arm64] (groovy-proposed/universe) [1.1-16] (no packageset) [17:45] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [source] (focal-proposed) [1:6.4.5-0ubuntu0.20.04.1] [17:45] ricotz: hmmm, I wanted to accept libreoffice, but I got this error: "libreoffice_6.4.5.orig-tarballs.tar.xz is already published in archive for focal with a different SHA1 hash (dd676f6a65ab6910b90a944be59e17cb1b34b127 != 79767488a539577fb3a5db828c9245a0fbd0491c)" [17:46] ricotz: how did that happen? I would expect it to get rejected on queue upload [17:46] vorlon: ^ do you know? [17:47] It's weird since now libreoffice is gone from the queue, but I wonder if it actually got accepted [17:48] sil2100, hmm, no idea :(, I didn't create these packages. hellsworth did [17:49] sil2100, I can prepare fixed ones though [17:50] -queuebot:#ubuntu-release- Unapproved: accepted chromium-browser [source] (focal-proposed) [84.0.4147.89-0ubuntu0.20.04.1] [17:52] ricotz: I think it might be good to start preparing new ones (and making sure that the same orig tarballs are used as available in the archive) [17:52] Ah, could it be that this was uploaded first to the queue and only afterwards to groovy? [17:52] Anyway, I see it as accepted, but it doesn't appear anywhere, so probably LP rejected it [17:53] sil2100, sorry, I don't know, hellsworth is quite new to the packaging process [17:57] sil2100, https://people.ubuntu.com/~ricotz/libreoffice/ [17:59] bdmurray: hey! So regarding the u-r-u SRU: I'd like to make sure about one thing as this bit us multiple times already in the past [18:00] bdmurray: do you know if at any moment of time the tryMarkObsoleteForRemoval() function of MyCache in DistUpgradeCache is being used by update-manager? [18:01] bdmurray: since you know how stupid this is - update-manager uses MyCache from u-r-u but doesn't call it's constructor, so I just want to make sure that update-manager won't suddenly start crashing because of self.linux_metapackage being undefined [18:01] (as it's defined in the u-r-u constructor, not the update-manager MyCache-derivative) [18:12] sil2100: I'll have a look [18:13] bdmurray: thanks! [18:23] sil2100: that's a check that doesn't happen until after the unapproved stage [18:39] hi release team, do we have a release schedule for groovy? https://wiki.ubuntu.com/GroovyGorilla/ReleaseSchedule is empty [18:39] oh [18:39] it magically appeared [18:39] it redirected to discourse, oh [18:41] sil2100, is the repackaged libreoffice sufficient? [19:30] -queuebot:#ubuntu-release- New binary: galax [riscv64] (groovy-proposed/universe) [1.1-16] (no packageset) [19:45] sil2100: update-manager does not use "tryMarkObsoleteForRemoval" additionally I ran update-manger with the new focal u-r-u packages installed and it worked without issue [19:51] bdmurray: excellent, thanks for checking! [19:56] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (focal-proposed) [1:20.04.24] [21:09] vorlon / ubuntu-archive: can you repromote libargon2-1-udeb to main please? [21:09] (see https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#cryptsetup) [21:21] vorlon: lintian in proposed newly depends on lzip, which has no i386 build. can that be sorted? [22:03] mwhudson: done the other way, cryptsetup udebs demoted (since no longer used). c-m output suggests something in main in -proposed still depends on them but we'll sort that out anon [22:04] RikMills: lintian is arch: all, so why does it need to be installable on i386? [22:05] RikMills: (lintian is not in the build-dep closure for i386, so I believe the answer is it doesn't need to be) [22:05] when pkg-kde-tools needs lintian for i386 builds [22:05] vorlon: can we stop publishing udebs at some stage? [22:05] mwhudson: possibly [22:06] RikMills: ah, sounds like a bug in the germinate handling, blech [22:07] RikMills: otoh why is lintian being used at build-time? [22:07] it would be more convenient for me to fix this misfeature of pkg-kde-tools instead :) [22:08] vorlon: pkg-kde-tools uses it for kubuntu QA and CI scripts/pages [22:09] hmph [22:09] :) [22:09] ok I'll dig into it [22:10] thanks :) [22:13] vorlon: oh, and currently pkg-kde-tools does not depend on lintian, due to a separate bug with the lintian in -release, but we do want the depend back once fixed lintian in proposed migrates [22:14] * RikMills thinks lintian is out to get me this week! [23:14] -queuebot:#ubuntu-release- New binary: album-data [amd64] (groovy-proposed/multiverse) [4.05-7.1] (no packageset) [23:14] hmm how do we feel about removing src:frr i wonder