[11:35] <jamespage> if there are any archive admins around, the three neutron-* packages I just uploaded to the vivid NEW queue are refactorings of drivers out of the core neutron codebase, two involve moving binary packages as well - 1:2015.1~b1-0ubuntu4 of neutron drops these from the neutron source package.
[11:36] <jamespage> coreycb, zul: fyo ^^
[16:04] <arges> mlankhorst: hey. I see two xserver-xorg-vide-intel packages uploaded into trusty. Can you confirm if I should reject the older upload and only review the newer one? Thanks
[16:05] <mlankhorst> reject older I think
[16:05] <mlankhorst> *checks*
[16:06] <mlankhorst> yeah
[16:06] <arges> mlankhorst: thanks
[19:21] <ogra_> stgraber, are there any known issues with the importer, it seems to take really long for the last touch image (the rootfs finished over 1h ago) i see it running when i check the processlist on nusakan though
[19:21] <stgraber> ogra_: yep, it was broken, I fixed the bug about 20min ago, so it must be running for good now
[19:22] <ogra_> ah. perfect, thanks !
[21:23] <tkamppeter> bdmurray, hi
[21:24] <bdmurray> tkamppeter: hello
[21:24] <tkamppeter> bdmurray, I got a mail about a possible s-c-p regression from some error report bot which you are running.
[21:26] <tkamppeter> bdmurray, looking into the tracebacks of these crashes they happen at places which I did not change, which did not change for long time, so they seem unrelated to the update. What do I have to do?
[21:26] <bdmurray> tkamppeter: I can override those but this looks new - https://errors.ubuntu.com/problem/d2a942520573c92c3250978db9ff5c8fee2962ed
[21:27] <bdmurray> tkamppeter: and https://errors.ubuntu.com/problem/ace34f647267a4452d4ccc0d603a1e7bb9d6fbc2
[21:32] <tkamppeter> The first one seems to be caused that a _query_jockey() call tries to access the discontinued Jockey. Strange is here that this bug did not get hit earlier.
[21:34] <tkamppeter> One would need to know which printer(s) these users have so that one can run the driver queries for them. Seems that making the driver queries working reveals some bugs which were hidden behind the broken driver query part.
[21:34] <bdmurray> Wasn't the SRU related to downloading printer drivers?
[21:35] <tkamppeter> bdmurray, yes.
[21:35] <bdmurray> the individual crashes should have some information to help out
[21:35] <tkamppeter> bdmurray, driver package download via OpenPrinting query did not work. This I have fixed and made available as an SRU.
[21:39] <tkamppeter> I am looking in one of the crash reports now, it does not contain info about which preinter the user tried to add. I would like to ask the user what he did, bnut it seems that the reports are anonymizes.
[21:42] <tkamppeter> I would either need tyo be able to reproduce the bug or to interact with a user suffering the bug to be able to fix it.
[21:46] <bdmurray> mightn't it be in lsusb?
[21:47] <bdmurray> Lsusb
[21:47] <bdmurray> Bus 001 Device 003: ID 04b8:08ae Seiko Epson Corp.
[21:52] <tkamppeter> Yes, this is already a hint, but also not perfect, as Epson does not have PIDs for each printer model. One even knows at least that it probably happens for printers which are supported by a downloadable driver.
[21:53] <tkamppeter> This means that most people are unaffected, but people with a supported printer are not able to get the driver in all cases. Some will get it some will hit this bug.
[22:00] <bdmurray> this support was also added to 15.04?


[08:32] <shang__> bigjools: ping, curious if the new maas has been backported to 12.04 yet?
[09:23] <bigjools> shang__: you'll have to ask roaksoax, he's sorting that out
[09:24] <shang__> bigjools: thanks
[09:24] <shang__> roaksoax: thoughts? :)
[10:03] <dholbach> hiya
[10:03] <dholbach> can somebody reply to https://code.launchpad.net/~racb/ubuntu/precise/squid-deb-proxy/cloud-archive/+merge/142088 or let me know if bug 1087145 can be closed?
[11:23] <dholbach> hey rbasak
[11:24] <dholbach> I asked this earlier - maybe you can help:
[11:24] <dholbach> can somebody reply to https://code.launchpad.net/~racb/ubuntu/precise/squid-deb-proxy/cloud-archive/+merge/142088 or let me know if bug 1087145 can be closed?
[11:24] <dholbach> (trying to get the sponsoring queue cleaned up)
[11:24]  * rbasak looks
[11:26] <rbasak> dholbach: we've had the discussion on conffile updates in SRUs now, and my understanding is that we can do it here if needed. Daviey thought an SRU to Precise was appropriate for this which is why I prepared the merge. But I don't have permissions to create that sort of bug task. Daviey, do you think we still need this?
[11:26] <rbasak> ^^
[11:26] <dholbach> rbasak, did you see mvo's response in the merge proposal?
[11:27] <rbasak> Yes
[11:27] <dholbach> ok
[11:27] <dholbach> thanks :)
[11:27] <rbasak> The issue is that MAAS users in Precise are presumably affected, hence the desire for an SRU
[11:28] <dholbach> sure
[13:11] <roaksoax> dholbach: cold u please assing the bug to me :)
[13:11] <roaksoax> shang__: soon after we fix few moew issues
[13:11] <dholbach> done
[13:12] <roaksoax> dholbach: thanks ;)
[17:06] <roaksoax> rvba: howdy
[17:06] <roaksoax> how can we delete all nodes from maas (without accessing the shell)
[17:09] <allenap> roaksoax: I shall attempt to help! Do you mean from the web UI?
[17:10] <roaksoax> allenap: from anywhere (just looking for a user friendly)
[17:11] <allenap> roaksoax: Right, so "without accessing the shell" means "no hackery", so maas-cli is okay. Let me see...
[21:24] <roaksoax> bigjools: ping
[23:39] <bigjools> roaksoax: yo


