#1237 Architectures field in build target uses 2 different separators
Closed: Fixed 3 years ago by mikem. Opened 4 years ago by pbabinca.

Koji returns inconsistent data for architectures from build target, because both space and comma separators are allowed.

Could be possible to unify separators to space character only (at least in API responses)?

Ideally it would be great to get same order of the architectures no matter in which order they have been provided (e.g. sort them alphabetically).


Koji returns inconsistent data for architectures from build target

Where specifically in the api are you seeing this? I need to see the actual problem.

Koji uses space separators for the arch field of tags. There are a few places in the cli (not the api) where a list of arches can be specified with commas because it is the argument of a single option and using commas avoids having to quote the option in shell.

You are correct. It has turned out that architecture(s) has been set as x86_64,ppc64le over API and because comma wasn't replaced by space hub has treated this as single architecture.

I guess this bug report can be then closed as invalid.

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

4 years ago

I've seen this already - we probably should introduce some hub-level arch sanitization (comma can't be part of any arch)

Metadata Update from @tkopecek:
- Issue status updated to: Open (was: Closed)

4 years ago

What characters should be allowed? I'm thinking [a-zA-Z0-9_]

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.18

4 years ago

Commit 558e129 relates to this ticket

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #1272 Merged 3 years ago