Hi Gonzalo, On 2025-01-29 14:43:34, Gonzalo Silvalde Blanco wrote:
I checked some packages, went to the bugs section, selected “all,” and reviewed the reported issues. I found some that, if I understood correctly,I might be able to work on once I have a Salsa account.
to start working on improving packages does not require a salsa account. Only submitting improvements as merge requests requires a salsa account.
However, one of them caught my attention. The 'papi' package [1] only has one listed bug according to the Debian Bug Report [2]. In this bug, someone from the Debian team (or so I assume, based on their email) reports an issue on the 's390x' architecture—an architecture I discovered while reading the bug report. Another Debian team member responds: *"Upstream does not support s390x.And I won't accept any third-party patches for this."* Does this mean that this bug cannot be worked on, or am I misunderstanding something?
Given the constraints mentioned by the maintainer in #861765, the only fix I see is that the upstream authors start supporting s390x. I have not followed papi development. Hence I cannot judge how likely this is. Therefore I would recommend to look for other bugs where there is a higher chance to get improvements included.
[An alternative approach might be to make it explicit that s390x is not a supported architecture.]
Best regards Peter
[0] https://tracker.debian.org/teams/debian-hpc/ [1] https://tracker.debian.org/pkg/papi [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861765