[00:34] <bryceh> hmm, question
[00:35] <bryceh> we have mesa 9.x in the mesa9 ppa
[00:35] <bryceh> for precise
[00:35] <bryceh> can we just do the same change to make that mesa Recommends on s2tc and have that get pulled in from precise's universe?
[00:36] <bryceh> or would that ppa mesa need s2tc to be in main as well?
[00:36] <RAOF> That'll work fine.
[00:36] <RAOF> The main-must-be-closed-under-transitive-dependencies rule is just policy.
[00:39] <bryceh> ok, suspected so
[00:39] <bryceh> RAOF, so if the user has only main enabled, and installs this ppa, they'll get prompted to enable universe or some such automatically?
[00:40] <RAOF> Hm. No, they won't.
[00:40] <RAOF> How many people don't have universe enabled? It's been enabled by default for a while, right?
[00:40] <bryceh> I suppose we could just stick s2tc into the ppa
[00:40] <RAOF> That would also work.
[00:40] <bryceh> no clue
[00:42] <bryceh> ok anyway, fixable problem.
[04:03] <tjaalton> i guess torchlight needs s2tc, resolution got changed to 720x400 but the game didn't start
[04:03] <tjaalton> on ivb
[04:09] <tjaalton> nope, still crashes
[04:14]  * bryceh eod's
[06:21] <tjaalton> RAOF: so, are we getting a newer ati snapshot? this would probably be the last time to decide :)
[06:21] <RAOF> We should.
[06:22] <RAOF> We'll need an extra Xserver patch to prevent my laptop from crashing on startup, though :)
[06:22] <tjaalton> heh
[06:22] <tjaalton> for hybrid?
[06:23] <RAOF> Yeah. airlied's ‘don't crash if there's a GPU with no outputs hooked up’ patch.
[06:24] <tjaalton> ok
[06:26] <RAOF> I've been happily tootling along, playing Civ V on the ATI card in this laptop.
[06:27] <RAOF> It's worth a snapshot.
[06:27] <tjaalton> cool
[06:28] <tjaalton> hmm, thinking about sna again..
[06:28] <tjaalton> we get these gpu lockups with uxa only, and little hope in getting them fixed
[06:30] <RAOF> Oh, really? Urgh.
[06:30] <RAOF> IIRC sna doesn't have the prime stuff hooked up :)
[06:33] <tjaalton> it does
[06:33] <tjaalton> 2.20.8 should have it
[06:34] <tjaalton> need to check..
[06:35] <tjaalton> yes
[06:36] <tjaalton> df68723baae71 and some fixes later on
[06:42] <RAOF> Ah, cool.
[06:42] <RAOF> Would you like me to do the -ati snapshot, or shall youL?
[06:43] <tjaalton> please, you've at least tested it :)
[06:48] <RAOF> I guess you'd also like me to do the accompanying Xserver upload too, then :)
[06:48] <tjaalton> heh, yeah
[06:48]  * RAOF files the FFe
[06:48] <tjaalton> i've been too lazy to do those
[06:49] <tjaalton> but since -ati is crazy it's probably best
[06:49] <RAOF> ...slowly, because I have the baby.
[06:51] <tjaalton> take your time :)
[06:54] <mlankhorst> morning
[06:55] <tjaalton> how's xdc so far?
[06:55] <tjaalton> RAOF: is bug 1043458 something related?
[06:55] <tjaalton> intel/ati hybrid
[06:56] <RAOF> Yes; that's what needs fixing
[06:57] <RAOF> Did I submit that?
[06:57] <tjaalton> no, I just see some dupes
[06:58] <RAOF> Oh! Modesetting!
[06:58] <RAOF> You so crazy
[07:04] <tjaalton> oh, indeed
[07:04] <tjaalton> five dupes now
[07:06] <RAOF> That's -ati bailing out because the GPU doesn't have any outputs, then modesetting helpfully saying "I can drive that!", and running into the X server bug :)
[07:07] <tjaalton> how helpful :)
[09:15] <tjaalton> RAOF: I can push the fixes to xserver for you unless you've started already
[09:15] <mlankhorst> wow, can't remember my gpg key passphrase, sigh!
[09:16] <jcristau> what did you drink last night? :)
[09:16] <mlankhorst> I blame not being at home and not consciously remembering my password
[09:17] <tjaalton> phoronix beer, obviously
[09:36] <mlankhorst> hm, seems mesa is broken in my ppa
[11:31] <tjaalton> RAOF: I'm adding the patch for dynamic gpu poweroff too, would be fun to test how that works
[11:32] <tjaalton> also, having numbers in these patches is silly
[11:43] <ricotz> tjaalton, how did you got this funky patch? ;) http://launchpadlibrarian.net/116696132/mesa_9.0~git20120917.7cfd42ce-0ubuntu2_9.0~git20120917.7cfd42ce-0ubuntu3.diff.gz
[11:43] <tjaalton> wth?
[11:44] <tjaalton> sigh
[11:44] <ricotz> is contains quite some xml/html stuff
[11:44] <ricotz> it might still apply though
[11:44] <tjaalton> oh it applies and builds
[11:45] <tjaalton> just looks ugly
[11:47] <tjaalton> oh yes, used the link, should've opened it and select plain
[11:48] <tjaalton> and pushed git too, can reset the clock back :)
[11:51] <tjaalton> had a gpu hang on my ivb, everything looks otherwise fine but fonts in t-bird are funky
[12:24] <mlankhorst> can someone upload mesa again to the q backports ppa?
[12:26] <tjaalton> what's wrong there?
[12:26] <mlankhorst> i was missing llvm-3.1 and recent enough wayland to build it :-)
[12:26] <tjaalton> ok
[12:27] <mlankhorst> if it rejects bump version number to ppa4.1
[12:27] <tjaalton> don't have the script to mangle it ;)
[12:27] <mlankhorst> update xorg-pkg-tools
[12:27] <mlankhorst> go to mesa directory and run xorg-pkg-tools/lts-pkg-rename
[12:27] <tjaalton> i should probably have that checked out
[12:27] <mlankhorst> yeah need it updated :-)
[12:29] <tjaalton> what's the lp repo?
[12:30] <mlankhorst> ppa:ubuntu-x-swat/q-lts-backport
[12:30] <tjaalton> no for the tools
[12:30] <tjaalton> can't find them
[12:30] <tjaalton> here
[12:30] <mlankhorst> it's in edgers
[12:31] <mlankhorst> https://code.launchpad.net/~xorg-edgers/xorg-server/xorg-pkg-tools
[12:31] <tjaalton> really?
[12:31] <mlankhorst> have you updated it?
[12:31] <tjaalton> sounds like the wrong place for it
[12:31] <tjaalton> no
[12:31] <tjaalton> I don't have it at all on this machine
[12:32] <mlankhorst> just check out that branch and it's in there
[12:37] <tjaalton> uploading
[12:38] <mlankhorst> thanks :)
[12:39] <mlankhorst> seems I lost connection to my machien at home
[12:41] <mlankhorst> can you do xorg-server 1.13 too to pick up that autobind patch?
[12:43] <tjaalton> just uploaded more hybrid goodies
[12:45] <mlankhorst> ah k
[12:46] <tjaalton> so you got those as well
[12:46] <tjaalton> uploaded
[12:47] <mlankhorst> perfect, less chance of things exploding tomorrow then
[12:47] <tjaalton> oh right :)
[12:47] <tjaalton> how has it been so far?
[12:48] <mlankhorst> good, met all the people I've been collaborating with except airlied
[12:48] <tjaalton> he's not there?
[12:48] <mlankhorst> sadly not :(
[12:49] <tjaalton> ok
[14:31] <mlankhorst> hm looks like the control files are generated wrongly
[14:32] <tjaalton> both?
[14:32] <mlankhorst> yeah it was before but I didn't notice it yet
[14:32] <tjaalton> what's wrong there?
[14:33] <mlankhorst> it handles conflicts/replaces/provides wrongly when it's all on 1 line, it seems
[14:34] <tjaalton> right
[14:49] <mlankhorst> I'll fix it next week, guess it's better to butcher my local install for now
[16:34] <MestreLion> Is there any way to override the EDID of a given display?
[16:39] <bjsnider> that's a strange thing to want to do unless the chip is not working
[16:40] <MestreLion> bjsnider: it was poorly programmed...
[16:40] <MestreLion> it says 50Hz is the prefered for all reasolutions
[16:41] <jwi> MestreLion: Documentation/EDID/* in a kernel tree
[16:41] <bjsnider> modelines in xorg.conf might work
[16:41] <MestreLion> so whenever I go to/back from fullscreen, it goes back to 50Hz, and I have to use Catalyst to put it back to 60Hz
[16:41] <bjsnider> the nvidia blob lets you use an external edid file
[16:42] <MestreLion> bjsnider: but I need to *remove* the modelines, not include them... how?
[16:42] <bjsnider> yeah but why not just include the correct modelines?
[16:43] <MestreLion> the correct modelines are there... they are just not the default
[16:43] <MestreLion> and the default is used in all games when switching to and from fullscreen
[16:43] <MestreLion> very few apps allow me to set the frequency... most only deal with resolution... and TV goes to 50Hz


[06:14] <jibel> hi all
[07:11] <oSoMoN> good morning desktoppers
[07:21] <didrocks> good morning
[07:24] <oSoMoN> salut didrocks
[07:24] <didrocks> salut oSoMoN !
[08:28] <seb128> gooood morning desktopers
[08:33] <fidencio> didrocks: morning! heya, may I bother you for a review on https://gitlab.com/libosinfo/osinfo-db/merge_requests/54 ?
[08:33] <gitbot> libosinfo issue (Merge request) 54 in osinfo-db "ubuntu: Add 19.10 entry" [Opened]
[08:33] <fidencio> didrocks: we'd like to upate gnome-boxes to have latest ubuntu as part of the recommended downloads
[08:33] <fidencio> didrocks: but we need this one merged as the first thing for hat
[08:33] <fidencio> *for that
[08:47] <didrocks> fidencio: oh sure! Will have a look this morning
[08:47] <didrocks> thanks :)
[08:47] <didrocks> hey seb128
[08:47] <seb128> lut didrocks, comment ça va aujourd'hui ?
[08:47] <didrocks> ça va
[08:48] <fidencio> didrocks: thanks!
[08:48] <seb128> jibel, did you end up testing the preseeding install to see if you were able to reproduce the issue?
[09:00] <jibel> no, not yet
[09:03] <Laney> moinsssssss
[09:03] <seb128> hey Laney, wb! had a nice 2 days off? how is the jetlag?
[09:07] <Laney> hey seb128
[09:07] <Laney> was mostly relaxing around the house
[09:07] <Laney> jetlag is ok but I didn't sleep great last night for some reason, so tired today anyway
[09:07] <Laney> :S
[09:07] <Laney> how are you?
[09:12] <seb128> I'm good, I did ajust back to the tz without issue but lack a bit of sleep
[09:12] <seb128> and it's freeze and the kid got a cold, which i've a feeling I'm getting now as well :-/
[09:13] <fidencio> didrocks: minimum requirement for disk is still 5GB?
[09:15] <Laney> :<
[09:16]  * seb128 is trying to unblock some of the proposed things
[09:16] <seb128> quite some transitions/backlog there
[09:18] <fidencio> didrocks: nevermind, just checked https://help.ubuntu.com/community/Installation/SystemRequirements
[09:18] <fidencio> I'll bump the recommended resources then
[09:20] <Laney> seb128: looks like these could be done btw: https://people.canonical.com/~ubuntu-archive/component-mismatches.txt ?
[09:22] <seb128> Laney, doing
[09:22] <Laney> \o/
[09:22] <didrocks> fidencio: thanks :)
[09:22] <Laney> hey didrocks
[09:22] <didrocks> hey Laney
[09:39] <seb128> Laney, maybe you can help me understanding proposed migration better, that's never clear to me those cases
[09:39] <seb128> Laney, https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libixion
[09:40] <seb128> libixion-0.14-0 missing is normal since the package is renamed
[09:41] <seb128> what's the proper way to hint/resolve that?
[09:41] <seb128> we can't delete the current version from the release pocket since that would break things in the archive until the proposed version does migrate (which could take a while depending on what other things blocks it)
[09:42] <Wimpress> Morning  o/
[09:42] <seb128> also I'm wondering why it lists python3-ixion
[09:42] <seb128>  python3-ixion | 0.14.1-4 | focal/universe          | amd64, arm64, armhf, i386, ppc64el, s390x
[09:42] <seb128>  python3-ixion | 0.15.0-3 | focal-proposed/universe | amd64, arm64, armhf, i386, ppc64el, s390x
[09:42] <seb128> hey Wimpress, how are you today?
[09:42] <Laney> seb128: which line in excuses are you talking about?
[09:42] <Laney> hi Wimpress
[09:43] <seb128> Laney, #libxion as mentioned in the url :)
[09:43] <Laney> that doesn't say anything about NBS here
[09:44] <seb128> shrug, firefox struggle on that page, it won't like me select/copy
[09:45] <seb128> Laney, k, looks like the content changed, it was probably just not built yet
[09:45] <seb128> sorry for the noise
[09:45] <Laney> ahhh ok
[09:45] <marcustomlinson> morning all
[09:45] <seb128> I refreshed and those lines are gone now, makes more sense
[09:45] <seb128> hey marcustomlinson
[09:45] <Laney> yo marcustomlinson
[09:46] <seb128> bah, laptop battery blinking now
[09:46] <seb128> time to go back to my desk
[09:46] <seb128> brb
[11:00] <Laney> oSoMoN: i forgot if I pinged you about firefox/armhf autopkgtests already
[11:01] <oSoMoN> Laney, if you did I don't remember it
[11:01] <oSoMoN> let me check
[11:01] <Laney> the html5test started timing out
[11:01] <Laney> would be good if you could, thanks!
[12:41] <GunnarHj> Hey Laney, the glib2.0 SRU has made it to eoan-proposed at last. Considering that you seem to be struggling with glib2.0 in focal, I just wanted to check if version 2.62.2-2~ubuntu19.10.1 is it for the SRU before doing the verification.
[12:47] <Laney> why do I seem to be struggling?
[12:48] <Laney> feel free to do the verification, yeah
[12:50] <GunnarHj> Laney: Well, I noticed updates in -proposed without anything has migrated to -release yet. Maybe that's normal. Ok, will verify.
[12:51] <Laney> It needed work, but that's normal enough :-)
[12:51] <GunnarHj> Ack.
[16:17] <seb128> hellsworth, hey, so pango tests worked on a retry, http://autopkgtest.ubuntu.com/packages/p/pango1.0/focal/amd64 , glib migrated, that lower the importance of that card/task for now I would say so feel free to lower prioritize, we will have a better idea over time if the test is really flacky and or if that was a one time thing (still a bug but that would make it low importance)
[18:04] <Laney> night, see you monday!
[18:43] <hellsworth> seb128: thanks for the tip about pango!
[18:57] <hellsworth> are code blocks a thing in launchpad?
[18:58] <hellsworth> i'd like to make my comment look nice and code blocks would help if it's a thing
[19:18] <sarnold> no :(
[19:18] <sarnold> at least the emails look good
[19:18] <sarnold> but the web version gets pretty unreadable pretty quick
[19:20] <hellsworth> darn, i was afraid of that
[19:20] <hellsworth> thanks sarnold !
[19:21] <sarnold> honestly given what launchpad *does* I'm surprised it's not the other way around -- all "code-blocks" except for occasional "I'd like to write some prose" blocks :)
[19:21] <hellsworth> haha good point


[09:47] <janisozaur> hi, why would a firefox-next be compiled and information about package not pushed for clients to update? i can see 25-b1 .deb, but "Packages" reports 24-b10 as latest. is this on purpose (like there is a known bug) or by mistake?
[09:47] <janisozaur> i'm talking about raring


[13:57] <InHisName> andrew: get yer nom noms here: http://www.youtube.com/watch?v=SMWi7CLoZ2Q
[13:57] <PennBot> Title: YouTube - Nom Nom Nom Nom Nom Nom Nom - Parry Gripp (at www.youtube.com)
[15:36] <SamuraiAlba> Good bacon to all!
[15:49] <teddy-dbear> good chocolate to all!
[15:53] <SamuraiAlba> aye!
[15:53] <SamuraiAlba> Good Runescape to all!
[15:54] <ssweeny> Good Farscape to all!
[16:08] <HowdyDoody> hello any grubbers listening ?
[16:09] <HowdyDoody> hello mr bacon, SamuraiAlba
[16:09] <teddy-dbear> no
[16:10] <HowdyDoody> only a stuffed bear is paying attention ?
[16:14] <SamuraiAlba> heya
[16:15] <HowdyDoody> my grub has been messed by ubuntu update
[16:16] <HowdyDoody> I think it fried my Bacon
[16:17] <HowdyDoody> I am InHisName on another machine, SamuraiAlba
[16:40] <SamuraiAlba> ahhh
[16:40] <SamuraiAlba> Sorry, was filling out my FAFSA
[16:43] <HowdyDoody> SamuraiAlba:  upon booting liveCD saw error of hard drive controller.   REseated SATA cable.  Now works again.
[16:43] <HowdyDoody> School funding for College or ??  SamuraiAlba
[16:47] <SamuraiAlba> College
[16:51] <HowdyDoody> What major are you choosing ?
[16:51] <SamuraiAlba> Now for the Hesaa...
[16:51] <SamuraiAlba> Computer Science with a focus on Network Security @ Camden
[17:02] <HowdyDoody> Cool,  I am in Cisco training right now and a microsoft series.  Finish up late march.
[17:02] <SamuraiAlba> Sweet.
[17:02] <SamuraiAlba> Enjoying it?
[17:03] <HowdyDoody> Sorta,  lotta info, heavy exams for certifications.
[17:03] <SamuraiAlba> I have most of the Cisco study guides and videos here :)
[17:04] <HowdyDoody> The big trick is will a future employer want me rather than someone else with bazillion years experience and no certs.
[17:04] <SamuraiAlba> That is a big trick :O
[17:05] <HowdyDoody> I have accumulated 7 Gigs of study helps dumps pdfs  and nuggets etc.
[17:05] <SamuraiAlba> Now I have to find out how to convert my dynamic HD to a simple volume so I can install Ubuntu :)
[17:05] <HowdyDoody> Delete partitions
[17:05] <SamuraiAlba> It's my laptops ONLY partition
[17:05] <HowdyDoody> Start with bare drive.
[17:06] <SamuraiAlba> Not an option with a broken DVD burner and no backup external...
[17:06] <HowdyDoody> Do you  still want dual boot?
[17:06] <HowdyDoody> wubi
[17:06] <SamuraiAlba> I have Wubi.  I was also going to install CentOS, tho
[17:07] <ChinnoDog> If you have one hard drive and one partition I don't think there is any value in making it dynamic in the first place.
[17:07] <HowdyDoody> wubi is only one to install into file in windows drive.   NO reformatting
[17:07] <HowdyDoody> sort of a 'nested' dual boot
[17:08] <HowdyDoody> What about that black edition, is there a dvd player there ?
[17:08] <HowdyDoody> Opps its a laptop
[17:09] <SamuraiAlba> the black edition desktop is still here :)
[17:09] <SamuraiAlba> I put a PSU in it, but now it needs an HD
[17:09] <SamuraiAlba> You bought the HD :)
[17:09] <HowdyDoody> You sold me two now have none?
[17:09] <SamuraiAlba> none
[17:10] <ChinnoDog> Sell it back to him at a profit
[17:10] <HowdyDoody> do you have a USB to SATA box or adapter ?
[17:11] <SamuraiAlba> Nay
[17:11] <SamuraiAlba> I'm just gonna have to stick with Wubi :'(
[17:11] <HowdyDoody> I could try ChinnoDog  but he was out of stock on cash then and gave it to his girl friend to pay bills.  So I assume still empty.
[17:12] <HowdyDoody> wubi plays pretty nice without spending any $$
[17:13] <ChinnoDog> oh. hmm. I see.
[17:13] <HowdyDoody> ChinnoDog: do you know much about grub2 ?
[17:13] <ChinnoDog> Rent to own?
[17:13] <ChinnoDog> not really
[17:13] <HowdyDoody> bummer
[17:15] <ChinnoDog> I know that if you installed Windows on a simple disk and then converted it to dynamic that you should be able to change it back though
[17:15] <ChinnoDog> Making it dynamic doesn't remove the structures that were there before you did it. You made it a dynamic disk without any dynamic volumes, which does nothing for you.
[17:18] <SamuraiAlba> now to find out how to convert it back...
[17:19] <ChinnoDog> might be able to right click on it in disk management and convert back with a couple clicks
[17:20] <SamuraiAlba> no joy there
[17:21] <SamuraiAlba> maybe gparted?
[17:22] <SamuraiAlba> HIRENS!  WOOWOO!
[17:23] <ChinnoDog> no. Linux tools do not know anything about dynamic disks last I checked.
[17:23] <ChinnoDog> Have you created any dynamic volumes?
[17:25] <SamuraiAlba> no
[17:26] <SamuraiAlba> brb trying Hirens
[17:33] <HowdyDoody> ChinnoDog: In my usoft class, when converting to dynamic, there is NO going back.  Sorta like lvm in ubuntu, its delete partition to go back to basic disks.
[17:34] <HowdyDoody> There might be a hacker way to do it but would not be pretty.
[17:35] <ChinnoDog> It is completely different from LVM
[17:35] <ChinnoDog> At least, for the first paritition
[17:35] <ChinnoDog> There is a caveat with dynamic disks. You can't install Windows onto them.
[17:35] <HowdyDoody> Can't install boot volume to it.
[17:35] <ChinnoDog> right
[17:35] <HowdyDoody> But can convert others.
[17:35] <ChinnoDog> So when you install Windows you will be installing onto a standard partition
[17:36] <HowdyDoody> its Gates 's goofy answer to lvm
[17:36] <ChinnoDog> It isn't possible to remove the partition information for that first partition
[17:36] <ChinnoDog> The only thing converting a disk to dynamic does is mark it as dynamic, until you create dynamic volumes on it which still don't affect the first partition
[17:37] <ChinnoDog> I'm pretty sure I've converted disks in the other direction before
[17:37] <HowdyDoody> It has physical and logical buried deep in it.
[17:37] <ChinnoDog> But, only if you don't have dynamic volumes created on it
[17:38] <HowdyDoody> maybe
[17:38] <ChinnoDog> When they were first introduced it created a problem with disk imaging software because none of the existing solutions could read it
[17:38] <HowdyDoody> Probably his one volume was converted to dynamic.   He can see it in disk management.
[17:38] <ChinnoDog> So I would have to convert it back in order to image it
[17:40] <HowdyDoody> If he never converted the one disk to dynamic then he might have a chance to undo the little bit flag.
[18:45] <InHisName> @stats
[18:45] <PennBot> InHisName: I have 2 registered users with 1 registered hostmasks; 1 owner and 0 admins.
[18:45] <InHisName> @logs
 we haz logs, http://ubuntupennsylvania.org/PennBot/ or What happens in #ubuntu-us-pa stays in the logs


[14:47] <Naveen> while getting the code using 'bzr branch lp:gtg trunk' command, I'm getting an error
[14:48] <Naveen> bzr: ERROR: Connection error: while sending CONNECT xmlrpc.launchpad.net:443: [Errno 110] Connection timed out
[14:48] <Naveen> Does anyone has any solution?


[00:00] <wxl> sorry git+ssh
[00:00] <wxl> the USERNAME is perhaps optional, depending on your config, but being explicit is good
[00:01] <wxl> following the same path as the original remote is ideal, too
[00:01] <gsilvapt> Okay, thanks guys!
[00:01] <wxl> so yes, wgrant and clivejo are both essentially correct :)
[00:02] <clivejo> so " git remote add gsilvapt<EMAIL_ADDRESS>"
[00:02] <clivejo> and then " git push gsilvapt kubuntu_unstable "
[00:02] <gsilvapt> Hum, okay that seems reasonable. I'll give that a try
[00:06] <clivejo> gsilvapt: did you push yet?
[00:06] <gsilvapt> just did
[00:06] <wxl> https://code.launchpad.net/~gsilvapt/kubuntu-packaging/+git/ksnakeduel
[00:06] <wxl> it's there
[00:06] <gsilvapt> exactly
[00:06] <wxl> so now click on the right branch
[00:06] <wxl> (kubuntu_unstable)
[00:07] <wxl> then click on the "Propose for merging" link
[00:07] <gsilvapt> I'm following
[00:09] <gsilvapt> clivejo, the merge message should be something like, the package was failing to build in KF5 because some packages were missing and this change adds that to the source code?
[00:09] <clivejo> I can see the commit
[00:09] <wxl> whatever you do make sure you pick the right repo/target!!!!!
[00:09] <clivejo> but no MR yet
[00:10] <wxl> and the merge request doesn't have to be anything really extensive
[00:10] <gsilvapt> Yea, I was going into those, wxl :D
[00:10] <wxl> it's very common to accidentially select the wrong repo
[00:10] <wxl> note that if you choose a repo from the repo, it doesn't automatically select the radio button
[00:10] <gsilvapt> target repository should be this ? https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ksnakeduel
[00:10] <wxl> yes
[00:11] <gsilvapt> reference path? What's that?
[00:11] <wxl> that would be the branch
[00:11] <gsilvapt> kubuntu_unstable then, right?
[00:12] <wxl> should be yes
[00:12] <gsilvapt> Okay, thanks!
[00:12] <gsilvapt> I don't need to add any reviewer for now, or do I ?
[00:13] <wxl> no
[00:13] <gsilvapt> I know someone must sponsor this but I'm not sure if I should add someone or request sponsorship in another form
[00:13] <wxl> unless you've specifically talked to someone
[00:13] <wxl> otherwise the whole of the kubuntu-packaging team will get notification
[00:13] <gsilvapt> Right, okay.  wxl, thank you very much! I know you're busy with work so sorry for taking your time!
[00:13] <clivejo> you can direct it to me if you want?
[00:14] <gsilvapt> clivejo, too late now but I guess I can resubmit the proposal
[00:14] <clivejo> no, its fine, Ill get it anyway
[00:14] <gsilvapt> ah, or request another review
[00:14] <clivejo> got it
[00:15] <gsilvapt> I think I've done it correctly
[00:16] <gsilvapt> we can move this conversation to devel, if you prefer, clivejo. Seems more adequate to me
[00:16] <clivejo> sure :)
[00:16]  * wxl high 5s gsilvapt
[00:17] <gsilvapt> thank you wxl!
[18:04] <gQuigs> is there any way to close all bugs on a package or project?  example: https://bugs.launchpad.net/ubuntu/+source/unity-2d
[18:05] <gQuigs> it's no longer in any supported ubuntu releases
[18:05] <gQuigs> or should I figure out how to script it to the LP api?
[18:05] <wxl> i don't know about the possibility of the former but it should be pretty trivial with the api
[18:09] <gQuigs> should that just be an automatic thing?  if Ubuntu release goes EOL (precise), and no action has been taken on the bug after 14.04 release, then mark it incomplete and ask to confirm if it's on a newer release?
[18:09] <wxl> yeah that's completely reasonable
[18:11] <nacc> gQuigs: wxl: server team is going through that process manually too :)
[18:12] <gQuigs> nacc: why manually?
[18:13] <nacc> gQuigs: well, we have to review each bug as well, in our case. For some, we are removing from our backlog, for some, we are updating the state.
[18:13] <nacc> gQuigs: most of them, in our case, are 'stale' in that they were triaged once, maybe 2 years ago and not touched since
[18:14] <gQuigs> nacc: what packages haven't you gotten to yet?
[18:14] <gQuigs> gQuigs is looking to get some technically good users (but possibly with little LP triage experience) a starting point of bugs to clean up/triage
[18:15] <gQuigs> so we might be able to help do a pre-clean on some packages
[18:15] <nacc> gQuigs: oh nice -- we're just finishing up a sprint, maybe I can ping you a list on monday?
[18:15] <gQuigs> nacc: sure, I'll shoot you an email  - thanks!
[18:16] <nacc> gQuigs: np, thank you
[19:16] <pmatulis> how do i branch/check-out/get a specific revision of a branch?
[19:20] <cjwatson> gQuigs: it's not IMO reasonable for it to be automatic, because it does happen that a source package is replaced or renamed and bugs should be moved around instead.  I'm much more comfortable with human judgement in the loop.
[19:24] <gQuigs> cjwatson: yea, that makes sense, especially with package renames..
[19:26] <gQuigs> cjwatson: any chance you know of a API script that already does part of what I'm looking to do?  (list all bus from one project, make  a comment and close)
[19:26] <gQuigs> most of the example scripts I'm finding are from 2010-2012..
[19:48] <pmatulis> disregard. bzr branch -r<rev#> ...
[20:06]  * gQuigs is currently trying to modify hugdaylist to do it..
[21:25] <cjwatson> gQuigs: Not offhand, but it's surely not that hard?


[09:59] <niram> socket activation does not seem to work
[10:00] <niram> when using unix domain sockets
[10:00] <niram> but it works when using inet sockets
[10:00] <niram> any idea?
[10:00] <niram> i am using ubuntu trusty, it comes with upstart 1.12.1
[11:26] <Marqin> upstart is not goig to be maintained after 14.04 eol? are there any promising forks?


[14:19] <nathwill> morning early birds!
[16:27] <c_smith> morning, nathwill
[16:27]  * c_smith will brb, needs to restart his desktop for some updates
[16:27] <nathwill> :)
[16:59] <c_smith> back, took longer than it should have since I decided to do some testing on the RAM I bought, memtest told me there were some error.
[16:59] <c_smith> *errors
[17:11] <nathwill> interesting
[17:25] <c_smith> not sure which stick would have the errors, as I saw no indication to that. or whether it's the connection.
[17:25] <c_smith> and joy, I deleted my Documents folder......
[17:25] <nathwill> well, you can pull them sequentially and re-run memtest...
[17:25] <nathwill> hrm
[17:26] <c_smith> true. I still have my Laptop operable,
[17:26] <c_smith> the documents folder was deleted on my laptop
[17:26] <c_smith> need to pay more attention to what I delete.
[17:27] <c_smith> worth a try. I'll try sequentially testing one stick.
[17:27] <c_smith> at a time that is.
[17:36] <c_smith> ok, running Memtest on the first stick.
[17:36] <c_smith> think for this I can spare my mouse and use it for my laptop
[17:51] <bkerensa> such a busy week
[17:52] <bkerensa> DocFreeze is Thursday and were no where close to done so were requesting a exception from the release team which is also pushing the translations behind schedule
[17:58] <c_smith> sounds busy. I'd offer to help if I wasn't preoccupied with other stuff and I knew what to do there.
[18:50] <c_smith> so, after testing 2 of my RAM sticks, no errors, testing the third, which is at 77% complete total, there are no errors, I'm guessing that it might have been that 2 of them weren't in all the way (my doing) so if this stick proves to have no errors, I'm going to insert all 3 again and run Memtest86 then, after making sure all 3 are in correctly.
[19:00] <nathwill> good times
[20:07] <bkerensa> nathwill: I sent out a e-mail regarding the LoCo Council's update approval guidelines if you have any feedback
[20:12] <nathwill> k, i'll check it out
[20:12] <nathwill> thanks bkerensa
[20:20] <bkerensa> nathwill: finn should be here soon :D
[20:21] <bkerensa> sending him back to Washington with some Ubuntu swag and other stuff so he can go convert the Microsoft folks
[20:24] <nathwill> hehe
[20:52] <c_smith> yay for kernel problems........
[21:21] <bkerensa> c_smith: what kernel problems?
[21:24] <c_smith> my desktop, after a few minutes of being booted up, has either a kernel panic, or dumps what looks to be a kernel crash dump to my screen.
[21:26] <bkerensa> c_smith: Have you reported this?
[21:26] <bkerensa> c_smith: Have you reported this?
[21:27] <c_smith> I'm currently trying to figure out if this is due to the 3 1GB RAM sticks, or the kernel itself.
[21:28] <c_smith> like I was going to say, it only started doing this when I looked in the tower after having issues with them, and found they hadn't been inserted all the way, and I fixed that.
[21:29] <c_smith> my laptop is unaffected.
[21:30] <c_smith> but even if this was a bug, I couldn't get the new fix into my desktop, as it doesn't last long enough to get a new kernel version onto it.
[21:30] <c_smith> or any update, for that matter. atm, all it's good for is a really expensive RAM tester.
[21:57] <bkerensa> c_smith: have you tried installing from the alternate iso?
[21:57] <bkerensa> are you sure your using the right iso for your hardware?
[22:11] <sbeattie> c_smith: also, what release are you trying this with?
[22:27] <c_smith> yaaaay
[22:27] <c_smith> my laptop no long gives me kernel problems! :D
[22:27] <c_smith> *desktop, not laptop
[22:27] <c_smith> bkerensa, care to hear how I fixed it?
[22:27] <bkerensa> c_smith: sure
[22:28] <c_smith> bkerensa, I simply removed one stick of RAM, seems the kernel doesn't like 3 slots being taken up.
[22:28] <c_smith> and that's the  amount of slots total.
[22:28] <bkerensa> c_smith: What architecture are you using?
[22:28] <c_smith> strange, but that's how it goes I guess.
[22:28] <bkerensa> are you certain one stick was not bad?
[22:29] <c_smith> i386, x86, i686, however you want to label the arch
[22:29] <bkerensa> are you certain the extra slot was not defective?
[22:29] <bkerensa> c_smith: what capacity was the total ram if you had all sticks in?
[22:29] <c_smith> and I'm sure the stick is good, not sure about the slot, but memtest86 gave me no errors on the ram.
[22:29] <c_smith> the max is what i had, 3 GB.
[22:30] <c_smith> for memtest86. I ran all 9 tests once on each stick individually, then again with all 3 put in.
[22:30] <c_smith> no errors both times.
[22:30] <c_smith> *both ways
[22:31] <c_smith> I might consult with someone to see what might have happened. though.
[22:32] <c_smith> bkerensa, for the kernel probs, I can tell you that it had khelper. and similarly named mentions in it.
[22:32] <c_smith> well. I'm gonna leave this running to see if anything else pops up.
[22:34] <bkerensa> c_smith: you might consult #ubuntu-kernel
[22:59] <c_smith> bkerensa, thanks
[23:18] <nathwill> pae kernel?


[03:11] <Rocket2DMn> jjesse, on a roll buddy!
[03:11] <jjesse> Rocket2DMn: i think i have most if not all of the reported karmic bugs fixed for kubuntu-docs
[03:11] <jjesse> so then we can somehow figure out how to do an SRU for kubuntu-docs
[03:11] <Rocket2DMn> that's awesome
[03:11] <jjesse> yeah
[03:12] <Rocket2DMn> I just sent out a request to help get ubuntu-docs bugs fixed
[03:12] <jjesse> and the lucid kubuntu-docs are started to rock again
[03:12] <jjesse> which is nice
[03:12] <jjesse> ok i'm out to walk the dog, see you later :)
[03:12] <Rocket2DMn> okie dokie, peace
[07:09] <mistrynitesh> any reason why link to karmic specs still showing on the /Kubuntu/Todo/Lucid wiki page?
[07:10] <Darkwing-Netbook> mistrynitesh: Not sure, hang on...
[07:20] <Darkwing-Netbook> mistrynitesh: Fixed. :) Thanks for pointing that out.
[07:22] <mistrynitesh> Darkwink-Netbook: thanks for redirecting :)
[07:23] <Darkwing-Netbook> hehe I just realized you were in there LOL
[07:24] <mistrynitesh> :D
[15:37] <Rocket2DMn> mdke, if you get a few minutes today, I have some questions I'd like to run by you
[20:17] <dhillon-v10> nixternal, hi :)
[20:17]  * dhillon-v10 says hi to everyone


[00:00] <BobJonkman1> Hello Everybodeee!
[00:01] <BobJonkman1> Ubuntu-ca IRC meeting about to get under way.
[00:01] <BobJonkman1> Roll call: F|ReSTaRT jlamothe oracology zul Yompa MagicFab DarwinSurvivor jaguar johanbr mars bregma komputes KombuchaKip ryanakca IdleOne dscassel azend Chex  cyphermox sipherdee txwikinger    egerlach
[00:01] <Chex> hello :)
[00:02] <oracology> BobJonkman1: greetings! i'm unfortunately in the UK and am heading to bed but will idle here to read up in a few hours.
[00:02] <Chex> oracology: and I am actually in Glasgow as well, and will be idling doing the same
[00:02] <BobJonkman1> oracology: No problem.  There'll be logs, and I'll put minutes on https://wiki.ubuntu.com/CanadianTeam/Meetings/2013-01-24
[00:02] <BobJonkman1> which is also where today's agenda is
[00:03] <oracology> ahh duly noted. :)
[00:03] <oracology> catch up with you all in a bit then!
[00:03] <BobJonkman1> oracology: Seems you blinked out just as I said " oracology: No problem.  There'll be logs, and I'll put minutes on https://wiki.ubuntu.com/CanadianTeam/Meetings/2013-01-24
[00:03] <BobJonkman1> See you!
[00:04] <oracology> BobJonkman1: had to restart Pidgin i'm afraid! but yes, see you !!
[00:04] <BobJonkman1> And Hello Chex
[00:05] <BobJonkman1> dscassel sends word that he's currently engaged in domestic obligations, but he'll pop in from his phone as time permits
[00:06] <BobJonkman1> Let me start with the greeting ritual:  I'm Bob Jonkman, a new contact for Ubuntu Canada, and I'm IRCing from Al Madina Restaurant in Waterloo, Ontario
[00:08] <BobJonkman1> Off the top of the agenda is Current Events
[00:09] <BobJonkman1> In Waterloo we're having an Ubuntu Hour in an hour, right after the IRC meeting.
[00:10] <BobJonkman1> If you're within 50 minutes driving (or biking or walking) distance, c'mon by!
[00:11] <BobJonkman1> And Charles McColm (chaslinux when he's online) has moved the Ubuntu Hour Kitchener to Thursday, 7 February, 6:00pm at Egg Roll King
[00:12] <BobJonkman1> Charles says: http://charlesmccolm.com/2013/01/22/next-ubuntu-hour-date-and-timing/
[00:12] <BobJonkman1> tl;dr: more domestic obligations, and ERK is just too packed on a Friday night
[00:14] <BobJonkman1> If you're wondering how to host an Ubuntu Hour, you can just go to a local coffee shop, restaurant, pub, or other gathering place, announce it (here in IRC, and/or on the mailing list).
[00:15] <BobJonkman1> People show up, and you chat.  About Canadian things like the weather, divisive things like sports, and even Ubuntu stuff!
[00:16] <BobJonkman1> If you take a picture of the event and send it to dscassel he'll send you a handful of Ubuntu-branded DVDs to hand out at your next Ubuntu Hour.
[00:16] <BobJonkman1> This is the famous "CD/DVD Bribery Programme"
[00:18] <BobJonkman1> Other stuff happening: Ubuntu Developer Week, 29-31 January https://wiki.ubuntu.com/UbuntuDeveloperWeek
[00:18] <BobJonkman1> Looks like there are some interesting things on the UDW agenda.
[00:19] <BobJonkman1> All are accessible on #ubuntu-classroom, right here in IRC
[00:19] <hakimsheriff> Hi everyone, sorry I'm late
[00:19] <BobJonkman1> Hi hakimsheriff
[00:19] <BobJonkman1> I'm just working my way through upcoming events...
[00:19] <BobJonkman1> hakimsheriff: Are you still the ubuntu-ca distributor for stickers?
[00:20] <hakimsheriff> Yes I am
[00:20] <BobJonkman1> Can you remind me how that works?
[00:21] <hakimsheriff> Sure, you just send a self addressed stamped envelope to me; my address is on system76.com
[00:21] <hakimsheriff> And I'll send you back the envelope with 4 grey powered by Ubuntu stickers
[00:22] <BobJonkman1> Got a picture?
[00:22] <hakimsheriff> Address is here : https://www.system76.com/community/stickers/ under Canada
[00:23] <hakimsheriff> Sorry, I don't have one now
[00:23] <BobJonkman1> I'll poke around the System76 site, see if there's a sample
[00:24] <hakimsheriff> I'm on my phone, would you like me to try and upload one later?
[00:25] <BobJonkman1> Actually, there's pictures right at the top of https://www.system76.com/community/stickers/
[00:26] <BobJonkman1> The System76 sticker page says you're in Quebec. Do you know of any Ubuntu Hours or other events?
[00:27] <hakimsheriff> The picture on the website is white though, the ones I have are the same but with a grey, metallic looking backing
[00:27] <BobJonkman1> Oooh!  Metalized stickers!
[00:28] <hakimsheriff> I don't really participate with the Ubuntu hours here, so I don't really know
[00:29] <BobJonkman1> No problem.  I was just curious.  Ubuntu-qc has their own schedule and calendar; I can always go look there.
[00:29] <BobJonkman1> So, continuing with events...
[00:29] <BobJonkman1> There's Ubuntu User Days on 9 and 10 February: https://wiki.ubuntu.com/UserDays
[00:31] <BobJonkman1> UUD also takes place in #ubuntu-classroom on IRC
[00:31] <BobJonkman1> And at the same time as UUD is Ubuntu LoCo Games.  There's a Web site at http://viajemotu.wordpress.com/2013/01/07/ubuntu-loco-games-2013-1/
[00:32] <BobJonkman1> dscassel was considering setting up a LAN party for Ubuntu-ca, probably at Kwartzlab, the local hackerspace where he's much involved.
[00:33] <BobJonkman1> I haven't really looked through the ULG web site, so I don't know what's required.
[00:33] <BobJonkman1> Sounds cool, tho.
[00:34] <BobJonkman1> Maybe we can organize something here (in IRC) or on the mailing list.
[00:34] <BobJonkman1> People _do_ know about the Ubuntu-ca mailing list, right?
[00:35] <BobJonkman1> You can sign up at https://lists.ubuntu.com/mailman/listinfo/ubuntu-ca
[00:36] <BobJonkman1> It's a fairly low-volume mailing list, maybe a couple of messages a week, although there's the odd burst of traffic.
[00:36] <BobJonkman1> I post announcements about Ubuntu Hours, this IRC meeting; it's good medium for keeping the community (Canada-wide!) together.
[00:37] <BobJonkman1> And, yes, it's also used for support questions and answers.
[00:37] <BobJonkman1> That's what community does, provide assistance when needed.
[00:37] <bregma> we try at any rate
[00:38] <BobJonkman1> Yup.  Hi, bregma!
[00:38] <bregma> O/
[00:38] <hakimsheriff> Hello bregma
[00:39] <BobJonkman1> Did you read the Ars Technica article on Ubuntu changing to rolling releases? http://arstechnica.com/information-technology/2013/01/ubuntu-considers-huge-change-that-would-end-traditional-release-cycle/
[00:40] <BobJonkman1> I think it's a great idea. Already I'm getting updates for LibreOffice, Firefox, Thunderbird and many other apps whenever there's an update.  That works for me, and I can see it working for the OS too
[00:41] <bregma> I imagine nothing will be set in stone until after the next UDS, although there was some discussion at the last one
[00:41] <BobJonkman1> My biggest worry is that Ubuntu Release Parties would only happen every other year for an LTS release
[00:41]  * BobJonkman1 still thinks he's a young pup and a party animal
[00:42] <bregma> the bigger problems come with things like new versions of Python or GTK, which can be awkward to roll out gradually
[00:43] <BobJonkman1> Yes, I can imagine the dependency hell when a fundamental building block is rolled out before the application layer is ready.
[00:43] <bregma> but the alphas and betas are already gone, and daily raring Ringtail releases are pretty usable, if you want to see what a rolling release is like
[00:45] <BobJonkman1> Well, if you go to the next UDS and have input, here's one user who's in favour.
[00:45] <bregma> I'll pass that along if I get the chance
[00:46] <BobJonkman1> OK, now to the elephant in the room.  With dscassel not here, I'm not sure how much we can get done on the Canadian Team ReApproval
[00:47] <BobJonkman1> I'm hoping to have a ReApplication Preparation Party in February.
[00:47] <BobJonkman1> Some folks from nearby Listowel have expressed an interest in holding something IRL
[00:48] <BobJonkman1> Mostly, it's finishing off the ReApproval application page at https://wiki.ubuntu.com/CanadianTeam/ReApprovalApplication2012
[00:49] <BobJonkman1> Removing old stuff, coming up with a roadmap, and generally making it ready to present to the LoCo Council.
[00:49] <BobJonkman1> If we can get that done in February then we can put in our application for March, and be approved again for the Raring Ringtail release in April
[00:51] <BobJonkman1> Of course, everyone is welcome to fix up the ReApprovalApplication page at any time.  No need for a format get-together
[00:51] <BobJonkman1> But things are more fun when done in a group when there's pizza
[00:52] <hakimsheriff> So things the team has done and will do?
[00:52] <hakimsheriff> Or just what has already been done
[00:53] <BobJonkman1> Both, really.
[00:54] <BobJonkman1> I've added the things we've done that I know about, but I'm sure there's more.  F'instance, there's a spot on the page that mentions stickers that needs fixing up
[00:54] <hakimsheriff> I'll get right on it ;)
[00:55] <BobJonkman1> But also a roadmap for the future.  I'd like to have some advice on how to attract more people, how to put Ubuntu in the mainstream.
[00:55] <BobJonkman1> For a country with 35 million people, we're getting pretty poor turnout for IRC meetings, for example.
[00:56] <BobJonkman1> Mind you, I don't know how the other LoCos are for attendance.
[00:57] <BobJonkman1> I sat in on the last LoCo Council IRC meeting, where czjakowski (sp?) said that 300+ members in LaunchPad is pretty good.
[00:57] <BobJonkman1> Also, we really need to do something about http://ubuntu-ca.org
[00:58] <BobJonkman1> I can't get logged in (something to do with LDAP integration to LaunchPad), and that site is terribly out-of-date.
[00:58] <BobJonkman1> I'm thinking that if we can't get it fixed in time for the ReApproval, we should remove mention of it on the Ubuntu Wiki, and use the Wiki for that information instead.
[00:59] <BobJonkman1> It's mostly event announcments, which we're already doing on the LoCo event site anyway
[01:00] <hakimsheriff> If we do get the website up and running, I would be glad to keep it up to date with all the events we talk about in the mailing list
[01:01] <BobJonkman1> hakimsheriff: Can you get logged in? I seem to recall you had admin access at one time...
[01:01] <hakimsheriff> I remember being given access, but I was never able to log in
[01:02] <BobJonkman1> Yeah, a common problem.
[01:02] <BobJonkman1> I may see txwikinger soon; I'll ask him in person
[01:02] <BobJonkman1> (txwikinger hosts the site)
[01:03] <dscassel> thanks for doing all this, Bob.
[01:04] <BobJonkman1> OK, looks like the hour is up.  I've been hogging the channel long enough -- anyone got anyting else?
[01:04] <BobJonkman1> O hai, dscassel
[01:04]  * dscassel has a minute while Ellen is getting ready. don't let me interrupt.
[01:05] <BobJonkman1> I think we're close to done.
[01:05] <dscassel> I'll get a Sunday at Ubuntu hour later. :)
[01:06] <dscassel> er, summary. :P
[01:06] <BobJonkman1> OK, see you when you get here!
[01:07] <BobJonkman1> Schawarma Poutine is an excellent choice today.
[01:08] <BobJonkman1> All rightie then.
[01:08]  * BobJonkman1 pounds gavel
[01:08] <hakimsheriff> OK well bye everyone, got to go, have a ton of homework to do
[01:08] <BobJonkman1> Next IRC meeting should be on 28 February, the fourth week of the month.
[01:09] <BobJonkman1> Bye hakimsheriff!
[01:09] <BobJonkman1> See y'all later!
[01:09]  * BobJonkman1 needs to unplug the tethered phone to call home...
[01:09] <bregma> BobJonkman1, thanks for hosting
[01:10] <BobJonkman1> You're welcome, bregma!
[20:03] <antiface> Hi, I'm not even sure which ubuntu IRC channel to go to.. maybe someone can help?
[20:30] <DarwinSurvivor> darn, almost caught that one :(


[02:54] <rawpenguin> morning. trying to update Ubuntu. but:   404  Not Found [IP: <IP_ADDRESS> 443]
[02:54] <rawpenguin> Err:18 https://packages.o1test.net jammy/stable all c-n-f Metadata
[02:55] <leftyfb> !next | rawpenguin
[03:28] <rawpenguin> morning. installing php on Jammy. Running the build in server. when checking address, i get the 'choose an application to open the localhost link'. What am i missing?
[03:29] <leftyfb> !next | rawpenguin
[03:29] <rawpenguin> hi bot
[03:30] <leftyfb> rawpenguin: please stop asking for support with versions of ubuntu that are still under development. You are already in #ubuntu-next and have asked the same question. Be patient and someone there might be able to help you. This is not the appropriate place to ask for help with 22.04
[04:29] <Bashing-om> For info: [rt.ubuntu.com #61049] WIKI authentication restored :D
[05:18] <saksol> @bar(input):button1
[06:13] <NetEcho> what's the proper way to add a user who's only purpose is to run a single application I.e. the user apache
[06:26] <lotuspsychje> NetEcho: are you asking for ubuntu desktop or -server, whats the full story of your purpose? maybe with more details volunteers can enlight more ideas
[06:40] <NetEcho> lotuspsychje: Ubuntu Server, I'm setting up a media server with several applications that it's been suggested the daemons run as their own user with access to /var/lib/daemon
[06:43] <NetEcho> in past I've just ran them as my normal user and had them use /home/myuser/.daemon for their data storage but this time around I'd like to do it correctly
[07:23] <blb201483> dmesg: read kernel buffer failed: Operation not permitted. AFAIR before 22.04 dmesg worked without sudo, am i wrong?
[07:26] <mrkubax10> looks like yes
[07:27] <blb201483> yes what?
[07:27] <mrkubax10> it works without sudo
[07:27] <mrkubax10> in 20.04
[07:43] <drewbert> what library would you recommend for real-time audio?
[07:44] <drewbert> currently using rodio, but it seems to be more playback oriented than real-time
[07:44] <lotuspsychje> drewbert: you could start a topic in #ubuntu-discuss if you like
[07:44] <drewbert> oh wrong channel, my b
[07:45] <blb201483> jitter free, warm lamp sound?
[11:30] <zacts> hi
[11:31] <zacts> if I install Ubuntu 22.04 LTS Beta (Jammy Jellyfish)  BETA how would I upgrade once 22.04 is actually released?
[11:31] <zacts> would I just use apt update;apt upgrade for this and it would work?
[11:32] <zacts> I'm just wondering if I can go ahead and install it or if I should wait
[11:32] <zacts> this is for a desktop (not a server)
[11:36] <oerheks> zacts, when released you will get the full version
[11:36] <zacts> I don't understand
[11:36] <zacts> can I go ahead and install BETA and apt upgrade will upgrade automatically when it's released?
[11:37] <oerheks> yes
[11:37] <zacts> thanks
[11:37] <oerheks> no need to de extra steps
[11:37] <oerheks> have fun!
[11:39] <freddy_> I hope you don't mind me asking an off topic questioin. Long story short, I have my own VPN server in another country. I used a very old laptop to set it up. It works fine, but I was wondering, if I changed the hardware (and honestly any Raspberry Pi is better than what I have), using the same internet connection, would that help increasing the speed of my VPN?
[11:45] <oerheks> faster hardware would save time encrypt your data, but this is a minor part
[11:55] <freddy_> oerheks, so it's not worth it?
[12:04] <freddy_> ok, thank you oerheks
[12:04] <freddy_> bye
[12:04] <zacts> thanks oerheks
[12:25] <BluesKaj> Hi all
[16:14] <cockatoodude> Should
[16:51] <CorvusCorax> Hi. I'm using Ubuntu bionic. I have an issue with Thunderbird and the calendar options, the current time (which also affects event notifications as well as display) is off by an hour. The system time and timezone is correct (`date` shows correct time and timezone) any ideas how to fix this? we switched to daylight saving recently, somehow it seems thunderbird is stuck in winter time
[16:52] <rob0> wrong time zone setting, I guess
[16:53] <rob0> oh, only in tbuird?  strange
[16:53] <tomreyn> preferences -> calendar -> timezone
[16:54] <rob0> maybe it has its own TZ setting independent of ^^
[16:54] <rob0> Also if started from an environment with a TZ setting, that would do it.
[16:55] <rob0> "TZ=US/Pacific thunderbird" at the command line or in the shortcut to start it
[16:55] <tomreyn> oh, but actually i see that same issue
[16:58] <tomreyn> actually no, not an issue here, sorry.
[16:58] <tomreyn> CorvusCorax: did setting the timezone in thunderbird help then?
[17:02] <CorvusCorax> no. i checked, in TB the timezone is set to "Europe/Berlin" - which is the correct timezone. except this should imply GMT+2 in summer and GMT+1 in winter. and it seems to be stuck on GMT+1
[17:02] <CorvusCorax> the only enries in the dropdown list are of the form Continent/City ... there's no manual GMT+X daylight saving independent entries
[17:03] <tomreyn> open calendar and click on synchronize on the top left, then close calendar and open it again - did this help?
[17:04] <tomreyn> how do you tell what calendar thinks is the current time?
[17:05] <CorvusCorax> the calendar displays a red bar on the current day at the current time for NOW
[17:05] <CorvusCorax> that is off by an hour
[17:05] <CorvusCorax> and i did click on synchronize
[17:05] <rob0> could the TB instance have been running continually since before the time change?
[17:05] <CorvusCorax> no, i did reboot
[17:05] <CorvusCorax> let me check something
[17:06] <CorvusCorax> ok fun, i switched the timezone in TB to a different timezone, which was displayed correctly, and then back to Europe/Berlin. now its correct
[17:06] <tomreyn> i can reproduce this (or a ifferent?) issue like follows: open tasks, click on synchronize, open calendar, switch to day view if needed, check current time - it is incorrect. click on synchronize, current time is now correct.
[17:06] <CorvusCorax> that seems to be a bug in TB. it seems to update DS only when the timezone is changed
[17:07] <rob0> Thunderbug! :)
[17:07] <tomreyn> which thunderbird version are you using there?
[17:07] <tomreyn> 91.7.0 here
[17:07] <CorvusCorax> 91.5.0
[17:08] <tomreyn> well i have the 91.7.0+build2-0ubuntu<IP_ADDRESS> deb from bionic-updates
[17:08] <CorvusCorax> i'm running apt update right now to see if theres a newer one
[17:09] <tomreyn> this sounds like you are not installing security updates, or not regularly. but since my version is also buggy it won't fix *this* issue anyways.
[17:09] <tomreyn> !info thunderbird bionic
[17:10] <tomreyn> apt policy thunderbird   may help you diagnose this
[17:10] <CorvusCorax> update updates to 91.7 now
[17:10] <CorvusCorax> so i just hadn't updated in a while
[17:11] <CorvusCorax> btw whats the easiest way to show the update history for a package (and previous versions, in case an upgrade broke something)
[17:11] <tomreyn> i see. this original -security upgrade has since migrated to -updates, so it must have been out for a while
[17:11] <tomreyn> apt changelog thunderbird
[17:12] <CorvusCorax> weird, the -security stuff should have at some point installed with unattended upgrades
[17:12] <tomreyn> or, if you're referring to when it was installed on your system, see /var/log/apt/history.log and term.log
[17:12] <CorvusCorax> no, i meant the changelog
[17:13] <tomreyn> which server have you configured to receive security updates from?
[17:14] <CorvusCorax> http://security.ubuntu.com/ubuntu
[17:14] <CorvusCorax> do i need to switch that to archive?
[17:15] <tomreyn> hmm that's fine, it will have to be an issue with how often your system checks for security updates then
[17:15] <tomreyn> switch to which archive?
[17:15] <CorvusCorax> http://archive.ubuntu.com
[17:15] <tomreyn> no, security updates should be retrieved from security.ubuntu.com
[17:16] <CorvusCorax> ok, then thats setup correctly. but its possible i had unattended upgrades disabled. gotta check that
[17:16] <CorvusCorax> still i thought i had done the latest manual update more recently than January
[17:18] <CorvusCorax> no, unattended updates service is running and /etc/apt/apt.conf.d/50unattended-upgrades has security enabled
[17:18] <CorvusCorax> this should have installed
[17:18] <CorvusCorax> weird
[17:22] <CorvusCorax> is there a logfile for the unattended upgrades to debug that?
[17:22] <tomreyn> yes, at the expected location
[17:23] <tomreyn> /var/log/unattended-upgrades/unattended-upgrades.log
[17:23] <tomreyn> unattended-upgrades is triggered by a systemd-timer
[17:23] <tomreyn> systemctl list-timers apt*
[17:37] <CultusFerox> unattended-upgrade is one of the first things I purge after installation
[18:08] <CultusFerox> ping asf
[19:22] <hafiz> hey
[19:52] <jhutchins> Hay is off-topic here, please join #horses
[19:53] <XATRIX> Hi guys! Need advice. My RTL8821ce adapter ,time to time is unable to connect to wireless network. I suspect system powersave options. When this happens, i see the following in dmesg log. It looks like, it sees the wifi networks, but it can't assoc. to. My NetworkManager system tray icon just spinning inititively and nothing happens.
[19:53] <XATRIX> [  194.295800] rtl8821ce 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0009 address=0xdfeec000 flags=0x0000]
[19:53] <XATRIX> [  194.295814] rtl8821ce 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0009 address=0xdfeec030 flags=0x0000]
[19:56] <Jeremy31> XATRIX: Does it show power management on in results for iwconfig
[19:58] <XATRIX> Jeremy31: currently it's: Power Management:off
[19:58] <XATRIX> But i can't check it right now.
[19:58] <XATRIX> Need to wait for this bug to come out again
[20:02] <Jeremy31> XATRIX: what number does this show>  cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
[20:21] <tomreyn> XATRIX: what number does this show>  cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
[20:23] <XATRIX> tomreyn: Hi again dude! glad to see you :)
[20:23] <XATRIX> it gives me '3'
[20:23] <jhutchins> XATRIX: Also consider that it could be your AP that's causing the problem.
[20:24] <XATRIX> Nope. my previous laptop did good. no problem with other devices
[20:24] <tomreyn> does is only happen when the laptop went through a suspend / resume cycle?
[20:25] <tomreyn> how is the rtl8821ce driver installed that you're using?
[20:25] <tomreyn> and hi to you, too, XATRIX ;-)
[20:26] <XATRIX> tomreyn: no, i don't use suspend/hibernate as for now. simply poweroff.
[20:26] <XATRIX> [xatrix@MERNOV-NB ~]$ dkms status
[20:26] <XATRIX> rtl8821ce, <IP_ADDRESS>, 5.13.0-39-generic, x86_64: installed
[20:26] <rob0> jhutchins: possibly, but to me IO_PAGE_FAULT sounds more like a driver bug.
[20:27] <blackop> hi. will 22.04 be released on 21st April exactly?
[20:27] <tomreyn> apt list --installed rtl8821ce-dkms
[20:27] <XATRIX> I chose this driver in the ubuntu propietary drivers dialog
[20:27] <tomreyn> ok
[20:28] <XATRIX> https://imgur.com/5MZFnxw.png
[20:28] <XATRIX> this one
[20:28] <tomreyn> yes, this answers my previous question.
[20:29] <tomreyn> https://github.com/tomaspinho/rtl8821ce is a newer version of this driver.
[20:31] <tomreyn> https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1904177 reports the same issue, though here it's related to suspend. there's a chance that you didn't actually notice the laptop went through suspend though
[20:32] <XATRIX> tomreyn: em..i
[20:32] <tomreyn> journalctl -b | fgrep ' PM: ' | nc termbin.com 9999
[20:32] <Jeremy31> XATRIX: what number does this show>  cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
[20:32] <XATRIX> i'm sure it goes poweroff. i don't send it to suspend
[20:33] <XATRIX> 3
[20:33] <Jeremy31> XATRIX: in terminal>  sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
[20:34] <Jeremy31> That will prevent Network Manager from enabling wifi power management on its own
[20:34] <tomreyn> after next reboot, i assume
[20:35] <Jeremy31> Yes
[20:36] <luka_33> wifi auto-powersave is the most annoying feature I can think of
[20:36] <luka_33> If the PC is idle long enough for it to kick in, why not auto-suspend? Why disable the one module/etc that is almost guaranteed to be needed/in use
[20:39] <XATRIX> Jeremy31: is it permanent ? Or do i have to set in on each restart ?
[20:39] <tomreyn> it's permanent
[20:40] <Jeremy31> XATRIX: That is permanent until you change it back to a 3
[20:40] <XATRIX> Cool
[20:40] <tomreyn> you changed the configuration file
[20:40] <XATRIX> I don't think WF powersave save much batter power
[20:40] <XATRIX> Ah..right
[20:41] <tomreyn> note that you will need to reboot or restart network manager to apply the change
[20:41] <XATRIX> No problem, will test it tomorrow
[20:41] <Jeremy31> XATRIX: you could also edit /usr/src/rtl8821ce-<IP_ADDRESS>/Makefile and change line 52 to CONFIG_POWER_SAVING = n
[20:41] <XATRIX> emm..not a good idea i guess, to change something in code here
[20:42] <XATRIX> Next update , and i'll loose the changes or whatever
[20:42] <Jeremy31> XATRIX: The kernel you have installed now wont be affected, the next one will see the change
[20:43] <XATRIX> Alright, i'll test the conf changes, if it won't work, i'll change the code
[20:43] <Jeremy31> XATRIX: save the command and just swap the 3 and 2 to reverse it
[20:44] <XATRIX> yeap
[20:44] <XATRIX> thanks for the help guys!
[20:44] <Jeremy31> later
[20:44] <tomreyn> apparently the power saving cofiguration *may* also be stored in an existing connection profile. so you might want / ned to delete the wireless network configuration and re-create it. unless Jeremy31 knows better?
[20:45] <jhutchins> Change one thing at a time.
[20:46] <XATRIX> Also, i have some mess up with bluetooth on this laptop. I guess my Wifi adapater is a part of. I think it's combined with WF/BT
[20:46] <XATRIX> https://pastebin.com/Zy77q6gk
[20:48] <Jeremy31> XATRIX: do you ever use BT?
[20:49] <tomreyn> this should be set to 0 for your hotspot (here: My_WiFi_Hotspot_Name): nmcli connection show My_WiFi_Hotspot_Name | grep ^802-11-wireless.powersave
[20:49] <tomreyn> i mean for your wireless connection profile
[20:50] <XATRIX> 802-11-wireless.powersave:              0 (default)
[20:50] <XATRIX> 802-11-wireless.powersave:              0 (default)
[20:50] <XATRIX> Jeremy31: yeap
[20:50] <XATRIX> BT stereo phones
[20:51] <XATRIX> File transfer mobile phone -> laptop
[20:51] <XATRIX>  time to time 3G/LTE mobile modem
[20:53] <Jeremy31> XATRIX: what result for> cat /sys/modules/rtl8821ce/paramaters/rtw_btcoex_enable
[20:54] <XATRIX> cat: /sys/modules/rtl8821ce/paramaters/rtw_btcoex_enable: No such file or directory
[20:55] <tomreyn> maybe it's called slightly differently?   modinfo -p rtl8821ce | grep coex
[20:56] <XATRIX> rtw_btcoex_enable:BT co-existence on/off, 0:off, 1:on, 2:by efuse (int)
[20:56] <tomreyn> oh there's a typo in parameters
[20:56] <tomreyn> oh there's a typo in "parameters"
[20:57] <tomreyn> cat /sys/modules/rtl8821ce/parameters/rtw_btcoex_enable
[20:57] <Jeremy31> It is /sys/module
[20:57] <XATRIX> cat: /sys/modules/rtl8821ce/parameters/rtw_btcoex_enable: No such file or directory
[20:57] <Jeremy31> It is set to 2 by default
[20:58] <rob0> Pair o' 'maters!  Yum!
[20:58] <tomreyn> cat /sys/module/rtl8821ce/parameters/rtw_btcoex_enable
[21:01] <Jeremy31> XATRIX: you could test different setting of the btcoex but it will disconnect wifi for a few seconds>  sudo modprobe -r rtl8821ce && sleep 5 && sudo modprobe rtl8821ce rtw_btcoex_enable=0 # then change the 0 to 1 for the second test
[21:01] <XATRIX> tomreyn: 2
[21:01] <XATRIX> Ok, let's try
[21:05] <XAT> So, now, i have some segfaults in dmesg. But i was able to connect to wireless. And now my NetworkManager system tray indicator shows me no signal to. But the link works pretty well
[21:05] <XAT> I can check it with 'iwconfig' - it tells me 72Mb\s
[21:06] <XAT> Still 'hcitool dev' says me i have no BT
[21:07] <Jeremy31> XAT: URL from terminal for> lsusb | nc termbin.com 9999
[21:07] <XAT> https://termbin.com/7m4x
[21:08] <XAT> But i'm sure it's not a usb-controller
[21:08] <XAT> It's a WF/BT mini-Pciex laptop interface
[21:09] <Jeremy31> XAT: try a reboot, most of the integrated BT are on the USB bus even if the wifi is PCI(e)
[21:10] <XAT> Ah..sorry then. Din't know it
[21:10] <XAT> ok.. restarting
[21:13] <oerheks> there was a BT fix for 8821ce https://github.com/tomaspinho/rtl8821ce/issues/19#issuecomment-452196840 ..
[21:13] <oerheks> as BT might be detected as lmp_subver=8221 & hci_ref=000c.
[21:13] <XATRIX> Ok, restarted 2 times, because of i had AMD-Vi: Event logged [IO_PAGE_FAULT again
[21:13] <XATRIX> time times in a row
[21:14] <XATRIX> Now my NM indicator works well, it shows the singal power. I have a connection. Iwconfig says power management:off
[21:14] <XATRIX> Still no BT
[21:15] <Jeremy31> XATRIX: You might need to power it down as for some reason no BT device showed in lsusb
[21:16] <XATRIX> Also, there's a problem with a backlight. After we fixed an amdgpu drivers, i'm able to control the backlight. But after the restart of a laptop, my BL is on MAX level. If i try to change it, it does.
[21:16] <XATRIX> Jeremy31: sorry ?
[21:17] <Jeremy31> XATRIX: Complete power off instead of a reboot
[21:17] <XATRIX> Ahh
[21:17] <XATRIX> Alright. I'll try now
[21:19] <XATRIX> Also, i have a kernel string param in grub: pci=noaer
[21:20] <Jeremy31> XATRIX: I don't think that would do it.  It might be a bad connection between the wifi card and the motherboard
[21:20] <XATRIX> still hcitool dev says no devices
[21:21] <jhutchins> Tab completion is your friend.
[21:21] <XATRIX> Jeremy31: it's a new laptop, never been disassembled
[21:21] <Jeremy31> XATRIX: Might try a BIOS reset to defaults.
[21:22] <XATRIX> Did it a few days ago, after firmware upgrade
[21:22] <XATRIX> I still think that the trouble is in rtl8821ce driver
[21:23] <XATRIX> it's a modern WF/BT interface. So i think it has some bugs in
[21:25] <Jeremy31> XATRIX: I will still expect to see the BT part in lsusb results
[21:25] <oerheks> lspci ..
[21:26] <XATRIX> sorry. https://termbin.com/i3us
[21:27] <XATRIX> 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter
[21:27] <XATRIX> lspci
[21:31] <Jeremy31> Still no BT device shown.  I am not sure why
[21:32] <i-garrison> XATRIX: ooc what does this say: dmesg | grep 'RTL: rtl:'
[22:19] <ldericher> I wanna freshly install some Ubuntu MATE machines as soon as 22.04 is released. if I install the pre-release now - will that just transition into being the mainline version in a few days, or should I expect major hiccups?
[22:19] <tomreyn> if you will run   sudo apt full-upgrade    it will.
[22:20] <tomreyn> (after sudo apt update)
[22:20] <tomreyn> or, for automation,    sudo apt-get update && sudo apt-get dist-upgrade
[22:20] <tomreyn> !next | ldericher
[22:28] <jhutchins> The stable version of Ubuntu 22.04 is scheduled to be released on April 21, 2022.


[04:26] <sagaci> head_victim: was there something extra needed to invite the team to add suggestions, just in ref: to the re-marked TODO on the ISO blueprint.
[05:05] <ikt_> hello all :)
[05:45] <head_victim> ikt: gday mate
[07:13] <hot_wheelz> anyone been able to install ubuntu-11.10-desktop-amd64.iso successfully?
[07:13] <hot_wheelz> so mythbuntu
[07:13] <hot_wheelz> i mean mythbuntu
[15:23] <sagaci> that's good, 5 years desktop LTS
[15:35] <ikt> wha?
[21:09] <jan_> hi i was wondering if anyone here has used edubuntu ltsp
[21:10] <jan_> it will be helpful so that i have few questions on ot


[08:54] <smb> Is this channel the right one to ask about an additional hint to britney badtest(s)?
[08:54] <LocutusOfBorg> yep
[08:55] <smb> So I have added a comment to the bug report here https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1878214. Basically the upload is stuck due to s390x failing which looks to be a known thing
[08:55] <smb> https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#dahdi-linux
[08:56] <LocutusOfBorg> apw, ^^ yes, we fixed dkms to stop throwing errors in bionic or so
[08:56] <LocutusOfBorg> can we please get an hint?
[08:57] <smb> apw, sorry, did not know it would fire back at you :)
[08:58] <LocutusOfBorg> he should be the one who hinted it at the begin, that backlight driver doesn't exist on s390x, we did a lot of work to exclude dkms building when the arch was not supported
[08:58] <LocutusOfBorg> but that work didn't reach xenial, and I don't think it should be backported there
[08:58] <smb> No, certainly one (and if only minimally) hopes to stop caring that much about xenial soon
[09:25] <LocutusOfBorg> and thanks to you, I updated dkms to debian sid and groovy :)
[09:26] <smb> heh :)
[10:38] <Laney> https://people.canonical.com/~ubuntu-archive/laney/proposed-migration/update_excuses.html
[10:38] <Laney> first run from over the weekend
[10:38] <Laney> couple of bugs there heh
[11:35] -queuebot:#ubuntu-release- New source: plasma-wayland-protocols (groovy-proposed/primary) [1.0-0ubuntu1]
[11:50]  * Laney runs again
[12:58] -queuebot:#ubuntu-release- New binary: linux-signed-gcp-5.3 [amd64] (bionic-proposed/main) [5.3.0-1027.29~18.04.1] (no packageset)
[13:36] -queuebot:#ubuntu-release- Unapproved: deja-dup (focal-proposed/main) [40.6-1ubuntu2 => 40.7-0ubuntu1] (ubuntu-desktop)
[13:54] -queuebot:#ubuntu-release- New binary: u-boot [amd64] (groovy-proposed/main) [2020.04+dfsg-2ubuntu1] (core)
[13:56] <Laney> We managed to recover some more arm64/ppc64el capacity
[13:56] <Laney> so those queues should start going down faster now
[13:56] <Laney> hopefully
[14:02] <coreycb> sil2100: hello, if you happen to have cycles today we have neutron packages in the eoan and xenial unapproved queue
[14:14] -queuebot:#ubuntu-release- New binary: u-boot [riscv64] (groovy-proposed/main) [2020.04+dfsg-2ubuntu1] (core)
[14:22] <sil2100> coreycb: o/
[14:23] <coreycb> sil2100: o/
[14:56] -queuebot:#ubuntu-release- Unapproved: rejected evince [source] (focal-proposed) [3.36.5-0ubuntu1]
[15:00] -queuebot:#ubuntu-release- Unapproved: evince (focal-proposed/main) [3.36.0-2 => 3.36.5-0ubuntu1] (ubuntu-desktop)
[15:13] <vorlon> LocutusOfBorg: because perl-base is essential, and apt won't remove perl-base:amd64 in favor of perl-base:i386 in the cross-test environment.  These just need to be hinted away.
[15:16] -queuebot:#ubuntu-release- Unapproved: gnutls28 (focal-proposed/main) [3.6.13-2ubuntu1.1 => 3.6.13-2ubuntu1.2] (core, i386-whitelist)
[15:23] <vorlon> LocutusOfBorg: hinted now
[15:31] <seb128> sil2100, hey, any chance you could review that gnutls SRU ^ it's a small diff and should fix connection to yahoo and other servers failing
[15:57] -queuebot:#ubuntu-release- Unapproved: parted (bionic-proposed/main) [3.2-20ubuntu0.2 => 3.2-20ubuntu0.3] (core)
[16:18] -queuebot:#ubuntu-release- New: accepted dlpack [amd64] (groovy-proposed) [0.0~git20200217.3ec0443-2]
[16:18] -queuebot:#ubuntu-release- New: accepted dlpack [armhf] (groovy-proposed) [0.0~git20200217.3ec0443-2]
[16:18] -queuebot:#ubuntu-release- New: accepted dlpack [riscv64] (groovy-proposed) [0.0~git20200217.3ec0443-2]
[16:18] -queuebot:#ubuntu-release- New: accepted mp3check [amd64] (groovy-proposed) [0.8.7-3.1]
[16:18] -queuebot:#ubuntu-release- New: accepted mp3check [armhf] (groovy-proposed) [0.8.7-3.1]
[16:18] -queuebot:#ubuntu-release- New: accepted dlpack [arm64] (groovy-proposed) [0.0~git20200217.3ec0443-2]
[16:18] -queuebot:#ubuntu-release- New: accepted dlpack [s390x] (groovy-proposed) [0.0~git20200217.3ec0443-2]
[16:18] -queuebot:#ubuntu-release- New: accepted mp3check [riscv64] (groovy-proposed) [0.8.7-3.1]
[16:18] -queuebot:#ubuntu-release- New: accepted dlpack [ppc64el] (groovy-proposed) [0.0~git20200217.3ec0443-2]
[16:18] -queuebot:#ubuntu-release- New: accepted mp3check [arm64] (groovy-proposed) [0.8.7-3.1]
[16:18] -queuebot:#ubuntu-release- New: accepted golang-github-joyent-gosdc [amd64] (groovy-proposed) [0.0~git20161202.ec8b350-1]
[16:18] -queuebot:#ubuntu-release- New: accepted mailutils [arm64] (groovy-proposed) [1:3.9-2]
[16:18] -queuebot:#ubuntu-release- New: accepted mailutils [ppc64el] (groovy-proposed) [1:3.9-2]
[16:18] -queuebot:#ubuntu-release- New: accepted mailutils [s390x] (groovy-proposed) [1:3.9-2]
[16:18] -queuebot:#ubuntu-release- New: accepted mp3check [s390x] (groovy-proposed) [0.8.7-3.1]
[16:18] -queuebot:#ubuntu-release- New: accepted mailutils [amd64] (groovy-proposed) [1:3.9-2]
[16:18] -queuebot:#ubuntu-release- New: accepted mailutils [riscv64] (groovy-proposed) [1:3.9-2]
[16:18] -queuebot:#ubuntu-release- New: accepted mailutils [armhf] (groovy-proposed) [1:3.9-2]
[16:18] -queuebot:#ubuntu-release- New: accepted mp3check [ppc64el] (groovy-proposed) [0.8.7-3.1]
[16:19] -queuebot:#ubuntu-release- New: accepted gnome-pass-search-provider [amd64] (groovy-proposed) [0.0~20191115+da2db41-1]
[16:19] -queuebot:#ubuntu-release- New: accepted gnustep-gui [arm64] (groovy-proposed) [0.28.0-2]
[16:19] -queuebot:#ubuntu-release- New: accepted gnustep-gui [ppc64el] (groovy-proposed) [0.28.0-2]
[16:19] -queuebot:#ubuntu-release- New: accepted golang-github-suapapa-go-eddystone [amd64] (groovy-proposed) [0.0~git20190827.8d8c1bb-1]
[16:19] -queuebot:#ubuntu-release- New: accepted haskell-aeson-diff [amd64] (groovy-proposed) [<IP_ADDRESS>-1]
[16:19] -queuebot:#ubuntu-release- New: accepted r-cran-epiestim [amd64] (groovy-proposed) [2.2-3+dfsg-1]
[16:19] -queuebot:#ubuntu-release- New: accepted gnustep-gui [amd64] (groovy-proposed) [0.28.0-2]
[16:19] -queuebot:#ubuntu-release- New: accepted gnustep-gui [s390x] (groovy-proposed) [0.28.0-2]
[16:19] -queuebot:#ubuntu-release- New: accepted libtest-dbic-expectedqueries-perl [amd64] (groovy-proposed) [2.002-2]
[16:19] -queuebot:#ubuntu-release- New: accepted gnustep-gui [armhf] (groovy-proposed) [0.28.0-2]
[16:19] -queuebot:#ubuntu-release- New: accepted google-auto-value-java [amd64] (groovy-proposed) [1.7.2-1]
[16:19] -queuebot:#ubuntu-release- New: accepted libtest-metrics-any-perl [amd64] (groovy-proposed) [0.01-2]
[16:20] -queuebot:#ubuntu-release- New: accepted rustc [amd64] (groovy-proposed) [1.43.0+dfsg1+llvm-1~exp1ubuntu1]
[16:20] -queuebot:#ubuntu-release- New: accepted rustc [armhf] (groovy-proposed) [1.43.0+dfsg1+llvm-1~exp1ubuntu1]
[16:20] -queuebot:#ubuntu-release- New: accepted rustc [ppc64el] (groovy-proposed) [1.43.0+dfsg1+llvm-1~exp1ubuntu1]
[16:20] -queuebot:#ubuntu-release- New: accepted rustc [arm64] (groovy-proposed) [1.43.0+dfsg1+llvm-1~exp1ubuntu1]
[16:20] -queuebot:#ubuntu-release- New: accepted rustc [s390x] (groovy-proposed) [1.43.0+dfsg1+llvm-1~exp1ubuntu1]
[16:20] -queuebot:#ubuntu-release- New: accepted rustc [i386] (groovy-proposed) [1.43.0+dfsg1+llvm-1~exp1ubuntu1]
[16:23] -queuebot:#ubuntu-release- New: accepted cd-boot-images-ppc64el [source] (groovy-proposed) [3]
[16:28] -queuebot:#ubuntu-release- New binary: cd-boot-images-ppc64el [ppc64el] (groovy-proposed/universe) [3] (no packageset)
[16:33] -queuebot:#ubuntu-release- Unapproved: mesa (bionic-proposed/main) [20.0.4-2ubuntu1~18.04.2 => 20.0.8-0ubuntu1~18.04.1] (core, xorg)
[16:35] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (focal-proposed/main) [0.136ubuntu6.1 => 0.136ubuntu6.2] (core, i386-whitelist)
[16:36] <LocutusOfBorg> vorlon, thanks!
[16:36] <LocutusOfBorg> btw please NBS cleanup libplacebo7? this makes vlc migrate and the transition end, hopefully
[16:37] -queuebot:#ubuntu-release- Unapproved: libvpd (focal-proposed/main) [2.2.6-1build1 => 2.2.6-1ubuntu1~20.04.1] (core)
[16:37] <LocutusOfBorg> some archive admin might have decrufted it before the build was over, it still exists on riscv64 and s390x
[16:41] <sil2100> seb128: hey! Sure, I'll try, but I have my +1 maintenance shift today and tomorrow so I'm only doing minimal SRU work - will get to it on Thursday for sure if not
[16:44] -queuebot:#ubuntu-release- Unapproved: accepted makedumpfile [source] (focal-proposed) [1:1.6.7-1ubuntu2.1]
[16:45] -queuebot:#ubuntu-release- Unapproved: accepted makedumpfile [source] (eoan-proposed) [1:1.6.6-2ubuntu2.1]
[16:48] -queuebot:#ubuntu-release- Unapproved: accepted makedumpfile [source] (bionic-proposed) [1:1.6.5-1ubuntu1~18.04.5]
[16:49] -queuebot:#ubuntu-release- Unapproved: accepted makedumpfile [source] (xenial-proposed) [1:1.6.3-2~16.04.3]
[17:15] -queuebot:#ubuntu-release- Unapproved: libxau (bionic-proposed/main) [1:1.0.8-1 => 1:1.0.8-1ubuntu1] (core, xorg)
[17:16] -queuebot:#ubuntu-release- New binary: bamkit [amd64] (groovy-proposed/none) [0.0.1+git20170413.ccd079d-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: bbhash [s390x] (groovy-proposed/none) [1.0.0-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: libbaseencode [s390x] (groovy-proposed/none) [1.0.9-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: meliae [s390x] (groovy-proposed/none) [0.5.1-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: wys [amd64] (groovy-proposed/none) [0.1.7-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: bbhash [amd64] (groovy-proposed/none) [1.0.0-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: magnum-tempest-plugin [amd64] (groovy-proposed/none) [1.0.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: wys [s390x] (groovy-proposed/none) [0.1.7-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: cloudkitty-tempest-plugin [amd64] (groovy-proposed/none) [2.0.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: senlin-tempest-plugin [amd64] (groovy-proposed/none) [1.0.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: heat-tempest-plugin [amd64] (groovy-proposed/none) [1.0.0-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: libstatistics-pca-perl [amd64] (groovy-proposed/none) [0.0.1-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: mmtf-python [amd64] (groovy-proposed/none) [1.1.2-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: ylva [amd64] (groovy-proposed/none) [1.6-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: libbaseencode [amd64] (groovy-proposed/none) [1.0.9-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: python-django-import-export [amd64] (groovy-proposed/none) [2.2.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: meliae [amd64] (groovy-proposed/none) [0.5.1-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: ylva [s390x] (groovy-proposed/none) [1.6-2] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: abacas [amd64] (groovy-proposed/universe) [1.3.1-8] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: jsmn [amd64] (groovy-proposed/none) [1.1.0-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: tomcat-jakartaee-migration [amd64] (groovy-proposed/none) [0.0.2-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: python-django-cache-machine [amd64] (groovy-proposed/none) [1.1.0-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: bbhash [ppc64el] (groovy-proposed/universe) [1.0.0-2] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: python-django-ical [amd64] (groovy-proposed/universe) [1.7.0-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- Unapproved: lsvpd (focal-proposed/main) [1.7.10-1build1 => 1.7.10-1ubuntu0.1] (core)
[17:25] -queuebot:#ubuntu-release- New binary: bbhash [riscv64] (groovy-proposed/universe) [1.0.0-2] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: meliae [ppc64el] (groovy-proposed/universe) [0.5.1-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: ylva [ppc64el] (groovy-proposed/universe) [1.6-2] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: libbaseencode [ppc64el] (groovy-proposed/universe) [1.0.9-2] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: wys [ppc64el] (groovy-proposed/universe) [0.1.7-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: ylva [riscv64] (groovy-proposed/universe) [1.6-2] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: libbaseencode [riscv64] (groovy-proposed/universe) [1.0.9-2] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: bbhash [arm64] (groovy-proposed/universe) [1.0.0-2] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: meliae [riscv64] (groovy-proposed/universe) [0.5.1-1] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: libbaseencode [arm64] (groovy-proposed/universe) [1.0.9-2] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: wys [armhf] (groovy-proposed/universe) [0.1.7-1] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: ylva [armhf] (groovy-proposed/universe) [1.6-2] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: libbaseencode [armhf] (groovy-proposed/universe) [1.0.9-2] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: ylva [arm64] (groovy-proposed/universe) [1.6-2] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: meliae [armhf] (groovy-proposed/universe) [0.5.1-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: wys [arm64] (groovy-proposed/universe) [0.1.7-1] (no packageset)
[17:39] -queuebot:#ubuntu-release- New binary: meliae [arm64] (groovy-proposed/universe) [0.5.1-1] (no packageset)
[17:41] -queuebot:#ubuntu-release- New binary: wys [riscv64] (groovy-proposed/universe) [0.1.7-1] (no packageset)
[17:47] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (bionic-proposed/main) [1.10~ubuntu18.04.3 => 1.10~ubuntu18.04.4] (no packageset)
[17:47] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (focal-proposed/main) [1.27 => 1.27ubuntu0.1] (core)
[17:47] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (eoan-proposed/main) [1.10.2 => 1.10.2ubuntu0.1] (core)
[17:53] <vorlon> xnox: "shim is broken, just use grub" - false?
[17:53] <vorlon> xnox: (cd-boot-images-arm64)
[17:54] <xnox> vorlon: i think i forgot which one is broken (shim or grub), but i thought currently in groovy we have broken shim (the reverted one, without arm64 signature) and broken grub (needs rebase) to work in secureboot on arm64.
[17:54] <xnox> vorlon:  thus shim->grub does not work in groovy at the moment, until we rebase grub & get new shim.
[17:54] <xnox> vorlon:  but booting grub directly works.
[17:55] <xnox> vorlon:  what's wrong in the above?
[17:55] -queuebot:#ubuntu-release- New: accepted cd-boot-images-arm64 [source] (groovy-proposed) [3]
[17:55] <vorlon> xnox: it doesn't work if secureboot is turned on.  But I don't think we have any problems booting shim->grub with sb disabled.
[17:55] <xnox> vorlon:  oh really. In that case i should upload better cd-boot-images-arm64!
[17:55] <vorlon> xnox: I was pretty sure we had the working shim in focal and groovy
[17:56] <xnox> ack
[17:56] <xnox> will test in kvm as well
[17:57] <sbeattie> Hi, can we get the fwupd uefi images in the unappoved queue for focal, eoan, and bionic published. We have fwupd-signed source pacakges in the unapproved queues to build when the uefi bits are available.
[18:01] -queuebot:#ubuntu-release- New binary: cd-boot-images-arm64 [arm64] (groovy-proposed/none) [3] (no packageset)
[18:07] <sbeattie> ubuntu-achive: Hi, can the security team get the fwupd uefi images in the unappoved queue for focal, eoan, and bionic published. We have fwupd-signed source pacakges in the unapproved queues to build when the uefi bits are available.
[18:26] -queuebot:#ubuntu-release- Unapproved: accepted fwupd-signed [source] (focal-proposed) [1.27ubuntu0.1]
[18:36] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.9-4ubuntu0.1 => 1.3.10-1ubuntu1] (core)
[19:07] -queuebot:#ubuntu-release- Unapproved: accepted fwupd-signed [source] (eoan-proposed) [1.10.2ubuntu0.1]
[19:10] -queuebot:#ubuntu-release- New binary: gnustep-back [s390x] (groovy-proposed/universe) [0.28.0-2] (ubuntustudio)
[19:11] -queuebot:#ubuntu-release- New binary: gnustep-back [ppc64el] (groovy-proposed/universe) [0.28.0-2] (ubuntustudio)
[19:12] -queuebot:#ubuntu-release- New binary: gnustep-back [amd64] (groovy-proposed/universe) [0.28.0-2] (ubuntustudio)
[19:13] -queuebot:#ubuntu-release- New binary: gnustep-back [arm64] (groovy-proposed/universe) [0.28.0-2] (ubuntustudio)
[19:13] -queuebot:#ubuntu-release- New binary: gnustep-back [armhf] (groovy-proposed/universe) [0.28.0-2] (ubuntustudio)
[19:17] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-signed [source] (bionic-proposed) [1.10~ubuntu18.04.4]
[19:18] -queuebot:#ubuntu-release- Unapproved: accepted fwupd-signed [source] (bionic-proposed) [1.10~ubuntu18.04.4]
[19:18] <vorlon> sbeattie: I think this is all done now
[19:36] <sbeattie> vorlon: ugh, looks like for focal we need a different version? https://launchpad.net/ubuntu/+source/fwupd-signed/1.27ubuntu0.1
[19:41] <vorlon> sbeattie: yep, appears so
[19:43] <vorlon> sbeattie: in particular, it seems that 1.27ubuntu0.1 sorts earlier than 1.27+, so the fwupd part of the version string needs to be bumped somehow
[19:43] <vorlon> whether through reupload of fwupd or by more aggressive mangling in fwupd-signed's debian/rules
[19:47] <sbeattie> vorlon: why did this not get rejected in eoan?
[19:47] <sbeattie> is it only checking the version in the release pocket and not eoan-updates?
[19:48] <vorlon> sbeattie: uh possibly
[19:56] <Bashing-om> vorlon: 2) 18.04 upgrade: "The following packages have been kept back: fwupd ".
[20:37] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (eoan-proposed/main) [1.10.2ubuntu0.1 => 1.10.3ubuntu1] (core)
[20:40] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (focal-proposed/main) [1.27ubuntu0.1 => 1.27.1ubuntu1] (core)
[20:41] <sbeattie> vorlon: okay, updated fwupd-signed sources with bumped versions that should superced existing versions in the eoan and focal unapproved queues ^
[20:50] <sbeattie> (adjusting fwupd-signed versions seemed less error prone than trying to adjust debian/rules for this update.)
[20:59] <sbeattie> also, as a heads up, superm1 uploaded a followup sru for fwupd to the focal proposed queue.
[21:27] -queuebot:#ubuntu-release- Unapproved: accepted fwupd-signed [source] (focal-proposed) [1.27.1ubuntu1]
[21:33] -queuebot:#ubuntu-release- Unapproved: accepted fwupd-signed [source] (eoan-proposed) [1.10.3ubuntu1]
[21:35] <sbeattie> woot, thanks!
[21:52] -queuebot:#ubuntu-release- New: accepted gnustep-back [amd64] (groovy-proposed) [0.28.0-2]
[21:52] -queuebot:#ubuntu-release- New: accepted gnustep-back [armhf] (groovy-proposed) [0.28.0-2]
[21:52] -queuebot:#ubuntu-release- New: accepted gnustep-back [s390x] (groovy-proposed) [0.28.0-2]
[21:52] -queuebot:#ubuntu-release- New: accepted gnustep-back [arm64] (groovy-proposed) [0.28.0-2]
[21:52] -queuebot:#ubuntu-release- New: accepted gnustep-back [ppc64el] (groovy-proposed) [0.28.0-2]
[21:52] -queuebot:#ubuntu-release- New: accepted bbhash [arm64] (groovy-proposed) [1.0.0-2]
[21:52] -queuebot:#ubuntu-release- New: accepted libbaseencode [armhf] (groovy-proposed) [1.0.9-2]
[21:52] -queuebot:#ubuntu-release- New: accepted meliae [armhf] (groovy-proposed) [0.5.1-1]
[21:52] -queuebot:#ubuntu-release- New: accepted wys [arm64] (groovy-proposed) [0.1.7-1]
[21:52] -queuebot:#ubuntu-release- New: accepted wys [riscv64] (groovy-proposed) [0.1.7-1]
[21:52] -queuebot:#ubuntu-release- New: accepted ylva [armhf] (groovy-proposed) [1.6-2]
[21:53] -queuebot:#ubuntu-release- New: accepted libbaseencode [arm64] (groovy-proposed) [1.0.9-2]
[21:53] -queuebot:#ubuntu-release- New: accepted meliae [riscv64] (groovy-proposed) [0.5.1-1]
[21:53] -queuebot:#ubuntu-release- New: accepted ylva [arm64] (groovy-proposed) [1.6-2]
[21:53] -queuebot:#ubuntu-release- New: accepted meliae [arm64] (groovy-proposed) [0.5.1-1]
[21:53] -queuebot:#ubuntu-release- New: accepted wys [armhf] (groovy-proposed) [0.1.7-1]
[21:53] -queuebot:#ubuntu-release- New: accepted bbhash [ppc64el] (groovy-proposed) [1.0.0-2]
[21:53] -queuebot:#ubuntu-release- New: accepted jsmn [amd64] (groovy-proposed) [1.1.0-1]
[21:53] -queuebot:#ubuntu-release- New: accepted libbaseencode [riscv64] (groovy-proposed) [1.0.9-2]
[21:53] -queuebot:#ubuntu-release- New: accepted python-django-cache-machine [amd64] (groovy-proposed) [1.1.0-1]
[21:53] -queuebot:#ubuntu-release- New: accepted wys [ppc64el] (groovy-proposed) [0.1.7-1]
[21:53] -queuebot:#ubuntu-release- New: accepted ylva [riscv64] (groovy-proposed) [1.6-2]
[21:53] -queuebot:#ubuntu-release- New: accepted bbhash [riscv64] (groovy-proposed) [1.0.0-2]
[21:53] -queuebot:#ubuntu-release- New: accepted meliae [ppc64el] (groovy-proposed) [0.5.1-1]
[21:53] -queuebot:#ubuntu-release- New: accepted ylva [ppc64el] (groovy-proposed) [1.6-2]
[21:53] -queuebot:#ubuntu-release- New: accepted libbaseencode [ppc64el] (groovy-proposed) [1.0.9-2]
[21:53] -queuebot:#ubuntu-release- New: accepted python-django-ical [amd64] (groovy-proposed) [1.7.0-1]
[21:53] -queuebot:#ubuntu-release- New: accepted abacas [amd64] (groovy-proposed) [1.3.1-8]
[21:53] -queuebot:#ubuntu-release- New: accepted libbaseencode [amd64] (groovy-proposed) [1.0.9-2]
[21:53] -queuebot:#ubuntu-release- New: accepted meliae [amd64] (groovy-proposed) [0.5.1-1]
[21:53] -queuebot:#ubuntu-release- New: accepted python-django-import-export [amd64] (groovy-proposed) [2.2.0-1]
[21:53] -queuebot:#ubuntu-release- New: accepted wys [amd64] (groovy-proposed) [0.1.7-1]
[21:53] -queuebot:#ubuntu-release- New: accepted ylva [s390x] (groovy-proposed) [1.6-2]
[21:53] -queuebot:#ubuntu-release- New: accepted heat-tempest-plugin [amd64] (groovy-proposed) [1.0.0-2]
[21:53] -queuebot:#ubuntu-release- New: accepted mmtf-python [amd64] (groovy-proposed) [1.1.2-2]
[21:53] -queuebot:#ubuntu-release- New: accepted ylva [amd64] (groovy-proposed) [1.6-2]
[21:54] -queuebot:#ubuntu-release- New: accepted libstatistics-pca-perl [amd64] (groovy-proposed) [0.0.1-1]
[21:54] -queuebot:#ubuntu-release- New: accepted tomcat-jakartaee-migration [amd64] (groovy-proposed) [0.0.2-1]
[21:54] -queuebot:#ubuntu-release- New: accepted bamkit [amd64] (groovy-proposed) [0.0.1+git20170413.ccd079d-2]
[21:54] -queuebot:#ubuntu-release- New: accepted bbhash [s390x] (groovy-proposed) [1.0.0-2]
[21:54] -queuebot:#ubuntu-release- New: accepted libbaseencode [s390x] (groovy-proposed) [1.0.9-2]
[21:54] -queuebot:#ubuntu-release- New: accepted meliae [s390x] (groovy-proposed) [0.5.1-1]
[21:54] -queuebot:#ubuntu-release- New: accepted wys [s390x] (groovy-proposed) [0.1.7-1]
[21:54] -queuebot:#ubuntu-release- New: accepted bbhash [amd64] (groovy-proposed) [1.0.0-2]
[21:54] -queuebot:#ubuntu-release- New: accepted magnum-tempest-plugin [amd64] (groovy-proposed) [1.0.0-1]
[21:54] -queuebot:#ubuntu-release- New: accepted cloudkitty-tempest-plugin [amd64] (groovy-proposed) [2.0.0-1]
[21:54] -queuebot:#ubuntu-release- New: accepted senlin-tempest-plugin [amd64] (groovy-proposed) [1.0.0-1]
[23:15] -queuebot:#ubuntu-release- New binary: python-nest-asyncio [amd64] (groovy-proposed/universe) [1.3.3-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: error-prone-java [amd64] (groovy-proposed/universe) [2.3.2+ds-1] (no packageset)