releng/tickets

flatpak / branching: clone old flatpak tag instead of making a new one #12431

Merged

jnsamyak merged 1 commit from flatpak-mass-branching into main

2025-01-06 20:57:33 +00:00

kevin commented

2024-10-30 17:08:24 +00:00

Owner

We should just do the same thing we do for rpm packages here and clone
the flatpak tag to get all the flatpaks we had in the previous release.

Signed-off-by: Kevin Fenzi kevin@scrye.com

We should just do the same thing we do for rpm packages here and clone the flatpak tag to get all the flatpaks we had in the previous release. Signed-off-by: Kevin Fenzi <kevin@scrye.com>

kevin commented

2024-10-30 17:08:58 +00:00

Author

Owner

CC: @yselkowitz @otaylor

CC: @yselkowitz @otaylor

yselkowitz commented

2024-10-30 18:57:08 +00:00

Member

Nack. Flatpaks don't work the same way as RPMs in this regard, we neither want nor need the builds from a previous release tagged into the new one. We just need to make sure that the package list is fully carried over.

Nack. Flatpaks don't work the same way as RPMs in this regard, we neither want nor need the builds from a previous release tagged into the new one. We just need to make sure that the package list is fully carried over.

kevin commented

2024-10-30 19:13:16 +00:00

Author

Owner

Yeah, I know you don't want the builds, but we do want the package list and this seems a easy way to do that?

None of the builds will go anywhere without an update...

But perhaps there's a better way to populate the new pkg list?

Yeah, I know you don't want the builds, but we do want the package list and this seems a easy way to do that? None of the builds will go anywhere without an update... But perhaps there's a better way to populate the new pkg list?

yselkowitz commented

2024-10-30 19:17:31 +00:00

Member

$ koji clone-tag --help
Usage: koji 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)

Options:
  -h, --help        show this help message and exit
  --config          Copy config from the source to the dest tag
  --groups          Copy group information
  --pkgs            Copy package list from the source to the dest tag
  --builds          Tag builds into the dest tag
  --all             The same as --config --groups --pkgs --builds
  --latest-only     Tag only the latest build of each package
  --inherit-builds  Include all builds inherited into the source tag into the
                    dest tag
  --ts=TIMESTAMP    Clone tag at last event before specific timestamp
  --no-delete       Don't delete any existing content in dest tag.
  --event=EVENT     Clone tag at a specific event
  --repo=REPO       Clone tag at a specific repo event
  --notify          Send tagging/untagging notifications
  -f, --force       override tag locks if necessary

So --config --groups --pkgs?

``` $ koji clone-tag --help Usage: koji 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) Options: -h, --help show this help message and exit --config Copy config from the source to the dest tag --groups Copy group information --pkgs Copy package list from the source to the dest tag --builds Tag builds into the dest tag --all The same as --config --groups --pkgs --builds --latest-only Tag only the latest build of each package --inherit-builds Include all builds inherited into the source tag into the dest tag --ts=TIMESTAMP Clone tag at last event before specific timestamp --no-delete Don't delete any existing content in dest tag. --event=EVENT Clone tag at a specific event --repo=REPO Clone tag at a specific repo event --notify Send tagging/untagging notifications -f, --force override tag locks if necessary ``` So `--config --groups --pkgs`?

kevin commented

2024-11-01 16:43:53 +00:00

Author

Owner

rebased onto 54c531ee9a

rebased onto 54c531ee9ab03185454ae642f4d2f65f93762745

kevin commented

2024-11-01 16:44:11 +00:00

Author

Owner

Yeah. How does that look?

Yeah. How does that look?

yselkowitz commented

2024-11-01 16:48:02 +00:00

Member

That seems to make sense.

That seems to make sense.

jnsamyak commented

2024-11-11 06:26:41 +00:00

Owner

rebased onto b3c082af7a

rebased onto b3c082af7a9784487c716016ca0bf0a7636fbe19

yselkowitz commented

2025-01-06 20:40:16 +00:00

Member

This needs to be rebased, but is it otherwise ready now?

This needs to be rebased, but is it otherwise ready now?

kevin commented

2025-01-06 20:57:08 +00:00

Author

Owner

rebased onto b2d54e7691

rebased onto b2d54e76917e648bbadee658ddba4e295a2302df

kevin commented

2025-01-06 20:57:33 +00:00

Author

Owner

Pull-Request has been merged by kevin

Pull-Request has been merged by kevin

Sign in to join this conversation.

No reviewers

No labels

change-noreleng

Fixed with Explanation

Insufficient data

mini-initiative

waiting on external

release-process

No milestone

No project

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

releng/tickets!12431

No description provided.