[02:37] <lotuspsychje> good morning
[07:21] <chromebittin> morning
[11:32] <wez> chromebittin: Lets discuss Ubuntu! We can do it! We can turn this currently salutations based conversation channel around!
[11:32] <chromebittin> wez: :p
[11:33] <wez> :)  How about that 22.04, am I right?
[11:34] <chromebittin> i run 20.04 and 18.04
[11:46] <wez> Oh, You haven't considered do-release-upgrade'ing yet?
[11:48] <chromebittin> can't for various reasons
[11:49] <chromebittin> one being a https://wiki.freebsd.org/Linuxulator install the other one a 32 bit system
[11:51] <wez> ouch, 32bit. I guess they are still around aren't they.


[18:05] <Brainstorm> Updates for Bangladesh: +312 cases (now 1.6 million), +3 deaths (now 27961), +21002 tests (now 10.8 million) since a day ago


[03:38] <stub> lifeless: You might be interested in reviewing https://code.edge.https://code.edge.launchpad.net/~stub/launchpad/cronscripts/+merge/36005 -- cronscript oops stuff we discussed and some delinting noise.
[03:39] <lifeless> what was  LibrarianFormatter for ?
[03:49] <stub> lifeless: Instead of spitting out exceptions to stderr, it stored them in the Librarian and spat out a URL. For a while some of the batch jobs where insanely noisy and this made them slightly more readable.
[03:50] <lifeless> kk
[03:51] <lifeless> CrashScript has huge vertical whitespace
[03:52] <lifeless> could you compact it a little?
[03:53] <stub> k
[03:55] <lifeless> I only ask cause I couldn't really read it without my eyes rolling back in their sockets
[04:18] <thumper> lifeless: there is also https://code.edge.launchpad.net/~thumper/launchpad/branch-distro-set-old-mature/+merge/36095 if you'd like to approve another trivial branch
[04:20] <lifeless> line 30, the extra vws weirds me
[04:20] <lifeless> up to you
[04:31] <thumper> lifeless: are you vws phobic?
[04:32]  * wgrant likes LibrarianFormatter.
[04:32] <wgrant> It's handy until Soyuz gets fixed.
[04:32] <lifeless> thumper: no, but it often makes things harder to read
[04:32] <lifeless> thumper: my rule of thumb is that if I need vws I need a new function
[04:32] <lifeless> thumper: but its a shallow thing - I don't fundamentally care; I'll make it look how I prefer when I touch something, but really, anything goes.
[04:40] <thumper> :)
[04:52] <stub> wgrant: I can leave it if it is useful. I didn't think anyone liked it any more.
[04:53] <wgrant> stub: It's still useful for people to see it in Soyuz upload logs.
[04:53] <wgrant> Since Soyuz can be a bit harsh sometimes.
[04:55] <stub> https://bugs.edge.launchpad.net/launchpad-foundations/+bug/641103
[04:55] <_mup_> Bug #641103: LibrarianFormatter should die <Launchpad Foundations:Triaged> <https://launchpad.net/bugs/641103>
[06:14] <thumper> mwhudson: interested in the branch-distro script change to avoid the scan/
[06:14] <thumper> ?
[06:14] <thumper> mwhudson: it is surprisingly small
[06:15] <mwhudson> thumper: sure
[06:16]  * thumper gets it ready
[06:17]  * thumper sighs
[06:17] <thumper> other test failures
[06:17] <thumper> due to my groovey new code
[06:17] <thumper> which now assumes real database data
[06:18] <mwhudson> heh
[06:18] <mwhudson> there are some rather extreme fakes in the tests for branch-distro iirc
[06:19]  * thumper is rerunning the tests
[06:19]  * thumper forgot -v
[06:20] <thumper> it is snowing again
[06:20] <mwhudson> !
[06:20] <mwhudson> very pleasant day in wellington today
[06:20] <thumper> w00t
[06:20] <thumper> all passing again
[06:24] <thumper> mwhudson: https://code.edge.launchpad.net/~thumper/launchpad/branch-distro-avoid-scan/+merge/36103
[06:26] <thumper> mwhudson: I'm going to help with dinner, feel free to leave comments, and I'll look later
[06:27] <mwhudson> thumper: ok
[10:43] <bryceh>  On call: gmb || Reviewing: noodles775 || queue: [bryceharrington]  || This channel is logged: http://irclogs.ubuntu.com/ || https://code.launchpad.net/launchpad/+activereviews
[10:47] <noodles775> Thanks gmb
[10:48] <gmb> noodles775, r=me; one change needed and one slight refactoring requested.
[10:48] <noodles775> Thanks gmb, I'll take a look.
[10:49] <gmb> bryceh, lp-617679-code, right?
[11:11] <noodles775> gmb: with makeLaunchpadService(), why not just put it in TestCaseWithFactory? (ie. is there a reason why I should have to think about a separate subclass etc. when adding an API test?)
[11:12] <gmb> noodles775, Well, if you added a WebServiceTestCase, you could also set its layer to AppServiceLayer by default. Other than that, though, there's no reason not to just put it in *WithFactory.
[11:12] <lifeless> gmb: why do you need a WebServiceTestCase
[11:13] <gmb> lifeless, You don't. It would save people from having to re-do what noodles775 did in one of his test cases for the webservice, but it was just an idea. As noodles775 said, might as well add his makeLaunchpadService() method to TestCaseWithFactory,.
[11:14] <lifeless> I haven't seen the code, but unless it also uses factory methods, why not just have it standalone ?
[11:16] <gmb> That would also work. noodles775, can you confirm that that's doable?
[11:17] <noodles775> It does use factory.makePerson currently.
[11:20] <noodles775> But sure, it could go in lp.testing._webservice.py
[11:20] <lifeless> if its using factory.makePerson it should be on the factory
[11:23] <gmb> D'OH.
[11:24] <gmb> I blame lack of caffeine for my not spotting the blindingly obvious.
[11:37] <gmb> noodles775, So, as has been said, that method should be on the factory, not on some other TestCase.
[11:37] <noodles775> Yep, I'll move it to the factory.
[11:39] <gmb> Cool.
[11:39]  * gmb grabs a drink; bbiab
[14:00] <gmb> Morning mars
[14:00] <mars> Morning gmb!
[14:38] <gmb> mars, I have one for your queue. https://code.edge.launchpad.net/~gmb/launchpad/bug-644346/+merge/36143
[14:38] <gmb> Nice and small.
[14:38] <mars> gmb, thanks
[14:58] <jcsackett> hello, mars and gmb.
[14:58] <jcsackett> https://code.edge.launchpad.net/~jcsackett/launchpad/series-need-usage-attributes-643902/+merge/36145 could use a review, when you have time.
[14:59] <gmb> jcsackett, I'll take a look shorly.
[14:59] <gmb> *shortly
[14:59] <mars> jcsackett, I have two in the queue before that
[14:59] <mars> thanks gmb
[14:59] <jcsackett> gmb, thanks. :-)
[14:59]  * gmb grabs a drink first
[15:10] <gmb> jcsackett, On line 177 you say "# If translations_usage is set for the Product, respect it" but then you reference self.distribution.translations_usage. I'm assuming you need to s/Product/Distribution in the comment.
[15:11] <jcsackett> gmb: you're correct. making the change.
[15:11] <gmb> Same on line 241
[15:12] <gmb> jcsackett, You need to add some comments or docstrings to the start of your tests explaining what they test (you should phrase this as a statement of expected behaviour, e.g. "The frobnob goes boing." rather than "Test that the frobnob goes boing."
[15:13] <gmb> Other than that, r=me.
[15:14] <jcsackett> gmb: you got it; i'll make those changes.
[15:14] <jcsackett> thanks a lot!
[16:06] <abentley> rockstar, could you review https://code.edge.launchpad.net/~abentley/launchpad/incremental-diff-driveby/+merge/36156 please?
[16:08] <rockstar> abentley, sure.
[16:08] <abentley> rockstar, thanks.
[16:09] <rockstar> abentley, is any of that lint legitimate?
[16:09] <abentley> rockstar, I don't think so, but I'm open to other opinions.
[16:09] <rockstar> abentley, it looks like the first one, line 715 of ./lib/lp/code/interfaces/branchmergeproposal.py, might be.
[16:11] <abentley> rockstar, AFAICT, there are two blank lines above notify_modified.
[16:11] <rockstar> abentley, yeah, I looked. WTF.
[16:12] <abentley> rockstar, I think it's because the comment is there, but if that's the reason, it should say "found 0".
[17:26] <henninge> danilos: https://code.edge.launchpad.net/~henninge/launchpad/recife-poimport/+merge/36165
[17:27] <danilos> henninge, thanks, can you please find someone else as a reviewer if you are in a hurry to get some rest because I am chasing that nasty bug you filed :)
[17:28] <henninge> danilos: ok
[17:28] <henninge> danilos: that is a good excuse ;-)
[17:29] <henninge> unfortunately it's oversized
[18:10] <sinzui> mars I added a large branch to your queue. While most the the branch are deletes, It still looks scary. I can get EdwinGrubbs or bac to do it tomorrow if you do not have time
[18:20] <mars> sinzui, I'll take it
[19:02] <mars> deryck[lunch], ping when you return
[19:40] <deryck> hi mars
[19:41] <mars> hi deryck
[19:42] <mars> deryck, I have a review here from mbp where he asks for a careful review and some advice on testing his mail handling code.
[19:42] <mars> deryck, I was wondering if someone on your team would have knowledge in that domain that could help Martin out?
[19:43] <mars> deryck, it is some work he did on the DKIM code: https://code.edge.launchpad.net/~mbp/launchpad/dkim/+merge/35985
[19:43] <deryck> mars, perhaps gmb or allenap.  But the code team should have some expertise there, too. abentley wrote BaseMailer, I believe.
[19:44] <mars> deryck, great. thank you for the help
[19:44] <deryck> np
[19:56] <mars> StevenK, I am going to save jml's review for you.  It moves code, so no need to balk at the line-count :)
[20:08] <abentley> rockstar, could you please review https://code.edge.launchpad.net/~abentley/launchpad/safe-delete-recipe-build/+merge/36195 ?  I think you'll like it.
[20:42] <rockstar> abentley, sure.
[21:09] <abentley> rockstar, how about this? https://code.edge.launchpad.net/~abentley/launchpad/upload-failure-email-log/+merge/36205
[21:35] <abentley> rockstar, mercy buckups.
[21:35] <rockstar> abentley, no problem.  Thanks for fixing that.
[21:59] <mwhudson> thumper: sorry for not reviewing branch-distro-avoid-scan yesterday, i don't know how i managed to forget about it
[21:59] <thumper> mwhudson: np, it isn't super urgent
[21:59] <thumper> not critical that is
[22:03] <abentley> thumper, incremental diff screenshot: http://people.canonical.com/~abentley/Screenshot-5.png
[22:04] <thumper> abentley: do we record the (from, to) revno pairs/
[22:04] <thumper> abentley: it'd be nice to see a heading on that block
[22:05] <thumper> perhaps saying something like "Incremental diff from revno 123 - 130"
[22:05] <thumper> maybe
[22:05] <abentley> thumper, no, we don't record revnos.  We record the revisions.
[22:05] <thumper> yay, another reason for the branch revision table
[22:05] <thumper> abentley: skype?
[22:06] <abentley> thumper, sure.
[22:07] <thumper> abentley: no headphones


