[06:53] <simar> If the FTBFS starts building automatically then what to do? Should I create a bug for it...
[08:35] <and471> is it possible (and if so, can someone point me to a guide) to update a package using the ubuntu bzr branch
[08:35] <and471> i.e. https://code.launchpad.net/~ubuntu-branches/ubuntu/maverick/lernid/maverick
[08:35] <and471> and then the upstream bzr branch
[08:35] <and471> i.e. https://code.launchpad.net/~lernid-devs/lernid/trunk
[08:45] <geser> and471: https://wiki.ubuntu.com/DistributedDevelopment/Documentation has some documentation, perhaps it helps you further
[08:46] <and471> geser, thanks
[08:46] <geser> one can use those packaging branches to create the next package revision but an upload with "dput" is still needed
[09:17] <and471> geser, after following instructions here https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate I have updated the package, however I don't have upload privelledges so do I need to create a debdiff?
[09:21] <geser> or a merge proposal
[09:21] <and471> geser, which is it I need to create?
[09:22] <geser> when working with branches it's IMHO better to also create a merge proposal (but as usual depends on your sponsor)
[12:40] <ari-tczew> BlackZ: ping bug 598184
[12:48] <BlackZ> ari-tczew: feel free to take it, if you want
[12:49] <ari-tczew> ok
[13:34] <ari-tczew> who from MOTU uses amarok?
[13:34] <ari-tczew> or clementine?
[15:00] <coolbhavi> bdrung, I have attached a patch that ignores guile-pg build error there
[15:00] <coolbhavi> :)
[15:02] <ari-tczew> o, hey coolbhavi
[15:02] <ari-tczew> I want to comment on your application
[15:02] <coolbhavi> hey ari-tczew
[15:03] <coolbhavi> Its on the DMB agenda
[15:03] <coolbhavi> wiki link i meant
[15:14] <bdrung> coolbhavi: please use "Closes" instead of "DBTS". you could drop the rm command instead of making it ignoring errors
[15:16] <coolbhavi> bdrung, okay thanks for the review!
[15:21] <shadeslayer> ari-tczew: btw .. were you approved as MOTU?
[15:21] <ari-tczew> shadeslayer: never, huh?
[15:21] <shadeslayer> er what?
[15:21] <shadeslayer> were or were you not? :P
[15:22] <ari-tczew> shadeslayer: I'm not in MOTU.
[15:22] <shadeslayer> ok .. :)
[15:23] <ari-tczew> shadeslayer: everybody can comment on expectant's application.
[15:23] <ari-tczew> you, me...
[15:23] <ari-tczew> sponsors usually gives endorments
[15:24] <shadeslayer> yes.. but i just wanted to know what happened to *your* application :P
[15:24] <ari-tczew> shadeslayer: my applications was rejected.
[15:24] <shadeslayer> ok.. sorry to hear that
[15:24] <ari-tczew> shadeslayer: lol, I didn't cry due to this.
[15:25] <shadeslayer> :P
[15:25] <shadeslayer> why would you :D
[15:25] <ari-tczew> shadeslayer: you can read my application in current state.
[15:26] <shadeslayer> ari-tczew: sure ..
[15:26] <coolbhavi> done bdrung_ thanks
[15:26] <ari-tczew> shadeslayer: when do you plan approve ?
[15:27] <shadeslayer> approve?
[15:27] <shadeslayer> im not MOTU :P
[15:27] <ari-tczew> shadeslayer: I'm asking when do you plan applicate
[15:27] <shadeslayer> ah.. well .. i think in another 2 months
[15:27] <coolbhavi> shadeslayer, good luck!
[15:27] <shadeslayer> right now college + kubuntu ninjas keep me busy :D
[15:28] <shadeslayer> coolbhavi: ah thanks :D
[15:28] <shadeslayer> coolbhavi: same to you too dude :)
[15:28] <bdrung_> coolbhavi: and you can combine "(LP: #611965) (Closes: #590952)" to "(LP: #611965, Closes: #590952)" or more common "(Closes: #590952, LP: #611965)"
[15:28] <coolbhavi> bdrung_, okay!
[15:28] <bdrung_> coolbhavi: that looks better :)
[15:29] <coolbhavi> :)
[15:29] <bdrung_> coolbhavi: and please update the title + bug description
[15:29] <ari-tczew> bdrung_: which program for music do you use?
[15:29] <coolbhavi> bdrung_, sure!
[15:29] <bdrung_> ari-tczew: look at my debian qa site: xmms2
[15:29] <bdrung_> and audacious
[15:30] <ari-tczew> bdrung_: could you review clementine?
[15:30] <ari-tczew> it;s in REVU queue with 1 sponsors comment. 2nd comment needed
[15:31] <bdrung_> ari-tczew: link?
[15:31] <bdrung_> ari-tczew: what are the plans for debian?
[15:32] <ari-tczew> bdrung_: I didn't create the package, but I think about it.
[15:32] <ari-tczew> bdrung_: http://revu.ubuntuwire.com/details.py?upid=8134
[15:33] <ari-tczew> it's great
[15:33] <ari-tczew> Wyświetl tekst transliterowany na alfabet łaciński
[15:33] <ari-tczew> successor
[15:33] <ari-tczew> for amarok 1.4
[15:33] <ari-tczew> wtf copy failed ;p
[15:40] <ari-tczew> bdrung_: I don't use a Debian. Could I be a maintainer then?
[15:41] <coolbhavi> ari-tczew, yeah
[15:41] <coolbhavi> if you work on ITP in debian
[15:41] <coolbhavi> but you have to mention that you have based the work on ubuntu package
[15:42] <coolbhavi> in the changelog
[15:42] <bdrung_> ari-tczew: yes. you should have debian installed somewhere to do test (in rare casses a bug occurs only in debian and not in ubuntu). i have debian installed on a separate hard drive and in kvm.
[15:43] <coolbhavi> ari-tczew, http://packages.qa.debian.org/e/emu8051/news/20100617T184717Z.html I did the same wrt emu8051
[15:43] <coolbhavi> bdrung_, arent debian and ubuntu chroots different?
[15:43] <ari-tczew> bdrung_: I got a 20gb disk and I can install Debian there.
[15:44] <bdrung_> coolbhavi: yes. i use pbuilder to do the building.
[15:45] <coolbhavi> bdrung_, okay!
[15:46] <bdrung_> coolbhavi: in most cases i build the package locally until i am ready and then i use pbuilder to build it for the target distribution
[15:47] <coolbhavi> bdrung_, okay is there any trick to mimic sid chroot on ubuntu?
[15:48] <bdrung_> coolbhavi: it's possible. i use pbuilder for it, which creates the chroot for you.
[15:49] <coolbhavi> bdrung_, okay let me try I have been using sbuild on sid thanks for clearing my doubt :)
[15:50] <ari-tczew> does someone know whether can I check DDoS attack on my router?
[15:50] <porthose> coolbhavi, http://manpages.ubuntu.com/manpages/maverick/man1/pbuilder-dist.1.html
[15:51] <coolbhavi> thanks porthose will try tonight
[15:52] <porthose> coolbhavi, I find it very useful :)
[15:52] <coolbhavi> :)
[15:52] <ari-tczew> porthose: could you sponsors some patches for me?
[15:53] <porthose> ari-tczew, sure, I can have a look later tonight, but right now I have to go put the timing belt back on my car :(
[15:54] <bdrung_> ari-tczew: package reviewed
[16:07] <ari-tczew> BlackZ: is it possible to forward changes from giftrans package?
[16:16] <X3> hey Im trying to compile new upstream of ntfs-3g 5.22 stable when I run pdebuild I get http://pastebin.com/hZxQNDPF
[16:19] <X3> can anyone help
[16:20] <shadeslayer> dude be patient :)
[16:21] <shadeslayer> idk the error as well :p
[16:46] <Bachstelze> X3: probably depends on a more recent FUSE version
[16:47] <Bachstelze> X3: similar bug in Gentoo was fixed by making ntfs-3g depend on FUSE 2.8.0: http://bugs.gentoo.org/320579
[16:47] <Bachstelze> right now, you're using 2.7.4
[16:48] <X3> ive backported 2.81 lemme see
[17:05] <X3> i made it depend on 2.8.1 as well
[17:05] <X3> lemme try again
[17:10] <shadeslayer> X3: btw after your done with ntfs 3g, maybe you can port it to maverick ;)
[17:14] <X3> its not working
[17:14] <X3> keeps failing
[17:16] <X3> im too green to make this work
[17:16] <coolbhavi> X3, can you post log now?
[17:17] <X3> sec
[17:20] <X3> http://pastebin.com/sUdLJgqk
[17:20] <X3> there
[17:21] <coolbhavi> same error hmm
[17:21] <geser> check if a header file from fuse has this defines
[17:22] <coolbhavi> geser, +1
[17:22] <X3> wheres the file and what?
[17:22] <X3> sorry < noob
[17:23] <geser> if you don't want to install libfuse-dev, unpack it into some temporary directory and check then (rgrep)
[17:24] <coolbhavi> X3, that means check the  source for a header file which contains the function which is causing FTBFS
[17:24] <geser> and I see that the second log has also "Setting up libfuse-dev (2.7.4-1.1ubuntu4)". Didn't you update the fuse package?
[17:24] <X3> mate thats way too technincal
[17:25] <X3> ya I update it it
[17:25] <geser> but your pbuilder doesn't use it (yet). It still used the old one
[17:25] <X3> idk
[17:26] <X3> how can I clean it and start again
[17:26] <geser> pbuilder starts always from clean
[17:26] <X3> Package: libfuse-dev
[17:26] <X3> State: installed
[17:27] <X3> Automatically installed: no
[17:27] <X3> Version: 2.8.1-1.1ubuntu2~karmic1~ppa1
[17:27] <X3> Priority: optional
[17:27] <X3> Section: libdevel
[17:27] <geser> it unpacks the base.tgz, chroots into it, tries building the package there and cleans up afterwards (deletes the unpacked base.tgz again)
[17:27] <X3> ah
[17:29] <X3> idk why it keeps installing the old fuse
[17:29] <geser> because the old one is the repositories your pbuilder uses, and the new one isn't
[17:30] <X3> so how can I fix that?
[17:31] <geser> https://wiki.ubuntu.com/PbuilderHowto#Building%20With%20Local%20Packages
[17:33] <X3> thx
[17:33] <X3> my brain hurts nnow
[17:33] <X3> one would think this be all automated
[17:35] <coolbhavi> yes you can use PPA for that X3
[17:35] <coolbhavi> I think
[17:35] <X3> ya well some of this is well beyond skills
[17:36] <X3> specially when guys that know better go I think
[17:36] <X3> im too noob
[17:37] <geser> we all started with no knowledge how all this works
[17:37] <X3> ya i bet
[17:38] <X3> only i have a lack of brain
[17:38] <X3> :)
[17:41] <coolbhavi> X3, chill mate we have all been through that stage :)
[17:42] <X3> :/
[17:53] <X3> http://pastebin.com/hBcNVW1z
[17:53] <X3> idk
[17:54] <X3> i give
[17:55] <coolbhavi> X3, can you upload to a PPA and try if not to check
[17:56] <X3> ill try
[17:59] <X3> signed them and uploading
[18:00] <coolbhavi> :)
[18:00] <X3> now wait for 3 days
[18:00] <X3> and see if it fails too
[18:00] <coolbhavi> X3, yeah due to upload queue :)
[18:00] <X3> https://edge.launchpad.net/~x3lectric/+archive/experimental
[18:01] <X3> thats where I uloaded this to
[18:01] <coolbhavi> great :)
[18:01] <X3> so if this fails up there then what?
[18:02] <coolbhavi> X3, patching the ftbfs :)
[18:03] <X3> is there like any other pdebuild commands I could run to try
[18:03] <coolbhavi> X3, no its automated buildd
[18:03] <X3> :(
[18:03] <X3> i thought you knew some cheat
[18:05] <X3> got email packages accepted ok
[18:05] <coolbhavi> X3, only thing is you can have a PPA dependency or which of the ubuntu release pockets to be enabled within your PPA
[18:06] <X3> what dependency
[18:06] <X3> now its Use all Ubuntu components available.
[18:06] <X3> and default
[18:06] <coolbhavi> X3, PPA dependencies like you depend on other PPA's components
[18:07] <coolbhavi> read up more on launchpad help :)
[18:08] <X3> ya but do nyou recommend I select a ppa which builds ntfs-3g
[18:08] <coolbhavi> no
[18:08] <coolbhavi> unless you use some bleeding edge stuff
[18:08] <coolbhavi> to build packages on your PPA
[18:09] <X3> its not withing ubuntu
[18:09] <X3> ubuntu is 3.6
[18:09] <X3> im trying to compile and build on ppa 5.22
[18:09] <coolbhavi> no problems
[18:09] <X3> which is actually stable
[18:10] <X3> but im building from source
[18:10] <coolbhavi> what counts is the versions of the Build-Depends
[18:10] <coolbhavi> during build
[18:10] <X3> on ppa
[18:10] <coolbhavi> yeah
[18:11] <X3> so its gonna depend on fuse 2.8.1
[18:11] <X3> cause i made it depend on that
[18:12] <X3> doesnt it make sense then to add the fuse ppa as a dependency?
[18:12] <coolbhavi> yeah the latest version of the package available in ubuntu pockets
[18:12] <X3> thats just it
[18:13] <coolbhavi> if fuse-ppa has latest version of fuse built fine
[18:13] <coolbhavi> then you can check
[18:13] <X3> I backported the fuse i made it depend
[18:13] <X3> no the default ppa is 2.7.4
[18:14] <coolbhavi> but caution is PPA software is unstable most times and it could break the build
[18:14] <X3> idk
[18:14] <coolbhavi> thats why PPA dependency is not recommended
[18:14] <X3> well no matter
[18:15] <coolbhavi> except if you want to test bleeding edge stuff
[18:15] <coolbhavi> :)
[18:15] <X3> the ppa i uploaded ntfs-3g 5.22 already has fuse 2.8.1 built in
[18:15] <coolbhavi> hope this clears it
[18:15] <coolbhavi> :)
[18:15] <X3> thats where I backported fuse to
[18:15] <X3> bleeding edge is svn
[18:16] <X3> im using a stable release 5.22
[18:16] <X3> since old ubuntu 3.6 has a many bugs this fixes
[18:16] <coolbhavi> then no problems :)
[18:16] <coolbhavi> in giving a shot
[18:16] <X3> idk im well confused
[18:17] <coolbhavi> X3, well this happens as time goes you ll get hold of it :)
[18:18] <coolbhavi> anyways its latenight here
[18:18] <X3> you hope
[18:18] <coolbhavi> goodnight all
[18:18] <X3> nite man and thx
[18:18] <coolbhavi> X3, no mention
[18:18] <X3> just dont have any wet dreams
[18:18] <coolbhavi> sure!
[18:23] <shadeslayer> hmm
[18:23] <shadeslayer> anyone notice why nvidia-current does not have a dep on linux-headers?
[18:24] <shadeslayer> because without linux-headers, nvidia-current is fail :P
[18:29] <X3> eh ntfs-3g is already building
[18:29] <X3> ah no
[19:12] <X3> https://launchpad.net/~x3lectric/+archive/experimental/+builds?build_text=&build_state=all
[19:13] <X3> its building?? wt?
[19:47] <ximion_> Is someone interested in reviewing my package oxygen-molecule ( http://revu.ubuntuwire.com/p/oxygen-molecule )
[19:47] <ximion_> (Provides a GTK+-Theme for better integration of GTK+-apps in the KDE4 desktop)
[19:49] <shadeslayer> ximion_: it wont be packaged
[19:52] <shadeslayer> theres a valid reason for it
[19:52] <ximion_> shadeslayer: What do you mean? s/packages/sponsored/g ?
[19:52] <shadeslayer> err...
[19:52] <shadeslayer> ximion_: i meant it wont be included in archives...
[19:53] <shadeslayer> licensing issues i see
[19:53] <shadeslayer> or wait one sec
[19:54] <ximion_> shadeslayer: I thoght i resolved all license issues with upstream.
[19:54] <shadeslayer> yes i just saw that :)
[19:54] <ximion_> ...he told me that all designes are GPLv3 licensed, including the stuff he took from another theme.
[19:55] <shadeslayer> oh this went all messy... i confused it with bug 430013
[19:55] <shadeslayer> ximion_: carry on please :)
[19:56] <shadeslayer> extremly sorry for the confusion
[19:56] <shadeslayer> *extremely
[19:56] <ximion_> this bug was about making oxygen-molecule *default* in Kubuntu, like openSUSE did... I just want to have it in the repos, not more :)
[19:57] <ximion_> shadeslayer: no problem :-D
[20:28] <ximion> shadeslayer: any news?
[20:29] <shadeslayer> ximion: er what?
[20:29] <shadeslayer> im no MOTU ;)
[20:29] <ximion> shadeslayer: ...but you can comment on packages :P
[20:30] <ximion> anyway, I better wait for Jonathan Thomas to comment on the package.
[20:30] <shadeslayer> ximion: you might find him on #kubuntu-devel
[20:31] <shadeslayer> if he doesnt idle here
[20:32] <ximion> shadeslayer: Thanks! I'm not at the Kubuntu channel, so I can't know if he's there.
[20:32] <shadeslayer> hes not atm ;)
[22:02] <ari-tczew> porthose: thanks for sponsoring! I look forward to get more cooperate with you :)
[22:27] <bdrung_> \o/ sponsoring queue under 200 again
[22:30] <carstenh> if someone wants to change this ... aegir-provision/sid fixes two rc bugs ;)
[22:34] <crimsun> which LP bug reports?
[22:36] <bdrung_> carstenh: porthose requested a sync: bug #610655
[22:37] <carstenh> you are really fast :)
[22:38] <bdrung_> carstenh: he requested it three days ago :)
[22:39] <carstenh> bdrung_: wow, that is _really_ fast :)
[22:39] <carstenh> from the changelog: "Works at least for new installations; and as the package hasn't been part of a stable release, that should be okay" - this is wrong for ubuntu, maybe someone should take a closer look at it before it is synced
[22:39] <bdrung_> porthose: ^
[22:44] <carstenh> if it does not work for upgrades and someone comes up with a clean solution I could sponsor a delayed NMU to debian sid
[22:49]  * porthose places #610655 on his TODO list