[00:00] <soee> http://www.statista.com/statistics/268299/most-popular-internet-browsers/
[00:00] <soee> i wouldnt say our users but generally users
[00:01] <soee> so the current, the new ones that might come etc.
[00:26] <ScottK> Generically, I think FF or Chromium might be OK, but for the better security support for FF.  Chromium is not so great on low memory systems either.
[04:30] <msx> Gn! I'm looking for the KCM user-management GIT address but I'm unable to find it, I think it's a wonderful approach for GUI user managment and I would like to bring it Arch Linux and Chakra, can you guys please point me in the right direction? Thanks in advance =D
[05:33] <ahoneybun> lordievader: valorie http://summit.ubuntu.com/uds-1311/meeting/21980/community-1311-docteam-roundtable/ I believe that one of us should be there. I can not as I will be at work.
[05:48] <valorie> I think I have a doctor's appt, but I'll check
[05:59]  * ahoneybun is going to see "Day of the Doctoer"
[05:59] <ahoneybun> Doctor
[08:49] <jalcine> msx: might wanna ask #kde-devel that
[11:16] <BluesKaj> 'Morning all
[11:52] <markey> uhm, I'm wondering if I actually have the gold linker installed, as my linking got so slow here
[11:53] <markey> can't make sense of what apt-get is telling me here:
[11:53] <markey> http://pastie.org/8484695
[11:53] <markey> looks like it's not installed, but installing it doesn't work either
[11:56] <markey> Mamarok: do you know what this means? ^
[13:33] <soee> :/ Samsung started to ship Android 4.3 for S3 and now they stopped because of problems lol
[13:33] <soee> how do they test it before release ? :)
[14:47] <lordievader> Good afternoon.
[16:04] <msx> jalcine: ok! I came because I know Johnattan is behind it, but #kde-devel seems the proper please to ask. Thank you!
[16:04] <msx> *came here


