This bug was fixed in the package ubuntu-report - 1.6.4
---
ubuntu-report (1.6.4) hirsute; urgency=medium
* Add new metric for glibc hwcaps (LP: #1922712)
-- William 'jawn-smith' Wilson Wed, 07
Apr 2021 16:52:26 -0500
** Changed in: ubuntu-report (Ubuntu)
Status: Fix
** Changed in: ubuntu-report (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
To manage notifications
I reviewed the branch and after some fixes, we +1 on it.
CI is passing, the new code is covered by the same amount of testing than the
rest of the code.
I did a run-try locally with ubuntu-report --show:
{
"Version": "21.04",
"OEM": {
"Vendor": "Entroware",
"Product": "Kratos",
Oh man, this is *late*. It's also quite a big change too - only
collecting new information, but still. But yeah, it's either now or in
21.10, so eh. If the desktop team +1's the PR and considers it 'safe' to
land, this has a +1 from the release team.
** Changed in: ubuntu-report (Ubuntu)
** Description changed:
+ FFe: We would like to collect that information with 21.04 to get a
+ better view of supported hardware for the new hwcaps. The risk should
+ be minimal, only adding an extra flag, and the server side collecting
+ the data can handle that, according to Didier.
+
+ pull
Thanks! I've added a trello card to review the PR in our trello backlog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
To manage notifications about
Seb, I have made a PR in the github repo. This PR also pulls in the
changes in version 1.6.3, which were previously not present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add
** Changed in: ubuntu-report (Ubuntu)
Importance: Undecided => Low
** Changed in: ubuntu-report (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
@William, thanks for working on a patch. The project is hosted on
github, is there a chance that you could set up a proper pull request on
https://github.com/ubuntu/ubuntu-report/pulls ? that would make
reviewing and merging easier than having to comment on a non trivial
patch in a comment on
The attachment "lp1922712.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if
Attached is a patch to add the hwcap metric to ubuntu-report.
** Patch added: "lp1922712.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+attachment/5485728/+files/lp1922712.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: ubuntu-report (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
To
it's much more work to build up a table for each cpu and map that to
some base level, and continue to update that table. just take that
information from the glibc hwcaps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: fr-1265
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwcaps
To manage notifications about this bug go to:
What is the point for that?
Ubuntu-report already collects the CPU string from which the hwcap can be
computed:
$ ubuntu-report interactive
This is the result of hardware and optional installer/upgrader that we
collected:
{
...
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "4",
15 matches
Mail list logo
