>>>>> "Lucas" == Lucas Nussbaum <[email protected]> writes:
Lucas> Hi, I'd like to open a discussion about using
Lucas> https://debaudit.debian.net data to gate testing
Lucas> migrations. The service is quite new, so this would likely
Lucas> need a long testing period, but I guess that it's probably
Lucas> better to open the discussion early.
Lucas> In short, debaudit currently includes two "checkers"
Lucas> (orig-check and git2dsc). orig-check ensures that the orig
Lucas> tarball in Debian matches upstream's. git2dsc ensures that
Lucas> the Vcs-Git repository matches the Debian source package.
Lucas> I think that it would make sense to block migration when
Lucas> packages regress (similar to what was implemented for
Lucas> reproducible builds, if I remember correctly) -- that would
Lucas> allow packages that fail in testing to still migrate, while
Lucas> still gradually improving the overall status.
I'm not convinced we have a consensus that using upstream tarballs is
the best practice.
I agree that we have a consensus that it is a best practice, but I think
that for example repacking an upstream git tag is also a best practice
or other workflows that are more git centered.
I don't want to have to get release team permission to get a migration
when I move from one of these best practices to another. I absolutely
support blocking migrations on unintended regressions if the false
positive rate is lower, but I think maintainers should have a way to
indicate a workflow change.
--Sam
