For build debian packages I'm using this tools: schroot + sbuild + gbp-buildpackage
After bootstrap schroot environment and setup sbuild you can build package with command like this: gbp buildpackage --git-builder="sbuild --arch=amd64 --host=amd64 --chroot=debian-sid-amd64-sbuild --dist=sid --arch-any" --git-verbose --git-export-dir=/mnt/packages/build
In debian rules for compile ceph I'm using cmake+ninja (also it's
official dev way to compile ceph).
On 2023-04-21 22:34, sascha a. wrote:
Hey,
Thanks Igor, Thanks Dan.
I'm running "make-debs.sh", which creates debian packets.
But still there's no crimson-osd packet. Thats why im asking how to build those packets in debian format as well.
@Igor
Thanks for this repo, there's plenty of debian.install files, but there's no documentation on how to build this branch(?) as well.
What's the proper way of building those files?
cmake, ninja, make, bash script?
Ceph is full of thousand approaches, and it's pretty hard (at least for me) to understand what's the proper way of building things.The dokumentation also is not very consistent about the way of building things and in many places outdated..
On top there's not really a ci/cd file / pipeline or at least I didn't find any, to find the building steps...
On Fri, Apr 21, 2023 at 6:25 PM Igor Savlook <isav@xxxxxxxxx> wrote:
Hi.
For debian you can check this repo
https://github.com/isavl/ceph/tree/debian/master
On 2023-04-19 10:45, sascha a. wrote:
> Hello,
>
> There's so many ways to build ceph, from sources i'm pretty confused,
> so i need some help.
> I want to build regularly ceph from "main/master", to create debian
> packets out of it.
> I somehow have a solution which is working, but what's the best
> practice for doing this right now?
>
> On top of that, I didn't find ANY solution to build a "crimson-osd"
> packet out of the latest sources, i even spent hours on this, what's
> the correct way to do this?
>
> Thanks!
>
> Sascha
>
> _______________________________________________
> Dev mailing list -- dev@xxxxxxx
> To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
