[04:12] <ripps> Should I remove the intrepid builds from my gmpc/mpd ppas?
[04:15] <persia> Up to you.  It's supported for another 12-15 hours :)
[04:15] <persia> But I suspect that there will be some mass-disablement at some point (much like there are no longer gutsy PPAs).
[04:31] <micahg> persia: ripps: I think that's just the builders, not the PPA archvie
[04:32] <persia> micahg: Then why aren't there gutsy PPAs anymore?
[04:33] <micahg> persia: you can't build, but if it's built, I think it satys
[04:33]  * persia definitely remembers them existing in the past
[04:34] <persia> Ah, interesting.  And one has to hack the URL to see them (e.g. https://launchpad.net/~ubuntu-mobile/+a)rchive/ppa?field.series_filter=gutsy
[04:34] <persia> Anyway, probably does no harm to just leave them then.
[04:35] <micahg> as long as there aren't any security issues IMHO
[04:35] <wgrant> Right. obsolete-distroseries.py only does primary/partner.
[08:37] <KIAaze> hi
[08:37] <KIAaze> will all the official builders from the build farm be reallocated to the PPAs later?
[08:37] <KIAaze> https://launchpad.net/builders
[08:38] <wgrant> KIAaze: The PPA builders are currently busy serving Ubuntu releases.
[08:38] <KIAaze> ah ok
[08:38] <KIAaze> and what are thoe preivate builds?
[08:38] <KIAaze> "private source"
[08:38] <wgrant> Probably security updates.
[08:39] <KIAaze> ok
[08:39] <KIAaze> everything will be back to normal on 2010-05-01?
[08:39] <wgrant> Probably not.
[08:39] <wgrant> But what do you mean by "all the"?
[08:39] <KIAaze> :/
[08:39] <wgrant> There are three official i386 builders, and only two amd64 ones.
[08:39] <wgrant> Not many.
[08:40] <KIAaze> well, there are a lot of "private source" builds listed there
[08:40] <KIAaze> and the rest is marked as idle
[08:40] <wgrant> Note that most of those builders are for obscure non-PPA architectures.
[08:41] <KIAaze> true
[08:41] <KIAaze> can they switch architecture?
[08:42] <wgrant> Not without incredibly, incredibly slow emulation.
[08:42] <KIAaze> everything feels slowed down when a new ubuntu release comes out. ^^
[08:44] <KIAaze> on wednesday, packages started to build within a few minutes, now it looks like a 2-6 days queue. I'm guessing a lot of rebuilding against the new lucid repositories.
[09:00] <Peng_> Isn't it possible to mark a merge proposal superseded?
[09:00] <Peng_> I don't see it now.
[09:01] <Peng_> A merge proposal was superseded by a different branch. For now it was marked 'Rejected', but that's not ideal.
[09:10] <spiv> The Superseded state exists, but I think is only set by submitting a new merge proposal for the same branch.
[09:11] <spiv> So in your case Rejected is probably as close as it gets :/
[09:11] <spiv> (Unless maybe the launchpad APIs let you set it?)
[11:14] <FloSoft> hi, is it possible to upload files via email?
[11:14] <FloSoft> like the upload-python script, but via mail?
[12:21] <tsimpson> FloSoft: for bugs, yes https://help.launchpad.net/Bugs/EmailInterface#Attaching%20files%20to%20bugs
[12:23] <thopiekar> hi
[12:23] <thopiekar> maxb: ping
[12:24] <FloSoft> tsimpson: and for "release"s?
[12:24] <wgrant> FloSoft: There is no email interface for them.
[12:24] <tsimpson> there may be a way with the LP API, but not via email
[12:25] <FloSoft> okay i have a python script which does not work correctly
[12:25] <FloSoft> which uploads it via lp api
[12:25] <thopiekar> I created a new ssk-key with seahorse, removed the old ssh key and added the new one but I just get ssh thopiekar@bazaar.launchpad.net -> Permission denied (publickey).
[12:25] <thopiekar> why?
[12:33] <tsimpson> thopiekar: did you remove your old key from your system?
[12:33] <thopiekar> yep
[12:33] <thopiekar> and I think I found the problem..
[12:34] <thopiekar> the using bzr it is using the default .id_rsa
[12:34] <thopiekar> but my ssh key for lp is in .id_rsa_1
[12:35] <tsimpson> you can change that in your ~/.ssh/conf
[12:35] <thopiekar> found a article about that here: http://20y.hu/20081012/how-to-use-different-ssh-keys-for-different-services-smoothly.html
[12:35] <thopiekar> yep
[12:35] <tsimpson> * ~/.ssh/config
[12:35] <thopiekar> you should add that to the launchpad / bzr wiki
[12:35] <tsimpson> it is
[12:35] <thopiekar> :O
[12:35] <tsimpson> https://help.launchpad.net/Code/UploadingABranch#Pushing%20your%20Bazaar%20branch%20to%20Launchpad
[12:35] <tsimpson> :)
[12:51] <tsimpson> I've been meaning to ask something, are "bug nicknames" used any more?
[12:51] <tsimpson> where you could assign a bug a "memorable name"
[12:58] <ubuntujenkins> I have been pointed in this direction to ask, I have done 'dget http://ftp.debian.org/debian/pool/main/x/xindy/xindy_2.4~pre1-3.dsc' which gives me a *.orig.tar.gz *.diff.gz and a *.dsc. This is all from debian but is not in ubuntu due to a build fail. I would like to put it all in a ppa, how ever i don't know how to make a *.changes file for it. (source is here : http://packages.debian.org/source/stable/xindy )
[12:59] <ubuntujenkins> does any one know how to make the *.changes file?
[13:00] <tsimpson> "debuild -S" from the extracted directory should do it
[13:00] <akheron> dpkg-source -x *.dsc; cd dir-name; debuild -S
[13:00] <akheron> altough this recreates the *.dsc file too
[13:00] <ubuntujenkins> thanks tsimpson and akheron I will give it ago
[13:01] <tsimpson> or dpkg-genchanges
[13:02] <tsimpson> but then you'd need to "debsign" the changes files to upload
[13:05] <ubuntujenkins> wow tsimpson and akheron, thank you two days of pain solved. (on another problem as well)
[13:15] <ubuntujenkins> It worked with xindy but with texlive-base i get this error http://paste.ubuntu.com/425217/ any suggestions?
[13:16] <tsimpson> install quilt
[13:19] <ubuntujenkins> doh! thats obvious thanks. the xindy package got rejected http://paste.ubuntu.com/425219/ any thoughts?
[13:20] <tsimpson> change "unstable" to "lucid" in the debian/changelog
[13:20] <tsimpson> or just bump the version with dch -i
[13:22] <ubuntujenkins> ok thanks I will give it a go
[13:41] <ubuntujenkins> they have been excepted now thanks tsimpson.
[14:02] <kromagg> hi uh
[14:02] <kromagg> do I report launchpad bugs on launchpad?
[14:02] <intellectronica> kromagg: yes
[14:03] <kromagg> I actually came here to ask if there was a problem with launchpad but it just came through so
[14:03] <kromagg> bug report it is then
[14:04] <deryck> kromagg, you can report here:  https://bugs.launchpad.net/malone
[14:04] <deryck> kromagg, if you file against launchpad itself it gets moved to malone eventually, but it's slightly quicker of you file on malone.
[14:05] <kromagg> okay thanks, I was having trouble finding the exact project to report against
[14:06] <kromagg> In case you're interested, I got an OOPS-1581D1213 on reporting a bug against xorg
[14:07] <kromagg> I'm assuming it's because of the crapload of attachments xorg adds
[14:07] <kromagg> ah the number is a uniqid
[14:09] <kromagg> it's already in there though, #357907
[14:09] <kromagg> thanks for the hint
[14:10] <lifeless> that oops hasn't propogated yet, sorry
[14:14] <kromagg> eventually managed to report the bug anyway so nps
[14:14] <kromagg> the original one, that caused the oops
[14:50] <rdb> Just wondering - how is it possible to assign multiple people to a single blueprint?
[14:52] <bac> rdb: there is a single assignee, which can be a person or team
[15:11] <xnox> am I having maverick hallucinations or we have amel ppa now?
[15:12] <jpds> xnox: Yes.
[15:12] <xnox> WOW
[15:12] <xnox> amazing thank you =)
[15:19] <rdb> armel ppa? wh00t!
[15:24] <rdb> How can it be enabled?
[15:24] <bigjools> armel will be reserved, it's not for general use
[15:24] <rdb> Oh, OK.
[15:24] <bigjools> way too flaky apparently
[15:25] <rdb> What defines the lucky elite that is priviledged to make armel builds?
[15:25] <rdb> Who do I have to sleep with to get an armel ppa?
[15:25] <bigjools> right now, just the Canonical OEM team
[15:26] <rdb> Hmm... OK. Well, still an interesting development. =)
[15:32] <xnox> rdb, I love the "who do I have to sleep with" test =)
[15:33] <rdb> =)
[15:43] <qense> Are patches accessible via the API in the bug.attachments collection, or do they have their own entry point?
[15:46] <tsimpson> qense: those include patches too, you can see if it's a patch from the type attribute
[15:46] <qense> tsimpson: OK, thanks
[15:46] <tsimpson> it will be either "Patch" or "Unspecified"
[15:46] <qense> ok, great!
[17:13] <humphreybc> hiya everyone, who should I speak to about build machines?
[22:44] <BlackZ> Could somebody delete a project registered by me on launchpad ? It was a test.
[22:45] <tsimpson> BlackZ: you need to file a request on https://answers.launchpad.net/launchpad
[22:45] <BlackZ> tsimpson: OK, thanks
[22:46] <tsimpson> btw, if you want to test things out you should use https://staging.launchpad.net/
[22:46] <tsimpson> it's database gets reset daily
[22:49] <wgrant> Well, not quite daily these days.
[22:50] <tsimpson> well, it non-permanent anyhow
[22:56] <brax> http://paste.ubuntu.com/425505/
[22:57] <brax> apt won't install anything. :(
[22:58] <BlackZ> brax: This channel is for launchpad support & questions only. Please ask in #ubuntu .
[23:00] <brax> I asked in ubuntu and they told me to ask g=here... :C
[23:01] <azop> brax: either another package manager is running, or you have a more serious problem that might be fixed by simply restarting the computer
[23:01] <azop> but, it's a #ubuntu question for sure
[23:04] <tsimpson> when they said check LaunchPad, they meant http://bugs.launchpad.net/ubuntu
[23:05] <tsimpson> oh, he left anyway
[23:16] <lbieber> From https://code.launchpad.net/~drizzle-developers/drizzle/development I click on "All revisions" but keep getting "Sorry, there was a problem connecting to the Launchpad server"
[23:45] <_habnabit> So it looks like the code browser is down.
[23:45] <_habnabit> It said wait a minute or two, but it's been about half an hour for me.
[23:46] <wgrant> LOSAs: ^^