Skip to content
Snippets Groups Projects
  1. Aug 02, 2023
  2. Aug 01, 2023
    • Joey Hess's avatar
      stack.yaml: Update to build with ghc-9.6.2 and aws-0.24 · 6da6449f
      Joey Hess authored
      This enables some new features that need the new aws.
      
      Use http-client-restricted-0.1.0 because it uses the crypton side of the
      cryptonite/crypton fork, which seems to be needed for ghc-9.6.2.
      
      Dependency on connection removed because of the cryptonite/crypton fork.
      This avoids needing a build flag. It was only used to throw a typed
      exception in Utility.Url, which nothing depended on.
      
      Used a fork of bloomfilter because it's not being maintained and no longer
      builds as-of this ghc version. (I have been trying to contact its
      maintainer about it, and emailed him today suggesting I take over the
      package.)
      
      Sponsored-by: Brock Spratlen on Patreon
      6da6449f
  3. Feb 20, 2023
    • Joey Hess's avatar
      Revert "stack.yaml: Update to lts-19.33 and aws-0.24" · 8f2829e6
      Joey Hess authored
      This reverts commit 648e59ca.
      
      Failed to build on windows, because
      
             In the dependencies for haskeline-0.8.2:
                 Win32-2.11.1.0 from Stack configuration does not match >=2.1 && <2.10 || >=2.12 (latest
                                matching version is 2.13.4.0)
      
      jkniiv did find a solution that builds:
      
      -- Win32-2.11.1.0
      +- Win32-2.9.0.0
      +- Cabal-3.6.3.0
      +- directory-1.3.7.1
      +- process-1.6.17.0
      +- time-1.11.1.2
      
      But that is a quite old version of Win32 and risks bugs from it, and bumping
      Cabal and directory to newer than lts-19.33 has seems also likely to be risky.
      
      So, I've given up. aws-0.24 won't be able to be in the stack build until
      there's a stackage lts (or nightly) that has filepath (>=1.4.100.0),
      which will not happen until sometime after the next ghc release.
      8f2829e6
  4. Feb 15, 2023
    • Joey Hess's avatar
      stack.yaml: Update to lts-19.33 and aws-0.24 · 648e59ca
      Joey Hess authored
      This enables some new features that need the new aws.
      
      Win32 downgraded from the version in lts-19.33 because git-annex does not build
      with that version, and newer versions of Win32 need a newer filepath version,
      which can't be upgraded while using lts-19.33.
      
      Sponsored-By: Brett Eisenberg on Patreon
      648e59ca
  5. Jan 04, 2023
  6. Dec 26, 2022
    • Joey Hess's avatar
      Removed the vendored git-lfs and the GitLfs build flag · efda8114
      Joey Hess authored
      AFAICS all git-annex builds are using the git-lfs library not the vendored
      copy.
      
      Debian stable does have a too old haskell-git-lfs package to be able to
      build git-annex from source, but there is not currently a backport of a
      recent git-annex to Debian stable. And if they update the backport at some
      point, they should be able to backport the library too.
      
      Sponsored-by: Svenne Krap on Patreon
      efda8114
  7. Nov 14, 2022
    • Joey Hess's avatar
      revert change to use lts-19.32 · def779b2
      Joey Hess authored
      This reverts commit 15dd7fe8.
      
      aws 0.23 is not used any longer, so read-only S3 import won't be
      supported yet when building with stack.
      
      That commit broke the build on windows, because the new version of Win32 that
      was included (because the old one does not work with this lts version)
      needs a version of filepath that is newer than the one bundled with the
      ghc in that lts version. It is not possible to override that to a newer
      filepath.
      
      Seems that the only solution to get aws 0.23 will be to wait for a ghc that
      contains filepath 1.4.100.0. No ghc yet contains it. (Backporting the Win32
      fix to a point release version that does not include this bleeding edge
      filepath would also resolve it, but seems unlikely to happen.)
      
      Sponsored-by: Jarkko Kniivilä on Patreon
      def779b2
  8. Nov 09, 2022
  9. Nov 04, 2022
    • Joey Hess's avatar
      complete support for S3 signature=anonymous · e1009939
      Joey Hess authored
      aws-0.23 has been released.
      
      When built with an older aws, initremote will error out when run
      with signature=anonymous. And when a remote has been initialized with
      that by a version of git-annex that does support it, older versions will
      fail when the remote is accessed, with a useful error message.
      
      Sponsored-by: Dartmouth College's DANDI project
      e1009939
    • Joey Hess's avatar
      revert demo changes to stack.yaml · f3fbdddb
      Joey Hess authored
      done to test aws before releasing it
      f3fbdddb
  10. Oct 10, 2022
    • Joey Hess's avatar
      S3: Support signature=anonymous to access a S3 bucket anonymously · ca91c3ba
      Joey Hess authored
      This can be used, for example, with importtree=yes to import from a public
      bucket.
      
      This needs a patch that has not yet landed in the aws library, and will
      need to be adjusted to support compiling with old versions of the library,
      so is not yet suitable for merging.
      See https://github.com/aristidb/aws/pull/281
      
      The stack.yaml changes are provided to show how to build against the aws
      fork and will need to be reverted as well.
      
      Sponsored-by: Dartmouth College's DANDI project
      ca91c3ba
  11. Aug 29, 2022
    • Joey Hess's avatar
      move assistant and webapp build-depends into main build-depends · 78440ca3
      Joey Hess authored
      For some reason, cabal 3.4.1.0 builds w/o the assistant and webapp,
      even when the flag is explicitly turned on. Moving the build-depends from
      inside the if flag section to the main build-depends somehow fixes this.
      
      Since the webapp build deps are thus always available, there is no reason
      not to build the webapp when building the assistant. So, got rid of the
      webapp build flag. Kept the assistant build flag for now, since building
      without it does at least still speed up the build.
      
      Sponsored-by: Brock Spratlen on Patreon
      78440ca3
  12. Aug 01, 2022
  13. Jul 29, 2022
    • Joey Hess's avatar
      remove explicit-setup-deps · b2d2711b
      Joey Hess authored
      This has not been needed since stack <1.4.0, and even the i386ancent
      build uses stack 2.1.1.
      
      Stack 2.7.5 seems to have forgotten about this old config and warns
      about it, so this avoids that warning.
      
      The libtinfo-dev was added to the docs at the same time, I assume it is
      also not necessary.
      b2d2711b
  14. Jul 26, 2022
    • Joey Hess's avatar
      stack.yaml: Updated to lts-19.16 · b5dc0409
      Joey Hess authored
      Last try at this broke on windows with a problem installing ghc, but I
      wanted to try again.
      
      Also this has a version of aws that allows using aeson 2.0, which has a
      potential security fix.
      b5dc0409
  15. Jul 05, 2022
    • Joey Hess's avatar
      Revert "lts-19.13 (ghc 9.0.2)" · d01530ac
      Joey Hess authored
      This reverts commit d2bc2683.
      
      That seemed to break building on windows, before it starts building
      git-annex at all, it tried to install ghc and something blew up:
      
      Processing archive: C:\Users\runneradmin\AppData\Local\Programs\stack\x86_64-windows\ghc-9.0.2.tar.xz
      Extracting  ghc-9.0.2.tar
      ...
      Extracted total of 11790 files from ghc-9.0.2.tar
      C:\Users\runneradmin\AppData\Local\Programs\stack\x86_64-windows\ghc-9.0.2-tmp-6d0fbe7f3b29e56c\ghc-9.0.2\: renameDirectory:pathIsDirectory:CreateFile "\\\\?\\C:\\Users\\runneradmin\\AppData\\Local\\Programs\\stack\\x86_64-windows\\ghc-9.0.2-tmp-6d0fbe7f3b29e56c\\ghc-9.0.2\\": does not exist (The system cannot find the file specified.)
      
      Hopefully a newer ghc version or updated stackage version will fix this
      at some point, in the meantime revert it.
      d01530ac
  16. Jun 29, 2022
  17. Jun 28, 2022
  18. Mar 22, 2022
    • Joey Hess's avatar
      Removed the NetworkBSD build flag · a460aa8b
      Joey Hess authored
      Debian stable and the i386ancient build both have a new enough network
      to not need this flag any longer.
      
      Sponsored-by: Svenne Krap on Patreon
      a460aa8b
    • Joey Hess's avatar
      remove vendored http-client-restricted · 982eb7ed
      Joey Hess authored
      Removed vendored copy of http-client-restricted, and removed the
      HttpClientRestricted build flag that avoided that dependency.
      
      http-client-restricted is in Debian stable, and the i386ancient build also
      uses it, so I think this vendored copy is no longer needed.
      
      Sponsored-by: Noam Kremen on Patreon
      982eb7ed
  19. Nov 16, 2021
  20. Oct 19, 2021
  21. Oct 18, 2021
  22. Dec 29, 2020
  23. Oct 02, 2020
  24. Sep 08, 2020
    • Joey Hess's avatar
      Removed the S3 and WebDAV build flags · 6ea511be
      Joey Hess authored
      So these special remotes are always supported.
      
      IIRC these build flags were added because the dep chains were a bit too
      long, or perhaps because the libraries were not available in Debian stable,
      or something like that. That was long ago, those reasons no longer apply,
      and users get confused when builtin special remotes are not available, so
      it seems best to remove the build flags now.
      
      If this does cause a problem it can be reverted of course..
      
      This commit was sponsored by Jochen Bartl on Patreon.
      6ea511be
  25. Aug 24, 2020
    • Joey Hess's avatar
      stack.yaml: Updated to lts-16.10 · 27329f0b
      Joey Hess authored
      Needs stack version 2.3 to build, which has only recently made it into
      debian unstable.
      
      This commit was sponsored by Jake Vosloo on Patreon.
      27329f0b
  26. Jun 30, 2020
    • Joey Hess's avatar
      fix stack file syntax and deps · 761252ce
      Joey Hess authored
      In stack-lts-12.14.yaml, there were dep issues using the new libraries,
      which may not be resolvable with those old versions. Didn't check, just
      disabled using the libraries there, which will hold us for a couple
      years.
      
      (It would probably be easy enough to relax some of the dep versions in
      http-client-restricted and git-lfs to the older versions.)
      761252ce
    • Joey Hess's avatar
      add new deps · 10abf964
      Joey Hess authored
      10abf964
  27. Jun 22, 2020
    • Joey Hess's avatar
      Build with the http-client-restricted library when available · 104b3a9c
      Joey Hess authored
      Otherwise use the vendored copy as before.
      
      The library is in Debian testing but not stable. Once it reaches
      stable, the vendored copy can be removed.
      
      Did not add it to debian/control because IIRC that's used to build
      git-annex on stable too, possibly. However, the Debian maintainer will
      probably want to make the package depend on libghc-http-client-restricted-dev
      
      This commit was sponsored by Ilya Shlyakhter on Patreon.
      104b3a9c
    • Joey Hess's avatar
      Build with the git-lfs library when available · 01eb863a
      Joey Hess authored
      Otherwise use the vendored copy as before.
      
      The library is in Debian testing but not stable. Once it reaches
      stable, the vendored copy can be removed.
      
      Did not add it to debian/control because IIRC that's used to build
      git-annex on stable too, possibly. However, the Debian maintainer will
      probably want to make the package depend on libghc-git-lfs-dev.
      
      This commit was sponsored by Ilya Shlyakhter on Patreon.
      01eb863a
  28. Mar 02, 2020
  29. Dec 30, 2019
  30. Dec 27, 2019
  31. Dec 18, 2019
  32. Dec 11, 2019
    • Joey Hess's avatar
      use filepath-bytestring for annex object manipulations · c1921177
      Joey Hess authored
      git-annex find is now RawFilePath end to end, no string conversions.
      So is git-annex get when it does not need to get anything.
      So this is a major milestone on optimisation.
      
      Benchmarks indicate around 30% speedup in both commands.
      
      Probably many other performance improvements. All or nearly all places
      where a file is statted use RawFilePath now.
      c1921177