[05:10] <syn-ack> How long does it usually take for a package to hit the main server's repo once it's been built in Launchpad?
[05:10] <syn-ack> I'm waiting on a package respin and it's been about 35 - 40 minutes already
[05:10] <wgrant> In the primary archive?
[05:11] <syn-ack> yeah
[05:11] <ScottK> Another ~34 minutes
[05:11] <wgrant> The primary archive publisher only runs once an hour, so it could take nearly two hours for it to appear on archive.ubuntu.com if it was at just the wrong time.
[05:12] <syn-ack> ah, gotcha
[05:12] <ScottK> Generally the publisher starts at :03 and finishes at :45.
[05:12] <syn-ack> that's good to know. Thanks, guys.
[05:12] <ScottK> So if it's done by :03, it'll be available at :45.
[05:12] <syn-ack> right
[05:12] <ScottK> Except of course when it isn't.
[05:12] <syn-ack> heh
[05:13] <ScottK> There's two hours each night when the publisher doesn't run.
[05:13] <ScottK> I've forgotten what happens instead.
[05:13] <syn-ack> Which are which times?
[05:13] <wgrant> ScottK: Contents generation.
[05:13] <ScottK> Yeah.  That's it.
[05:13] <wgrant> It starts at 0400UTC, or maybe a bit earlier.
[05:13] <wgrant> So, now!
[05:13] <syn-ack> heh
[05:13] <ScottK> Which I'd also forgotten about when I mentioned how long you'd have to wait.
[05:14] <ScottK> So it's longer.
[05:14] <wgrant> 02 4 * * * /srv/launchpad.net/codelines/current/cronscripts/publishing/gen-contents/generate-contents >> /srv/launchpad.net/production-logs/lp_publish/      generate-contents.log 2>&1
[05:14] <ScottK> 1:31, AFAICT.
[11:04] <MTecknology> I just got notified that my request to import svn://svn.nginx.org/nginx/trunk was rejected... https://code.launchpad.net/~mtecknology/nginx/trunk
[11:05] <MTecknology> OH! I lied.....
[11:05] <MTecknology> Sender: launchpad-bugs-bounces@lists.canonical.com
[11:05] <MTecknology> Your message was rejected
[11:12] <wgrant> Grar, not that again.
[11:14] <MTecknology> wgrant: sorry
[11:29] <maxb> lifeless proposed removing ~launchpad's contact address, but the thread fizzled
[11:30] <maxb> given that it's now spamming users, not only dev-oriented LP people, maybe it should just be done, since no-one objected
[11:44] <MTecknology> maxb: no objection here :)
[11:50] <maxb> MTecknology: svn://svn.nginx.org looks a bit wrong as am import URL :-)
[11:51] <MTecknology> maxb: ya, I tried to correct it to svn://svn.nginx.org/nginx/trunk
[11:52] <maxb> MTecknology: ok, suggest you delete https://code.edge.launchpad.net/~mtecknology/nginx/upstream then
[11:52] <MTecknology> maxb: done
[11:58] <MTecknology> maxb: thanks :)
[11:58] <maxb> np
[11:58] <MTecknology> maxb: nginx finally has its dev branch public :)
[11:59] <MTecknology> maxb: oh... I actually did grab the whole repo.. svn://svn.nginx.org/  .. 2.9GB :P
[12:06] <MTecknology> short nap before work... ttyal
[13:46] <exarkun> is there some way to find out why a message posted to a launchpad mailing list was held for moderation?
[13:59] <DigitalFlux> Hi Guys
[13:59] <DigitalFlux> if i commented on a bug on launchpad that was marked as fixed, will the contributors/commentors on this bug be notified
[13:59] <DigitalFlux> ?
[13:59] <wgrant> DigitalFlux: Yes.
[13:59] <wgrant> exarkun: Looking.
[13:59] <DigitalFlux> wgrant: cool, thanks
[13:59] <jpds> DigitalFlux: If they're subscribed, yes.
[14:02] <wgrant> exarkun: Intriguing. There is a column on the table for the hold reason, but it doesn't seem to be used :(
[15:13] <Ursinha> anyone here willing to help with a really quick test? :)
[15:17] <Peng> Was that question the test? Did we pass?
[15:17] <Ursinha> :P
[15:18] <Ursinha> Peng, could you help me, please?
[15:18] <Ursinha> it's supereasy
[15:26] <Peng> Ursinha: The answer is probably no, but the answer is definitely no without knowing what you need.
[15:27] <Ursinha> Peng, I need to know what do you see when you go to https://translations.qastaging.launchpad.net/ubuntu/natty/+source/gwibber/
[15:28] <Ursinha> if there's anything related with Sharing
[15:28] <Peng> What do you mean, exactly? And I'm not logged in.
[15:29] <Peng> OpenID++
[15:30] <Ursinha> Peng, that's a translation page
[15:30] <Ursinha> when logged in
[15:30]  * Peng has never used the translation system, ever.
[15:34] <Ursinha> hehe
[15:59] <CarlFK> if I upload something to my PPA dist=natty, is there a risk that changes in natty will break it?  (I think yes, just want to confirm)
[15:59] <CarlFK> or do the magic elves fix it in the night
[16:06] <cnd> abentley, thumper, jelmer: got a question on daily recipes
[16:06] <abentley> cnd: shoot
[16:06] <cnd> I was wondering how I could nest-part a debian packaging directory
[16:06] <cnd> but strip out debian/patches
[16:07] <cnd> because debian/patches includes cherry-picked patches that already exist in our trunk
[16:07] <jelmer> cnd: Hi
[16:07] <jelmer> cnd: I'd recommend merging in another branch that removes that directory
[16:09] <abentley> cnd: Or you can just create your own version of the packaging branch without the patches, and forgo the merge.  (which would mean you won't get further packaging changes from upstream until you manually update the branch.)
[16:43] <cnd> jelmer, abentley: sorry, got corralled into a phone call :)
[16:44] <cnd> jelmer, is it possible to create a dummy branch that deletes the debian/patches directory, even if the directory contents change?
[16:44] <cnd> or will that cause a merge conflict?
[16:46] <cnd> hmm... looks like it creates a conflict...
[16:47] <cnd> jelmer, abentley: and the run command isn't supported by launchpad's builder right?
[16:47] <abentley> cnd: yes, it creates a conflict, no the run command is not supported.
[16:48] <abentley> cnd: I think we might want to add a delete command, but there isn't one yet.
[16:50] <abentley> cnd: a compromise would be deleting the contents of the directory, but not the directory itself.
[16:51] <abentley> cnd: specifically, we run "bzr dailydeb" with the --safe flag.
[16:52] <cnd> abentley, ahh, then I can test it locally
[16:52] <cnd> thanks
[16:52] <abentley> cnd: no problem.
[17:19] <FloSoft> hi, how can I set/create a ppa for a project?
[17:20] <bigjools> You can't have PPAs for projects (yet), they're for teams and people.
[17:21] <FloSoft> bigjools: but can I set a people's ppa as an ppa link in a project somewhere?
[17:21] <bigjools> projects know nothing about PPAs, you can just link to it in the description.
[17:22] <FloSoft> okay
[17:28] <achiang> hello, i'm seeing a strange FTBFS that i've never seen before (and the package built fine locally in a pbuilder)
[17:28] <achiang> binmode() on unopened filehandle at /usr/share/perl5/Dpkg/Substvars.pm line 145.
[17:28] <achiang> readline() on unopened filehandle at /usr/share/perl5/Dpkg/Substvars.pm line 146.
[17:28] <achiang> dh_sameversiondep: cannot continue because package libphonon4 has no Depends field to scan
[17:28] <achiang> make: *** [common-binary-predeb-arch] Error 255
[17:34] <cnd> jelmer, abentley: when I try building my recipe, it errors out cause it can't find the orig tarball
[17:34] <cnd> is there something I need to specify to tell it to run uscan or to build a pristine tarball?
[17:34] <jelmer> cnd: recipes don't support non-native packages yet
[17:34] <cnd> oh...
[17:44] <FloSoft> how can i upload packages for multiple distributions?
[17:45] <FloSoft> if i write "natty maverick" in debian/changelog, launchpad does not parse that -.-
[17:54] <bigjools> FloSoft: you need to either upload different versions, one for each series, or upload one version for one series and then use the copy packages function in the PPA
[17:59] <FloSoft> bigjools: hmm okay, copy packages never worked for me (already published ...)
[18:00] <bigjools> FloSoft: it prevents you from shooting yourself in the foot by not letting you copy illegally.
[18:00] <bigjools> FloSoft: you can't copy the same version intra-archive unless you include binaries
[18:00] <bigjools> this is a restriction of pool-based repos like the Debian repo is
[18:01] <FloSoft> bigjools: oh okay hmm
[18:01] <FloSoft> so i have to create multiple versions for every distro?
[18:02] <bigjools> only if you want it recompiled on each, otherwise upload to one and copy with binaries
[19:13] <jussi> good evening all
[19:16] <jussi> Im just following up on an old todo for kubuntu, which was: Investigate status of bugzilla<->launchpad plugin for KDE. does anyone know if there has been any progress on that?
[19:18] <jussi> If someone does know, even very much later, please either PM me or email me: jussi01 at ubuntu dot com.
[19:18] <jussi> thanks!
[20:28] <tenach> Hello, I've recently changed my mainline branch externally and would like to change the mainline branch in Launchpad as well. I seem unable to do so, however (project: whube)
[22:04] <chichak> hi everyone
[22:05] <chichak> I already got an openid account from myopenid, so I do not want to create another one for launchpad use. How can I use that one?
[22:07] <mwhudson> chichak: you can't, sadly
[22:07] <chichak> why that?
[22:07] <mwhudson> it's not been implemented yet
[22:07] <mwhudson> it's a desired feature, but never made it to the top of the list
[22:11] <chichak> I see ... I already wondered if that was a policy, since on the FAQ is advertised that you can sign on everywhere else...
[22:54] <popey> is it possible to have a team/project which has "private by default" for new bugs?
[23:04] <sinzui> popey: projects can be configured to have bugs private by default. It is a commercial feature
[23:05] <popey> :(
[23:05] <popey> ok
[23:06] <maco> setting up a project for security bugs?
[23:06] <popey> no, just a personal project
[23:07] <lifeless> popey: its a commercial feature because projects that are operating behind closed doors aren't participating in the open source community
[23:07] <sinzui> maco: that is exactly the kind of project where we need to ignore the commercial rules. We all want security bugs noted as security issues (and private) until the issue is ready to be public
[23:07] <popey> its not technically an open source project
[23:07] <popey> we have no code
[23:08] <popey> we're just using the bug tracker as a ticket system because it works and has some nice features
[23:08] <popey> (not my selection, but hey)
[23:08] <lifeless> popey: you could file them all as security bugs
[23:08] <lifeless> but it won't stop other folk filing public bugs there
[23:09] <popey> I dont mind other people filing bugs there
[23:09] <popey> I'll ignore those ;)