From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/bees/
Date: Thu, 24 Jul 2025 21:25:00 +0000 (UTC) [thread overview]
Message-ID: <1753392274.0b7b1945633e1dbcab9501c53ae3022c06fa45c5.sam@gentoo> (raw)
commit: 0b7b1945633e1dbcab9501c53ae3022c06fa45c5
Author: Kai Krakow <kai <AT> kaishome <DOT> de>
AuthorDate: Sun Jun 29 09:56:01 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jul 24 21:24:34 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0b7b1945
sys-fs/bees: add 0.11
Signed-off-by: Kai Krakow <kai <AT> kaishome.de>
Part-of: https://github.com/gentoo/gentoo/pull/42796
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-fs/bees/Manifest | 1 +
sys-fs/bees/bees-0.11.ebuild | 109 +++++++++++++++++++++++++++++++++++++++++++
2 files changed, 110 insertions(+)
diff --git a/sys-fs/bees/Manifest b/sys-fs/bees/Manifest
index c5d207aa4f5f..5329a0306ce1 100644
--- a/sys-fs/bees/Manifest
+++ b/sys-fs/bees/Manifest
@@ -1,2 +1,3 @@
DIST bees-0.10.tar.gz 177509 BLAKE2B 269cf65d5250a07297dfaee6c0fd6bc25199d63fe423d63ce39df8bcdb64d6f8110a0e03d0dc7dc1b105a8886f2a9364da8878481546eaa8dbf3dc46abc569ed SHA512 77a4ae3d66430c2d9dc0351c16c60bad95f21e238fc00f5f5787f55929ba75ee25212ac4bb4a3e4a9419cec27bbcfd2987aa925a54bc2872609b38a698dbedc3
DIST bees-0.11-rc3.tar.gz 193475 BLAKE2B bb3d867843266ea5766bc079d6731c79bdc80b9df5cf08a3fa3361ecbe439002a396610b32d3875085c672cf891b55c61ccce7260d22a537d705c2a89b040e4c SHA512 66f42ff60ccdbd56a022d94370aa856453d016d69469c503a2182535b630e5b6d0d0fecf12574f1b23750942b48a9473414424cb9ad1954ef11a3b7a8e6ea1a6
+DIST bees-0.11.tar.gz 198122 BLAKE2B c5d42a1f8ed539c0923034b9e599859b1a10b67d8d77de0ba40bcaa45f373c5844be3967ec30673ff00191efc8318065394aea19025ca5cf8997d787802addd0 SHA512 1dee7f8f5f2043c63af4c812ca527403fce725b79bbcd6cfc7702307e87137b2d140b4f3368a1af662f290de4910b1f7b83d58a1b6acc304517b3e0297ed7f8f
diff --git a/sys-fs/bees/bees-0.11.ebuild b/sys-fs/bees/bees-0.11.ebuild
new file mode 100644
index 000000000000..c4cbb13e68c4
--- /dev/null
+++ b/sys-fs/bees/bees-0.11.ebuild
@@ -0,0 +1,109 @@
+# Copyright 1999-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit linux-info systemd toolchain-funcs
+
+DESCRIPTION="Best-Effort Extent-Same, a btrfs dedup agent"
+HOMEPAGE="https://github.com/Zygo/bees"
+
+if [[ ${PV} == 9999 ]] ; then
+ inherit git-r3
+ EGIT_REPO_URI="https://github.com/Zygo/bees.git"
+else
+ MY_PV=${PV/_/-}
+ MY_P=${P/_/-}
+ S=${WORKDIR}/${MY_P}
+
+ SRC_URI="https://github.com/Zygo/bees/archive/v${MY_PV}.tar.gz -> ${MY_P}.tar.gz"
+ KEYWORDS="~amd64 ~arm64"
+fi
+
+LICENSE="GPL-3"
+SLOT="0"
+
+DEPEND="
+ >=sys-apps/util-linux-2.30.2
+ >=sys-fs/btrfs-progs-4.20.2
+"
+RDEPEND="${DEPEND}"
+
+CONFIG_CHECK="~BTRFS_FS"
+ERROR_BTRFS_FS="CONFIG_BTRFS_FS: bees does currently only work with btrfs"
+
+pkg_pretend() {
+ if [[ ${MERGE_TYPE} != buildonly ]]; then
+ if kernel_is -lt 5 7; then
+ ewarn "With kernel versions below 5.4.96 and 5.7, the kernel may hold file system"
+ ewarn "locks for a long time while at the same time CPU usage increases when bees is"
+ ewarn "operating. bees tries to avoid this behavior by excluding very common extents"
+ ewarn "from deduplication. This has only a minimal impact on dedupe effectiveness."
+ ewarn
+ fi
+ if kernel_is -lt 5 4 19; then
+ ewarn "With kernel versions below 5.4.19, bees may trigger a btrfs bug when running"
+ ewarn "btrfs-balance in parallel. This may lead to meta-data corruption in the worst"
+ ewarn "case. Especially, kernels 5.1.21 and 5.2.21 should be avoided. Kernels 5.0.x"
+ ewarn "after 5.0.21 should be safe. In the best case, affected kernels may force"
+ ewarn "the device RO without writing corrupted meta-data. More details:"
+ ewarn "https://github.com/Zygo/bees/blob/master/docs/btrfs-kernel.md"
+ ewarn
+ fi
+ if kernel_is -gt 5 15 106; then
+ if kernel_is -lt 6 3 10; then
+ ewarn "With kernel versions 5.15.107 or later, there is a memory fragmentation"
+ ewarn "issue with LOGICAL_INO which can lead to cache thrashing and cause IO"
+ ewarn "latency spikes. This version ships with a work-around at the cost of not"
+ ewarn "handling highly duplicated filesystems that well. More details:"
+ ewarn "https://github.com/Zygo/bees/issues/260"
+ ewarn
+ fi
+ fi
+ if kernel_is -lt 5.7; then
+ ewarn "WARNING: Starting with bees v0.11, kernel versions below 5.7 (except 5.4 LTS)"
+ ewarn "are no longer supported. Using bees with such kernels may introduce kernel"
+ ewarn "crashes, system hangs, or data corruption. Please DO NOT runs bees with such"
+ ewarn "kernels. You will be using bees AT YOUR OWN RISK!"
+ ewarn
+ fi
+ fi
+}
+
+pkg_postinst() {
+ if [[ ${MERGE_TYPE} != buildonly ]]; then
+ elog "Bees recommends running the latest current kernel for performance and"
+ elog "reliability reasons, see README.md."
+ elog
+ elog "NEWS: bees now defaults to a much improved extent-based scanner. It is compatible"
+ elog "with your existing state database in \`\$BEESHOME\` but it may start over from the"
+ elog "beginning. However, it will keep the state of the old scanner, so you can switch"
+ elog "back and forth. To actually use the new scanner, use scan mode 4 or remove the"
+ elog "scan mode parameter from your init script. Requires kernel 4.14 or higher!"
+ fi
+}
+
+src_prepare() {
+ default
+ sed -i 's/ -Werror//' makeflags || die
+}
+
+src_configure() {
+ tc-export CC CXX AR
+ cat >localconf <<-EOF || die
+ ETC_PREFIX="${EPREFIX}/etc"
+ LIBEXEC_PREFIX="${EPREFIX}/usr/libexec"
+ PREFIX="${EPREFIX}/usr"
+ SYSTEMD_SYSTEM_UNIT_DIR="$(systemd_get_systemunitdir)"
+ DEFAULT_MAKE_TARGET=all
+ EOF
+ if [[ ${PV} != "9999" ]] ; then
+ echo BEES_VERSION=v${MY_PV} >>localconf || die
+ fi
+}
+
+src_compile() {
+ default
+ # localconf quotes leak in the systemd unit but are still needed for spaces
+ sed -i 's/"//g' scripts/beesd@.service || die
+}
next reply other threads:[~2025-07-24 21:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 21:25 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-23 12:08 [gentoo-commits] repo/gentoo:master commit in: sys-fs/bees/ Arthur Zamarin
2025-07-24 21:25 Sam James
2025-07-24 21:25 Sam James
2025-04-28 14:03 Sam James
2025-01-20 3:36 Sam James
2025-01-20 3:36 Sam James
2025-01-20 3:36 Sam James
2024-12-01 16:15 Sam James
2024-08-08 14:12 Joonas Niilola
2023-12-28 14:58 Sam James
2023-09-27 10:11 Joonas Niilola
2023-07-10 3:54 Sam James
2023-07-10 3:53 Sam James
2023-07-10 3:53 Sam James
2023-07-10 3:53 Sam James
2023-07-10 3:53 Sam James
2023-07-07 2:20 Sam James
2023-02-09 13:33 Joonas Niilola
2023-02-09 13:33 Joonas Niilola
2023-02-09 13:33 Joonas Niilola
2023-02-09 13:33 Joonas Niilola
2023-02-09 13:33 Joonas Niilola
2022-12-17 19:33 Sam James
2022-12-17 19:33 Sam James
2022-12-17 19:33 Sam James
2022-12-17 19:33 Sam James
2022-05-30 7:38 Sam James
2021-07-09 0:11 Ionen Wolkens
2021-07-07 18:47 Ionen Wolkens
2021-07-07 18:47 Ionen Wolkens
2021-01-04 13:56 Joonas Niilola
2021-01-04 13:56 Joonas Niilola
2020-11-07 20:04 Sam James
2019-11-30 7:50 Joonas Niilola
2019-11-30 7:50 Joonas Niilola
2019-11-28 16:34 Joonas Niilola
2019-11-28 16:34 Joonas Niilola
2019-06-18 5:40 Michał Górny
2019-06-18 5:40 Michał Górny
2018-10-01 8:01 Georgy Yakovlev
2018-10-01 8:01 Georgy Yakovlev
2018-09-29 20:08 Michał Górny
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=1753392274.0b7b1945633e1dbcab9501c53ae3022c06fa45c5.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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