[00:07] <cjohnston> m_3: ping
[00:53] <mhall119> broder: jelmer: I'm back, did you guys come to a consensus?
[03:23] <infinity> smoser: Can you do me a favour and grab the patch from my latest bacula upload and forward that upstream instead of the one you gave them previously?
[03:24] <infinity> smoser: Their bug tracker seems to require an account, and I can't be bothered, but I assume you have one. :P
[04:14] <infinity> smoser: Also (relating to bacula against), does the console client need curses?  I saw some "curses.h: No such file" zip past in the build log, though this isn't new, old logs have that too.
[04:16] <infinity> smoser: If that's required, I'd assume it's missing a build-dep.  But I dunno.  Maybe it's fine without.
[04:25] <infinity> smoser: Oh, I see.  I think this is just a maintainer oops, based on the fact that readline-dev used to depend on curses-dev.  I'll do a test-build with the fixed build-dep and upload again.
[04:36] <tjaalton> slangasek: well, it shouldn't run chvt if a dm is installed, as i see it
[04:37] <tjaalton> slangasek: but yeah, if you know the issue exists then that's enough for me :)
[04:53] <infinity> smoser: Oh, haha.  Even better.  The curses thing is upstream brain damage.  We turn off conio (their readline substitute) and turn on readline, but if conio's tests (which need curses) fail, it doesn't enable either.
[04:54] <infinity> smoser: So, having curses.h makes the readline support work, despite not actually needing it for the build.  Smart.
[05:52] <pitti> good morning
[05:52] <pitti> roaksoax: the recommended way is to not set a password at all
[05:53] <pitti> roaksoax: and use ident authentication -- i. e. create a system user for that service, and a db user of the same name
[05:53] <pitti> roaksoax: static passwords do not make sense
[05:53] <pitti> roaksoax: so if it needs to be a custom one, you need to ask a debconf question and then pg_createuser
[06:19] <jono> hey folks
[06:20] <jono> does anyone know who looks after Twisted in Ubuntu?
[06:20] <jono> I found a pretty ugly bug - https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/949685
[06:24] <cody-somerville> jono, Is the problem on precise?
[06:25] <jono> cody-somerville, I can confirm it on Precise
[06:25] <jono> cody-somerville, I am not sure if the issue is on Oneiric
[06:25] <jono> there is a script to test attached to the bug
[06:26] <cody-somerville> Hmm... dobey made an upload to twisted on 2012-02-16 that might be related.
[06:27] <jono> cody-somerville, I have noticed this problem for a while
[06:27] <jono> I presumed it was a bug in my code
[06:27] <jono> until I dug into it last night
[07:26] <pitti> jdstrand: seems we have a huge boot speed regression since March 06 -- http://reports.qa.ubuntu.com/reports/boot-speed/acer-veriton-02/2012-03-07_13-17-19/bootchart.png
[07:26] <pitti> jdstrand: seems the apparmor_parser now needs some 40 seconds
[07:43] <dholbach> good morning
[09:18] <seb128> slangasek, hey
[09:18] <seb128> slangasek, I got over 30 bug emails about that gconf upgrade issue on yours this night
[09:19] <seb128> slangasek, is there any chance you raise up it in your todolist?
[09:19] <seb128> on yours->of yours
[09:28] <dupondje> pitti: thanks for the cryptsetup follow up :) Good to have new version in Precise now :D
[09:28] <pitti> dupondje: no worries, thanks for the merge and testing!
[09:35] <apw> anyone else seeing a new 'Progress' popup when pushing from the command line?  and is anyone else seeing it get stuck on the screen after the command has finished
[09:37] <jodh> apw: yup
[09:37]  * apw is perplexed enough getting on screen bling for a command line incantation
[09:37] <apw> jodh, know if there is a bug, or if he should be filing ...
[09:38] <jodh> apw: I was about to check. looks like a rogue bzr-notify process not being killed off.
[09:39] <apw> jodh, so perhaps i can deinstall it ... hmm
[09:39]  * apw asks on #bzr
[09:42] <jodh> apw: bug 949798
[09:48] <apw> jodh, thanks, doesn't seem to be known on #bzr either, though they also sound like they'd like it too :/
[09:51] <xdatap1> Hello guys. I just noticed that libmysqlclient18 libqt4-sql-mysql mysql-common are seeded into the CD but no package seeded look like to needed them. Is that correct? Do should I open a bug?
[10:11] <dholbach> pitti, ^ do you know anything about xdatap1's question?
[10:24] <noodles785> Hi people, does anyone know if there are reasons why the nodejs package on precise is so old? Is something holding back updating it, or is it just gettiing someone to do it?
[10:24] <noodles785> https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/892034
[10:25] <noodles785> IIt seems like something that could be quite important for an LTS resease (although it may be too late).
[10:26] <pitti> xdatap1, dholbach: it's a dependency chain; unity-2d needs qt needs libqt4-sql recommends libqt4-sql-mysql depends libmysqlclient18 depends mysql-common
[10:28] <xdatap1> pitti, it's a dependency of a recommendation then. Thank you
[10:28] <pitti> we could seed libqt4-sql-sqlite and thus satisfy the recommends
[10:28] <pitti> this might downsize the CD a bit even
[10:29] <pitti> Size: 946770
[10:29] <pitti> urgh, indeed!
[10:29] <pitti> xdatap1: thanks for pointing out, I'll try this
[10:29] <xdatap1> pitti, you're welcome
[10:30] <pitti> xdatap1: FYI, http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.precise/desktop.depends is quite helpful for this
[10:30] <xdatap1> pitti, WOW! awesome! this is super useful!
[10:49] <tseliot> pitti: can you accept nvidia-settings-updates in oneiric-proposed for testing, please? (since nvidia-current-updates was accepted)
[10:50] <tseliot> pitti: same SRU (bug #919992)
[10:51] <pitti> tseliot: yep, will do an SRU round soon
[10:51] <tseliot> pitti: thanks a lot!
[10:56] <geser> noodles785: as jamespage merged nodejs the last time, try asking him if he intends to merge it for precise or not (I don't know if nodejs would get the needed FFe)
[10:57] <noodles785> geser: Thanks. And yes, it might be too late, but perhaps worth checking. jamespage ^^?
[10:59] <jamespage> geser, noodles785: the later version of nodejs (and libev + libv8) only landed in Debian unstable a couple of weeks ago
[10:59] <jamespage> the Debian maintainer did let me know but I've not had the time to take a look at it....
[11:00] <jamespage> it is relatively self contained (just the three packages) but would need an FFe
[11:07] <noodles785> jamespage: cool, good to know. Thanks for the info!
[11:10] <jamespage> noodles785, its on my list but right at the bottom so probably won't get done for precise so if you want to pick it up please feel free
[11:12] <noodles785> jamespage: I'm no packager, but I can try :) It's not for me personally (it's pretty easy to install), I just thought it would benefit Ubuntu server.
[12:27] <zyga-xchat> anyone interested in repeatable X crash on fglrx?
[12:44] <directhex> zyga, not a lot anyone can do with closed-source crashes
[12:44] <zyga> directhex, yeah but I'm sure we can do better than that, raise a ticket with AMD or something
[12:47] <seb128> zyga, is that on video playing?
[12:47] <zyga> seb128, yes but it also happens when totem runs visualization for audio
[12:47] <seb128> zyga, known issue
[12:48] <zyga> seb128, ah, I've reported it, should I find the master and dupe?
[12:48] <seb128> zyga, bug #921384
[12:48] <zyga> seb128, thanks
[12:48] <seb128> yw
[12:49] <zyga> seb128, done
[13:03] <mhall119> pitti: ping
[13:03] <pitti> mhall119: hello
[13:03] <mhall119> hiya, is https://bugs.launchpad.net/ubuntu/+bug/942782 waiting on something?
[13:03] <pitti> mhall119: yes, on an archive admin processing it through source NEW
[13:04] <mhall119> ok, so nothing to do but be patient?
[13:04] <pitti> or prod the archive admin of the day
[13:04] <pitti> mhall119: https://wiki.ubuntu.com/ArchiveAdministration#Archive_days
[13:05] <mhall119> thanks
[13:05] <mhall119> StevenK: ping
[13:14] <pitti> ogra_: can you start gnome-language-selector on current arm?
[13:14] <pitti> ogra_: I wonder if anyone can reproduce bug 936045
[13:15] <ogra_> ogra@horus:~$ gnome-language-selector
[13:15] <ogra_> Segmentation fault
[13:15] <ogra_> though this system is armel and outdated
[13:15] <ogra_> i have another armhf that was installed with B1, gimme a sec
[13:15] <pitti> armel, armhf, shoudln't make much difference
[13:15] <pitti> ogra_: ah, thanks
[13:16] <ogra_> pitti, works fine with the newer armhf install
[13:17] <ogra_> in fact i had used it right after install
[13:17] <ogra_> i get a unicode warning in the terminal though
[13:19] <pitti> ogra_: I get that as well, that's harmless
[13:19] <nigelb> mhall119: FWIW StevenK is probably asleep. At least he should be.
[13:23] <TLE> pitti: Hallo, could I persuade you to copy the last batch of oneiric language packs over to the -proposed archive
[13:23] <pitti> TLE: I'm just running that :)
[13:24] <pitti> TLE: it took a while to get the builds sorted out as they starved
[13:24] <pitti> one build failed, I need to hack around that a bit
[13:24] <TLE> awesome, you were already on it, it must be my part betazoid heritage
[13:25] <pitti> TLE: well, it really was your mail, but close enough :)
[13:26] <TLE> :)
[13:26] <TLE> let me know when it's all ready
[13:26] <pitti> I will
[13:31] <mhall119> nigelb: thanks, I'll try him tonight then
[13:33] <mhall119> though...it'll be Friday for hiim, so he wont be the archive admin of the day anymore
[13:33] <jalcine> mhall119: fantastic post about packaging patching :)
[13:33] <mhall119> jalcine: thanks, though there never was a conclusion last night about whether to apply patches before committing
[13:33] <mhall119> I'm hoping this is still okay
[13:36] <pitti> TLE: copying done now, also mailed back
[13:36] <TLE> pitti: thanks
[14:15] <ogra_> does anyone know why i cant open .manifest files inline in the browser anymore ? its pretty annoying to have to download and start gedit every time ...
[14:15] <ogra_> did the mime type change ? the browser or the .htaccess on the server ?
[14:19] <mhall119> jdstrand: ping
[14:26] <smoser> infinity, thank you for your bacula fixes.
[14:30] <smoser> infinity, i forwarded patch to http://bugs.bacula.org/view.php?id=1829
[14:34] <infinity> smoser: I can't read that URL anyway, but thanks. ;)
[14:34] <smoser> infinity, wow.
[14:34] <smoser> that is annoying.
[14:34] <infinity> smoser: Might be worth mentioning to them that the exact same mysql_config fix can (and should) be applied about 200 lines up in the dbi-mysql section (which we don't use, so I didn't bother).
[14:35] <smoser> i'll mention in bug.
[14:35] <infinity> Danke.
[14:35] <smoser> fwiw, i am not really a bacula user :)
[14:35] <smoser> i just pulled a bug at one point, and it was an unending task
[14:36] <infinity> Hah.
[14:36] <smoser> you use it?
[14:36] <infinity> Does this mean I've inherited the TILM mantle?
[14:36] <infinity> No, I don't use it.
[14:36] <infinity> GrueMaster complained to me about it being broken, so I fixed it.
[14:36] <smoser> well i pass the baton to you then
[14:36] <smoser> :)
[14:36] <infinity> Cause I was bored.
[14:36] <smoser> but, its in a *much* better state now than it was in oneiric.
[14:36] <smoser> (ie, it can install and run!)
[14:37] <infinity> You're setting a pretty high bar there.
[14:38] <jdstrand> mhall119: hi
[14:39] <mhall119> jdstrand: hey, I know you're not archive admin of the day, but could you look at https://bugs.launchpad.net/ubuntu/+bug/942782 if you have time?
[14:40] <dupondje> a missing depend, reason for SRU ?
[14:41] <jdstrand> mhall119: ok
[14:41] <mhall119> thanks jdstrand
[15:01] <dholbach> jelmer, are we going to sync the new bzr-builddeb from Debian?
[15:03] <jelmer> dholbach: yes, please (I just synced it); 2.8.3 is a bug-fix-only-upload
[15:03] <dholbach> ah, ok, so you just synced it - great :)
[15:03] <dholbach> awesome :)
[15:05] <jelmer> dholbach: smoser just asked about it in #bzr
[15:05] <dholbach> great, I saw it on the rcbugs list :)
[15:05]  * jelmer wonders if he's whatever is causing everybody to talk about it in the last 5 minutes..
[15:06] <smoser> jelmer, well, i just woke up, came into work, and that bug was on my screen
[15:06] <smoser> since the last thing i did before leaving was have 'bzr  merge' crash on me
[15:06] <smoser> and i had hit the submit-bug dialog
[15:06] <smoser> so i asked.
[15:06] <eitch> locking the screen doesn't work on my precise installation with all updates installed. Can someone tell me for which package i should file a bug report? Or is this already known and no bug report is required?
[15:08] <mdeslaur> eitch: when is it not locking? ie: how are you trying to get it to lock?
[15:09] <eitch> both ways i know: ctrl+alt+l and the action from the system/user menu
[15:10] <mdeslaur> eitch: file it against gnome-screensaver
[15:10] <eitch> i thought maybe it was a configuration bug from an earlier version as i have had precise installed for about 1.5 months now, but even then it didn't work
[15:10] <eitch> ok
[15:10] <eitch> mdeslaur, thanks
[15:16] <mhall119> jdstrand: quickly-unity-lens-template doesn't have a separate source tarball
[15:16] <mhall119> so what should I put in debian/watch?
[15:18] <jdstrand> mhall119: I mentioned it in the email. Ideally, you would have a tarball rather than a bzr snapshot. you need to provide instructions on how to generate the tarball. you can do that in watch or README.source. you can also write a get-orig-source for debian/rules
[15:18] <jdstrand> mhall119: (if watch file, it needs to be comments only
[15:20] <m_3> cjohnston: pong
[15:22] <roaksoax> pitti: cool, thanks for the recommendation.
[15:27] <dholbach> superm1, should bug 931626 be resolved by a sync? (will probably need release team ack)
[15:28] <pitti> tseliot: I didn't see nvidia bits in the oneiric-proposed unapproved queue?
[15:35] <jodh> Please could someone bump the 2 builds here: https://code.launchpad.net/~jamesodhunt/+recipe/upstart-daily-build-test ?
[15:37] <cjohnston> m_3: whats the status of the charm
[15:41] <mhall119> jdstrand: I've added a watch file to the branch
[15:41] <mhall119> it looks for a tar.gz download on Launchpad, which I've also uploaded
[15:41] <jdstrand> mhall119: perfect! thanks :)
[15:42]  * jdstrand reviews
[15:42] <m_3> cjohnston: hey.. summit's still in progress, still on schedule to hand it off tomorrow
[15:42] <cjohnston> cool
[15:42] <cjohnston> jcastro: ^
[15:43] <m_3> cjohnston: only problem so far has been the charm trying to branch from bzr+ssh: repos without creating a key first!
[15:43] <cjohnston> ic
[15:43] <mhall119> m_3: for the pullapps?
[15:43] <mhall119> can't we pull them over http or something?
[15:43] <cjwatson> jodh: done
[15:44] <cjwatson> why not use lp: and let bzr DTRT
[15:44] <m_3> mhall119: yes, but I'd have to push those changes back to summit and/or rewrite them on the fly in the charm
[15:44] <jibel> pitti, FYI I added a post-upgrade  test that checks for obsolete config files.
[15:44]  * m_3 finding repos
[15:44] <jibel> pitti, It's currently enabled only for LTS to LTS. That's what explain lucid desktop and server became unstable.
[15:44] <mhall119> m_3: tell cjohnston what changes need to be made, I'm okay with making it always use http
[15:45] <cjwatson> m_3: if you use lp: instead it should use the equivalent of bzr+ssh: if it can and otherwise http:, as I understand it
[15:45] <m_3> mhall119: thanks
[15:45] <mhall119> cjwatson: I tried using lp:, but since it's calling bzrlib, not bzr cli, it didn't like it
[15:46] <cjwatson> oh, well, you can do directory lookups in bzrlib too although I don't happen to know how
[15:46] <mhall119> yeah, I was probably just not using the write API calls
[15:46] <mhall119> s/write/right/
[15:50] <blackbug> i am trying to make some changes in a application packaged with ubuntu. but even after compiling and building my changes, they are not reflected in the executable. I even tried just to print a message the moment application is initialised, but nothing is displayed. is there any special way to test any application? i am doing this first time.
[15:53] <cjwatson> when I work on packages and want to test the program I just built I generally just run it from the build tree rather than bothering to install it
[15:54] <cjwatson> unless there's some reason I need other associated files in place rather than just the executable
[15:54] <cjwatson> is that what you're trying to do?
[15:55] <jodh> cjwatson: thanks!
[15:58] <blackbug> yes i am running the exe from the build tree, i am not much familiar with gtk code, simple printf statements doesnt display message on console on a gtk application? with wxwidgets i can display messages on console using printf or cout
[15:59] <cjwatson> blackbug: silly question, exactly what command line are you using to run it from the build tree?
[15:59] <cjwatson> gtk doesn't fiddle with standard output; printf should work
[16:01] <tseliot> pitti: oh, my bad, please try again now
[16:02] <blackbug> i am making changes in necessary .c & .h file, compiling and building with make and make install
[16:02] <blackbug> and then using the executable
[16:02] <cjwatson> blackbug: exactly what command line are you using to run the executable?  please copy and paste
[16:05] <blackbug> sudo make;sudo make install; ./leafpad
[16:05] <pitti> jibel: thanks
[16:05] <cjwatson> you don't need make install if you're running from the current directory; and you don't need sudo in front of make, only make install
[16:06] <cjwatson> I would suggest as a test putting a printf right at the top of main() and seeing what that does
[16:07] <cjwatson> did make print any errors?
[16:07] <blackbug> actually i was trying it from build tree and the dir location wic i used with configure --prefix option. i had to use sudo bcz there were some permission issues with my user and compilation was interuppted while creating files.
[16:08] <cjwatson> 'sudo make clean' and then you shouldn't need sudo any more.
[16:08] <cjwatson> I don't understand what you mean about --prefix; the prefix shouldn't be involved when you're just running 'make'
[16:11] <blackbug> no i used prefix initially with ./configure file.
[16:12] <cjwatson> sure, but you said you were trying it "from ... the dir location" [--prefix]
[16:12] <cjwatson> that doesn't make sense :)
[16:12] <ogra_> cjwatson, sudo might be needed depending *where* exactly the build tree is unpacked :)
[16:12] <blackbug> i just cleaned everything and tried again. now i can see the messages
[16:12] <cjwatson> this would be easier with full transcripts on paste.ubuntu.com rather than summarised versions
[16:12] <cjwatson> ok
[16:12] <ogra_> (i.e. in /usr/src ...)
[16:12] <cjwatson> ogra_: well, yeah, but Don't Do That Then ...
[16:13] <ogra_> indeed
[16:13] <cjwatson> /usr/src <- abomination
[16:13] <blackbug> but in my user home directory i should have permissions for it..still it was giving errors without sudo
[16:13] <ogra_> did you run apt-get source with sudo before ?
[16:13] <cjwatson> if you built it as root once then there might have been root-owned files
[16:13] <cjwatson> or, indeed, if you incorrectly used sudo apt-get source
[16:15] <blackbug> yes i did, you right cjwatson it looks the same :)
[16:19] <tseliot> pitti: thanks
[16:22] <ev> pitti: might I trouble you to cherry pick r2226 from lp:~ev/apport/whoopsie
[16:22] <blackbug> thanks for suggestions cjwatson and ogra_
[16:23] <pitti> ev: ah, did you get the tests fixed?
[16:23] <ev> tests fixed?
[16:23] <pitti> ev: https://code.launchpad.net/~ev/apport/whoopsie/+merge/96416
[16:24] <pitti> ev: without my "if 'DistroRelease' in self.report:" fix I get KeyErrors
[16:24] <ev> ah, odd that didn't come through to my inbox
[16:24] <ev> I'll have a look
[16:25] <pitti> ev: ah, 2226 looks fine, applying
[16:25] <ev> cheers
[16:26] <kees> hrm, I think the fix for 890434 needs to be reverted. See 949732.
[16:26] <pitti> ev: should I link that to any bug?
[16:26] <ev> pitti: I haven't filed one, but can if you think that's what it needs to get in the archive
[16:27] <pitti> ev: no, that's fine
[16:27] <pitti> just wondering about existing bugs
[16:27] <ev> sure
[16:27] <pitti> ev: cherry-picked, trunk r2225
[16:27] <ev> cheers
[16:27] <blackbug> one more question, how in ubuntu the code flow is returned back. for eg say i have entered invalid data, pathname, filename. shall i terminate application with proper message or should i ask for the input again. what is usual pattern with ubuntu apps.
[16:31] <cjwatson> blackbug: if it's command-line parsing it should terminate with an error; if it's graphical, e.g. text boxes, display error and ask again
[16:32] <jdstrand> mhall119: quickly-lens-templates never showed up in new
[16:32] <blackbug> cjwatson: thanks for the information)
[16:38] <mhall119> jdstrand: I pushed to the branch, I don't think I can uploaded it
[16:38] <superm1> dholbach: already been synced, just forgot to close the bug
[16:39] <dholbach> ah cool
[16:39] <jdstrand> mhall119: can you prepare a new source package incorporating the fix and have your sponsor reupload it? (if I upload it, I am not allowed to deNEW it)
[16:47] <dobey> anyone care to sponsor https://code.launchpad.net/~dobey/ubuntu/precise/twisted/fix-935756/+merge/96617 ? jono and the world will love you if you do :)
[16:55] <mhall119> didrocks: will you be around for a bit to upload a new source package for my quickly template?
[16:56] <didrocks> mhall119: I'm leaving in a hour, but happy to be help you again
[16:56] <didrocks> or drop me an email if not
[16:56] <didrocks> do you know what the rejection was about?
[16:56] <mhall119> didrocks: initially for lack of a debian/watch file
[16:57] <mhall119> but also jdstrand would like just the debian/ files on their own
[16:57] <didrocks> jdstrand: you do reject on that? :) even when upstream won't cut "outside ubuntu" tarballs?
[16:57] <didrocks> hum, which ones, just being curious :)
[17:00] <mhall119> didrocks: jdstrand: https://code.launchpad.net/~mhall119/unity-quickly-templates/precise-package
[17:00] <jdstrand> didrocks: I don't care so much about debian/ being separate. I do care about being able to verify the source integrity of the package. there wasn't an upstream tarball with a corresponding watch file. but there also wasn't any documentation in the packaging on how to create the tarball.
[17:01] <jdstrand> didrocks: so I asked to either do upstream tarball + watch, use get-orig-source or document how the tarball was generated
[17:01] <mhall119> jdstrand: you now have either the combined branch or the stand-alone package branch, both have watch files to pull the source tarball
[17:02] <jdstrand> mhall119: if I upload I can't deNEW for you (this is archive admin policy). please have someone upload on your behalf and I can review then
[17:02] <mhall119> didrocks: ^^ please upload for jdstrand
[17:02] <didrocks> jdstrand: ok, we do have quite some packages that are using a split bzr mode without upstream tarball
[17:03] <mhall119> didrocks: lp:unity-quickly-templates/precise-package is the ./debian/ only branch
[17:03] <jdstrand> didrocks: I realize that, and one by one as they come through NEW I ask for this
[17:03] <didrocks> jdstrand: ok, good to know, I never made this a requirement for packages that were ubuntuish
[17:03] <jdstrand> my long term goal is to be able to automate the source integrity of the archive
[17:04] <didrocks> jdstrand: do you have anything to do with… security? j/k ;)
[17:04] <jdstrand> heh
[17:05] <stgraber> pitti: ping
[17:05]  * mhall119 has been causing so much trouble in this channel lately
[17:05] <mhall119> I apologize
[17:06] <jdstrand> mhall119: no trouble on my end
[17:06] <mhall119> yet
[17:06] <didrocks> mhall119: you can have shorter url in debian/watch btw
[17:07] <mhall119> yeah probably
[17:07] <mhall119> if there's one thing I've discovered about packaging, it's that there's *always* a better way to do it
[17:07] <didrocks> version=3
[17:07] <didrocks> https://launchpad.net/unity/+download .*/unity-([0-9.]+)\.tar\.bz2
[17:07] <didrocks> mhall119: for instance ^
[17:08] <didrocks> don't need to put again the full URL
[17:08] <mhall119> didrocks: thanks, I'll remember that next time I write one, that is a lot easier
[17:08] <didrocks> mhall119: you can maybe stage the change in bzr so that next upload can get it
[17:09] <mhall119> ok
[17:09] <didrocks> jdstrand: uploaded
[17:11] <mhall119> thanks didrocks
[17:11] <didrocks> mhall119: yw ;)
[17:11] <jdstrand> thanks, will deNEW now
[17:13] <mhall119> thanks jdstrand
[17:16] <mhall119> bdrung: pinging you again about devscripts/edit-patch
[17:46] <zyga> hi, I've noticed that rhythmbox cannot play more than a few seconds of most of my media library
[17:46] <zyga> while banshee/totem have no issues
[17:46] <zyga> has anyone observed this?
[17:47] <zyga> ah, just noticed it's a duplicate from launchpad
[17:47] <zyga> https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/815837
[17:48] <zyga> https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/949886
[17:53] <kk_> I am trying to fix an issue, i have done sanity testing it's almost fine, but how to make sure it adher's ubuntu coding guidelines. who will review it?
[17:55] <cjwatson> https://wiki.ubuntu.com/SponsorshipProcess
[17:58] <blackbug> hi again cjwatson, can you answer my question it was from different id (kk_) before..  I am trying to fix an issue, i have done sanity testing it's almost fine, but how to make sure it adher's ubuntu coding guidelines. who will review it?
[17:58] <cjwatson> https://wiki.ubuntu.com/SponsorshipProcess
[17:59] <cjwatson> it's not possible to give you a specific name of somebody who will review it in advance
[17:59] <cjwatson> in many cases it ought to go to the upstream developers
[17:59] <blackbug> ah ok, thanks)
[17:59] <shnatsel> Hello! I suspect that one unit test in Ubiquity goes mad and doesn't let me build a package
[17:59] <cjwatson> as in the people who actually wrote the software in question; Ubuntu is just a distributor, although we do often modify packages
[18:00] <cjwatson> shnatsel: oh?
[18:00] <shnatsel> I've replaced two pics with pics of smaller size, and now it fails in "test_pages_fit_on_a_netbook"
[18:00] <shnatsel> cjwatson: bug 950125
[18:00] <cjwatson> that test is a bit delicate
[18:00] <cjwatson> ftbfs isn't accurate though, that means unmodified builds in the archive ...
[18:01] <shnatsel> cjwatson: it builds fine locally, but not in PPA
[18:01] <cjwatson> I think it may be somewhat theming-dependent
[18:01] <blackbug> hmm ok, the thing is intially one is ot aware about the coding guidelines and practices followed, and it can go smooth only with some tips or suggestions after reviewing code. anyway thanks for the link cjwatson.
[18:01] <cjwatson> blackbug: there's no single such thing as Ubuntu coding guidelines though, it depends on the package you're working on
[18:01] <shnatsel> cjwatson: thanks! , won't misuse again
[18:01] <cjwatson> blackbug: you should follow the coding style of the package you're working on
[18:02] <shnatsel> s/ ,/my bad,/
[18:02] <cjwatson> shnatsel: have you tried it in a local sbuild?
[18:03] <shnatsel> cjwatson: no, because I don't know what's an sbuild
[18:03] <cjwatson> apt-cache show
[18:03] <cjwatson> or pbuilder
[18:04] <shnatsel> cjwatson: thanks, will do!
[18:05] <cjwatson> the important bit is that it's a clean chroot without any bits of your normal user's desktop environment lying around in it
[18:06] <cjwatson> but, if it's really getting in your way, you can of course just bump the numbers there or disable the test; you may not care about what it's testing for
[18:07] <shnatsel> that's going to land in elementary OS, so I do care
[18:07] <shnatsel> brb relogin to make sbuild work
[18:18] <cjwatson> shnatsel: ah, apparently broke in 2.9.25 (#ubuntu-installer)
[18:18] <cjwatson> so it's not about your changes, something changed under us
[18:19] <shnatsel> cjwatson: is this going to be fixed for Precise or it's a low-priority item and I should just disable testing if I want it to work?
[18:19] <cjwatson> it will have to be fixed for precise since it's blocking us
[18:20] <cjwatson> so the ftbfs tag was accurate after all ;)
[18:20] <shnatsel> cjwatson: ok, is there a bug report to which I should mark mine as duplicate?
[18:20] <cjwatson> no
[18:21] <stgraber> shnatsel: yours just became the main bug report ;)
[18:22] <shnatsel> stgraber: good to know :)
[18:22] <stgraber> shnatsel: I'm currently looking into that bug as it caused by upload to fail even though I ran the test before uploading...
[18:22] <shnatsel> stgraber: thanks!
[18:44] <cjwatson> blackbug: please don't do that, DCC is useless
[18:44] <cjwatson> (it can't traverse NAT, at least not in my setup, and I've no intention of putting the work in to figure out how to fix that)
[18:45] <stgraber> cjwatson: IPv6!
[18:45] <blackbug> ok, does gnome-screenshot has any bzr branch? i couldnt find it
[18:45] <cjwatson> DCC CHAT is pointless anyway, just use /query.  but in any case why ask me this kind of thing personally, I have nothing to do with gnome-screenshot
[18:46] <cjwatson> stgraber: I have IPv6 but I'm willing to bet most of the people who try to DCC CHAT me don't :-)
[18:46] <cjwatson> (and I rather suspect my firewall would deny it anyway ...)
[18:48] <blackbug> ok, actually i was workin on 949341 which i encountered last night, but i could not find any branch registered on bzr, so was curious to know.
[18:49] <stgraber> bug 949341
[18:49] <shnatsel> blackbug: I'll try to look up the branch for you
[18:50] <yofel> cjwatson: hi, could you add konsole back to the kubuntu packageset please? It's not in there anymore for some reason
[18:51] <blackbug> shnatsel: thanks)
[18:51] <cjwatson> yofel: needs a manual exception - please send me mail so I have an audit trail
[18:51] <stgraber> blackbug: it's usually under ~ubuntu-desktop but this package doesn't seem to have one, so the UDD branch is probably the right one "bzr branch ubuntu:gnome-screenshot"
[18:51] <yofel> will do
[18:52]  * micahg wonders why konsole would need an exceptions as it's explicitly seeded
[18:52] <blackbug> shnatsel: doesnt seem to work "bzr branch ubuntu:gnome-screenshot"
[18:53] <broder> hmm. why don't we patch debcheckout to know about udd branches?
[18:53] <shnatsel> blackbug: bzr branch lp:ubuntu/gnome-screenshot then
[18:53] <stgraber> blackbug: hmm, indeed, odd
[18:54] <shnatsel> blackbug: that's how I do it
[18:54] <blackbug> nope..doesnt work either
[18:54] <cjwatson> micahg: it's in desktop-core, presumably something pulls it in more deeply
[18:55] <stgraber> blackbug: the importer failed (http://package-import.ubuntu.com/status/gnome-screenshot.html#2012-02-17%2010:17:39.345154)
[18:55] <shnatsel> ah, that's why some bzr branches in launchpad lag behind versions in the archive!
[18:55] <stgraber> blackbug: so you probably should just go with a good old "apt-get source gnome-screenshot" (requires deb-src lines in /etc/apt/sources.list), then diff manually your changes
[18:55] <micahg> cjwatson: I think that's a bug too :)
[18:56] <stgraber> shnatsel: yep, not everyone pushes to the branch before uploading which causes the lag, also there are bugs causing the importer to fail for some branches
[18:56] <shnatsel> stgraber: I actually planned to maintain patched versions of Ubuntu packages using those branches and LP recipes. Looks like it's a bad idea.
[18:57] <shnatsel> stgraber: in fact, that ubiquity thing is one of them
[18:57] <stgraber> shnatsel: yeah, for ubiquity you'd want to use lp:ubiquity instead, that's where we push the changes as they happen
[19:00] <shnatsel> stgraber: that won't let me maintain older versions though... this way Precise will get Ubiquity from Q release eventually
[19:00] <cjwatson> shnatsel: we tag every version we upload and you can branch off a tag
[19:00] <blackbug> yes i made changes on the source code fetched from apt-get source. but how should i attached my changes with the bug?
[19:00] <cjwatson> or indeed off any revision you like
[19:01] <shnatsel> cjwatson: thanks, will do something like that
[19:15] <stgraber> shnatsel: ubiquity bug fixed
[19:15] <stgraber> shnatsel: I'm releasing 2.9.26 now
[19:15] <shnatsel> stgraber: w00t! thanks a lot!
[19:16] <stgraber> shnatsel: adding a build-dependency on ubuntu-artwork makes the test use the right theme and succeed
[19:17] <shnatsel> stgraber: thanks for the info, that's a thing for me to patch away XD
[19:18] <stgraber> shnatsel: well, it's just a build-dependency, it won't result in a runtime dependency on ubuntu-artwork, so even if you don't use ubuntu-artwork it should be safe to use as a build-dep
[19:18] <stgraber> shnatsel: though I guess it'd be best to run the test with your own theme to ensure the rendering works with yours :)
[19:18] <shnatsel> stgraber: yep, that's the plan :)
[19:53] <broder> hmm, did the kernel stop passing its command line arguments to PID 1? upstart doesn't seem to be getting my --verbose argument
[19:53] <broder> oh wait, i'm an idiot
[19:54] <stgraber> broder: the kernel passes them to /sbin/init in the initramfs, which then has to passe them to /sbin/init on the filesystem
[19:54] <broder> stgraber: hmm...
[19:54] <broder> evan@caron:~$ cat /proc/1/cmdline | xargs -0
[19:55] <broder> /sbin/init
[19:56] <stgraber> broder: /usr/share/initramfs/tools/init doesn't show anything for --debug
[19:57] <stgraber> broder: oh but it uses $@ so you should be getting everything indeed
[19:58] <broder> right. so apparently the initramfs init isn't getting any arguments
[19:58] <broder> i feel like i remember that being a distro patch...
[19:59] <broder> i wonder if it should be passing $(cat /proc/cmdline) instead
[20:04] <broder> or alternatively if upstart should be injecting /proc/cmdline into its argv before parsing
[20:17] <infinity> broder: init shouldn't be getting cmdline completely raw, though, as it might get parsed and stripped by the initrd.  In theory.
[20:18] <broder> infinity: ok, i didn't know that was a theoretical possibility. in that case i offer that /usr/share/initramfs-tools/init should be passing $(cat /proc/cmdline) to real root's /sbin/init
[20:19] <infinity> Well, I was just saying that I don't think that's sane. :P
[20:19] <broder> err, oh, you're complaining about spaces/quotes/etc?
[20:19] <broder> was any of that ever actually handled correctly when the kernel was passing it on?
[20:20] <infinity> Or just stuff that's meant for the initramfs init.  There's no need to pass that on.
[20:20] <infinity> But the real question here is what't the bug/issue?
[20:20] <broder> i passed --verbose on the kernel commandline expecting that to get me information from upstart as to what events were being processed
[20:22] <infinity> I'm not entirely positive that /proc/1/cmdline is an accurate representation of reality.
[20:23] <broder> that's possible, but upstart definitely wasn't getting the --verbose argument - the log-priority was still set at message when i managed to get to enough of a userspace to check
[20:24] <infinity> Sure, but we know, for instance, that --log works.
[20:24] <infinity> So, it's obviously getting arguments.
[20:24] <broder> err, i should have clarified incidentally that i'm using oneiric
[20:24] <broder> have not tested this on precise yet
[20:25] <infinity> initramfs hasn't changes much in that time.
[20:25] <infinity> Nor klibc.
[20:25] <infinity> (And /proc/1/cmdline on my precise machine claims init has no arguments, which I know is patently false)
[20:25] <infinity> So, I suspect it's a red herring that has more to do with all the init pivoting insanity done by run-init to keep PID 1 as PID 1.
[20:26] <slangasek> I'm sure that I've used --verbose with precise and oneiric kernels and gotten the expected results from upstart
[20:27] <broder> wait...wtf. it works for me now. wtf was i doing before?
[20:27] <infinity> :P
[20:27] <infinity> I probably don't want to know.
[20:27] <infinity> And you likely don't either.
[20:27] <broder> probably
[20:27] <infinity> Back away from the keyboard, grab a drink, and go back to what you were debugging. ;)
[20:28] <broder> :)
[20:28] <infinity> I have a lunch date that I should head off to.
[22:36] <cfhowlett> *oem mode: what is the sudo passwd?*  reinstalled and autologin to oem account.  can't add my users as I don't know oem's admin passwd...
[22:43] <ScottK> cfhowlett: oem, IIRC.
[22:44] <mgolisch> will ubuntu for android be available generaly?
[22:44] <mgolisch> or is that somekind of vendor integration thing only?
[22:44] <mgolisch> the idea sounds realy cool, id love to test that on my phone
[22:45] <cfhowlett> mgolisch: ask #ubuntu-phone
[23:01] <bdrung> mhall119: i tried https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/947180/comments/2 with your patch applied, but it failed: http://paste.ubuntu.com/875311/
[23:38] <kees> mterry: did you see my notes on the bison bug?
[23:38] <kees> mterry: if you don't object, I'd like to just sync bison from Debian.
[23:39] <mterry> kees, yeah, I saw the comment but didn't have time to re-examine.  if that's the only delta, then I don't disagree
[23:39] <kees> mterry: yeah, it was.
[23:39] <kees> mterry: I couldn't find the example FTBFS so I couldn't see what else was suffering from a poor yyerror implementation
[23:40] <mterry> kees, nip2 is all I can remember
[23:41] <kees> mterry: yeah, the ftbfs build log vanished off LP, so I couldn't check it :(