search for: inpection

Hello, I got a notification regarding a failure to pass incoming checks automatically after a CRAN submission. The details are given here: https://win-builder.r-project.org/incoming_pretest/diveMove_1.5.0_20200908_191325/ The only visible issue is a NOTE from the macosx build, with the very terse: "No Protocol Specified" My searches suggest this can be ignored, but it would be nice

I''m trying to post comments using Ajax. It seems that I have an infinite loop somewhere, because it hangs on the return from the Ajax call. The comment does get saved to the DB, but I have to refresh the page for it to show. The reason I know it''s some sort of infinite loop, is because I''m showing a "loading.gif" image, and it never goes away. Plus, if

...t; The only visible issue is a NOTE from the macosx build, with the very > terse: > > "No Protocol Specified" > > My searches suggest this can be ignored, but it would be nice to squash > it. Any tips welcome. > For some reason this should hgave undergone manual inpection but got auto rejected. Ideally you would reduce the test timing so that the overall check time is less than 10 min . Best, Uwe Ligges ------------------------------ Message: 22 Date: Wed, 9 Sep 2020 16:48:40 +1000 From: Hugh Parsonage <hugh.parsonage at gmail.com> To: Jeroen Ooms <...

...th the very terse: >> >> "No Protocol Specified" >> >> My searches suggest this can be ignored, but it would be >> nice to squash it. Any tips welcome. >> > For some reason this should hgave undergone manual > inpection but got auto rejected. Ideally you would reduce > the test timing so that the overall check time is less > than 10 min . > Best, Uwe Ligges > ------------------------------ > Message: 22 Date: Wed, 9 Sep 2020 16:48:40 +1000 From: > Hugh Parsonage <...

...etect many different Linux distributions, Windows, BSD, and others. The currently mounted root filesystem is ignored, since when running under libguestfs, that filesystem is part of the libguestfs appliance (this is the main difference compared to programs like facter). Guestfs-inpection is written in C, but most of the C is generated by a rules compiler from a set of inspection rules written in a more compact, declarative, Prolog-inspired language. If you want to write or modify the rules, see "WRITING RULES" below. OPTIONS -? --help Display...

Previously posted: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html Inspection now really succeeds on a small number of simple guests. To test it out: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" Rich.

This is a more working version. Inspection (partially) succeeds on a real guest this time :-) You can test it out on a real guest (in this case, a CentOS disk image located at /tmp/centos-6.img) by doing: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" which will print lots of debugging, and at the end the

For background on this change, see: https://rwmj.wordpress.com/2015/12/06/inspection-now-with-added-prolog/ v2 was previously posted here: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html To test this patch series on a real guest, you can do: $ ./run guestfish -v -x -a /var/tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection