=== pace_t_zulu_ is now known as pace_t_zulu
[00:13] <chilicuil> Laney: ping
[00:13] <micahg> bdrung: thanks
[00:14] <bdrung> micahg: yw
[00:15] <bdrung> micahg: next time give me a main sponsor request ;)
[00:15] <micahg> oh, sorry, I didn't have any I was working on ATM
[00:15] <bdrung> micahg: i have to process main requests first, because the lack of main sponsors is bigger than the lack of universe sponsors
[00:30] <ari-tczew> didrocks: ping bug 614091
[00:30] <ubottu> Launchpad bug 614091 in powder (Ubuntu) "Sync powder 114-1 (multiverse) from Debian unstable (non-free)" [Undecided,New] https://launchpad.net/bugs/614091
[00:49] <micahg> bdrung: I'm glad you're doing that, will keep in mind :)
=== fta_ is now known as fta
[01:57] <grold> bdrung, please checkout bug 612862 once more
[01:57] <ubottu> Launchpad bug 612862 in bash-completion (Ubuntu) "Merge bash-completion 1:1.2-2 (main) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/612862
[02:20] <zooko> bdrung: how can I figure out who uploaded Tahoe-LAFS into Karmic and Lucid?
[05:12] <ScottK> zooko: https://launchpad.net/ubuntu/lucid/+source/tahoe-lafs/1.6.0-0ubuntu1
[05:13] <ScottK> zooko: https://launchpad.net/ubuntu/maverick/+source/tahoe-lafs/1.6.1-0ubuntu2
[05:13] <ScottK> That will tell you who's touched the package.
[05:13] <zooko> Thanks!
[05:21] <zooko> Aha. Paul Hummer is hanging out in #tahoe-lafs right now...
[05:22] <zooko> james_w: would you be willing to upload a new release of Tahoe-LAFS for Maverick?
[05:51]  * micahg notes that the official builders are basically empty
[05:58]  * micahg feeds the hungry builders
=== Pupuser402 is now known as mysteriousdarren
[08:06] <dholbach> good morning!
[08:10] <ajmitch> morning dholbach
[08:10] <dholbach> hey ajmitch
=== yofel_ is now known as yofel
=== fta_ is now known as fta
=== fta_ is now known as fta
=== fta_ is now known as fta
[10:39]  * Adri2000 needs a core-dev to approve lucid task in bug #569365, please - no one helped me in -devel :-( 
[10:39] <ubottu> Launchpad bug 569365 in mountall (Ubuntu) "mountall messages are showed untranslated in Plymouth" [Medium,In progress] https://launchpad.net/bugs/569365
=== lifeless_ is now known as lifeless
[11:18] <Rhonda> How can I set a bug to "forwarded" in launchpad? I have an upstream bug tracker URL, but "affects distribution" doesn't seem to be it?
[11:25] <dholbach> "affects project"?
[11:28]  * hyperair loves the new link in the affects project page that automatically fills in the upstream bug tracker with the needed information.
[11:28] <Rhonda> dholbach: Ah, the URL for the upstream bug has to be entered on a seperate page here.
[11:29] <Rhonda> dholbach: This is a bit misleading because affects distribution has it on the same page. %-/
[11:29] <Rhonda> *sigh*
[11:29] <Rhonda> "Launchpad does not recognize the bug tracker at this URL."
[11:29] <Rhonda> So I can't add the URL anyway?
[11:29] <dholbach> which one is it?
[11:30] <Rhonda> https://support.process-one.net/browse/EJAB-1258
[11:30] <vish> Rhonda: nope , for such just just add it in the comments , or better if you can add it in the bug description
[11:30] <Rhonda> Jira seems to be the bug software used there.
[11:31] <vish> such bugs* just
[11:31] <Rhonda> vish: A bit annoying for people to have to dig around different places to look wether there is an upstream bug, IMHO.  :/
[11:31] <dholbach> I don't know what's the status of jira integration with LP is
[11:31] <vish> Rhonda: true ;)
[11:31] <Rhonda> If it doesn't support the upstream bug tracker it should *still* allow to put the upstream URL in there.
[11:32] <dholbach> https://bugs.launchpad.net/bugs/bugtrackers
[11:32] <dholbach> best to ask in #launchpad
[11:32] <Rhonda> And in the case when it starts to pick it up it can scan them right ahead.
[11:32] <Rhonda> That way of forbidding to add a not yet supported bugtracker means losing information right ahead.
=== fta_ is now known as fta
=== fta_ is now known as fta
[12:09] <vish> tumbleweed: yay! daily murrine :)
=== didrocks1 is now known as didrocks
=== fta_ is now known as fta
[13:54] <didrocks> RainCT: hey, around?
[13:55] <didrocks> RainCT: just to know if you received my mail (saw that you update zg to 0.5 yesterday in debian)
[13:55] <RainCT> Hey didrocks. Yeah got it :)
[13:56] <didrocks> RainCT: ok, great ;)
[14:02] <dpm> Adri2000, good work on nailing bug 567126 down! Translators and those with non-English locales will certainly be happy
[14:02] <ubottu> Launchpad bug 567126 in mountall (Ubuntu) "Localization support does not work at boot time (dup-of: 569365)" [Undecided,Confirmed] https://launchpad.net/bugs/567126
[14:02] <ubottu> Launchpad bug 569365 in mountall (Ubuntu Lucid) "mountall messages are showed untranslated in Plymouth" [Medium,In progress] https://launchpad.net/bugs/569365
[14:33] <highvoltage> it's me and version numbers again! I'm using nanny (2.29.4-0ubuntu2) for the package nanny, but lintian complains about:
[14:34] <highvoltage> W: nanny source: debian-watch-file-in-native-package
[14:34] <highvoltage> W: nanny source: native-package-with-dash-version
[14:34] <highvoltage> what am I doing wrong again?
[14:34] <tumbleweed> highvoltage: do you have a .orig.tar.gz in the parent directory?
[14:34] <tumbleweed> highvoltage: also, do you have a debian/source/format?
[14:35] <highvoltage> I have debian/source/format, and a orig.tar.gz in the parent directory
[14:35] <tumbleweed> highvoltage: contents of source/format?
[14:36] <geser> highvoltage: have you the .orig.tar.gz named correctly?
[14:36] <highvoltage> tumbleweed: ah, I guess there's my problem. it says 3.0 (quilt) but that's clearly wrong :)
[14:36] <geser> highvoltage: why it's wrong?
[14:36] <tumbleweed> highvoltage: no, that would be right (for that version number)
[14:36] <highvoltage> I mean, it says 3.0 (native)
[14:36] <tumbleweed> aah, right :)
[14:39] <highvoltage> this package uses cdbs, so would changing it to 3.0 (quilt) be wrong?
[14:39] <tumbleweed> highvoltage: no, any idea why it was made native?
[14:40] <tumbleweed> (daily builds have to be native, that's about the only reason I can think of)
[14:41] <highvoltage> tumbleweed: nope
[14:45]  * highvoltage slaps himself over the head (been running lintian on the wrong .dsc file after fixing the source/format file)
[14:45]  * highvoltage goes to talk to squirrels
[16:03] <Laney> porthose: I see you uploaded darcs. What do you think about the ftbfs?
[16:28] <AnAnt> Hello
[16:32] <AnAnt> I have a NEW package that I want to get into maverick (it won't get into Debian since squeeze has frozen), is it better to upload to REVU first ? or shall I just directly upload it to Ubuntu ?
[16:37] <Laney> you can still upload to experimental
[16:39] <ScottK> AnAnt: You can still get it in Unstable, no problem.
[16:39] <ScottK> Laney: Uploads to Unstable are still fine, they just won't migrate to Testing until after Squeeze is released.
[16:39] <AnAnt> ScottK: that's something I need to understand, remember Neils Wilson ? I hope I got the name right
[16:39] <Laney> I know, but I wouldn't do it for fear of disturbing something
[16:40] <Laney> I guess that a new package would be alright though
[16:40] <ScottK> Laney: New packages (as opposed to updates to an existing package) are perfectly fine.  For existing packages it's nice to keep Unstable available for RC bug fixes.
[16:40] <AnAnt> ScottK: I recall that last year or so, he posted that people should not upload to unstable during freeze, and experimental should be used
[16:41] <ScottK> AnAnt: The name vaguely rings a bell, but I don't recall specifics.
[16:41] <ScottK> AnAnt: That's only relevant for packages that are in Testing.
[16:41] <maco> AnAnt: thats what lfaraone says persia told him too
[16:41] <AnAnt> Neil Williams is the name
[16:41] <ScottK> Right.
[16:42] <ScottK> For new packages there's no reason to avoid Unstable.
[16:43] <AnAnt> ScottK: ok, my usual sponsor in in DebConf, would you review/sponsor it ?
[16:43] <AnAnt> it's a python app
[16:43] <ScottK> AnAnt: Possibly next week, but today and this weekend are pretty busy for me.
[16:50] <zooko> Hm, Maverick feature freeze is Aug 12th and the release of Tahoe-LAFS v1.8.0 is Aug 15th.
[16:51] <maco> time to file a ffe?
[16:51] <zooko> http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/NEWS
[16:52] <zooko> It would be good to have the New-Downloader in Maverick.
[16:55] <zooko> Well, first of all, could someone please help me upload Tahoe-LAFS v1.7.1 into Maverick?
[16:55] <zooko> That could be done right away.
[16:58] <zooko> iulian: a while back you offered to help get Tahoe-LAFS upgraded in Maverick. Are you around?
=== vincs is now known as vinc-mai
[17:02] <vinc-mai> Hi.
[17:11] <vinc-mai> I have uploaded a package on revu. After a  comment on this channel I have integrate it in debian sid. What should I do with the revu package ?
[17:11] <vinc-mai> http://revu.ubuntuwire.com/p/libglobalhotkeys-ruby1.8
[17:12] <vinc-mai> I have open a bug. Should I close it  and ask for a sync ?
[17:12] <vinc-mai> https://bugs.launchpad.net/ubuntu/+bug/531523
[17:12] <ubottu> Launchpad bug 531523 in Ubuntu "[needs-packaging] rghk" [Wishlist,In progress]
[17:13] <Laney> vinc-mai: You can retitle it into a sync request. I'll archive your revu upload now. Thanks for doing it properly!
[17:31] <vinc-mai> Laney: Thank for the archiving process. I have retitle and retag the bug https://bugs.launchpad.net/ubuntu/+bug/531523
[17:31] <ubottu> Launchpad bug 531523 in Ubuntu "[sync] rghk" [Wishlist,New]
[17:32] <huats> Does anyone if aware of a change un doxygen in maverick that leds to a build failure in maverick while it builds fine in lucid ?
[17:36] <geser> have you an error log?
[17:45] <huats> geser, sure
[17:47] <huats> geser, http://pastebin.ubuntu.com/474135/
[17:47] <huats> It is just the part that fails (I have run it again in a shell inside my pbuilder)
[17:48] <geser> oh nice, a segfault
[17:49] <geser> hmm, did doxygen segfault or the program generating input for doxygen?
[17:50] <geser> looks like the input is generated with echo so doxygen segfaulted
[17:58] <huats> geser, that is my opinion too
[17:59] <huats> and it builds fine on lucid
[18:06] <geser> the same package?
[18:06] <geser> looking at the recent archive rebuild, libgdamm4.0 isn't listed there a FTBFS
[18:07] <huats> yes at the same package
[18:07] <huats> it is a new version that is not in the archive yet
[18:10] <geser> then you have to debug doxygen :(
[18:11] <huats> geser, hum
[18:11] <huats> sounds complicated :)
[18:12] <geser> or figure out what changed in the source as the current source seems to build with the doxygen in maverick (as is didn't FTBFS in the archive rebuild)
[18:16] <huats> geser, the doc was not done using doxygen in the current maverick version
[18:16] <huats> but it should in the version
[18:17] <huats> and this new version builds fine on lucid (using doxygen) and fails on maverick (using doxygen too)
[18:18] <geser> ah, ok
[18:21] <iulian> zooko: Hey.  I apologies for the delayed response.  I'm currently pretty busy with something else now.  I do not know when I'm available to take a look at tahoe-lafs.  Could you please ping me next week in case you don't find someone else who can upgrade it?
[18:22] <iulian> zooko: E-mail would be a better way to contact me and you'd likely get a faster response.
[20:32] <AnAnt> Hello, is the freeze on Thursday  for main only ? or also for universe/multiverse ?
[20:34] <micahg> AnAnt: feature freeze is for everything, I suggest reading the wiki
[20:34] <micahg> AnAnt: https://wiki.ubuntu.com/FeatureFreeze
[20:34] <AnAnt> micahg: I read it , but I forget the details every release
[20:35] <stalcup> everything except bugs
[20:38] <simar> micahg: hi
[20:38] <simar> micahg: do you remember me?
[20:39] <simar> micahg: you helped to correctly patch my fix of FTBFS some days back
=== emma is now known as em
[20:55] <zooko> iulian: okay, thanks!
=== em is now known as emma