[00:03] <lifeless> cjohnston: can't be done
[00:03] <cjohnston> What do you mean?
[00:04] <lifeless> we can't convert
[00:04] <cjohnston> Ok.. So it needs to be a new project
[00:04] <lifeless> we can rename a project and make a project group at the old name
[00:04] <lifeless> but we can't convert
[00:04] <cjohnston> Gotcha..
[00:04] <cjohnston> I guess thats what i will need then
[00:04] <lifeless> if you want that done please open a ticket at answers.launchpad.net/launchpad
[00:04]  * mwhudson is going to do a bunch of that today while the rest of the world isn't looking
[00:05] <cjohnston> theres one open
[00:05] <lifeless> we don't expose it in the UI because most folk get confused by project groups
[00:05] <lifeless> mwhudson: win
[00:05] <cjohnston> Is it possible to then delete the project that is already created as it isnt needed
[00:06] <lifeless> we can deactivate it
[00:06] <lifeless> if its got no assets we can delete it
[00:07] <lifeless> (e.g. bugs, branches, links to ubuntu etc)
[00:07] <lifeless> cjohnston: you do realise project groups can't have bugs etc ?
[00:07] <mwhudson> (only for our own projects though, to be clear)
[00:07] <cjohnston> ya.. theres nothing on it..  yes.. we want a "parent" project for all of the different community websites (loco.ubuntu.com, summit.ubuntu.com etc) to group them all together
[00:54] <thumper> lifeless: so you know much about mailing lists in LP and if private teams can have private email lists?
[00:54] <thumper> lifeless: or is it better to go with an internal list?
[00:57] <lifeless> private teams can have private lists
[00:57] <lifeless> you were (probably still are) on at least 2 of those yourself :)
[00:59] <thumper> ok
[00:59] <thumper> how does one get a private team?
[00:59] <lifeless> I *think* its a losa task unless you have a commercial ticket
[00:59]  * thumper relocates
[00:59] <thumper> and enlunchenates
[00:59] <lifeless> e.g. ask a losa ;)
[01:00] <thumper> ack
[01:00] <wgrant> It's a LOSA/commercialadmin task.
[01:00] <wgrant> Even if you have an entitlement.
[01:02] <exarkun> maxb: not the useful response I was hoping for, https://answers.launchpad.net/launchpad/+question/158547
[01:02] <wgrant> Indeed.
[01:02] <wgrant> Let me see.
[01:04] <wgrant> 2011-05-21 20:24:08 INFO    Updating branch scanner status: 2675 revs
[01:04] <wgrant> Fatal Python error: deletion of interned StaticTuple failed
[01:04] <wgrant> Aborted
[01:04] <wgrant> Looks like bzrlib exploded.
[01:07] <wgrant> Oh, no, it's actually a MemoryError.
[01:08] <exarkun> so transient problem that should be detected by launchpad automatically, but meanwhile another commit probably will deal with it?
[01:09] <exarkun> should I file a bug about MemoryError handling?
[01:10] <wgrant> exarkun: A bug would be good. What happened here is that a kernel branch caused the scanner to hit its rlimit, but scan_branches.py didn't notice, so it continued trying to execute more jobs, and yours was next.
[01:12] <lifeless> thumper: please don't be discouraged by my comments about the wiki LEP; wikkid may well be what we need but we need to walk before we run in terms of designing what we /want/ rather than picking what tools we have available
[01:13] <wgrant> exarkun: And yes, a new commit should fix it, or you could request a rescan using the API.
[01:14] <lifeless> thumper: I know you aimed wikkid directly at doing wikis in Launchpad, but AFAICT the customer analysis behind what we should do has never really been done.... and it seems awfully tricky to me.
[01:24] <thumper> lifeless: true...
[01:24] <thumper> lifeless: it seems that geoff is attempting to get stuff into the tree without looking at what is needed too
[01:24] <thumper> lifeless: getting wikkid hooked up isn't that much work
[01:25] <thumper> what is work is getting more functionality into wikkid
[01:25] <lifeless> thumper: if in fact we want a full wiki
[01:25] <lifeless> thumper: which is one of the things that isn't clear to me
[01:25] <thumper> lifeless: true, but what is meant by that?
[01:25] <lifeless> well
[01:25] <lifeless> some folk want document publishing for docs
[01:25] <thumper> lifeless: -> LEP pl
[01:25] <thumper> z
[01:25] <persia> I kinda like the idea of just exposing some bzr tree to the webserver
[01:26] <thumper> lifeless: having that discussion here isn't going to help everyone else looking at it
[01:26] <lifeless> thumper: I've put it in the LEP
[01:26] <thumper> good
[01:26] <thumper> that's the place for it AFAICT
[01:26] <lifeless>  we need jml to look at it
[01:26]  * thumper agrees
[01:27] <lifeless> and I really think getting clarity on the problems we're trying to solve is essential
[01:27] <thumper> lifeless: are you going to kiwipycon?
[01:27] <thumper> lifeless: if so, where are you looking at staying?
[01:27] <lifeless> githubs markdown README thing works very well because its coupled to the branch, so if you have one you have the other
[01:27] <lifeless> thumper: I'm not no, Lynne is due very cloes to then
[01:28] <thumper> ah, good luck with that
[01:28] <lifeless> thanks!
[01:28] <lifeless> 27th aug is the official date, but all sorts of possible complications
[01:29] <lifeless> so missing pyconau & nz
[01:29]  * thumper nods
[01:29]  * thumper heads AFK
[03:53] <AfC> I initiated a new PPA, but rather than uploading packages to it I've just copied in from somewhere else. That didn't trigger a build, so it hasn't generated a GPG key. Is that expected or a bug?
[03:54] <micahg> AfC: are the packages published yet?
[03:59] <lifeless> AfC: whats the PPA
[04:09] <wgrant> AfC: The OpenPGP key will be generated by a cron job after the first source is published.
[04:09] <wgrant> AfC: So that copy should have triggered it.
[04:09] <wgrant> But it can take a while.
[04:09] <lifeless> we should fix
[04:09] <wgrant> Yes.
[04:09] <wgrant> At least by bumping the cronjob higher...
[04:13] <AfC> lifeless: https://launchpad.net/~afcowie/+archive/gnome3
[04:14] <AfC> wgrant: so I did the copy without doing a rebuild. I was wondering if that would end up being a sneak short circuit that would accidentally bypass key generation kickoff.
[04:14] <wgrant> AfC: It has a key now.
[04:14] <AfC> er, oh :)
[04:14] <wgrant> AfC: The generation cron job pretty much just looks for archives without keys but with published sources.
[04:14] <AfC> {sigh} That was bound to be a Murphy's Law thing, wasn't it :/
[04:15] <wgrant> Yay cronjobs.
[04:15] <AfC> wgrant: ok, I see it has a key now. Thanks.
[04:15] <lifeless> wgrant: why don't we just create the key on creation ?
[04:16] <wgrant> lifeless: Lots of people create PPAs but never upload anything.
[04:16] <wgrant> And keys are forever.
[04:16] <AfC> lifeless: if you don't, a "Signing key: pending" (as you have with "package status: pending") would be informative.
[04:17] <wgrant> There are currently more than 15000 PPAs that have never been used.
[04:17] <wgrant> 15000 extra keys would be bad.
[04:18] <lifeless> wgrant: 'meh'
[04:18] <wgrant> lifeless: It's uploading user data somewhere that it can never be removed.
[04:18] <wgrant> Best not to do it if we can avoid it.
[04:18] <lifeless> wgrant: it can be revoked, and its not user data - its lp system data
[04:18] <wgrant> It is in the name of the user.
[04:19] <lifeless> wgrant: thats separate (and contentious in its own right)
[04:20] <AfC> I wonder if/whether/ideally I should be signing said PPA's key with my own, etc. As I understand it when this was all set up some years ago it was all just for general protection, not w-o-t. But still.
[04:20] <AfC> Anyway, not to derail you from talking about more important things. Thanks for your help.
[04:23] <tsimpson> AfC: that would get very complicated very quickly with team PPAs
[04:24] <tsimpson> you do need to sign the source packages to upload, so it's not like it's insecure
[04:26] <wgrant> AfC: WoT is unclear here.
[04:26] <wgrant> AfC: Since you are meant to get the fingerprint over HTTPS from LP.
[04:26] <wgrant> AfC: And if you don't trust LP, you are in trouble.
[04:26] <wgrant> AfC: So the effectiveness of the WoT is questionable.
[04:27] <AfC> tsimpson: yeah, I get that
[06:56] <sepidev>  HELP: bzr: ERROR: Connection error: curl connection error (couldn't connect to host)
[06:57] <henninge> sepidev: what are you trying to do?
[06:58] <sepidev> im trying to login to launchpad
[06:58] <sepidev> Indeed I cannot do anything with launchpad
[06:58] <sepidev> I used to connect to launchpad easily
[06:59] <sepidev> I think after i updated my system it happened to me
[07:00] <sepidev> this is the error message i get:
[07:00] <sepidev> bzr: ERROR: Connection error: curl connection error (couldn't connect to host)
[07:00] <sepidev> on https://launchpad.net/~sepehr.aryani/%2Bsshkeys
[07:02] <spiv> sepidev: he
[07:02] <spiv> sepidev: hi,
[07:02] <spiv> sepidev: which version of bzr?
[07:02] <sepidev> hi, version 2.3.1
[07:03] <spiv> It might perhaps be an HTTP proxy issue, or perhaps pycurl isn't able to validate the SSL certificate for some reason.
[07:03] <sepidev> I uploaded my ssh public key again, but it didnt work
[07:04] <spiv> sepidev: yes, it's not a problem with that.
[07:04] <sepidev> spiv: so what do you think I should do?
[07:05] <spiv> sepidev: bzr is trying to contact launchpad.net via HTTPS, but is failing for some reason
[07:05] <spiv> "couldn't connect to host" suggests that it is probably network related
[07:05] <sepidev> can it result from a firewall or something?
[07:06] <spiv> Like that you need to use a proxy, but bzr for some reason isn't using the proxy you have configured.
[07:06] <sepidev> as far as i know, there is no proxy in between
[07:07] <spiv> You could try passing --no-check to "bzr lp-login" and see if that works, although I expect you'll still have the same trouble if you try to access "lp:" URLs
[07:08] <sepidev> hehehe, yes it worked
[07:08] <sepidev> spiv: how?
[07:09] <spiv> How what?
[07:10] <sepidev> :(, I can login, but how to branch or push or pull something?
[07:10] <StevenK> How were you trying before?
[07:11] <sepidev> StevenK: what?
[07:11] <braiam> branch or push?
[07:12] <braiam> I already test it and is allright
[07:12] <sepidev> i used to do like this: bzr branch lp:some_prj
[07:12] <braiam> but now?
[07:12] <spiv> sepidev: that should still work.  Does it fail for you?  If so, what is the error?
[07:12] <henninge> To add to the confusion: I get this when doing rocketfuel-branch. http://paste.ubuntu.com/611700/
[07:13] <henninge> s/rocketfuel-branch/rocketfuel-get/
[07:13] <sepidev> spiv: am i right?   "bzr branch lp:steadyflow --no-check"
[07:14] <braiam> henninge: you have write permissions?
[07:14] <spiv> sepidev: no
[07:14] <spiv> braiam: no, nor should he need them
[07:14] <sepidev> after I issue this command, bzr says:  "bzr: ERROR: no such option: --no-check"
[07:14] <spiv> sepidev: --no-check is only an option to lp-login,
[07:14] <henninge> braiam: I am not trying to write to the branch. Maybe it's a bug in rocketfuel-get
[07:15] <sepidev> spiv: ok iget this error: bzr: ERROR: Connection error: while sending CONNECT xmlrpc.launchpad.net:443: [Errno 111] Connection refused
[07:15] <spiv> sepidev: I suggested it only for lp-login, as a workaround for lp-login failing to reach launchpad.net via HTTPS in order to check that your account exists and has a plausible SSH public key.
[07:15] <spiv> sepidev: ok, that looks very much like an HTTP proxy issue
[07:16] <spiv> sepidev: perhaps you have an HTTP proxy configured that disallows connecting to HTTPS sites?
[07:16] <spiv> Or perhaps bzr is trying to use an HTTP proxy that doesn't exit
[07:16] <spiv> *exist
[07:16] <sepidev> spiv: how can i make sure that there is an HTTP proxy or bzr using an invalid proxy?
[07:18] <spiv> IIRC bzr typically finds HTTP proxy to use from an environment varible.  Run "export | grep -i proxy"  and see if it find anything likely.
[07:19] <sepidev> this is the result:
[07:19] <sepidev> declare -x http_proxy="http://127.0.0.1:9051"
[07:19] <sepidev> declare -x https_proxy="http://127.0.0.1:9051"
[07:20] <StevenK> Then you have nothing listening on port 9051
[07:20] <StevenK> Which is why you get "Connection refused"
[07:20] <spiv> Ok, so that's the proxy bzr is trying to use.  Does  "netstat -ntlp | grep 9051"  find anything?
[07:21] <spiv> That number is familiar... perhaps you had a tor proxy or something running?
[07:21] <sepidev> nothing
[07:21] <spiv> Anyway, the obvious next steps to fix are either: unset those variables, or make sure that proxy really is running.
[07:23] <sepidev> spiv: yes, I installed tor on my system few weeks ago, ok how do i get rid of this proxies?
[07:26] <spiv> sepidev: I guess you could uninstall tor
[07:28] <spiv> sepidev: you can unset those environment variables in the current shell instance by running "export http_proxy=" and "export https_proxy="
[07:28] <spiv> But really you want to find and fix whatever on your system is setting those in the first place
[07:28] <spiv> Other programs are likely to be affected.
[07:29] <sepidev> ok, uninstalled tor, but the error still exists
[07:32] <sepidev> i disabled the proxy variables, but can you explain how it can affect other applications
[07:32] <sepidev> ?
[07:33] <sepidev> spiv: and now bzr works correctly. you deserve a A big thanks spiv, thaaaaaaaaaaaaaaaaaaaank yoooooou
[07:34] <geser> sepidev: bzr is not the only applications with honours http_proxy
[07:36] <sepidev> geser: hmm?
[07:37] <braiam> sepidev: did you use tor?
[07:37] <braiam> sepidev: sorry
[07:38]  * braiam have to review the back log
[07:42] <spiv> sepidev: any other program that uses HTTP would be likely to be affected.
[07:50] <spiv> henninge: any luck with your issue?
[07:51] <henninge> spiv: the failing command was "bzr update" on a branch bound to lp:lp-source-dependencies.
[07:51] <henninge> (download-cache)
[07:52] <henninge> spiv: I recreated the branch using checkout and now it works fine. But I still have the broken branch here.
[07:52] <spiv> henninge: hmm, rocketfuel-setup and rocketfuel-get are in disagreement
[07:52] <StevenK> They are?
[07:52] <spiv> henninge: -setup makes download-cache a branch of lp:lp-source-dependencies, but -get makes it a checkout.
[07:53] <henninge> oh!
[07:54] <StevenK> That should be fixed
[07:54] <henninge> spiv: but that does not explain the error message AFAICT
[07:54] <spiv> henninge: no, I don't think so either, but it was something odd I noticed while looking :)
[07:54] <henninge> ;)
[07:55] <StevenK> spiv: I can't see where -setup does anything with download-cache
[07:55] <StevenK> spiv: The only time is a comment
[07:56] <spiv> henninge: I guess it'd be good to know what 'bzr info' is for that checkout
[07:56] <StevenK> And lib/devscripts/sourcecode.py makes my eyes bleed
[07:56] <spiv> StevenK: ah yes it is a comment, but still, it's disagreeing with what -get will do.
[07:57] <spiv> Perhaps the comment should just recommend rocketfuel-get?
[07:59] <StevenK> spiv: I think -setup just runs -get after branching devel
[08:01] <spiv> StevenK: hmm, depends on DO_WORKSPACE
[08:01] <spiv> henninge: (and also which bzr version are you using?)
[08:09] <henninge> spiv: Bazaar (bzr) 2.3.3
[08:09] <henninge>   Python interpreter: /usr/bin/python 2.7.1
[08:09] <henninge>   Python standard library: /usr/lib/python2.7
[08:09] <henninge>   Platform: Linux-2.6.38-8-generic-i686-with-Ubuntu-11.04-natty
[08:09] <henninge>   bzrlib: /usr/lib/python2.7/dist-packages/bzrlib
[08:09] <henninge>   Bazaar configuration: /home/henning/.bazaar
[08:09] <henninge>   Bazaar log file: /home/henning/.bzr.log
[08:10] <henninge> spiv: http://paste.ubuntu.com/611718/
[08:12] <StevenK> henninge: Heh, 'dustpuppy' :-)
[08:12] <henninge> ;-)
[08:28] <spiv> henninge: interesting that its parent branch is the same branch as the master branch, but using a different URL
[08:29] <spiv> henninge: possibly that's what is confusing bzr; I'd file a bug.
[08:30] <henninge> spiv: the checkout which created just now does not mention a parent branch at all.
[08:31] <henninge> spiv: sure, I'll file a bug ;)
[09:58] <mmc> I have a PPA. I wonder, if  ... adopting bzr or using some git-bzr bridge (for now I use Git only) and creating a bzr repo on launchpad .... if I could make a "release" by just tagging a commit?
[10:03] <jfi> mmc, you can automaticly create debian packages each day (or on request) and upload them into a ppa
[10:04] <jfi> mmc, https://help.launchpad.net/Packaging/SourceBuilds
[10:04] <mmc> this request is some tag/special commit, and I could have different branches for different distros. and somehow it can be integrated with issue tracker?
[10:08] <lifeless> so you can certainly just push a tag or branch and use that for the release
[10:08] <mmc> for now I cannot even file a bug on my ppa.
[10:08] <mmc> I guess I need a bzr repo for that to be possible.
[10:09] <lifeless> we don't (yet) support making a tarball from a tag in the web ui (but bzr can do this)
[10:09] <lifeless> ppas don't have bugs support
[10:09] <lifeless> projects & distributions do
[10:10] <lifeless> there is some discussion around letting PPAs have bugs filed in them
[10:13] <mmc> lifeless: you mean  bzr on _launchpad_  can do  ... tarball from a tag?  That would be a small step for me. But yes, without bug support, it's very small step.
[10:15] <lifeless> I mean bzr can do tarball from a tag - bzr export foo.tgz -r tag
[10:16] <mmc> lifeless: but I want it done on the  (remote) server, automatically.
[10:16] <lifeless> we don't support it yet; there is a bug open asking for it
[10:17] <mmc> what you say ... I can do it with git as well.   And what I need is  to run the   "git-buildpackage -S && debrelease -S  --debs-dir=../build-area  --dput PPA"  equivalent
[10:17] <zyga> hi, is launchpad offline now?  I got "bzr: ERROR: Invalid http response for https://xmlrpc.launchpad.net/bazaar/: Bad status line received"
[10:22] <lifeless> zyga: no, its up
[10:22] <lifeless> zyga: thats served from the same cluster - but that looks like a known bug in bzr with https proxies
[10:31] <zyga> lifeless, ah, I'm behind some idiotic spanish proxy here, I cannot turn it off
[10:31] <zyga> lifeless, is it a bug in the proxy or in http stack used by python/bzr
[10:35] <lifeless> zyga: IIRC python stdlib not support https/proxies, and there is a workaround in newer bzrs
[10:35] <lifeless> zyga: what bzr version do you have?
[10:39] <zyga> lifeless, I'm on 2.3.1  I'm assuming you're talking about 2.4 beta
[10:39] <ChiThu> hi all
[10:40] <lifeless> zyga: #bzr might have more answers. Perhaps 2.3.4 has the fix, or 2.4 beta
[10:40] <zyga> lifeless, thanks
[10:40] <ChiThu> I need help with broken branches : bzr merge lp:~zkrynicki/abrek/limbs
[10:40] <ChiThu> bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~pwlars/abrek/trunk/".
[10:48] <fagan> I have a request for pad.lv could we have a shorten url for search results
[10:48] <wgrant> poolie: ^^
[10:48] <fagan> The search result urls are really long
[10:50] <fagan> the only reason why im asking is I just saw one that was exceptionally long and I laughed pretty hard
[10:51] <fagan> http://paste.ubuntu.com/611756/ you get the idea
[10:55] <lifeless> fagan: so we should just generate better queries in the first place
[10:55] <lifeless> fagan: just needs some js love for the form
[10:57] <fagan> lifeless: it would be nice since there is the odd time that you need to paste the results
[12:11] <mok0> Vi starter vores Python studiekreds torsdag kl 10 tror jeg nok
[12:12] <mok0> Errr sorry, wrong window
[12:13] <soren> Heh :)
[14:29] <dmart> Hi all, does anyone know whether it's possible to rename a launchpad account?
[14:37] <persia> dmart, It is, but it gets to be very painful if that account has a PPA, branches, etc.  I don't remember the acceptable limit of pain, but if one is beneath that threshold, one files a question at answers.launchpad.net/launchpad
[14:40] <wgrant> dmart: You can rename it yourself at https://launchpad.net/people/+me/+edit unless you have a PPA.
[14:40] <wgrant> If you do have a PPA... well, I'll explain if you do.
[14:42] <persia> Oh, it's working in +edit?  Cool!  I'll have to remember that.
[14:43] <wgrant> persia: It has since like 2005.
[14:43] <wgrant> Only a couple of years ago did it stop working for people with PPAs.
[14:45] <persia> I thought it stopped working for everyone a couple of years ago.  This is me failing to properly interpret backscroll.
[14:46] <wgrant> Heh
[14:49] <StevenK> ... of 3 years
[14:49] <StevenK> That's commitment
[14:49] <StevenK> Of some kind
[14:54] <persia> StevenK, We don't have an oral history: we have a backscroll history.  Documentation is nice, but not currently coherent (for any of the backscroll I follow).  Having missed a couple months recently, I feel completely lost.
[14:56] <dmart> wgrant: I do have a PPA, but it's not much used and could go away
[15:05] <wgrant> dmart: I would suggest that you delete it, then. Give it a few minutes to actually delete it once you hit the button, then you can rename.
[15:11] <dmart> wgrant: ok, thanks.  I may try this at some point, but it's not urgent...
[15:52] <plars> Is someone available who can fix (or tell me how to fix) all the branches I have in LP against a trunk that is now under a new owner?
[15:53] <plars> I was really thinking I had changed the owner long ago, but it just now seems to be affecting us
[15:53] <plars> it seems to be hitting all the branches against lp:abrek
[16:05] <maxb> Ah, this sounds familiar, let me check something quickly
[16:07] <maxb> Right, yes. I can guide you to fixing any branches to which you have write access and need right now, and I will file a request with the admins to get the rest fixed up
[16:08] <maxb> https://answers.launchpad.net/launchpad/+question/158700 is filed
[16:09] <maxb> You may wish to subscribe to the question for notifications
[16:09] <wgrant> The global, permanent fix is in progress, but I guess will be stalled this week as the LOSAs are sprinting.
[16:10] <maxb> urgh
[16:10] <wgrant> Rather.
[16:10] <maxb> The LOSAs should not be allowed to disappear for a week all together :-(
[16:11] <wgrant> 'tis upsetting.
[16:11] <wgrant> Although at least they are near my timezone this time :)
[16:15] <plars> maxb: awesome, thanks
[16:15] <plars> maxb: how do I fix the ones I have write access to?
[16:15] <maxb> You'll need to grab a small script I wrote: http://j.maxb.eu/~maxb/bzr-set-stacked-url
[16:17] <maxb> And then run bzr-set-stacked-url lp:~foo/abrek/foo lp:~linaro-validation/abrek/trunk
[16:22] <plars> thanks a bunch maxb
[16:42] <Laney> does the depwait breaker not work on virtual packages?
[16:42] <Laney> https://launchpad.net/ubuntu/+source/haskell-syb-with-class/0.6.1.1-1/+build/2467144
[16:43] <cjohnston> gary_poster: I just provided more info on my LP Answers Question
[16:43] <cjohnston> :-)
[16:44] <gary_poster> :-) thanks cjohnston, lookin :-)
[16:44] <cjohnston> Thank you
[16:46] <Laney> looks like 335913
[16:51] <gary_poster> cjohnston: done
[16:52] <gary_poster> bug 335913
[16:53] <cjohnston> Thanks gary_poster
[16:53] <gary_poster> np
[16:53] <gary_poster> Laney, you are right, it sounds like that's what you've found.  Does that tell you what you need to know, or should I see if I can find someone with more LP build/package knowledge than I?
[16:54] <Laney> gary_poster: no, that's fine
[16:54] <gary_poster> ok cool
[16:54] <Laney> If you can find someone to fix it then... ;-)
[16:54] <gary_poster> heh
[16:54] <gary_poster> not right now I'm afraid
[16:54] <gary_poster> "Medium" won't be addressed by the Canonical team soon
[16:58] <cjohnston> gary_poster: I'm a little confused.. I went through and added that project to all of the other projects, but only the first oen I did is showing up.
[16:59] <cjohnston> on the front page
[16:59]  * gary_poster looking, cjohnston
[17:04] <gary_poster> sinzui: cjohnston has added project https://launchpad.net/summit to project group https://launchpad.net/community-web-projects , and now bugs are showing up on https://launchpad.net/community-web-projects but the summit project itself is not displaying in the "Projects" heading of that page.  Is that expected, and perhaps something that will fix itself after some kind of async processing?
[17:04] <gary_poster> (...now *summit bugs are showing up...)
[17:09] <sinzui> gary_poster: I think there is a memcache tales tag around that chunk
[17:10] <gary_poster> sinzui, cool, that makes sense.  Thank you
[17:11] <gary_poster> cjohnston: I suspect that part of the page will be updated ...soon....  Meanwhile, you are doing everything right as far as I can tell.
[17:15] <cjohnston> ok.. thanks
[19:09] <cjohnston> gary_poster: If I create a delegated team for the group project that you just created for me, and then add teams to it (each team being the specific group who is responsible for that project) would the members of the team have the access described in "This is a project group-wide appointment. Think carefully here! This person or team will be able to set feature goals and approve bug targeting and backporting for ANY se
[19:11] <cjohnston> Or anyone else who is around
[19:11] <gary_poster> cjohnston, if I understand you, I believe so.  Typically you would want to create a team for the group, and make that team members of the sub groups if you want a direct membership connection.  I'm going to doublecheck with some of the groups I'm a member of...
[19:12] <gary_poster> cjohnston, you are talking about the maintainer?  No...
[19:12] <cjohnston> both driver and maintainer
[19:13] <gary_poster> cjohnston, so, I'm correct that you don't want to do what you said
[19:13] <cjohnston> ok
[19:13] <gary_poster> There are many things you might want
[19:14] <gary_poster> So I'm having a hard time iterating them for you
[19:14] <gary_poster> But if you do what you said, then yes, the members of the subteams would have the super teams powers
[19:15] <cjohnston> ok.. That's what I thought.
[19:15] <gary_poster> FWIW, the groups I'm a member of don't have a group-level driver, and they have a "special" group who is the maintainer
[19:20] <scott-work> the ubuntu studio team is considering cleaning up it's launchpad organization structure which would mean removing a number of teams and/or projects, is there a process or procedure to follow to accomplish this?
[19:20] <scott-work> sorry, i should have introduced myself first...i'm scott lavender, ubuntu studio project lead
[19:24] <cjohnston> ty again gary_poster
[19:26] <gary_poster> np at all cjohnston.  Thanks for https://code.launchpad.net/~chrisjohnston/launchpad/728192/+merge/61046 :-)
[19:28] <cjohnston> Not a problem.. I got quite a few bugs done last sunday.. Good learning.
[19:53] <maxb> scott-work: Teams can be deleted outright. Projects cannot be deleted, but can be deactivated, which hides them from most people. Either way, a request into https://answers.launchpad.net/launchpad/+addquestion is the way to go - preferably from the person who owns the item in question (or member of the owning team)
[19:57] <nicoulaj> Hi, is there a way to create a PPA for a project ? Or PPA are only for users and teams ?
[20:07] <doko> trying to copy a package into a different series in the same ppa, I always get:
[20:07] <doko> The following source cannot be copied:
[20:07] <doko>     binutils 2.21.0.20110523-0ubuntu1 in natty (same version already has published binaries in the destination archive)
[20:07] <doko> any idea why?
[20:08] <doko> the source is not there, and there can't be any binaries
[20:08] <doko> yellow: ^^^
[20:15] <gary_poster> doko, hi.  Let me see if I can find anyone who might know
[20:15] <doko> gary_poster: it's in the ubuntu-toolchain-r/ppa directory
[20:15] <doko> ppa
[20:16] <lifeless> doko: which series are you trying to copy into?
[20:17] <gary_poster> lifeless, heh, I was just about to ping you, thanks
[20:19] <doko> lifeless: to maverick
[20:22] <lifeless> doko: maverick has a newer binutils
[20:22] <lifeless> https://launchpad.net/~ubuntu-toolchain-r/+archive/ppa?field.series_filter=maverick
[20:22] <gary_poster> nicoulaj, only for a team/user to my knowledge.  A typical solution is to create a team specifically for the project.
[20:22] <lifeless> doko: binutils 2.21-3ubuntu1~ppa1
[20:23] <lifeless> doko: or, I just woke up and can't do version comparisons in my head before food :)
[20:23] <nicoulaj> gary_poster: yes, that what I did, thanks. This is not very natural though
[20:23] <doko> lifeless: but I'm trying to copy 2.21.0.20110523-0ubuntu1
[20:25] <gary_poster> nicoulaj, ok.  If you want to pursue that, we could file a bug.  Did it not feel natural because the team was small, and so creating a team felt unnecessary, or for some other reason?
[20:26] <lifeless> there is a bug I think
[20:26] <lifeless> bug 245183
[20:26] <gary_poster> ah ha
[20:26] <gary_poster> cool, thanks lifeless
[20:26] <nicoulaj> gary_poster: It seems to me that binary repositories are more often related to projects than people
[20:26] <lifeless> no worries, just searched for 'ppa project'
[20:27] <gary_poster> :-)
[20:27] <nicoulaj> gary_poster: But may be I'm not getting the launchpad way
[20:27] <nicoulaj> gary_poster: same goes for branches
[20:27] <lifeless> doko: I think you may have found a bug; can you file one please?
[20:28] <doko> lifeless: ok; do you the current status to reproduce, or can I upload to maverick manually?
[20:28] <doko> do need ...
[20:28] <lifeless> doko: I would like to run it past wgrant as-is, he can capture the info
[20:29] <lifeless> doko: that would be in about 4 hours
[20:29] <doko> ok
[20:29] <lifeless> (or stevenk - also gmt+10)
[20:32] <gary_poster> nicoulaj, :-) gotcha.  Doing it by person/team is certainly more flexible, since having a team for the project can model what you want, as well as other approaches, and it's the way other similar services do it as well, AFAIK (github, for instance).  But maybe there's something in bug 245183 that might help with the disconnect?  If so, please add a comment there.
[20:32] <doko> lifeless: bug #787167
[20:34] <nicoulaj> gary_poster: yes, you are right, this is more the real problem.
[20:35] <ikus060> Hey, should I use any tool to change the changlog ??
[20:35] <doko> lifeless: hmm, now I see bug #557647.  but then, why am I offered to copy the sources only to the same PPA?
[21:07] <lifeless> doko: UI bug I would say
[21:07] <lifeless> doko: I'll confirm with wgrant, and if it is that will rephrase to be a bug about the ui
[22:30] <nigelb> Hi, can someone please remove the spam comment from bug 566827
[22:30]  * nigelb pings yellow
[22:30] <nigelb> I wonder if there's a /hilight
[22:30] <lifeless> done
[22:30] <nigelb> thanks lifeless :)
[22:30] <lifeless> thank jcsackett for making it super easy
[22:30] <persia> nigelb, Seems one generally just has to pick the appropriate colour to represent the severity.
[22:31] <nigelb> persia: heh
[22:31] <nigelb> I wonder if there's a red team and blue team
[22:31] <nigelb> hang on, its morning for persia and lifeless.
[22:32] <nigelb> Darn, I really need to sleep.
[22:32] <persia> I haven't seen those.  The worst I ever saw was sev-erity mau-ve
[22:32] <nigelb> Oh, there is a /hilight then :)
[22:34] <alkisg> Hi, is this a correct place to report spam? https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/566845/comments/4
[22:34] <alkisg> "amichair             wrote             18 minutes ago:                                Last year our penny stock picks cashed in over 570% combined!"
[22:35] <jcsackett> alksig: spam is removed.
[22:35] <alkisg> It looks like this user's mail is used for spam, he sent a dozen mails in bug reports in the last 2 minutes
[22:35] <lifeless> nigelb: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/566845/comments/4
[22:36] <nigelb> lifeless: Interesting. Can you block the user temporarily for that?
[22:37] <lifeless> The account "amichair" has been suspended
[22:37] <lifeless> jcsackett: where are the docs for what to do when we suspend someone?
[22:38] <jcsackett> lifeless: https://wiki.canonical.com/Launchpad/DealingWithSpam#Dealing%20with%20spam (internal link, sorry all)
[22:38] <lifeless> thanks
[22:39] <jcsackett> yw.
[22:39] <alkisg> Thanks too :)
[22:39] <jcsackett> saw your comment about flask and packaging btw. bummer.
[22:39] <jcsackett> lifeless ^
[22:39] <jcsackett> yw too, alkisg. :-)