[07:41] <ochosi> JackFrost: do we have PPA for 4.16 in 20.04?
[07:41] <ochosi> oh right, it all seems to be in staging
[07:44] <JackFrost> Yep.
[07:59] <ochosi> kewl, ty
[08:10] <JackFrost> I try to be my best. ;)
[08:11] <JackFrost> ochosi: Oh hey, I pinged you elsewhere.


[07:40] <ducasse> good morning
[20:28] <duuude> how would you find out upstream backdoors?
[20:45] <ogra> by sneaking into upstreams backyard ?
[21:02] <duuude> lol


[12:13] <phillw> tsimonq2: when you arise, please check Fb - someone is saying your instructions for Qt are not working, thanks.
[13:26] <tsimonq2> phillw: I get notifications ;)
[13:46] <phillw> tsimonq2: okies :P
[13:49] <tsimonq2> phillw: I have a VM and I'm hacking on it right now
[14:40] <tsimonq2> phillw: uploading a potential fix now
[14:40] <phillw> :)
[18:02] <phillw> tsimonq2: ready to test, yet?
[20:52] <glazr> can any1 tell me how to setup initrd for squashfs and loop device?
[20:54] <krytarik> glazr: Support is in #lubuntu indeed.
[23:24] <phillw> wxl: ping
[23:33] <phillw> wxl: you have mail.
[23:54] <ianorlin> and probably some for me


[14:31] <sarnold> good morning
[14:31] <eslerm_> good morning o/
[14:33] <cpaelzer> uuuh
[14:33] <slyon> hello! o/
[14:33] <cpaelzer> late - sry
[14:34] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[14:34] <meetingology> Meeting started at 14:34:11 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[14:34] <meetingology> Available commands: action, commands, idea, info, link, nick
[14:34] <cpaelzer> Ping for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )
[14:34] <jamespage> o/
[14:34] <cpaelzer> so Oraculus Oraculous Ora... I still need to get this into my fingers
[14:34] <cpaelzer> it opened
[14:34] <cpaelzer> so we might see new things soon
[14:34] <cpaelzer> #topic current component mismatches
[14:34] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[14:34] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:34] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:35] <cpaelzer> it is https://launchpad.net/ubuntu/oracular
[14:35] <cpaelzer> ok, no syncs or uploads yet
[14:35] <cpaelzer> and noble is stable in regard to uploads
[14:35] <sarnold> is that large 'beta' banner new?
[14:35] <cpaelzer> ok, next section
[14:35] <cpaelzer> I do not remember it from past releases
[14:35] <cpaelzer> but could not guarantee that it is super new
[14:35] <sarnold> ah focal has one too :) https://launchpad.net/ubuntu/focal
[14:36] <cpaelzer> #topic New MIRs
[14:36] <cpaelzer> Mission: ensure to assign all incoming reviews for fast processing
[14:36] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir
[14:36] <sarnold> it must be the section, hehe
[14:36] <cpaelzer> I think that is for Buster not for Focal
[14:36] <cpaelzer> anyway not going into that, also suggesting trixie here
[14:36] <cpaelzer> no new open bugs
[14:36] <cpaelzer> #topic Incomplete bugs / questions
[14:37] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[14:37] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir
[14:37] <cpaelzer> only recent update is
[14:37] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054480
[14:37] -ubottu:#ubuntu-meeting- Launchpad bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, Incomplete]
[14:37] <cpaelzer> ok, sarnold got to the shallow review we wanted
[14:37] <cpaelzer> thakns
[14:38] <cpaelzer> we won't add it to Noble based on that
[14:38] <cpaelzer> but that means it is unblocked for 24.10 right?
[14:39] <sarnold> yes, or 24.04.1 ought to be fine, too
[14:39] <cpaelzer> the required TODOs are still a few non-trivial tests
[14:39] <cpaelzer> and consider adding confinement as recommended todo
[14:39] <cpaelzer> IIRC there were answers to that
[14:39] <cpaelzer> checking ...
[14:40] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054480/comments/4
[14:40] -ubottu:#ubuntu-meeting- Launchpad bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, Incomplete]
[14:40] <sarnold> confining all the things would be nice, yeah, but the primary use of nbd-client is likely during early boot with 'fixed' values .. the remote peer will be serving a filesystem, so very very powerful
[14:41] <cpaelzer> yes, the isolation is a "try to" ask
[14:41] <cpaelzer> but the testing that was mentioned has not landed yet
[14:41] <cpaelzer> I think the order from here is
[14:41] <cpaelzer> 1. land the testing that they mentions
[14:41] <cpaelzer> 2. continue trying to confine if possible
[14:41] <cpaelzer> 3. SRU at least the testing
[14:42] <cpaelzer> actually 3. promoting in 24.10
[14:42] <cpaelzer> then SRU
[14:42] <cpaelzer> and then consider promoting in 24.04.1
[14:42] <slyon> waveform: ^
[14:44] <cpaelzer> updated the case
[14:44] <cpaelzer> #topic Process/Documentation improvements
[14:44] <cpaelzer> Mission: Review pending process/documentation pull-requests or issues
[14:44] <cpaelzer> #link https://github.com/canonical/ubuntu-mir/pulls
[14:44] <cpaelzer> #link https://github.com/canonical/ubuntu-mir/issues
[14:44] <cpaelzer> nothing new
[14:45] <eslerm_> I added to my end-of-cycle comment
[14:45] <waveform> slyon, thanks -- I'll stick those on my todo list
[14:45] <cpaelzer> I see
[14:45] <eslerm_> an issue from the late cycle request of qrtr/protection-domain-mapper is causing issues
[14:45] <cpaelzer> the arm64 issues you mean?
[14:45] <eslerm_> yes
[14:45] <cpaelzer> I wasn't even aware of those late additions
[14:46] <cpaelzer> oh that is the x13s story
[14:46] <eslerm_> they were a late ask in mantic
[14:46] <sarnold> I think xn_ox bought a new laptop :)
[14:46] <cpaelzer> ok, it is a good "another example" to the problem overall
[14:46] <cpaelzer> thanks eslerm_
[14:46] <cpaelzer> The action still didn't change
[14:46] <eslerm_> the packages looked dangerous, but were ack'd exculsively for x13s hardware enablement
[14:47] <cpaelzer> Hmm
[14:47] <cpaelzer> that adds the thought of "how to ensure limited acks stay limited"
[14:47] <cpaelzer> I have no great suggestion to make yet, need to ponder about that ...
[14:47] <cpaelzer> we all might need to, let me go on with the agenda for now
[14:47] <eslerm_> +1
[14:48] <cpaelzer> #topic Any other business?
[14:48] <cpaelzer> oh and more feedback on the topic above
[14:48] <cpaelzer> you can be sure that I'll mention too huge too late changes in any 24.04 retrospective I'm in
[14:48] <cpaelzer> not sure it will change things, but it is the right thing to d
[14:48] <cpaelzer> o
[14:49] <cpaelzer> other than that - nothing MIR'ish from me or server in general
[14:49] <sarnold> are you thinking t64 or xz or boto?
[14:49] <cpaelzer> "or ..." and that is the problem
[14:49] <cpaelzer> but more t64, crisis, ...
[14:49] <cpaelzer> huge things we could have done otherwise
[14:49] <cpaelzer> not so much xz and boto which just fell onto us
[14:49] <cpaelzer> but that is opinion
[14:50] <sarnold> t64 really ought to have been done 22.10 or so
[14:50] <cpaelzer> if we could keep the things we control in -dev
[14:50] <cpaelzer> that would help
[14:50] <sarnold> many things only happen when they become a crisis .. alas i'm guilty of this myself
[14:50] <cpaelzer> yeah sarnold, exactly what you say
[14:51] <cpaelzer> anything else else?
[14:51] <sarnold> none here
[14:51] <slyon> nothing from my side
[14:51] <cpaelzer> this is the last agenda item, so next would otherwise be closing
[14:51] <sarnold> except to idly wonder what the next t64 is :)
[14:51] <eslerm_> none for me
[14:51] <cpaelzer> sarnold: that is for a talk at beer'o'clock - not for this meeting
[14:51] <cpaelzer> ok, thank you all
[14:51] <cpaelzer> closing
[14:51] <cpaelzer> #topic Any other business?
[14:51] <sarnold> ooo lucky you, already ti feierabend :)
[14:52] <sarnold> beer oclcock is a looong ways off..
[14:52] <eslerm_> o/
[14:52] <sarnold> cpaelzer: btw that wasn't the usual #endmeeting :)
[14:52] <cpaelzer> hehe
[14:52] <cpaelzer> bad copy pasta
[14:52] <sarnold> thanks cpaelzer, all :)
[14:53] <cpaelzer> #endmeeting
[14:53] <meetingology> Meeting ended at 14:53:00 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-04-30-14.34.moin.txt


