Dear fellow packagers, Would anyone be able to provide an example of an sbuild config for building packages targetting experimental with working lintian, autopkgtest and piuparts support? Bonus points for a similar config offering supports for -backports!
For uploads targetting unstable, I have had packages building successfully for a long time with sbuild (via git-buildpackage), with lintian and autopkgtests automatically running as expected. I have sbuild configured so that mmdebstrap generates distribution tarballs if missing, and additional config via $unshare_mmdebstrap_extra_args to "echo" the experimental repo into the experimental tarball when created. Tarballs for both unstable and experimental are created successfully. The sbuild config uses the aspcud dependency resolver and recommended $aspcud_criteria for package builds. However, this resolver configuration doesn't appear to propagate to autopkgtest when testing an experimental package, and apt reaches a stalemate: "Unable to satisfy dependencies. Reached two conflicting assignments". When I migrated my sbuild config to mmdebstrap/unshare from schroot, local builds for unstable continued to work with little updating required to my sbuild config, and with no hardcoding of e.g. arch or distribution. However, despite having DEP-14 enabled in gbp.conf and building from a branch called debian/experimental, I have to manually include the experimental distribution name in the sbuild config otherwise the package gets built against unstable. Perhaps this is expected? Similarly, I have not cracked how to get autopkgtests working for experimental packages either, likely due to not yet handling the apt stalemate above. My deep gratitude if anyone can provide some secret sauce for packages targetting experimental (and backports) to clear up any misunderstandings that I have in my config. Cheers, Nick
