similar to: Yet Another Call for Installer Bugs...

Lots of progress has been made in fixing installer bugs lately, but there are probably many such bugs hiding in plain view still. It would be very helpful if people could look for bugs which: a) happen while running installers (preferably MSI based installers, but don't worry if you don't know what that means) b) occur in freely downloadable executables (e.g. trial versions) and c)

Hi Valery, On Tue, 2007-04-10 at 13:15 +0200, Valery Khamenya wrote: > Hi, > > where could one find any LLVM development roadmap for this > and perhaps next year? About the best "roadmap" we have is the list of enhancements in Bugzilla:

Howdy Wine users! Looking for an easy way to help Wine? There are plenty of bug reports that could use a retest in current Wine, but developers are busy fixing bugs :-). Here's a list of bugs (536) that have a download available, but haven't been checked on in the last 6 months. If you'd got time and bandwidth to kill, and want to help Wine, please test them. After testing, leave a

MJ, I put some extra info on this for the list. This is a new Debian Jessie install with sernet samba packages. The Keytab file is not created with sernet 4.6.1 packages but it is with the sernet 4.5.7 samba packages. Bug list show some keytab reported but i dont see any related to this.

I'd be interested in the existence of a high-quality, open-source, portable linker for apple platforms, but not enough to help make that happen. If I _was_ gonna work on something related to that, I'd probably be inclined to instead add any required features to allow an ELF linker to target a notional darwin-elf target, and to have clang emit darwin-elf object files, and then write a

Hello all, I'm trying to better understand the state of Mach-O support in lld. The lld docs state that "the linker supports ELF (Unix), PE/COFF (Windows), Mach-O (macOS) and WebAssembly in descending order of completeness." [1] True to that statement, I found an email on this list from Jan 2018 stating that "MachO support in lld is not really ready for real world usage. It was

I've got some bad news: libvirt remote support is probably not going to make libguestfs 1.20. John Eckersberg is diligently working on this, but I don't want to hold up the release of the next stable libguestfs for this, particularly since it needs dependent changes in libvirt. The last stable branch of libguestfs (1.18) happened in the middle of May. That's 7 months ago, making

Libguestfs 1.34 was released on 2016-08-08, which is about 6 months ago. I'd would like to think about what needs work for the next stable 1.36 release, which might happen at the end of this month. Any new APIs added in the 1.35 cycle will become supported and guaranteed when we release 1.36, so we need to check those. See: git diff v1.34.0 -- generator/actions.ml It looks like there

It has been a ludicrously long time (over 8 months) since the last stable release of libguestfs. So I'd like to plan a new 1.30 release soon. Please follow-up if there are features / blockers / bugs that need to be addressed for 1.30. As usual, bugs which have "1.30" (without quotes) in the Devel Whiteboard field in Bugzilla are nominated as blockers for the release. You can see

It has been 5 months since the last stable release of libguestfs and over that time we've accumulated many exciting new features: http://libguestfs.org/guestfs-release-notes.1.html#release-notes-for-libguestfs-1.22 It's time to plan for the release of libguestfs 1.22. As usual, bugs which have "1.22" (without quotes) in the devel whiteboard field are nominated as blockers for

It has been 5 months since the last stable release of libguestfs and over that time we've accumulated many exciting new features. It's time to plan for the release of libguestfs 1.24. As usual, bugs which have "1.24" (without quotes) in the Devel Whiteboard field in Bugzilla are nominated as blockers for the release. You can see a list of those here, currently empty:

It has been 3 months since the last stable release of libguestfs. I'd like to plan a new 1.26 release towards the middle/end of next month. There are some virt-builder features I'd like to get in before then: - virt-builder needs to be able to use Linux distro published cloud images as a source (without requiring a lot of manual config as now) - virt-builder must be able to

HI, Richard Is there any plan to make daemon to directly run on the hypervisor, not starting a guest? e.g. directly export a guest image to be a block device on the hypervisor? On Tue, Oct 7, 2014 at 8:28 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > It has been an amazing 6½ months since the last stable release of > libguestfs. > > I'd like to plan a new 1.28 release

Libguestfs 1.30 was released on 2015-07-21 and because of my wish to rebase libguestfs in RHEL 7.3, I'd like to release 1.32 in early December. Please follow-up if there are features / blockers / bugs that need to be addressed for 1.32. As usual, bugs which have "1.32" (without quotes) in the Devel Whiteboard field in Bugzilla are nominated as blockers for the release. You can see

Morning, I've installed asterisk on FC4 and had a few problems with zaptel stuff. Having installed it on SuSE I was able to check a few things that were different. When installed with the RPMS, the udev stuff gets put into the normal 50-udev file under /etc/udev. On SuSE, it worked when the necessary zaptel section was in a separate file name 55-zaptel.udev (the name is arbitrary,

too many UNCO bugs are listed for wine < 1.0 . I suggest purging or archiving the really old ones since they must have been fixed or no-one cares for them atm. Either way they're too confusing!

It's been nearly 5 months since we last released a stable version of libguestfs, and so I'm trying to get everything ready for the next stable version. This will be called libguestfs 1.10, and there is already a fantastic array of new features, summarised in part here[1]. Bugs ---- If there are bugs that you think ought to be fixed before 1.10 is released, then you need to (a) file them

Libguestfs 1.32 was released on 2016-01-06, which is over 6 months ago. In fact the previous stable version of libguestfs (1.30) was released on 2015-07-21, almost exactly 12 months ago. Are we heading for a 6 month release cycle? Not officially. Anyway, I would like you to think about what needs work for the next stable 1.34 release. Any new APIs added in the 1.33 cycle will become supported

The GnuCash development team announces GnuCash 5.3, the fourth release in the stable 5.x series. This is a snap release to fix the bug listed below. Between 5.2 and 5.3, the following bugfixes were accomplished: ? Bug 798967 - Cannot Save to Any Path After Upgrading to 5.2 Fix inverted if statement condition for save success flag The following fixes and improvements were not associated with bug

Hi, I meet an amazing issue, when I convert a raw file to the oVirt environment using virt-v2v. All seems to work fine, my VM is composed of 9 disks, the processes finishes without any trouble, the files are well present in the right import volume, but only the first system disk appear un my oVirt Import VM. I've retried twice and had the same issue . Here the results of the conversion : [