--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: libcpuid, cpu-x
- From: "Barak A. Pearlmutter" <barak@pearlmutter.net>
- Date: Tue, 13 May 2025 12:19:49 +0100
- Message-id: <CANa01BJ7h=sR=Q-EeeiRnbfzL8zS1eaAu08m1at7V-rwqMdALw@mail.gmail.com>
Package: release.debian.org
Dear Release Managers,
Version 0.8.0 of libcpuid supports arm/arm64 and I've uploaded a
version that includes those architectures, first to experimental to
check that it all went okay, then to unstable. I've also built cpu-x
5.3.1, which requires the libcpuid 0.8.0+, and which supports
arm/arm64. Again, first to experimental for some sanity checks, then
to unstable.
Although libcpuid is a shared library, it's pretty much a leaf
package: the only things that use it are cpu-x and nix-bin. And
although there was an so bump from 17 to 18, this was actually due to
an extremely minor API change: two structs were lengthened for
additional CPU information.
Aside from supporting ARM/ARM64, the new versions recognize some more
recent Intel and AMD CPU models.
So, I'm requesting that libcpuid and cpu-x be unblocked, because
basically the new versions broaden support to include extra
architectures, both a new family and new micro-architectures.
Cheers,
--Barak.
--- End Message ---
--- Begin Message ---
- To: 1105206-done@bugs.debian.org, "Barak A. Pearlmutter" <barak@pearlmutter.net>
- Subject: Re: Bug#1105206: transition: libcpuid
- From: Graham Inggs <ginggs@debian.org>
- Date: Fri, 15 Aug 2025 09:10:35 +0000
- Message-id: <CAM8zJQsLZQf9DvHvr0Wvxry12zBNOdSjyWU_vwREO-21hQ--dA@mail.gmail.com>
- In-reply-to: <aCo9sFMKor7TKVIj@ramacher.at>
- References: <CANa01BJ7h=sR=Q-EeeiRnbfzL8zS1eaAu08m1at7V-rwqMdALw@mail.gmail.com> <aCo9sFMKor7TKVIj@ramacher.at>
It looks like this is already done.
On Sun, 18 May 2025 at 20:09, Sebastian Ramacher <sramacher@debian.org>
> > Although libcpuid is a shared library, it's pretty much a leaf
> > package: the only things that use it are cpu-x and nix-bin. And
> > although there was an so bump from 17 to 18, this was actually due to
> > an extremely minor API change: two structs were lengthened for
> > additional CPU information.
libcpuid18 is in testing, and libcpuid17 is already removed, closing.
--- End Message ---