lp:lazr-js 403s even though it isn't private
Bug #352701 reported by
William Grant
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Tim Penhey |
Bug Description
lp:lazr-js isn't accessible by non-privileged users, even though it appears in branch listings and can be browsed in Loggerhead - it's not a private branch.
Changed in launchpad-bazaar: | |
milestone: | 2.2.4 → 2.2.5 |
Changed in launchpad-code: | |
assignee: | nobody → Jonathan Lange (jml) |
status: | Triaged → In Progress |
assignee: | Jonathan Lange (jml) → nobody |
status: | In Progress → Triaged |
Changed in launchpad-code: | |
milestone: | 2.2.5 → 2.2.6 |
Changed in launchpad-code: | |
assignee: | nobody → Tim Penhey (thumper) |
Changed in launchpad-code: | |
status: | Triaged → In Progress |
Changed in launchpad-code: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'll bet that it's because there are merge proposals for private branches both to and from lp:lazr-js.
Operationally, those branches should be made public. Code-wise, we should not 403 on public branches with private merge proposals, I think.