[00:01] <GridCube> oh! xubutu session! is working!
[00:02] <GridCube> but i still can see anything on the ttys
[00:10] <GridCube> bug 813240
[00:11] <GridCube> okay
[00:12] <GridCube> i updated the spreadsheet
[00:12] <GridCube> now i gotta go
[00:12] <GridCube> :) good night people, see you tomorrow from work!
[00:12] <GridCube> :D
[00:13] <Unit193> I'll confirm and add
[00:18] <Unit193> charlie: You have mail
[00:31] <charlie-tca> still installing here
[00:31] <charlie-tca> Thanks
[00:31] <charlie-tca> mail?
[00:33] <Unit193> Er...  The wiki sent you an edit notification
[00:36] <charlie-tca> oh, yeah, I get a lot of those
[00:36] <charlie-tca> Thanks
[00:36] <charlie-tca> hm, I got a restart now button instead of a black screen.
[00:37] <charlie-tca> Maybe GridCube has his memory or video too low
[00:37] <charlie-tca> or trying to use yesterdays broken image
[00:39] <Unit193> I got a restart prompt. And I'm sure the email was just something you were SO happy to see :P (Re: Thanks)
[00:39] <charlie-tca> can't log in though without using "Other..."
[00:40] <charlie-tca> I always am. It just lets me see what is being changed in https://wiki.ubuntu.com/Xubuntu as soon as it happens
[00:40] <charlie-tca> Thank you for adding that bug!
[00:40] <charlie-tca> That's what makes me happy
[00:41] <charlie-tca> Now I still have to go do a few writeups for today, before it gets too late
[00:43] <Unit193> ...and I'm going to have to edit that page again with MY bug report -_-
[00:44] <Unit193> I know it's there, but I got a black screen from grub > lightdm
[00:50] <charlie-tca> Oh, man
[00:50] <charlie-tca> tried a restart? sometimes it screws up, but can not be reproduced
[01:18] <Unit193> It's all working, just as normal, Plymouth doesn't show up (Grub is fine, LightDM is fine, and it boots fine)
[01:21] <charlie-tca> Sounds good then?
[01:22] <Unit193> Yeah, I'll file the 11.04 Plymouth bug
[02:30] <charlie-tca> Okay, I am gone now. Will see you good people in the morning
[02:33] <Unit193> Forgot to say Bug 813267
[02:33] <Unit193> I couldn't think of a good name :/
[02:58] <charlie-tca> That's the best name you could give it
[02:58] <charlie-tca> It is very specific
[03:00] <Unit193> I thought you were going to sleep
[03:03] <charlie-tca> I am
[03:03] <charlie-tca> Just forgot to turn off the monitor
[06:24] <Guest89512> how do I get higher resolutions?
[06:29] <micahg> !topic | Guest89512
[06:29] <micahg> hmm, I think I meant offtopic
[06:29] <micahg> !offtopic | Guest89512
[06:30] <Guest89512> where should i bring this topic?
[06:30] <micahg> that's better :)
[06:30] <micahg> Guest89512: #xubuntu
[06:30] <Guest89512> no one is there
[06:31] <micahg> Guest89512: it's the middle of the night or early morning for most people in the channel
[06:31] <Guest89512> would you mind helping me out?
[06:32] <micahg> sorry, I'm about to go to sleep, I suggest asking your question in there and idling, someone should respond in a few hours hopefully
[06:33] <micahg> Guest89512: otherwise, there's a xubuntu-users list: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
[13:28] <charlie-tca> Good morning
[13:29] <charlie-tca> alternate images being rebuilt, waiting to see if we get any today
[13:42] <GridCube> good morning
[13:43] <GridCube> charlie-tca: about yesterday, every time i install that virtualbox using alternate i have no problems, will try to install the desktop edition whit higer video memory today
[13:45] <charlie-tca> weird, I use 512MB ram and 64MB video here
[13:48] <GridCube> i think i've reduced the video ram to 32mb :P
[13:53] <charlie-tca> astraljava: thanks for asking about alternate images.
[14:25] <astraljava> charlie-tca: I'm a sucker for those.  I always install from the alternate images for my own systems
[14:27] <astraljava> Right, yeah that works too.
[14:27] <astraljava> Well, I might be able to test tonight, but after that not for a few days, most likely until Monday.
[14:28] <astraljava> Hope that's not a problem.
[14:28] <astraljava> Off to a finnish "baseball" game, see ya later. :)
[14:28] <charlie-tca> Okay, I will keep on eye open for images, and can run both yours and ours (studio and xubuntu)
[14:30] <charlie-tca> Alternate images dated today are posted now.
[16:15] <micahg> mr_pouit: FYI, gnumeric is still pulling in evince (it uses it for print preview), I need to find out if that's just opening a PDF in the default viewer or using the evince libraries
[18:44] <J21> Looks like I forgot to put my tests in the GDoc
[18:54] <charlie-tca> It's never too late, if there is not room, just add a line
[18:55] <J21> Yeah, I ran the tests yesterday and even put that the live failed (This is Unit193's shell account)
[23:04] <GridCube> well the desktop installer doesnt like 256MB of ram
[23:05] <GridCube> it just stops there
[23:20] <GridCube> finally
[23:21] <GridCube> but  i can't seem to get a session
[23:27] <GridCube> I don' know if its relevant, but in the login  list from lightdm the user names have an uppercase on the first letter
[23:28] <GridCube> this is wrong and if i try to log in whit my user whit uppercase it just fails (like it should)
[23:33] <GridCube> after rebooting choosing my name on the list gives me xubuntu session, no "other" workarround needed
[23:33] <GridCube> i get a "System problem detected" screen
[23:34] <GridCube> woah i got a lot of "system problem detected"
[23:39] <GridCube> http://imagebin.org/164076
[23:47] <charlie-tca> looks like probable conflicts with GTK2 and GTK3 right now
[23:48] <charlie-tca> I think 256 is not enough at this point in development. Somewhere closer to beta2 will work better with 256MB
[23:48] <GridCube> i upped it to 512 already
[23:48] <charlie-tca> Make a note on the spreadsheet about those errors
[23:49] <GridCube> i did
[23:49] <charlie-tca> see if it clears up in a day or two, then file the bug
[23:49] <GridCube> ok
[23:50] <charlie-tca> I have been busy with 10.04.3 testing, so I may not get a chance to try oneiric tests again until Friday
[23:51] <GridCube> ok
[23:52] <GridCube> :) hope any of my messings arround do help somehow XD


[02:32] <jbicha> fossfreedom: could you propose bug 1670054 as a merge proposal against https://code.launchpad.net/~ubuntu-desktop/evince/ubuntu/ ?
[09:04] <fossfreedom> jbicha: k - thanks. merge proposal made
[13:07] <xryuu> Hello
[13:08] <xryuu> Can i install gnome extensions(dash to dock, todo.txt etc) on ubuntu budgie?
[13:25] <fossfreedom> xryuu: no - those will need to be recoded using budgie-desktop applet API
[13:25] <xryuu> Damn. Any extensions tho for budgie?
[13:27] <xryuu> fossfreedom
[13:28] <fossfreedom> I'm aware of a native applet for taking screenshots and I think there is a weather applet lurking somewhere.  Which distro are you using?
[13:29] <xryuu> Im not using linux atm but im looking forward to
[13:29] <xryuu> Thinking of ubuntu budgie
[13:30] <fossfreedom> ah - in that case, ubuntu budgie has an applet that displays appindicators - so all ubuntu appindicators can be used with budgie
[13:30] <xryuu> Would love to use dash to dock and a couple of others tho
[13:32] <fossfreedom> dash to dock would be pointless under budgie-desktop - the native icon tasklist applet performs the same thing.
[13:32] <fossfreedom> you can also run docky or raven which if you want a separate app launcher
[13:33] <fossfreedom> raven ... typo sorry I meant plank
[13:33] <xryuu> Oh ok will look into it
[13:33] <xryuu> Thank you!
[13:34] <fossfreedom> yw
[21:06] <jbicha> fossfreedom: https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22&id=31832f86
[21:07] <jbicha> that commit (revert) is being pushed to sid now and will be in the next zesty upload whenever that is
[21:15] <jbicha> the individual who responded on https://bugs.debian.org/856603 is not on the release team so his opinion isn't final
[21:43] <fossfreedom> jbicha: scratching my head on this.  Its a theme - the best people to validate a theme is the theme maintainer.  Not sure why people are second guessing the reasons my theme maintainers do stuff.  Whatever.
[21:44] <fossfreedom> s/my/why
[21:51] <fossfreedom> jbicha: imho - this will just confuse theme maintainers - they would be expecting to support all distros - now debian ... and ubuntu do stuff one way and other distro do stuff in a different way.  crazy
[21:51] <jbicha> I think better Cinnamon 3.2 compatibility is a decent justification for getting the update into stretch before release
[21:52] <jbicha> Debian historically is very strict about stable updates
[21:54] <jbicha> https://release.debian.org/stretch/freeze_policy.html
[21:55] <jbicha> if you want it in stretch I think you'll need a RC bug to go along with it
[21:55] <jbicha> otherwise, it can still be uploaded to sid; but if not unblocked it just won't migrate to stretch
[21:57] <jbicha> if you want to discuss more about unblocking, you can ping pochu (who is Release Team) in say, #debian-gnome
[21:57] <jbicha> but I'd wait until it got into sid before worrying about unblocking
[21:57] <fossfreedom> jbicha: is debian going with the breaking 2.23.9 series or staying with 2.23.8 ?  I dont see any consensus.  If they stay behind there isnt any issues.
[21:59] <fossfreedom> 3.22.8 vs 3.22.9
[22:18] <jbicha> 3.22.9 but that breaking change has been reverted in both gtk upstream and Debian
[22:19] <jbicha> https://lists.debian.org/debian-devel-changes/2017/03/msg00274.html
[22:19] <jbicha> like I said, the guy who commented isn't a Release Team member
[22:20] <jbicha> I'm not sure I understand your comment about theme maintainers
[22:20] <jbicha> everyone knows that Debian stable is very stable (does not really change much)
[22:22] <fossfreedom> don't worry - I've got two people talking to me at the same time at the same time as you! They've gone now.  multitasking on a sunday.
[22:22] <fossfreedom> k - I'll let the arc maintainer know about the reversion. cheers


[00:52] <wgrant> Any reviewers still around for a trivial API export?
[00:53] <wgrant> https://code.edge.launchpad.net/~wgrant/launchpad/export-das-chroot/+merge/19759


[08:23] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4602 Proposed pocket (impish/linux-unstable, impish/suricata). Successfully built (impish/linux-raspi-unstable, impish/snapd, impish/systemd)
[16:14] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4498 Abandoning ticket
[16:16] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4315 Generating diffs
[16:16] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4530 Generating diffs
[16:50] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4530 Pending binary packages
[16:56] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4315 Failed to build
[17:11] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4530 Successfully built
[18:32] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4633 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[18:53] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4633 Pending binary packages
[19:13] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4633 Diff missing
[20:33] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4633 Diff missing (impish/debhelper). Pending binary packages (impish/virtualbox)
[21:13] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4633 Diff missing
[21:37] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4633 Abandoning ticket
[21:55] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4634 Ready to build


