• Bits from the Debian riscv64 porters

    From Manuel A. Fernandez Montecelo@21:1/5 to All on Sun Jul 30 23:30:01 2023
    Hello dear developers,

    As you may have noticed, the riscv64 architecture has been promoted in
    recent days from Debian-ports to the main Debian archive and
    infrastructure.

    As the Release Managers mentioned in their recent bits after the release
    of Bookworm [1], the expectation is to be in a position to ship Trixie
    with riscv64 support (subject to architecture qualification later in the
    cycle, as usual).

    Here are some highlights and a bit of information in a nutshell. For
    more details, refer to the wiki page [2].


    [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
    [2] https://wiki.debian.org/RISC-V


    Bootstrap in progress
    ---------------------

    As part of becoming an official architecture, the established procedure
    is to rebootstrap the port from a minimal set of packages. This process
    has just started, that's why the sid and experimental suites are almost
    empty, and many packages that were available before (when in
    debian-ports) now appear as "BD-Uninstallable" in wanna-build.

    The build daemons have already started to build packages for the
    official archive, and on our side we will concentrate on breaking build-dependency loops and fix FTBFS problems of packages in the
    critical paths.

    In order to make this process as smooth as possible, we would like to
    ask you:

    - Please help us by merging related patches that are available in the
    BTS promptly. They might not be directly related to riscv64, but can
    be a more general problem like a FTBFS due to the switch to GCC 13 as
    the default compiler.

    - Please do not to disable any features in your packages due to the
    unavailability of specific build-dependencies in riscv64, they should
    come back at some point in the next weeks.

    - Unless explicitly asked by the porters, please refrain from uploading
    manually built packages to the archive.

    - In general any help understanding, debugging or fixing
    riscv64-specific issues are welcome. You might want to use the
    porterbox for that (see below).

    During the bootstrap process, the debian-ports archive is still
    accessible; however, it will no longer receive updates, except (in very
    few exceptions) if it's to help with the rebootstrapping of the main
    archive.


    Build daemons
    -------------

    The current build daemons consist in 9 HiFive Unmatched boards,
    graciously hosted at OSUOSL [3] and MAN-DA [4].

    While this should be sufficient to keep up with the port, we are aware
    that the build time for some packages is quite important. We are
    actively working on acquiring next generation RISC-V hardware, it is
    however challenging to get hardware that matches the requirements [5], especially being supported by the mainline Linux kernel. However, we
    are optimistic that it will happen before the release of Trixie, and we
    already have identified a few promising candidates.

    Once the initial rebootstrap is done, the current build daemons will be
    handed over to DSA. Until then, the packages are now manually signed,
    so it's normal if they stay a few hours in "Built" state before getting "Uploaded".


    [3] https://osuosl.org/
    [4] https://www.man-da.de/
    [5] https://dsa.debian.org/ports/hardware-requirements/


    Porterbox
    ---------

    The current porterbox [6] is also based on an HiFive Unmatched board.
    It is available to Debian Developers to help debugging riscv64 issues.

    The porterbox includes two sets of chroots:

    - The chroot for the official archive are called 'sid' and
    'experimental' and are regularly updated, however a limited number of
    packages are currently available.

    - The original debian-ports archive chroots are called 'sid-dp' and
    'experimental-dp', and are no longer updated. However it can still be
    a valuable resource for debugging issues that were identified before
    the rebootstrap process started. They will eventually be removed.


    [6] https://db.debian.org/machines.cgi?host=debian-riscv64-porterbox-01


    Thanks
    ------

    We would like to take this opportunity to thank everyone who contributed
    to this significant milestone, including individuals (too many to
    mention) and Debian teams, as well as the organizations and companies
    that provided us with resources (by rough chronological order):

    MIT CSAIL
    SiFive
    Mullvad
    tetaneutral.net
    OSU Open Source Lab
    Microsemi (now Microchip)
    BeagleBoard.org Foundation
    RISC-V international,
    PLCT Lab (ISCAS)
    StarFive
    Metropolitan Area Network Darmstadt


    On behalf of the Debian riscv64 porters

    --
    Manuel A. Fernandez Montecelo <manuel.montezelo@gmail.com>

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

    iQIzBAABCgAdFiEEKo6AUFxIYphDDdCTf3YGpEXcqA4FAmTG1aEACgkQf3YGpEXc qA5S4w//Uo2mprz3gR1FaX/rAWCUix4UDi1KhSj3juCWQ3JMgxp2jetM/mOiLlZ+ tpr7ekdexBiDMQUpsIPDaZ0BmW74ppf/OVvdVzStr4K+eQw6+8+FSQrOE1+UYwqS Eg9tXdOmX5URwD9pSPo/TCUOE8U7kjUHHqLQC1W/UbdYeRgYK/Uxho3PhRPIaJu5 QfPbDnG+vBTLODrysdi72YmE5Uur1pDcXPUenLhonwlqL3q3GZn6YQ+s7Ay6pwpz 18YqQmhBCtgdo9ecYV4oP618QXPqMVl2fZTA6EYJ1ENLr/uC3qktjpCz6UPI73GI o2EcA90mfwgvAolji/U4EFHOVbUMzYeawN6SP4pCuitXszQTJRsJzXYEuI5jR2Y5 MQZsyFwpuF6Z3bPo5sTaE3AiOowLhN0L1f5Hx0r+L1qq1H9mDfSrqY3vD1LCZXBU ZQFtWH/nkVwITGLhpwkBodDrRGuqr94tfbFEpASJTXSh9WUgF+GVGpnU5oibvF+p jCemwGvixweYkVz0aDJrocpY14rq7vG6qupFriBnXonYU5k2G1B4CcCc+oUD4L2w jdLWN0/PCG/7PhVVuQgFdlub0vWysUVH1s18iLsJ2PTxTHJjJ05eFncGO3wDGtAi jxTpWJAdVb2W+MEVUn4UfyabclyIoteZsHcfoZZvSySAajchLZA=
    =2uM9
    -----END PGP SIGNATURE-----

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