[02:53] <psusi> I thought that the opinion status was supposed to be different than invalid, but it seems to be hidden from all searches just like invalid.  am I not seeing a difference that is there, or shouldn't it show up when doing a text search for a bug, just not when listing open bugs in a particular package?
[02:55] <wgrant> psusi: There is no functional difference between Invalid, Opinion and Won't Fix, except that Won't Fix and Opinion can only be set by the bug supervisor.
[02:58] <psusi> wgrant, umm... shouldn't there be some difference?  I mean... why have them if there is no difference?  I would think that won't fix and opinion should show up when a user goes to report a new bug and searches to see if it has already been reported, but invalid wouldn't
[02:58] <wgrant> psusi: That is one of the big unanswered questions of the universe.
[02:58] <nhomar00> Hello
[02:58] <psusi> wgrant, let there be light ;)
[02:59] <nhomar00> I'm  using Lp topost a blueprint, and when i suscribe my team to the blueprint it is shown in "gray" and the tooltip is telling "No longer Uses Launchpad", somebody knows what it means?
[02:59] <wgrant> nhomar00: Which blueprint, and which team?
[03:00] <nhomar00> https://blueprints.launchpad.net/openerp-venezuela-localization/+spec/requisitos-fiscales-6.0
[03:00] <nhomar00> look suscribers
[03:00] <nhomar00> team: openerp-venezuela
[03:03] <nhomar00> Hello :-s - so difficult ¿?
[03:03] <wgrant> nhomar00: Have you tried refreshing the page?
[03:03] <wgrant> It looks OK for me now.
[03:03] <wgrant> But there is a problem here.
[03:05] <wgrant> Ahh
[03:07] <nhomar00> well
[03:07] <nhomar00> aomething is wrong
[03:07] <nhomar00> something
[03:07] <nhomar00> i refreshed
[03:07] <wgrant> The subscriber listing shows the wrong icon for teams.
[03:07] <wgrant> Sometimes.
[03:08] <nhomar00> mmm, BTW the tool tip is telling "no longer uses launchpad"
[03:08] <nhomar00> I'm worried about this
[03:08] <nhomar00> we use a LOT LP ;-)
[03:08] <wgrant> It's assuming that everyone in that list is a person, not a team.
[03:08] <wgrant> So it calls is_valid_person to determine which icon to show... and is_valid_person is False for teams.
[03:09] <wgrant> So it's nothing to worry about.
[03:09] <wgrant> Just a display bug.
[03:09] <nhomar00> ok ok ok ok ok
[03:09] <nhomar00> i got it
[03:09] <nhomar00> fine!
[03:09] <nhomar00> good answer
[03:09] <nhomar00> but must i publish a bug for this?
[03:10] <nhomar00> or it should be in roadmap already?
[03:10] <wgrant> Let me check if there's one already.
[03:14] <wgrant> Bug #516301
[03:25]  * lifeless makes it high
[03:29] <nhomar00> I can see
[03:30] <nhomar00> THANKS
[03:31] <cody-somerville> Weird. It doesn't say "no longer uses launchpad" and the icon isn't grayed out for me.
[03:32] <wgrant> cody-somerville: It depends on who you're logged in as.
[03:32] <wgrant> We have a caching bug.
[03:32] <wgrant> Something is populated is_valid_person incorrectly.
[03:33] <wgrant> (it should always be False for a team0
[15:59] <mwb_suse> hi.  is anyone around familiar with the api, specifically the PATCH calls?
[17:24] <Ampelbein> hi there! I'm having trouble accessing staging.lp.net via the python api, getting a "Unknown access token (c1gqlQh03cMKsfkm3V4T)." error. production works without problem
[19:18] <james_w> Ampelbein, are you trying to use a token that you got a few days ago?
[19:18] <james_w> Ampelbein, if so then delete it and get a new one
[19:18] <james_w> staging gets reset frequently, and so will forget about the tokens
[19:29] <Ampelbein> james_w: thanks, that was it. on  that note, the keyring entry is named "network password", it isn't immediately obvious that this is for lplib.
[19:29] <james_w> Ampelbein, you could file a bug about that
[19:31] <Ampelbein> will do
[19:32] <Ampelbein> thanks again ;-)
[21:53] <bdrung> maxb: regarding https://code.launchpad.net/~jd-team/jdownloader/trunk - the read-protected subtree is not needed. is it possible to ignore that subtree and continue the import?
[21:56] <maxb> bdrung: No. bzr-svn's design doesn't really permit such a thing
[21:58] <bdrung> maxb: and it can't be work around manually?
[22:34] <maxb> bdrung: Manually? There isn't really any scope for "manually" perturbing the results of a bzr-svn conversion
[22:36] <maxb> I guess you should talk to jelmer for a final word on this, but I think you're out of luck on this unless you contrive to set up a svnsync-ed mirror of the upstream, and then have bzr-svn import from that
[22:37] <maxb> If you do such a thing, it would be good to ensure the svnsynced svn repository has a different uuid to the original, since it will contain elided content
[22:39] <bdrung> maxb: no way for doing something for one time and then let the LP importer continue the imports?
[22:48] <maxb> I'd be shocked if you didn't run into errors due to data inconsistencies very quickly
[23:37] <blueyed> The vim code imports appear to not work anymore? https://code.launchpad.net/vim
[23:46] <spiv> blueyed: known bug
[23:46] <spiv> blueyed: oh, you don't mean package imports
[23:47] <spiv> Might still be a known bug of course!
[23:49] <spiv> Hmm, I don't see one filed.
[23:51] <blueyed> I wanted to use it for recipes, but when it's broken then there's not much reason..
[23:51] <spiv> Filed.
[23:51] <spiv> https://bugs.launchpad.net/bzr-hg/+bug/738498
[23:53] <blueyed> Thanks, spiv.