Learn more about these different git repos.
Other Git URLs
The script that retires packages has a bug for epel packages and only blocks packages from epel and not epel-build. This has been going on for several years and we need the packages cleaned up.
Please block the packages in epel9-build-need-block in epel9-build. Please block the packages in epel8-build-need-block in epel8-build.
When do you need this? (YYYY/MM/DD) 2024/06/30
When is this no longer needed or useful? (YYYY/MM/DD) Never
If we cannot complete your request, what is the impact? This is affecting koschei, as well as other script/automations that utilize the -build tag.
<img alt="epel9-build-need-block" src="/releng/issue/raw/files/16fb56fe5237f6554720d64eb75c4e2bdc92ef61847ddd1b7dbc4930de59d67b-epel9-build-need-block" />
I can't seem to upload the epel8-build-need-block file ... so here is the list.
amavisd-new bashtop caribou convert2rhel dwarves ecj edk2-epel flameshot flatpak-epel flintqs fstrm fts-rest fwupd-epel git-lfs git-subrepo golang-github-prometheus-node_exporter hashcat hostapd jrnl ktoblzcheck libpinyin-epel librem libscn libselinux-epel libslirp libtpms libtraceevent lmdb lmdbxx lutris mate-optimus memleax mobile-broadband-provider-info-epel modulemd-tools mpark-variant mustache pcllib perl-Convert-ASN1 perl-LDAP perl-Mail-Sender pidgin-groupchat-typing-notifications pidgin-toobars purple-discord purple-googlechat purple-libsteam purple-matrix purple-skypeweb py3c pybind11 pycairo-epel python39-zstd-epel python3-pyxattr python-asynctest python-distro python-FireflyAlgorithm python-psutil python-pyghmi python-pytelegrambotapi python-sphinx-autodoc-typehints python-sphinx-epel python-tomli rubygem-qpid_proton semver singularity sshpass stress-ng swtpm system-switch-displaymanager tesseract tomcat tpm2-pkcs11 tracer tweeny upower utf8proc-epel whois wxsvg xapian-core xmlstarlet xrdcl-http xrefresh xxhash yara zabbix40 zstd zswap-cli
better than blocking them should perhaps be to remove all packages from these build tags. Then they will inherit from the base tag and the package will be blocked there (because it's blocked in the base tag).
Whatever works.
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
Metadata Update from @jnsamyak: - Issue tagged with: medium-gain, medium-trouble, ops
I tried removing the package from the tag, but i got stuck at policy violation error, is this happening because the parent tag (epel8 is blocked?)
koji remove-pkg epel8-build zswap-cli 2024-05-30 16:42:32,636 [ERROR] koji: ActionNotAllowed: policy violation (package_list)
Yep.
Look in roles/koji_hub/templates/hub.conf.j2 in ansible. Thats our hub policy:
... package_list = # Removing packages is almost always a mistake, so deny it. # Admins can still override this with --force, if necessary. match action remove :: deny # Admins can do pretty much everything. has_perm admin :: allow ...
So, by default we deny removing packages (because it's usually 100% the right thing to do). In this case we do want to remove, so since you are an admin you can use '--force' on it. :)
Hello, thanks for the policy, link all the above packages are now removed from epel8-build/epel9-build tag, if there are still any issues please let us know, thanks!
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.