Multiple source packages in one repository
Bug #1693942 reported by
Nish Aravamudan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| git-ubuntu |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
Right now, we assume a repository is for a single source package. This is fine on the remote side (Launchpad), but locally, we might be dealing with a package rename (with sequential version numbers), etc. It should be easy to use the same repository for as many source packages as I want. This will require refactoring of the core repository, and possible adjustments to the namespaces and refspecs.
| Changed in usd-importer: | |
| importance: | Undecided → Wishlist |
| Changed in usd-importer: | |
| milestone: | none → future |
Revision history for this message
| Robie Basak (racb) wrote | #1 |
| Changed in usd-importer: | |
| status: | New → Fix Released |
| tags: | added: workflow |
To post a comment you must log in.
I would like tooling to never make the assumption that there is only source package. From this perspective I think this is done: I'm not aware of any regular tooling that breaks things if a user is doing this.
The exception is the importer. But that is expected to manage its own repository, and I don't think we'd ever fix it to handle this.
So I think this bug is done from the perspective of most tooling, and Won't Fix from the perspective of the importer. I think this was the original intention, so we can mark this Fix Released as the tooling side is fixed.