[00:05] <bdrung> tumbleweed: current state of script foo: http://paste.debian.net/81773/
[00:08] <bdrung> tumbleweed: it downloads the patch and the corresponding ubuntu source package
[00:45] <techm3> .
[01:08] <techm3> Hi
[01:28] <micahg> bdrung: what do you think of my requestmerge script idea?
[01:29] <bdrung> micahg: it could be useful for people who needs sponsoring.
[01:29] <bdrung> :)
[01:29] <bdrung> micahg: you are welcome to write this tool. what should the tool do differently to requestsync?
[01:30] <micahg> bdrung: do you think it's worth factoring out common parts of requestsync/requestmerge to requestfoo?
[01:30] <bdrung> micahg: dunno. you have to check how much overlap you will have.
[01:30] <micahg> bdrung: basically the same thing except not subscribe spronsors and use the word merge in place of sync
[01:31] <bdrung> micahg: should it be for just requesting a merge without providing a debdiff?
[01:31] <micahg> bdrung: yes, I think so, so others can usefully request a merge of their favorite app
[01:32] <bdrung> micahg: hm. do you think that it will make a difference?
[01:32] <bdrung> someone has to do the work and prepare a debdiff
[01:32] <micahg> bdrung: I think makes it easy to title a merge properly and add the changelog
[01:33] <micahg> bdrung: true, but people might not realize that merge is necessary/wanted
[01:33]  * micahg guesses that's not what u-d-t is really for though
[01:33] <bdrung> micahg: really?
[01:34] <micahg> bdrung: idk, maybe no one would see it then
[01:34] <bdrung> u-d-t is mostly used by ubuntu devs
[01:34] <micahg> I guess there's no point for random people, but I guess it would be good just for devs with an optional attachment
[01:34] <bdrung> i doubt that a normal user will install u-d-t
[01:35] <micahg> to create the bug easily and mark in progress at least
[01:36] <bdrung> micahg: if requestmerge is used for requesting the merge and attaching a debdiff, then i support your idea.
[01:37] <micahg> bdrung: k, that works, I would make the debdiff optional or add an option to add one to a merge bug in case the merge will be done over a couple days so the bug can be open as a placeholder
[01:37] <bdrung> micahg: requestsync foo -> do you have a debdiff -> either attach it and subscribe u-s or ask if the requester works on the debdiff -> assigning the request
[01:38] <micahg> basically
[01:38] <bdrung> micahg: either the patch is given as cli parameter or you ask for it
[01:39] <micahg> bdrung: right, but it should still be optional so the bug can get filed at least so people know it's in progress
[01:39] <bdrung> micahg: yes
[01:43] <bdrung> micahg: i need a fake sync
[01:46] <grold> bdrung, what is fake sync? (did not find any desc in wiki)
[01:48] <micahg> bdrung: k, do you mean a use case?
[01:48] <bdrung> grold: if the md5sums of the source tarballs for one upstream version differ between debian and ubuntu. then we can't sync the package. we have to use our own source tarballs then.
[01:49] <bdrung> micahg: i am working on syncpackage and will test the fakesync part
[01:50] <grold> why upstream version may be differ?
[01:52] <micahg> grold: if it's generated vs provided by upstream
[01:52] <micahg> upstream as in upstream from Debian
[01:53] <bdrung> grold: md5sums of the tarballs. this can happen when you repack the source tarball
[01:53] <bdrung> micahg: upstream as in source tarball :)
[01:53] <micahg> bdrung: yes
[01:54] <micahg> was more of an issue before source format 3
[01:55] <grold> why I need to repack it? why not just download the original tarball? (if it's sync?)
[01:58] <grold> this case https://bugs.launchpad.net/ubuntu/+source/ruby1.9.1/+bug/611251 (i386 package builds in debian, but failed in ubuntu) is a fake sync?
[01:59] <micahg> grold: no, just different versions of build-depends
[01:59] <bdrung> grold: no, that just a build failure
[02:07] <grold> still don't understand what is the use case for changing a source tarball...O:-)
[02:09] <micahg> grold: http://people.debian.org/~daniel/documents/packaging.html#source-tarball
[02:09] <RAOF> grold: There are a number of times when it's necessary.  Most commonly: when part of the tarball isn't {redistributable,free-software}.
[02:11] <bdrung> grold: in some cases they are repacked by accident leading to a tarball with the same content but a different md5sum
[02:13] <grold> RAOF, but debian more strict in issues of free-software, if tarball suitable in debian - it shall be serve for ubuntu, no?
[02:13] <RAOF> grold: Yes, but not if we repack it independently (ie: we package it first, and then Debian packages it again)
[02:19] <grold> bdrung, micahg, RAOF - thanks to all, now I have some kind of clarity :) will do more investigation...
[02:27] <ScottL> is there a good place to see the packages that FTBFS?  something like person.ubuntu.com/ftbfs ?
[02:28] <micahg> ScottL: see /topic :)
[02:28] <micahg> ScottL: and if you're referring to the ones you uploaded, see launchpad.net/~you/+related-software
[02:36] <ScottL> micahg, neither are the one that persia showed me, this one was on a ubuntu server i believe :(  but thanks!
[02:37] <ScottL> i get an automated email from colin watson and i wanted to check up on why they aren't building
[02:54] <micahg> ScottL: idk
[06:04] <ripps> Hmm... the new compiz in Maverick is looking for libdbus-qt-1-dev, but it doesn't exist in the repos. A libdbusmenu-qt-dev does, though. Is it a missing package, or simply a misnamped dependency?
[06:06] <RAOF> libdbusmenu-qt-dev is quite a different beast.
[06:06] <ripps> RAOF: so it's a missing package then
[06:10] <RAOF> ripps: Looks like it's after libqt4-dev; it seems that the qt4 development packages aren't split out.
[06:23] <micahg> can we add a binary to a release if a newer version from the next release needs to be SRUd or should I release everything in the same package?
[07:45] <dholbach> good morning
[07:52] <bilalakhtar> dholbach: good morning
[07:53] <dholbach> hi bilalakhtar
[07:53] <bilalakhtar> hi
[09:35] <huats> morning
[09:58] <bdrung> dholbach: why did you assing me to bug #599725?
[09:58] <dholbach> bdrung: because you fixed the bug
[09:58] <dholbach> it was … like … giving you credit for your fix
[09:59] <bdrung> dholbach: i use it for marking thing that i work on
[09:59] <dholbach> well it's closed now so it won't turn up, no? :)
[09:59] <dholbach> unassign yourself if you want
[10:00] <dholbach> I just thought it was fair to credit you for your fix
[10:00] <dholbach> thanks again for that
[10:03] <bdrung> dholbach: i am subscribed to the bug and i am in the bzr log
[10:04] <dholbach> bdrung: as I said: if you don't want this, feel free to change it back
[10:05] <dholbach> it's standard practice in other projects I'm part of and I don't think I had this discussion ever before :)
[10:07] <dholbach> for example do I like it in overviews like https://launchpad.net/loco-directory/+milestone/0.2.14 https://launchpad.net/loco-directory/+milestone/0.2.13 etc
[10:08] <bdrung> ok
[10:09] <bdrung> dholbach: how long does one generation run takes on your machine?
[10:12] <chilicuil> hi, sry to bother u, but #ubuntu-bugs looks empty (I must be in a wrong UTC), anyway, I'm trying to run $requestsync and I'm getting the following output: http://pastebin.com/6V49HqFC I've tried with both version, the one who's in the repositories and the one who can be downloaded with bzr
[10:14] <tumbleweed> chilicuil: That error means it can't find python-debian, it is installed, right?
[10:15] <chilicuil> yes it's installed tumbleweed
[10:15] <chilicuil> actually it was marked as being installed manually
[10:17] <chilicuil> $ dpkg -l |grep python-deb --> "ii  python-debian                                  0.1.14ubuntu2"
[10:24] <bdrung> chilicuil: for the bzr version, you have to use a newer python-debian version
[10:24] <chilicuil> tumbleweed, bdrung : I've just purge it and reinstall it, and now it works O.o!
[10:26] <chilicuil> another non related question, after featurefreeze I can still play with the packages that ftbfs, right?
[10:30] <bdrung> chilicuil: yes
[10:30] <chilicuil> ok, great, thx for your time
[10:37] <dholbach> bdrung: 11m on the DC machine, and ages locally, somebody in the office is doing a HUGE upload
[10:38] <bdrung> dholbach: isn't there a way to speed it up a little bit?
[10:38] <dholbach> bdrung: I'm sure there, but I don't have time for it right now
[10:39] <dholbach> bdrung: I'm in a bunch of other important projects right now and try to focus on them
[10:39] <dholbach> bdrung: one obvious fix would be: get stuff OFF the list quicker
[10:40] <bdrung> dholbach: and how can we do that without regeneration?
[10:40] <dholbach> ?
[10:40] <bdrung> dholbach: or do you talk about actual sponsoring?
[10:41] <dholbach> I meant: do more sponsoring → list is short → takes less time to rerun the script
[10:41] <dholbach> yes
[10:41] <bdrung> dholbach: i first thought: getting sponsored bugs quicker off the list to avoid clashes
[10:41] <bdrung> :)
[10:42] <dholbach> http://blog.launchpad.net/api/three-tips-for-faster-launchpadlib-api-clients might help too
[10:42] <dholbach> I don't know
[10:42] <dholbach> I just can't put much effort into it now
[10:43] <bdrung> dholbach: i was thinking about  splitting the data collection and the page generation into two different parts. what do you think about it?
[10:44] <dholbach> it won't speed it up but might make the code prettier, yes
[10:46] <bdrung> dholbach: it will make debugging the code output better
[10:49] <dholbach> bdrung: yeah
[11:03] <coolbhavi> hi all is there a separate ubuntu-sru channel on irc?
[11:06] <Laney> no
[11:07] <coolbhavi> because this SRU https://bugs.edge.launchpad.net/ubuntu/lucid/+source/mobile-broadband-provider-info/+bug/607788 fixes a lot of bugs like this https://bugs.edge.launchpad.net/mobile-broadband-provider-info/+bug/497319 so I asked
[11:12] <coolbhavi> Laney, so mailing the devs in the team is the only way for a quick upload
[11:13] <kaushal> hi
[11:13] <kaushal> is there a way to get php5.3 on Ubuntu Hardy 8.04 ?
[11:14] <coolbhavi> kaushal, yes you need a backport or so I think
[11:14] <coolbhavi> maybe
[11:14] <kaushal> coolbhavi: please point me to the URL ?
[11:16] <bdrung> kaushal: https://help.ubuntu.com/community/UbuntuBackports
[11:16] <coolbhavi> kaushal, https://help.ubuntu.com/community/UbuntuBackports
[11:16] <coolbhavi> bdrung, hey typed the link at the same time :)
[11:17] <bdrung> coolbhavi: yes :)
[11:17] <bdrung> coolbhavi: s/typed/pasted/
[11:18] <coolbhavi> bdrung, I sent you a mail yesterday :)
[11:18] <Laney> coolbhavi: The SRU team members don't do the sponsoring themselves
[11:18] <bdrung> coolbhavi: yes, it's on my todo list
[11:19] <coolbhavi> bdrung, thanks
[11:19] <bdrung> coolbhavi: yesterday i worked on "foo"
[11:19] <coolbhavi> oh!
[11:20] <coolbhavi> Laney,  so contacting a dev might help?
[11:20] <kaushal> http://packages.ubuntu.com/hardy-backports/allpackages
[11:20] <bdrung> coolbhavi: subscribe ubuntu-sponsors and get me finishing "foo"
[11:20] <kaushal> i dont see php5.3 there
[11:21]  * coolbhavi checks
[11:32] <coolbhavi> bdrung, which was that foo package?
[11:33] <bdrung> coolbhavi: "foo" is a script that will end up in u-d-t and currently looks like this: http://paste.debian.net/81799/
[11:35] <coolbhavi> bdrung, great /me fires up python-interpreter
[11:36] <kaushal> coolbhavi: please suggest
[11:37] <coolbhavi> kaushal, please follow backport workflow there
[11:44] <bdrung> coolbhavi: can you fix the typo in the url: https://wiki.ubuntu.com/Bhavani_Shankar/MOTUrApplication
[11:45] <coolbhavi> bdrung, yeah
[11:45] <bdrung> coolbhavi: and can you use lists in the "Examples of my work / Things I'm proud of" section
[11:46] <coolbhavi> bdrung, you mean segregation?
[11:48] <coolbhavi> of the bugs or links to the devel-changes list?
[11:48] <bdrung> coolbhavi: segretation? i was thinking about one list entry per bug
[11:49] <bdrung> coolbhavi: do you want to join ubuntu-sponsors once you are MOTU?
[11:49] <coolbhavi> bdrung, okay... I meant New upstream under one heading merge on another ftbfs on another and so on
[11:49] <coolbhavi> bdrung, yes
[11:50] <kaushal> coolbhavi: I have followed it already
[11:51] <coolbhavi> kaushal, once those processes are followed please report a bug adhering to those processes
[11:52] <kaushal> coolbhavi: so hardy wont have php5.3 in it ?
[11:53] <bdrung> coolbhavi: the bug lists should look like: http://paste.debian.net/81801/
[11:53] <kaushal> coolbhavi: is there a existing bug for it ?
[11:53] <coolbhavi> bdrung, got it will reformat once I get home
[11:54] <coolbhavi> kaushal, please search hardy-backports :)
[11:54] <coolbhavi> bdrung, thanks for the comments
[11:57] <kaushal> http://packages.ubuntu.com/search?keywords=php5&searchon=names&suite=hardy-backports&section=all
[11:57] <kaushal> i dont have it there
[11:58] <coolbhavi> kaushal, then you need to request a backport
[11:58] <coolbhavi> I think
[11:58] <kaushal> how can i request it ?
[11:58] <porthose> coolbhavi, thx for the list will leave my endorsement today :)
[11:58] <coolbhavi> thanks porthose
[11:59] <coolbhavi> :)
[12:00] <bdrung> coolbhavi: renamed your application: https://wiki.ubuntu.com/Bhavani_Shankar/MOTUApplication
[12:00] <coolbhavi> thanks bdrung will reformat it tonight
[12:03] <coolbhavi> kaushal, please follow the backporting process in the ubuntu backporters wiki page
[12:21] <bdrung> coolbhavi: you have my endorsement
[12:21] <coolbhavi> thanks bdrung :)
[14:50] <LucidFox> I have a problem when creating an armel pbuilder image
[14:50] <LucidFox> the .tgz does get created, but it spams the console with lots of "qemu: Unsupported syscall: 335"
[15:04] <LucidFox> Okay, so it does build after all
[15:04] <LucidFox> despite the console spam
[18:43] <ari-tczew> TheMuso: ping
[19:58] <andreserl> Hi guys I have a quick question. is it possible to have a binary package that only recommends other packages like: http://pastebin.ubuntu.com/471212/
[19:59] <micahg> andersk: sure, they're usually referred to as meta packages IIRC
[20:01] <micahg> andersk: sorry, tab complete failure
[20:01] <micahg> andreserl: ^^
[20:01] <micahg> andreserl: see the -desktop packages for examples
[20:01] <andreserl> micahg, ok thanks :)
[21:40] <ari-tczew> question to main sponsors: if we will upload/attach a patch for merge any package before FeatureFreeze and you'll review patch after start FF, do you will require FFe process?
[21:43] <simar> What is quilt package in ubuntu and in general from where can we know that what a package is about?
[21:46] <ari-tczew> !quilt | simar
[21:46] <simar> !quilt
[21:47] <micahg> simar: apt-cache show PKGNAME is a good way to find out about packages
[21:48] <simar> micahg: Thanks a lot. You cleared a bug hurdle in my life .. huh
[22:09] <simar> micahg: I have fixed a FTBFS now where to submit the debdiff and how? Should I create a bug and then close it?
[22:10] <micahg> simar: file a bug, attach the debdiff, subscribe ubuntu-sponsors
[22:10] <micahg> simar: you should close the bug in teh debdiff
[22:10] <micahg> LP: #XXXXXX
[22:10] <micahg> simar: here's teh document on requesting sponsorship: https://wiki.ubuntu.com/SponsorshipProcess
[22:14] <simar> micahg: thanks, one more doubt. I have modified the source and created the ..ubuntu1.dsc. Now when I run dch -i again it will create ubuntu2.dsc I think. So Should I delete a new modify log that will be created and append changes to the old one ??
[22:15] <micahg> simar: to edit the current changelog (i.e. fix something before you upload) use dch -e
[22:16] <simar> micahg: thanks , I will try :)
[22:30] <bluefoxicy> eughhhh
[22:30] <bluefoxicy> my net is slow
[22:30]  * bluefoxicy has spent 20 minutes trying to get logged into launchpad so he can upload an strace for a system-crashing bug in Thunderbird ~_~
[22:32] <simar> micahg: I have done the process but one thing, the bug is still present in the list http://udd.debian.org/cgi-bin/ubuntu_ftbfs.cgi . Should'nt it be removed so that someone else should not waste time on it?
[22:33] <micahg> simar: it will once the debdiff is uploaded
[22:33] <micahg> to the archive, not launchpad
[22:34] <simar> micahg: ya but, now I have a intuition that the next bug I will try may be already fixed. How to check that its not fixed by someone.
[22:35] <simar> micahg: Whats the normal updation time in archives ?
[22:36] <micahg> simar: well, depends on who can sponsor when, anywhere from a few hours to a couple weeks or longer
[22:36] <micahg> simar: what's the bug #?
[22:37] <bluefoxicy> ugh
[22:37] <simar> bug #611867
[22:37] <bluefoxicy> I still can't get logged in.
[22:37] <simar> micahg:
[22:37] <bluefoxicy> AND I can't use thunderbird without it turning itself into a fork() bomb
[22:38] <simar> micahg: I have a intuition that the next bug I will try may be already fixed. How to check that its not fixed by someone.
[22:38] <micahg> look at the bugs for the package in Ubunut
[22:38] <micahg> Ubuntu
[22:39] <micahg> simar: a few things, one the  changelog is targetted to Lucid, I'm guessing you meant it for maverick
[22:40] <simar> micahg: ya sure for maaverick
[22:41] <simar> maverick
[22:41] <micahg> simar: the way to open a changelog for maverick is to do 'dch -i -Dmaverick' from lucid
[22:41] <micahg> simar: did you do a test build?
[22:41] <simar> micahg: k
[22:42] <simar> micahg: ya in a pbuilder for maverick
[22:42] <micahg> k
[22:43] <micahg> simar: does the package have a patch system?
[22:43] <simar> micahg:  Should I upload again. I think I should start everything again for kball to make a clean debdiff
[22:43] <simar> micahg: I'm not sure as i'm a new to packaging.
[22:44] <micahg> simar: yeah, you should attach a new debdiff, also, you can just say modify includes in teh files, no need to add the include directives in teh changelog
[22:45] <micahg> simar: also, the package has a quilt patch system, so you'll want to add the changes as a quilt patch
[22:45] <simar> micahg: k
[22:46] <simar> micahg: ya had to install quilt to make source
[22:46] <simar> micahg: But how to add changes to quilt. Is there a wiki page
[22:47] <micahg> simar: 'quilt help' is useful
[22:47] <simar> micahg: k
[22:48] <micahg> simar: https://wiki.ubuntu.com/PackagingGuide/Complete#quilt%20%28Example%20Package:%20xterm%29
[22:48] <simar> micahg: Should I add changes of quilt patch system to same bug report?
[22:48] <micahg> simar: well, we usually note the patch name and what it does
[22:49] <simar> k
[22:50] <micahg> simar: example: https://edge.launchpad.net/ubuntu/+source/vlc/1.0.5-2ubuntu2
[22:51] <simar> micahg: Thanks, I think i really need it  :)
[22:51] <simar> micahg: Now I will study it :)
[22:51] <micahg> simar: you're doing great :)
[22:52] <simar> micahg: :))
[22:52] <micahg> simar: I'll unsubscribe -sponsors for the moment, please resubscribe when ready
[22:52] <simar> micahg: k