Hi Daniel, Dne 24.03.2024 (ned) ob 17:46 +0100 je Daniel Gröber napisal(a): > For building I use debuild or git-buildpackage+sbuild depending on context. > > I create chroots for sbuild with a wrapper script around > sbuild-createchroot using btrfs-snapshots for efficiency. > > To keep working on a package without having to reinstall the entire > dependency tree (as sbuild does) every time I tweak sbuild's > --anything-failed-commands or use schroot directly with a different chroot > profile setup which has my homedir mounted. > > I'm not sure all of that is the easiest setup these days. It certainly > needs "gardening" to keep it updated and in-sync between both my laptop and > workstation and I have been looking into alternatives. > Thank you for the valuable information. Currently i managed to reactivate my Salsa account, so that i am properly accessing your 'git-subrepo' repo. I was also able to setup debian-sid chrooted environment on my old Ubuntu laptop up to the point that i think i can successfully rebuild your current 'git-subrepo' project using the following commands after entering 'debian-sid' (schroot -c debian-sid): $ gbp clone --pristine-tar g...@salsa.debian.org:dxld/git-subrepo.git $ cd git-subrepo $ gbp buildpackage --git-pristine-tar-commit $ gbp buildpackage
I hope this is the correct procedure - i wasn't very confident seing 'sbuild' requireing another 'chroot' from within my original 'chroot', however it seems to be working now? My plan now is to fork your git-subrepo project, fetch latest upstream changes and rebuild the latest version. Would that be ok to get to the point, when a new ITP could have been issued? > https://github.com/lkhq/debspawn looks really neat and tidy but may be > untrodden ground. Could be workable if you feel up to trying it. I would > also be curios to know if it works well. See > https://github.com/lkhq/debspawn/issues/27 for some discussion between > ximion (the author) and josh (sbuild maintainer) how it compares against > sbuild. > I might try debspawn on another 'non-debian' 'nixos-based' machine, but this may not happen very quickly. As i understood, it only requires a systemd-based Linux. > When trying to understand how the build tools work and fit together keep in > mind that debuild (the traditional default) is nothing but a wrapper around > dpkg-buildpackage (which has a more extensive manpage) and passess most > options down as-is. git-buildpackage (by default) wraps debuild (or > optionally sbuild if you tell it to). sbuild allows building in chroots and > has a number of fancy options to make that easy. > > Aah, it's nice and warm in the jungle but simetimes you get lost between > all the vines~ > --Daniel I get lost a lot. Three years ago even so that i created new docker-pbuilder- based packaging tool: https://salsa.debian.org/spog/debdocker, just to get my head around debian ways. You can imagine that the project wasn't accepted very well on debian-devel:). thanks again, Samo