[00:35] <_Techie_> heya bal
[02:03] <frenzy42> so i upgraded to the beta this after noon on my laptop and now my screen won't stop flickering
[02:06] <frenzy42> how should i stop it
[02:19] <rr72> is anyone else having problems with remote places in gigolo not opening a file browser on 9.10?
[02:50] <rr72> does xubuntu 9.10 gigolo come with support for sftp/ssh remote location or does it needed to be added?
[04:54] <Balsaq> is there a way to clear my screen of all the previous text or chat?
[05:04] <leaf-sheep> Does anybody here know the best command for slim-xubuntu-desktop?
[05:04] <leaf-sheep> >_>
[06:18] <_Techie_> yay, im down $30 but im back on the net again
[06:35] <Balsaq> yeah huh Tech
[06:38] <Balsaq> _Techie_  you were saying i outta do the server thing here with my old computer. they are giving me those old dels tomorrow.....how would it benefit my network if i did that?
[06:39] <_Techie_> yeah, i can guide you through setting up a ZNC server and bypassing work firewalls and proxy's so you can use a proper IRC connection
[06:40] <_Techie_> and it will also be a great learning experience
[06:40] <Balsaq> bypass? they are all going to be at my home?
[06:41] <_Techie_> no, i mean if your work has a restrictive proxy or firewall implemented at work i can help you tunnel out to your home connection
[06:41] <Balsaq> oh yes they got a big one
[06:41] <_Techie_> lemme guess, you can only open web pages
[06:41] <Balsaq> and a whole dept of pro hackers all over it
[06:42] <Balsaq> huge corp w/IT dept
[06:42] <Balsaq> we'll do it here
[06:42] <Balsaq> can i get free internet here at home?
[06:42] <_Techie_> no, unless your ISP implements some sort of free traffic policy
[06:43] <Balsaq> the school is about 300 yards away
[06:44] <_Techie_> you thinking about connecting to their wireless?
[06:44] <Balsaq> well if possible
[06:44] <Balsaq> i pay 20 per month for this stuff
[06:45] <_Techie_> thats not too bad
[06:45] <Balsaq> but wouldnt like it if i get bumped off all the time
[06:45] <Balsaq> is that why you are always in and out
[06:46] <_Techie_> nah, im in and out because i go do other stuff
[06:46] <Balsaq> figured that
[06:46] <_Techie_> or im at school and ihave to go to my next class
[06:47] <Balsaq> i like my connection but would enjoy ridin on the school too for fun but not to cause any trouble
[06:47] <Balsaq> people pull in the lot and use it i hear
[06:47] <Balsaq> 300 yds is too far isnt it
[06:47] <_Techie_> depends on the strength of the network
[06:48] <_Techie_>
[06:48] <_Techie_> 300 yards = 274.32 meters
[06:48] <Balsaq> buy anyway, knowing it all about my home network do i still need or have use for a server
[06:48] <_Techie_> you will be pushing it to the limit if its just a standard connection
[06:49] <_Techie_> depends
[06:49] <Balsaq> so do i have any reason to have a server in my home?
[06:49] <_Techie_> well from a professional point of view, no... from a hobbyist point of view, it wouldnt hurt
[06:49] <Balsaq> as of tommorow i will have 7 PC and a lapper
[06:50] <_Techie_> is this a different lapper, or are you counting the mac?
[06:50] <Balsaq> likie can 1 be a server that host a website that is 24-7 or something (no the mac is the same)
[06:51] <_Techie_> kk, yeah website hosting is easy
[06:51] <_Techie_> you could even do that from whatever computer you use as your main box
[06:51] <Balsaq> ok so the server really is not needed
[06:51] <Balsaq> i thought it proteceted the otheres or something
[06:52] <_Techie_> well you could have it as mp3 storage and stream your music to the lappy via itunes
[06:52] <Balsaq> well the music would be long after i get good at stuff
[06:54] <Balsaq> only do radio usually for some reason-but occasionally play utube rock videoa aand fire up the jackson
[06:55] <Balsaq> i bought a 22 in mon today for 89...stole it
[06:55] <Balsaq> flat panel
[06:56] <_Techie_> nice
[06:56] <Balsaq> cuase all those dell come with the big ole type
[06:57] <Balsaq> hey you should look up the specs and see if there is any hacks i could do too make em better...think i will just toss some rdram in em and run those standard dell internal tests
[07:00] <Balsaq> 1. will get xp pro sp3, 2, xubuntu, 3. pupptlinux 4. my old dell has ubuntu.....NETWORK
[07:00] <Balsaq> THER EST WHO KNOWS
[07:01] <__Techie__> thats gonna be a large network for one person
[07:02] <Ongaku> Aloha bruderz
[07:03] <__Techie__> sup
[07:03] <Ongaku> Good mornin' Trollz
[07:04] <Balsaq> yeah huh Ongaku
[07:05] <Ongaku> Balsaq brotha aloha
[07:07] <Balsaq> i want to do the website asap T
[07:07] <Ongaku> Anyone from Hungary?
[07:08] <Balsaq> im starving
[07:08] <Ongaku> Balsaq brotha whic website?
[07:08] <Ongaku> which
[07:08] <Balsaq> dunno didnt invent it yet
[07:09] <Ongaku> website for wine and beerz?
[07:11] <_Techie_> well you come up with an idea then you can work out how your gonna make it
[07:11] <Balsaq> _Techie_ how long will it take to get a website built?..once i get the idea
[07:12] <_Techie_> well, depending on the design and if you code it yourself it could take anywhere between a few days to a month+
[07:12] <_Pete_> Balsaq: depends on idea
[07:13] <_Techie_> oh, hello pete
[07:13] <_Pete_> my idea I have now takes 10seconds
[07:13] <Balsaq> hey Pete
[07:13] <_Pete_> morning
[07:13] <Balsaq> ypu 213am here in eastern usa
[07:13] <_Pete_> ready!
[07:13] <_Pete_> # cd /var/www/
[07:13] <_Pete_> root@quadcore:/var/www# cat >idealeas_www.html
[07:13] <_Pete_> no ideas at all
[07:14] <Ongaku> hola Pete britha
[07:14] <Ongaku> brotha
[07:14] <_Pete_> now its ready :)
[07:14] <_Pete_> http://quadcore.homeunix.net/idealeas_www.html
[07:15] <_Techie_> sigh
[07:15] <Balsaq> that was a little bland
[07:15] <Balsaq> may add some clores and a few games
[07:15] <Ongaku> it is a new porn site?:D
[07:16] <Ongaku> that is greta
[07:18] <Balsaq> you see we go back and forth...if i thought my company would keep giving tons of old puters...i would stsart some kind of non profit thing to give free computeres to the needy and blend that into the buntu stuff for free OS's and link it to these chats for free support?/ i dunno
[07:19] <_Techie_> Balsaq- ill see if i can find you one of my old sites
[07:19] <Balsaq> and if they dont know how to use it would go to their house and install it and show en how to use the buntu free
[07:20] <Balsaq> you see if i actually become a non profit they may give hundreds of puters...like  i told you once i saw a guy get 30 one day
[07:22] <Balsaq> i think buntu allows people to use thier logos right?
[07:22] <_Techie_> umm, im not sure
[07:22] <Balsaq> me neither...i know they talk about "open"
[07:23] <Balsaq> prolly ask em whoever they are
[07:28] <Balsaq> so i hope to do a couple installs tomorrow....prolly wont take long cause these processors are bigger than my clunker
[07:28] <Balsaq> hopin uxub is a lot faster than mu ubun
[07:31] <_Techie_> Balsaq- http://quadcore.homeunix.net/~techie/
[07:32] <Balsaq> cool
[07:32] <_Techie_> from back when i primarily did gameservers
[07:32] <Balsaq> so you have old one out there on the www
[07:32] <Ongaku> Techie bruder ccooooll
[07:33] <_Pete_> _Techie_: have you made those pages yourself?
[07:33] <Balsaq> see the gam ething is a great idea to begin with cause the games drive the entire computer business
[07:33] <_Techie_> _Pete_- yep, notepad and nano
[07:33] <_Pete_> nice
[07:33] <Balsaq> notepad?
[07:33] <_Techie_> windows text editor
[07:34] <Ongaku> NLHED = notepad like html editor:D
[07:34] <Balsaq> where is nana _Techie_
[07:34] <Ongaku> windows? that a tonz of penguinzshit
[07:35] <_Techie_> Balsaq- nano is a command line text editor
[07:36] <Balsaq> in linux or windows
[07:36] <_Techie_> linux
[07:36] <Balsaq> man i got a looonnnggg way to go
[07:36] <_Techie_> haha
[07:41] <Balsaq> this guy i know has a website, he does free tech support...i could link too him for part of my service
[07:42] <_Techie_> you do realise most #ubuntu and #xubuntu users can be described the same way
[07:42] <Balsaq> not sure
[07:42] <_Pete_> nerds with nolife?
[07:42] <Sysi> weird hippies?
[07:43] <_Techie_> that sums me up _Pete_
[07:43] <Balsaq> earthy crunchy?
[07:43] <Sysi> i'd say i don't have even nolofe
[07:44] <Balsaq> heck i am married with a full time job and a mortgage!
[07:44] <Balsaq> no kids here though so i guess that throws me in there
[07:45] <Balsaq> a guy did a website called joecartoon...he got so many hits that eventually someone bought it for A TON OF MONEY...so you can do that Techie
[07:46] <Balsaq> if you see joecartoon you will see what atracts so many people that people start offering money to own it
[07:47] <Balsaq> and you already have all the skills
[07:48] <Balsaq> he did maintain it for years before the offer came in...
[07:49] <_Techie_> anyway, im gonna restart into linux to watch some south park
[07:49] <TheSheep> originality
[07:49] <_Techie_> ill be back
[07:50] <Balsaq> where does he go?
[07:56] <_Techie_> okay South Park time
[08:00] <Sysi> swedish lesson..
[08:01] <Sysi> notes with laptop ♥
[08:16] <Ongaku> Hosanna brothers
[08:49] <filthpig> hi all. I have an issue with Xubuntu karmic beta (and the last alpha). Installing and using it is just fine, but after updating the packages and rebooting I cannot start X
[08:51] <filthpig> I can log in from console and all and GDM starts, but when I'm supposed to get my desktop on screen it just throws me back to the login promt
[08:53] <ablomen> filthpig, less /var/log/Xorg.0.log << type that and look for lines starting with (EE)
[08:53] <ablomen> near the bottom
[08:59] <filthpig> ablomen: ok, well, there is nothing with EE there
[09:00] <filthpig> the last few lines are Entering Restore TV, Restore TV PLL, Restore TVHV, Restore TV Restarts, Restore Timing Tablets, Restore TV standard, Leaving Restore TV
[09:01] <filthpig> and that's the end
[09:06] <Ongaku> I am Da King of TrolLZ
[09:06] <Ongaku> Heavy TroLLz Attak Warning!
[09:07] <Ongaku> Whatta muttafucka fat holy shit linuks-penguin now?
[09:07] <Ongaku> They called TUKS
[09:08] <Balsaq> _Techie_ emailed buntu to see if i can use their logos on my site..
[09:09] <ablomen> wow, that was fast
[09:09] <ablomen> filthpig, try running startx
[09:09] <ablomen> see if there are any errors there
[09:10] <filthpig> server is already active for display 0
[09:10] <ablomen> oh, try pressing ctrl+alt+f7
[09:10] <Balsaq> TheSheep: <Balsaq stands and salutes TheSheep!!!>
[09:11] <filthpig> ablomen, I get GDM up and running
[09:11] <TheSheep> Balsaq: please don't do that, just ignore that
[09:11] <_Techie_> Balsaq, that is the power of the silent ops
[09:11] <ablomen> filthpig, ok so it works?
[09:11] <filthpig> no :(
[09:12] <ablomen> huh.. you said and i quote: "I get GDM up and running"
[09:12] <filthpig> when I type my password gdm starts loading my desktop
[09:12] <filthpig> and then I'm thrown back to login
[09:12] <ablomen> hmm
[09:12] <Balsaq> yes i saw it
[09:13] <ablomen> filthpig, did you check your session?
[09:13] <filthpig> however, another bloke over at ubuntu-testing thinks this issue was resolved on monday and wants me to try the lastest build
[09:13] <Balsaq> why does it say to me please don't do that?
[09:13] <TheSheep> Balsaq: they come here for the attention, if you give it to them, they will come back for more
[09:14] <Balsaq> oh i thoughthe was now gone from here and if you look back you will see he was trying to provoke us earlier and you will see we did not help to ignite him
[09:17] <TheSheep> yeah, but he can have another login
[09:19] <Balsaq> i noticed whether i come in as Balsaq or Balsaque it still shows my address so can you now lock it if you choose to do so
[09:20] <Balsaq> lock it on a real troll i mean
[09:21] <Balsaq> _Techie_ can you do that?
[09:50] <lab> hi. I'm trying to install ATI drivers on jaunty 9.04. I followed these instructions and they were a disaster: https://help.ubuntu.com/community/BinaryDriverHowto/ATI   . I googled and I didn't find anything useful. Any suggestion? All worked fine for 8.10, but with 9.04 these drivers are a nightmare.....
[10:05] <Wyzirke> Hozsanna bruderz
[10:06] <Wyzirke> Welcomew back again
[10:51] <nikolam> hm :) did anyone heard of a program for *ubuntu that can turn computer intu mobile telephone, by using usb hardware GSM/GPRS/3G modem?
[10:51] <nikolam> like you are saying something and it transfers into ordinary telephone call over GSM?
[10:52] <lab> hi. I'm trying to install ATI drivers on jaunty 9.04. I followed these instructions and they were a disaster: https://help.ubuntu.com/community/BinaryDriverHowto/ATI   . I googled and I didn't find anything useful. Any suggestion? All worked fine for 8.10, but with 9.04 these drivers are a nightmare.....
[10:52] <nikolam> lab, I always did install of ATI drivers by making .deb packages out of it and hen install
[10:53] <nikolam> maybe you could post your findings on phoronix.com forum, i think there are some AMD/ATI developers there answering questions
[10:53] <nikolam> Or try to use a bit older driver then newest one..
[10:59] <nikolam> lab, try this: http://wiki.cchtml.com/index.php/Main_Page
[10:59] <nikolam> http://wiki.cchtml.com/index.php/Ubuntu
[10:59] <nikolam> http://wiki.cchtml.com/index.php/Ubuntu_Jaunty_Installation_Guide
[11:02] <lab> nikolam: not a good link
[11:02] <lab> already triexc
[11:02] <lab> tried
[11:08] <nikolam> did you made .deb packages? lab
[11:08] <nikolam> what version of amd driver you downloaded?
[11:08] <nikolam> you can also use #ati and #radeon channels
[11:09] <nikolam> My experience with Amd fglrx driver is that if driver does not behave, use older one that does.
[11:10] <nikolam> lab, also on pages like this where you download driver from:
[11:10] <nikolam> http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=<IP_ADDRESS>.36&lang=English
[11:10] <nikolam> there are links where you can send your requests about driver not working well and describe to them
[11:11] <nikolam> As workaround, untill you hit one that works well for your 9.04, you can use opensource driver that comes from ubunut
[11:11] <nikolam> what card it is?
[11:11] <nikolam> also try #ati and #radeonhd channels for fglrx and open driver, respectfully
[11:12] <lab> nikolam: sorry, I really appreciate your help, but I have to tell you to give me tips only if you have already experience with the problem
[11:13] <lab> I'm fighting with it from days and days
[11:14] <nikolam> lab, i installed all fglrx drivers till 9.3 on my machine on 64-bit hardy
[11:14] <nikolam> That is all you need
[11:14] <nikolam> What card it is
[11:14] <lab> nikolam: as said before I need instructions for jaunty. I had no problems with intrepid
[11:15] <nikolam> I posted you link with detailed instructions..
[11:15] <lab> nikolam: they don't work. I already checked that link
[11:15] <nikolam> http://wiki.cchtml.com/index.php/Ubuntu_Jaunty_Installation_Guide
[11:16] <lab> nikolam: It's not good
[11:16] <nikolam> but what don`t work, how you installed, did you made .deb packages or installed directly with GUI?
[11:17] <nikolam> try also previous drivers:
[11:17] <nikolam> http://support.amd.com/us/gpudownload/linux/previous/Pages/radeon_linux.aspx
[11:17] <lab> nikolam: do you have jaunty with ATI ?
[11:17] <nikolam> I have hardy with integrated Ati/amd graphics
[11:18] <nikolam> and i am stuck with latest driver
[11:18] <lab> nikolam: in this case you CAN'T help me
[11:18] <nikolam> lab, you are wrong, i helped you a lot. You can also go to phoronix.com forum and also you can go to ubuntuforums.org
[11:19] <nikolam> most of the answers in my history of usage i found there
[11:19] <nikolam> on ati discussion on ohoronix, even ati/amd developers come you can ask them
[11:19] <lab> nikolam: no, it's a very specific problem, associated with this version (jaunty) of ubuntu. as said before, I had no problems with the previous version. you can't help me in this way
[11:19] <nikolam> anyway, #ati is right channel for closed fglrx driver..
[11:20] <lab> yes, in fact I'm asking in #ati too
[11:20] <nikolam> ok, I tried. :) Use radeonhd till you fix it :)
[12:49] <MaxFrames> hello
[12:49] <MaxFrames> stupid question: I have got a script which sets the gamma for the display; it works if I double click it; how do I make it run automatically when I log on?
[12:51] <MaxFrames> currently the script is in my home directory and is called .xinitrc
[12:53] <Sysi> in "settings" is something like "sessiosns and startup"
[12:53] <Sysi> an there automatic start
[12:53] <MaxFrames> yes I tried that, but it does not let me select the script, it does not show in the selection window
[12:54] <Sysi> i dont have any selection, just add
[12:55] <Sysi> you can run script by ./script
[12:55] <MaxFrames> ?
[12:56] <Sysi> put that to add-window; command
[12:57] <MaxFrames> ok, I'll try
[12:58] <MaxFrames> if I succeed, will the script run at PC boot or at user logon?
[12:58] <Sysi> on logon
[12:59] <MaxFrames> is there a way to run it at boot?
[12:59] <MaxFrames> so that any user gets the gamma adjusting?
[12:59] <Sysi> propably, but i don't know that
[12:59] <_Pete_> MaxFrames: see /etc/rc.local
[12:59] <Sysi> maybe need to do on every user
[13:04] <MaxFrames> thanks, it works when I logon, I had to rename the script to something.sh
[13:04] <MaxFrames> I don't think it would run at boot anyway because it needs X running
[16:07] <jarnos> Where can I find information on which packages are included in the default xubuntu installation?
[16:09] <likemindead> All of them? That'd be a long list. I'm not sure.
[16:13] <arossouw> hello, one of our developers has written a program in QT4 , if you use kde and go to the print function on that program it gives you a list of printers locally installed, but if you do the same on xubuntu it only displays pdf and postscript printing
[16:13] <arossouw> any ideas
[16:18] <likemindead> Do you have the necessary QT libraries installed in Xubuntu, arossouw
[16:18] <likemindead> ?
[16:22] <arossouw> the developer used qtsdk-2009.02, i guess he has his own qt libraries
[16:23] <arossouw> he puts qt libraries into qtsdk-2009.02 and then the program uses those libraries, the qtsdsk-2009.02 gets copied to /opt folder
[16:24] <arossouw>         apt-get install libmysqlclient16
[16:24] <arossouw>         apt-get install libqt4-sql-mysql
[16:24] <arossouw> thats whats installed
[16:30] <thht> hi there, i am using xubuntu 9.10 beta with some qt-written programs such as vlc and Google-Earth; how do i change the look of these programs to "blend in"?
[16:35] <likemindead> I don't know that you can too much, thht.
[16:35] <likemindead> It's like running iTunes in Windows...
[16:36] <thht> likemindead: i know there are some tools that provide a gtk look for qt-programs, i just forgot the name ^^
[16:37] <ochosi> thht
[16:37] <thht> ochosi: hi
[16:37] <ochosi> i'm using that package, looking it up for, one sec
[16:38] <ochosi> thht: qgtkstyle
[16:38] <ochosi> unfortunately it's not in the repos
[16:38] <thht> ochosi: thanks i'm looking it up
[16:38] <ochosi> after you installed qgtkstyle you'll also need qt4config in order to change the theme to gtk
[16:39] <ochosi> in case you're using 64bit the package might be hard to find, i can send it to you
[16:40] <thht> ochosi: when i used the former 9.04 xubuntu there was a package in the repositories, did they delete it?
[16:40] <ochosi> oh and also (even though you might know that already): it only works for qt4 apps, qt3 apps are not affected
[16:40] <ochosi> thht, supposedly, frankly i don't know and i think it's a pity it's not there anymore
[16:41] <thht> ochosi: damn :(
[16:41] <thht> ochosi: i found this: http://en.wikipedia.org/wiki/QGtkStyle
[16:42] <thht> wait a minute, i have an idea ;-)
[16:43] <ochosi> yeah, unfortunately there's not even a ppa for qgtkstyle
[16:44] <ochosi> thht, idea > waiting > listening
[16:45] <thht> ochosi: i checked via synaptic, there is a gtk2-engines-qtcurve package, but the description is a bit short; if i check it the package-manager wants to install an additional 170 megabytes (!)
[16:46] <ochosi> thht, qtcurve doesn't provide the same functionality as qgtkstyle
[16:46] <ochosi> at least afaik
[16:49] <thht> ochosi: I GOT IT! i am so proud :-)))
[16:50] <ochosi> thht where from? did you finally find a repo hosting it?
[16:50] <thht> ochosi: i installed qt4-qtconfig
[16:50] <thht> ochosi: run it and check "gtk+"
[16:50] <thht> ochosi: vlc is now in xubuntu - loook :-)))
[16:51] <ochosi> thht, but you also installed qgtkstyle, didn't you?
[16:51] <thht> ochosi: no
[16:51] <thht> ochosi: it runs that way :-D
[16:52] <ochosi> thht, hm, will check that out the next time i boot to karmic... (in jaunty now)
[16:52] <thht> ochosi: Google-Earth looks as ugly as ever, though; guess because of qt3 :(
[16:52] <ochosi> thht, hehe, yeah, guess so...
[16:52] <thht> wohoo
[16:53] <thht> ochosi: thanks for your help
[16:54] <ochosi> thht, you're welcome, great that it works that way!
[18:10] <alegro> Hello. Can I ask a beginner question here?
[18:10] <Sysi> of course
[18:10] <alegro> Do you know why in Xubuntu 9.04 I have to change the screen resolution to 1024x768 everytime I log in?
[18:23] <alegro> Sysi?
[18:24] <Sysi> humm
[18:24] <Sysi> what video card?
[18:25] <alegro> Nvidia Riva TNT2 Model 64/Model 64 Pro -16MB
[18:25] <Sysi> restricted drivers?
[18:26] <alegro> What?
[18:27] <Sysi> have you installed restricted drivers?
[18:27] <alegro> No, I haven't installed any drivers.
[18:27] <Sysi> settings → hardvare drivers
[18:29] <alegro> It says: No propreitary drivers are in use on this system.
[18:29] <Sysi> i'm not sure how good open drivers are
[18:30] <alegro> Should I install a proprietary driver?
[18:31] <Sysi> it may not work, that sounds so old
[18:31] <Sysi> sorry, g2g
[18:31] <alegro> thanks anyway
[18:39] <alegro>  Do you know why in Xubuntu 9.04 I have to change the screen resolution to 1024x768 everytime I log in?
[18:51] <ochosi> alegro, you could try to mess with /etc/X11/xorg.conf (even though that shouldn't be needed in jaunty anymore)
[18:53] <alegro> I'm new. How do I access the file?
[19:03] <alegro> ocoshi?
[19:25] <TheSheep> !xorg.conf
[20:50] <likemindead> Should most any Bluetooth device pair with *buntu? I have a set of MOTOROKR S9-HD Bluetooth headphones that aren't showing up at all. They pair just fine with my phone.
[21:05] <likemindead> !bluetooth
[21:12] <ActionParsnip> hey guys
[21:12] <ActionParsnip> is the default file browser in Xubuntu livecd, thunar??
[21:17] <likemindead> Yes, ActionParsnip.
[21:17] <likemindead> !thunar
[21:17] <ActionParsnip> cool
[21:17] <ActionParsnip> can it manage smb:// like addressing for accesing remote samba shares?
[21:21] <rr72> hey has anyone succesfully installed gnome on xubuntu? i get a dep issue
[21:21] <Sysi> yes i had, many times
[21:22] <Sysi> you remembered update packages?
[21:22] <rr72> yes, it is telling me that gnome-vfs-obexftp is not installable, 9.10
[21:24] <rr72> bbl
[21:25] <Sysi> you're installing it with apt/synaptic?
[21:31] <Dai> if you're on 9.10, you should really be asking in +1
[21:31] <Dai> at least for the next couple weeks
[21:33] <Danny22> is anyone there?
[21:34] <TheSheep> !ask | Danny22
[21:34] <Sysi> you won't get rid of us :P
[21:34] <Danny22> Does any one know haow to get parental controll for the internet?
[21:35] <Sysi> what?
[21:35] <Sysi> is my english bad or what
[21:35] <Danny22> You know internet filters, so you can block things so your kids don't see it
[21:35] <TheSheep> Danny22: you could install squid with some parental control settings, and set up your browser to use it
[21:36] <Sysi> ah, bad english (not native)
[21:36] <Danny22> how do you get it?
[21:36] <TheSheep> Danny22: it's an advanced task though
[21:36] <Danny22> how hard is it?
[21:37] <TheSheep> Danny22: hmm... there are easier ways, say, did you try to google for it?
[21:38] <TheSheep> Danny22: for example this http://ubuntuforums.org/showthread.php?t=843510
[21:38] <Danny22> ok thanks I'll try that :)
[21:43] <Danny22> I went to the link you provided. all the downloads are .tar.gz can I install those?
[21:43] <TheSheep> Danny22: it's better to add ppa to your software sources and install using synaptic
[21:43] <TheSheep> !ppa
[21:44] <Danny22> ok
[22:05] <Danny22> ok the terminal says it is installed now how do I find it :)
[22:06] <nicklas_> Danny22: find what?
[22:07] <Danny22> I installed webcontroll a internet filter using the terminal now how do i find it?
[22:07] <nicklas_> hm that i dont know, in firefox?
[22:08] <Danny22> Yea i'm using fire fox
[22:09] <Danny22> never mind I found it
[22:09] <Danny22> Thanks for the help TheSheep :)
[22:09] <nicklas_> cool :-)
[23:12] <S0210> Hello! I try to "cat *.jpg >xxx.avi" and it works fine. Is there a way to change the default framerate and/or picture size?
[23:40] <rr72> Dai~ thankyou for your suggestion
[23:42] <Dai> erm?
[23:42] <Dai> oh!  +1
[23:42] <Dai> you're welcome.  were they able to get you sorted?
[23:43] <rr72> just asking now, got back right now


[02:49] <superfly> Evening all
[06:04] <thatgraemeguy> mornings
[06:22] <superfly> Night thatgraemeguy
[06:22] <superfly> Time for me to zzzz
[06:22]  * night superfly
[06:55] <Langjan> Good morning from a very wet Bushveld
[06:55] <Langjan> You ok Kilos ?
[06:56] <Kilos> morning Langjan yes ty im fine
[06:56] <Langjan> Mini flood with 80 mm in short time early hours
[06:56] <Kilos> wow
[06:56] <Langjan> lekker
[06:56] <Kilos> we had about 5mm this morning
[06:57] <Langjan> sjoe, at least wet
[06:57] <Langjan> I have to own up I told a lie the other day
[06:57] <Kilos> yeah will help the farmers dryland plantings to kick off
[06:57] <Kilos> oh my
[06:57] <Langjan> good
[06:57] <Kilos> about what?
[06:58] <Langjan> when I said my grub had picked up the second hard drive
[06:58] <Langjan> I thought it had because I saw something in the output
[06:58] <Kilos> what is on the second drive
[06:58] <Langjan> but no luck so far
[06:58] <Langjan> win 7
[06:59] <Kilos> use boot-repair
[06:59] <Kilos> it will find it
[06:59] <Langjan> I tried boot repair did not work
[06:59] <Kilos> or wait
[06:59] <Kilos> um
[06:59] <Kilos> some bell ringing
[07:00] <Kilos> fsck -f i think it was
[07:00] <Langjan> hear them beels...
[07:00] <Langjan> bells not belles
[07:00] <Kilos> lol
[07:00] <Kilos> oh and remember with lies
[07:00] <Kilos> revelations 21 v 8 i think it was
[07:00] <Langjan> you have to have a great memory
[07:01] <Kilos> nono never lie
[07:01] <Kilos> all liars gonna pay
[07:01] <Kilos> oh hahaha
[07:01] <Kilos> did you see the video of when i arrived in oz
[07:02] <Langjan> You know your Bible, but it also says I am forgiven if I own up
[07:02] <Kilos> debs is a cheeky chick so i told her i am taking my walking stick to beat her into submission
[07:02] <Kilos> nono
[07:02] <Kilos> nono
[07:02] <Langjan> lmga
[07:02] <Kilos> peeps misunderstand that
[07:02] <Kilos> all liars
[07:03] <Kilos> anyway
[07:03] <Langjan> He who was without sin paid for our sins
[07:03] <Kilos> we had just got together at the airport when she asked where is the walking stick
[07:03] <Langjan> and?
[07:03] <Kilos> all liars
[07:04] <Kilos> i forgot the stick
[07:04] <Langjan> that means all are lost
[07:04] <Kilos> you can be forgiven
[07:04] <Langjan> through unmerited grace
[07:04] <Kilos> but i dont believe daily liars will be able to use that excuse
[07:05] <Kilos> its like teaching a child
[07:05] <Langjan> correct but we cannot judge
[07:05] <Kilos> you talk twice then the third time you get the stick
[07:06] <Langjan> So you picked up sticks in oz
[07:06] <Kilos> anyway man tara took lotsa vids when i arrived there
[07:06] <Langjan> ok did not see them saw some pics
[07:06] <Kilos> and posted on my facebook where debs asked about the walking stick
[07:07] <Langjan> I will have a look
[07:07] <Kilos> very funny
[07:07] <Kilos> whew thats too far back
[07:07] <Kilos> anyway
[07:07] <Kilos> back to the drive
[07:07] <Kilos> um
[07:07] <Langjan> should be able to search back
[07:07] <Langjan> ok thks
[07:08] <Kilos> sudo fsck -f /dev/sdb1 i think it was
[07:08] <Kilos> where are the clever guys when you need them
[07:09] <Langjan> shows up as folder(inode/directory)
[07:09] <Kilos> doesnt it fix it?
[07:10] <Langjan> does network share have any effect here?
[07:10] <Kilos> i dunno
[07:10] <Kilos> im a greeter bot man
[07:10] <Kilos> good morning south africa
[07:10] <Kilos> that fsck should repair inodes
[07:10] <Kilos> whatever they are
[07:11] <Langjan> It says I must install samba
[07:11] <Langjan> for folder share
[07:11] <Kilos> oh maybe i had samba
[07:11] <Kilos> paddatrapper help
[07:12] <Kilos> i have no idea where inetpro is
[07:17] <Kilos> read through this whole page https://www.maketecheasier.com/check-repair-filesystem-fsck-linux/
[07:17] <Kilos> gparted also seems able to sort things
[07:17] <Kilos> oh
[07:18] <Kilos> you have done a sudo update-grub hey?
[07:18] <Kilos> also is the win7 drive from another pc
[07:19] <Kilos> if so you might need to unplug your linux drive then boot from 7 dvd and repair the installation
[07:19] <Langjan> Hi Kilos sorry I was sidetracked
[07:19] <Kilos> np
[07:19] <Kilos> read everything before you decide what to try next
[07:20] <Langjan> OK will work on those guidelines, a bit later just busy with some other dual boot hiccups but winning
[07:20] <Langjan> The grub prob is not urgent
[07:21] <Kilos> ok
[07:21] <Langjan> thks
[07:21] <Kilos> im here most of the time
[07:21] <Langjan> going for brekfis
[07:21] <Langjan> thks
[07:21] <Kilos> or outside so be patient
[07:21] <Kilos> enjoy
[07:58] <paddatrapper> Kilos: sorry, grub is still magic to me
[09:05] <inetpro> good mornings
[09:05] <inetpro> Kilos: 19mm of rains
[09:06] <inetpro> or more
[09:06] <magespawn> good morning
[09:06] <inetpro> should check my rain meter, think it might be leaky
[09:07] <inetpro> hello magespawn
[09:07] <inetpro> how are you doing?
[09:07] <magespawn> good and you inetpro?
[09:35] <Kilos> you lucky inetpro
[09:35] <Kilos> hi magespawn
[09:51] <magespawn> Hey Kilos.
[12:59] <inetpro> Kilos: lucky?
[12:59] <inetpro> did you not get rain on that side?
[13:00] <paddatrapper> All we have is fire here... Rain would be amazing
[13:09] <Kilos> about 1 mm inetpro
[13:09] <inetpro> ai!
[13:09] <MaNI> yeah some rain right now would be fantastic
[15:43] <pavlushka> ahoy ZA!
[15:54] <magespawn> hey pavlushka
[15:54] <pavlushka> hey magespawn  :)
[15:54] <pavlushka> magespawn: in the office still?
[15:57] <magespawn> yup working the late shift.
[18:31] <magespawn> chater later all, home time
[18:54] <Langjan> Hi Kilos hoe was jou dag?
[19:13] <Langjan> hi nsnzero
[19:14] <Langjan> and all others
[19:55] <Kilos> ai!
[19:55] <Kilos> sleep tight everyone
[19:55] <smile> good night! :)
[20:05] <smile> bye :)
[21:23] <calhax> whats up guys


[09:25] <tomwardill> as handy as it is, the weird string concatination 'feature' of python  catches me out more often than not
[11:11] <tomwardill> https://code.launchpad.net/~twom/launchpad-buildd/include-base-in-digests/+merge/383584 extract the base from OCI images.
[14:58] <cjwatson> tomwardill: Could you have a look at https://code.launchpad.net/~cjwatson/launchpad-buildd/+git/launchpad-buildd/+merge/383594 ?  It sort of partially reverts one of your OCI-related changes from a while back, which I think doesn't cause any problems there but you should probably have a look
[14:59] <tomwardill> yep, looking
[15:01] <tomwardill> `CarefulFakeProcessFixture`
[15:01] <tomwardill> this is a good name
[15:20] <cjwatson> :)
[15:49] <tomwardill> cjwatson, pappacena: Tidied up https://code.launchpad.net/~twom/launchpad-buildd/include-base-in-digests/+merge/383584 and found some other bits that were doing silly things with exceptions, if you could check it over again
[16:04] <cjwatson> tomwardill: re-reviewed
[16:04] <tomwardill> ta
[16:05] <tomwardill> cjwatson: the KeyError is actually the same cause as the LXDException
[16:05] <tomwardill> it's the error the FackBackend raises on a missing file
[16:05] <cjwatson> Oh right
[16:06] <cjwatson> Still, my point was that the exceptions raised by copy_out vs. the exceptions raised by everything else are logically different
[16:06] <tomwardill> yeah, fair, that block should be shorter
[16:12] <tomwardill> all fixed
[16:27] <teward> just going to share things here, but RE: DMARC compliance I'm still going to iron out the kinks locally once LP catches up to what I'm after (a branch in my userspace for the LP code) but it looks like DMARC compliance for bug mails might be easier to implement than previously thought heh.  fixing up the tests will be the next Big Problem for that but from the functionality perspective it shouldn't be too hard.
[16:27] <teward> thank you cjwatson for pointers at where to look in the codebase
[16:27] <teward> once i get that working you'll all ahve a merge to review for those changes :)
[16:28] <cjwatson> Trying to work out why your fork is timing out - LP has four refs so it really shouldn't be an issue
[16:28] <cjwatson> Guess I'll try repacking the repository
[16:29] <teward> cjwatson: unless something else is going wonky?
[16:29] <cjwatson> No, it's clearly an API timeout on the repository create call
[16:40] <teward> cool.  more work for you then cjwatson xD  :P
[16:42] <cjwatson> teward: Can you retry your push now?
[16:42] <teward> 1 moment
[16:42] <teward> didn't time out and is 'writing objects' right now
[16:42] <teward> (*waits for the eternity to pass*)
[20:25] <teward> i'm assuming that the dev launchpad env attempts to use localhost:25 for email sending?
[20:25] <teward> (just checking)
[21:29] <cjwatson> teward: An improperly configured Launchpad instance could very easily spam a whole bunch of innocent people, so by default it's either configured not to send email at all or to drop them into an mbox somewhere, I forget which.  See doc/email.txt
[21:30] <teward> Yep.  I also configure a postfix locally that literally just delivers to an mbox xD  So far though i caught two things that needed altered in the tests :P
[21:33] <teward> You also werent lying the test suite takes an eternity to run
[21:33] <cjwatson> teward: To give you an idea, the dogfood instance has a mail-configure-normal.zcml that looks like https://paste.ubuntu.com/p/dq5P36X95D/, which just drops everything into an mbox
[21:33] <cjwatson> You probably don't want to run the entire test suite.
[21:34] <cjwatson> lp.bugs should be enough - maybe lp.coop.answersbugs too, though it's tiny.
[21:34] <teward> running the bugs testsuite with the command you stated in #launchpad earlier.  Which is fine 'cause I want to make sure that works :)
[21:34] <teward> yeah i am running lp.bugs :)
[21:34] <cjwatson> The whole thing takes six hours on my laptop.  Fortunately most changes don't require running it all
[21:37] <teward> indeed.  but because I want to make sure nothing with my minor changes in the LP codebase explode all of bugs I"m running lp.bugs entirely.  Found a docs discrepancy too because of the email From generations being different, that was an easy thing to fix, but i'm waiting to see what else triggers
[21:37] <teward> 'course APache just exploded but that i think might've been my fault (oops)
[21:37] <teward> (like literally seized up the container)
[21:38] <teward> i only can blame myself there :)
[22:14] <teward> cjwatson: i think one of the tests is just 'busted' to some extent
[22:15] <teward> but it might be on my end... *retests with a clean setup*
[23:02] <cjwatson> teward: We have some flaky tests, but they do all pass
[23:02] <cjwatson> On a correct setup
[23:03] <cjwatson> And most of the flakiness doesn't manifest when you're just running the tests serially locally rather than in more complicated parallel setups
[23:25] <teward> the flakiness i'm seeing is in... lib/lp/bugs/doc/bugnotification-sending.txt
[23:26] <teward> where Subject lines with ... fail because it's got an actual numeric in there
[23:26] <teward> ellipsized text not matching
[23:26] <teward> similar for link behavior
[23:26] <teward> and the From addresses but it *seems* to be more a case of the docs not matching the expected outputs (hence failures)
[23:26] <teward> i'm quadruple tasking at the moment heh
[23:27] <teward> let me run a 'pure' test with LP pure just to make sure this isn't my code changes causing the errors (if it reproduces in clean master I'm assuming the issue is due to flakyTest)
[23:29] <wgrant> That test is not known to be flaky, and it's not of the kind that is likely to be flaky.
[23:29] <teward> wgrant: true, but i'm curious why it's triggering here but not elsewhere hence testing a clean deploy atm
[23:30] <teward> to rule out my changes (which were only to the from address generator) as the cause
[23:30] <teward> (i'm testing local heh)
[23:33] <teward> wgrant: the *expected* failures with those changes are, as I stated, expected, but the specific ones that *aren't* expected are with handling of the Subject line matches
[23:35] <teward> let me get the traceback into a file that I can share (and then delete after)
[23:46] <cjwatson> Beware that doctest mismatch output can be extremely confusing and can suggest mismatches that don't exist if you aren't completely sure of how to read them
[23:46] <teward> cjwatson: yeah those're the tests that failed.  This said, those're the only failures in the entire bugs test suite
[23:46] <teward> (with my changes).  Trying to get full output but E:SLOW


[12:29] <rbasak> ilasc: hi! https://code.launchpad.net/~git-ubuntu-import/ubuntu/+source/ffmpeg/+git/ffmpeg says "Repository scan failed" with a retry button. When I retry, it changes to a message saying a rescan is in progress, but very soon after says it failed again. Please could you take a look?


[00:00] <sarnold> ideally, with some upstream attention on valgrind or -fsanitize=address or coverity or something, to spot more cases like these
[00:14] -queuebot:#ubuntu-release- New binary: ffcv [amd64] (lunar-proposed/none) [0.0.3-2build1] (no packageset)
[00:16] -queuebot:#ubuntu-release- New binary: ffcv [arm64] (lunar-proposed/none) [0.0.3-2build1] (no packageset)
[00:16] -queuebot:#ubuntu-release- New binary: ffcv [ppc64el] (lunar-proposed/none) [0.0.3-2build1] (no packageset)
[00:16] -queuebot:#ubuntu-release- New binary: ffcv [armhf] (lunar-proposed/none) [0.0.3-2build1] (no packageset)
[00:18] -queuebot:#ubuntu-release- New binary: ffcv [s390x] (lunar-proposed/none) [0.0.3-2build1] (no packageset)
[00:33] -queuebot:#ubuntu-release- Unapproved: nextepc (lunar-proposed/universe) [0.3.10+nods-4.2 => 0.3.10+nods-4.2ubuntu1] (no packageset)
[00:34] -queuebot:#ubuntu-release- Unapproved: accepted nextepc [source] (lunar-proposed) [0.3.10+nods-4.2ubuntu1]
[00:44] -queuebot:#ubuntu-release- New: accepted ffcv [amd64] (lunar-proposed) [0.0.3-2build1]
[00:44] -queuebot:#ubuntu-release- New: accepted ffcv [armhf] (lunar-proposed) [0.0.3-2build1]
[00:44] -queuebot:#ubuntu-release- New: accepted ffcv [arm64] (lunar-proposed) [0.0.3-2build1]
[00:44] -queuebot:#ubuntu-release- New: accepted ffcv [ppc64el] (lunar-proposed) [0.0.3-2build1]
[00:45] -queuebot:#ubuntu-release- New: accepted ffcv [s390x] (lunar-proposed) [0.0.3-2build1]
[00:47] <vorlon> fyi snakefruit has been turned off.  As far as we know everything has been migrated to the new instance but if anyone sees anything not working, please ping
[00:55] <athos> Hi! I am about to push a new bug-fix version of ubuntu-advantage-tools. lucasmoura will probably mention additional details for a beta freeze exception request on this one :)
[00:56] <lucasmoura> yes, we have created this bug to detail the whole reason why thig bug should be a BetaFreezeException: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2012735
[00:56] -ubottu:#ubuntu-release- Launchpad bug 2012735 in ubuntu-advantage-tools (Ubuntu) "update-manager crashed with uaclient.exceptions.UserFacingError in get_lscpu_arch()" [Critical, New]
[00:56] <lucasmoura> Please let me know if there is any additional detail that I need to provide regarding this release
[00:57] <vorlon> "we believe the dpkg command is stable enough" um lol it better be
[00:58] <vorlon> lucasmoura, athos: beta freeze exception means you believe the user impact is so critical that it's worth potentially delaying the beta release over; I want to make sure that assessment is correct
[01:00] <lucasmoura> vorlon, currently, ubuntu-advantage-tools is breaking update-manager on any release that is using a non-english locale. Since we are pushing this fix during beta freeze, that's why we thought the Beta Freeze Exception was needed
[01:00] <vorlon> any non-english locale is sufficient for me
[01:01] <vorlon> just wanted to check that this was the scope, since it didn't immediately look like a recent regression
[01:01] <vorlon> lucasmoura, athos: upload ASAP so I can review it in the queue, please
[01:02] <vorlon> ah but in fact, it's a regression from the immediately preceding version, so
[01:02] <vorlon> can we PLEASE lose these ~23.04 decorations on version numbers
[01:03] <lucasmoura> Yep, we have actually discussed about dropping those. We can remove it for the next release
[01:04] <athos> vorlon: ^ is this acceptable for this beta freeze?
[01:04] <vorlon> yes
 any non-english locale is sufficient for me
[01:05] <athos> I meant keeping the ~23.04 for this specific upload as suggested by lucasmoura
[01:05] <vorlon> athos: yes, as much as I hate it and as easy as I think it ought to be to change I'm not blocking you on version numbers being ugly
[01:06] <vorlon> kanashiro_: why is ruby-rackup in unstable if ruby-rack 3.0 is in experimental?
[01:19] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [27.13.6~20.04.1 => 27.14.2~20.04.1] (core)
[01:19] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (kinetic-proposed/main) [27.13.6~22.10.1 => 27.14.2~22.10.1] (core)
[01:19] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (jammy-proposed/main) [27.13.6~22.04.1 => 27.14.2~22.04.1] (core)
[01:19] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (lunar-proposed/main) [27.14.1~23.04.1 => 27.14.2~23.04.1] (core)
[01:19] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (bionic-proposed/main) [27.13.6~18.04.1 => 27.14.2~18.04.1] (core)
[01:19] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (xenial-proposed/main) [27.13.6~16.04.1 => 27.14.2~16.04.1] (no packageset)
[01:19] <kanashiro[m]> vorlon: ruby-rackup in unstable was a mistake. It should have gone to experimental
[01:20] <vorlon> kanashiro[m]: fair enough. ruby-rack-session also?
[01:20] <kanashiro[m]> yes
[01:20] <vorlon> athos: lucasmoura: so does that run of notifications mean this bug is believed to break update-manager in all series?
[01:21] <lucasmoura> yes, it will. But 27.14.1 is not yet released on the other releases
[01:21] <athos> vorlon: it would with the current pending uploads in those series
[01:21] <vorlon> ok
[01:33] <vorlon> athos, lucasmoura: so there are some corner cases here, that are in no way supported configurations and I don't believe we have to care about them, but I wonder - is there a reason you weren't using the output of `uname -m` for this in the first place?
[01:35] <lucasmoura> We were using lscpu here because Livepatch was also using it to fetch architecture information
[01:35] <lucasmoura> And we wanted it to be consistent
 "If there are too many problems..." <- None... I think it's better to handle the issues, that were just been ignored or hidden before but for sure were still causing some crashes hard to reproduce
[01:35] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (lunar-proposed) [27.14.2~23.04.1]
[01:36] <vorlon> lucasmoura: ok well that's a weird interface for them to have been using too
[01:37] <lucasmoura> But if the question is related to why we are using dpkg --print-architecture instead of uname, I think the decision was made here: https://github.com/canonical/ubuntu-pro-client/issues/914
[01:37] -ubottu:#ubuntu-release- Issue 914 in canonical/ubuntu-pro-client "Do not use `uname` to determine architecture" [Closed]
[01:37] <lucasmoura> vorlon, yes I think one of member of the Pro client team has opened an issue on Livepatch we found out about that issue
[01:38] <lucasmoura> I will confirm that tomorrow once he is working again
[01:39] <vorlon> right.  So the thing I'm thinking of is that it is entirely possible to be running an armhf userspace on an arm64 kernel and in this case dpkg --print-architecture and uname -m (or lscpu) give you two *different* answers.  I don't think we have arm64 livepatch and running ua pro for armhf on arm64 would just be a weird thing to even be trying to do, but it's technically possible
[01:40] <vorlon> so IMHO you should all be clear about which you *mean* (from the set of: dpkg userspace architecture; CPU architecture; kernel architecture) and be consistent with that
[01:42] <lucasmoura> vorlon, we already have a architecture mapping for those differences between dpkg and lscpu: https://github.com/canonical/ubuntu-pro-client/blob/main/uaclient/util.py#L611
[01:43] <lucasmoura> But if the architecture you are mentioned is not there, we can extend that mapping
[01:44] <lucasmoura> s/mentioned/mentioning
[02:50] <vorlon> lucasmoura: the point is it is not a 1:1 mapping
[02:50] <vorlon> and not a fixed mapping
[02:53] <lucasmoura> vorlon, yes, of course. I am just mentioning that it currently covers the scenarios we expect Livepatch to be covered by. But we can better align with the Livepatch team about how to better handle that mapping in the future
[03:02] <lucasmoura> Maybe with us not using lscpu anymore, we don't even need it. Then we could just rely on the output of dpkg. But I will need confirmation from Livepatch that the architectures will be properly handled by the Livepatch API
[03:02] <lucasmoura> I will bring that to team tomorrow so we can better discuss this
[03:03] <sarnold> lucasmoura: do we intend to support livepatch on eg ubuntu core systems? do those have a dpkg available?
[03:05] <lucasmoura> sarnold, this is being discussed. But we would first need to support a snap version of the Pro client. But I don't have an answer right now about dpkg support for that type of system
[03:12] <sarnold> lucasmoura: aha! good enough for me :)
[03:12] <sarnold> [ ] a problem for another day :D
[04:22] -queuebot:#ubuntu-release- Unapproved: papi (lunar-proposed/universe) [7.0.0-2 => 7.0.0-2ubuntu1] (no packageset)
[04:23] -queuebot:#ubuntu-release- Unapproved: accepted papi [source] (lunar-proposed) [7.0.0-2ubuntu1]
[04:41] -queuebot:#ubuntu-release- Unapproved: swi-prolog (lunar-proposed/universe) [8.4.2+dfsg-2ubuntu1 => 9.0.4+dfsg-1ubuntu1] (no packageset)
[04:42] -queuebot:#ubuntu-release- Unapproved: accepted swi-prolog [source] (lunar-proposed) [9.0.4+dfsg-1ubuntu1]
[05:23] -queuebot:#ubuntu-release- New binary: graph-tool [riscv64] (lunar-proposed/universe) [2.45+ds-10ubuntu1] (no packageset)
[05:24] <vorlon> -ifneq (,$(filter $(DEB_HOST_ARCH),arm hppa))
[05:24] <vorlon> lovin' it
[05:30] -queuebot:#ubuntu-release- New: accepted graph-tool [amd64] (lunar-proposed) [2.45+ds-10ubuntu1]
[05:30] -queuebot:#ubuntu-release- New: accepted graph-tool [ppc64el] (lunar-proposed) [2.45+ds-10ubuntu1]
[05:30] -queuebot:#ubuntu-release- New: accepted graph-tool [s390x] (lunar-proposed) [2.45+ds-10ubuntu1]
[05:30] -queuebot:#ubuntu-release- New: accepted graph-tool [arm64] (lunar-proposed) [2.45+ds-10ubuntu1]
[05:30] -queuebot:#ubuntu-release- New: accepted graph-tool [riscv64] (lunar-proposed) [2.45+ds-10ubuntu1]
[05:45] -queuebot:#ubuntu-release- Unapproved: vectorscan (lunar-proposed/universe) [5.4.8-2.1 => 5.4.9-1] (no packageset) (sync)
[05:46] -queuebot:#ubuntu-release- Unapproved: accepted vectorscan [sync] (lunar-proposed) [5.4.9-1]
[06:06] <vorlon> test results are in for mesa on arm64.  s390x is not but s390x is behind and is not an interesting mesa architecture generally (and regressions wouldn't affect s390x beta images).  Unblocking mesa, preparing for mass-respins
[06:29] -queuebot:#ubuntu-release- Unapproved: newsboat (lunar-proposed/universe) [2.21-1.5 => 2.21-1.5ubuntu1] (no packageset)
[06:29] -queuebot:#ubuntu-release- Unapproved: accepted newsboat [source] (lunar-proposed) [2.21-1.5ubuntu1]
[06:52] -queuebot:#ubuntu-release- Unapproved: gmenuharness (lunar-proposed/universe) [0.1.4-5 => 0.1.4-5ubuntu1] (no packageset)
[06:53] -queuebot:#ubuntu-release- Unapproved: accepted gmenuharness [source] (lunar-proposed) [0.1.4-5ubuntu1]
[07:16] -queuebot:#ubuntu-release- Unapproved: accepted xorg-server [source] (focal-proposed) [2:1.20.13-1ubuntu1~20.04.7]
[07:38] -queuebot:#ubuntu-release- Unapproved: sphinx (lunar-proposed/main) [5.3.0-3 => 5.3.0-3ubuntu1] (i386-whitelist, ubuntu-desktop, ubuntu-server)
[07:59] -queuebot:#ubuntu-release- Unapproved: bioxtasraw (lunar-proposed/universe) [2.1.1-4build1 => 2.1.1-4build2] (no packageset)
[08:00] -queuebot:#ubuntu-release- Unapproved: accepted bioxtasraw [source] (lunar-proposed) [2.1.1-4build2]
[08:30] <ricotz> hello, please accept libreoffice/lunar, its autopkgtests passed https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#libreoffice
[08:46] -queuebot:#ubuntu-release- Builds: Ubuntu Core amd64 edge [Lunar Beta] has been updated (20230329)
[09:33] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Lunar Beta] has been updated (20230329)
[09:36] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop (Legacy) amd64 [Lunar Beta] has been updated (20230329)
[09:39] -queuebot:#ubuntu-release- Builds: Edubuntu Desktop amd64 [Lunar Beta] has been updated (20230329)
[09:41] -queuebot:#ubuntu-release- Unapproved: snapd (lunar-proposed/main) [2.58.3+23.04ubuntu1 => 2.59.1+23.04] (desktop-core, ubuntu-server)
[09:43] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Lunar Beta] has been updated (20230329)
[09:44] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Lunar Beta] has been updated (20230329)
[09:45] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Lunar Beta] has been updated (20230329)
[09:47] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Lunar Beta] has been updated (20230329)
[09:51] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Lunar Beta] has been updated (20230329)
[10:18] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Lunar Beta] has been updated (20230329)
[10:30] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Lunar Beta] has been updated (20230329)
[10:30] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64 [Lunar Beta] has been updated (20230329)
[10:38] -queuebot:#ubuntu-release- Unapproved: accepted studio-controls [source] (jammy-backports) [2.3.9-0ubuntu2~bpo22.04.1]
[10:41] -queuebot:#ubuntu-release- Unapproved: accepted borgmatic [source] (jammy-backports) [1.7.9-0ubuntu1~bpo22.04.1]
[10:42] -queuebot:#ubuntu-release- Unapproved: tzdata (lunar-proposed/main) [2023b-1exp1ubuntu1 => 2023c-1exp1ubuntu1] (core)
[10:44] -queuebot:#ubuntu-release- Builds: Ubuntu WSL [Lunar Beta]<PHONE_NUMBER>) has been added
[10:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Lunar Beta] has been updated (20230329)
[10:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Lunar Beta] has been updated (20230329)
[10:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Lunar Beta] has been updated (20230329)
[10:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Lunar Beta] has been updated (20230329)
[10:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Lunar Beta] has been updated (20230329)
[10:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Lunar Beta] has been updated (20230329)
[11:04] -queuebot:#ubuntu-release- Unapproved: tzdata (kinetic-proposed/main) [2023b-0ubuntu<IP_ADDRESS> => 2023c-0ubuntu<IP_ADDRESS>] (core)
[11:10] -queuebot:#ubuntu-release- Unapproved: tzdata (jammy-proposed/main) [2023b-0ubuntu<IP_ADDRESS> => 2023c-0ubuntu<IP_ADDRESS>] (core)
[11:16] -queuebot:#ubuntu-release- Unapproved: tzdata (focal-proposed/main) [2023b-0ubuntu<IP_ADDRESS> => 2023c-0ubuntu<IP_ADDRESS>] (core)
[11:22] -queuebot:#ubuntu-release- Unapproved: python-certbot (lunar-proposed/universe) [2.1.0-2 => 2.1.0-3] (no packageset) (sync)
[11:23] -queuebot:#ubuntu-release- Unapproved: accepted python-certbot [sync] (lunar-proposed) [2.1.0-3]
[11:25] -queuebot:#ubuntu-release- Unapproved: tzdata (bionic-proposed/main) [2023b-0ubuntu<IP_ADDRESS> => 2023c-0ubuntu<IP_ADDRESS>] (core)
[11:32] <bdrung> rbasak, bdmurray: The new SRUs for tzdata 2023c are ready. I reused https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599
[11:32] -ubottu:#ubuntu-release- Launchpad bug 2012599 in tzdata (Ubuntu Lunar) "tzdata 2023a/2023b/2023c release - Egypt restoring DST" [Critical, Fix Committed]
[12:36] -queuebot:#ubuntu-release- Unapproved: fsarchiver (lunar-proposed/universe) [0.8.6-2ubuntu1 => 0.8.7-1] (no packageset) (sync)
[12:37] -queuebot:#ubuntu-release- Unapproved: therion (lunar-proposed/universe) [6.1.6-2 => 6.1.6-3] (no packageset) (sync)
[12:37] -queuebot:#ubuntu-release- Unapproved: accepted fsarchiver [sync] (lunar-proposed) [0.8.7-1]
[12:37] -queuebot:#ubuntu-release- Unapproved: accepted therion [sync] (lunar-proposed) [6.1.6-3]
[13:02] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Lunar Beta] has been updated (20230329)
[13:02] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Lunar Beta] has been updated (20230329)
[13:02] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+icicle [Lunar Beta] has been updated (20230329)
[13:02] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+licheerv [Lunar Beta] has been updated (20230329)
[13:02] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+nezha [Lunar Beta] has been updated (20230329)
[13:02] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive [Lunar Beta] has been updated (20230329)
[13:14] <AlsoItzSwirlz> It looks like Cinnamon didn't build yesterday, did something fail or is it building through everything
[13:48] <rbasak> bdrung: "The SRUs to the stable include the recent changes for generating the debconf template and the timezone mappings in convert_timezone(). Previous SRUs did forget to update them for the changes from upstream." -> shouldn't this be in a Test Plan somewhere for SRU verification?
[13:48] <ginggs> AlsoItzSwirlz: no build yesterday or today, I'll look into it
[13:48] <rbasak> It seems still relevant now since AFAICT that change hasn't landed in updates yet.
[13:48] <AlsoItzSwirlz> ginggs: thx
[13:49] <adrien> hi, can someone unblock strace 6.2? it cannot migrate due to the FF but exception has been granted (and in the future, it will probably follow the kernel freeze instead)
[13:49] <adrien> thanks :)
[13:49] <rbasak> bdrung: and I think this upload needs a -v2022g-0ubuntu<IP_ADDRESS> to cover everything that hasn't landed yet.
[13:50] <rbasak> I've only been looking at Kinetic - I assume the older stable release uploads are identical and will need the equivalent stuff done there too.
[13:51] <ginggs> adrien: strace is blocked from migration due to beta freeze, please ping me on Friday
[13:52] <adrien> ok, will do, thanks
[14:04] <bdrung> rbasak, regarding the test plan: the SRUs got enhanced with autopkgtest test cases (with all things that i could come up with)
[14:05] <bdrung> rbasak, good point for the -v parameter. do i need to re-upload them?
[14:07] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Lunar Beta] has been updated (20230329)
[14:08] -queuebot:#ubuntu-release- Builds: Ubuntu Cinnamon amd64 [Lunar Beta] (20230327) has been added
[14:08] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Lunar Beta] has been updated (20230329)
[14:08] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Lunar Beta] has been updated (20230329)
[14:08] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Lunar Beta] has been updated (20230329)
[14:08] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Lunar Beta] has been updated (20230329)
[14:12] <rbasak> bdrung: I appreciate the new dep8 tests - thanks! Do they cover the debconf templates?
[14:13] <ginggs> AlsoItzSwirlz: cinnamon spinning now...
[14:13] <AlsoItzSwirlz> ginggs: thanks
[14:14] <rbasak> bdrung: also I have no issue with fixing debconf templates lagging behind by autogenerating them instead, including in an SRU. I just want to make sure that given we're touching them, we're checking that they don't regress something. I don't mind if that's automatic or manual - just that it's not missed.
[14:19] <rbasak> bdrung: yes - please re-upload with -v.
[14:20] <bdrung> rbasak, yes. see debian/tests/debconf
[14:21] <rbasak> Oh great. Sorry I missed tat.
[14:22] <rbasak> C
[14:23] <bdrung> rbasak, the debconf template was generated in bash before but is now done using Python
[14:26] <bdrung> the combination of generating them and the debconf test case ensure that they are in good shape.
[14:27] <rbasak> bdrung: I think https://wiki.ubuntu.com/StableReleaseUpdates#tzdata could do with an explanation of that. Otherwise SRU reviewers will see an unexplained diff.
[14:27] <rbasak> (which is usually an error)
[14:28] <bdrung> let's see if I can log-in to the wiki
[14:29] <rbasak> Oh, hang on. Is it being generated before upload or as part of the build?
[14:30] <bdrung> yes
[14:30] <rbasak> If the latter, then it wouldn't result in unexplained diffs (except this time, and this time it is explained in the SRU bug which I very much appreciate!)
[14:32] <bdrung> Yes. it's the latter. the generated debconf template is part of the source package
[14:38] <bdrung> rbasak, I checked it again. People can forget to include the template update in the source package. In this case lintian will complain about an outdated template in the source package.
[14:39] <rbasak> bdrung: the SRU team doesn't check lintian output. At least I'm not aware that anyone does.
[14:40] <bdrung> rbasak, at least I am doing that. So if I miss to include it, I will notice it before the upload.
[14:40] <rbasak> bdrung: could we stick steps into the wiki to verify that the mistake isn't made somehow maybe? Like ask for lintian to be run explicitly, or something in a standard Test Plan, or an additional dep8 test maybe.
[14:40] <rbasak> For this time it's fine. I'd just like to make the process smoother for everyone in the future.
[14:45] -queuebot:#ubuntu-release- Unapproved: swtpm (lunar-proposed/main) [0.6.3-0ubuntu5 => 0.7.3-0ubuntu1] (no packageset)
[14:45] <rbasak> ^ FFe approved and it's not in an image
[14:47] -queuebot:#ubuntu-release- Unapproved: accepted swtpm [source] (lunar-proposed) [0.7.3-0ubuntu1]
[14:52] -queuebot:#ubuntu-release- Unapproved: vim (lunar-proposed/main) [2:9.0.1000-4ubuntu2 => 2:9.0.1000-4ubuntu3] (core, i386-whitelist)
[14:56] <bdrung> rbasak, I am not sure if not having the debconf generation in the debdiff is really a problem. Let me explain the debconf issue with some examples: Kiev was renamed Kyiv. Without any change, both names could be selected in debconf. if you add kiev to the conversion list in tzdata.config, you will get an inconsistency which will not detected by test_timezone_conversions
[14:58] <bdrung> rbasak, explaining this now makes me think that the debconf template generation should have a allow list for symlinks as well. Then it will fail in this Kiev to Kyiv rename case if both could be selected.
[14:58] <rbasak> bdrung: I'm not saying it's a problem. I'm just saying that whatever changes are made, they should be verified - either automatically or manually. And for review, everything that appears in the debdiff should have an explanation. If there's automated stuff happening, then that's fine, but we should explain it in the wiki, so that it doesn't get held up by confused reviewers.
[14:59]  * bdrung agrees.
[15:41] <vorlon> ricotz: libreoffice/lunar should not be accepted today, it's not beta-critical and does not warrant media respins and re-testing
[15:45] <jbicha> ubuntu-release: please promote the Ubuntu Desktop amd64 iso from pending/ to current/ since the isotracker download link points to current/
[15:46] <jbicha> promoting from pending to current is manual currently, after the switch to the new installer
[15:49] -queuebot:#ubuntu-release- Unapproved: swi-prolog (lunar-proposed/universe) [9.0.4+dfsg-1ubuntu1 => 9.0.4+dfsg-1ubuntu2] (no packageset)
[15:50] -queuebot:#ubuntu-release- Unapproved: accepted swi-prolog [source] (lunar-proposed) [9.0.4+dfsg-1ubuntu2]
[15:52] -queuebot:#ubuntu-release- Unapproved: logol (lunar-proposed/universe) [1.7.9+dfsg-6 => 1.7.9+dfsg-6build1] (no packageset)
[15:53] -queuebot:#ubuntu-release- Unapproved: accepted logol [source] (lunar-proposed) [1.7.9+dfsg-6build1]
[15:53] -queuebot:#ubuntu-release- Unapproved: ppl (lunar-proposed/universe) [1:1.2-8.1build1 => 1:1.2-8.1build2] (no packageset)
[15:53] <ricotz> vorlon, I see, ack (unfortunately the autopkgtests were slow again)
[15:54] -queuebot:#ubuntu-release- Unapproved: accepted ppl [source] (lunar-proposed) [1:1.2-8.1build2]
[16:00] <rbasak> bdrung: are you planning re-uploads of tzdata today with the -v?
[16:01] <schopin> ubuntu-release: vim isn't beta critical either, I kinda forgot about the beta freeze, sorry :/
[16:09] <vorlon> schopin: no worries, we can just not look at the unapproved queue for anything people aren't screaming for
[16:17] <orndorffgrant> lucasmoura, vorlon: following up on the lscpu vs dpkg arch differences conversation. I've submitted an issue for livepatch-client here to discuss moving away from parsing lscpu outpu: https://github.com/canonical/livepatch-client/issues/348 and for pro-client I made this issue for using uname -m for livepatch related things
[16:17] <orndorffgrant> https://github.com/canonical/ubuntu-pro-client/issues/2517
[16:17] -ubottu:#ubuntu-release- Issue 2517 in canonical/ubuntu-pro-client "livepatch support should be queried with kernel architecture, not user-space package arch" [Open]
[16:18] <vorlon> orndorffgrant: cheers
[16:21] <bdrung> rbasak, yes. Do you need to drop the current version or can I just do the upload?
[16:21] <rbasak> You can just upload on top.
[16:22] <rbasak> I'm reviewing from what's there currently so it's easier to keep it there for now if you don't mind. I'll clean up after.
[16:22] <rbasak> No need to change the version strings.
[16:26] -queuebot:#ubuntu-release- Unapproved: tzdata (kinetic-proposed/main) [2023b-0ubuntu<IP_ADDRESS> => 2023c-0ubuntu<IP_ADDRESS>] (core)
[16:26] -queuebot:#ubuntu-release- Unapproved: tzdata (jammy-proposed/main) [2023b-0ubuntu<IP_ADDRESS> => 2023c-0ubuntu<IP_ADDRESS>] (core)
[16:27] <bdrung> rbasak, re-upload done
[16:27] -queuebot:#ubuntu-release- Unapproved: tzdata (bionic-proposed/main) [2023b-0ubuntu<IP_ADDRESS> => 2023c-0ubuntu<IP_ADDRESS>] (core)
[16:27] -queuebot:#ubuntu-release- Unapproved: tzdata (focal-proposed/main) [2023b-0ubuntu<IP_ADDRESS> => 2023c-0ubuntu<IP_ADDRESS>] (core)
[16:30] <rbasak> Thanks!
[16:35] <jbicha> vorlon: are you able to do the iso promotion or do you know who we could ask?
[16:36] <vorlon> jbicha: what do you mean by "iso promotion"
[16:37] <jbicha> vorlon: copy the Ubuntu Desktop amd64 daily-live iso from pending/ to current/
[16:38] <vorlon> that's supposed to happen automatically based on test results
[16:38] <jbicha> it doesn't work yet
[16:38] <vorlon> (or the absence of test results if none are defined)
[16:38] <vorlon> well that seems bad!
[16:39] <vorlon> jbicha: daily-live/current has a bunch of symlinks pointing to today's build
[16:39] <vorlon> ah but not for amd64 which is at 20230324
[16:39] <vorlon> so if that one was promoted but 20230329 was not does that mean tests *did* pass but have regressed?
[16:40] <vorlon> jbicha: I would note that none of this is relevant for beta
[16:41] <jbicha> vorlon: maybe there is a different bug but http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275082/testcases "link to the download information" is pointing to current
[16:41] <vorlon> well that's silly, it should point to the serial
[16:41] <jbicha> so I'm concerned that we could get test reports for the wrong iso
[16:42] <jbicha> it did for previous milestones 🤷
[16:42] <vorlon> let me check that
[16:42] <vorlon> fixed
[16:43] <jbicha> my understanding is that previous amd64 ISOs since the switch to subiquity have been promoted to current manually ☹
[16:43] <vorlon> don't know who did that
[16:43] <jbicha> thanks!!
[16:43] <vorlon> ok well I'm not touching manual promotion given that the beta problem is fixed.  Someone on Desktop Team needs to either own getting the auto tests fixed, or own regressing auto test coverage
[16:44] <vorlon> (and it would be ideal if QA Team were resourced to address sorting this out, but in the meantime-)
[16:46] <bdmurray> vorlon: you may have fixed bug 2012345
[16:46] -ubottu:#ubuntu-release- Bug 2012345 in Ubuntu QA Website "Links for Ubuntu Lunar ISO downloads are incomplete" [Undecided, New] https://launchpad.net/bugs/2012345
[16:47] <rbasak> Argh. tzdata Focal and Bionic are *differently different*? :-/
[16:49] <seb128> vorlon, I'm working with paride on getting the ISO tests working with the new installer, the provisioning got updated to switch from d-i preseeding style to subiquity autoinstall but there are some problems still so we have been relying on Lukasz to promote our images from pending to current on a semi regular basis through pings after rounds of manual testing
[16:50] <vorlon> ack
[16:51] <vorlon> still not relevant for beta (anymore) ;)
[16:51] <vorlon> bdmurray: partial fix.  This new product was set up without all the usual auxiliary links, as mentioned
[16:51] <vorlon> queuing that to maybe finish today
[17:37] <AlsoItzSwirlz> ginggs: sorry, but is everything ok with the cinnamon image? the qa tracker says its rebuilding, i don't see a 3/29 build and if an image is taking 3 hours to build, I don't think its just installing cinnamon
[17:37] <AlsoItzSwirlz> is it installing every single flavor package? lol
[17:40] -queuebot:#ubuntu-release- Unapproved: sphinx (lunar-proposed/main) [5.3.0-3 => 5.3.0-4] (i386-whitelist, ubuntu-desktop, ubuntu-server) (sync)
[17:42] <vorlon> ItzSwirlz: you can always check here if an image build has been successfully dispatched https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/lunar/ubuntucinnamon
[17:42] -queuebot:#ubuntu-release- Unapproved: libsigc++-3.0 (lunar-proposed/universe) [3.4.0-1 => 3.4.0-1ubuntu1] (no packageset)
[17:43] <AlsoItzSwirlz> 30 seconds left supposedly?
[17:43] <vorlon> in this case we ran into some hangups with the image builds actually getting dispatched; owing to ubuntucinnamon being a new product
[17:43] <AlsoItzSwirlz> no problem, it's alright
[17:43] <vorlon> yes, the build was only kicked off a few minutes ago when bdmurray noticed it
[17:43] <AlsoItzSwirlz> no problem
[17:43] -queuebot:#ubuntu-release- Unapproved: accepted libsigc++-3.0 [source] (lunar-proposed) [3.4.0-1ubuntu1]
[17:44] <vorlon> note that this is the eta for the squashfs build - it then has to be wrapped into an ISO and rsynced over to the web frontend. I'd say give it 10-15 minutes
[17:44] <AlsoItzSwirlz> no problem, i got a free period right now
[17:45] <AlsoItzSwirlz> looks like, according to the logs it isn't installing firefox
[17:46] <vorlon> the snap?
[17:46] <bdmurray> AlsoItzSwirlz: per a previous private conversation I'l be adding the test cases "nstall (entire-disk) and Live Session" for Ubuntu Cinnamon
[17:46] <AlsoItzSwirlz> bdmurray: thank you!
[17:47] <AlsoItzSwirlz> vorlon: yeah, in the seed it's there: https://git.launchpad.net/~ubuntucinnamon-dev/ubuntu-seeds/+git/ubuntucinnamon/tree/desktop
[17:47] <vorlon> AlsoItzSwirlz: livecd-rootfs probably needs to be updated to know to look in this seed for snaps
[17:47] <AlsoItzSwirlz> vorlon: or could it be that i think i put snap as a recommend [(snap:firefox) instead of snap:fierfox]
[17:48] <vorlon> I mean, that's quite possible
[17:49] <vorlon> it's meaningless to 'recommend' a snap from a seed since they're not expressed via dpkg deps
[17:49] <AlsoItzSwirlz> let me check other seeds
[17:49] <vorlon> and yeah I checked livecd-rootfs and the code is generic with respect to picking up snaps from 'desktop'
[17:49] <arraybolt3[m]> I'm almost positive Lubuntu doesn't attempt to "recommends" the Firefox snap, it just includes it.
[17:50] <AlsoItzSwirlz> Yep. Studio's code highlights it well, putting the parens around "firefox" and later saying specifically snap:firefox
[17:50] <vorlon> is this... the first image build
[17:50] <vorlon> ?
[17:51] <vorlon> ah no there were builds before but they've been expired out
[17:53] <AlsoItzSwirlz> i'm trusting snap:gnome-42-2204 is necessary
[17:53] <AlsoItzSwirlz> along with gtk-common-themes
[17:55] -queuebot:#ubuntu-release- Builds: Ubuntu Cinnamon Desktop amd64 [Lunar Beta] (20230327) has been added
[17:57] <bdmurray> AlsoItzSwirlz: https://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275105/testcases
[17:57] <AlsoItzSwirlz> gracias
[17:57] <bdmurray> The latest build didn't actually get published on the isotracker, I could rebuild it now or wait for the firefox issue. AlsoItzSwirlz what do you think?
[17:58] <AlsoItzSwirlz> I didn't push the firefox fix yet so dont worry
[17:58] <AlsoItzSwirlz> There's a few more packages I want to check
[17:58] <AlsoItzSwirlz> okay now it pushed but dw about it
[17:59] <bdmurray> rebuilding now then (good thing its nice and quick!)
[17:59] <AlsoItzSwirlz> its going to take as long as it will to download the current most recent file on school wifi but no problem
[18:01] -queuebot:#ubuntu-release- Unapproved: libsigc++-3.0 (lunar-proposed/universe) [3.4.0-1 => 3.4.0-1ubuntu2] (no packageset)
[18:02] -queuebot:#ubuntu-release- Unapproved: accepted libsigc++-3.0 [source] (lunar-proposed) [3.4.0-1ubuntu2]
[18:08] -queuebot:#ubuntu-release- Unapproved: libsigc++-3.0 (lunar-proposed/universe) [3.4.0-1 => 3.4.0-1ubuntu3] (no packageset)
[18:09] -queuebot:#ubuntu-release- Unapproved: accepted libsigc++-3.0 [source] (lunar-proposed) [3.4.0-1ubuntu3]
[18:14] <AlsoItzSwirlz> ubiquity "try or install" screen still has debian wallpaper, so note #1
[18:16] <bdmurray> Respinning xubuntu-minimal since its rebuild request failed
[18:18] -queuebot:#ubuntu-release- Builds: Ubuntu Cinnamon Desktop amd64 [Lunar Beta] has been updated (20230329.1)
[18:33] -queuebot:#ubuntu-release- Builds: Xubuntu Minimal amd64 [Lunar Beta] has been updated (20230329.1)
[18:42] <bdmurray> vorlon: did you fix the libevernt issue? lubuntu failed to build earlier because of that
[18:42] <bdmurray> *libevent
[18:43] <vorlon> bdmurray: yes, libevent migrated last night
[18:43] <vorlon> bdmurray: so hopefully "earlier" means before that
[18:44] <bdmurray> earlier means the 28th - so rebuilding lubuntu too
[18:45] <seb128> vorlon, could you promote pending to current anyway? it's not an iso for the iso tracker and beta but we still have users testing current and we would like that pointing to an uptodate image
[18:45] <seb128> not an issue...
[18:46] -queuebot:#ubuntu-release- Unapproved: otf2 (lunar-proposed/universe) [3.0.2-1 => 3.0.2-1ubuntu1] (no packageset)
[18:47] -queuebot:#ubuntu-release- Unapproved: accepted otf2 [source] (lunar-proposed) [3.0.2-1ubuntu1]
[18:47] <vorlon> rebuilding ubuntu-unity after fixing the seed for snaps
[18:48] <vorlon> seb128: not a priority from my side, sorry
[18:49] <seb128> vorlon, sorry I though that was a one command 5s type of job, if it's creating work it can wait
[18:49] <vorlon> seb128: 5 minutes to figure out what the command is, 5s to run it
[18:50] <seb128> fair enough, sounds like something to document in the team process for the next person to figure it out
[18:52] <seb128> Lukasz know how to do it but he doesn't seem to be around or at least not on IRC?
[18:52] <vorlon> sure; it's past EOD
[18:53] <vorlon> (also today is a sick day for him)
[18:53] <seb128> right, I meant he was not there earlier, I checked hr.c.c but that didn't reflect it
[18:56] <vorlon> seb128: what I *DO* know how to do offhand is to disable waiting for test results before promoting to current, if you want that
[18:57] <seb128> vorlon, the end result is the same right?
[18:57] <seb128> I just want to avoid confusion of people thinking they test beta by fetching current
[18:57] <vorlon> the difference is whether you're pinging the release team daily, or only once you're ready to turn the gating back on
[18:58] <seb128> I think at this point of the cycle that's what we want so please do it
[19:08] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Lunar Beta] (20230329) has been added
[19:15] <bdmurray> Okay, lubuntu built
[19:22] <arraybolt3> \o/
[19:23] <arraybolt3> Ah, and Unity is already fixed. Very nice.
[19:23] <arraybolt3> Guess this is "test like crazy" day.
[19:32] <vorlon> seb128: ok I've marked it as not-blocked by test results.  (Would be nice to block the legacy images instead by those same tests but I assume code needs changed in 5 other places to handle that, given the discontinuity)  I don't know that this will cause the currently-pending image to be promoted, if you don't see it promoted in the next hour I can sort out a manual promotion
[19:39] <vorlon> bdmurray, jbicha, seb128: fixed the download links, http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275082/downloads
[19:49] -queuebot:#ubuntu-release- Unapproved: otf2 (lunar-proposed/universe) [3.0.2-1ubuntu1 => 3.0.2-1ubuntu2] (no packageset)
[19:50] -queuebot:#ubuntu-release- Unapproved: accepted otf2 [source] (lunar-proposed) [3.0.2-1ubuntu2]
[19:57] <rbasak> bdrung: what was the purpose of https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/tzdata/commit/?h=ubuntu/kinetic&id=fb5ab09a595b2a7eeeddd6630adae99471a8828e? Was that generated by something?
[19:57] -ubottu:#ubuntu-release- Commit fb5ab09 in ~ubuntu-core-dev/ubuntu/+source/tzdata "d/tzdata.config: Use convert_timezone from 2023g-1"
[20:11] <arraybolt3> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2013236 Looks like something has broken with ubuntu-drivers or possibly Broadcom firmware.
[20:11] -ubottu:#ubuntu-release- Launchpad bug 2013236 in ubiquity (Ubuntu) "Failed to install bcmwl wireless driver during the install" [Undecided, Confirmed]
[20:12] <arraybolt3> wget-ing the Ubuntu Desktop Legacy image to confirm that this affects that too.
[20:14] <arraybolt3> uh... tar, I actually no longer have the hardware to test taht.
[20:14] <arraybolt3> *that
[20:18] <vorlon> arraybolt3: thanks.  Probably not something we're fixing for beta.  May be an ubuntu-drivers issue wrt replacing bcmwl source package with broadcom-sta.  Logs on the bug show no evidence of ubuntu-drivers installing broadcom-sta-dkms
[20:19] <arraybolt3> +1, figured it was worth mentioning since it's been happening for a while.
[20:19] <arraybolt3> (btw, for bugs that I think will probably hang things up but that are going unnoticed, what's a good way to bring them up *before* we're in a time crunch?)
[20:20] <vorlon> logs do confirm broadcom-sta-dkms is present on the ISO. apt show confirms that it has Modaliases consistent with the previous bcmwl package
[20:20] <vorlon> arraybolt3: good way> flagging them here works as well as anyt
[20:21] <arraybolt3> Nice, will do.
[20:21]  * arraybolt3 vanishes back into other work
[20:22] <vorlon> arraybolt3: kernel logs don't show a pci dev matching what's supported by either bcmwl or broadcom-sta
[20:23] <arraybolt3> Try looking at the logs of my duplicate bug report, I have a chip in a laptop I used to use for testing that I *know* works with the bcmwl driver.
[20:24] <vorlon> arraybolt3: confirmed, *your* dev matches modaliases (14e4:4359)
[20:25] <arraybolt3[m]> Oh weird.
[20:25] <vorlon> arraybolt3: I suggest deduping the bugs based on this
[20:26] <arraybolt3[m]> +1
[20:28] <vorlon> arraybolt3: yeah on the parent bug, the device in question wouldn't have had bcmwl loaded in jammy either
[20:29] <arraybolt3[m]> That's weird, since it used to work for him. Are there multiple Broadcom drivers or something?
[20:29] <arraybolt3[m]> Oh, actually there are. The STA driver, the new STA driver, and the b43 driver...
[20:29] <vorlon> arraybolt3: he asserts "bcmwl was installed correctly" but I doubt this is true
[20:29] <vorlon> he probably had wifi *working*, with a different driver
[20:30] <arraybolt3[m]> Which would make sense since I think Macbooks have different Broadcom chips than normal laptops at least in some instances.
[20:34] <vorlon> arraybolt3: from the live env, please run 'ubuntu-drivers devices', 'ubuntu-drivers list' and paste to the bug
[20:34] <vorlon> ubuntu-unity build failed, saying it couldn't download the very snap I just seeded
[20:34] <vorlon> investigating
[20:34] <arraybolt3[m]> Unfortunately, the laptop I reproduced the bug on had to be put into normal use and isn't available for testing right this second. I might be able to boot it into a live env in a bit though.
[20:35] <vorlon> arraybolt3: 'ubuntu-drivers' probably works in a chroot fwiw
[20:36] <arraybolt3> Hmm, not a bad idea, but I have Jammy installed on the machine right now, not sure if that's helpful?
[20:36] <arraybolt3> But if it's just the live env, no big deal, I can just flash a USB, boot it, do the test, then boot it back into the normal OS.
[20:37] <vorlon> I'm saying if it's easier than taking your current workload down for rebooting, you can mk-sbuild yourself a lunar chroot, install ubuntu-drivers-common into that, and see what it says
[20:38] <vorlon> trying the ubuntu-unity build again in case this is a fluke with the store
[20:38] <arraybolt3> Ah, that makes sense. It's not that hard though (that alternative is actually harder :P)
[20:38] <arraybolt3> (It's not being used as my PC, I'm turning it into a weird server of sorts.)
[20:52] <arraybolt3> OK, booting a legacy Desktop ISO on it now.
[20:52] <rbasak> bdrung: also, what's the upstream source for debian/icu?
[20:52] -queuebot:#ubuntu-release- Unapproved: ubuntu-unity-backgrounds (lunar-proposed/universe) [22.10.1-0ubuntu1 => 23.04-0ubuntu1] (no packageset)
[20:52] <rbasak> I found https://github.com/unicode-org/icu/tree/main/icu4c/source/data/misc, but it isn't clear to me if that's where you're getting it from. I don't see a matching tag.
[20:52] <arraybolt3> vorlon: Info added to report.
[21:04] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Lunar Beta] has been updated (20230329.2)
[21:08] <vorlon> found the ubuntu-unity issue, it was my dumb editing mistake
[21:25] -queuebot:#ubuntu-release- Unapproved: qtcreator (lunar-proposed/universe) [9.0.2-1 => 9.0.2-2] (qt5) (sync)
[21:25] <bdmurray> rbasak: icu-data upstream is here https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew
[21:26] <vorlon> blaaaahhhh ubuntu-unity still failed because livecd-rootfs pulls the seeds from archive-team.internal which hadn't refreshed yet
[21:26] <vorlon> should've waited 5 minutes
[21:31] <bdrung> rbasak, see update-icu from debian/rules
[21:35] <vorlon> jbicha: looking at reports I don't check up on often, I see that gnome-remote-desktop in jammy-updates has had phasing at 0 since January 5.  Are you aware of this, have you reviewed the errors that caused phasing to halt?
[21:35] <vorlon> (https://ubuntu-archive-team.ubuntu.com/phased-updates.html)
[21:47] <rbasak> bdrung: ah thanks! I looked for a debian/README* or similar and in debian/watch, debian/upstream/ etc  but didn't think to look for a custom rule.
[21:48] <vorlon> since it's under debian/ unfortunately a debian/watch wouldn't dtrt
[21:50] <rbasak> yeah but I was looking for a comment or something
[21:50] <rbasak> I had also looked in debian/copyright
[21:50] <rbasak> just for a pointer
[21:50] <rbasak> bdrung: debian/icu/zoneinfo64.txt seems to mismatch?
[21:50] <LocutusOfBorg> please reject sphinx/5.3.0-3ubuntu1 in unapproved queue
[21:50] <rbasak> Only on version, but is that expected?
[21:50] <LocutusOfBorg> 5.3.0-4 in the same queue has a proper fix
[21:51] -queuebot:#ubuntu-release- Builds: Ubuntu Unity Desktop amd64 [Lunar Beta] (20230329.3) has been added
[21:51] <rbasak> bdrung: https://paste.ubuntu.com/p/g9JScs3rRK/
[21:52] <rbasak> I don't know if a version mismatching the expected one might cause an issue
[21:54] <rbasak> bdrung: also did you see my earlier question? What was the purpose of https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/tzdata/commit/?h=ubuntu/kinetic&id=fb5ab09a595b2a7eeeddd6630adae99471a8828e? Was that generated by something?
[21:54] -ubottu:#ubuntu-release- Commit fb5ab09 in ~ubuntu-core-dev/ubuntu/+source/tzdata "d/tzdata.config: Use convert_timezone from 2023g-1"
[22:02] <rbasak> Oh, I see:   * Update the ICU timezone data to 2023a (2023b is not available yet)
[22:03] <rbasak> OK so just the tzdata.config question remaining right now. I'll continue to review.
[22:09] <bdrung> rbasak, the convert_timezone function is used to update obsolete timezones (e.g. rename kiev to kyiv) to timezones that can also be selected by debconf.
[22:10] <bdrung> The use of convert_timezone from 2023g-1 ensures that the conversion is consistent with all the updates.
[22:13] <bdrung> commit 09c572f98c4d55478ab163488ee2ad12e2fdc24b ("Build timezones that differ pre-1970"), da07a111db15f0f70957fb6aa68cac6ee1a9b051 ("Update conversion targets to America/Indiana/Indianapolis"), 5c6c755c00842a77dc7c186a4b8622f8b7f1fa99 ("Do not update US/* timezones to their America/* counterparts"), 4c2b898ef99c134a9d202405643136d4b0d38048 ("Drop wrong conversion of the Pacific/Enderbury timezone")
[22:13] <rbasak> bdrung: I don't understand how that relates to the diff
[22:13] -queuebot:#ubuntu-release- Unapproved: unity-tweak-tool (lunar-proposed/universe) [0.0.7+-0ubuntu10 => 0.0.7+-0ubuntu11] (no packageset)
[22:14] <rbasak> Looks like a bunch of refactoring with no functional change? Where did that come from?
[22:14] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (lunar-proposed/main) [2.817 => 2.818] (desktop-core, i386-whitelist)
[22:15] -queuebot:#ubuntu-release- Unapproved: ubuntu-settings (lunar-proposed/main) [23.04.3 => 23.04.4] (ubuntu-desktop)
[22:16] <bdrung> rbasak, since i took the whole function from 2023g-1 it includes the refactorings as well: be005c0482bd45d676e9ab85beb8a89f584dee0e ("d/tzdata.config: Sort timezone case matches alphabetical"), 6648a42324af7e4a27e65640e383a99c70445bc5 ("d/tzdata.config: Group matches by target timzones")
[22:17] <bdrung> and commit 41a71b73947165a26583218421ece599b3009b6a ("d/tzdata.config: Make case statement format consistent")
[22:17] <rbasak> I see :-/
[22:17]  * rbasak isn't sure how to review this then
[22:18] <rbasak> Normally I wouldn't expect an SRU to do refactoring.
[22:18] <rbasak> https://wiki.ubuntu.com/StableReleaseUpdates#tzdata also says that we don't expect to change packaging in tzdata SRUs
[22:21] <rbasak> What about stuff like the removal of "Enderbury" -> "Pacific/Kanton"?
[22:21] <bdrung> tzdata SRUs include addition and renames of timezones. That causes changes to the convert_timezone function and also to the debconf template generation code. That's why I backported the changes to those parts to the SRU, but kept the remaining part of tzdata.config unchanged.
[22:23] <rbasak> But isn't stuff being removed, too?
[22:24] <rbasak> Which is particularly hard to see because of the reordering refactor, but "Enderbury" is a concrete example.
[22:27] <bdrung> rbasak, the timezone "Enderbury" did not exist, the replacement was meant to be "Pacific/Enderbury"
[22:27] <rbasak> Oh OK so that one came from https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/tzdata/commit/?id=4c2b898ef99c134a9d202405643136d4b0d38048
[22:27] -ubottu:#ubuntu-release- Commit 4c2b898 in ~ubuntu-core-dev/ubuntu/+source/tzdata "Drop wrong conversion of the Pacific/Enderbury timezone"
[22:27] <rbasak> But that's a change that might regress users, no?
[22:27] <rbasak> Fine for a development release, but not for a stable release?
[22:30] <bdrung> not really, since the timezone "Enderbury" did / does not exist and users could not set it and it would have been broken. On upgrades these broken timezone would not be changed to "Pacific/Kanton".
[22:30] <bdrung> user could have set the timezone to Pacific/Enderbury.
[22:31] <rbasak> How can I confirm that for my review?
[22:33] <bdrung> You could check that no package ships /usr/share/zoneinfo/Enderbury. You could dpkg-reconfigure tzdata to Pacific -> Enderbury. Then upgrade the package.
[22:36] <rbasak> Are there other changes like this one that need similar consideration?
[22:36] <rbasak> This kind of thing is what SRU documentation is supposed to be used for, and why we don't expect unrelated changes to be backported without an SRU bug to explain it :-/
[22:37] <rbasak> It might all be correct, but what's the point of an SRU review if not to check, and in that case, surely this isn't a reasonable way to present it to the SRU team for review?
[22:38] <bdrung> would it have been better to cherry pick all those changes to the tzdata.config file separately?
[22:39] <rbasak> From a review perspective it's easier not to cherry-pick unnecessary changes at all. SRU policy is to keep changes minimal, and I think this thread is one good explanation as to why.
[22:41] <rbasak> The same goes for the bash -> Python template generation refactoring really.
[22:42] <rbasak> It should at least have been explained in an SRU bug
[22:42] <rbasak> Like maybe it is a better approach and we do want it in an SRU. But that decision is supposed presented for review by the SRU team.
[22:43] <rbasak> supposed *to be* presented
[22:44] <rbasak> I haven't finished reviewing that part either FWIW. I was working breadth-first - trying to understand what bits were changed for what reason first.
[22:45] <bdrung> The Python code is simple to read/write than Shell code and more robust compared to the "find | egrep | sort" construct that needs to be touched.
[22:45] <bdrung> rbasak, do you look at the git repository? the commits have some explanation.
[22:47] <rbasak> "Drop wrong conversion of the Pacific/Enderbury timezone" isn't really an explanation!
[22:47] <rbasak> I mean I can see it's a conversion from the diff. So that might as well say "Fix wrong thing".
[22:48] <bdrung> "Drop wrong conversion of the Pacific/Enderbury timezone" -> "Pacific/Enderbury" != "Enderbury"
[22:49] <rbasak> The Python code is simple...> sure, but that's not normally what we do in SRUs.
[22:49] <rbasak> To review such an SRU, it's then required to review all of that, rather than what might be small diffs.
[22:50] <rbasak> See "In line with this, the requirements for stable updates..." in https://wiki.ubuntu.com/StableReleaseUpdates
[22:50] <rbasak> That's my expectation when reviewing an SRU, and I would expect deviation from that to come with an explanation as to why this case is exceptional.
[22:50] <rbasak> I'll ask other SRU team members for an opinion on how to proceed here.
[22:50] <rbasak> And move on for now.
[22:51] <bdrung> https://paste.ubuntu.com/p/pRQMHMCTng/
[22:58] <bdrung> rbasak, I extended the [ Other Info ] section in bug #2012599
[22:58] -ubottu:#ubuntu-release- Bug 2012599 in tzdata (Ubuntu Lunar) "tzdata 2023a/2023b/2023c release - Egypt restoring DST" [Critical, Fix Committed] https://launchpad.net/bugs/2012599
[23:01] <bdrung> rbasak, including the changes for "Build timezones that differ pre-1970" makes the diff bigger. Maybe it would have been better to split that into two SRUs.
[23:18] <teward> ubuntu-archive: spotcheck my knowledge please - the builders for releases, release-updates, and release-security (where release is any given release name) do NOT include the backports repo in available libraries in the build envs, correct?
[23:18] <teward> (it was my understanding that only -backports targeted things get -backports included in the builder at build time)
[23:19] <cjwatson> teward: correct, see https://git.launchpad.net/launchpad/tree/lib/lp/soyuz/adapters/archivedependencies.py#n72
[23:19] <teward> Eickmeyer: ^ relevant to the pinging in #ubuntustudio-devel you're doing for me
[23:20] <cjwatson> (and just to be clear, they're all the same builders, just with different job configuration dispatched to them)
[23:24] <Eickmeyer> teward: ack, kindof knew that.
[23:25] <teward> cjwatson: ack, i knew they're the same builders but I was implying in the *environment* within the builder at build time (hence the different job confs)
[23:25] <teward> cjwatson: thanks for confirming what I already knew ;)
[23:26] -queuebot:#ubuntu-release- Unapproved: xdg-terminal-exec (lunar-proposed/universe) [0~20221120-1 => 0~20230318-1] (no packageset) (sync)
[23:26] <teward> this came up as a q from Eickmeyer about backporting libzita-alsa-pcmi which would cause an ABI bump and be incompatible with the current version in LTS if backported so then it'd be NCR(s) against "backported" but that's not a thing, hence the question to confirm my knowledge of the builder envs
[23:26] -queuebot:#ubuntu-release- Unapproved: accepted xdg-terminal-exec [sync] (lunar-proposed) [0~20230318-1]
[23:27] <teward> (so the only way that'd work would be to backport the library, and then backport all the tools that depend on it) cc ddstreet_away mapreri
[23:28] <Eickmeyer> I'd have no problem with backporting any of those tools since it's only a handful so long as I get everything to build correctly in a PPA first.
[23:28] <Eickmeyer> And of course, submitting as separate backport requests.
[23:29] <Eickmeyer> The biggest issue is that it doesn't qualify for SRU since it's two versions ahead and several changes, not a simple bugfix, nor can it be cherry-picked without opening a can of worms.
[23:46] <vorlon> Trevinho: it would have been helpful to have some follow-through from the Desktop side on the gtk4 promotion of libgtk-4-media-gstreamer to a Recommends:, Recommends are not enforced by proposed-migration so users who install the beta will not have it because libgtk-4-media-gstreamer is not yet in main and wasn't included on the candidate images
[23:48] <Trevinho> vorlon: oh, I thought seb128 had handled that main inclusion
[23:48] <vorlon> not according to https://ubuntu-archive-team.ubuntu.com/component-mismatches.html