From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"t.lamprecht@proxmox.com" <t.lamprecht@proxmox.com>,
"aderumier@odiso.com" <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH ceph 0/2] Build rocksdb in non-debug mode
Date: Tue, 9 Jan 2024 15:46:56 +0000 [thread overview]
Message-ID: <fcfb55d62b88fac36e51d3919dd55a35f0e50332.camel@groupe-cyllene.com> (raw)
In-Reply-To: <0db806b2-1d9e-4ed8-95f9-1e3889b2f26b@proxmox.com>
oh, I have tested with 17.2.7-pve1
I'll look for 18.2
-------- Message initial --------
De: Thomas Lamprecht <t.lamprecht@proxmox.com>
À: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Objet: Re: [pve-devel] [PATCH ceph 0/2] Build rocksdb in non-debug mode
Date: 09/01/2024 16:39:52
Am 09/01/2024 um 15:50 schrieb Alexandre Derumier:
> They are a bug in current debian packaging,
> where rocksdb is build in debug mode (not inheriting from cmake
> flags)
>
> patch 1 already exist in ubuntu
> patch 2 is a newer patch commited in ceph recently
>
> (patch 2 should be enough, but I'm keeping patch1 by security).
thanks, but this does not apply to the master branch of our ceph.git,
or
is this for an older release than Reef 18.2?
next prev parent reply other threads:[~2024-01-09 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 14:50 Alexandre Derumier
2024-01-09 14:50 ` [pve-devel] [PATCH ceph 1/2] patch: debian/rules: fix build type Alexandre Derumier
2024-01-10 9:18 ` Fabian Grünbichler
2024-01-09 14:50 ` [pve-devel] [PATCH ceph 2/2] patch: add 0022-rocksb-inherit-parent-cmake-cxx-flags.patch Alexandre Derumier
2024-01-09 15:39 ` [pve-devel] [PATCH ceph 0/2] Build rocksdb in non-debug mode Thomas Lamprecht
2024-01-09 15:46 ` DERUMIER, Alexandre [this message]
2024-01-09 16:12 ` Thomas Lamprecht
2024-01-09 16:16 ` DERUMIER, Alexandre
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=fcfb55d62b88fac36e51d3919dd55a35f0e50332.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.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