similar to: API/ABI changes tracker for libguestfs

Displaying 20 results from an estimated 300 matches similar to: "API/ABI changes tracker for libguestfs"

2017 Mar 20
12
Announce: OpenSSH 7.5 released
OpenSSH 7.5 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. OpenSSH also includes transitional support for the legacy SSH 1.3 and 1.5 protocols that may be enabled at compile-time. Once again, we would like to thank the OpenSSH community
2015 May 26
6
[PATCH 0/6] Update the way that API versions are generated for the man page.
The existing mechanism was clunky, slow and used ~ 10 MB of local disk. Rich.
2014 Sep 24
2
missing symbol
Hi, when pushing libguestfs 1.27.53 (1:1.27.53-1) through my build setup befor uploading it to Debian, I noticed that "guestfs_internal_lstatlist@Base", a symbol that has been there since 1.20, is now missing. This causes dpkg-gensymbols(1) whose job it is to compare the symbols from the newly-built libraries to the known state to fail. If the guestfs_internal_* functions are not
2017 Mar 20
2
API/ABI changes review for OpenSSH
Hello, Here is the review of API/ABI changes for OpenSSH since 5.4p1 version: https://abi-laboratory.pro/tracker/timeline/openssh/ The report is updated 3 times a week. Hope it will be helpful for users and maintainers of the library. Created with the help of open-source abi-tracker tool: https://github.com/lvc/abi-tracker Thank you.
2020 Feb 24
3
*** buffer overflow detected *** accessing invalid FD in libguestfs
We have extended collectd virt plugin to extract info about disk usage from a libvirt domain using libguestfs. In addition to my previous mail I am attaching some more infomration about the problem. Currently the collectd plugin works fine and retrieves the required statistics. The problem that I face happens after certain number of cycles (getting disk usage statistics). Collectd is terminated
2012 Aug 06
1
[PATCH V2] virt-diff: add new virt-diff tool
add new virt-diff tool Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- Hi Rich, It can work now, please give some comments. ;) Cheers, Wanlong Gao cat/Makefile.am | 20 ++- cat/virt-diff.c | 525 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ po/POTFILES | 1 + 3 files changed, 545 insertions(+), 1 deletion(-) create mode 100644 cat/virt-diff.c diff
2020 Feb 24
3
[PATCH commit] options: Compile blocksize code conditionally.
Since the blocksize option was added since the minimum version of libguestfs for virt-v2v, we need to make it conditional so that virt-v2v can still be compiled with the older libguestfs. This commit does the minimum fix to make it build. It doesn't conditionalize the --blocksize option altogether. However I believe, at least for virt-v2v, that is OK since the --blocksize option is not used
2016 Nov 08
4
[PATCH 1/3] generator: c: move internal functions
Move the generate_all_structs and generate_all_headers functions, previously internal within the implementation of generate_guestfs_h, to be usable by other functions in the same "C" module (but not public). Only code motion. --- generator/c.ml | 163 +++++++++++++++++++++++++++++---------------------------- 1 file changed, 82 insertions(+), 81 deletions(-) diff --git a/generator/c.ml
2017 May 26
4
[Bug 101199] New: nouveau_screen.c: undefined reference to `nouveau_drm_del'
https://bugs.freedesktop.org/show_bug.cgi?id=101199 Bug ID: 101199 Summary: nouveau_screen.c: undefined reference to `nouveau_drm_del' Product: Mesa Version: 17.1 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:
2020 Feb 13
1
[common PATCH v4 0/1] options: add '--blocksize' option for C-based tools
From: Nikolay Ivanets <stenavin@gmail.com> v4 fixes issues found during code review: - whitespace-change-only hunks are removed - options are alphabetically orderred now v3 is just a spelling correction spotted by Eric Blake https://www.redhat.com/archives/libguestfs/2020-February/msg00111.html In v2 I've moved '--blocksize' parameter description into the separate file called
2024 Feb 05
7
Bug#1063270: xen: NMU diff for 64-bit time_t transition
Source: xen Version: 4.17.3+10-g091466ba55-1 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-arm at lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond
2020 Feb 12
1
[common PATCH v3 0/1] options: add '--blocksize' option for C-based tools
From: Nikolay Ivanets <stenavin@gmail.com> v3 is just a spelling correction spotted by Eric Blake In v2 I've moved '--blocksize' parameter description into the separate file called blocksize-option.pod so we can include it everywhere we need similar to key-option.pod. https://www.redhat.com/archives/libguestfs/2020-February/msg00099.html v1 was here:
2015 Oct 05
3
[PATCH 1/2] Change 'fprintf (stdout,...)' -> printf.
Result of earlier copy and paste. --- align/scan.c | 35 ++++++++++--------- cat/cat.c | 39 +++++++++++---------- cat/filesystems.c | 69 +++++++++++++++++++------------------- cat/log.c | 35 ++++++++++--------- cat/ls.c | 61 +++++++++++++++++---------------- df/main.c | 43 ++++++++++++------------ diff/diff.c | 67
2020 Feb 12
3
[common PATCH v2 0/1] options: add '--blocksize' option for C-based tools
From: Nikolay Ivanets <stenavin@gmail.com> In v2 I've moved '--blocksize' parameter description into the separate file called blocksize-option.pod so we can include it everywhere we need similar to key-option.pod. v1 was here: https://www.redhat.com/archives/libguestfs/2020-February/msg00096.html Nikolay Ivanets (1): options: add '--blocksize' option for C-based
2015 Oct 21
2
"could not parse ovf:Name" converting OVA
I got the "IE10 on Win 8" VM download from here: https://dev.modern.ie/tools/vms/linux/ and am trying to convert the .ova file to a format that will work with virt-manager and KVM on Fedora 21. I tried this: $ virt-v2v -v -x -i ova -o libvirt IE10\ -\ Win8.ova and got this output: virt-v2v: libguestfs 1.28.12 (x86_64) [ 0.0] Opening the source -i ova IE10 - Win8.ova tar -xf
2012 Jan 09
3
[PATCH 1/3] launch: move the filename checking to a wrapper
Move the filename's comma character checking to a wrapper. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- src/launch.c | 18 ++++++++++++------ 1 files changed, 12 insertions(+), 6 deletions(-) diff --git a/src/launch.c b/src/launch.c index ca89b63..8eaaac8 100644 --- a/src/launch.c +++ b/src/launch.c @@ -277,6 +277,16 @@ valid_format_iface (const char *str) return
2017 Apr 28
2
[PATCH] common/options: Change drv struct to store drive index instead of device name.
The device name is only used by guestfish (when using the -N option to prepare drives). We constructed the device name very naively, basically ‘sprintf ("/dev/sd%c", next_drive)’. This stores the device index instead, and only constructs the device name in guestfish. Also the device name is constructed properly using guestfs_int_drive_name so it can cope with #drives > 26. ---
2005 Jul 13
2
CLI BT tracker/tracker
I have been hunting around the inet trying to find a CLI BT tracker/hoster. I want to use one of my linux servers as a BT torrent hoster/tracker. Anyone have any good informaiton they can point me to? -- My "Foundation" verse: Isa 54:17 No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. This is the
2006 Jul 19
0
Please Use The Bug Tracker
Hi Everyone, Just a friendly reminder that if you hit something you think is a bug, please use the bug tracker for it. http://rubyforge.org/tracker/index.php?group_id=1306&atid=5145 I have a hard time wading through the Forums, mailing list, and my personal e-mail box pulling out the bugs I need to fix. I just finished doing it for this last round and there was about 7 bugs and 5 feature
2007 May 12
1
Custom form fields in tracker?
Hello, I was just reading the following bug ticket: http://rubyforge.org/tracker/?func=detail&atid=3149&aid=10744&group_id=797 I notice that you devs have to repeat yourselves quite a bit about requiring the different types of data that are required to diagnose bugs. Could you modify the RubyForge tracker to accommodate this information? You could even make them all required