[02:06] <DM|> Ok i cant get into #ubuntu
[02:06] <DM|> !ops
[02:06] <ubotu> Help! Mez, LjL, elkbuntu, imbrandon, DBO, gnomefreak, Hobbsee, rob, ompaul, Madpilot, Burgundavia, Seveas, CarlK, crimsun, ajmitch, tritium, Nalioth, thoreauputic, apokryphos, tonyyarusso, PriceChild, Amaranth, jrib, jenda, nixternal, Myrtti or mneptok
[02:07] <ubotu> DM| called the ops in #ubuntu-ops
[02:08] <nalioth> DM|: could you just not wait a minute or two?
[02:10] <DM|> nalioth well i came in for help, because i cant access #ubuntu, no one responded, so how am I to know anyone is there
[02:10] <DM|> Im not a mind reader
[02:10] <nalioth> you waited all of half a minute
[02:10] <nalioth> not all of us watch this channel 24/7
[02:11] <nixternal> DM|: have you fixed your router?
[02:11] <DM|> I did the last time
[02:11] <nixternal> hrmm, it seems that is the only ban I see, and that was from 6/13
[02:12] <DM|> That was supposed to be cleared up
[02:13] <nixternal> try and connect now
[02:13] <DM|> that did it thanks nixternal
[02:13] <nixternal> DM|: will you join me really quick in ##woohoo just to double check your router?
[02:15] <nixternal> enjoy :)
[06:55] <mneptok> dum dee dee
[06:55] <mneptok> dee la dee da
[07:05] <Hobbsee> mneptok!!!
[07:19] <Hobbsee> hey SportChick!
[07:19] <SportChick> hiya
[07:20] <mneptok> HI!
[07:20] <SportChick> hi :p
[07:20] <mneptok> HI! HI! HI!
[07:20] <mneptok> wheeee!
[07:49] <tonyyarusso> Weird.  If you set a +d, it doesn't show up in the /bans in irssi.
[07:55] <Hobbsee> it does if you do a /mode $channel d though
[07:55] <tonyyarusso> Hobbsee: Aaah, that's the way I was trying to remember.  ty
[07:56] <tonyyarusso> Hobbsee: any better way to include spaces than with a ? wildcard?
[07:56] <Hobbsee> no idea
[07:56] <tonyyarusso> k
[07:57] <tonyyarusso> judging from what others have done in my logs, that's the way to do it
[08:21] <poningru> happy 777 everyone!!
[08:22] <Hobbsee> hiya poningru
[08:22] <poningru> yarr
[08:22] <Hobbsee> does that mean the crazies will be out, then?
[08:22] <poningru> who knows
[08:22] <poningru> I mean if they are out
[08:22] <poningru> how is that different than any other day?
[08:22] <poningru> atleast in irc land
[08:24] <Hobbsee> there are more crazy and less crazy days in ircland
[08:28] <poningru> yeah anyday mneptok doesnt logon is the less crazy day!
[08:28] <poningru> ;p
[10:27] <ompaul> bbrazil, I love the understatement
[10:28] <ompaul> okay I am out of here
[10:28] <ompaul> bbrazil,  you in dublin?
[10:28] <GazzaK> ompaul, morning, we are at LugRadio Live :-)
[10:29] <ompaul> GazzaK, morning
[10:29] <ompaul> enjoy it
[10:29] <ompaul> bbrazil, if you are sms me - I'll drop over that way in two or so hours and have a cup of tea :)
[10:29] <ompaul> if you have the time
[10:30] <ompaul> gtg
[10:32] <bbrazil> ompaul: I am, but I'm oncall
[11:03] <ubotu> Jordan_U called the ops in #ubuntu
[11:03] <stefg> Ermm... i'm a bit surprised finding myself banned from #ubuntu, #ubuntu-offtopic when i tried to login this morning. what gives?
[11:13] <stefg> ping! some op awake? (i know it's night on the other side of the big pond)
[11:18] <gresola> ola
[11:18] <gresola> ola atoponce
[11:23] <stefg> Mez, LjL, elkbuntu, imbrandon, DBO, gnomefreak, Hobbsee, rob, ompaul, Madpilot, Burgundavia, Seveas, CarlK, crimsun, ajmitch, tritium, Nalioth, thoreauputic, apokryphos, tonyyarusso, PriceChild, Amaranth, jrib, jenda, nixternal, Myrtti or mneptok. Someone awake of you? I find myself banned from #ubuntu, #ubuntu-offtopic when trying to login. Must be some error. Someone unban, me please
[11:30] <jenda> hm?
[12:54] <stefg> ping, someone alive who can unban me from #ubuntu , and -offtopic ? No idea why i found myself banned when i tried to join this morning
[12:56] <gnomefreak> stefg: i didnt see you banned from ubuntu unless its been a long time
[12:57] <stefg> hi, good morning, (or whatever is appropiate in your timezone)... vhatzilla tells me i'm banned from #ubuntu ... can /join #kubuntu. someone put an unclever hostmask to some other ban?
[12:59] <gnomefreak> @btlogin
[12:59] <gnomefreak> give me a few minutes
[01:01] <gnomefreak> stefg: im not showing you banned at all anywhere
[01:01] <gnomefreak> stefg: not by name nor hostmask
[01:01] <gnomefreak> stefg: use xchat see if you can log in
[01:01] <stefg> hmmm.... wait a sec, i'll try from the laptop
[01:04] <stefg> ugh.... xchat works
[01:04] <gnomefreak> its chatzilla
[01:04] <gnomefreak> i saw
[01:07] <bbrazil> hmm, is there a ban on n=chatzill@* or something?
[01:14] <gnomefreak> no
[01:14] <gnomefreak> not htat i saw
[01:16] <gnomefreak> thats odd
[01:27] <ubuntu_laptop> @btlogin
[01:27] <gnomefreak> @btlogin
[01:27] <gnomefreak> only works on this nick
[01:28] <gnomefreak> ok who banned chatzilla and how did you ban it?
[01:29] <gnomefreak> they seemed to all been removed but still cant get in
[01:31] <elkbuntu> gnomefreak, nalioth might know?
[01:31] <gnomefreak> nalioth: you around?
[01:31] <gnomefreak> ty elkbuntu
[01:32] <elkbuntu> gnomefreak, or another staffer, maybe ompaul or jenda
[01:32] <gnomefreak> wouldnt it still show up in ban list either bt or /node?
[01:32] <jenda> hm?
[01:32] <gnomefreak> mode even
[01:32] <gnomefreak> jenda: can you check staff bans on chatzilla?
[01:32] <elkbuntu> gnomefreak, dunno
[01:33] <jenda> staff bans?
[01:33] <jenda> there's certainly no k-lines on it.
[01:33] <gnomefreak> jenda: its not in bantracker nor /mode #channel
[01:33] <jenda> hmm
[01:33] <gnomefreak> so i figured maybe you have your own list
[01:34] <jenda> Well, I'll report it, but it would have to be a k/g/d-line, and I'm sure we don't (wittingly) ban a client.
[01:34] <gnomefreak> ty its strange that any of us would ban a client anyway
[01:35] <jenda> besides, the people can connect to the network, no?
[01:35] <gnomefreak> im connected with ubuntu_laptop on chatzilla
[01:35] <jenda> ok
[01:35] <jenda> and you're banned from #ubuntu?
[01:35] <gnomefreak> jenda: but you also ban in channels without oping so im not sure if it uses same list
[01:36] <gnomefreak> jenda: and -offtopic
[01:36] <jenda> it does
[01:36] <gnomefreak> INFO] 	Channel view for #ubuntu opened. [INFO] 	You are banned from this channel.
[01:36] <ubuntu_laptop> INFO] 	Channel view for #ubuntu opened.
[01:37] <ubuntu_laptop> 	[INFO] 	You are banned from this channel.
[01:37] <gnomefreak> oops
[01:38] <jenda> funky
[01:40] <gnomefreak> someone else complained about it and it confused me becasue i couldnt find it he connected with xchat and works
[01:40] <elkbuntu> i'd say it's time to harrass other staffers :
[01:41] <gnomefreak> elkbuntu: jenda is the only one on i know ;)
[01:41] <bbrazil> 313 bans? this will take a bit...
[01:41] <gnomefreak> i try not to harrass staff i dont know
[01:41] <elkbuntu> gnomefreak, but he will be able to harrass others :)
[01:41] <gnomefreak> bbrazil: yes it does i went over it 3 times
[01:42] <gnomefreak> elkbuntu: good point
[01:42] <bbrazil> 242 - #ubuntu: ban ubotu?*!*@* [by ballard.freenode.net, 3821661 secs ago]
[01:43] <bbrazil> 12:43 -!- 0 - #ubuntu: ban New?Now?Know?How [by tonyyarusso!n=anthony@ubuntu/member/tonyyarusso, 20691 secs ago]
[01:43] <gnomefreak> thats ubotu? ban
[01:43] <bbrazil> that's why ubuntu_laptop can't join
[01:44] <jenda> I alread harassed some :)
[01:44] <gnomefreak> bbrazil: no its not related to that
[01:44] <gnomefreak> stegf couldnt get in either
[01:44] <jenda> I'm quite sure this isn't a staff issue, though.
[01:45] <ubuntu_laptop> im in all channels
[01:45] <ubuntu_laptop> im sure it would have muted or removed me
[01:45] <bbrazil> ubuntu_laptop: /cycle to be sure
[01:45] <ubuntu_laptop> still there
[01:45] <jenda> ubuntu_laptop: how about changing your 'username' to chatzill?
[01:46] <ubuntu_laptop> jenda: than i will be banned
[01:46] <ubuntu_laptop> lol
[01:46] <jenda> you sure? :)
[01:46] <jenda> perhaps it's something about chatzilla itself :)
[01:46] <ubuntu_laptop> ill let you know
[01:48] <bbrazil> worked for me with n=chatzill
[01:48] <ubuntu_laptop> thats frigging odd
[01:49] <elkbuntu> i think tonyyarusso's ban is the culprit
[01:49] <bbrazil> for gnomefreak, yes
[01:49] <ubotu> Hirvinen called the ops in #ubuntu
[01:49] <ubotu> stefg called the ops in #ubuntu
[01:49] <ubuntu_laptop> im using iceape chatzilla and it should be differnet than firefox-chatzill
[01:50] <ubuntu_laptop> hmmm
[01:51] <gnomefreak> ok let me check on this
[01:53] <gnomefreak> if it was chatzilla why could i join here?
[01:53] <gnomefreak> stefg: thanks ;)
[01:53] <robdeman> hello all
[01:53] <gnomefreak> robdeman: we know
[01:54] <gnomefreak> robdeman: try joining #ubuntu+1 please
[01:54] <robdeman> why am I banned from ubuntu?
[01:54] <robdeman> oh ok
[01:54] <gnomefreak> robdeman: and let me know
[01:54] <gnomefreak> robdeman: dont ask for support there though
[01:54] <bbrazil> could one of ye do /mode -d New?Now?Know?How
[01:54] <bbrazil> that should fix it
[01:54] <gnomefreak> its not chatzilla
[01:54] <bbrazil> it's the default realname it puts in
[01:54] <gnomefreak> bbrazil: ofcourse
[01:54] <robdeman> gnomefreak: yes I can access #ubuntu+1
[01:54] <gnomefreak> i saw
[01:55] <robdeman> so what happened?
[01:55] <gnomefreak> try to join #ubuntu
[01:56] <elkbuntu> i just joined successfully
[01:56] <bbrazil> robdeman: over-broad ban on a default setting by the looks of it
[01:56] <gnomefreak> elkbuntu: yes i removed the bans in both channels
[01:56] <gnomefreak> -offtopic and main
[01:57] <stefg> ok. so i tried a fresh profile with chatzilla... since i can join all the other channels on freenode it must be related to #ubuntu-settings
[01:57] <gnomefreak> someone is gonna have to rethink that ban
[01:57] <stefg> ah, ok
[01:57] <gnomefreak> stefg: you can join now
[01:57] <elkbuntu> my god this client is atrocious
[01:57] <stefg> phewww.... thanks. i can't stand xchat, to be honest
[01:57] <gnomefreak> elkbuntu: agreed
[01:57] <elkbuntu> they cant pick any single font size or anything
[01:57] <bbrazil> time was ZZ:58 - 6 hours ago
[01:57] <gnomefreak> ty bbrazil
[01:58] <bbrazil> can someone check #ubuntu? I only rejoin a few hours back
[01:58] <gnomefreak> bbrazil: its fixed
[01:58] <gnomefreak> the ban you mean?
[01:58] <bbrazil> I'm just wondering what the context was
[01:59] <gnomefreak> context of time?
[01:59] <gnomefreak> it works fine here at 7:58
[02:00] <bbrazil> I mean that's when the ban was originally set in ubuntu-offtopic
[02:00] <stefg> ok, so for the record: what was it that banned all the chatzillas?
[02:00] <elkbuntu> stefg, the default real name
[02:01] <stefg> ah, good to know (and to change that)
[02:01] <elkbuntu> this is why defaults are not good ;)
[02:04] <gnomefreak> i only show seconds (i have to find a script that changes that
[02:39] <ompaul> gnomefreak, what you are talking about looks like someone used +lart in xchat
[02:39] <gnomefreak> for that ban?
[02:39] <ompaul> yeah it hits nick user@ip ::real name
[02:39] <gnomefreak> ah
[02:39] <ompaul> all four part
[02:39] <ompaul> s
[02:40] <ompaul> I looks cos I ain't looked
[02:40] <gnomefreak> well im sure it will end up banned again
[02:40] <ompaul> check in bugbot
[02:40] <ompaul> if not there then it was in the autoremove
[02:40] <ompaul> so that would be a really short thing to do
[02:40] <ompaul> which is not the idea of autoremove
[02:40] <ompaul> kinda silly
[02:41] <gnomefreak> ill look sometime today
[02:41] <gnomefreak> im trying to fix firefox atm
[03:01] <ompaul> okay I am about to remove a large amount of old server side bans
[03:01] <ompaul> none of the special ones
[03:01] <ompaul> #ubuntu
[05:39] <TheSheep> what's intelhda?
[05:39] <ompaul> intel hda
[05:39] <ompaul> or something
[05:39] <TheSheep> hdd = hard disk drive, hda = hard disk a?
[05:39] <Pumpernickel> high def audio
[05:40] <TheSheep> Pumpernickel: thanks :)
[05:40] <Pumpernickel> It's their replacement standard for ac'97.
[05:40] <ompaul> standard, is it open?
[05:40] <mc44> @gnu open?
[05:40] <ubotu> GNU/open?
[05:41] <ompaul> @Gnu Publicly available free to use documents on said standard
[05:41] <ubotu> GNU/Publicly GNU/available GNU/free GNU/to GNU/use GNU/documents GNU/on GNU/said GNU/standard
[05:44] <Pumpernickel> Looks open ish, at least. http://www.intel.com/design/chipsets/manuals/307017.htm
[05:45] <Pumpernickel> I'm hardly an expert on it, though.
[06:03] <ishock_> WHY am I still affected by this?
[06:05] <ishock_> Hello?
[06:06] <ubotu> magnetron called the ops in #ubuntu
[06:13] <ishock_> HELLO
[06:13] <ishock_> EXCUSE me.............
[06:13] <Pumpernickel> Yes, we see that you're there.  No, there's no one around who can help you right now.  Please be patient.
[06:14] <ishock_> I need tested for some stupid reason...
[06:15] <ishock_> GLOBAL: http://vidgaming.org/Dstudio.zip for anyone who needs t download Dialog Studio.
[06:17] <elkbuntu> ishock_, why are you linking warez?
[06:18] <ishock_> How am I linking warez?
[06:18] <elkbuntu> you're linking to software downloads that are not in repos for starters
[06:18] <ishock_> Well
[06:18] <ishock_> That was mainly for the other server I am on
[06:19] <ishock_> Where a lot of mIRC scripters rely on that program
[06:19] <elkbuntu> that sort of global messaging will get you banned from any ubuntu channel
[06:19] <ishock_> I didn't even know it would come over here...
[06:20] <elkbuntu> you also have a history of verbal abuse
[06:21] <ishock_> I know
[06:21] <ishock_> I'm more insterested in why I can;t join Ubuntu
[06:22] <elkbuntu> it seems you're quarantined for the d c c exploit
[06:23] <elkbuntu> i don't know the test strings for that, so i cannot do anything about it
[06:23] <ishock_> Its odd
[06:23] <ishock_> Considering Im connected on port 8001..
[06:25] <elkbuntu> ishock_, you may have coincidentally dropped off in the middle of a huge spree. there's been a few this week with large impacts. we prefer to err on the side of caution, however, for the security of everyone who uses our channels
[07:15] <ompaul> !pronouce
[07:15] <ubotu> pronouce is point your movie player at /usr/share/examples/example-content/experience-ubuntu.ogg
[07:55] <ubotu> In ubotu, naes said: ? where did this come from is someone here?
[07:56] <nalioth> !tell naes about bot
[08:02] <tonyyarusso> elkbuntu: ban issue?
[08:03] <mc44> tonyyarusso: you banned all chatzilla apparently :)
[08:04] <tonyyarusso> ...
[08:04] <tonyyarusso> seriously?
[08:04] <nalioth> it was tonyyarusso ?
[08:04] <tonyyarusso> nalioth: If New?Now?Know?How is all chatzilla, then yes.
 12:43 -!- 0 - #ubuntu: ban New?Now?Know?How [by tonyyarusso!n=anthony@ubuntu/member/tonyyarusso, 20691 secs ago]
