[03:39] <alester> I hope it's OK to run a LP project that is just a community, and isn't releasing actual software
[03:40] <beuno> it sure is
[03:41] <alester> I've been working on Drizzle and I'm really impressed, both with LP and Bazaar
[03:41] <alester> so we're gonna host the website stuff on LP rather than Google Code
[03:42] <beuno> that's perfectly fine
[03:42] <beuno> as long as it's open source, it's aaaal good
[03:43] <alester> well, it's just HTML for the website so far. :-)
[03:44] <alester> https://launchpad.net/ocus
[03:44] <alester> is us
[03:44] <alester> gotta fix up DNS
[03:45] <beuno> it's a perfect fit for LP, so feel free to use anything you'd like
[03:53] <alester> thanks
[03:53] <alester> Also, I'm going to post ISOs of Windows Vista, and kiddie porn.
[03:54] <beuno> as long as it's open source (?)
[03:54] <alester> hahaha
[03:56] <alester> So glad Canonical is doin' this.  Thanks, all.
[03:56] <alester> And lest anyone reading logs thinks I'm serious: I was kidding about the ISOs and kiddie porn. :-)
[03:56] <alester> g'night
[04:51] <saivann> Does someone know what the new functionnality "Does this bug affect you?" of launchpad exactly does?
[04:52] <beuno> saivann, it will be used to decide which bugs affect more people
[04:53] <beuno> si, I think the feature is still incomplete
[04:53] <saivann> beuno : thanks for the answer, then I think that bug 149775 might be closed in a near future :)
[04:53] <beuno> saivann, yeap, sounds like it
[05:35] <EagleScreen> I have one bug report that i want to separate in two different reports, to do it, i must remove an affected package, and also a nominaton for release, ¿How can I do it?
[05:35] <Hobbsee> where you'd normally change an affected package, make it blank
[05:35] <Hobbsee> the other: you can't, afaik
[05:36] <Hobbsee> unless you decline the nomination for release for the whole bug
[05:38] <wgrant> EagleScreen: If you want to split it, you'll have to file a new one.
[05:39] <wgrant> To get rid of a package or nomination, you would generally mark it as Invalid or Won't Fix, depending on what it is and whether LP feels like documenting things today.
[05:40] <EagleScreen> thanks you
[05:55] <EagleScreen> the problem is that now the three afected packages has nomination for Hardy, and they only should have nomination for Intrepid
[05:56] <EagleScreen> the package that was nomination for Hardy is now separate to another report
[05:56] <EagleScreen> and maked as Invalid
[05:58] <EagleScreen> so I would like to can revoke nomination for Hardy
[05:58] <wgrant> EagleScreen: Mark them as Won't Fix.
[06:00] <EagleScreen> I cannot edit Importance, but I think that wouldn't solve my problem
[06:00] <wgrant> EagleScreen: It's a status. Maybe you don't have privileges.
[06:00] <wgrant> Which bug?
[06:00] <EagleScreen> #259180
[06:01] <wgrant> Bug #259180
[06:01] <wgrant> Oh.
[06:01] <wgrant> So they're not approved yet.
[06:01]  * wgrant declines them.
[06:02] <wgrant> There's probably little point having an Intrepid task.
[06:02] <wgrant> What does RM Hobbsee think?
[06:02] <wgrant> Or RA or RE, whatever your title may be.
[06:04] <Hobbsee> oh look, another user throwing out ultimatums.
[06:04] <Hobbsee> if it should be fixed in intrepid, and should be on the release team radar, then i think it should have an intrepid task, iirc.
[06:05] <wgrant> This hasn't been publicised well.
[06:05] <wgrant> But that would make sense.
[06:05] <Hobbsee> no.  there was a really good summary of it in one of the recent meetings, though
[06:05] <Hobbsee> would be good to publicise that
[06:05] <wgrant> Indeed.
[06:05] <wgrant> I'm tempted to reject the bug, really.
[06:06] <Hobbsee> on what basis?
[06:06] <EagleScreen> I think these packages are necessary on Intrepid
[06:06] <wgrant> Hobbsee: The ultimatum.
[06:07] <Hobbsee> wgrant: you can't reject bugs because the user is being a pain in the neck.
[06:07] <wgrant> Hobbsee: Sure I can.
[06:07] <Hobbsee> wgrant: nor can you write comments such as "don't let the door hit you on your way out"
[06:08] <Hobbsee> well, okay.  you *shouldn't* do that.
[06:08] <Hobbsee> EagleScreen: can you define missing?  these packages definetly appear in my apt-cache.
[06:09] <Hobbsee> EagleScreen: all 55 of them.
[06:09] <EagleScreen> Hobbsee i am going to check it, my be they have been uploaded yet
[06:09] <Hobbsee> looks like they were last updated on sept 8.
[06:10] <EagleScreen> then i will test them and if they works i will mark the bug as fixed
[06:12] <Hobbsee> cool
[06:12] <EagleScreen> but my initial issue of nomination continues here
[06:13] <Hobbsee> it should be nominated.
[06:13] <Hobbsee> if it should be fixed in intrepid
[06:13] <Hobbsee> OTOH, based on the bug title, ti should be marked as fix released.
[06:13] <wgrant> Hobbsee: But everything *should* be fixed in Intrepid.
[06:13] <EagleScreen> i want remove Hardy nomination after having separated the bug in two
[06:14] <Hobbsee> EagleScreen: you can't.
[06:14] <EagleScreen> anybody can't?
[06:14] <Hobbsee> wgrant: that's true.  But stuff that should be on the RT's radar, and fixed in intrepid, and is going to have someone to fix it.
[06:14] <wgrant> Nobody can.
[06:14] <Hobbsee> EagleScreen: nope.
[06:14] <wgrant> Unless you want to find a LOSA, but I don't they'd do it.
[06:14] <wgrant> +think
[06:15] <EagleScreen> okay
[06:15] <Hobbsee> EagleScreen: you probably should open another bug saying that they don't work, if they don't.
[06:15] <Hobbsee> rather than mangling titles, etc.
[06:16] <EagleScreen> yes, i think
[06:16] <EagleScreen> some packages has version 4.0.98
[06:16] <EagleScreen> will works them on KDE 4.1.1?
[06:17] <Hobbsee> presumably.  try it.
[06:17] <Hobbsee> they may not have had more translations added to them in a while, though
[07:36] <cwillu> is the openid provider broken right now?
[07:38] <cwillu> livejournal gives me "No claimed id: no_identity_server: The provided URL doesn't declare its OpenID identity server." when I try to login with https://login.launchpad.net , and I have no openid thingy under my user profile.  I was able to use it with stackoverflow a week ago however
[08:28] <luks> hi, is there a way to make the Launchpad Janitor not close inactive questions as Expired?
[08:29] <luks> there is an option for bug reports, I'd like to do the same for answers
[08:32] <wgrant> luks: I don't know of an option, but there might be one deviously hidden somewhere.
[08:37] <wgrant> luks: I happen to have a copy of the names of fields in that schema floating around, and there's Product.enable_bug_expiration, but nothing similar for Answers.
[08:38] <luks> if I file a bug report, is there any chance of getting it implemented or would it be a waste of everybody's time? :)
[08:40] <persia> luks: Filing a bug report at least starts the conversation.  Be patient, as there's a bit of a queue.
[08:41] <wgrant> If you wanted some irony, you could ask a question about it on the launchpad project. They often expire a couple of times before somebody gets to them...
[08:42] <luks> heh
[09:32] <dholbach> hiya
[09:33] <dholbach> for launchpadlib.resource.HostedFile is there an easy way to get just the URL of the file? (let's say I'd like to get the mugshot of a person and display it somewhere)
[09:50] <thumper> dholbach: best person to ask is leonard when he starts
[09:52] <dholbach> thanks thumper
[09:52] <thumper> dholbach: np
[09:54] <dholbach> thekorn: do you know if there's anything in the launchpadlib world that gets me from u'2008-06-05T04:04:48.830632+00:00' to some more useful time format? :)
[09:55] <dholbach> (apart from time.strptime())
[09:56] <thekorn> dholbach, no, I don't think so,
[09:56] <Odd_Bloke> dholbach: I'm not sure that having a NIH'd time library in launchpadlib would be desirable.
[09:56] <thekorn> I'm using strptime()
[09:57] <dholbach> thanks thekorn
[09:57] <dholbach> Odd_Bloke: no, not a time library :)
[09:57] <dholbach> but a UTC timestamp would be nice :-)
[09:58] <Odd_Bloke> dholbach: I see what you mean, sure. :)
[10:00]  * wgrant would have expected launchpadlib to return a datetime or similar.
[10:42] <salutis> hello all. yesterday I removed 3 packages from my PPA. now I can't upload new packages, every time I try, I receive mail with this error - "Rejected: File ........ already exists in PPA for Rudolf Adamkovic, but uploaded version has different contents." - what can I do? please help
[10:43] <bigjools> salutis: https://help.launchpad.net/Packaging/PPA#Deleting packages
[10:44] <salutis> bigjools: so, I must increase version :(
[10:45] <bigjools> salutis: yes, why is that bad?
[10:47] <salutis> bigjools: because, I am only in testing stage, repository is not used by real people. I don't want write to changelog, because it's only testing :( so, thanks for URL - I will increase versions and my testing repository will be moved back to my own server...
[10:48] <bigjools> salutis: right - the version bump is necessary because there's no way of knowing if your packages were downloaded and used by someone.  Re-using the same version Would Be Bad.
[10:55] <bigjools> salutis: regarding bug 275509, I am trying to re-create it.  Do you have available the package upload that originally caused the problem?
[10:57] <salutis> bigjools: it was problem with all packages until I changed name in profile
[10:57] <bigjools> salutis: okay, would you mind signing a small package for me that I can test on our dogfood server?
[10:59] <salutis> bigjools: yes
[11:00] <bigjools> salutis: thank you - can you upload something to upload.dogfood.launchpad.net please
[11:00] <bigjools> you won't get any email confirmations but I will see your upload on the server
[11:01] <salutis> bigjools: Uploading to dogfood (via ftp to upload.dogfood.launchpad.net)... Successfully uploaded packages.
[11:02] <salutis> bigjools: it's 'salutis-connect' package
[11:02] <bigjools> salutis: thank you!  very helpful, I'll let you know how I get on
[11:02] <salutis> bigjools: perfect
[11:08] <bigjools> salutis: the signing key you used is not registered in dogfood, can you use the one that is?
[11:18] <salutis> bigjools: i am only this one GPG key and I know nothing about dogfood. so, I don't know what can I do :)
[11:19] <bigjools> salutis: dogfood is an old copy of the production database, so you might have changed your key?
[11:19] <bigjools> it has your key ID as C60968A5
[11:24] <salutis> bigjools: yes, it was my old key and it's rejected
[11:25] <salutis> bigjools: new one is B0298FA8
[11:25] <bigjools> salutis: what is its fingerprint?
[11:27] <salutis> bigjools: fingerprint of new key is EE66 FB0F 6895 D743 FF98 34CF DF28 A983 B029 8FA8
[11:27] <bigjools> salutis: great, thanks
[11:28] <salutis> bigjools: np
[11:33] <bigjools> salutis: I sent you an email, can you decrypt and confirm the new dogfood key please!
[11:34] <salutis> bigjools: fyi: Your MobileMe Mail is currently unavailable. We apologize for this service interruption and are working hard to resolve the problem.
[11:34] <bigjools> gar
[11:35] <wgrant> Pastebin solves world hunger.
[11:35] <bigjools> already there :)
[11:35] <wgrant> Do any non-production Launchpad instances receive mail?
[11:35] <bigjools> yes but we capture it all
[11:36] <wgrant> I knew that about sending.
[11:36] <wgrant> But it seems most non-production instances lack the appropriate cron jobs to receive it.
[11:36] <wgrant> (I presume)
[11:36] <bigjools> salutis: http://pastebin.ubuntu.com/52047/
[11:37] <bigjools> wgrant: I see - ummm, I'm not sure
[11:37] <elmo> staging at least can receive email
[11:37] <wgrant> elmo: Hmm, I thought I tried that when I needed it.
[11:38] <elmo> well, I say 'can', I mean on the MX/MTA level.  whether or not anyone's listening/caring, I don't know ;-)
[11:38] <salutis> bigjools: confirmed
[11:38] <wgrant> Ah.
[11:38] <bigjools> salutis: awesome, thanks for your help
[11:38] <salutis> bigjools: np :)
[11:41] <bigjools> salutis: umm, sorry to bother you again, can you become an ubuntero on dogfood so I can do test uploads to your PPA
[11:43] <salutis> bigjools: and how to do that?
[11:44] <bigjools> salutis: go to https://dogfood.launchpad.net/~salutis
[11:44] <bigjools> sign the CoC
[11:48] <salutis> bigjools: I signed up at http://www.cocdirectory.com/COCs%20Sign-up%20Form.htm
[11:48] <salutis> bigjools: hah, just joking :) done
[11:49] <bigjools> salutis: thank you again :)
[11:51] <salutis> bigjools: np
[11:51] <ronny> hi
[11:52] <bigjools> salutis: well, I can't re-create that bug, your test package uploaded ok with UTF-8 in your LP name :(
[11:53] <salutis> bigjools: :(
[11:53] <wgrant> Is it the LP displayname and not Maintainer or Changed-By?
[11:53] <bigjools> definitely not the latter two, we have explicit tests for those
[11:54] <bigjools> he gets the problem in production when his display name in LP has UTF-8 in it
[11:54] <wgrant> Fun, fun.
[11:55] <bigjools> he's not the only one who's had this issue, someone emailed -users about it too
[11:55] <persia> Wait, are there any users in LP whose names *don't* contain UTF-8 data?
[11:55] <wgrant> I think it used to work.
[11:55] <wgrant> persia: I hope not.
[11:55] <wgrant> Though I have had an email come from LP with an illegal unencoded Latin-1 From.
[11:57] <bigjools> grrr I hate these
[11:57] <persia> I get a fair amount of bug notifications from users whose names are only expressed in Hangul or Hanzi, but don't generally look at the mail very carefully.
[11:57] <wgrant> persia: This wasn't bugmail; normal LP mail seems to work fine.
[11:58] <persia> Ah.  That makes more sense then, as I didn't think it was that broken.
[11:59] <wgrant> Python 3 will be nice, with its enforced unicode/bytes split. It will be less easy to code in stupid bugs like this.
[12:00] <bigjools> utf8 is the bane of my life
[12:00] <persia> bigjools: Why?
[12:00] <bigjools> well, combined with Python throwing wobblies
[12:01] <persia> bigjools: Well, consider that we could be asking to support the various different ISO-2022-* encodings ...
[12:01] <bigjools> fun
[12:01] <persia> Yeah.  UTF8 is your saviour: only one source of encoding madness :)
[12:02] <wgrant> ... until Microsoft decides to use UTF-16 for everything instead.
[12:02] <persia> Um.  Microsoft *does* use UCS-2 for nearly everything.
[12:03] <wgrant> They do.
[12:03] <wgrant> Unlike the rest of the world which uses UTF-8.
[12:03] <persia> Right, but it's foolishly trivial to switch between the two.  Try that with KO18 vs. EUC
[12:05] <persia> (even ignoring little things like KO18-R vs, KO18-U or EUC-KR vs. EUC-JP)
[12:05] <wgrant> Does anybody actually use !(ASCII|Unicode) any more?
[12:05] <persia> Yes.
[12:05] <persia> ISO-2022-jp is still the most common encoding for email here.
[12:07] <persia> Since *all* the handsets (even the linux ones) do that, it makes it hard to convince anyone UTF-8 is useful, unless they need to type in Cyrillic.
[12:09] <wgrant> persia: Do they at least decode UTF-8?
[12:10] <persia> Some very small percentage can handle UTF-8.
[12:11] <persia> At issue is that email is 85% handset based here, so the volume of workstation or laptop originated mail is sufficiently small that any problems are considered to be problems with the computers.
[12:11] <persia> Microsoft, Apple, GNOME, and Mozilla all have special workaround patches.  I don't know about other clients.
[12:12] <wgrant> Urgh.
[12:12] <bigon> is there anyway to completely remove a gpg key from a lp account?
[12:12] <persia> bigon: There's no way to completely remove a gpg once it's in the keyservers.  Are you sure you don't want to revoke it instead?
[12:12] <persia> s/gpg/gpg key/
[12:13] <persia> (maybe it can be removed from LP, but that's different)
[12:13] <bigon> yeah I will send the revoked key to the ubuntu keyserver
[12:13] <persia> That ought revoke it on all the keyservers.  As someone who foolishly let a subkey expire, I can say that Soyuz respects that sort of thing.
[12:14] <persia> bigon: Mind you, if you just want to get it off LP, but still retain exclusive control, revocation is a big hammer.
[12:14] <wgrant> Why do you want it entirely off LP?
[12:14] <wgrant> Others cannot see it if it is deactivated.
[12:14] <bigon> yeah I know, I've revoked the key (someone steal my laptop :(
[12:15] <wgrant> Ooh, fun.
[12:15] <bigon> yeah
[12:15] <persia> That's annoying.
[12:15] <bigon> good news to begin a new week
[12:15] <Dominic> oh, was it insured?
[12:21] <bigon> they break into my apartment, so the insurance should work
[13:23] <danilos> mdke: ping
[13:23] <mdke> danilos: (In case I'm not around at the moment, please provide a bit of information about what you want and I will respond when I get back)
[13:49] <Odd_Bloke> Has there been any recent news about Launchpad becoming free software?
[13:50] <wgrant> Odd_Bloke: Before OSCON next year, I believe.
[13:50] <Odd_Bloke> wgrant: Do you have a link I could reference?
[13:51] <wgrant> It wasn't very well publicised.
[13:52]  * Odd_Bloke found http://arstechnica.com/journals/linux.ars/2008/07/23/mark-shuttleworth-launchpad-to-be-open-source-in-12-months
[13:52] <wgrant> But there are a few like http://www.phoronix.com/scan.php?page=news_item&px=NjYwOA
[14:44] <andrea-bs> How can I know how many people have clicked on "this bug affects me too"?
[14:50] <salgado> andrea-bs, so far that information is not being displayed anywhere.  intellectronica should be able to tell us where we plan to display it
[14:51] <andrea-bs> salgado: is there a blueprint or a bug task for that?
[14:52] <andrea-bs> salgado: found :)
[14:52] <salgado> andrea-bs, https://blueprints.edge.launchpad.net/malone/+spec/malone-me-too
[14:52] <intellectronica> andrea-bs, salgado: you probably will never be able to know exactly how many people are affected, but eventually this information will be used to help you find relevant bugs to look at
[14:55] <andrea-bs> intellectronica: I think that knowing more or less the number of people affected would help to set the bug importance, at least for Ubuntu: https://wiki.ubuntu.com/Bugs/Importance
[14:56] <persia> intellectronica: Is there a reason that the number of people who pressed the button won't be visible?  Especially for packages with smaller userbases, this is interesting (where 8 could be most users)
[14:56] <intellectronica> andrea-bs: yes, that's the idea, but what you want to know is not so much how many users are affected for each bug, but how bugs related to one another on that axis
[14:58] <intellectronica> persia: the risk with displaying the number of users is that it will invite people to use this feature as a 'voting' facility. it isn't, and we want to design in in such a way that helps project collect useful information about which bugs happen a lot, rather than to emulate brainstorm
[14:59] <intellectronica> we might make it available via the api at some point, if it proves useful for some cases
[14:59] <persia> intellectronica: I understand.  My point is that setting the numbers against some range is only useful for a few packages with lots of bugs (e.g. firefox).  For packages with fewer users, the button won't do anything for those userbases.
[14:59] <andrea-bs> intellectronica: how about displaying the number only to bug contacts?
[15:00] <persia> intellectronica: For example, if I have 10 people reporting that kourou has a display issue, it's probably critical.  If I have 10 people reporting that firefox crashes on a given web page, I'm significantly less concerned.
[15:00] <intellectronica> andrea-bs: interesting idea. i think we might want to consider that
[15:01] <intellectronica> still, given a list of bugs you can fix, whether one is affecting 1000 users and the other 500, or one is affecting 100 users and the other 50, doesn't make much difference. the one affecting most users is the one you'll want to look at first
[15:02] <persia> Not necessarily, it depends on who you are.
[15:02] <intellectronica> persia: for example?
[15:02] <persia> For example, if you're a flavour developer, you're interested in report counts on bugs against your flavour, and bugs against other flavours may not be as important.
[15:03] <persia> (hence my comparison of kourou with ~10 confirmed users, and firefox with ~10,000,000 confirmed users)
[15:03] <intellectronica> persia: sure, but sorting within the criteria you've defined (using, say, tags, or packages, or whatever) will still be correct
[15:03] <persia> So, if you're flavour doesn't have very many users, the affected number that is a criticial priority is lower than for a flavour with more users.
[15:04] <persia> intellectronica: This is only for sorting?  There won't be any way to search for bugs that hit some criteria?
[15:05] <intellectronica> persia: for now it's onlt for collecting data. but yes, the initial use case is sorting
[15:06] <persia> intellectronica: OK.  I'd like more, as that's not very useful for me.
[15:06] <intellectronica> persia: what else do you think will be useful for you?
[15:06] <persia> intellectronica: But getting the data model, etc. integrated first is probably good.  The fact that it's not yet useful isn't a statement it shouldn't be done.
[15:07] <Hobbsee> intellectronica: i wonder if that will go the way of packages removals for ppa - a kind of useful feature, but so limited to not be of very much use at all...
[15:07] <persia> intellectronica: I want to be able to highlight issues that are affecting a significant number of users of a given flavour (I work on three flavours, none of which are Ubuntu Desktop), to build task lists, etc. and identify what needs to get done for certain milestones.
[15:07] <intellectronica> Hobbsee: i don't see how this has anything to do with package removals from ppas, tbh
[15:08] <intellectronica> persia: well, that's something you can do with sorting, no?
[15:08] <persia> intellectronica: The problem is identifying the cutoff point.
[15:08] <Hobbsee> intellectronica: only in that they both appeared to be very useful, but actually aren't so useful?
[15:09] <persia> If there's 200 hours of work needing doing in a week, that means there's a need for a bunch of people to coordinate.  If there's 30, then only a couple people can do it, and there's more bandwidth to work on future stuff.
[15:09] <intellectronica> persia: i would say that the cutoff point is defined by the resources you've got to throw at the problem. if you've got no one to fix the bug, it doesn't really matter how important it is
[15:10] <Hobbsee> or, are perceived to be, anyway
[15:10] <persia> intellectronica: That assumes I want to apply all available resources to fixing bugs, and none to developing features in the future, or working upstream.  That's not a safe assumption for any of the flavours with which I work.
[15:10] <intellectronica> Hobbsee: that's always a possibility. it's still worth trying out some stuff
[15:10] <Hobbsee> intellectronica: indeed.  I hope it can be made more useufl, before it's released :)
[15:11] <intellectronica> Hobbsee: in this particular case, just search for the huge amount of "me too" comments in bugs to see that there is a feature there wanting to become a reality
[15:11] <Hobbsee> intellectronica: the comments that i've seen in multiple channels so far about it have basically been "when did this appear?"  and "how do I see how many people have agreed with this?"
[15:11] <Hobbsee> intellectronica: indeed.  It's a good idea!
[15:12] <intellectronica> Hobbsee: for the next release, i don't think that this feature will become much more useful. there will be some additional tweaks to make the UI better, but i don't think we'll make anything other than being able to mark the bug as affecting you available. but we'll follow that with some goodies for querying too
[15:12] <Hobbsee> intellectronica: ahhh, pity.
[15:14] <persia> Well, it's a time thing.  If querying usefully becomes possible, it can become useful.  No reason to hold it out-of-trunk just because it's not useful yet.
[17:15] <salutis> hello all. salutis here again :) I have problem with PPA. I uploaded 3 packages and status is Built and Published. but I can't install packages on my system (No candidate version found for <package-name>). can anyone help me, please?
[17:17] <bigjools> salutis: you can browse your archive http://ppa.launchpad.net/salutis/
[17:17] <bigjools> and see if what you're expecting is there
[17:18] <salutis> bigjools: yes, it is. I can 'apt-get source' my packages, but I want install binary versions :(
[17:19] <bigjools> salutis: what is the package name/version please
[17:19] <geser> bigjools: is "published" the published date/time of the source or the binaries?
[17:19] <geser> I guess salutis should give it some more time (published 16 min ago)
[17:20] <salutis> 8 minutes
[17:20] <salutis> ah, I will wait...
[17:21] <bigjools> salutis: yes,it takes some time to publish, give it a while
[17:23] <salutis> ok guys, it's working - bigjools & geser - thanks!
[17:23] <bigjools> rock
[19:37] <AirBender> Hi, any issues with the servers? because I've tried to send a bug report, but the uploading process fails
[19:38] <AirBender> the file is 7MB in size...
[19:39] <salgado> the file size is likely to be the reason why it failed
[19:39] <salgado> intellectronica, do we have a size limit on attachments?
[19:40] <salgado> AirBender, where does that file come from?
[19:41] <AirBender> is a crash report from apport(ubuntu)
[19:41] <AirBender> targzipped(actually it's 9.5 MB)
[19:41] <AirBender> ok, so, would be great to know the size limit
[19:43] <salgado> AirBender, I don't think it's failing because of a size limit (I asked just to be sure).  I'm guessing the upload is timing out and the bug reporting fails thanks to that
[19:44] <AirBender> well, actually, after the failed bug report, I tried to upload the file as an attachment posting in the bug thread, and it failed in the uploading process...
[19:45] <AirBender> then I see the message"Please try again, otherwise tell the guys in IRC... bla bla bla"
[19:52] <salgado> AirBender, did you get an OOPS id when it failed?
[19:53] <intellectronica> salgado: yes, we do
[19:53] <intellectronica> (though i don't remember what it is off the top of my head. let me check)
[19:54] <AirBender> em nop, I don't know what this is is like an error code?
[19:56] <salgado> AirBender, yes, when something goes wrong you should get an OOPS page with a unique OOPS id
[19:57] <AirBender> I only get a page with 4 lines
[19:58] <AirBender> saying Please try again in green
[20:01] <kiko> salgado, it's an apache timeout I believe
[20:01] <kiko> and it happens because the connection's been left open for too long
[20:02] <AirBender> yes, I think so
[20:02] <AirBender> may be a customized apache error page
[20:02] <kiko> AirBender's right on the money
[20:03] <kiko> salgado, there is a bug open for this. what I'd like to suggest (it's crazy, so warning)
[20:03] <kiko> is to check whether or not AirBender would be able to upload the same file using sftp:// into a .bzr directory of a random branch he has write access to.
[20:03] <kiko> salgado, IYSWIM you will see how evil I can be
[20:05] <salgado> kiko, and then link to that file from the bug report?  or can he use the file's URL when attaching it to a bug?
[20:06] <kiko> salgado, well.. I just wanted to check whether or not the upload would succeed. if it would, then I am suggesting we generalize the SFTP service we have to allow uploading other stuff apart from .bzr branches. crazy? :)
[20:07] <kiko> salgado, as to his specific problem, I guess my best suggestion right now is using something like easyshare :-/
[20:08] <AirBender> so the problem is just the uploading time?
[20:09] <salgado> AirBender, it seems so.  can you try what kiko suggested?
[20:09] <kiko> AirBender, yeah. if you're not super-fast it times out.
[20:09] <kiko> AirBender, IIRC sidnei has a script to upload using wget in fact!
[20:09] <kiko> or curl
[20:09] <kiko> sorry
[20:11] <AirBender> but I don't have access to the server(if you want me to use sftp)
[20:16] <AirBender> curl sounds good, but I don't know where to upload
[20:16] <AirBender> lol
[20:16] <AirBender> well it's not that urgent anyway
[20:17] <AirBender> it's just pidgin crashing then you try to send a tar.gz file 0D
[20:18] <salgado> AirBender, you can register a new branch at https://code.launchpad.net/people/+me/+addbranch and then upload the file using sftp
[20:19] <salgado> as kiko suggested
[20:19] <salgado> AirBender, or you can upload the file to a hosting service like easyshare/dropbox and link to it from the bug report
[20:21] <AirBender> mmm well, don't even know if the report is needed, since there's no too much activity in this bug, but good sugestion anyway
[21:00] <dogi> hi all
[21:03] <dogi> on this page https://code.launchpad.net/bitbox in my lauchpad testing process i added 2 vcs trunks
[21:03] <dogi> now is wanted the delet them but i dont find the right button ...
[21:03] <dogi> ups
[21:04] <dogi> i want to delet them, but i dont know how to do that
[21:06] <mwhudson> dogi: you want to delete both of them?
[21:07] <rockstar> dogi, when you go to the branch page, it's the red icon next to the title.
[21:07] <mwhudson> rockstar: these branches are owned by ~vcs-imports though :)
[21:08] <rockstar> mwhudson, Good thing we know some members of vcs-imports then.  :)
[21:08] <dogi> yupp both vcs es
[21:09] <dogi>  ~vcs-imports/bitbox/bitbox there
[21:09] <dogi> is no red logo
[21:12] <mdke> danilo[home]_: pong?
[21:28] <mwhudson> dogi: done
[21:38] <dogi> thx mwhudson
[21:38] <dogi> :)
[21:40] <dogi> ciao
[22:48] <Verterok> mwhudson: thanks for the cleanups to my logging branch ;)
[22:49] <mwhudson> Verterok: np!
[23:48] <kees> does anyone have examples of how to get a list of files from a PPA using the LP API code?
[23:48] <wgrant> kees: You can't.
[23:48] <wgrant> (yet)
[23:48] <cprov> kees: LP API doesn't cover PPAs yet
[23:49] <wgrant> Bug #276020
[23:49] <kees> cprov: oh... the docs for "archive" mention PPA
[23:50]  * wgrant hadn't noticed that that was exposed yet, but it does seem to be.
[23:53] <kees> wgrant: I'm not sure it does very much
[23:54] <wgrant> It doesn't.
[23:54] <wgrant> It seems to just expose the attributes of an Archive object, and nothing more.
[23:54]  * kees starts writing xpath to screen-scrape...