[13:31] <jrwren> cmaloney: I found out that they don't live where I thought. They are at Utica Rd near Hayes Rd.
[13:31] <cmaloney> Yeah, that's right by the river.
[13:42] <jrwren> What sounds does a Linux machine make?
[13:42] <jrwren> Only a spinning fan since the audio drivers don't work.
[13:56] <cmaloney> Har har
[13:56] <cmaloney> btw: Happy Birthday and all that, jrwren
[14:21] <jrwren> thanks cmaloney
[15:24] <jcastro> n0p_, I feel like bigalora tonite
[15:36] <jrwren> jcastro: oh sure, the one night I can't crash :p
[15:37] <greg-g> jrwren: happy birthday dude
[15:37] <jrwren> thanks greg-g !
[15:37] <jcastro> heh
[15:48] <jrwren> jcastro: you might see me wandering around there trying beer anyway :p
[15:53] <jrwren> greg-g: now THAT was a political tweet :)
[15:58] <greg-g> jrwren: the "oops, we broke the router trying to spy" one?
[16:19] <jrwren> greg-g: no, the Governor of New York.
[16:33] <cmaloney> Fuck, 2016 PyCon is in Portland Oregon
[16:33] <cmaloney> Now we'll never get rick_h__ back. :)
[16:35] <greg-g> jrwren: I... don't remember that?
[16:41] <jrwren> cmaloney: rick_h should leave pycon behind in favor of gophercon
[16:41] <jrwren> greg-g: it was right when I wrote it here.
[16:57] <cmaloney> jrwren: Bite. Your. Tongue. :)
[17:01] <cmaloney> http://www.metalinjection.net/latest-news/guitarist-malcolm-young-reportedly-not-coming-back-to-acdc
[17:07] <greg-g> jrwren: oh, misunderstood you, got it now :)
[17:08] <cmaloney> which tweet is this?
[17:21] <jrwren> cmaloney: I linked to a NYT article about how their Governor sucks.
[17:21] <jrwren> cmaloney: I found it funny because yesterday I said I don't tweet politics :)
[17:44] <jcastro> jrwren, I'm in tonight if you guys are.
[17:44] <jcastro> I want pizza badly
[17:56] <jrwren> jcastro: Its my birthday. My family is taking me out. We might end up going there for that. But I think we may hit Mani.
[17:56] <jcastro> oh! happy birthday!
[17:57] <jrwren> Thanks!
[18:54] <cmaloney> jcastro: You should go to Royal Oak
[18:54] <cmaloney> I hear they have restaurants there
[18:54] <cmaloney> and then you could meet up for coffee at CHC
[19:42] <cmaloney> I don't understand why people password-protect zip files.
[19:45] <jrwren> why not?
[19:45] <cmaloney> Because it's pointless?
[19:46] <cmaloney> It's like securing your bike with zip-ties?
[19:46] <cmaloney> no pun intended.
[19:47] <cmaloney> It's not real encryption or protection
[19:47] <cmaloney> It's at best an annoyance and at worst an inconvenience.
[22:23] <skellat> cmaloney: Password-protected zip files -- US Treasury's view of securely moving data around via e-mail


[02:21] <uvirtbot`> New bug: #1093934 in puppet (main) "puppetmaster-passenger fails to run" [Undecided,New] https://launchpad.net/bugs/1093934
[03:32] <StashBox> Hi Everyone, is there anyone here that could help me with Samba?
[03:33] <highvoltage> I guess no one will know until you ask your question.
[03:48] <StashBox> not sure if there is an exact question to ask.. I've gone through all the standard setup. Config smb.conf, smbd service is running, but unable to connect from win7 computer.
[03:57] <StashBox> The Win7 computer won't even detect the samba share, entering \\HOSTNAME fails to connect
[13:15] <samba35> i have install tftpd-hpa server and get installed and netstat and service is saying  tftpd ("she") is running but when i try  to telnet localhost 69 its not working why ?
[13:15] <samba35> telnet: Unable to connect to remote host: Connection refused
[13:26] <uvirtbot`> New bug: #1094019 in lxc (universe) "Linux's getdents gets /.. inode number from host system under LXC" [Undecided,New] https://launchpad.net/bugs/1094019
[13:46] <freesbie> tftpd listens on UDP
[14:45] <Error404NotFound> Shameless marketing message: Do you manage backups? Help me by providing your feedback: http://goo.gl/gmmLs
[14:45] <uvirtbot`> New bug: #1094052 in net-snmp (main) "default install of snmpd leaks memory when VLAN interfaces present" [Undecided,New] https://launchpad.net/bugs/1094052
[14:50] <uvirtbot`> New bug: #1094057 in memcached (main) "package memcached 1.4.14-0ubuntu1 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 2" [Undecided,New] https://launchpad.net/bugs/1094057
[17:40] <slyboots> Hello
[17:41] <slyboots> Im curious, anyone here using ZFS within Ubuntu server?  Setting up a fileserver and wondering if its worthwhile going down the zfs route.  ITs for a home-enviroment but still, dont want something thats going to fall over on me
[17:44] <patdk-lap> slyboots, #zfsonlinux
[17:45]  * slyboots nods
[17:50] <Industrial> I have several NodeJS services to run, these are just TCP servers listening on ports. Should I create a new user called web or something to run these servers with? the user needs access to port 80. How do I do that? Can I shield the user from logging in or going anywhere else then the directories where these websites run?
[17:51] <maco> if you set a user's default shell in /etc/passwd to /bin/false they can't get a shell
[17:51] <Industrial> ok
[17:51] <maco> there's also rbash for a restricted bash shell
[17:52] <maco> i believe it restricts them to their home directory
[17:52] <Industrial> but say one of my servers is breached and allows the script to call e.g. child_process.exec(shellcmd)
[17:52] <Industrial> I guess thats not an OS problem ;P
[17:53] <maco> if you "man rbash" there's actually quite a few more restrictions it does
[17:53] <Industrial> maco: if I can't log in with the users, how do I actually run the services with the user?
[17:53] <Industrial> ok
[17:53] <maco> no cd, no commands using a /,  no redirects...
[17:54] <maco> su - user -c command
[17:54] <maco> or sudo -u user command
[17:54] <Industrial> okay
[18:35] <Industrial> maco: so then I just create a /var/www and chown it to the web user?
[18:36] <Industrial> (I won't ever run an apache so I don't think the name clash will matter.. alternatively should I use /var/node or something?)
[18:36] <maco> Industrial: should work. i tend to add a sticky bit and group write so i can add/modify files as my user. the dir doesn't really matter--apache could be configured to some other dir too, after all. i tend to make mine under /srv
[18:38] <Industrial> Right. I'm using a git based deploy system anyway, so I just do the final deploy and run steps with the web user I think ..
[20:29] <PryMar56> using recent lucid, anyway to get KMS with Matrox g550? any vga code on kernel cmdline is ignored also
[20:31] <RoyK> what's kms?
[20:31] <PryMar56> need 1360x768 (LCD TV)
[20:31] <PryMar56> kernel mode setting
[20:32] <RoyK> dunno - sorry
[20:32] <PryMar56> I run ubuntu-server gateway/router/web on a box next to my TV and it does mp3 into my home theatre also
[20:33] <PryMar56> abraca/xmmsd
[21:18] <salik> hi all!


