[04:55] <thunderstruck> where is the link to change title in a bug report? I dohnt see a link for it.
[04:56] <Hobbsee> it's called edit description
[04:56] <Hobbsee> use the page search
[04:56] <ScottK> Another victory for the new U/I.
[04:56] <Hobbsee> page search is *very* useful for launchpad, now.
[05:06] <thunderstruck> thanks
[05:31] <thunderstruck> what is the correct name for launchpad ?
[05:31] <jamesh> Launchpad
[05:32] <gnomefreak> ok thats what i did but i shouldnt be able to change status and such but i can
[05:32] <gnomefreak> bug 252137
[05:32] <RAOF> Just to check: I can only get the signed changes file out of my PPA because I've uploaded that package, and am logged in as myself, right?
[05:33] <ScottK> RAOF: Link me and let's see if I can get it.
[05:34] <RAOF> https://edge.launchpad.net/~raof/+archive
[05:34] <RAOF> I'd _hate_ for someone to upload any of those packages to Ubuntu!
[05:34] <ScottK> ;-)
[05:35] <jamesh> RAOF: I don't see the "(changesfile)" links on your PPA, but I see them on mine.
[05:36] <RAOF> Good.  I just got a bit surprised when I checked one of those links and found it was still signed.
[05:37] <ScottK> Same here.
[05:37] <jamesh> it isn't totally secure though
[05:37] <jamesh> the real solution is to not accept the same signed changes file twice
[05:38] <ScottK> Except Ubuntu hasn't accepted those changes files.
[05:38] <jamesh> ScottK: Launchpad has.
[05:39] <jamesh> it is the same build system
[05:39] <RAOF> Can't LP just strip the signature from the changes file?
[05:39] <ScottK> It'd be nice though if the librarian was going to serve up signed .changes files, it'd at least use https.
[05:40] <RAOF> jamesh: Sorry, you mean that someone browsing librarian could grab the signed changes file?
[05:40] <jamesh> RAOF: if they can guess the URL, yes.
[05:40] <RAOF> And by browsing, I mean 'guess the right url'
[05:40] <RAOF> !!!
[05:40] <ScottK> jamesh: True, but I think any linkage between PPA and the official build system is not likely to have a happy ending.
[05:40] <ScottK> RAOF: Happy bug filing.
[05:40] <jamesh> bugs have already been filed.
[05:41] <jamesh> ScottK: there are plans to introduce a more secure upload mechanism
[05:42] <ScottK> RIght.  First release, then go get a design.
[05:42] <jamesh> we can do so much better than anonymous FTP
[05:44] <Hobbsee> RAOF: that bug was filed ages ago.
[05:44] <Hobbsee> RAOF: this is the fixed version.
[05:44] <Hobbsee> the hchanges file used to be blatantly obvious
[05:44] <ScottK> Hobbsee: I'm sure they have 'Top Men' working on it.
[05:44] <Hobbsee> and the LP url is easily guessable.
[05:44] <Hobbsee> ScottK: i'm not.
[05:45] <ScottK> Hobbsee: Did you see the first Indiana Jones movie, "Raiders of the Lost Ark"?
[05:46] <Hobbsee> nope
[05:46] <ScottK> Ah.  You ought to.
[05:46] <RAOF> jamesh: Are you sure there are bugs filed?  There doesn't seem to be anything with the ppa tag against soyez.  That'd be the right target, yes?
[05:47] <ScottK> I guess I'm showing my age, but at one point pretty much everyone would have known that I was saying I doubted much was happening.
[05:47] <jamesh> RAOF: yes
[05:47] <ScottK> On that note, I'm off to bed.
[05:47] <RAOF> ScottK: _I've_ seen Raiders of the Lost Ark, and I did'nt get that :)
[05:48] <ScottK> Ah.
[05:48] <ScottK> RAOF: Remember the scene at the end of the movie ...
[05:48] <RAOF> Um...
[05:48] <RAOF> Which one?
[05:48] <RAOF> The answer may well be "no" :)
[05:49] <RAOF> jamesh: Is this filed as a security bug, which is why I can't seem to find it?
[05:49] <jamesh> yes
[05:50] <RAOF> I'll stop looking, then.
[05:50] <jamesh> bug 159304
[05:55] <RAOF> So, in short, the only thing preventing someone from taking a package from my PPA and making it look like I uploaded that to Ubuntu is that they'd need to first guess a URL?
[05:56] <ScottK> Yes
[05:57] <ScottK> OK.  Two new launchpad bugs filed.  I've done my duty and I'm really going to bed.
[05:58] <RAOF> ScottK: 'night.
[05:59] <Hobbsee> RAOF: they've already been filed.  and closed.
[05:59] <Hobbsee> RAOF: this is why you should be careful what you upload to a ppa.
[05:59]  * Hobbsee has no idea why they can't strip the sigs, either.
[06:00] <RAOF> Why does launchpad even _serve_ the changes files?
[06:01] <Hobbsee> because they're useful, in seeing the changes?
[06:02] <RAOF> But it's the parsed changes file that gets displayed.
[06:03] <Hobbsee> istr that there was information on it not duplicated in the UI
[06:03] <Hobbsee> but maybe that's their solution, and to eventually nuke the changes file.  i'm not sure
[06:38] <mwhudson> hm, i've just been logged out of launchpad
[06:39] <Hobbsee> mwhudson: sacrifice another goat.
[06:40] <Hobbsee> you are behind in your sacrifices, and must rectify this.
[07:00] <stub> That was me sorry. It was either log people out or schedule downtime. Annoying you is more fun, so I chose that option.
[07:02] <mwhudson> stub: hooray
[08:04] <Bowasilu> There aren't dumb questions, right? ;) I registered a project but how can I initially commit my files? The help site seems to jump over this step.
[08:08] <spiv> Bowasilu: have you seen http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html ?
[08:10] <Bowasilu> spiv: Yes. I tried "bzr push bzr+ssh://john.doe@bazaar.launchpad.net/~john.doe/+junk/myproject". But the files were not yet transferred.
[08:11] <spiv> Bowasilu: What output did "bzr push" give you?
[08:12] <spiv> Bowasilu: if this is a new project and new branch, then the process is generally "bzr init; bzr add; bzr commit; bzr push SOME-URL".
[08:13] <Bowasilu> spiv: I will start over, I must have made an error somewhere... I'll report back if I succeed. Thanks for the moment.
[08:14] <spiv> If you e.g. forgot to do "bzr add", then bzr commit will fail because there will be no changes.  If you forget to commit, then bzr push will tell you that there are no revisions to push.  So the messages from bzr should help diagnose what's gone wrong.
[08:16] <Bowasilu> spiv: Great! I think I did not commit. Thanks a lot.
[08:17] <Bowasilu> spiv: Hm. "Pushed up to revision 1.". Shouldn't I see the files online now?
[08:22] <spiv> Bowasilu: yes, you should.  (It can take a minute or maybe two, but it shouldn't take more than that)
[08:22] <spiv> Which branch?
[08:24] <Bowasilu> spiv: You mean the web address of the branch?
[08:24] <spiv> Yeah
[08:25] <Bowasilu> https://code.launchpad.net/~markus-weimar/otrdecoderx/trunk
[08:25] <Bowasilu> I get "No new revisions to push.".
[08:26] <Bowasilu> spiv: So it should be there, right?
[08:26] <spiv> Bowasilu: http://bazaar.launchpad.net/%7Emarkus-weimar/otrdecoderx/trunk/files shows the files
[08:27] <spiv> code.launchpad.net just hasn't caught up yet, which seems unusually slow.
[08:27] <spiv> Also, it confusingly doesn't give a link to the source code browser even though it should know that source has been uploaded.
[08:27]  * spiv files a bug
[08:27] <Bowasilu> spiv: I see. Then I just wait some time.
[08:38] <Bowasilu> That takes a while... :)
[08:39] <spiv> Bowasilu: I'm guessing that something is broken, but the relevant people have all just finished for the day I think.
[08:54] <Bowasilu> spiv: The code has arrived!
[08:55] <Bowasilu> Thanks for saving me an hour to figure out why it does not arrive. :)
[08:58] <spiv> Bowasilu: You're welcome :)
[09:56] <coolbhavi> how to add gpg keys in new launchpad
[09:56] <coolbhavi> ?
[09:59] <ToyKeeper> coolbhavi: From your profile, click "change details" then "GPG keys"
[09:59] <coolbhavi> OK!
[09:59] <ToyKeeper> It used to be a direct link, but now it requires two clicks.  :(
[11:00] <mpt> Gooooooooooooooooooooood morning Launchpadders!
[11:22] <zyx386> hi
[11:22] <zyx386> anyone from translate team?
[11:39] <jmunro> is there a way i can make launchpad rebuild a package in my ppa?
[11:40] <jmunro> i tried just updating the changlog and dputting in the hope that it would rebuild new binaries, however it didnt seem to produce any debs
[11:44] <wgrant> jmunro: That's the right way to do it
[11:45] <wgrant> What gives you the idea that it didn't produce any binaries?
[11:46] <jmunro> oh they just appeared, 25 minutes after the build
[11:46] <jmunro> it said it was fully published etc
[11:46] <jmunro> so i thought there had been a problem
[11:47] <wgrant> That refers to the sources.
[11:47] <wgrant> They will appear within 20 minutes of the build completing.
[12:29] <smarter> hey
[12:29] <smarter> Is there a way to get a "private" PPA for a team yet?
[12:32] <cprov> smarter: Yes. Please, file a question on soyuz mentioning the reason and the team name and we will arrange it for you.
[12:32] <smarter> cprov: thanks, we'll do that
[12:33] <laga> how is it "private"? is it protected by a password?
[12:35]  * Adri2000 re-asks his question that got no answer during the week-end:
[12:36] <Adri2000> is it a known bug that an upload to hardy-backports with LP: #nnnnnn closes the hardy "nominate for release" task?
[12:36] <Adri2000> bug #248081 is an example
[12:36] <wgrant> Adri2000: That's more a bug in Ubuntu workflows than Soyuz.
[12:36] <wgrant> But Soyuz should perhaps adapt to our brokenness.
[12:37] <Adri2000> wgrant: why is it a bug in our workflows?
[12:37] <wgrant> Because one shouldn't be using a strange external project to manage backport requests...
[12:38] <Adri2000> right
[12:39] <wgrant> In my ideal world, each distroseries task would have a pocket assigned, so we could do away with <distroseries>-backports projects.
[12:39] <wgrant> And I could request a security fix in -updates, -security and -backports.
[13:51] <smarter> cprov: if you have some time: [14:48:09] <apachelogger> Riddell: https://answers.launchpad.net/soyuz/+question/40489
[13:52] <wgrant> Huh. So much for open source.
[13:53] <wgrant> Improving collaboration by hiding things.
[13:53] <apachelogger> lol
[13:53] <cprov> smarter: okay, thanks. I will organise it later today.
[13:53] <smarter> thanks
[13:53] <wgrant> apachelogger: No, it's seriously ridiculous...
[13:54] <apachelogger> wgrant: why?
[13:54] <wgrant> Why are pre-releases to be kept secret? That seems against the spirit of open source and testing!
[13:55] <apachelogger> wgrant: because there might be problems in the initial tarballs
[13:55] <wgrant> So we should keep Intrepid under lock and key?
[13:55] <apachelogger> now if we would publish these initial tarballs right away KDE would have to roll .1 instead of just exchanging the tarballs
[13:56] <wgrant> So they reuse version strings!?
[13:56] <apachelogger> no
[13:56] <apachelogger> they pimp their tarballs
[13:56] <wgrant> Are they trying to confuse people to death or something?
[13:56] <apachelogger> well
[13:56] <apachelogger> that is why the tarballs are secret :P
[13:57] <Hobbsee> wgrant: also, it takes a shedload of time to actually build all of it.
[13:57] <Hobbsee> wgrant: and a lot of people whine because their favorite metapackage isn't updated and such
[13:57] <wgrant> Hobbsee: How's this relevant?
[13:58] <apachelogger> wgrant: because they might have to remove kdepim if it is not yet built against a new kdelibs
[13:58] <Hobbsee> wgrant: just saying the reasons they do it.
[13:58] <Hobbsee> also, i'm not sure how much it's tested to be integrated together, before the release.
[13:58] <wgrant> apachelogger: Package managers aren't normally that silly.
[13:58] <Hobbsee> ie, it's libs and everything else 'released' to ktown at the same time
[13:59] <apachelogger> the problem is really that KDE is source distributor
[13:59] <apachelogger> everything has to work on hundreds of distros
[13:59] <wgrant> Same with every other upstream.
[13:59] <apachelogger> and most minor quirks get squashed by packagers within that 1 week binary preparation time
[14:00] <apachelogger> wgrant: no other upstream releases ~80 source distributions at the same time
[14:00] <wgrant> Isn't that what RCs are for?
[14:00] <apachelogger> wgrant: so rcs can be broken?
[14:00] <apachelogger> I guess that would make testers quite pissed
[14:00] <apachelogger> anyway
[14:00] <wgrant> apachelogger: What?
[14:01] <apachelogger> quite off-topic here
[14:01] <Hobbsee> wgrant: most other upstreams don't take so long to build together.
[14:01] <wgrant> RCs are there to find bugs in before the release.
[14:01] <Hobbsee> wgrant: actually upgrading kde takes...a good few days.
[14:01] <wgrant> Rather than releasing a tarball that isn't what it is.
[14:01] <Hobbsee> add extra for buildd handholding.
[14:01] <Hobbsee> and they want it released at the same time.
[14:01] <wgrant> Hobbsee: I don't see why that means it should be hidden, nor how that improves collaboration.
[14:02] <apachelogger> wgrant: #kde-devel
[14:02] <Hobbsee> wgrant: that would be to stop the users being silly, and pulling partial updates.
[14:02] <apachelogger> ask for someone from the release working group
[14:02] <wgrant> Hobbsee: So it's a PPA owner's fault if they upload something to their PPA and some user is crazy enough to dist-upgrade with it?
[14:02] <Hobbsee> wgrant: it's probably synonymous with how launchpad rolls out - all at once.
[14:03] <Hobbsee> and while it should all work together, some bits may not, and it may not have been found on edge/staging.
[14:03] <wgrant> Hobbsee: One can copy fine from a non-private PPA, AFAIK.
[14:03] <Hobbsee> indeed.
[14:03] <apachelogger> wgrant: there are users which suggest other users to use that ppa
[14:03] <apachelogger> these other users don't really know what they are doing and trusting that other user
[14:03] <wgrant> apachelogger: Then those users need to be told to stop it.
[14:04] <apachelogger> which might make them end up with a broken system and them switching back to windows
[14:04] <wgrant> There are many more dangerous PPAs around.
[14:04] <Hobbsee> this entire argument is effectively the same as the one regarding firefox.
[14:04] <Hobbsee> if upstreams are requesting specific, reasonable things - like everything to release at the same time - it's reasonable to do that.
[14:05] <wgrant> apachelogger: Do we make Intrepid private because somebody could break their systems with it? No; we just put up warnings.
[14:05] <Hobbsee> wgrant: i don't think it's a question of fault - more ensuring a good user experience.
[14:05] <Hobbsee> wgrant: people don't read warnings.
[14:05] <wgrant> Hobbsee: Then we need to chmod lots of files on a.u.c very quickly.
[14:05] <Hobbsee> wgrant: why do you think anyone recommending rm -rf / in any of our support channels gets a boot?
[14:06] <wgrant> Hobbsee: What warnings?
[14:06] <Hobbsee> any warnings.
[14:06] <wgrant> Those who advise others to rm -rf / do not put a warning immediately beforehand saying 'Do not do this'
[14:07] <Hobbsee> some do.
[14:07] <apachelogger> wgrant: do you think users who suggest using that pre-release ppa add a warning?
[14:07] <wgrant> apachelogger: If they have a conscience they probably should.
[14:07] <Hobbsee> and there are more dangerous ppas around, yes - however, they don't get thrown around whenever anyone hears about a new release coming around.
[14:08] <Hobbsee> wgrant: if the prospective developers can't follow warnings on launchpad, why would you expect users to?
[14:08] <wgrant> Hobbsee: Hm?
[14:08] <apachelogger> wgrant: everyone should use FLOSS as well
[14:08] <Hobbsee> wgrant: i assume you know just how many people applied to join ubuntu-universe-sponsors, without being MOTUs?
[14:09] <wgrant> Hobbsee: Right. They're not prospective developers.
[14:09] <Hobbsee> no?
[14:09] <Hobbsee> what are they, then?
[14:09] <wgrant> People collecting badges, I suspect.
[14:09] <wgrant> apachelogger: Where did I contradict that?
[14:09] <Hobbsee> sure, but some of them actually have patches to put forward and such.
[14:10] <Hobbsee> and that u-u-s queue looks evil.
[14:10] <wgrant> There are much more dangerous things around than a KDE4 prerelease PPA.
[14:11] <apachelogger> [15:07:49] <Hobbsee> and there are more dangerous ppas around, yes - however, they don't get thrown around whenever anyone hears about a new release coming around.
[14:11] <wgrant> Embargoing security updates is sometimes necessary, but embargoing new upstream versions is more than slightly strange.
[14:13]  * wgrant -> bed.
[14:13] <wgrant> Anyway, although I of course have no standing in the situation, I
[14:13] <wgrant> * I must strongly object, and feel it is against any normal Free Software principles.
[14:14] <apachelogger> the source is free
[14:14] <apachelogger> none stops anyone from fetching the tagged sources
[14:14] <wgrant> No, it's not.
[14:14] <wgrant> What!?
[14:14] <wgrant> So they're secret except not?
[14:15] <apachelogger> http://websvn.kde.org/tags/KDE/4.1.0/
[14:15] <apachelogger> the tarballs are secret
[14:15] <apachelogger> for above started reasons
[14:15] <wgrant> The above stated reasons are completely invalid if the tag is public.
[14:15] <apachelogger> but if someone insists on getting the source before it got a fair amount of testing they might as well do it
[14:15] <wgrant> How does it get a fair amount of testing if it is embargoed?
[14:16] <apachelogger> wgrant: this is not about the code
[14:16] <apachelogger> this is about the buildsystem
[14:16] <apachelogger> and documentation
[14:16] <apachelogger> that all entities work and stuff
[14:21] <cprov> wgrant, apachelogger: Sorry, I'm not paying much attention right now (busy with other things), but AFAICS, the privacy requirement comes from KDE community, a P3A would be just propagating (coping with) it, if we want to argue about making early releases public we should make it at KDE workflow level. Do you both agree ?
[14:21] <wgrant> cprov: Right.
[14:24] <apachelogger> cprov: exactly :)
[14:32] <Adri2000> cprov: should I file the issue I mentioned earlier as a soyuz bug?
[14:33] <TuniX12> hello is there any bazaar channel ?
[14:33] <Hobbsee> TuniX12: #bzr ?
[14:34] <TuniX12> thanks
[14:41] <cprov> Adri2000: well, the upload fixed the bugtask target to the filezilla, not the one targeted to hardy-backports. Is that correct or am I mistaken ?
[14:48] <ScottK> (LP: #NNNNNN) has never worked for backports uploads.  Dunno if that's a feature or a bug.
[14:52] <cprov> ScottK: hard to say, the code only closes sourcepackage tasks (ignoring PPA and -proposed uploads). It doesn't touch distroseries tasks.
[14:54] <ScottK> It seems to me that Soyuz has enough information to know what to close.
[14:57] <cprov> ScottK: quite possible, then it looks like a missing feature. File a bug, I'd say
[14:59] <Adri2000> cprov: the upload was targeted to hardy-backports, so it should close the hardy-backports task and not touch the hardy "nominate for release task" as it did in this case
[14:59] <Adri2000> only -security and -updates uploads should close a "nominate for release" task I think
[15:02] <cprov> Adri2000: as I said, the upload didn't close the distroseries task, Martin did. Do you confirm it ?
[15:04] <Adri2000> I closed the hardy (nominate for release) task as invalid
[15:04] <Adri2000> Martin closed the hardy-backports task as fix released
[15:04] <Adri2000> the upload (launchpad janitor) closed the hardy task as fix released
[15:06] <RainCT> Launchpad (Edge) already asked me twice to log in today.. Is there something wrong?
[15:06] <Hobbsee> RainCT: yeah, they've been messing iwth it.
[15:06] <Hobbsee> RainCT: and, of course, the dual login, if you start with production, is normal.
[15:08] <RainCT> ok, thx
[15:10] <afflux> Is it possible to rename a project to avoid a name conflict? I registered pyotr a while ago and noticed that there seems to be a sourceforge project called pyotr (though it does not seem too popular, as was unable to find it using google).
[15:19] <ScottK> cprov: Bug 252583
[15:19] <kiko> ScottK, heh, that's such a funny bug, we explicitly were asked to not make LP: work for backports because it used to :)
[15:22] <ScottK> kiko: IIRC it closed mainline Ubuntu tasks when uploads to backports were made.  I agree that's wrong.
[15:22] <mthaddon> afflux, just create a question here - https://launchpad.net/launchpad/+addquestion stating what you want it changed from and to
[15:23] <kiko> ScottK, yeah
[15:23] <afflux> mthaddon: ah okay, thank you
[15:23] <mthaddon> sure
[15:54] <dmishd> Hello all.  Wanted to check on the process for getting a new upstream version of mypasswordsafe uploaded for intrepid.  I've packaged it in my ppa, registered it as a bug in launchpad, nominated it for release and subscribed the ubuntu-universe-sponsors.  Did that a few weeks ago and have heard nothing since.  Is that usual or is there something else I should do?
[15:54] <dmishd> The bug url is https://bugs.launchpad.net/ubuntu/+source/mypasswordsafe/+bug/221893
[15:55] <andrea-bs> dmishd: you should ask on #ubuntu-devel for this kind of questions ;-)
[15:55] <dmishd> ah ok, thank you :)
[16:09] <SURFgijs> anybody knows where I can find the code of conduct?
[16:09] <SURFgijs> https://help.launchpad.net/BecomingAnUbuntero
[16:09] <SURFgijs> I think the directions are invalidg
[16:12] <kiko> SURFgijs, on launchpad itself, launchpad.net/codeofconduct/
[16:12] <kiko> iirc
[16:14] <SURFgijs> aaah
[16:14] <SURFgijs> thx
[16:19] <apachelogger> cprov: about the private ppa question - will we be able to copy the packages to a normal ppa? +is there a method for us to "sort the special access"?
[16:20] <cprov> apachelogger: no, copies via the UI will not work either.
[16:22] <apachelogger> cprov: I guess we will have to wait then, this is one of the most important advantages when it comes to actually publishing it ... i.e. not having to rebuild it :)
[16:23] <cprov> apachelogger: right, let the question opened for now, i will build a list of the missing features for you and other interested teams
[16:23] <apachelogger> cprov: ok, thank you
[17:58] <zyx386> jtv, hi
[17:58] <jtv> zyx386: hi
[17:59] <erdalronahi> hi jtv
[17:59] <jtv> erdalronahi: hi
[17:59] <zyx386> we wont some change in our launchpad team?
[17:59] <erdalronahi> Have a look at https://translations.edge.launchpad.net/+groups/wordpress-translators
[18:00] <erdalronahi> there are two Kurdish teams, but only one link
[18:00] <erdalronahi> the second team is for another variant of Kurdish and should link to another team
[18:01] <jtv> Oh, I remember that
[18:01] <erdalronahi> I am just struggling with the new interface to set it up
[18:01] <zyx386> erdalronahi, you must create the kurmanji team first, then nickolay or jtv can switch it :)
[18:01] <jtv> zyx386: actually, it would be bad manners for me to do it, since Nikolay manages it.  :-)
[18:02] <jtv> erdalronahi: zyx386 is right: assuming there is no confusion such as 2 WordPress translation team for the _same_ version of Kurdish, first set up a team to manage the translation, then present it to Nikolay so he can add it.
[18:03] <ApOgEE-> hi all... i'm creating a team on launchpad and request for a mailing list. i just got a reply which says it is declined and I should contact launchpad admin
[18:03] <erdalronahi> ok, just created https://edge.launchpad.net/~wp-ku
[18:03] <jtv> ApOgEE-: let me see if I can find someone who knows about mailing lists.
[18:04] <zyx386> erdalronahi, perfect and send nickolay in wp-polyglots
[18:04] <zyx386> http://lists.automattic.com/mailman/listinfo/wp-polyglots
[18:06] <ApOgEE-> jtv, i got decline reply from Jorge O. Castro says The right place to ask for an Ubuntu mailing list is rt@ubuntu.com. How was that?
[18:07] <ApOgEE-> previously, I clicked on the request mailing-list button
[18:07] <jtv> ApOgEE-: I don't know about Ubuntu, but that sounds like a request tracker.
[18:07] <leonardr> ApOgEE: rt@ubuntu.com is the ticket tracker
[18:08] <erdalronahi> zyx386, I mailed him
[18:08] <ApOgEE-> leonardr, I do it on launchpad
[18:08] <erdalronahi> but not on that list.
[18:08] <jtv> erdalronahi: personal mail should work as well.
[18:09] <jtv> erdalronahi: (unless there is an established process within the WordPress community that I don't know, which is also possible)
[18:09] <ApOgEE-> i did it from here https://edge.launchpad.net/~ubuntu-my-webteam/+mailinglist
[18:09] <jtv> ApOgEE-: maybe the problem has something to do with what the list is for.
[18:10] <erdalronahi> jtv, no there isn't, but I started translating in Launchpad
[18:11] <ApOgEE-> jtv, the page stated The application for this team's mailing list has been declined. Please contact a Launchpad administrator for further assistance.
[18:12] <ApOgEE-> any problems?
[18:12] <jtv> ApOgEE-: I see, this is a LoCo team.  I don't know how Ubuntu mailing lists are set up, but it sounds like there's a special arrangement for setting those up.  You can always try emailing that address.
[18:12] <leonardr> ApOgEE: i think this is the issue: because your project is part of ubuntu, you should talk to the ubuntu maintainers to get a list set up
[18:12] <leonardr> that is, send a request to rt@ubuntu.com to get a task ticket
[18:14] <ApOgEE-> i see...
[18:17] <kiko> leonardr, ApOgEE-: well, hang on a second.
[18:17] <kiko> leonardr, ApOgEE-: would a launchpad mailing list not serve what ApOgEE- is looking for?
[18:17] <kiko> we're happy to host ubuntu mailing lists -- they don't show up under lists.ubuntu.com, but instead are LP mailing lists
[18:18] <leonardr> kiko: i don't see why it wouldn't, but his request was rejected
[18:18] <kiko> but that's usually fine
[18:18] <leonardr> possibly because it wouldn't show up under lists.ubuntu.com
[18:18] <kiko> ApOgEE-, leonardr: the right person to talk to is jcastro
[18:18] <kiko> jcastro, ping?
[18:18] <cody-somerville> The CC said that the community shouldn't use the launchpad mailing lists yet
[18:18] <jcastro> kiko: pong
[18:19] <ApOgEE-> jcastro, told me to ask rt@ubuntu.com instead
[18:19] <kiko> cody-somerville, jcastro: why not?
[18:19] <jcastro> kiko: the CC decided to use lists.ubuntu.com
[18:19] <kiko> why?
[18:19] <jcastro> namespace issues or something I guess.
[18:19] <kiko> it's much harder to manage those lists
[18:19] <kiko> I think the CC should really reconsider that suggestion
[18:20] <kiko> and we can fix whatever issues people are having as long as they don't decide to not use the lists themselves :)
[18:20] <jcastro> kiko: I just decline on LP and approve in RT, I neither made the decision or had anything to do with it. (ie. Don't shoot the messenger!)
[18:20] <cody-somerville> kiko: https://wiki.ubuntu.com/CommunityCouncilAgenda/talk
[18:20] <kiko> jcastro, I'm not shooting you, but I think it's kinda crazy to create more work for IS after having mailing lists actually reimplemented in launchpad to avoid this
[18:20] <kiko> thanks cody-somerville
[18:21] <jcastro> kiko: I agree
[18:21] <jcastro> thanks for that cody-somerville
[18:22] <kiko> it has to do with the lists appearing under lists.ubuntu.com
[18:22] <kiko> I wonder if that's really such a big deal, or if them being linked from lists.ubuntu.com would be good enough
[18:23] <jcastro> kiko: having to manage RT and stuff now, I would say, the sooner someone were to fix the stuff mentioned on that wiki page so I can just approve via launchpad, the better. :)
[18:24] <kiko> jcastro, we need to figure out why lists.ubuntu.com is important. is it just the directory? or something else?
[18:24] <jcastro> kiko: I am not sure, Jono was the poc for all this but he's on holiday
[18:25] <kiko> jcastro, you can fit right in :)
[18:25] <ApOgEE-> jcastro, is that means I can't create mailing lists for my team then?
[18:25] <jcastro> for a LoCo?
[18:26] <jcastro> no, those go under lists.ubuntu.com
[18:27] <ApOgEE-> jcastro, actually we have loCo mailing list but we would like to separate the list just for the web team
[18:28] <ApOgEE-> so it won't mixed up with LoCo mailing lists. can I do that?
[18:30] <jcastro> ApOgEE-: policy right now is only one mailing list per LoCo.
[18:32] <ApOgEE-> jcastro, I see... even on launchpad mailing lists?
[18:32] <jcastro> not really, but they don't want ubuntu mailing lists on launchpad to begin with
[18:33] <jcastro> at this point I think discussing this with the CC at the next meeting would probably help iron all this out
[18:35] <ApOgEE-> If that so, I'll just use groups.google.com then
[18:42] <jcastro> ApOgEE-: kiko: I'll attend the CC meeting on the 5th and see if we can't get some clarification on this
[18:42] <jcastro> because the current situation is just as bad if people end up going to freelists/google groups, etc.
[18:42] <kiko> cool
[18:44] <RichW> Ive uploaded my package to the PPA, when will it appear? - Heres my results: https://launchpad.net/~richies/+archive
[18:44] <RichW> My username is richies
[18:45] <kiko> soon.
[18:45] <kiko> (unless you forgot to GPG-sign it)
[18:46] <RichW> Never mind i have results in email
[18:47] <cprov> RichW: good.
[18:49] <ApOgEE-> thanks jcastro , kiko
[18:50] <kiko> cool
[18:54] <RichW> It rejected it and now ive made some changes to my files, dput says its "Already uploaded to ppa.launchpad.net" and wont let me upload it again.
[18:55] <RichW> Hmm maybe i have to rebuild it.
[18:56] <afflux> RichW: dput -f will do the trick
[18:58] <RichW> thanks afflux, that helped.
[19:48] <RichW> My ppa package is building on intrepid when it is uploaded, how do i make it build on hardy?
[19:49] <beuno> RichW, you have to re-upload and target hardy instead
[19:50] <beuno> there is a copy package feature, but it has never worked properly for me  (I'm probably using ir wrong somehow)
[19:50] <kiko> beuno, can't he copy the package?
[19:50] <kiko> beuno, it should work, and cprov can definitely explain if it doesn't
[19:50] <kiko> he's been doing lots of work on that
[19:51] <beuno> kiko, the 3 times I've done it, none of the copied packaged worked (mostly when I did bzr uploads and some bzr plugins)
[19:51] <beuno> had to re-upload all of em
[19:51] <beuno> but of course, I may of done something wrong  :)
[19:51] <RichW> im trying copy
[19:52] <beuno> RichW, I *think* they have to have the same dependencies (and versions) to be able to copy them. kiko is that correct?
[19:52] <kiko> beuno, i.e. they copied across but were uninstallable?
[19:52] <beuno> kiko, yeap. Due to dependency issues
[19:53] <beuno> it asked for versions of packages that weren't in that release
[19:53] <RichW> my package didnt build on intrepid due to dependency issues so im copying it to hardy
[19:53] <beuno> which makes sense if you think about it, although I'm sure you guys are smarter than that
[19:54] <kiko> beuno, so you depended on specific versions?
[19:55] <beuno> kiko, nope, just seems it gets built that way
[19:55] <kiko> no...
[19:55] <beuno> build-depends?  maybe it's something with the bzr packaging
[19:56] <beuno> or, again, me doing it wrong
[19:57] <geser> beuno: it's not a good idea to copy packages "downwards" (from intrepid to hardy) as the package will still have the dependencies from the intrepid build
[19:58] <beuno> geser, ah!  now *that* makes sense
[19:58] <beuno> it's exactly what I did
[19:58] <geser> beuno: when you copy package they won't get rebuild
[19:59] <kiko> geser, well, you can copy source only
[19:59] <kiko> I personally think that copying binaries across in PPAs is kinda crazy
[19:59] <kiko> it only really makes sense when copying between pockets
[20:00] <beuno> maybe the help should be expanded a bit: https://help.launchpad.net/PPAQuickStart#Copying%20packages
[20:00] <beuno> it didn't make sense to me either, but poolie told me he had done it before succesfuly, so I blindly went on with it
[20:01] <geser> kiko: how should that work (copy just source) as the build debs will have the same file names as the ones from the other distribution?
[20:02] <beuno> RichW, with the information above, I'd say you just re-upload to Hardy instead  :)
[20:03] <geser> and a different revision than the upload to intrepid
[20:03] <RichW> beuno: I looked at the build farm, its compiling :D
[20:04] <RichW> https://launchpad.net/+builds
[20:04] <cprov> then if it works (builds) you can safely copy source & binary "upwards" (to intrepid)
[20:04] <RichW> Launchpad is amazing, must be thousands of lines of code and alot of hard word in it.
[20:04] <RichW> Very clever scripting.
[20:08] <kiko> RichW, thanks! it's indeed many KLOC, and these engineers keep adding on more!
[20:09] <kiko> mtaylor, ping?
[20:10] <radix> Is there a bzr plugin for associating a branch with a ticket? Or some other automated way to register a branch with a ticket?
[20:10] <kiko> radix, do you mean a bug? bzr --fixes
[20:11] <radix> yes, bug, thanks
[20:11] <radix> kiko: oh cool, so if you commit a change with a --fixes and push it to LP it'll automatically be linked?
[20:12] <kiko> radix, I /think/ so. abentley knows more than me though :)
[20:12]  * beuno thinks "not yet"
[20:12]  * beuno searches for the bug
[20:14] <beuno> seems you can!    https://bugs.launchpad.net/launchpad-bazaar/+bug/246166/comments/1
[20:14] <kiko> tolja!
[20:14] <beuno> you guys just don't keep still, do you...
[20:14] <beuno> I can't keep up!
[20:15] <kiko> we try hard to make it hard!
[20:16] <RichW> wow dell has a ppa?!?!
[20:17] <RichW> https://launchpad.net/~dell-team
[20:28] <kiko> warren, ping?
[20:47] <jordi> hello
[20:47] <jordi> http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1121
[20:48] <jordi> can I get a real unidiff from here?
[20:48] <jordi> or a quick command line that would extract it?
[20:49] <beuno> jordi, apart from the "unified diff" option on top?
[20:50] <jordi> beuno: try it
[20:51] <jordi> I want something I can feed to patch
[20:51] <beuno> jordi, bzr diff http://bazaar.launchpad.net/~mailman-coders/mailman/2.1 -r 1120..1121
[20:51] <beuno> that would be better for a patch then
[20:54] <jordi> beuno: fantastic
[20:54] <jordi> thanks
[20:55] <beuno> jordi, welcome'
[21:08] <mtaylor> kiko: pong
[21:08] <kiko> mtaylor, hey there. there is indeed an issue with mailing lists, which francis has a fix for and which should be deployed in the next hours
[21:09] <mtaylor> kiko: awesome!
[21:09] <mtaylor> thanks
[21:09] <kiko> mtaylor, thanks for pointing this out, it was hard to notice
[21:09] <mtaylor> kiko: well, lucky for us, we have vocal devs :)
[21:09] <kiko> heh
[21:13] <radix> beuno: oh, thanks for the pointer (sorry, got distracted)
[23:06] <mtaylor> kiko-fud: fwiw... now a person who _was_ getting list emails is no longer getting list emails...
[23:07] <kiko-fud> mtaylor, yeah, known problem but the fix is bring processed as we speak!
[23:08] <mtaylor> k
[23:08] <mtaylor> just double checking :)
[23:08] <kiko-fud> mtaylor, pity we didn't manage to say hi to each other, but I enjoyed your panel on organic software last friday
[23:08] <mtaylor> kiko-fud: wasn't me... but thanks!
[23:08] <mtaylor> kiko-fud: I, funny enough, as in Brazil :)
[23:09] <kiko-fud> mtaylor, really? I could have sworn..
[23:09] <kiko-fud> mtaylor, we're near misses then. when do you come back?
[23:09] <mtaylor> kiko-fud: not sure... possibly october
[23:10] <kiko-fud> mtaylor, gar, indeed, it was brian aker who presented. heh
[23:10] <mtaylor> well... there are worse people to confuse me with :)
[23:11] <kiko-fud> mtaylor, do you spend the weekends there when you go?
[23:11] <kiko-fud> mtaylor, I was confused because he mentioned launchpad and I said hmmm
[23:11] <mtaylor> we've got him hooked on the kool-aid
[23:11] <kiko-fud> heh
[23:12] <mtaylor> kiko-fud: I spend the weekends sometimes... normally I come down for 2 weeks at a time and do the inside weekend
[23:12] <mtaylor> but this last time I was just in rio for 4 days
[23:12] <kiko-fud> mtaylor, well, when you do come and have a weekend let me know and you can come visit
[23:13] <mtaylor> kiko-fud: I will!
[23:14] <kiko-fud> mtaylor, I live about 3h out of são paulo but the bus ride is easy and it's fun up here -- and quieter
[23:14] <mtaylor> kiko-fud: what? quieter than São paulo? never!
[23:14] <kiko-fud> heh