[00:49] <micahg> dupondje: what's your base Ubuntu version?
[07:35] <dholbach> good morning
[07:45] <dholbach> how is everyone doing on Fix It Friday?
[07:45] <dholbach> :)
[07:46] <geser> good morning dholbach
[07:46] <geser> what's broken?
[07:47] <dholbach> http://harvest.ubuntu.com lists quite a number of things which are broken :)
[07:47] <dholbach> I would think we could recommend the 'bitesize' and 'resolved-upstream' opportunities for example
[07:48] <micahg> nice list of broken: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20120201-precise.html
[07:48] <dholbach> yeah, good one too :)
[07:51] <geser> I hope to get to look at some FTBFS next week
[07:55] <broder> happy fix it friday, dholbach :) i'll be back in about 12 hours or so
[07:55] <dholbach> Is anyone here for Fix It Friday? Did anyone bring questions? Or wants something reviewed? Or wants to chat? :)
[07:55] <dholbach> broder, excellent - sleep tight then :)
[07:55] <valdur55> Hey!
[07:56] <dholbach> hey valdur55
[07:57] <valdur55> How can i check dailly build packages version?
[07:57] <valdur55> geminate log?
[08:00] <dholbach> valdur55, for example this one: http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu/precise/daily-20120223.1.log
[08:01] <valdur55> Oh i just got it... lazyness :) I already aswered to my question
[08:01] <dholbach> search for "hardlink:" - that's the section where you can find the packages and their versions
[08:01] <dholbach> valdur55, it took me a bit too to find them :)
[08:04] <valdur55> OK. other problem is desktop files translation
[08:07] <geser> dholbach, valdur55: what about looking into the manifest? http://cdimage.ubuntu.com/daily-live/current/precise-desktop-i386.manifest
[08:07] <micahg> anyone care to do a quick review? http://revu.ubuntuwire.com/details.py?upid=9397  (lightdm-gtk-greeter)
[08:07] <valdur55> geser, good point!
[08:07] <dholbach> geser, that's sounds like a clever alternative ;-)
[08:08] <dholbach> micahg, I can take a look in a bit
[08:08] <dholbach> I'm just reviewing one of the unity-quicklist merge proposals
[08:08] <dholbach> and will offer some advice about how to work with edit-patch for the next time they submit something ;-)
[08:16] <dholbach> valdur55, you had a question about desktop file translations?
[08:16] <dholbach> dpm, might be just your man
[08:16] <dholbach> hey dpm :)
[08:17] <dpm> hey, morning ;)
[08:17] <dpm> what's up in the desktop file translations world?
[08:18] <valdur55> dpm, Is it possible to send all changes in one folder? Without needing to make personal branch for every package
[08:19] <dpm> valdur55, can you give me a bit more of context? I can't quite understand how the question relates to desktop file translations
[08:21] <dholbach> micahg, done
[08:22] <micahg> dholbach: thanks, I just grabbed the pkg-xfce branch and tweaked it a bit
[08:23] <micahg> dholbach: not sure what that patch is for to write a description for it, I got it from Debian
[08:24] <dholbach> yeah, no idea either :)
[08:27] <micahg> dholbach: do you want to see another version? I fixed everything I think except the patch header
[08:28] <dholbach> sure, in a bit
[08:31] <valdur55> dpm, false alarm.... need some thinking time.
[08:31] <dpm> valdur55, no worries :)
[08:38] <ajmitch> evening
[08:39] <nixternal> morning
[08:48] <bcbc2> I've got some Wubi fixes. Not sure on the procedure to get them reviewed. I uploaded them to https://code.launchpad.net/~bcbc/+junk/wubi ... what do I have to do to get these reviewed?
[08:49] <valdur55> bcbc2, some recent blog bost about this procedure: http://mhall119.com/2012/02/contributing-to-unity-for-non-developers-quicklists/
[08:50] <micahg> valdur55: WUBI is the windows installer ;)
[08:51] <valdur55> micahg, yea i know, but contributing model is same ...
[08:51] <bcbc2> valdur55: thanks I'll give that a try
[08:56] <valdur55> bcbc2, https://wiki.ubuntu.com/WubiGuide#Where_is_the_source_code.3F - some links for wubi source code
[08:57] <dholbach> bcbc2, I think you should be able to click on "propose for merging" somewhere
[08:58] <bcbc2> dholbach: I don't see it on that page.
[08:59] <dholbach> ah ok
[08:59] <dholbach> did you branch from https://code.launchpad.net/wubi?
[08:59] <dholbach> in that case you could try to push to lp:~<yourlaunchpadid>/wubi/<branchname>
[08:59] <dholbach> and see if you can find the "propose for merge" there
[09:00] <bcbc2> dholbach: I don't think the branch is the problem. I used: bzr branch lp:wubi
[09:01] <ajmitch> where you push to affects what launchpad will show
[09:01] <dholbach> bcbc2, I think it might be a namespace problem - so ~bcbc/+junk/wubi vs ~bcbc/wubi/<branch>
[09:02] <bcbc2> dholbach: I'm trying to push to a new branch now.
[09:04] <bcbc2> dholbach: okay, it's still scanning, but I see a 'propose for merge' there. Thanks for the help all
[09:04] <dholbach> bcbc2, cool
[09:04] <dholbach> de nada
[09:05] <broder> bcbc2: you can't open a merge proposal for anything you push to +junk
[09:06] <dholbach> broder, can't sleep? :)
[09:07] <broder> dholbach: this is me pulling out my laptop for a quick fix before i go to sleep
[09:07] <broder> although i just started laundry, so it might be a longer fix...
[09:14] <dholbach> micahg, there still seem to a be a number of files in http://revu.ubuntuwire.com/revu1-incoming/lightdm-gtk-greeter-1202240906/lightdm-gtk-greeter-1.1.4/debian/copyright which don't exist in the source
[09:14] <micahg> dholbach: that's not the latest version ;)
[09:14] <dholbach> like ./src/ contains only lightdm-gtk-greeter.c  Makefile.am  Makefile.in
[09:14] <micahg> dholbach: http://revu.ubuntuwire.com/details.py?upid=9399
[09:14] <dholbach> ok, I should have used http://revu.ubuntuwire.com/p/lightdm-gtk-greeter instead
[09:15] <micahg> or that :)
[09:16] <ajmitch> micahg: see, it's not completely broken :)
[09:17] <krychek> hi, can anyone help me in opening an upstream kernel bug for this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/811464 ?
[09:17] <krychek> i donno which category to choose
[09:18] <dholbach> krychek, you could try asking in #ubuntu-kernel - they will know for sure
[09:18] <krychek> ok thanks
[09:25] <micahg> dholbach: thanks
[09:27] <ajmitch> micahg: I see there's a new bzr-rewrite in debian to fix the FTBFS, but do you want to fix bug 791041 at the same time?
[09:27] <micahg> ajmitch: I do, I pinged jelmer earlier in the week, but got no response, I"ll JFDI this weekend
[09:28] <ajmitch> ok, looks like bzr-xmloutput & bzr-cvsps-import can at least be synced
[09:31] <rigved> hi everyone. i had filed a bug against one version of a package. now that package has moved two minor revision numbers up. the bug still exists. should i submit a patch against the old version (against which the bug report has been linked) or the new version, currently in precise?
[09:32] <ajmitch> preferably against the new version
[09:32] <ajmitch> if it warrants it, after it's fixed in precise it may be able to be fixed in a stable release update for previous releases
[09:33] <rigved> ajmitch: ok. thanks!
[09:35] <ajmitch> micahg: do you know if there's been a push to move packages off libdb4.8?
[09:35]  * ajmitch is just looking at RC bugs & wondering if it's serious enough for precise
[09:35] <turbotax> anyone have smtp server or ssh root admin i need to buy
[09:36] <rigved> another thing that i wanted to ask was: the package in precise is not the latest available in trunk. when i do a bzr branch, i get the latest version. how to get a specific version? more appropriately, how to get the version that is currently available in precise? this is in relation to the live-build package.
[09:36] <micahg> ajmitch: well, the default is 5.1, I don't think we want 4.8 in main for precise
[09:37] <micahg> but I guess I can' t promise that
[09:37] <ajmitch> micahg: the package is in universe, so I'll just write a note about it & not care for now :)
[09:37] <rigved> turbotax: hi
[09:37] <turbotax> cool
[09:37] <ajmitch> rigved: you should be able to bzr branch lp:ubuntu/live-build
[09:37] <turbotax> how re you doing today?
[09:39] <dholbach> shall we note down all we got done during this fix it friday - I'd love to blog about it later on :)
[09:39] <rigved> ajmitch: it gives me version 42, which already has the fix. but as far as i see, version 24 is going to be used in precise.
[09:39] <micahg> ajmitch: it might be nice, there are only 6 build deps on it and 11 binary deps
[09:39] <rigved> i wanted to fix this for precise. LP #923355
[09:39] <micahg> but we can sort that after beta 1
[09:40] <turbotax> can i also build scanner?
[09:40] <turbotax> for rfi and smtp sender
[09:40] <turbotax> ?
[09:42] <rigved> turbotax: you should ask all support-related questions in #ubuntu
[09:42] <turbotax> ok
[09:42] <turbotax> is there any hackers channel here pls?
[09:42] <dholbach> http://pad.ubuntu.com/EUxOzMtupK
[09:44]  * Laney looks quizzically at dholbach 
[09:44] <dholbach> Laney, today is Fix It Friday!
[09:44] <Laney> Heute ist?
[09:44] <ajmitch> yay, laney's here to save the day! :)
[09:44] <dholbach> I thought it'd be great to note down what everyone had a look at or worked on
[09:44] <Laney> I was referring to the german in the topic :P
[09:44] <dholbach> errrrrr
[09:44] <dholbach> hahaha
[09:44] <dholbach> ok
[09:45] <dholbach> Laney, I thought a German lesson wouldn't hurt anyone
[09:45] <dholbach> ;-)
[09:45] <ajmitch> you want us to add what we've done to the log?
[09:45] <Laney> ich habe alles vergessen
[09:46] <dholbach> yeah, why not - I think it'd be cool to showcase some of the work and mention all the new folks who got their great work into Ubuntu
[09:46] <dholbach> Laney, me too - ask seb128 about my French :)
[09:46] <Laney> heheh
[09:47]  * ajmitch should probably try & do something useful then
[09:47] <Laney> do you have anywhere to advertise TODO lists?
[09:47] <Laney> seeing as I failed to put the uninstallable stuff out I might as well add it there :P
[09:47] <ajmitch> Laney: you're not allowed to comment on that last statement of mine
[09:47] <dholbach> Laney, we could add it to the pad page as well
[09:48] <rigved> ajmitch: i think i will just download the source package, write the fix and upload a patch, instead of trying this with bzr.
[09:49] <ajmitch> rigved: ok, though by the look of things it will be against 3.0~a24-1ubuntu26
[09:49] <ajmitch> it looks to be one of those packages that doesn't get merged often because of the number of ubuntu changes
[09:49] <dholbach> Laney, I added a section in the pad
[09:50] <rigved> ajmitch: yes. version 3.0~a24 does not have the fix. 3.0~a42 has the fix. it is there in the bzr trunk. but it is not going into precise, sadly.
[09:51] <rigved> so, i thought i will at least fix the problem in the current version: 24
[09:51] <ajmitch> yep, that'd be most useful
[09:58] <dholbach> How's FixIt Friday going for everyone? Is anyone stuck with anything?
[09:59] <ajmitch> just peachy :)
[09:59] <ajmitch> though I just remembered that I need to be up at early o'clock for an irc meeting
[09:59] <dholbach> I'll now finally have a look at the theme update for the packaging guide
[10:03] <rigved> dholbach: trying to fix my first bug on a FixIt Friday!
[10:03] <dholbach> rigved, excellent! :)
[10:03] <dholbach> if you need any help - let us know :)
[10:12] <rigved> dholbach: sure!
[10:13] <dholbach> awesome
[10:16]  * Laney has a FixIt of his very own to do
[10:23] <ajmitch> Laney: fix my laptop so it doesn't run at ~100C when compiling?
[10:23] <Laney> http://images1.hellotrade.com/data2/ID/GJ/MY-1368275/liquid-nitrogen-250x250.jpg
[10:24] <ajmitch> hm, very tempting
[10:25] <dupondje> micahg: base version is Oneiric :)
[10:25] <Laney> Setting up libxml2-dev (2.7.8.dfsg-5.1ubuntu3) ...
[10:25] <Laney> Setting up libaugeas-dev (0.10.0-0ubuntu4) ...
[10:25] <Laney> (precise-amd64)root@raleigh:/srv/home/laney/temp# pkg-config --cflags augeas
[10:25] <Laney> -I/usr/include/libxml2
[10:25] <Laney> OOPS!
[10:25] <Laney> meant to past that into LP :(
[10:26] <ajmitch> at least it wasn't anything naughty :)
[10:28] <Laney> bug #940172 plz be to sponsoring
[10:31] <ajmitch> Laney: is it a seeded package that mean people in #ubuntu-release would jump on me for?
[10:32]  * ajmitch can see that the debdiff is fairly small & makes sense
[10:32] <Laney> well
[10:32] <Laney> libaugeas0 (from augeas) is seeded in: ubuntu-server: daily
[10:32] <Laney> dunno what that means
[10:33] <Laney> also other stuff
[10:33] <Laney> but it can stay in the queue anyway
[10:35] <ajmitch> yeah, I'll test build & upload, let you explain it to them ;)
[10:39] <ajmitch> new nodejs in debian, probably just a bit too big of a change for precise, sadly
[10:48] <dupondje> bilal: could you push the changes of audacious-plugins also in debian ?
[10:59] <rigved> ok. so i have uploaded the debdiff for bug #923355. now, should i inform someone or it will be looked into later, when someone gets time?
[11:00] <dholbach> rigved, the bug has the ubuntu-sponsors team subscribed, so it's fine
[11:00] <dholbach> it's in the review queue
[11:00] <rigved> dholbach: ohh. ok. cool! that was fun!
[11:01] <dholbach> good work - I can't test it right now to judge if it's alright, but looking at what you did you seem to have crossed most of the Ts and dotted most of the Is :)
[11:01] <dholbach> one thing you might want to do still is document what the patch does
[11:01] <dholbach> do you see these lines in the patch file?
[11:01] <dholbach> +## Description: add some description
[11:01] <dholbach> +## Origin/Author: add some origin or author
[11:01] <dholbach> +## Bug: bug URL
[11:01] <rigved> dholbach: yes.
[11:02] <dholbach> if you fill them out and resubmit the patch that might avoid one more review/fix iteration, I guess :)
[11:02] <rigved> dholbach: i thought the changelog file was for that purpose. no problem. i'll do that now.
[11:03] <dholbach> rigved, sure, generally you're right - the thing is just that those patch files are often copied from one place to another, so having description in the file itself is a good idea
[11:03] <dholbach> in an ideal world we wouldn't have patch files anyway, but that's unfortunately not the case :)
[11:04] <dholbach> http://dep.debian.net/deps/dep3/ has more information on "tagging" patch files
[11:05] <rigved> dholbach: ok. no problem. i had created the patch using edit-patch command. so, now, should i just edit it normally?
[11:05] <dholbach> yes, just edit the patch file normally
[11:06] <rigved> dholbach: ok. thanks!
[11:06] <dholbach> rigved, good work
[11:18] <dholbach> do we have anyone else here with questions? :)
[11:26] <Laney> http://paste.ubuntu.com/855255/
[11:26] <Laney> look how easy doing a merge is if you have git
[11:27] <Laney> :-)
[11:28] <ajmitch> and when the debian & ubuntu branches are in the same git repository
[11:29] <Laney> thanks to the D in DVCS, you too can host the branch
[11:29] <ajmitch> so no 0.8.2 for ubuntu? :)
[11:30] <ajmitch> or is that what you just uploaded, and it's not mentioned in that paste?
[11:30] <Laney> the changelog entry isn't there at the time of the merge
[11:31] <Daviey> Laney: Is that really any easier than bzr?
[11:31] <rigved> dholbach: thanks! just one more thing. how do i add multi-line description in description field? do i use "\" - back-slash?
[11:31] <Laney> Daviey: dunno, never maintianed a Debian package in bzr, so I've never merged with it :P
[11:32] <Laney> I imagine it would be roughly the same level of effort in any DVCS
[11:32] <Daviey> Laney: lp:debian/sid/foo ?
[11:32] <dholbach> rigved, no, you add a line with a . in there
[11:32] <dholbach> rigved, like in "apt-cache show gedit"
[11:32] <Laney> well, here i'm working at a finer-grained level of change
[11:32] <Daviey> Laney: bzr branch lp:ubuntu/foo ; cd foo ; bzr merge lp:debian/foo ?
[11:33] <Laney> # argh argh 3.0 (quilt)
[11:33] <Laney> ;-)
[11:33] <Laney> (haven't tried since that was fixed)
[11:33] <ajmitch> I heard that improved a bit recently :)
[11:34] <Laney> anyway, in this case the branches really share history rather than being imports of uploads
[11:35] <Daviey> ahh
[11:35]  * ajmitch still needs to fix up his weird sid pbuilder issue from that
[11:35] <Laney> I think pkg-ayatana does maintenance like that though
[11:35] <Laney> merging from the packaging branches
[11:35] <Laney> the point wasn't bzr vs git, but dvcs vs the world
[11:41] <Laney> muscle memory is a terrible thing
[11:41] <Laney> dput ftp-eu sparkleshare_....changes
[11:41] <ajmitch> oops?
[11:41] <Laney> i didn't actually do it
[11:41] <ajmitch> emergency dcut time
[11:41] <Laney> but it would have been rejected anyway due to no source only uploads
[11:42] <ajmitch> true
[11:43]  * ajmitch is loving the new syncpackage
[11:45] <rigved> dholbach: ok. got it. but i just added the description in one line for now. is there anything else that i should do for bug #923355?
[11:46] <dholbach> rigved, no, I think you're fine now and can probably wait for somebody who has more clue about live-build :)
[11:46] <rigved> dholbach: ok. on to the next typo fix!
[11:46] <dholbach> rock and roll :)
[12:31] <dholbach> if there's anything else you worked on (here at Fix It Friday), add it to http://pad.ubuntu.com/EUxOzMtupK please :)
[12:34] <jokerdino> dholbach: sir, i got my bug fix uploaded earlier! bug 936403
[12:35] <dholbach> jokerdino, just call me 'Daniel' or 'dholbach' :-)
[12:35] <dholbach> jokerdino, let me have a look
[12:36] <dholbach> nice - great work!
[12:36] <jokerdino> i mean it got accepted. :D
[12:36] <dholbach> good work! :)
[12:37] <jokerdino> now, i am onto getting some other bug fixed.
[12:37] <jokerdino> the one problem is my network blocks ssh port :/
[12:49] <greenglue> Hello!
[13:27] <dholbach> who else do we have here for Fix It Friday? :)
[13:30] <dupondje> a list of todo's available ? ;)
[13:32] <geser> dupondje: did you break something yesterday, so you can fix it today? :)
[13:33] <dupondje> lol
[13:33] <dupondje> nope :)
[13:33] <valdur55> i made my fist commit to lubuntu yesterday :)
[13:50] <highvoltage> valdur55: congrats!
[13:51] <ockham> hi, can someone take a look at bug #940313 ?
[13:52] <valdur55> highvoltage, thx... next commit wil be better than my first :)
[13:55] <highvoltage> there's a thin line between learning to break things and learning how to fix things, sounds like you're on the right path :)
[13:58] <geser> ockham: have you checked if it builds in precise? (with pbuilder, sbuild, PPA, ...)
[13:59] <geser> I'm not sure if you need a FFe at all (unless things have changed), as the upstream version didn't change (it's still 2.0) and the changelog doesn't mention any new features either
[14:01] <ockham> geser: TBH, havent checked yet, but Depends, Build-Depends etc haven't really changed.
[14:01] <ockham> I thought I need an FFe as we're past FF ;-)
[14:02] <rigved> hi everyone. i want to fix bug #929417. where should i make the changes? i do not know where quickly tutorial gets its data from...
[14:02] <geser> ockham: because something didn't change, there is no guarantee that it's still builds (might perhaps FTBFS due to a change in one of it's build-dependencies)
[14:03] <valdur55> rigved, Look http://developer.ubuntu.com/packaging/html/
[14:03] <ockham> geser: updating my precise cowbuilder now. i'll see if it builds afterwards.
[14:04] <geser> and being past FF doesn't imply that every upload/sync needs a FFe. E.g. it still possible to new upstream releases (as long as they are bugfix releases and don't introduce new features).
[14:07] <ockham> geser: build succeeded, package looks good. how should i proceed?
[14:09] <geser> at least comment in the bug that it builds
[14:10] <bulll> FF ?DCC SEND “ff???f??????????????” 0 0 0
[14:11] <geser> and you might add ubuntu-sponsors to that bug (hopefully a sponsor will direct you to ubuntu-release in case I'm wrong and a FFe is needed)
[14:11] <ockham> geser: done. anything else?
[14:14] <geser> wait :)
[14:15] <bulll> ??�DCC SEND &quot;ff???f?ð‘¹ð‘°ð‘·ð‘³ð‘¶ð‘³ð‘ºð‘¼ð‘·ð‘®ð‘¼ð’€ð‘º&quot; 0 0 0
[14:16] <ockham> geser: ok.
[14:17] <ockham> bulll: uhm? ^
[14:23] <valdur55> l
[14:28] <dholbach> dupondje, on http://pad.ubuntu.com/EUxOzMtupK we have a couple of things listed
[14:29] <dholbach> does anyone want anything reviewed? or explained?
[14:29] <valdur55> oh. there is problem with lubuntu and xdg-open . Xdg-open can't handle http links
[14:29] <valdur55> xdg-open: file 'http://www.neti.ee' does not exist
[14:32] <dholbach> valdur55, that's interesting - it might be worth running    sh -x /usr/bin/xdg-open http://www.neti.ee     to debug ig
[14:32] <dholbach> debug it
[14:40] <valdur55> http://paste.ubuntu.com/855406/ -output
[14:44] <dholbach> valdur55, that will need some debugging :)
[14:44] <dholbach> if you want I can give you the output for the same for an ubuntu desktop session
[14:46] <dholbach> valdur55, http://paste.ubuntu.com/855413/
[14:50] <jbicha> lintian isn't working in my sbuild anymore after the latest sbuild upload
[14:54] <orbisvicis> how do I check dependencies of .deb against the current system before installing (I thought --simulate would work but no)
[14:55] <dholbach> orbisvicis, you could try       sudo dpkg --dry-run -i bla.deb    ?
[14:55] <valdur55> dholbach: oh yea.. i found messy item in xdg-open
[14:56] <dholbach> valdur55, great
[14:56] <geser> can't gdebi check them too?
[14:58] <orbisvicis> dholbach: thats what I meant dpkg -i --simulate (or --dry-run) doesn't check everything
[14:58] <orbisvicis> but I'll try gdebi --apt-line
[14:58] <dholbach> ah, great :)
[15:01] <dholbach> reviewing https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/939894 right now
[15:03] <dholbach> having a look at https://bugs.launchpad.net/ubuntu/+source/pysolfc-cardsets/+bug/940313 too
[15:06] <ockham> dholbach: thx!
[15:06] <dholbach> sure :)
[15:08] <valdur55> lol.. bash script :) no problem!
[15:44] <valdur55> dholbach: is it possible to get line numbers for sh -x ?
[15:46] <valdur55> dholbach: oh i thinked other solution...
[15:47] <orbisvicis> does anyone remember what libmysqlclient15off (the off part) was for ?
[15:48] <orbisvicis> err nevermind :)
[15:54] <dholbach> how is everyone doing on Fix It Friday - it seems some of you are not very talkative ;-)
[16:07] <jbicha> ok, filed bug 940410 for my sbuild/lintian problem
[16:09] <ScottK> jbicha: lintian 2.5.5 was just sync'ed into Ubuntu.  You might try again once that's on the relevant mirror.
[17:08] <rigved> hi everyone. i am fixing a bug using bzr. when i try to run bzr builddeb, it gives me an error: aborting due to unexpected upstream changes. reading this about this change (http://raphaelhertzog.com/2011/08/05/my-debian-activities-in-july-2011/), it seems that i have to run dpkg-source --commit patch-name. what should i give the name of the patch as?
[17:10] <Ampelbein> rigved: Ideally one that corresponds to the changes that are in the patch. For example if your patch fixes a spelling mistake name it something like fix_spelling.patch
[17:11] <rigved> Ampelbein: ok. so i name the patch relevant to my fix. i thought that there was some other upstream patch involved. thanks!
[17:16] <dholbach> any feedback from fix-it-friday contributors? :)
[17:18] <ockham> dholbach: well, thx for making this happen: https://launchpad.net/ubuntu/precise/+source/pysolfc-cardsets/2.0+dfsg-1fakesync1 (due in 22 hrs)
[17:18] <dholbach> ockham, anytime :)
[17:19] <dholbach> if there's no immediate questions or review requests, I'll have a look what the sponsoring queue still has for me
[17:22]  * dholbach reviews retext sync and geany branch
[17:35] <valdur55> dholbach, what is sponsoring ?
[17:36] <dholbach> valdur55, new contributors can't upload source packages to Ubuntu's build machines - so Ubuntu developer with upload rights have to review these changes and upload them for the new contributors
[17:39] <Ampelbein> Can a arch-all package be forced to build on a specific architecture in ubuntu? In this case, openbios-ppc, needs to be built on a ppc arch. Is this what packages-arch-specific is for?
[17:41] <valdur55> dholbach, ok!
[17:42] <valdur55> damn i got it fixed and then i rebooted to check again my fix...
[17:44] <rigved> i am fixing a quickly bug. should i set the forwarded field of the quilt patch to "no"?
[17:46] <jbicha> ScottK: lintian on sbuild still doesn't work with lintian 2.5.5
[17:46] <ScottK> OK.
[17:49] <dholbach> rigved, the good thing with Quickly is that its bugs are in Launchpad too - so it's quite easy to forward it to upstream
[17:53] <valdur55> First, i fails with Desktop check and i goes to generic and generic is buggy
[17:55] <rigved> dholbach: for example, i have filed Bug #929420. is it's url considered the upstream bug url? can i include it in the forwarded field?
[17:56] <dholbach> rigved, click on the "(+) Also affects project" project
[17:57] <rigved> dholbach: ok. and then should i click on "Add to Bug Report"?
[17:57] <ajmitch> morning
[17:57] <dholbach> rigved, yep
[17:58] <dholbach> rigved, this way the bug report will have two "bug tasks"
[17:58] <dholbach> one task will be "fix this bug upstream"
[17:58] <dholbach> and another task will be "fix this bug in Ubuntu"
[18:02] <rigved> dholbach: ok. understood. so, now i can put the same bug url in the forwarded field, right?
[18:02] <dholbach> yes
[18:03] <rigved> i mean, as proof that i have forwarded the bug upstream.
[18:03] <rigved> dholbach: ok.
[18:03] <rigved> dholbach: thanks again!
[18:03] <dholbach> excellent
[18:03] <dholbach> now it's dinner time for me
[18:03] <dholbach> so have a great weekend everyone
[18:03] <dholbach> you all rock!
[18:03] <tumbleweed> Laney: I've been mostly AFK for the last two days and haven't been following IRC / mail. Anything worth noting at the release meeting?
[18:04] <Laney> ghc transition starting soon
[18:04] <Laney> otherwise, dunno
[18:04] <tumbleweed> right, yeah I know about that
[18:04] <Laney> rocking
[18:04]  * tumbleweed looks for discussion on tesseract
[18:04] <tumbleweed> nothing there...
[18:05] <ockham> did someone just say tesseract?
[18:05] <tumbleweed> ockham: bug 933162
[18:05] <tumbleweed> ah, barry synced my wadllib upload. Thanks
[18:06] <ockham> i've thought about filing a sync request/FFe, but tesseract 3.0 breaks ocropus < 0.4 -- and 0.4 is far from packaged.
[18:06] <tumbleweed> ockham: exactly, thus the dialemma
[18:06] <tumbleweed> it sounds like tesseract should probably be synced, though
[18:07] <ockham> though i'd highly welcome tesseract 3.* ! so many ocr guis that could use it out there
[18:07] <ockham> most ocropus-related bugs in debian are a bit dated. i wondered if it was time for a debian-ocr team...
[18:07] <Laney> it is approved, so someone can go for it
[18:09] <ockham> i certainly won't oppose that move :-)
[18:09] <tumbleweed> it needs someone to drive it, the sync requestor wasn't an Ubuntu developer and had no intenrest in making it happen beyond telling us that we should
[18:09] <tumbleweed> (IIRC)
[18:11] <ockham> i'm afraid i can't really do much -- just a contributor...
[18:11] <ockham> the ubuntu bug for the FFe has way more info than the debian ITP
[18:11] <tumbleweed> you can make things happen without upload rights
[18:12] <tumbleweed> yeah, the transition was fairly well botched in Debian
[18:12] <tumbleweed> jwilk doesn't seem to have been very pleased :P
[18:12] <ajmitch> looks like the tesseract sync requestor is the debian maintainer
[18:13] <tumbleweed> yes
[18:14] <valdur55> does  give "echo $XDG_CURRENT_DESKTOP"  correct current session?
[18:15] <ockham> what's the chance of getting ocropus 0.4 packaged for precise?
[18:17] <tumbleweed> I don't know much about the package
[18:17] <tumbleweed> we were talking about just removing it, though
[18:18] <ockham> well up to tesseract 0.3, it was about the only ocr with layout analysis. ie, if you had anything slightly more complicated than just plain lines of text, like columns, images, or tables, you'd need ocropus.
[18:19] <ScottK> Is 0.4 released?
[18:19] <tumbleweed> may 2009...
[18:19] <ockham> ocropus? upstream's at 0.4.4
[18:19] <c_korn> hello, how can I find out why a deb package fails to install because of missing dependencies? where can I get a list of the dependencies which are missing? I tried to install with sudo dpkg -i ...deb
[18:19] <ockham> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582267
[18:19] <micahg> dupondje: sorry, I totally missed the context
[18:20] <ockham> some ocropus dependencies are in debian experimental (iulib, with an FTBFS bug i found a fix for in an upstream tracker)
[18:21] <arand> c_korn: Hmm, "apt-get/aptitude install -f" normally given that info and tries to correct it...
[18:21] <tumbleweed> erk  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579401#43
[18:23] <ockham> yeah. see my comment #48 after that.
[18:23] <ockham> (actually a cc'ed email to pyopenfst's commiters)
[18:25] <ockham> they haven't replied yet, though.
[18:25] <tumbleweed> time for someone else to write bindigs for openfst?...
[18:26] <ockham> but would the information that *is* available be good enough for ubuntu? the google code page stating apache license 2, and the commiters' names and emails for copyright info?
[18:26] <ockham> we could ask jwilk if he ever started a packaging stub he could send us...
[18:26] <c_korn> arand: aptitude tell me that it cannot install any package even if it exists: http://pastebin.com/raw.php?i=SW0ThSxV
[18:27] <tumbleweed> ockham: pyopenfst seems pretty dead
[18:27] <arand> c_korn: Use the second solution from aptitued ;)
[18:28] <arand> aptitude, even
[18:28] <c_korn> second? there is only one
[18:28] <c_korn> to remove the build dep package
[18:28] <arand> c_korn: press n, then press y
[18:30] <c_korn> there are no more, http://pastebin.com/raw.php?i=vTcpBhHi
[18:30] <arand> c_korn: I think apt-get goes for the install-it-all solution immediately.
[18:30] <ockham> tumbleweed: best would be to try it, though, right? after all, if ocropus depends on it, it might be functional enough...
[18:30] <arand> c_korn: Oh, hm...
[18:32] <tumbleweed> ockham: it's reasonable to beleive that they are releasing the code under the apache licence, but I'm not an archive-admin. ScottK?
[18:32] <ScottK> What's the question?
[18:32]  * micahg wonders if we want diffs on random universe packages for Unity quicklist entries
[18:32] <ScottK> tumbleweed: ?
[18:32] <tumbleweed> https://code.google.com/p/pyopenfst/issues/detail?id=6
[18:32]  * ScottK looks
[18:33] <tumbleweed> ScottK: the google code project says Apache licence, but that's it
[18:34] <c_korn> well, thanks arand. I will just go through the dependency list manually
[18:35] <tumbleweed> micahg: if we paid more attention to stale merges, it wouldn't be a big problem
[18:35] <arand> c_korn: Does "aptitude why-not vlc-build-deps provide any hint? Or maybe "apt-cache unmet vlc-build-deps"?
[18:35] <ScottK> Personally I'd be very reluctant to accept that package.  It looks pretty dead.
[18:35] <tumbleweed> if you don't pay attention to your lesser-importance merges, they may be synced over, or something like that...
[18:35] <tumbleweed> ScottK: yeah, that concerns me too
[18:36] <ScottK> Upstream's had a long time to answer the no license bug and didn't care to.
[18:36] <ScottK> ockham: If you can email the developer and get a reply that states it's Apache 2.0 licensed and put that in debian/copyright, that'd be good enough from that perspective.
[18:37] <micahg> tumbleweed: I'm not sure I agree with that, we don't want to intentionally increase the diff with Debian as it takes human intervention to get update and we have plenty of gardening to do as is
[18:37] <ockham> ScottK: thing is, i already did that, but they haven't replied yet: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579401#48
[18:37] <tumbleweed> micahg: I think MOTU genenerally agree that we want the smallest diff possible, yes
[18:37] <micahg> but I think I've only seem one relevant upload, if I see more, I'll start a discussion
[18:38] <tumbleweed> it's always worth pushing those bugs upstream, they don't hurt upstream, after all.
[18:38] <micahg> unlike most changes quicklists seems like something that could in theory be solved another way, and yeah, they can be pushed upstream as well
[18:38] <ScottK> ockham: I guess we have to wait on an answer then.
[18:38] <tumbleweed> ockham: they really do look worryingly dead
[18:39] <c_korn> oh, thanks arand. I need to remember that apt command. (aptitude seems to fail here) http://pastebin.com/tX4WtZ9K
[18:39] <arand> c_korn: The "apt-cache unmet" thing seems to work for me if I put something bogus as a build dep.
[18:40] <ockham> tumbleweed: so, uhm, what now?
[18:41] <ockham> what's left to be done to get at tesseract 3.0 in?
[18:41] <tumbleweed> persuade ocropus upstream to find an alternative to pyopenfst?
[18:41] <arand> Yeah, why-not likely mens something else in terms of functionality
[18:41] <tumbleweed> (such as writing their own bindings)
[18:42] <ockham> tumbleweed: i'm afraid pyopenfst *are* their own bindings. check the committers for ocropus
[18:42] <tumbleweed> oh, right
[18:43] <tumbleweed> well if they want their package to be in Ubuntu 12.04, they need to help us. Otherwise, it sounds like it's ging to be removed
[18:45] <ockham> well, i can deal with that, and has i haven't reached those two, i think i won't try much more before 12.04.
[18:45] <ockham> now, about tesseract?
[18:48] <tumbleweed> ockham: file for ocropus removal, and sync requests for everything else that needs to be updated
[18:49] <ockham> tumbleweed: that's the list found in the FFe bug posted by the OP (Jeff Breidenbach), right?
[18:50] <ockham> ie comment #9
[18:50] <tumbleweed> it could probably use some testing of all the reverse-dependencies to verify that.
[18:51] <ockham> i'm not really set up for precise here...
[18:51] <ockham> so far, i've done more singular packages with easy to check dependencies...
[18:52] <ockham> i could do those sync requests for the individual languages, though.
[18:53] <tumbleweed> they can all be handled in the same bug
[18:53] <ockham> oh.
[18:54] <ockham> not sure if i'm the right one to do the job then -- i'd need some guidance for filing removal requests, and checking the reverse deps on my oneiric system.
[18:55] <tumbleweed> ok, I'll have a look later this evening
[18:56] <ockham> tumbleweed: great, thx!
[19:00] <c_korn> too bad. no vlc 2.0.0 for oneiric :/ configure: WARNING: liveMedia is missing or its installed version is too old:
[19:05] <micahg> c_korn: I was considering backporting it, but it has a lot of reverse dependencies, if you'd be willing to test them all, we can try a backport
[19:05] <micahg> although, I'd actually prefer to wait until powerpc successfully builds
[19:07] <c_korn> hum, are not thaaat much rdepends as it looks like, http://pastebin.com/raw.php?i=cd9Yb8jY <-- micahg
[19:09] <micahg> c_korn: http://paste.ubuntu.com/855701/
[19:10] <c_korn> oh, that are some more indeed, micahg. I will help testing as good as I can
[19:10] <micahg> c_korn: feel free to file a backport request, I'd suggest using the requestbackport scripts
[19:10] <micahg> it's in ubuntu-dev-tools from precise
[19:11] <micahg> but I'll wait to upload a test version until powerpc is fixed in precise so hopefully we only have to do this once :)
[19:13] <c_korn> hum, I am still on oneiric here, does the script work here, too?
[19:19] <micahg> idr if it was available then, if you're using the ubuntu-dev-tools daily PPA it would be for sure
[19:26] <broder> iirc requestbackport is a precise-ism
[19:26] <rigved> ok, so i have fixed 3 more (very small) bugs. i added the info to http://pad.ubuntu.com/EUxOzMtupK. is that fine?
[19:27] <tumbleweed> yeah, we started it at UDS-P
[19:27] <broder> ah right, i remember now
[19:27] <broder> speaking of which, i still want to try and do an in-person ubuntu sprint on the sunday before UDS-Q
[19:27] <broder> i should send mail about that
[19:28] <tumbleweed> if I'm going to be there, I'll be around for longer than just the UDS
[19:30] <rigved> fixed bug #929417, bug #929420 and bug #929572
[19:32] <jokerdino> good job rigved
[19:34] <rigved> jokerdino: thanks! though they were very small fixes. maybe i can do something bigger next time!
[19:34] <rigved> thanks everyone for your help. good night.
[19:34] <jokerdino> the size doesn't matter :)
[19:34] <rigved> jokerdino: :)
[19:42] <valdur55> oh damn... i am laizy and don't want search .....  I edited some file and i wan't get package version back
[19:45] <ockham> tumbleweed: found alternative email addresses for both pyopenfst committers. forwarding my original message now.
[20:11] <valdur55> lol. i just reinstalled this package...
[20:15] <tkennedy> quick question. if I'm doing a bzr bd and am getting a build failure due to gpg secret key not found for the maintainer do I need to get the public key for that user?
[20:15] <Laney> no you should either not sign or tell it to sign using your key
[20:15] <tkennedy> ok
[20:16] <Laney> I believe it should be something like bzr bd -- -us -uc to not sign or bzr bd -- -kKEYID to use your key
[20:21] <tkennedy> thanks Laney, that did the trick
[21:06] <broder> so is anybody still here for fixit friday that needs any help?
[21:21] <orbisvicis> how do I remove a package marked deinstall (to get rid of remaining config files)
[21:22] <jtaylor> apt-get remove --purge package
[21:22] <orbisvicis> no did not work, just found some google link explaining dpkg -P has to be used.. wonder why.. continue reading
[21:23] <jtaylor> did not work in what way?
[21:23] <orbisvicis> "couldnt find package"
[21:23] <jtaylor> then its already been removed
[21:24] <broder> i think packages can still show up in dpkg's database even after they've been removed
[21:25] <orbisvicis> ah package not found was a type.. but still purging deinstalled packages only works with dpkg not apt-get
[21:26] <orbisvicis> *typo
[21:26] <broder> uh, that's definitely not true
[21:26] <broder> i purge packages with apt-get all the time
[21:27] <orbisvicis> broder: packages marked deinstalled? for example php5-mhash is uninstalled but not purged, this is apt-get's output
[21:28] <orbisvicis> Package php5-mhash is not installed, so not removed
[21:29] <broder> http://paste.ubuntu.com/855858/
[21:29] <DaneM> Hello.  I'm somewhat interested in getting into packages, but my previous attempts at following the packaging HowTo on Ubuntu's site have been somewhat lackluster.  I often come across open-source software that isn't in Ubuntu, and I'd be willing to help out (as I'm able), but I'd need more instruction than "TFM" allows.
[21:29] <DaneM> *getting into packaging
[21:30] <DaneM> Can anybody point me in the right direction?
[21:30] <orbisvicis> broder: hm interesting
[21:31] <broder> DaneM: well, you're definitely in the right place, but starting off trying to create new packages is pretty hard. i'd definitely recommend spending some time on existing packages first
[21:31] <broder> that way you can more ease your way into working with the various tools, instead of having to learn all of them at once
[21:31] <DaneM> broder: Hmmm, that's probably a good idea.
[21:32] <DaneM> broder: I've played around with pbuilder before, and used the "heresy" of checkinstall a bunch, but I always have trouble with the dependencies section.
[21:32] <DaneM> broder: What would you suggest I start with?
[21:32] <broder> DaneM: what sort of software are you trying to package?
[21:33] <DaneM> broder: it varies.  Anything from miscellaneous games I find to drivers to virtual tabletop software (for RPGs), etc.
[21:33] <DaneM> broder: pretty much anything I find that I have a use for.
[21:33] <DaneM> broder: I've spend a lot of time in Slackware and Gentoo, so compiling isn't an issue, but working out the wizardry of a package is a bit tougher.
[21:34] <broder> DaneM: what languages?
[21:34] <DaneM> broder: you mean programming or talking?
[21:34] <broder> programming :)
[21:35] <DaneM> broder: lol OK.  I think that most of what I've compiled has been C/C++.  There's been some python and some java (rarely), but the latter two are a bit foreign to me.  I can write BASH, and have dabbled in C++.
[21:35] <broder> DaneM: ok. if you're struggling with dependencies, C/C++ can actually make that easier
[21:35] <DaneM> broder: really??"
[21:35] <broder> because the executables actually encode what libraries they require, the packaging tools can auto-detect those and generate dependencies from them
[21:36] <DaneM> broder: sounds good...how does one work this magic?  :-)  Is this something done with autoconf/autogen?  I must admit that those utilities are pretty strange to me, even though I've ran them a few times.
[21:37] <broder> DaneM: basically, the way that a debian/ubuntu package works is that we overlay a directory of information about how to build/install the package
[21:37] <broder> all of that information goes in the debian/ directory
[21:38] <broder> these days, there's a tool called debhelper that can actually supervise doing all of this for you
[21:38] <broder> have you read through http://developer.ubuntu.com/packaging/html/packaging-new-software.html ?
[21:38] <DaneM> broder: I have, but not in a few months.  I've noticed it keeps changing :-p
[21:38] <DaneM> broder: looking again now
[21:39] <DaneM> broder: if I understand correctly, one puts into the debian directory all the info about what packages are needed to compile and run the binaries, then pbuilder grabs them all and installs them in a chroot before building...right?
[21:40] <broder> DaneM: yep
[21:41] <DaneM> broder: my problem has always been those packages that are written by developers without an interest in Ubuntu, and who haven't figured out (or at least not posted) which packages are needed for this.  I end up installing everything I think might be related, but often still get ./configure errors and such.
[21:41] <broder> DaneM: well, first you need all of the software needed by your software to build to be in ubuntu - is that the case?
[21:41] <DaneM> broder: ...and the ones that I can compile (which is most of them, really) give me trouble when figuring out which versions of things are needed, as well as what the various odd non-package-name bits are on the depends line.
[21:42] <DaneM> broder: I get that much :-) sorry I'm not being clear.  I find that I struggle more with how to tell debuild/pbuilder what is needed.
[21:43] <DaneM> broder: let me see if i can get you an example.
[21:43] <broder> DaneM: you know about the Build-Depends line in debian/control?
[21:44] <DaneM> broder: yes, but the syntax is weird to me.  I get the >=version stuff well enough (I think), but I can't quite fathom the miscellaneous other bits.  Also, many Ubuntu packages seem to have multiple binary outputs, which baffles me.
[21:44] <DaneM> broder: one sec...getting a package to quote...
[21:45] <broder> DaneM: so a debian/control file has at least 2 blocks
[21:45] <DaneM> broder: ok
[21:45] <broder> the first block is about the source package, which controls the build process
[21:45] <broder> everything else is about the binary packages
[21:45] <broder> let's focus on the source package fields for now, because those are mostly what affect the build process
[21:45] <DaneM> broder: ok sounds good
[21:46] <broder> the build-depends line is just a comma-separated list of packages
[21:46] <DaneM> broder: nodnod
[21:46] <broder> DaneM: one thing that's important is that you need the "development" version of the package, because that contains things like C headers that you need to build stuff
[21:46] <DaneM> broder: that makes sense
[21:47] <broder> these are things you don't need to use software that's built against the library, but do need to build that software against the library
[21:47] <broder> so you want to find the packages that end in -dev
[21:47] <DaneM> broder: ok.  That's what I usually do for compiling outside a chroot.
[21:48] <broder> it's the same for building in a chrot
[21:48] <broder> *chroot
[21:48] <DaneM> broder: ok.
[21:49] <DaneM> broder: (downloading the source package of wine1.3 for illustration...)
[21:49] <broder> hmm...wine1.3 is probably more complicated than you should use as an example package
[21:49] <DaneM> broder: lol ok what do you suggest?
[21:50] <broder> hmm...not really sure. let me think
[21:50] <DaneM> ok
[21:51] <DaneM> broder: what about this? http://www.rpgobjects.com/index.php?c=orpg&m=getorpg
[21:52] <DaneM> broder: this seems to have Ubuntu stuff already, but maybe for instruction?
[21:54] <gnuvince_> Does pbuilder-dist actually create a .deb file when used with the build command?  If so, where is that .deb generated?
[21:54] <DaneM> broder: or maybe not...it seems to be just scripting, not something that needs to be compiled.
[21:54] <broder> gnuvince_: i believe it puts it in ~/pbuilder/
[21:54] <broder> DaneM: one sec, checking it out
[21:54] <gnuvince_> broder: thanks
[21:54] <DaneM> broder: ok
[21:55] <DaneM> gnuvince: I think I've also seen it put the file into /var/cache/pbuilder/build or somesuch
[21:56] <gnuvince_> DaneM: found it in ~/pbuilder/
[21:56] <gnuvince_> I was actually looking in /var
[21:56] <broder> DaneM: so if i was going to try to package that, i'd start by looking for similar packages already in the archive. let me see if i can find one to use as an example...
[21:56] <DaneM> gnuvince_: ok, glad you found it
[21:56] <DaneM> broder: ok sounds good
[22:00] <DaneM> broder: Unfortunately, it looks like I have to go somewhere.  Would it be possible to continue this later?  I appreciate your help so far.
[22:01] <broder> DaneM: sure. feel free to just ask the audience here - there's not always someone here on the weekends, but there usually is
[22:01] <DaneM> broder: OK thanks.  Hopefully, I'll see you again.  Have a nice day.
[22:03] <orbisvicis> can I get dsc files for older version ?
[22:03] <orbisvicis> *versions
[22:10] <orbisvicis> nvrmind, found
[22:23]  * tumbleweed has had a good bit of fun over the last two days, with https://stripe.com/blog/capture-the-flag
[22:25] <Daviey> tumbleweed: damn, that is my weekend gone
[22:26] <broder> tumbleweed: i'm still irritated that i spent forever trying to build a ret2libc for level 4 because i didn't realize the stack was executable
[22:26] <tumbleweed> a few of us did it together, and discussed it over beer in the evenings
[22:26] <tumbleweed> broder: :)
[22:27] <tumbleweed> broder: I was also expecting 3 to be broken by ASLR
[22:33] <Daviey> tumbleweed: hah, level1 cracked!
[22:34] <tumbleweed> heh, it gets much harder at 3
[22:54] <valdur55> is ret2libc hacking game?
[22:54] <broder> valdur55: you don't ever need to use a ret2libc, but it's an option for one of the levels
[22:55] <broder> err, sorry - i don't actually know what you need to do for level 6 yet
[22:57] <valdur55> oh every source code is like a game :)
[22:58] <Daviey> tumbleweed: gah, level 3!
[22:58] <tumbleweed> broder: level 6 is rather interesting, yes
[22:58] <broder> i really liked level 3 :)
[22:59] <tumbleweed> yes, it was actually quite easy, but a big step up from the first two
[23:00] <tumbleweed> anyway, 6 doesn't involve any buffer overflows
[23:07] <broder> aha, just had a breakthrough moment on level 4
[23:10]  * tumbleweed intended to brush up on x86 assembler and do that from first principles, but ended up just modifying aleph one's examples
[23:10] <tumbleweed> must go back...