[05:22] <achiang> how do i make a launchpad bug point to an upstream bugzilla? i thought there was a way to do that, yes?
[05:24] <micahg> achiang: also affects project
[05:24] <achiang> micahg: hm, so i put the link to the upstream bz in that field?
[05:25] <lifeless> yes
[05:25] <achiang> lifeless: i get an error: "there is no project in launchpad named http://bugzilla....."
[05:26] <micahg> achiang: you need to choose the project first
[05:27] <achiang> hm, reading this: http://blog.launchpad.net/cool-new-stuff/links-to-external-bug-trackers-right-where-you-need-them
[05:28] <achiang> makes me think that i need to link to the upstream bugzilla instance, not the actual upstream bugzilla entry
[05:29] <achiang> perhaps the upstream project has not been registered in launchpad
[05:30] <achiang> searching for "fossology" returns nothing
[05:32] <lifeless> just putting the url in should work
[05:32] <achiang> so, i don't think launchpad knows about this bug tracker: http://bugs.linux-foundation.org
[05:32] <lifeless> but there are like 3 differen upstream links
[05:33] <achiang> "There is no project in Launchpad named "http://bugs.linux-foundation.org". Please search for it as it may be registered with a different name."
[05:34] <lifeless> yes, wrong field
[05:34] <lifeless> achiang: in fact
[05:34] <lifeless> just put the bug ref in acomment
[05:34] <lifeless> thats all you need to do now
[05:34] <achiang> lifeless: well, i wanted to do it the "proper" way...
[05:34] <lifeless> it is proper
[05:37] <achiang> putting the linux-foundation bugzilla link in the field on this page results in an error too. https://launchpad.net/ubuntu/natty/+source/fossology/+edit-packaging
[05:39] <lifeless> achiang: Just Put It In A Regular Comment Please
[05:43] <achiang> lifeless: ok, i'll do that, but in the 2 minutes between my last message and your reply, i managed to register the upstream project in launchpad, which is probably not what you or i wanted. sorry about that. i'll just leave it alone for now.
[07:22] <StevenK> popey: O hai, did you end up filing the bug for the PPA reject message?
[07:23] <lifeless> bug ?664380
[07:24] <StevenK> lifeless: That would be it, thanks
[07:24] <lifeless> I googled: ppa reject site:bugs.launchpad.net
[08:23] <poolie> bug expiry hasn't kicked in yet?
[08:23] <poolie> according to derycks' blog post it was supposed to happen around the 18th
[08:32] <lifeless> we'll be doing controlled runs shortly
[08:32] <lifeless> as per his mails to the dev list
[08:39] <poolie> sure, i just thought i might see it happening
[10:00] <CcxCZ> hi, from what I've read, there's no irc notification bot for launchpad projects, so I'm writing one.
[10:02] <CcxCZ> I'm trying to debug it using staging launchpad, but I'm waiting for half hour since I pushed to a branch and it still wasn't updated
[10:02] <CcxCZ> is this normal for (staging) launchpad? :-|
[10:04] <spiv> CcxCZ: waiting for an email from staging?  I don't think it sends them.
[10:04] <CcxCZ> nope, for branch to be rescanned
[10:05] <CcxCZ> https://code.staging.launchpad.net/~ccx/executable/trunk-1
[10:06] <CcxCZ> or, more exactly, for revision id to be bumped on api.staging.
[10:15] <dothebart> hm, so i've changed the directory layout in git the way launchpad excepts it and waited for launchpads bzr branch to catch up (trunk/webcit/po/webcit/webcit.pot)
[10:15] <dothebart> tried to change the settings in launchpad, and no feedback whether it found some files or not
[10:54] <CcxCZ> what is the busiest project on launchpad? I need someone commiting like crazy. :-)
[10:54] <Tak> bzr? launchpad?
[10:55] <CcxCZ> launchpad is too many projects iirc :-), tracking bzr now
[10:56] <jpds> CcxCZ: They all share the same codebase: https://code.launchpad.net/~launchpad-pqm/launchpad/devel
[11:01] <CcxCZ> does api's getBranches limit count to 50? because that's what I get for both launchpad and bzr
[13:32] <dothebart> ah. import from bzr worked out. henninge can you have another look at my import queue?
[13:32] <dothebart> https://translations.launchpad.net/citadel/7.9/+imports
[13:34] <dothebart> and, for some reasons it won't accept the export branch? https://translations.launchpad.net/citadel/7.9/+link-translations-branch
[13:34] <henninge> dothebart: how many templates do you have? 2 or 4?
[13:34] <dothebart> 2
[13:34] <dothebart> the debian ones aren't nessecary currently
[13:34] <dothebart> so, webcit, and citadel-setup
[13:34] <dothebart> i've renamed the ee as you sugested
[13:35] <henninge> dothebart: I think the "debian" directory does not belong in a branch in the first place.
[13:36] <dothebart> well, its there so I can easily develop & compile .debs after the release.
[13:36] <henninge> dothebart: I have set them to "blocked" so they don't get imported.
[13:36] <dothebart> ok.
[13:37] <dothebart> i've tried to make 'lp:~w-goesgens/citadel/trunk' the export bzr
[13:37] <dothebart> it won't let me
[13:37] <dothebart> just tells me 'There is 1 error.' without any details
[13:38] <henninge> dothebart: that is most likely bug 407260
[13:39] <dothebart> hm, don't I own that branch?
[13:40] <henninge> dothebart: ah, it is an imported branch.
[13:41] <dothebart> https://code.launchpad.net/~w-goesgens/citadel/trunk
[13:41] <dothebart> yes. I want to be able to merge back translation into the git main repo
[13:41] <dothebart> bzr is a little slow ;)
[13:42] <Tak> lies and slander!
[13:42] <henninge> dothebart: sorry, only LP-hosted bzr branches are possible here.
[13:42] <henninge> Tak: You take the words out of my mouth ... ;-)
[13:42] <dothebart> Tak: a git clone doesn't engage my fan
[13:42] <dothebart> a bzr clone does
[13:42] <dothebart> and the bzr just is trunk without branches
[13:42] <Tak> but switching bzr branches doesn't make my HD thrash for 10min ;-)
[13:43] <henninge> dothebart: anyway, you will have to create a empty bzr branch and push it to Launchpad and use that.
[13:43] <dothebart> hm, thats working for me with git in sub-seconds with more than 8k commits
[13:44] <dothebart> ok
[13:44] <dothebart> how? ;-)
[13:44] <dothebart> oh, plus i'm working on slow flash all the time.
[13:45] <dothebart> I have to admit, exporting from svn to git was hell slow...
[13:46] <dothebart> ok, bzr init done.
[13:47] <henninge> dothebart: eventually (after add and commit): bzr push lp:~w-goesgens/citadel/translations-export
[13:47] <henninge> or whatever you want to call it.
[13:54] <dothebart> ah. that did it.
[13:57] <dothebart> so if I now edit some thing it should push it there?
[13:57] <dothebart> but... everything is still in review mode...
[14:10] <Tak> what's the best way to install (a stable) launchpad locally?
[14:21] <bigjools> Tak: https://dev.launchpad.net/Running
[14:22] <Tak> yeah, I saw that, but it kind of assumes you're branching launchpad trunk to hack on it, right?
[14:22] <Tak> or have I misunderstood?
[14:24] <Tak> or can I just s/devel/stable/g in the setup script?
[14:24] <maxb> There is no documented or supported procedure for installing a stable local launchpad
[14:25] <Tak> awesome
[14:38] <henninge> dothebart: they will be approved automatically now that the templates are approved and imported.
[14:40] <dothebart> within which timeframe? hours?
[14:40] <dothebart> https://translations.launchpad.net/citadel/trunk/+imports?field.filter_status=all&field.filter_extension=pot shows the pots are still not approved?
[14:40] <dothebart> or should I log off & on again?
[14:41] <henninge> dothebart: sorry, I was on the 7.9 series. ;-)
[14:41] <dothebart> ah, so i'm wrong here?
[14:42] <dothebart> ah, thats the reason why it behaves differntly now and then...
[14:42] <henninge> I don't know. Which series do you want to do translations in? Usually trunk is good but you pointed me to 7.9 earlier.
[14:42] <henninge> dothebart: translations are shared between series, so there won't be any doubled work.
[14:43] <henninge> dothebart: ok, I approved those in trunk, too.
[14:44] <dothebart> I don't think i've added another real branch
[14:44] <dothebart> wonder why its doing 7.9 & trunk in separate...
[14:45] <dothebart> will the deleted ones disappear sometime soon?
[14:45] <henninge> dothebart: deleted queue entries are removed after three days.
[14:45] <henninge> so are imported entries
[14:46] <henninge> dothebart: both series import from the same branch
[14:47] <henninge> dothebart: it should be enough to only import into trunk because the translations will be shared with 7.9
[14:47] <henninge> but that's the reasons why you have the same files in both queues.
[14:48] <ricotz> hello, could someone please kill this build https://edge.launchpad.net/~ricotz/+archive/staging/+build/2005064
[14:49] <dothebart> henninge: I don't know how I created that 7.9 thing...
[14:50] <dothebart> ah, got mail from it. will it send mail if somebody adds translations?
[14:54] <dothebart> hm, looking at https://translations.launchpad.net/citadel/trunk/+lang/de , and https://translations.launchpad.net/citadel/trunk/+pots/webcit/de/+translate?start=0&batch=10&show=untranslated&field.alternative_language=&field.alternative_language-empty-marker=1&old_show=all
[14:55] <dothebart> it doesn't show the change which I committed to git yesterday, is that screen still referencing the deleted webcit/de.po?
[15:06] <henninge> dothebart: deleting from the queue has no effect once an entry has been imported.
[15:06] <henninge> dothebart: the "thing" is a "series". Ist there no "7.9" version of the software?
[16:09] <dothebart> henninge: its going to be the next version, so, its basicaly trunk.
[16:53] <c_korn> hello, any guess when bug 660832 will be fix released?
[16:54] <sinzui> c_korn, the milestone says 2010-11-10, you could update scripts to use edge for the next month and use the fix now
[17:01] <c_korn> sinzui: ah, ok. so the patch is already in edge. will test this now.
[17:05] <c_korn> hm, no difference: $ wget -q -O /tmp/1 https://edge.launchpad.net/people/getdeb-uploaders/+rdf ; wget -q -O /tmp/2 https://launchpad.net/people/getdeb-uploaders/+rdf ; diff -u /tmp/2 /tmp/1
[17:05] <c_korn> sinzui: ^
[17:06] <sinzui> !
[17:06] <sinzui> where did my rdf go
[17:07] <sinzui> my script fails again
[17:07] <sinzui> c_korn, my script is based on your script and gets every kind of rdf
[17:07] <sinzui> it ran and passed a few days ago
[17:07] <sinzui> bugger
[17:07] <c_korn> http://pastebin.com/VE74CbBk
[17:08] <sinzui> c_korn, staging is good. I think edge was rolledback. Edge updates are stopped because we are preparing to abandon edge
[17:08] <sinzui> c_korn, verify on staging. The data is 5 6 days old though
[17:09] <c_korn> hm, the diff looks fine
[17:10] <persia> sinzui, abandon edge?
[17:11] <sinzui> we are moving to daily updates of lpnet. bugs and even features will be released the day after they are verified to be ready
[17:11] <sinzui> We will still have  monthly releases for schema changes
[17:12] <sinzui> Features will be developed using flag to indicate who should see the new behaviour when the feature is not released. beta users (the users who see edge) will be the default users to see features, but user could join other teams to see just specific features in development
[17:15] <persia> Oh my.  Let's hope that works.
[17:15] <persia> Will users be able to flip the flag setting?  I don't use edge myself, but I know of a few folk who have switched back and forth during particularly odd times.
[17:15] <sinzui> While manging features is more complicated, releases are easier because there is less to rollout
[17:17] <sinzui> persia, they will not be to flip the setting. Since the rules can be governed by team membership, user can join teams. I think the engineers need to do more blog posts to inform users about how they can test a new feature
[17:18] <persia> Heh, well, maybe it works :)  Let's hope there are no layout bugs on the team membership page :)
[17:30] <c_korn> sinzui: staging does not give an error thanks. but it seems the rdf has also changed differently. there are no keys imported with this script: http://pastebin.com/tu8W6w6q
[17:31] <sinzui> I did not change keys.
[17:31] <sinzui> you may need to traverse deeper. Users are described using foaf only. I think
[17:33] <c_korn> hm
[17:33] <c_korn> I think the select statement does not fit any longer
[18:08] <joshuahoover> anybody else having problems viewing attachments that were recently uploaded (within the past 30 minutes)?
[18:15] <joshuahoover> appears to be quite a delay between when you upload the attachment and being able to download it successfully...was getting 404's before
[18:22] <deryck> joshuahoover, private bugs?
[18:22] <joshuahoover> deryck: yep
[18:22] <deryck> joshuahoover, yeah, there's gremilins in the librarian for private attachments.
[18:23] <joshuahoover> deryck: don't tell my kids that, they think there are gremlins in our basement ;)
[18:23] <joshuahoover> deryck: ok, thanks for letting me know :)
[18:23] <deryck> heh
[18:23] <deryck> joshuahoover, more specifically, lifeless has done a nice token-base private librarian work that will fix all this when it can be deployed.
[18:24] <joshuahoover> deryck: great!
[19:24] <jcastro> hey deryck, I have an idea for you
[19:24] <jcastro> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/665240
[19:25] <jcastro> we do bug watches, what do you think about the ability to link up git commits like we do patches?
[19:25]  * deryck is thinking about that....
[19:25]  * jcastro pencils it in for UDS agenda
[19:26] <deryck> jcastro,so we're just pointing at git commits somewhere else on the web?
[19:27] <jcastro> deryck: or auto import them or whatever
[19:27] <jcastro> deryck: something that let's maintainers know "there could be a possible easy backport/fix here"
[19:27] <jcastro> whatever gets it on that list
[19:27] <deryck> ah, ok.
[19:28] <jcastro> but if someone knows there's a git commit someplace that fixes their problem there should be a way to mark that
[19:28] <jcastro> (note that I have no clue if it fixes this dude's problem)
[19:28] <deryck> jcastro, so certainly I'm open to discuss it.  Sounds interesting as a concept.  I would value someone from launchpad code team input as well.
[19:28] <jcastro> but if someone is clued in enough to know that there could be a commit out there that fixes the problem then perhaps we should look at those
[19:29] <jcastro> deryck: yeah, I just ran into it and was like "we should talk about this!"
[19:29] <jcastro> I'm sure jfo will have a bunch of opinions
[19:29] <deryck> jcastro, yeah, I agree, it's definitely a cool idea to talk about.
[19:30] <jcastro> I look forward to possibly creating more work for gmb
[19:33] <deryck> jcastro, heh.  gmb might welcome anything after how long we've been working on subscriptions.
[19:34] <jcastro> good, let's break him a bit, assign him to importing external bug trackers.
[19:35] <deryck> I don't want to lose him from my team :-)
[20:01] <pmjdebruijn> is ppa stuck again?
[20:01] <pmjdebruijn> my build ETA's are pretty much onstant
[20:01] <pmjdebruijn> constant*
[20:03] <c_korn> pmjdebruijn: they are quite busy https://launchpad.net/builders
[20:03] <pmjdebruijn> oh
[20:03] <pmjdebruijn> then it's more of a conincidence
[20:07] <pmjdebruijn> c_korn: thanks
[20:07] <c_korn> np
[22:55] <avo> Hey guys.. so I'm writing a SUPER small app that is literally only useful to one or two other people (my friends.. it's about our school). However, I'd like them to be able to code the little project as well, and use a system to keep all this straight. There's no reason, and frankly I wouldn't want to make this visible to the public. How/can I do this? Thanks!