[08:05] <mc44> ah yes
[08:05] <nalioth> bad tonyyarusso bad bad  :D
[08:05] <nalioth> tonyyarusso: you know that anyone who uses chatzilla ain't got the experience to use a real irc client, how do you think they'll know to change their user name in it?
[08:05] <tonyyarusso> Please excuse my ignorance of chatzilla's defaults :S
[08:06] <mc44> at least banning them might have caused some people to get a real client :)
[08:06] <tonyyarusso> nalioth: I don't - i just didn't know something that strange could be a default for anything
[08:06] <nalioth> tonyyarusso: chazilla is strange
[08:06] <tonyyarusso> indeedy
[08:07] <tonyyarusso> All right, finishing up the scrollback it seems a number of people (eventually) figured out where the blame lay, so thanks to all of them, and sorry again.
[08:07] <tonyyarusso> Meanwhile, I'm supposed to be in Woodbury in an hour, so I should be off again.
[08:30] <poningru> http://slickdeals.net/?pno=9807&lno=1&afsrc=1
[08:34] <stefg> shame on tonyyarusso
[08:35] <stefg> nalioth: btw, you owe us chatzillians an excuse for speaking low of the most usable gui irc client, don't you
[08:48] <ubotu> geser called the ops in #ubuntu-motu
[08:49] <geser> could someone please ban icf7_ from #ubuntu-motu?
[08:52] <minghua> any #ubuntu-motu ops around?
[08:52] <PriceChild> wooo LugRadio Live :P
[08:52] <joejaxx> minghua: there are only those four :\
[08:53] <joejaxx> and the are all afk it seems
[08:53] <PriceChild> and sladen is at LRL so he won't be able to do anything..
[08:53] <poningru> WTF
[08:53] <poningru> http://www.youtube.com/watch?v=g6UWUTCeRaI
[08:54] <nixternal> what is the ban forward for "fix your router"?
[08:55] <nalioth> nixternal: to #ubuntu-read-topic
[09:28] <nixternal> if you all get bitch complaints from anlar, tell him to blow it out his arse, I am awaiting a response from him for something he just pm'd me, and if I don't like it, he goes bye bye
[11:31] <Stormx2> poningru: my god.


