[00:08] <grunthus> Thanks lifeless, found out its like this:
[00:08] <grunthus> https://code.launchpad.net/~chris-ascentsoftware/ubuntuone-control-panel/fixes_715820
[01:01] <arand> Do most(all) packages use xpm files for icons?
[03:28] <c2tarun> I am grabbing a package by grab.merge.sh script and its automatically applying the patch. I updated the .quiltrc file but still nothing happned. I tried to pop the patch but No patches found. When I am pushing I am getting Hunk** failed. What should I do?
[05:08] <c2tarun> I am grabbing a package by grab.merge.sh script and its automatically applying the patch. I updated the .quiltrc file but still nothing happned. I tried to pop the patch but No patches found. When I am pushing I am getting Hunk** failed. What should I do?
[05:12] <artfwo> c2tarun, are you trying to undo the patch, which is applied after unpacking source package?
[05:17] <c2tarun> artfwo: yup
[05:17] <artfwo> c2tarun, but why do you want to undo the patch?
[05:18] <c2tarun> artfwo: unless I wont pop the patch I wont be able to create proper source package. I will always get error that hunk failed.
[05:19] <artfwo> I thought, if a package uses quilt, it should automatically unapply the patch when creating source package
[05:20] <artfwo> which package are you trying to merge?
[05:20] <c2tarun> artfwo: freevo
[05:22] <artfwo> c2tarun, did you fix the conflict in debian/rules?
[05:22] <c2tarun> artfwo: I think so, the line in ubuntu is just a comment, so all I need to see is how the package responds with debian line.
[05:23] <artfwo> so, you want to build the base debian version?
[05:24] <c2tarun> artfwo: I'll do that as well, its the only way to check that I should call for a sync or merge>
[05:24] <artfwo> (I'm still downloading the source package, so I have trouble figuring your problem)
[05:25] <c2tarun> artfwo: I can wait :)
[05:27] <c2tarun> artfwo: in rules file there are two lines including two mk files. They are grabbing them from my system, but they are not present there.
[05:27] <c2tarun> artfwo: one is debhelper.mk and other is python-distutils.mk
[05:28] <artfwo> c2tarun, these are files from cdbs
[05:28] <artfwo> they're supposed to be present in /usr/share/cdbs
[05:29] <artfwo> and cdbs is a build-dependency for freevo
[05:29] <c2tarun> yup they were missing, I installed build deps and done. :)
[05:32] <c2tarun> artfwo: hey pacakge is build succesfully. :/
[05:33] <artfwo> c2tarun, I've managed to build it too just a moment ago
[05:33] <c2tarun> artfwo: sorry but I was not aware that packages get automatically unapplied. I ran into a package trouble 2 days ago and I thought I should be careful :(
[05:34] <artfwo> I only had experience with 3.0 format (quilt) and cdbs, so I can't say that's true for all packaging schemes
[05:37] <c2tarun> artfwo: BTW you build the package with debian line in rules file or without it?>
[05:46] <c2tarun> what about this error: dpkg-source: error: File ./freevo_1.9.0.orig.tar.gz has size 34309907 instead of expected 27182867
[05:53] <c2tarun> ping^^
[06:14] <c2tarun> can anyone please help me with this error: dpkg-source: error: File ./freevo_1.9.0.orig.tar.gz has size 34309907 instead of expected 27182867
[06:37] <c2tarun> can anyone please help me with this error: dpkg-source: error: File ./freevo_1.9.0.orig.tar.gz has size 34309907 instead of expected 27182867
[07:09] <artfwo> c2tarun, sorry I was away
[07:11] <c2tarun> artfwo: no prob :)
[07:11] <c2tarun> artfwo: can you help me with that error?
[07:12] <artfwo> i don't know the reason, why this error occurs
[07:12] <artfwo> but I'd just redownload freevo_1.9.0.orig.tar.gz and overwrite the file in the merge directory
[07:12] <artfwo> and to answer your question, I've built the package with the Ubuntu fix
[07:13] <c2tarun> artfwo: you tested your build on pbuilder?
[07:14] <artfwo> no, by simply running debuild on my working system
[07:14] <c2tarun> artfwo: try testing it on pbuilder as well.
[07:15] <artfwo> I cannot do this right now, because I have a slow internet connection here
[07:15] <artfwo> does it build in pbuilder for you?
[07:16] <udienz> c2tarun, conratulation your merge (epdfview) has been approved
[07:16] <c2tarun> nope I got that error of size mismatch. Can you please tell me the size of your orig.tar.gz
[07:16] <c2tarun> udienz: thanks :)
[07:16] <artfwo> c2tarun, my orig.tar.gz is exactly 27182867 bytes
[07:17] <c2tarun> artfwo: hmm.... that is weird. that means something is wrong with grab.merge.sh script?
[07:17] <artfwo> unlikely, because I downloaded the merge tree by running grab-merge.sh
[07:18] <c2tarun> artfwo: but you just said that you redownloaded the orig tarball and overwrote the file in merge directory.
[07:18] <artfwo> no
[07:18] <artfwo> I said, I would do that, if I needed to fix the error :)
[07:19] <artfwo> or just remove the entire merge directory and start over
[07:19] <c2tarun> artfwo: hmm... that may be a better option, but still my problem is unexplained :( I am going to  try :)
[07:20] <artfwo> well, I cannot explain it, but maybe someone else here can
[07:21] <c2tarun> i'll try it from start :) and wait for some to explain my prob :) thanks for helping. I'll request a merge when I'll complete it :)
[08:37] <c2tarun> artfwo: ping
[08:38] <c2tarun> can anyone please take a look at this bug for sponsorship bug 721686 Thank you
[08:39] <artfwo> yes, c2tarun?
[10:27] <c2tarun> need sponsorship bug 721686 thank you
[10:33] <shadeslayer> c2tarun: +	#rm debian/tmp/usr/share/freevo/icons/themes/geexbox/mimetypes/folder.png
[10:33] <shadeslayer> if we don't need that, remove it
[10:34] <shadeslayer> and the changelog is wrong
[10:34] <shadeslayer> -freevo (1.9.0-10) unstable; urgency=high << Why did you remove that?
[10:35] <shadeslayer> c2tarun: fix the changelog please :)
[10:37] <shadeslayer> kthxbai
[10:56] <hakermania> bdrung: Hello, what's going on with wallch's review :) ?
[13:05] <ari-tczew> bdrung: dget https://launchpad.net/ubuntu/+archive/primary/+files/gdk-pixbuf_2.23.0-1ubuntu2.dsc and try to run update-maintainer
[16:23]  * RainCT wonders if anyone here is using Ubuntu with a touch screen
[18:00] <hyperair> is there any tool that creates a dsc out of an orig.tar.gz and debian.tar.gz  file?
[18:02] <ScottK> You could do it by hand, but it'd take a few steps.
[18:04] <hyperair> hmm yeah
[18:05] <geser> why can't you "unpack" the source and call "dpkg-source -b" on it?
[18:06] <hyperair> i could
[18:06] <hyperair> but then debian.tar.gz would change checksums
[18:06] <hyperair> though i guess it doesn't really matter
[18:34] <ari-tczew> hyperair: why are you taking to sponsor a bug assigned to someone else?
[18:34] <hyperair> ari-tczew: er
[18:34] <hyperair> which bug?
[18:34] <ari-tczew> hyperair: bug 721702
[18:35] <hyperair> oh sorry about that
[18:35] <hyperair> i guess i didn't refresh the page
[18:35] <ari-tczew> ...
[18:36] <hyperair> ari-tczew: also, i didn't realize there was a custom to assign a bug to the sponsor. i thought it was assigned to the sponsoree.
[18:37] <ari-tczew> hyperair: o_O
[18:38]  * hyperair shrugs
[18:38] <hyperair> maybe i'm outdated
[18:38] <hyperair> but that was the practice before i became motu
[18:38] <hyperair> and i haven't sponsored stuff for some time as i was pretty busy
[18:40] <ari-tczew> hyperair: so advices for future: 1st refresh the page before taking a look
[18:40] <ari-tczew> 2nd check whether bug reported and assigned is the same person
[18:40] <hyperair> ari-tczew: more like i was already taking a look, but didn't assign the bug to myself.
[18:40] <hyperair> ari-tczew: but yes, i'll keep an eye out for it in the future[
[18:40] <ari-tczew> reporter*
[18:40] <hyperair> thanks
[18:41]  * hyperair reads through https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue again
[18:48] <ari-tczew> hyperair: and 3rd in future if you're taking bug to sponsor, assign to myself
[18:48]  * hyperair nods
[18:49] <c2tarun> need help with this control file entry http://paste.ubuntu.com/569292/
[18:49] <c2tarun> I think the Maintainer and XSBC* entry will be the one of ubuntu one, but I am not sure about the other two entries. Can anyone please help
[18:49] <hyperair> update the Vcs- fields
[18:50] <hyperair> keep the *Maintainer fields
[18:51] <hyperair> looks like ampache has moved from svn to git.
[18:51] <ari-tczew> c2tarun: I really encourage to patch d/control manually
[18:52] <ari-tczew> so get debian source, unpack by dpkg-source -x *.dsc and do merge professionally
[18:53]  * hyperair stuff everything into git and lets it do the merge
[18:53] <ari-tczew> sometimes it will get more time but you will get to know how it works
[18:53] <hyperair> stuffs*
[18:54] <c2tarun> actually I am new and dont know what git is actually, so even If i do it manually I'll not be able to understand, Can you please give me any documentation on git?
[18:56] <mok0> c2tarun: better do it manually then
[18:56] <ari-tczew> +1 ^^
[18:58] <c2tarun> mok0 ari-tczew: ya I can take a look on control file manually :) but still it will be the same entries separately that are mentioned together in the control file by mom.
[19:00] <atagar> Hi (again). A package I maintain was just added to natty (https://launchpad.net/ubuntu/natty/+source/tor-arm/1.4.0.1-2) - can I now file a ticket to request a backport or should I wait until natty has been released?
[19:00] <ari-tczew> c2tarun: changes (delta) will be the same yes but you don't have a mess in d/control
[19:00] <ari-tczew> atagar: you can do it right now
[19:01] <atagar> fantastic - thanks
[19:01] <mok0> c2tarun: It seems the maintainer moved from svn to git for maintaining the package
[19:01] <c2tarun> mok0: what are svn and git actually?
[19:04] <c2tarun> !svn
[19:04] <c2tarun> !git
[19:06] <mok0> c2tarun: there you go :-)
[19:06] <hyperair> mok0!
[19:07] <ari-tczew> c2tarun: looking on ampache example, I guess easier is unpack current natty's source and add Debian changes from -10 revision
[19:08] <ari-tczew> (*10.patch)
[19:08] <ari-tczew> but you have to do it manually on unpacked natty's source of ampache
[19:10] <c2tarun> ari-tczew: after adding the debian changes I have to run update-maintainer that will change Maintainer and XSBC* entries, and as mok0 told that maintainer moved from svn to git, I think those entries will be good in debian's control. so I think these entries will be good for control file http://paste.ubuntu.com/569294/  can you please take a look.
[19:11]  * hyperair recommends using something like meld
[19:11]  * ari-tczew wonders if maintainer has switched to git why these changes are not in Debian...
[19:11] <hyperair> ari-tczew: the Vcs- fields were updated in the debian revision though..
[19:11] <hyperair> ari-tczew: and the merge is bringing them in
[19:11] <ari-tczew> hyperair: so what's the problem
[19:11] <hyperair> ari-tczew: nothing?
[19:12] <c2tarun> so should I make the changes as I suggested?
[19:14] <ari-tczew> c2tarun: let me grab-merge ampache
[19:14] <c2tarun> ari-tczew: sure.
[19:17] <mok0> hi hyperair
[19:17] <hyperair> hey mok0
[19:17] <hyperair> long time no see. =D
[19:18] <mok0> hyperair: indeed
[19:18] <hyperair> =)
[19:20] <mok0> meld is good. /me loves meld
[19:23]  * iulian nods.
[19:25] <ari-tczew> old army? :)
[19:27] <c2tarun> ari-tczew: grabbed the package?
[19:28] <ari-tczew> c2tarun: not yet, I have to finish some things
[19:28] <c2tarun> sure :) I'll wait, just ping me.
[19:37] <ari-tczew> c2tarun: OK grabbed. I had to recreate MoM patches, as well. Why recreate? See more info on bug 711454
[19:40] <zooko> So is the 24th of this month -- Thursday -- the deadline for https://bugs.launchpad.net/ubuntu/+source/tahoe-lafs/+bug/719092 ?
[19:40] <ari-tczew> c2tarun: OK I see d/controls right now, could you ask me again on what do you wonder?
[19:40] <c2tarun> ari-tczew: Not getting, what do you mean by wrong patch?
[19:40] <ari-tczew> .pc files in patches created by MoM
[19:41] <c2tarun> ari-tczew: actually what do you mean by wrong? How can a patch be a wrong? I mean if it is wrong the package wouldn't compile.
[19:43] <ari-tczew> c2tarun: this is probably bzr issue, MoM just gives you messed patches
[19:43] <ari-tczew> if you want to get clear patches, you have to do these commants:
[19:43] <ari-tczew> debdiff ampache_3.5.4-9.dsc ampache_3.5.4-10.dsc > ampache_3.5.4-10.patch
[19:43] <ari-tczew> debdiff ampache_3.5.4-9.dsc ampache_3.5.4-9ubuntu4.dsc > ampache_3.5.4-9ubuntu4.patch
[19:44] <c2tarun> ari-tczew: and I was wondering about Vcs-svn and Vcs-Browser entries, in older version maintainer was using Svn, but in newer it is git, so What the entries should be?
[19:46] <c2tarun> ari-tczew: I think the entries should be as I mentioned in my pastebin.
[19:46] <ari-tczew> c2tarun: ampache_3.5.4-9ubuntu4.patch shows current Ubuntu delta and I don't see changed Vcs-* fields, so don't touch this and keep Debian style.
[19:55] <ari-tczew> udienz: Write in bug 721722 why this sync is necessary point out to bug of sync squid3.
[19:56] <c2tarun> ari-tczew: I have a question, I builded the new native debian version of ampache on natty machine, and it builded succesfully. Is it still necessary to merge? I mean why merge when it is building without any problem?
[19:59] <c2tarun> ari-tczew: exactly I mean why apply ampache_3.5.4-9ubuntu4.patch when its not needed?
[20:00] <ari-tczew> c2tarun: builded is english wrong, built is OK
[20:01] <c2tarun> ari-tczew: sorry :9
[20:01] <c2tarun> :(
[20:01] <ari-tczew> c2tarun: fact that package built fine it doesn't mean that you can drop all changes.
[20:02] <c2tarun> ari-tczew: it means if mom fails we have to merge?
[20:02] <ari-tczew> c2tarun: I have to know that merging process are not always can be automatically done by MoM. It usually has to be done manually.
[20:02] <ari-tczew> s/I have/You have
[20:03] <c2tarun> ari-tczew: actually I was thinking about a sync, if the package is built succesfully than we can also go for sync? am i right?
[20:03] <ari-tczew> c2tarun: You must understand changes done in Ubuntu and figure out whether and which changes are incorporated in Debian. Then you have to sort out which changes are still nedeed in Ubuntu.
[20:05] <ari-tczew> c2tarun: Did you check whether changes from Ubuntu were incorporated in Debian?
[20:07] <c2tarun> ari-tczew: hmm... according to changelog, there are many changes for ubuntu, how can i check whether these changes are incorporated in debian or not?
[20:09] <ari-tczew> c2tarun: Open ampache_3.5.4-9ubuntu4.patch and ampache_3.5.4-10.patch and compare.
[20:09] <c2tarun> ari-tczew: I think they are incorporated, please look the debdiff of ampache_3.5.4-10.dsc ampache_3.5.4-9ubuntu4.dsc
[20:11] <ari-tczew> c2tarun: Yes, all changes have been incorporated in Debian. It's ready to sync,
[20:11] <c2tarun> ari-tczew: good :) still I dont know how to sync :(
[20:20] <c2tarun> !sync
[20:27] <hggdh> why would a quilt patch (first patch in the series) fail, but a 'patch --dry-run' on the patch succed?
[20:27] <ScottK> Quilt (IIRC) assumes -p1.  Maybe you had it different for the dry run?
[20:28] <hggdh> no, I had -p1: http://pastebin.ubuntu.com/569316/
[20:29] <hggdh> oops. hum... I dry-ran on a different patch, let me check again
[20:30] <hggdh> nope dry-run still succeeds
[21:06] <hggdh_> got it
[21:10] <c2tarun> need help in filing a sync request. Error: failed to connect mx.launchpad.net. What is mx.launchpad.net?
[21:25] <jmarsden> c2tarun: mx.launchpad.net is the machine indium.canonical.com, at IP 91.189.90.7
[21:26] <c2tarun> why did requestsync failed to connect?
[21:27] <c2tarun> jmarsden: ^^
[21:29] <jmarsden> c2tarun: Sorry, I don't know the answer to that, I am not anything official at Canonical or Launchpad :)  Do you have good working connectivity to mx.launchpad.net ?  You might want to ask in #launchpad
[21:30] <c2tarun> jmarsden: thanks :) I'll try once more if it fails again, I'll ask on #launchpad
[21:49] <zooko> Anybody want to help upgrade Tahoe-LAFS in Ubuntu?
[21:49] <zooko> There has been much talk recently about Freedom-Compatible tools, including Tahoe-LAFS.
[22:12] <lifeless> zooko: what help do you need?
[22:14] <zooko> lifeless: hm...
[22:14] <zooko> lifeless: take the package v1.7.1 that is already in Ubuntu, upgrade it to the latest release, build a new package. :-)
[22:15] <jmarsden> zooko: https://wiki.ubuntu.com/PackagingGuide/Complete#Updating%20an%20Ubuntu%20Package
[22:17] <zooko> I don't have a working linux system at the moment.
[22:18] <zooko> Although I might soon if this dual boot project works out.
[22:19] <lifeless> zooko: what system do you have?
[22:22] <zooko> lifeless: OSX
[22:26] <hggdh_> ari-tczew: hi, sorry for the delay, bug bug 663925 now has a branch for lucid-updates
[22:26] <lifeless> zooko: doesn't that come with a vm thingy?
[22:27] <ari-tczew> hggdh_: hi! ok thanks for spending time on it. :-)
[22:31] <zooko> lifeless: I could install virtualbox and install ubuntu in vbox.
[22:31] <hggdh_> ari-tczew: also, this is my first branch, so please correct me
[22:31] <zooko> That is approximately as much work as installing ubuntu dual-boot,...
[22:31] <ari-tczew> hggdh_: OK.
[22:38] <lifeless> zooko: I find that having any secondary platforms available as vms makes adhoc fixes on those platforms a lot easier
[22:38] <lifeless> zooko: thats the only reason I suggest it
[22:44] <ari-tczew> hggdh_: could you add DEP3 tags to patch?
[22:54] <hggdh_> ari-tczew: darn! I forgot -- again... will do
[22:54] <ari-tczew> hggdh_: I pointed out issues on branch review.
[22:54] <hggdh_> ari-tczew: going there noew
[22:58] <hggdh_> ari-tczew: same format as my original patch to Maverick? I remember you had some issues there, but I do not remember which -- http://pastebin.ubuntu.com/569371/
[23:00] <ari-tczew> hggdh_: Generally yes, but would be nice to have a note in description that you have adjusted this patch to 0.4.1.
[23:00] <hggdh_> ari-tczew: sure, will do
[23:00] <hggdh_> ari-tczew: no problem is it is an update to the branch?
[23:01] <ari-tczew> hggdh_: No, but I guess I can't merge branch directly, since there is no lucid-proposed branch.
[23:02] <ari-tczew> It will be direct upload to archive via dput.
[23:05] <hggdh_> and -- IIRC -- we cannot set it to lucid-proposed, correct?
[23:06] <hggdh_> I guess this is what you said...
[23:06] <ari-tczew> hggdh_: Yes, we cannot.
[23:13] <hggdh_> ari-tczew: done
[23:13] <hggdh_> oh hell, indication applet is barfing continuously...