[00:04] <cprov> Whoopie, wgrant:  email lookup issue fixed.
[00:05] <Whoopie> cprov: so I can re-upload?
[00:05] <Whoopie> cprov: and btw, wow, fixed very fast.
[00:06] <cprov> Whoopie: yes, you can re-upload.
[00:06] <wgrant> cprov: Nice quick fix.
[00:06] <cprov> Whoopie: it was a known problem.
[00:07] <Whoopie> cprov: aha, so I just prodded you to fix it? :)
[00:08] <mwhudson> the thing is, it was fixed already, the fix just wasn't on all the machines it needed to be
[00:08] <Whoopie> mwhudson: thanks to you, too.
[00:08] <wgrant> Ahh.
[00:09] <mwhudson> Whoopie: i'm just another grateful beneficiary of cprov's sleuthing :)
[00:09] <mwhudson> maxb: ssh-ing in to bazaar.launchpad.net should be faster now, btw
[00:11] <cprov> Whoopie: gstm accepted!
[00:16] <wgrant> Is it useful to update the last modified date on a branch just for attribute changes?
[00:16] <maxb> mwhudson: Woot! That's a tenfold improvement! :-)
[00:17] <maxb> Very many thanks indeed!
[00:17] <wgrant> I care about when the branch changed, not when somebody set its status.
[00:18] <Whoopie> cprov: package was accepted. ;)
[00:19] <cprov> Whoopie: cool
[00:22] <spiv> wgrant: ISTR a bug report about that...
[03:46] <wgrant> Why is Launchpad Answers sending emails with my name and some email address which isn't mine?
[03:46] <wgrant> It decides that my email address is the question's email address, it seems.
[03:49] <spm> wgrant: whee. that sounds like a fun trick. which Q in particular?
[03:49] <wgrant> spm: The one you fixed for me.
[03:49] <wgrant> But it happens for all.
[03:50] <wgrant> From: Some User <question1234@answers.launchpad.net>
[03:50] <cody-somerville> wgrant, Is it possible that maybe its your mail client doing it?
[03:50] <cody-somerville> wgrant, What mail client do you use?
[03:50] <wgrant> cody-somerville: Evolution.
[03:51] <wgrant> cody-somerville: But no, the RFC2822 has that header in it.
[03:51] <spm> that sounds like a nasty bug - I know there is a fix around that area that was supposed to go out yesterday/today. So...
[03:51] <wgrant> It is definitely Launchpad.
[03:51]  * wgrant looks for a bug.
[03:52] <spm> wgrant: so., with my update to that Q I see: From: Steve McInerney <question66189@answers.launchpad.net>  & then yours has: From: William Grant <question66189@answers.launchpad.net>
[03:52] <spm> is that what you're referring to?
[03:52] <wgrant> spm: Yes.
[03:52] <wgrant> That is going to break anything that autocreates contacts.
[03:52] <spm> ah. I call feature.
[03:52] <wgrant> Which is lots of things.
[03:53] <spm> heh
[03:53] <wgrant> How is it a feature?
[03:53] <wgrant> Malone doesn't do it.
[03:53] <wgrant> And I tend to think Malone is right about most things with regard to email.
[03:54] <spm> well - it's been doing it for a while - fwiw - I have a similar one from late March.
[03:54] <spm> so my 2c guess at feature? 1. it comes from the person who responded - imho a good thing - ie their name. But from their email address would be... bad.
[03:55] <wgrant> Why?
[03:55] <spm> 2. the actual address is the question; which can be parsed/responded to and the right thing will happen
[03:55] <wgrant> Malone sends it from the right person.
[03:55] <wgrant> s/person/address/
[03:55] <spm> if it comes from their email address? that will break with some anti-spam solutions.
[03:55] <wgrant> Those antispam solutions are broken.
[03:55] <wgrant> You cannot filter on From.
[03:55] <wgrant> Sender, yes.
[03:56] <wgrant> If you filter on From, you should be blasted off the Internet.
[03:57] <wgrant> Malone does it properly.
[03:57] <spm> From filter: eg SPF
[03:57] <wgrant> SPF is Sender, not From.
[03:58] <wgrant> Or most Launchpad bugmail would get nowhere.
[03:58] <spm> I suspect we're disagreeing on terminolgy?
[03:59] <wgrant> I speak of real RFC2822 header fields names.
[03:59] <wgrant> SPF doesn't care about From, just Sender.
[03:59] <wgrant> Malone uses the Person's display name and primary email address to construct From. It uses bounces@canonical.com as Sender. It sets Reply-To to the bug address.
[04:03] <spm> so. to rephrase your concern: it's around the diff between the use of the Sender vs From header fields? is that it in a nutshell?
[04:04] <wgrant> spm: My objection is that it's reporting my email address as something it is not.
[04:05] <spm> btw. SPF is (should!) be based on (E)SMTP headers, not email body text headers - very different beasties those.
[04:05] <wgrant> Blah, yes, Return-Path, not sender, though those should usually be the same.
[04:05]  * wgrant dies.
[04:06] <spm> :-)
[04:06] <cody-somerville> Is it possible to use launchpadlib to get all the source packages a team is subscribed to?
[04:07] <wgrant> cody-somerville: No.
[04:07] <wgrant> Structural subscriptions are not exported.
[04:10] <spm> wgrant: oki.I can see your concern then. I (obviously!) can't speak to the reasons why A vs B for Answers. My personal take is that what works for one group - eg bugs, probably wouldn't work for another, eg answers. despite the similarity. I guess this also falls into the Great Debate on lists and ReplyTo header usage. I'll stick with vi vs emacs for now myself. ;-)
[04:11] <wgrant> IMO Malone's use of Reply-To is wrong, but it's probably the best that exists now.
[05:31] <poolie> https://bugs.edge.launchpad.net/ubuntu/+bug/286193/comments/11 <--- YHBT :-)
[05:32] <wgrant> poolie: I actually laughed when I read that.
[05:33] <poolie> i laughed at both the original post by elmo and the response
[05:33] <wgrant> Yes.
[05:33] <wgrant> I wondered if anybody would fall for it.
[05:33] <wgrant> But I thought everybody would know who elmo was...
[05:51]  * wgrant wishes there was some throwaway Launchpad instance that sent email.
[06:12] <wgrant> Any Code people around?
[06:15] <cody-somerville> Waz is your question? :)
[06:26] <jml> I'm around.
[07:43] <wgrant> jml: Blah, didn't see that message. You might have seen a bug I filed an hour or so ago.
[07:43] <jml> wgrant: yeah I did.
[07:43]  * jml comments.
[08:50] <progfou> hi there
[08:50] <progfou> any current known problem with bazaar.launchpad.net?
[08:51] <intellectronica> progfou: i'm not having any problems with it. what's going wrong for you?
[08:53] <wgrant> intellectronica: Loggerhead is unhappy.
[08:55] <intellectronica> right, now i also can't get it to cooperate
[08:55] <spm> ok. /me gets out the codebouncy restart gun
[08:56] <progfou> when going to my project's sources, I'm getting an error page informing I should reload the page in a few minutes and if it persists come here and inform about this problem
[08:56] <progfou> here is my project's sources link: http://bazaar.launchpad.net/~progfou/ovniconv/trunk/files
[08:57] <spm> progfou: wgrant: is restarted. try now?
[08:58] <progfou> it works now, thanks!
[08:58] <progfou> was it my fault?
[08:58] <intellectronica> jml: LH is occasionally unresponsive. movie at 11
[08:58] <progfou> something I have to tune?
[08:58] <spm> progfou: no. is very well known. hence the "codebouncy" comment :-)
[08:58] <progfou> oh... ok :-)
[08:59] <progfou> thanks spm
[08:59] <progfou> have a nice day everybody!
[09:12] <geser> cprov: about the soyuz LP API: do I understand it correctly that build.current_source_publication only works for the most recent build and older builds (for older versions) return None there?
[09:15] <cprov> geser: yes, that's correct.
[10:13] <geser> question about the LP API: what's the difference between distribution.current_series and distribution.getDevelopmentSeries()?
[10:29] <jtv1> adiroiban, hi!  do you get the "change details" option on Ubuntu templates now?
[10:43] <waraqa> As a translator, Lanuchpad asked me If I want put my translations under BSD license.
[10:44] <waraqa> How can I can change my choice ?
[10:45] <wgrant> waraqa: https://translations.launchpad.net/people/+me/+licensing
[10:45] <waraqa> wgrant: Thank you.
[13:07]  * wgrant grimaces.
[13:07] <wgrant> Apparently the 'This bug affects me to' link does in fact cause people to not post '+1' comments.
[13:08] <wgrant> Instead they post comments with the identical text 'This bug affects me too'.
[15:41] <radix> hey guys, if we create a superproject which contains one private project and one public project, would there be any danger of information leak?
[15:41] <mbt> Hello, looking into bug 358200 leads me to a forbidden page, is a dupe of a private bug... can anyone determine why bug 213573 is private and either subscribe me to it or make it public?
[15:42] <mbt> And ubottu has it wrong, 358200 is public
[15:44] <james_w> mbt: it's private due to Ubuntu policies
[15:45] <james_w> it needs an initial triage to make it public, which I can do now for you
[15:46] <mbt> james_w: Thanks :)
[15:47] <james_w> mbt: have at it
[15:48] <mbt> james_w: Thank you very much!
[15:48] <james_w> that step is just a safety check in case it crashes while trying to do something with your password, say
[15:48] <james_w> we just check there's no sensitive information in the bug and then open it up
[15:49] <mbt> james_w: Understandable; I figured there had to be a reason being it was old.  Still, hard to fix software if the bug isn't viewable. :-P
[15:54] <barry> radix: unclear.  i can check around for you though
[15:54] <radix> barry: I assume nothing bad would happen, I guess I'd just like to know if this is being done already
[15:55] <barry> radix: i'm not aware of any such existing arrangement
[15:55] <barry> radix: and i can't *think* of any problems
[15:57] <radix> barry: okay, I think I'll just try it
[15:57] <radix> barry: and if something goes wrong I'll yell at a LP dev :)
[15:58] <barry> sounds good! :)
[15:58] <radix> oh
[15:59] <radix> I guess there's still no UI for creating new superprojects. barry: should I register a Question?
[15:59] <barry> radix: yes, i think only lp admins can do that.  possibly lp devs, but then aren't you an lp dev?
[15:59] <radix> barry: no, I'm landscape :-)
[16:00] <barry> radix: it's all the same, right? :)  but no, it's an lp admin thing.  give me the q# and i'll assign it to a losa
[16:00] <radix> Okay cool
[16:01] <radix> barry: q #66961
[16:02] <barry> radix: assigned to losas
[16:03] <radix> barry: thanks very much!
[16:09] <geser> question about the LP API: what's the difference between distribution.current_series and distribution.getDevelopmentSeries()?
[16:12] <barry> geser: it's a bit subtle.  current_series returns one series, getDevelopmentSeries() can return many
[16:12] <barry> geser: it's made confusing because 'series' is its own plural
[16:12] <barry> geser: internally, the method is called getDevelopmentSerieses() which isn't a word :)
[16:13] <geser> barry: and which one is preferred if I want the distro_series object for jaunty? I currently use current_series for it
[16:15] <barry> geser: that's a good question.  i think current_series should do it
[16:16] <geser> and btw: doesn't "Pre-release Freeze" count as development version? I looked at the return value for ubuntu.getDevelopmentSeries() and wondered that it was empty
[16:19] <barry> geser: i don't know.  i could try to track down a distro guy to ask.
[16:21] <barry> geser: actually, it will only return series that strictly have a status of 'Active Development', so 'Pre-release Freeze' doesn't count
[16:23] <geser> barry: thanks. So I will continue to use current_series in my script to always get the current ubuntu development version.
[18:00] <Agafonov> Hi. Can you help me with some "team contact e-mail" magic?
[18:03] <kiko> Agafonov, sure?
[18:05] <Agafonov> yes. forgive the noob :)
[18:09] <kiko> Agafonov, what's your question?
[18:10] <Agafonov> We are organizing https://launchpad.net/~ubuntu-ru and I set temporarly my e-mail as team contact to not disturb whole team hierarchy. Now we have list for group and I set it as team contact.
[18:10] <Agafonov> Previous temp email remains...
[18:11] <kiko> hmmm
[18:11] <kiko> I think you can adjust it using +editemails
[18:11] <kiko> sinzui, barry: is that right?
[18:12] <barry> +contactaddress i think
[18:12] <barry> Agafonov: yep.  go to ~ubuntu-ru/+contactaddress
[18:13]  * sinzui waits for the next request that will highlight a bug where the team cannot remove a temporary email address.
[18:14] <Agafonov> There is no my previous email in шею Only new list.
[18:14] <Agafonov> There is no my previous email in it. Only new list.
[18:16] <Agafonov> barry: ?
[18:16] <barry> Agafonov: sorry.  hang on just a sec...
[18:16] <Agafonov> Is screenshot needed?
[18:17] <barry> Agafonov: nope, sorry, i just had to clear my plate of something else
[18:17] <barry> looking now
[18:17] <barry> Agafonov: you have two contact addresses for your team?
[18:17] <barry> Agafonov: is that the problem?
[18:18]  * barry wonders how that's even possible
[18:18] <Agafonov> yes. Things must be in order :)
[18:18] <barry> Agafonov: okay, let's try this: go to your +contactaddress page and click on "Each member individually"
[18:19] <barry> Agafonov: then click on Change and let me know when you've done that
[18:19] <Agafonov> ok
[18:19] <Agafonov> switch back to the list?
[18:20] <Agafonov> (noted no team contact email)
[18:20] <barry> Agafonov: yes.  looks like that cleared both
[18:20] <barry> Agafonov: let's see if switching it back to the mailing list does the right thing
[18:20] <Agafonov> ha. nope...
[18:21] <Agafonov> both returned
[18:21] <barry> Agafonov: weird!  let me poke at this with one of my teams and i'll get right back to you
[18:22] <Agafonov> ok
[18:25] <barry> Agafonov: okay, i can't reproduce this with one of my teams.  i'm going to click on contact this team, can you tell me if you receive a copy and if the list also receives a copy?
[18:26] <barry> Agafonov: email sent
[18:28] <Agafonov> first received (second may delay, so I'll wait ~5 minutes)
[18:28] <barry> Agafonov: which have you received?  the personal copy or the list copy?
[18:28] <Agafonov> list
[18:29] <barry> Agafonov: cool
[18:30] <mdz> I noticed I'm getting email from rosetta for each upload I've made to jaunty.  is this normal?
[18:33] <barry> Agafonov: you may not get a second copy.  i'm checking things, but that might just be a page display glitch
[18:36] <Agafonov> am i need to report a bug?
[18:37] <barry> Agafonov: yes, i think it's a good time to report a bug
[18:37] <Agafonov> :-/
[18:38] <barry> Agafonov: please do mention that i sent a Contact This Team email and which copies you do or don't get
[18:38] <Agafonov> ok
[18:44] <barry> Agafonov: let me know the bug number when you've submitted it
[18:45] <Agafonov> sure
[18:56] <kwah> hi all
[18:56] <kwah> were one may find a documentation on what kind of e-mails may be used as a team contact?
[19:05] <sinzui> kwah: you may use any email address. That email address may be the address of a mailing list. You can create a mailing list on launchpad and use that list for the team members
[19:06] <rbelem> hello all
[19:08] <rbelem> is there any way to build package in ppa for multiple ubuntu versions without edit changelog?
[19:08] <cody-somerville> rbelem, yes, by changing the Distribution field in the changes file
[19:08] <rbelem> cody-somerville, hum...
[19:09] <cprov> rbelem: so, cody-somerville means 'no' ;)
[19:09] <rbelem> :-(
[19:10] <rbelem> i'm building a ppa to host enlightenment foundation libraries
[19:10] <cprov> rbelem: there are plans to support multiple distribution targets in the changelog entry like "foo-bar (1.0) hardy intrepid jaunty; urgency=normal"
[19:10] <rbelem> cprov, cool
[19:11] <rbelem> https://launchpad.net/~e17-packaging/+archive/ppa
[19:11] <rbelem> cprov, when will this feature be ready?
[19:11] <cprov> rbelem: and it would imply in one build per target with a implicit and distinct rebuild index
[19:12] <cprov> rbelem: unfortunately, not soon, maybe by May.
[19:13] <kwah> sinzui, yep, right, but I could not do it with my existing e-mail
[19:13] <cprov> rbelem: sabdfl has *special* interests on it, so we better get it done ;)
[19:13] <rbelem> cprov, next month?
[19:13] <rbelem> ehehehehe
[19:13] <kwah> and lp mailing-list of other group could not be used either
[19:14] <sinzui> kwah: not if the email is already registered with you. Actually I recommend not using an email that is associate with you. we cannot transfer email addresses between users and between teams :(
[19:14] <rbelem> cprov, it's not so far away
[19:14] <sinzui> kwah: there is a bug filed about that
[19:14] <sinzui> kwah: by setting up a mailing list, you get an email address for free
[19:14] <kwah> sinzui, :(
[19:15] <kwah> what about structure like that
[19:15] <cprov> rbelem: we will be planning it soon, I will ping you when I have an ETA.
[19:15] <kwah> group > subgroup
[19:15] <kwah> I tried to use group's list address as a contact for subgroup - no luck
[19:15] <cprov> rbelem: meanwhile you can use auto-ppa for automating the source generation for multiple distroseries.
[19:16] <rbelem> cool!!! thanks a lot cprov
[19:16] <sinzui> kwah: right, because addresses cannot be shared, and the cannot be transfered
[19:16] <cprov> rbelem: you are welcome.
[19:17] <rbelem> cprov, is this feature available right now?
[19:17] <cprov> rbelem: auto-ppa ?  yes
[19:17] <sinzui> kwah: and in truth, they cannot be deleted. Removing an address just means you do not intend to use it, but there is no sensible result that allows someone else to use ti
[19:17] <rbelem> cool!
[19:17] <cprov> let me find the LP project for you.
[19:17] <rbelem> ok
[19:17] <cprov> rbelem: https://edge.launchpad.net/autoppa
[19:18] <kwah> sinzui, so, sensible use-case group > subgroup1, subgroup2 etc can not be really implemented in terms easy contacting subgroups
[19:19] <rbelem> cprov, that's awesome
[19:19] <kwah> only by arranging a list for every group and CC-ing all over the place?
[19:19] <rbelem> thanks again cprov
[19:20] <sinzui> kwah: launchpad will contact each member individually if the team or subteam does not have a contact address
[19:20] <rbelem> cprov, i will find out how to use
[19:20] <cprov> rbelem: no worries, it will make your life easier until we support source uploads with multiple targets.
[19:21] <sinzui> kwah: by giving a team a contact address you are saying there is some mechanism to will forward the message to some or all of the team members
[19:21] <kwah> sinzui, yep, we noticed that already... that's why we are trying to figure out what would be more reasonable setup in terms of contacts etc.
[19:21] <sinzui> kwah: Launchpad's hosted mailing lists is such a mechanism
[19:21] <kwah> when we have umbrella team
[19:22] <rbelem> cprov, nice! :-)
[19:22] <barry> kwah: we don't currently support hierarchical mailing lists
[19:23] <Shock> hi. what does launchpad invoke when I upload a source package to my PPA in order to build it?
[19:23] <kwah> barry, hm. Is it hierarchical?
[19:23] <kwah> subteams are treated as memebers of umbrella team
[19:24] <cprov> Shock: `sbuild`
[19:24] <barry> kwah: team structure can be, but not (directly) mailing lists.  each team can have a separate mailing list and any member of a subteam can join the superteam's list
[19:24] <kwah> why tema contacts are treated differently?
[19:24] <kwah> s/tema/team
[19:25] <barry> kwah: i'm not sure what you're asking. mailing lists are related to teams, but are different
[19:25] <barry> contact addresses are basically just the address to send messages to
[19:25] <cprov> Shock: it does pretty much the same as `debuild` but within a pristine chroot (pbuilder) with extra security paranoia. Are you having any problems with your sources ?
[19:26] <Agafonov> barry: https://bugs.launchpad.net/launchpad/+bug/358661
[19:27] <Shock> cprov: i'm trying to learn how to make it build just for a specific arch
[19:27] <cprov> Shock: adjust the 'Architecture:' field in debian/control file.
[19:27] <kwah> barry, yep, I got it.
[19:28] <Shock> cprov: i'm trying to build the kernel, there's lots of "Architecture:" fields :)
[19:28] <kwah> barry, but still it is a kind of not logical for me ;)
[19:29] <cprov> Shock: oh, an existing source.
[19:29] <barry> Agafonov: thanks.  i've added an update.  i think this is a shallow-ish bug tho no eta for fixing yet.  it should not affect your team's contact address.  such mails should go to your team properly without a copy to you
[19:29] <barry> kwah: ;)
[19:29] <Shock> yeah :)
[19:29] <kwah> barry, so, one conact e-mail for different teams is ALSO not possible if I got it correctly
[19:29] <cprov> Shock: the kernel binaries (except the docs) are architecture 'any', so they will build in any supported architecture in the build env
[19:30] <cprov> Shock: why do you want to change it ? aren't you uploading it to a PPA ?
[19:30] <cprov> Shock: let it build where it is supposed to.
[19:30] <barry> kwah: you could try this (i'm actually not sure if it will allow you to do it).  create your superteam and give it a mailing list.  then in your subteams, use "explicit address" and point them at your superteam's mailng list
[19:30] <Shock> cprov: so it only builds the kernel packages on only one arch
[19:30] <Agafonov> barry: kwah is talking about our ~ubuntu-ru group :)
[19:31] <kwah> barry, yep, tried it already
[19:31] <barry> kwah: subteam members can subscribe to super team mailing lists, but all subscriptions must be explicit
[19:31] <barry> Agafonov: ah :)
[19:31] <kwah> confirmation e-mail got lost somewhere
[19:31] <cprov> Shock: no, 'any' means build on each available arch.
[19:31] <Shock> cprov: i've created a different flavor, so if people use my ppa i don't want to duplicate the packages that are already in the ubuntu repos
[19:31] <barry> kwah: yes, that's the tricky part.  look on the team's home page and see if you see a "moderate mailing list"
[19:31] <kwah> nothing is there
[19:31] <Shock> cprov: i understand that :)
[19:32] <barry> kwah: pick the confirmation url out of that message, then discard the conformation so it doesn't go to your list
[19:32] <kwah> I checked a couple of times
[19:32] <barry> kwah: ok.  so that's probably because the confirmation is not sent from a registered lp address
[19:32] <kwah> or at least was not
[19:32] <barry> kwah: yay!  you're stuck :(
[19:32] <kwah> will check again
[19:33] <cprov> Shock: I don't see why would you be bothered with it, it's more work for you and if someone using 'lpia', for instance, tries to use your PPA it won't be possible.
[19:33] <kwah> barry, nope, naothing
[19:33] <barry> kwah: this is an interesting use case that we do not handle.  you might report a bug on it.  let me know what the bug number is and i'll triage it as a 'wish list' item
[19:33] <barry> kwah: yep.  if you haven't gotten it by now, you won't.  and my previous explanation makes sense
[19:35] <Shock> cprov: my kernel is only useful on i386. i'm concerned that if some packages are also in my ppa as well as ubuntu repos my packages might get installed
[19:40] <RachedTN> Hello, I have create a project on lauchpad, and now I want to delete it, does anybody know how ?
[19:43] <cprov> Shock: independently of the arch-issue, your ppa packages should have a different (lower) version than the ones in ubuntu repo
[19:44] <RachedTN> cprov: ??
[19:44] <barry> RachedTN: we can mark the project disabled for you
[19:45] <barry> RachedTN: what is the project name?
[19:45] <Shock> cprov: unfortunately if I do that the build fails with ABI errors and i haven't found the help to fix it in the #ubuntu-kernel channel :(
[19:45] <RachedTN> barry : fine , so here is the link : ﻿https://edge.launchpad.net/ubuntu-tn-redaction
[19:45] <Shock> cprov: so I've created a new flavor
[19:47] <cprov> Shock: oh, I see
[19:47] <cprov> Shock: the kernel is *special*
[19:48] <kwah> barry, it looks like the same policy... if some e-mail used once, you can not use it anymore
[19:48] <kwah> as a team contact at least
[19:50] <kwah> and it does not matter, whether the team you try to assign it to is a subteam of the team with the contact e-mail in question
[19:51] <Shock> cprov: and so is the kernel team ;)
[19:54] <cprov> Shock: is it hard to define a new kernel version for a specific flavor  ?
[19:54] <Shock> cprov: the documentation is lacking i think
[19:55] <cprov> Shock: anyway, if you have it overridden for i386, I don't see the problem in propagating it to the other PPA archs
[19:55] <Shock> cprov: i'm now trying to understand it by looking at the build system scripts
[19:55] <cprov> Shock: unless your kernel explodes on them, is that the case ?
[19:55] <Shock> cprov: my only changes affect the i386 arch
[19:56] <Shock> cprov: i'v managed to generate a debian/control file with just the packages i need, will see how that goes
[19:56] <cprov> Shock: that's fine, let the kernel build where it wants and avoid a bigger diff with the ubuntu  source.
[19:56] <cprov> okay
[19:58] <Shock> cprov: thanks for taking an interest
[19:58] <barry> RachedTN: okay, your project should be disabled now.  please check your email for confirmation
[19:58] <cprov> Shock: np
[19:59] <barry> kwah: i think you're stuck.  please do open a bug on this
[20:00] <kwah> barry, I will
[20:10] <verterok> cprov: hi! statik pointed you as the one that might have some answers about this https://pastebin.canonical.com/16135/ ;)
[20:13] <RachedTN> barry: thanks a lot, it's desactivated now :)
[20:13] <barry> np!
[20:13] <cprov> verterok: let me see it.
[20:14] <verterok> cprov: thanks
[20:14] <cprov> verterok:  I can download the file.
[20:16] <verterok> cprov: me too, but I keep getting that error when using "apt-get install"
[20:17] <cprov> verterok: which error ?
[20:17] <verterok> cprov: the http 501 response
[20:18] <verterok> cprov: hmm, it seems to be working now
[20:19] <verterok> cprov: thanks for fixing it so quicky! ;)
[20:20] <cprov> verterok: I haven't changed anything ...
[20:22] <verterok> cprov: I know :) maybe my isp turned off their proxy...or fixed it :/
[20:27] <barry> well, unfortunately it's a short day for me folks.  i'm off now.
[20:27] <RachedTN> thanks anyway, and keep the good work :)
[20:51] <mbt> Does the apport retracing service delete stack traces if it determines that a bug is a duplicate?
[21:01] <rbelem> cprov, autoppa is not available yet for jaunty, right? but i built the package for me
[21:01] <cprov> rbelem: yes, checkout the branch, I'm not sure if it's packaged.
[21:02] <rbelem> cprov, ok ;-)
[21:02] <cprov> rbelem: apparently it is -> https://edge.launchpad.net/ubuntu/+ppas?name_filter=auto-ppa
[21:05] <rbelem> cprov, the last version in ppa is for gutsy
[21:06] <cprov> rbelem: look from the bright side, you can re-package it using trunk in your PPA :)
[21:06] <rbelem> cprov, eheheheh ;-)
[21:07] <rbelem> cprov, i will do this
[21:07] <cprov> rbelem: cool
[21:07] <rbelem> :-)
[21:18] <gnomefreak> a LP admin around? i would like to discuss removing someones LP account
[21:24] <kiko> gnomefreak, we don't usually do that sort of thing..
[21:24] <kiko> gnomefreak, what's the issue?
[21:24] <gnomefreak> kiko: one sec
[21:25] <gnomefreak> kiko: https://bugs.edge.launchpad.net/ubuntu/+source/pulseaudio/+bug/192888/comments/342  not sure if this was only time he did it
[21:25] <gnomefreak> im betting its not but dont know
[21:25] <kiko> gnomefreak, heh, that is absolutely spam. hang on.
[21:25] <gnomefreak> kiko: thanks
[21:27] <kiko> gnomefreak, can you contact the user for us meanwhile? i think he's a valid user, so either it's a spambot using his from: address, or a responder he's got set up
[21:28] <gnomefreak> ill try to email him but im not even sure if the hotmail address is valid ill look at his LP page to see what address he gives
[21:28] <kiko> gnomefreak, he's commented on bugs before, I think it is
[21:29] <gnomefreak> k
[21:29] <kiko> gnomefreak, he's french btw.
[21:32]  * intellectronica thinks that free software and nudism mix quite well, actually, doesn't understand what the fuss is about
[21:33] <gnomefreak> intellectronica: other than the 130+ comments? takes a while to load but still should never be on a bug report IMHO
[21:34] <kiko> intellectronica, it's really irrelevant to the bug report at least, and nobody should get nudist invitation spam redirected from us
[21:34] <gnomefreak> kiko: https://edge.launchpad.net/~zobbychris
[21:34] <gnomefreak> its blank
[21:34] <kiko> gnomefreak, bugs.edge
[21:34] <gnomefreak> oh
[21:41] <gnomefreak> sending
[21:59] <radix> I can't find the button for adding a release any more (on edge). does anyone know where it is?
[22:01] <radix> I really can't find it. this is strange.
[22:02] <kiko> sinzui, ^^
[22:04] <radix> oops, okay, someone pointed me to where it is
[22:04] <radix> on the Milestone page now
[22:04] <sinzui> radix for this month only, you need to create the milestone, then create the release
[22:04] <radix> okay, that's fine, we were already using version-milestones
[22:04] <radix> I just didn't think to look there
[22:05] <sinzui> radix, If you can wait until monday, you can see EdwinGrubbs's very nice create a release and select/create milestone UI.
[22:05] <radix> I'll have to make the release today, I'm afraid ;-) but I do look forward to it!
[22:55] <mbt> radix: This new interface, will that let arbitrary releases be made again?  I'd like to make "snapshot" releases that do not belong to a milestone, for example... I don't see a way to do that ATM
[22:56] <radix> mbt: you've got the wrong guy. I don't know anything about it, I was just trying to use it :-)
[22:56] <mbt> Oh, lol.  I need to learn how to read my scrollback buffer, lol
[22:56] <mbt> sinzui: Can you answer that last question?  :-D
[22:59] <sinzui> mbt: for this month *only* you must create a milestone first
[22:59] <sinzui> mbt Next week on on edge, we will begin testing the new create a release ui that will create a milestone on demand
[23:00] <mbt> Oh, so a milestone is still always required, it will just be automatic soon?
[23:01] <sinzui> mbt: when you create a release, you will select a milestone (which prives the series and code name, etc.). If the milestone does not exit, you can create it at that moment, then continue to add your release notes
[23:01] <mbt> Ahh, alright
[23:01] <sinzui> mbt a release is really just a milestone with release notes and files
[23:11] <RachedTN> I have create a team on launchpad, and now, I wanna to add some blueprints, but I can't find the add bouton like when I  create a project ?
[23:19] <kwah> barry-away, https://bugs.launchpad.net/launchpad/+bug/358788