• Re: Bug#1100914: RFS: composefs/1.0.8-8 [ITP] -- mechanism for stacking

    From Soren Stoutner@21:1/5 to Hieber on Thu Mar 20 11:25:08 2025
    XPost: linux.debian.devel.mentors
    Copy: 1100914@bugs.debian.org

    On Thursday, March 20, 2025 7:29:15 AM Mountain Standard Time Roland
    Hieber wrote:
    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.

    That is correct. You cannot reupload a version number once it has
    entered Debian (unstable, experimental, etc.) However, you can and
    should reuse version numbers for successive uploads to Mentors, or if
    you have to resubmit something to NEW after is has been rejected.

    --
    Soren Stoutner
    soren@debian.org
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmfcXYQACgkQwufLJ66w tgNVIg//TGqOKfOUiORRE93QfGT26ZDYipR6/P+6P0ZU6Y1yHtmB07+QxI3tNA6b i+9l3N6CM4Fi5mkZDoCIYEBsOKIj/LHgk9w3dmLJcaO5mPpoawNopLkznSbG1VRW GWN7aA69iba9f0ZFgS55NJTEcvarnbSKRpApPADoIPdfUBkf/DJUBPrpUvx2BvWg XoQyXP9+Qlp12Z/TEe1LLZPaB9soM5x4upS48+yXrz8VmMWcTw+cEzduRwV8pcoy ZIfvu6K2EbedzWlqDjhKRQzHEW71QaqSTfSgQvJmAK5fBKyA8V0PDCJEcnPIagr2 pMlII6+2dQIDv+f3TH7nkH8HsBiGVT8eLN+jXG3sndiEYl6Mn72+t03sfn17cxGT RFplbdQr8l2Ron7Ns2bEHE+3zQNdXUfpe8LoMz2QyM3nPCiDS2rah8hUiXF+I3LF ggMh5JqNXjSlj6IIjxMnxk7moTiFzjOPp0Kbebmn3CahPpL9YsB0A/5lGiUOVS7M Dhu4CWtZpykRkv+ce6GxMx6BZlc9xaoArovbAdOuqO1RyyiNcB9EVsKMg+e0VKVB gpvy3E1WkSB0pn9QFURc7SjxIat9PLX6NfBNI68uOx9ngsTJaWM7fEiYzhHiMmQB Ar7IVBDRkWYUAGXKqQm5olm/pKAZSIDHCAazOwmSZxm0+2J0MUo=
    =YvxX
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Soren Stoutner@21:1/5 to Hieber on Thu Mar 20 15:46:41 2025
    XPost: linux.debian.devel.mentors
    Copy: 1100914@bugs.debian.org

    On Thursday, March 20, 2025 3:29:10 PM Mountain Standard Time Roland
    Hieber wrote:
    On Thu, Mar 20, 2025 at 11:27:59PM +0500, Andrey Rakhmatullin 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
    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?

    Try running the following:

    lintian -iIE --pedantic

    The output will include all the experimental and pedantic tags, which
    you are free to resolve if they are helpful to you and free to ignore
    if they aren't.

    --
    Soren Stoutner
    soren@debian.org
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmfcmtEACgkQwufLJ66w tgNQUg/+LiR9l1Z3VNdof8NyADz8euBk7gYegL7AFBH3LQpRbKl7GKx9aln62MRs yFw2U6Hjp3zu2i8Wz3BYXd1V0TtYgMNyAQwzdUN/23aistoHmWt9le9xS7ZAxOKL +hYy6/q6I8ReJ01MRhxzX28DjVL2rat+2gyoV5D1IypZBufBQcwM3WOtQO3tVNo7 Rq0577PvSY/5qD8JsL77LweyiQ8w2OxOBRBgr6NnKl7PRuAm/QggaSZC+sdoa2rX nhyOEGa7OK7vO5BM/2s5siMpBw3/qu0W0cJ/gUONWUm544J7AXXzltYLu/QiM5Ad WbzUZudg0Wj62UExn0GQVDXa/k09HO/bDpz9l79pKMoESlhKA8570z5jLWeZZK5D tzE2RFVXmRtHDnrpTEGyZUItaz2TZTsbyUEkk/sG6+41I62E3h75ENSXVTFETUGm 2unPtqSKp7fv8P52QH73nFPb/B2C2pSSHFMt80X6ykHECwRFj4KRpOKzamY1R3iB Sur18J3PjhAjiT3AVIKf6NYyIhBpSk10nXOm9q6tUEmxFAwbNvZ4CXAkbyLWvi/u 8IMZZyPf9f1e5l9tRrqT1Ap3mKJP2XRqwtENSglFIREecgmcuRX8yLlsDByu0mtg tPFS559RoR7MImGZ7IK3EefLM834exPXUVUOLcbaYXDsCQg23v4=
    =hnvj
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Soren Stoutner@21:1/5 to Hieber on Mon Mar 24 12:11:42 2025
    XPost: linux.debian.devel.mentors
    Copy: 1100914@bugs.debian.org

    On Sunday, March 23, 2025 3:05:17 AM Mountain Standard Time Roland
    Hieber wrote:
    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 or
    not passing arguments to enable additional message
    types/severities.
    Ah yes, I've got it now! I was looking for a --verbose option, but --display-info and --display-experimental do the right thing.

    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…)

    Only worry about them if they are an actual problem. For example. the very-long-line-length-in-source-file can sometime be caused by
    minified JavaScript, which would need an accompanying source. Other
    times, it is just a long line of perfectly fine source, so the tag can
    be ignored.

    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>.

    Even though this is covered in the documentation, I have never seen a
    package actually use a license field in the header stanza.

    https://salsa.debian.org/rohieb/composefs/-/blob/debian/latest/debian/ copyright?ref_type=heads#L8

    As such, lintian just might not be aware it is an option.

    --
    Soren Stoutner
    soren@debian.org
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmfhrm4ACgkQwufLJ66w tgOS7Q/+O6oZoY3QZQ953UzhG0MpDMXMJeFi4Bj5sEqAHuS7LdMb9iIgiU6TkUk7 HVE3uT2yeHGc8XQBbOKd+ERoQhe3znDaoG+XOxucuCIf7X6Ee8XYYJoSN93F9D+f QwAaTsxIw+VWxPdacKeaQ1SUJXcd5+9vQGLmmsBX6SczQGu9dauTsSYp/nGjek9F tHMXGttvPUJkndJVoeuIyrledrB+UG0pDX2XTnUtrznDeWfMhXV5qqMjZBKn8fUg IuOE59v1LvdtqxWrU16XT+5yTgAAsbXs2TfRpMxrsvqwjOpKOLTu3tag493/FEBf Dswn94yzQQZBWUJ8iE8rbx5VwSAsu4r+b4nBorW38oQVvltMlb+eBNg8txfLbW1I o6JInnsr+Z0AtdrWZyyAjXUhIJnpj0HgDOXeDcyCeqjtcM7eSkJhPeF5g2G13Fjl ebFmI1bm7ugYK8J8s8QMrtrV/4D64MhvNnSKT791F1j7fz9biuueiad+Xp2C/U2t HP/ppuGhiJpaDR9TN0fWhbTeh7PdeaC7sY45GfTLl6mKNKxlWoj1/b7MISuOVTk+ ZZgFWzqSg0tLp8L0wrSsLA1gbPYTEMtwsGfiETNjEK/c53MFBprq1XlQ8k7QTDTZ wX+dX9+yJIFbnKCbW07dKuH6d2LIwkBDfgOZS2EzUsgasIrfPQw=
    =iScm
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)