-
Notifications
You must be signed in to change notification settings - Fork 63
Open
Description
From the Matrix channel today, an end user reported a depsolve transaction that failed:
Enabled rpm-md repositories: fedora updates copr:copr.fedorainfracloud.org:atim:starship fedora-cisco-openh264 updates-archive
Updating metadata for 'copr:copr.fedorainfracloud.org:atim:starship'...done
Importing rpm-md...done
rpm-md repo 'fedora' (cached); generated: 2025-10-23T03:37:18Z solvables: 68135
rpm-md repo 'updates' (cached); generated: 2025-12-05T02:04:39Z solvables: 11860
rpm-md repo 'copr:copr.fedorainfracloud.org:atim:starship'; generated: 2025-08-13T08:35:57Z solvables: 2
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2025-03-05T10:45:56Z solvables: 6
rpm-md repo 'updates-archive' (cached); generated: 2025-12-05T02:15:43Z solvables: 14001
Resolving dependencies...done
error: Could not depsolve transaction; 1 problem detected:
Problem: conflicting requests
- package git-2.51.0-2.fc43.aarch64 from fedora requires git-core = 2.51.0-2.fc43, but none of the providers can be installed
- package git-2.52.0-1.fc43.aarch64 from updates requires git-core = 2.52.0-1.fc43, but none of the providers can be installed
- package git-2.52.0-1.fc43.aarch64 from updates-archive requires git-core = 2.52.0-1.fc43, but none of the providers can be installed
- cannot install both git-core-2.51.0-2.fc43.aarch64 from fedora and git-core-2.51.1-1.fc43.aarch64 from @System
- cannot install both git-core-2.52.0-1.fc43.aarch64 from updates and git-core-2.51.1-1.fc43.aarch64 from @System
- cannot install both git-core-2.52.0-1.fc43.aarch64 from updates-archive and git-core-2.51.1-1.fc43.aarch64 from @System
After some investigation I realized git-2.51.1-1 was not added to f43/aarch64.
$ repoquery --repofrompath=tmp-1,https://fedoraproject-updates-archive.fedoraproject.org/fedora/43/aarch64 --disablerepo=* --enablerepo=tmp-* git
git-0:2.52.0-1.fc43.aarch64
whereas in x86_64
repoquery --repofrompath=tmp-1,https://fedoraproject-updates-archive.fedoraproject.org/fedora/43/x86_64 --disablerepo=* --enablerepo=tmp-* git
git-0:2.51.1-1.fc43.x86_64
git-0:2.52.0-1.fc43.x86_64
Later on @dustymabe clarified the situation by showing the archive-repo-manager logs:
Oct 26 22:51:18 archive-repo-manager archive-repo-manager[2774]: Downloading [2/4]: gimp-devel-tools-3.0.6-5.fc43.aarch64.rpm
Oct 26 22:51:18 archive-repo-manager archive-repo-manager[2774]: Downloading [3/4]: gimp-devel-3.0.6-5.fc43.aarch64.rpm
Oct 26 22:51:18 archive-repo-manager archive-repo-manager[2774]: Downloading [4/4]: gimp-3.0.6-5.fc43.aarch64.rpm
Oct 26 22:51:20 archive-repo-manager archive-repo-manager[2774]: 2025-10-26 22:51:20,578 [ERROR] koji: ReadTimeout: HTTPSConnectionPool(host='kojipkgs.fedoraproject.org', port=443): Read timed out. (read timeout=10)
Oct 26 22:51:20 archive-repo-manager archive-repo-manager[2774]: Downloading [1/17]: git-core-doc-2.51.1-1.fc43.noarch.rpm
The proposed solution is to add some retry mechanism in https://pagure.io/releng/archive-repo-manager when downloading the subpackages to have more guarantee.
Metadata
Metadata
Assignees
Labels
No labels