#2959 `koji -c $config_path build` seems to have no effect
Closed: Fixed by ttomecek. Opened by ttomecek.

I just tried to submit a build against stg fedora koji like this:

$ koji -c /etc/koji.conf.d/stg.conf build --scratch --nowait rawhide ./python-ogr-0.26.1.dev30+gc8a7226-1.20210719135004248282.main.30.gc8a7226.fc33.src.rpm
Uploading srpm: ./python-ogr-0.26.1.dev30+gc8a7226-1.20210719135004248282.main.30.gc8a7226.fc33.src.rpm
[====================================] 100% 00:00:03   3.06 MiB 960.71 KiB/sec
Created task: 72239597
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=72239597

To my surprise, the task was created on the production instance. When I specify -s https://koji.stg.fedoraproject.org/kojihub it's submitted against stg instance correctly.

Is the -c option being ignored?

koji-1.25.0-1.fc33.noarch


It could be confusing. Right call for your usecase is:
koji -p stg build --scratch...
-c will override values from relevant profiles. But in your case you're just overriding stg section with default one, so it is no-op in the end. -p will select section/profile. If it is not used, profile with same name as prog (in this case koji = fedora's koji) is used. If you create stg symlink to koji, it will use stg profile as default.

Metadata Update from @tkopecek:
- Custom field Size adjusted to None

@tkopecek thanks Tome, will adjust our call to koji then

(it indeed is confusing :D )

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

I think we can improve the UX here slightly by updating the --help text. PR in https://pagure.io/koji/pull-request/2985

Commit 9f8b74cd fixes this issue

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/2959

Please continue any further discussion there.

Metadata
Related Pull Requests