[MacPorts] #36301: py26-mysql package exists but its rmd160 file does not (was: py26-mysql ; error 404)

[MacPorts]

#36301: py26-mysql package exists but its rmd160 file does not
-----------------------------+---------------------
  Reporter:  hani.jann@…     |      Owner:  admin@…
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:  2.1.2
Resolution:                  |   Keywords:
      Port:  py26-mysql      |
-----------------------------+---------------------
Changes (by ryandesign@…):

 * owner:  rwilcox@… => admin@…
 * cc: rwilcox@…, ryandesign@… (added)
 * component:  ports => server/hosting


Comment:

 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
 [http://packages.macports.org/py26-mysql/ 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/36301#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS