[00:03] <jml> :)
[00:03] <jml> six minutes of developer time!
[00:03] <jml> luxury!
[00:04] <sinzui> poolie: I blieve we should I mark every high bug that has not been fixed in 3 releases to low (clear it was not high enough for someone to close it)
[00:04] <poolie> sinzui: a quicker way to close off obsolete milestones and series would also be luxurious...
[00:05] <poolie> or, indeed, maybe they should just be automatically removed from the list shown for bug targets
[00:05] <sinzui> Yes, I think you are right
[00:05] <jml> when I was a boy, we had to participate constructively in four meeting in the snow before being allowed to petition for a keyboard -- and then we'd get a belting and we'd like it.
[00:06] <wgrant> jml: You can't expect to have more than a few minutes of dev team in a team named like yours...
[00:06] <wgrant> Er, dev *time*
[00:08] <jml> :)
[00:08] <wgrant> (although I guess it's now just Launchpad Code, rather than Launchpad Bazaar Integration :))
[00:12] <thewrath> hey all wats up
[00:12] <thewrath> havent been in here for a while
[00:13] <lifeless> poolie: apis; we could do it yourself
[00:13] <poolie> true
[00:13] <lifeless> sinzui: there is a problem with projects with a greater bug-add than bug-close rate
[00:13] <lifeless> oh, you said 'high' bugs specifically.
[00:14] <jml> lifeless: yeah, I like to call that problem "software"
[00:14] <lifeless> jml: :P
[00:18] <SamB> lifeless: that's actually pretty normal
[00:18] <SamB> for it to be slightly higher
[00:18] <SamB> it's somewhat proportional to the number of users + size of code base
[00:22] <exarkun> SamB: reference?
[00:22] <SamB> exarkun: greater bug-add than bug-close rate
[00:23] <SamB> I mean, the number of open bugs open is going to be somewhat proportional to those things
[00:23] <SamB> hmm. too many opens.
[00:23] <exarkun> SamB: I mean cite your sources
[00:24] <SamB> exarkun: sources?
[00:24] <SamB> I'm using a simple randomized model
[00:25] <SamB> where users stumble into bugs at random
[00:25] <exarkun> ie, making stuff up :)
[00:26] <SamB> yeah!
[00:26] <SamB> exactly
[00:48] <lifeless> SamB: I'm saying that using a algorithm to close bugs in such situations is a problem
[00:48] <lifeless> SamB: not that any given % of projects are in that situation
[01:00] <mneptok> i use a complex algorithm to determine heuristically the most opportune time to ask my wife for sex.
[01:01] <mneptok> we last made love the night before i started developing my algorithm.
[01:15] <lifeless> mneptok: :P
[01:35] <djails> Hi everybody, I wanted to know if there is  way to access the number of downloads for a package in a PPA
[01:35] <beuno> djails, no, not currently
[01:35] <beuno> but it's on our roadmap
[01:36] <beuno> so it will likely happen in the next month or two
[01:36] <djails> beuno: cool, thanks
[06:52] <tansell> what am I doing wrong here?
[06:52] <tansell> After installing, the following source dependencies are still unsatisfied:
[06:52] <tansell> gccxml(inst 0.9.0+cvs20090508-0~jaunty0 ! = wanted 0.9.0+cvs20090508)
[07:00] <lifeless> 0.9.0+cvs20090508-0~jaunty0 is before 0.9.0+cvs20090508
[07:00] <lifeless> oh hang on
[07:00] <lifeless> its not
[07:00] <lifeless> but perhaps you have a equality constraint?
[07:01] <tsimpson> 0.9.0+cvs20090508-0~jaunty0 is less than 0.9.0+cvs20090508
[07:02] <lifeless> tsimpson: no, its not, the -0 is after, the ~jaunty0 is between 0.9.0+cvs20090508 and 0.9.0+cvs20090508-0
[07:02] <lifeless> I made the same mistake on first reading it
[07:02] <tsimpson> lifeless: $ dpkg --compare-versions 0.9.0+cvs20090508-0~jaunty0 lt 0.9.0+cvs20090508;echo $?
[07:02] <tsimpson> 0
[07:02] <tsimpson> dpkg thinks it is
[07:02] <lifeless> ugh
[07:02] <lifeless> dpkg is arguable insane
[07:03] <tsimpson> true, but we all must obey it
[07:03] <maxb> It does actually make sense, let me explain
[07:04] <maxb> The version comparision is not simply applied to the entire string
[07:04] <maxb> First, the string is split into 'version' and 'release' components at the last hyphen
[07:05] <maxb> Now here's the trick.... if there is no hyphen, that's the same as an empty release component
[07:05] <maxb> Now here's the second trick... the empty component compares identically to 0
[07:05] <maxb> Hence, 0~jaunty0 is before 0
[07:05] <lifeless> maxb: sure
[07:06] <lifeless> maxb: though I wouldn't say 'component' that has a rather specific meaning in debian packaging
[07:07] <maxb> hmm, yes. ok 'parts' then
[07:07] <lifeless> in particular the bit under discussion is the 'debian revision'
[07:08] <lifeless> http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version has the actual algorithm
[07:08] <lifeless> and its interesting to note that youre explanation is false, even if it fits the behaviour;)
[07:08] <lifeless> concretely in this case, the matching digits are stripped
[07:09] <lifeless> so this end up comparing '' to '~jaunty'
[07:09] <lifeless> actually no
[07:09] <lifeless> more complex...
[07:09] <lifeless> ah right
[07:09] <lifeless> '0' and '' is 0 and 0
[07:09] <lifeless> then '~jaunty' and '' is <
[07:12] <maxb> ...which I what I said :-)
[07:13] <maxb> toss in some extra fun about apt and dpkg not *quite* having the same behaviour in some obscure corner cases just for fun, to complete the technical discussion :-)
[07:15] <lifeless> maxb: not quite the same - you missed the nondigits, digits loop in the algorithm :)
[07:15] <lifeless> not that I'm pedantic or anything ;)
[07:15] <lifeless> maxb: apt behaves differently? thats very odd..
[07:16]  * maxb hunts a reference
[07:17] <lifeless> believeable, but od
[07:17] <lifeless> d
[07:20] <tansell> so how do I make the it accept any debian version which is equal to an upstream version?
[07:20] <lifeless> tansell: >= upstream, < (upstream+1)
[07:21] <tansell> IE 0.9.0+cvs20090508-0~jaunty0 and 0.9.0+cvs20090508-1 and 0.9.0+cvs20090508-0~jaunty1
[07:21] <tansell> lifeless, that makes me sad :(
[07:21] <lifeless> tansell: indeed; something is tickling my mind though
[07:21] <lifeless> I think it may be that -0~jaunty0 is not equal enough
[07:21] <lifeless> and that -1 will work wth =0.9.0+cvs20090508
[07:21] <lifeless> I'd need to test though
[07:22] <tansell> 0.9.0+cvs20090508-0~jaunty0 ! = wanted 0.9.0+cvs20090508
[07:23] <lifeless> indeed; I said though that 0~jaunty0 may be your problem
[07:23] <lifeless> try 1~jaunty0
[07:26] <tansell> tansell@tansell:~/src/google3$  dpkg --compare-versions 0.9.0+cvs20090508-1~jaunty0 eq 0.9.0+cvs20090508;echo $?
[07:26] <tansell> 1
[07:28] <maxb> eq really does mean *equal*
[07:28] <tansell> dunno :)
[07:28] <tansell> dpkg: --compare-versions bad relation
[07:29] <tansell> IE if you give it something like == it complains with that
[07:29] <iaculallad> possibly eq=equal
[07:30] <tansell> man page says eq is fine
[07:32] <iaculallad> man page says eq is fine?
[07:32] <tansell> lt le eq ne ge gt
[07:32] <tansell> man dpkg
[07:34] <tansell> you guys should steal the opensuse dependency analyser
[08:49]  * cafetiere is commonly seeing 'failed to connect to launchpad' errors the first time i go to a page.  the error implies i should only report it if it persists.  but as its nearly every time i go to a page i think it warrents a whine
[08:50] <cafetiere> typically the page is fine even on an instant reload
[08:50] <wgrant> cafetiere: that's the bug mentioned in the topic.
[08:51] <cafetiere> wgrant, ok thanks ... stupid topic is right truncated so i missed it
[09:26] <stas> hi, I have a problem registering a project
[09:26] <stas> I'm trying to register ubuntu-md project
[09:27] <stas> but launchpad says its used already by somebody else, but I can't see anything registered at http://launchpad.net/ubuntu-md
[09:27] <stas> any help will be appreciated
[09:30] <stas> Am I alone on this channel ? :-/
[09:30] <wgrant> stas: That project has probably been deactivated, so it's not visible any more. I'd recommend asking at https://answers.launchpad.net/launchpad/+addquestion
[09:30] <wgrant> You can probably steal that name.
[09:30] <stas> wgrant: thanks a lot
[09:41] <lifeless> how do multiple ppa names work
[09:41] <lifeless> I have a ppa called releases
[09:41] <lifeless> putting that in the dput conf -> fails
[09:41] <lifeless> or is the first ppa created special?
[09:42] <lifeless> Rejected:
[09:42] <lifeless> Could not find PPA named 'releases' for 'subunit'
[09:42] <lifeless> is the exact error
[09:44] <wgrant> lifeless: 'releases' there is the display name.
[09:44] <wgrant> The first PPA is always named 'ppa'
[09:44] <wgrant> So yes, the first PPA is special.
[09:44] <wgrant> Subsequent PPAs have an additional field on the creation page.
[09:44] <wgrant> if it has confused you, though, it's a bug.
[09:45] <lifeless> thanks
[09:46] <cprov> we could certainly make it clearer providing local instructions for 'installing packages from this ppa' and 'uploading packages to this ppa'
[09:46] <cprov> by 'local' I mean related to the context PPA.
[09:47] <wgrant> cprov: And having an uneditable field for the name when there are no existing PPAs.
[09:47] <spm> stas: it was deactivated. I just renamed the old, so please reapply/register when you're ready.
[09:47] <stas> spm: thanks :)
[09:47] <stas> it works
[09:48] <cprov> wgrant: uhm, sorry, I don't get it.
[09:48] <LenzGr> Hello there
[09:49] <wgrant> cprov: At the moment, the first PPA creation page doesn't show the name, but subsequent ones have a field for it. Perhaps the initial page could show the name, but with just the text 'ppa' rather than a textbox.
[09:49] <wgrant> That would make things less confusing, as lifeless clearly took the 'Display name' field to be the URL name.
[09:49] <LenzGr> Could anybody tell me how long it usually takes for an SVN import to kick off?
[09:50] <wgrant> LenzGr: It has to be manually reviewed, but I've found it normally happens within a working day or two.
[09:51] <LenzGr> wgrant: OK, then I guess I need to be patient :) - I submitted one 42 hours ago...
[09:51] <cprov> wgrant: yes, that can be done, but will only be seen by people who can 'edit' the PPA.
[09:51]  * LenzGr wants to encourage a project to choose bzr instead of git 
[09:51] <lifeless> cprov: I've filed a bug
[09:51] <wgrant> cprov: lifeless' problem was that he assumed he could name the initial PPA.
[09:52] <lifeless> wgrant: it asked me for a name
[09:52] <wgrant> cprov: Because there was a name (well, 'display name', but 'name') all the same.
[09:52] <LenzGr> Thus I would like to demonstrate how easy the migration from SVN to bzr/launchpad is...
[09:52] <lifeless> I assumed I understood what it was asking :)
[09:52] <cprov> lifeless: thanks
[09:52] <lifeless> in fact in this case, I would rather have liked to be able to edit the first ppa's name
[09:53] <lifeless> as it would be clearer to people setting up apt
[09:53] <wgrant> Right.
[09:53] <wgrant> I don't see why it's locked.
[09:54] <wgrant> Should the tuple of data within an Unauthorized really be returned as content? The first element is the repr of the object in question, which seems like it could be a security risk.
[09:54] <wgrant> (when using the API, this is)
[09:55] <cprov> wgrant: kinda legacy.
[09:55] <cprov> lifeless: why didn't you create a new PPA with the name you wanted ?
[09:56] <cprov> lifeless: I see you are concerned about used who already use it, but renaming would break it in the same way, right ?
[09:57] <lifeless> cprov: I'd be happy to rename this; its new
[09:57] <lifeless> cprov: I wasn't given the choice to set the real name, only the display name
[09:59] <cprov> lifeless: right, the default PPA name is locked as 'ppa'. That's just the legacy thing, I thought you had a different problem.
[09:59] <lifeless> I was confused
[10:00] <lifeless> because I was asked for a name, I gave it, but it didn't work in dput etc
[10:00] <wgrant> It can't be a legacy thing; the form must have been changed a couple of releases ago to explicitly hide that field when no other PPAs exist.
[10:00] <cprov> lifeless: anyway, in this circumstance you just activate the default one and don't use it, like a misnamed branch in LP.
[10:00] <lifeless> cprov: mmm, that seems... hard for people to discover
[10:01] <lifeless> I'm now fine; data learnt and on my merry way
[10:01] <cprov> wgrant: the legacy I refer to is the IPerson.archive property, it points to the default PPA.
[10:01] <lifeless> I'd like to prevent others failing/make it easier, and thats why the bug report ;)
[10:01] <wgrant> cprov: Right, I wondered about that.
[10:01] <cprov> wgrant: yes, that's the underlying problem that needs fixing.
[10:02] <wgrant> cprov: But all the code handles IPerson.archive being None fine, so absence of an Archive named 'ppa' would surely not break anything?
[10:02] <wgrant> Apart from the redirect, obviously.
[10:03] <cprov> wgrant: redirect, signing_key propagation and API would break atm.
[10:03] <cprov> but they are all fixable.
[10:03] <wgrant> cprov: Didn't you fix the signing key propogation bug a couple of days back?
[10:03] <wgrant> And the API is buggy.
[10:04] <cprov> wgrant: yes, I did, and it rely on IPerson.archive
[10:04] <wgrant> cprov: Wasn't the problem that it *couldn't* rely on that, because it might have not had a key due to being disabled?
[10:04] <cprov> wgrant: but it can easily change from name='ppa' to 'the oldest one'
[10:04] <wgrant> That's true.
[10:48] <matti> Hello folks.
[11:17] <matti> Any one alive?
[11:19]  * qball checks the bodies for a pulse
[11:19] <qball> no
[11:20] <hyperair> there's one
[11:20]  * hyperair points at qball 
[11:21]  * wgrant finishes qball off.
[11:21] <wgrant> Not any more!
[11:21]  * hyperair points at wgrant
[11:21] <hyperair> but now there's another!
[11:21] <wgrant> This is awkward.
[11:22] <wgrant> matti: Have you a question?
[11:23] <hyperair> heheh
[11:26] <matti> Yes.
[11:26] <matti> Sorry.
[11:27] <matti> I have sent an e-mail to feedback@ and I was wondering if anyone had a chance to look at it... as I haven't heard anything back :)
[11:28] <wgrant> matti: That's going to require an actual Launchpad person to answer, and nobody speaking here recently is one. Maybe one will appear soon.
[11:29] <matti> wgrant: Oh I see :)
[11:32] <wgrant> matti: Unless your question needs to remain private, you might get a better response in more public places (eg. here or Launchpad Answers)
[11:35] <matti> wgrant: I was asking about account merge.
[11:35] <wgrant> matti: Do you have access to both email addresses?
[11:36] <matti> wgrant: No.
[11:36] <matti> ;]
[11:36] <matti> wgrant: I know the procedure, no worries :)
[11:36] <wgrant> matti: OK.
[11:37] <matti> wgrant: I just want to confirm that they actually got my e-mail.
[11:37] <matti> wgrant: As it is some time right now since I have sent it :)
[11:38] <wgrant> matti: How long?
[11:38] <matti> Since monday :)
[11:39] <wgrant> Ah.
[11:39] <VK7HSE-Eee> Hi to all...  I sent a request a few days back to request for a ppa I created (thinking I could remove it) I have no use for a second ppa attached to my account. How do I or who do I need to talk to?
[11:42]  * tumbleweed assumes someone knows that the *.launchpad.net cert (used for edge.lp.net) expires tomorrow
[11:43] <wgrant> I remember last time it expired.. it was a few hours before they replaced it, IIRC.
[12:03] <Odd_Bloke> Is Rosetta amongst the Launchpad stuff due to be free'd?
[12:04] <wgrant> Odd_Bloke: Yes.
[12:04] <Odd_Bloke> \o/
[12:04] <Odd_Bloke> wgrant: Thanks. :)
[12:05] <Odd_Bloke> wgrant: That's happening RSN, not in a later release?
[12:05] <wgrant> Odd_Bloke: Parts of Launchpad (including all of Rosetta, as far as is publicly known...) will be open sourced on July 21st.
[12:06] <Odd_Bloke> Ah, excellent.
[12:06] <Odd_Bloke> Elleo: 12:05:55 < wgrant> Odd_Bloke: Parts of Launchpad (including all of Rosetta, as far as is publicly known...) will be open sourced on July 21st.
[12:06] <Elleo> ah, cool
[12:06] <Elleo> now we just need to convince mattl to be non-free for 2 months... :/
[13:01] <rowinggolfer> bug 360846
[13:01] <petski> I would like to know why malone didn't parsed the command I gave via the email interface. The comment is https://bugs.launchpad.net/ubuntu/+source/amsn/+bug/371103/comments/12 , and I expected it to change the assignee and to add some subscribers. Can anybody tell me what I've done wrong?
[13:02] <beuno> petski, you didn't add a space
[13:02] <petski> Secondly, "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1" is hidden by default, why isn't my "SIGNATURE" as well?
[13:03] <petski> beuno: where should I have added some space?
[13:03] <beuno> petski, before the commands
[13:03] <beuno>  status confirmed
[13:03] <petski> ahhh!
[13:04] <petski> It's in bold ... https://help.launchpad.net/Bugs/EmailInterface ... :S ... sorry
[13:06] <beuno> petski, happens to the best of us  :)
[13:06] <beuno> not sure what happened with the GPG sig
[13:06] <beuno> maybe BjornT or gmb can enlighten us
[13:06] <petski> thanks beuno :)
[13:11] <gmb> wsfgn?
[13:11]  * gmb reads scrollback
[13:12] <gmb> petski: Good question. I'm not sure. I suspect that's a bug.
[13:13] <petski> gmb: could you please verify if it's a bug or not. If it's the case, I'll file a report if that's needed.
[13:15] <gmb> petski: Well, it should be hidden and it isn't, so that's a bug.
[13:15] <gmb> I mean, it might be that there's some reason for it that I don't know about, but if that's so we'll just mark the bug Invalid.
[13:15] <gmb> petski: So please file it :)
[13:16] <petski> gmb: I will, thanks :)
[13:19] <kiko> I hate this crack
[13:19] <beuno> kiko, get a new dealer already
[13:21] <savvas> erm.. git tags are like bzr branches?
[13:21] <wgrant> savvas: git tags are like bzr tags. git branches are like bzr branches.
[13:22] <wgrant> git confusion is also like nothing ever seen before.
[13:22] <savvas> oh ok :)
[13:22] <savvas> I thought bzr doesn't use tags :P
[13:22] <wgrant> They're not quite the same, but they're similar.
[13:22] <wgrant> bzr can attach a tag to label a revision.
[13:22] <petski> gmb: looks like a dup of LP #161822
[13:23] <savvas> wgrant: are the tags visible somehow in launchpad?
[13:23] <wgrant> savvas: Only in loggerhead, I suspect.
[13:23] <beuno> wgrant, we don't show them in loggerhead just yet  :/
[13:24] <gmb> petski: Okay, thanks.
[13:24] <wgrant> beuno: Oh.
[13:24] <savvas> beuno: is there an open bug wishlist for it? :)
[13:24] <beuno> savvas, there is
[13:24] <beuno> and there
[13:24] <beuno> is a patch
[13:25] <beuno> which doesn't quite fit
[13:25]  * beuno looks for the bug #
[13:25] <beuno> bug 246739
[13:25] <savvas> cool, thanks!
[13:26] <beuno> savvas, poke me if you put together a patch  ;)
[13:26] <beuno> it should be very simple to do
[13:27] <savvas> will do
[13:27] <savvas> I've never seen the loggerhead, but I'll try :P
[13:27] <savvas> *loggerhead code
[13:27] <beuno> savvas, there's some code in a patch on the bug
[13:28] <beuno> to get you started
[13:28] <beuno> bzrlib is super nice
[13:29] <savvas> oki doki
[13:43] <VK7HSE> Is this normal ??? https://launchpad.net/builders
[13:44] <VK7HSE> as most builders are in a manual state?
[13:44] <wgrant> VK7HSE: That's to stop Karmic builds, as there's a bit of a disaster being fixed right now.
[13:45] <wgrant> Although I'm not sure why they care if PPAs are affected.
[13:45] <VK7HSE> Oh ok!... just push a new release of Me TV ....
[13:46] <VK7HSE> anyway I't will build when its ready then ! :)
[13:46] <wgrant> It will, yes.
[13:50] <wgrant> mpt: Did you mean to mark the public, triaged datepicker change bug as a duplicate of a private one? That doesn't seem like an entirely good idea (although it did reveal a security hole)
[13:51] <mpt> wgrant, oops, no, I should have made the original public. I've just done that now.
[13:51] <mpt> And please do report the security hole. :-)
[13:51] <wgrant> mpt: Already half-way through. Thanks.
[13:53]  * wgrant kicks the appservers again.
[14:22] <notRowingGolfer> hey savvas
[14:22] <notRowingGolfer> are you the gent who took a look at openmolar?
[14:23] <savvas> hey :)
[14:23] <savvas> erm..
[14:23] <savvas> refresh my memory :)
[14:23] <notRowingGolfer> med student from the baltic state?
[14:23] <savvas> the very same :P
[14:24] <notRowingGolfer> I was checking your profile. impressive.
[14:24] <savvas> oooh you had a problem with your locks
[14:24] <notRowingGolfer> ah that's right.
[14:24] <savvas> thank you :)
[14:24] <savvas> trying to get by in both "lifes" hehe
[14:24] <notRowingGolfer> I was putting 2 and 2 together and making 5
[14:25] <notRowingGolfer> I assumed that you had a look at the project because it is loosely a medical database app
[14:25] <notRowingGolfer> and you'll probably agree the medical profession needs such apps?
[14:28] <savvas> it does, badly if you ask me :)
[14:28] <savvas> does it support sqlite by the way?
[14:29] <notRowingGolfer> no, but that would be trivial to do.
[14:29] <notRowingGolfer> the python database api really nicely pulls all that stuff together.
[14:30] <notRowingGolfer> I think being database agnostic is important nowadays
[14:30] <notRowingGolfer> with big bad oracle on the march
[14:30] <savvas> it would be great addition if you ask me :) you could have an all-in-one binary and another one split to server/client
[14:30] <sladen> Soyuz people, can anyone tell me how often cron.daily is run these days?  And is it the same for the development distribution as the stable versions?
[14:31] <wgrant> sladen: Hourly.
[14:31] <notRowingGolfer> savvas: that's a fair suggestion. I'll look into it.
[14:31] <wgrant> sladen: And yes, it's the same for all series.
[14:31] <wgrant> sladen: (although I'm not a Soyuz person)
[14:31] <sladen> wgrant: ta.
[14:31] <noodles775> but he knows more about soyuz than some soyuz people ^^ ;)
[14:31] <wgrant> sladen: PPAs are published three times an hour, though.
[14:31] <wgrant> noodles775: pfft
[14:43] <matti> Any LP person present? :)
[14:43] <beuno> matti, there's like 30 of us
[14:43] <matti> :)
[15:13] <jblount> Hello! What happens when I push a project to lp:~jblount/project-name/awesome-branch, then months later push a new unrelated branch to the same place?
[15:13] <beuno> jblount, it will tell you they are unrelated
[15:13] <beuno> unless you push --overwrite
[15:15] <jblount> beuno: Nice, thanks.
[15:15] <jblount> (for what it's worth, I've been giving my branches more and more ridiculous names because I was nervous about what might happen)
[15:16] <beuno> jblount, bzr has some smart built into it  :)
[15:17] <lamalex_2> is there a way to regenerate a diff without doing resubmit on a merge proposal?
[15:17]  * jblount notes that bzr will *attempt* to protect him :)
[15:17] <lamalex_2> a mergee updated his branch with fixes, and I want to review them but I dont want to lose the review history
[15:18] <beuno> lamalex_2, there's some API to do it
[15:18] <beuno> and I think a script
[15:18] <beuno> rockstar would know
[15:18]  * rockstar knows nothing
[15:19] <lamalex_2> I mean I know how to do it in my bzr tree
[15:19] <james_w> anyone know how to set-up an SSH master connection to launchpad?
[15:19] <lamalex_2> but I'm at work, not doing my work :)
[15:19] <rockstar> lamalex_2, so, which diff do you want to update?
[15:19] <lamalex_2> reviewing merges instead
[15:20] <lamalex_2> rockstar: https://code.launchpad.net/~gotomail/do-plugins/TimerApplet/+merge/5456
[15:20] <lamalex_2> er
[15:20] <lamalex_2> thats not it
[15:20] <lamalex_2> https://code.edge.launchpad.net/~ulrik-sverdrup/do-plugins/screen/+merge/5680
[15:20] <lamalex_2> i always forget windows cant select to copy
[15:21] <rockstar> lamalex_2, so, when you submit a merge proposal, it creates what we call a "Review Diff"  that can't be changed.  However, if you look at the API (and you do, right? :) there's also the PreviewDiff that can be changed/updated with an app like MAD.
[15:21] <rockstar> lamalex_2, https://edge.launchpad.net/mad
[15:22] <lamalex_2> well if I wanted to do it myself I could just do bzr diff no?
[15:23] <lamalex_2> or does this actually update the LP ui
[15:23] <rockstar> lamalex_2, so, I have a plugin that's now part of bzr-launchpadplus that uses the command line to do reviews, and it generates diffs for me.
[15:23]  * wgrant hasn't worked out why the review diff is separate.
[15:24] <james_w> ah, sftp can maintain a master connection
[15:24] <rockstar> lamalex_2, MAD links the preview diff so that you can download it, but that's the only UI change.
[15:25] <lamalex_2> yah, it seems like I could just use bzr diff. I dont see the advantage of MAD
[15:27] <ChrisW> hey all, how do I join a team in launchpad?
[15:28] <james_w> the review diff not updating is going to be quite a pain I fear
[15:29] <wgrant> james_w: It thoroughly confused some members of my team when we started using it.
[15:29] <james_w> I can imagine
[15:29] <rockstar> lamalex_2, well, if you run MAD as a cron job like we do in the Launchpad team, we always have it.
[15:29] <lamalex_2> it definitely /should/ update
[15:30] <james_w> removing it when it is out of date would be better than leaving it unchanged
[15:30] <rockstar> lamalex_2, it's a fundamental part of a review.
[15:30] <lamalex_2> what's a fundamental part of review
[15:30] <wgrant> No, a correct diff is a fundamental part of a review.
[15:31] <wgrant> An incorrect one is not.
[15:31] <lamalex_2> ^ truth
[15:31]  * beuno agrees and thinks we should have an "update this diff" button or an automatic-update-on-page-load
[15:32] <wgrant> beuno: One can already update the diff, but only the secondary one.
[15:32] <james_w> is it resource consumption that means that it's not always up to date?
[15:32] <beuno> wgrant, but not from the webui?
[15:32] <wgrant> The one that is only linked to in one place, and should be the same as the displayed one, but is in fact separate.
[15:32] <beuno> james_w, I think that's the argument, yes
[15:32] <lamalex_2> cant you check if there are new revs since it was generated?
[15:32] <lamalex_2> and only generate it if there are newer revisions?
[15:33] <beuno> lamalex_2, yes. Still icnredibly resource intensive
[15:33] <wgrant> For some reason which I cannot fathom, there are two diffs. One is rendered nicely on the MP page, but the other is just linked.
[15:33] <ChrisW> seriously, I must be missing something big: where in the lp ui do I go to join a team? This is hte team I'm looking to join: https://launchpad.net/zope2
[15:33] <wgrant> One can update the linked diff through the webservice, but not the displayed one.
[15:33] <beuno> ChrisW, that's not a team  :)
[15:33] <beuno> ChrisW, https://edge.launchpad.net/~zope2-dev
[15:33] <ChrisW> well, how do I get to handle bugs on it?
[15:34] <beuno> I guess that's the team you want to join?
[15:34] <ChrisW> and where did you find that?
[15:34] <wgrant> You can perform most bug actions without being a member of any team.
[15:34] <beuno> ChrisW,  "Driver: Zope 2 Developers"
[15:34] <james_w> beuno: keeping preview diffs up to date would be massively more expensive than keeping review diffs up to date I assume
[15:34] <beuno> clicked on the link
[15:34] <wgrant> james_w: How? They should be identical.
[15:34] <james_w> wgrant: nope
[15:34] <beuno> james_w, I don't know the details, thumper does
[15:35] <ChrisW> beuno: what's "Driver" supposed to mean?!
[15:35] <james_w> wgrant: review diff can only change when there are new revisions in the source branch, preview diff will change when there are new revisions in either
[15:35] <james_w> so pushing a new revision to trunk would mean updating every preview diff
[15:35] <beuno> ChrisW, "the guy in charge"? I don't know, I kinda hate that word as well
[15:35] <wgrant> james_w: Oh, right, I think somebody told me that ages ago.
[15:36]  * ChrisW finds launchpad baroque and difficult to use
[15:36] <wgrant> james_w: Is it the preview diff or the review diff that's visible?
[15:36] <james_w> you would only update the review diff when someone pushed up new revisions to the source branch, which would presumably be in response to review comments
[15:36] <ChrisW> certainly wouldn't use it for any of my own projects...
[15:36] <james_w> wgrant: the review diff is the visible one I believe
[15:36] <wgrant> james_w: So it's the cheap one, but it's immutable!?
[15:36] <james_w> yeah, that's my understanding
[15:37] <beuno> ChrisW, I'm working on it  :)   a lot of changes coming down the pipe in the next few months
[15:37] <james_w> it's also probably cheaper to generate in terms of work bzr has to do FWIW
[15:38] <james_w> find common ancestor between source and target, diff that revision with the tip
[15:38] <james_w> rather than do a merge and diff the resulting tree to the tip of the target branch
[15:38] <wgrant> Right.
[15:39] <sinzui> We want current diff NOW
[15:39] <ChrisW> beuno: been hearing that for too many years, bored now...
[15:39]  * sinzui looks at the code team
[15:39] <wgrant> So, is there a good reason for the displayed diff to never be correctable?
[15:39] <james_w> I don't know of one
[15:39] <james_w> MAD could keep both up to date in theory
[15:39] <wgrant> Or a reason that the difference between the diffs isn't mentioned anywhere?
[15:40] <wgrant> I'd imagine that would be what it should do.
[15:40] <wgrant> But it can't.
[15:40] <beuno> ChanServ, not from me you haven't
[15:40] <beuno> ARGH
[15:40] <wgrant> Nice timing.
[15:40] <beuno> not from me you haven't
[15:40]  * beuno stops trying
[15:41] <wgrant> What happened to the project<->team linkage that was meant to be happening for 3.0?
[15:42] <wgrant> We're rather close, and it still hasn't shown up...
[15:43] <beuno> wgrant, sinzui has all kinds of branches down his sleeves
[15:44] <sinzui> beuno: I am one design and one model change from bringing sanity to projects and teams
[15:44] <beuno> :)
[15:45]  * sinzui looks for more Molotov cocktails to get these done
[15:45] <wgrant> Good news!
[15:46] <sinzui> wgrant: The project/team linkage is a real shame that we did not solve this years ago. We have lots of little problems that lead to teams solving the same problem over and over again
[15:46] <wgrant> I do, like beuno and ChrisW, hope Driver dies. It has been there for as long as I can remember, yet I can still only guess at its purpose.
[15:46] <LarstiQ> yet it seems so clear to me
[15:47] <sinzui> wgrant: I just gave driver the power to create series so that he can plan releases. The driver might be better called the release manage
[15:47] <sinzui> r
[15:47] <beuno> sinzui, +1000000000
[15:47] <wgrant> sinzui: That makes more sense.
[15:48] <sinzui> wgrant: I think the problem with that role, is that we codified it in our application, then denied the role all the powers that he or she needs
[15:48] <wgrant> I wonder if having fixed non-superuser roles is a flawed idea, though.
[15:50] <sinzui> wgrant: I think the app needs them, but the app needs to understand that community create roles too, and it should honor those roles
[15:50] <wgrant> sinzui: Why does the app need them? It can be made to handle more flexible roles.
[15:51] <sinzui> wgrant: Yes, it can be made to handle them more flexibly
[15:51] <sinzui> wgrant: Making teams access control was a mistake.
[15:52] <wgrant> sinzui: It does make things very simple for projects that fit into the expected model.
[15:52] <wgrant> sinzui: But for anything else... erk.
[15:54] <wgrant> But anyway, it's 1am and I'm sure you've discussed this all before.
[15:54] <sinzui> wgrant: exactly. sabdfl wants projects to define their own communities without forcing themselves to take the shape of how Launchpad currently works
[15:55] <wgrant> sinzui: I'm glad he supports that idea.
[16:25] <kiko> MTecknology, ping?
[16:39] <blacknred0> i've been trying to upload my packages and i've been receiving this error message "Further error processing not possible because of a critical previous error."  any thoughts?
[16:57] <sinzui> cprov: do you have any insights into blacknred0's problem?
[16:58] <cprov> blacknred0: doesn't it say what the error is further in the email ?
[16:59] <blacknred0> cprov, the latest one says "my_package Unknown section 'unknown'"
[17:00] <blacknred0> is there something in specific that should go under "debian/controls" in the section area?
[17:00] <cprov> blacknred0: right, you found it. You have to fix your debian/control data
[17:00] <blacknred0> cprov, ok, then... what are the categories?
[17:00] <blacknred0> any?
[17:00] <cprov> blacknred0: a valid/known 'section'.
[17:01] <cprov> the fact that they are not exposed in LP is a bug .. but it should be somewhere in ubuntu/debian wikis. Let me look for it
[17:04] <cprov> blacknred0: http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections, is a start.
[17:05] <blacknred0> cprov, thnx. got it ;)
[17:06] <nishant> to all
[17:25] <lazermouse> sinzui: has that spamming prblem been sorted yet?
[17:25] <sinzui> lazermouse: I am not aware of a spamming problem. Can you elaborate.
[17:26] <lazermouse> wel, I was speaking to bac earlier
[17:26] <lazermouse> A few users were sending spam to my email address
[17:26] <lazermouse> and to someone elses
[17:27] <sinzui> I will ask ...
[17:27] <lazermouse> thanks
[17:35] <sinzui> lazermouse: The user was suspended
[17:35] <lazermouse> woohoo!
[17:35] <lazermouse> serves him right
[17:36] <lazermouse> thank you
[17:36] <sinzui> thank bac and the admin
[18:31] <Adri2000> someone uploaded a package to his PPA with my name in the changelog. now that package shows up on my +related-software page. is there a bug reported about this?
[19:06] <sinzui> Adri2000: Did you make a change to the source package?
[19:08] <sinzui> Adri2000: We are debating the usefulness of +related-software. The rules of how it works are not clear nor is its value.
[19:30] <bigjools> sinzui: the motu guys use that page
[19:32] <sinzui> bigjools: I know the page is used, but why is it the same of +related-projects. Why do we have two links the to same page? Why the overlap, what is the real purpose of this information and do we really know how to collection the information
[19:32] <james_w> bigjools: I'm not sure we do, as we find it to be unreliable, or at least confusing
[19:33] <bigjools> well I've done bug fixes on it as people have requested before
[19:34] <james_w> maybe it's improved now then
[19:34] <sinzui> bigjools: I'm sure you have, there is definitely a lot of bugs with the page.
[19:34] <sinzui> beuno: and I have discussed the page, but we do not have a clear answer as to what needs to be done
[19:34] <bigjools> it's probably a good subject for UDS then
[19:35] <Adri2000> sinzui: yes I did upload this package to ubuntu. someone took it to make some changes and uploaded it to his ppa with my name in the changelog
[19:36] <kiko> MTecknology, ping?
[19:36] <bigjools> sinzui: you're at UDS right?
[19:36] <sinzui> Adri2000: Launchpad has learned a lot about all of us because changelogs are public. So I am not surprised that you are connect with the package, being directly connected to a PPA is a surprise
[19:37] <sinzui> bigjools: for the first 2 days
[19:37] <bigjools> sinzui: ok we can grab some motus and get some use cases
[19:38] <Adri2000> sinzui: see https://launchpad.net/~adri2000/+ppa-packages and https://launchpad.net/ubuntu/+source/amsn
[19:39] <sinzui> Wow, I finally see a real Delete Link button. I wonder if it really works
[19:40]  * sinzui is aware that there is a bug with those link
[19:41] <bigjools> Adri2000: the only bug is that the package is deleted in that PPA now, so it should not be listed in +ppa-packages for you
[19:41] <sinzui> Oh I see, PPA Packages, not the actual +related-software page
[19:42] <Adri2000> sinzui: it's on the +related-software page as well
[19:42] <Adri2000> bigjools: the problem is that I did *not* upload amsn to my PPA nor to any PPA
[19:42] <Adri2000> frenchy82 did
[19:42] <bigjools> Adri2000: that's not the point, it tracks your packages, no matter who uploaded it.
[19:42] <Adri2000> see the "Uploaded to" column
[19:42] <Adri2000> it is not my package
[19:43] <Adri2000> it is not my ppa
[19:43] <Adri2000> I'm not the uploader
[19:43] <beuno> well
[19:43] <Adri2000> no reason to say it's mine
[19:43] <beuno> we have the same problem with branches
[19:43] <beuno> if I commit with your email
[19:43] <beuno> you're tied to it
[19:43] <beuno> it sucks as well
[19:43] <SamB> arguably, it's only your package if you approved that version ...
[19:43] <beuno> and we need to figure out a good way around this
[19:43] <sinzui> SamB: I think I agree
[19:43] <SamB> signatures on the source package?
[19:43] <Adri2000> check who signed the signature instead of relying on the Changed-By field?
[19:43] <Adri2000> signed the package*
[19:44] <Adri2000> at least for PPAs
[19:44] <SamB> or, just go by who's PPA it is
[19:44] <LarstiQ> SamB: what to do for team PPAs?
[19:44] <Adri2000> I think we can trust ubuntu developers who sign someone else's package because that person doesn't have upload rights (sponsoring)
[19:44] <LarstiQ> beuno: signing your commits before counting them, or is that to onerous?
[19:45] <Adri2000> in this case, the package should still be assigned to the person in the changelog
[19:45] <bigjools> the person who signed it is not necessarily the maintainer, nor the changer
[19:45] <beuno> LarstiQ, most people don't sign them, and we don't process that on Launchpad today anyway
[19:45] <bigjools> but I agree we need to review that page
[19:45] <beuno> LarstiQ, but yes, that would be one solution (albeit it would add complexity to it)
[19:45] <SamB> well, if we're going to be trusting, we could just count packages where the latest changelog entry contains a particular name ...
[19:46] <beuno> one place to start is let you say "no, this is not mine"
[19:46] <SamB> where we of course doesn't include me, actually ;-P
[20:58] <colonelqubit> I'm seeing a lot of dupes (and making some of them myself) due to launchpad flakiness recently. Is there a way for launchpad to have some kind of dupe detection? (maybe if an entry has exactly the same data as an entry made within the same hour or same day, it would be flagged)
[20:59] <beuno> colonelqubit, yes
[20:59] <LarstiQ> colonelqubit: I thought the bug filing process is supposed to suggest similar bugs to you
[20:59] <beuno> it's on our roadmap
[20:59] <colonelqubit> LarstiQ: I'm getting dupes with Answers and FAQ entries.
[20:59] <beuno> ah
[20:59] <beuno> interesting
[21:01] <beuno> sinzui, do we have dupe detection for answers?
[21:01] <sinzui> No
[21:01] <beuno> colonelqubit, do you want to file a bug for that?
[21:01] <colonelqubit> beuno: sure
[21:01] <beuno> thanks
[21:02] <sinzui> beuno: we rely on answer contacts to say "Bugger this. This is an FAQ"
[21:03] <colonelqubit> beuno: quick question -- how do I file a bug against answers?
[21:03] <colonelqubit> I found it yesterday..
[21:03] <sinzui> launchpad-answers
[21:03] <colonelqubit> maybe if there was a button on answers.launchpad.net that said "File a bug against me" or something...
[21:03] <colonelqubit> thanks
[21:03] <sinzui> bugs.launchpad.net/launchpad-answers
[21:04] <sinzui> colonelqubit: we triage all bugs in /launchpad. We will move it to answers
[21:29] <MTecknology> kiko-afk: hi
[21:30] <MTecknology> kiko-afk: s/hi/pong/
[21:31] <MTecknology> Anytime a random Canonical guy wants to get a hold of me, it can't be good.
[21:36] <soren> MTecknology: Oh, don't worry. kiko isn't random.
[21:36] <alan__> hello
[21:39] <MTecknology> soren: that makes me even more nervous
[21:39] <MTecknology> :P
[21:39] <beuno> MTecknology, what's up?
[21:39]  * soren has no comment
[21:40] <MTecknology> beuno: I was responding to a previous ping
[21:40] <beuno> kiko just likes to say hi to people
[21:40] <beuno> he's *that* nice
[21:42] <MTecknology> kiko-afk: You can email me too. I know you know my addy :)
[22:18] <bencrisford> I cannot mark bug reports as duplicates, I am assuming this is due to bug 360846?
[22:23] <sinzui> bencrisford: duplicate handling is now a JavaScript AJAX operation
[22:23] <sinzui> bencrisford: Do you know if you are getting a javascript error or have it disabled
[22:24] <bencrisford> I was geting a javascript-ajax kind of box
[22:25] <bencrisford> and it had the error which i am getting every now and then today
[22:25] <sinzui> but you do not get a green flash with the updated text
[22:25] <bencrisford> no, its working  now
[22:25] <bencrisford> now its opening a new page
[22:26] <sinzui> the appserver could be a cause, but incomplete loading of the page is more liketly
[22:26] <box02> halo .. somebody could help me? I had uploaded my package to ppa, but it was rejected. Could you tell me why?
[22:27] <sinzui> box02: reject messages are often accompanied with a message
[22:27] <box02> sinzui: Have I show you?
[22:28] <sinzui> Pasting part of the message is all that is usually needed
[22:29] <box02> from	Launchpad PPA <no_reply@launchpad.net>
[22:29] <box02> reply-to	Launchpad PPA <no_reply@launchpad.net>
[22:29] <box02> to	box02 <thebox02@gmail.com>
[22:29] <box02> date	Fri, May 8, 2009 at 11:10 PM
[22:29] <box02> subject	zawgyi-kb_0.1.2-1~ppa1_source.changes rejected
[22:29] <box02> mailed-by	canonical.com
[22:29] <box02> 	
[22:29] <box02> hide details 11:10 PM (17 minutes ago)
[22:29] <box02> 	
[22:29] <box02> 	
[22:29] <box02> Reply
[22:29] <box02> 	
[22:29] <box02> 	Follow up message
[22:29] <box02> - Hide quoted text -
[22:29] <box02> Rejected:
[22:29] <hggdh> oh boy
[22:29] <box02> zawgyi-kb_0.1.2-1~ppa1.dsc: Unknown section 'X11'
[22:29] <box02> zawgyi-kb_0.1.2.orig.tar.gz: Unknown section 'X11'
[22:29] <box02> zawgyi-kb_0.1.2-1~ppa1.diff.gz: Unknown section 'X11'
[22:29] <box02> Further error processing not possible because of a critical previous error.
[22:29] <box02> Format: 1.8
[22:29] <box02> Date: Fri, 08 May 2009 21:47:03 +0200
[22:29] <box02> Source: zawgyi-kb
[22:29] <sinzui> thank you
[22:29] <box02> Binary: zawgyi-kb
[22:29] <box02> Architecture: source
[22:29] <sinzui> Unknown is the key
[22:29] <box02> Version: 0.1.2-1~ppa1
[22:29] <box02> Distribution: jaunty
[22:29] <box02> Urgency: low
[22:29] <box02> Maintainer: box02 <thebox02@gmail.com>
[22:30] <box02> Changed-By: box02 <thebox02@gmail.com>
[22:30] <box02> Description:
[22:30] <box02>  zawgyi-kb  - Zawgyi Keyboard for Ubuntu Linux.
[22:30] <box02> Changes:
[22:30] <box02>  zawgyi-kb (0.1.2-1~ppa1) jaunty; urgency=low
[22:30] <box02>  .
[22:30] <box02>   * New Upstream Release for Ubuntu.
[22:30] <box02> Checksums-Sha1:
[22:30] <box02>  a77af9b39300b431d29bc4bb457d9900a02266f0 1091 zawgyi-kb_0.1.2-1~ppa1.dsc
[22:30] <box02>  bbaa65eaa49daa1b5c03870743031f6d475d537c 661740 zawgyi-kb_0.1.2.orig.tar.gz
[22:30] <box02>  5d14435449383afea0dfc983d8b8637290183336 1935 zawgyi-kb_0.1.2-1~ppa1.diff.gz
[22:30] <box02> Checksums-Sha256:
[22:30] <box02>  1e4b7e35d19f183899c4bc066480fa98771bff920df8a183ae74841e8187b494 1091 zawgyi-kb_0.1.2-1~ppa1.dsc
[22:30] <box02>  c1a74ea54e692f9196c29ee08172bd574dc2dcfc4c6da1821c7b951bcdd7962f 661740 zawgyi-kb_0.1.2.orig.tar.gz
[22:30] <box02>  74a1fb474796059d28ab1ca3aa032f14be4b1315e15781582a4655b87703bc88 1935 zawgyi-kb_0.1.2-1~ppa1.diff.gz
[22:30] <box02> Files:
[22:30] <box02>  05e98037eae910b28366e73487572739 1091 X11 optional zawgyi-kb_0.1.2-1~ppa1.dsc
[22:30] <box02>  bdd6b71f6d85eada9c1f60ae6a49f665 661740 X11 optional zawgyi-kb_0.1.2.orig.tar.gz
[22:30] <box02>  d742ad78051afbd330404762d4c47fc3 1935 X11 optional zawgyi-kb_0.1.2-1~ppa1.diff.gz
[22:30] <box02> [22:30] <box02> If you don't understand why your files were rejected please send an email
[22:30] <box02> to launchpad-users@lists.launchpad.net for help (requires membership).
[22:30] <box02> sorry
[22:30] <box02> aha .. so the key wasn't correct?
[22:30] <box02> what should I do?
[22:31] <matsubara> box02: next time use http://pastebin.ubuntu.com/
[22:31] <sinzui> box02: I think you are missing information in the debian/control data. The Unknown section needs correction
[22:32] <box02> matsubara: thank you, but how to use it?
[22:32] <box02> sinzui: aha
[22:32] <sinzui> box02: http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
[22:33] <sinzui> I think you want x11, not X11
[22:33] <box02> sinzui: aha .. I will check it out.
[22:34] <box02> sinzui: thank you so much :-)
[22:34] <box02> sinzui: and something else?
[22:34] <matsubara> box02: paste whatever you want in the content field there, click the paste button and then give the URL to the person who requested the paste output
[22:34] <sinzui> I blame X for insisting that we capitalise it. That is an easy mistake to make.
[22:34] <box02> matsubara: aha .. alright :-) .. thank you! later I will do it. :)
[22:35] <matsubara> sure, np :-)
[22:36] <box02> sinzui: yes, I'll change it and repeat build again. thank you for your help. :-)
[22:36] <sinzui> box02: your welcome
[22:36] <box02> matsubara: thank you :-)
[22:37] <box02> sinzui: well I'll try it out and good bye for now all. :-)
[23:06] <aruetten> hy everyone, a few weeks i registered a branch to a projekt and i remember that there was a whiteboard textfield in the branch,today i register a branch and there is no whiteboard,was there a change in launchpad? I'msearching for a place to add a few word to my branch where i can explain for what i will use the branch.
[23:06] <beuno> aruetten, yes, we removed whiteboards for ever and ever
[23:07] <beuno> you should have a description field
[23:09] <aruetten> beuno: ok, can you give me a hint where i can find the description field please
[23:10] <beuno> aruetten, you should have an edit button next to the branch title
[23:10] <beuno> ah
[23:10] <beuno> wait
[23:10] <beuno> interesting
[23:10]  * beuno summons rockstar 
[23:13] <aruetten> yes and in the details i have  fields for owner. project, name and status,but nothing more
[23:13] <beuno> aruetten, yes, you're right
[23:13] <beuno> I was expecting a description field to be there
[23:13] <beuno> if rockstar doesn't pop in in a minute ore so
[23:14] <beuno> would you file a bug about a lack of description field for branches?
[23:14] <beuno> he may blame me, and may be right, but we should have one
[23:24] <Laney> can I access my team memberships through launchpadlib?
[23:24] <aruetten> ok, no rockstar
[23:25] <aruetten> i will open a bug
[23:27] <aruetten> beuno:  what would be the right project? launchpad itselfs,launchpad foundations, ...?
[23:28] <beuno> aruetten, launchpad itself is fine
[23:28] <aruetten> ok
[23:28] <james_w> Laney: not the sensible way I don't think
[23:29] <Laney> is there any way?
[23:29] <james_w> Laney: you can enumerate members of teams
[23:29] <Laney> u-d-t seems to screen scrape for some text which doesn't exist any more
[23:30] <james_w> Laney: ah, there may be a better way to do that
[23:30] <Laney> surely
[23:30] <james_w> no, I mean a better way that looking for membership of ~ubuntu-dev
[23:31] <james_w> uploaders = launchpad.distributions['ubuntu'].main_archive.getUploadersForPackage(source_package_name="foo")
[23:31]  * Laney tests
[23:32] <james_w> then you need a recursive walk of uploaders I think
[23:32] <james_w> but it will work for specific package upload rights and the like
[23:32] <james_w> so the rule will be "if you can upload the package you don't need sponsorship"
[23:32] <Laney> well that expresses the intent accurately
[23:33] <james_w> we'll hopefully be able to use syncSource soon :-)
[23:34] <james_w> the recursive walk needs to check is_valid
[23:34] <aruetten> beuno: Bug #373913
[23:34] <james_w> but you can use launchpad.me and compare it to everything in uploaders.members and uploaders.members[i].members etc.
[23:35] <james_w> there is is_team to know whether members will make sense, but I presume members is just the empty list for people, so it won't break
[23:39] <beuno> aruetten, thanks
[23:43] <kiko-afk> fe fi fo fum
[23:45] <rockstar> Whoa, apparently people have been pinging me in this channel, and I haven't noticed.
[23:45] <Nafallo> kiko-afk: I do not want to be the person getting that review ;-)
[23:45] <rockstar> aruetten, hi
[23:57] <aruetten> rockstar: hey
[23:57] <aruetten> rockstar: ﻿Bug #373913
[23:58] <aruetten> beuno ﻿summons you for this