[02:45]  * ogra_cmpc reads the "academic free license"
[02:45] <ogra_cmpc> ... 5) This section intentionally omitted. ...
[02:46] <ogra_cmpc> i wonder if that the academic part of it ...
[02:46]  * ogra_cmpc shakes head
[02:46] <LaserJock> heh
[02:46] <kgoetz> hehe
[02:47] <johnny> lol
[02:48] <johnny> ogra wtf is is a classmatepc
[02:48] <johnny> hmm.. btw.. i'm not impressed by bzr so far
[02:48] <johnny> i was hoping i'd like it better
[02:48] <ogra_cmpc> http://www.classmatepc.com/
[02:49] <johnny> oh.. their olpc competition
[02:49] <johnny> i forgot about that thing
[02:49] <ogra_cmpc> pfft
[02:49] <ogra_cmpc> no competition if you look at the HW
[02:50] <ogra_cmpc> or at the strategies
[02:52] <kgoetz> for what value of 'no'? heh
[02:53] <ogra_cmpc> OLPC tries to develop new concepts for hard and software based on sociological studies about human interaction in teaching
[02:53] <ogra_cmpc> they are a scientific project ....
[02:53] <LaserJock> yep
[02:54] <ogra_cmpc> intel is a HW manufacturer ... they want to give every kid in the world a usable laptop and earn some money with it
[02:54] <LaserJock> ogra_cmpc: somebody tried to sneak OLPC's squeak into Fedora saying it was "MIT" license ;-)
[02:54] <ogra_cmpc> LOL !
[02:55] <LaserJock> I'm surprised they use squeak so much given it's non-freeness
[02:55] <ogra_cmpc> especially since fedora really just turns into a second debian regarding their license policy changes recently
[02:56] <kgoetz> LaserJock: how does olpcs squeak differer from normal squeak?
[02:56] <ogra_cmpc> there were some silly removals i heard of
[02:57] <johnny> i've had this prejudice against rpm that i cant shake
[02:57] <johnny> have't used an rpm based distro sine 2001
[02:57] <kgoetz> thier being hyper caustios
[02:57] <kgoetz> *sp
[03:00] <LaserJock> kgoetz: it's got some special stuff to work with OLPC hardware
[03:00] <LaserJock> and then they've built a lot of goodies for kids I guess
[03:00] <LaserJock> using etoys
[03:01] <LaserJock> I've recently spent a week with Fedora when I didn't have an Ubuntu alternate disk around
[03:01] <kgoetz> LaserJock: i was wonderin if olpc's version was less-free then the standard squeak, or if its just the normal 'non-freeness'
[03:01] <ogra_cmpc> and ?
[03:01] <LaserJock> it was definitely better than openSUSE
[03:01] <kgoetz> *wondering
[03:01] <LaserJock> but some things are hard to get used to
[03:02] <LaserJock> I had a lot of problems with networking
[03:02] <LaserJock> that "Just Worked" in Ubuntu
[03:02] <ogra_cmpc> really ?
[03:02] <LaserJock> yeah, Fedora won't work with my uni's VPN
[03:02] <ogra_cmpc> they claim their NM works better :P
[03:02] <LaserJock> well
[03:02] <LaserJock> NM isn't even turned on by default
[03:02] <ogra_cmpc> i had some discussions with warren :)
[03:02] <ogra_cmpc> heh
[03:02] <LaserJock> I had to go into the service config thingy
[03:02] <ogra_cmpc> i didnt know that
[03:02] <LaserJock> and enable it
[03:03] <LaserJock> then go into the network config thingy
[03:03] <LaserJock> and tell it to let NM manage the interfaces
[03:03] <LaserJock> *that* took me some time to figure out
[03:03] <ogra_cmpc> yeah, i can imagine
[03:03] <LaserJock> but the VPN issue was the hardest
[03:03] <LaserJock> Ubuntu has network-manager-pptp
[03:03] <LaserJock> which makes my uni VPN a breeze
[03:04] <LaserJock> but I couldn't for the life of me get Fedora to work with it
[03:04] <LaserJock> they're really wanting to beef up Edu stuff though
[03:04] <LaserJock> not just LTSP
[03:05] <ogra_cmpc> well, from hardy+1 on we'll do that too
[03:05] <ogra_cmpc> for hardy i just want the cd change to work
[03:05] <ogra_cmpc> in hardy+1 we can finally take care for some apps and for filling up the CD
[03:06] <ogra_cmpc> warren tries to merge k12ltsp into fedora ...
[03:07] <LaserJock> what is the CD situation
[03:07] <ogra_cmpc> but he just starts
[03:07] <LaserJock> I saw cjwatson making seed changes
[03:07] <ogra_cmpc> the seed and germinate chnages are done
[03:07] <ogra_cmpc> cd build changes are still missing
[03:07] <ogra_cmpc> but should be done next week
[03:08] <LaserJock> ok
[03:08] <LaserJock> I had wanted to try to get a little more onto it
[03:08] <ogra_cmpc> alpha5 will definately have the new setup
[03:08] <LaserJock> but squeak is taking most of my *buntu time at the moment :(
[03:08] <LaserJock> the new octave3.0 is supposed to be a real good Matlab replacement
[03:08] <ogra_cmpc> we need to find a way to only have langpacks on there that are not on the ubuntu cd already
[03:09] <LaserJock> oh, that's a good point
[03:09] <ogra_cmpc> currently we waste a lot of space
[03:09] <LaserJock> ltsp is also on there as well, right?
[03:09] <LaserJock> but that doesn't take much space
[03:09] <ogra_cmpc> i'm not even sure anyone uses the langpacks from the cd
[03:09] <ogra_cmpc> nope
[03:09] <ogra_cmpc> no ltsp on there
[03:10] <LaserJock> it might be worth having all the gcompris sound packages if we don't already
[03:10] <ogra_cmpc> moodle, postgres, apache, php ...
[03:10] <LaserJock> those things are a pain to download
[03:10] <ogra_cmpc> everything in /live will go to addon
[03:10] <ogra_cmpc> -live
[03:11] <LaserJock> ah, shipaddon has then
[03:11] <LaserJock> *them
[03:11] <LaserJock> I spent a good part of the day in #gcompris
[03:11] <ogra_cmpc> we'll have the old edubuntu desktop again ... but with the difference that it depends on ubuntu-desktop
[03:11] <LaserJock> yeah
[03:11] <LaserJock> there's a new release of gcompris I'm gonna try to get into Hardy
[03:11] <LaserJock> it should fix a bunch of crashers
[03:12] <ogra_cmpc> great
[03:12]  * ogra_cmpc thinks he finally found the right combo of apps for a speedy and blingy cmpc desktop
[03:16] <ogra_cmpc> i've tried a good amount of docks now on this HW ... cairo-dock is the first one thats not stuttering ... really impressive
[03:18] <LaserJock> I talked to the gcompris Debian maintainer and he said he'd have the new version shortly
[03:18] <LaserJock> I'll file a UVFe/sync request after that
[03:18] <ogra_cmpc> cool
[07:32] <achandrashekar> hello. I had posted to the list with my question(s) as well. Hoep someone can answer here as well.
[07:32] <achandrashekar> When installing in standalone mode. I first receive a message on a single nic device that I need to edit /etc/default/dhcp
[07:32] <achandrashekar> and then i notice that once installed NOT all packages are installed to make to serve ltsp
[07:33] <achandrashekar> as a result, I completely re-installed ltsp-standalone
[07:33] <achandrashekar> then..re-edit the dhcp.conf.
[07:33] <achandrashekar> The question is - Am I going about the standalone correctly?
[07:33] <achandrashekar> Next question is about failover-dhcp
[07:34] <achandrashekar> I couldnt get it working following the directions to the T on wiki
[07:34] <achandrashekar> but i had only one box installed, do i need both to be up?
[07:34] <achandrashekar> I couldnt even get the image to boot on my clients.
[07:34] <achandrashekar> but if i try to get a simple config of dhcp.conf...then no issues.
[09:43] <achandrashekar> all right we will try the mail lists....again.
[09:43] <achandrashekar> :/
[10:38] <lowercase_> greetz everyone
[20:24] <edu_help_pls> hello
[20:24] <edu_help_pls> is there anybody who can help me with an issue?
[20:25] <edu_help_pls> ?
[20:27] <edu_help_pls> who can help me with an issue with edubuntu???
[20:27] <laga_> edu_help_pls: ask a question and wait - someone might have an answer
[20:27] <edu_help_pls> ok
[20:27] <edu_help_pls> so
[20:29] <edu_help_pls> i have tried to implement a project  with edubuntu. 1 server and 20 diskless clients. 10/100 24 port switch. 10/100/1000 nic. I need to run Firefox on all clients. But when 3-4-5 clients access a flash website any other client does not respond as the network is suffocated
[20:29] <edu_help_pls> the network reaches 12MBs traffic
[20:29] <edu_help_pls> why????
[20:29] <edu_help_pls> is flash doing so much traffic????
[20:30] <edu_help_pls> flash=swf
[20:31] <laga_> edu_help_pls: relax with the question marks. i don't have an answer (other than flash playback probably takes a lot of playback as each picture is transmitted over the network).
[20:31] <laga_> maybe someone in here knows :)
[20:32] <edu_help_pls> but i hope there is a sollution because otherwise i'm dead
[20:32] <edu_help_pls> :(


[02:56] <miltos> hi ppl:-)
[02:59] <miltos> how to unrar multiple files f.g part1.rar, part2.rar. I've tried to install rar unrar on my lubuntu but I've got the message "unrar has no installation candidate"
[03:16] <xangua> Sudo apt update && sudo apt install rar unrar p7zip-full
 thanks but it does not work...maybe it's because I run lubuntu on my odroid xu4...
