[19:00] <rbasak> o/
[19:00] <lvoytek> o/
[19:00] <sil2100> o/
[19:00] <kanashiro[m]> \o
[19:00] <utkarsh21021> \o
[19:00] <bdmurray> o/
[19:01] <utkarsh21021> nice, we are quorate. Should we start?
[19:01] <rbasak> Sure
[19:01] <rbasak> #startmeeting Developer Membership Board
[19:01] <meetingology> Meeting started at 19:01:41 UTC.  The chair is rbasak.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[19:01] <meetingology> Available commands: action, commands, idea, info, link, nick
[19:02] <rbasak> Let's deal with the action items after our applicant, as the only person who has an action isn't here today anyway.
[19:02] <rbasak> #topic Package Set/Per Package Uploader Applications
[19:02] <rbasak> #subtopic Lena Voytek (2023-01-23 @ 19:00 UTC meeting)
[19:03] <rbasak> So lvoytek is a colleague on my team, so my usual approach is to recuse myself unless I'm needed to make quorum after a unanimous +1 vote from everyone else. But now kanashiro[m] and utkarsh21021 are also close colleagues, so that might not be helpful.
[19:03] <rbasak> Let's see how this goes. But I'll still leave the others to do the questioning I guess.
[19:03] <rbasak> I also added an endorsement a few minutes ago.
[19:03] <utkarsh21021> #link https://wiki.ubuntu.com/LenaVoytek/UbuntuServerDeveloperApplication
[19:04] <rbasak> Thanks!
[19:04] <rbasak> lvoytek: would you like to introduce yourself please?
[19:04] <lvoytek> sure thing
[19:04] <lvoytek> Hi all! I am Lena Voytek. I work on the Server Distro team at Canonical, focusing mostly on packages related to mysql, django, and libvirt, alongside various server packages that need fixes or merges. Today I'm applying for upload permissions for the ubuntu-server package set.
[19:04] <utkarsh21021> whilst kanashiro and rbasak are direct colleagues, I am not ;)
[19:05] <rbasak> Any questions for lvoytek please?
[19:06] <kanashiro[m]> I am going to skip the questioning as well, nothing to ask to be honest
[19:06] <sil2100> I see a lot of good endorsements
[19:07] <sil2100> lvoytek: one question, just out of curiosity - did you ever had an upload sponsored by someone outside of your team?
[19:08] <lvoytek> yes, when we created the virtualbmc package in Ubuntu Corey Bryant sponsored: https://launchpad.net/ubuntu/+source/virtualbmc/2.2.2-0ubuntu3
[19:08] <sil2100> \o/
[19:08] <utkarsh21021> I have sponsored her upload after moving to CPC :P
[19:08] <lvoytek> Since this package ended up going to the openstack team for maintenance
[19:08] <lvoytek> thats true too :)
[19:09] <sil2100> Ah, I keep forgetting the mixture between teams ;p
[19:09] <sil2100> lvoytek: ok, so more of a technical question: I'd like to ask you a bit about SRUs. What can you tell me about what an SRU needs additionally, besides what's needed for a regular devel series upload?
[19:09] <seb128> hey, sorry I got delayed
[19:10] <utkarsh21021> seb128: \o
[19:10] <lvoytek> For an sru the fix for the bug must be in the development release. Then the SRU template must be filled out in the launchpad bug description above the original text, including the impact it will have when released, the plan for testing the fix, in depth info on where problems could arise.
[19:11] <sil2100> lvoytek: good, what needs to be done after the upload is accepted into -proposed?
[19:12] <lvoytek> The sru team will review it to make sure all is good and either continue the upload or block and request changes
[19:12] <sil2100> That's true, but what about after the upload is already accepted? What needs to be done for it to land on the user's machines?
[19:13] <lvoytek> It has to move to the release pocket then the user can update on their end to get the fix
[19:14] <bdmurray> For a stable release would a package move to the release pocket?
[19:14] <lvoytek> the -updates pocket specifically
[19:15] <sil2100> What about validation of the update in -proposed? What do you, as the uploader, need to do to get this update into the -updates pocket?
[19:16] <lvoytek> Ah, make sure all builds succeed and autopkgtests pass
[19:17] <sil2100> That is important, yes, but is there something else needed for the update to be considered 'good-to-go'?
[19:18] <lvoytek> Yes, the package fix must be validated by enabling proposed and testing accordingly
[19:18] <sil2100> That's right o/
[19:19] <sil2100> lvoytek: ok, another one about SRUs: let's say you have a need for a new upstream release of a package as an SRU, because of reasons™. Is that possible?
[19:20] <lvoytek> Yes, specifically in the case of MREs - minor releases that make a stable release more stable. Working on that for bind9 right now
[19:22] <sil2100> lvoytek: can you tell me what is required when preparing such an SRU? What are the requirements for the SRU bug and project/package that you are preparing?
[19:22] <sil2100> In other words: what would be the accept/not-accept criterium for such an upload
[19:24] <lvoytek> It also requires additional information in the report, some packages have special cases in this regard. The bugs that are being fixed should also be noted, along with security fixes. Releases after the current should also have a version >= the one being updated to
[19:25] <sil2100> When in doubt, where would you look for more information about this?
[19:26] <lvoytek> The sru wiki page shows special cases: https://wiki.ubuntu.com/StableReleaseUpdates For info on the release its best to look at the relevant upstream news or commits.
[19:27] <sil2100> Thanks! No more questions from me
[19:27] <lvoytek> Thanks!
[19:28] <utkarsh21021> I have a quick q/general curiosity - is there a reason you've not shadowed in any +1 maintenance yet? Because I believe, you'd be net win for Ubuntu/Canonical in doing that.
[19:28] <lvoytek> I haven't yet. Christian said it would be a good idea as I move toward core dev though
[19:29] <lvoytek> Just need to set it up when there's time
[19:30] <sil2100> Any other questions from other DMB members?
[19:31] <utkarsh21021> none from me
[19:31] <seb128> not from me
[19:31] <bdmurray> not from me
[19:32] <sil2100> rbasak: back to you then!
[19:32] <rbasak> Great, thanks!
[19:32] <rbasak> #vote Grant lvoytek membership of the ubuntu-server packageset
[19:32] <meetingology> Please vote on: Grant lvoytek membership of the ubuntu-server packageset
[19:32] <meetingology> Public votes can be registered by saying +1, -1 or +0 in channel (for private voting, private message me with 'vote +1|-1|+0 #channelname')
[19:33] <sil2100> +1 Solid endorsements and the experience/knowledge is there. PPU is a good start!
[19:33] <meetingology> +1 Solid endorsements and the experience/knowledge is there. PPU is a good start! received from sil2100
[19:35] <seb128> +1 the endorsements on the wiki are really positive feedback from trusted members, the replies to the questions here were great, ppu make sense as a start on the road to coredev
[19:35] <meetingology> +1 the endorsements on the wiki are really positive feedback from trusted members, the replies to the questions here were great, ppu make sense as a start on the road to coredev received from seb128
[19:36] <utkarsh21021> +1; super happy to see her application, I know she'd be a really good addition.
[19:36] <meetingology> +1; super happy to see her application, I know she'd be a really good addition. received from utkarsh21021
[19:37] <bdmurray> Sorry I'm in another meeting
[19:37] <bdmurray> +1 from me
[19:37] <meetingology> +1 from me received from bdmurray
[19:37] <rbasak> #endvote
[19:37] <meetingology> Voting ended on: Grant lvoytek membership of the ubuntu-server packageset
[19:37] <meetingology> Votes for: 4, Votes against: 0, Abstentions: 0
[19:37] <meetingology> Motion carried
[19:37] <rbasak> Congrats lvoytek! I don't think kanashiro[m] or I need to vote in this case.
[19:38] <sil2100> lvoytek: congrats!
[19:38] <lvoytek> Thanks everyone!
[19:38] <rbasak> But I'm +1 obviously, since I endorsed you.
[19:38] <kanashiro[m]> lvoytek: congrats :)
[19:38] <rbasak> I can take the announcement and ACL actions, unless someone else wants to do it?
[19:38] <kanashiro[m]> I am +1 too
[19:39] <rbasak> #action rbasak to announce lvoytek's successful application
[19:39] <meetingology> ACTION: rbasak to announce lvoytek's successful application
[19:39] <rbasak> #action rbasak to make appropriate ACL changes to add lvoytek to
[19:39] <meetingology> ACTION: rbasak to make appropriate ACL changes to add lvoytek to
[19:39] <rbasak> #undo
[19:39] <meetingology> Removing item from minutes: ACTION
[19:39] <rbasak> #action rbasak to make appropriate ACL changes to add lvoytek to ~ubuntu-server-dev
[19:39] <meetingology> ACTION: rbasak to make appropriate ACL changes to add lvoytek to ~ubuntu-server-dev
[19:39] <rbasak> #topic Review of previous action items
[19:39] <rbasak>     teward follow up to get all application process wiki/docs to explain the process to be able to edit wiki pages, for applicants who don't yet have wiki edit access (carried over)
[19:39] <rbasak> teward said he couldn't make it, so we can carry this over.
[19:40] <rbasak> #action     teward follow up to get all application process wiki/docs to explain the process to be able to edit wiki pages, for applicants who don't yet have wiki edit access (carried over)
[19:40] <meetingology> ACTION: teward follow up to get all application process wiki/docs to explain the process to be able to edit wiki pages, for applicants who don't yet have wiki edit access (carried over)
[19:40] <rbasak> #topic Outstanding mailing list requests to assign
[19:41] <teward> rbasak: fun fact, i just got hoem from the doctors appt i was at (emergency appts are not fun)
[19:41] <teward> but yes carry that one over ;)
[19:41] <rbasak> ack
[19:41] <utkarsh21021> teward: I'd say exactly what I said last time: it's fun to see what you're up to usually around this time, haha ;)
[19:41] <rbasak> The thread at https://lists.ubuntu.com/archives/devel-permissions/2022-November/002099.html still needs a reply from most other DMB members please.
[19:42] <rbasak> Maybe we can discuss and vote on it in the next meeting that doesn't have applicants otherwise.
[19:42] <rbasak> I don't see any other ML requests.
[19:42] <rbasak> #topic Open TB bugs
[19:43] <rbasak> #info There aren't any open TB bugs.
[19:43] <rbasak> #topic AOB
[19:43] <rbasak> Anyone?
[19:44] <utkarsh21021> nothing from me
[19:44] <rbasak> #endmeeting
[19:44] <meetingology> Meeting ended at 19:44:44 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-01-23-19.01.moin.txt
[19:45] <kanashiro[m]> thanks for chairing rbasak
[19:45] <kanashiro[m]> o/
[19:46] <utkarsh21021> rbasak: fwiw, I replied to the thread. +1'ing all the way
[19:46] <rbasak> Thanks!
[19:46] <seb128> thanks


