Re: FYI Koji 1.35 changed how side tag newRepo works

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 23, 2024 at 9:57 AM Petr Pisar <ppisar@xxxxxxxxxx> wrote:
>

(snip)

> Just to be sure:
>
> "koji wait-repo <tag> --build=<build>" waits on the build,
> but never itself start a repository regeneration.

Yes. Though this might be improved with koji 1.35.2, there's a PR for it.

> "koji wait-repo <tag> --build=<build> --request" starts the regeneration if
> the build is not yet there. I'm not sure what happens if the build is already
> there. Does it start the regeneration nevertheless?

If the latest available repo already has the build, --request will
*not* cause a new repo to be generated.

Similarly, using `koji wait-repo <tag> --request` without specifying a
build will currently do nothing (though this should be fixed in koji
1.35.2 hopefully).

> If find current (koji-1.35.1-1.fc39) "koji wait-repo --help" output misleading:
>
>     Options:
>       -h, --help         show this help message and exit
>       --build=NVR        Check that the given build is in the newly-generated repo
>                          (may be used multiple times)
>       --target           Interpret the argument as a build target name
>       --request          Create a repo request (requires auth)
>       --no-request       Do not create a repo request (the default)
>       --timeout=TIMEOUT  Amount of time to wait (in minutes) before giving up
>                          (default: 120)
>       -v, --verbose      Be verbose
>       --quiet            Suppress output, success or failure will be indicated by
>                          the return value only

Yes, multiple places need to be updated (both in the koji and fedpkg).

> What does mean "newly-generated repo" in case of (the default) --no-request
> option?

I think this means "don't request a new repo, but wait for one to
happen regardless" :)

Note that if you *really* need to trigger a fresh newRepo for a specific tag,
the koji 1.35 CLI has an entirely new command that provides a workaround:

koji request-repo <tag> --current --wait

This will launch a newRepo task if and only if the latest available
repo is not current, but will exit immediately if the new repo would
have the same contents as the current one (which is probably what most
people need).

Fabio
-- 
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux