There was difficulty building on bullseye due to the older version of GCC
available: https://tracker.ceph.com/issues/61845
On Mon, Aug 21, 2023 at 3:01 AM Chris Palmer wrote:
> I'd like to try reef, but we are on debian 11 (bullseye).
> In the ceph repos, there is debian-quincy/bullseye and
> de
We weren't targeting bullseye once we discovered the compiler version
problem, the focus shifted to bookworm. If anyone would like to help
maintaining debian builds, or looking into these issues, it would be
welcome:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030129
https://tracker.ceph.co
Ohhh.. so if I read that correctly we can't upgrade either
debian or ceph until the dependency problem is resolved, and even then
we have to do both debian & ceph simultaneously That's an
uncomfortable situation in several ways...
On 21/08/2023 15:25, Josh Durgin wrote:
There was
Another option is moving to cephadm, then you can keep the same ceph
version and upgrade distro independently.
On Mon, Aug 21, 2023 at 9:19 AM Chris Palmer wrote:
> Ohhh.. so if I read that correctly we can't upgrade either debian
> or ceph until the dependency problem is resolved, and
Last few upgrades we upgraded ceph, then upgraded the O/S... it worked
great... I was hoping we could do the same again this time.
On 2023-08-21 12:18, Chris Palmer wrote:
Ohhh.. so if I read that correctly we can't upgrade either
debian or ceph until the dependency problem is resolved,
Hi,
On 21/08/2023 17:16, Josh Durgin wrote:
We weren't targeting bullseye once we discovered the compiler version
problem, the focus shifted to bookworm. If anyone would like to help
maintaining debian builds, or looking into these issues, it would be
welcome:
https://bugs.debian.org/cgi-bin
Hi,
On 21/08/2023 17:16, Josh Durgin wrote:
We weren't targeting bullseye once we discovered the compiler version
problem, the focus shifted to bookworm. If anyone would like to help
maintaining debian builds, or looking into these issues, it would be
welcome:
https://bugs.debian.org/cgi-bin
