* Package name : bees Version : 0.7 Upstream Author : Zygo Blaxell bees@furryterror.org * URL : https://github.com/Zygo/bees * License : GPL-3+ Programming Lang: C++ Description : a btrfs deduplication agent Best-Effort Extent-Same, a btrfs deduplication agent. bees is a block-oriented userspace deduplication agent designed for large btrfs filesystems. It is an offline dedupe combined with an incremental data scan capability to minimize time data spends on disk from write to dedupe.
Am Samstag, dem 06.11.2021 um 21:32 +0300 schrieb Alexander GQ Gerasiov: I totally forgot to look if there's already an ITP filed when I did my one #1002036. How far are you with packaging? And do you want a Co-Maintainer? Though I'm only a DM not DD. I just did a first version of a Debian package avaible at: https://salsa.debian.org/fzielcke/bees/ Feel free to use anything of it. Regards, Felix
Please take a look on https://salsa.debian.org/debian/bees Will make the upload on x-mas holidays. (quite busy right now)
Hi, > Please take a look on https://salsa.debian.org/debian/bees Umm, could you please base your work on the upstream tree? Also, personal choice but IMHO checking debian/patches into git is … bah. Just apply them, and let the builder sort them out. > Will make the upload on x-mas holidays. (quite busy right now) That appears to not have happened. ;-) NB, please upgrade to current git master, as fbf6b39 fixes a somewhat-nasty bug. I have done all of the above: https://salsa.debian.org/smurf/bees/ If you don't have the time I'm OK with taking over, and/or co-maintain the package.
Hi! I've been looking at bees, created a debian package for it locally and thought about uploading it to debian. And found your repository on salsa for it, and the ITP bugreport too (#998697). There's also https://salsa.debian.org/smurf/bees/ . So now we've 3 packaging of bees for debian. Will you upload your packaging? Or should I process mine (which is at version 0.8, and looks quite similar to your work)? Or what? :) Thanks, /mjt
I looked at the software closely, and it seems like it needs quite a bit more love than it receives now. Upstream "startup wrapper" is quite strange, this is why Alexander rewrote it to a debian-specific thing, but this thing has its own issues. I asked upstream about this, and how whole thing should be used and how to package it and run it in a distribution. A discussion emerged, resulting in https://github.com/Zygo/bees/issues/244 . In that discussion I've added my view of how it should be done, together with a PoC script which can be temporarily used as a wrapper script for bees binary to play with it, and should gone once bees itself implements this functionality internally. Hopefully we'll end up with no startup script at all, - this is my goal here. So this is pending upstream review/comments for now, once we settle on something, it can be uploaded to debian and used by other distributions too. Since the original packaging as done by Alexander has now very little in common with the current packaging, I created a new repository (private for now) for bees debian packaging. This one also fixes some shortcomings of the Alexander's work, e.g. it is based on the upstream git repository branches/history instead of on contents of upstream tarballs without git history. Please stay tuned :) And if you want to help, I advise you to focus on https://github.com/Zygo/bees/issues/244 . Thanks, /mjt