Package Details: dislocker 0.7.1-2

Git Clone URL: (read-only)
Package Base: dislocker
Description: Read BitLocker encrypted volumes under Linux
Upstream URL:
Licenses: GPL2
Conflicts: dislocker-git
Submitter: mrxx
Maintainer: mrxx
Last Packager: mrxx
Votes: 15
Popularity: 0.337725
First Submitted: 2014-06-02 17:25
Last Updated: 2017-02-09 16:38

Dependencies (6)

Required by (0)

Sources (1)

Latest Comments

1 2 3 Next › Last »

mrxx commented on 2019-03-11 10:21

GI_Jack, no problems here compiling dislocker on multiple production machines as well as on fresh test VMs.

GI_Jack commented on 2019-03-10 22:43

Looks like it fails compile trying to find ruby.h. Have some kludge:

mrxx commented on 2019-01-23 01:48

pacman calls ldconfig when updating libraries, so most probably it recreated the cache for you.

auroq commented on 2019-01-22 20:23

Hmm. I haven't had a chance to look at this for a while, but today I updated again and re-built and reinstalled dislocker. Now I have no issues. Didn't even have to recreate the linker cache...

mrxx commented on 2019-01-17 15:38

auroq, no problems here with ruby 2.6. Maybe your linker cache is broken. Try to recreate it (as root: ldconfig) Then rebuild the package.

auroq commented on 2019-01-17 01:14

This broke for me after ruby updated to 2.6. I got a message about being missing when trying to mount my drives.

I downgraded back to 2.5 to fix the issue. I haven't investigated enough to know if this could be fixed in the package here or if it's an issue with the source, but I thought I'd comment here in case anyone else has issues.

madman_xxx commented on 2018-11-25 23:09

My bad, was missing that package... Sorry. Classic 'Layer 8 problem' :)

mrxx commented on 2018-11-25 13:13

madman_xxx, please follow "Ensure the base-devel package group is installed"

madman_xxx commented on 2018-11-24 18:25

I have just tried to build this package on a fairly fresh Arch installation and couldn't: "No CMAKE_C_COMPILER could be found." Please include gcc as build-time dependency.

mrxx commented on 2017-02-09 17:19

In v0.7.1, upstream made a mistake in the build script for the man pages. I noticed that and put a workaround in the PKGBUILD.

15 hours later, upstream discovered their error, too. Unfortunately, they decided to do the commit without a new version number, resulting in a tar.gz with the same name, but different sha1sum.