Opened 12 years ago
Closed 8 years ago
#36301 closed defect (fixed)
py26-mysql package exists but its rmd160 file does not
Reported by: | hani.jann@… | Owned by: | admin@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | server/hosting | Version: | 2.1.2 |
Keywords: | Cc: | rwilcox (Ryan Wilcox), ryandesign (Ryan Carsten Schmidt) | |
Port: | py26-mysql |
Description
Hello, I enjoy my first bug report :)
I want to install py26-mysql on my mac but I get this error :
Error: Target org.macports.archivefetch returned: Failed to fetch signature for archive: The requested URL returned error: 404 Log for py26-mysql is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-mysql/py26-mysql/main.log Error: Status 1 encountered during processing.
Could someone explain me how to resolve that.
See you soon.
Attachments (1)
Change History (8)
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to rwilcox@… |
---|---|
Port: | py26-mysql added |
Changed 12 years ago by hani.jann@…
comment:2 Changed 12 years ago by hani.jann@…
I am currently running Snow Leopard.
I have joined the main.log file.
See you.
comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | rwilcox@… ryandesign@… added |
---|---|
Component: | ports → server/hosting |
Owner: | changed from rwilcox@… to admin@… |
Summary: | py26-mysql ; error 404 → py26-mysql package exists but its rmd160 file does not |
Ah, I see:
:msg:archivefetch ---> Attempting to fetch py26-mysql-1.2.3_0+mysql5.darwin_10.x86_64.tbz2 from http://packages.macports.org/py26-mysql :msg:archivefetch ---> Attempting to fetch py26-mysql-1.2.3_0+mysql5.darwin_10.x86_64.tbz2.rmd160 from http://packages.macports.org/py26-mysql :debug:archivefetch The requested URL returned error: 404
The archive itself fetched just fine, but its rmd160 hash file is not found. This is confirmed by looking in the py26-mysql directory on the packages server. We had a problem with our upload script some time ago that would sometimes lead to this situation. The problem with the script was resolved but apparently not all affected archives were removed from the packages server. Bill, could you maybe just delete all packages from the server that don't have a corresponding rmd160 file?
As for how to get around the problem now, it's simple: run "sudo port selfupdate" and try again. You're trying to fetch py26-mysql @1.2.3_0, but I updated the port to 1.2.3_1 over two months ago in r95500.
comment:4 Changed 12 years ago by hani.jann@…
When I run "sudo port -d selfupdate", i get this:
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs ---> Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Connection refused (61) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-40/rsync/clientserver.c(105) [receiver=2.6.9] shell command "/usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs" returned error 10 DEBUG: Error synchronizing MacPorts sources: shell command failed (see log for details) while executing "macports::selfupdate [array get global_options] base_updated" Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details)
comment:5 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Sounds like your network blocks rsync traffic. If you cannot resolve that problem with your network administrator, then you'll have to update your ports tree via Subversion or via the daily ports tarball.
comment:6 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from admin@… to admin@… |
---|---|
Status: | new → assigned |
comment:7 Changed 8 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Seems to be resolved.
You haven't shown us the entire error, so we don't know what archive it was trying to fetch. But we only have packages for Snow Leopard and Lion at this time, and only using the default variants, so if you're trying to install something different, then it would be completely understandable for the archive fetch to fail, and that should not necessarily lead to failure to install the port; in those cases, MacPorts should try to download the source and compile it on your system. Did that not happen? Please attach the entire main.log so we can see what happened.