Mathias Gibbens <gibmat@debian.org> writes: > On Mon, 2025-09-01 at 20:17 +0200, Simon Josefsson wrote: >> 2) Update all reverse build dependencies of golang-github-intel-go-cpuid >> and golang-github-klauspost-cpuid to use golang-github-canonical-cpuid >> instead. >> >> 3) Ask for removal of golang-github-klauspost-cpuid to use >> golang-github-canonical-cpuid. > > It really should be the opposite. :) golang-github-klauspost-cpuid is > maintained, while golang-github-intel-go-cpuid is dead upstream and has > been stuck migrating to testing for almost four years. > > I think it would be better to ask Canonical to switch to golang- > github-klauspost-cpuid rather than maintain a fork of a dead library. +1 I was merely explaining how this could be done in a hypothetical situation assuming both golang-github-klauspost-cpuid and golang-github-intel-go-cpuid were basically unmaintained upstream. Even if that were the case, I think that a "dead" project that has been around for 5+ years in Debian may be better to use than creating a new shiny fork with no real difference except that it has a new release. /Simon
Attachment:
signature.asc
Description: PGP signature