Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.devel > #112294
| From | Otto Kekäläinen <otto@debian.org> |
|---|---|
| Newsgroups | linux.debian.devel |
| Subject | Builds that pass locally but fail on sbuild? (Re: Reviving schroot as used by sbuild) |
| Date | 2024-06-28 05:00 +0200 |
| Message-ID | <IUa09-67k5-9@gated-at.bofh.it> (permalink) |
| References | <ITT90-5VWu-1@gated-at.bofh.it> <ITIZX-5Pwp-9@gated-at.bofh.it> <IU1gd-61Ja-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Simon! > There are lots of options for doing this, some of which are listed in > <https://wiki.debian.org/SystemBuildTools#Package_build_tools>. > > All of these have the same problem as cowbuilder, pbuilder, and any > other solution that is not sbuild + schroot: it isn't (currently) what > the production Debian buildds use, therefore it is entirely possible > (perhaps even likely, depending on what packages you maintain) that your > package will build successfully and pass tests in your own local builder, > but then fail to build or fail tests on the buildds as a result of some > quirk of how schroot sets up its chroots, which is a worse-than-RC bug > making the package unreleasable. Could you point me to some Debian Bug # or otherwise share examples of cases when a build succeeded locally but failed on official Debian builders due to something that is specific for sbuild/schroot? I have never run in such a situation despite doing Debian packaging for 10 years with fairly complex C++ software targeting all archs Debian supports. Also as a member of the Salsa-CI team I don't recall ever seeing a bug report about something built on Salsa in a container successfully but failed to build on actual buildd. I am not dismissive of your claim - as a very senior DD you surely have those experiences - I am just curious to learn what those cases might have been. I could imagine that buildd builds fail if they the source was prepared in a non-hermetic environment that ran as root, or had network access, or if build environment was unclean and debian/control was missing some dependencies, but that is elementary hermetic build environment properties and not inherently something that *only* sbuild/schroot does. Related, you might want to take a peek at the source code of https://salsa.debian.org/otto/debcraft how it supports both Podman and Docker, and how it generates the 'root.tar.gz' equivalent container automatically based on debian/control and debian/changelog contents, and then runs the actual build as a regular non-root user in a container that has no network access. If I learn about other requirements for a hermetic build environment I would be happy to incorporate it. - Otto
Back to linux.debian.devel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Reviving schroot as used by sbuild Helmut Grohne <helmut@subdivi.de> - 2024-06-25 10:20 +0200
Re: Reviving schroot as used by sbuild Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-06-25 11:40 +0200
Re: Reviving schroot as used by sbuild Simon McVittie <smcv@debian.org> - 2024-06-25 15:10 +0200
Re: Reviving schroot as used by sbuild Andrey Rakhmatullin <wrar@debian.org> - 2024-06-25 15:30 +0200
Re: Reviving schroot as used by sbuild Faidon Liambotis <paravoid@debian.org> - 2024-06-25 15:30 +0200
Re: Reviving schroot as used by sbuild Antonio Terceiro <terceiro@debian.org> - 2024-06-25 17:30 +0200
Re: Reviving schroot as used by sbuild Russ Allbery <rra@debian.org> - 2024-06-25 18:40 +0200
Re: Reviving schroot as used by sbuild Guillem Jover <guillem@debian.org> - 2024-06-25 18:50 +0200
Re: Reviving schroot as used by sbuild Marco d'Itri <md@Linux.IT> - 2024-06-25 19:10 +0200
Re: Reviving schroot as used by sbuild Russ Allbery <rra@debian.org> - 2024-06-25 19:30 +0200
Re: Reviving schroot as used by sbuild Andrey Rakhmatullin <wrar@debian.org> - 2024-06-25 19:40 +0200
Re: Reviving schroot as used by sbuild Russ Allbery <rra@debian.org> - 2024-06-25 19:50 +0200
Re: Reviving schroot as used by sbuild PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2024-06-25 19:50 +0200
Re: Reviving schroot as used by sbuild Simon McVittie <smcv@debian.org> - 2024-06-26 18:10 +0200
Re: Reviving schroot as used by sbuild Simon McVittie <smcv@debian.org> - 2024-06-25 19:00 +0200
Re: Reviving schroot as used by sbuild Helmut Grohne <helmut@subdivi.de> - 2024-06-25 19:00 +0200
autopkgtest + podman user experience (Was: Re: Reviving schroot as used by sbuild) Gioele Barabucci <gioele@svario.it> - 2024-06-25 20:20 +0200
Re: autopkgtest + podman user experience (Was: Re: Reviving schroot as used by sbuild) Paul Gevers <elbrus@debian.org> - 2024-06-25 22:20 +0200
Re: Reviving schroot as used by sbuild Paul Gevers <elbrus@debian.org> - 2024-06-25 22:00 +0200
Re: Reviving schroot as used by sbuild Stefano Rivera <stefanor@debian.org> - 2024-06-26 18:40 +0200
Re: Reviving schroot as used by sbuild Simon McVittie <smcv@debian.org> - 2024-06-26 19:20 +0200
Re: Reviving schroot as used by sbuild Reinhard Tartler <siretart@gmail.com> - 2024-06-27 00:10 +0200
Re: Reviving schroot as used by sbuild Helmut Grohne <helmut@subdivi.de> - 2024-06-27 13:50 +0200
Re: Reviving schroot as used by sbuild Reinhard Tartler <siretart@gmail.com> - 2024-06-27 14:10 +0200
Re: Reviving schroot as used by sbuild Simon McVittie <smcv@debian.org> - 2024-06-27 16:00 +0200
Re: Reviving schroot as used by sbuild Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-06-27 17:30 +0200
Re: Reviving schroot as used by sbuild Simon McVittie <smcv@debian.org> - 2024-06-27 19:20 +0200
Re: Reviving schroot as used by sbuild Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-06-27 23:10 +0200
reproducible Debian containers exists today (Re: Reviving schroot as used by sbuild) Holger Levsen <holger@layer-acht.org> - 2024-06-26 11:20 +0200
Re: Reviving schroot as used by sbuild Bastian Venthur <venthur@debian.org> - 2024-06-27 11:00 +0200
Re: Reviving schroot as used by sbuild Simon McVittie <smcv@debian.org> - 2024-06-27 19:40 +0200
Builds that pass locally but fail on sbuild? (Re: Reviving schroot as used by sbuild) Otto Kekäläinen <otto@debian.org> - 2024-06-28 05:00 +0200
Re: Builds that pass locally but fail on sbuild? (Re: Reviving schroot as used by sbuild) Simon McVittie <smcv@debian.org> - 2024-06-28 12:00 +0200
Re: Builds that pass locally but fail on sbuild? (Re: Reviving schroot as used by sbuild) Richard Lewis <richard.lewis.debian@googlemail.com> - 2024-06-29 18:20 +0200
Re: Builds that pass locally but fail on sbuild? (Re: Reviving schroot as used by sbuild) Sam Hartman <hartmans@debian.org> - 2024-06-30 00:00 +0200
Re: Reviving schroot as used by sbuild Philipp Kern <pkern@debian.org> - 2024-07-01 09:20 +0200
Re: Reviving schroot as used by sbuild Simon McVittie <smcv@debian.org> - 2024-07-01 18:00 +0200
Re: Reviving schroot as used by sbuild Reinhard Tartler <siretart@gmail.com> - 2024-07-01 21:20 +0200
Re: Reviving schroot as used by sbuild Helmut Grohne <helmut@subdivi.de> - 2024-07-06 18:40 +0200
Re: Reviving schroot as used by sbuild Leandro Cunha <leandrocunha016@gmail.com> - 2024-06-25 20:00 +0200
Re: Reviving schroot as used by sbuild Sam Hartman <hartmans@debian.org> - 2024-06-28 15:10 +0200
Re: Reviving schroot as used by sbuild Helmut Grohne <helmut@subdivi.de> - 2024-09-14 12:00 +0200
Re: Reviving schroot as used by sbuild Simon McVittie <smcv@debian.org> - 2024-09-14 12:40 +0200
csiph-web