[00:00] <shadeslayer> maxwellian: hehe.. i have a 40 GB / thats 13 GB used :
[00:01] <maxwellian> shadeslayer: Me too, I think 40 gig.  I pretty much screwed my Windows partition when I installed Ubuntu, it runs out of disk all the time. :P
[00:01] <maxwellian> shadeslayer: Serves it right.
[00:02] <shadeslayer> maxwellian: true :D
[00:03] <maxwellian> tumbleweed: Sorry, just to be sure, are you saying most of the savings are gained through a cache?
[00:18] <tumbleweed> maxwellian: no, I'm saying you can save some bandwidth with a proxy. But for the ocassional pbuildering it's possibly not worth it
[00:24] <shadeslayer> tumbleweed: bug 603831
[00:24] <shadeslayer> i dont understand what you mean
[00:25] <shadeslayer> did  debian release a new version?
[00:25] <shadeslayer> nope..
[00:30] <shadeslayer> tumbleweed: bug 604102 , rbot can be syncd
[00:31] <micahg> shadeslayer: you should change the merge bug to a sync bug then
[00:31] <shadeslayer> micahg: hmm ok
[00:32] <shadeslayer> micahg: done
[00:32] <shadeslayer> build log is attached
[00:50] <tumbleweed> shadeslayer: re fprint-demo: you attached an ubuntu to ubuntu diff. Where's the debian to ubuntu diff
[00:53] <shadeslayer> meh.. how did i not see that :S
[01:01] <tumbleweed> shadeslayer: re rbot: when you have dealt with a reviewers comments, you should set the bug back to new/confirmed and re-subscribe sponsors. (no need to do that now, because I'm looking at it)
[01:02] <shadeslayer> tumbleweed: oh.. i didnt know
[01:03] <tumbleweed> also, for sync bugs, it helps if you have set a public e-mail address in launchpad, then the ack-sync tool can automatically use it.
[01:03] <shadeslayer> hmm
[01:03] <shadeslayer> tumbleweed: i can set it now
[01:03] <tumbleweed> thanks
[01:04] <shadeslayer> tumbleweed: i just have to unselect Hide my email addresses from other Launchpad users , right?
[01:05] <tumbleweed> yes
[01:05] <shadeslayer> done
[01:26] <shadeslayer> tumbleweed: thanks :)
[01:27] <shadeslayer> uh.. it failed 0_o
[01:28] <shadeslayer> how come it built in pbuilder and failed in buildd
[01:29] <shadeslayer> http://launchpadlibrarian.net/51750280/buildlog_ubuntu-maverick-i386.rbot_0.9.15%2Bpost20100705%2Bgitb3aa806-2_FAILEDTOBUILD.txt.gz << if anyone can tell me why it failed
[01:29] <tumbleweed> shadeslayer: read the buildlog, it explains. I'm off ot bed
[01:29] <shadeslayer> tumbleweed: i am reading it...
[01:29] <shadeslayer> tumbleweed: thanks anyways
[01:29]  * shadeslayer is not sure what the error means
[01:33] <shadeslayer> anyone else around to help? :)
[01:35] <shadeslayer> brr... im off to sleep as well
[01:42] <micahg> shadeslayer: empty translations files?
[01:57] <DaVinci> hello
[01:59] <YokoZar> hmm, why did imagemagick disappear from maverick archive...
[02:02] <micahg> YokoZar: looks like it's there
[02:04] <jmarsden> YokoZar: rmadison -s maverick imagemagick says: imagemagick | 7:6.6.2.6-1 |      maverick | source, amd64, i386
[02:22] <YokoZar> micahg: jmarsden: so why does http://packages.ubuntu.com/search?keywords=imagemagick  not show any results for maverick?
[02:22] <micahg> YokoZar: it probably doesn't show any results for anything in maverick
[02:22] <YokoZar> ahh ok
[02:23] <YokoZar> it has a maverick search box though ;)
[02:23] <micahg> YokoZar: yeah, that site's been having issues, it's known though
[07:59] <dholbach> good morning
[08:38] <bilalakhtar> Someone, please help me with http://launchpadlibrarian.net/51744908/buildlog_ubuntu-maverick-i386.krename_4.0.4-2ubuntu1_FAILEDTOBUILD.txt.gz
[08:45] <bilalakhtar> Someone, please help me with http://launchpadlibrarian.net/51744908/buildlog_ubuntu-maverick-i386.krename_4.0.4-2ubuntu1_FAILEDTOBUILD.txt.gz
[08:51] <bilalakhtar> sebner: you there?
[08:52] <Rhonda> Server is too old for streaming pull, reconnecting.  (Upgrade the server to Bazaar 1.2 to avoid this)
[08:52] <sebner> bilalakhtar: just entered, yes
[08:52] <Rhonda> I get this message when I do a bzr checkout of the planet-ubuntu config.
[08:54] <bilalakhtar> sebner: please help me with http://launchpadlibrarian.net/51744908/buildlog_ubuntu-maverick-i386.krename_4.0.4-2ubuntu1_FAILEDTOBUILD.txt.gz
[08:58] <sebner> bilalakhtar: I'm no kde guy but either you have a wrong versioning in your controls file or the kde libs are currently b0rken in the archibe
[08:59] <sebner> *archive
[09:00] <bilalakhtar> sebner: ok, I will push the package to my PPA for another test build.
[09:20] <Laney> bilalakhtar: why don't you try asking in
[09:20] <Laney> ...in #kubuntu-devel?
[09:21] <Laney> in general if someone doesn't answer it means that nobody knows
[09:22] <sebner> huu Laney :)
[09:22] <Laney> alright boss
[09:23] <bilalakhtar> Laney: thanks
[09:58] <Rhonda> cjwatson: Any news on the packages site? Just curious, not pushing.
[09:59] <Rhonda> … or any other canonical employee who could take a look for me in the internal RT?
[10:04] <cjwatson> Rhonda: I haven't heard anything
[10:07] <Rhonda> Ah, alright. It sounded a bit like that elmo would take a look last time we spoke. But I can understand that he tries to contact Frank first.
[12:24] <SpamapS> So, the CEPH project produces their own userspace tool .deb's and debian source packages.. debian doesn't have them yet though (there's an ITP but its gone a bit stale). Since upstream produces debs.. can Universe take those directly until Debian gets the packages?
[12:29] <ripps> Can someone help me get my wacom-dkms package into ubuntu. It doesn't seem the kernel is going to fix the broken bamboo ctl-460 (and other new models) anytime soon. I have a working packages for lucid and maverick in my ppa:ripps818/wacom. I have the current version of my package uploaded to REVU
[12:38] <ripps> http://revu.ubuntuwire.com/p/wacom-source
[14:10] <shadeslayer> micahg: how come it builds on my pbuilder then 0_o
[14:18] <shadeslayer> ScottK: poke
[14:18] <shadeslayer> http://launchpadlibrarian.net/51750280/buildlog_ubuntu-maverick-i386.rbot_0.9.15%2Bpost20100705%2Bgitb3aa806-2_FAILEDTOBUILD.txt.gz
[14:18] <ScottK> Looking
[14:19] <shadeslayer> ScottK: thanks :D
 shadeslayer: empty translations files? << thats what micahg said
[14:20] <ScottK> Yep.
[14:20] <ScottK> Figure out why that's happening.
[14:20] <shadeslayer> ScottK: but why does it build in pbuilder then?
[14:21] <shadeslayer> and it does seem the file is empty
[14:21] <EzraR> anyone want to review a package on REVU? It has one advocation already and I have fixed the remaining problems.
[14:21] <EzraR> http://revu.ubuntuwire.com/p/mangler
[14:23] <ScottK> shadeslayer: Because your pbuilder chroot doesn't have pkgbinarymangler installed.
[14:24] <ScottK> That's on the buildds, but not part of the standard install
[14:50] <shadeslayer> hmm
[15:39] <geser> shadeslayer: because you don't pkgbinarymangler installed (and enabled) in your pbuilder
[15:40] <shadeslayer> geser: yeah ScottK mentioned that...
[15:40] <shadeslayer> geser: altho i dont understand the concept of pkgbinarymangler
[15:40] <shadeslayer> !pkgbinarymangler
[15:40] <shadeslayer> :S
[15:40] <geser> !info pkgbinarymangler
[15:41] <shadeslayer> geser: hmm.. so that translations go into another package?\
[15:42] <geser> not exactly, they got put into an own tar which then somehow into LP (rosetta), but I don't know the details
[15:43] <dpm> shadeslayer, geser -> here are the details: https://wiki.ubuntu.com/Translations/TranslationLifecycle
[15:46] <dpm> basically, pkgbinarymangler extracts translations from a package, puts them in a tarball and imports them into Launchpad. Then these are exposed to translators at translations.lp.net/ubuntu to complete or change. Their translations are periodically exported from Launchpad in a big tarball containing all translations, which is fed to the langpack-o-matic script, which ultimately produces a set of language pack packages, which contain the transaltions
[16:12] <hyperair> is there a way i can glob files in python?
[16:13] <hyperair> like the equivalent of for file in *someglobpattern*; do something_with_$file; done
[16:20] <danohuiginn> hyperair: http://docs.python.org/library/glob.html
[16:20] <hyperair> aha, thanks.
[16:22] <Laney> hyperair: porting git-archive-all?
[16:24] <hyperair> Laney: *sigh* yea.
[16:25] <Laney> you get all the fun :)
[16:25] <hyperair> Laney: it's easy enough to do half-baked support for submodules, but proper support for submodules needs recursion.
[16:27] <hyperair> hmm maybe i'll just work around it.
[16:28] <Laney> what's wrong with that?
[16:28] <Laney> just recursively archive-all the submodules
[16:48] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek starting in 12 minutes in #ubuntu-classroom
[17:16] <shadeslayer> anyone around to help me with rbot ?
[17:16] <shadeslayer> im stuck with the fact that one of the translations is empty :p
[17:16] <geser> still the same problem or a new one?
[17:17] <geser> the .pot files, right?
[17:17] <shadeslayer> geser: same problem,but i was thinking that i could use the current git checkout and use that translation as a patch
[17:17] <shadeslayer> geser: yes
[17:18] <shadeslayer> meh.. its empty in git too
[17:18] <shadeslayer> geser: ^
[17:20] <shadeslayer> geser: seems some translations are empty...
[17:20] <geser> add "find -empty -name '*.pot' -delete" to the clean target to make pkgstriptranslations happy
[17:21] <shadeslayer> geser: ok.. and the new version would be 1ubuntu1 right?
[17:22] <geser> yes
[17:22] <shadeslayer> geser: and i guess testing in pbuilder is useless :P
[17:23] <geser> no, install pkgbinarymangler inside your pbuilder (and enable it) and you can reproduce the problem in your pbuilder
[17:26] <shadeslayer> geser: how do i enable it in pbuilder?
[17:29] <geser> "pbuilder login --save-after-login"; "apt-get install pkgbinarymangler"; edit "/etc/pkgbinarymangler/stripstranslations.conf" (the file is inside the pbuilder) and set 'enable: true'
[17:31] <geser> and while you are it you could check if "/etc/pkgbinarymangler/santitychecks.conf" is also enabled (enable: true). Don't remember if it's enabled by default or if I changed it.
[17:32] <geser> and if you want that your pbuilder also creates .ddebs install "pkg-create-dbgsym" too
[17:32] <shadeslayer> geser: delta debs?
[17:33] <geser> debug debs, those with the debug symbols
[17:33] <shadeslayer> ok
[17:36] <shadeslayer> geser: i see a control.in file.. is that required?
[17:37] <geser> no, some packages generate the control file from a template (control.in)
[17:37] <shadeslayer> geser: so i can remove it?
[17:40] <geser> I don't know if the package really needs it in this case, but it creates an unnecessary delta if you remove it
[17:41] <shadeslayer> yeah.. ill leave it as such then
[17:48] <shadeslayer> geser: http://pastebin.com/JKKJL9C8
[17:49] <geser> but you got a source package?
[17:49] <shadeslayer> yes
[17:49] <shadeslayer> geser: i guess thats the work of the clean rule i added
[17:50] <geser> yes, and you can ignore those warnings
[17:50] <MTecknology> What's the right way to install a file to /etc/default/ just install -f my_file /etc/default/ in rules ?
[17:50] <geser> shadeslayer: it because the file deletion can be stored in the .debian.tar.gz but that is no problem here as we remove them on every clean call
[17:51] <geser> MTecknology: IIRC yes
[17:52] <MTecknology> geser: thanks
[17:54] <shadeslayer> geser: still fails :P
[17:55] <shadeslayer> this time at rbot-fortune.po
[17:55] <geser> then remove empty .po files too
[17:56] <tumbleweed> MTecknology, geser: dh_installinit will install debian/packagename.default appropriately
[17:56] <shadeslayer> geser: didnt the clean part do that?
[17:57] <geser> shadeslayer: if you look at the find call, you will notice that it only delete empty files matching "*.pot"
[17:58] <shadeslayer> ohh
[18:00] <MTecknology> tumbleweed: thanks
[18:02] <shadeslayer> geser: http://pastebin.com/vqL3MfZC
[18:03] <geser> shadeslayer: what exactly did you change in debian/rules?
[18:04] <shadeslayer> geser: i added find -empty -name '*.pot *.po' -delete in the clean part
[18:05] <shadeslayer> geser: http://pastebin.com/W6eb0DBt
[18:06] <shadeslayer> now come to think of it.. i should just to *.po*
[18:08] <geser> yeah, that would work
[18:12] <shadeslayer> geser: seems to work now
[18:12] <geser> shadeslayer: or "find . -empty \( -name '*.pot' -o -name '*.po' \) -delete" if you only want to match those two cases
[18:15]  * shadeslayer has to learn regexp
[18:16] <geser> and the syntax of find
[18:17] <shadeslayer> geser: regex first since im using it in ruby as well
[18:17] <shadeslayer> :P
[18:18] <shadeslayer> geser: your rule seems to work too
[18:18] <ryanakca> How can I force something into /usr/local ? dh_usrlocal seems to insist on trying to clobber everything I try to put there.... (It's a work related package with hardcoded paths to /usr/local ... )
[18:18] <shadeslayer> geser: redy to sponsor? :D
[18:18] <geser> yes
[18:18] <shadeslayer> *ready
[18:20] <shadeslayer> geser: want me to pastebin debdiff?
[18:20] <geser> yes, that's enough
[18:20] <shadeslayer> geser: http://pastebin.com/raw.php?i=kSSXnjhs
[18:20] <shadeslayer> geser: thanks for telling me how to do it right ;)
[18:22] <carstenh> ryanakca: by using override_dh_whatever, see man 1 dh - alternatively you could use the more verbose debian/rules variant (examples are in /usr/share/doc/debhelper/examples)
[18:22] <ryanakca> carstenh: Thanks
[18:27] <geser> shadeslayer: uploaded
[18:28] <shadeslayer> geser: thanks :D
[18:31] <ryanakca> carstenh: Hmm... now dpkg-deb quits because of files in /usr/local :/ Would it be easier just to 's@/usr/local@/usr@g' in the files that match /usr/local ?
[18:35] <carstenh> ryanakca: weird, "$ grep usr/local *" in dpkg.git/dpkg-deb/ returns nothing
[18:36] <ryanakca> sorry, dh_builddeb
[18:36] <carstenh> ryanakca: if you can adapt the hardcoded paths faster than you could convince dpkg-deb to install files to usr/local you should probably just do it ;)
[18:36] <carstenh> grep local =dh_builddeb returns nothing too
[18:37] <carstenh> (zsh, not bash)
[18:37] <ryanakca> Hmm... odd.  sed it is.
[18:39] <carstenh> ryanakca: ok, so you either spend this evening with finding the error or you use a workaround (fixing the hardcoded paths) and get time to drink a beer ... your choice
[18:49] <shadeslayer> geser: i think something is wrong with the builder :P
[18:49] <shadeslayer> its building since 20 mins :D
[18:49] <shadeslayer> and its not that huge a package
[18:50] <shadeslayer> gahhhhhh
[18:50] <geser> damn pastebin :(
[18:50] <shadeslayer> geser: :S
[18:51] <shadeslayer> geser: i gave you raw output :S
[18:51] <shadeslayer> geser: you wget'd the link?
[18:51] <geser> yes
[18:51] <shadeslayer> that explains it
[18:51] <shadeslayer> :P
[18:53] <geser> I looked over the debdiff before signing and uploading but missed it
[18:54] <geser> 2nd try :)
[19:17] <geser> micahg: Hi, as I hope that you are much more familiar with xul-ext-* packages than me: do you know if we should keep weave (binary: xul-ext-sync) in the archive or remove it again? (regarding the mozilla extension policy)
[19:18] <micahg> geser: was it accidentally sync'd?
[19:18] <micahg> geser: it'll probably be integrated into either Firefox 4 or Firefox 4.1
[19:18]  * micahg forgets if there are binary components in it
[19:18] <geser> micahg: sort of, it's a new package
[19:19] <geser> it got synced together with the other new packages as it isn't (yet) on the sync blacklist
[19:19] <geser> shadeslayer: rbot: Successfully built
[19:19] <shadeslayer> geser: whee
[19:19] <shadeslayer> geser: ++
[19:22] <micahg> geser: I'm torn, since it's arch specific, I think it should be in, but on the other hand, they plan on integrating it
[19:22] <micahg> chrisccoulson: what do you think about weave ^^^
[19:24] <micahg> geser: I'd say let's take it for the moment and we can review before beta freeze
[19:24] <geser> micahg: ok, it FTBFS too
[19:24] <micahg> geser: heh, I'll need to file a bug to add it to my package set
[20:06] <tumbleweed> shadeslayer: I'm glad to hear that :)
[21:11] <ari-tczew> porthose: thanks for sponsoring
[21:11] <porthose> :)
[21:16] <ari-tczew> porthose: do you want take next?
[21:26] <porthose> ari-tczew, sorry busy with one of my upstream, leave me a bug number and I will look later
[21:27] <ari-tczew> porthose: hmm, ok, so in this case I'm going to ask tumbleweed to sponsor: bug 604235
[21:28] <tumbleweed> looks like I'm doing too much sponsorship then... :)
[21:33] <porthose> tumbleweed, are you going to look at xmp?
[21:34] <porthose> tumbleweed, if not, I will :)
[21:34] <tumbleweed> porthose: I will
[21:35] <porthose> tumbleweed, k
[21:38] <tumbleweed> ari-tczew: please don't close the lp merge bug on the same line as "Add PulseAudio support". It makes it look like that bug was the original bug adding this support
[21:39] <ari-tczew> tumbleweed: could you move up LP: ?
[21:39] <tumbleweed> of course
[21:41] <tumbleweed> ari-tczew: besides that, looks good. building
[22:12] <ari-tczew> tumbleweed: thanks!
[22:15] <tumbleweed> garr, I keep forgetting -sa tonight
[22:16] <ari-tczew> tumbleweed: done 7 sponsorships for me
[22:30] <Laney> I saw some stats on how many packages are synced, merged, packaged separately, ... — does anyone know where these are?
[22:30] <Laney> think it was a graph
[22:31] <geser> the ones on MoM?
[22:31] <Laney> maybe. /me looks
[22:32] <Laney> ah I like that, thanks geser