[00:23] <GridCube> ochosi, one of madnick's awesome mockup greeters had a nice clock like that, it also said the version of ubuntu you where using i remember :P
[00:24] <madnick> I had? :P
[00:24] <GridCube> you did
[00:25] <GridCube> remember back in the day, i made a silly mspaint mockup too :P
[00:25] <madnick> I will take your word for it, I acctually don't have access to my old ones
[00:25] <madnick> My sister has the USB drive :P
[00:26] <madnick> http://www.madnick.se/~madnick/test-draft-res.png
[00:26] <madnick> http://www.madnick.se/~madnick/test-draft2.png
[00:26] <GridCube> those are new ones
[00:26] <madnick> yeah :P
[00:27] <GridCube> great i start making a bugreport and software-center decides to work
[00:28] <GridCube> well it did not
[00:29] <GridCube> https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/890025
[00:30] <GridCube> damn me and whit
[01:16] <knome> mr_pouit, micahg_: http://paste.ubuntu.com/737846/
[01:16] <knome> mr_pouit, micahg_: 'sudo apt-get install alacarte'
[01:21] <micahg_> knome: yes?  that's why we don't seed it :)
[01:21] <knome> what's the alternative?
[01:22] <knome> we tell the people you can edit menus in 11.10, but the fallback is that you need to install compiz?
[01:22] <micahg_> not sure
[01:23]  * micahg_ wonders if obmenu would work in xfce
[01:27] <knome> does it support the fd.org spec?
[01:35] <micahg_> no idea, just found it
[01:35] <micahg_> ah, no, it's openbox specific
[01:42] <knome> mmh :|
[01:43] <knome> i'll be off for today
[01:43] <knome> see you later!
[09:43] <mr_pouit> micahg_: hey, do you have an oneiric system to test exo from -proposed? (Bug #878069) I uploaded it, so I think I can't set it to verification-done myself ;-)
[09:48] <ochosi> mr_pouit: does it make sense to test it on 64bit oneiric?
[09:51] <mr_pouit> ochosi: yes, it's only broken on amd64, i386 will work fine
[09:51] <mr_pouit> most of the helpers should be broen on amd64 in oneiric, and they should work again with the -proposed package
[09:53] <micahg_> mr_pouit: yeah, can try later this week
[09:54] <mr_pouit> thanks!
[10:10] <ochosi> mr_pouit: if the package is already in proposed, i'll quickly switch mirrors and then upgrade and let you know
[10:18] <ochosi> mr_pouit: seems like the package isn't there yet (using main mirror)
[10:19] <micahg_> ochosi: mr_pouit: exo is stuck in binary new
[10:21] <ochosi> oh, ok
[11:01] <knome> i just asked in #ubuntu-website and they told the team reports are abandoned until somebody takes care of the project.
[11:01] <knome> ...
[11:06] <madnick> All team reports?
[11:06] <knome> all team reports.
[11:57] <astraljava> Well, it sounded too good to be true in the first place.
[11:58] <knome> mmh. well, i suppose it worked for some time...
[11:58] <Unit193> I seemed to have missed something
[11:59] <knome> 13:01  knome: i just asked in #ubuntu-website and they told the team reports  are abandoned until somebody takes care of the project.
[11:59] <Unit193> Dang
[11:59] <knome> Unit193, want to start caring after it?
[12:01] <Unit193> I don't fully know what that is
[12:01] <knome> https://wiki.ubuntu.com/BuildingCommunity/TeamReporting
[16:45] <ochosi> meh, i was pretty sure that the gtk3-version of thewidgetfactory gets shipped in oneiric, but it seems like it's gtk2 :/
[17:17] <plantoschka> is 12.04 going to use xfce 4.10 ?
[17:17] <baizon> if 4.10 will be released until then
[17:17] <baizon> plantoschka: http://wiki.xfce.org/releng/4.10/roadmap
[17:18] <Unit193> They aren't on schedule, so my guess is no
[17:18] <plantoschka> march should be ok?
[17:18] <baizon> yes but then xubuntu will be in beta status
[17:18] <baizon> so its too late then
[17:19] <baizon> i think 4.10 will be on 12.10
[17:20] <plantoschka> ok
[17:20] <baizon> but who knows :)
[17:20] <plantoschka> probably the better decision for a LTS
[17:21] <baizon> you can ask on feb
[18:13] <ochosi> i think there's no way that 4.10 will land in 12.04
[18:14] <Unit193> That's what I thought, but I'm just a random
[21:33] <pleia2> knome: btw, 22UTC on Saturday would be great for the site sprint, turns out I have a cousin from far away in town on Saturday and she wants to do lunch before that ;)
[21:45] <astraljava> Hey guys, my Studio installation Indicator Plugin doesn't show the volume icon. Since I still know very little of XFCE, can anyone hazard a guess as to why is that?
[23:30] <knome> pleia2, right. :)


