pipelight fedora 20 404 repository error

Asked by Feared Takyon

The follow below shows my issue. I've reinstalled fedora 20 and this now seems to be happening while previously this repository worked fine as well as pipelight. I've looked around for other repositorys and found one named postinstallerf however it doesn't work either.

I'm on Fedora 20 x86_64 running Gnome 3.10

I don't believe I'm doing anything wrong. I've changed Fedora_19 to Fedora_20 on the line given on the pipelight installation page and I've had this working before on my previous installation of Fedora 20 running gnome 3.12.

==============================================
">sudo yum install pipelight
Loaded plugins: langpacks, refresh-packagekit
fedora/20/x86_64/metalink | 18 kB 00:00:00
home_DarkPlayer_Pipelight | 1.6 kB 00:00:00
rpmfusion-free | 3.3 kB 00:00:00
rpmfusion-free-updates | 3.3 kB 00:00:00
rpmfusion-nonfree | 3.3 kB 00:00:00
rpmfusion-nonfree-updates | 3.3 kB 00:00:00
updates/20/x86_64/metalink | 16 kB 00:00:00
home_DarkPlayer_Pipelight/prim FAILED
http://download.opensuse.org/repositories/home%3A/DarkPlayer%3A/Pipelight/Fedora_20/repodata/be67266a967fe920b589cb21f88a26442b06c6abc7c17e17de54278d86f7b5bd-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://download.opensuse.org/repositories/home%3A/DarkPlayer%3A/Pipelight/Fedora_20/repodata/be67266a967fe920b589cb21f88a26442b06c6abc7c17e17de54278d86f7b5bd-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.

 One of the configured repositories failed (Pipelight (Fedora_20)),
 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).

     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 home_DarkPlayer_Pipelight

     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=home_DarkPlayer_Pipelight.skip_if_unavailable=true

failure: repodata/be67266a967fe920b589cb21f88a26442b06c6abc7c17e17de54278d86f7b5bd-primary.xml.gz from home_DarkPlayer_Pipelight: [Errno 256] No more mirrors to try.
http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Fedora_20/repodata/be67266a967fe920b589cb21f88a26442b06c6abc7c17e17de54278d86f7b5bd-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found"

Question information

Language:
English Edit question
Status:
Answered
For:
Pipelight Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Sebastian Lackner (slackner) said :
#1

Hi,

thanks for reporting this problem.

Our fedora 20 repositories are hosted on the OpenSUSE build server
system, and it seems like they currently have some problems with their
mirrors. When I try to download the files from my location everything
works well, but when manually checking out some other mirrors I can see
that some of them still contain outdated data or miss some packages.

We reported this problem to the OpenSUSE build server team, and they
promised to take a look at it till monday. I'll report back when I know
some more details.

Regards,
Sebastian

Am 25.05.2014 19:21, schrieb Feared Takyon:
> New question #249259 on Pipelight:
> https://answers.launchpad.net/pipelight/+question/249259
>
> The follow below shows my issue. I've reinstalled fedora 20 and this now seems to be happening while previously this repository worked fine as well as pipelight. I've looked around for other repositorys and found one named postinstallerf however it doesn't work either.
>
> I'm on Fedora 20 x86_64 running Gnome 3.10
>
> I don't believe I'm doing anything wrong. I've changed Fedora_19 to Fedora_20 on the line given on the pipelight installation page and I've had this working before on my previous installation of Fedora 20 running gnome 3.12.
>
> ==============================================
> ">sudo yum install pipelight
> Loaded plugins: langpacks, refresh-packagekit
> fedora/20/x86_64/metalink | 18 kB 00:00:00
> home_DarkPlayer_Pipelight | 1.6 kB 00:00:00
> rpmfusion-free | 3.3 kB 00:00:00
> rpmfusion-free-updates | 3.3 kB 00:00:00
> rpmfusion-nonfree | 3.3 kB 00:00:00
> rpmfusion-nonfree-updates | 3.3 kB 00:00:00
> updates/20/x86_64/metalink | 16 kB 00:00:00
> home_DarkPlayer_Pipelight/prim FAILED
> http://download.opensuse.org/repositories/home%3A/DarkPlayer%3A/Pipelight/Fedora_20/repodata/be67266a967fe920b589cb21f88a26442b06c6abc7c17e17de54278d86f7b5bd-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
> http://download.opensuse.org/repositories/home%3A/DarkPlayer%3A/Pipelight/Fedora_20/repodata/be67266a967fe920b589cb21f88a26442b06c6abc7c17e17de54278d86f7b5bd-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
>
>
> One of the configured repositories failed (Pipelight (Fedora_20)),
> 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).
>
> 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 home_DarkPlayer_Pipelight
>
> 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=home_DarkPlayer_Pipelight.skip_if_unavailable=true
>
> failure: repodata/be67266a967fe920b589cb21f88a26442b06c6abc7c17e17de54278d86f7b5bd-primary.xml.gz from home_DarkPlayer_Pipelight: [Errno 256] No more mirrors to try.
> http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Fedora_20/repodata/be67266a967fe920b589cb21f88a26442b06c6abc7c17e17de54278d86f7b5bd-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found"
>

Revision history for this message
Sebastian Lackner (slackner) said :
#2

Did you test again after my last response? As far as I know noone else encountered this problem during the last time, so I assume the OpenSUSE guys must have fixed it. Does it also work for you, now?

Can you help with this problem?

Provide an answer of your own, or ask Feared Takyon for more information if necessary.

To post a message you must log in.