#2012 brew clone-tag requires "config" option
Closed: Fixed by tkopecek. Opened by tkopecek.

$ koji clone-tag --pkgs --builds --inherit-builds --verbose --latest-only tag_a tag_b
Usage: brew clone-tag [options] <src-tag> <dst-tag>
clone-tag will create the destination tag if it does not already exist
(Specify the --help global option for a list of other help options)
koji: error: Cannot create tag without specifying --config

I would expect that the brew clone-tag will create the destination tag (even without the --config option) but only skips copy of config (like "Required permission").

My use-case when I hit this is:

  • I have a user (automation keytab) with only "tag" perm.
  • The user is supposed to clone RHEL tag and then add few builds there.
  • If we clone tag with --config then RHEL original tag permission (trusted) is copied as well and the automation cannot tag builds to the tag it just created.

Furthermore, config doesn't actually duplicate config. The only thing is does is fail the command if the tag does not yet exist and the tag is missing.

  • values in the tag_config table are not synced when the destination already exists
  • values in the tag_extra table are not synced in any case
  • values in the tag_package_owners table are not synced unless the corresponding package list entry is added (granted, perhaps that should be a separate option?)
  • external repos are not synced (see also #1792), though perhaps we don't want to get into that with this command.

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

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.23 (was: 1.22)

values in the tag_extra table are not synced in any case

This has been filed as #2371

PR #2442

Metadata Update from @jcupova:
- Issue tagged with: testing-ready

Metadata Update from @mfilip:
- Issue tagged with: testing-done

Commit 3067461b fixes this issue

Commit aa16b5cc fixes this issue

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

Please continue any further discussion there.

Metadata
Related Pull Requests