chore: align with go-fdo-server rpm builds

[mmartinv]

Build the go-fdo-client RPMs in the same way as go-fdo-server ones

[kgiusti]

Nice improvement!

[runcom]

lgtm (but probably pending the go-fdo bump + use of go1.25)

[runcom]

if you've rebased, the to0 call is now gone and tests need to be adapted unfortunately

 > GET /api/v1/to0/ea47cf1af24a1dfa8de77e599d25b175 HTTP/1.1
> Host: owner:8043
> User-Agent: curl/8.5.0
> Accept: */*
> 
< HTTP/1.1 404 Not Found
< Content-Type: text/plain; charset=utf-8
< X-Content-Type-Options: nosniff
< Date: Wed, 12 Nov 2025 16:01:27 GMT
< Content-Length: 19
* The requested URL returned error: 404
* Closing connection
[{"dns":"172.18.0.2","port":"8043","protocol":"http","ip":"172.18.0.2"}]

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {2: {'packages': defaultdict(<class 'dict'>, {'go-fdo-client-fedora': {'value': {'rawhide': ['Unknown field.']}}})}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command config validate or our pre-commit hooks for validation of the configuration.

[runcom]

tests still failing with

Nov 19 16:30:46 ip-172-31-18-144.us-east-2.compute.internal sh[3983]: Error: open /etc/go-fdo-server/owner.key: permission denied

[runcom]

The spec file used here doesn't have commit/version/release modified (it seems it's using the hardcoded commit value) see https://dashboard.packit.dev/jobs/propose-downstream/22467

[mmartinv]

Yeah, it looks like fix-spec-file does not apply to propose-downstream action, we need to modify the commit hash in the post-upstream-clone or pre-sync hooks. See: https://packit.dev/docs/configuration/actions