[19:44] <qwebirc89778> Hi, new user here named ROB, new to ubuntu and ubuntu studio. trying to setup audio recording for 2 microphones and skype
[19:46] <OvenWerks> qwebirc89778: go ahead, what kind of mics, what interface, what have you tried?
[19:47] <qwebirc89778> I have two ATR 2100 USB mics which are detected. I'm using ardour 5 but am unable to seperate audio sources to different tracks. I think my main problem is setting up JACK
[19:48] <OvenWerks> How are you setting up jack?
[19:49] <OvenWerks> Are you using a GUI based application or commandline?
[19:49] <qwebirc89778> GUI based. And currently can't even find jack in my programs
[19:50] <OvenWerks> Jackd/jackdbus do not on their own have a GUI
[19:50] <Eickmeyer[m]> qwebirc89778: What version of Ubuntu Studio?
[19:50] <qwebirc89778> I want to say it was Jack Server
[19:50] <qwebirc89778> had patches in it and everything
[19:51] <OvenWerks> jackd can be started on command line with jack_control or jackd. The GUI start up applications are ubuntustudio-control or qjackctl
[19:51] <OvenWerks> for using two USB mics, ubuntustudio-controls is probably the best thing to use.
[19:51] <Eickmeyer[m]> Important to know which version, though.
[19:52] <OvenWerks> yes
[19:52] <OvenWerks> (-controls needs an about box or version listed somewhere else in the GUI)
[19:53] <qwebirc89778> I just installed it from software so I suppose it's the latest version
[19:53] <Eickmeyer[m]> Or, really, the installed Ubuntu Studio version is a key (from the comand line: lsb_release -a)
[19:53] <OvenWerks> which flavour and version of ubuntu are you using.
[19:53] <Eickmeyer[m]> qwebirc89778: It might not be, which is why I'm asking what version of Ubuntu Studio.
[19:53] <Eickmeyer[m]> !yy.mm
[19:55] <qwebirc89778> i don't know which version. right now it's not letting me scroll through applications to get to command line
[19:55] <qwebirc89778> installed in the last 2 weeks though
[19:56] <Eickmeyer[m]> You still could have installed 18.04, 18.10, or 19.04. It all depends on what you downloaded, not when.
[19:56] <qwebirc89778> 18.04.2
[19:56] <Eickmeyer[m]> Okay. Now we're getting somewhere.
[19:57] <Eickmeyer[m]> !ubuntustudio-backports | qwebirc89778: did you enable this?
[19:57] <OvenWerks> -controls will be old.
[19:57] <qwebirc89778> Don't know if backports are enabled
[19:57] <Eickmeyer[m]> It isn't by default. It's something you would have to intentionally do.
[19:58] <Eickmeyer[m]> Follow that guide I just linked. You'll need the backports.
[20:01] <qwebirc89778> ok followed that guide.
[20:02] <Eickmeyer[m]> !ubuntustudio-controls | qwebirc89778: This is the next thing you'll need:
[20:06] <qwebirc89778> ok thank you. reading through that now. Is there specific guidance in here about recording skype?
[20:07] <OvenWerks> there is more than one choice...
[20:07] <Eickmeyer[m]> qwebirc89778: video or just audio?
[20:08] <OvenWerks>  but with two usb mics you will need to make them both available as one device not two.
[20:08] <qwebirc89778> just audio. I'm in ardour 5 and trying to see my microphones and skype as sources
[20:08] <Eickmeyer[m]> Okay. The only thing that Skype is going to see is whatever is sent to PulseIn.
[20:08] <OvenWerks> skype is pulse only. so the bridge between jack and pulse is your friend.
[20:09] <Eickmeyer[m]> I'd use Patchage or install Carla to do the connections.
[20:10] <OvenWerks> you will need some sort of application to mix your mics into one channel to send to skype so the other person can hear as well as record. I would almost say that idjc might be the best thing for this.
[20:10] <OvenWerks> (AKA "Interbet DJ Console"
[20:10] <OvenWerks> *internet
[20:11] <OvenWerks> it has mic inputs and a phone input (all jack)
[20:11] <OvenWerks> it is able to record and/or stream to the internet
[20:11] <Eickmeyer[m]> I'd use Ardour as if it were an actual mixer, but that's how my audio engineer brian works.
[20:12] <OvenWerks> Eickmeyer[m]: have you ever tried IDJC?
[20:12] <qwebirc89778> just fired IDJC up now
[20:12] <OvenWerks> IDJC is quite common for radio station use in the studio.
[20:13] <Eickmeyer[m]> ¯\_(ツ)_/¯ @freenode_OvenWerks:matrix.org: I have not, but that's just because I'm so used to Ardour.
[20:14] <OvenWerks> :)
[20:14] <OvenWerks> rivendale comes packed with idjc for controlroom I think.
[20:19] <qwebirc89778> anyone know how to get skype to recognize pulse as a microphone input?
[20:19]  * OvenWerks worked in the standard analog radio statio of yore. Mcurdy, mixer and turn tables with cart machines.
[20:20] <OvenWerks> with just pulse or with the jack-pulse bridge?
[20:21] <qwebirc89778> really a novice here. either way really
[20:21] <OvenWerks> skype uses pulse by default
[20:21] <OvenWerks> I am not suggesting one way or the other so much as finding what you are trying
[20:22] <OvenWerks> I have to know what you are trying before I can A) make it work that way or B) suggest an alternative
[20:22] <qwebirc89778> my knowledge is limited to copy and paste into the terminal. My goal is to be able to record audio for a podcast interview happening over skype in 3 hours time. :-/
[20:23] <qwebirc89778> I'm used to Windows and GUI's having previously used Bananameter
[20:23] <OvenWerks> I hope we can do quicker than that :) I have to leave sooner.
[20:23] <qwebirc89778> lol
[20:24] <qwebirc89778> right now i'm playing with IDJ and have it recognizing both microphones on the Meter but I've yet to hear any audio from the mics
[20:24] <OvenWerks> so why did you switch? (never mind)
[20:24] <OvenWerks> ok, good start.
[20:24] <OvenWerks> if you open patchage
[20:24] <OvenWerks> you should see idjc and pulse
[20:25] <qwebirc89778> idjc is shaking like crazy
[20:26] <OvenWerks> thats not nice, solid here
[20:27] <qwebirc89778> ok got it to stop shaking
[20:27] <OvenWerks> anyway, the normal thing is to connect idjc "voip_out_l and _r to PulseIn left and right
[20:28] <OvenWerks> and connect PulseOut to voip_in_l and _r
[20:30] <qwebirc89778> is it weird to have 2 pulse ins and no pulse outs?
[20:30] <OvenWerks> very.
[20:30] <OvenWerks> but not if your mic is the only audio device
[20:31] <qwebirc89778> yeah mics have headphone jacks in them. no other external speakers.
[20:32] <OvenWerks> that is still an output and should show up in jack and pulse should be there too. It could be that the pulseout is off of patchage's screen
[20:33] <qwebirc89778> trying a rearrange
[20:33] <qwebirc89778> found pulse out and pulse in
[20:33] <OvenWerks> you can use the name tag in patchage to grab and move a device around.
[20:35] <qwebirc89778> I have two of each pulse out/in, connect both to the voips?
[20:37] <qwebirc89778> and should I disconnect System from PulseIn to prevent feedback/echo?
[20:37] <OvenWerks> you may need to do that yes.
[20:39] <qwebirc89778> ok system playback has 8 tracks
[20:39] <qwebirc89778> tracks 1 and 2 are getting PulseOut, DJ Out, and Alarm out
[20:39] <qwebirc89778> by tracks i mean "playback"
[20:40] <OvenWerks> once you have pulse going through idjc, you probably don't want pulse to go through systemplayback.
[20:41] <OvenWerks> you are using pulse for your "phone" only in this case
[20:41] <OvenWerks> you would not be able to play audio from a web page at this point.
[20:42] <qwebirc89778> no audio from webpage, that's fine
[20:42] <OvenWerks> (controls does not yet have a way to set up more than one bridge at a time... add that to the list...)
[20:43] <OvenWerks> so does you mic show up as 8 outputs? or is that your internal device?
[20:44] <qwebirc89778> mic is 2. i have monitored audio by connecting DJ_out to Mic Playback
[20:45] <qwebirc89778> System has the 8 playbacks
[20:45] <OvenWerks> ok that works.
[20:46] <OvenWerks> The one problem I can see is that your second usb mic may try to be the same device name
[20:46] <qwebirc89778> ok Skype is playing test audio but i'm not hearing it nor seeing it on the meter
[20:46] <qwebirc89778> skype is set to default in skype settings
[20:47] <OvenWerks> Ya, the thing to try in idjc is to click on the green phone icon.
[20:47] <qwebirc89778> oooo
[20:47] <qwebirc89778> testing
[20:48] <qwebirc89778> ok did'nt record me in skype
[20:48] <OvenWerks> did you have the "DJ" button pressed?
[20:49] <qwebirc89778> i did before. it's greyed out now
[20:49] <OvenWerks> (the two verticle bars should be red)
[20:49] <qwebirc89778> they are red
[20:49] <qwebirc89778> aux was also red
[20:54] <OvenWerks> I am having difficulty too hang on.
[20:57] <OvenWerks> ok now I have it.
[20:57] <OvenWerks> not sure what I did though...
[20:57] <OvenWerks> The meters on the right ch1 should be showing level when you speak in the mic
[20:58] <qwebirc89778> i have mics assigned to channel 1 and 3
[20:58] <OvenWerks> right
[20:58] <qwebirc89778> and i have montioring so I'm hearing them
[20:58] <OvenWerks> with the DJ red you should be able to hear what you say in the output.
[20:59] <qwebirc89778> yes dj is allowing me to hear channel 1. not affecting channel 3
[20:59] <qwebirc89778> aux is doing channel 3 though
[21:00] <OvenWerks> at the top of the screen in the manu bar there is a little speaker where you would turn volume up and down.
[21:00] <OvenWerks> if you click on that and select sound settings
[21:01] <OvenWerks> Input devices... you should see a volume level (which should be at about 100%) and a bar below that.
[21:01] <OvenWerks> you mic level should show up there
[21:01] <qwebirc89778> yup, not showing activity
[21:02] <OvenWerks> And you have voip_out connected to pulsein?
[21:03] <qwebirc89778> yes i have voip_out to pulse_in
[21:03] <OvenWerks> And the green phone pressed?
[21:03] <OvenWerks> (a green phone should appear in the middle of the screen)
[21:04] <qwebirc89778> yes it's pressed and green phone visible
[21:06] <OvenWerks> Hu, I just have one voip_out plugged into pulsein and it seems to work here
[21:07] <qwebirc89778> any idea why i have two pulse-ins?
[21:07] <OvenWerks> Should be just a left and a right
[21:08] <OvenWerks> (front-left and front-right)
[21:08] <qwebirc89778> i have left and right on both PulseIn and PulseIn-01
[21:08] <qwebirc89778> same with out
[21:09] <OvenWerks> in the Volume Control app, do you also have a drop down where it says Jacksource?
[21:09] <qwebirc89778> it's a window and neither shows activity
[21:10] <OvenWerks> There should not be two bridges.
[21:10] <OvenWerks> That alomst sounds like an older controls application
[21:10] <qwebirc89778> let's blow up some bridges
[21:10] <OvenWerks> (there was such a bug)
[21:12] <OvenWerks> If you enabled the backports ppa and reinstalled ubuntustudio-controls that bug should be gone.
[21:13] <OvenWerks> in a terminal type px x |grep autojack
[21:13] <OvenWerks> you should only get two lines not three
[21:13] <OvenWerks> sorry not px
[21:14] <OvenWerks> ps x |grep autojack
[21:15] <qwebirc89778> rob@openair:~$ ps x |grep autojack 14747 pts/0    S+     0:00 grep --color=auto autojack 19878 tty1     Sl+    0:00 /usr/bin/python3 -u /usr/bin/autojack 19923 tty1     Sl+    0:00 /usr/bin/python3 -u /usr/bin/autojack
[21:16] <qwebirc89778> still both there. restart?
[21:16] <OvenWerks> kill one of them
[21:17] <OvenWerks> at the far left there should be a number. kill <number>
[21:17] <OvenWerks> kill 19923 for example
[21:18] <qwebirc89778> not sure how to do that
[21:19] <OvenWerks> in a terminal type kill 19923
[21:20] <qwebirc89778> still there
[21:21] <OvenWerks> maybe try kill -9 19923
[21:21] <qwebirc89778> no such process
[21:21] <OvenWerks> you may then have to restart jack (and and the other apps)
[21:22] <OvenWerks> ok so it is not really there
[21:22] <OvenWerks> did patchage show some of the things are gone or are they all still there?
[21:24] <qwebirc89778> restarted all apps and Jack, pulseIn-01 is gone
[21:24] <qwebirc89778> still no activity in settings
[21:25] <qwebirc89778> skype not receiving minc
[21:25] <OvenWerks> if you connect directly from your mic capture to pulse in does that work?
[21:27] <qwebirc89778> the settings showed activity, skype didn't register
[21:27] <OvenWerks> does skype show up in the recording tab?
[21:29] <qwebirc89778> applications tab yes
[21:29] <OvenWerks> So you have activity in inputs? but not in recording?
[21:30] <qwebirc89778> yes
[21:31] <OvenWerks> in recording there should be a box that is grey that says Jakc source
[21:31] <OvenWerks> (right after the words "input from"
[21:32] <OvenWerks> clicking on it gives a drop down where jack source should be available
[21:34] <OvenWerks> There is also a speaker with x beside it. make sure that is not muted
[21:35] <qwebirc89778> i don't see a recording tab.
[21:35] <qwebirc89778> i see the applications tab in the sound settings
[21:36] <OvenWerks> This is the one that says "Volume Control" at the top?
[21:37] <qwebirc89778> Settings     Sound
[21:37] <OvenWerks> It should have Playback, Recording, Output Devices, Input Devices and Configuration tabs across the top.
[21:37] <qwebirc89778> That sounds like Windows to me
[21:37] <OvenWerks> I am sure it trys to mimic that yes.
[21:38] <OvenWerks> in a terminal type pacvucontrol
[21:38] <OvenWerks> Ac!
[21:38] <OvenWerks> pavucontrol
[21:38] <OvenWerks> I can;t spell all the time
[21:41] <OvenWerks> Eickmeyer[m]: I don't know if you can help here, but I need to pick up "The Lovely Laura" (my wife) from work.
[21:41] <OvenWerks> Back later
[21:41] <Eickmeyer> OvenWerks: o/
[21:41] <qwebirc89778> thank you for your help
[21:42] <qwebirc89778> i've now installed pavucontrol
[21:42] <Eickmeyer> I'll be honest, I haven't been following along.
[21:43] <qwebirc89778> that's cool. Trying to setup patch so I can record a podcast interview in an hour and a half using either ardour 5 or InternetDJ. skype is not hearing the microphone inputs going through PulseIn
[21:43] <Eickmeyer> Yeah, I think I gathered that, but thanks for the summary.
[21:44] <Eickmeyer> Did OvenWerks have you use alsamixer on the command line?
[21:44] <qwebirc89778> no
[21:45] <qwebirc89778> oh and i'm quite the noob at Linux, though I understand command line, i know not actual commands
[21:45] <Eickmeyer> Oh, it's an easy one. It's not an actual command, but opens a graphical/text interface (much like the DOS days of old).
[21:46] <Eickmeyer> My speculation is that the volume on your microphones in ALSA is all the way down.
[21:46] <Eickmeyer> So, open a terminal and type "alsamixer".
[21:47] <Eickmeyer> Then press F6 and select one of the microphones, then F4 for capture.
[21:47] <Eickmeyer> These are USB microphones, correct?
[21:47]  * Eickmeyer missed that part
[21:48] <qwebirc89778> yup usb
[21:49] <Eickmeyer> Okay, then try alsamixer and see if you can see the microphones in there.
[21:50] <Eickmeyer> Then make sure that "capture" for each one is up to at least 50%-ish (hard to tell sometimes based on the device).
[21:50] <qwebirc89778> i see them, i've raised volumes to 100
[21:50] <Eickmeyer> Okay. They're patched in Patchage to PulseIn, correct?
[21:51] <qwebirc89778> capture is at 100,
[21:51] <qwebirc89778> does it matter that it's that high?
[21:51] <Eickmeyer> Well, let's give it a try. Keep alsamixer open, you can always lower it if you get distortion.
[21:52] <Eickmeyer> They're patched in Patchage to PulseIn?
[21:53] <qwebirc89778> they were not they were set to channels for internetdj but restarting everything erased all of that for some reason
[21:53] <qwebirc89778> voip in and voip out were sending to pulse
[21:55]  * Eickmeyer is now wishing he had more experience with Internet DJ.
[21:58] <qwebirc89778> how about ardour 5?
[22:00] <Eickmeyer> Well, I just gave myself a crash course. Skype is looking at "Jack source (PulseIn)", correct?
[22:01] <qwebirc89778> yes
[22:01] <Eickmeyer> Here's how I have it patched (looks slightly different than Patchage, it's a program called Carla): https://imgur.com/87xVG8q.png
[22:02] <qwebirc89778> pulsein is the sound settings is registering the microphone activity
[22:03] <Eickmeyer> But Skype isn't? (I can't see any sound indications in Skype either, but I think that's a poor design).
[22:03] <qwebirc89778> oh you have voipout going to system
[22:05] <Eickmeyer> Yeah, I changed that though.
[22:05] <Eickmeyer> Hang on...
[22:06] <Eickmeyer> https://imgur.com/dLQpspW.png
[22:06] <qwebirc89778> skype is frozen and won't hang up the test call. what's the kill command?
[22:07] <Eickmeyer> I'd open a terminal and try "killall skype".
[22:07] <Eickmeyer> I just tested with my configuration (built-in laptop mic, built-in laptop speakers) and it seemed to work.
[22:08] <qwebirc89778> the way you have that setup though, i worry that DJ out will send the Skype callers audio back to them in a wicked echo
[22:09] <Eickmeyer> Yeah, mine was quick and dirty That latest imgur image is what I did.
[22:09] <qwebirc89778> just restarted skype, it's currently not seeing any speakers or microphones
[22:09] <qwebirc89778> i think i need to restart the system at this point
[22:10] <Eickmeyer> Eep. Yeah, something is definitely wrong if it can't see PulseIn/Out. (really, all it needs to see)
[22:16] <qwebirc62715> Rob is back on with Ardour/InternetDJ/Skype questions
[22:17] <Eickmeyer> Hey Rob!
[22:17] <qwebirc62715> Hello!
[22:17] <Eickmeyer> I'm working on a way to do it in Ardour.
[22:17] <Eickmeyer> Really, that's how I would do it, but that's because I'm an audio engineer and think like a mixer.
[22:18] <qwebirc62715> i want to do it in Ardour 5
[22:20] <Eickmeyer> Okay. Here's how I set it up: https://imgur.com/t8Lw0qM.png
[22:21] <Eickmeyer> I added two mono audio tracks, one for each microphone. Then I added a stereo track for Pulse. Then I added a bus to act as a send to send the microphones to Pulse, giving them each an internal aux send to that bus.
[22:22] <qwebirc62715> ok, adding a bus is not something I'm familiar with :-(
[22:22] <Eickmeyer> Patched it like this.
[22:22] <Eickmeyer> https://imgur.com/12Vm5xu.png
[22:22] <Eickmeyer> Adding a bus is just like adding a track, but selecting "Audio bus" on the left instead of track.
[22:25] <qwebirc62715> Audio 1 output - Ardour Bus -Land R
[22:26] <Eickmeyer> https://imgur.com/sFH2lqx.png
[22:29] <Eickmeyer> I sent Mic 1 and 2 to Main with each having an aux send to "Pulse Send" and then Pulse Send routed to PulseIN.
[22:29] <Eickmeyer> PulseOUT routed to Pulse RTN, which is then routed to Main.
[22:29] <Eickmeyer> In this configuration, the people on Skype won't be able to hear themselves, but you'd be able to hear the mics and Skype.
[22:31] <qwebirc62715> ok trying to set this up...
[22:35] <qwebirc62715> skype is sending audio back to ardour. I'm not hearing it though
[22:36] <qwebirc62715> i'm not hearing it i believe becuase i have nothing going to microphone out (headphones
[22:38] <qwebirc62715> test call to skype failed on hearing my own voice
[22:39] <Eickmeyer> That's possible, but I'm concerned that the headphone jack on those mics is for listening to just the microphone.
[22:39] <Eickmeyer> Meaning, it's not for computer audio.
[22:40] <Eickmeyer> Reason is because I've seen those advertised on Amazon.
[22:40] <qwebirc62715> worked for the last year on a windows system
[22:40] <Eickmeyer> Oh, then I'm wrong.
[22:41] <Eickmeyer> Strange, and you have the main outs routed back to the microphone headphone outs?
[22:41] <Eickmeyer> main from Ardour, that is.
[22:42] <qwebirc62715> yeah, just checked youtube. I can hear audio through the headphones, skype isn't picking up the audio from my mic
[22:43] <qwebirc62715> sound settings are no longer showing input from Jack PulseIn
[22:43] <qwebirc62715> maybe ihave the bis setup wrong
[22:43] <Eickmeyer> Something is wrong with Skype then. Try closing Skype and reopening.
[22:43] <qwebirc62715> bus
[22:44] <Eickmeyer> Well, if the sound settings aren't showing input from PulseIn, then there's a problem.
[22:44] <Eickmeyer> Does Patchage see the PulseIn/PulseOut?
[22:45] <qwebirc62715> i think i fixed the bus
[22:45] <qwebirc62715> yes it sees that
[22:45] <Eickmeyer> Okay, then you're good.
[22:45] <Eickmeyer> Probably needed to patch the bus to PulseIn.
[22:45] <qwebirc62715> WE'VE DONE IT!!!
[22:45] <Eickmeyer> \o/
[22:45] <Eickmeyer> OvenWerks: ^
[22:45] <qwebirc62715> Needed to send to the buss
[22:46] <Eickmeyer> Ah, yes. The aux send.
[22:46] <qwebirc62715> ok how do I put a noise gate on these tracks?
[22:47] <Eickmeyer> Right-click in the black area in the track (Mixer view), click New Plugin > Plugin Manager. Search for "Gate" and you should have a few to choose from.
[22:47] <Eickmeyer> Also, you can drag the plugins into whatever order you need them on your channel strip.
[22:49] <qwebirc62715> ok thank you
[22:49] <Eickmeyer> You're quite welcome. Glad we got this working.
[22:49] <qwebirc62715> Checkout SpreadAviation.com to see where this work is going
[22:49] <Eickmeyer> Enjoy your... podcast, was it?
[22:49] <Eickmeyer> SpreadAviation!!!!
[22:49]  * Eickmeyer is a former pilot
[22:49] <Eickmeyer> <3 <3 <3
[22:51] <qwebirc62715> Pilot for life
[22:51] <Eickmeyer> Seriously. I'm medically disqualified now, but man, I miss it.
[22:51] <qwebirc62715> No such thing as former, just not current
[22:51] <qwebirc62715> and you can always go up with a flight instructor
[22:52] <Eickmeyer> That's true. Now if I had the money.... ;)
[22:52] <qwebirc62715> I understand that!
[22:52] <Eickmeyer> Ha! Feel free to drop in anytime or on #ubuntustudio-offtopic.
[22:52]  * Eickmeyer is the Ubuntu Studio Flavor Lead
[22:53] <qwebirc62715> Excellent and tahnk you for your help
[22:55] <Eickmeyer> You're quite welcome. :)
[23:10] <OvenWerks> good, glad it was figured out.
[23:10]  * OvenWerks closes all the extra windows on his desktop...
[23:10] <Eickmeyer> Haha! Did the same.
[23:12] <Eickmeyer> Just kinda cool to have helped one of biggest aviation podcasts on the planet. XD
[23:13]  * Eickmeyer is off to get "The Jumping Jonny" (my son) from school
[23:13] <OvenWerks> o/


