#2378 Changes to buildinfo output break existing scripts
Closed: Dropped 3 years ago by cobrien. Opened 3 years ago by cobrien.

PR #2016 changed the output format of the buildinfo command to inject additional signature information inline with the list of artifacts.

May I please suggest that more care should be taken in changes that alter what's written to stdout? I'm finding myself tracking down small scripts which have worked for a decade that borrow paths from the brew buildinfo output, which now need to chop of the additional information.

I understand that the PR was to resolve an RFE, but that could have just as well been solved by making koji list-signed --build [...] actually work


We focus on API stability, but it's much harder to keep the CLI output stable.

Can these scripts use the API instead?

You should switch to use API instead. There are no guarantees on CLI output.

Metadata Update from @cobrien:
- Issue close_status updated to: Dropped
- Issue status updated to: Closed (was: Open)

3 years ago

For posterity, here's an example of scraping a build's information with the getBuild RPC on the command-line:

koji --noauth call --json getBuild mypackage-1.0-1

Users can pipe that JSON output through jq to select values, etc.

note this wouldn't have helped, as the relevant aspects were the full paths to the artifacts of the build.

solved by writing a custom tool.

Login to comment on this ticket.

Metadata