branch privacy for packages (of projects with privacy enabled)
Bug #444498 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
It would be nice, when working on something that is embargoed..
it has some code that is 'upstream' [with private branches enabled], and
some code that is 'packaging' - branches of upstream with debian/ added.
The packaging branches are built in a private ppa using deb source
packages, but the right place to push those branches is
~team/ubuntu/
Is is possible to have branches pushed to that sort of url honour the
upstream private-branches settings?
jml says probably no and that I should file a bug.
Related to this bug is bug 347772 which asks for private branch support for package branches in their own right. They don't appear to be duplicates, though quite closely related.
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
| Changed in launchpad-code: | |
| status: | New → Confirmed |
| status: | Confirmed → Triaged |
| Changed in launchpad: | |
| importance: | Undecided → High |
| description: | updated |
| tags: | added: disclosure privacy |
| tags: | removed: disclosure |
To post a comment you must log in.
Yeah, this is certainly the case -- we have no support for private package branches currently.
It's probably not very hard to have the policy for a source package to follow that of a linked project -- look at lp.code.
I don't feel I can set the importance of this bug.