similar to: libguestfs 1.2.x (stable series) and 1.3.x (development series) created

I've uploaded Xapian 1.2.0 (including Search::Xapian 1.2.0.0). This is the first release in a new stable release series! 1.0.x will continue to be updated with bug-fixes for a while, but we will be moving focus away from it and once any issues with 1.2.x have been sorted out, we'll only fix critical bugs in 1.0.x. Please don't confuse 1.2.0 with 1.0.20 announced a few days ago.

Hi After having updated some GEMS I get `load_missing_constant'': uninitialized constant ActiveSupport::Cache (NameError) on starting the server of a freshly generated rails project. Before, I already had Rails 2.3.2 projects succesfully running, now all of them generate this error. These are my GEMS: actionmailer (2.3.2, 2.2.2, 2.1.2, 2.1.1, 2.1.0) actionpack (2.3.2, 2.2.2, 2.1.2,

Hello, I'm on a Mac and I'm noticing that encoding via the flac command line is significantly slower with version 1.3.0 than 1.2.1. I'm encoding a 24/96 file to flac, both from wav and aiff and both formats are showing the same speed decrease when using 1.3.0. To give an idea of the speed decrease, encoding at flac level 8: 24/96 wav file 1.21: 61.05 seconds. ratio=0.690 1.3: 222.48

Hello, I'm on a Mac and I'm noticing that encoding via the flac command line is significantly slower with version 1.3.0 than 1.2.1. I'm encoding a 24/96 file to flac, both from wav and aiff and both formats are showing the same speed decrease when using 1.3.0. Also, 1.2.1 will not encode an aiff-c file, but 1.3.0 will. Is this change documented anywhere? Thanks, Scott --------------

Are you sure they didn't change the default encoding level ? I would include some example timings to give a better idea of what "significantly slower" is Wonder if you see same for 44/16 files? > On Jul 25, 2014, at 2:29 AM, Martijn van Beurden <mvanb1 at gmail.com> wrote: > > Hi, > > You might want to report this to the flac-dev mailinglist instead of the

Le mar 18/05/10 12:10, emmanuel at engelhart.org a ?crit: > Le mar 18/05/10 11:49, "Charlie Hull" charlie at j > uggler.net a ?crit:> On 14/05/2010 18:29, Emmanuel Engelhart > wrote:> > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > Le 14/05/2010 13:31, Charlie Hull a > ?crit> : > >> On 29/04/2010 08:22, Olly

First off, if I do this correctly it shouldn't affect anything or anyone's workflow. Here's hoping anyway :-) Problem ------- We've got a lot of changes going into nbdkit. I think we've had 53 commits since the previous release (1.1.28). There's: (a) a danger we might break something without noticing and push that brokenness into a released tarball, and (b) we

http://www.winehq.org/announce/1.2 I also submitted it to Slashdot, please click up: http://slashdot.org/submission/1284766/Wine-12-released - d. ---------- Forwarded message ---------- From: Alexandre Julliard <julliard at winehq.org> Date: 16 July 2010 19:22 Subject: Post-release plans To: wine-devel at winehq.org Folks, First I want to thank everybody for your great work of the

At the moment I post new versions when I feel there has been a significant amount of work and/or time passed since the previous release. This however does not give a good indication of the quality of the release, for example if it includes mainly bugfixes and stability improvements, or bleeding edge features. Therefore I would like to propose a change to the way that libguestfs versions are

Op 03-12-14 om 15:49 schreef Olivier Tristan: > [...] > If you want to check this on a single piano note, I would be > happy to know if this improves the monophonic use case as well. This sample is indeed a case where the retuning of FLAC 1.3.1 shows a severe regression. It seems the patch does work quite well in this case, but it does not fully fix the regression. FLAC 1.3.0 -5:

Please cc: the results from dev list back here though I would run some tests on a diff platform but don't have access to my PC for a few weeks Would also be interesting to see what decoding stats you get > On Jul 25, 2014, at 7:38 AM, Scott Brown <scottcbrown at gmail.com> wrote: > > I will post to the dev list, sorry about that. > > To give an idea, though, at flac

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's a bit after 11pm, on the 11th day of the 11th month of the year, so what better time for a new release of X11! Release Candidate 1 of X11R7.6 has been posted at: http://www.x.org/releases/X11R7.6-RC1/ This includes all the source tar files for the versions of the modules currently considered part of the core release set (aka the

I've heard from several users who report no difficulties using the Rwinst.exe installer for the released version of 1.2.0. I've blown away all traces of 1.2.0 on my system and have re-downloaded all 10 zip files and the installer on both my NT and Win2K boxes. The memory-overwrite error persists on both systems, suggesting that there is some incompatibility between the 1.2.0

Hi all, Sorry for bringing this up this short before the release, but I noticed something rather strange. I was doing some more exotic checks on the last pre-release when I tried test_streams.sh with FLAC 1.3.0 encoding and an older version (1.1.0 or something like that) decoding. This failed for 24-bit samples and I wondered why. After quite some tests and hex-editors, I found out this is

On 2014-11-23 3:01 AM, Janne Hyv?rinen wrote: > At least Windows users expect to find official version at > https://xiph.org/flac/download.html. Right now it links to old > sourceforge page http://sourceforge.net/projects/flac/files/flac-win/ > that only has version 1.2.1. Is this just a static build of the 'flac' command-line tool? I can do that for 1.3.0 and 1.3.1, or

Like most people, I''ve got two machines: one for development and one for production. I''ve done everything I can to make sure the ruby/rails environments are the same, but of course they''re not identical (I''ll get into that in a moment). The error that I''m getting happens when I call a method in a background task controller on the production machine; I

I received two mails about faile to apply patches to 3.16-stable tree: FAILED: patch "[PATCH] virtio-rng: skip reading when we start to remove the device" failed to apply to 3.16-stable tree FAILED: patch "[PATCH] virtio-rng: fix stuck of hot-unplugging busy device" failed to apply to 3.16-stable tree Amit already backported two patches for 3.16-stable, then cherry-pick of my

I received two mails about faile to apply patches to 3.16-stable tree: FAILED: patch "[PATCH] virtio-rng: skip reading when we start to remove the device" failed to apply to 3.16-stable tree FAILED: patch "[PATCH] virtio-rng: fix stuck of hot-unplugging busy device" failed to apply to 3.16-stable tree Amit already backported two patches for 3.16-stable, then cherry-pick of my

lvqcl wrote: > I have a couple of questions: > > 1) Do you plan to release 1.3.1 pre1, pre2 etc or just 1.3.1 w/o any pre-releases? I had not planned to do a pre-release. > 2) Do you plan to release any official binaries (flac, metaflac, maybe something else)? Nor had I planned to release binaries. The source code tarball ends up here: https://svn.xiph.org/releases/flac/ I

As you might have seen for the past 3 days I've been tackling a nasty data corruption bug[1][2]. The bug occurs when ALL of the following conditions are true: (a) You are using a qcow2 image file. (b) You are writing out data to the image file using libguestfs or a libguestfs-using tool like guestfish or virt-resize. (c) The data is not being written to a filesystem (to files or