[2019-05-12 22:12] Vagrant Cascadian <[hidden email]>
> On 2019-05-13, Dmitry Bogatov wrote:
> > Hello. I am working on setting up CI for my packages, and one of them
> > fail "reprotest" phase with error: "FATAL: kernel too old".
> This is probably due to the kernel variation using "setarch", which will
> cause uname to report a 2.6 kernel, which is too old for some things...
> You should be able to disable it with --variations=+all,-kernel
Thank you very much. It did solve the issue. But while setting up CI for
another package, I encountered another issue:
install: fatal: unable to chown /tmp/reprotest.1SX4Bu/build-experiment-1/debian/qmail/var/lib/qmail: invalid argument
Package builds fine, both on CI and locally, and content
Dmitry Bogatov <[hidden email]> wrote:
> But while setting up CI for another package, I encountered another issue:
> install: fatal: unable to chown /tmp/reprotest.1SX4Bu/build-experiment-1/debian/qmail/var/lib/qmail: invalid argument
> Package builds fine, both on CI and locally, and content
I run into the exactly same issue (chown erroring iwth 'Invalid
argument') in the reprotest job of salsa-ci on my package mailman-suite:
chown: modification du propriétaire de
'debian/mailman3-web/var/lib/mailman3': Argument invalide
The package has 'chown list:list' for several files in debian/rules.
Trying to reproduce and debug it locally (with the help of Iñaki Malerba
and Agustin Henze - kudos to them), we found out that 'unshare -r' is
the problem here. Removing the '-r' argument to unshare makes the chown
work (and the package build) again.
I wonder whether it's a good idea to map the current user+group to root
in reprotest at all, as it definitely breaks chown at build time.
I'm looking forward to your (the maintainers') take on this ;)