Hi Ioannis, On Thu, Oct 18, 2018 at 02:46:14AM +0100, Ioannis Valasakis wrote: > I am interested in getting assigned this bug
There is no technical way to assign a bug - but readers of the bug log will know now that somebody is working on it. > and getting to know the process of creating an autopkg test :) Regards ioannis The general description of best practices is in Debian Wiki: https://wiki.debian.org/ContinuousIntegration/AutopkgtestBestPractices In the packaging template I've created for Debian Med packages there is also a boilerplate for an autopkgtest: https://salsa.debian.org/med-team/community/package_template/tree/master/debian/tests Please note: We usually install the run-unit-test script in the docs of a package to enable users to run the test as an example on the local machine. In the Debian Med policy https://med-team.pages.debian.net/policy/ you get general hints about packaging inside the Debian Med team. Writing an autopkgtest boils down to adding the debian/tests dir to the packaging. Hope this helps as first hints - keep on asking here if something remains unclear Andreas. -- http://fam-tille.de
