Opened 12 years ago

Closed 12 years ago

#1575 closed defect (fixed)

Error Downloading Packages

Reported by: jeck Owned by: nosnilmot
Milestone: Component: pidgin (gtk)
Version: 2.0.1 Keywords:
Cc:

Description

After adding pidgin.repo yum produces this output:

 yum update
Loading "installonlyn" plugin
Setting up Update Process
Setting up repositories
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for pidgin to pack into transaction set.
pidgin-2.0.1-0.el5.i386.r 100% |=========================|  66 kB    00:00     
---> Package pidgin.i386 0:2.0.1-0.el5 set to be updated
--> Running transaction check
--> Processing Dependency: libpurple.so.0 for package: pidgin
--> Processing Dependency: perl(Purple) for package: pidgin
--> Processing Dependency: libgaim.so.0 for package: nautilus-sendto
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for libpurple to pack into transaction set.
libpurple-2.0.1-0.el5.i38 100% |=========================|  36 kB    00:00     
---> Package libpurple.i386 0:2.0.1-0.el5 set to be updated
--> Running transaction check
--> Processing Dependency: libtk8.4.so for package: libpurple
--> Processing Dependency: libgaim.so.0 for package: nautilus-sendto
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for tk to pack into transaction set.
tk-8.4.13-3.fc6.i386.rpm  100% |=========================|  27 kB    00:00     
---> Package tk.i386 0:8.4.13-3.fc6 set to be updated
--> Running transaction check
--> Processing Dependency: libgaim.so.0 for package: nautilus-sendto
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 pidgin                  i386       2.0.1-0.el5      pidgin            6.0 M
     replacing  gaim.i386 2:2.0.0-0.28.beta5.el5

Installing for dependencies:
 libpurple               i386       2.0.1-0.el5      pidgin            6.2 M
 tk                      i386       8.4.13-3.fc6     base              889 k

Transaction Summary
=============================================================================
Install      3 Package(s)         
Update       0 Package(s)         
Remove       0 Package(s)         

Total download size: 13 M
Is this ok [y/N]: y
Downloading Packages:
http://rpm.pidgin.im/centos/5/i386/pidgin-2.0.1-0.el5.i386.rpm: [Errno 12] Timeout: <urlopen error timed out>
Trying other mirror.
(2/3): tk-8.4.13-3.fc6.i3 100% |=========================| 889 kB    00:07     

http://rpm.pidgin.im/centos/5/i386/libpurple-2.0.1-0.el5.i386.rpm: [Errno 12] Timeout: <urlopen error timed out>
Trying other mirror.


Error Downloading Packages:
  pidgin - 2.0.1-0.el5.i386: failure: pidgin-2.0.1-0.el5.i386.rpm from pidgin: [Errno 256] No more mirrors to try.
  libpurple - 2.0.1-0.el5.i386: failure: libpurple-2.0.1-0.el5.i386.rpm from pidgin: [Errno 256] No more mirrors to try.

Accessing the repo per Firefox returns "403 Forbidden; You don't have permission to access /centos/5/i386/ on this server". Is there something wrong with the server setup?

Change History (2)

comment:1 Changed 12 years ago by kstange

  • Component changed from webpage to pidgin (gtk)
  • Owner set to nosnilmot

This is certainly not a web page ticket, but I don't know what it is.

comment:2 Changed 12 years ago by nosnilmot

  • Resolution set to fixed
  • Status changed from new to closed

There is not much we can do about sourceforge mirrors being slightly unreliable, but retrying (possibly a few times) should fix it if it happens again. I've also made http://rpm.pidgin.im/ browsable (and pretty!)

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!