[01:27] <Ampelbein> Hi! Could some member of bug-control please set bug 219593 to wishlist? thanks in advance.
[01:46] <hggdh> Ampelbein, it was already wishlisted. I set it to triaged, though
[01:46] <Ampelbein> hggdh: yeah. but for the record: it was not wishlisted as i posted here. ;-) thanks.
[01:47] <hggdh> :-)
[02:29] <Hobbsee> hggdh: repong.
[02:31] <hggdh> Hobbsee, reping
[02:31] <Hobbsee> hggdh: what did you want yesterday?
[02:33] <hggdh> Hobbsee, nothing, you were pointing your bubblegun at me (or my my general direction, which is the same, given that bubbleguns are known to have a wide range)
[02:33] <Hobbsee> hggdh: oh, fair enough :P
[02:33]  * Hobbsee covers hggdh in bubbles
[02:34]  * hggdh swims for safety
[02:34] <hggdh> huh, floats, methinks
[16:13] <Ampelbein> Hi! Could some member of bugcontrol please set bug #260659 to wishlist? Thanks in advance.
[16:17] <persia> Ampelbein: Why is that wishlist?  Is it not possibly Low, as forgetful users might fail to lock the workstation, andsomeone else could run `rm -rf /`without a password?
[16:17]  * persia is open to "Wishlist", but would like to hear a justification
[16:19] <qense> Ampelbein: I agree with the reporter of the bug in this issue. However, you could consider it as a small usability bug. It's surely not a wishlist, since it's a really small change.
[16:19] <qense> I would set it to Low.
[16:19] <Ampelbein> Just thought it might be wishlist because its just a change of default behavior.
[16:20] <Ampelbein> but after rethinking persia's comment i agree to low.
[16:20] <qense> Are you a member of the bugsquad?
[16:21] <Ampelbein> bugsquad yes, bugcontrol no.
[16:21] <qense> OK
[16:23] <qense> Do you want to confirm the bug and tell the user about that to collect bugs for your (possible) application to bugcontrol, or shall I do that?
[16:23] <Ampelbein> am just writing the confirmation.
[16:24] <qense> ok
[16:25] <Ampelbein> done
[16:25] <qense> nice
[16:25] <qense> I'm going to set the importance to low
[16:26] <qense> aargh!
[16:26] <qense> done, btw
[16:26] <qense> But the status was set to new in some way when I set the importance to low, so I had to set that again to confirmed
[16:27] <qense> That's really weird
[16:29] <Ampelbein> yeah, sometimes the webinterface seems to not do what i want it to do. but most of the time it just works ok.
[16:40] <persia> qense: I'm confused.  Why is it not wishlist because it's a small change?
[16:41] <qense> It's not something new, a new feature.
[16:41] <qense> It's a change of something that could be a security riks, or a usability bug
[16:41] <qense> (in its current state)
[16:41] <persia> Sure, but wishlist isn't only that.  If I say that I think the links in xchat-gnome ought to be human brown by default, surely that's also wishlist.
[16:42] <persia> In the case of this bug, I also think it's "Low", but I'm not sure that there aren't trivial wishlist bugs.
[16:42] <qense> I agree with that.
[16:42] <qense> Your example is a wishlist, because it doesn't cause problems when it isn't, just you not liking the colour.
[16:43] <qense> (that was probably a horrible sentence)
[16:44] <persia> Sure.  I think "wishlist" is for anything that doesn't actually cause a problem today.  This might be changling a colour, or it might be adding a feature, or it might be fixing a spelling mistake, or anything, really.
[16:46] <qense> That's my opinion too. :) I just used a bad argument.
[16:48] <persia> qense: With the right conclusion :)  I only pick on you for the benefit of those reading the logs.
[16:49] <qense> I don't mind :) It learned me to use better arguments when telling people why I agree with something and it was a good example to learn other people about the wishlist importance.
[16:50] <persia> qense: Excellent.  Sometimes I worry when I pick on people even when they got it right
[16:52] <qense> I have that too sometimes. You can't send body language over IRC
[16:52] <persia> Indeed.
[16:54] <Ampelbein> Another importance question: bug #256820 - i think this should get high priority, because it affects a small portion of users (those with the same card). I googled for the problem and found some similar reports. other opinions?
[16:55] <Ampelbein> (just using the chance seeing some of bugcontrol round here, if its not ok to ask such questions, please say so)
[16:55] <persia> Ampelbein: Asking such questions is one of the primary reasons for this channel.
[16:56] <Ampelbein> ok.
[16:56] <persia> I'm undecided between "Medium" and "High" for that one.  Lots of people who use that package doesn't have that hardware.  On the other hand, it could be considered to fall under "A problem with an essential hardware component".
[16:57] <persia> On the other hand, it only happens when watching movies, which makes me thing it's not quite as essential.
[16:57] <persia> Nor really that severe.  I guess it depends on whether one considers watching movies to be a core application.
[16:58] <Ampelbein> for the standard user i think watching movies IS important.
[16:58] <persia> (On a related note, why is "network card" considered a non-essential hardware component, and "laptop built-in wireless" considered an essential component?
[16:58] <Ampelbein> nothing worse than sitting pants down and having to debug xserver-crashes ;-)
[16:58] <persia> Heh.  Maybe so.
[16:59] <qense> About that related note: I think that nowadays you should consider networking as essential, since it's often the main reason why people buy computers and all updates are downloaded.
[17:00] <persia> qense: That's what I'm thinking.  Even on some of my laptops, I'm more likely to use the network adapter than wireless.
[17:00] <Ampelbein> back to the bug, i'd say though it affects a small number it renders ubuntu for them quite useless.
[17:01] <qense> Not completely, they still can check their email and flashplayers aren't affected, are they?
[17:01] <persia> Ampelbein: I disagree entirely that it renders Ubuntu useless, but I'll mark it High anyway, as Xv *really* ought work.
[17:03] <Ampelbein> depends. i'm trying to take my colleagues and friends as example. they want to browse, hear music and watch video. if one of this fails -> useless. but i agree that for the more technical interested users its not useless without video.
[17:04] <persia> Not just the technical folk.    These people almost never watch video, but text and sound are vital.
[17:19] <stefanlsd> When should the status be set to fix released?
[17:20] <qense> When the fix is accpeted in the repositories
[17:20] <qense> Launchpad should do that by itself, actually
[17:21] <stefanlsd> qense: Whats the diff between fix commited then?
[17:21] <qense> When the fix is comitted it still needs to be tested and accepted.
[17:22] <persia> Well, it's more complicated than that.
[17:22] <qense> There is a good explanation of both statuses here: https://wiki.ubuntu.com/Bugs/Status
[17:22] <persia> In the case of most projects on launchpad, "Fix Committed" means that the fix is in bzr, and "Fix Released" means that the fix is in a tarball.
[17:23] <persia> In the case of Ubuntu, "Fix Committed" is nearly meaningless.  It tends to be used to indicate that an upload happened, but maybe the upload is waiting for something, and it will be closed in 5 minutes (if the changelog included the appropriate syntax)
[17:24] <persia> Sometimes it's also used for some special processes.  I don't remember if the SRU process uses it right now, but at one point it was used to indicate a fix was in -proposed.
[17:25] <persia> Generally, for Ubuntu, don't use "Fix Committed" unless you have a special reason to do so, and someone instructed you to set it that way.
[17:27] <stefanlsd> persia: thanks for that. If i upload a debdiff and subscribe u-u-s. What status should i be setting?
[17:27] <stefanlsd> in progress?
[17:50] <persia> stefanlsd: Confirmed.  In Progress is when you are working on it.  There's a bug aganst LP about this, but it's not closed yet.
[17:50] <persia> Ideally there should be a "Needs Review" status to indicate we have a fix not yet committed.
[17:51] <persia> LP assumes that everyone who is capable of suggesting a fix is also a developer, which while true in a sense, doesn't really match the permissions configuration in launchpad.
[19:29] <stefanlsd> persia: thanks. makes sense
[19:41] <Ampelbein> Could someone from bugcontrol please set the importance of bug #85439 to low? I think it should be low because this only affects a minor part of the system.
[19:45] <Rocket2DMn> Ampelbein, done
[19:45] <Ampelbein> thx
[19:45] <Rocket2DMn> np
[20:07] <Ampelbein> Another Request: Bug #172343 - I think it could be set to status triaged, importance low. I reproduced the problem myself and verified with a non-ubuntu-version of ktorrent, then reported the bug upstream. Opinions?
[20:22] <persia> Ampelbein: Done.
[20:22] <Ampelbein> thx
[22:13] <Ampelbein> hi! i have a question about bug #259387 ? i'm unsure whether it deserves medium or high importance. i tend to medium because it causes moderate impact on a non-core application. What is your opinion on this case?
[22:14] <Ampelbein> Also, I think this could be set to triaged.
[22:22] <Ampelbein> Another request: Bug #260356 - Could some member of bug-control please set it to status triaged, importance low? I have reproduced the problem myself and submitted the issue upstream.
[22:31] <asomething> Ampelbein: I think you are right... I set the importances and marked as triaged. thanks for linking upstream!
[22:33] <Ampelbein> thank you.
[23:09] <bcurtis> anyone alive in here?
[23:30] <Ampelbein> bcurtis: me ;-)
[23:31] <bcurtis> Ampelbein, thank you.  Is there any way that traigers can set a bug as wishlist?
[23:31] <bcurtis> or just permissions issues u can't
[23:31] <Ampelbein> only members of bug-control can set wishlist
[23:31] <Ampelbein> you can post a request in here and someone will set it for you.
[23:32] <bcurtis> https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/260747
[23:32] <bcurtis> wishlist
[23:32] <bcurtis> how am i faster than ubottu?
[23:33] <bcurtis> and that was just me scrounging through bugs
[23:34] <Ampelbein> bcurtis: i usually write something like "can some member of bug-control please set status blah on bug #12345"
[23:34] <Ampelbein> so when later on someone looks in the channel he can act upon it.
[23:34] <bcurtis> ohhhhh, ok
[23:35] <bcurtis> Can someone please set status "wishlist" on bug #260747
[23:35] <bcurtis> ty :-)
[23:35] <Ampelbein> np
[23:36] <bdrung> bcurtis: done
[23:36] <bcurtis> bdrung: ty
[23:36] <bdrung> np
[23:36] <bdrung> easiest thing to do.
[23:45] <bcurtis> what gives you the permissions to do so? j/w
[23:46] <bdrung> bcurtis: you have to be member of ubuntu-bugcontrol
[23:46] <bcurtis> ahhh ok.
[23:47] <bcurtis> i've just recently started triaging bugs, so its all a new experience to me.
[23:49] <bdrung> if you like triaging and think you know how all these things work you can request to join
[23:51] <bcurtis> bdrung: the only thing i've done is take really old bugs and marked them for closure, and/or taken a package and tested the issue other users are having.. i've gone nowhere into the higher level triage.. i'd love to, but have no idea what to do and worry about being more of a nuisance than a benefit


