• Re: rebootstrap status update for Loongarch

    From Johannes Schauer Marin Rodrigues@21:1/5 to All on Thu Nov 3 12:40:01 2022
    Quoting Zhang Ning (2022-11-03 11:45:17)
    6, gcc, binutils: need help, I don't know how to submit a patch to Debian toolchain-team, don't accept a poll request.

    7, m4, diffutils: need help, I don't know where is correct upstream[1][2], the patch[3][4] is for generated files, but Debian source has these files, thus how can I submit these patch to Debian source? these two packages don't have VCS.

    8, newt: need help, build failed without python. cdebconf and base-passwd are skipped.

    9, gmp: pass with manuall cross_build action, need help.

    10, libffi: need help, I don't know how to submit a patch to debian libffi, no VCS.

    In Debian, for packages having a VCS is still optional in 2022. And for those packages that do have a VCS, it up to them whether or not they enable receiving merge requests.

    What works for all packages in Debian is to send patches as a bug to the Debian bugtracking system. So just file a bug against the source packages in question and attach your patch to the bug.

    So you can either send all your patches to the bugtracker in the first place (because all source packages accept that way to submit patches) or (and that's what I do) first check if the source package is on salsa and receiving merge requests and submit the patch there and fall back to the bugtracker if there is no reaction to my merge request on salsa.

    Thanks!

    cheers, josch
    --==============66849407384635315=MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Description: signature
    Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmNjpn4ACgkQ8sulx4+9 g+E9ZA/9HYjfVQJat6nVTWZTIfvOaKWYX4ASzi3xiutNDfmzuufZR6eOJEz+KTT/ zFV7mAwQZkM4PvuqVhiTjnB+0R8IPmq4PGADoXRb9/ncEDI/Koad48DyNr1G4Std odIncGlKFGet6gI6xXhiJ3g7q9jHRSL+mqLMrCBl1YT1zZwvTt3yCds+KEzWfT4D EqeulJcJm/GZC3g8Q4Gzg2vLn+5OCNwNGj+s844nMgIaf6QrWEiIkiYpiB+7/17D pL+irfnVRVz0PTIWbhtWW5w4zCAJ2SiLdd/7HAcy/kcm3nPBowO2o+P7GMrH/Jg7 RGVwdRMoe/BNxSwQERtOIkN/Cg4o8nNJsQECtscGhZSaiDeuOuK4NqgE7PLuB1ZX hTjWXI8SV+S8mq1A6tXeSMXPAxuM9YZHPEZ7s7XYtVP1CVBQ7DbP6Ynd02r2H8PO QIZCAlIgiHXBFtKUh1QujCMxlwAz6TpoVBTjyM6/guhVnY9rpP8kbCO7hIVgWf11 kFBUSfTamhxaAj/IEXKl5DFdqYlGPX+ZARsPHMNc68hp9eylja4PLNEIR+KEDWUU LFaPYj6ALj8hl1gIBP6/WZOHm6g7B/h+dOZZ+qb9xT1hIkf3fP3djX/7zl/I5p9a wHwUWSqhx0DEHEKZoDLZFeDqH4q6MlfOFA+bkw4vYjGK+nGkjEY=
    =3EnE
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Wise@21:1/5 to Zhang Ning on Fri Nov 4 03:50:01 2022
    On Thu, 2022-11-03 at 18:45 +0800, Zhang Ning wrote:

    7, m4, diffutils: need help, I don't know where is correct
    upstream[1][2], the patch[3][4] is for generated files, but Debian
    source has these files, thus how can I submit these patch to Debian
    source? these two packages don't have VCS.

    It is best not to patch generated files, instead they should be
    regenerated from source (and probably removed from the upstream VCS).

    It is best not to patch embedded code copies, instead they should be
    removed from the upstream VCS and tarballs and the system version used.

    In Debian, the dh-autoreconf package is used at build time to
    automatically regenerate all files generated by autotools.

    In Debian, the stack-direction.m4 file is provided by gnulib, but I am
    not sure if that is the canonical place this file is maintained or if
    it is just yet another copy of this file..

    $ apt-file search stack-direction.m4
    gnulib: /usr/share/gnulib/m4/stack-direction.m4

    For m4, it seems Santiago Vila disabled dh-autoreconf in debian/rules,
    but there is no indication of the reason for that. So I suggest you
    test what happens when it is enabled and if the build succeeds and has
    no warnings in the log, then open a bug asking for it to be enabled.

    For diffutils, the same issue and solution applies.

    Another solution would be to ask the upstream m4 and diffutils projects to
    make new releases with updated configure and stack-direction.m4 files and
    then file bugs in Debian asking for package updates to the new releases.

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmNkfLwACgkQMRa6Xp/6 aaM1DBAAghShvdeuWk+GAZLVXI7l+lck5QEx9BO8ULOuzczfNdLpSV1Jjag2TTe0 /USeWt/DqX7AGZZm8XdVY3EWcUko8sItMtV6/tlkyWgQ9kNYwaH9zAaRiatzKrb/ JVQaWi6N4augkIYCR/XRuSNeADXaYB0L6uzK/00X+blqAkxRM7ji/2MBK3w9Lbtr dyZskVQeLhGz/xqiLHCOqt1SdJjLWXhVZBQ9Pvmy+w0r8IXwUGnwxwCj+LTDkbQU S879vmPiu/1KmwNj+IoTXfJxFlEIX1xsy88jFQ3wXvYsgZTNrPRJ6Rfgf5lr9APJ B9CxLdPRCIBxDPN4wsTDTmL1LzgZ4NSC2W1E86gMs7QYYqyNwWibePj12CYfYNcM g3e2YofJlpxyHzciDkaR2uKYJOE7uWMnFpAqI/3GgQ5jyv/EA1fCz4thJexJ3eSF One8jJ/tkv1WtZGjkZY/8Keoy4Qfjx/Xh+i0qOi9jGP9A7ydjqFJKSHHlSXxw4q2 klMSV5cMmqc1WOLcvpI1+hfKCjhcfKwY7DFlvn+OgT7JpqvZH2tRU4A41aGHbey+ yBd+475plE1rq3qVO/PnCah+8Tn3KgVmh7lC6h4SCdtj3kzGYI4frUVfIy2+uYLR F8JwsNlpcPcCTNnA7DDmM6WkQNPXx5dkz921OAA3FBMWb0CySYQ=
    =cYQz
    -----END PGP SIGNATURE-----

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