[00:00] <Ukikie> jbicha: ...Or you could cheat and just add the provides to current debhelper, but that seems less than ideal.
[00:02] -queuebot:#ubuntu-release- Unapproved: rejected nvidia-graphics-drivers-440 [source] (focal-proposed) [440.82+really.440.64-0ubuntu4]
[00:40] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-440 (focal-proposed/restricted) [440.82-0ubuntu1 => 440.82+really.440.64-0ubuntu4] (i386-whitelist)
[00:44] <xnox> jbicha:  it was rejected.
[00:45] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (focal-proposed/main) [2.661 => 2.663] (desktop-core, i386-whitelist)
[00:45] <xnox> cjwatson:  the one thing that is not nice, is that teh VMs are "upgraded" daily
[00:45] <xnox> meaning one cannot quiete rebuild them independantly without knowing when/what they upgraded things to
[00:49] <cjwatson> TBH even just getting a list of installed package names and versions from one of those VMs would be helpful
[00:50] <xnox> git clone lp:autopkgtest-cloud
[00:50] <xnox> has ./tools/build-adt-image-all-clouds
[00:50] <cjwatson> If you can launch a VM from it do you think you could extract the output of "dpkg-query -W"?
[00:50] <cjwatson> But I'll look at that too, thanks
[00:51] <xnox> which does call from $ pull-lp-source autopkgtest => calls setup-commands/setup-testbed
[00:51] <xnox> which does a lot
[00:51] <xnox> like installing dbus & installing libpam-systemd
[00:51] <xnox> potentially triggering session auditing and what not.
[00:51] <cjwatson> dbus could well be relevant
[00:51] <xnox> cjwatson:  right, but i'm about to sleep. Will do that for you tomorrow. Unless someone beats me to it. i.e. juliank maybe.
[00:53] <xnox> also gpg is installed
[00:53] <xnox> which means that systemd- user session jobs are probably started
[00:53] <cjwatson> Thanks, me too.  Will see how far I get
[01:08] <vorlon> bdmurray: nvidia-graphics-drivers-440 now build- and install-tested; I'll self-accept after a couple of hours if no one else is available to review
[01:10] -queuebot:#ubuntu-release- Unapproved: mutter (focal-proposed/main) [3.36.1-3ubuntu2 => 3.36.1-3ubuntu3] (desktop-core, desktop-extra)
[01:35] <cjwatson> Ah, maybe I see the launchpadlib bug by zen debugging
[01:44] <cjwatson> Possibly https://code.launchpad.net/~cjwatson/launchpadlib/postpone-keyring-errors-import/+merge/382465
[05:26] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-440 [source] (focal-proposed) [440.82+really.440.64-0ubuntu4]
[05:28] <cpaelzer> cjwatson: for "exact images we use for autopkgtest" in one of such cases that I had (local  autopkgtest-buildvm-ubuntu-cloud) didn't reproduce it - someone (IIRC Laney) was able to upload the image used in the tests into canonistack
[05:28] <cpaelzer> cjwatson: that way I was able to spawn exactly what the tests used
[05:29] <cpaelzer> I read the backlog and was unsure if you got to a solution already, if you did please ignore the noise
[05:29] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (focal-proposed) [2.662]
[05:45] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (focal-proposed) [2.663]
[06:38] <seb128> does anyone know how we there is so much backlog on autopkgtest?
[06:38] <seb128> we are in freeze, it's not like we had synced half of the archive or done a python transition
[06:42] <RikMills> I guess glibc which triggers the world of tests under 'huge' is part of it?
[06:57] <seb128> rikMills, right, I guess that could be it, unfortunate that one update can DoS the infra for over a day :-/
[07:03] <RikMills> I guess at least it limits the immediate worker availability for !huge things.
[07:03]  * RikMills shrugs
[07:20] <juliank> ugh
[07:24] <juliank> Laney: Apparently we got stuck with duplicate servers again in l{cy,gw}01, so we did not get updated images for a week
[07:24] <juliank> Really gotta add some error reporting _somewhere_
[07:29] <juliank> cjwatson: So, dpkg -l on the autopkgtest image https://paste.ubuntu.com/p/NvQqMTKjGC/
[07:29] -queuebot:#ubuntu-release- Unapproved: ceph (focal-proposed/main) [15.2.0-0ubuntu2 => 15.2.1-0ubuntu1] (desktop-core, ubuntu-server)
[07:35] <juliank> I'll build some new focal images for amd64
[07:39]  * juliank accidentally overwrote the logs for the other image builds
[07:40] <juliank> lgw is exceeding quota, and hence, not building
[07:40] <juliank> trying by hand
[07:42] <juliank> So I guess modifying create-nova-image-new-release to delete any server with the same name as the one we're about to create will solve the issue
[07:42] <juliank> I think the script is exiting somewhere due to set -e and not reaching the part where it does the removing
[07:43] <juliank> Also, I hacked the script to not build i386 images on focal anymore
[07:44] -queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (focal-proposed) [3.36.1-3ubuntu3]
[07:51] <sil2100> hm, this is weird
[07:53] <sil2100> seb128: so I ran my langpack sanity tests and noticed that most of the new base refreshes are basically dropping snapd-glib.po
[07:56] <sil2100> Ah, ok, I see the translation strings are completely different now
[07:56] <sil2100> Which is why probably most languages didn't translate it
[07:56] <seb128> sil2100, right, it was not properly set for translation until yesterday :-/
[08:00] <sil2100> seb128: ACK
[08:01] <sil2100> I also see we MoinMoin.po and JabberBot.po being dropped in comparison to the last base refresh, but I suppose it's due to moin being removed from the archive
[08:01] <seb128> likely
[08:02] <sil2100> Anyway, thanks for the info, I'll start the upload process of those packs
[08:06] <Laney> juliank: hacked> please commit it
[08:06] <Laney> I'm not happy with the cowboys we're building up there
[08:10] <Laney> cjwatson: if you change log.gz in your url to artifacts.tar.gz there's a 'testbed-packages' in there which is the stuff that was preinstalled in the testbed itself, perhaps that's useful to you
[08:10] <juliank> Laney: I will
[08:11] <Laney> xlnt
[08:11] <juliank> Laney: I'm not sure what happened to the Cross-Test changes, why are they not committed?
[08:11] <Laney> there's a MP and I gave some review comments on there, but they AFAIK didn't get addressed
[08:15] <Laney> juliank: perhaps installing a 'trap' once we have an ID of an image-build instance would help
[08:15] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (focal-proposed/multiverse) [6.1.6-dfsg-1ubuntu20.04.1 => 6.1.6-dfsg-2ubuntu20.04.1] (no packageset)
[08:15] <Laney> and not referring to instances by name probably
[08:15] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-hwe [source] (focal-proposed) [6.1.6-dfsg-2ubuntu20.04.1]
[08:15] <juliank> Yeah, like trap  "openstack server delete $foo" EXIT
[08:16] <Laney> yep
[08:16] <juliank> oh well, with nova
[08:16] <Laney> I tried to make this all much more robust in the new deploymment
[08:16] <Laney> so hopefully it's better $soon
[08:17] <juliank> I feel like deleting any leftover instances before booting a new one is probably easiest, though
[08:18] <Laney> I would probably do both
[08:19] <juliank> haha I was tailing the log and wondering why it did not exit, thinking it was the process itself
[08:20] <juliank> amd64 images are uptodate now
[08:20] <juliank> Laney: Does the new one also retry? Sometimes we fail on quota and need to retry later
[08:20] <juliank> Or maybe we should fix our number of instances we use
[08:21] <Laney> check it out in wip/mojo-juju-2
[08:21] -queuebot:#ubuntu-release- Unapproved: yaru-theme (focal-proposed/main) [20.04.5 => 20.04.6] (desktop-core)
[08:21] <Laney> there's a lot of retrying going on in there
[08:21] <juliank> I think we don't account for building images in parallel to workers running tests
[08:21] <juliank> like, building the image probably should pause one worker
[08:21] <Laney> and indeed the trap that I just mentioned, forgot I did that!
[08:22] <Laney> well we don't usually run at 100% of our quota
[08:22] <Laney> because some tests require m1.large
[08:22] <juliank> ok, but it's not exactly the first time I saw a quota failure
[08:22] <juliank> ERROR (Forbidden): Quota exceeded for cores: Requested 1, but already used 30 of 30 cores (HTTP 403) (Request-ID: req-da4689aa-e861-4852-b4e3-2b8ded1af1a0)
[08:22] <Laney> yeah, it's common
[08:23] <Laney> I guess one suggestion would be to run the script more frequently - like, hourly - but have it exit 0 if the image it wants to make already exists
[08:30] -queuebot:#ubuntu-release- Unapproved: strace (focal-proposed/main) [4.26-0.2ubuntu3 => 5.5-3ubuntu1] (core) (sync)
[08:32] <wgrant> ooh
[08:32] <wgrant> rbalint: Thanks for that, makes my weekend easier.
[08:33] <rbalint> please see FFe in LP: #1873409
[08:50] -queuebot:#ubuntu-release- Unapproved: nova (focal-proposed/main) [2:21.0.0~b3~git2020041013.57ff308d6d-0ubuntu1 => 2:21.0.0~b3~git2020041013.57ff308d6d-0ubuntu2] (openstack, ubuntu-server)
[08:52] -queuebot:#ubuntu-release- Unapproved: linux-meta (focal-proposed/main) [<IP_ADDRESS>.29 => <IP_ADDRESS>.30] (core, kernel)
[08:53] -queuebot:#ubuntu-release- Unapproved: rejected linux-meta [source] (focal-proposed) [<IP_ADDRESS>.30]
[08:53] -queuebot:#ubuntu-release- Unapproved: linux-meta (focal-proposed/main) [<IP_ADDRESS>.29 => <IP_ADDRESS>.30] (core, kernel)
[08:54] <sil2100> Will approve all the langpacks in a moment
[08:55] <apw> sil2100, can i have linux-meta first :)
[08:56] <apw> else it will take hours to build :)
[08:56] <sil2100> Looking ;)
[08:58] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [source] (focal-proposed) [<IP_ADDRESS>.30]
[08:59] <sil2100> apw: ^
[08:59] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (focal-proposed) [2:21.0.0~b3~git2020041013.57ff308d6d-0ubuntu2]
[08:59] -queuebot:#ubuntu-release- Unapproved: ironic (focal-proposed/universe) [1:14.0.1~git2020041013.af9e6ba90-0ubuntu1 => 1:14.0.1~git2020041013.af9e6ba90-0ubuntu2] (openstack)
[09:00] -queuebot:#ubuntu-release- Unapproved: openmpi (focal-proposed/universe) [4.0.3-0ubuntu1 => 4.0.3-6ubuntu1] (i386-whitelist, kubuntu) (sync)
[09:06] -queuebot:#ubuntu-release- Unapproved: gnome-calendar (focal-proposed/main) [3.36.0-1 => 3.36.1-0build1] (desktop-extra, ubuntu-desktop)
[09:12] <cjwatson> Laney: testbed-packages> oh, handy,  and thanks juliank
[09:56] <cpaelzer> ubuntu-archve: hi the dbgsym seem to be out of date again
[09:56] <cjwatson> hi we're already working on it
[09:56] <apw> cpaelzer, it is known that ddebs.u.c is lagging and it is ... oh
[09:56] <cjwatson> it's not "again", it's still.  stalled on 2020-04-02 and we only noticed a couple of days ago, so it has a big backlog
[09:57] <cpaelzer> ok cjwatson apw
[09:57] <cpaelzer> from my limited POV it was "again", didn't know there was a known lag
[09:57] <cjwatson> it's about 50% through the catch-up
[09:57] <cpaelzer> ok, thanks then
[09:57] <cjwatson> 26 hours in or so
[09:57] <cpaelzer> maybe just rechecking on monday then
[09:58] -queuebot:#ubuntu-release- Unapproved: accepted yaru-theme [source] (focal-proposed) [20.04.6]
[10:15] <locutus__> any archive admin, pleeeeeeeeease remove node-run-sequence from focal see debian bug: #954832
[10:16] <locutus__> ubot5, stop saying that closed bugs are open, thanks
[10:37] <Laney> Wimpress / popey: (cc sil2100 jibel paride bdmurray): Yo ho de ho, for the release we were thinking of maintaining a 'status whiteboard' on Discourse that people can look at to find out what's going on with respins / bugs / etc. wdyt about giving us a wiki post in the announcements category that we can use for that?
[10:37] <jamespage> cpaelzer: I think I can push the jwcrypto dependency from websockify to a suggests which would take MIR pressure off this late in cycle
[10:37] <jamespage> testing now
[10:38] <Wimpress> Laney, that's a great idea.
[10:38] <paride> Laney, +1
[10:38] <philroche> Laney: I'm happy to contribute to that dashboard for cloud images
[10:39] <Wimpress> Do you want a reserved wiki post now Laney?
[10:39] <Laney> philroche: nice, ok
[10:39] <Laney> Wimpress: Yeah, that'd work
[10:39] <Laney> if you can make it so that all of those CCed people + philroche can edit
[10:39] <Laney> it
[10:40] <Wimpress> popey: Can we get together in a bit and set that up? 👆
[10:41] <jamespage> cpaelzer: yep lgtm
[10:43] -queuebot:#ubuntu-release- Unapproved: websockify (focal-proposed/main) [0.9.0-0ubuntu1 => 0.9.0-0ubuntu2] (ubuntu-server)
[10:43] <jamespage> please can ^^ and the ironic upload I did today be accepted - they should unblock ubuntu-openstack proposed-migration blocks
[10:44] <rbalint> sil2100, could strace go in today?
[10:48] <sil2100> rbalint: ouch, that's a big jump
[10:49] <Laney> indeed it is
[10:49] <Laney> final freeze ...
[10:50] <sil2100> I need to think about it, as this doesn't make me feel very happy
[10:50] <rbalint> Laney, sil2100: indeed, it is, please see the FFe
[10:52] <rbalint> i'm not sure how far we are from building riscv64 images, but strace is a blocker, i believe
[10:54] <sil2100> rbalint: just for the record: did you look at if it's easy to identify which changes would make the test passing on riscv64? Or would that be hard to determine with all the changes?
[10:55]  * Laney hasn't heard anything about images
[10:55] <jamespage> and also the ceph 15.2.1 point release - it includes important upgrade and security fixes :)
[10:55] <Laney> I think I lean towards saying that this should be moved to an SRU
[10:55] <sil2100> I mean, I wouldn't mind pulling this into focal in principle somewhen, but doing it so late in the cycle is bad, this has a lot of behavior changes
[10:56] <rbalint> sil2100, it seems hard, i have not looked (for 5.5)
[10:57] <Laney> then (1) no risk to the focal release, (2) can have explicit verification and it can be rolled back if necessary
[10:57] <rbalint> Laney, how would verification look like?
[10:58] <Laney> You tell me
[10:58] <Laney> how does verification of *this* look like?
[10:58] <rbalint> Laney, builds and autopkgtests
[10:59] <rbalint> Laney, i'm fine with postponing it to focal+1
[11:00] <rbalint> Laney, interested people can sru later
[11:00] <wgrant> strace, being mostly a debugging tool, seems relatively low risk to the release in general. It also doesn't have a massive history of regressions. But yes, big jump.
[11:01] <rbalint> yes, imo is it is very low risk, but having old strace in focal missing syscalls is very annoying
[11:02] <rbalint> we never had an strace sru/security update per rmadison
[11:02] <juliank> just add the syscalls?
[11:03] <popey> Wimpress sure thing
[11:03] <rbalint> juliank, if someone else is interested i would not block her/him, but i'm not interested at all doing it , rather use strace from a ppa
[11:05] <rbalint> how about having strace in -proposed but not letting it in until after the release? then riscv64 bootstrap can continue
[11:05] <sil2100> I think this might be an option
[11:06] <Laney> sounds possible
[11:06] <sil2100> It's unlikely we'd have to do any release-blocking hotfixes for strace
[11:06] <wgrant> I need to drop -proposed from the chroots for at least a bit to finish the haskell and rust trees because -proposed is a bit of a mess, but yeah, makes sense
[11:07] <Laney> So we've definitely had strace being the cause of build failures / autopkgtest failures (more so these) in the past
[11:07] <sil2100> Oh, we did?
[11:07] <Laney> It's the kind of thing that I don't want to risk us having with not much time to get things aligned
[11:07] <Laney> it should be ok in -proposed for the autopkgtest side, as this strace won't be pulled in unless requested
[11:08] <rbalint> Laney, the test rebuilds and bileto tests should have minimized the potential disruption
[11:08] <sil2100> Yeah, +1 - guess it would be easiest if we had the bug number attached in the changelog
[11:08] <Laney> yeah but we know that we only catch first level regressions by these methods
[11:08] <sil2100> Though I guess I can just do a block hint for it
[11:08] <Laney> that's most of our problems in autopkgtest-land
[11:09] <Laney> anyway I think blocking is ok
[11:09] <Laney> if we do hit problems, it can always be removed then
[11:09] <sil2100> Laney: I'll look at the diff, add a block hint and accept
[11:09] <Laney> nod
[11:09] <rbalint> sil2100, thanks!
[11:14] <jbicha> ubuntu-archive please take a look at removal requests bug 1872598 and bug 1872593
[11:17] -queuebot:#ubuntu-release- Unapproved: horizon (focal-proposed/main) [3:18.2.1~git2020041013.754804667-0ubuntu1 => 3:18.2.1~git2020041013.754804667-0ubuntu2] (openstack, ubuntu-server)
[11:20] <Laney> sil2100: so about the discourse thing, some of the sections on the release document should move over there I think
[11:20] <sil2100> Laney: ah, the discourse thread?
[11:21] <sil2100> For release?
[11:21] <Laney> yeah
[11:21] -queuebot:#ubuntu-release- Unapproved: pepperflashplugin-nonfree (focal-proposed/multiverse) [1.8.4ubuntu2 => 1.8.6ubuntu1] (no packageset)
[11:21] <Laney> status summary / current blockers / bugs to watch ?
[11:21] -queuebot:#ubuntu-release- Unapproved: accepted pepperflashplugin-nonfree [source] (focal-proposed) [1.8.6ubuntu1]
[11:22] <Laney> if you agree, I'll do that and add a link once the post is created
[11:23] <sil2100> Laney: +1 on that - did you create that thread already? Could you paste the link once you have it?
[11:23] <Laney> see ^ - Wimpres_s and pope_y are on it
[11:23] <sil2100> This will be something new for me as I never was a discourse person ;)
[11:24] <Laney> ah, you can have 'wiki posts', so it'll not be too un-familiar for you
[11:25] -queuebot:#ubuntu-release- Unapproved: accepted strace [sync] (focal-proposed) [5.5-3ubuntu1]
[11:25] <sil2100> jamespage: holy shit 9MB of diff for ceph
[11:30] -queuebot:#ubuntu-release- Unapproved: neutron (focal-proposed/main) [2:16.0.0~b3~git2020041516.5f42488a9a-0ubuntu1 => 2:16.0.0~b3~git2020041516.5f42488a9a-0ubuntu2] (openstack, ubuntu-server)
[11:31] <sil2100> jamespage: the changelog in the diff has much more changes than the ones listed on the diff - whyyy is this so late
[11:33] <sil2100> eh, let me try that again
[11:33] <sil2100> jamespage: the changelog in the diff has much more changes than the ones listed on the bug - whyyy is this so late
[11:34] <jamespage> sil2100: sorry which one?
[11:34] <sil2100> jbicha: looking at some of those in a moment
[11:34] <jamespage> the ceph diff?
[11:39] <jamespage> sil2100: do you mean the list in doc/releases/octopus.rst ? I think upstream did a catchup in the docs from the 15.1.0 beta release between 15.2.0 and 15.2.1
[11:40] <jamespage> sil2100: this point release only appeared this week and it takes me a while to validate due to build times
[11:53] -queuebot:#ubuntu-release- Unapproved: cinnamon (focal-proposed/universe) [4.4.8-3 => 4.4.8-4] (no packageset) (sync)
[11:53] -queuebot:#ubuntu-release- Unapproved: accepted cinnamon [sync] (focal-proposed) [4.4.8-4]
[12:00] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (focal-proposed) [3:18.2.1~git2020041013.754804667-0ubuntu2]
[12:00] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (focal-proposed) [2:16.0.0~b3~git2020041516.5f42488a9a-0ubuntu2]
[12:00] -queuebot:#ubuntu-release- Unapproved: accepted ironic [source] (focal-proposed) [1:14.0.1~git2020041013.af9e6ba90-0ubuntu2]
[12:00] -queuebot:#ubuntu-release- Unapproved: pdfchain (focal-proposed/universe) [1:<IP_ADDRESS>-1build1 => 1:<IP_ADDRESS>-2] (no packageset) (sync)
[12:01] -queuebot:#ubuntu-release- Unapproved: accepted pdfchain [sync] (focal-proposed) [1:<IP_ADDRESS>-2]
[12:01] -queuebot:#ubuntu-release- Unapproved: balsa (focal-proposed/universe) [2.5.9-4 => 2.6.0-2] (no packageset) (sync)
[12:02] -queuebot:#ubuntu-release- Unapproved: accepted balsa [sync] (focal-proposed) [2.6.0-2]
[12:06]  * sil2100 AFK for lunch
[12:17] <Wimpress> Laney: Re: release wiki post on Discourse. Do you want people to be able to comment?
[12:17] <Laney> Wimpress: ideally not, we don't want to be replying there really
[12:19] <kanashiro> could someone please take a look at this MP to unblock mysql-8.0? https://code.launchpad.net/~lucaskanashiro/britney/hint-update-mysql-connector-c++/+merge/382246
[12:28] -queuebot:#ubuntu-release- Unapproved: openjdk-lts (focal-proposed/main) [11.0.7+10-2ubuntu1 => 11.0.7+10-3ubuntu1] (core, i386-whitelist) (sync)
[12:30] -queuebot:#ubuntu-release- Unapproved: openjdk-8 (focal-proposed/universe) [8u252-b09-1 => 8u252-b09-1ubuntu1] (i386-whitelist) (sync)
[12:34] <Wimpress> Laney: Here's your topic - https://discourse.ubuntu.com/t/focal-fossa-final-release-status-tracking/15366
[12:34] <Wimpress> Release team members have write access to that category.
[12:34] <Wimpress> When that post has something in it, I will pin it.
[12:35] <Laney> Wimpress: Ta duck
[12:42] <Laney> ooh
[12:42] <Laney> it copies from google docs with proper formatting
[12:47] <Laney> ok filled out with some initial content
[12:47] <Wimpress> Great.
[12:48] <Laney> sil2100: want to check you can edit that?
[12:49] <Wimpress> sil2100: I could not find you in Discourse. So let me know your username.
[12:50] <Wimpress> Laney: Post globally pinned until 23:59 on April 24th.
[12:51] <Laney> 😎
[12:51] <Laney> Wimpress: popey:: Another idea for that category might be a post with some links giving people info on how to contribute to the release (testing), then I could link to it from the top of this wiki post
[12:52] <Laney> Or maybe in the Quality category and we link to that as a place for testers to gather
[12:53] <Laney> (if you like, just edit the release post and add a short sentence linking people to where you want them to go)
[12:57] <popey> Knock yourself out :D
[12:59] <Laney> sorry, to remove that doubt, I'm suggesting but not volunteering to write that content I'm afraid :-)
[13:10] -queuebot:#ubuntu-release- Unapproved: stress-ng (xenial-proposed/universe) [0.05.23-1ubuntu3 => 0.05.23-1ubuntu4] (no packageset)
[13:21] <jibel> Laney, there is this post which already links to testing resources and daily builds https://discourse.ubuntu.com/t/testing-ubuntu-20-04-lts-official-ubuntu-flavors/14053
[13:26] <tjaalton> Laney: hey, did you see my updates to the vulkan ffe?
[13:40] <sil2100> Laney: thanks! Let me first try logging in
[13:41] <sil2100> Laney, Wimpress: ok, I actually didn't even have an account - I have now created it
[13:42] <sil2100> Wimpress: can you try adding me now?
[13:54] <philroche> Wimpress: Should I be able to edit that post directly to update cloud image status? I don't seem to have perms to do so .. or is it pulling the updates from elsewhere?
[13:55] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-8 [sync] (focal-proposed) [8u252-b09-1ubuntu1]
[13:55] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-lts [sync] (focal-proposed) [11.0.7+10-3ubuntu1]
[14:12] <apw> sil2100, you ok with an update to the oem-5.6 kernel ?
[14:13] <sil2100> ...we don't have it on any images now, right?
[14:13] <Laney> sure we do
[14:14] <xnox> apw:  i will upload ubiquity in a moment..... so yeah, they will respin.
[14:14] <xnox> Laney:  sil2100: vorlon: paride reports that ssh -i /var/lib/jenkins/.ssh/cdimage<EMAIL_ADDRESS>'/srv/cdimage.ubuntu.com/bin/mark-current -p ubuntu-server -s focal -t legacy-server -a amd64 20200417'
[14:14] <xnox> fails
[14:15] <xnox> when i run something similar, on my local machine..... it works.
[14:15] <xnox> is there something missing? like clearing out the old 'focal-server-arm64.iso' from current & pending?
[14:15] <xnox> or rather is stray published
[14:15] <paride> xnox, did you try with "-t legacy-server" ?
[14:16] <xnox> paride:  yes.
[14:16] <sil2100> xnox: let me run that on nusakan and see how it fails
[14:16] <xnox> Laney:  sil2100: vorlon: I think it is bad that "server" builds are listed on http://cdimage.ubuntu.com/ubuntu-server/daily/current/ together with "legacy-server" builds.
[14:16] <xnox> paride:  but my local deployment has no "server.iso" builds.
[14:16] <paride> sil2100, https://paste.ubuntu.com/p/m9cqKMmxjK/
[14:16] <sil2100> huh
[14:17] <paride> sil2100, note that is was passed "-a amd64" but still looks for an arm64 image
[14:17] <sil2100> Need to see what current is right now, as I purged the old images from the latest publish directory
[14:18] <sil2100> paride, xnox: I think I see the reason
[14:19] <sil2100> paride: can you try now?
[14:19] <apw> xnox, so are you happier if i drop it in now, rather than waiting ?
[14:20] <xnox> sil2100:  the tree looks better!
[14:20] <xnox> apw:  yeah, but oem kernel respins are cheap. It is only on the /pool => such that we can rebuild desktop iso, without rebuilding livefs.
[14:20] <sil2100> xnox: yeah, stupid current was a mixture of different publish sets, and some were actually invalid symlinks because of my earlier purge
[14:20] <xnox> apw:  it simply would redownload the old squashfs, and redo debian-cd add packages to the pool.
[14:20] <xnox> apw:  ditto e.g. nvidia-*
[14:21] <apw> xnox, ok then i will dump it in
[14:21] <xnox> sil2100:  ful!
[14:21] <xnox> sil2100:  fun!
[14:21] <sil2100> apw: yeah, throw it at us
[14:21] <apw> sil2100, if you are in agreement
[14:21] <Laney> apw: you know you're not talking to a release team member for these acks right
[14:21]  * Laney sees sneaky xnox
[14:21] <sil2100> ;)
[14:21] <apw> Laney, which is why i am deferring to sil2100  :)
[14:22] <sil2100> Oh, actually apw is a release team member, so he can ACK himself?!
[14:22] <apw> sil2100, but one should not really count ones own ack in this context me thinks
[14:22] <Laney> ok good
[14:22] <paride> sil2100, mark-current -p ubuntu-server -s focal -t legacy-server -a amd64 20200417: success
[14:22] <Laney> what is this new oem kernel for, out of interest?
[14:22] <paride> thanks!
[14:22] <apw> Laney, fixes for graphics and the like for supported platforms
[14:24] <apw> Laney, and we get to make one last choice with britney yet
[14:24] <sil2100> Laney: here's the changes file: https://launchpadlibrarian.net/474833166/linux-oem-5.6_5.6.0-1008.8_source.changes
[14:25] <apw> by our standards tiny
[14:25] <sil2100> I'd prefer not having a new release of that, but the GPU fixes sound legit...
[14:28] <Laney> fair enough
[14:28] <Laney> I was expecting it to be revved along with the GA kernel on that cadence but I just assumed that
[14:29] <Laney> guess we're considering that kernel freeze only applies to the default kernel
[14:30] -queuebot:#ubuntu-release- Unapproved: dbus-c++ (focal-proposed/universe) [0.9.0-8.1build1 => 0.9.0-8.1ubuntu1] (i386-whitelist, ubuntustudio)
[14:30] <apw> Laney, it is a newer base, so yeah.  but we can hold this in -proposed and release it after too
[14:31] -queuebot:#ubuntu-release- Unapproved: atk1.0 (focal-proposed/main) [2.35.1-1ubuntu1 => 2.35.1-1ubuntu2] (core, i386-whitelist)
[14:34] <Laney> nod
[14:37] -queuebot:#ubuntu-release- Unapproved: accepted dbus-c++ [source] (focal-proposed) [0.9.0-8.1ubuntu1]
[14:37] -queuebot:#ubuntu-release- Unapproved: accepted websockify [source] (focal-proposed) [0.9.0-0ubuntu2]
[14:37] -queuebot:#ubuntu-release- Unapproved: accepted atk1.0 [source] (focal-proposed) [2.35.1-1ubuntu2]
[14:38] <sforshee> sil2100, Laney: fyi I'm respining the kernel for a couple of install-related issues
[14:38] <sforshee> just the primary kernel, no derivatives
[14:40] <Laney> sforshee: ok, eta?
[14:40] <sforshee> Laney: I'm test building now, should upload within the hour
[14:41] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (eoan-proposed/main) [5.3.0-1020.21] (core, kernel)
[14:42] <sil2100> sforshee: thanks for the heads up o/
[14:42] <Laney> probably be spinning images later than my normal EOD then!
[14:43] <bdmurray> remember there's somebody in a different TZ who can help! ;-)
[14:43] <sforshee> sil2100, Laney: we usually use a build ppa, would be eaiser this time if I just upload to -proposed instead?
[14:43] <sforshee> *would it
[14:44]  * apw would lean to the PPA as it gives us one more chance to not take it
[14:45] <sil2100> sforshee: let's keep the PPA approach
[14:45] <sforshee> ack
[14:45] <sil2100> We already recommended that for other bigger things
[14:45] <Laney> yeah it doesn't add much delay
[14:46] <sil2100> And we can deal with bin-sync in such cases, since we're expecting those and know where to look
[14:47] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (eoan-proposed) [5.3.0-1020.21]
[14:50] -queuebot:#ubuntu-release- Unapproved: collectd (focal-proposed/universe) [5.9.2.g-1ubuntu4 => 5.9.2.g-1ubuntu5] (no packageset)
[14:50] <sil2100> I'm pushing some NBS fixes if anything ^
[14:51] -queuebot:#ubuntu-release- Unapproved: accepted collectd [source] (focal-proposed) [5.9.2.g-1ubuntu5]
[14:51] <sil2100> Only few more left \o/
[15:04] <sforshee> new kernel is building, should be done in ~8 hours
[15:09] <xnox> Laney:  https://paste.ubuntu.com/p/vZX45YS8fB/
[15:09] <xnox> Laney:  so, should i just upload this, or do i need to explain my head bashing aobut this?
[15:11] <Laney> xnox: If you have more explanation, put it in the changelog itself so that future students can study your thoughts
[15:15] <bdmurray> jibel: Have you looked at these upgrade (automatic testing) failures at all?
[15:20] -queuebot:#ubuntu-release- Unapproved: automake-1.15 (focal-proposed/universe) [1:1.15.1-5ubuntu1 => 1:1.15.1-5ubuntu2] (no packageset)
[15:21] -queuebot:#ubuntu-release- Unapproved: accepted automake-1.15 [source] (focal-proposed) [1:1.15.1-5ubuntu2]
[15:45] <sil2100> cjwatson, stgraber: hey guys, need a quick opinion about something: I want to get rid of the last thing from the NBS report - basically the whole libopencl-clang-dev libopencl-clang9 libllvmspirvlib9 chain - basically both libllvmspirvlib9 and libopencl-clang9 can be safely removed as this is all caused by a dangling old version of libopencl-clang-dev (9.0.0-1build1)
[15:46] <sil2100> cjwatson, stgraber: so I'm wondering, why is libopencl-clang-dev both 10.0.0-2 and 9.0.0-1build1 visible still? There is no reverse-dependency explicitly depending on the old version, so I'd assume the binary should be superseeded and no longer visible
[15:46] <sil2100> Should I also remove the 10.0.0-2 libopencl-clang-dev binary package manually in this case?
[15:46] <sil2100> eh, I mean, remove 9.0.0-1build1
[15:47] <sil2100> Or will everything go fine when I simply remove the chain of libopencl-clang9 and libllvmspirvlib9 ? I guess maybe that's holding it in somehow
[15:48] <locutus__> the clang approach for NBS stuff is usually do it an cross fingers :D
[15:50] <locutus__> in this case, they are not provided by llvm-defaults, so you should be good to let them go, I'm not even sure why they existed in first place, maybe some sync from experimental
[15:51] <locutus__> oh indeed, they are not provided by llvm-* so meh
[15:51] <cjwatson> libopencl-clang-dev is Architecture: all, so LP conservatively keeps it around as long as any arch-dependent binaries from the same source and version are still active
[15:51] <sil2100> cjwatson: oh!
[15:51] <cjwatson> you shouldn't need to remove it manually
[15:52] <sil2100> cjwatson: ok, so it will resolve itself once I remove the other two, thanks! Yeah, this makes total sense
[15:52] <cjwatson> it'll be automatically superseded by the dominator once the other binaries are gone
[15:52] <cjwatson> right
[15:52] <locutus__> Package: libopencl-clang-dev
[15:52] <locutus__> Architecture: amd64 i386
[15:52] <locutus__> not anymore fortunately
[15:52] <cjwatson> right, it was arch: all at version 9.0.0-1build1
[15:52] <locutus__> yep :)
[15:53] <locutus__> also debian tracker is confused by it
[15:55] <sil2100> Thanks guys
[15:55] <sil2100> Ok, so hopefully when stuff migrates, we'll be able to remove the last NBS binaries and we'll have a clean report
[15:57] <Laney> sil2100: next: focal_uninst.txt :-)
[15:59] <sil2100> :(
[16:08] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (focal-proposed/main) [2.663 => 2.664] (desktop-core, i386-whitelist)
[16:10] <rcj> Could I get a review of livecd-rootfs in the queue?
[16:28] <sil2100> Wimpress: hey! Can you give me the powers now to edit that post? ;)
[16:28] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (focal-proposed) [2.664]
[16:31] <sil2100> jamespage: ok, looking at ceph now again
[16:32] <sil2100> jamespage: so as said the diff is huge, 9MB, and I guess I see a lot of huge directories being added - just wanted to make sure that's correct
[16:32] <Laney> xnox: you going to upload that soon?
[16:32] <Laney> please close bug #1873434 when you do
[16:33] <xnox> Laney:  yes.
[16:33] <sil2100> jamespage: there's like src/rocksdb added and src/civetweb and those seem to have like super a lot of source files
[16:33] <Laney> merci merci
[16:33] <jamespage> sil2100: reviewing now
[16:34] -queuebot:#ubuntu-release- Unapproved: ubiquity (focal-proposed/main) [20.04.13 => 20.04.14] (core)
[16:35] -queuebot:#ubuntu-release- Unapproved: ubuntu-meta (focal-proposed/main) [1.448 => 1.449] (core)
[16:35] <xnox> paride:  did things work, or not?
[16:36] <xnox> paride:  sil2100: should sil2100 mark all latests builds as current himself? cause then he will see what's broken
[16:37] <xnox> sil2100:  can you please ./bin/mark-current for -t legacy-server for 20200417 for all 4 arches?
[16:37] <xnox> Laney:  ubiquity uploaded
[16:38] <Laney> xnox: R O C K O N
[16:38] <paride> yes xnox it works now, but for the other archs the jobs still have to run. UTAH needs to be rebuilt
[16:38] <paride> but the promotion worked
[16:39] <xnox> paride:  ah cool!
[16:39] <xnox> sil2100:  unping
[16:40] <sil2100> ;)
[16:43] -queuebot:#ubuntu-release- Unapproved: rejected gnome-calendar [source] (focal-proposed) [3.36.1-0build1]
[16:47] <jamespage> sil2100: leave it with me - I had a load of exclusions in d/copyright that have somehow got dropped between 15.2.0 and 15.2.1
[16:47] <jamespage> hence the stupid diff
[16:51] <Laney> xnox: no idea how having "${OEM_KERNEL}" there causes the default kernel to remain installed
[16:51] <Laney> voodoo
[16:52] <jamespage> sil2100: would you like to reject that version and I'll have another run at it...
[16:54] <sil2100> jamespage: ok o/
[16:55] <sil2100> jamespage: rejected, give me a poke when you re-upload o/
[16:55] -queuebot:#ubuntu-release- Unapproved: rejected ceph [source] (focal-proposed) [15.2.1-0ubuntu1]
[16:58] <jamespage> me listens to xz running his fans hard
[16:59] <bdmurray> Shouldn't we just stop listing Eoan as active on the isotracker?
[17:11] -queuebot:#ubuntu-release- Unapproved: python-launchpadlib (focal-proposed/main) [1.10.11-1 => 1.10.12-1] (core) (sync)
[17:13] <cjwatson> ^- should fix autopkgtests
[17:16] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (focal-proposed) [1:4.0.2-0ubuntu1]
[17:16] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (focal-proposed) [20.04.14]
[17:16] -queuebot:#ubuntu-release- Unapproved: accepted python-launchpadlib [sync] (focal-proposed) [1.10.12-1]
[17:16] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (focal-proposed) [1.449]
[17:24] <Laney> bdmurray: ok I updated the discourse with the packages that I think we should wait for before spinning
[17:24] <Laney> going now
[17:24] <bdmurray> Laney: ack, thanks!
[17:26] <philroche> bdmurray: Laney: Wimpress: Can CPC team have edit access to the post too  so we can update cloud image build progress? myself and rcj if possible.
[17:34] <sil2100> Laney: o/
[17:37] <Laney> philroche: can't help with that, sorry
[17:37] <Laney> bdmurray: sil2100: btw there's an autopkgtest backlog and quite a few things waiting in proposed
[17:38] -queuebot:#ubuntu-release- Unapproved: virt-manager (focal-proposed/universe) [1:2.2.1-3ubuntu1 => 1:2.2.1-3ubuntu2] (no packageset)
[17:38] -queuebot:#ubuntu-release- Unapproved: accepted virt-manager [source] (focal-proposed) [1:2.2.1-3ubuntu2]
[17:41] <Laney> we're probably going to want to make a call on remaining things on monday, and I guess punt some of them to SRUs
[17:48] -queuebot:#ubuntu-release- Unapproved: virtualbox (focal-proposed/multiverse) [6.1.6-dfsg-1 => 6.1.6-dfsg-2] (ubuntu-cloud) (sync)
[17:56] -queuebot:#ubuntu-release- New binary: linux-signed-oem-5.6 [amd64] (focal-proposed/main) [5.6.0-1008.8] (no packageset)
[18:03] <sil2100> Laney: yeah
[18:31] -queuebot:#ubuntu-release- Unapproved: spirv-headers (focal-proposed/universe) [1.5.1-4 => 1.5.1+git20200409-1] (i386-whitelist) (sync)
[18:31] -queuebot:#ubuntu-release- Unapproved: spirv-tools (focal-proposed/universe) [2020.1-2 => 2020.2-1] (i386-whitelist) (sync)
[18:31] -queuebot:#ubuntu-release- Unapproved: vulkan-loader (focal-proposed/main) [<IP_ADDRESS>-1 => <IP_ADDRESS>-2] (desktop-core, i386-whitelist) (sync)
[18:31] <tjaalton> synced these ^ back for the ffe
[19:10] <jamespage> sil2100: OK re-uploading - I think I've got it right now...
[19:10] <jamespage> (ceph that is)
[19:12] -queuebot:#ubuntu-release- Unapproved: ceph (focal-proposed/main) [15.2.0-0ubuntu2 => 15.2.1-0ubuntu1] (desktop-core, ubuntu-server)
[19:16] <cjwatson> Bah, http://autopkgtest.ubuntu.com/packages/p/python-launchpadlib/focal/amd64 still failing.  Not sure I'll manage to cram this into focal now :-/
[19:16] <cjwatson> ddstreet: ^- FYI
[20:04] -queuebot:#ubuntu-release- Unapproved: lxd (focal-proposed/universe) [1:0.8 => 1:0.9] (edubuntu, ubuntu-server)
[20:04] <stgraber> ^ this is a tiny change but apparently quite critical for LTS to LTS upgrade on WSL
[20:04] <stgraber> (the lxd deb isn't seeded, this is used during upgrades only to switch over to the snap)
[20:45] -queuebot:#ubuntu-release- Unapproved: lxcfs (focal-proposed/universe) [4.0.2-0ubuntu1 => 4.0.3-0ubuntu1] (edubuntu)
[20:46] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (focal-proposed) [4.0.3-0ubuntu1]
[20:47] <matlock> ^lxd We discovered in testing under some circumstances a user who upgraded from 16.04 to 18.04 and then upgrades to 20.04 on WSL would have their upgrade stall and could leave them with a broken system. This patch better handles that scenario. https://bugs.launchpad.net/ubuntuwsl/+bug/1862550
[21:01] <rbalint> vorlon, could you please merge https://code.launchpad.net/~rbalint/britney/hints-ubuntu/+merge/382530 for glibc? the rest seems just flakiness
[21:11] <xnox> matlock:  ok.... do you have a question?
[21:11] <xnox> matlock:  did you want to open a bugtask against "lxd" package in Ubuntu project for the focal series?
[21:15] <vorlon> rbalint: done
[21:17] <xnox> matlock:  nevermind, i see the request from stgraber now.
[22:16] -queuebot:#ubuntu-release- Unapproved: update-manager (focal-proposed/main) [1:20.04.7 => 1:20.04.9] (core)
[22:47] -queuebot:#ubuntu-release- New sync: gnome-shell-extension-dashtodock (focal-proposed/primary) [67+git20200225-1]
[22:51] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-workspaces-to-dock (focal-proposed/universe) [52-1 => 52+git20200318-1] (no packageset) (sync)
[22:51] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-workspaces-to-dock [sync] (focal-proposed) [52+git20200318-1]
[22:52] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (focal-proposed) [1:20.04.9]
[22:55] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-system-monitor (focal-proposed/universe) [38-2 => 38+git20200414-32cc79e-1] (no packageset) (sync)
[22:55] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-system-monitor [sync] (focal-proposed) [38+git20200414-32cc79e-1]
[23:05] -queuebot:#ubuntu-release- Unapproved: valentina (focal-proposed/universe) [0.6.1~dfsg-9build1 => 0.6.1~dfsg-10] (no packageset) (sync)
[23:05] -queuebot:#ubuntu-release- Unapproved: accepted valentina [sync] (focal-proposed) [0.6.1~dfsg-10]
[23:48] -queuebot:#ubuntu-release- Unapproved: accepted ceph [source] (focal-proposed) [15.2.1-0ubuntu1]