…er man page.
…HBZ#1088262). When you call guestfs_disk_create on a block device with format=raw then it will try to discard the blocks on the device.
qemu-system-arm now requires that you pass '-machine virt' (or some -machine type) explicitly. Change the configure test so it works on upstream ARM.
Add the possibility to configure the proxy in each repository .conf file, specifying whether use no proxy at all, follow the system configuration or use a specific proxy.
List manually and remove the content left (hidden files/directories) in temporary directories after the glob listing & removal.
Previous commit 97c57a8 added a potential bug in the sparsify build. If virt-sparsify had used a *.mli file then it would have tried to run a command like: ocamlc mlguestfs.cmxa -c foo.mli -o foo.cmi This would fail because ocamlc doesn't know about native code libraries (*.cmxa). In fact virt-sparsify was not affected by this because it doesn't use any *.mli files. Fix this by adjusting the automake variables.
This way they are affected less by the environment.
…#1079182). If a disk has type 0x42 partition (which would indicate LDM), but LDM is not available then try parsing the partition anyway. It might be parseable as plain old NTFS.
There are two observations which make this possible: (1) virt-sparsify contains at least one C unit, so automake thinks it is compiling a C program. (2) Automake lets us add a *_LINK rule to override linking. We list the C sources of virt-sparsify as virt_sparsify_SOURCES, so automake thinks it is building a C program as normal. We override virt_sparsify_LINK to make it actually link an OCaml program. We add virt_sparsify_DEPENDENCIES listing the OCaml objects so that they get built before linking. We need a small linker script (link.sh) which adds some options at the end of the linker command line which are impossible to add using pure automake. Inspired by the same idea in supermin: https://github.com/libguestfs/supermin/blob/master/src/Makefile.am
This reverts commit 5a2e320.
As long as over ~300MB is recovered, declare sparsification to be successful in this test. It looks as if the journal or other metadata takes up a variable amount of space after sparsification.
Output was: yes Now the output is: checking if we should run the GNUlib tests... yes
Add the chmod customize command to change the permissions of files.
Libguestfs >= 1.26 makes this easy.
This is List.mapi from the stdlib. RHEL 6 did not have this function.
We must avoid touching appliance/supermin.d unless it is necessary, so that we avoid unnecessary rebuilds of the full appliance. Unfortunately since we created temporary files there, even if we didn't decide to keep those temporary files they would still end up touching supermin.d. To stop this, move the temporary files out.
Exclude the arch-independent pkg-config files (no pkg-config available in the appliance). Exclude also the doc-base and reportbug files, typically found in Debian systems.
No functional change.
The file contained no replacement patterns so generating it with configure did nothing.
Add a new lexer token, unused in the grammar, for the unknown lines in index files; this should allow to better handle such kind of parsing errors, removing the need to exit() directly (and leave things in an unclean state).