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


-- 
1034756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034756
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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_dpkg_architectures.3F

-- 
Regards,
--
  Bo YU

From 2e254fb802635742bb81f2e0a776e87c71360e1f Mon Sep 17 00:00:00 2001
From: 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
-- 
2.36.1

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
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

--- End Message ---

Reply via email to