[03:27] <xangua> Ooh...
 it doesn't matter
[13:43] <jomar> i have a problem installing lubuntu
[13:44] <jomar> failed to install bootloader how can i fix this?
[13:44] <Sabotender> hello, I am using lubuntu with LXDE and entire UI is super tiny on my 4K screen. how can I scale ALL UI elements?
[13:45] <jomar> i dont know im new on installing lubuntu
[13:45] <Sabotender> well, we won't be much help to each other then.
[13:45] <jomar> yeah i guess
[13:45] <jomar> do you know how to fix bootloader?
[13:46] <Sabotender> nope
[13:46] <jomar> danggg
[13:46] <jomar> im new to linux
[13:47] <jomar> i tried linux and now my laptop is fcked up
[13:49] <jomar> youtube may help fix your problem
[13:52] <hateball> !fixgrub | jomar
[13:52] <hateball> ignore that it says windows, just follow the steps to reinstall grub
[13:54] <jomar> it always says bootloader failed to install
[13:55] <jomar> i have 320 GB HDD can you tell me how to create partision?
[13:58] <jomar> i dont know how to fix grub
[13:58] <jomar> please help me
[13:58] <jomar> how to reinstall grub?
[14:02] <jomar> i use old sony vaios laptop hoping to use it again using lununtu
[14:06] <jomar> what kind of mount point should i use
[14:08] <jomar> hey?
[14:08] <jomar> anyone?
[14:08] <jomar> i need help
[14:09] <jomar> how to create a right partition
[14:12] <hateball> jomar: If you follow the documentation on the wiki it should be quite clear
[14:12] <hateball> jomar: And if this is a fresh install, the install wizard will create partitions for you. No need to do it manually unless you have specific requirements
[14:12] <jomar> where?
[14:13] <hateball> !fixgrub | In case you have less than 10 lines scrollback jomar
[14:13] <jomar> i use old laptop
[14:13] <hateball> liveboot, install&run boot-repair, be happy
[14:14] <jomar> and i dont know how to setup
[14:14] <hateball> What do you need to know? Just let the installer choose for you
[14:14] <jomar> i always stock at bootloader
[14:15] <jomar> i tried erase disk and install lubuntu but same problem bootloader failed
[14:15] <jomar> i tried lvm too
[14:17] <hateball> jomar: are you using UEFI or BIOS?
[14:17] <jomar> im using bios
[14:18] <jomar> im using old laptop sony vaios
[14:19] <hateball> jomar: Do you get any error message?
[14:19] <jomar> failed to install bootloader
[14:19] <jomar> im stock on it
[14:20] <jomar> its says choose another partition (idk) it's asking me to change partion or something else
[14:21] <jomar> choose another partition to save bootloader something like that
[14:21] <hateball> well the bootloader goes into the MBR of your disk, but /boot resides in the filesystem
[14:21] <hateball> jomar: Where do you choose to install the bootloader then?
[14:21] <hateball> If your laptop drive is /dev/sda, you should install grub to that
[14:22] <jomar> yes i do and i put  /  in mount point
[14:22] <jomar> i create swap linux too
[14:23] <hateball> jomar: So you are doing manual partitions? Why not let the installer wizard just do it for you?
[14:24] <jomar> yes i tried that method too
[14:24] <jomar> same problem bootloader failed to install
[14:25] <jomar> if you have some time we can both use team viewer so you can see what the problem is ( if you just have time )
[14:25] <hateball> jomar: is it 17.04 ?
[14:25] <jomar> 16.10
[14:25] <hateball> jomar: I am at work so I dont really have time
[14:25] <jomar> its okay no problem
[14:25] <hateball> jomar: 16.10 will be unsupported soon, so use 16.04 or 17.04
[14:26] <jomar> awww
[14:26] <jomar> seriously?
[14:26] <hateball> !lts
[14:26] <hateball> jomar: LTS is supported for 5 years, and the other versions are only supported for 9 months, then you need to upgrade to the next release
[14:27] <hateball> jomar: So it would be better for you to install 17.04 if you want the latest supported. Maybe that magically works also
[14:28] <jomar> any direct download link?
[14:32] <jomar> okay okay thank you for helping
[14:33] <jomar> is there any way to contact you if there's a problem installing the new release version?
[14:33] <hateball> jomar: Well this channel is always around
[14:33] <jomar> email , gamail or facebook
[14:33] <hateball> Heh, no.
[14:34] <hateball> jomar: Also you can ask in #ubuntu too, there are more people there... even some that use Lubuntu
[14:34] <jomar> oh i see
[14:34] <jomar> Grub installation failed again
[14:36] <jomar> the "grub-pc" package failed to install to /target/. without the grub boot loade, the installed s ystem will not boot
[14:37] <jomar> i think the "Grub" is the problem here because it says "the installed system will not boot
[14:37] <hateball> well yes, you need grub installed to be able to boot your system
[14:38] <jomar> how to install it?
[14:38] <hateball> I dont quite understand why it would fail to install tho, unless using some exotic UEFI setup
[14:38] <hateball> jomar: well the installer should "just work"
[14:38] <jomar> i use bios
[14:39] <jomar> how to fix Grub?
[19:14] <Pablo___> Hello! I need help
[19:15] <Pablo___> Is there anyone who can help me with a wireless connection problem?
[19:19] <Gaup82> Anyone there?
[19:20] <Gaup82> I need help
[19:20] <Gaup82> Anyone there?
[19:20] <Gaup82> Hello?
[19:21] <Gaup82> bye


