X-Git-Url: http://git.annexia.org/?p=libguestfs.git;a=blobdiff_plain;f=BUGS;h=00ce125d5158299136758b53d62ce7111227fea5;hp=287586a7a0e439a325e8d7069688298f2431b9a8;hb=080545d0f87cca424420d05a743ab1f42becb72f;hpb=9501ab7792e50e464dc65e9190a0e1d84b5dd423 diff --git a/BUGS b/BUGS index 287586a..00ce125 100644 --- a/BUGS +++ b/BUGS @@ -30,3 +30,45 @@ parent process, or at least that's what I think is happening] [libguestfs] Some occasional data corruption, certainly on tgz-out. Try using tgz-out on a very large directory. [we think this is fixed by 64a6a828bd318622420cf3018899392fd80c14e7] + +[libguestfs] futimens (do_touch) not available in glibc 2.5 +(reported by Charles Duffy) +[fixed] + +[ocaml] Does not compile with OCaml 3.09.3 from RHEL 5 +(reported by Charles Duffy) +[fixed] + +[inspector] If there are missing Perl module deps, it still +configures the inspector. (eg. if perl-Sys-Virt is missing). + +[build] "exec: chroot not found" +Setting PATH to include /usr/sbin solves this temporarily. + +[libguestfs] FileOut parameters can cause +"internal error: reply callback called twice" +This bug is rare but well-understood. Unfortunately it's also +quite hard to fix cleanly. + +[libguestfs] write-file does not support strings containing ASCII NUL. + +[perl] Perl bindings cause a segfault when you call any command which +takes a StringList (eg. $g->command). +[should be fixed now] + +[libguestfs] OptString parameters in the bindings are often not +handled correctly. For example in OCaml (but this is NOT exclusive +to OCaml), OptString should become 'string option'. + +[libguestfs] Certain functions such as 'set-path' can take NULL +parameters, but the parameters are not OptString. + +[tests] command and command-lines tests fail if test-command binary +cannot be statically linked by libtool. The workaround is to install +glibc-static. + +[tests] Should be possible to conditionally skip tests based on a +runtime check. + +[fedora] Depends on 'qemu' but should depend on the real subpackage, +eg. qemu-kvm or qemu-system-x86_64 or whatever. [reported by markmc]