Bug 4434

Summary: sa-update fail
Product: Mageia Reporter: Michael Scherer <misc>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: Normal    
Version: 1   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: spamassassin CVE:
Status comment:

Description Michael Scherer 2012-02-07 23:08:25 CET 
Description of problem:
It seems that since we ship a svn snapshot of spamassassin on the stable release, the sa-update tool fail.

# sa-update 
http: GET http://www.sa-update.pccc.com/3.tar.gz request failed: 404 Not Found: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /3.tar.gz was not found on this server.</p> <hr> <address>Apache/2.2.21 (Unix) Server at www.sa-update.pccc.com Port 80</address> </body></html> 
http: GET http://daryl.dostech.ca/sa-update/asf/3.tar.gz request failed: 404 Not Found: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /sa-update/asf/3.tar.gz was not found on this server.</p> <hr> <address>Apache/2.2.6 (Fedora) Server at daryl.dostech.ca Port 80</address> </body></html> 
http: GET http://sa-update.secnap.net/3.tar.gz request failed: 404 Not Found: <html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <hr><center>nginx/1.0.5</center> </body> </html> 
channel: could not find working mirror, channel failed


How reproducible:
each time

Steps to Reproduce:
1. run "sa-update" as root


The problem is fixed in cauldron with a upgrade to the stable version ( 3.2.2 ), and per the update policy, should be also pushed to stable ( since the svn version we currently have is not supported, and broken due to modification of the online repository.

As a side note, that's broken on mageia server, and could explain why we received a spam in the previous days.
Comment 1 Manuel Hiebel 2012-02-07 23:16:13 CET 
already reported

*** This bug has been marked as a duplicate of bug 3814 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE