On adding private project to private team

Asked by Nadim Charara on 2017-07-26

Hi:

I have commercial subscription and created a private project at https://launchpad.net/etactista and need to have 2 private teams
( https://launchpad.net/~dell.ethertronics and https://launchpad.net/~ethertronics ) accessing the project code and bug. I could not find a way to do that. I had added them to the sharing list but still the project do not appear under the Related projects for each team. What do I need to do so the 2 teams can access the project privately?
Also I had a public ppa (https://launchpad.net/~ncharara/+archive/ubuntu/etactista) which I want to convert into private ppa for each team, do I have to delete the public one and create ppa for each team or there is other way around?

Thanks for your help

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
2017-07-27
Last query:
2017-07-27
Last reply:
2017-07-27
William Grant (wgrant) said : #1

Projects only show up in a team's "Related projects" section if they have a specific role in that project (eg. maintainer or bug supervisor). They can see the project as long as they're on the Sharing list.

When you say you want a private PPA for each team, do you mean that each team should be able to download, or each team should be able to upload? The standard approach would be to create a PPA on the private team that should have upload privileges, and then subscribe any other teams or users that should be able to install packages from it. It's not possible to make an existing public PPA private, and you probably don't want to use a PPA bound to your own personal username long-term anyway.

Nadim Charara (ncharara) said : #2

Thanks William: That answered my question for the project but I still have the following question on private ppa:

I have created a private ppa under one off the private team, then within that private ppa I added access to the 2 private teams( under manage access). I am member of those 2 private teams. But when I try to install the package I get the following error:

- When using apt-get update:
       E: Failed to fetch https://private-ppa.launchpad.net/teamxx-name/ppaxx-name/ubuntu/dists/zesty/main/binary-amd64/Packages 401 Authorization Required

-When I do sudo add-apt-repository ppa: teamxx-name/ppaxx-name I get

Cannot add PPA: 'ppa:~teamxx-name/ubuntu/ppaxx-name'.
ERROR: '~ teamxx-name ' user or team does not exist.

I must be missing something but cannot figure it out. As I said in my previous email I had this ppa as public I was able to install it successfully using my personal account. The private ppa is exactly the same as the public one. Simply using my personal account as member of the private team seems not sufficient to install the private ppa. What is required for a member of the team to do in order to install the private ppa?

Again thanks for your help,

Nadim Charara

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of William Grant
Sent: Thursday, July 27, 2017 3:09 AM
To: Nadim Charara <email address hidden>
Subject: Re: [Question #653647]: On adding private project to private team

Your question #653647 on Launchpad itself changed:
https://answers.launchpad.net/launchpad/+question/653647

    Status: Open => Answered

William Grant proposed the following answer:
Projects only show up in a team's "Related projects" section if they have a specific role in that project (eg. maintainer or bug supervisor).
They can see the project as long as they're on the Sharing list.

When you say you want a private PPA for each team, do you mean that each team should be able to download, or each team should be able to upload?
The standard approach would be to create a PPA on the private team that should have upload privileges, and then subscribe any other teams or users that should be able to install packages from it. It's not possible to make an existing public PPA private, and you probably don't want to use a PPA bound to your own personal username long-term anyway.

--
If this answers your question, please go to the following page to let us know that it is solved:
https://answers.launchpad.net/launchpad/+question/653647/+confirm?answer_id=0

If you still need help, you can reply to this email or go to the following page to enter your feedback:
https://answers.launchpad.net/launchpad/+question/653647

You received this question notification because you asked the question.
The contents of this transmission are Ethertronics Inc. Confidential and may contain proprietary or legally privileged information which may not be disclosed, copied or distributed without the express written consent of Ethertronics Inc. The information is intended to be for the use of the individual or entity named on this transmission. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this transmission in error, please notify us by telephone immediately so that we can arrange for the retrieval of the original documents at no cost to you. Alternatively, notify the sender by replying to this transmission and delete the message without disclosing it. Thank you

Colin Watson (cjwatson) said : #3

apt doesn't have your credentials so the system doesn't know who you are. You need to go to the PPA and use "Manage access" to grant yourself credentials that you can use for this; that'll give you sources.list lines containing your username and a token.

Colin Watson (cjwatson) said : #4

Oh, and if you've already done "Manage access", then you probably need to go to https://launchpad.net/~/+archivesubscriptions to retrieve the actual credentials here.

Nadim Charara (ncharara) said : #5

Thanks for your quick answer. I tried it and this works. Before I moved it to solved Can you let me know why I get the following warning when I do apt-get update:

W: GPG error: https://private-ppa.launchpad.net/teamxx_name/ppaxx_name/ubuntu zesty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D66279BB743D0616
W: The repository 'https://private-ppa.launchpad.net/ teamxx_name/ppaxx_name /ubuntu zesty InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Thanks,
Nadim Charara

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Colin Watson
Sent: Thursday, July 27, 2017 12:11 PM
To: Nadim Charara <email address hidden>
Subject: Re: [Question #653647]: On adding private project to private team

Your question #653647 on Launchpad itself changed:
https://answers.launchpad.net/launchpad/+question/653647

Colin Watson proposed the following answer:
Oh, and if you've already done "Manage access", then you probably need to go to https://launchpad.net/~/+archivesubscriptions to retrieve the actual credentials here.

--
If this answers your question, please go to the following page to let us know that it is solved:
https://answers.launchpad.net/launchpad/+question/653647/+confirm?answer_id=3

If you still need help, you can reply to this email or go to the following page to enter your feedback:
https://answers.launchpad.net/launchpad/+question/653647

You received this question notification because you asked the question.
The contents of this transmission are Ethertronics Inc. Confidential and may contain proprietary or legally privileged information which may not be disclosed, copied or distributed without the express written consent of Ethertronics Inc. The information is intended to be for the use of the individual or entity named on this transmission. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this transmission in error, please notify us by telephone immediately so that we can arrange for the retrieval of the original documents at no cost to you. Alternatively, notify the sender by replying to this transmission and delete the message without disclosing it. Thank you

Best Colin Watson (cjwatson) said : #6

You need to import the signing key for that PPA. Normally add-apt-repository would do this for you, but not in this case since it doesn't support private PPAs. Instead you need to do it by hand:

  apt-key adv --keyserver keyserver.ubuntu.com --recv-keys D66279BB743D0616

(You must be careful to check the key ID there against what Launchpad shows you for the relevant subscription under https://launchpad.net/~/+archivesubscriptions.)

Nadim Charara (ncharara) said : #7

Thanks Colin Watson, that solved my question.