similar to: [PATCH] p2v: Calculate offset of the Real Time Clock from UTC.

In an effort to reduce the code, start to use few bits of GLib: - replace the gnulib c-type module - replace the gnulib getprogname module - use g_spawn_sync to launch curl, and drop a file reading function Pino Toscano (6): Include glib.h in p2v.h Use g_ascii_isspace instead of c_isspace from gnulib Use g_get_prgname instead of getprogname from gnulib build: remove no more used gnulib

Calculate the offset of the physical host's Real Time Clock (RTC) from UTC and pass this to virt-v2v through the libvirt XML description of the physical machine. The libvirt XML is modified to add one of the following: (no <clock/> element) - if the RTC could not be read or there was some other time calculation error. <clock offset='utc' /> - if the RTC is the

These are a prelude to fixing https://bugzilla.redhat.com/show_bug.cgi?id=1590220 A lot of the virt-p2v configuration code was duplicated manually. These changes make sure that most of it is generated. Rich.

Now that virt-p2v has its own repository [1] and releases [2], it is time to remove it from libguestfs. [1] https://github.com/libguestfs/virt-p2v [2] http://download.libguestfs.org/virt-p2v/ Pino Toscano (2): Remove virt-p2v Remove remaining virt-p2v bits .gitignore | 4 - Makefile.am | 7 +- bash/Makefile.am

Hi, this series update libguestfs to a recent gnulib version, so that we can use its new getprogname module, and solve altogether one of the porting issues (the need for 'program_name' by the error module of gnulib), and have a single way to get the name of the current program. A number of changes in tools mostly, although mechanical. Thanks, Pino Toscano (3): Update gnulib to latest

ncurses didn't have pkg-config files in not-that-old versions. If those couldn't be found, then try the ncurses6-config tool. --- m4/guestfs_libraries.m4 | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/m4/guestfs_libraries.m4 b/m4/guestfs_libraries.m4 index c5a4a01..e751db1 100644 --- a/m4/guestfs_libraries.m4 +++ b/m4/guestfs_libraries.m4 @@ -113,7 +113,14 @@

Hey there! Here are a few patches to fix unrelated things: one fixes the configure for older ncurses releases having no pkg-config files. The other two are fixing what Richard mentioned about guestfs subvolumes display Cédric Bosdonnat (3): configure: handle older version of ncurses api: add mountable_device and mountable_subvolume fish: fix btrfs subvolumes display in error case

Hi all, Here is version 2 of the patch series, including the changes for Pino's remarks. Cédric Bosdonnat (3): configure: handle older version of ncurses api: add mountable_device and mountable_subvolume fish: fix btrfs subvolumes display in error case fish/options.c | 28 ++++++++++++++++++++++++++- generator/actions.ml | 26 +++++++++++++++++++++++++

v1 -> v2: - No functional changes to the patch, just fixes a few bugs. Rich.

Hi there, Latest and greatest version including all new remarks from both Pino and Rich. Cédric Bosdonnat (3): configure: handle older version of ncurses api: add mountable_device and mountable_subvolume fish: fix btrfs subvolumes display in error case fish/options.c | 28 ++++++++++++++++++++++++++- generator/actions.ml | 26 +++++++++++++++++++++++++ m4/guestfs_libraries.m4

As preliminary steps in splitting virt-p2v to an own repository, start making p2v more independent within libguestfs. This is accomplished by the following changes: - generate the p2v kernel config sources & docs at build time using a Perl script, rather than the generator (so no need for OCaml when building from git, and no generated sources in dist tarballs) - create two local test

v2 -> v3: - Drop gnulib fallback.

I am trying to build from source but am getting errors -bash-4.3$ grep -n AM_GNU_GET /tmp/t 2595:m4/guestfs_libraries.m4:145: warning: macro 'AM_GNU_GETTEXT' not found in library 2598:m4/guestfs_libraries.m4:145: warning: macro 'AM_GNU_GETTEXT' not found in library 2600:configure:57872: error: possibly undefined macro: AM_GNU_GETTEXT 3834:./configure: line 57872:

v1 -> v2: - Removed the f_type field from StatVFS.statvfs structure. - New function StatVFS.filesystem_is_remote, written in C. [Thinking about it, this should probably be called ?is_network_filesystem?, but I can change that before pushing]. - Use statvfs instead of fstatvfs, and statfs instead of fstatfs. - Rejigged the comments in builder/builder.ml to make them simpler

https://www.visualstudio.com/en-us/news/vs2015-vs.aspx Is it time? 2016-03-31 12:03 GMT-07:00 Aaron Ballman via llvm-dev < llvm-dev at lists.llvm.org>: > On Thu, Mar 31, 2016 at 2:57 PM, Zachary Turner <zturner at google.com> > wrote: > > > > > > On Tue, Mar 29, 2016 at 10:42 AM Aaron Ballman <aaron at aaronballman.com> > > wrote: > >>

On Tue, Mar 29, 2016 at 10:42 AM Aaron Ballman <aaron at aaronballman.com> wrote: > > Not everyone can upgrade to the latest version of the toolchain, even > if it has been released for a while. We did drop MSVC 2012 support > early, but MSVC 2015 was in RC or RTM stages by that point, and we had > some pretty big incentive to upgrade early (without function templates >

There are certainly enough people making commits that work with VS2015 but not VS2013 that the "would it be useful" question is pretty well answered. I've already brought up the idea on my team, as it's obviously coming and we need time to coordinate with internal consumers of the toolchain. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Zachary

FWIW, no objections from me, after all I proposed this 3 months ago :) Probably Aaron Ballman should comment though since the primary objection last time was his. On Fri, Jul 29, 2016 at 2:00 PM Sean Silva <chisophugis at gmail.com> wrote: > On Fri, Jul 29, 2016 at 1:23 PM, Robinson, Paul via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> There are certainly

Probably not. It's very confusing because they are transitioning to a new versioning scheme. The current version if Visual Studio 2015. The next version is Visual Studio 15. The link you posted was for the RTM of 2015, just over a year ago. But 15 is still in Preview. When 15 goes to RTM, then we can revisit the question of making 2015 the minimum required version. On Fri, Jul 29, 2016

> -----Original Message----- > From: aaron.ballman at gmail.com [mailto:aaron.ballman at gmail.com] On Behalf > Of Aaron Ballman > Sent: Friday, July 29, 2016 2:19 PM > To: Zachary Turner > Cc: Sean Silva; Robinson, Paul; Piotr Padlewski; llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] Upgrading to MSVC 2015 > > There are not that many people making commits to