No way to cross-link specs across products

Bug #3552 reported by Daniel Silverstone
32
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Michael Hudson-Doyle

Bug Description

In some circumstances, such as when a project has multiple products split out, it would be useful to cross-link a spec dependency. For example, https://launchpad.net/products/malone/+spec/bugsubs is dependent on https://launchpad.net/products/launchpad/+spec/subscription-consolidation, but this dependency cannot be expressed in Launchpad.

It'd be nice to be able to say "Construct a roadmap aggregating this set of products/projects/whatever".

Related branches

description: updated
Dafydd Harries (daf)
Changed in launchpad:
assignee: nobody → sabdfl
status: New → Accepted
Revision history for this message
Robert Collins (lifeless) wrote :

Having a vocabulary for the spec selection would probably go a long way to making this bug solvable. I wonder if we need a spec for this?

Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

For the moment I would prefer to limit spec dependencies to the single product. When the system has been used and abused a bit more we can reconsider this.

Revision history for this message
David Allouche (ddaa) wrote :

It is meaningful to have a specification depends on another specification in a different product. For example the launchpad-bazaar/supermirror-smart-server spec should depend on bzr/smart-server.

Revision history for this message
Colin Watson (cjwatson) wrote :

I just ran into the same issue. I would like to make /distros/ubuntu/+spec/ubiquity-driver-updates depend on /products/soyuz/+spec/personal-package-archives, but at the moment I just have to note this in the status whiteboard.

Changed in blueprint:
importance: Wishlist → Medium
Revision history for this message
Eleanor Berger (intellectronica) wrote :
Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

> When the system has been used and abused a bit more we can reconsider this.
I think that now there are enough people who use Launchpad.

Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

A workaround for this is to register all blueprints on one project and then retarget them.

Curtis Hovey (sinzui)
Changed in blueprint:
assignee: Mark Shuttleworth (sabdfl) → nobody
importance: Medium → Low
tags: added: feature
Changed in blueprint:
assignee: nobody → Michael Hudson (mwhudson)
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
Changed in blueprint:
milestone: none → 10.09
tags: added: qa-needstesting
Changed in blueprint:
status: In Progress → Fix Committed
tags: added: qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui)
Changed in blueprint:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.