On Thu, Mar 20, 2025 at 07:10:40PM +0500, Andrey Rakhmatullin wrote:
Neither 1.0.8-8 nor 1.0.8-9 are correct versions for an initial
upload, it should be 1.0.8-1.
Hmm. I was under the impression that I could not re-upload a new -1
version while still iterating on fixing lintian errors found by mentors.debian.net. But it seems that is possible. So I'll just
upload the new versions as 1.0.8-1.
On Thu, Mar 20, 2025 at 11:27:59PM +0500, Andrey Rakhmatullin wrote:wrote:
On Thu, Mar 20, 2025 at 03:29:15PM +0100, Roland Hieber wrote:
On Thu, Mar 20, 2025 at 07:10:40PM +0500, Andrey Rakhmatullin
Neither 1.0.8-8 nor 1.0.8-9 are correct versions for an
initial upload, it should be 1.0.8-1.
Hmm. I was under the impression that I could not re-upload a newPlease also note that you don't need to upload the package to
-1 version while still iterating on fixing lintian errors found
by mentors.debian.net. But it seems that is possible. So I'll
just upload the new versions as 1.0.8-1.>
mentors to see lintian output.
I thought so too at first, but the lintian output on mentors found
more issues compared to when I was running it on my own machine;
even after I updated my lintian version to unstable and used
--pedantic. Is there something else I'm missing?
On Fri, Mar 21, 2025 at 12:05:01PM +0500, Andrey Rakhmatullin wrote:
On Thu, Mar 20, 2025 at 11:29:10PM +0100, Roland Hieber wrote:
Neither 1.0.8-8 nor 1.0.8-9 are correct versions for an
initial upload, it should be 1.0.8-1.
Hmm. I was under the impression that I could not re-upload a
new -1 version while still iterating on fixing lintian
errors found by mentors.debian.net. But it seems that is
possible. So I'll just upload the new versions as 1.0.8-1.>
Please also note that you don't need to upload the package to
mentors to see lintian output.
I thought so too at first, but the lintian output on mentors
found more issues compared to when I was running it on my own
machine; even after I updated my lintian version to unstable
and used --pedantic. Is there something else I'm missing?
Yes, you are either not running it against the binary .changes orAh yes, I've got it now! I was looking for a --verbose option, but --display-info and --display-experimental do the right thing.
not passing arguments to enable additional message
types/severities.
The remaining issues are info and experimental only; is it a
requirement to fix those too? (For the
"very-long-line-length-in-source-file" I'm not even sure if they
can be fixed…)
I also think
"unused-license-paragraph-in-dep5-copyright gpl-2 or apache-2 [debian/copyright:8]" is a false-positive, and the license line in
the header stanza looks correct to me according to <https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ #license-field>.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 491 |
Nodes: | 16 (2 / 14) |
Uptime: | 107:11:41 |
Calls: | 9,684 |
Calls today: | 5 |
Files: | 13,725 |
Messages: | 6,175,496 |
Posted today: | 1 |