[02:15] <sary> Salutations!
[02:16] <sary> i thought i was Idle in here ;(
[02:17] <sary> http://snipt.org/ziGh4
[02:35] <darkxst> sary, they are harmless warnings
[03:11] <sary> hi darkxst, thank you .. it's good to know! as I've have been having many crash reports lately!
[03:11] <darkxst> sary that is mainly because apport is enabled while we are still in beta
[03:12] <sary> Nm-applet,gnome-shell, mission-control.
[03:13] <sary> darkxst: yeah .
[03:14] <darkxst> but would be particularly interest in any gnome-shell crashes
[03:15] <darkxst> well for 3.8, assuming you are using the ppa
[03:18] <sary> here is one !bug #1163651
[03:18] <sary> hmm, wait ..
[03:21] <sary> I don't quite remember if i was using 3.8 of the shell and ppa was enabled while the crash in the above bug occurred.
[03:23] <sary> But, I don't see this crash anymore , or any other abnormal activities coming from the shell.
[03:45] <darkxst> sary memory usage should be much better now we have the new spidermonkey ppa
[03:46] <darkxst> in that bug though, it seems like something locked up your gpu
[03:59] <sary> darkxst: yeah, difinitely was coming from nvidia closed source driver .
[04:02] <sary> as i remembered now, i saw a driver-updates for the current driver, i had to give it a shoot and try it, so i hae acivated the driver-updates while i had gnome 3.8 installed .
[04:04] <darkxst> the later nvidia drivers (313 series) have been pretty much perfect here with g-s
[04:05] <skinlayers> Quick question, if anyone knows the answer off hand. I run apt-cacher-ng on my server, so I usually install ubuntu via PXE netboot. I have the ISO for Ubuntu GNOME, but I was wondering if the linux, and initrd.gz files for it were around somewhere?
[04:06] <darkxst> skinlayers, they are in the iso
[04:06] <darkxst> just mount it and grab what you need
[04:06] <skinlayers> Thank you! I wasn't sure if I could use the ones straight off the iso or if the netboot ones were modified.
[04:06] <darkxst> they are also going to be exactly the same (I believe) as the vanilla ubuntu ones
[04:07] <skinlayers> hmm... then how does it pick which packages to install? Is there a preseed option for ubuntu-gnome?
[04:07] <darkxst> or actually maybe the casper stuff goess into initrd.gz
[04:08] <darkxst> that is mostly done when building the iso, everything is installed to a squashfs filesystem
[04:09] <darkxst> that gets copied to target machine, and then a few other bits and pieces will get installed by ubiquity
[04:11] <darkxst> yes, you should be able to do a oem preseed with it
[04:27] <skinlayers> Ubuntu Gnome uses the exact same repos as regular Ubuntu right? Its just a difference of packages?
[04:27] <darkxst> skinlayers, yes
[04:27] <darkxst> does a netboot use the squashfs off the iso?
[04:31] <skinlayers> Nope... it boots pxelinux.0, which then, depending on your menu choice, boots "linux" with a "inird.gz".
[04:31] <skinlayers> initrd.gz*
[04:31] <darkxst> I meant after that
[04:31] <skinlayers> And that boots a minimal debian installer that grabs all packages straight from the ubuntu repos
[04:32] <darkxst> ah I see
[04:32] <skinlayers> And it gives you the option to use a proxy, so I point it at my local apt-cacher-ng server.
[04:32] <skinlayers> So that way I can install from my network, and build from the latest packages
[04:33] <skinlayers> and But it doesn't use teh squashfs at all from what I know
[04:33] <darkxst> ok so you might need to track down the seed files that are used to build the iso
[04:33] <darkxst> they are on launchpad somewhere
[04:34] <darkxst> or just install ubuntu-gnome-desktop and ubuntu-gnome-default-settings
[04:34] <darkxst> on top of debian mini
[04:40] <darkxst> although I have no experience with netboot, its easy to unpack the ramdisk (initrd.gz) and have a look what is going on in there
[05:25] <skinlayers> @darkxst Thanks for the info! I've been digging around in the initrd for a while ;)
[12:32] <bennypr0fane>  hey, I am thinking about replacing regular Ubuntu 12.04 on my laptop with 13.04 Gnome - or Gnome Remix 12.10, given that the latter oddly has a longer life cycle as of now. Which of the 2 would you say comes with the more advanced state of Gnome out of the box, as of now? I now they both come with 3.6, but how about integration of extensions, user themes and other customizability (if that is even a direction that Gnome development is going in)?
[12:33] <bennypr0fane> * I know they both....
[12:45] <darkxst> bennypr0fane, 13.04 will be better supported regardless of apparent life cycles
[12:48] <darkxst> I have a gnome-shell update that has been stuck in the update queue for like 6+ weeks now.... (for 12.10)
[12:49] <darkxst> not sure how we can really support updates in old releases when it takes that long
[12:51] <bennypr0fane> you mean you got that update pushed to 13.04 while it hasn't been in the repos for 12.10 at the same time?
[12:51] <darkxst> bennypr0fane, its in 13.04
[12:51] <darkxst> waiting in queue for 12.10
[12:52] <tommie-lie> hope that will be better with the shorter release cycles
[12:55] <darkxst> the packages in main seem to get priority for SRU's
[12:55] <darkxst> that said we will mostly be running from ppa's if you want the latest and greatest, so atleast we can fix those instantly
[12:56] <tommie-lie> but PPAs also have the problem of problems spreading quickly to everyone, just as quick as fixes
[12:56] <bennypr0fane> any of you guys help developing 13.04 Gnome?
[12:57] <bennypr0fane> tommie-lie isn't that more an asseT?
[12:57] <darkxst> gnome3 ppa is as official as you will get from a ppa
[12:58] <tommie-lie> bennypr0fane: hum... for my everyday working machine I'd like software that has been around for a month or so (if the userbase is large enough)
[12:58] <bennypr0fane> I don't get why theyx not taking in the shell extensions ppa from the webupd8 team
[12:58] <darkxst> tommie-lie, most things in gnome3 have been tested in staging before landing
[12:58] <darkxst> unless they are just minor updates
[12:58] <bennypr0fane> tommie-lie in that case, you might check the dates of packages you update...
[12:59] <tommie-lie> darkxst: you mean ppa:gnome3-staging?
[12:59] <darkxst> tommie-lie, yes
[13:00] <tommie-lie> darkxst: how well tested can I expect packages from gnome3? is every single update to one of them proposed to be an SRU (even if not accepted)?
[13:00] <darkxst> no SRU's
[13:00] <darkxst> big updates are tested in staging
[13:01] <darkxst> minor updates we test locally then update
[13:01] <darkxst> sometimes regressions might get through, but shouldnt be anything major
[13:01] <tommie-lie> thanks, good to know
[13:01] <tommie-lie> you seem to have changed the workflow over the last year ;-)
[13:02] <darkxst> tommie-lie, previously gnome3 had the bits that werent ready
[13:02] <darkxst> now we have a split in cycles, that bits not ready, are actually in staging
[13:03] <tommie-lie> yep, but it also had the pieces missing from ubuntu because they were deemed not ubuntu-ish enough (like gdm)
[13:04] <darkxst> tommie-lie, gdm is in the archives
[13:04] <darkxst> any version in ppa would have been deemed not ready for archives, that is all
[13:04] <bennypr0fane> darkxst, what's an sru?
[13:05] <darkxst> Stable Release Update
[13:05] <tommie-lie> darkxst: it is now, but when the transition from the old-style gdm to the new lockscreen occurred and Ubuntu already switched to lightdm, the main repo was one major version behind for half a year (or even a full year? can't remember)
[13:05] <darkxst> essentially all updates that happen after release have to go through that
[13:05] <darkxst> tommie-lie, yes behind, because it was horribly broken
[13:11] <bennypr0fane> darkxst, which one, the older one or the update?
[13:11] <tommie-lie> darkxst: well, the update from the gnome3-ppa worked and was not really broken, it just didn't make it in time for the feature freeze
[13:15] <tommie-lie> darkxst: out of curiosity, is there and other place where development coordination for ubuntu-gnome related stuff takes place except here and ubuntu-gnome on lists.ubuntu.com?
[13:16] <darkxst> bennypr0fane, like 3.6 before we landed it in 12.10
[13:16] <darkxst> tommie-lie, mostly here
[13:31] <bennypr0fane> Is beta 2 the final beta? Or would you recommmend daily bulid over the betA?
[13:32] <darkxst> bennypr0fane, beta 2 is broken for some regions
[13:32] <darkxst> I would suggest daily
[13:32] <bennypr0fane> http://cdimage.ubuntu.com/ubuntu-gnome/releases/13.04/beta-2/ it doesn't say here that it's final
[13:33] <darkxst> its beta 2, how more final than that do you want?
[13:33] <darkxst> just grab the daily though
[13:33] <darkxst> beta-2 has some major locale issues for certain countries/regions
[13:33] <bennypr0fane> ah I see it does say it here http://fridge.ubuntu.com/2013/04/05/ubuntu-13-04-raring-ringtail-beta-2-released/
[13:33] <bennypr0fane> Ok willd o, thanks!
[15:35] <atrus> is it bad that gnome-control-center/gnome-settings-daemon aren't up to 3.8.x in the gnome3 ppa? i see they're in staging...
[22:33] <Guest43498> Hello.  I am just wondering if I should use Ubuntu-Gnome or use regular Ubuntu and install all of the Gnome things myself.
[22:35] <Guest43498> Hello?
[22:36] <Guest43498> join #ubuntu


[02:01] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/4280 Pending binary packages
[02:21] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/4280 Diff missing
[02:28] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/4280 Generating diffs
[02:28] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/4280 Successfully built
[03:39] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/4280 Publishing packages
[04:00] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/4280 UNAPPROVED queue
[07:08] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4246 Dependency wait (groovy/kio-extras). Needs rebuild due to burned version number (groovy/calligra, groovy/opencv). Needs rebuild due to higher version at destination (groovy/gst-plugins-bad1.0, groovy/kimageformats). Successfully built (groovy/aqsis, groovy/blender, groovy/darktable, groovy/enblend-enfuse, groovy/exactimage, groovy/freeimage, groovy/gegl, groovy/gimp, groovy/hugin, groovy/i
[12:03] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4281 QA Signoff:
[12:03] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4281 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[12:12] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4281 Generating diffs
[12:15] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4281 Dependency wait (groovy/node-rollup). Pending binary packages (groovy/node-bl, groovy/node-d3-hierarchy, groovy/node-entities, groovy/node-eventemitter3, groovy/node-handlebars, groovy/node-ip-address, groovy/node-json-loader, groovy/node-less-loader, groovy/node-markdown-it, groovy/node-markdown-it-html5-embed, groovy/node-moment, groovy/node-mongodb, groovy/node-mqtt-packet, groovy/node-
[12:42] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4281 Pending binary packages (groovy/node-rollup). Successfully built (groovy/node-bl, groovy/node-d3-hierarchy, groovy/node-entities, groovy/node-eventemitter3, groovy/node-handlebars, groovy/node-ip-address, groovy/node-json-loader, groovy/node-less-loader, groovy/node-markdown-it, groovy/node-markdown-it-html5-embed, groovy/node-moment, groovy/node-mongodb, groovy/node-mqtt-packet, groovy/no
[12:58] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4275 Diff missing (focal/gcc-10-cross-mipsen, focal/gcc-9-cross-mipsen). Proposed pocket (focal/gcc-10, focal/gcc-9). REJECTED queue (focal/python2.7)
[13:22] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4281 Successfully built
[14:18] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4275 Diff missing (focal/gcc-10-cross-mipsen, focal/gcc-9-cross-mipsen). Proposed pocket (focal/gcc-10, focal/gcc-9). UNAPPROVED queue (focal/python2.7)
[14:36] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4275 Proposed pocket (focal/gcc-10, focal/gcc-9). UNAPPROVED queue (focal/gcc-10-cross-mipsen, focal/gcc-9-cross-mipsen, focal/python2.7)
[15:36] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4275 Proposed pocket
[15:41] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3801 Successfully built
[17:11] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4281 Publishing packages
[17:22] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4281 Proposed pocket
[18:42] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4161 Diff missing (focal/libvirt). Uploading build (focal/qemu)
[19:02] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4161 Diff missing
[19:22] -queuebot:#ubuntu-ci-eng- LocutusOfBorg, https://bileto.ubuntu.com/#/ticket/4281 Needs rebuild due to higher version at destination (groovy/node-rollup-plugin-replace). Proposed pocket (groovy/node-bl, groovy/node-d3-hierarchy, groovy/node-entities, groovy/node-eventemitter3, groovy/node-handlebars, groovy/node-ip-address, groovy/node-json-loader, groovy/node-less-loader, groovy/node-markdown-it, groovy/node-markdown-it-html5-embed, groovy/node-moment, groovy/node-mong
[21:41] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3801 Needs rebuild due to higher version at destination


[14:37] <youngbin_> kenvandine: Hi. I'm the leader at Korean LoCo. If you are not busy, It would be appreciated if you review our reverification application. Thank you.