[00:00] <henrik_> then download the source of the kernel, sudo apt-get install linux-source
[00:00] <henrik_> move in to the right directory.
[00:00] <henrik_> cd /usr/src/
[00:01] <henrik_> then you unpack the source. sudo tar -xjvf linux-source-2.6.31.tar.bz2
[00:03] <henrik_> sudo ln -s /usr/src/linux-source-2.6.31 /lib/modules/$(uname -r)/source
[00:03] <henrik_> go in to your home direcotry and download the latest v4l
[00:04] <henrik_> hg clone http://linuxtv.org/hg/v4l-dvb
[00:04] <henrik_> enter the directory v4l-dvb
[00:05] <superm1> you actually need the source too?
[00:05] <superm1> that doesnt sound right
[00:05] <henrik_> then do sudo make menuconfig, remove the fire dtv
[00:05] <superm1> henrik_, i'm not sure about scan issues btw
[00:05] <henrik_> I needed it..
[00:05] <superm1> you were probably missing one more headers package then
[00:06] <superm1> linux-headers-2.6.31-15-generic
[00:06] <superm1> that would have done the trick
[00:06] <superm1> or linux-headers-$(uname -r)-generic better yet
[00:06] <mechcozmo> so, sudo apt-get install linux-headers-$(uname -r)-generic
[00:07] <henrik_> try that out..
[00:07] <henrik_> don't forget to remove the firedtv in sudo make menuconfig
[00:07] <mechcozmo> E: Couldn't find package linux-headers-2.6.31-15-generic-generic
[00:07] <mechcozmo> easy fix though :-p
[00:08] <mechcozmo> linux-headers-2.6.31-15-generic is already the newest version.
[00:08] <mechcozmo> seems i already have the headers
[00:08] <henrik_> and when you do the sudo make -j3 if you have a dual core.. alot quicker..
[00:09] <mechcozmo> hah, dual core... you think i have a budget...
[00:11] <superm1> if you had that, the missing one was just "linux-headers-2.6.31-15".  there's that and "linux-headers-2.6.31-15-generic". both have to be installed
[00:11] <mechcozmo> doing this as a proof of concept, if it works well, money can be found to make an HD box when we get an HDTV
[00:11] <mechcozmo> right now, it is getting linux-source
[00:11] <henrik__> I got kicked of the server.
[00:12] <henrik__> superm1, it's not the scan issue right now, it's the signal strength
[00:13] <henrik__> I fixed the scan issue, by getting the new v4l and recompiling the kernel..
[00:13] <henrik__> but the cable has about 75% signal strenght messured, and mythtv only says it's 39%
[00:15] <henrik__> mechcozmo, I have been using mythtv for quite some time now.. it has changed the way I live..
[00:16] <mechcozmo> henrik__: hoping to make such an impression here, too
[00:17] <mechcozmo> henrik__: i've got the kernel unpacked and the symlink made... where do i go from there?
[00:17] <henrik__> My kids however have been very spoiled, in there world you never need to look when something is on and then adjust.. they just want to be able to se any show when ever..
[00:17] <henrik__> home directory
[00:18] <henrik__> and download v4l
[00:18] <mechcozmo> ok, so i still need to do that step
[00:18] <henrik__> hg clone http://linuxtv.org/hg/v4l-dvb
[00:18] <henrik__> yes..
[00:18] <henrik__> the step with the source was the step that might could have been avoided..
[00:18] <henrik__> but no harm..
[00:18] <mechcozmo> henrik__: wasn't sure if superm1 was referencing this step or not
[00:19] <henrik__> and he is problebly right, he always is, but I was not able to get it to work that way..
[00:19] <henrik__> this morning..
[00:19] <mechcozmo> don't have hg, do i need to install mercurial?
[00:19] <henrik__> yes
[00:20] <mechcozmo> what is mercurial?
[00:20] <henrik__> a program to check out source
[00:20] <henrik__> cvs program..
[00:20] <mechcozmo> all used to git and svn here...
[00:21] <henrik__> I don't know why some use svn and some hg..
[00:22] <mechcozmo> bah, need to install ncurses
[00:22] <henrik__> v4l has been on hg for as long as I have known..
[00:22] <henrik__> :)
[00:22] <henrik__> yes
[00:22] <mechcozmo> sudo apt-get install ncurses?
[00:22] <henrik__> ncurses-dev
[00:22] <henrik__> even
[00:23] <mechcozmo> k
[00:23] <mechcozmo> trying again...
[00:23] <henrik__> have you checked out v4l?
[00:23] <mechcozmo> yes
[00:23] <henrik__> and make?
[00:23] <mechcozmo> yup
[00:23] <mechcozmo> i am looking at the menu screen now
[00:24] <henrik__> good..
[00:24] <mechcozmo> is the fire dtv somewhere among these menus?
[00:25] <henrik__> under multimedia support
[00:25] <henrik__> in the bottom
[00:25] <henrik__> ops forst multimedia support, then dvb/atsc adapters
[00:26] <henrik__> then in the bottom of that list
[00:26] <mechcozmo> found it
[00:26] <henrik__> just prace space on that module, there are no headers for it so it will halt the next process
[00:26] <henrik__> good!
[00:26] <mechcozmo> any other options to change?
[00:26] <henrik__> just press space on it and the M will be removed
[00:26] <henrik__> nope
[00:26] <henrik__> just exit and save changes
[00:27] <mechcozmo> done
[00:27] <henrik__> what cpu do you have?
[00:27] <mechcozmo> Athlon 2500+ or 2600+
[00:28] <henrik__> only one core right..
[00:28] <mechcozmo> i686 but elderly
[00:28] <mechcozmo> oh my yes
[00:28] <henrik__> then just write make
[00:28] <mechcozmo> no sudo?
[00:28] <henrik__> 'make'
[00:28] <henrik__> no unless you did the hg with sudo
[00:29] <mechcozmo> no
[00:29] <henrik__> then 'make'
[00:29] <henrik__> when that is done 'sudo make install'
[00:29] <mechcozmo> in FreeBSD this process would be "cd /usr/ports/multimedia/v4l; make install clean"...
[00:30] <henrik__> ohh..have not been involved with *bsd
[00:30] <mechcozmo> it's actually annoying how different they are while still being so similar
[00:30] <mechcozmo> i really enjoy working with FreeBSD
[00:30] <henrik__> then sudo make load
[00:30] <henrik__> after that do a cold start..
[00:30] <mechcozmo> it's still making
[00:30] <henrik__> I know :)
[00:31] <henrik__> power off, unjack the power cord.. so it gets in a cold state
[00:31] <mechcozmo> :-p
[00:31] <henrik__> power coard out, and at the same time press the power button
[00:31] <mechcozmo> how long did this process take on your machine?
[00:32] <henrik__> that takes out the power from the conducturs
[00:32] <henrik__> Don't know quite fast
[00:32] <mechcozmo> and what hardware do you have?
[00:32] <henrik__> amd x2 somethign
[00:32] <mechcozmo> ah
[00:33] <henrik__> I just got a new pc for my htpc..
[00:33] <henrik__> I need to have vdpau support
[00:33] <mechcozmo> for HD?
[00:33] <henrik__> yes
[00:33] <mechcozmo> very nice
[00:34] <henrik__> And then I have one hauppauge win nova t-500 and then this 1300
[00:34] <henrik__> So right now I have 3 dvb-t tuners
[00:34] <mechcozmo> this is my grandfather's old PC that i found extra RAM for and an IDE hard drive that wasn't quite dead yet
[00:35] <mechcozmo> how are those HD tuners working?
[00:35] <henrik__> hd tuners??
[00:35] <henrik__> this is no hd tuners..
[00:35] <mechcozmo> they are HD, aren't they?
[00:35] <mechcozmo> oh
[00:35] <henrik__> however they don't really care
[00:35] <henrik__> they can handle mpeg4 and mpeg2 accoring to the hardware in the computer
[00:35] <mechcozmo> then why the need to handle HD?
[00:35] <henrik__> as long as it's not dvb-t2 there is no problem
[00:36] <henrik__> well.. I can watch hd from tv with the card..
[00:36] <henrik__> and I can watch movies thru the system that is in 1080p
[00:36] <mechcozmo> ah, ok
[00:36] <mechcozmo> how do those cards work for you?
[00:38] <henrik__> well the other works really good..
[00:38] <henrik__> I'm just having problem with the 1300 with the signal quality..
[00:39] <mechcozmo> that start recently?
[00:39] <henrik__> If I don't get this solved I might just have to go and get anohter t-500
[00:39] <henrik__> mechcozmo, sorry don't understand
[00:40] <mechcozmo> did the 1300 signal problem start recently, or did it never work well?
[00:40] <henrik__> Just got the damn card..
[00:40] <henrik__> so I have never had it before.. the t500 is my old card
[00:40] <henrik__> my fist digital card
[00:42] <mechcozmo> ah, ok
[00:42] <henrik__> mechcozmo, how is it going.. its getting close to 2am here :)
[00:42] <mechcozmo> henrik__: it is still 'make'ing
[00:42] <henrik__> Was planing on getting some sleep tonight ;)
[00:42] <henrik__> nice..
[00:42] <mechcozmo> up to stage 2
[00:42] <mechcozmo> building modules
[00:43] <mechcozmo> good thing the PVR500 does hardware MPEG-2 or this computer would die so hard... :-p
[00:43] <mechcozmo> do you run frontend separate from the backend?
[00:44] <henrik__> well don't count on it.. the mythtv is quite efficient
[00:44] <henrik__> well my backend also is working as frontend.. but then I have 4 other frontends connected to the backend
[00:44] <mechcozmo> ok
[00:45] <mechcozmo> i have an EPIA MII10000 i am using as a frontend
[00:45] <mechcozmo> thinking about running Mythbuntu off of a 4GB Microdrive i had to save cost, power, and noise
[00:46] <henrik__> will problebly do it for you.. those via is quite nice
[00:46] <mechcozmo> hooray, it is done
[00:47] <mechcozmo> ok, now i need to go find the computer to restart it :-p
[00:47] <henrik__> have you done the sudo make install?
[00:48] <mechcozmo> yes
[00:48] <mechcozmo> and sudo make load
[00:50] <henrik__> good cold start now..
[00:51] <mechcozmo> it is back up
[00:51] <mechcozmo> anything else to do, or scan for channels?
[00:51] <henrik__> just scan for channels
[00:52] <mechcozmo> stopped at "Scanning us-cable 12 No Lock" again
[00:52] <mechcozmo> same issue as before
[00:52] <mechcozmo> signal of 0%, scan 5%
[00:53] <henrik__> I got that before I did the v4l update
[00:54] <henrik__> don't know why it's not working for you sorry..
[00:55] <mechcozmo> bah
[00:55] <mechcozmo> that's a dissapointment
[00:55] <henrik__> yes shure is..
[00:55] <henrik__> sure*
[00:56] <mechcozmo> well, thanks for your help
[00:56] <henrik__> did you have the 1300 card 2
[00:56] <mechcozmo> no, i went for the 500 because it was $50 shipped and i'm a cheap bastard :-)
[00:57] <mechcozmo> i would just sell it and buy what you know works
[00:57] <henrik__> ahh.. okej.. then you were not affected by the bug we fixed..
[00:57] <henrik__> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/439163
[00:57] <henrik__> only for the 1300 3000 and 4000 card
[00:57] <henrik__> I thaught you were on the same card as I was.
[00:58] <mechcozmo> seems similar, but nope
[00:58] <mechcozmo> no, i have just one PVR
[00:58] <mechcozmo> 500
[00:58] <mechcozmo> https://bugs.launchpad.net/mythbuntu/+bug/470756
[01:01] <henrik__> sorry man can't help you! but I know I need to go and sleep..
[01:01] <henrik__> my kids will wake up in 4h wanting something to eat ;)
[01:01] <henrik__> sleep tight youall
[01:01] <mechcozmo> alright, thanks for the attempt
[03:57] <tmkt> anyoine using kbd_i2c as their driver?
[03:57] <tmkt> need to figure out how to get the rest of the keys working
[03:57] <tmkt> very few work right now
[04:00] <eddie128> Hi,   Hoping someone can help explain why mythbackend install from the mythbuntu control panel results in mythbackend running its own gnome user session???
[04:12] <eddie128> hi
[05:13] <superm1> eddie128, its because the upstart script is using 'su'
[05:13] <superm1> its arguable whether the bug lies in consolekit or that upstart script still
[05:13] <superm1> it only happens when you load mythbackend on standard ubuntu
[05:13] <superm1> mythbuntu boxes won't encounter it
[05:26] <eddie128> thanks
[05:27] <eddie128> superm.   Is there a listed 'fix' anywhere that you could point me to?
[05:29] <superm1> look at the bug i posted in #mythtv-users
[05:29] <superm1> there's a workaround
[06:34] <ripperda> hey superm1, got a chance to review over your comments from last night. I have to admit, I'm not very clear what in my config is in storage groups and what isn't
[06:35] <ripperda> so far, I have a single system w/ front & backend  on the same system. when I configured, I set the storage groups on the backend and the frontend config to the same directories
[06:35] <ripperda> so I'm  not clear whether files were stored via the frontend or storage groups
[06:36] <ripperda> I'm thinking maybe I should set the 2 sets differently, maybe even delete all artwork, then I can redownload metadata and see how things get stored
[06:37] <ripperda> I'm reading a couple of web pages on how storage groups interact with mythvideo
[06:38] <superm1> ripperda, generally you want the storage group set items to be the ones in /var/lib/mythtv and the local paths to be in ~/.mythtv
[06:44] <PMantis> Hi, seem to be having lots of trouble downloading. Will a few people please seed the i386 torrent?  http://www.mythbuntu.org/files/mythbuntu-9.10-desktop-i386.iso.torrent
[07:21] <gbutters> PMantis: ok seeding
[08:39] <hume> hi... I recently upgraded to mythbuntu 9.10, and now everytime I start the computer, the sound is switched off. How can I change the sound to be switched ON on boot?
[08:49] <Thermoelectric> Anyone here able to help me with my channel scanning? I have set a grabber and all, but the scan for channels button isn't selectable...
[08:55] <Thermoelectric> Could that possibly be because my tuner isn't supported? It's a swann tuner.
[11:37] <khunt> something weird has happened to my backend
[11:37] <khunt> cant ssh in
[11:37] <khunt> says wrong password
[11:37] <khunt> can run sudo commands directly
[11:37] <khunt> says wrong password
[11:37] <khunt> sorry cant run sudo commands
[11:45] <khunt> what is the mythtv users password?
[11:48] <Thermoelectric> Were you talking to me?
[11:49] <Thermoelectric> Nvm
[11:49] <khunt> talking to anyone
[11:49] <khunt> :-)
[11:49] <Thermoelectric> Oh
[11:49] <Thermoelectric> :-)
[11:50] <Thermoelectric> I messed up by backend somehow too, I can't get it to scan for channels, But that's what would usually happen to amythtv noob.
[11:50] <Thermoelectric> Shouldn't you use your computer's password, not mythtv's?
[11:51] <Thermoelectric> For sudo...
[11:51] <khunt> yes
[11:52] <khunt> if it hadnt decided that password was wrong
[11:52] <Thermoelectric> :-/
[11:52] <khunt> i cant run frontend or do sudo commands
[11:52] <khunt> or ssh in
[11:52] <khunt> I was fine about 3 hours ago
[11:53] <Thermoelectric> Couldn't you use a external monitor on your backend?
[11:54] <Thermoelectric> That would get around the SSH error, I guess, Iirc what SSH is...
[11:54] <Thermoelectric> Hey temba
[11:55] <temba> ?
[11:55] <temba> hey
[11:55] <khunt> how do i change my password when my password doesnt work?
[11:57] <Thermoelectric> Can't help you with that one, sorry.
[12:08] <khunt> figured out
[12:08] <khunt> but cant get into recovery console
[12:10] <Thermoelectric> Hmm
[12:10] <Thermoelectric> You wouldn't happen to know how I can update the driver on my tv tuner? I want to see if that will do anything...
[12:12] <khunt> linux tv website has instructions and drivers i think
[12:14] <Thermoelectric> Thanks
[12:30] <Thermoelectric> Ah, That's right, I was going to try IVTV
[13:31] <tmkt> anyone using ir-kbd-i2c driver?
[14:01] <tmkt> my problem is some of the keys on the remotes work...just not the good ones..like back/guide/info
[15:44] <Thom-> hello guys, could anyone tell me how mythbuntu handles the mythtvfrontend upstart? I couldn't find anything about that in the rc.x folders
[17:56] <dashcloud> hi, I'm currently on 8.10, and would like to move up to the latest version so I can run myth .22- what's the best way to go about this? upgrade, or clean install?
[18:16] <KjetilK> Any chance of seeing the s2-liplianin driver in Lucid? It seems to be maturing well, and it is the driver I use (or should use, I currently use the old mantis) for my DVB-C card
[18:17] <elmojo> when installing mysql-server should I set a  "root" password or leave blank?
[18:17] <elmojo> wondering how the mythtv-* packages know what password to use when they are configured
[21:29] <tmkt> anyone else experiencing a 2-3 minute delay for the remote to start working when the front end starts up
[21:32]  * KjetilK doesn't, but is on 0.21
[21:50] <superm1> elmojo, these days it should get off fine with or without a root password
[21:50] <superm1> the mythtv packages are supposed to try to use the debian system maintainer account to make the database now (hopefully!) :)
[23:23] <elmojo> superm1: k, thanks for the info... I was trying the 0.22-fixes packages on Ubuntu 8.10 and had some issues with mysql permissions
[23:23] <superm1> oh rlly?
[23:23] <elmojo> went ahead and installed 9.10
[23:23] <superm1> that's peculiar
[23:23] <superm1> did they actually fail?
[23:23] <elmojo> yes
[23:23] <superm1> or just say that the pw was wrong?
[23:24] <elmojo> ran dpkg-reconfigure mythtv-database and it always failed saying it couldn't access the database
[23:25] <superm1> right, but was it Really failing?
[23:25] <elmojo> I even removed (and purged) the mysql-server packages and blew away any existing databases and restarted everything from scratch and it still wouldn't work properly
[23:25] <superm1> it's supposed to use the debian-sys-maint account
[23:25] <superm1> i wonder if that didn't exist on 8.10
[23:25] <elmojo> I didn't check the mysql logs (probably should have)
[23:25] <PMantis> Opinions guys? ATI or NVIDIA for an AGP based Mythbuntu frontend?
[23:26] <superm1> nvidia
[23:26] <superm1> you'll have a better experience still today
[23:26] <PMantis> k
[23:26] <elmojo> superm1: you are probably right about the debian-sys-maint account
[23:27] <superm1> it didn't exist?
[23:27] <elmojo> I don't think so
[23:27] <PMantis> I have an nvidia card right now that I can't load the nvidia drivers for. When I activate them, it boots to a black screen... had to hack xorg.conf back to vesa. ICK!
[23:27] <superm1> well maybe our logic needs some fixing then
[23:27] <superm1> PMantis, how did you install the drivers?
[23:28] <superm1> you should either pick them in the installer itself or from the hardware drivers tool
[23:29] <superm1> elmojo, well it checks like this: "    if echo "show databases;" | mysql --defaults-file=/etc/mysql/debian.cnf >/dev/null 2>&1; then
[23:29] <superm1> "
[23:29] <PMantis> superm1: With the restricted drivers gui. I was going to try downloading the binary from nvidia directly, but I tried ubuntu 9.10, 9.04, 8.10... none of them are working right now, so I think my card died.
[23:29] <superm1> if that failed t shouldnt have been able to use the debian-sys-main
[23:29] <superm1> PMantis, you'll run into even more trouble with the binary directly from nvidia
[23:29] <superm1> it conflicts with packaging systems currently
[23:29] <PMantis> superm1: oh fun.
[23:29] <superm1> what card is this?  is the wrong series being offered maybe for your card?
[23:30] <superm1> and does /var/log/Xorg.0.log show any more information about what's up?
[23:30] <elmojo> superm1: ok, I no longer have 8.10 installed so I'll give 9.10 a shot
[23:31] <PMantis> superm1: This used to be a myth frontend and I re-purposed for something else... and it used to work. I didn't look at the log, but I found that I cannot kill the X process without locking the machine to the point where my SSH session locks up.
[23:31] <superm1> PMantis, where the SSH session locks up?  that screams bad hardware
[23:32] <superm1> but look at the log to be sure
[23:32] <superm1> there aren't many instances that the machine hard locks like that though
[23:33] <PMantis> superm1: and... with gdm running, the local screen blinks, like it keeps swapping to tty 7 and back... also it hangs for 2-3 seconds, comes back, hangs... etc. When I kill gdm, it's smooth.
[23:33] <superm1> look at the logs
[23:33] <PMantis> superm1: Yeah. The local kb is dead, SSH dies, but Ctrl-Aly-SysRec-B still reboots.
[23:33] <superm1> that's the important thing here
[23:34] <PMantis> K, I'll have to get back in there and look... it's off right now, and dinner is ready. :)
[23:34] <PMantis> Just had a couple minutes, so I thought I'd pop in and seek feedback.
[23:34] <elmojo> do the latest nightly fixes packages work with 190.42 nvidia packages or does it still require 185.x nvidia?
[23:35] <superm1> 190.42 is on the repo now
[23:35] <superm1> using libvdpau
[23:35] <elmojo> excellent
[23:35] <superm1> and it just got into debian, so we'll have it in the archive for lucid
[23:36] <elmojo> do I need to add anything to /etc/apt/sources to get the nightly builds?
[23:41] <superm1> just install the mythbuntu-repos deb from the website
[23:41] <superm1> it does everything for you
[23:48] <elmojo> superm1: awesome
[23:48] <superm1> tgm4883 did a great job with it, thank him :)
[23:48] <elmojo> everything is working perfect on 9.10
[23:49] <elmojo> the database set-up happened automagically for me
[23:54] <PMantis>
[23:54] <PMantis> heh oops


