Felix Lechner pushed to branch master at lintian / lintian
Commits:
-
fa4f9645
by Felix Lechner at 2022-01-19T03:49:15-08:00
-
0b08b61a
by Felix Lechner at 2022-01-19T04:00:46-08:00
-
829deb4c
by Felix Lechner at 2022-01-19T04:02:13-08:00
3 changed files:
- t/scripts/tags/fields.t
- tags/a/ambiguous-paragraph-in-dep5-copyright.tag
- tags/v/very-long-line-length-in-source-file.tag
Changes:
| ... | ... | @@ -156,14 +156,12 @@ for my $tag_path (@tag_paths) { |
| 156 | 156 |
select $fh;
|
| 157 | 157 |
|
| 158 | 158 |
print "<!DOCTYPE html><head><title>$tag_name</title></head><body>";
|
| 159 |
- $html_output->describe_tags([$tag]);
|
|
| 159 |
+ $html_output->describe_tags($profile->data, [$tag]);
|
|
| 160 | 160 |
say '</body>';
|
| 161 | 161 |
|
| 162 | 162 |
select *STDOUT;
|
| 163 | 163 |
close $fh;
|
| 164 | 164 |
|
| 165 |
- print $html_description;
|
|
| 166 |
- |
|
| 167 | 165 |
my $tidy_out;
|
| 168 | 166 |
my $tidy_err;
|
| 169 | 167 |
|
| 1 | 1 |
Tag: ambiguous-paragraph-in-dep5-copyright
|
| 2 | 2 |
Severity: warning
|
| 3 | 3 |
Check: debian/copyright/dep5
|
| 4 |
-See-Also: Bug#652380, https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
|
|
| 5 |
-Explanation: The paragraph has a "License" and a "Copyright" field, but no
|
|
| 6 |
- "Files" field. Technically, this is a valid paragraph per the DEP 5
|
|
| 7 |
- specification. However, it is mostly likely a mistake.
|
|
| 4 |
+Explanation: The paragraph has both <code>License</code> and
|
|
| 5 |
+ <code>Copyright</code> fields, but no <code>Files</code> field. The paragraph
|
|
| 6 |
+ is technically valid according to the DEP 5 specification, but it is probably
|
|
| 7 |
+ a mistake.
|
|
| 8 | 8 |
.
|
| 9 |
- If it is a <code>stand-alone license paragraph</code>, the "Copyright"
|
|
| 10 |
- field is not needed and should be removed. On the other hand, if it
|
|
| 11 |
- is a <code>files paragraph</code>, it is missing the "Files" field.
|
|
| 9 |
+ If the paragraph is a "stand-alone" license paragraph, the <code>Copyright</code>
|
|
| 10 |
+ field is not needed. If it is, on the other hand, "files" paragraph, the
|
|
| 11 |
+ <code>Files</code> field is missing.
|
|
| 12 | 12 |
.
|
| 13 |
- Please note that while the "Files" field was optional in some cases
|
|
| 14 |
- in some of the earlier draft versions, it is mandatory in *all*
|
|
| 15 |
- <code>files paragraphs</code> in the current specification.
|
|
| 16 |
- .
|
|
| 17 |
- Lintian will attempt to guess what you intended and continue based on
|
|
| 18 |
- its guess. If the guess is wrong, you may see spurious tags related
|
|
| 19 |
- to this paragraph.
|
|
| 13 |
+ The <code>Files</code> field was at some point optional in some circumstances
|
|
| 14 |
+ but is now mandatory in all "files" paragraphs.
|
|
| 15 |
+See-Also:
|
|
| 16 |
+ Bug#652380,
|
|
| 17 |
+ https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
|
| ... | ... | @@ -25,7 +25,7 @@ Screen: autotools/long-lines |
| 25 | 25 |
Advocates: Russ Allbery <rra@debian.org>
|
| 26 | 26 |
Reason:
|
| 27 | 27 |
Upstream sources using <code>autoconf</code> have traditionally been
|
| 28 |
- distributed with generated <code>./configure<code> scripts as well as
|
|
| 28 |
+ distributed with generated <code>./configure</code> scripts as well as
|
|
| 29 | 29 |
other third-party <code>m4</code> macro files such as <code>libtool</code>.
|
| 30 | 30 |
.
|
| 31 | 31 |
When paired with <code>automake</code>, there may also be some intermediate
|