[09:48] <popey> I am getting a timeout when visiting a group in lp - (Error ID: OOPS-843cff6dfa2bfa8aec99953a877ff7e9)
[10:40] <bigjools> popey: rvba is working on that as we speak, it's a known bug
[10:40] <popey> thanks
[10:46] <bigjools> popey: I can see the page, so ping me if you need anything
[10:46] <popey> I need adding to the team
[10:47] <popey> so i have access to push to a ppa there
[12:54] <tumbleweed> why isn't there a link from binary_package_publishing_history back to the source that built it? LP knows that, right?
[13:13] <bigjools> tumbleweed: there is, but you need to do it via the build
[13:16] <tumbleweed> bigjools: and how do I get to the build from the binary?
[13:17] <tumbleweed> I simply want to find what source builds a binary in a particular release
[13:18] <geser> like it's possible with rmadison but with LP API?
[13:19] <tumbleweed> geser: rmadison doesn't tell you that either
[13:19] <tumbleweed> but DDE does (and apt)
[13:22] <geser> ah, right, you can limit the output of rmadison to source package names once you know it (e.g. from apt)
[13:24]  * tumbleweed commits a version of pull-lp-source that'll use DDE (until bug 597041 is fixed)
[13:25] <geser> it was "apt-cache madison" which also lists the source package(s) (if one has a deb-src line)
[13:26] <tumbleweed> geser: aah
[14:27] <dobey> i seem to be having some trouble building a recipe that has some patches. it seems quilt wants to apply the final patch, but then just simply exits without the patch being applied, and so fails later when patches are unapplied during debuild -S
[14:28] <dobey> anyone know why that would be? building a source package locally works fine with debuild -S -sa, and bzr dailydeb recipe doesn't seem to work locally for another reason (it apparently wants the source tree to be a bzr builddeb compatible one with all the upstream-foo tags)
[14:44] <kirkland> howdy all!  question about email settings in launchpad....
[14:45] <kirkland> I see how I can select which email address of mine registered with Launchpad would receive mail from a given mailing list
[14:45] <kirkland> but can I do that on a project-by-project, or team-by-team basis?
[14:45] <kirkland> for instance, let's say I want to receive any mail about Ubuntu package/distribution bugs at kirkland@ubuntu
[14:46] <kirkland> but I want to receive any mail about my upstream projects @gmail?
[14:46] <kirkland> is this possible?
[14:53] <Rewt`> hey all, am having the "failed to fetch" 404 errors. I don't see any ppa.launchpad.net urls in sources.list . Any suggestions?
[14:54] <tumbleweed> dobey: are the patch's line-numbers current? I seem to recall dpkg-source being picky about that
[14:56] <dobey> tumbleweed: yes :-/
[14:57] <tumbleweed> dobey: that's all I can think of, then
[14:59] <dobey> https://launchpadlibrarian.net/86377740/buildlog.txt.gz is one of the build logs
[15:04] <tumbleweed> dobey: patch 4 is commented out in your daily packaging branch
[15:05] <tumbleweed> I suspect nesting on a UDD branch with patches already applied isn't going to work that well
[15:05] <dobey> tumbleweed: it is now; it wasn't when that recipe ran
[15:05] <dobey> i'm not nesting on a UDD branch with patches already applied
[15:05] <dobey> i'm nesting on the upstream git import
[15:06] <tumbleweed> oh, right it's no tUDD
[15:06] <dobey> and even if i comment out all the patches except for one, which is a one line change, it's still failing with the same error on that one patch :(
[15:18] <tumbleweed> dobey: you can reproduce it locally by passing --allow-fallback-to-native
[15:18] <dobey> yes
[15:19] <dobey> but that doesn't really tell me anything
[15:19] <dobey> bzr-builder removing the tmp directory after it fails, is very unhelpful :(
[15:20] <tumbleweed> if you specify the builddir, it leaves it behind
[15:28] <dobey> uhm
[15:28] <dobey> tumbleweed: it seems debian/patches got removed for some reason
[15:29] <tumbleweed> yeah, I see that too
[15:29] <dobey> wtf?
[15:29]  * tumbleweed wonders if falling back to native is responsible for that
[15:30] <tumbleweed> yes, it is
[15:30] <dobey> :(
[15:30] <tumbleweed> just put 3.0 (native) in your debian/source/format
[15:35] <dobey> seems to fix it; thanks
[15:52] <Rewt`> hey all, am having the "failed to fetch" 404 errors. I don't see any ppa.launchpad.net urls in sources.list . Any suggestions?
[15:54] <dobey> Rewt`: probably not a launchpad issue then? you'll have to be more specific on what is failing exactly
[16:23] <Rewt`> Err http://ppa.launchpad.net oneiric/main Sources                                      404  Not Found
[16:24] <bigjools> Rewt`: look in /etc/apt/sources.list.d/
[16:24] <Rewt`> hmm. googling that shows promise.
[16:26] <Rewt`> k, now down to Err http://ppa.launchpad.net oneiric/main amd64 Packages                               404  Not Found
[16:27] <bigjools> did you look where I asked?
[16:27] <Rewt`> yes
[16:28] <Rewt`> took out the uneeded stuff
[16:29] <bigjools> one of the lines is trying to access a nonexistent PPA - you need to remove/comment anything with ppa.launchpad.net in it and add them back in one by one to see which is failing
[16:29] <bigjools> alternatively look in the archives using a web browser
[16:29] <Rewt`> yep, took care fo it
[16:29] <Rewt`> just didn't think of sources.list.d for some reason this morning
[16:32] <dobey> software-properties-gtk is a nice place to look for that :)
[18:10] <komputes> SPAM found here - https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/575186/comments/24
[18:21] <tgm4883> Is there a way that I can download something that is in a bzr branch on LP via a python program? What I mean is, if I try through the browser, I get a link with what looks to be randomly generated and I'm unsure if that link will persist over time
[18:21] <tgm4883> I get a link like  http://bazaar.launchpad.net/~mythbuntu/mythbuntu/mythbuntu-repos/download/head:/mythbunturepos.db-20110701013326-zkyc2b8dxf072vof-2/mythbuntu-repos.db
[18:24] <dobey> bzr is a python program
[18:25] <dobey> that is a link to a specific file at a specific revision in the code browser; so it will be there, unless somoene deletes the revision, or the branch
[18:28] <tgm4883> dobey, well I don't want it to be a specific revision
[18:28] <tgm4883> it does reference head:, so perhaps it is always the latest version?
[18:29] <tgm4883> what worries me is this mythbunturepos.db-20110701013326-zkyc2b8dxf072vof-2
[18:29] <tgm4883> which looks to me randomly generated
[18:29] <dobey> no, that is the revision id
[18:30] <tgm4883> :(
[18:30] <dobey> why don't you just do bzr branch lp:~mythbuntu/mythbuntu/mythbuntu-repos ?
[18:30] <tgm4883> dobey, because then my program needs to depend on bzr
[18:30] <tgm4883> let me clarify
[18:31] <tgm4883> this would be downloaded when users click a "refresh" button in order to find the latest repos we have for their particular version
[18:32] <tgm4883> it would be much easier for me to have them pull it from the bzr branch rather than having to manually stick that file on our website every time we update it
[18:37] <dobey> hmm; i don't have an answer for you that doesn't involve putting it on the mythbuntu web site instead
[18:37] <tgm4883> dobey, yea thats how it's done right now :/
[20:47] <shnatsel> hello everyone
[20:47] <shnatsel> description of https://launchpad.net/~papercuts-ninja says that only bugs reaching "triaged" status reach the mailing list of the team
[20:48] <shnatsel> I'm setting up a similar team at https://launchpad.net/~elementary-driveby
[20:48] <shnatsel> I wonder if I can do a similar thing there
[20:48] <shnatsel> I'd prefer to post only assignment/unassignment messages to it, though
[20:48] <shnatsel> I mean, when this team is assigned or un-assigned from a particular bug
[20:57] <flacoste> shnatsel: have you look at custom subscription?
[20:58] <flacoste> shnatsel: http://blog.launchpad.net/cool-new-stuff/better-bug-subscriptions
[20:58] <flacoste> you can subscribe to bugs on your project matching certain Status/Importance
[20:58] <flacoste> not possible to select only when an assignment occur though
[21:00] <shnatsel> flacoste: ah... I actually have LOTS of projects, ruled by one project group, and I'd like only the assignment messages to make it into the mailing list of this team... not even for a project, but when bugs are assigned to this team.
[21:00] <shnatsel> flacoste: but it's not critical, and I think I have a very narrow use case.
[21:00] <shnatsel> flacoste: thanks for your help!
[21:01] <flacoste> shnatsel: well, you will be emailed whenever you are assigned to a bug
[21:01] <flacoste> but you'll get all emails from that point on
[21:01] <flacoste> which is probably not what you want
[21:01] <shnatsel> even when the team is un-assigned from the bug?
[21:01] <flacoste> no, at that point you will get one email saying you were unassigned
[21:01] <flacoste> and nothing beyond that
[21:04] <shnatsel> ah, great
[21:04] <shnatsel> that's almost what I need
[21:04] <shnatsel> comments are probably OK in my case
[21:04] <shnatsel> thanks again!