[03:20] <ScottL> TheMuso, i'm back, was out with family, changing and be back on in a sec
[03:59] <ScottL> TheMuso, do you want to coordinate about what needs to be done?
[04:11] <TheMuso> ScottL: Sorry, been in and out a bi8t.
[04:11] <TheMuso> ScottL: Ok, so as I said in my recent email, I have the lintian errors in hand.
[04:11] <TheMuso> But I don't know who needs contacting in the kernel team about the ABI numbers.
[04:42] <ScottL> TheMuso, i admit that i do not fully understand the 'abi numbers'
[04:42] <ScottL> TheMuso, thank you for correcting the lintian errors
[04:43] <ScottL> TheMuso, however, i will gladly bug UKT members about the ABI numbers
[04:44] <ScottL> TheMuso, but are we pushing the limits to get a second review before thursday?  should we mobilize a few people to bug #ubuntu-motu or other places/people?
[04:44] <ScottL> just to be clear....
[04:45] <ScottL> TheMuso, if you can explain a little more about the ABI numbers i certainly don't mind doing the leg work to follow up with people, however i am not currently doing it
[04:50] <TheMuso> ScottL: Ok, the aBI number changes every time the kernel ABI changes when there are changes made to the kernel. This is done to make sure modules/other stuff built against the kernel doesn't break, more more correctly, shows when external stuff against the kernel breaks due to changes.
[05:24] <ScottL> TheMuso, okay, i will bug a few people in #ubuntu-kernel about it but also email apw (or ping him directly) about it
[05:24] <ScottL> TheMuso, i'll also start announcing in #ubuntu-motu and poking a few other people about reviewing the kernel tomorrow morning
[05:24] <ScottL> TheMuso, i am presuming you dput'ed the kernel changes back into REVU
[05:34] <TheMuso> ScottL: Not yet, but I can.
[05:34] <TheMuso> ScottL: Oh, who do you want as maintainer? The maintainer field cannot have 2 maintainers listed.
[05:34] <TheMuso> According to lintian anyway.
[05:36] <micahg> correct, 1 maintainer (which should be ubuntu-devel-discuss), the rest should be Uploaders:
[05:39] <TheMuso> It doesn't have to be ubuntu-devel-discuss, but it has to be someone with an ubuntu.com address.
[05:44] <micahg> no, it really should be ubuntu-devel-discuss
[05:45] <micahg> a secondary team address can be added to Uploaders
[05:45] <TheMuso> Fair enough.
[05:46]  * micahg is guilty of making the Maintainer a team address as well, but it's not right
[05:46] <TheMuso> Is that policy?>
[05:47] <micahg> unoffical, we changed update-maintainer a while back to set ubuntu-devel-discuss as the maintainer across the board
[05:48] <micahg> as Ubuntu doesn't officially have maintainers, setting Maintainer to something other than ubuntu-devel-discuss gives the wrong impression
[05:49] <micahg> that doesn't mean that everyone that can should randomly upload stuff, but it shouldn't be used to give the impression of excluding people who want to help with things
[05:49] <TheMuso> Right.
[06:23] <ScottL> TheMuso, i would suggest me as maintainer as i don't want to impose on abogani (although i will most likely rely on his expertise)
[06:24] <ScottL> TheMuso, although would it be possible to put the ubuntustudio-dev team as maintainer?  if not, then certainly feel free to use my name 'Scott Lavender<EMAIL_ADDRESS>[09:05] <TheMuso> ScottL: read above re what micahg said, I can certainly put you guys as uploaders.
[14:38] <scott-work> TheMuso: ping
[14:38] <scott-work> astraljava: ping
[16:11] <len> scott-work: Would you like me to try making the theme work?
[16:12] <len> You had mentioned the menus, but all the required apps are not in place yet.
[16:12] <scott-work> len: i was hoping to look at this this afternoon, but i certainly have enough to do, so please do so :)
[16:12] <len> What is the package name?
[16:13] <scott-work> len: when i mentioned the menu i meant more about the larger structure, not if every app is in the correct place
[16:13] <scott-work> len: what i mean, i would like the 'audio production' menu not under the 'multimedia' menu
[16:13] <scott-work> those types of things
[16:13] <len> OK, I am not sure how I would change it.
[16:13] <holstein> i actually like it there though
[16:13] <holstein> and it matches the way it was
[16:14] <scott-work> holstein: i don't think it matches the way it was
[16:14] <holstein> scott-work: used to be under "audio"
[16:14] <holstein> i think the multimedia label is better anyways
[16:14] <holstein> it was under a sub-heading like that
[16:14] <holstein> i mean.. go for it.. im just stating opinion and preference
[16:15] <len> Using multimedia is fine when there are three apps... video, audio and volume...
[16:15] <scott-work> but what if we used "multimedia" for more desktop actions, play a movie, play a cd, etc
[16:15] <scott-work> but have another menu for audio production
[16:15] <holstein> eh.. i like it being there
[16:15] <scott-work> and another for video stuff, and antoher for graphic
[16:15] <holstein> not getting an extra one
[16:15] <holstein> and its already like that
[16:15] <holstein> but again.. im with you scott-work
[16:16] <holstein> i just remember looking there on the live CD.. seeing it under multimedia and thinking "hey, thats where it should be"
[16:16] <holstein> i went right to it.. where as in gnome, some of the stuff seemed out of place where it was
[16:16] <len> graphics is already split.. ok I will look at that. Where are we putting that I see there is some in the share directory, but some in /etc too
[16:18] <len> holstein: we could do both.
[16:19] <holstein> nah.. i can move them if i want in the end.. im just stating my preference for the things as-is, which is easier to maintain as well :)
[16:19] <holstein> doesnt mother me personally either way
[16:19] <scott-work> i downloaded the image last night to test a few things, i'll see if i can put the menu like i see it and i'll post an image to show the structure
[16:19] <holstein> i just hope i *actually* get this evening to myself :/
[16:19]  * holstein running to the concert.. o/
[16:20] <scott-work> my thougth again, is that we are media creation distribution and that those work flows should be very present and accessible
[16:21] <len> Do we really want to split the menu to every work flow?
[16:23] <len> scott-work: we were originally talking about having a software loader that just loaded the wanted workflows, but I think that is gone because we want the live dvd to have "everything" and live dvd seems to mean it has whatever an install has.
[16:24] <len> So the only reason for splitting the metas into workflows wold be so someone who has another ubuntu/deb flavour can just install one workflow.
[16:24] <len> It seems like ubiquity will just install eveything.
[16:25] <len> That being the case it may be just as easy to have only a few metas.
[16:28] <len> ardour3b3 is released...
[16:32] <len> We may be able to have a shiny new ardour3 for 12.11
[16:34] <scott-work> len: this isn't for every work flow
[16:34] <scott-work> len: but do you want every audio, video, graphical, and photography application int he same menu?
[16:34] <scott-work> i don't think that is a very practical approach
[16:35] <scott-work> nor do i think having your pedestrian applications (like totem and audacious) in media creation menus (i.e. audio production, graphical, or video menus)
[16:35] <scott-work> i view totem and audacious to be desktop applications, things you do to consume media, tasks that your everyday user would do as well
[16:36] <scott-work> but i would like the things you do to create the media in their own menus, but not under the multimedia menu
[16:36] <len> Ya, I thought something like that
[16:37] <len> It would be nice to let audio interface card controllers be on their own.
[16:37] <len> We end up with a lot of extra stuff clogging up the audio menu with all of them
[16:39] <astraljava> scott-work: pong, wait what‽ You're working on Sunday?
[16:46] <len> Anybody know PA very well? I was wondering how easy it is to change settings on the fly from the CLI
[16:48] <len> I would like to change the audio interface (to none) when jackd starts so that PA-jackd bridging works.
[16:48] <len> exit
[16:49] <len> opps...ignore thaT
[16:55] <scott-work> astraljava: yeah, but i'm leaving now...i was just wondering if we were going to have a meeting (informal or otherwise)
[16:55] <scott-work> see you in about thirty minutes
[16:57] <astraljava> ScottL: We can haz. It's informal turn.
[17:24] <len> ScottL astraljava whoever... I was just wondering if a tearoff menu for each workflow would be of use.
[17:27] <ScottL> i'm back
[17:27] <len> That is an app that has just the menubar and each item is a different workflow. Click on the workflow and tear it off and that menu can be put anywhere on the desktop. It would have just the apps for that workflow.
[17:27] <ScottL> len, yes, i agree that having the mixers in their own sub-menu would be helpful.  i have also considered putting plugins in their own submenu as well
[17:28] <ScottL> nothing is formalized yet, but i would like to see what makes sense, helpful to users, and not too much trouble for us
[17:28] <len> I would put a synth or sound generator sub
[17:28] <ScottL> len, that is a good suggestion
[17:30] <len> I don't know if xfce supports tearoffs, but I will whip up a tk/tcl app with two workflows just to see how it would look.
[17:32] <ScottL> len, i'm not sure about "tearoffs", i haven't heard of them before
[17:32] <len> It may be possible (but dangerous?) to detect the sound IF and only show mixers that fit.
[17:32] <len> That is why I will put together a tktcl script to show you...
[17:33] <ScottL> len, one thing i've done is use the panel and added a basic work flow in a "fly-out" or "stack"
[17:33] <len> It is easier to show than tell.
[17:33] <ScottL> in the menu, you click on the single icon and an entire string of work flow icons comes out (in my case it was sideways because it was a side menu)
[17:34] <len> My thought is that the main menu of work flows would go away when one of the subs was selected
[17:34] <len> The main would come back when it was closed.
[17:36] <len> I would suggest that the mini menu/pannel on the bottom be moved by default to be on the side... any one I have talked to puts it there and all the new screens are wider.
[17:37] <ScottL> len, not to shut down your enthusiasm but, i'm not too worried about this right now
[17:37] <ScottL> len, i DO want to focus on it in a cycle or two though :)
[17:37] <len> ScottL: you are at least the third person who has said yours is vertical
[17:38] <ScottL> i'm hoping to get the basic functionality pretty stable and well rounded this cycle and the next
[17:38] <ScottL> then i wanted to start focusing on making things better for new, inexeperienced users (i.e. non-linux users)
[17:39] <ScottL> this would even mean changes to how jackd behaves perhaps and better project management for audio
[17:39] <len> ScottL: I would say the theme is standing in the way of new users right now ;-)
[17:39] <ScottL> (ladish could be the chosen "audio project management" tool, maybe not, maybe we go with scripts and our own dialouge)
[17:40] <ScottL> len, yeah, i'm going upstairs in a bit to install the latest image and see what's up
[17:41] <len> To use Jackd, properly... PA needs to either be restarted after jackd or needs to have it's alsa ports set to none on the fly. and a2jmidid needs to be started after jackd.
[17:42] <len> It would almost be better to default PA to no output and run jackd all the time.
[17:43] <ScottL> len, it may be that the pulseaudio-module-jack isn't installed or installed properly or we need to make another adjustment
[17:43] <len> PA is the problem. The modules are all there.
[17:44] <len>  PA just doesn't drop it's alsa connection when it connects to jack.
[17:44] <len> This way of doing things may actually be correct.
[17:45] <len> Because jack may be using one audio IF and PA may also be meeding a second.
[17:45] <len> meeding should be feeding
[17:47] <len> I ran a session with jackd/pulse/a2jmidid with all the multimedia stuff running
[17:48] <len> like audacious, video, flash, minitube etc. it all worked fine.
[17:48] <len> I used audacious as an input audacity which also worked fine.
[17:49] <len> Anyway, I need to go. Be back after lunch.
[17:50] <ScottL> len, but also jack may need to be the the jack-dbus version or have it enabled or similar
[17:50] <ScottL> i'm not sure what jack is working right now
[21:15] <TheMuso> ScottL: Sorry, I got sidetracked last night.
[21:16] <ScottL> TheMuso, that's okay, i'm still feeling a little off myself
[21:17] <ScottL> what should the next step be?
[21:19] <TheMuso> Well I need to upload the revised package.
[21:19] <TheMuso> And will do so in the next hour or so, just coming online for work after the weekend, so processing email and such.
[21:59] <len-nb> ScottL: Yup jackd is dbus... at least that is what it says in ps x.
[21:59] <len-nb> It really is a PA issue. Just changing PA settings makes it work.
[22:06] <TheMuso> len-1204: What settings need changing?
[22:09] <len-1204> TheMuso: when jackd is started, the output settings of PA need to be set to none.
[22:10] <len-1204> I can do that manually with pavucontrol (last tab) and everything works.
[22:10] <len-1204> I can do this before or after I start jackd and it still seems to work either way.
[22:12] <len-1204> As long as PA is using alsa as an output and jackd is using it, PA can't output anything as it is in a wait state.
[22:13] <len-1204> One point of view might be this is a bug and another that this is a correct action.
[22:13] <TheMuso> Hrm. Do you have the jackdbus module loaded? When pulse is running but not jack, have a look at the "pmc list-modules" command output.
[22:13] <TheMuso> Sorry that shoudl be "pacmd list-modules"
[22:15] <len-1204> Wow, that is about 5 pages. What am I looking for?
[22:15] <len-1204> name: <module-jackdbus-detect>
[22:17] <len-1204> Soon as jackd starts, PA connects to it and a look at jackd connections through qjackctl shows it set up correctly.
[22:18] <TheMuso> Ok.
[23:39] <len-1204> ScottL: There seems to be more than one menu file that does the same thing.
[23:40] <len-1204> There is /usr/share/ubuntustudio-menu/menus/applications.menu
[23:42] <len-1204> and there is /etc/xdg/menus/applications-merged/ubuntustudio-mutimedia.menu


