From 38a8f59a65a034d58bcccee875c45c21b57f4f82 Mon Sep 17 00:00:00 2001 From: Carlos Nihelton Date: Fri, 28 Nov 2025 18:23:59 -0300 Subject: [PATCH] Attempts to phrase the debian/watch paragraph more future proof By acknowledging that there are alternatives, mentioning the current modern one (git-buildpackage with debian/upstream/metadata) and allowing future standards to be considered without fear. Fixes #328 --- docs/MIR/mir-reporters-template.md | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) diff --git a/docs/MIR/mir-reporters-template.md b/docs/MIR/mir-reporters-template.md index 7a567f63..55f39684 100644 --- a/docs/MIR/mir-reporters-template.md +++ b/docs/MIR/mir-reporters-template.md @@ -268,14 +268,19 @@ TODO: - This package is minimal and will be tested in a more wide reaching TODO: solution context TBD, details about this testing are here TBD [Quality assurance - packaging] -RULE: - The package uses a debian/watch file whenever possible. In cases where -RULE: this is not possible (e.g. native packages), the package should either -RULE: provide a debian/README.source file or a debian/watch file (with -RULE: comments only) providing clear instructions on how to generate the -RULE: source tar file. -TODO-A: - debian/watch is present and works -TODO-B: - debian/watch is not present, instead it has TBD -TODO-C: - debian/watch is not present because it is a native package +RULE: - The package uses a debian/watch or debian/upstream/metadata files +RULE: whenever possible. The second options is the current modern alternative +RULE: for packages maintained with git-buildpackage. Consider whether that's +RULE: still true at the time of reporting your MIR. In cases where this is +RULE: not possible (e.g. native packages), the package should either provide +RULE: a debian/README.source file or a debian/watch file (with comments only) +RULE: providing clear instructions on how to generate the source tar file. +RULE: For clarity the TODOs below refer as "upstream watch file" to any +RULE: solution similar to the alternatives above which must be present in the +RULE: package so tools can detect and fetch new upstream releases. +TODO-A: - upstream watch file is present and works +TODO-B: - upstream watch file is not present, instead it has TBD +TODO-C: - upstream watch file is not present because it is a native package RULE: - The package should define the correct "Maintainer:" field in RULE: debian/control. This needs to be updated, using `update-maintainer`