RedHat 7上安装ffmpeg但需要先安装atrpms,未发现404问题

RedHat 7上安装ffmpeg但需要先安装atrpms,未发现404问题

我正在跟进此处给出的说明安装 atrpms 存储库。

设置完所有内容并尝试执行以下操作后:yum install ffmpeg我收到以下错误。该错误表明它是 404 未找到。你现在做什么?

Loaded plugins: product-id, search-disabled-repos, subscription-manager                                                                                                                                                                                               
This system is registered to Red Hat Subscription Management, but is not receiving updates. You can use subscription-manager to assign subscriptions.                                                                                                                 
http://dl.atrpms.net/el7Server-x86_64/atrpms/stable/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found                                                                                                                                                        
Trying other mirror.                                                                                                                                                                                                                                                  
To address this issue please refer to the below knowledge base article                                                                                                                                                                                                
~                                                                                                                                                                                                                                                                     
https://access.redhat.com/articles/1320623                                                                                                                                                                                                                            
~                                                                                                                                                                                                                                                                     
If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.                                                                                                                                                                        
~                                                                                                                                                                                                                                                                     
~                                                                                                                                                                                                                                                                     
~                                                                                                                                                                                                                                                                     
 One of the configured repositories failed (Fedora Core 7Server - x86_64 - ATrpms),                                                                                                                                                                                   
 and yum doesn't have enough cached data to continue. At this point the only                                                                                                                                                                                          
 safe thing yum can do is fail. There are a few ways to work "fix" this:                                                                                                                                                                                              
~                                                                                                                                                                                                                                                                     
     1. Contact the upstream for the repository and get them to fix the problem.                                                                                                                                                                                      
~                                                                                                                                                                                                                                                                     
     2. Reconfigure the baseurl/etc. for the repository, to point to a working                                                                                                                                                                                        
        upstream. This is most often useful if you are using a newer                                                                                                                                                                                                  
        distribution release than is supported by the repository (and the                                                                                                                                                                                             
        packages for the previous distribution release still work).                                                                                                                                                                                                   
                                                                                                                                                                                                                                                    0,0-1         All
     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

            yum-config-manager --disable atrpms

     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=atrpms.skip_if_unavailable=true

failure: repodata/repomd.xml from atrpms: [Errno 256] No more mirrors to try.
http://dl.atrpms.net/el7Server-x86_64/atrpms/stable/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

答案1

您需要查看您创建的文件,其中包含以下内容:

[atrpms]
name=Fedora Core $releasever - $basearch - ATrpms
baseurl=http://dl.atrpms.net/f$releasever-$basearch/atrpms/stable
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
enabled=1
gpgcheck=1

注意 $releasever 和 $basearch。这些需要填写从您的服务器收集的适当信息以匹配正确的链接。

如果您直接访问此处的网址:http://dl.atrpms.net/

您会注意到其适用的所有 Linux 版本。但首先您需要在系统中执行此操作:

rpm-qa'发布'

您将获得需要在该链接中输入的正确版本。

相关内容