[17:44] <fagan> Hey, I caused an issue with lp because of a weird bzr whoami that got pushed and merged
[17:44] <fagan> (I think)
[17:44] <jcsackett> fagan: what issue? is there an example you can point me to?
[17:44] <jcsackett> or just some more details?
[17:45] <fagan> jcsackett: I had a # at the end of my bzr whoami
[17:45] <fagan> now if you go to lp on a merge page it gives an oops
[17:45] <fagan> I dont know if its all of them but its definitely on the one I merged to
[17:46] <jcsackett> fagan: no worries, you're whoami change didn't cause the oops.
[17:46] <fagan> Ah ok
[17:46] <jcsackett> we're currently investigating that issue. you can follow along, if you like, on bug 759928
[17:46] <fagan> Oh I broke tarmac
[17:46] <fagan> I thought that I blew up lp too
[17:46] <fagan> :)
[17:46] <fagan> its cool
[17:48] <jcsackett> fagan: bzr whoami is used to identify a commiter. you may see a change in the "committed by <some-name>" data in the revision logs for your branch.
[17:48] <fagan> jcsackett: yeah I know but it just strangely started oopsing when I broke tarmc so I thought I should at least ask and/or say sorry :)
[17:49] <jcsackett> fagan: just a coincidence of timing. no worries. :-)
[17:49] <nigelb> fagan: omg, you blew up LP! :P
[17:49] <fagan> nigelb: wouldnt that be badass
[17:50] <nigelb> fagan: it only would if you got all the builders down
[17:50]  * nigelb touches wood 'just in case'
[17:50] <fagan> nigelb: good to know ill mark it down that I have to do that to kill lp
[17:51]  * fagan is an intern so breaking everything is a minor possability
[17:51]  * jcsackett makes note to have fagan "watched."
[17:51] <jcsackett> :-p
[17:52] <nigelb> fagan: this reminds of something :p
[17:52] <fagan> nigelb: what would that be? :)
[17:53] <nigelb> sec, finding
[17:54] <nigelb> fagan: http://quotes.burntelectrons.org/2804
[17:55] <fagan> nigelb: yeah thats the idea
[17:55] <nigelb> fagan: heh, glad to know :P
[17:56] <fagan> but at least I am exposing awesome bugs
[17:56] <nigelb> Yeah,I follow your blog posts, interesting to hear :)
[17:57] <fagan> nigelb: oh cool its good to see that people are enjoying them ill have a nice one today anyway
[17:57] <fagan> :)
[17:57] <nigelb> :)
[18:03] <fagan> tarmac is fixed now :)
[18:07] <fagan> (ill write in my post how the guys fixed it)
[18:12] <FloSoft> hi - i try to upload a new "orig" file for one of my packages to my ppa but it always gets rejected even i delete the package in the ppa
[18:15] <fagan> nigelb: http://shanefagan.com/internship-day-15
[18:15] <fagan> :D
[18:17] <nigelb> fagan: hahah
[18:17] <TheEvilPhoenix> FloSoft:  you never should upload a new orig file.
[18:18] <FloSoft> TheEvilPhoenix: shouldnt it remove it if the corresponding package is deleted in the ppa?
[18:18] <micahg> TheEvilPhoenix: FloSoft: to be more correct, you need an "upstream" version bump when uploading a new .orif file
[18:18] <micahg> *orig
[18:19] <fagan> later all
[18:21] <FloSoft> micahg: okay, i'll try that - but: shouldnt it remove the orig-source from the ppa too, if no package references it??
[18:23] <micahg> FloSoft: no, to prevent having to original files w/the same name and different contents
[18:23] <FloSoft> okay
[19:15] <ScottK> lifeless: Error ID: OOPS-1929F1046 is on the package accept page.
[19:18] <lifeless> ScottK: thanks; triggering a log sync
[19:18] <ScottK> Good luck.
[19:22] <bigjools> that page is a nightmare
[19:27] <ScottK> Same two packages worked on the second try.
[19:37] <lifeless> SQL time: 7798 ms
[19:37] <lifeless> potassium
[19:37] <lifeless> 1/2 a second looking up the same archive 70 times
[19:38] <lifeless> 0.3 looking up the distroseries arch tags the same 70 times
[19:38] <lifeless> 0.8 of a second pulling back 6 SourcePackageFilePublishing entries
[19:39] <lifeless> 1.4 seconds bring back *bug subscriptions* - wtf
[19:39] <lifeless> make that 2.5 seconds
[19:40] <lifeless> ScottK: lots of fat there, but spread all over in little bits
[19:40] <ScottK> Fin
[19:40] <lifeless> ScottK: it needs a big flattening
[19:40] <ScottK> Fun
[19:41] <lifeless> anyhow
[19:41] <lifeless> you were on a slow appserver we're replacing
[19:41] <lifeless> its litle that that was a dominating factor
[19:42] <lifeless> s/litle/likely/
[19:43]  * elmo twitches
[19:44] <marktraceur> Hi there, #launchpad, want to help a fellow upload a package?
[19:59] <saulus> HELP: I cant login any more and my pw reminder does not get towards me. I had a look in the spam section but there was nothing. I waited 12h. Whan can I do?
[20:01] <saulus> Im registered in freenode with this nick. This nick is also on my info page in launchpad. Also I should get all mails that you send me to my launchpad account (hopefully). So there are ways to veryfy me.
[20:02] <sinzui> saulus: https://help.launchpad.net/Feedback
[20:02] <sinzui> saulus: I think you want to use https://forms.canonical.com/lp-login-support/
[20:03] <saulus> thy sinzui , Ill try that
[20:03] <saulus> thanks
[20:09] <Darxus> In a source build recipe, how do I specify an official ubuntu source package as the source of the packaging information (debian directory)?
[20:13] <Darxus> I mean, what's the path?
[20:17] <Darxus> Ah, looks like I want lp:ubuntu/spamassassin ?
[20:21] <FloSoft> hi, any idea to https://answers.launchpad.net/launchpad/+question/152715
[20:32] <Darxus> I can't edit https://help.launchpad.net/Packaging/SourceBuilds/Recipes ?
[20:39] <Darxus> "Conflict adding file debian.  Moved existing file to debian.moved."
[20:39] <Darxus> "bzr: ERROR: Conflicts from merge"
[20:40] <Darxus> In a source build recipe I told it to merge the debian directory from the normal ubuntu package on top of the source from spamassassin's svn trunk.  Trunk contains an (old, useless) debian directory.  Moving the old one out of the way was the right thing.  What do I do to get it to ignore this and build?
[20:43] <Darxus> Build log was https://launchpadlibrarian.net/69302542/buildlog.txt.gz
[21:02] <sinzui> Darxus: I think you want to branch the upstream. You can delete debian/ from that one.
[21:03] <sinzui> Darxus: The alternative is to try nest instead of merge with a packaging branch with some hope that the nested branch overwrites the old debian dir
[21:12] <Darxus> sinzui: I did use nest-part.  https://code.launchpad.net/~darxus/+recipe/spamassassin-daily
[21:13] <Darxus> I don't want to branch it, because the whole rason I was trying to do this was automated daily builds.
[21:13] <Darxus> Should I open a (feature request) bug against launchpad?
[21:14] <lifeless> Darxus: please
[21:14] <lifeless> Darxus: what you can do in the interim is:
[21:14] <lifeless>  - branch it and delete debian
[21:14] <lifeless>  - have a three-rule recipe
[21:15] <Darxus> lifeless: Thanks.  Three rule recipe?
[21:15] <lifeless> that is - start with trunk, merge your branch (which deletes /debian only), merge the packaging (which adds a good /debian)
[21:17] <sinzui> Switching from bzr-builder to recipes was harder than I hoped for me. many things are easier with shell commands
[21:17] <Darxus> lifeless: Ohh, I didn't realize merging a branch could delete a directory, thanks.
[21:18] <lifeless> Darxus: definitely file a bug
[21:18] <Darxus> I am.
[21:18] <lifeless> Darxus: because it would be nice to do it more directly.
[21:18] <lifeless> Darxus: but this should get you going
[21:21] <Darxus> https://bugs.launchpad.net/launchpad/+bug/760201
[22:56] <lifeless> Darxus: see sinzui's comment on your bug
[22:56] <lifeless> Darxus: he has given you a few steps
[22:58] <Darxus> lifeless: Oh, thanks.
[23:13] <doko> https://launchpad.net/builders
[23:13] <doko> Not allowed here
[23:13] <doko> Sorry, you don't have permission to access this page.
[23:13] <doko> is this expected?
[23:14] <doko> lifeless: ^^^
[23:14] <lifeless> doko: iz bug
[23:14] <lifeless> there is an embargoed build shown on the page right now
[23:14] <lifeless> Unauthorized: (<lp.code.model.sourcepackagerecipebuild.SourcePackageRecipeBuild object at 0x1931a150>, 'title', 'launchpad.View')<br />
[23:14] <doko> ahh, ok
[23:15] <lifeless> I thought there was a bug but I can't see it - filing one
[23:16] <lifeless> bug 760303
[23:17] <mwhudson> that's a but that keeps reappearing
[23:17] <mwhudson> *bug
[23:18] <lifeless> we haven't fixed it by filtering on load :)
[23:20] <maxb> The same class of bug exists on the +code-imports list
[23:25] <sinzui> 403 bugs should be tagged as such. I think several of them could be fixed together if we knew them all
[23:28] <Darxus> So why does https://code.launchpad.net/~ubuntu-branches/ubuntu/natty/spamassassin/natty contain patches against spamassassin v3.3.0 when the spamassassin package has contained patches against v3.3.1 since lucid?
[23:30] <sinzui> Darxus: I think the package maintainers could answer that. Source package branches are copied/cloned for each release. So while the package might be updated by a human, I doubt he will update the branch unless something breaks
[23:31] <Darxus> Ah, thanks.
[23:31] <Darxus> That sucks :)
[23:44] <maxb> Darxus: That sounds like an automated package import branch.
[23:44] <maxb> Sometimes the importer has issues with some packages, leading to the branches being stale
[23:45] <maxb> And indeed in this case: http://package-import.ubuntu.com/status/spamassassin.html
[23:46] <Darxus> Ahh, thanks.
[23:47] <Darxus> I'm pretty sure that second tarball shouldn't be included.
[23:47] <Darxus> I think the whole point was to keep rules separate so people would set up a cron job to update them regularly via sa-update.
[23:59] <bryceh_> https://launchpadlibrarian.net/68484762/Lspci.txt (and other attachments) are giving out 503 errors