On Fri, Jan 30, 2026 at 05:27:25PM +0100, Lucas Nussbaum wrote: >... > > The current regressions can be browsed on: > https://debaudit.debian.net/orig-check/regressions/forky > and > https://debaudit.debian.net/git2dsc/regressions/forky > > There are currently 14 source packages that would be blocked because of > orig-check regressions, and 32 because of git2dsc regressions. > > I'm not aware of false positives (= AFAIK, regressions are real problems > that should be fixed). >...
- 700 - generated dsc differs │ -asn1c deb devel unknown arch=any │ - asn1c-doc deb doc unknown arch=all │ +asn1c deb devel optional arch=any │ + asn1c-doc deb doc optional arch=all That looks like a false positive? - 290 - uscan did not produce an orig tarball with matching name With the same tarball, caused by * update watch file to version 5 IMHO it would be bad if people were forced to upload "new" upstream tarballs for the same upstream code when debian/watch changed. - Sid result: 220 - uscan failed -- network error Testing migration shouldn't depend on network connectivity to the upstream location. How will debaudit handle it when an upstream location adds a JavaScript Challenge that is not yet supported by uscan? > Best, > > Lucas cu Adrian
