Package Details: wimlib 1.11.0-1

Git Clone URL: https://aur.archlinux.org/wimlib.git (read-only)
Package Base: wimlib
Description: A library and program to extract, create, and modify WIM files
Upstream URL: https://wimlib.net
Licenses: custom
Submitter: Synchronicity
Maintainer: Synchronicity
Last Packager: Synchronicity
Votes: 63
Popularity: 0.809336
First Submitted: 2012-05-02 03:25
Last Updated: 2017-01-18 06:53

Dependencies (9)

Required by (0)

Sources (1)

Latest Comments

Synchronicity commented on 2017-02-11 23:53

If the mount test is failing for you, then please send me your test-suite.log, and let me know whether you are using a non-standard kernel such as grsecurity, and what the permissions on your /dev/fuse are.

wat commented on 2017-02-11 21:20

I am having the same problem as rasoran

rasoran commented on 2017-01-22 00:12

wimlib 1.11.0-1 is failing a test

FAIL: tests/test-imagex-mount

swiftgeek commented on 2016-05-19 09:48

Got new issue - due to GUID not being the same as boot.wim from source Win10 install image, mkwinpeimg creates unbootable image :(
EDIT:Sorry i think i made the same mistake again - it requires mbr partition scheme to boot, no change to bcd needed

tancrackers commented on 2016-03-12 22:45

Weird. It worked now O_o
Nevermind!

Synchronicity commented on 2016-03-12 15:22

Please send me your test-suite.log.

tancrackers commented on 2016-03-12 12:19

I get this error:

Makefile:2063: recipe for target 'test-suite.log' failed
make[2]: *** [test-suite.log] Error 1
make[2]: Leaving directory '/tmp/yaourt-tmp-john/aur-wimlib/src/wimlib-1.9.1'
Makefile:2169: recipe for target 'check-TESTS' failed
make[1]: *** [check-TESTS] Error 2
make[1]: Leaving directory '/tmp/yaourt-tmp-john/aur-wimlib/src/wimlib-1.9.1'
Makefile:2403: recipe for target 'check-am' failed
make: *** [check-am] Error 2

Synchronicity commented on 2016-02-02 01:19

Thanks. I will remove ntfsprogs from the PKGBUILD in the next version.

chungy commented on 2016-02-01 15:59

ntfsprogs can be removed from the optdepends. They've been part of ntfs-3g for a while now.

Synchronicity commented on 2015-11-14 20:36

v1.8.3 of the package, just uploaded, addresses the issue reported earlier in these comments by 'techryda'.

All comments