[12:31] <tjaalton> I'm debugging a weird swap issue on my main desktop, where the swap is fully allocated not long after a fresh reboot though smem shows it's not the apps using it
[12:31] <tjaalton> so I wonder if btrfs is to blame, I have a four disk raid on it
[12:32] <tjaalton> swapoff takes an eternity, making shutdown really slow
[12:32] <tjaalton> running vivid
[12:32] <tjaalton> but it was the same on trusty too
[12:33] <tjaalton> the box has 16GB of ram, and usually ~10G is for cache
[12:33] <tjaalton> so there's plenty of ram to use
[12:34] <tjaalton> swap is only 4G, running swapoff now and it's halfway done and cache amount has not changed
[12:41] <tjaalton> um, actually it increased, free ram is constantly around ~160M
[12:41] <tjaalton> guess I'm better off without swap, disabled it for now..
[14:18] <nemo> So... Nexia, someone who plays the game I help dev (Hedgewars) has a card that is an rt5390
[14:18] <nemo> When he reluctantly reboots to ubuntu from Windows, he gets disconnected all the time
[14:18] <nemo> I found several bugs and forum threads from 2013 indicating a patch exists that fixes the 64 bit support in the driver...
[14:18] <nemo> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173759/comments/14  for example
[14:18] <nemo> (that link is corrupted btw)
[14:19] <nemo> the patch link is good though, so I'm hoping it works on ubuntu's version of the driver
[14:19] <nemo> so... I was wondering. since he clearly has a semi-functional card now in 2013, did this patch never make it upstream?
[14:19] <nemo> or is it only an incomplete fix?
[14:20] <nemo> BTW, all the bugs I could find in launchpad were closed for various reasons like "inactivity" or "the laptop you happened to report this against was recalled (even though the card is common enough)"
[14:34] <nemo> er. s/now in 2013/now in 2015/
[15:06] <Aram> Hi:
[15:06] <Aram> dpkg-deb: building package `linux-image-3.19.0-rc6-uprobes-dbg' in `../linux-image-3.19.0-rc6-uprobes-dbg_3.19.0-rc6-uprobes-1_arm64.deb'.
[15:06] <Aram> It's been 40 minutes now and it's not finished. There doesn't seem to be any file I/O on the generated file. Is it stuck? What to do?
[15:06] <Aram> Thanks.
[15:08] <Aram> dpkg-deb uses 100% CPU.
[15:09] <Aram> straceing it looks liek it's doing lots of 4k reads and writes
[15:09] <Aram> oh, it either finished or my attempts to debug it killed it
[15:10] <Aram> it generated a 330MB file
[15:11] <data> hi, did something in the build process change between 3.16.0-28 and -29? My servers do not boot with -29 due to not being able to mount the rootfs, and the busybox rescue does not have the necessary drivers to support iDRAC or a USB keyboard
[15:36] <Aram> ok, so my arm64 machine does not boto with this kernel
[15:36] <Aram> boot
[15:36] <Aram> http://sprunge.us/OfFV
[15:36] <Aram> I don't see any output from the kernel
[22:18] <apw> data, not knowingly
[22:19] <apw> nemo, if someone can test, then you should (sadly) file a new bug with "ubuntu-bug linux" and add the info on the patch to that, and we can get someone to build a test kernel for it.  do paste the new bug number here.
[22:19] <apw> Aram, no idea what that kernel source is, nor whether i would expect it to boot ubuntu
[22:21] <Aram> it's an experimental patch that implemented uprobes on arm64, but that is not very relevant as I tried with vanilla kernel too, and that doesn't boot either on this machine.
[22:22] <Aram> and that boot log is complete, there is no kernel output at all.
[22:22] <Aram> I also tried earlycon= options


