[elbrus at debian.org: Bug#905117: please make autopkgtest smarter than just /bin/true]

Sebastiaan Couwenberg sebastic at xs4all.nl
Tue Jul 31 23:13:57 BST 2018


Hi Ruben,

On 07/31/2018 11:57 PM, Ruben Undheim wrote:
>> I just resolved the bug by removing the autopkgtest.
> 
> Ok. Good! and Thanks!
> 
>> If you're willing to spend time to develop a more in-depth autopkgtest,
>> please do.
> 
> For me, it is more of a little interesting brain exercise to figure
> out how to do it.

Martin Pitt's documentation is a good reference:

 https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html

The change <-> test cycle is quite time consuming because you need to
build the source package every time and run the tests again. Especially
if your using chroots which take a lot of time to setup due to large
dependency chains.

Developing on an unstable system or VM where the required versions of
the dependencies are installed and not using a chroot is pretty much a
must if you want to avoid these large setup and times.

>> There are simply too many packages for which I'm the only active
>> contributor.
> 
> I hear you! You are doing an awesome job! Thanks for that!
> 
>> It also doesn't help that sbuild breaks every time the kernel is updated in
>> unstable and the system hasn't been booted with it yet, thanks to its aufs
>> dependency only building built for the latest kernel package.
> 
> On my side, I have never gotten sbuild up running. I am happy running
> pbuilder via cowbuilder :)

Getting sbuild up and running is not that difficult, the documentation
on the wiki was enough for me:

 https://wiki.debian.org/sbuild

It's very annoying that autopkgtest doesn't support cowbuilder as an
alternative to sbuild, forcing you to duplicate chroots instead of
reusing the chroots that are already used by git-buildpackage.

Kind Regards,

Bas




More information about the Pkg-grass-devel mailing list