Hello there, When I want to upgrade my box from 33 to 34 I have faced an issue with this message: (Errors during downloading metadata for repository 'fedora-cisco-openh264': - Status code: 404 for https://codecs.fedoraproject.org/openh264/34/x86_64/repodata/repomd.xml) The file in 33 repo is in a different location than which is in 34, this is for 33 and 34: https://codecs.fedoraproject.org/openh264/33/x86_64/repodata/repomd.xml https://codecs.fedoraproject.org/openh264/34/x86_64/os/repodata/repomd.xml So, in 34 the xml file is in /os/.. while in 33 there isn't /os/ directory. This issue in other words there is no matching between the two repos location in both Fedora releases. thank you.
This is being looked at as part of releng https://pagure.io/releng/issue/10006
Metadata Update from @smooge: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
I believe this one here is a mirrormanager issue and unrelated to the releng ticket. Mirrormanager's redirect is incorrect for the f34 openh264 repo.
Not sure I understand it. Looking at the metalinks I always see the same result:
https://codecs.fedoraproject.org/openh264/32/x86_64/os/repodata/repomd.xml https://codecs.fedoraproject.org/openh264/33/x86_64/os/repodata/repomd.xml https://codecs.fedoraproject.org/openh264/34/x86_64/os/repodata/repomd.xml
All of these file exist. Can you be more specific where the error is?
Ah, sorry, I was commenting without actually checking things :)
@jalalsfs, what does your /etc/yum.repos.d/fedora-cisco-openh264.repo look like?
Not sure I understand it. Looking at the metalinks I always see the same result: https://codecs.fedoraproject.org/openh264/32/x86_64/os/repodata/repomd.xml https://codecs.fedoraproject.org/openh264/33/x86_64/os/repodata/repomd.xml https://codecs.fedoraproject.org/openh264/34/x86_64/os/repodata/repomd.xml All of these file exist. Can you be more specific where the error is?
In the actual fedora-cisco-openh264.repo in F33 it looks for https://codecs.fedoraproject.org/openh264/33/x86_64/repodata/repomd.xml without "/os/" folder, but when the file want to look to the same file in 34, it doesn't find it because there is another folder in between, by the way I have to edit the file repo manually to upgrade.
Ah, sorry, I was commenting without actually checking things :) @jalalsfs, what does your /etc/yum.repos.d/fedora-cisco-openh264.repo look like?
like this: baseurl=https://codecs.fedoraproject.org/openh264/$releasever/$basearch/ but I have changed it to baseurl=https://codecs.fedoraproject.org/openh264/$releasever/$basearch/os/ to continue upgrading my system.
We changed it to use metalink instead of baseurl before the F33 release and fedora-repos-33-3.noarch it instead has:
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-$releasever&arch=$basearch
I guess you somehow have the old .repo contents still around from before we did the change. I wonder if we should some kind of workaround for that in place for a bit -- a symlink on the server, maybe?
We changed it to use metalink instead of baseurl before the F33 release and fedora-repos-33-3.noarch it instead has: metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-$releasever&arch=$basearch I guess you somehow have the old .repo contents still around from before we did the change. I wonder if we should some kind of workaround for that in place for a bit -- a symlink on the server, maybe?
I think you are completely right, I have my system I think since F26, so just upgrading fedora from release to another, I see on the yum.repos.d folder two file of "fedora-cisco-openh264.repo" the other file with this name "fedora-cisco-openh264.repo.rpmnew" that means of you said. thank you Kalev
Login to comment on this ticket.