Felix Lechner pushed to branch master at lintian / lintian
Commits: 62000233 by Felix Lechner at 2019-08-27T18:12:11Z In check python, use new multi-facet facility. This check was already split. Execution branched in ::run. It can immediately use the new facilities for source and binary. Gbp-Dch: ignore - - - - - 4514fd42 by Felix Lechner at 2019-08-27T18:12:44Z In check gir, use new multi-facet facility. This check was already split. Execution branched in ::run. It can immediately use the new facilities for source and binary. Gbp-Dch: ignore - - - - - 95330537 by Felix Lechner at 2019-08-27T18:24:51Z In checks, allow new entry point 'always'; warn on outdated 'run'. Checks are now encouraged to split their tags by binary, source, etch. When that is not possible, a new entry point 'always' was created. It functions like the old entry point 'run'. It is always called, even when other components were run, which is reflected in the new name. Warns when checks use the old entry point 'run'. Not sure why the warning is only issued for the first offender. Perhaps it has something to do with the class Test::Builder::Module. This test would probably do fine using straight TAP. Gbp-Dch: ignore - - - - - 9a3662a9 by Felix Lechner at 2019-08-27T18:27:28Z Rename check script entry point 'run' to 'always'; do not invoke components on 'run'. This commit is intended as segue toward using 'always'. The old entry point 'run' is still executed, but no others are. Gbp-Dch: ignore - - - - - 896dc8dc by Felix Lechner at 2019-08-27T18:27:28Z Use entry point 'source' for all source-only checks. These checks do not need to use the more general entry point 'always'. Gbp-Dch: ignore - - - - - f933a613 by Felix Lechner at 2019-08-27T18:27:28Z Use entry point 'binary' for binary-only checks. These checks do not need to use the more general entry point 'always'. Gbp-Dch: ignore - - - - - f64d25fc by Felix Lechner at 2019-08-27T18:27:29Z Use entry point 'changes' for one changes-only check. This check does not need to use the more general entry point 'always'. Gbp-Dch: ignore - - - - - 86c0b488 by Felix Lechner at 2019-08-27T18:27:29Z Use entry point 'always' in all checks using 'run' and accepting multiple input processables. It would be nice to have these checks converted at some point. Tags issued only for sources and binaries should be separated out to their respective entry points. Gbp-Dch: ignore - - - - - 9528fe34 by Felix Lechner at 2019-08-27T18:27:29Z Adjust examples for new check entry point 'always'. Avoids a warning about using the old entry point 'run'. Gbp-Dch: ignore - - - - - 30 changed files: - checks/apache2.pm - checks/application-not-library.pm - checks/appstream-metadata.pm - checks/automake.pm - checks/binaries.pm - checks/changes-file.pm - checks/conffiles.pm - checks/control-file.pm - checks/control-files.pm - checks/copyright-file.pm - checks/cruft.pm - checks/dbus.pm - checks/deb-format.pm - checks/debconf.pm - checks/debhelper.pm - checks/debian-readme.pm - checks/debian-source-dir.pm - checks/description.pm - checks/duplicate-files.pm - checks/elpa.pm - checks/fields.pm - checks/filename-length.pm - checks/files.pm - checks/gir.pm - checks/group-checks.pm - checks/huge-usr-share.pm - checks/infofiles.pm - checks/init.d.pm - checks/java.pm - checks/manpages.pm The diff was not included because it is too large. View it on GitLab: https://salsa.debian.org/lintian/lintian/compare/36839e8af7b31ea045ae80102c5ec535192ffa7e...9528fe3406c84805d0c25450ac36ce6de0c01a51 -- View it on GitLab: https://salsa.debian.org/lintian/lintian/compare/36839e8af7b31ea045ae80102c5ec535192ffa7e...9528fe3406c84805d0c25450ac36ce6de0c01a51 You're receiving this email because of your account on salsa.debian.org.