[02:22] <emilio> hey guys
[02:41] <emilio> can someone help me?
[02:41] <wgrant> emilio: Probably -- ask your question, and someone will help if they can.
[02:42] <emilio> i'm installed the Launchpad "itself" on my ubuntu
[02:42] <emilio> and want to know some things...
[02:43] <emilio> what is the real purpose of this?
[02:43] <wgrant> Why have you done that, rather than using Launchpad.net? While you *can* run it yourself, it's very difficult, so nobody does, and that wasn't the intention behind releasing the code.
[02:43] <emilio> can i have a my own launchpad with my own projects running on a server without any connection with launchpad.net?
[02:44] <maxh> You CAN, but you (usually) SHOULDN'T.
[02:44] <wgrant> You could, but you'd have to replace all of the images and branding used by the application, and obtain all the necessary resources and knowledge required to run it successfully.
[02:45] <wgrant> It's a very rare case when it's a good idea to do it.
[02:45] <emilio> humm
[02:45] <maxh> You probably want to put your project on launchpad.net.
[02:45] <wgrant> If you are at all unsure, you want to put it on Launchpad.net.
[02:46] <emilio> on my local build of launchpad i don't have a "create account", and only can loggin with the default<EMAIL_ADDRESS>[02:47] <wgrant> That's right. It's set up as a development instance, not a production one.
[02:47] <wgrant> Unless you know the application well and are really sure that you want to run your own, you *do not* want to run your own.
[02:47] <wgrant> It's no small undertaking.
[02:48] <maxh> If you ARE really sure you want to run your own you still probably don't want to.
[02:48] <wgrant> That's also true.
[02:50] <emilio> yeah but you said "it's set up as a development instance, not a production one.", so i need do make another build to set up for production?
[02:51] <wgrant> Yes.
[02:51] <wgrant> But there are no instructions for that, and you don't want to do it.
[02:51] <emilio> oh ok.
[02:52] <emilio> ty for your attention!
[02:56] <nigelb> wgrant: you mean its impossible to set up a production instance?
[02:57] <wgrant> nigelb: Not impossible. But you need to know what you're doing, or to have access to wiki.canonical.com.
[02:57] <wgrant> And then you still need to know what you're doing.
[02:57] <nigelb> :(
[02:57] <nigelb> Its supposed to be oss :(
[02:57] <wgrant> Not impossible: just difficult and in most cases foolish.
[02:57] <maxh> (Now watch as 124 people attempt to go to said wiki.)
[02:57] <nigelb> heh
[02:58] <wgrant> Heh.
[03:00] <wgrant> Vostok may change everything, however.
[03:01] <nigelb> Vostok?
[03:01] <wgrant> The derivative distro management tool that Linaro is developing.
[03:01] <nigelb> oh, its based on LP?
[03:01] <wgrant> At the moment the plan is for it to be an alternative UI onto a subset of Launchpad, which OEMs can run locally.
[03:01] <wgrant> And it will probably interact in some ways with Launchpad.net.
[03:02] <maxh> How exactly does Launchpad determine how to link to PGP key pages? I'm getting results for '0xdc471ac2d963ea539409322b6926ebb2c16905f0', which shows my key, but not all the addresses I've added in the past... however long since I uploaded the key, whereas results for '0xc16905f0' (which is obviously the same) shows all addresses.
[03:07] <wgrant> maxh: The former is the fingerprint. They both show the same list of addresses for me -- I suspect the URLs you checked differ another way.
[03:07] <wgrant> (note that the lst eight hexadecimal degits of the fingerprint are your key ID)
[03:08] <maxh> I just manually replaced the relevant portion of the URL to make sure it's otherwise the same. The fingerprint gets two addresses listed, and the key ID gets four.
[03:08] <wgrant> Aha. Looks like the build queue might finally be empty in a day or two!
[03:09] <wgrant> maxh: Hm. In both cases for me the four addresses are listed.
[03:10] <maxh> Well, I suppose if it works elsewhere, it doesn't matter if I see it correctly, since I already have it.
[04:24]  * achiang wonders if anyone knows how to get to a private PPA using the API
[04:25] <wgrant> achiang: Same as a public PPA.
[04:26] <wgrant> getPPAByName should work.
[04:27] <achiang> wgrant: ah! thanks, i didn't see that method. i was poking around the people.archive attribute
[04:27] <wgrant> achiang: That's from the days when people had only one PPA.
[04:27] <wgrant> It just grabs the first one.
[04:27] <achiang> nod, got it, thanks
[06:08] <achiang> anyone want to take pity on a git user who's struggling with bzr?
[06:08] <achiang> in git, my working model is: many logical branches in the same physical source directory
[06:08] <achiang> and then i just move between branches with git checkout
[06:09] <achiang> what's the equivalent in bzr?
[06:11] <wgrant> achiang: #bzr may be more help, but for most projects I have a project directory, with each branch as a separate directory inside that. You can get a system similar to git by using something like bzr-colo, but for non-gigantic projects I see little point.
[06:11] <wgrant> So I'll do something like this to set up a project:
[06:12] <wgrant> mkdir project
[06:12] <wgrant> cd project
[06:12] <wgrant> bzr get lp:project trunk # Will get the default branch from LP, and put it in the 'trunk' directory locally
[06:12] <wgrant> bzr branch trunk my-feature-branch
[06:13] <wgrant> That will create a new directory, my-feature-branch, as a branch from trunk.
[06:13] <wgrant> You can then hack around in there.
[06:14] <achiang> wgrant: and then to push my-feature-branch, i cd into that directory and... what: bzr push lp:project/my-feature-branch ?
[06:16] <wgrant> achiang: bzr push lp:~username/project/my-feature-branch
[06:16] <wgrant> It will then remember that URL for subsequent pushes.
[06:16] <wgrant> You can also later configure bzr to automatically calculate that URL, so you can just 'bzr push' from a new branch.
[06:20] <achiang> wgrant: thanks
[07:17] <MTecknology> So this package has been hovering between 4 second and 4 minutes until it's time to build - for over an hour
[07:17] <MTecknology> I think the math is a little mucked up for some reason.. :P
[07:17] <wgrant> MTecknology: The maths is fine... the buildd manager is not :(
[07:18] <MTecknology> wgrant: what's up with it?
[07:18] <wgrant> MTecknology: It is very much not a fan of having large build queues and lots of builders building lots of small builds.
[07:19] <MTecknology> wgrant: oh- mine is probably about as small as there is :P
[07:19] <wgrant> It sort of ends up taking 180 times longer than expected -- 15 minutes to complete one cycle, instead of 5 seconds.
[07:20] <MTecknology> heh.. that's a bit of a difference
[07:20] <MTecknology> I see that the queue is about half now though
[07:21] <wgrant> Right, the queue is shrinking.
[07:21] <MTecknology> yay for positives
[07:21] <wgrant> Assuming nobody decides that they need to throw another 2700-build Python rebuild onto the queue and then delete it as soon as it's finished, we should have a reasonable queue in 24-48 hours.
[07:22] <MTecknology> wgrant: and then delete it??
[07:22] <wgrant> MTecknology: In the last week we have had two or three rebuilds of Python 2.7 and everything that depends on it.
[07:22] <wgrant> This takes a couple of days of build farm time.
[07:22] <wgrant> The PPAs were then mysteriously deleted.
[07:22] <wgrant> And a fourth one has been created, but is not yet building, and if it does start building then people are probably going to start strangling other people :)
[07:23] <MTecknology> wgrant: ..yucky
[07:23] <MTecknology> only word I could think of
[07:24] <wgrant> I would have chosen something more violent.
[07:24] <wgrant> But yes.
[07:24] <MTecknology> why four rebuilds?
[07:24] <wgrant> I do not know.
[07:24] <wgrant> There was probably some mistake in the first three.
[07:24] <wgrant> Which they didn't discover until they had built EVERYTHING.
[07:25] <MTecknology> shoulda build it locally first :)
[07:26] <MTecknology> pbuilder ftw (on a hefty hefty machine)
[07:27] <MTecknology> wgrant: so if I went along and decided to rebuild all of python and perl and firefox/xul - would you come over here and kill me?
[07:33] <bilalakhtar> noodles775: my daily build is pending from the last 4 days
[07:34] <bilalakhtar> https://code.edge.launchpad.net/~bilalakhtar/+recipe/daily-builds-test
[09:12] <bilalakhtar> noodles775: Back. Power cut over here
[09:13] <wgrant> bilalakhtar: The build queue has been horrific for the last weekish. It should return to normal in the next day or so.
[09:13] <wgrant> .... if the buildds ever come back.
[09:13] <bilalakhtar> hanks wgrant
[09:13] <bilalakhtar> thanks
[13:06] <rioch> I've made a release out of one of my milestones, and that milestone has some bugs set to "Fix committed". Will they automatically be set to "Fix released"?
[13:15] <geser> IIRC no
[13:16] <wgrant> No. We had that for a while, but it proved to be too slow, so it was switched off.
[13:17] <lifeless> wgrant: ?
[13:18] <wgrant> lifeless: Milestoned bugs used to be closed when the milestone was released. But that had to be disabled, as it timed out for large milestones.
[13:19] <lifeless> bah
[13:19] <lifeless> I've requested rabbit be installed
[13:19] <lifeless> if you want to write up a out-of-transaction task for it, please do.
[13:20] <wgrant> lifeless: Ha ha ha.
[13:20] <wgrant> We won't see a message queue for at least two years yet...
[13:20] <lifeless> why ?
[13:20] <wgrant> Because it's been proposed a few times in the last 18 months, and never happened.
[13:21] <lifeless> check lp-developer-dependencies
[13:21] <wgrant> Oh, yes, I know it's in there.
[13:21] <wgrant> It doesn't mean it's going to be on production or in the code any time in the next decade.
[13:21] <lifeless> right
[13:21] <lifeless> I'll be surprised if we don't have the staging instance up next week
[13:22] <wgrant> Ooh.
[13:22] <wgrant> This is is good news indeed.
[13:23] <wgrant> You've not left Prague yet?
[13:23] <lifeless> platform sprint next week
[13:23] <lifeless> GNU hackers meeting after that.
[13:23] <lifeless> Then home.
[13:23] <lifeless> sorry, 'platform rally'
[13:23] <wgrant> Oh, right.
[13:24] <lifeless> 200 ppl in one room is not a sprint
[13:24] <lifeless> anyhow
[13:24] <wgrant> Heh.
[13:24] <lifeless> amqplib
[13:24] <lifeless> play with it.
[13:24] <lifeless> doit.
[13:29] <wgrant> I hate bad tests.
[13:31] <lifeless> jml: http://pypi.python.org/pypi/contextdecorator/0.10.0
[13:37] <jml> wgrant, hello
[13:39] <wgrant> jml: Hi.
[13:42] <lifeless> wgrant: so do I.
[13:43] <lifeless> wgrant: lets fix them
[13:43] <wgrant> lifeless: Oh, I'm rewriting this batch, don't worry.
[13:43] <wgrant> It's just infuriating how bad the Soyuz tests are.
[13:44] <lifeless> jml: http://www.mypressi.com/
[14:10] <geser> is there some ready vm-image for LP development? I planned to setup LP for development (in a chroot or vm as I want to have it seperate from my normal system) but didn't find time to do it
[14:11] <wgrant> There's no pre-built image, but there's https://dev.launchpad.net/Running/VirtualMachine
[14:23] <infinity0> how do i delete a contact email from my launchpad login service account? (as opposed to launchpad itself)
[14:24] <wgrant> infinity0: Despite the name, that's not actually part of Launchpad -- it's developed and managed by another team entirely.
[14:24] <infinity0> oh
[14:24] <wgrant> At the moment it's not possible to remove email addresses. However, I saw some bugmail this morning which suggests that it's fixed in the next release.
[14:24] <infinity0> oh, ok, thanks
[14:24] <infinity0> any estimate of a timeframe on that?
[14:24] <wgrant> No idea, sorry.
[14:25] <wgrant> Bug 507214
[14:25] <infinity0> cool, thanks
[14:26] <wgrant> It's targetted to 2.7.0, which is scheduled for the 22nd.
[14:26] <wgrant> Not sure how reliable that is, though.
[15:19] <MysteryX> Can I host my own, closed-source, software on launchpad for a fee? (or even without one?)
[15:22] <nigelb> for a fee, yes
[15:23] <MysteryX> good
[15:25] <MysteryX> I'll host my websites source there
[18:49] <d1b> morning - is there a way to view all source repos for a project
[18:49] <d1b> like i can do with say a gitweb representation (or hg)
[18:50] <thumper> d1
[18:50] <thumper> d1b: hi
[18:50] <d1b> MORNING
[18:50] <thumper> d1b: things are somewhat different on Launchpad than git or hg
[18:51] <d1b> eg http://bazaar.launchpad.net/~zeitgeist/
[18:51] <thumper> d1b: for a project to look at the branches for the project, go to https://code.launchpad.net/<project>
[18:51] <d1b> nothing is there
[18:51] <d1b> thumper: :/
[18:51] <thumper> that is a person or team
[18:51] <thumper> not a repository
[18:51] <d1b> http://bazaar.launchpad.net/~zeitgeist/zeitgeist/trunk/files
[18:51] <d1b> ...
[18:51] <d1b> but i can't view http://bazaar.launchpad.net/~zeitgeist/zeitgeist/
[18:51] <thumper> http://code.launchpad.net/~zeitgeist
[18:51] <d1b> why not?
[18:52] <thumper> d1b: because we haven't set it up that way :-|
[18:52] <thumper> the filesystem isn't what you see
[18:52]  * d1b grumbles about usability
[18:52] <d1b> ok i never was linked at any point to
[18:52] <d1b> http://code.launchpad.net/~zeitgeist
[18:52] <d1b> or code.launchpad.net
[18:52] <d1b> so without coming on irc
[18:52] <d1b> how would i have found that page?
[18:52] <d1b> neva
[18:52] <thumper> d1b: the branch name is a hyperlink on the bazaar.launchpad.net site
[18:53] <thumper> d1b: which takes to the LP page
[18:53] <d1b> thumper: from the launchpad site
[18:53] <d1b> oh god
[18:53] <thumper> we could do better here
[18:53] <d1b> sorry yes i did
[18:53] <d1b> weird - maybe it was because i came through edge?
[18:54] <d1b> ok
[18:54] <d1b> so what happened was i hit
[18:54] <d1b> https://code.launchpad.net/zeitgeist-project
[18:55] <d1b> thumper: sorry you are correct
[18:55] <d1b> i haven't got much sleep
[18:55] <d1b> my applogies
[18:55] <thumper> d1b: the usability still sucks
[18:55] <thumper> and I accept that
[18:55] <d1b> i just had problems finding the correct zeitgiest page i wanted
[18:55] <thumper> we do need to work on it
[18:55] <d1b> like i was on one of them
[18:55] <d1b> and i wanted to go up a dir / thing and view for al lof them
[18:55] <thumper> d1b: can you file a bug for me?
[18:56] <thumper> d1b: file it on launchpad-code
[18:56] <d1b> let me nail down the behaviour i want
[18:56] <thumper> ack
[18:56] <d1b> so i ened up https://launchpad.net/zeitgeist there
[18:57] <d1b> sorry wrong entry point
[18:57] <d1b>  https://launchpad.net/gnome-activity-journal --> to view the code --> wanted to see where the zeitgeist stuff was
[18:58] <d1b> mm this is not a problem that is fixable - but the solution would be neat
[18:58] <d1b> if launchpad was able to do ctags but like for python - where the dev could give it hints that would have been a solution
[18:59] <d1b> sort of like - the registered branches thing but extending on that
[19:00] <d1b> thumper: anyways - when i click on the link from the code page i as a user expect to see the files and not the project page for a branch
[19:00] <d1b> that may be 'wrong'
[19:01] <d1b> in any case pages like
[19:01] <d1b> https://code.launchpad.net/~zeitgeist/zeitgeist/magic
[19:01] <d1b> should have the  View the branch content --> larger
[19:01] <thumper> d1b: very soon (hopefully) it'll be more obvious
[19:01] <d1b> awesome
[19:01] <thumper> I want to move to make the code browsing and history more a part of Launchpad
[19:01] <d1b> oh neat
[19:02] <thumper> but right now it has too much in the way of memory leaks, excessive memory usage, and bad caching
[19:02] <d1b> what about integrating bugs to code?
[19:02] <thumper> we're working on that
[19:02] <d1b> awesome
[19:02] <thumper> what do you mean by "integrating bugs to code"?
[19:02] <d1b> when i fix a bug, and in the commit i say "this fixes foo"
[19:02] <d1b> and then i close a ticket
[19:03] <thumper> ah, the related bug status setting
[19:03] <d1b> or saying "this is fixed in commit number xyz"
[19:03] <thumper> it's on my hit list
[19:03] <d1b> awesome
[19:03] <thumper> howevery my hit list is kinda long
[19:03] <thumper> a big feature for us right now is building directly from a branch into a ppa
[19:03] <d1b> also
[19:03] <d1b> why is it that http://bazaar.launchpad.net/~zeitgeist/zeitgeist/magic/annotate/head:/zeitgeist-daemon.py
[19:04] <d1b> for example shows me the revision it was changed - but i can't view who the author was?
[19:04] <d1b> nor the date
[19:04] <thumper> really?
[19:04]  * thumper clicks
[19:04] <d1b> no i mean i have to click on it
[19:04] <thumper> d1b: just mouse over and pause
[19:04] <d1b> yes but i would prefer to be able to see that without doing that
[19:05] <thumper> that content would be really repetitive
[19:05] <d1b> oh i meant as an optional thing
[19:08] <d1b> oh wait what?
[19:08] <d1b> there is no search
[19:08] <d1b> hehehe
[19:08] <d1b> but bzr-search no?
[19:08] <thumper> when loggerhead stops being such a memory hog, we may integrate it
[19:08] <thumper> but yes, it is feasible
[19:08] <d1b> well that's where gitweb /hg thingy are at :/
[19:09] <d1b> thumper: out of interest could you link me to the code that does this that "leaks"
[19:09]  * thumper shrugs
[19:09] <thumper> d1b: lp:loggerhead
[19:09] <d1b> ... im not so good with lp:loggerhead stuff
[19:10] <d1b> i mean i need a url ;P
[19:10] <thumper> if it was any more specific, we'd have fixed it by now
[19:10] <thumper> bzr branch lp:loggerhead
[19:10] <d1b> sorry i think i need bzr 2 or something no?
[19:10] <thumper> yes
[19:11] <d1b> not going to happen ^^
[19:11] <thumper> why?
[19:11] <d1b> debian lenny
[19:11] <d1b> and virtualbox is currently foobared on me
[19:11] <d1b> http://bazaar.launchpad.net/~loggerhead-team/loggerhead/trunk-rich/files/head:/loggerhead/
[19:11] <d1b> right location?
[19:11] <thumper> should be
[19:12]  * thumper goes to grab more fud
[19:12] <d1b> i take it i can't get a 'snapshot'
[19:12] <d1b> from the interface like i can in hg and gitweb
[19:14] <d1b> http://bazaar.launchpad.net/~loggerhead-team/loggerhead/trunk-rich/annotate/head:/loggerhead/config.py ... :/ def _level_to_int_level(value):
[19:14] <d1b> ..... omg
[19:15]  * d1b ok sleep time
[19:15] <thumper> night
[19:23] <d1b> thumper: question does the memory leaking occur with threads only - or does it also occur without
[19:23] <thumper> d1b: I've not looked into it much
[19:24] <d1b> thumper: well i would be interested
[19:24] <d1b> is it even possible to run it without threading?
[19:24] <d1b> sure i could 'mock' threading but
[19:25] <thumper> d1b: it is just a wsgi app
[19:25] <thumper> so sure you could using the python reference impl
[19:27] <d1b> also haaha - why only so so few commits per a page
[19:27] <thumper> hey, I didn't write it
[19:27] <thumper> I'm just kinda responsible for it in LP
[19:28] <d1b> heeh
[19:28] <thumper> there is a loggerhead mailing list with other devs hosted through LP I think
[19:28] <thumper> if you are seriously interested in getting involved with loggerhead, start there
[19:30] <d1b> not really
[19:30] <d1b> i have already seen too many things that hurt my eyes
[19:32] <thumper> heh
[19:32]  * d1b crawls back to github
[19:34] <d1b> don't you love it when people go and close stdin, then mark stderror ...... oh nevermind
[19:34] <rockstar> thumper, where are you?
[19:34] <thumper> rockstar: LHR
[19:35] <rockstar> thumper, ah.  I thought you were headed straight to Singapore from here and thought "That was quick."
[19:35] <thumper> heh
[19:35] <thumper> no
[19:35] <thumper> and it is hong kong


[00:48] <Epx998> its too bad i cannot pxe boot my pi3
[00:53] <TJ-> Epx998: you can do network boot
[00:53] <TJ-> Epx998: see https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/net_tutorial.md
[01:02] <Epx998> think my pi is broken
[01:02] <Epx998> there is no standard pw for ub16 arm if you dont preseed is there?
[01:07] <TJ-> Epx998: I don't think so, it's either blank or 'ubuntu' I think
[01:08] <Epx998> hmm ill try ubuntu
[01:08] <Epx998> this arm64 box is wonky
[01:11] <Epx998> hmm nope
[01:12] <Epx998> aha ubuntu/ubuntu
[01:29] <Epx998> heh restarting the network after adding interfaces hung the system
[01:29] <sarnold> did you do /etc/init.d/networking restart or its moral equivalent?
[01:30] <Epx998> service networking restart in the console, this hardware is bad - its not ubuntu at all
[01:30] <Epx998> im not a fan of this qualcomm eval
[01:30] <sarnold> at least ubuntu doesn't handle "service networking restart" real well. I'm guessing debian doesn't handle it well either.
[01:38] <Epx998> ill do it the proper way going forward
[01:38] <Epx998> this server takes 5 minutes to restart
[01:41] <Epx998> heh its just spamming Ubuntu 16.04, guessing thats the prompt who knows -> https://gist.github.com/anonymous/309b9d3c30ea565b3af4c9fa49489d5a
[01:42] <sarnold> crazy
[01:44] <Epx998> its doing it again
[01:48] <TJ-> is that via a serial console or something else?
[01:51] <Epx998> yeah
[01:51] <Epx998> it came up eventually
[01:52] <Epx998> ipmi
[05:55] <cryptodan> anyone running Dovecot, Postfix, and SASL successfully on Ubuntu Server 16.04?
[06:49] <cpaelzer> good morning
[07:06] <lordievader> Good morning
[07:07] <cpaelzer> hiho lordievader
[07:08] <lordievader> Hey cpaelzer How are  you doing?
[07:08] <cpaelzer> fine, and you?
[07:08] <lordievader> Doing good here, spitting through puppet emails -.-
[09:47] <jamespage> coreycb: hmm we're starting to trip on debhelper >= 11~ for the queens UCA
[10:30] <jamespage> cpaelzer: hi - this was the qemu-block-extras  thingmy right?
[10:33] <jamespage> cpaelzer: replied to your email
[10:34] <cpaelzer> hi jamespage
[10:34] <cpaelzer> no this is "another one"
[10:35] <cpaelzer> but in a simimlar spirit I'd say
[10:35] <cpaelzer> jamespage: think of it as "the qemu-block-extra" thing but for libvirt storage support
[10:35] <cpaelzer> jamespage: I discussed with coreycb yesterday and started as we did on qemu-block-extra
[10:36] <cpaelzer> with making the suggest a recommend (for now)
[10:36]  * cpaelzer reading mail ...
[10:36] <jamespage> cpaelzer: +1
[10:37] <jamespage> that's basically what I said :-)
[12:58] <DammitJim> what does this do? Unattended-Upgrade::Allowed-Origins {
[12:58] <DammitJim>         "${distro_id}:${distro_codename}";
[12:58] <DammitJim> I don't want anything to be updated automatically on my servers
[12:59] <coreycb> jamespage: saw that with debhelper, need to figure that out. maybe we can move those packages back to 10.
[13:00] <coreycb> jamespage: most of b3 is uploaded.  keystone has 1 test failure i'm trying to figure out and i'm creating a heat-dashboard package since that's been split from horizon. i left you gnocchi.
[13:10] <rbasak> DammitJim: "I don't want anything to be updated automatically" -> "I want to keep my servers insecure"
[13:10] <rbasak> You should install security updates.
[13:10] <rbasak> 99% of people who disable updates do not.
[13:10] <rbasak> But if you insist, you can remove the unattended-upgrades package. That's probably the easiest way.
[13:10] <rbasak> Alternatively, disable unattended-upgrades in /etc/apt/apt.conf.d/20auto-upgrades
[13:11] <rbasak> Then the Allowed-Origins setting won't matter.
[13:21] <jamespage> coreycb: ta (for gnocchi)  I'll do that work PM today and re-introduce the py2 gnocchi package for tobasco
[13:21] <DammitJim> rbasak, I have to test them before I roll them out
[13:22] <DammitJim> rbasak, how do I disable unattended-upgrades in /etc/apt/apt.conf.d/20auto-upgrades ? comment everything out?
[13:42] <rbasak> DammitJim: as long as you do roll them out promptly, every time. What I'm saying is that I get the impression that 99% of the people who disable for this reason actually end up neglecting the roll out and leave everything vulnerable, which is also quite hostile to others on the Internet too.
[13:42] <rbasak> DammitJim: APT::Periodic::Unattended-Upgrade "0"; presumably
[13:43] <DammitJim> rbasak, that is very true!
[13:43] <DammitJim> we are on a schedule... it's weird
[13:44] <DammitJim> when something really critical comes out, I have to manually go through stuff
[13:44] <rbasak> DammitJim: you should have it all automated
[13:44] <rbasak> DammitJim: automated deployment tests, and automatic rollout of security updates if green.
[13:44] <DammitJim> the problem is that some of those updates will fill up your /boot partition also
[13:45] <rbasak> DammitJim: "apt autoremove" (optionally with --purge) should work well nowadays.
[13:45] <rbasak> (to clean /boot)
[13:45] <DammitJim> what is the configuration for that to be done automatically when it runs the critical update?
[13:45] <rbasak> For what to be done automatically?
[13:45] <DammitJim> autoremove
[13:46] <DammitJim> because your /boot partition will get full otherwise
[13:46] <rbasak> Unattended-Upgrade::Remove-Unused-Dependencies
[13:46] <rbasak> See 50unattended-upgrades
[13:46] <rbasak> But test that first.
[13:46] <rbasak> Depending on how you've deployed, autoremove may remove extra stuff (if you don't have what you need marked as manual)
[13:46] <rbasak> Because many people deploy in non-standard, unsupported ways.
[13:46] <DammitJim> I had that set on a server I tested this on and it never cleaned up /boot
[13:47] <rbasak> Did "apt autoremove" do it?
[13:47] <DammitJim> but maybe I need to do more testing
[13:47] <rbasak> How was the server installed?
[13:47] <DammitJim> so, you might be right and I have a weird setting
[13:47] <DammitJim> it's from a template
[13:48] <rbasak> Depends on what you mean by "template". Users often hack up their own deployment systems which are subtly broken in some way.
[13:48] <DammitJim> I could have possibly done that
[14:43] <jamespage> coreycb: my head is still a bit fuzzy so going to work through the bom failures for queens pm today
[14:44] <coreycb> jamespage: great, thanks
[14:44] <coreycb> jamespage: keystone's uploaded. just working through heat-dashboard.
[14:45] <jamespage> coreycb: awesome
[14:49] <rh10> guys, how can i find out - what processes exactly in buffer/cache?
[14:53] <Ussat> I 100% disagree with automated updates, I have that off on all systems
[15:09] <dpb1> I used to feel that way.  But, I found that the vast majority of upgrades worked great for me on ubuntu, and taking the stance of security first helped me get over that hump.
[15:13] <Ussat> I have monthly a monthly main downtime for my systems...
[15:13] <Ussat> maint
[15:13] <dpb1> fair enough, good discipline to have
[15:14] <Ussat> Ya, I know I am lucky that way, I basically built our Linux infra from zero, so built that in from the start
[15:14] <Ussat> Said "this is how it is" and my director backed me up
[15:16] <dpb1> msft set the model with it's patch tuesday.  But, what do you do about the out of band hot security items?  just wait?
[15:17] <Ussat> dpb1, depends on the vuln and how me and the sec team here determine how bad we are effected.
[15:18] <Ussat> if it requires an immediate patch/reboot, well, we do that. TBH in this env not a lot does, 99% of my systems are not public facing and are VERY locked down
[15:18] <Ussat> or I may sechedule a week out, it really depends on the issue it addresses
[15:20] <Neo4> what is crontab?
[15:21] <Neo4> for example I want create scraper and put there data using php, can I do it?
[15:21] <Neo4> * * * * * wget -q -O - http://google.com  >/dev/null 2>&1
[15:24] <jamespage> coreycb: hmm after fixing three debehlper downgrades, going todo a backport
[15:24] <jamespage> debian have something in bpo which is close enough
[15:24] <rbasak> Ussat: sounds like you're part of the 1% that actually follows through :)
[15:25] <coreycb> jamespage: ok
[15:25] <Ussat> rbasak, I work in healthcare/edu we are pretty regulated....
[15:26] <Neo4> does exist difference  between curl and wget?
[15:26] <Neo4> why we install curl if we can use wget?
[15:26] <rbasak> Here in the UK, healthcare is also pretty regulated but they still run tons of XP and the NHS were infected by that ransomware not long ago. I'm not sure regulation and security are correlated :)
[15:27] <rbasak> Neo4: relatively little difference from a user point of view. Use whichever you prefer.
[15:27] <Ussat> rbasak, true, but at least here we try to keep a tight grip on things
[15:28] <Neo4> rbasak: I try bread down php code there however used exec function and installed crontab and this wget
[15:28] <Neo4> code is very complicated, can't understand how it works...
[15:29] <Neo4> it seems use wget for get ulrs from internet
[15:29] <rbasak> I wouldn't use exec from PHP to call wget or curl. That's pretty dangerous.
[15:29] <Neo4> rbasak: do you know what is crontab?
[15:29] <rbasak> Does PHP have a built in function to do that?
[15:29] <rbasak> Neo4: I do, but please try Google first.
[15:29] <Neo4> rbasak: it has exec() function
[15:30] <rbasak> Neo4: which is dangerous to use from a web app.
[15:30] <Neo4> we can do exec('pwd', $output, $result); and in result should be path to our current dirrectory where is file
[15:30] <Neo4> rbasak: php can run shell commands
[15:32] <Neo4> rbasak: what is dengerous? wget?
[15:32] <Neo4> crontab is dangerous?
[15:35] <rbasak> Neo4: calling exec from a PHP script is dangerous if based on unvalidated input
[15:35] <rbasak> Neo4: search "input validation"
[15:35] <rbasak> Since otherwise an attacker can inject arbitrary shell commands.
[15:45] <Neo4> rbasak: ok
[16:06] <cpaelzer> FYI - Server Team Office hours started - https://wiki.ubuntu.com/ServerTeam/Meeting
[16:07] <cpaelzer> we actually don't mind when questions are asked, but if - for whatever reason - you held back questions, now is the time
[16:07] <cpaelzer> around should be atm rbasak, nacc, dpb1, ahasenack, powersj and myself
[16:07] <ahasenack> o/
[16:09] <ahasenack> cpaelzer: hm, I missed a universe dependency in the new bind9 package
[16:09] <ahasenack> lmdb
[16:09] <ahasenack> I'll check
[16:14] <cpaelzer> sure I saw it in excuses
[16:15] <cpaelzer> but libvirt also complains and it is a false positive
[16:15] <cpaelzer> so I wanted to give britney a chance to overthink things
[16:23] <nacc> o/ as well
[16:25] <ahasenack> cpaelzer: you mean about lmdb?
[16:25] <ahasenack> ah, no, your case is glusterfs
[16:32] <|\n> hello, i was looking for some channel where i could possibly ask a stupid hardware-related question, any hints are appreciated sincerely
[16:33] <nacc> |\n: #hardware?
[16:33] <nacc> !alis | |\n
[16:33] <|\n> ah, thanks nacc
[16:33] <nacc> |\n: can't remember if it's #hardware or ##hardware
[16:33] <|\n> will try both, thanks, i'm slow =)
[16:47] <jamespage> coreycb, beisner: https://www.percona.com/doc/percona-xtradb-cluster/LATEST/howtos/upgrade_guide.html
[16:51] <coreycb> jamespage: seems simple enough. does the package need to run the upgrade commands or can that be left to the user?
[16:51] <jamespage> coreycb: well... I think I see why this is not part of the pkg upgrade
[17:27] <tdb> hi! the xenial daily images here http://cdimage.ubuntu.com/ubuntu-server/xenial/daily/ - when will they start using the newer 4.13 HWE kernel for the installer? I notice 4.13 kernel packages in the install media, but not for running the installer itself
[17:28] <nacc> iirc, isn't that a menu choice?
[17:28] <nacc> powersj: --^
[17:29] <tdb> it is, but the hwe option still uses the older 4.10 kernel
[17:29] <tdb> (as opposed to 4.4, for non-hwe)
[17:29] <nacc> tdb: hrm, i'm not sure how that's decided, powersj would know
[17:30] <tdb> I heard the 16.04.4 release has been put back, which is totally understandable, but I thought the daily builds might be ready for some testing
[17:30] <powersj> looks like the udeb are all still 4.10
[17:32] <powersj> basically those udeb (listed in the list file) need to be updated
[17:33] <powersj> oh wait, I see 4.13 as well :) http://cdimage.ubuntu.com/ubuntu-server/xenial/daily/current/xenial-server-amd64.list
[17:33] <tdb> yeah :)
[17:34] <tdb> that's what made me think the installer itself might be using the newer kernel too
[17:34] <powersj> sure enough uname -a shows 4.10 still
[17:35] <tdb> I have new hardware which won't work with 4.10 :/
[17:41] <powersj> not sure what project makes sense for a bug
[17:41] <dpb1> I'm looking for the same
[17:41] <powersj> ubiquity? syslinux?
[17:42] <dpb1> powersj: https://bugs.launchpad.net/ubuntu-cdimage
[17:42] <powersj> Since the kernel is already there I don't think hwe-linux
[17:42] <dpb1> ?
[17:42] <powersj> yeah
[17:42] <dpb1> tdb: could you please file a bug there and report back?
[17:43] <tdb> I wasn't sure if it was a bug, or just a "not yet done" thing
[17:43] <powersj> it is worth filing to track it in either case
[17:43] <dpb1> +1
[17:43] <tdb> ok
[17:44] <powersj> tdb: and please let us know the bug #
[17:51] <tdb> powersj: 1746304
[17:51] <powersj> tdb: great thanks!
[17:52] <tdb> thanks for your help :)
[18:05] <rlangford77> Where can I find out if ubuntu/canonical has an SNS topic for ami publish events?  Trying to keep things updated response to spectre/meltdown. I'm aware of the cloud image tracker, but we're looking to automate things like we're currently doing for amazon linux
[18:07] <nacc> Odd_Bloke: --^ ?
[19:00] <nacc> rbasak: grr, think i found a bug in debian_support.py's Version regex :/ upstream_version for e.g. 57ubuntu1 gets set to '57ubuntu1'
[19:00] <nacc> :)
[20:08] <Pinkamena_D> I have been using x2go+xfce4 for remote desktop connections but sometimes it is very slow, esp with internet browsers / any transitions. Is there any faster remote desktop software you would recommend? I like evrything about x2go except for the performance issues.
[20:09] <sarnold> how does x2go compare to plain old ssh -X ?
[20:14] <dpb1> Xrdp is an option.
[22:27] <rbasak> nacc: that's a native package. It it supposed to be a debian version only in that case? I don't recall the spec.
[22:27] <nacc> rbasak: yeah, see my MP, i'lll try to find the docs
[22:29] <nacc> rbasak: i guess i should clarify here and there
[22:29] <nacc> rbasak: it is 'correct' by the spec
[22:29] <nacc> but is not at all what anyone wants :)
[22:29] <nacc> since the point is to compare between ubuntu and debian packages
[22:31] <rbasak> nacc: which MP please?
[22:31] <nacc> rbasak: one moment
[22:31] <rbasak> https://code.launchpad.net/~usd-import-team/usd-importer/+git/usd-importer/+ref/master/+activereviews is rather crowded right now :-/
[22:31] <nacc> rbasak: https://code.launchpad.net/~nacc/usd-importer/+git/usd-importer/+merge/336870
[22:31] <rbasak> nacc: or actually, which MP do you want me to look at first right now?
[22:32] <nacc> rbasak: https://code.launchpad.net/~nacc/usd-importer/+git/usd-importer/+merge/336645 is the one i need the most help with
[22:32] <nacc> rbasak: and is probably chronologically the most urgent (so we cann start phasing main)
[22:32] <rbasak> OK
[22:33] <nacc> rbasak: iiuc, you're under the weather, though, so take care of yoursellf first :)
[22:33] <dpb1> nacc: +1
[22:33] <rbasak> I'm wide awake and alert right now
[22:33] <nacc> loll
[22:33] <rbasak> So I might as well look :)
[22:34] <nacc> rbasak: if you want to chat about it, just let me know
[22:34] <rbasak> ack
[22:34] <dpb1> rbasak: :)
[22:40] <nacc> rbasak: if you are around, though, I did have one question for you that is probably easiest to do in a HO
[22:43] <rbasak> I'm around but not really in a position to join a HO
[22:44] <rbasak> IYSWIM :)
[22:44] <nacc> rbasak: i do :)
[22:44] <nacc> not urgent, so that's fine
[22:44] <rbasak> nacc: for that MP, +1 up to and including 4c6e3c7de1
[22:44] <rbasak> That all looks reasonable, so please put that in a separate MP and land it to avoid another mega MP
[22:45] <nacc> rbasak: oh sure, i can do that
[22:45] <nacc> yeah those were cleanups i pulled up the stack as i went
[22:45] <nacc> rbasak: i'll do that now?
[22:45] <rbasak> sURE
[22:46] <rbasak> nacc: next, in 4c6e3c7de1, what's the reasoning to not use pytest exactly? I don't mind but it feels inconsistent. We're already using pytest when we need to parameterise.
[22:46] <nacc> rbasak: it was from my discussion with powersj
[22:46] <rbasak> (IOW, we have exactly one pattern for parameterisation right now)
[22:46] <nacc> on getting to one model for our testing
[22:47] <nacc> i think he suggested unittest over pytest, but i might be misremembering
[22:47] <nacc> also this way we don't need pytest in the snap..
[22:47] <nacc> but i can switch it back
[22:47] <powersj> heh I've had separate conversations with each of you, but think we reached different conclusions.
[22:47] <nacc> heh
[22:47] <rbasak> I'm open to discussion on this
[22:48] <rbasak> If we can replace everything we're doing with pytest I'm happy to lose pytest entirely.
[22:48] <powersj> when I talked to rbasak last fall it was pytest, as it was very handy, even though other projects were using unittests/nose/etc.
[22:48] <nacc> rbasak: (and i assume you meant a differenrt hash, as that's the one you just hacked)?
[22:48] <nacc> *acked
[22:48] <rbasak> nacc: sorry, 23729b3
[22:49] <rbasak> ...but if we can't drop pytest, then it would be nice to have a consistent set of patterns to use for the different test needs we have in the project.
[22:49] <rbasak> eg. "need parameterisation? Use _this_ pattern"
[22:49] <nacc> right
[22:49] <nacc> to be clear the subTest thing is newer in unittest
[22:49] <nacc> so maybe it wasn't there when you looked before
[22:50] <nacc> and i thnk we could abstract it up one level so it isn't so nest-y/indented
[22:51] <rbasak> In any case, perhaps that's a discussion we need to have.
[22:51] <nacc> yeah
[22:51] <nacc> i guess i preempted it with code :)
[22:51] <rbasak> If we do decide to switch the parameterisation pattern, we'll need to change all the other occurances.
[22:51] <nacc> i also, for whatever reason, found unittest easier to understand then pytest
[22:51] <rbasak> So how about, for now, we keep the existing pattern?
[22:51] <rbasak> Rather than have two in the codebase at once.
[22:52] <rbasak> If we decide to switch patterns, then we can have a single commit switching them all over
[22:52] <rbasak> And the subsequently not use the old pattern again
[22:52] <rbasak> Introducing a second pattern forces a future fix regardless of which way we go
[22:52] <nacc> rbasak: ok, the other thing i found handy is that unittest can do test discovery, perhaps pytest can as well
[22:53] <rbasak> pytest does test discovery by default. So I'm not sure what you mean
[22:53] <nacc> rbasak: right now we have to pass files to pytest
[22:53] <nacc> rbasak: unittest can find them from the modulel
[22:53] <rbasak> You can just give it a directory
[22:54] <nacc> rbasak: https://code.launchpad.net/~nacc/usd-importer/+git/usd-importer/+merge/336877 cleanups only
[22:54] <rbasak> nacc: +1'd
[22:54] <nacc> rbasak: and resubmitted the fixes as dependent o that one
[22:59] <nacc> rbasak: i'll land it once CI passes (I expect it to)
[23:01] <rbasak> OK
[23:13] <nacc> powersj: can i tell tox to use a particular version of python3?
[23:14] <nacc> powersj: i think the CI env (xenial?) has 3.5.1-3, while we use 3.6.3 in the snap, so there might issues
[23:14] <nacc> e.g https://jenkins.ubuntu.com/server/job/git-ubuntu-ci/274/console which passes locally on bionic
[23:15] <rbasak> nacc: for testing the Sources file downloads, verification, etc, I'd either get some small files from the archive (eg. restricted?) and put them in a test directory and use those instead of HTTP, or I'd prepare my own minimal ones, sign them with a test key and adjust the code to verify with the test public key. The test keys would want to be text in the repo though, so there'd have to be a test
[23:15] <rbasak> fixture to import them into a keyring.
[23:15] <rbasak> The latter is cleaner but possibly more work.
[23:15] <powersj> nacc: my understanding is the version of python you want to use has to be installed
[23:16] <nacc> rbasak: ah that's a good idea
[23:16] <powersj> so even if you add a py34 (for 3.4) or py36 in your case, if that version of python is not already installed it will fail trying to find that version of the interpreter
[23:16] <nacc> powersj: so how should i do this? :)
[23:18] <powersj> well do we know for a fact that 3.5 fails? or has consequences for running with it?
[23:19] <powersj> of course testing on the version you are using is probably more important :)
[23:19] <powersj> so we could run tox in bionic a container
[23:19] <nacc> powersj: right, the latter is the relevant point, but let me spin up a xenial
[23:19] <nacc> powersj: right, but that doesnt' really solve the problem, it just punts it furhter into the future?
[23:19]  * powersj thinks he messed up the word order there
[23:20] <powersj> nacc: how so?
[23:20] <nacc> powersj: let's say we envetually move ahead of the bionic python3
[23:20] <nacc> the bionic container doesn't help us :)
[23:20] <powersj> true - we could still use a container and install the version that you are using
[23:21] <nacc> powersj: we build it from source, though, meaning it might not be available as a package
[23:23] <powersj> nacc: I guess I don't see that as an issue we can do the same thing, it only makes testing longer and more complicated
[23:23] <nacc> powersj: ok, i just didn't wannt to have to have our testing infra build python3 every time
[23:23] <nacc> it's not exactly fast
[23:23] <powersj> yeah :\
[23:23] <powersj> I guess the other alternative is install from something close? or try to get your own development stuck to a specific version and if you move we have to move testing as well?
[23:24] <nacc> yep
[23:24] <nacc> powersj: confirmed xenial's python3 does not work
[23:25] <nacc> and there is no python3.6 in xeniall
[23:25] <nacc> hrm
[23:26] <nacc> rbasak: --^ thoughts?
[23:26] <nacc> (i think the big thing is it looks like NamedTuple support is either different or missing)
[23:26] <nacc> possibly in pylint3
[23:26] <nacc> i wondner
[23:26] <rbasak> We should develop and test against whatever version the snap uses
[23:26] <rbasak> Right?
[23:27] <nacc> that would be ideal
[23:27] <nacc> but that wouldl mean every CI job needs to buildl the snap's env
[23:27] <powersj> we could try using pyenv maybe? I haven't played much with it
[23:27] <nacc> outside of the snap
[23:27] <rbasak> Could it be cached somehow?
[23:27] <rbasak> Feels like a fundamental issue with developing a project deploying with snaps
[23:27] <rbasak> Snap upstream should have a solution for us on this
[23:28] <nacc> i'll ask
[23:28] <rbasak> Thanks
[23:29] <nacc> meanwhile, do we want to bump our tox env?
[23:29] <nacc> artful would be sufficient for now
[23:30] <powersj> nacc: when you said didn't work on xenial? was that using python3.6 because it doesn't exist? or something else?
[23:30] <nacc> powersj: tox itself fails on xenial with the branch referred to above
[23:31] <nacc> powersj: because it's using 3.6 features and only 3.5 is available to run
[23:31] <nacc> (we currently just call python3)
[23:31] <nacc> rbasak: if we were to add pylint to our snap, i thinnk we can run the tests as an app
[23:31] <nacc> possiblly using tox itself
[23:32] <rbasak> I have no objection to that
[23:32] <nacc> powersj: if we did that, we'd change the jenkins to something like git-ubuntu.self-test
[23:32] <rbasak> We might need to add pytest though
[23:32] <nacc> yeah
[23:32] <nacc> rbasak: true, if we were to lift up all of CI, that's true
[23:33] <nacc> i was initially just suggesting the bit we know is broken
[23:33] <nacc> but might as well fix it rigth :)
[23:33] <nacc> powersj: if i get you a branch with the corresponding changes, wouldl you be able to do a test CI run with it?
[23:33] <nacc> not sure how easy it is to do a one-off pipelline
[23:36] <powersj> nacc: branch changing the CI?
[23:36]  * powersj is also confused why you are changing how you call tox
[23:37] <nacc> powersj: have a moment for a quick HO?
[23:37] <powersj> yeah
[23:38] <nacc> powersj: i think i can expllain it better that way :) standup-server
[23:52] <nacc> powersj: do you have a link to your script running pytest3?
[23:53] <powersj> nacc: https://github.com/canonical-server/jenkins-jobs/blob/master/git-ubuntu/jobs-ci.yaml
[23:53] <nacc> powersj: ta