Hi, we need to block maven:3.8 packages when building Java based packages for virt9s-ovirt-45* tags due to https://bugzilla.redhat.com/show_bug.cgi?id=2128991 . We have found out that we can define a macro value for specific tag in https://docs.pagure.org/koji/setting_rpm_macros/#setting-rpm-macro-values, but we don't have enough permissions:
$ cbs edit-tag virt9s-ovirt-45-candidate -x rpm.macro.block_maven_38=1 2023-11-29 12:09:12,205 [ERROR] koji: ActionNotAllowed: tag permission required (logged in as mperina)
So could you please set macro block_maven_38 to 1 for all following tags, so we can block maven:38 packages within spec files of our Java packages?
block_maven_38
1
Thanks, Martin
@sbonazzo
Not sure if any approval needed on my side, but if needed: I approve.
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs, high-gain, medium-trouble
Done but should be on the build tag though, and now applied :
cbs taginfo virt9s-ovirt-45-el9s-build Tag: virt9s-ovirt-45-el9s-build [2387] Arches: x86_64 aarch64 ppc64le Groups: build, srpm-build Tag options: mock.new_chroot : 0 mock.package_manager : 'dnf' mock.yum.module_hotfixes : 1 rpm.macro.block_maven_38 : 1 rpm.macro.dist : '.el9' This tag is a buildroot for one or more targets Current repo: repo#1134833: 2023-11-29 12:43:52.169883+00:00 Targets that build from this tag: virt9s-ovirt-45-el9s External repos: 5 centos9s-baseos (http://mirror.stream.centos.org/9-stream/BaseOS/$arch/os/, merge mode: bare), arches: inherited from tag 10 centos9s-appstream (http://mirror.stream.centos.org/9-stream/AppStream/$arch/os/, merge mode: bare), arches: inherited from tag 15 centos9s-crb (http://mirror.stream.centos.org/9-stream/CRB/$arch/os/, merge mode: bare), arches: inherited from tag Inheritance: 5 .... buildsys9s-release [2363] 10 .... virt9s-ovirt-45-candidate [2384]
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks a lot, the solution works fine!
Log in to comment on this ticket.