[00:03] <penguin42> yes, those broadcasting under managers are dangerous
[00:20] <broder> Laney: do you still need a give-back on rhythmbox?
[03:48] <bobweaver> Hello there I am trying to make a ubuntu core installation happen. but for some reason I can not chroot into the mounted /mnt/root I get the error chroot: failed to run command  `/bin/bash': Exec format error. Any ideas what is going on ? Also if this is the wrong channel I am sorry just point me to the correct one thanks a bunch :)
[03:50] <bobweaver> never mind it is the arch that the host live cd is on sorry to waste your time.
[04:20] <scientes> whats the name of the privacy control panel?
[04:20] <scientes> (source)
[04:21] <scientes> gnome-control-center doesn't seem to have it
[04:21] <Chauncellor> Hi, I'm trying to develop a lens for Unity via a quickly template - when I try to install/run it (via sudo quickly install and quickly run) I get errors the lens not being provided by any service files: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name unity.singlet.lens.wikipedia was not provided by any .service files
[04:21] <scientes> (and why does finding out what  programs are in gnome so damn difficult)
[04:21] <Chauncellor> scientes, activity-log-manager
[04:22] <Chauncellor> scientes, my bad, not that....
[04:22] <scientes> i'm just trying to figure out how it does it
[04:22] <scientes> so i can add similar functionality to my application
[04:22] <scientes> (well just an opt-out of zeitgeist)
[04:23] <slangasek> kees: hmm.  does bug #637303 look familiar?
[06:00] <finch> Hello folks, I'm working on a puppet provider for network interfaces, and I have some questions about the allow-hotplug stanza. Is that value used these days, or is everything handled via udev for hotplugged network devices?
[06:25] <vibhav> Can https://bugs.launchpad.net/ubuntu/+source/python-scipy/+bug/655192 be nominated for oneiric?
[06:29] <micahg> vibhav: done
[06:29]  * vibhav hugs micahg
[06:53] <vibhav> The version of python-scipy in oneiric is 0.9.0+dfsg1-1build1 , what should be version for the Ubuntu Delta?
[06:53] <vibhav> micahg: ^
[06:53] <micahg> 0.9.0+dfsg1-1ubuntu0.1
[06:54] <vibhav> remove the build?
[06:54] <micahg> yes
[07:12] <vibhav>  can
[07:12] <vibhav> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/932439
[07:12] <vibhav>                 be nominated for oneiric?
[09:35] <micahg> Daviey: prettytable is trying to pull python-support back into main
[09:44] <Laney> broder: looks like it
[09:45] <Daviey> micahg: nah it aint.
[09:46] <micahg> Daviey: sure, with your upload :)
[09:46] <Laney> or one of you two could do it for me
[09:46] <Laney> ubuntu-build rhythmbox quantal retry
[09:46] <Laney> ^o)
[09:46] <Daviey> micahg: I think you are mistaken :)
[09:46] <micahg> Daviey: I meant that your new upload just fixed it
[09:47] <Daviey> Laney: given back
[09:47] <Laney> cheers boss
[09:47] <vibhav> Can https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/932439 be nominated for oneiric?
[09:49] <jtaylor> vibhav: please prepare 655192 according to https://wiki.ubuntu.com/StableReleaseUpdates first please
[09:51] <vibhav> jtaylor: What is wrong in the debdiff I provided?
[09:51] <vibhav> 655192 according to https://wiki.ubuntu.com/StableReleaseUpdates first  please
[09:54] <jtaylor> the debdiff is fine, but the bug description updated a bit
[09:54] <vibhav> like?
[09:54] <jtaylor> https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
[09:54] <vibhav> Oh wait
[09:54] <Daviey> *sigh* http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673618 .. it's already using dh_python3 .. but refusing to use dh_python2.
[09:55] <Laney> what debdiff?
[09:56] <jtaylor> Daviey: this is to be expected from morph, never mention you're related to ubuntu to him :)
[09:56] <micahg> Daviey: not mostly, actually deprecated: http://article.gmane.org/gmane.linux.debian.devel.python/6948
[09:57]  * Laney fails at voting in the diversity GR
[09:59] <Daviey> jtaylor: he took the python3 patch from us. *sigh*
[09:59] <Laney> perhaps some other member of DPMT could broker a deal
[09:59] <jtaylor> unlikely
[10:00]  * Daviey replies
[10:00] <Laney> is there some kind of team policy around switching from python-support for example?
[10:00] <jtaylor> other dpmt members also refuse dh_python2 patches
[10:00] <vibhav> jtaylor: Not sure what to put in the [Regression Potential] section
[10:01] <jtaylor> vibhav: e.g. low, just adds dependencies
[10:02] <vibhav> jtaylor: done
[10:02]  * micahg would think it should be escalated if the team is being obstructionist
[10:03] <jtaylor> its no release goal in debian to remove pysupport
[10:04] <jtaylor> the python team is not very ubuntu friendly in the first place mainly to how python maintenance is done, I would advise against pouring oil into the fire
[10:04] <vibhav> jtaylor: Is the bug description fine?
[10:04] <jtaylor> just patch it in ubuntu and wait
[10:04] <micahg> yeah, I guess it's not a release goal for wheezy
[10:04] <micahg> maybe for wheezy + 1
[10:05] <micahg> we're still ~700 packages away from being done anyways: http://people.canonical.com/~ubuntu-archive/transitions/dh-python2.html
[10:06] <jtaylor> vibhav: you should also mention why -imaging is added
[10:06] <vibhav> jtaylor: Why did you add -imaging to the recommends?
[10:07] <jtaylor> vibhav: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648036
[10:09] <vibhav> jtaylor: jtaylor Done
[10:09] <vibhav> oops
[10:11] <jtaylor> the latest fftw3 update in unstable pulls in openmpi, that would need patching out in ubuntu?
[10:11] <jtaylor> as its in main
[10:15] <jtaylor> vibhav: looks ok I'll check it later
[10:15] <vibhav> thanks
[10:15] <jtaylor> *upload
[13:57] <Bluefoxicy> it looks to me like Ubuntu doesn't recognize SSD, and thus doesn't put 'discard' into the fs options for SSD partitions
[14:04] <broder> Bluefoxicy: you can set the discard option regardless of whether or not there's an ssd involved - it'll gracefully fallback to a noop if the device doesn't support it, but we're following upstream's decision to leave it "by default until sufficient testing has been done"
[14:04] <Bluefoxicy> broder ah
[14:05] <Bluefoxicy> broder:  what about setting deadline scheduler on SSD?
[14:05] <broder> don't know anything about that
[14:05] <Bluefoxicy> it's supposedly faster than CFQ
[14:06] <Bluefoxicy> basically noop is just FIFO, deadline will try to get reads scheduled before writes, and CFQ will try to be fair and account for how close sectors are to each other so as to reduce seek time
[14:06] <ion> [citation needed] (not sarcastically, i’m interested sincerely)
[14:06] <Bluefoxicy> of course there's no seek time on an SSD
[14:07] <Bluefoxicy> http://ubuntuforums.org/showthread.php?t=1464706
[14:07] <ion> Thanks
[14:08] <Bluefoxicy> you can set these through /sys/block/[device]/queue/scheduler
[14:08] <Bluefoxicy> I'm using CFQ on my hard drive and Deadline on my SSD right now
[14:08] <Bluefoxicy> forum post of course says set it on the kernel command line, but that's system-wide default
[14:08] <Bluefoxicy> something like maybe
[14:08] <Bluefoxicy> check_trim() {
[14:08] <Bluefoxicy>         sudo hdparm -I "$1" | grep -q "Data Set Management TRIM supported" && return 0
[14:08] <Bluefoxicy>         return 1
[14:08] <Bluefoxicy> }
[14:09] <Bluefoxicy> check_trim /dev/sda && echo deadline >/sys/block/sda/queue/scheduler
[14:09] <Bluefoxicy> and so on
[14:09] <Bluefoxicy> but with something to read /etc/fstab, build an array of all the block devices with partitions to mount, and then loop through them
[14:09] <broder> if you were going to do that, i'd look more directly at /sys/block/sda/queue/rotational
[14:10] <Bluefoxicy> nice :)
[14:10] <broder> but basically, i think ubuntu is fairly unlikely to pick something like that up without upstream kernel buy-in
[14:11] <Bluefoxicy> I don't think the kernel will ever auto-deadline
[14:11] <broder> you could imagine it auto-nooping for non-rotational disks
[14:12] <Bluefoxicy> on the one hand you might say, since the kernel can see it's non-rotational maybe it should stop taking a "Default Scheduler" approach and instead implement a smart policy that applies deadline to non-rotational media and CFQ to rotational media
[14:12] <Bluefoxicy> but this argument has already come and gone
[14:12] <Bluefoxicy> the kernel developers--Linus especially--do not support policy in kernel
[14:12] <broder> hmm, fair
[14:12] <broder> ok, i guess you could take it to upstream udev
[14:12] <Bluefoxicy> This happened with grsecurity/PaX etc
[14:12] <Bluefoxicy> yeah udev makes sense
[14:13] <Bluefoxicy> in fact udev makes a lot of sense
[14:13]  * Bluefoxicy checks to see if his cell phone shows up as non-rotational media
[14:14] <Bluefoxicy> odd, it does.  (it's an SD card)
[14:14] <penguin42> why do you say odd?
[14:15] <Bluefoxicy> sorry, it shows up as a spinning disk
[14:15] <Bluefoxicy> ~# cat /sys/block/sdc/queue/rotational
[14:15] <Bluefoxicy> 1
[14:15] <penguin42> ah yeh, that's odd
[14:15] <broder> usb doesn't expose the rotational flag
[14:16] <Bluefoxicy> yeah
[14:16] <Bluefoxicy> i was gonna say, this would be useful for things like USB flash drives too, except it's ... not.
[14:16] <geser> do you get a 0 for any block device? I get only ones for "cat /sys/block/*/queue/rotational"
[14:17] <Bluefoxicy> geser:  I have an SSD
[14:17] <Bluefoxicy> / is on SSD, /home/_vm/ is on SSD (I tried putting it in /var/vm/ and Ubuntu decided to delete its contents during installation, so screw that), /home/ is a spinning disk system
[14:19] <geser> I get 1 for even /sys/block/ram0/queue/rotational (isn't this from a tmpfs mount?)
[14:19] <Bluefoxicy> heh
[14:20] <Bluefoxicy> this is a mess :P
[14:27] <Bluefoxicy> Chromium is so friggin' awesome
[14:27] <Bluefoxicy>  2806 bluefox   20   0 1708m 690m  34m S    5  8.8 599:21.25 chromium-browse
[14:27] <Bluefoxicy>
[14:28] <Bluefoxicy> 690MB!?
[14:28] <Bluefoxicy> 2806	Plug-in Shockwave Flash
[14:31] <penguin42> Bluefoxicy: Can you see it in the developer tools , it has some profiles/heap snapshotting etc
[14:31] <Bluefoxicy> penguin42:  ???
[14:32] <Bluefoxicy> penguin42:  I pulled up the memory stats and Chromium informed me that the huge 700 meg process was just the Flash plug-in doing nothing.
[14:32] <penguin42> Bluefoxicy: chromium's tools menu has a task manager and developer tools option, it shows you which tab is using what memory (to some degree)
[14:33] <Bluefoxicy> the next biggest process is the browser itself at 230MB, and then the biggest actual tab eats about 55MB
[14:33] <Bluefoxicy> so ... Flash is a ridiculous memory hog.
[15:22]  * vibhav hugs jtaylor
[17:50] <melodie> hi
[17:50] <melodie> is it possible to ask a pair of questions about the topic "LiveCDCustomizationFromScratch" please ?
[17:51] <melodie> the link is : https://help.ubuntu.com/community/LiveCDCustomizationFromScratch
[17:51] <melodie> is it ok to ask here ?
[17:54] <JanC> I suppose it's okay to ask (depending on the exact question, there might be better places to ask, but people can point you there then)
[17:54] <melodie> I would like to know if the part mentioning "There is a problem with 10.04 upstart package not containing /sbin/initctl.distrib ... " is still valid for Precise ? and if no one here knows, where could I ask ?
[17:54] <melodie> hi JanC
[17:56] <melodie> and in fact I don't understand at all this part, it lacks information
[17:57] <melodie> and what does "sudo chroot chroot" mean ? Never seen chrooting that way before : is it the right command, or maybe, some mistake ?
[17:58] <melodie> thanks for all pointers. :)
[18:02] <penguin42> I think the second one is the directory of your chroot - ie. sudo chroot /whereever/you/put/yourchroot
[18:06] <melodie> penguin42, I get it. I thank you !
[18:06] <JanC> melodie: upstart-specific questions can also be asked in #upstart (but not so many people are active there) or on the upstart mailing list
[18:06] <melodie> ahem... what does "upstart" mean ?
[18:07] <melodie> I am there and I see a few persons
[18:08] <JanC> upstart is the init system used in Ubuntu, basically the first program started by the kernel that then starts all other programs needed by the OS
[18:08] <JanC> https://en.wikipedia.org/wiki/Init
[18:14] <melodie> JanC, thank you very much !*
[18:15] <JanC> I don't know what that specific issue is/was about, BTW, or whether it's fixed now
[18:23] <melodie> JanC, ok thanks
[18:27] <melodie> I am reading the page of the bug report. It more or less looks like an egg and hen problem
[18:53] <melodie> cool the comment #44 is to say the chroot pb is solved ! I'll fetch someone to update the howto maybe ? I read the rest just in case
[18:54] <JanC> melodie: it's a wiki?  ;)
[18:55] <JanC> (although maybe the help part is locked, not sure?)
[18:56] <melodie> JanC, I don't know yet but I will try to discover, and if needed will visit #ubuntu-doc (if it still exists of course)
[18:58] <melodie> JanC, are we are being cooking now, I'll first finish to read that page to make sure the bug fix is effective, then I will look further. anyhow, thanks for your support !
[18:58] <JanC> melodie: you can log in using your Ubuntu SSO account (the same account/password as used by UbuntuOne & Launchpad)
[18:58] <melodie> JanC, ok
[18:59] <melodie> I meant, I'll have to look at the rest a little later. :)
[19:04] <JanC> yes, and "smakelijk" / "bon appétit" / "Mahlzeit" / "enjoy your meal" or whatever they say in your country...  ;)
[19:21] <melodie> JanC, merci ! bon appétit aussi ! smakelijk too !
[19:21] <melodie> bbl
[19:21] <JanC> :) I ate a couple of hours ago  ;)
[22:54] <malkauns> any X11 experts here?


[01:55] -queuebot:#ubuntu-release- New binary: flang [ppc64el] (disco-proposed/universe) [20181226-1] (no packageset)
[02:05] -queuebot:#ubuntu-release- New binary: clickhouse [amd64] (disco-proposed/universe) [18.16.1+ds-1] (no packageset)
[06:24] -queuebot:#ubuntu-release- New: accepted bcbio [amd64] (disco-proposed) [1.1.2-3]
[06:24] -queuebot:#ubuntu-release- New: accepted clickhouse [amd64] (disco-proposed) [18.16.1+ds-1]
[06:24] -queuebot:#ubuntu-release- New: accepted nbsphinx0.3 [amd64] (disco-proposed) [0.4.1+zero.3.5+ds-1]
[06:24] -queuebot:#ubuntu-release- New: accepted python-django-simple-history [amd64] (disco-proposed) [2.7.0-1]
[06:24] -queuebot:#ubuntu-release- New: accepted cava [amd64] (disco-proposed) [0.6.0-1]
[06:24] -queuebot:#ubuntu-release- New: accepted opam [amd64] (disco-proposed) [2.0.1-1]
[06:24] -queuebot:#ubuntu-release- New: accepted dfvfs [amd64] (disco-proposed) [20190122-1]
[06:30] -queuebot:#ubuntu-release- New: accepted flang [ppc64el] (disco-proposed) [20181226-1]
[07:00] <doko> jbicha: missing symbol in zlib???
[08:05] -queuebot:#ubuntu-release- New binary: intel-media-driver-non-free [amd64] (disco-proposed/multiverse) [18.3.0+ds1-2ubuntu1] (no packageset)
[08:10] -queuebot:#ubuntu-release- New binary: intel-media-driver-non-free [i386] (disco-proposed/multiverse) [18.3.0+ds1-2ubuntu1] (no packageset)
[09:02] -queuebot:#ubuntu-release- New sync: gcc-8-cross-mipsen (disco-proposed/primary) [1~c1]
[09:09] -queuebot:#ubuntu-release- New: accepted gcc-8-cross-mipsen [sync] (disco-proposed) [1~c1]
[09:09] -queuebot:#ubuntu-release- New: accepted intel-media-driver-non-free [i386] (disco-proposed) [18.3.0+ds1-2ubuntu1]
[09:10] -queuebot:#ubuntu-release- New: accepted intel-media-driver-non-free [amd64] (disco-proposed) [18.3.0+ds1-2ubuntu1]
[09:11] -queuebot:#ubuntu-release- New binary: node-istanbul [amd64] (disco-proposed/universe) [0.4.5+ds-4ubuntu1] (no packageset)
[09:29] -queuebot:#ubuntu-release- New: accepted node-istanbul [amd64] (disco-proposed) [0.4.5+ds-4ubuntu1]
[10:03]  * sil2100 uploads bionic langpack updates to -proposed
[10:11] -queuebot:#ubuntu-release- New binary: node-opencv [amd64] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:11] -queuebot:#ubuntu-release- New binary: node-opencv [s390x] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:11] -queuebot:#ubuntu-release- New binary: node-opencv [i386] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:12] -queuebot:#ubuntu-release- New binary: node-opencv [ppc64el] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:18] -queuebot:#ubuntu-release- New binary: node-opencv [armhf] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:20] -queuebot:#ubuntu-release- New binary: node-opencv [arm64] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [amd64] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [armhf] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [ppc64el] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [arm64] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [s390x] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [i386] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:40] -queuebot:#ubuntu-release- Unapproved: fwts (cosmic-proposed/universe) [18.09.00-0ubuntu1 => 18.09.00-0ubuntu2] (no packageset)
[10:46] -queuebot:#ubuntu-release- Unapproved: fwts (bionic-proposed/universe) [18.03.00-0ubuntu3 => 18.03.00-0ubuntu4] (no packageset)
[11:03] -queuebot:#ubuntu-release- Unapproved: fwts (xenial-proposed/universe) [16.03.00-0ubuntu1.2 => 16.03.00-0ubuntu1.3] (no packageset)
[12:17] <doko> apw, sforshee: now nearly everything hangs on linux migrating, or ignoring the failing autopkg tests. binutils is waiting for 40 days now
[12:17] <doko> xnox: besides a few systemd failures. some were fixed however
[12:25] <xnox> doko, yes. but not all. I'm currently pending to figure out udisks2 & systemd on ppc64el
[12:26] <xnox> apw, sforshee: re:kernel. I see that it is ignored on amd64,i386,ppc64el. "passing" on armhf. But it is a regression on arm64 & s390x. Can we please apply/bump the same "ignored failure" onto arm64 and s390x?
[12:26] <xnox> apw, sforshee cause it is affecting migration of userspace packages.
[12:28] <tjaalton> doko: bug 1813155
[12:48] <sforshee> doko, xnox: it should be fine to ignore the current failures for promoting other packages, I know I've said this at least once before already
[12:48] <sforshee> but I don't have the power to make it happen
[12:48] <xnox> horum.
[12:49] <doko> well apw has ...
[12:52] <tjaalton> doko: did you add freeipa to the bug above? there's no version in proposed
[12:54] <doko> yes
[12:54] <doko> demoting
[12:55] <apw> doko, just been investigating ...
[12:56] <doko> tjaalton: jss cannot be removed, has more rdeps
[12:58] <tjaalton> doko: which ones?
[12:58] <doko> * libidm-console-framework-java  (for libjss-java)
[12:58] <doko> * libldap-java                  (for libjss-java)
[12:58] <doko> * libsymkey-java                (for libjss-java)
[12:58] <doko> * libtomcatjss-java             (for libjss-java)
[12:58] <doko> * pki-base-java                 (for libjss-java)
[12:58] <doko> * pki-console                   (for libjss-java)
[12:58] <doko> * ldapjdk                       (for libjss-java)
[12:59] <tjaalton> where are you removing these from?
[12:59] <tjaalton> the ones in disco should be fine, ones in proposed should be removed
[12:59] <sforshee> apw: let me know if you have questions. I've just retried the failing ones as we have fixes for some of the selftest failures in autotests, and tyhicks has confirmed that the apparmor failures are because the tests need updating after the /usr merge
[13:00] <doko> disco
[13:00] <doko> no, that doesn't help. if it's broken, it needs to be removed in the release pocket, not the proposed pocket
[13:01] <tjaalton> bah
[13:01] <tjaalton> start from freeipa, then dogtag-pki, tomcatjss...
[13:01] <tjaalton> ldapjdk
[13:04] -queuebot:#ubuntu-release- New binary: gcc-8-cross-mipsen [i386] (disco-proposed/universe) [1~c1] (no packageset)
[13:16] <tjaalton> doko: now with freeipa/dogtag gone, jss and the others should not cause issues
[13:27] <doko> yes, exactly
[13:28] <doko> now these test failures block readline: gsequencer coyote idlastro mothur ngraph-gtk redmine
[13:28] <doko> ahh, and gap-io
[13:41] <LocutusOfBorg> oSoMoN, https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/16316513
[13:41] <LocutusOfBorg> looks like using llvm-6 instead of llvm-7 works...
[13:42] <LocutusOfBorg> maybe we can switch to that one for now?
[13:42] <LocutusOfBorg> btw firefox failed for some reason I don't get, it doens't fail locally :/ github network error
[13:44] <doko> LocutusOfBorg: better check forward with 8
[13:55] <LocutusOfBorg> doko, llvm-6 is not going to disappear for cosmic, so I care about making llvm-4 disappear right now
[14:00] <doko> and mir is getting in the way again ...
[14:02] -queuebot:#ubuntu-release- New binary: linux-signed-azure-edge [amd64] (xenial-proposed/universe) [4.18.0-1008.8~16.04.2] (no packageset)
[14:12] <LocutusOfBorg> doko, llvm-7 and llvm-8 are both making firefox sad
[14:12] <LocutusOfBorg> before mir-ing you should try some no change rebuilds :)
[14:15] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-edge [amd64] (xenial-proposed) [4.18.0-1008.8~16.04.2]
[14:20] <doko> no, the package mir ...
[14:22] <LocutusOfBorg> ok, but shouldn't this mean that something should go out from main?
[14:23] <LocutusOfBorg> oh we have only llvm-7 in main right now, nice
[14:23] <LocutusOfBorg> btw I'm syncing llvm-8 from experimental when its picked up
[14:24] <doko> you are too late
[14:30] -queuebot:#ubuntu-release- Unapproved: vulkan (bionic-proposed/universe) [1.1.70+dfsg1-1 => 1.1.73+dfsg-0ubuntu<IP_ADDRESS>] (kubuntu)
[14:31] -queuebot:#ubuntu-release- Unapproved: rejected vulkan [source] (bionic-proposed) [1.1.73+dfsg-0ubuntu<IP_ADDRESS>]
[14:34] -queuebot:#ubuntu-release- Unapproved: vulkan (bionic-proposed/universe) [1.1.70+dfsg1-1 => 1.1.73+dfsg-0ubuntu<IP_ADDRESS>] (kubuntu)
[14:42] <LocutusOfBorg> doko, I don't think so :)
[14:42] <doko> https://launchpad.net/ubuntu/+source/llvm-toolchain-8/1:8~svn351401-1~exp1
[14:42] <LocutusOfBorg> oSoMoN, thunderbird with llvm-6 -> good, llvm-7 -> bad, llvm-8 -> bad
[14:43] <doko> ahh, you mean the next one
[14:43] <LocutusOfBorg> :)
[14:43] <LocutusOfBorg> rc1!
[14:53] <oSoMoN> LocutusOfBorg, ack, so we should go with llvm-6
[14:53] <oSoMoN> I'm seeing the same github connection error when doing unrelated builds of firefox, btw
[14:54] <oSoMoN> LocutusOfBorg, would you mind commenting on the bug report with your findings about llvm versions?
[15:00] <doko> ginggs: fyi, trilinos ftbfs
[15:00] <ginggs> doko: thanks
[15:02] <ginggs> doko: ah no, that's fine - only 32-bit ftbfs
[15:13] <LocutusOfBorg> sure oSoMoN !
[15:13] <oSoMoN> thanks
[15:15] <LocutusOfBorg> done
[15:15] <LocutusOfBorg> btw, lots of the third_party applications are already in the archive, so maybe miring them would be nice instead of using bundled old versions?
[15:26] <oSoMoN> looks like the firefox github network error might be caused by the new version of cargo
[16:04] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (cosmic-proposed) [2.02+dfsg1-5ubuntu8.1]
[16:04] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (cosmic-proposed) [2.02+dfsg1-5ubuntu8.1]
[16:22] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [<IP_ADDRESS> => <IP_ADDRESS>] (core)
[16:33] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (bionic-proposed) [0.130ubuntu3.7]
[16:52] -queuebot:#ubuntu-release- Unapproved: accepted apport [source] (cosmic-proposed) [2.20.10-0ubuntu13.2]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (bionic-proposed) [2.02-2ubuntu8.10]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (bionic-proposed) [2.02-2ubuntu8.10]
[17:11] <Ark74> Hi guys!
[17:12] <Ark74> Do you know if apache2 (2.4.34) shipped on disco already has http2 support?
[17:13] <teward> Ark74: probably an #ubuntu-server question but I can find out
[17:14] <Ark74> Oh, cool!
[17:14] <teward> Ark74: I believe it does, because there's HTTP/2 patches being applied.  let me double check the package itself
[17:14] <Ark74> teward, should I go there?
[17:14] <teward> nah you can wait here
[17:15] <Ark74> very appreciated!
[17:15] <Ark74> tnaks
[17:15] <Ark74> *thanks
[17:16] <teward> Ark74: I believe it's available, but not enabled by default, in Disco.  But it's been that way for a while, possibly even Bionic (untested, unconfirmed)
[17:17] <Ark74> I have build (backport) from disco to xenial, and it seems it doesn't
[17:17] <Ark74> seems only by using PPAs is possible to get it
[17:17] <Ark74> I'll hang on #ubuntu-server and ask further
[17:17] <Ark74> there
[17:17] <Ark74> thanks
[18:19] <vorlon> anyone want to dig into the breakage in protobuf that causes mir to FTBFS?
[18:20] <vorlon> I got as far as fixing the first build failure locally and that turned up further bugs, which look to all be on the protobuf side
[18:25] <ahasenack>  /bin/sh: 1: /usr/lib/bin/capnp: not found <-- which failure is that, the one you fixed, or one of the new ones?
[18:26] <vorlon> ahasenack: that's the one I hacked around locally (by editing the cmake templates to use the correct path to /usr/bin/capnp)
[18:27] <vorlon> ahasenack: after fixing that, I get another error with invalid arguments to the command; all of which originates from those same cmake templates in the protobuf package
[18:57] <LocutusOfBorg> vorlon, interesting but the -4 version, that was in proposed before your upload, has been built with the protobuf that is currently in release...
[18:57] <LocutusOfBorg> Preparing to unpack .../266-libprotobuf-lite17_<IP_ADDRESS>-1_amd64.deb ...
[18:59] <vorlon> LocutusOfBorg: sorry, I meant capnproto, not protobuf
[18:59] <vorlon> ahasenack: ^^
[19:00] <LocutusOfBorg> ok this makes sense now :)
[19:11] -queuebot:#ubuntu-release- Unapproved: rejected vulkan [source] (bionic-proposed) [1.1.73+dfsg-0ubuntu<IP_ADDRESS>]
[23:10] <bdmurray> Why is the apt in -proposed greater than the one in updates and security but older?
[23:12] <tsimonq2> ahasenack, vorlon: capnproto> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920230
[23:12] <tsimonq2> I ran into it when packaging Mir for Debian.
[23:12] <tsimonq2> The upstream GitHub issue shows a potential solution but I'm just about as stumped.
[23:13] <vorlon> tsimonq2: well, I don't think the binary's location is wrong (that's where it was previously), but that the cmake templates it itself provides look for it in the wrong place.  And when I hack the templates for this, other things fail
[23:13] <tsimonq2> When I had some spare time (which I do tonight) I was going to look at a recently removed CMake-related patch in the packaging.
[23:13] <vorlon> ok
[23:13] <tsimonq2> vorlon: Please do reply to the bug if you believe it's wrong. :)
[23:14] <tsimonq2> vorlon: https://github.com/thomaslee/capnproto-debian/blob/e29449fdef45ec460e02dbe0d870914faf8efa50/debian/patches/01_cmake-debian.patch - how fitting does this look?
[23:14] <tsimonq2> (That's the patch I was looking at.)
[23:15] <vorlon> ENOCLUE
[23:15] <tsimonq2> Alright. I'll poke at it.
[23:17] -queuebot:#ubuntu-release- New binary: jupyter-sphinx-theme [amd64] (disco-proposed/universe) [0.0.6+ds1-5] (no packageset)


[19:11] <marco-parillo> Kinfocenter reports 5.6.4
[19:11] <marco-parillo> Whoops. Sorry.
[19:12] <knome> note excused, do 20 pushups
[19:12] <knome> *not
[19:13] <knome> (and just kidding...)
[19:22] <marco-parillo> I COULD use them. Too much time in chari.
[19:22] <marco-parillo> chair.
[19:22] <knome> indeed...


[07:59] <dholbach> good morning
[08:00] <hyperair> dholbach: i think you could benefit from a script that sends "good morning" to every channel you've joined just after you've connected ;-)
[08:01] <dholbach> haha
[08:01] <dholbach> hey hyperair
[08:01] <hyperair> hi dholbach =)
[09:17] <dholbach> nigelbabu: meet bobbo
[09:17] <dholbach> bobbo: meet nigelbabu
[09:17] <dholbach> :)
[09:17] <nigelbabu> hello bobbo :)
[09:18] <bobbo> hello nigelbabu :)
[09:19] <dholbach> bobbo: basically we don't want to expect patch submitters to do all the leg work, but give them a good experience of getting their patch somewhere
[09:19] <dholbach> bobbo: we might have submitters there who know about upstream, debian and all the rest of it already and they'll surely help out if they can
[09:20] <dholbach> but I wouldn't expect that to be the majorit
[09:20] <dholbach> y
[09:20] <bobbo> yeah, it took me a while to understand that when I first started contributing
[09:21] <nigelbabu> since you're fairly new to the process, you can perhaps look at our docs and give us feedback on what's missing
[09:21] <dholbach> it's tough, particularly with all the different upstream bug trackers and all the rest of it
[09:21] <nigelbabu> or what's confusing -  it helps a *lot*
[09:22] <bobbo> nigelbabu, okay, I'm reading over them now, I'll say if I see anything :)
[09:22] <nigelbabu> bobbo: awesome! thanks :)
[09:22] <nigelbabu> I'm at work, so I may respond a bit late
[09:28] <bobbo> nigelbabu, ping
[09:28] <nigelbabu> bobbo: yes?
[09:29] <bobbo> nigelbabu, those docs are pretty good, there seems to be enough there to fully explain the process to a newbie and get them ready to start reviewing :)
[09:29] <nigelbabu> bobbo: awesome :)
[09:30] <dholbach> bobbo: these are the plans for this cycle for the patch reviewers team:
[09:30] <dholbach> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-initiative/
[09:30] <dholbach> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-process
[09:30] <dholbach> maybe you can see if there's anything on there you'd like to help with that looks particularly good or important to you?
[09:31] <bobbo> dholbach, looking now :)
[09:31] <dholbach> cool :)
[09:36] <bobbo> dholbach, maybe one of the more "technical" ones, I'm not the greatest documentation writer, the edit-patch feature (Bug #586787) was one that immediately stood out
[09:36] <ubot4> Launchpad bug 586787 in ubuntu-dev-tools (Ubuntu) "edit-patch should take an existing patch as an argument and apply it (affects: 1)" [Undecided,New] https://launchpad.net/bugs/586787
[09:37] <dholbach> bobbo: sure, if you want to have a look at it, that'd be awesome
[09:37] <dholbach> bobbo: mvo wrote most of edit-patch so it'd might be worth talking to him
[09:38] <dholbach> bobbo: also there's james_w who wrote some kind of "test patches from bug X for sponsoring" tool, stefanlsd was interested in that task too
[09:38] <dholbach> that's all the info I can dump on you :)
[09:40] <bobbo> dholbach, so I should take a look at edit-patch and report in if I hit any brick walls?
[09:41] <dholbach> bobbo: sure, just try having a chat with the others if they have an immediate idea or a piece of code you can use and see how far you get with the tool :)
[09:42] <dholbach> good luck :)
[09:42] <bobbo> dholbach, great :D
[10:58] <dholbach> nigelbabu: http://daniel.holba.ch/blog/?p=689
[10:59]  * nigelbabu hugs dholbach
[11:00]  * dholbach hugs nigelbabu back
[11:00] <dholbach> if you all can blog about it too, that'd be sweet
[11:00] <dholbach> ALL: ^
[11:00] <nigelbabu> dholbach: Also, I'm writing a script all report-debian, takes an LP bug as input and forwards that bug through report-debian to debian!
[11:00] <nigelbabu> s/all/called
[11:01] <dholbach> nigelbabu: isn't the LP team working on something like that?
[11:01] <nigelbabu> dholbach: I haven't heard of them working on that
[11:01] <nigelbabu> I heard bryce working on a pedro button
[11:02] <dholbach> also it might be worth wrapping it around submittodebian (from ubuntu-dev-tools)
[11:04] <nigelbabu> but submittodebian is when we have a patch already in a package and want to forward it
[11:04] <nigelbabu> at least thats the impression I got when I tried it last
[11:23] <dholbach> nigelbabu: yes, so you just want to forward bugs to debian?
[11:23] <nigelbabu> dholbach: yep, seb128 asked if we had something for it and I started writing
[11:23] <dholbach> nigelbabu: I'd have a chat with the LP folks first
[11:24] <nigelbabu> I already talked to bryce, he helped me a bit when I got stuck
[11:25] <dholbach> just in case they're working on it so we don't duplicate work :)
[11:26] <nigelbabu> hm, I should perhaps talk to jml today
[11:41] <BlackZ> hey dholbach
[11:52] <dholbach> hi BlackZ
[11:56] <nigelbabu> BlackZ: btw, you guys should think of taking a class at developer week ( when it happens )
[11:57] <BlackZ> dholbach: I'm following up your e-mail
[12:00] <BlackZ> nigelbabu: will be done
[12:00] <nigelbabu> :)
[12:01] <BlackZ> currently we're re-working to the program
[13:35] <vish> dholbach: hmm , whats up with the countdown meter? [on the blog]  it just shows a black strip with red patch on the side
[13:35] <vish> or is it a progress bar?
[13:36] <vish> oops , it is a progress bar :D  , for some reason i was expecting a number there ;)
[13:42] <dholbach> vish: progress bar
[13:43] <dholbach> vish: if you can improve the script to make it prettier… :-)
[13:43] <vish> dholbach: yeah , i'm trying to find a pretty progress bar , we used it for the -manual
[13:44] <dholbach> I use python-imaging
[13:44] <dholbach> it's very primitive
[13:50] <vish> dholbach: hmm , the guy who did the progressbar for the manual site isnt around right now. I'll hook you up with the good stuff soon ;p
[13:54] <dholbach> awesome
[14:53] <dholbach> bobbo: how are things looking? do you think the process will be easy enough for my mom and dad to make use of? ;-)
[14:54] <bobbo> dholbach, yeah, the instructions are pretty good, I've worked through quite a few of the bugs and not really hit any problems
[14:55] <dholbach> cool, that's how we like it
[14:55] <bobbo> one thing I'm not sure about though is that the instructions tell you to remove the "patch" tag whenever we add "patch-forwarded-upstream" etc.
[14:55] <dholbach> nigelb, bdmurray: ^?
[14:55]  * dholbach doesn't know about the state of the discussions and I don't particularly care either way
[14:56] <bobbo> haha, I struggled with that when I was forwarding a patch to gwibber because I know they use the patch tag to identify patches in their bugs and didn't want to trample all over their project
[15:00] <bobbo> dholbach, should I just keep working through these bugs or is there anything else you'd like me to do?
[15:04] <dholbach> let me have a look at the blueprints again and see if there's something
[15:06] <dholbach> bobbo: what do you think about "add documentation about how to turn a patch into a merge proposal if it's a project maintained in Launchpad"? it might be interesting for cases like gwibber and I wrote up a few bits for that already
[15:06] <dholbach> bobbo: if you have a look at https://wiki.ubuntu.com/Bugs/HowToFix - there's a few reusable bits
[15:06] <bobbo> dholbach, branch merge proposal?
[15:06] <dholbach> yep
[15:08] <bobbo> I could have a look at it, basically grabbing the project's trunk, applying the patch, (testing it?), then committing, pushing and merge requesting?
[15:08] <dholbach> yep, there might be something on help.launchpad.net too
[15:09] <dholbach> I don't think you need to write a lot of docs yourself
[15:09] <dholbach> just string those bits nicely together, so people can work on that if they hit such a case
[15:09] <bobbo> sure I'll give that a go, you say you've already written up some stuff for it?
[15:09] <dholbach> https://wiki.ubuntu.com/Bugs/HowToFix
[15:10] <bobbo> great, thanks :)
[15:10] <dholbach> if you could blog about the operation cleansweep some time this week that'd be nice too
[15:10] <dholbach> so we keep the message on everybody's radar
[15:10] <dholbach> bobbo: where do you think we should post the message too?
[15:10] <bobbo> my domain name has just expired :( too poor to buy it again :D
[15:11] <dholbach> I think right now we just covered planet ubuntu, maybe ubuntu-devel@
[15:11] <bobbo> twitter/identi.ca covered?
[15:11] <dholbach> bobbo: nevermind - that's fine - I just saw you were listed on planet
[15:11] <dholbach> might be worth mentioning it there too
[15:12] <dholbach> bobbo: do you think we have enough examples in the docs and stuff that explains when to forward upstream and when not to?
[15:12] <dholbach> bobbo: somehow I get the feeling that's what's probably most complicated to newcomers
[15:13] <dholbach> nigelb, stefanlsd and I agreed to have a look at the docs again and I already did a few bits
[15:14] <bobbo> dholbach, actually yeah, I think that could be expanded, I can imagine people not knowing when to send it up (and whether to go to Debian or straight to upstream)
[15:15] <dholbach> bobbo: if you have an idea what else to add there in terms of indication or documentation, that'd be nice
[15:15] <dholbach> bobbo: some times it's just 2 or 3 bullet points that make a difference
[15:15] <dholbach> … when you're new
[15:16] <bobbo> dholbach, cool, I'll give it a think :)
[15:16] <dholbach> thanks muchly :)
[15:54] <bobbo> dholbach, how does https://wiki.ubuntu.com/DavidFutcher/PatchMergeRequests look?
[15:55] <dholbach> bobbo: I'll take a look in a sec
[15:56] <bobbo> dholbach, it's just a "first draft", I've never written any (decent) technical docs before :)
[15:56] <dholbach> bobbo: it's great
[15:57] <dholbach> bobbo: I'd probably add a link to general bzr docs somewhere and put "bzr lp-open" somewhere too, because I like it so much
[15:57] <dholbach> bobbo: other than that it's in a perfectly mergable state
[15:57] <dholbach> maybe Mr nigelb can take another look
[15:57] <dholbach> bobbo: very awesome
[15:57] <bobbo> dholbach, great, thanks alot, I'd never head of lp-open before
[15:59] <dholbach> bobbo: opens the lp page of the branch
[15:59] <dholbach> bobbo: so you just need to click on "submit for merge" or whatever it's called
[15:59] <bobbo> dholbach, yeah, it's awesome, don't know why more people don't use it :D
[16:00] <dholbach> bobbo: you're there to improve things: you documented it :-D
[16:00] <bobbo> heh :D
[16:02] <nigelb> bobbo: yes, there should only be one tag at a time patch or patch-*
[16:04] <bobbo> nigelb, what if the upstream actively uses the patch tag to identify bugs with patches? Or should we tell them to just use the "Bugs with patches" filter instead?
[16:04] <nigelb> bobbo: upstream using LP?
[16:04] <nigelb> then its a mess :p
[16:04] <bobbo> hehe :D
[16:05] <bobbo> are the LP team going to implement a patch status system or are we stuck using tags for a long time?
[16:05] <nigelb> bobbo: in that case, you can have both.  I see no other way, sadly :(
[16:05] <dholbach> bobbo: I think we'll get it at some stage, people should be using branches :-D
[16:05] <bobbo> awesome :)
[16:05] <dholbach> bobbo: or we should auto-reflow-patches-into-branches
[16:06] <dholbach> patches, interdiffs, .diff.gz, tarballs *SHUDDER*
[16:06] <bobbo> hehe :P
[16:07] <bobbo> I've added some more links in my merge request docs (one to BZR's own docs site and one to help.lp's code review page :)
[16:07] <nigelb> dholbach: I think there was some talk of having the code review workflow for patches too
[16:07] <dholbach> nigelb: yep
[16:08] <nigelb> that would rock!
[16:08] <bobbo> that'd be awesome :D
[16:08] <dholbach> bobbo: awesome - are you going to merge it into the guide?
[16:08] <dholbach> nigelb: you happy with that?
[16:09] <nigelb> dholbach: what? where?
[16:09] <bobbo> :D
[16:09] <dholbach> nigelb: the document bobbo wrote
[16:09] <bobbo> nigelb, https://wiki.ubuntu.com/DavidFutcher/PatchMergeRequests
[16:10] <dholbach> nigelb: bobbo is totally rocking it
[16:11] <nigelb> I got busy with work and missed what was happening here
[16:11] <dholbach> no worries - take it easy :)
[16:11] <nigelb> bobbo: ROCK!
[16:11] <dholbach> seems we're all a pretty excitable bunch :-)
[16:11] <nigelb> you can make it part of the knowledge base
[16:12] <nigelb> dholbach: there is a low hanging task for anyone intrested
[16:12] <dholbach> make it part of the ReviewersTeam namespace and link it from the reviewguide and the knowledge base?
[16:12] <nigelb> hunt through the linux packaging that we're subscribed, confirm that kernel patch is required and unsubscribe the team
[16:12] <nigelb> dholbach: yep
[16:13] <nigelb> bobbo: so, it would be ReviewersTeam/PatchMergeRequests and you can link both to review guide and knowledge base :)
[16:14] <bobbo> nigelb, great, I'm on it now :)
[16:15] <dholbach> nigelb: hemanth wants to get involved too
[16:15] <nigelb> dholbach: get in and get participating :)
[16:16] <hemanth> :)
[16:16] <dholbach> nigelb: eh?
[16:16] <nigelb> ah, I did see him join
[16:17] <hemanth> nigelb, hi
[16:19] <nigelb> hemanth: hello, thanks for helping out!
[16:20] <hemanth> nigelb, my pleasure, was blogging the same, wanted more info on involvement, more related info rather, i went through the wiki
[16:30] <bobbo> okay, that's the merge proposals guide linked from the Knowledge Base and review Guide and prettied up a bit :)
[16:41]  * hemanth going through the Workflow
[16:41] <bobbo> dholbach, any more jobs to offload to me today? I'm working through some more patch bugs but if there're any other things you'd like me to do?
[16:42] <dholbach> bobbo: is there anything in the patch review blueprint work items that's glaring at you?
[16:43] <bobbo> dholbach, documentation to help make the decision whether to go upstream or Debian looks do-able?
[16:43] <dholbach> bobbo: sure, if you have some additional thoughts for it, that'd be fantastic
[16:44] <bobbo> dholbach, okay, I'll give it a closer look, first idea is a subsection of the page linked to from the workflow that explains it in more detail but won't bulk up the workflow paragraph, maybe gives some example bug reports etc
[16:45] <dholbach> that sounds like music to my ears
[16:45] <bobbo> haha, I'll get looking at it then :D
[16:46] <dholbach> bobbo: https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-process has your name on it twice now :)
[16:46] <dholbach> you just went and took over for somebody else :)
[16:46] <bobbo> wooot :D
[16:47] <bobbo> dholbach, is there an official Canonical time to stop working?
[16:48] <dholbach> bobbo: I guess that depends on what your contract is ;-)
[17:40] <nigelb> bobbo: how much of coding do you do?
[17:41] <nigelb> if you'd like to code, I have a task you might want to take over
[17:42] <dholbach> nigelb: bobbo's gone for today I think
[17:43] <dholbach> and I'm just about to leave too so I'll make it home before the rain starts
[17:43] <dholbach> see you tomorrow
[17:56] <bobbo> nigelb, ping
[23:43] <ajmitch> greetings


[03:52] <deserted> hey all, anyone here had much experience with custom upstart jobs?
[04:01] <jea> I can't say I have done much of that myself
[06:18] <deserted> hey bicranial you from Tassie to?


[09:47] <LocutusOfBorg> doko, I'm attempting a python-networkx mere
[09:47] <LocutusOfBorg> *merge
[09:47] <LocutusOfBorg> this should unblock: givaro fflas-ffpack linbox sagemath
[09:47] <LocutusOfBorg> and probably more
[12:52] <didrocks> bdmurray: hey, around? Did you get time to look at my questions about apport/whoopsie?
[14:10] <bdmurray> didrocks: Yeah, sorry still thinking about it.
[14:17] <didrocks> bdmurray: sure! As you saw, I fixed one on the 2 bugs, for the other, I'm currently heading thinking we should put the systemd units in apport binary package and removing them from apport-noui, but tell me once you are settled on it
[14:17] <bdmurray> didrocks: apport-noui seemed good for servers, what do you see apport-noui still doing?
[14:18] <didrocks> bdmurray: it's not installed on servers though?
[14:19] <didrocks> bdmurray: and people still need to use whoopsie API to autoreport (or drop the file)
[14:19] <didrocks> basically, just to create /var/lib/apport/autoreport file
[14:19] <bdmurray> didrocks: right, but if you install apport-noui the thought was crash reporting would just work
[14:19] <didrocks> (so, installing apport-noui alone isn't enough to autoreport)
[14:19] <didrocks> hum
[14:20] <bdmurray> Its been a while since I looked at this though.
[14:20] <didrocks> let me look again, but I'm pretty sure it doesn't create that file
[14:20] <didrocks> bdmurray: yeah, it doesn't from what I see… So, basically, you install apport-noui and nothing happens
[14:22] <didrocks> ah
[14:22] <didrocks> the postinst is touching /var/lib/apport/autoreport
[14:22] <bdmurray> Okay, good!
[14:22] <didrocks> bdmurray: so, basically, what we could is move the systemd services to apport (binary package)
[14:22] <didrocks> and have apport-noui just touching that file (and depending on whoopsie)
[14:23] <didrocks> then, it enables
[14:23] <didrocks> others to have the autoreport functionality without installing it
[14:23] <didrocks> as the whoopsie-preferences API is doing the same (touching or removing that file, based on what you request)
[14:24] <didrocks> does it make sense to you?
[14:24] <bdmurray> Okay, I just wanted to make sure there was still an easy way to setup automatic crash reporting without using a UI.
[14:25] <bdmurray> Yes, this sounds reasonable to me.
[14:26] <didrocks> I think we fix the bug and still cover this use case
[14:26] <didrocks> bdmurray: ok, I'll MP that later on :)
[14:26] <didrocks> thanks for raising this on the bug report, I was just assuming the API was working :p
[14:26] <bdmurray> didrocks: Great thanks! It'll be good to get this sorted and get more crash reports. :-|
[14:27] <bdmurray> Well get more data. ;-)
[14:28] <didrocks> bdmurray: ahah, yes, in some ways… :p
[15:39] <didrocks> bdmurray: do you mind refreshing ~ubuntu-core-dev/ubuntu/cosmic/apport/ubuntu (and maybe bionic? didn't check yet) with your latest uploads?
[15:40] <didrocks> (weird, it seems 2.20.10-0ubuntu3 has been uploaded as a native package where bzr bd clearly requests an upstream tarball)