[08:33] <dholbach> hiya
[08:34] <dholbach> are recipe pages timing out for anyone else?
[08:34] <dholbach> https://code.launchpad.net/~ubuntu-packaging-guide-team/+recipe/ubuntu-packaging-guide-daily
[08:34] <dholbach> https://code.launchpad.net/~uak-admins/+recipe/uak-daily
[08:35] <StevenK> https://bugs.launchpad.net/launchpad/+bug/1201984 ?
[08:41] <dholbach> ah thanks StevenK
[09:52] <dodiesis> Hi all!
[09:52] <dodiesis> I need some help in suing the launchpad http API
[09:52] <dodiesis> I have to retrieve the personal project of an user
[09:52] <dodiesis> the same list I have when I go at https://launchpad.net/~dodiesis/+related-projects
[09:52] <dodiesis> of course I need it not in html... but in json
[09:53] <dodiesis> I tried with
[09:53] <dodiesis> wget -qO- https://api.launchpad.net/1.0/~dodiesis
[09:53] <dodiesis> but it does not contains what I need
[09:53] <dodiesis> Any help please?
[09:53] <dodiesis> probably something like
[09:53] <dodiesis> wget -qO- 'https://api.launchpad.net/1.0/projects?ws.op=latest&user=dodiesis'
[09:53] <dodiesis> Tnx!
[09:54] <wgrant> dodiesis: There isn't currently an API to retrieve that information.
[09:56] <dodiesis> wgrant: ok thanks... I read the docs.. I thought I was missing something
[09:57] <dodiesis> I will hack the html then, thanks
[09:57] <wgrant> Launchpad deals with a lot of different types of data in a lot of different ways, and there sadly isn't an API for everything yet.
[09:59] <dodiesis> no prob! I already did the html way.. I'm just afraid that someone will change the html-css... and my work wont work anymore
[10:00] <dodiesis> anyway: do you have some better hints that parsing the html from the website?
[10:00] <dodiesis> s/that/than/
[10:00] <wgrant> That's the only place that information is exposed today, I'm afraid.
[10:00] <dodiesis> ok tnx!
[10:01] <dodiesis> tnx.. bye!
[10:45] <ArcticLight> Hello, I have a question about Ubuntu Launchpad bugs... Is it possible to A) mark a bug as a possible regression and/or B) note which versions of Ubuntu contain the bug?
[22:52] <slackner> is there any possibility to speed up builds a bit / increase priority? 12 hours of wait time for an update (actual build time <1min) that fixes a remote code execution is a bit too long at my opinion :-/
[22:58] <wgrant> slackner: Sure, do you have links to the builds in question?
[22:59] <slackner> wgrant: https://code.launchpad.net/~mqchael/+recipe/pipelight-release
[23:00] <slackner> wgrant: thx :O :)
[23:01] <wgrant> :)
[23:07] <ehoover> wgrant: can open source projects buy a commercial PPA?
[23:08] <wgrant> ehoover: Sure.
[23:09] <wgrant> ehoover: Activating a commercial subscription on an open source project is slightly awkward, though: you need to add "Other/Proprietary" to the licenses, at least until you activate the subscription.
[23:09] <ehoover> wgrant: is it still $250? and would this for sure bump our build priority?
[23:10] <ehoover> wgrant: interesting, so it won't let you buy the subscription until you set the license that way?
[23:12] <wgrant> ehoover: Private PPAs always get a very high score, and we can add per-PPA score bumps for public PPAs for projects with a commercial subscription.
[23:12] <wgrant> There's no price difference, and indeed, you can't easily trigger the subscription purchase without having a commercial-requiring license set on the project at the moment.
[23:14] <ehoover> wgrant: ok, right now we put our builds in a couple of different PPAs - i assume we'd either have to consolidate or pay that $250 twice, is that accurate?
[23:15] <wgrant> ehoover: No, multiple PPAs are fine as long as they're roughly related to the one project.
[23:16] <ehoover> wgrant: awesome, at the moment we're split out as "netflix-desktop" and "pipelight" - but we've mostly consolidated over into the "pipelight" team except for PPAs
[23:16] <wgrant> Either way is fine :)
[23:21] <ehoover> wgrant: so, how should we setup our projects so that once we do this that it recognizes they're connected?
[23:23] <wgrant> ehoover: I'll need to do it manually for this case. So poke me or email<EMAIL_ADDRESS>[23:25] <ehoover> wgrant: ok, i'll chat with everyone and probably come back to you tomorrow :)
[23:30] <DarkPlayer> wgrant: in case we would decide for this option, would it be possible to change the owner of a ppa to a team without changing the repository url?
[23:32] <wgrant> DarkPlayer: Uhh, not really but sort of. You'd have to copy the packages from the PPA into some temporary archive, delete the PPA, rename the old owner, create a team in its place, create a new PPA with the same name as the old one, then copy the packages back in. But that would end up with a different archive signing key.
[23:33] <wgrant> You could alternatively add a team as an additional uploader for the existing PPA.
[23:34] <DarkPlayer> wgrant: the second options seems much more feasible, didn't know that it is possible
[23:35] <wgrant> It's not well-advertised, but you can use the API's newComponentUploader method on a PPA.
[23:35] <DarkPlayer> wgrant: okay, i am already used to the launchpad api to collect statistics
[23:36] <ehoover> ooo, fancy :)
[23:40] <maxb> obscure detail - that permits uploads, but not package deletions (last time I checked)
[23:40] <wgrant> Ah yes, true.
[23:41] <ehoover> eh, we can just contact each other if a deletion is necessary - that's not as critical as getting the new builds up
[23:53] <maxb> I should also say: thanks very very much for netflix-desktop :-) - it amused me no end when it took me 5 minutes to get netflix working on Ubuntu, compared to taking my brother something like an hour of struggling with Silverlight on Windows :-)


[17:09] <rgh> Eickmeyer: do you happen to know an "8-bit" font, which I can embed in a plugin interface ?