From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-user@pve.proxmox.com, uwe.sauter.de@gmail.com
Subject: Re: [PVE-User] ceph-volume binary missing in Quincy ceph-osd package
Date: Tue, 22 Nov 2022 11:15:54 +0100 [thread overview]
Message-ID: <1669112010.pbgzs6rswu.astroid@yuna.none> (raw)
In-Reply-To: <6c0e3f72-e303-a5ce-2c31-3aa0550d76a8@gmail.com>
On November 22, 2022 11:03 am, Uwe Sauter wrote:
> Am 22.11.22 um 11:00 schrieb Fabian Grünbichler:
>> On November 22, 2022 10:52 am, Uwe Sauter wrote:
>>> Hi all,
>>>
>>> looks like that ceph-volume is missing in the current Quincy ceph-osd package.
>>
>> it got its own package now: ceph-volume
>>
>> but it seems that is only recommended by ceph-osd, so depending on apt settings
>> it gets pulled in or not..
>>
>
> Hi Fabian,
>
> looks like the package metadata is wrong then as apt-file still thinks that it belongs to ceph-osd.
> And "pveceph install" didn't pull it in either.
well, it's simply incomplete. apt-file relies on separate, optional metadata
(Contents indices) that PVE repos don't have. so you get the result based on the
ceph-osd package from the main Debian repo ;)
>
> I'll install the package manually.
yes, that works. I'll double check whether there is some check missing (for new
`pveceph install` calls, the package is added to the set of packages to be
installed if quincy is selected) or if we can adapt some other dependency to get
it pulled in on upgrades.
prev parent reply other threads:[~2022-11-22 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 9:52 Uwe Sauter
2022-11-22 10:00 ` Fabian Grünbichler
2022-11-22 10:03 ` Uwe Sauter
2022-11-22 10:15 ` Fabian Grünbichler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1669112010.pbgzs6rswu.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-user@pve.proxmox.com \
--cc=uwe.sauter.de@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox