microsoft / microsoft/winget-pkgs

Geekbench version detection is broken

Open
#128,554 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Matching Help-Wanted Issue-Task Package-Update
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Brief description of your issue

Part of the issue is that as of today (11/21/23) Geekbench 6.0 through 6.2.1 has a bug in the installer where it fails to register any version number with Windows. (tried to reach out to the developer multiple times about the installer bug but no response)

WinGet is stuck on an older version of Geekbench 6.1.0 when there are newer version as can be seen in the release notes page https://www.primatelabs.com/release/geekbench6/

Steps to reproduce
  1. winger upgrade -- include unknown
Expected behavior

Show the current version and able to detect it

Actual behavior

Stuck on an old version 6.1.0 (also partly due to a bug in Geekbench installer)

Environment
WinGet 2023.1122.238.480
Win 11 23H2 with all updates installed
Geekbench 6.2.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report with the listed WinGet upgrade command and compare the installed Geekbench version with the Geekbench 6 release notes. Determine which package metadata or version-detection entry is involved; done means WinGet identifies the current Geekbench version instead of remaining at 6.1.0.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.