similar to: [v2v PATCH] libosinfo: remove auto-cleanup for OsinfoList

This patch series integrates libosinfo in virt-v2v to get the list of files for Windows from libosinfo, if possible. The actual data is still from virtio-win, just unpacked. Changes from v1: - adapt to use the priority in libosinfo 1.7.0+ - filter out non-pre-installable drivers - collect all the drivers matching the requirements, not just the first, sorting them by priority like libosinfo does

This patch series integrates libosinfo in virt-v2v to get the list of files for Windows from libosinfo, if possible. The actual data is still from virtio-win, just unpacked. Pino Toscano (3): build: require libosinfo v2v: add a minimal libosinfo interface v2v: try to get windows driver files from libosinfo m4/guestfs-v2v.m4 | 3 + v2v/Makefile.am | 9 +-

libosinfo changed the way OsinfoList is declared in 1.7.0, however that was changed back to the old way in 1.8.0; the change was an ABI break, and made OsinfoList a Module class. Starting from 2.63.3, Module classes have already auto-cleanup functions declared for them, leading to double declarations in certain setups. Hence, do some version check dance to declare the OsinfoList only when using

libosinfo 1.8.0 declares them automatically for all of its classes, so there is no need to declare ours. This requires fixing the definition of the IS_LIBOSINFO_VERSION macro to wrap its body in brackets. While in the process, simplify the workaround for a related bug by removing a now-useless check. --- v2v/libosinfo-c.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff

Starting from glib 2.63.3, Module classes have already auto-cleanup functions declared for them. Reported by: Kevin Locke. --- v2v/libosinfo-c.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/v2v/libosinfo-c.c b/v2v/libosinfo-c.c index 1ab6bb4d..e6827f76 100644 --- a/v2v/libosinfo-c.c +++ b/v2v/libosinfo-c.c @@ -44,7 +44,9 @@ G_DEFINE_AUTOPTR_CLEANUP_FUNC(OsinfoFilter, g_object_unref)

Hi All, I'm attempting to compile virt-v2v 1.42.0 on Debian testing. With gcc 9.3.0, libosinfo 1.7.1, and glib 2.64.2, `./configure && make` fails on libosinfo-c.c with the following error message: -8<-------------------------------------------------------------------- In file included from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9, from

Hello, Can you please tell me what the overload point is for OPUS in dBm0 or dBV? As an example, the G.711 A law codec has an overload point of +3.14 dBm0 across a 600 ohm circuit. In ITU-T G.100.1 section 5.8 you can read more about the relationship between dBm0 and dBov. In that same section you can see that the G.711 A law, u law, and G.722 codec overload points are also defined.

On Monday, 1 June 2020 04:17:00 CEST Kevin Locke wrote: > Hi All, > > I'm attempting to compile virt-v2v 1.42.0 on Debian testing. With gcc > 9.3.0, libosinfo 1.7.1, and glib 2.64.2, `./configure && make` fails > on libosinfo-c.c with the following error message: > > -8<-------------------------------------------------------------------- > In file included

Hi, yes there is a way. Have a close look at the samba VFS modules. Vfs objects = recycle Recycle: repository = .recyclebin_or_whatever_you_want Recycle: keeptree = yes With this, everything you delete is going to a directory .recyclebin_or_whatever_you_want in the share. Ok, it is not the original recycler of windows, but much better than throwing the files away. Michael

Can anyone recommend a good high-end sound card to use on a streaming server? Basically all I need are two channels, a good 96 kHz sampling chip, and it needs to run on Linux. -- Jeff Simmons jsimmons@goblin.punk.net Simmons Consulting - Network Engineering, Administration, Security "You guys, I don't hear any noise. Are you sure you're

Hi Marc, It's not exactly clear how to define the an "overload point" for Opus. In normal use, it's not a good idea to go beyond the +/- 32767 values for 16-bit PCM or +/- 1.0 for float. That being said, internally Opus can represent signals that are up to about 48 dB louder than the PCM saturation point and if you use the float implementation you can actually encode and decode

On Fri, Mar 3, 2023 at 4:01?PM Eugenio Perez Martin <eperezma at redhat.com> wrote: > > On Fri, Mar 3, 2023 at 4:32 AM Jason Wang <jasowang at redhat.com> wrote: > > > > > > ? 2023/3/1 15:01, Eugenio Perez Martin ??: > > > On Mon, Feb 27, 2023 at 8:04 AM Jason Wang <jasowang at redhat.com> wrote: > > >> > > >> ? 2023/2/24

-----BEGIN PGP SIGNED MESSAGE----- Hi, a security hole has been found in the auxiliary fax scripts "faxq" and "faxrunq" in the mgetty+sendfax package. It has been in there since the first day those scripts were written. Due to improper quoting in these shell scripts, it''s possible to execute code with a foreign user id, and get root access to the machine. The

Hi, This is an initial implementation of a vhost-user backend for the VirtIO RPMB device. The device is currently in the draft of the next VirtIO specification and describes block device which uses combination of a key, nonce, hashing and a persistent write counter to prevent replay attacks (hence Replay Protected Memory Block). It is implemented as a vhost-user device because we want to