=== RainCT_ is now known as RainCT
=== fta_ is now known as fta
[09:57] <philn> hi
[09:58] <philn> i'd like to associate my GPG key with another account, so i deactivated it in my settings and tried to activate it in the new account.. but launchpad tells me it has already been imported
[10:22] <siretart> gmb: does the launchpad bugzilla plugin automatically import upstream bugs to launchpad?
[10:23] <siretart> gmb: or phrased differently, now that xine-lib has the lp plugin installed, what has changed now?
[10:29] <gmb> siretart: Launchpad should automatically use the plugin API to import bug statuses and comments from the xine-lib bugzilla. However, to be sure that it is doing so we'll reset the bug watches and then run the bug watch checker against that bugtracker specifically.
[10:29] <gmb> At the moment importing bugs isn't enabled.
[10:30] <gmb> Since we need to be sure that syncing comments works properly before we enable full bug imports.
[10:47] <wgrant> Why are branches enveloped to all changes?
[10:48] <wgrant> Er, people enveloped to all changes on branches.
[10:48] <wgrant> Is it one of those rare instances of questionable rebus on Launchpad?
[10:52] <jamesh> rebus?
[10:56] <wgrant> http://en.wikipedia.org/wiki/Rebus
[10:56] <wgrant> jamesh: ^^
[10:57] <jamesh> wgrant: I still have no idea what you're talking about
[10:58] <wgrant> The portlet on https://code.edge.launchpad.net/~fta/apport/apport/+merge/758
[10:59] <wgrant> These are strange times. One can unambiguously say portlet.
[10:59] <jamesh> okay.  That makes more sense.  It wasn't clear what you were talking about
[10:59] <jamesh> what page
[10:59] <wgrant> Sorry.
[11:00] <jamesh> It could probably do without the icon completely.
[11:01] <wgrant> It was meant to be added, but I don't think that's the right place.
[11:01] <wgrant> Let me find the bug...
[11:01] <wgrant> Bug #256546
[11:01] <ubottu> Launchpad bug 256546 in launchpad-bazaar "Branch subscribers and owner have annoying green ticks next to them" [Medium,Triaged] https://launchpad.net/bugs/256546
[11:02] <wgrant> Hm, maybe it was just a coincidence, as that bug isn't assigned.
[11:15] <siretart> gmb: ah, so that means that I 'just' have to identify and maintain cross bugtracker links manually, but launchpad will sync comments autmatically between the bugtrackers, is that correct?
[11:17] <gmb> siretart: At the moment, someone has to create a bug watch in Launchpad for Launchpad to be able to do any communicating with the remote bug tracker. Once the bug watch is added, though, comment syncing should start automatically. The idea is that we bring this functionality in slowly so as to a) make sure that it works right on our end, b) make sure it works right on your end and - most importantly - c) make sure that it's working as effici
[11:18] <gmb> Launchpad should also, as of the next release, start telling remote bug trackers which bug on Launchpad links to which bug on that tracker.
[11:25]  * NCommander is away: This creature sleeps beyond the reaches of time itself
[11:25] <siretart> gmb: ah, I see. thanks!
[11:25] <gmb> np
[11:28] <philn> are there any issues with PPA? I uploaded a package but it doesn't appear on the PPA and i got no mail notification
[11:28] <wgrant> philn: How long have you been waiting?
[11:28] <bigjools> what he said
[11:29] <Hobbsee> philn: did you sign the package, with a key that's in launchpad?
[11:29] <philn> an hour or so
[11:29] <philn> Hobbsee: yes
[11:29] <wgrant> Oh, a Soyuz dev. This is good.
[11:29] <bigjools>  /o\
[11:29] <wgrant> I suspect that seeing the .changes may be of some utility.
[11:29] <bigjools> philn: which PPA did you upload to?
[11:30] <philn> ~elisa-developers package elisa-plugins-bad
[11:30] <bigjools> thanks, give me some time to go log hunting
[11:32] <philn> uploader was elisa-packager
[11:55] <philn> bigjools: i just did a new upload
[11:55] <elmo> 2008-09-01 09:45:08 ERROR   Unhandled exception from processing an upload -> http://launchpadlibrarian.net/17201984/hcV05rRmPW7aemY7u2CUW4vYgFe.txt (File elisa-plugins-bad_0.5.5-1ubuntu1~pp
[11:55] <elmo> philn: ^--
[11:55] <elmo> a2_source.changes is signed with a deactivated key 153061DE)
[11:56] <philn> ok, got a mail this time ;)
[11:56] <bigjools> thanks elmo
[11:57] <philn> latest upload failed because uploader is not an ubuntero
=== thekorn_ is now known as thekorn
[12:40] <asac> mpt: i have a project on launchpad and now i want to make a release (not really a series). how do i do that?
[12:40] <asac> mpt: the peculiarity here is that the release is a tag-branch in bzr
[12:40] <wgrant> Releases are within a series.
[12:40] <asac> wgrant: let me check
[12:41] <asac> wgrant: "Add milestone" ?
[12:41] <mpt> asac, I don't really know
[12:41] <mpt> asac, but as wgrant says, I think you first need to make a series
[12:42] <mpt> then go into that series, and I think you'll find something for registering a release
[12:42] <asac> ok. i have a series: trunk ... now making a release would be like specifying which revision that is ;) ... but that doesnt exist
[12:42] <asac> oh yeah
[12:42] <asac> "register a release ";)
[12:42] <wgrant> That's likely what you want.
[12:42] <asac> lets see what happens next
[12:42] <wgrant> Much magic.
[12:43] <asac> either there is no way to link a revision or branch ... or that comes after i registered it
[12:43] <wgrant> Branches are linked to series.
[12:43] <asac> true. but what i want to do is to provide a tag or revision of a branch when making a release
[12:44] <wgrant> It may make sense for a release to be able to specify a tag.
[12:44] <asac> apparently thats not supported (yet)
[12:44] <wgrant> But I don't believe that functionality to be currently implemented.
[12:44] <asac> wgrant: well ... branches make sense too
[12:44] <wgrant> No, a series has a branch.
[12:44] <asac> personal preference might be ignorable
[12:44] <wgrant> A release should not.
[12:44] <wgrant> That fails to make sense.
[12:44] <asac> wgrant: theory and praxis diverge here ;)
[12:44] <asac> we have to cover a big use-caase:
[12:44] <wgrant> Why would one want a branch for something that will never change?
[12:44] <asac> http://bzr-mirror.gnome.org/
[12:45] <asac> http://bzr-mirror.gnome.org/ghex/tags/
[12:45] <asac> i mirror my branch for trunk development.
[12:45] <asac> but when i want to plumber a package for release i want to use the tag ;)
[12:46] <asac> thats why i hoped for that launchpad has a syntax like: lp:network-manager/release/0.0.2
[12:46] <wgrant> Tags are not branches...
[12:46] <lifeless> tags make sense for releases though
[12:46] <wgrant> They do.
[12:46] <asac> which would give me a branch of a release i have registered
[12:46] <asac> either tag
[12:46] <asac> or a "release" branch
[12:46] <asac> wgrant: i dont see any option to specify a bzr thing for release here
[12:46] <asac> neither tag, nor revision nor branch
[12:46] <wgrant> I don't believe there is one.
[12:47] <wgrant> Branch doesn't make sense.
[12:47] <wgrant> Tag or revision do.
[12:47] <asac> branch makes sense too ... for practical reasons
[12:47] <wgrant> But none seem to be options now.
[12:47] <lifeless> asac: in the lp model, branch == series, release == tarball
[12:47] <asac> like svn mirrors
[12:47] <asac> lifeless: true. thats fine, but that could be better integrated imo
[12:47] <wgrant> SVN tags don't make sense.
[12:47] <lifeless> asac: releases as revisions is in the datamodel, no UI for it
[12:47] <asac> like i want to bake a releas in launchpad ... i specify a tag or revision and then the tarball gets produced ;)
[12:47] <lifeless> asac: and tags are just revisions
[12:47] <asac> ok
[12:48] <lifeless> asac: I asked for that specific feature, kiko says no for now :(
[12:48] <lifeless> asac: but nag kiko - more voices more chance
[12:48] <asac> lifeless: too bad. would have helped me to easily do package releases
[12:49] <asac> i track packaging based on trunk by regularly merging
[12:49] <asac> and for releasee do a merge from the "release branch/tag/revision" ... whatever
[12:49] <asac> lifeless: ok thanks
[12:49] <asac> lifeless: you know if there is a bug for that?
[12:49] <lifeless> asac: no, I don't know
[12:50] <asac> ok ... i go directly to him then by next chance
[12:50] <lifeless> as far as using urls to svn; they map to bzr tags, so a bzr tag (actually revision is needed for immutability) is fine
[12:51] <asac> lifeless: they map to bzr tags?
[12:51] <asac> lifeless: i am looking at bzr-mirror.gnome.org
[12:52] <asac> hmm ... how can i list tags ;)
[12:52] <lifeless> bzr tags URL
[12:53] <asac> ah ;)
[12:53] <asac> i looked for bzr tag -l ;)
[12:53] <lifeless> why? :)
[12:53] <asac> lifeless: not sure where this idea comes from
[12:53] <asac> maybe git?
[12:53] <asac> ok that really works
[12:53] <asac> fine
[12:54] <asac> now i just need the feature to model a bzr release in launchapd ;)
[12:55] <asac> lifeless: bzr tags <empty> works ... but remove urls dont work here
[12:55] <asac> bzr tags http://bzr-mirror.gnome.org/libmbca/trunk/
[12:55] <asac> bzr: ERROR: extra argument to command tags: http://bzr-mirror.gnome.org/libmbca/trunk/
[12:55] <asac> ok ... there is no <URL> argument in help
[12:56] <asac> would make sense as a feature i think
[13:00] <lifeless> oh
[13:00] <lifeless> right, add that then :P
[13:00] <lifeless> as a bug
[13:15] <gour> LP admins are mostly over the pond?
[13:15] <No`> howdy launchpadders
[13:16] <No`> maybe it's a silly question: is there any way to automatically pull *every* branch linked to a project?
[13:16] <No`> let me explain
[13:16] <No`> I'm following a project, for example gwibber
[13:17] <No`> I can pull trunk, but it happens that the bleeding edge of gwibber might be in gwibber-experimental-stuff
[13:17] <No`> without browsing code.launchpad.net/gwibber, I am not informed that a new branch has appeared
[13:17] <No`> or, another way to put this: could it be possible to get notified whenever a new branch appears in a project?
[13:23] <jpds> No`: If you're on Ubuntu you can install the ubuntu-dev-tools package which has a script which does just that.
[13:23] <jpds> No`: bzr branch lp:ubuntu-dev-tools
[13:25] <jpds> No`: Forget that, I just remembered that get-branches only does teams, not projects.
[13:30] <No`> jpds: ah... Anyway, I think I have a solution... using the RSS feeds. It looks like you can have an RSS item every time a new revision has been pushed
[13:30] <No`> it's not precisely what I wanted, but that's a start
=== asac_ is now known as asac
=== mrevell is now known as mrevell-lunch
=== damoxc is now known as darkcharizard
=== darkcharizard is now known as damoxc
[14:08] <salgado> andrea-bs, ping (re: bug 263320)
[14:08] <ubottu> Launchpad bug 263320 in launchpad "Team admins aren't warned when a membership expires" [Undecided,Incomplete] https://launchpad.net/bugs/263320
[14:08] <andrea-bs> salgado: pong
[14:09] <salgado> hi andrea-bs.  I wanted to ask you a couple more questions about that bug and I figured asking them here would be quicker...
=== damoxc is now known as pikachu
=== pikachu is now known as damoxc
[14:10] <andrea-bs> salgado: great, thanks
[14:10] <salgado> andrea-bs, what was the expiration date you used?  and where do you see the membership listed as 'Expired 12h ago'?
[14:11] <andrea-bs> salgado: I've used 2008-09-01 (today) and here's the team: https://edge.launchpad.net/~beeseek-artists/+members
[14:12] <salgado> ah, I see.  it says that it expired 13h ago but the status is Approved
[14:12] <salgado> that's rather confusing
[14:13] <andrea-bs> salgado: yep, I assume that's because members are deleted daily
[14:14] <salgado> that's correct
[14:14] <salgado> we shouldn't say it 'Expires 13h ago' as that suggests it's expired already
[14:14]  * salgado files a bug
[14:15] <salgado> now we just need to wait until the script actually flags that membership as expired to see if a notification is sent
[14:16] <andrea-bs> salgado: can you run the script now?
[14:16] <salgado> andrea-bs, I can't, no
[14:17] <andrea-bs> salgado: no problem
[14:26] <gour> what is the usual admin-response-time for tasks such as creating project-group?
[14:28] <Hobbsee> gour: depends on if the stars align.
[14:29] <gour> Hobbsee: huh, then i'm in trouble :-D
[14:29] <Hobbsee> gour: if your question expires, then you can just reopen it a few times, until they get to it.
[14:29] <Hobbsee> gour: i've not done some stats on the invalid-no-response ones in a few months now.
[14:29] <gour> Hobbsee: cool. so it means one can expect to solve it during this lifetime
[14:30] <Hobbsee> it may be considerably faster.  but yes, unless you die tomorrow, or this week, it should definetly be done in this lifetime :P
[14:30] <gour> lol
[14:31] <gour> btw, there are quite a few requests for creating project-group. it would be nice to have some FAQ that it's not possible to 'upgrade' project to project-group and it will save some time for LP-admins
[15:00] <andrea-bs> gour: I've submitted bug #263630
[15:00] <ubottu> Launchpad bug 263630 in launchpad-documentation "FAQs doesn't say that project groups are created from scratch" [Undecided,New] https://launchpad.net/bugs/263630
=== mrevell-lunch is now known as mrevell
[15:09] <No`> mrevell: howdy, master revell
[15:10] <mrevell> hello No`!
[15:10] <mrevell> No`: Thanks for your email. I've been away, which is why I haven't replied yet.
=== thekorn_ is now known as thekorn
[15:11] <No`> mrevell: no problem, mate
[15:11] <No`> it was your request, not mine
[15:11] <No`> ;)
[16:01] <gour> nice addition to FAQ by andrea-bs...
=== emgent is now known as emgent`NL
[16:13] <gour> i'm not clear why the step "1. create the sub-projects you need;" is required when it is stated later that "Once your group has been created, you'll be able to link more sub-projects by yourself." or it means at least ONE sub-project is required?
[16:14] <gour> ...according to https://help.launchpad.net/FAQ/Draft1#How do I create a project group?
[16:21] <No`> you may be interested by: http://jehaisleprintemps.net/blog/en/2008/09/01/things-i-know-about-launchpad/
[16:22] <No`> (self pimping, but I wanted to write that for ages)
[16:22] <No`> and it's on topic :p
[16:28] <gour> No`: nice post ;)
[16:30] <gour> No`: do you recommend the same when the project(group) is split into several sub-projects?
[16:37] <gour> andrea-bs: nice add-on to FAQ?
[16:38] <andrea-bs> thanks gour
[16:38] <exarkun> When I run 'bzr pull', it says to run 'bzr upgrade' for better performance, but the repository is on launchpad, how can I upgrade it?
[16:38] <exarkun> or will launchpad automatically upgrade it eventually?
[16:39] <andrea-bs> exarkun: there are two ways: you can upgrade via sftp or you can upgrade your local branch and then push it
[16:39] <gour> andrea-bs: one question - http://rafb.net/p/s3zR9z90.html ?
[16:41] <andrea-bs> gour: actually I don't know... I've put this because admins always ask for the subprojects to be linked :)
[16:41] <andrea-bs> gour: I think that at least one subproject is needed
=== matsubara is now known as matsubara-lunch
[16:43] <Adri2000> No`: you know that you don't need to be in the "bugsquad" team of a project to follow its bug reports?
[16:43] <gour> andrea-bs: hmm, ok. then i'm better creating one 'cause the present one will be rm-ed after project-group is created
[16:44] <andrea-bs> gour: actually you can rename the present project
[16:44] <andrea-bs> gour: I'll make this clearer ;)
[16:45] <gour> andrea-bs: thanks
[16:45] <No`> gour: dunno, I've never been in a project big enough to need it
[16:45] <No`> Adri2000: you mean "every bug of the project"?
[16:46] <Adri2000> yes
[16:46] <No`> ah didn't know
[16:46] <Adri2000> you don't need to be the "bug supervisor" contact or in the team being the "bug supervisor"
[16:46] <No`> where's it hidden?
[16:46] <Adri2000> you can just "subscribe to bug mail"
[16:46] <Adri2000> bugs.lp.net/<project>
[16:46] <gour> Adri2000: good to know - no need fo *-bug team
[16:47] <andrea-bs> gour: I've tried on staging.launchpad.net and I saw that project groups can also have no subprojects
[16:49] <gour> andrea-bs: thank you. i'll try to rename present project to new sub-project to save same admin :-)
[16:50] <andrea-bs> gour: sorry, but you can't rename a project without the help of an admin
[16:51] <gour> andrea-bs: yeah, i see now :-(
[16:52] <No`> Adri2000: nice. changing blog post right now
[16:53] <gour> andrea-bs: some (un)necessary complications
[16:55] <andrea-bs> gour: is it ok for you now? https://help.launchpad.net/FAQ/Draft1#How%20do%20I%20create%20a%20project%20group?
[16:57] <gour> andrea-bs: yeah. it's ok. it would be nice if i'd know it earlier
[16:57] <gour> andrea-bs: does the same apply to teams as well?
[16:57] <gour> i.e. can one rename the team without admin?
[16:57] <andrea-bs> gour: let me check
[16:58] <andrea-bs> gour: you can rename it by yourself only if the team doesn't have a mailing list
[16:59] <gour> andrea-bs: cool. it's good that i did some upfront thinking :-)
[17:05] <gour> andrea-bs: what could be the reason for "The name 'bvj-admin' has been blocked by the Launchpad administrators" ?
[17:05] <andrea-bs> gour: I don't know... you should ask an admin
[17:08] <ara> hello, all, I have a quick question. is there a way to set someone as the bug supervisor for an ubuntu package?
[17:08] <Adri2000> gour: you're trying to register that name?
[17:09] <Adri2000> ara: bug supervisor no, but bug subscriber yes
[17:09] <ara> Adri2000: thanks :)
[17:09] <gour> Adri2000: team
[17:10] <Adri2000> gour: probably all *-admin are blocked
[17:10] <gour> Adri2000: hmm, then No`s post is meaningless :-)
[17:13] <salgado> gour, all names which end in '-admin' are blocked
[17:14] <gour> salgado: i see. thanks
[17:14] <salgado> reserved, actually
[17:14] <gour> heh, same for end-users ;)
[17:14] <Adri2000> salgado: that doesn't apply for already registered teams/users it seems?
[17:16] <salgado> Adri2000, it doesn't seem to
[17:20] <Adri2000> salgado: btw is it intended that searching people/teams for "-whatever" actually shows all people/teams? I guess that's what happened but can't reproduce now as it's always timeouting
[17:20] <Adri2000> (edge)
[17:25] <salgado> Adri2000, that's because '-foo' is interpreted as "all names not containing foo"
=== salgado is now known as salgado-lunch
[17:31] <Adri2000> salgado-lunch: but I'd say it's the a bug that it tries to show everything - anyway, how can I search for "-foo" then?
=== matsubara-lunch is now known as matsubara
=== salgado-lunch is now known as salgado
[19:05] <joaopinto> Hello, how do I ask for a project removal ? I am the Maintainer
[19:07] <jpds> joaopinto: You could file a question for it at: https://answers.launchpad.net/launchpad/+addquestion
=== _neversfelde is now known as neversfelde
[20:31] <mdke> 4~/win 13
[20:31] <mdke> gah
=== kiko is now known as kiko-afk
=== salgado is now known as salgado-afk
[21:55] <Kaivalagi> hi all
[21:56] <mwhudson> hello
[21:56] <Kaivalagi> I have a couple of questions about PPA's on launchpad
[21:57] <Kaivalagi> feeds - would it be possible to have an rss feed for PPA's similar to what is available for code revisions? I would like to publish my PPA's version release info onto my site...
[21:59] <Kaivalagi> displaying the changelog along with the package would be really useful
[22:00] <mwhudson> that sounds like it should be possible
[22:00] <mwhudson> file/look for a bug report?
[22:00]  * mwhudson is not a PPA person
[22:00] <beuno> bigjools, ^
[22:01]  * bigjools is close to going to bed, however
[22:01] <bigjools> we're not planning on doing that sort of thing but feel free to file a bug
[22:02] <Kaivalagi> okay I'll log a bug for it
[22:02] <beuno> bigjools, g'nigh bigjools
[22:02] <bigjools> Kaivalagi: thanks
[22:02] <bigjools> beuno: and thanks :)
[22:04] <Kaivalagi> the other question was more of a long term one, currently the preferred packaging arrangement to get projects into the ubuntu universe is REVU, will this continue to be the standard or do you see an easy migration path from PPA to universe solely in launchpad?
[22:05] <beuno> Kaivalagi, I see the PPA -> Archive migration happening at some point
[22:05] <beuno> it has been discussed
[22:05] <bigjools> at some point we'll be able to do copy packages from PPAs, yes
[22:05] <Kaivalagi> it does seem a big long winded at present...it would be great for everything to be centralised :)
[22:06] <Kaivalagi> I'll keep a look out for any news...any feeds worth subscribing to to get this sort of info through?
[22:09] <bigjools> keep an eye on the usual LP announcements
[22:16] <Kaivalagi> alrightly, will do...for now I'll stick with providing my packages outside of the universe...
[22:16] <Kaivalagi> thanks bigjools
[22:16] <Kaivalagi> thanks beuno
[22:17] <beuno> Kaivalagi, :)
[22:18] <Kaivalagi> bye all