[07:21] <sakrecoer[m]> <OvenWerks "徒 𝖘𝖊𝖙𝖙𝖔 セット🕸🏴: detach?a"> Well.. when I run a2jmidi_bridge or j2amidi_bridge on the terminal, it runs fine, but it Will put my terminal on standby until I stop the process
[07:21] <sakrecoer[m]> Meaning if I run a2jmidi_bridge and now I also want to run a j2amidi_bridge I have to start another terminal
[07:22] <sakrecoer[m]> For my setup I need 2x j2amidi_bridge and 1x a2jmidi_bridge
[07:24] <sakrecoer[m]> This is because ardour is showing up as a jack midi connection (probably die to my FireWire soundcard?) while most of my hardware synths show up in alsa midi because they have USB midi port.
[07:25] <sakrecoer[m]> Wait... I haven't even tried running `a2jmidid`
[07:26] <sakrecoer[m]> Have to look into that... I usually just run the bridge
[07:28] <sakrecoer[m]> No, a2jmidid doesn't detachm not in the send I understand it...
[07:28] <sakrecoer[m]> Sense*
[07:29] <sakrecoer[m]> It runs all good, but the terminal is not useable once it's raining. I have to stop the process to be able to do anything
[07:29] <sakrecoer[m]> Gah... Spelling
[07:29] <sakrecoer[m]> Once it's *running
[07:30] <sakrecoer[m]> Also a2jmidid doesn't give me a j2a bridge... Only a2j
[07:31] <sakrecoer[m]> Hmm... No... It does gives me both....
[07:31] <sakrecoer[m]> But I need more of them I'll figure it out
[07:33] <sakrecoer[m]> Well that was easy!!! Sorry for wall of text, but thank you for clearing it up for me OvenWerks !!!
[07:34] <sakrecoer[m]> For anyone wondering `a2jmidid -e` will create a bridge for each connected hardware too
[08:51] <sakrecoer[m]> Oh yes oh yes!!! Ardour templates saves the midi connection :') as expected but still. :')
[13:57] <OvenWerks> sakrecoer[m]: why do you need more midi bridges?
[13:57] <OvenWerks> sakrecoer[m]: by the way, the commandline you are probably looking for is: a2jmidid -e &
[13:58] <sakrecoer[m]> <OvenWerks "徒 𝖘𝖊𝖙𝖙𝖔 セット🕸🏴: why do y"> I don't when I run a2jmidid. But just running j2a/a2jmidi_bridge I needed more because I had to do a bridge per device...
[13:59] <sakrecoer[m]> <sakrecoer[m] "I don't when I run a2jmidid. But"> `a2jmidid -e` even
[13:59] <OvenWerks> or if the random outputs are anoying: a2jmidid -e >~/midi.log &
[13:59] <OvenWerks> if you add the & on the end it will go background
[14:00] <sakrecoer[m]> <OvenWerks "if you add the & on the end it w"> Thanks!! I didn't know that one! :)
[14:01] <OvenWerks> but unless you redirect all the terminal i/o it will still stop if you get rid of that terminal
[14:01] <sakrecoer[m]> But I made so that a2jmidid -e is ran when I start jack.
[14:01] <OvenWerks> how are you starting jack?
[14:01] <sakrecoer[m]> With qjackctl
[14:02] <OvenWerks> so with "execut script after startup" then. you can still add the &
[14:02] <OvenWerks> s/can/should/
[14:04] <sakrecoer[m]> Awesome!! Noted. I haven't actually tried it yet. It just stroke me earlier when away from compu that there is that option to execute script after startup
[14:04] <sakrecoer[m]> Many many thanks OvenWerks !!!
[14:04] <OvenWerks> YW
[20:03] <myNonSpellChecke> Hi all, I'd appreciate your asssitance on the following.
[20:03] <myNonSpellChecke> ubuntustudio@UBUNTU-STUDIO:~$ lsb_release -a No LSB modules are available.Distributor ID: UbuntuDescription:    Ubuntu 20.04 LTSRelease:    20.04Codename:   focal
[20:03] <myNonSpellChecke> I have a front and rear mic input on my PC. I can only hear mic input when either front or rear mic is connected to Input Source, 0. If I switch either front or mic input to Input Source, 1 or Input Source, 2 I don't hear anything. Also increased front and rear mic boost with no effect. Any idea what I'm doing wrong? TIA.
[20:03] <myNonSpellChecke> Screenshot of Carla and QasMixer Config: https://i.stack.imgur.com/cGFq4.png
[20:04] <myNonSpellChecke> I also ran a diagnostic tool I found here: http://www.alsa-project.org/alsa-info.sh
[20:04] <myNonSpellChecke> This is the output: https://paste.ubuntu.com/p/8TbW5sVZGR/
[20:04] <OvenWerks> can you also do: arecord -l |pastebinit
[20:05] <myNonSpellChecke> sure one moment
[20:05] <myNonSpellChecke> https://paste.ubuntu.com/p/mjSMHmbVCX/
[20:06] <OvenWerks> One of your inputs is PCH,0,0 and the other one is PCH,2,0
[20:07] <OvenWerks> so it depends on which program you are recording with
[20:08] <OvenWerks> qasmixer or alsa mixer will show the controls for both at the same time (because that's the way alsa works)
[20:09] <OvenWerks> I guess any recording program would have the same problem. It will only record one device at a time. Using jack with zita-a2j should show both
[20:09] <OvenWerks> ubuntustudio-controls can set this up though.
[20:13] <myNonSpellChecke> In the screen shot I've provided of carla, PCH,0,0 = System Capture_1 and PCH,2,0 = System Capture.2?
[20:14] <myNonSpellChecke> Capture_2
[20:15] <OvenWerks> how did you start jack?
[20:15] <OvenWerks> or did you start jack that you are aware?
[20:16] <myNonSpellChecke> I didn't actively start jack. I opened Ubuntu Studio Controls, then clicked the corresponding buttons for Open Carla and Open QasMixer.
[20:17] <OvenWerks> ok so Carla hit the "if jack isn't running start it" thing :P
[20:18] <OvenWerks> if you use -controls to start jack, it will show up with PA bridges in it. (you would need to restart carla after using controls to start jack.
[20:18] <OvenWerks> in -controls you should see an extra devices tab.
[20:19] <OvenWerks> in that tab there is a drop down called "Add". If you set the jack master to PCH,0,0
[20:20] <OvenWerks> then add PCH,2,0
[20:20] <OvenWerks> Apply the new settings (and start jack if you haven't already)
[20:22] <OvenWerks> If you start Carla and look at the patch bay you should have system:capture, system:playback, PCH,2,0:capture and two pulse (in and out) nodes as well
[20:26] <OvenWerks> system capture will be one of the inputs and PCH,2,0 capture should be the other
[20:31] <myNonSpellChecke> jack master settings: https://imgur.com/eeoaC7i.pngextra settings tab: (I added PCH 2,0 and PCH 2,1) https://imgur.com/jC2Anvs.pngCarla Patchbay results: https://imgur.com/WxBrhyl.png
[20:40] <myNonSpellChecke> ALso one item I'm confused about. I reviewed an intro to ALSA here: http://www.volkerschatz.com/noise/alsa.html and the author indicates one must reference car, device, sub device in certain situations, but I see PCH,2,0 as missing a third number. Is that because PCH is a device and hence the card doesn't need to be referenced by number here?
[20:45] <myNonSpellChecke> Also my apologies I just noticed you said to add PCH,2,0 so I remove PCH,2,1. Same result though in Carla.
[20:46] <OvenWerks> PCH replaces the first number yes.
[20:46] <OvenWerks> we use PCH because on systems with more than one audio device the device numers change with differednt boots.
[20:47] <myNonSpellChecke> gotcha
[20:48] <OvenWerks> The last time I booted PCH went from being device 2 to device 1... so using PCH always points to the same device
[20:48] <OvenWerks> after adding the device did you hit the "Apply audio settings"?
[20:49] <OvenWerks> to be honest, I have not played around with PCH audio devices much.
[20:50] <myNonSpellChecke> confirmed, yes I hit apply audio settings.
[20:51] <OvenWerks> interesting
[20:52] <OvenWerks> in a terminal can youn type: ps x |grep zita
[20:52] <OvenWerks> do you see one entry or two?
[20:53] <myNonSpellChecke> https://paste.ubuntu.com/p/q53zz7Z3nq/
[20:53] <myNonSpellChecke> oops
[20:53] <myNonSpellChecke> yes
[20:53] <myNonSpellChecke> although they're all listed as defunct
[20:54] <OvenWerks> Yikes!
[20:55] <OvenWerks> try: killall -sigint zita-a2j zita-j2a
[20:56] <OvenWerks> That should get rid of them all but if not That is ok for now.
[20:57] <myNonSpellChecke> getting an error on the command
[20:57] <myNonSpellChecke> ubuntustudio@UBUNTU-STUDIO:~$ killall -sigint zita-a2j zita-j2aigint: unknown signal; killall -l lists signals.
[20:58] <myNonSpellChecke> -signals ?
[20:59] <OvenWerks> may have to be -s INT
[20:59] <myNonSpellChecke> k
[20:59] <OvenWerks> so killall -s INT zita-a2j zita-j2a
[21:00] <myNonSpellChecke> gotcha, ran the command but ps x |grep zita is still showing the same list of processes, all defunct
[21:01] <myNonSpellChecke> https://paste.ubuntu.com/p/rDdzFMGtjG/
[21:01] <OvenWerks> possible, it means there was nowhere for the output to go when it quit
[21:01] <myNonSpellChecke> gotcha
[21:01] <OvenWerks> Anyway, (lets make another one to see if we can figure out what is happening.
[21:02] <myNonSpellChecke> k
[21:03] <OvenWerks> in a terminal: zita-a2j -j extra -d hw:PCH,2,0 -v
[21:04] <myNonSpellChecke> appears to have succeeded
[21:04] <myNonSpellChecke> it's stated "starting synchronization" and is spitting out 3 columns of numbers
[21:05] <OvenWerks> ok
[21:05] <OvenWerks> control c to stop and the same line with no -v
[21:05] <OvenWerks> (control c is the same a sig INT)
[21:06] <myNonSpellChecke> done. "Starting synchronisation." message
[21:06] <OvenWerks> In carla you should see it.
[21:06] <OvenWerks> (carla patch bay)
[21:07] <myNonSpellChecke> yup got it. I see a box labelled "extra" and a capture_1 and capture_2 inside the box
[21:07] <OvenWerks> That should be your second input.
[21:08] <OvenWerks> Though it seems to think it is a stereo line in rather than a mic.
[21:09] <OvenWerks> The only thing different (things) is that the SR would be 48000 and the buffer would be 256.
[21:10] <myNonSpellChecke> I did a quick google on zita-a2j, and this command creates a bridge from the second input, PCH,2,0 to something that JACK, and by extension Carla can see?
[21:10] <OvenWerks> I find it odd that it would complain if it shows only 48k -controls should have caught that
[21:10] <OvenWerks> yes it does
[21:11] <OvenWerks> this is the same command that -controls uses internally
[21:11] <myNonSpellChecke> gotcha
[21:11] <OvenWerks> The only thing I can think is that the buffer size -controls is using is too small
[21:12] <OvenWerks> controls (in 20.04) uses jack buffersize/2 (as recomended by the auther of zita-ajbridge)
[21:13] <myNonSpellChecke> I hooked everything up in Carla and ran through some tests in Qas Mixer. I'm now about to hear sound on Capture 0 and Capture 1 for either front and rear mic.
[21:13] <OvenWerks> -controls in 20.10 will make sure the buffer for a PCH device is at least 128
[21:13] <myNonSpellChecke> about = able
[21:13] <OvenWerks> So it just mixes the two together?
[21:14] <OvenWerks> or are then on separate chanels?
[21:14] <OvenWerks> channels even
[21:18] <myNonSpellChecke> My apologies I'm an absolute n00b on the details here. But I think they are on separeate channels. I've got front mic on capture 0 and rear mic on capture 1. when I increase the slider for capture 0 only front mic increases in vol. same for capture 1. I'd assume that if the inputs were mixing they volume would go up and down for both regardless of
[21:18] <myNonSpellChecke> which slider I was using in QASMixer.
[21:19] <OvenWerks> ok.
[21:20] <myNonSpellChecke> my problem appears to be solved, thank you very much.
[21:20] <myNonSpellChecke> is there any action I can take to auto matically execute the command you sent for me?
[21:20] <OvenWerks> can you type: cat ~/.config/autojack/autojackrc |pastebinit
[21:21] <myNonSpellChecke> https://paste.ubuntu.com/p/vHmXHwW6y7/
[21:22] <OvenWerks> wow how did you do that? I didn't think it was possible
[21:23] <OvenWerks> if you can wait for 5 min or so I will be back.
[21:23] <myNonSpellChecke> sure
[21:26] <OvenWerks> in -controls you have Added both PCH,0,0 _and_ PCH,2,0
[21:27] <OvenWerks> it should only be PCH,2,0
[21:27] <OvenWerks> so remove PCH,0,0 from the extra devices
[21:27] <OvenWerks>  Then apply and then restart jack
[21:29] <OvenWerks> The zita extra will also stop.
[21:29] <OvenWerks> you already have PCH,0,0 set up as jack's master device.
[21:31] <myNonSpellChecke> confirmed, only PCH,2,0 is now selected in other audio interfaces
[21:32] <OvenWerks> and you have applied and restarted jack?
[21:32] <myNonSpellChecke> confirmed
[21:32] <OvenWerks> carla will probably be blank :) and need to be restarted to pick up jack
[21:33] <OvenWerks> it should now show PCH,2,0:capture
[21:33] <OvenWerks> (PCH_in,2,0 maybe?)
[21:34] <myNonSpellChecke> shit! sorry about this I have to go. I can return to this in about 45 mins if you're still around.
[21:34]  * OvenWerks can't remember
[21:34] <myNonSpellChecke> thank you very much for your help so far.
[21:34] <OvenWerks> no problem... may take me a miniute to respond
[21:34] <myNonSpellChecke> ok great
[22:29] <myNonSpellChecke> I'm back
[22:31] <myNonSpellChecke> OvenWerks I confirmed that restarted jack. when I reopen Carla extra is gone.
[22:32] <OvenWerks> cat ~/.config/autojack/autojackrc |pastebinit
[22:32] <OvenWerks> Again
[22:33] <OvenWerks> Just so I know what we are dealing with
[22:33] <myNonSpellChecke> https://paste.ubuntu.com/p/fqJNY26Zm4/
[22:33] <OvenWerks> Still has not changed
[22:34] <OvenWerks> in the extra tab remove PCH,0,0
[22:34] <OvenWerks> (the only thing left in that tab should be PCH,2,0)
[22:35] <OvenWerks> Then Apply Audio Settings
[22:35] <OvenWerks> then cat ~/.config/autojack/autojackrc |pastebinit
[22:38] <myNonSpellChecke> Simply to clarifiy, atm, Jack Master Settings -> Jack Master Device (no USB) : PCH,0,0 . PCH,0,0 doesn't appear as a device that can be added in Extra Devices -> Connect Other Audio Internal Interfaces
[22:38] <myNonSpellChecke> (or removed, for that matter)
[22:38] <OvenWerks> huh
[22:39] <OvenWerks> ya it should not be available. I am just wondering how it got there
[22:39] <OvenWerks> So maybe start over.
[22:39] <OvenWerks> rm ~/.config/autojack/autojackrc
[22:40] <OvenWerks> restart -controls
[22:40] <myNonSpellChecke> one thing before I execute that command. "how it got there" = how it got set as  Jack Master Device (no USB) ?
[22:40] <OvenWerks> No how it got to be in xtra devices.
[22:40] <myNonSpellChecke> gotcha.
[22:41] <OvenWerks> That should not have been possible
[22:42] <OvenWerks> So after removing that file restart ubuntustudio-controls
[22:42] <OvenWerks> Audio Setup->Jack Master Settings
[22:42] <myNonSpellChecke> ok, so I closed Ubuntu Studio Controls, executed rm ~/.config/autojack/autojackrc in a terminal, reopened Ubuntu Studio Controls, and clicked Start or Restart Jack.
[22:43] <OvenWerks> no
[22:43] <OvenWerks> hit stop jack for a sec
[22:43] <myNonSpellChecke> ok done
[22:43] <OvenWerks> Jack master should be PCH,0,0
[22:44] <OvenWerks> under extra devices->remove there should be nothing
[22:44] <OvenWerks> Apply Audio settings should write the file you just removed.
[22:45] <OvenWerks> so cat ~/.config/autojack/autojackrc |pastebinit to make sure that has done what I expect.
[22:49] <myNonSpellChecke> simply to clarify: I should confirm that jack master and extra devices -> are as you expect _before_ clicking Apply Audio settings?
[22:52] <OvenWerks> no after
[22:52] <OvenWerks> That file should not exist before (I think)
[22:53] <OvenWerks> unless starting jack created it
[22:53] <myNonSpellChecke> let me send you 2 screenshots of where I'm at with Ubunutu studio controls. I just want to make sure I'm understanding your directions properly. Here's how the 2 tabs appear on my computer right now:
[22:53] <myNonSpellChecke> jack master settings - https://imgur.com/WiaHmID.pngextra settings tab - https://imgur.com/dMd3R1j.png
[22:54] <myNonSpellChecke> notice per your instruction also that jack is stopped
[22:56] <OvenWerks> ok in Jack Master Settings change default to PCH,0,0
[22:57] <myNonSpellChecke> done
[22:57]  * OvenWerks notes that there is no "default" in the next version of controls
[22:57] <OvenWerks> ok, Apply audio settings
[22:57] <OvenWerks> then cat ~/.config/autojack/autojackrc |pastebinit
[22:59] <OvenWerks> I want to make sure controls is writing the config file right
[22:59] <myNonSpellChecke> https://paste.ubuntu.com/p/XFgP4rrnHx/
[22:59] <OvenWerks> good
[23:00] <OvenWerks> in extra devices Add, select PCH,2,0
[23:00] <OvenWerks> the do the cat ~/.config/autojack/autojackrc |pastebinit
[23:01] <myNonSpellChecke> Click apply audio settings after Add, select PCH,2,0 and before cat....?
[23:01] <OvenWerks> yes
[23:01] <OvenWerks>  :) thanks
[23:02] <myNonSpellChecke> np
[23:02] <myNonSpellChecke> https://paste.ubuntu.com/p/jM7cdSH7YZ/
[23:03] <OvenWerks> ok start jack
[23:03] <myNonSpellChecke> done
[23:04] <OvenWerks> in terminal: jack_lsp -c |pastebinit
[23:04] <myNonSpellChecke> https://paste.ubuntu.com/p/swzYTSXWKq/
[23:06] <OvenWerks> ps x |grep zita
[23:06] <OvenWerks> does it still show all the defunct ones or is there one good one?
[23:07] <myNonSpellChecke> https://paste.ubuntu.com/p/Kb8Hj4q78B/
[23:07] <myNonSpellChecke> all appear defunct i think
[23:08] <OvenWerks> but we can start zita in the terminal like before?
[23:08] <myNonSpellChecke> would you like me to try that command again at the terminal? zita-a2j -j extra -d hw:PCH,2,0
[23:08] <OvenWerks> zita-a2j -j extra -d hw:PCH,2,0
[23:10] <myNonSpellChecke> gotcha. I just executed that command in a terminal and see the message "Starting synchronisation.". I opened Carla and see the box lablelled "Extra" with capture_1 and capture _2 inside.
[23:11] <OvenWerks> which is what you want
[23:11] <OvenWerks> I do not know (at this time) why controls is not able to do the same
[23:14] <OvenWerks> But I do get the same thing here. so I can continue to trouble shoot here
[23:15] <myNonSpellChecke> gotcha. well the good thing I guess is the problem is reproduceable.
[23:19] <OvenWerks> seems to be that any device,0,0 works (I have three of them) but any device,1,0 or ,2,0 don't
[23:31] <myNonSpellChecke> For the time being, kicking off zita-a2j from the command line should be a good work around for me. Thanks again for your help with this I appreciate it. Did you need any more info from me before I go?
[23:31] <OvenWerks> No it is fine... works the same here
[23:32] <myNonSpellChecke> sounds good. good day!


[03:56] <baelem> so
[03:56] <baelem> anyone here
[03:56] <baelem> well alright then
[03:56] <baelem> bye
[04:58] <Redneck_> howdy all
[05:03] <Redneck_> adios :-/
[05:08] <di> i want to
[05:08] <di> fuuuuuck
[05:08] <di> a duck
[15:27] <Omkar_> Hi all
[15:27] <Omkar_> When will next LTS version come??


[06:06] <pwnguin> is there a gitweb of the ubuntu kernel?
[06:07] <pwnguin> aha
[06:09] <pwnguin> fun. which one of these branches should i be looking at as a base?
[06:09] <pwnguin> ubuntu/ubuntu-hardy.git?
[08:52] <pwnguin> ah; i guess the usbgecko would be the console one logs in with?
[09:32] <bullgard4> What is the function of the bash script /usr/lib/pm-utils/funcrtions?
[09:33] <bullgard4> What is the function of the bash script /usr/lib/pm-utils/functions?
[16:37] <AnAnt> Hello, regarding the blank ttys bug #129910 , is there any further info I should provide ?
[16:37] <ubotu> Launchpad bug 129910 in linux "Blank ttys when using vesafb (vga=xxx)" [Medium,Fix released] https://launchpad.net/bugs/129910
[17:00] <AnAnt> Hello ?
[22:48] <pwnguin> opinions on including the following patch in hardy?
[22:49] <pwnguin> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/updates/2008.0/kernel-2.6/current/PATCHES/patches/DB35_mmc_power_up_delay.patch?view=markup&pathrev=114631
[22:49] <pwnguin> reports suggest it fixes bug #137686
[22:49] <ubotu> Launchpad bug 137686 in linux-source-2.6.22 "[gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs" [Low,Triaged] https://launchpad.net/bugs/137686


[04:10] <guiverc> remind me someone please - what's the command to view keyboard/mouse input  (verify keypresses etc)
[04:12] <Bashing-om> guiverc: 'xev' .
[04:12] <guiverc> merci !!   (i was a long way from x<tab><tab> so thanks heaps Bashing-om !!
[04:14] <Bashing-om> guiverc: We all get writters block .. happens to the best of us :P
[04:14] <guiverc> if only it wasn't so many times per hour :(
[04:15] <Bashing-om> LOL .. Ya must be over 40 years old then.
[04:15] <guiverc> alas yeah
[04:20] <guiverc> if system suspended (qa-test 19.04; lubuntu), after wake mouse-buttons don't work - what package is likely involved?  (for ubuntu-bug...)
[04:21] <Bashing-om> guiverc: The mouse also falls under Xorg .
[04:21] <guiverc> hence the `xev` - makes sense I guess
[04:21] <guiverc> thanks Bashing-om again ...
[11:41] <lotuspsychje> !info linux-image-generic
[15:21] <lordcirth__> During development of Disco, will kernel major versions be bumped before KernelFreeze, or is it assumed that major is static, and only minor updates will happen until KernelFreeze?
[15:24] <lotuspsychje> lordcirth__: this news came out today: https://news.softpedia.com/news/ubuntu-19-04-disco-dingo-will-be-powered-by-linux-kernel-5-0-525202.shtml
[15:24] <lotuspsychje> lordcirth__: i think we can say, until final release alot can still happen
[15:24] <lordcirth__> lotuspsychje, ok, thanks
[15:25] <lordcirth__> 4.20 has the new tcp scheduling that is really cool. No idea if it will be a big performance difference.
[15:26] <lotuspsychje> currently dingo is on 4.19
[15:27] <lordcirth__> Yeah, your bot question reminded me


[07:35] <dholbach> good morning
[07:37] <dpm> morning all
[07:38] <dholbach> hey dpm
[07:41] <dpm> hey hey :)
[08:31] <dpm> hm, on 15.10 gimp consistently crashes X :/
[08:50] <davidcalle> Morning o/
[09:13] <popey> Soooo many pictures on G+ of nexus 4s and nexus 7s running on an external display :)
[09:23] <dpm> yeah \o/
[09:32] <popey> dpm, how did you get the camera rotated correctly? On my device it's rotated 90 degrees
[09:33] <dpm> popey, I rotated the phone :)
[09:33] <dpm> on mine it was 180 degrees
[09:33] <popey> oh, interesting
[09:33] <dpm> I played with both the front and back ones
[09:34] <dpm> both worked well, but I ended up using the front one to show the phone screen on the picture
[09:35] <dpm> I also noticed that either bluetooth or hdmi output really suck batteries
[09:36] <dpm> but my phone power cable didn't reach to the adapter's power input for the pic :)
[14:11] <daker> dpm: hi, can you share your ubucon.de presentation ? is it hosted somewhere ?
[14:12] <dpm> daker, sure, I've not yet uploaded it, but I can e-mail you the PDF in the meantime if you want
[14:12] <daker> dpm: yes thanks!
[14:12] <dpm> the ubucon guys are also putting together the videos, but the feed on my talk is missing the first 15 mins
[14:14] <dpm> done
[14:19] <daker> dpm: oh nice :D
[14:22] <dpm> :)
[14:24] <Pici> /36/36
[14:43] <popey> dpm, spotted an error in your presentation, the mx4 resolution is wrong
[14:44] <dpm> popey, aha. What's the correct value?
[14:44] <dpm> mhall119, how do I schedule the plenaries? I.e. when creating the meeting in summit, which track do I choose for the plenary?
[14:44] <popey> dpm, 1152 × 1920
[14:45] <mhall119> dpm: no track, make it a plenary type and you'll be able to drag and drop it to a plenary slot
[14:45] <dpm> mhall119, great
[14:45] <dpm> thanks popey
[14:45] <popey> np
[14:45] <dpm> czajkowski, hggdh, I'm starting to schedule some of the tracks on the Community track, along with the plenaries
[14:46] <dpm> some of the *sessions*, sorry
[14:49] <dpm> mhall119, just created Jane's plenary (plenary type, no track), but I can't see it on my list of sessions to schedule. Anything else I need to do?
[14:50] <mhall119> dpm: refresh?
[14:50] <mhall119> I can see it
[14:50] <mhall119> oh, maybe you need extra permissions in summit, let me check
[14:50] <dpm> mhall119, that was my point
[14:51] <mhall119> hmmm, you're listed as a manager, so you should see it, let me make you a scheduler too and see
[14:51] <mhall119> dpm: try refreshing now
[14:52] <mhall119> hey, so is our team call today still at 1500 UTC or has it moved to 1600 UTC because of europe's DST change?
[14:54] <mhall119> dpm: I think we need to re-consider the "convergence" track next cycle, it seems about half of my sessions are actually better suited for Show & Tell or App Dev
[14:55] <dpm> mhall119, I always rely on the calendar, regardless of dst. It depends on who scheduled the event. In this case, it's in 1h for this week
[14:56] <dpm> mhall119, I spotted that, but was thinking the other way round: reconsidering show & tell being too successful and stealing the thunder of other tracks :)
[15:02] <dpm> mhall119, dholbach, czajkowski, pleia2, were you thinking of doing another CC Q&A at UOS?
[15:03] <mhall119> next week is a regularly scheduled IRC meeting, but I don't think we have anybody on the schedule forit
[15:18] <davidcalle> mhall119, can you make me a summit scheduler as well?
[15:22] <mhall119> davidcalle: aren't you a track lead?
[15:24] <davidcalle> mhall119, I am, afaict, I can only propose meetings and wait for them to be acked
[15:24] <mhall119> ok, I've made us all schedulers in addition to being managers (and track leads), that should give everybody all the permissions needed
[15:26] <dpm> Schedule looking much better now: http://summit.ubuntu.com/uos-1511/all
[15:32] <davidcalle> dpm, and there are still some pending sessions to ack :) mhall119, I'm davidc3 on summit, not davidcalle, I'm telling you since I haven't seen any changes in my interface
[15:41] <dholbach> davidcalle, do you know why https://developer.ubuntu.com/en/snappy/build-apps/ works fine, but the editor page is empty?
[15:41] <dholbach> is there a way to check the version history?
[15:42] <mhall119> davidcalle: ugh, that would explain it
[15:43] <mhall119> dholbach: in draft mode you will have a "History" menu at the top
[15:43] <davidcalle> dholbach, history -> view history
[15:43] <davidcalle> :)
[15:43] <dholbach> aha!
[15:43] <mhall119> dholbach: as well as a "Revert to live" option
[15:44] <dholbach> thanks a bunch!
[15:44] <mhall119> davidcalle: refresh summit and see if you have permissions now
[15:45] <davidcalle> mhall119, works, thanks :)
[15:49] <davidcalle> mhall119, what's the overflow column of the schedule, can I put any track in there?
[15:56] <dholbach> davidcalle, the old snappy 'build apps' page is gone! :-)
[15:58] <davidcalle> hah, rick was asking about it 20min ago :D
[15:59] <jono> dpm, good to go?
[16:00] <dpm> jono, dst hiccup, we've got the community team meeting now. Are you free in 1h?
[16:00] <davidcalle> (asking for it to be removed of course ;-) )
[16:00] <mhall119> davidcalle: yeah, that's for when you can't fit a session into your track's room
[16:00] <jono> dpm, I should be, yep
[16:00] <davidcalle> mhall119, perfect, thanks
[16:01] <dpm> jono, great, ttyl then
[16:01] <jono> dpm, :-)
[16:24] <popey> Getting like 1fps in hangouts, so I may disappear soon when my gpu blows up
[16:32] <popey> dialling down to no video helps tremendously!
[16:34] <jcastro> mhall119: oic, this plugs into elasticsearch
[17:08] <jcastro> mhall119: also, today might be a good day to socialize that magical KVM command that lets me try unity8 on the desktop.
[17:08] <dholbach> all right my friends - I call it a day - see you all tomorrow!
[17:09]  * popey hugs dholbach
[17:10]  * dholbach hugs popey back :)
[17:11] <mhall119> jcastro: you mean running it in LXC?
[17:11] <jcastro> yeah
[17:12] <mhall119> I haven't tried it recently
[17:12] <jcastro> I want to try what that dude has on that youtube video
[17:12] <jcastro> And I am debating going 16.04 right now
[17:13] <mhall119> not much different in 16.04 just yet
[17:13] <mhall119> I wouldn't think anyway
[17:24] <popey> unity 8 in lxc is broken
[17:26] <jcastro> ok 16.04 it is
[17:26] <jcastro> if my computer breaks I will blame both of you
[17:27] <mhall119> acheivement unlocked: broke jcastro's computer
[17:28] <mhall119> though if LXC breaks your computer, I'll consider that payback for when juju+lxc broke mine years ago
[17:32] <dpm> mhall119, did you get my e-mail about testing meetup.c?
[17:50] <dpm> mhall119, I'll send an e-mail to all, but I'm afraid I need to skip today's call, although that shouldn't be a reason for it not to happen


