[05:47] <retrojeff> how do I view the build logs of a package inside a PPA?
[05:48] <retrojeff> I know its possible I just forgot how
[05:48] <retrojeff> what I want to find out is what git revision got built
[05:51] <wgrant> retrojeff: Visit the PPA, click "View package details", click the relevant package row, then select the architecture that you're interested in.
[05:51] <retrojeff> thanks
[06:00] <retrojeff> ok I found the build logs
[06:00] <retrojeff> what its not showing is where its getting the .tar.gz from
[06:01] <wgrant> retrojeff: Which PPA and package?
[06:02] <retrojeff> https://launchpad.net/~libretro/+archive/ubuntu/testing/+build/8302184
[06:02] <wgrant> retrojeff: That package was built from a recipe, so you can find the details of the source build under "Source package recipe build" on the right.
[06:03] <retrojeff> it was built fine and everything works I just wish to know which github revision it is
[06:03] <retrojeff> so I need to check the build log from
[06:03] <retrojeff> https://launchpad.net/~libretro/+archive/ubuntu/testing/+recipebuild/1020450
[06:04] <wgrant> Yes.
[09:26] <alkisg> Hi guys, the "assignee" entry in launchpad is often mis-interpreted by not-native english speakers as "the person that reported this bug", so they frequently assign it to themselves
[09:26] <alkisg> I wonder if a different word could be used there
[09:36] <alkisg> They usually know what "assign" means, but the "-ee" part is a bit harder to get, they're interpreting it more like "assigner" than "assignee".
[09:46] <maxb> The only other word frequently used in this context is owner, but that's not really any better
[09:52] <alkisg> Maybe a notice could help then, in the box where they're trying to change it... "This is the first time that you've assigned a bug to yourself, are you sure that you are planning to solve this bug yourself and that you want to notify others to stop working on it?"
[10:46] <guest123456> Hello. I accidentally changed the information type on a bug. Is there a way to undo that/delete that from the bug's history?
[10:50] <guest123456> I'm talking about this bug report: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1317949
[10:50] <ubot5`> Ubuntu bug 1317949 in sssd (Ubuntu) "Unable to see secondary groups in `id` listing" [Undecided,Confirmed]
[10:53] <faenil> morning :)
[10:53] <faenil> is it possible to add ssh keys to a team account?
[10:55] <wgrant> guest123456: You can set the information type back, but it's not possible to remove items from the history.
[10:55] <wgrant> faenil: That's not possible. What are you trying to do?
[10:56] <guest123456> wgrant: I see. Thank you!
[10:56] <faenil> wgrant: the usecase is, you have a laptop which can be access by many users, and you want to be able to allow branching repos from that laptop without having everyone copying their private ssh keys to it
[10:57] <wgrant> faenil: You'll need to create an account that represents that shared laptop.
[10:57] <wgrant> It's not possible to authenticate directly as a team.
[10:57] <faenil> wgrant: that means having a shared account though, which is a security risk
[10:58] <wgrant> faenil: How's that more of a security risk than having a shared key on the team?
[10:59] <faenil> wgrant: I don't know, I'm just looking for ways to do this. Having everything handled as team could mean that when people leave the team they lose access
[10:59] <wgrant> faenil: Couldn't they just take the shared SSH key from the laptop?
[10:59] <faenil> wgrant: yes
[10:59] <wgrant> That's the problem with sharing creds.
[11:00] <wgrant> You can't revoke just one person's access.
[11:00] <wgrant> Whether or not it's a shared user or a team.
[11:01] <faenil> wgrant: that's why I'm asking here, I hoped there was a more clever way of doing it using launchpad features
[11:01] <faenil> :)
[11:01] <wgrant> It's a fundamental aspect of shared creds, unfortunately.
[11:01] <wgrant> Not much LP can do about it.
[11:03] <faenil> wgrant: we just want to download repos, there should be a way of downloading public stuff without the need of any authentication, shouldn't there?
[11:03] <faenil> I understand uploading/committing..
[11:03] <wgrant> faenil: Oh, sure, anonymous access to public stuff is fine.
[11:03] <wgrant> Doesn't require any keys.
[11:04] <faenil> wgrant: cool!
[11:05] <faenil> wgrant: so for private data the only alternative is the shared account, right?
[11:06] <wgrant> faenil: Well, shared accounts are bad and everyone should really have their own, but if that's not an option for you for some reason then you probably no choice.
[11:07] <faenil> wgrant: how is copying private keys to a machine which can be accessed by anyone any better?
[11:08] <wgrant> faenil: It's worse.
[11:08] <faenil> :)
[11:08] <wgrant> But you haven't described your use-case thoroughly; it's difficult to advise on better solutions.
[11:08] <faenil> wgrant: I don't think I can add any detail :/
[11:09] <faenil> wgrant: but hey, as long as downloading with anonymous user is fine, I guess we can handle the other cases separately with different security measures
[11:10] <wgrant> faenil: If you just need to branch private code, you'd probably want a separate LP account with an SSH key and read-only access to the code in question.
[11:10] <wgrant> We use that for deployments of private code, for example.
[11:10] <wgrant> But someone copying the key to retain access to the code after they leave the company is always a risk
[11:11] <faenil> wgrant: yeah, so the shared account
[11:11] <faenil> wgrant: alright, thanks for the help :)
[11:13] <faenil> wgrant: yeah, there doesn't seem to be an ideal solution :/
[11:18] <faenil> wgrant: how can I disable ssh in launchpad config? it seems it forces ssh if it finds ssh keys in the default folder
[11:20] <wgrant> faenil: Remove the username config from ~/.bazaar/bazaar.conf and ~/.bazaar/authentication.conf
[11:22] <faenil> wgrant: I renamed the folder, but it still expects a username
[11:22] <faenil> as in, it uses the system login as username
[11:22] <wgrant> faenil: What are you running?
[11:23] <faenil> 15.10
[11:23] <wgrant> I mean the command.
[11:23] <faenil> bzr merge
[11:23] <wgrant> bzr merge what?
[11:23] <wgrant> If there's no username configured, lp: will use HTTP
[11:23] <faenil> the parent repo
[11:24] <wgrant> If there is a username, it will use bzr+ssh
[11:24] <faenil> there's no .bazaar folder atm, I renamed it
[11:24] <wgrant> Right, but what's the URL you're trying to merge?
[11:24] <wgrant> If it starts with bzr+ssh://, it will require an SSH key.
[11:24] <faenil> wgrant: I see ...> "Merging from remembered parent location bzr+ssh://"
[11:24] <wgrant> The http:// equivalent supports anonymous access.
[11:25] <faenil> the cached value is ssh, that's why
[11:25] <faenil> I'll change that
[11:26] <faenil> wgrant: done and working, thanks o/
[12:18]  * israelplanaguma la_juyis
[12:18] <israelplanaguma> ukelele
[13:35] <dobey> uhm ok
[13:45] <israelplanaguma> hello
[13:45]  * israelplanaguma la_juyis
[13:45] <israelplanaguma> ukelele
[13:46] <dobey> why do you keep saying that?
[13:50] <la_juyis> hi israelplanaguma - please try now