[MacPorts] #39797: axel @ 2.4 distfile download unstable

[MacPorts]

#39797: axel @ 2.4 distfile download unstable
-----------------------------+--------------------------------
  Reporter:  sharon.dagan@…  |      Owner:  macports-tickets@…
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.1.3
Resolution:                  |   Keywords:
      Port:  axel            |
-----------------------------+--------------------------------

Comment (by ryandesign@…):

 Replying to [comment:5 ciserlohn@…]:
 > The distfile download is somewhat unstable, have a look a the buildbot
 logs from r108319 and r108321:
 >
 > * https://build.macports.org/builders/buildports-snowleopard-
 x86_64/builds/18862
 > * https://build.macports.org/builders/buildports-mtln-x86_64/builds/6274
 > * https://build.macports.org/builders/buildports-lion-
 x86_64/builds/12417

 Here, the old correct 50704-byte distfile was downloaded from
 distfiles.macports.org.

 > * https://build.macports.org/builders/buildports-snowleopard-
 x86_64/builds/18864
 > * https://build.macports.org/builders/buildports-mtln-x86_64/builds/6276
 > * https://build.macports.org/builders/buildports-lion-
 x86_64/builds/12419
 >
 > Sometimes it downloads the correct distfile, sometime a zero length
 distfile.

 By this time, the primary distfiles mirror had noticed that the new
 checksums in the portfile did not match the old distfile, so it deleted
 the old distfile and replaced it with the new 0-byte distfile from
 upstream.


 Replying to [comment:7 ciserlohn@…]:
 > The mirror servers had no distfile for axel 2.4, only for axel 2.3. I've
 checked that before the r108319 commit.

 Sure they do. For example:
 http://sea.us.distfiles.macports.org/macports/distfiles/axel/axel-2.4.tar.gz;
 I checked this before reopening the ticket.

-- 
Ticket URL: <https://trac.macports.org/ticket/39797#comment:8>
MacPorts <http://www.macports.org/>
Ports system for OS X