[01:55] -queuebot:#ubuntu-release- New binary: moc [amd64] (mantic-proposed/universe) [1:2.6.0~svn-r3005-3.1] (no packageset)
[01:55] -queuebot:#ubuntu-release- New binary: moc [armhf] (mantic-proposed/universe) [1:2.6.0~svn-r3005-3.1] (no packageset)
[01:55] -queuebot:#ubuntu-release- New binary: moc [s390x] (mantic-proposed/universe) [1:2.6.0~svn-r3005-3.1] (no packageset)
[01:56] -queuebot:#ubuntu-release- New binary: moc [arm64] (mantic-proposed/universe) [1:2.6.0~svn-r3005-3.1] (no packageset)
[01:56] -queuebot:#ubuntu-release- New binary: moc [ppc64el] (mantic-proposed/universe) [1:2.6.0~svn-r3005-3.1] (no packageset)
[02:20] -queuebot:#ubuntu-release- New binary: moc [riscv64] (mantic-proposed/universe) [1:2.6.0~svn-r3005-3.1] (no packageset)
[02:47] -queuebot:#ubuntu-release- New: accepted moc [amd64] (mantic-proposed) [1:2.6.0~svn-r3005-3.1]
[02:47] -queuebot:#ubuntu-release- New: accepted moc [armhf] (mantic-proposed) [1:2.6.0~svn-r3005-3.1]
[02:47] -queuebot:#ubuntu-release- New: accepted moc [riscv64] (mantic-proposed) [1:2.6.0~svn-r3005-3.1]
[02:47] -queuebot:#ubuntu-release- New: accepted nvidia-tegra-defaults [amd64] (mantic-proposed) [1.1]
[02:47] -queuebot:#ubuntu-release- New: accepted moc [arm64] (mantic-proposed) [1:2.6.0~svn-r3005-3.1]
[02:47] -queuebot:#ubuntu-release- New: accepted moc [s390x] (mantic-proposed) [1:2.6.0~svn-r3005-3.1]
[02:47] -queuebot:#ubuntu-release- New: accepted moc [ppc64el] (mantic-proposed) [1:2.6.0~svn-r3005-3.1]
[02:47] -queuebot:#ubuntu-release- New: accepted rust-libheif-rs [sync] (mantic-proposed) [0.20.0-2]
[02:50] -queuebot:#ubuntu-release- New binary: rust-libheif-rs [amd64] (mantic-proposed/none) [0.20.0-2] (no packageset)
[02:51] -queuebot:#ubuntu-release- New binary: rust-libheif-rs [arm64] (mantic-proposed/none) [0.20.0-2] (no packageset)
[02:51] -queuebot:#ubuntu-release- New binary: rust-libheif-rs [s390x] (mantic-proposed/none) [0.20.0-2] (no packageset)
[02:51] -queuebot:#ubuntu-release- New binary: rust-libheif-rs [ppc64el] (mantic-proposed/none) [0.20.0-2] (no packageset)
[02:55] -queuebot:#ubuntu-release- New binary: rust-libheif-rs [armhf] (mantic-proposed/none) [0.20.0-2] (no packageset)
[03:10] <zhsj> vorlon: oh, for 1 will you schedule the rebuilds for these reverse deps?
[04:35] <vorlon> zhsj: I guess there's no reason I shouldn't
[05:05] -queuebot:#ubuntu-release- New: accepted rust-libheif-rs [amd64] (mantic-proposed) [0.20.0-2]
[05:05] -queuebot:#ubuntu-release- New: accepted rust-libheif-rs [armhf] (mantic-proposed) [0.20.0-2]
[05:05] -queuebot:#ubuntu-release- New: accepted rust-libheif-rs [s390x] (mantic-proposed) [0.20.0-2]
[05:05] -queuebot:#ubuntu-release- New: accepted rust-libheif-rs [arm64] (mantic-proposed) [0.20.0-2]
[05:05] -queuebot:#ubuntu-release- New: accepted rust-libheif-rs [ppc64el] (mantic-proposed) [0.20.0-2]
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-somerville-cinccino-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-somerville-torchic-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-aerodactyl-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-alolan-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-asobo-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-bergmite-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-cascoon-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-cascppm-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-charmander-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-nobisuke-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-sutton-aitland-meta to canonical-oem-metapackages in focal
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-somerville-cinccino-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-somerville-torchic-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-aerodactyl-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-alolan-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-asobo-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-bergmite-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-cascoon-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-cascppm-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-charmander-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-stella.cmit-nobisuke-meta to canonical-oem-metapackages in jammy
[06:17] -queuebot:#ubuntu-release- Packageset: Added oem-sutton-aitland-meta to canonical-oem-metapackages in jammy
[06:22] <LocutusOfBorg> zhsj, looks like xpra autopkgtests are sad...
[06:41] -queuebot:#ubuntu-release- New binary: texlive-bin [i386] (mantic-proposed/main) [2023.20230311.66589-6] (i386-whitelist, ubuntu-desktop)
[06:42] -queuebot:#ubuntu-release- New binary: texlive-bin [amd64] (mantic-proposed/main) [2023.20230311.66589-6] (i386-whitelist, ubuntu-desktop)
[06:46] <LocutusOfBorg> vorlon, ^^ for your joy sse2 drop
[06:55] -queuebot:#ubuntu-release- New binary: texlive-bin [armhf] (mantic-proposed/main) [2023.20230311.66589-6] (i386-whitelist, ubuntu-desktop)
[07:06] <zhsj> LocutusOfBorg: :(
[07:55] -queuebot:#ubuntu-release- New: accepted texlive-bin [amd64] (mantic-proposed) [2023.20230311.66589-6]
[07:55] -queuebot:#ubuntu-release- New: accepted texlive-bin [i386] (mantic-proposed) [2023.20230311.66589-6]
[07:55] -queuebot:#ubuntu-release- New: accepted texlive-bin [armhf] (mantic-proposed) [2023.20230311.66589-6]
[07:56] <doko> LocutusOfBorg: armhf still has sse2 binaries ...
[07:57] <doko> jbicha: rust packages removed
[08:15] <luis220413> tjaalton: Can you release the virtualbox* packages in the unapproved queue to -proposed? Bug 2017101
[08:15] -ubottu:#ubuntu-release- Bug 2017101 in virtualbox-hwe (Ubuntu Kinetic) "[SRU] virtualbox 7.0.8 and 6.1.44" [Undecided, New] https://launchpad.net/bugs/2017101
[08:15] <LocutusOfBorg> luis220413, maybe wait some more
[08:16] <tjaalton> luis220413: handling of these updates is assigned to someone else
[08:16] <luis220413> Who is today's SRU vanguard?
[08:17] <tjaalton> I'm one
[08:19] <luis220413> tjaalton: To whom are these updates assigned to?
[08:21] <tjaalton> why? :)
[08:23] <luis220413> tjaalton: You said "handling of these updates is assigned to someone else" Who is that person?
[08:23] <luis220413> *else".
[08:23] <tjaalton> so you'll ping the other person instead?
[08:25] <tjaalton> actually, this is an open item for the next sru team meeting
[08:26] <tjaalton> virtualbox sru's
[08:26] <luis220413> tjaalton: No.
[08:26] <LocutusOfBorg> please I prefer to update vbox
[08:27] <LocutusOfBorg> there is a new version
[08:27] <LocutusOfBorg> lets do it only once
[08:27] <luis220413> OK
[08:28] <tjaalton> one issue has been the rather terse impact/test case of the sru's
[08:28] <tjaalton> there doesn't seem to be a standing MRE for virtualbox?
[08:29] <tjaalton> so you should apply for one
[08:29] <tjaalton> for starters
[09:23] <zhsj> sigh, i didn't go much further with the ftbfs of inkscape/i386. so i wonder why it's on i386 list?
[09:30] <LocutusOfBorg> reverse-depends -a i386 -r mantic -b inkscape
[09:31] <LocutusOfBorg> rmadison -u ubuntu -a i386 arc-theme bacula-doc chroma daps desktop-base dnsviz drbd-doc game-data-packager king minexpert2 neurodebian oxygencursors retroarch-assets rheolef sailcut  sympy view3dscene -s mantic
[09:31] <LocutusOfBorg> shows only arch:all :/
[09:32] <LocutusOfBorg> tjaalton, for some reasons we never had an MRE
[09:34] <LocutusOfBorg> tjaalton, https://lists.ubuntu.com/archives/technical-board/2015-November/002177.html
[09:34] <LocutusOfBorg> https://lists.ubuntu.com/archives/technical-board/2015-October/002173.html
[09:34] <LocutusOfBorg> I think I already have an MRE?
[09:38] <tjaalton> noted
[09:40] <LocutusOfBorg> vorlon, I have been MRE virtualbox since before MRE were introduced, I found this technical-board ^^ ack from <pitti>. I honestly don't know what was his role 8 years ago, I went ahead and marked virtualbox on this page https://wiki.ubuntu.com/StableReleaseUpdates
[09:41] <LocutusOfBorg> I don't want to do something not following the correct process, I can redo the MRE request, if tecnhical board is not the good and right place anymore, I know stuff has changed a lot in the meantime
[09:41] <tjaalton> fix the copypaste
[09:42] <LocutusOfBorg> where?
[09:42] <tjaalton> wouldn't hurt to have a page of it's own like in the old MRE request
[09:42] <tjaalton> it mentions ubuntudevtools
[09:43] <LocutusOfBorg> should I create a new page I guess?
[09:43] <tjaalton> that'd be better than linking to a random one :)
[09:43] <LocutusOfBorg> :D
[09:50] <tjaalton> I believe the correct order would be to first create the page, then ask the SRU team to review it, and then it accepted it would be added to the list on the front page
[09:50] <tjaalton> it/if
[10:09] <LocutusOfBorg> doko, the idea of texlive-binaries-sse2 was to have in universe, I know the default accept for main is main, but can you please move it?
[10:10] <LocutusOfBorg> tjaalton, how do I ask it?
[10:10] <LocutusOfBorg> mail?
[10:11] <rbasak> LocutusOfBorg: o/
[10:11] <rbasak> Before you email...
[10:12] <rbasak> We just want be consistent, which means we'd like some documentation of how the requirements at https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases are met.
[10:12] <rbasak> Those requirements are what I believe pitti wrote when the handling of how microrelease updates work in Ubuntu were changed?
[10:13] <rbasak> We'd also like a Test Plan that gives us confidence that the proposed package is being tested properly prior to release to the updates pocket.
[10:14] <LocutusOfBorg> I understand, I think I added on the wiki the information about the test plan
[10:14] <rbasak> OK, then you can email<EMAIL_ADDRESS>[10:15] <rbasak> Please also link to the wiki page from the bug - then the entire process will be discoverable.
[10:16] <rbasak> The expectation then would be that SRU verification time, somebody would follow the Test Plan and report what was done ("I followed the Test Plan at https://..." is fine) and the versions that were tested.
[10:16] <rbasak> That way we will hopefully avoid moving the goalposts.
[10:30] <LocutusOfBorg> email sent, will update vbox later, and be on VAC for the whole next week, sorry :/
[10:48] -queuebot:#ubuntu-release- New binary: p4est [amd64] (mantic-proposed/universe) [2.3.6-1] (no packageset)
[10:48] -queuebot:#ubuntu-release- New binary: p4est [s390x] (mantic-proposed/universe) [2.3.6-1] (no packageset)
[10:49] -queuebot:#ubuntu-release- New binary: p4est [ppc64el] (mantic-proposed/universe) [2.3.6-1] (no packageset)
[10:50] -queuebot:#ubuntu-release- New binary: p4est [arm64] (mantic-proposed/universe) [2.3.6-1] (no packageset)
[11:18] -queuebot:#ubuntu-release- New binary: p4est [riscv64] (mantic-proposed/universe) [2.3.6-1] (no packageset)
[11:26] <zhsj> LocutusOfBorg: Uploading xpra_3.1.5+dfsg1-0.2_source.changes / should fix the autopkgtest.
[11:29] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (jammy-proposed) [<IP_ADDRESS>]
[11:29] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (lunar-proposed) [<IP_ADDRESS>]
[11:50] -queuebot:#ubuntu-release- New: accepted p4est [amd64] (mantic-proposed) [2.3.6-1]
[11:50] -queuebot:#ubuntu-release- New: accepted p4est [ppc64el] (mantic-proposed) [2.3.6-1]
[11:50] -queuebot:#ubuntu-release- New: accepted p4est [s390x] (mantic-proposed) [2.3.6-1]
[11:50] -queuebot:#ubuntu-release- New: accepted p4est [arm64] (mantic-proposed) [2.3.6-1]
[11:50] -queuebot:#ubuntu-release- New: accepted p4est [riscv64] (mantic-proposed) [2.3.6-1]
[11:56] <doko> texlive-binaries-sse2 demoted
[12:19] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (lunar-proposed) [1:7.2+dfsg-5ubuntu2.3]
[12:22] -queuebot:#ubuntu-release- Unapproved: rejected qemu [source] (jammy-proposed) [1:6.2+dfsg-2ubuntu6.14]
[12:24] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (jammy-proposed) [1:6.2+dfsg-2ubuntu6.14]
[12:27] -queuebot:#ubuntu-release- Unapproved: accepted bind-dyndb-ldap [source] (lunar-proposed) [11.10-4ubuntu0.1]
[12:28] -queuebot:#ubuntu-release- Unapproved: accepted bind-dyndb-ldap [source] (jammy-proposed) [11.9-5ubuntu<IP_ADDRESS>]
[12:30] -queuebot:#ubuntu-release- Unapproved: accepted edubuntu-menu [source] (lunar-proposed) [<IP_ADDRESS>]
[12:31] <LocutusOfBorg> ta
[12:34] -queuebot:#ubuntu-release- Unapproved: accepted octavia-dashboard [source] (lunar-proposed) [11.0.0-0ubuntu1.1]
[12:34] -queuebot:#ubuntu-release- Unapproved: accepted octavia-dashboard [source] (jammy-proposed) [9.0.0-0ubuntu1.2]
[12:45] <falcojr> question for vorlon and/or other SRU reviewers. Per https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2033310 we were asked to make changes to our cloud-init uploads. We uploaded those changes last Wednesday. Do we need to do anything else to move it along, or is this just the pace of SRU review?
[12:45] -ubottu:#ubuntu-release- Launchpad bug 2033310 in cloud-init (Ubuntu Lunar) "sru cloud-init (23.3 update) Focal, Jammy, and Lunar" [Undecided, Incomplete]
[12:45] -queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (jammy-proposed) [42.9-0ubuntu5]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted python-os-brick [source] (jammy-proposed) [5.2.2-0ubuntu1.3]
[12:50] -queuebot:#ubuntu-release- Unapproved: accepted python-keystonemiddleware [source] (jammy-proposed) [9.4.0-0ubuntu1.1]
[12:52] <rbasak> falcojr: you can see the queue here: https://trello.com/b/XgBxtrZ9/sru or individually by series on Launchpad eg. https://launchpad.net/ubuntu/jammy/+queue?queue_state=1. As long as it's in the Unapproved queue, the SRU team knows about it and will either get to it or leave a comment in one of the linked bugs asking for more information.
[12:52] -queuebot:#ubuntu-release- Unapproved: accepted python-keystonemiddleware [source] (focal-proposed) [9.0.0-0ubuntu1.1]
[12:56] <falcojr> rbasak: Do you have an average turn around time for how long an items stays in the queue? I'm just trying to reset expectations correctly.
[12:58] <rbasak> falcojr: I think it's difficult to say. SRUs that change features through some kind of exception, such as the usual cloud-init SRUs, certainly take longer. Each SRU reviewer usually has a day in the week that they do reviews, and sometimes things end up waiting on an opinion from the person who originally asked for something, so I'd give at least enough time to get back to that reviewer again. So a
[12:58] <rbasak> couple of weeks for trivial SRUs, and longer for complex ones like cloud-init?
[12:59] <rbasak> falcojr: right now I see about 7 uploads that are requesting feature changes in stable releases. Sometimes reviewing one of these can take one entire shift.
[13:00] <falcojr> gotcha, thanks!
[13:03] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (focal-proposed) [3:18.3.5-0ubuntu2.2]
[13:08] -queuebot:#ubuntu-release- Unapproved: rejected libreoffice [source] (lunar-proposed) [4:7.5.6-0ubuntu<IP_ADDRESS>]
[13:31] -queuebot:#ubuntu-release- Unapproved: libreoffice (lunar-proposed/main) [4:7.5.5-0ubuntu<IP_ADDRESS> => 4:7.5.6-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[13:55] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [source] (lunar-proposed) [4:7.5.6-0ubuntu<IP_ADDRESS>]
[14:35] -queuebot:#ubuntu-release- Unapproved: libreoffice (jammy-backports/main) [4:7.5.5-0ubuntu<IP_ADDRESS>~bpo22.04.1 => 4:7.5.6-0ubuntu<IP_ADDRESS>~bpo22.04.1] (ubuntu-desktop)
[17:57] -queuebot:#ubuntu-release- New binary: deal.ii [amd64] (mantic-proposed/universe) [9.5.1-1] (no packageset)
[18:13] -queuebot:#ubuntu-release- New binary: deal.ii [ppc64el] (mantic-proposed/universe) [9.5.1-1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: deal.ii [arm64] (mantic-proposed/universe) [9.5.1-1] (no packageset)
[18:58] -queuebot:#ubuntu-release- New binary: deal.ii [s390x] (mantic-proposed/universe) [9.5.1-1] (no packageset)
[19:46] <vorlon> falcojr: I'm a bit disappointed that the resolution of LP: #2034273 involves adding more code; I pointed out to blackboxsw in one of the discussions that if gpgconf isn't present, there's nothing to do because dirmngr and gpg-agent both depend on gpgconf so they can't be running if gpgconf is not present
[19:46] -ubottu:#ubuntu-release- Launchpad bug 2034273 in cloud-init (Ubuntu) "23.3: when apt keyids provided in #cloud-config, implicit dependency on gpgconf breaks Ubuntu minimal images" [Critical, Fix Released] https://launchpad.net/bugs/2034273
[19:47] <vorlon> falcojr: this is not a blocker for SRU but it's added code complexity that I think should've been avoided
[19:51] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (lunar-proposed) [23.3.1-0ubuntu1~23.04.1]
[19:52] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (jammy-proposed) [23.3-0ubuntu0~22.04.1]
[19:57] <blackboxsw> vorlon: that additional code was added by me as an interim solution, ideally, per comment as well from mwhudson, we want actually want to interact with systemd-run when running gpg  commands scoped within a cgroup and use cloud-init to clean up that cgroup after completion of gpg interations. The plan was to take this work to tip of main and the longer-term solution but not in this SRU
[19:58] <blackboxsw> as part of that changeset, this will completely drop the static processing of any gpg-agent or dirmgr spawned processes and allow systemd to clean on our behalf based on a unique cgroup.
[20:17] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (jammy-proposed) [23.3.1-0ubuntu1~22.04.1]
[20:17] <vorlon> blackboxsw: ok
[20:17] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (focal-proposed) [23.3-0ubuntu0~20.04.1]
[20:19] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (focal-proposed) [23.3.1-0ubuntu1~20.04.1]
[20:50] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (lunar-proposed) [20230808.00-0ubuntu1~23.04.0]
[21:04] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (jammy-proposed) [20230808.00-0ubuntu1~22.04.0]
[21:06] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (focal-proposed) [20230808.00-0ubuntu1~20.04.0]
[22:55] -queuebot:#ubuntu-release- Unapproved: rejected openvpn [source] (jammy-proposed) [2.5.9-0ubuntu<IP_ADDRESS>]
[23:17] -queuebot:#ubuntu-release- Unapproved: rejected libfprint [source] (jammy-proposed) [1:1.94.3+tod1-0ubuntu2~22.04.05]
[23:49] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (jammy-proposed) [23.02-0ubuntu1~22.04.1]
[23:57] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (focal-proposed) [23.02-0ubuntu1~20.04.1]