Learn more about these different git repos.
Other Git URLs
Please retire the following packages in PDC and block them in Koji:
https://src.fedoraproject.org/rpms/dans-gdal-scripts/c/a513825e6371a1da393c5e241cbbea42ac7920e1?branch=rawhide https://src.fedoraproject.org/rpms/esniper/c/ad7396ba7b704ad4eb3a52219c0d6ea1d38fbba1?branch=rawhide https://src.fedoraproject.org/rpms/xcf-pixbuf-loader/c/7e1ecbe3f2835413ccba46bdd2b23be0b55c3334?branch=rawhide https://src.fedoraproject.org/rpms/python-jenkins-job-builder/c/c4f95b8a2006f187dd25aadc34223f52f553aeb0?branch=rawhide
The packages were retired in dist-git days ago. I suspect something is broken wrt automation.
Metadata Update from @zlopez: - Issue tagged with: automation, medium-gain, medium-trouble, ops
There are some more.
https://src.fedoraproject.org/rpms/fx/c/08baadb85280191f57dd0f6e5aaf948e0c01b2c4?branch=rawhide https://src.fedoraproject.org/rpms/fkill-cli/c/4ab9f5f9a11948b78b81049aa0ac9ae4de97525b?branch=rawhide https://src.fedoraproject.org/rpms/fx-completion/c/d8891b85015a73d6dadc421989b839526bba9766?branch=rawhide https://src.fedoraproject.org/rpms/nodejs-svgo/c/5ef739adda37632ada02e8bce9a263ed4ce39340?branch=rawhide https://src.fedoraproject.org/rpms/siril/c/8dbf5363b786de05a3ae3431cb5caeea4efe1cb9?branch=rawhide https://src.fedoraproject.org/rpms/npm-name-cli/c/2964124952a6d9e8b34d7c79a1c84c794a3db3d1?branch=rawhide https://src.fedoraproject.org/rpms/topojson-client/c/13fc402a405f6535d4392c136ce4e1705810cf20?branch=rawhide https://src.fedoraproject.org/rpms/topojson-server/c/5da8d81b5208fae6da14da26d9e02897b4a86ad9?branch=rawhide https://src.fedoraproject.org/rpms/topojson-simplify/c/2156c67ad067b3ab6d46c76ea379c0f447519fbb?branch=rawhide
Please do this before branching.
Here is the full list and how I obtained it:
$ cat should_be_retired curl -sIL --fail "https://src.fedoraproject.org/rpms/${1}/raw/rawhide/f/dead.package" >/dev/null && echo $1 $ parallel bash should_be_retired -- $(repoquery -q --repo=koji-source -a | pkgname | sort | uniq)
dans-gdal-scripts dotnet5.0-build-reference-packages esniper fkill-cli fx fx-completion golang-github-facebookincubator-ntp golang-github-facebookincubator-ptp idm-console-framework java-wakeonlan kata-proxy kiwix-lib libapogee libfli neXtaw nodejs-svgo npm-name-cli perl-Net-HL7 pgadmin3 php-aura-di php-aura-router php-bjeavons-zxcvbn-php php-cs-fixer-accessible-object php-cs-fixer-phpunit-constraint-isidenticalstring php-cs-fixer-phpunit-constraint-xmlmatchesxsd php-channel-pearplex php-pear-Console-CommandLine php-pear-crypt-gpg php-simplesamlphp-saml2_3 php-solarium python-jenkins-job-builder rubygem-rsolr rust-posish rust-ruma-api rust-ruma-appservice-api rust-ruma-client-api rust-ruma-federation-api rust-ruma-identifiers rust-ruma-push-gateway-api rust-unsafe-io siril system-config-repo topojson-client topojson-server topojson-simplify votca-csg votca-tools votca-xtp xcf-pixbuf-loader xemacs xemacs-packages-base xemacs-packages-extra
Alternatively, give me the right to do this myself, so I don't need to bother you again and again.
Updated the list, added:
+perl-Net-HL7 +rust-posish +rust-ruma-api +rust-ruma-appservice-api +rust-ruma-client-api +rust-ruma-federation-api +rust-ruma-identifiers +rust-ruma-push-gateway-api +rust-unsafe-io
What can I do to ensure this is done before branching?
So PDC is updated properly. "Just" the blocking of retired packages is not happening.
Oh, and I will block all packages at the end of today. And re-check tomorrow before the branching.
Blocked all of the 52 packages. After the mass branching tomorrow. I will investigate why the packages are not getting blocked.
Thanks.
Blocked all of the 52 packages.
Are you sure? Or did you miss some from the updated list? For example, rust-ruma (retired on Monday) is still not blocked from koji f36 / f37 tags:
$ koji list-pkgs --package rust-ruma --show-blocked Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- (...) rust-ruma f36 ignatenkobrain rust-ruma f37 ignatenkobrain
EDIT: Ah, it looks like the last list update from Miro does not contain all packages I retired on Monday. :(
I just ran the script provided by Miro again, and there's more affected packages:
python-concurrentloghandler rust-ruma rust-ruma-common rust-ruma-api-macros rust-ruma-identifiers-macros rust-ruma-events-macros rust-ruma-identity-service-api rust-ruma-serde rust-ruma-identifiers-validation rust-ruma-serde-macros rust-ruma-signatures wlroots0.12
All were retired either before the f36 branch point, or retired in both the rawhide and f36 branches.
Any updates here? I'm getting massive amounts of bugspam for packages that should've been removed from rawhide+f36 repositories a week ago.
Packages retired in rawhide dist git but not blocked in rawhide Koji:
laby mpir perl-VOMS-Lite python-concurrentloghandler python-sphinx-testing rust-javascriptcore-rs rust-javascriptcore-rs-sys rust-ostree rust-ostree-sys rust-ruma rust-ruma-api-macros rust-ruma-common rust-ruma-events-macros rust-ruma-identifiers-macros rust-ruma-identifiers-validation rust-ruma-identity-service-api rust-ruma-serde rust-ruma-serde-macros rust-ruma-signatures rust-soup-sys rust-webkit2gtk rust-webkit2gtk-sys uml_utilities wlroots0.12 wlroots0.13
Packages retired in f36 dist git but not blocked in f36 Koji:
laby mpir python-concurrentloghandler python-sphinx-testing rust-javascriptcore-rs rust-javascriptcore-rs-sys rust-ostree rust-ostree-sys rust-ruma-api-macros rust-ruma-identifiers-macros rust-ruma-identifiers-validation rust-ruma-serde rust-ruma-serde-macros rust-soup-sys rust-webkit2gtk rust-webkit2gtk-sys uml_utilities wlroots0.12 wlroots0.13
Packages without f36 dist-git branch that are not blocked in f36 Koji:
rust-ruma rust-ruma-common rust-ruma-events-macros rust-ruma-identity-service-api rust-ruma-signatures
The likely cause: https://pagure.io/releng/issue/10656
I've edited my comment to add more retired packages. Could somebody please block them or can I have the permission to do that myself?
The beta freeze is tmrw. Could you please give me the necessary permissions so I can help with this issue?
I'm fine with you having perms to do it, but note that if you have admin perms in koji you need to be very carefull, since you can override some things without even knowing it (ie, you can build a official package from a uploaded src.rpm)
I've made you an admin, so please go ahead and block away. If you want me to remove admin after that, happy to... or happy to let you keep it...
Thanks. I'll be very careful in what I am doing and will happily return my admin rights once the automation for this is fixed.
I've blocked the packages listed in my comment and I am re-running the script once again to see if some new packages were retired.
Just as a heads-up, I've retired a few more rust packages just a few minutes ago, not sure if your script will pick them up yet. :(
Metadata Update from @churchyard: - Issue assigned to churchyard
You can always share the list here.
Right, that would've been the obvious solution.
rust-bytes0.6 rust-crc1 rust-crypto-mac0.8 rust-rand_isaac0.2 rust-ron0.6 rust-textwrap0.12
You can verify that they are all retired for f36 + rawhide branches in dist-git.
$ parallel koji list-pkgs --show-blocked --tag f36 --quiet --package -- rust-bytes0.6 rust-crc1 rust-crypto-mac0.8 rust-rand_isaac0.2 rust-ron0.6 rust-textwrap0.12 rust-bytes0.6 f36 ignatenkobrain [BLOCKED] rust-ron0.6 f36 decathorpe [BLOCKED] rust-crc1 f36 decathorpe [BLOCKED] rust-rand_isaac0.2 f36 decathorpe [BLOCKED] rust-crypto-mac0.8 f36 decathorpe [BLOCKED] rust-textwrap0.12 f36 ignatenkobrain [BLOCKED] $ parallel koji list-pkgs --show-blocked --tag f37 --quiet --package -- rust-bytes0.6 rust-crc1 rust-crypto-mac0.8 rust-rand_isaac0.2 rust-ron0.6 rust-textwrap0.12 rust-crc1 f37 decathorpe [BLOCKED] rust-rand_isaac0.2 f37 decathorpe [BLOCKED] rust-crypto-mac0.8 f37 decathorpe [BLOCKED] rust-ron0.6 f37 decathorpe [BLOCKED] rust-textwrap0.12 f37 ignatenkobrain [BLOCKED] rust-bytes0.6 f37 ignatenkobrain [BLOCKED]
Metadata Update from @churchyard: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.