Hi, thanks bartm for noticing the duplicate here.  Ouch.  There seems to
be two completely different upstream projects claiming the 'spike' name:

https://bugs.debian.org/1122131
https://github.com/spiffe/spike

https://bugs.debian.org/1040380
https://github.com/riscv-software-src/riscv-isa-sim

It would be okay by me to rename the first source package into
'golang-spike' or 'spike-go' or similar.  Alternatively the other
project could be renamed, to say 'spike-riscv-isa-sim'?

However both appears to provide /usr/bin/spike so things will not be
pleasant anyway.

Reading the '1040380' bug report it says: "So you can close this bug.".

While I'm not sure I agree with Jessica about the merits of the
spike-riscv-isa-sim -- why not allow people to package what they want?
-- there is no release since 2021, so maybe Jessica has a point here.

Maybe we should really close 1040380 and allow 1122131 to use the
'spike' name for now?  If there is ever progress on the riscv-isa-sim
Spike in Debian, I'm sure that can be resolved later on.

Any objections to me re-opening 1122131 and closing 1040380 instead?
Other thoughts?

/Simon

Attachment: signature.asc
Description: PGP signature

Reply via email to