[00:09] <sil2100> bdmurray, vorlon: mfo is investigating an autopkgtest failure for a casper upload that's in focal-proposed - in case he figures out the situation there, I would like to get it included into .5
[00:09] <vorlon> ack
[00:09] <sil2100> So if he reaches out to you with some sane explaination, feel free to release it to -updates (I think the main part got already verified?)
[00:09]  * vorlon nods
[00:10] <sil2100> Thank you!
[00:10] <sil2100> o/
[01:09] -queuebot:#ubuntu-release- Unapproved: accepted kdesu [source] (jammy-proposed) [5.92.0-0ubuntu1.1]
[01:11] <RAOF> jbicha: SRU ping, re https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1976623/comments/4 , if you happen to be around.
[01:15] -queuebot:#ubuntu-release- Unapproved: accepted osinfo-db [source] (jammy-proposed) [0.20220214-1ubuntu2.1]
[01:24] <mfo> vorlon, hey o/ this should fix autopkgtest failure for casper in focal-proposed.
[01:24] <mfo> https://code.launchpad.net/~mfo/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/429182
[01:25] <mfo> vorlon, i've put details in the commit msg, happy to provide more info if needed.
[01:38] <mfo> bdmurray, ah, łukasz also mentioned to let you know about this ^ earlier.
[01:48]  * mfo EOD o/
[02:00] -queuebot:#ubuntu-release- Unapproved: accepted cmake [source] (jammy-proposed) [3.22.1-1ubuntu1.22.04.1]
[02:16] <vorlon> mfo: merged and retriggered the test
[03:59] <LocutusOfBorg> vorlon, what if we run "top" or "iotop" and print the output during the build process?
[03:59] <LocutusOfBorg> and cat the file at the end of the build? (w.r.t. haskell)
[04:02] <LocutusOfBorg> we can do in "build_recipe" haskell-devscripts?
[04:19] -queuebot:#ubuntu-release- Unapproved: rejected xserver-xorg-video-amdgpu [source] (jammy-proposed) [22.0.0-1ubuntu0.1]
[04:51] <vorlon> LocutusOfBorg: I think it's unlikely this is going to tell us anything useful, I don't think system load explains ghc being slow when nothing else is
[04:51] <vorlon> oh hey look, haskell-gi-gtk ftbfs with a failure that doesn't occur on Debian https://launchpad.net/ubuntu/+source/haskell-gi-gtk/3.0.38-1/+build/23849534
[05:30] -queuebot:#ubuntu-release- Unapproved: accepted dmidecode [source] (jammy-proposed) [3.3-3ubuntu0.1]
[05:46] <LocutusOfBorg> vorlon, iotop might do? for disks and so on?
[05:56] <vorlon> LocutusOfBorg: disk slowness doesn't explain a ghc-specific slowdown?
[06:42] <tjaalton> RAOF: huh, no idea what happened with xxv-amdgpu, will upload a corrected one if you still have time
[06:45] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-amdgpu (jammy-proposed/main) [22.0.0-1build1 => 22.0.0-1ubuntu0.1] (desktop-core)
[07:03] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-amdgpu [source] (jammy-proposed) [22.0.0-1ubuntu0.1]
[07:03] <tjaalton> thanks!
[07:05] <tjaalton> oh, if a debdiff is applied twice for whatever the reason, d/patches/* get messed up
[07:12] <RAOF> Very!
[07:14] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Focal 20.04.5] has been updated (20220831)
[07:16] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Focal 20.04.5] has been updated (20220831)
[07:28] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Focal 20.04.5] has been updated (20220831)
[07:28] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Focal 20.04.5] has been updated (20220831)
[07:30] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Focal 20.04.5] has been updated (20220831)
[07:32] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Focal 20.04.5] has been updated (20220831)
[07:38] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Focal 20.04.5] has been updated (20220831)
[07:38] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Focal 20.04.5] has been updated (20220831)
[07:42] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Focal 20.04.5] has been updated (20220831)
[07:42] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Focal 20.04.5] has been updated (20220831)
[07:42] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Focal 20.04.5] has been updated (20220831)
[07:42] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Focal 20.04.5] has been updated (20220831)
[07:48] <LocutusOfBorg> vorlon, don't know :/
[08:17] -queuebot:#ubuntu-release- New source: systemd-hwe (jammy-proposed/primary) [249.11.1]
[08:18] -queuebot:#ubuntu-release- Unapproved: tzdata (jammy-proposed/main) [2022a-0ubuntu1 => 2022c-0ubuntu0.22.04.0] (core)
[08:22] -queuebot:#ubuntu-release- Unapproved: tzdata (focal-proposed/main) [2022a-0ubuntu0.20.04 => 2022c-0ubuntu0.20.04.0] (core)
[08:24] -queuebot:#ubuntu-release- Unapproved: tzdata (bionic-proposed/main) [2022a-0ubuntu0.18.04 => 2022c-0ubuntu0.18.04.0] (core)
[08:28] <LocutusOfBorg> tzdata is removing changelog.gz during build, and moment-timezone.js is needing it...
[08:29] <LocutusOfBorg> schopin, ^^ any idea? it seems to be removed from pkgbinarymangler strip
[08:29] <LocutusOfBorg> but I don't know how to prevent that
[08:29] <schopin> LocutusOfBorg: on kinetic, right?
[08:33] <LocutusOfBorg> yep
[08:33] <LocutusOfBorg> it does check the changelog, to see if the version is correct or something like that
[08:35] <schopin> I'm confused that changelog.gz exists in the first place, to be honest.
[08:38] <schopin> Maybe `dh_installchangelogs NEWS` used to rename its input to `changelog` but doesn't anymore?
[08:38] <LocutusOfBorg> NEWS file becomes changelog.gz
[08:38] <LocutusOfBorg> it does rename it
[08:38] <LocutusOfBorg> but pkgbinarymangler has something like if changelog.Debian.gz exist -> remove it, otherwise remove a changelog.gz
[08:39] <schopin> what the hell?
[08:39] <LocutusOfBorg> check "strip_debian_changelogs" in pkgbinarymangler
[08:39] -queuebot:#ubuntu-release- Unapproved: gnome-tweaks (jammy-proposed/universe) [42~beta-1ubuntu1 => 42~beta-1ubuntu2] (no packageset)
[08:40] <LocutusOfBorg> # Remove buildinfo files and upstream changelogs; take care to keep native changelogs
[08:40] <LocutusOfBorg> #
[08:40] <LocutusOfBorg> clean_upstream_changelogs()
[08:40] <LocutusOfBorg>     dch=usr/share/doc/$PKGNAME/changelog.Debian.gz
[08:40] <LocutusOfBorg>     if [ ! -e "$dch" ] && [ ! -h "$dch" ]; then
[08:40] <LocutusOfBorg>         dch=usr/share/doc/$PKGNAME/changelog.gz
[08:40] <LocutusOfBorg> so, basically we don't have the Debian changelog, and arbitrary we decide to remove the upstream renamed one...
[08:46] <schopin> This behavior dates back to 2010, apparently, and is to save space on CDs
[08:58] <LocutusOfBorg> yes, part of the delta that debhelper has
[08:59] <LocutusOfBorg> maybe we should stop calling it changelog.gz and call it NEWS.gz?
[08:59] <LocutusOfBorg>        debian/package.NEWS
[08:59] <LocutusOfBorg>            Automatically installed into usr/share/doc/package/ in the package build directory.
[08:59] <LocutusOfBorg> maybe calling it this way is fixing in a better and debian-upstreamable way?
[09:01] <schopin> Why do you need this file again?
[09:03] <schopin> (I have 407 NEWS.gz files on my current system so that's probably a good approach)
[09:04] <LocutusOfBorg>        -k, --keep
[09:04] <LocutusOfBorg>            Keep the original name of the upstream changelog. This will be accomplished by installing the upstream changelog as changelog, and making a symlink from that to the original name of the
[09:04] <LocutusOfBorg>            changelog file. This can be useful if the upstream changelog has an unusual name, or if other documentation in the package refers to the changelog file.
[09:04] <LocutusOfBorg> or just use -k flag
[09:05] <LocutusOfBorg> the purpose is moment-timezone.js doing this:
[09:05] <LocutusOfBorg>         zcat /usr/share/doc/tzdata/changelog.gz > temp/download/$(TZVER)/NEWS
[09:05] <LocutusOfBorg>         grunt data-meta:$(TZVER)
[09:08] <Ukikie> Niiiiiice going.
[09:09] <schopin> LocutusOfBorg: according to https://www.debian.org/doc/debian-policy/ch-docs.html#changelog-files-and-release-notes NEWS.gz is the way to go anyway.
[09:20] <schopin> LocutusOfBorg: can I leave it to you to drive this change?
[09:35] <doko> xnox: can #1987870 be closed now?
[09:46] <xnox> doko:  no, it must stay open as the block-proposed-kinetic on it is what will keep broken intel-iotg LRM in proposed and thus allow britney to migrate the new nvidia/kernels.
[09:46] <xnox> doko:  instead, intel-iotg LRM migrated straight back after you demoted it yesterday.
[09:46] <xnox> doko:  can you please demote it again, and keep the bug open?
[09:47] <xnox> https://launchpad.net/ubuntu/+source/linux-restricted-modules-intel-iotg/+publishinghistory
[09:48] <xnox> ./demote-to-proposed -d ubuntu -s kinetic -m "v5.19 kernel migration LP:#1987870" linux-restricted-modules-intel-iotg linux-restricted-signatures-intel-iotg
[09:48] <xnox> we can unsubscribe ubuntu-archive from those bugs, once demotion is done.
[09:50] <schopin> rbasak: Hi! Could you please have a look at the LP: #1986984 SRU for jammy, focal and bionic? TIA
[10:36] -queuebot:#ubuntu-release- Unapproved: speech-dispatcher (jammy-proposed/main) [0.11.1-1ubuntu1 => 0.11.1-1ubuntu2] (i386-whitelist, ubuntu-desktop)
[10:40] <LocutusOfBorg> schopin, doing
[10:45] <xnox> doko:  thank you !!!! =)
[11:18] -queuebot:#ubuntu-release- Unapproved: linux-firmware (jammy-proposed/main) [20220329.git681281e4-0ubuntu3.4 => 20220329.git681281e4-0ubuntu3.5] (core, kernel)
[13:15] <paride> sil2100, hey, test results for subiquity .5 submitted to the ISO tracker. I also did some desktop testing this time
[13:18] <xnox> kinetic v5.19 kernels should be migrating in britney cycle after this one, so in 90 minutes or so.
[13:32] <seb128> the daily desktop and canary livefs kinetic built failed yesterday and today on dns issues https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu
[13:32] <seb128> is that some sort of known infrastructure problem?
[13:32] <seb128> '  Temporary failure resolving 'ftpmaster.internal''
[13:34] <rs2009> luna_ did mention there being problems with the network in the Londen datacenter
[13:34] <rs2009> s/Londen/London/g
[13:36] <sil2100> paride: yaay!
[13:36] <sil2100> seb128: yeah, looks like an infra problem
[13:37] <sil2100> seb128: btw. let me add the PPA to the isotracker rebuilds now
[13:37] <sil2100> But let's make it temporary, I'd like to remove the PPA before the Beta milestone
[13:42] -queuebot:#ubuntu-release- New: accepted systemd-hwe [source] (jammy-proposed) [249.11.1]
[13:42] <seb128> sil2100, great, it gives me a bit of time to iterate and try to aim at no ppa by beta
[13:42] <seb128> sil2100, should the infra problem be reported to IS?
[13:43] <sil2100> seb128: hm, usually those are transient or related to ongoing outages. But if it still fails and there's no known outage, I'd report that then
[13:43] -queuebot:#ubuntu-release- New binary: systemd-hwe [amd64] (jammy-proposed/none) [249.11.1] (no packageset)
[13:48] <seb128> sil2100, it was yesterday and today, could kick a retry for kinetic/desktop/amd64 and canary?
[13:48] <sil2100> Wait wait! Let's in a moment test if the PPA will be used in the isotracker rebuild
[13:52] <sil2100> seb128: ok, triggered a rebuild via the tracker, looks like it has the right arguments in dry-run
[13:52] <sil2100> Let's see how the build looks
[13:56] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (jammy-proposed) [2022c-0ubuntu0.22.04.0]
[13:57] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (bionic-proposed) [2022c-0ubuntu0.18.04.0]
[13:57] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (focal-proposed) [2022c-0ubuntu0.20.04.0]
[14:01] <rbasak> sil2100: any reason to release ubuntu-advantage-tools in Xenial?
[14:02] <rbasak> sil2100: any reason *not* to release ubuntu-advantage-tools in Xenial?
[14:02] <sil2100> rbasak: hm hm, I don't think so, I simply wasn't sure if we still supposed to do that for xenial or not (I guess yes, but wasn't sure!)
[14:04] <rbasak> sil2100: thanks. I'll release then. Yes, we agreed that we would, but I think it's on me to document that somewhere :-/
[14:14] -queuebot:#ubuntu-release- New: accepted systemd-hwe [amd64] (jammy-proposed) [249.11.1]
[14:14] <rbasak> (FTR, as an exception of normal ESM policy for ubuntu-advantage-tools, since that package is the "gateway" to ESM itself.
[14:14] <rbasak> )
[14:29] <rbasak> sil2100: sorry, I forgot Focal was in freeze, and have just released some stuff.
[14:29] <rbasak> makedumpfile, deja-dup
[14:29] <sil2100> eeek
[14:29] <rbasak> I also accepted (not released) tzdata
[14:30] <sil2100> Ouch, deja-dup is seeded, so that's unfortunate. But I suppose if we need to respin we'd be respinning the flavors that have it seeded anyway
[14:30] <sil2100> (good thing I did the source image and snapshot earlier!)
[14:30] <rbasak> Again, sorry.
[14:31] <rbasak> I wonder if we need to add some protection to sru-release
[14:40] <xnox> v5.19 kernel migration partially failed; because we don't know what to do with 418-server nvidia; and missing 450-server nvidia lrms
[14:42] <blackboxsw> rbasak: if you have SRU vanguard review time. We've queued a cloud-init SRU upload in response to RAOF's review on Friday (needing to include a postinst script) and we've sync'd changes for two potential bug fixes found and fixed before our SRU unapproved upload was accepted https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1987318.
[15:24] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9 [sync] (jammy-proposed) [9.5.0-1ubuntu1~22.04]
[15:29] <sil2100> seb128: ok, canary failed again, but a different error
[15:30] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9-cross [sync] (jammy-proposed) [26ubuntu3.1]
[15:31] <rs2009> hey sil2100 and vorlon, I just sent an email to the TB mailing list that is awaiting mod approval. could you please take a look?
[15:32] <rbasak> I've a
[15:32] <rbasak> I've moderator-accepted that email
[15:33] <rs2009> ty :)
[15:35] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9-cross-ports [sync] (jammy-proposed) [24ubuntu1.1]
[15:42] <vorlon> ginggs: you retriggered ensmallen/arm64 a couple times against new armadillo; this autopkgtest failure isn't reproduced in Debian but looks like a real regression. had you dug any further?
[15:42] <vorlon> (armadillo blocks NBS removals)
[15:43] <ginggs> vorlon: ensmallen was removed from debian testing
[15:43] <bdmurray> sil2100: FYI I opened bug 1988209 the other day but don't think it is critical
[15:43] <ginggs> vorlon: debian bug $1010431
[15:43] <ginggs> debu bug #1010431 even
[15:44] <vorlon> ginggs: heh, but removed for a failing autopkgtest we don't care about (i386)
[15:44] <vorlon> ginggs: this test calls into armadillo, looks to me like this is an armadillo regression :/
[15:45] <vorlon> (both i386 and Ubuntu arm64)
[15:45]  * ginggs retries the tests in unstable
[15:45] <sil2100> bdmurray: huh, ok, that's interesting. Do you know how it looked on .4?
[15:49] <bdmurray> sil2100: installing it now
[16:06] <bdmurray> sil2100: its hard to say given that the nvidia driver wasn't installed with 20.04.4 and it didn't boot to a GUI desktop
[16:07] <ginggs> vorlon: ensmallen's test passed on arm64 in unstable, but i noticed it's a different version.  we have 2.19.0-1 in proposed that FTBFS on amd64
[16:31] <vorlon> ginggs: oh fun
[16:47] <vorlon> ginggs: ahaha the ensmallen build failure on amd64 is that exact test case, failing when rebuilt
[16:51] <vorlon> ginggs: I think that's enough of an argument for dropping ensmallen given that the test case says "Approx" anyway and this is inherently fuzzy
[17:49] <rs2009> vorlon: was wondering if these are the required variables that need to be set manually before building with livecd-rootfs: ARCH, SUBARCH, SUITE, PROPOSED, IMAGEFORMAT, LIVE_BUILD
[17:49] <tsimonq2> rs2009: All depends on how you're calling it.
[17:50] <tsimonq2> rs2009: Give me a minute and I can run through a local setup once more and get you some instructions.
[17:53] <rs2009> tsimonq2: thanks :) I added Ubuntu Unity to auto/config, built the livecd-rootfs package, installed it, copied /usr/share/livecd-rootfs/ and was going to run `lb config`, which seems to require these variables to be set (from checking auto/config)
[17:59] <tsimonq2> rs2009: Okay, here's a few things for you. First off, a few years back I wrote some documentation on how exactly Lubuntu's ISOs are built, you can find it here: https://phab.lubuntu.me/w/release-team/iso-building/ (if someone sees obsolete info there, ping me)
[17:59] <tsimonq2> https://launchpadlibrarian.net/621115109/buildlog_ubuntu_kinetic_amd64_lubuntu_BUILDING.txt.gz <- This is the latest Lubuntu Kinetic log. In here I see this line:
[18:00] <tsimonq2> [2022-08-31 16:41:01] lb_config noauto --mode ubuntu --distribution kinetic --iso-preparer livecd-rootfs --bootstrap-keyring ubuntu-keyring --binary-images none --memtest none --source false --build-with-chroot false --parent-mirror-bootstrap http://ftpmaster.internal/ubuntu/ --parent-archive-areas main restricted universe multiverse --apt-source-archives false --linux-flavours generic --initsystem none --bootloader none --checksums none
[18:00] <tsimonq2> --cache false
[18:01] <tsimonq2> That output is confusing as heck unless you have the source code up in another window, simply because you don't know under which context something is ran...
[18:02] <rs2009> ah, so should I run lb config directly, or just run auto/config after setting the vars (that's what I did just now)?
[18:03] <rs2009> tsimonq2: these are all the variables I'm currently setting before running auto/config: https://paste.ruds.io/ozivujujav.bash
[18:05] <tsimonq2> Double-checking
[18:07] <rs2009> just went through those logs, and yes, looks like lb config (auto/config)'s running the command you sent. I just set those variables and ran lb config, and didn't get any errors and it ran the same command
[18:07] <tsimonq2> So, I just cloned livecd-rootfs locally, cd into live-build, and ran lb config, obviously it's missing some env vars so the project tasks can be set
[18:08] <tsimonq2> Let me concur with what you have so far - sec
[18:08] <tsimonq2> Do you have your Ubuntu Unity code anywhere?
[18:08] <rs2009> just added one more env var: PREINSTALLED=true
[18:08] <tsimonq2> why? iirc that's for RPIs and such :)
[18:09] <rs2009> I'm actually going to create a merge request for this after getting it to work in the livecd-rootfs repo, as suggested by vorlon
[18:09] <tsimonq2> (He's welcome to chime in at any time, btw, I'm just helping how I can :) )
[18:10] <rs2009> thanks :D I've also set BINARYFORMAT=true
[18:10] <rs2009> oops, meant BINARYFORMAT=iso
[18:13] <tsimonq2> fyi a lot of these env vars you're manually setting are kinda redundant dude :)
[18:14] <tsimonq2> hmm... maybe I'm speaking too soon... I'll shut up and come back when I have some progress :P feel free to PM me too
[18:14] <tsimonq2> I do eventually have to get back to $dayjob
[18:14] <rs2009> oh, was actually going through the scripts and setting the env variables I could find in the script that weren't being set by it
[18:14] <tsimonq2> ahhh, nice
[18:15] <rs2009> well, I ran `lb build` and no errors so far :)
[18:16] <tsimonq2> sweet, that might do the trick, the more complicated thing may be making the ISO ;P
[18:20] <rs2009> oh lmao
[18:21] <rs2009> we've actually been using our own ISO builder in the past (also used by UCR and others): https://gitlab.com/ubuntu-unity/ubuntu-remixes
[18:46] <rs2009> vorlon: our seed actually isn't under https://people.canonical.com/~ubuntu-archive/seeds/ yet, so was wondering whether I should change SEEDMIRROR to the Launchpad repo if the flavor being built is Ubuntu Unity
[18:50] <vorlon> rs2009: as soon as I have a git repo in launchpad to pull the seed from, I can get it published to https://people.canonical.com/~ubuntu-archive/seeds/
[18:54] <rs2009> vorlon: sure, I'll make it a git repo right away. we're actually going to add some Ubuntu Unity packages to the seed after all the Ubuntu Unity packages are uploaded by seb128 to universe, so I'll make it a git repo for now and make those changes to the seed later
[19:00] <rs2009> vorlon: ah, looks like I'm not an admin in the Unity7 Maintainers team (I've asked Khurshid to make me one, but I'm not sure when he'll respond). is it okay if I make it a personal branch for now?
[19:01] <rs2009> or I could create it under the Ubuntu Unity Devs team on Launchpad
[19:13] <vorlon> rs2009: I don't want to publish from a personal branch. Do you have to be an admin to push a new branch?
[19:13] <vorlon> that doesn't sound right to me
[19:23] <rs2009> vorlon: looks like I don't need to be an admin to push code branches/repos, so that wasn't a problem. I just created a new repo with the seed: https://code.launchpad.net/~unity7maintainers/+git/ubuntu-unity-seeds
[19:23] <vorlon> rs2009: perfect, thanks
[19:25] <vorlon> rs2009: I'm going to adjust this however - following the convention it should be https://code.launchpad.net/~unity7maintainers/ubuntu-seeds/+git/ubuntu-unity
[19:25] <rs2009> vorlon: ah okay
[19:26] <vorlon> rs2009: voilà: https://code.launchpad.net/~unity7maintainers/ubuntu-seeds/+git/ubuntu-unity
[19:27] <rs2009> vorlon: oh, was actually making that change too :)
[19:33] <vorlon> rs2009: https://people.canonical.com/~ubuntu-archive/seeds/ubuntu-unity.kinetic/
[19:34] -queuebot:#ubuntu-release- New sync: rust-python3-dll-a (kinetic-proposed/primary) [0.2.3-1]
[19:34] <rs2009> vorlon: ah, thanks :) I'll start the local build right away and create the merge request if it's successful
[20:09] <rs2009> hey vorlon, I seem to get "Could not resolve 'archive.ubuntu.com'" after all the install packages are installed in the ISO and before the live packages are installed
[20:09] <vorlon> hmm
[20:09] <vorlon> is your branch published somewhere that I can look at?
[20:10] <vorlon> also I wouldn't necessarily require you to have tested it before we merge since tests outside of launchpad are awkward
[20:18] -queuebot:#ubuntu-release- New binary: libshumate [amd64] (kinetic-proposed/universe) [1.0.0.beta-1fakesync1] (no packageset)
[20:21] <rs2009> vorlon: I've just pushed my changes to a branch on LP: https://code.launchpad.net/~rs2009/livecd-rootfs/+git/livecd-rootfs/+ref/ubuntu/master
[20:22] -queuebot:#ubuntu-release- New: accepted openvdb [armhf] (kinetic-proposed) [9.1.0-7ubuntu1]
[20:22] -queuebot:#ubuntu-release- New: accepted rust-python3-dll-a [sync] (kinetic-proposed) [0.2.3-1]
[20:22] -queuebot:#ubuntu-release- New: accepted openvdb [riscv64] (kinetic-proposed) [9.1.0-7ubuntu1]
[20:22] <rs2009> also, thank you very much for your vote :) just saw your email
[20:24] -queuebot:#ubuntu-release- New binary: rust-python3-dll-a [amd64] (kinetic-proposed/none) [0.2.3-1] (no packageset)
[20:24] -queuebot:#ubuntu-release- New binary: rust-python3-dll-a [s390x] (kinetic-proposed/none) [0.2.3-1] (no packageset)
[20:24] -queuebot:#ubuntu-release- New binary: rust-python3-dll-a [arm64] (kinetic-proposed/universe) [0.2.3-1] (no packageset)
[20:24] -queuebot:#ubuntu-release- New binary: rust-python3-dll-a [ppc64el] (kinetic-proposed/universe) [0.2.3-1] (no packageset)
[20:24] -queuebot:#ubuntu-release- New binary: rust-python3-dll-a [armhf] (kinetic-proposed/universe) [0.2.3-1] (no packageset)
[20:26] -queuebot:#ubuntu-release- New: accepted rust-python3-dll-a [armhf] (kinetic-proposed) [0.2.3-1]
[20:27] -queuebot:#ubuntu-release- New: accepted rust-python3-dll-a [amd64] (kinetic-proposed) [0.2.3-1]
[20:27] -queuebot:#ubuntu-release- New: accepted rust-python3-dll-a [ppc64el] (kinetic-proposed) [0.2.3-1]
[20:27] -queuebot:#ubuntu-release- New: accepted rust-python3-dll-a [arm64] (kinetic-proposed) [0.2.3-1]
[20:27] -queuebot:#ubuntu-release- New: accepted rust-python3-dll-a [s390x] (kinetic-proposed) [0.2.3-1]
[20:30] <vorlon> jbicha: why was libshumate a fakesync?
[20:30] <vorlon> jbicha: n/m is in changelog
[20:31] <rs2009> vorlon: should I create a merge request for the daily flavor?
[20:31] <vorlon> rs2009: yes please
[20:31] <jbicha> I manually created the tarball earlier because I needed a git snapshot and missed the step to convert the . to a ~. GNOME's prerelease numbering is really annoying
[20:31] -queuebot:#ubuntu-release- New: accepted libshumate [amd64] (kinetic-proposed) [1.0.0.beta-1fakesync1]
[20:32] <rs2009> vorlon: I've created the request: https://code.launchpad.net/~rs2009/livecd-rootfs/+git/livecd-rootfs/+merge/429249
[20:33] -queuebot:#ubuntu-release- New: accepted rust-average [sync] (kinetic-proposed) [0.13.1-3]
[20:35] -queuebot:#ubuntu-release- New binary: rust-average [amd64] (kinetic-proposed/none) [0.13.1-3] (no packageset)
[20:35] -queuebot:#ubuntu-release- New binary: rust-average [s390x] (kinetic-proposed/none) [0.13.1-3] (no packageset)
[20:35] -queuebot:#ubuntu-release- New binary: rust-average [ppc64el] (kinetic-proposed/none) [0.13.1-3] (no packageset)
[20:35] <vorlon> rs2009: uploaded
[20:36] <rs2009> vorlon: thanks :) would sil2100 and rbasak also be voting on the daily flavor?
[20:37] <vorlon> rs2009: they should (and cyphermox )
[20:37] -queuebot:#ubuntu-release- New binary: rust-average [arm64] (kinetic-proposed/none) [0.13.1-3] (no packageset)
[20:37] <rs2009> (it's past 2 am here in India and I was wondering if I should stay awake a little longer in case they're going to vote soon)
[20:38] <jbicha> rs2009: please get your rest. It may take a few days :)
[20:39] <rs2009> jbicha: sure :)
[20:40] <jbicha> you got a lot done today though. Congrats!
[20:40] -queuebot:#ubuntu-release- New binary: rust-python3-dll-a [riscv64] (kinetic-proposed/universe) [0.2.3-1] (no packageset)
[20:40] <vorlon> hah I don't think you should wait up for the vote
[20:40] <rs2009> ty jbicha
[20:41] <rs2009> sure vorlon :)
[20:41]  * tsimonq2 cracks open a case of Red Bull and slides one to rs2009
[20:41] -queuebot:#ubuntu-release- New: accepted rust-average [amd64] (kinetic-proposed) [0.13.1-3]
[20:41] -queuebot:#ubuntu-release- New: accepted rust-average [ppc64el] (kinetic-proposed) [0.13.1-3]
[20:41] -queuebot:#ubuntu-release- New: accepted rust-python3-dll-a [riscv64] (kinetic-proposed) [0.2.3-1]
[20:41] -queuebot:#ubuntu-release- New: accepted rust-average [arm64] (kinetic-proposed) [0.13.1-3]
[20:41] -queuebot:#ubuntu-release- New: accepted rust-average [s390x] (kinetic-proposed) [0.13.1-3]
[20:41] <tsimonq2> nah but in all seriousness, congrats, big step :)
[20:42] <rs2009> tsimonq2: tysm simon :D
[20:42]  * rs2009 doesn't drink red bull ;)
[20:43] <tsimonq2> not yet, just you wait ;)
[20:43] <rs2009> tsimonq2: lmao
[20:55] <vorlon> hmm now to remember how to create a livefs record in launchpad
[20:58] <vorlon> tada https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu-unity
[21:35] <mfo> 1
[21:35] <tsimonq2> 2
[21:35] <mfo> oops :)
[21:35] <tsimonq2> :)
[21:35] <mfo> tsimonq2, lol, that's even aligned w/ your nickname!
[21:35] <tsimonq2> hah :D
[21:57] <vorlon> bdmurray: this confuses me, the livecd-rootfs build is failing to resolve ftpmaster.internal but there shouldn't be anything special about the new flavor https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu-unity
[21:58] <tsimonq2> vorlon: Universal issue. Lubuntu has been failing the last two days it seems, same error.
[21:58] <vorlon> ah
[21:58] <tsimonq2> My guess is that ftpmaster.internal is ratelimiting. Had the same exact issue with apt-cacher-ng locally less than a week ago
[21:58] <jbicha> vorlon: I created a standard 'kinetic' branch so that the metapackage ./update script works more easily. Can I delete the other branch name?
[21:59] <jbicha> https://code.launchpad.net/~unity7maintainers/+git/ubuntu-unity-seeds
[22:03] <vorlon> jbicha: uh I thought that was the name of the branch I pushed, not sure what's happening there
[22:03] <vorlon> tsimonq2: ratelimiting> it's a name lookup error
[22:04] <tsimonq2> Aha, that'll do it. Sorry for not flagging it earlier
[22:04] <vorlon> tsimonq2: we were having dns issues in one of the cloud regions but I thought those were resolved
[22:04] <vorlon> (like, a couple months ago)
[22:05] <jbicha> ok, I deleted the ubuntu-unity.kinetic branch cc/ rs2009
[22:05] <vorlon> jbicha: oh - right that's the wrong repo
[22:05] <vorlon> jbicha: https://code.launchpad.net/~unity7maintainers/ubuntu-seeds/+git/ubuntu-unity please
[22:06] <vorlon> (the other repo should probably be deleted entirely)
[22:07] <jbicha> done
[23:18] -queuebot:#ubuntu-release- Unapproved: nginx (jammy-proposed/main) [1.18.0-6ubuntu14.1 => 1.18.0-6ubuntu14.2] (ubuntu-server)
[23:51] -queuebot:#ubuntu-release- New binary: phosh [amd64] (kinetic-proposed/universe) [0.20.0-2] (no packageset)
[23:52] -queuebot:#ubuntu-release- New binary: phosh [s390x] (kinetic-proposed/universe) [0.20.0-2] (no packageset)
[23:53] <vorlon> xnox: doing a bunch of other removals of orphaned binaries in kinetic-proposed now :/
[23:53] -queuebot:#ubuntu-release- New binary: phosh [ppc64el] (kinetic-proposed/universe) [0.20.0-2] (no packageset)