Is there a possibility that the ‘repodata’ subdirectory actually refers to ‘10.x’ ?
Everytime I attempt a ‘reposync’ for the 9.7 appstream packages, it starts to download the ‘10.1’ versions….
I’ve checked everything on ‘my end’ and when running with a ‘-x’ it shows the correct values (9.7) being passed to reposync…
No.
If you’re running reposync on a 10 system and you don’t specify --releasever 9, you will get the 10 packages. Same goes for running it on a 9 system, if you want 10 packages, you would need to specify --releasever 10.
[root@xmpp01 tmp]# dnf reposync --disablerepo=* --enablerepo=appstream --releasever 9
Rocky Linux 9 - AppStream 28 kB/s | 4.8 kB 00:00
(1/6406): 389-ds-base-snmp-2.7.0-7.el9.x86_64.rpm 206 kB/s | 46 kB 00:00
(2/6406): Box2D-2.4.1-7.el9.i686.rpm 606 kB/s | 116 kB 00:00
(3/6406): 389-ds-base-2.7.0-7.el9.x86_64.rpm 5.1 MB/s | 2.9 MB 00:00
(4/6406): Box2D-2.4.1-7.el9.x86_64.rpm 662 kB/s | 109 kB 00:00
(5/6406): CUnit-2.1.3-25.el9.i686.rpm 478 kB/s | 53 kB 00:00
(6/6406): 389-ds-base-libs-2.7.0-7.el9.x86_64.rpm 2.1 MB/s | 1.5 MB 00:00
(7/6406): CUnit-2.1.3-25.el9.x86_64.rpm 260 kB/s | 52 kB 00:00
(8/6406): HdrHistogram_c-0.11.0-6.el9.i686.rpm 326 kB/s | 34 kB 00:00
(9/6406): HdrHistogram_c-0.11.0-6.el9.x86_64.rpm 277 kB/s | 30 kB 00:00
(10/6406): Judy-1.0.5-28.el9.x86_64.rpm 990 kB/s | 128 kB 00:00
(11/6406): Judy-1.0.5-28.el9.i686.rpm 582 kB/s | 92 kB 00:00
[root@xmpp01 tmp]# dnf reposync --disablerepo=* --enablerepo=appstream --releasever 10
Rocky Linux 10 - AppStream 7.2 MB/s | 7.0 MB 00:00
Last metadata expiration check: 0:00:01 ago on Sun 07 Dec 2025 08:06:20 PM MST.
(1/4582): 389-ds-base-snmp-3.1.3-5.el10_1.x86_64.rpm 214 kB/s | 44 kB 00:00
(2/4582): CUnit-2.1.3-34.el10.x86_64.rpm 412 kB/s | 53 kB 00:00
(3/4582): HdrHistogram_c-0.11.8-7.el10.x86_64.rpm 239 kB/s | 30 kB 00:00
(4/4582): Judy-1.0.5-38.el10.x86_64.rpm 768 kB/s | 137 kB 00:00
(5/4582): 389-ds-base-libs-3.1.3-5.el10_1.x86_64.rpm 2.3 MB/s | 1.5 MB 00:00
(6/4582): NetworkManager-cloud-setup-1.54.0-1.el10.x86_64.rpm 609 kB/s | 76 kB 00:00
(7/4582): NetworkManager-config-connectivity-redhat-1.54.0-1.el10.noarch.rpm 130 kB/s | 15 kB 00:00
(8/4582): NetworkManager-libreswan-gnome-1.2.27-2.el10_0.x86_64.rpm 387 kB/s | 49 kB 00:00
(9/4582): NetworkManager-libreswan-1.2.27-2.el10_0.x86_64.rpm 1.1 MB/s | 174 kB 00:00
(10/4582): 389-ds-base-3.1.3-5.el10_1.x86_64.rpm 3.0 MB/s | 2.8 MB 00:00
Sorry, but that has no relevance to my issue…
You will need to provide a lot more information then than you have done so far. Louis has provided commands to prove the situation and that it’s possible to download both. So now we need to see more information from your side, like what commands are being used, etc, and what the system it is being ran on.
Here’s everything that I’ve gathered, after attempting to ‘debug’ the issue myself (running my script with a ‘-x’, and using “strace” for the reposync process…
I still don’t see anything incorrect on ‘my’ end, having only created a new ‘.conf’ file for the 9.7 release (copying from the ‘9.6’ version of the file), which DOES function properly for the “updates” (BaseOS) repo…
diff yum.reposync.rocky-9.6-x86_64.conf yum.reposync.rocky-9.7-x86_64.conf 1c1 < [rocky-9.6-x86_64-updates] > [rocky-9.7-x86_64-updates] 3,5c3,4 < baseurl=https://dl.rockylinux.org/pub/rocky/9.6/BaseOS/x86_64/os/ > baseurl=https://dl.rockylinux.org/pub/rocky/9.7/BaseOS/x86_64/os/ 10c9 < [rocky-9.6-x86_64-appstream] > [rocky-9.7-x86_64-appstream] 12,14c11,13 < baseurl=https://dl.rockylinux.org/pub/rocky/9.6/AppStream/x86_64/os/ > baseurl=https://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/
When executing my ‘reposync’ wrapper script, it completes successfully for the ‘updates’ (BaseOS) packages (none downloaded, as it had previously completed the download of new packages…
/usr/bin/reposync -u '--config=/export/software/linux/scripts/REPO_Sync/yum.reposync.rocky-9.7-x86_64.conf' '--repoid=rocky-9.7-x86_64-updates' '--download_path=/export/software/linux/scripts/REPO_Sync/repos/updates/rocky-9.7-x86_64' --allow-path-traversal --norepopath --newest-only 2>& 1
Tue Dec 9 20:12:46 MST 2025
** File Download Process Completed **
BUT, when used to download the AppStream updates, though the remote URL path indicates the “9.7” release, the packages listed are for ‘10’ (and or ‘10.1’)
Which if you goto ‘that’ URL directory specification, ‘those’ files do not exist…
/usr/bin/reposync -u '--config=/export/software/linux/scripts/REPO_Sync/yum.reposync.rocky-9.7-x86_64.conf' '--repoid=rocky-9.7-x86_64-appstream' '--download_path=/export/software/linux/scripts/REPO_Sync/repos/appstream/rocky-9.7-x86_64' --allow-path-traversal --norepopath --newest-only
+ 2>& 1
https://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/Packages/3/389-ds-base-3.1.3-5.el10_1.x86_64.rpm
https://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/Packages/3/389-ds-base-libs-3.1.3-5.el10_1.x86_64.rpm
https://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/Packages/3/389-ds-base-snmp-3.1.3-5.el10_1.x86_64.rpm
~
~
https://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/Packages/z/zram-generator-1.1.2-14.el10.x86_64.rpm
https://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/Packages/z/zziplib-0.13.78-2.el10.x86_64.rpm
https://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/Packages/z/zziplib-utils-0.13.78-2.el10.x86_64.rpm
Tue Dec 9 20:18:22 MST 2025
** File Download Process Completed **
There is nothing wrong with the repo data.
# 10 example
[root@xmpp01 tmp]# dnf reposync --disablerepo=* --enablerepo=appstream --releasever 10 -u
. . .
http://dl.rockylinux.org/pub/rocky/10/AppStream/x86_64/os/Packages/z/zlib-ng-compat-devel-2.2.3-2.el10.x86_64.rpm
http://dl.rockylinux.org/pub/rocky/10/AppStream/x86_64/os/Packages/z/zram-generator-1.1.2-14.el10.x86_64.rpm
http://dl.rockylinux.org/pub/rocky/10/AppStream/x86_64/os/Packages/z/zziplib-0.13.78-2.el10.x86_64.rpm
http://dl.rockylinux.org/pub/rocky/10/AppStream/x86_64/os/Packages/z/zziplib-utils-0.13.78-2.el10.x86_64.rpm
# 9 example
[root@xmpp01 tmp]# dnf reposync --disablerepo=* --enablerepo=appstream --releasever 9 -u
. . .
http://dl.rockylinux.org/pub/rocky/9/AppStream/x86_64/os/Packages/z/zziplib-0.13.71-12.el9.i686.rpm
http://dl.rockylinux.org/pub/rocky/9/AppStream/x86_64/os/Packages/z/zziplib-0.13.71-12.el9.x86_64.rpm
http://dl.rockylinux.org/pub/rocky/9/AppStream/x86_64/os/Packages/z/zziplib-utils-0.13.71-12.el9.x86_64.rpm
## I'll set 9.7 just to show that it's the same results
[root@xmpp01 tmp]# dnf reposync --disablerepo=* --enablerepo=appstream --releasever 9.7 -u
. . .
http://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/Packages/z/zziplib-0.13.71-12.el9.i686.rpm
http://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/Packages/z/zziplib-0.13.71-12.el9.x86_64.rpm
http://dl.rockylinux.org/pub/rocky/9.7/AppStream/x86_64/os/Packages/z/zziplib-utils-0.13.71-12.el9.x86_64.rpm
## I'll grep for el10 to show that only el9 content is served from a 9 repository
[root@xmpp01 tmp]# dnf reposync --disablerepo=* --enablerepo=appstream --releasever 9.7 -u | grep '\.el10'
[root@xmpp01 tmp]#
## No results
I’ll even go to our repo servers and look.
repo# pwd
/mnt/repos-production/mirror/pub/rocky/9.7/AppStream/x86_64/os/repodata
repo# zgrep -c '\.el9' 1b8e070009b5e658908f488f640ed9b4e511277d584edc9f00e0643ae867957f-primary.xml.gz
49531
repo# zgrep -c '\.el10' 1b8e070009b5e658908f488f640ed9b4e511277d584edc9f00e0643ae867957f-primary.xml.gz
0
repo# pwd
/mnt/repos-production/mirror/pub/rocky/9.7/BaseOS/x86_64/os/repodata
repo# zgrep -c '\.el10' f4c31849ae4939e90c7b541b24a1a82c3861c367a65bb77e09856c2f1907eb74-primary.xml.gz
0
repo# zgrep -c '\.el9' f4c31849ae4939e90c7b541b24a1a82c3861c367a65bb77e09856c2f1907eb74-primary.xml.gz
8189
There is no reference to el10 packages in our repo data.