RFE: missing cephfs-mirror
Bug #2003704 reported by
Peter Sabaini
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ceph (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
We're not currently shipping the cephfs-mirror tool. This is a tool present in the upstream packaging (and other distributions) but which has been omitted in our offering.
The linked patch follows upstreams' packaging and creates a separate binary .deb for this program.
[Test Plan]
For testing, it should be possible to install the newly introduced cephfs-mirror .deb
[Where problems could occur]
As this patch introduces a completely separate package with a single binary and without any dependents, and does not touch any existing packages, risk to existing installations should be minimal.
Related branches
~peter-sabaini/ubuntu/+source/ceph:bug/2003704/lunar
Merged
into
~ubuntu-server-dev/ubuntu/+source/ceph:ubuntu/lunar
at
revision 6b6a3cab4617f8514b69ff08708b7da6703ad7b2
- Ubuntu Server Developers: Pending requested
-
Diff: 44 lines (+19/-0)3 files modifieddebian/cephfs-mirror.install (+1/-0)
debian/changelog (+6/-0)
debian/control (+12/-0)
~peter-sabaini/ubuntu/+source/ceph:bug/2003704/kinetic
Rejected
for merging
into
~ubuntu-server-dev/ubuntu/+source/ceph:ubuntu/kinetic
- Ubuntu Server Developers: Pending requested
-
Diff: 44 lines (+19/-0)3 files modifieddebian/cephfs-mirror.install (+1/-0)
debian/changelog (+6/-0)
debian/control (+12/-0)
~peter-sabaini/ubuntu/+source/ceph:bug/2003704/jammy
Rejected
for merging
into
~ubuntu-server-dev/ubuntu/+source/ceph:ubuntu/jammy
- Ubuntu Server Developers: Pending requested
-
Diff: 44 lines (+19/-0)3 files modifieddebian/cephfs-mirror.install (+1/-0)
debian/changelog (+6/-0)
debian/control (+12/-0)
description: | updated |
tags: |
added: verification-done-jammy removed: verification-needed verification-needed-jammy |
To post a comment you must log in.
Usually intorducing new packages is safe - as they cannot possibly regress since they have never been used or installed by anyone. Usual checks apply w.r.t. newly added build dependencies or runtime dependencies.