[06:51] <lotuspsychje> can we assign bugs to a team without a project somehow?
[06:53] <wgrant> lotuspsychje: Can you explain in more detail what you're trying to do?
[06:53] <wgrant> Teams don't have dependencies on projects, so I'm not quite sure what you mean.
[06:55] <lotuspsychje> wgrant: our endgoal would be creating a team so we can see each others bugs
[06:56] <lotuspsychje> not focussed on the project or package
[06:56] <lotuspsychje> so different members of the team can add bugs to the team
[06:57] <lotuspsychje> we all have a LP account with existing bugs in it already
[06:57] <lotuspsychje> but is it possible to assign some bugs to the team?
[06:58] <wgrant> lotuspsychje: You can see a team's assigned bugs at https://launchpad.net/~TEAM/+assignedbugs, but that only finds bugs where the assignee is set to the team, not an individual in the team (since someone may be in many teams).
[06:59] <wgrant> For bugs that a team is interested in, you might consider subscribing the team to the bug and then using https://launchpad.net/~TEAM/+subscribedbugs
[06:59] <wgrant> Or using a bug tag (but that causes notifications, which isn't always desirable if you're working across many projects)
[07:00] <wgrant> But can you explain what you mean by "add bugs to the team"? What exactly is your use case?
[07:00] <wgrant> A bug isn't on or of or in a team.
[07:01] <lotuspsychje> wgrant: i just want a LP team with different admins, gathering each others bug in the team
[07:02] <lotuspsychje> wgrant: https://bugs.launchpad.net/~lotuspsychje this is mine for example
[07:02] <wgrant> lotuspsychje: That sounds like you've found a problem, gotten half way to an answer to the problem, and are now asking for the other half. But I don't know the original problem, so I'm not sure your half solution is the right way so it's hard to advise.
[07:03] <lotuspsychje> wgrant: i dont have an original problem or bug needing solved, i just want to know if i can add bugs to a team
[07:03] <lotuspsychje> https://launchpad.net/~ubuntu-discuss
[07:04] <wgrant> lotuspsychje: But to what end?
[07:04] <wgrant> It sounds like you want a group of people to be able to see a set of bugs that is chosen by that group of people.
[07:05] <lotuspsychje> wgrant: exactly
[07:05] <wgrant> That is the problem statement :)
[07:05] <wgrant> Not that you need to add bugs to a team.
[07:05] <wgrant> So, let's see.
[07:07] <wgrant> lotuspsychje: One approach that's used by some teams is to subscribe the team to relevant bugs, but that has the downside of causing email notifications to go to all the members (unless you set a contact address for the team, in which case notifications will go there)
[07:07] <wgrant> lotuspsychje: Also that's a very generic team name. Is there something more specific you can call it?
[07:08] <lotuspsychje> we dont have a problem getting mails from it
[07:08] <lotuspsychje> the team name isnt that important for us, what is important is we can see each others bugs in the team
[07:09] <wgrant> Right, but presumably there is some common purpose to these team members
[07:09] <wgrant> And "Ubuntu discuss" doesn't really explain that
[07:09] <wgrant> But it sounds like subscribing an appropriately named team to the bugs would solve your problem.
[07:09] <lotuspsychje> wgrant: well the crew will be mostly from #ubuntu-discuss
[07:09] <lotuspsychje> wgrant: and how do i subscribe a bug to the team?
[07:09] <wgrant> lotuspsychje: You subscribe a team to a bug
[07:10] <wgrant> On the bug, "Subscribe someone else"
[07:10] <wgrant> then search for the team
[07:10] <lotuspsychje> ah thats great!
[07:11] <lotuspsychje> exactly what we needed tnx alot wgrant
[07:11] <lotuspsychje> i owe you one
[07:11] <wgrant> Then the bug will show up on https://bugs.launchpad.net/~ubuntu-discuss
[07:11] <lotuspsychje> yep tested one
[07:11] <lotuspsychje> tnx mate
[13:15] <seb128> hey there
[13:16] <seb128> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1818584 got some files attached with what looks like cyrilic filenames, launchpad gives me no found errors when trying to open then, is that a known issue with maybe a workaround? (if not I'm going to ask the submitter to include them in a zip or rename them before uploading)
[13:26] <cjwatson> That's quite exciting.  The %3F is apparently not sufficient to encode the "?"; everything after that is interpreted as part of a query string.  I think this is wrong but it looks like maybe a frontend configuration bug.
[13:26] <cjwatson> Zip or rename is probably the only workaround for now.
[13:27] <wgrant> cjwatson: https://portal.admin.canonical.com/C56542
[13:27] <wgrant> https://bugs.launchpad.net/launchpad/+bug/983766
[13:27] <cjwatson> Ah yeah, I knew it rang a bell
[13:32] <seb128> cjwatson, wgrant, thx
[16:57] <blackswan> hi. i have a ppa on launchpad.net, but the signing key seems to have disappeared from keyserver.ubuntu.com. can anybody point me in the direction of fixing this? i had the exact same problem 2/22 and it then went away, i'm not sure if anybody determined the cause.
[16:58] <cjwatson> Which PPA?
[17:04] <blackswan> https://launchpad.net/~hermit
[17:35] <cjwatson> blackswan: Hmm, that links to https://keyserver.ubuntu.com/pks/lookup?fingerprint=on&op=index&search=0x166B6D7B59863696BB483868EADD5972943FF4C4 which is present for me, and indeed I can fetch the key from the keyserver.
[17:35] <cjwatson> blackswan: Perhaps some odd temporary problem?
[17:37] <blackswan> maybe, i'll check again.
[17:38] <cjwatson> I checked both of keyserver.ubuntu.com's IP addresses and they both seem to have it
[17:38] <blackswan> oh, the index works fine. it's exact search that's broken. sorry. i thought i had pasted that.
[17:38] <blackswan> https://keyserver.ubuntu.com/pks/lookup?search=0x166B6D7B59863696BB483868EADD5972943FF4C4&op=vindex
[17:39] <blackswan> sorry. i got distracted while asking.
[17:39] <blackswan> when it happened on 2/22, neither worked for me.
[17:41] <cjwatson> That looks OK to me as well?
[17:43] <blackswan> https://keyserver.ubuntu.com/pks/lookup&op=get&options=mr&exact=on&search=0x166B6D7B59863696BB483868EADD5972943FF4C4
[17:43] <blackswan> ok, third time's the charm.
[17:43] <blackswan> this link is still not working for me. the lookup?search link is now working for me, but was failing earlier.
[17:43] <cjwatson> That's a buggy URL.  Should be: https://keyserver.ubuntu.com/pks/lookup?op=get&options=mr&exact=on&search=0x166B6D7B59863696BB483868EADD5972943FF4C4
[17:43] <cjwatson> i.e. first & should be ?
[17:44] <cjwatson> Was that URL generated by something that we need to fix, or did you construct it manually?
[17:44] <blackswan> what failed for me was apt-add-repository. however, i manually constructed what i pasted here and may have made a transcription error.
[17:45] <blackswan> not in the search= paramter, though, that came from the ppa web page, i just changed the other bits
[17:46] <blackswan> wait, what?
[17:47] <cjwatson> OK.  Again works for me at the moment (both IP addresses), but the keyserver can be a bit flaky.  However, we don't actually maintain it here, we just make quite a lot of use of it.  #canonical-sysadmin or rt@ubuntu.com would be the place to take verifiable problems with the keyserver
[17:47] <cjwatson> Definitely worth retrying apt-add-repository though
[17:49] <blackswan> ok, yes, i made the ?->& transcription error, but, apt-add-repository was still not working for me. however, apt-add-repository just worked for me. so... i don't know what's going on.
[17:50] <blackswan> thx