Created https://pagure.io/koji/issue/1808 to track this.
@tkopecek please take a look

Is there any reason to use getBuildTargets instead of getBuildTarget? You are querying against strict name, so you can never get more than one (would also simplify rest of code)

I don't think this is the correct way to get a "BuildRoot" tag, since there is no strict rule to specify buildtarget's name as the same as a tag.
Usually, a BuildTag is treated as a BuildRoot tag, so I think the situation to warn such kind of msg is there is not any BuildTarget with args[0] as its BuildTag.

So I think it is something like

targets = session.getBuildTargets(buildTagID=session.getTag(args[0], strict=True)['id'])
...

I'm not sure I understand what is confusing about the current behavior. Would you please say more about what you expected to happen?

The reason I ask is that I have some code that does interrogate the latest build in a tag that is not a buildroot tag. I guess I can add --disable-buildroot-check to my code now, but this is a little surprising.

I wonder if we should make the "--help" text more verbose for "latest-build" instead?

@ktdreyer The confusing part is that you use koji build f32 to submit builds, but koji latest-build f32 shows package versions which are not actually in the buildroot and are not used by the build.

@julian8628 I do not have any opinion on Koji API use, I just put together something that appeared to be working for me. Sorry.

@julian8628 I do not have any opinion on Koji API use, I just put together something that appeared to be working for me. Sorry.

We should enrich the doc about tag and target :blush:

I have a concern about adding the warning as a default behavior. While cli output is not intended to be an API, there likely are scripts in the wild besides Ken's that are expecting the current output.

I would suggest that we change --disable-buildroot-check to --enable-buildroot-check

I think a warning controlled by a non-default flag defeats its purpose. If you use it, you'll likely be aware of the issue and don't need the warning.

Maybe we can add a different command that requires a buildroot and errors out for other tags? Then we can teach users to use this comment to check buildroot contents.

That's an option too. @tkopecek @mikem what's your opinion here?

It is reasonable and normal to use latest-build on any sort of tag, not just build tags. It seems wrong to print a warning about it. Seems like we need to improve the docs instead.

We could add some text to koji build --help and koji latest-build --help to make it clearer why each one operates on a tag versus a target.

Enriched help #2071