1. 29 Apr, 2019 1 commit
  2. 03 Oct, 2018 2 commits
    • Natanael Copa's avatar
      move logic of curl's http range error to abuild-fetch · c6609b47
      Natanael Copa authored
      Move the logic of deleting partial downloads to abuild-fetch, which
      knows if it is curl or wget that was executed.
      c6609b47
    • Oliver Smith's avatar
      Fix: incomplete partfile gets renamed to distfile · 07d9f3bf
      Oliver Smith authored
      Abuild-fetch uses curl (fallback to wget) to download files. They are
      saved with a ".part" extension first, so they can be resumed if
      necessary. When the download is through, the ".part" extension gets
      removed. However, when the server does not support resume of downloads
      (e.g. GitHub's on the fly generated tarballs), then the ".part"
      extension got removed anyway. Abuild aborts in that case. But when
      running a third time, the distfile exists and it is assumed that this
      is the full download.
      
      Changes:
      * abuild-fetch:
        * Only remove the ".part" extension, when curl/wget exit with 0
        * Pass the exit code from curl/wget as exit code of abuild-fetch
        * Wherever abuild-fetch would return an exit code on its own, the
          codes have been changed to be > 200 (so they don't collide with
          curl's as of now 92 exit codes)
        * Remove undocumented feature of downloading multiple source URLs at
          a time. This doesn't match with the usage description, was not used
          in abuild at all and it would have made it impossible to pass the
          exit code.
      * abuild:
        * After downloading, when curl is installed and abuild-fetch has
          33 as exit code (curl's HTTP range error), then delete the partfile
          and try the download again.
      07d9f3bf
  3. 11 Apr, 2018 1 commit
  4. 21 Jun, 2017 1 commit
  5. 20 May, 2016 1 commit
  6. 16 May, 2016 1 commit
  7. 10 Mar, 2016 1 commit
  8. 08 Oct, 2015 1 commit
  9. 26 Aug, 2015 1 commit
    • Natanael Copa's avatar
      abuild: fix fetch lock file on nfs · 92186b70
      Natanael Copa authored
      flock(2) on an NFS mount will on the server side convert the lock to a
      POSIX lock (fcntl(F_SETLK)). This means that abuild running on NFS
      server and client will create different locks and they will both try
      download same file at same time.
      
      We fix this by creating a small abuild-fetch application that will
      create a POSIX lock which works with NFS.
      92186b70