The source filename for s3switch is s3ssrc.zip, regardless of version. When you emerge the current stable ebuild, s3switch-1999082 it fetches the most recent s3ssrc.zip which, of course, doesn't match the digest for the file that this ebuild was expecting. Result: zach@tuna s3switch $ RESTRICT="nomirror" sudo emerge s3switch-19990826.ebuild Calculating dependencies ...done! >>> emerge (1 of 1) sys-apps/s3switch-19990826 to / >>> Downloading http://www.probo.com/timr/s3ssrc.zip --21:33:54-- http://www.probo.com/timr/s3ssrc.zip => `/usr/portage/distfiles/s3ssrc.zip' Resolving www.probo.com... 63.105.24.220 Connecting to www.probo.com[63.105.24.220]:80... connected. HTTP request sent, awaiting response... 200 OK Length: 8,854 [application/zip] 100%[====================================>] 8,854 14.87K/s 21:33:55 (14.85 KB/s) - `/usr/portage/distfiles/s3ssrc.zip' saved [8854/8854] !!! Couldn't download s3ssrc.zip. Aborting. The only way I could get this package to emerge was to manually hack the digest file to have the MD5 sum and file size for the zip file it downloaded. It seems there is no way to download the exact file that ebuild is expecting - even the mirrors all have the latest version. MD5 1328b070343ac79c5ed4c613a1113754 s3ssrc.zip 8854 What can we do here? 1) Get the author to add a version to his filenames. 2) Replace current ebuild with a single s3switch.ebuild that always grabs the latest version. ?
probbly this is related.. >>> Downloading http://www.probo.com/timr/s3ssrc.zip --00:49:35-- http://www.probo.com/timr/s3ssrc.zip => `/usr/portage/distfiles/s3ssrc.zip' Resolving www.probo.com... 63.105.24.220 Connecting to www.probo.com[63.105.24.220]:80... connected. HTTP richiesta inviata, aspetto la risposta... 416 Requested Range Not Satisfiable The file is already fully retrieved; nothing to do. !!! Couldn't download s3ssrc.zip. Aborting.
fixed digest in cvs
