Re: [moin-devel] Debian packages (Re: moin2 release with core functionality)
On Tuesday, 12 September 2023 22:56:26 CEST Nicholas D Steeves wrote:
Paul, you're already forwarding patches, maintaining a package, and deploying it using a not-particularly-well-known apt_repo-in-Salsa method, so I think a Debian team context would be an asset for those times when--for example--you want to take a holiday :) Also would mean that sysadmins who use downstreams like Ubuntu would also be able to benefit from your work, and this seems like it would reinvigorate Moin usage in the wild.
The moin-team group was Steve McIntyre's initiative, and publishing out of Salsa is just a workaround at present, but I agree that something more substantial is probably needed. [...]
sbuild-debian-developer-setup is the easiest way that I know to get a clean chroot:
https://manpages.debian.org/bookworm/sbuild-debian-developer-setup/sbuild-d ebian-developer-setup.1.en.html
Using sbuild will also do some minor fuzzing (eg: packages must declare all needed dependencies and must only write to safe locations during the package build)
Yes, I currently use gbp as follows: gbp buildpackage --git-debian-branch=debian/master \ --git-upstream-tag='upstream/%(version)s' \ --git-builder=sbuild I overlooked that sbuild might provide tools that are usable enough for more general activities, and I might even try this out myself! Thanks once again for the suggestions! Paul
Hi Paul, Sorry for the belated response. Reply follows in-line: Paul Boddie <paul@boddie.org.uk> writes:
sbuild-debian-developer-setup is the easiest way that I know to get a clean chroot:
https://manpages.debian.org/bookworm/sbuild-debian-developer-setup/sbuild-d ebian-developer-setup.1.en.html
Using sbuild will also do some minor fuzzing (eg: packages must declare all needed dependencies and must only write to safe locations during the package build)
Yes, I currently use gbp as follows:
gbp buildpackage --git-debian-branch=debian/master \ --git-upstream-tag='upstream/%(version)s' \ --git-builder=sbuild
I overlooked that sbuild might provide tools that are usable enough for more general activities, and I might even try this out myself!
:) Well, you figured it out enough to get work done, which is something that some people have complained is too hard! Yes, by default sbuild uses "schroot", which takes care of the creation and destruction of clean chroots, with session management, since 2005. If you prefer real containers or a fully virtualised build machine (with LXC), gbp can also uses these. I prefer schroots, because they don't eat into the RAM as much as real containers of VMs ;)
Thanks once again for the suggestions!
You're welcome! I wish you success, Nicholas
On Friday, 22 September 2023 18:23:46 CEST Nicholas D Steeves wrote:
:) Well, you figured it out enough to get work done, which is something that some people have complained is too hard! Yes, by default sbuild uses "schroot", which takes care of the creation and destruction of clean chroots, with session management, since 2005.
About a decade ago, I was using pbuilder which still seemed like the default choice. Of course, all of this is just tooling around chroot, as are my own tools for having local distribution installations. I do think packaging is too hard. gbp does provide some automation for common tasks, but it needs to be used in precisely the right way or it can get in the way. And getting up to speed with the right way is not as obvious as it might be.
If you prefer real containers or a fully virtualised build machine (with LXC), gbp can also uses these. I prefer schroots, because they don't eat into the RAM as much as real containers of VMs ;)
Virtual machines and containers have their uses but are arguably excessive in many respects, and Debian's tooling works well enough with chroots, anyway. A lot of this seems so much better than what users of the Red Hat derivatives seem to put up with. Steady progress is being made, and I intend to contact debian-www and to file ITP tickets for the different packages involved. That will surely awaken groups who have an interest in certain packages. Thanks once again for the encouragement! Regards, Paul P.S. I should ask whether there is a way of pruning chroots under /run/schroot that seem to be created but not removed.
participants (2)
-
Nicholas D Steeves -
Paul Boddie