Arch Linux User Repository

@korimitsu: try to uninstall and then reinstall the package.

Btw. please do not misuse the "Flag package out of date" function for reporting problems. (Install dislocker-git instead if you want to use the latest version.)

dislocker-fuse: error while loading shared libraries: libmbedcrypto.so.6: cannot open shared object file: No such file or directory

VERSION: pamac search dislocker dislocker-noruby 0.7.3-1 AUR Read/write BitLocker-encrypted volumes (no ruby bindings/dependency) dislocker-git 0.7.1.r0.g3939a18-1 AUR FUSE driver to read/write Windows' BitLocker-ed volumes dislocker [Installed] 0.7.3-2 AUR Read/write BitLocker-encrypted volumes

There is an issue to build with ruby 3.0. I suppose a tag has to be created in git and the package be updated.

Thanks

Fix this library issues:

sudo ln -s /usr/lib/libruby-2.7.so /usr/lib/libruby.so.2.7

Seems to be a Manjaro-specific problem then, I've got no problems on an up-to-date Arch system.

Thanks for that, I can confirm that the fix in korimitsu's comment worked for me as well. Running 5.10.7 kernel via Manjaro.

Error: dislocker-fuse: error while loading shared libraries: libmbedcrypto.so.3: cannot open shared object file: No such file or directory

Fix with: sudo ln -s /usr/lib/libmbedcrypto.so.6 /usr/lib/libmbedcrypto.so.3

This did not compile for me, I had to update the /usr/include/ruby-2.6.0/ path to 2.7.0

haobinnan's fix has already been backported to Aorimn's git repo: https://github.com/Aorimn/dislocker/pull/187

Therefore, there is no need to use some third-party repo. Just install dislocker-git to fix the issue.

This package (dislocker) was created to provide stable releases; unfortunately, the last upstream release package is from 2017. There is already a request for a new release: https://github.com/Aorimn/dislocker/issues/194

here is the updated package build in addition to @Tom-1234 comment:

Maintainer: mrxx <mrxx at cyberhome dot at>

pkgname=dislocker pkgver=20190929 pkgrel=5 pkgdesc="Read/write BitLocker-encrypted volumes" arch=('i686' 'x86_64') url="https://github.com/haobinnan/dislocker" license=('GPL2') depends=('fuse' 'mbedtls' 'ruby') makedepends=('make' 'cmake') conflicts=('dislocker-git') optdepends=('ntfs-3g: NTFS file system support') source=('dislocker::git+https://github.com/haobinnan/dislocker') sha1sums=('SKIP')

build() { cd "$srcdir/$pkgname"

cmake -DCMAKE_INSTALL_PREFIX=/usr \ -Dlibdir=/usr/lib \ -DC_INCLUDE_PATH="$C_INCLUDE_PATH:/usr/include/ruby-2.6.0/" \ -D WARN_FLAGS:STRING="-Wall -Wextra" \ . make }

package() { cd "$srcdir/$pkgname" make DESTDIR="$pkgdir/" install

install -Dm644 README.md ${pkgdir}/usr/share/doc/${pkgname}/README install -Dm644 CHANGELOG.md ${pkgdir}/usr/share/doc/${pkgname}/CHANGELOG install -Dm644 LICENSE.txt ${pkgdir}/usr/share/licenses/${pkgname}/LICENSE }

Hello, there were problems (segmentation fault) after the upgrade to Win10 19.03, see https://github.com/Aorimn/dislocker/issues/185. Thankfully a fixed was prepared by haobinnan and is now available in the develop branch. I made a brief test and at least it works for me. Just as info for those running in the same issue. Kudos to haobinnan and Aorimn.

alu1, I still can't reproduce the problem neither on my production machines nor on fresh test installations, it compiles fine with current ruby-2.6.3 everywhere.

Maybe this problem occurs only on systems with multiple (possibly outdated) versions of ruby installed in parallel. Because of this, I have added the path to the 2.6.0 includedir of ruby. Thank you for your feedback on this issue and kudos to GI_Jack for the fix.

Package doesn't build with current Ruby2.6. Appreciate dependency is listed as legacy Ruby1.8, but that package doesn't build from AUR either. Can confirm GI_Jack's kludge to the PKGBUILD from March fixes inability to find <ruby.h>

Thanks, BoneTone. Dislocker was not able to write to all types of Bitlocker volumes for some time after I created the package. This has changed over time, nowadays the upstream description states it is able to write to most versions of Bitlocker volumes.

As both the package description and upstream url were outdated, I've updated the PKGBUILD to reflect these changes.

Thanks mrxx. One other quick question, the description for this package states that it is to create a read only mount of dislocker encrypted volumes (there is even another package on the AUR for read/write capabilities). However, using this (your) package I am able to write to the encrypted volume once I've decrypted & mounted it. Should the description be updated, or is there a bug? Personally, I am pleased that it is able to write to the volume, and would prefer to keep it that way.

Indeed, the upstream URL is no longer valid. I'll update it when there is a new upstream release.

The source is available at https://github.com/Aorimn/dislocker

Is the upstream URL correct? It seems to be redirecting me to an unrelated page. Was hoping to take a look at the code and see if I can improve some error handling when the user submits the wrong user password for a volume.

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

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

https://pastebin.com/bfEsdqpp

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

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...

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.

This broke for me after ruby updated to 2.6. I got a message about libruby.so.2.5.0 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.

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

madman_xxx, please follow https://wiki.archlinux.org/index.php/Arch_User_Repository#Getting_started "Ensure the base-devel package group is installed"

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.