1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Processed: mono: FTBFS: Race condition in source-stamp target

    From Debian Bug Tracking System@21:1/5 to All on Thu May 22 19:20:01 2025
    Processing control commands:

    close -1 6.12.0.199+dfsg-6
    Bug #1106296 [src:mono] mono: FTBFS: Race condition in source-stamp target Marked as fixed in versions mono/6.12.0.199+dfsg-6.
    Bug #1106296 [src:mono] mono: FTBFS: Race condition in source-stamp target Marked Bug as done

    --
    1106296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106296
    Debian Bug Tracking System
    Contact [email protected] with problems

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Thu May 22 19:40:01 2025
    Processing commands for [email protected]:

    tags 1106296 patch
    Bug #1106296 {Done: Santiago Vila <[email protected]>} [src:mono] mono: FTBFS: Race condition in source-stamp target
    Added tag(s) patch.
    thanks
    Stopping processing here.

    Please contact me if you need assistance.
    --
    1106296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106296
    Debian Bug Tracking System
    Contact [email protected] with problems

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Santiago Vila@21:1/5 to All on Thu May 22 19:40:01 2025
    tags 1106296 patch
    thanks

    Maybe doing this instead:

    tar cJf ../mono-source.tar.xz -C .. $(basename $(pwd))
    mv ../mono-source.tar.xz debian

    would be enough to fix the problem.

    (But please double-check)

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Santiago Vila@21:1/5 to All on Thu May 22 22:50:01 2025
    El 22/5/25 a las 22:10, Antoine Le Gonidec escribió:
    And am now running the (seemingly endless) build to ensure it can complete with
    no surprise failure. If everything go well on this front, I’m going to follow
    with the reportbug release.debian.org step.

    Maybe Salsa CI could do that for you. There are some defaults about how long can a build take, but those values may be changed.

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Antoine Le Gonidec@21:1/5 to All on Thu May 22 22:20:02 2025
    Le Thu, 22 May 2025 20:11:30 +0200,
    Santiago Vila <[email protected]> a écrit :

    The relevant documentation is here:

    https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable

    In summary: an updated package for bookworm would have version 6.8.0.105+dfsg-3.3+deb12u1 and would be based on 6.8.0.105+dfsg-3.3. Use reportbug to ask stable release managers that they accept the package. In doubt, wait for approval before upload.

    On the salsa side, you would first locate the commit which matches the bookworm version, then create a branch called for example "bookworm" from it, cherry-pick the required change, add a changelog entry for 6.8.0.105+dfsg-3.3+deb12u1 and that's basically all.

    Thanks, between the developers-reference and your summary, I think I have everything I need.

    I already updated the salsa repo with a new debian/bookworm branch: https://salsa.debian.org/dotnet-team/mono/-/commits/debian/bookworm

    And am now running the (seemingly endless) build to ensure it can complete with no surprise failure. If everything go well on this front, I’m going to follow with the reportbug release.debian.org step.

    (Feel free to email me privately if you still have any doubt)

    I’d rather keep all that public, it might serve other people facing similar problems. Other people who have good chances to be future me ;)

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

    iHUEARYKAB0WIQSUsdxM90hewW6X7Jhja3j5HOuA2AUCaC+EyAAKCRBja3j5HOuA 2OnZAP4ocKHSU3AQV94RAR1dd11qmpsa1y7/fWgLr0LEIX7m0QEA/HsjBxN0PAps yCWwVd9OoOFD1s2EWS7PfS6bvjY1cgU=
    =F8S/
    -----END PGP SIGNATURE-----

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