#9485 f33-kde side tag
Closed: Fixed 2 years ago by mohanboddu. Opened 3 years ago by mkyral.

  • For which release?
    f33/rawhide

  • Name of the side tag? (Generally fxx-pkg)
    f32-kde

  • Number of builds that are expected in the side tag?
    ~50

  • How long do you need the side tag?
    ~3 weeks

  • Any extra information?
    Can't use usual side-tag feature due some current implementation limitations. Mostly: once a bodhi update gets created, the tag is deleted. I need to be able to do followup builds and edits.


Could this inherit from the f33-python side tag? We are about to merge soon.

corection:

  • Name of the side tag? (Generally fxx-pkg)
    f33-kde

Could this inherit from the f33-python side tag? We are about to merge soon.

I don't get the question: what would be the benefit of inheriting from f33-python? There is no connection between KDE/Plasma and python.

I suspect there are overlapping packages.

@mkyral Can you wait until the f33-python side tag is merged back into f33? That will save lot of your time as well.

Metadata Update from @mohanboddu:
- Issue tagged with: groomed, low-trouble, medium-gain

3 years ago

f33-python side tag is merged

f33-kde side tag has been created:

$ koji add-tag f33-kde --arches 'armv7hl i686 x86_64 aarch64 ppc64le s390x' --parent f33-build
$ koji add-target f33-kde f33-kde

You can do builds with:

$ fedpkg build –target=f33-kde

Let us know when you are done and we will move all the builds into f33.

Metadata Update from @mohanboddu:
- Issue tagged with: sidetarget

3 years ago

@mkyral What is the status on this? FYI, mass branching is tomorrow.

Closing this ticket, please reopen if you need anymore help.

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

2 years ago

Login to comment on this ticket.

Metadata