Update Udisks from 2.1.8 to 2.8.4 #1387
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Description][1]: > The libbytesize package is a library facilitates the common operations > with sizes in bytes. Create the bee file with the command below. ``` $ bee init https://github.com/storaged-project/libbytesize/releases/download/1.2/libbytesize-1.2.tar.gz creating libbytesize-1.2-0.bee from template '/etc/default/bee/templates/fallback' ``` [1]: http://www.linuxfromscratch.org/blfs/view/svn/general/libbytesize.html
[Description][1]: > libblockdev is a C library supporting GObject introspection for > manipulation of block devices. It has a plugin-based architecture > where each technology (like LVM, Btrfs, MD RAID, Swap,...) is > implemented in a separate plugin, possibly with multiple > implementations (e.g. using LVM CLI or the new LVM DBus API). ``` $ bee init https://github.com/storaged-project/libblockdev/releases/download/2.16-1/libblockdev-2.16.tar.gz creating libblockdev-2.16-0.bee from template '/etc/default/bee/templates/fallback' ``` [1]: http://www.linuxfromscratch.org/blfs/view/svn/general/libblockdev.html
Needed by libbytesize.
*** Libbytesize encountered the following issues during configuration:
No package 'libpcre2-8' found
The Linux From Scratch book uses it, so it’ll be easier to compare options.
This is required by udisks2.
Fix the error below (thanks to our package wrappers):
/dev/shm/bee-root/volume/volume_key-0.3.9-0/source/python/volume_key_wrap.c:125:10: fatal error: Python.h: No such file or directory
#include <Python.h>
^~~~~~~~~~
compilation terminated.
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/volume_key.html
> --without-python: This parameter prevents building the Python 2 bindings, if Python-2.7.16 is installed.
The configuration was fixed for volume_key 0.3.12.
Increment revision to 1.
Needed for cryptsetup 2.0.6.
The GPG tests fail, because our GPG installation is outdated.
Making all in gpgsm
make[2]: Entering directory '/dev/shm/bee-root/gpgme/gpgme-1.13.1-0/build/tests/gpgsm'
echo disable-crl-checks > ./gpgsm.conf
echo 32100C27173EF6E9C4E9A25D3D69F86D37A4F939 > ./trustlist.txt
GNUPGHOME=/dev/shm/bee-root/gpgme/gpgme-1.13.1-0/build/tests/gpgsm LC_ALL=C GPG_AGENT_INFO= top_srcdir=/dev/shm/bee-root/gpgme/gpgme-1.13.1-0/source gpgconf --kill all
echo faked-system-time 1008241200 >> ./gpgsm.conf
echo >> ./trustlist.txt
/bin/sh: gpgconf: command not found
make[2]: [Makefile:938: gpg-sample.stamp] Error 127 (ignored)
/bin/mkdir -p ./private-keys-v1.d
cp /dev/shm/bee-root/gpgme/gpgme-1.13.1-0/source/tests/gpgsm/32100C27173EF6E9C4E9A25D3D69F86D37A4F939 private-keys-v1.d/32100C27173EF6E9C4E9A25D3D69F86D37A4F939.key
echo x > ./gpg-sample.stamp
echo "agent-program `which gpg-agent`|--debug-quick-random" >> ./gpgsm.conf
echo "# CN=test cert 1,OU=Aegypten Project,O=g10 Code GmbH,L=Düsseldorf,C=DE" >> ./trustlist.txt
GNUPGHOME=/dev/shm/bee-root/gpgme/gpgme-1.13.1-0/build/tests/gpgsm LC_ALL=C GPG_AGENT_INFO= top_srcdir=/dev/shm/bee-root/gpgme/gpgme-1.13.1-0/source gpgsm --import /dev/shm/bee-root/gpgme/gpgme-1.13.1-0/source/tests/gpgsm/cert_g10code_test1.der
echo "3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E S" >> ./trustlist.txt
which: no gpg-agent in (/bin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/package/bin:/usr/local/bin:/home/pmenzel/bin:/home/pmenzel/.cargo/bin)
/bin/sh: gpgsm: command not found
make[2]: *** [Makefile:929: pubring-stamp] Error 127
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/dev/shm/bee-root/gpgme/gpgme-1.13.1-0/build/tests/gpgsm'
make[1]: *** [Makefile:720: all-recursive] Error 1
make[1]: Leaving directory '/dev/shm/bee-root/gpgme/gpgme-1.13.1-0/build/tests'
make: *** [Makefile:534: all-recursive] Error 1
Command exited with non-zero status 2
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/gpgme.html
> --disable-gpg-test: if this parameter is not passed to configure, the test programs are built during make stage, which requires GnuPG-2.2.17. This parameter is not needed if GnuPG-2.2.17 is installed.
It’s technically not necessary, as the files are linked against
`/usr/lib/libgpgme.so.11` and that stays the same.
lrwxrwxrwx 1 root root 18 May 10 2011 /usr/lib/libgpgme.so.11 -> libgpgme.so.11.7.0
lrwxrwxrwx 1 root root 19 Sep 28 11:04 /usr/lib/libgpgme.so.11 -> libgpgme.so.11.22.1
But, do it anyways, as some other small fixes went in.
Increment the revision to 1.
Now, people can use a different prefix.
[Description][1]:
> cryptsetup is used to set up transparent encryption of block devices
> using the kernel crypto API.
Needed by volume_key 0.3.6.
checking for libcryptsetup... no
configure: error: Package requirements (libcryptsetup) were not met:
No package 'libcryptsetup' found
[1]: http://www.linuxfromscratch.org/blfs/view/9.0/postlfs/cryptsetup.html
Fix the errors below:
*** Libblockdev encountered the following issues during configuration:
No package 'libcryptsetup' found
libvolume_key.h not available
Requested 'devmapper >= 1.02.93' but version of devmapper is 1.02.79
dmraid.h not available
No package 'libndctl' found
*** Libblockdev will not successfully build without these missing dependencies
udisks2 requires this.
[Version 2.7.6 was never built.] Changes: https://github.com/storaged-project/udisks/blob/7246165b8913e01fe547a551c617acbe27d91a24/NEWS#L17
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The versions in the first commits were never actually built due to missing dependencies.
Update with the commands below.
Tested on rabammel.