I wanted to create a repository for a namespaced flit-core for EPEL only. I ran:
fedpkg request-repo python3.13-flit-core --exception --no-initial-commit
Unfortunately, the initial README was added to the repo in the Rawhide branch (reported in https://pagure.io/releng/issue/12791). So to avoid moving that between branches, I requested EPEL branches with
fedpkg request-branch --no-git-branch epel9 fedpkg request-branch --no-git-branch epel10
fedpkg request-branch --no-git-branch epel9
fedpkg request-branch --no-git-branch epel10
I took a git state from the main python-flit-core and pushed.
This gave me some fatal errors:
remote: ERROR: ['git', 'ls-tree', 'epel9', '--name-only', '--', 'dead.package'] =-- 128 remote: remote: fatal: Not a valid object name epel9
But the branch was nevertheless pushed.
Now I opened PRs to this package to adjust them for EPEL: https://src.fedoraproject.org/rpms/python3.13-flit-core/pull-request/1 https://src.fedoraproject.org/rpms/python3.13-flit-core/pull-request/2
No CI (reported to https://pagure.io/fedora-ci/general/issue/521) is run. Something apparently went wrong. Please take a look.
$ koji list-pkgs --show-blocked --tag epel10 --quiet --package python3.13-flit-core (no matching packages) $ koji list-pkgs --show-blocked --tag epel9 --quiet --package python3.13-flit-core (no matching packages) $ koji list-pkgs --show-blocked --tag rawhide --quiet --package python3.13-flit-core python3.13-flit-core f43 ksurma
When do you need this? asap
When is this no longer needed or useful? when packages are created correctly
If we cannot complete your request, what is the impact? I can't build the packages
Note that there are two things to solve here:
Hey, is this the same thing as https://pagure.io/releng/issue/12791 ... which is really an upstream problem?
Also AIUI everything gets a rawhide branch, but you can not do anything with it and/or maybe kill it after ... so that part is expected.
Then I'm not sure what the problem is, did the package get built correctly but is in the wrong tags? Can you not rebuild it correctly in the right tag? Sorry, if I (and releng in general) aren't great this week and next ... it's not the best time ;)
Metadata Update from @james: - Issue tagged with: low-gain, low-trouble
Metadata Update from @james: - Issue assigned to james
Can you not rebuild it correctly in the right tag?
We assumed that, but apparently se can build it in epels.
https://koji.fedoraproject.org/koji/taskinfo?taskID=134426084 https://koji.fedoraproject.org/koji/taskinfo?taskID=134425997
BuildError: package python3.13-setuptools not in list for tag epel10.1-build-side-114208 BuildError: package python3.13-setuptools not in list for tag epel9-build-side-114206
So we do have a problem :(
https://koji.fedoraproject.org/koji/taskinfo?taskID=134426811 https://koji.fedoraproject.org/koji/taskinfo?taskID=134426814
BuildError: package python3.13-pip not in list for tag epel9-build-side-114206 BuildError: package python3.13-pip not in list for tag epel10.1-build-side-114208
FTR it does not seem to be caused by the use of side tags:
BuildError: package python3.13-pip not in list for tag epel9-testing-candidate BuildError: package python3.13-pip not in list for tag epel10.1-testing-candidate BuildError: package python3.13-setuptools not in list for tag epel9-testing-candidate BuildError: package python3.13-setuptools not in list for tag epel10.1-testing-candidate
Trying:
$ koji add-pkg --owner ksurma epel10 python3.13-setuptools Adding 1 packages to tag epel10 $ koji add-pkg --owner ksurma epel9 python3.13-setuptools Adding 1 packages to tag epel9 $ koji add-pkg --owner ksurma epel10 python3.13-pip Adding 1 packages to tag epel10 $ koji add-pkg --owner ksurma epel9 python3.13-pip Adding 1 packages to tag epel9
Works for epel9, but not for epel10. Trying with epel10.1.
Works with epel10.1.
So there is no immediate action we need. But something seems inherently broken in the tooling.
Metadata Update from @james: - Issue untagged with: low-trouble - Issue tagged with: medium-trouble
Same for this package:
BuildError: package python3-rpm not in list for tag epel10.1-testing-candidate
Added manually.
Log in to comment on this ticket.