@@ 123,6 123,7 @@
#:use-module (gnu packages tls)
#:use-module (gnu packages valgrind)
#:use-module (gnu packages version-control)
+ #:use-module (gnu packages vim)
#:use-module (gnu packages web)
#:use-module (gnu packages xml))
@@ 949,36 950,24 @@ minimal bcachefs-tools package. It is meant to be used in initrds.")
(define-public exfatprogs
(package
(name "exfatprogs")
- (version "1.2.5")
+ (version "1.2.9")
(source
(origin
(method git-fetch)
(uri (git-reference
- (url "https://github.com/exfatprogs/exfatprogs")
- (commit version)))
+ (url "https://github.com/exfatprogs/exfatprogs")
+ (commit version)))
(file-name (git-file-name name version))
(sha256
- (base32 "0plj52kjvhy94hdk0bq8bc7ql6yh44x76kryxhn46vwbxayv790j"))))
+ (base32 "0phimvrm13kjrfdlsvzkapy8hgfgf4w62yz3zg4y4yjvzsal2hqh"))))
(build-system gnu-build-system)
(arguments
(list
#:configure-flags
#~(list "--disable-static")
- #:phases
- #~(modify-phases %standard-phases
- (replace 'check
- (lambda* (#:key tests? #:allow-other-keys)
- (when tests?
- (setenv "FSCK1" "../fsck/fsck.exfat")
- ;; Upstream CI uses a second FSCK provided by its host operating
- ;; system to verify the results of the newly-built one. That
- ;; makes no sense in Guix, but we can detect crashes, unexpected
- ;; inconsistencies, and other badness by testing with only one.
- (setenv "FSCK2" (getenv "FSCK1"))
- (with-directory-excursion "tests"
- (invoke "./test_fsck.sh"))))))))
+ #:tests? #f)) ;the tests require QEMU
(native-inputs
- (list autoconf automake libtool pkg-config))
+ (list autoconf-2.72 automake libtool pkg-config))
(home-page "https://github.com/exfatprogs/exfatprogs")
(synopsis "Tools to create, check, and repair exFAT file systems")
(description