bzr: transition to breezy
Bug #1990186 reported by
Graham Inggs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bzr (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
| bzr-builddeb (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
| bzr-email (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
| bzr-fastimport (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
| bzr-git (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
| bzr-stats (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
| bzr-upload (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
| bzrtools (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
The binaries from source packages bzr and friends have been transitional dummy packages depending on their equivalents from source packages breezy (brz) and breezy-debian (brz-debian) since focal.
I think these can all be removed now.
There are several reverse-recommends on the old packages, but these are provided by the new packages.
Excerpt from src:breezy debian/control:
Package: brz
...
Provides: bzr, bzr-stats, bzr-email, bzr-upload, bzr-git, bzr-fastimport, git-remote-bzr
...
Excerpt from src:breezy-debian debian/control:
Package: brz-debian
...
Provides: brz-buildpackage
| Changed in bzr (Ubuntu): | |
| status: | New → Confirmed |
| Changed in bzrtools (Ubuntu): | |
| status: | New → Confirmed |
| Changed in bzr-upload (Ubuntu): | |
| status: | New → Confirmed |
| Changed in bzr-stats (Ubuntu): | |
| status: | New → Confirmed |
| Changed in bzr-git (Ubuntu): | |
| status: | New → Confirmed |
| Changed in bzr-fastimport (Ubuntu): | |
| status: | New → Confirmed |
| Changed in bzr-email (Ubuntu): | |
| status: | New → Confirmed |
| Changed in bzr-builddeb (Ubuntu): | |
| status: | New → Confirmed |
| tags: | added: foundations-todo |
| Changed in bzr (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in bzr-builddeb (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in bzr-email (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in bzr-fastimport (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in bzr-git (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in bzr-stats (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in bzr-upload (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in bzrtools (Ubuntu): | |
| importance: | Undecided → Medium |
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
| Changed in bzr (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| Changed in bzr-builddeb (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| Changed in bzr-email (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| Changed in bzr-fastimport (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| Changed in bzr-git (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| Changed in bzr-stats (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| Changed in bzrtools (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| Changed in bzr-upload (Ubuntu): | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
I think these should be filed as removal requests in Debian, and only if the Debian maintainer objects should we go through the effort of removing each of these and blacklisting them by hand in Ubuntu.