Bug#1034756: marked as done (dpkg-architecture: Please add support for riscv32 arch)
"Debian Bug Tracking System" <[email protected]> Sun, 07 Jun 2026 01:09:02 +0000
| Newsgroups | gmane.linux.debian.devel.dpkg.bugs |
|---|---|
| Message-ID | <handler.1034756.D1034756.17807944581191479.ackdone@bugs.debian.org> |
This is a multi-part message in MIME format... ------------=_1780794542-1192672-0 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Your message dated Sun, 7 Jun 2026 03:07:34 +0200 with message-id <[email protected]> and subject line Re: Bug#1034756: dpkg: please add support for riscv32 has caused the Debian Bug report #1034756, regarding dpkg-architecture: Please add support for riscv32 arch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) --=20 1034756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D1034756 Debian Bug Tracking System Contact [email protected] with problems ------------=_1780794542-1192672-0 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at submit) by bugs.debian.org; 23 Apr 2023 15:20:08 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02 (2021-04-09) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-15.2 required=4.0 tests=BAYES_00,DIGITS_LETTERS, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, HAS_PACKAGE,MD5_SHA1_SUM,MURPHY_DRUGS_REL8,PGPSIGNATURE, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 29; hammy, 150; neutral, 70; spammy, 0. spammytokens: hammytokens:0.000-+--H*ct:application, 0.000-+--H*ct:protocol, 0.000-+--H*ct:micalg, 0.000-+--H*ct:signed, 0.000-+--H*ct:pgp-signature Return-path: <[email protected]> Received: from mail-pj1-x102b.google.com ([2607:f8b0:4864:20::102b]:55546) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim 4.94.2) (envelope-from <[email protected]>) id 1pqbVW-003g0i-GZ for [email protected]; Sun, 23 Apr 2023 15:20:08 +0000 Received: by mail-pj1-x102b.google.com with SMTP id 98e67ed59e1d1-24986c7cf2dso3230265a91.2 for <[email protected]>; Sun, 23 Apr 2023 08:20:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682263204; x=1684855204; h=content-disposition:mime-version:message-id:subject:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=k4mUxEDvy+Lc4nqQRa+yxlKp2uXwxp74aYJlmCp35DY=; b=KhbrsFnk7t0No/J3W4DKtAp8SrWmfpbI+xprYK3/Dv5utWGGjpyiFx/3QM4I/jSrln Nc+v3saL6FVuQqzMhaUo7J8BTeL6/eaUEmo1k05xaKW0WCm+ySPLZDOmGQmEtlS8w7Db YRivRssDh6+IWZ24mvPXY5RWkvoY4yj+9lXqokaw3qbajfe5CAeonv95+IrIQxe2hrzu QwUvZTy92gqKRzbE0od6XoOAtZhLlAH5oL1v7YwMBtKUQ3ExdSBIT0a2jzzMKZ10Cfsg DwxYkG0z4ga1eWN2XYLA3snbz+2Mckg8pUIiWH2kvy4QC4aZgMFaqFjnLOBrGBEh1mMD 8iGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682263204; x=1684855204; h=content-disposition:mime-version:message-id:subject:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=k4mUxEDvy+Lc4nqQRa+yxlKp2uXwxp74aYJlmCp35DY=; b=X1BVvwVWlp0KYWx133hi53DF9qpGT0Gwgb+Npjk7OIUCrcYonfQ9YJumNComryLd1u O8d9wVbAb8pCkuk6Hr168JFM055ia3Sto5Tn5SIhXQ6AxQGyFdKuq7qFThNHCHbruaWU yjRBzp8llpgxVJVjIwyvG6lUNIahQOGTWa0P+N4AwS8KLa2ct5xk0DvsauUKW69agFPv Bn0H7VgZPb10HXqStRLdqmBYcL3Xf7/iywMi7X0jsxD+YWrKxmTSuthpL5OjXwNmWi6q VvFSh1e94ZGsR8hHe16fK55b3cUdzd5ewuuab4FzCnisUXCNmHHsWlvmpLggyRstrMcM bZnQ== X-Gm-Message-State: AAQBX9fxs0FeeBhEZ+1OBygV6EMFfFEzMsThLY5KOP5BeussuMFsDHdR i/37Nfy25LiLBx3pyW+LeL+nneXbvh7xQA== X-Google-Smtp-Source: AKy350ZO5zi0gL0Q+67JA1NBNmrSzZQi0sJ/aIKtPycP5o0CrysgD6MwdiMc+r0Ivic1PT86LaaCQg== X-Received: by 2002:a17:90b:3a8d:b0:23e:f855:79ed with SMTP id om13-20020a17090b3a8d00b0023ef85579edmr11241027pjb.28.1682263203957; Sun, 23 Apr 2023 08:20:03 -0700 (PDT) Received: from debian ([47.242.94.15]) by smtp.gmail.com with ESMTPSA id f9-20020a17090a638900b00246fbf416dasm5133922pjj.14.2023.04.23.08.20.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 23 Apr 2023 08:20:03 -0700 (PDT) Date: Sun, 23 Apr 2023 23:20:01 +0800 From: Bo YU <[email protected]> To: Debian Bug Tracking System <[email protected]> Subject: dpkg: please add support for riscv32 Message-ID: <20230423152001.mdzcghhrzxkbp4fy@debian> X-Reportbug-Version: 11.6.0 X-PGP-Key: https://github.com/yuzibo/yuzibo.github.io/blob/master/_includes/subkey-signing-06-18-143E4BAF-pub.asc MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tc4doa6g7m5nlyoa" Content-Disposition: inline Delivered-To: [email protected] --tc4doa6g7m5nlyoa Content-Type: multipart/mixed; boundary="lum52zgvqb5j2kfw" Content-Disposition: inline --lum52zgvqb5j2kfw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: dpkg Version: 1.21.21 Severity: wishlist Tags: patch User: [email protected] Usertags: riscv32 Dear Maintainer, Currently riscv32 has been supported upstream for a while[0] and people can setup a riscv32 qemu with yocto[1], but it is time consuming. There is no distro to support riscv32 AFAIK until now however I think this will benefits users who want to setup riscv32 rootfs quickly if we support this. I thought the riscv32 has met the request[2] also. Please let me know if there is any issue. [0]: https://github.com/riscv-collab/riscv-gnu-toolchain#installation-linux [1]: https://github.com/riscv/meta-riscv [2]: https://wiki.debian.org/Teams/Dpkg/FAQ#Q._Can_we_add_support_for_new_d= pkg_architectures.3F --=20 Regards, -- Bo YU --lum52zgvqb5j2kfw Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0001-add-support-for-riscv32.patch" Content-Transfer-Encoding: quoted-printable =46rom 2e254fb802635742bb81f2e0a776e87c71360e1f Mon Sep 17 00:00:00 2001 =46rom: Bo YU <[email protected]> Date: Sun, 23 Apr 2023 22:22:47 +0800 Subject: [PATCH] add support for riscv32 Signed-off-by: Bo YU <[email protected]> --- data/cputable | 1 + 1 file changed, 1 insertion(+) diff --git a/data/cputable b/data/cputable index 7b1ee2c58..7c2c1c1c8 100644 --- a/data/cputable +++ b/data/cputable @@ -45,6 +45,7 @@ powerpc powerpc (powerpc|ppc) 32 big powerpcel powerpcle powerpcle 32 little ppc64 powerpc64 (powerpc|ppc)64 64 big ppc64el powerpc64le powerpc64le 64 little +riscv32 riscv32 riscv32 32 little riscv64 riscv64 riscv64 64 little s390 s390 s390 32 big s390x s390x s390x 64 big --=20 2.36.1 --lum52zgvqb5j2kfw-- --tc4doa6g7m5nlyoa Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEIcmhjYVTlmab0tjp+RVP3hQ+S68FAmRFTJcACgkQ+RVP3hQ+ S6+m9Q//Q7kqNMgkI/cH2IMuT5Col7tCmKxvFwD7vUPzUzUkaP9EBY8kRwJ5E8r+ d/YG0EU3nJfed1TOGIMaE9DAumbnzkTM5nyM1JggPSMXqYkl3zFbREfCXws7jKTJ LpMigVS/JdfiocEiWpnSITG3dxMdXeluT6BAXeO3n5w+qGP3sJVnd4II86BvLnSQ +l35pulSK1bOk7JCER43AccGd6cRORZIlGoaa6I2eB8MJDs6E+rIbNsSyI1ayEkr DUgAG3Ukwkzb/kT6o06Z9OiBgdzljdlGCnagjuO9cND3mzbT46GCv9vmc0t8d3zv DhsqcCrGGbXfPDZbL/EY7PzHOZlQRtmniTRWYvt80zIWrxsjSSfgTntXf00mXX0Y Oyj1FxI3djfgdGiORCeabb2+D0k+7yM9anSJKbxisQXb6ORB1MMNaKQcOEbLXNZP nxGup5CxVFFSdUM3IYK8KcMyLknyMTySzt4XNZsHBTh8oReHWs1sp+qFcsk1xdWj KiF0lmtAum/e4dsMH9OMKgZ0Nqz34GyjRF1c9VKWJPeuEHV7R80zF/9ukD4kLIu/ z8/UPRzkEJwjlt7p1aBvlampE6t3+6Zp19gZChRz8TPMahORlr5mLeTBMcw3+dml rkVT8ThsxxomMiW05seLScCt2GtwZ5kcfSt3JdHFnKNjdTNIXCY= =pse5 -----END PGP SIGNATURE----- --tc4doa6g7m5nlyoa-- ------------=_1780794542-1192672-0 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at 1034756-done) by bugs.debian.org; 7 Jun 2026 01:07:38 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 (2024-03-25) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-110.4 required=4.0 tests=ALL_TRUSTED,BAYES_00, DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FOURLA, FROMDEVELOPER,HAS_BUG_NUMBER,SPF_HELO_NONE,SPF_NONE, USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 35; hammy, 150; neutral, 76; spammy, 0. spammytokens: hammytokens:0.000-+--Hx-spam-relays-external:36ff, 0.000-+--H*r:36ff, 0.000-+--H*RT:sk:master., 0.000-+--H*RT:36ff, 0.000-+--H*RT:fe40 Return-path: <[email protected]> Received: from master.debian.org ([2001:41b8:202:deb:216:36ff:fe40:4001]:48276) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from <[email protected]>) id 1wW1zF-004zxD-2e for [email protected]; Sun, 07 Jun 2026 01:07:38 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.master; h=In-Reply-To:Content-Type:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description; bh=PVh+UFh4aSR3crwUeuUYRmkobSgGrfU86DGFlucTo7E=; b=REtc0MDA8GT3PE4XNhjxl+GWrQ psD6hT4wCKheL6wfh7WvA9tybAujfQivCFbAq+0EiVHjqSfWS+HqBm5gJh8tGf/G35IAoXHf/VwYd f3N7sUQx5oERqmrjTkK8lxYgmF+JDl54tNjhTvsu0AuQ3ifc1QHciXUGofGyQKMIkiURupHe3kPMU sctwcrGasS0+BVVxk0etHS9+rw4XzKnNQdNt2QdKY+KGkZAVmJaSAp9yU3Q0cGmfHLI+VeAWAU/px p9b6mDfVmOwwnMNdu0xBtGubemuxAlnsAY26A81A9m11veI1CWQVnjg7aQcjT3VHfn6tdwnywRcvH FuBKeM/A==; Received: from guillem by master.debian.org with local (Exim 4.96) (envelope-from <[email protected]>) id 1wW1zE-00CQpM-0j; Sun, 07 Jun 2026 01:07:36 +0000 Date: Sun, 7 Jun 2026 03:07:34 +0200 From: Guillem Jover <[email protected]> To: [email protected] Cc: Bo YU <[email protected]>, Jessica Clarke <[email protected]>, [email protected] Subject: Re: Bug#1034756: dpkg: please add support for riscv32 Message-ID: <[email protected]> Mail-Followup-To: Guillem Jover <[email protected]>, [email protected], Bo YU <[email protected]>, Jessica Clarke <[email protected]>, [email protected] References: <20230423152001.mdzcghhrzxkbp4fy@debian> <[email protected]> <20230425145252.oejcoxzsdudcyxej@debian> <[email protected]> <20230426162234.uizuy4pinacmvjev@debian> <[email protected]> <20230423152001.mdzcghhrzxkbp4fy@debian> <CAKq8=3LMwdk=4SSMGqZSBH3i8aJmdEQnJEOUiYy+jbtxyEzvDA@mail.gmail.com> <20230423152001.mdzcghhrzxkbp4fy@debian> <[email protected]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[email protected]> Hi! On Thu, 2023-05-11 at 03:51:32 +0200, Guillem Jover wrote: > On Sun, 2023-04-30 at 10:12:01 +0800, Bo YU wrote: > > If you talk about the baseline ABI according to hardware, yeah, this > > is still open. > > > Thanks for more background here. I thought this might lead to a wider > > discussion before solid ABI as pabs' suggestion. > > Given the ongoing discussion, where the ABI does not seem clear, and > there is even concerns about the existence of the port at all, I'll > defer this one for now, so that I can submit the current pending > unblock request. Once things are more clear from the RISC-V porters > side, then I'm happy to include this in git HEAD, and even propose > updating dpkg in stable release branches to add it there if necessary. There's been not much progress (that I know of) with this port, (in rebootstrap, etc), so as part of some bug triaging I'm going to be closing this now. While I also question the point of introducing new 32-bit ports at this point in time, please don't consider this closure something final. If there's ever renewed interest in pushing forward this port, and there are no concerns from the various items before the dpkg one in <https://wiki.debian.org/PortsDocs/New>, then please feel free to either reopen this report or create a new one. Thanks, Guillem ------------=_1780794542-1192672-0--