[12:24] <Raito_Bezarius> Hello, I'm trying to understand if cloud-init supports update_etc_hosts for NixOS
[12:40] <Raito_Bezarius> https://github.com/canonical/cloud-init/pull/561 I have made this
[14:31] <Odd_Bloke> Hello everyone, I'm back from my two weeks of vacation. o/
[14:33] <Odd_Bloke> I'm catching up on scrollback and as we're introducing more and more development tools into cloud-init, I wonder if we should consider splitting the Ubuntu package into two: one for the actual "init" functionality, and one that people can install on dev machines (to get schema validation, MIME archive creation, etc.) without cloud-init (potentially) running on boot.
[14:34] <Odd_Bloke> (Potentially this could be implemented by just moving the systemd units to a separate package; we probably don't want to try splitting the source tree in packaging.)
[16:05] <smoser> i have 2 thoughts.
[16:05] <smoser> a.) with the generator, if you don't want cloud-init to run, touch /etc/cloud/cloud-init.disabled
[16:06] <smoser> b.) right the only tool i think that is in cloud-init that isn't really to be run on a system that *does* use cloud-init  during boot is 'make-mime'
[16:07] <rharper> maybe net-convert
[16:07] <smoser> maybe... that is a dev tool though.
[16:08] <smoser> the obviousl thing that i'd think to add would be the `cloud-localds` functionality from cloud-utils
[16:08] <rharper> yeah, the schema stuff is in the middle ground as well
[16:08] <smoser> but doing *that* would mean dependencies
[16:08] <smoser> which i wouldn't want a package to pick up (mkiso)
[16:08] <rharper> smoser: right
[16:09] <smoser> i can see the value of schema on non-running system for sure.
[16:11] <Odd_Bloke> The `analyze` subcommands can take an input file, so they could also be used on a non-running system.
[16:27] <smoser> but the
[16:28] <smoser> s/but the//
[16:40] <Odd_Bloke> I think we can categorise our commands as: functional (init etc.), on-instance utilities (collect-logs, query, clean, etc.), power-user development (at least schema, make-mime, perhaps analyse and others; localds would fit here, I think), developer (net-convert, render? (I don't know what render does))
[16:42] <Odd_Bloke> As I said, I don't think splitting up our code tree in packaging is worthwhile, but we could feasibly have (names not intended as suggestions for actual package names): cloud-init-library, cloud-init-systemd-services, and then cloud-init-power-users-install-me which would depend on cloud-init-library and packages which are only required for {power-user,developer} subcommands.
[16:43] <Odd_Bloke> Which would give us a way of installing mkiso on systems where people are opting into having the full functionality available, without bloating the dependency set of the packages that get installed on every system (-library and -systemd-services).
[16:55] <rharper> Odd_Bloke: render lets users expand/test jinja templated files
[17:18] <smoser> Odd_Bloke:the issue is that if you dn't split up the code tree, then cloud-init-library has to have the mkiso dependency
[17:18] <smoser> or its just broken, waiting for someone to try to use the library and fail
[17:41] <Odd_Bloke> I think it would be reasonable to exit with "`cloud-init localds` requires `mkisofs` to be installed" or similar; it's an interactive command so people can respond to that.
[17:41] <Odd_Bloke> But I agree that it's not ideal.
[18:15] <ananke> hmm, this makes no sense, but so far all the symptoms agree: 'cloud-init status --wait' claims that 'status: done', but tail'ing cloud-init-output.log still shows final modules still running (package installs/updates specifically). was there ever a bug related to this?
[18:16] <blackboxsw> ananke: https://bugs.launchpad.net/cloud-init/+bug/1890528 ?
[18:16] <ananke> thank you, I'll check. this may be it.
[18:16] <blackboxsw> ananke: was cloud-init stats --long an error condition too?
[18:17] <ananke> This is on kali, absed on debian: cloud-init/now 20.1-2 all [installed,upgradable to: 20.2-2]
[18:17] <blackboxsw> that would exit early
[18:17] <ananke> blackboxsw: nope, no errors
[18:17] <ananke> I've been trying to figure out for the past hour why our packer configuration is failing on kali 2020.2, while it worked on kali 2020.1, and I was seeing some odd race conditions in the output logs
[18:19] <ananke> we use cloud-init status --wait before proceeding to next steps, and that seemed to first exit when there were problems with bootcmd, but even after removing everything and no errors, I still see it claiming it's done, while modules are still running
[18:20] <blackboxsw> ananke: after "removing everything" do you mean running "sudo cloud-init clean"?
[18:20] <blackboxsw> if a "clean" is not performed, some artifacts will exist on the system that would trick cloud-init status into thinking it is done
[18:21] <ananke> blackboxsw: no, I mean after removing anything in our packer config that pertains to early stages/etc
[18:23] <ananke> we pass a cloud-init config via user-data, and we then tell packer to wait until cloud-init status --wait exits
[18:23] <blackboxsw> ananke: so, cloud-init status --wait looks at /run/cloud-init/status.json
[18:24] <ananke> k, I'll redo the process and see what's in that file
[18:25] <blackboxsw> If each  key(stage) if it sees start and finished times for each stage, then it assumes that cloud-init is complete
[18:25] <blackboxsw> yeah check that and /run/cloud-init/result.json contents
[18:32] <ananke> here's a sample output, after I ssh to the system that's being provisioned: https://dpaste.com/3DT6BTAEW
[18:34] <ananke> so modules-final is not done, yet claims it is?
[18:47] <Odd_Bloke> ananke: Hmm, what is it that's performing those downloads?
[18:47] <Odd_Bloke> Is that just cloud-config, or have you passed in a script or similar?
[18:49] <ananke> Odd_Bloke: just cloud-config
[18:50] <Odd_Bloke> ananke: Could we see a full cloud-init.log?
[18:50] <ananke> sure, do hold
[18:51] <Odd_Bloke> https://www.youtube.com/watch?v=6g4dkBF5anU
[18:53] <ananke> Odd_Bloke: : http://sprunge.us/KExsDJ
[18:55] <ananke> so this part is still not finished: 2020-08-31 18:34:20,861 - util.py[DEBUG]: apt-install [apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install fio time xrdp xorgxrdp aptitude elinks gedit htop leafpad nano nmap vim] took 131.844 seconds
[18:56] <ananke> which is populated via the 'packages:' directive
[18:57] <Odd_Bloke> ananke: It looks like "cloud-init mode 'modules' took" appears 4 times in the log; I believe we would only expect to see it twice: one for each of `--mode config` and `--mode final`.
[18:58] <ananke> ohh, damn, I think you just nailed the issue. in packer as a workaround we had to kick off 'cloud-init --mode=config' and 'cloud-init --mode=final' manually, and I never took that out
[18:59] <Odd_Bloke> That'd do it!
[18:59] <ananke> crap, I'm so sorry
[18:59] <blackboxsw> nice Odd_Bloke
[19:00] <ananke> Here's the offending code:
[19:00] <ananke>                 "cloud-init modules --mode=config; echo cloud-init module config error code is $?",
[19:00] <ananke>                 "cloud-init modules --mode=final; echo cloud-init module final error code is $?",
[19:00] <ananke>                 "/usr/bin/cloud-init status --wait; echo cloud-init status error code is $?",
[19:01] <ananke> It's interesting to see what the consequence is though
[19:03] <blackboxsw> +1 generally cloud-init doesn't prescribe machines invoking each stage directly as part of the boot process because of cloud-init uses systemd service/unit ordering to ensure the start of each stage after the appropriate stage in system boot.
[19:04] <blackboxsw> ...and if cloud-init every added boot stages images which only called into specific cloud-init boot stages might miss the introduction of a new cloud-init boot or configuration  stage  ( which *may* actually happen this year per https://bugs.launchpad.net/cloud-init/+bug/1892851)
[19:05] <blackboxsw> but I get that it is a good option while developing a new system to call into those stages directly
[19:05] <ananke> yeah, we had to put those workarounds due to broken Kali AMI
[19:06] <blackboxsw> roger. if you find there is something that makes sense to upstream, I'm sure we'd love to help get that support in
[19:06] <blackboxsw> into master
[19:07] <ananke> I can't imagine this would be a common issue, but I wonder if putting some locking/semaphore checking makes sense.
[19:10] <ananke> funny enough, I did remove these commands from packer earlier this morning, but then put them back because things were still breaking. so while I fixed the other things (I had to enable/start cloud-init-local.service and cloud-config.service), I never bothered to go back to this section
[19:13] <blackboxsw> ananke: each config module has it's own semaphore based on whether the module should be run per-boot, per-once, per-instance or per-always
[19:13] <blackboxsw> so as a whole, locking the entire boot stage doesn't quite work because some components within that stage want to be run always
[20:42] <ananke> on an unrelated (or semi-related) note, I need to figure out if there's a way to tail cloud-init's log _while_ waiting for cloud-init status --wait to finish
[20:43] <blackboxsw> tail -f /var/log/cloud-init.log?
[20:43] <blackboxsw> :) from a fok
[20:43] <blackboxsw> frok
[20:43] <blackboxsw> fork even
[20:43] <blackboxsw> :)
[20:44] <ananke> blackboxsw: that would work, but I'd have to kill it after cloud-init status --wait exits
[20:45] <ananke> otherwise that entire thing would hang and packer would never finish that stage
[20:48] <ananke> On error conditions I can dump the logs to stdout, which for us means packer sends them to gitlab CICD console and we can inspect them that way. However, it would be nice to view them real time, and see what's happening with the system as we wait ~20-30 mins for various cloud-init stages to finish
[23:32] <blackboxsw> ugh


 I am not getting a sound icon, and when I try some fixes from somewhere, I get dummy output. All in all, my sound doesn't work. Please help!
[17:38] <kunal_> !ping
[17:38] <kunal_> !help
[17:38] <kunal_> !patience
[17:38] <kunal_> !patience | gaurav
[17:39] <u-la-la> [ Official Ubuntu Documentation ] - https://help.ubuntu.com
[17:39] <u-la-la> [ Ubuntu Forums ] - https://ubuntuforums.org
[17:39] <u-la-la> [ Ask Ubuntu ] - https://askubuntu.com
[17:39] <kunal_> !patience | lubotu2
[17:39] <kunal_> !ask | gaurav
[17:39] <u-la-la> [ Official Ubuntu Documentation ] - https://help.ubuntu.com
[17:39] <u-la-la> [ Ubuntu Forums ] - https://ubuntuforums.org
[17:39] <u-la-la> [ Ask Ubuntu ] - https://askubuntu.com


[06:03] <cpaelzer> Church: you'd use it like any other cloud config, it just has to start with a different header as outlined https://cloudinit.readthedocs.io/en/latest/topics/format.html#user-data-script
[06:04] <cpaelzer> Church: so if all you want to do is to create a nocloud image bsaed on that, then yes passing it to cloud-localds should do it
[07:46] <Church> Nod, got it. A follow up question, what's a good way to execute a user data based script at the end of the cloud init process? Attempting to debug why user data on AWS isn't executing correctly so I'm attempting a nocloud image to debug locally.
[07:47] <Church> Thinking that my first command in the script to `cloud-init status --wait` isn't working correctly. Nor is waiting for the /var/lib/cloud/instance/data/boot-finished file to exist before continuing my user data script working either.
[12:56] <holtgrewe> Hello. I want to bootstrap a RockyLinux based machine with cloud-init. I have the following in /var/lib/cloud/instance/cloud-config.txt. https://pastebin.com/ZEMfmqnN However, eth0 and eth1 are configured with DHCP. Other configuration such as SSH host keys are written correctly.
[12:57] <holtgrewe> My VM is launched from OpenStack. Am I overlooking something? Why is my network configuration not applied from /var/lib/cloud/instance/cloud-config.txt?
[13:03] <holtgrewe> Hm, maybe this configuration must come from /etc/cloud/cloud.cfg{,.d/*} and not from the user-data...
[13:13] <holtgrewe> Yes, that is the case. https://stackoverflow.com/a/58368766/84349
[15:15] <martti> hello everyone


[00:00] <liushuyu> It has its root on a PPA: https://launchpad.net/~liushuyu-011/+archive/ubuntu/rust-updates-1.68
[00:00] <liushuyu> Because we do not keep older builds
[00:00] <liushuyu> So I have to keep them for bootstrapping purposes
[00:00] <liushuyu> Or we will need upstream stage0 binaries
[00:00] <vorlon> so rustc-1.68 needs to be bootstrapped from rustc 1.68, and can't use rustc 1.71?
[00:01] <liushuyu> vorlon: the build system will auto-reject if version isn't within 1.67..1.68
[00:02] <liushuyu> ... just like GCC 13 can't build GCC 4.8 successfully
[00:03] <liushuyu> (unmodified, I should add)
[00:03] <vorlon> ok, let me study this for a minute and see what I can come up with for a bootstrap path I could accept
[00:03] <liushuyu> Debian is using upstream binary for bootstrapping new architectures (like RISC-V and now LA64)
[00:04] -queuebot:#ubuntu-release- New: rejected rustc-1.68 [sync] (mantic-proposed) [1.68.2+dfsg0ubuntu1-0ubuntu4]
[00:07] <vorlon> liushuyu: my suggestion is to 1) upload rustc-1.68 to a team-owned lunar ppa where it can build against rustc 1.67.1+dfsg0ubuntu1-0ubuntu2; 2) copy the resulting binaries to the archive-admin-only bootstrap archive; 3) do a sourceful upload of rustc-1.68 to mantic and build the binaries in the Ubuntu archive against the bootstrap archive
[00:08] <liushuyu> vorlon: then where should I find a copy of rustc 1.67.1? You still need a prebuild binary copy
[00:09] <liushuyu> Oh, you said LL
[00:12] <vorlon> yep!
[00:13] <vorlon> https://launchpad.net/~canonical-foundations/+archive/ubuntu/archive-bootstrap
[00:13] <vorlon> looks like we need to get riscv64 enabled
[00:14] <liushuyu> I think powerpc32be isn't within our consideration?
[00:15] <vorlon> correct; it's enabled on the ppa but irrelevant for anything on recent releases
[00:16] <liushuyu> Can I turn it off since it probably won't build anyways
[00:17] <vorlon> just leave it be, it won't even be attempted for recent series
[00:17] <vorlon> powerpc is not enabled for >= bionic
[00:18] <liushuyu> Okay
[00:18] <vorlon> liushuyu: anyway, you're fine to upload (or sourcefully copy) a rustc-1.68 package to that ppa that build-depends on rustc
[00:18] <vorlon> (lunar)
[00:19] <liushuyu> Do we need to file a request to get riscv64 enabled?
[00:20] <liushuyu> Because if I upload the source package now, it will not build for riscv64
[00:20] <vorlon> I've pinged the launchpad team internally.  You don't have to wait for it to be enabled before uploading
[00:20] <vorlon> (we can generate a riscv64 build record using the secret trick of doing a binary copy of the package back to the same target)
[00:23] <liushuyu> I thought it was a Launchpad bug. I did not know you can take advantage of this to rebuild the same version for missing architectures
[00:23] <sarnold> ooo
[00:23] <sarnold> this is at least the third time I've learned this :)
[00:25] <liushuyu> oh well, it's now building, I will return to this PPA in 3 hours (that's about the average build time for rustc)
[00:26] <liushuyu> Excluding slower arm64 instances and "standard" riscv64 instances that is
[03:21] -queuebot:#ubuntu-release- New source: rustc-1.68 (mantic-proposed/primary) [1.68.2+dfsg0ubuntu1-0ubuntu4]
[03:26] -queuebot:#ubuntu-release- New: accepted rustc-1.68 [source] (mantic-proposed) [1.68.2+dfsg0ubuntu1-0ubuntu4]
[03:56] -queuebot:#ubuntu-release- New binary: sysprof [amd64] (mantic-proposed/universe) [45~beta-2] (i386-whitelist)
[03:56] -queuebot:#ubuntu-release- New binary: sysprof [s390x] (mantic-proposed/universe) [45~beta-2] (i386-whitelist)
[03:57] -queuebot:#ubuntu-release- New binary: sysprof [armhf] (mantic-proposed/universe) [45~beta-2] (i386-whitelist)
[03:57] -queuebot:#ubuntu-release- New binary: sysprof [ppc64el] (mantic-proposed/universe) [45~beta-2] (i386-whitelist)
[03:59] -queuebot:#ubuntu-release- New binary: sysprof [arm64] (mantic-proposed/universe) [45~beta-2] (i386-whitelist)
[04:35] -queuebot:#ubuntu-release- New binary: sysprof [riscv64] (mantic-proposed/universe) [45~beta-2] (i386-whitelist)
[05:31] -queuebot:#ubuntu-release- New: accepted sysprof [amd64] (mantic-proposed) [45~beta-2]
[05:31] -queuebot:#ubuntu-release- New: accepted sysprof [armhf] (mantic-proposed) [45~beta-2]
[05:31] -queuebot:#ubuntu-release- New: accepted sysprof [riscv64] (mantic-proposed) [45~beta-2]
[05:31] -queuebot:#ubuntu-release- New: accepted sysprof [arm64] (mantic-proposed) [45~beta-2]
[05:31] -queuebot:#ubuntu-release- New: accepted sysprof [s390x] (mantic-proposed) [45~beta-2]
[05:31] -queuebot:#ubuntu-release- New: accepted sysprof [ppc64el] (mantic-proposed) [45~beta-2]
[06:24] -queuebot:#ubuntu-release- New binary: mathcomp-analysis [amd64] (mantic-proposed/universe) [0.6.4-3] (no packageset)
[06:31] -queuebot:#ubuntu-release- New binary: mathcomp-analysis [ppc64el] (mantic-proposed/universe) [0.6.4-3] (no packageset)
[06:45] -queuebot:#ubuntu-release- New binary: mathcomp-analysis [arm64] (mantic-proposed/universe) [0.6.4-3] (no packageset)
[07:10] -queuebot:#ubuntu-release- New: accepted mathcomp-analysis [amd64] (mantic-proposed) [0.6.4-3]
[07:10] -queuebot:#ubuntu-release- New: accepted mathcomp-analysis [ppc64el] (mantic-proposed) [0.6.4-3]
[07:10] -queuebot:#ubuntu-release- New: accepted mathcomp-analysis [arm64] (mantic-proposed) [0.6.4-3]
[07:14] -queuebot:#ubuntu-release- New source: llvm-toolchain-17 (mantic-proposed/primary) [1:17.0.0~+rc3-1~exp1ubuntu1]
[07:14] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-17 [source] (mantic-proposed) [1:17.0.0~+rc3-1~exp1ubuntu1]
[07:14] -queuebot:#ubuntu-release- New: accepted mozjs115 [source] (mantic-proposed) [115.1.0-0ubuntu1]
[07:17] -queuebot:#ubuntu-release- New binary: rustc-1.68 [armhf] (mantic-proposed/universe) [1.68.2+dfsg0ubuntu1-0ubuntu4] (no packageset)
[07:24] -queuebot:#ubuntu-release- New binary: rustc-1.68 [amd64] (mantic-proposed/universe) [1.68.2+dfsg0ubuntu1-0ubuntu4] (no packageset)
[07:36] -queuebot:#ubuntu-release- New binary: rustc-1.68 [ppc64el] (mantic-proposed/universe) [1.68.2+dfsg0ubuntu1-0ubuntu4] (no packageset)
[07:40] -queuebot:#ubuntu-release- New binary: mozjs115 [amd64] (mantic-proposed/none) [115.1.0-0ubuntu1] (no packageset)
[07:41] -queuebot:#ubuntu-release- New binary: mozjs115 [ppc64el] (mantic-proposed/none) [115.1.0-0ubuntu1] (no packageset)
[07:54] -queuebot:#ubuntu-release- New binary: rustc-1.68 [s390x] (mantic-proposed/universe) [1.68.2+dfsg0ubuntu1-0ubuntu4] (no packageset)
[07:57] -queuebot:#ubuntu-release- New binary: mozjs115 [armhf] (mantic-proposed/universe) [115.1.0-0ubuntu1] (no packageset)
[07:57] -queuebot:#ubuntu-release- New binary: mozjs115 [s390x] (mantic-proposed/universe) [115.1.0-0ubuntu1] (no packageset)
[07:59] -queuebot:#ubuntu-release- New: accepted mozjs115 [amd64] (mantic-proposed) [115.1.0-0ubuntu1]
[07:59] -queuebot:#ubuntu-release- New: accepted mozjs115 [ppc64el] (mantic-proposed) [115.1.0-0ubuntu1]
[07:59] -queuebot:#ubuntu-release- New: accepted rustc-1.68 [amd64] (mantic-proposed) [1.68.2+dfsg0ubuntu1-0ubuntu4]
[07:59] -queuebot:#ubuntu-release- New: accepted rustc-1.68 [ppc64el] (mantic-proposed) [1.68.2+dfsg0ubuntu1-0ubuntu4]
[07:59] -queuebot:#ubuntu-release- New: accepted mozjs115 [armhf] (mantic-proposed) [115.1.0-0ubuntu1]
[07:59] -queuebot:#ubuntu-release- New: accepted rustc-1.68 [armhf] (mantic-proposed) [1.68.2+dfsg0ubuntu1-0ubuntu4]
[07:59] -queuebot:#ubuntu-release- New: accepted mozjs115 [s390x] (mantic-proposed) [115.1.0-0ubuntu1]
[07:59] -queuebot:#ubuntu-release- New: accepted rustc-1.68 [s390x] (mantic-proposed) [1.68.2+dfsg0ubuntu1-0ubuntu4]
[08:33] <mwhudson> britney seems to be crashing
[09:56] -queuebot:#ubuntu-release- Unapproved: accepted gcc-snapshot [sync] (jammy-proposed) [1:20220506-0ubuntu1]
[11:09] -queuebot:#ubuntu-release- New binary: llvm-toolchain-17 [i386] (mantic-proposed/universe) [1:17.0.0~+rc3-1~exp1ubuntu1] (i386-whitelist)
[11:12] <_doko> are all the printing packages now re-introduced? no printing snaps for 23.10?
[11:23] <jbicha> _doko: yes https://lists.ubuntu.com/archives/ubuntu-devel/2023-August/042764.html
[11:30] -queuebot:#ubuntu-release- New binary: llvm-toolchain-17 [amd64] (mantic-proposed/universe) [1:17.0.0~+rc3-1~exp1ubuntu1] (i386-whitelist)
[11:39] <_doko> ok, trying to promote all these again ...
[11:50] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-17 [amd64] (mantic-proposed) [1:17.0.0~+rc3-1~exp1ubuntu1]
[11:50] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-17 [i386] (mantic-proposed) [1:17.0.0~+rc3-1~exp1ubuntu1]
[12:27] -queuebot:#ubuntu-release- Unapproved: netplan.io (jammy-proposed/main) [0.105-0ubuntu2~22.04.3 => 0.106.1-7ubuntu<IP_ADDRESS>] (core)
[12:27] -queuebot:#ubuntu-release- Unapproved: netplan.io (lunar-proposed/main) [0.106-0ubuntu3 => 0.106.1-7ubuntu<IP_ADDRESS>] (core)
[12:28] <coreycb> Hello SRU team, I have 2 items I could use a review on please. one is the python-ovsdbapp microrelease for LP#2007919 in the jammy unapproved queue - I'm hoping to get that in based on the "New upstream microreleases" documented at https://wiki.ubuntu.com/StableReleaseUpdates. The other is a request for additional dependency packages being added to the openstack microrelease exception. I have an email out to the ubuntu-release
[12:28] <coreycb> mailing list for that:  https://lists.ubuntu.com/archives/ubuntu-release/2023-July/005698.html
[12:28] -ubottu:#ubuntu-release- Launchpad bug 2007919 in python-ovsdbapp (Ubuntu Jammy) "[SRU] Stable point releases for python-ovsdbapp" [High, Triaged] https://launchpad.net/bugs/2007919
[13:47] -queuebot:#ubuntu-release- Unapproved: thermald (jammy-proposed/main) [2.4.9-1ubuntu0.3 => 2.4.9-1ubuntu0.4] (core)
[14:40] <rbasak> coreycb: can you update bug 2007919 with the information required by https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases please?
[14:40] -ubottu:#ubuntu-release- Bug 2007919 in python-ovsdbapp (Ubuntu Jammy) "[SRU] Stable point releases for python-ovsdbapp" [High, Triaged] https://launchpad.net/bugs/2007919
[14:41] <rbasak> coreycb: also the dep8 tests are all superficial?
[14:46] <RikMills> vorlon: KDE renamed kalendar to merkuro for 23.08 gear release, hence a new merkuro source in the NEW queue. what do you require to get this accepted?
[14:47] <RikMills> there are no new features since the kalander RC in proposed apart from renaming the package
[14:49] <RikMills> if you want new source/FFe bugs then I will happily do that, but it is a slightly odd circumstance
[15:03] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (lunar-proposed/main) [28.1~23.04 => 29.2~23.04] (core)
[15:04] -queuebot:#ubuntu-release- Packageset: Added markdown to i386-whitelist in mantic
[15:04] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (jammy-proposed/main) [28.1~22.04 => 29.2~22.04] (core)
[15:05] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [28.1~20.04 => 29.2~20.04] (core)
[15:06] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (bionic-proposed/main) [28.1~18.04 => 29.2~18.04] (core)
[15:07] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (xenial-proposed/main) [28.1~16.04 => 29.2~16.04] (no packageset)
[15:22] <vorlon> jbicha: ... why did you push a change to the seeds for disco this year
[15:30] <vorlon> jbicha: also how did you arrive at the conclusion that openjdk-11-* were 'obsolete' and needed unseeded, when these binaries are built from the openjdk-lts source package
[15:38] <jbicha> my commit message says I was confused about the source package that provided openjdk-11
[15:39] <jbicha> I agree the disco change doesn't make sense
[15:44] <jbicha> vorlon: do you want me to revert those changes now?
[15:44] <vorlon> jbicha: yes please
[15:45] -queuebot:#ubuntu-release- Unapproved: rejected s390-tools [s390x] (mantic-proposed) [2.28.0-0ubuntu1]
[15:45] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (mantic-proposed) [2.29.0-0ubuntu1]
[15:46] <schopin> I was about to ask why that was booted. *phew*
[15:55] <vorlon> RikMills: I'll queue merkuro up to look at today, should be straightforward
[15:56] <RikMills> vorlon: cheers :)
[16:01] <sergiodj> vorlon: opinions about the lava situation?  I'm +1 for removing it from the archive
[16:02] <bdmurray> We are investigating issues with the autopkgtest environment.
[16:13] <vorlon> sergiodj: I had yet to look at the bug you referenced. I have now and don't see anything that gives a reason to keep it.  Could you file a bug report about it being unmaintainable (because it FTBFS if we change the source) and then I'll remove it?
[16:14] <sergiodj> vorlon: ACK. I'm in a meeting now, will file it later. thanks
[16:17] <coreycb> rbasak: thanks for taking a look. the dep8 tests are just doing python import testing. I guess they need to run unit tests according to the microrelease documentation. the plan was to run our standard openstack regression on this since python3-ovsdbapp is a dependency of neutron and nova, so it would get exercised there in functional testing.
[16:18] <rbasak> coreycb: thanks. I don't mean to rule out accepting it as is, if you think there's a good alternative case to make. But it should all be written up.
[16:19] <rbasak> (what is missing, what the alternative is and why it's good enough, etc)
[16:20] <coreycb> rbasak: Ok thanks I'll do that now and move it back to new if that is ok with you.
[16:20] <rbasak> Yes - thanks
[16:35] <coreycb> Thanks, I've updated the [Test Case] section
[17:55] -queuebot:#ubuntu-release- New source: time-daemon (mantic-proposed/primary) [0.1]
[18:00] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (lunar-proposed) [252.5-2ubuntu3.1]
[18:02] -queuebot:#ubuntu-release- New source: time-daemon (mantic-proposed/primary) [0.1]
[18:05] <sergiodj> vorlon: there you go: https://bugs.launchpad.net/ubuntu/+source/lava/+bug/2032978
[18:05] -ubottu:#ubuntu-release- Launchpad bug 2032978 in lava (Ubuntu) "Please remove lava from the archive (doesn't support Ubuntu; FTBFS with delta)" [Undecided, New]
[18:06] <vorlon> sergiodj: thanks
[18:06] <vorlon> (subscribed ubuntu-archive)
[18:07] <sergiodj> ah, I assigned the bug to ubuntu-release, but maybe I shouldn't have
[18:10] -queuebot:#ubuntu-release- New source: time-daemon (mantic-proposed/primary) [0.1]
[18:10] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (jammy-proposed) [249.11-0ubuntu3.10]
[18:15] <Eickmeyer> vorlon: Point of clarification: Entirely new, unseeded packages do *not* need an FFe, correct?
[18:22] -queuebot:#ubuntu-release- New: rejected time-daemon [source] (mantic-proposed) [0.1]
[18:22] -queuebot:#ubuntu-release- New: rejected time-daemon [source] (mantic-proposed) [0.1]
[18:22] <vorlon> Eickmeyer: correct
[18:22] <vorlon> they just need AA attention :)
[18:23] <Eickmeyer> vorlon: Cool. RAOF saw qprompt in NEW and thought it needed an FFe.
[18:24] <vorlon> just checked, it is written on https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_for_new_packages
[18:27] <Eickmeyer> vorlon: Thanks.
[18:29] <Eickmeyer> Just wanting to make sure everyone's on the same page. :)
[18:31] -queuebot:#ubuntu-release- New: rejected time-daemon [source] (mantic-proposed) [0.1]
[18:32] <bdmurray> Eickmeyer: My naming a specific person? That's not very nice.
[18:32] <Eickmeyer> bdmurray: I was just wanting to bring it to their attention. I meant no ill intentions.
[18:33] <_doko>      bdmurray: looks like https://autopkgtest.ubuntu.com/running is out-of-date, compared to update_excuses
[18:34] <Eickmeyer> bdmurray: I guess, I was thinking of it like a CC:, if you will. :)
[18:35] <bdmurray> Other people might read it as dimes being dropped.
[18:36] <bdmurray> _doko: I'm actively working on it
[18:36] <Eickmeyer> That was not the intention, I assure you (and others).
[18:36] <_doko> ta
[18:46] <bdmurray> _doko: should be squared away now
[18:54] <liushuyu> Hi release team, https://launchpad.net/ubuntu/+source/rust-minijinja this packages contain a lot of dependencies that are not yet exist in neither Ubuntu nor Debian. Should we remove it or wait for unspecified amount of time for the Debian maintainer to package the dependencies?
[18:54] <liushuyu> (But seriously, how did this got into the Debian archive)
[18:55] <liushuyu> (by not yet exist, I meant do not exist in any of: Ubuntu -proposed, Debian -proposed, Debian NEW)
[18:57] -queuebot:#ubuntu-release- New source: time-daemon (mantic-proposed/primary) [0.1]
[19:19] <jbicha> Debian NEW processing doesn't really check whether the dependencies exist yet
[19:20] <jbicha> I've seen a lot of Rust packages get into Debian before their dependencies do 😢
[19:39] -queuebot:#ubuntu-release- New: accepted time-daemon [source] (mantic-proposed) [0.1]
[19:41] -queuebot:#ubuntu-release- New binary: time-daemon [amd64] (mantic-proposed/none) [0.1] (no packageset)
[19:46] -queuebot:#ubuntu-release- New: accepted time-daemon [amd64] (mantic-proposed) [0.1]
[19:59] <vorlon> liushuyu: watching paint dry in the rustc-1.68 riscv64 build log: dpkg-shlibdeps: warning: relation < is deprecated: use << or <=
[20:00] <vorlon> 'deprecated' is really a misnomer, it's been deprecated for 20 years
[20:03] <liushuyu> vorlon: did a quick grep on the debian/ directory and I did find any `<` expression inside
[20:03] <liushuyu> All the version relations are either `<<` or `=`
[20:04] <vorlon> liushuyu: it's dpkg-shlibdeps so it may come from a library dependency
[20:05] <vorlon> RikMills: how is it that merkuro's debian/copyright appears to be completely different from kalendar's with no changes between them to the upstream copyright statements?
[20:23] <liushuyu> vorlon: I think if you are watching the paint dry in the rustc-1.68 riscv64 build, you probably should aware how the time is severely bent around on the instance
[20:23] <vorlon> heh
[20:24] <liushuyu> It might actually quite fast on their observation, but we just observe it to be slow
[20:24] <vorlon> well either way the tab stays open until it finishes and I can copy the output to the bootstrap archive :P
[20:24] <liushuyu> The time dilation is just too great
[20:24] <vorlon> https://launchpad.net/ubuntu/+source/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu4 is built for everything but riscv64
[20:24] <vorlon> which should actually unblock the kernel team for source packages other than linux-riscv64
[20:24] <liushuyu> We are lucky that qemu isn't getting stuck somewhere
[20:35] -queuebot:#ubuntu-release- Unapproved: magnum (lunar-proposed/universe) [16.0.0-0ubuntu1 => 16.0.1-0ubuntu1] (openstack)
[20:45] <liushuyu> Okay, it's built, but waiting for the publication
[20:55] <vorlon> liushuyu: ah but I don't have to wait for the publication, I'm grabbing the .debs from launchpad anyway ;)
[21:08] <mitchdz> Just want to confirm, is the final decision for mumax3 to remove arm64 builds? Just want to know if I should continue looking into https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2032624
[21:08] -ubottu:#ubuntu-release- Launchpad bug 2032624 in mumax3 (Ubuntu) "mumax3 test suite fails against glibc 2.38" [Critical, New]
[21:17] <vorlon> liushuyu: https://launchpad.net/ubuntu/+source/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu4/+build/26533122 is building with the rustc-1.68 build dependency resolved, so I believe this is all done from my side
[21:17] <liushuyu> vorlon: Thank you! Let's skip 16 hours and see how it's doing
[21:21] <vorlon> mitchdz: well I think this was in ginggs' court