similar to: Switching all tests to bash

Op 25-11-14 om 23:39 schreef Jan Stary: > Is there a reason the test scripts are calling bash? The change from sh to bash was made a little more than a year ago. The mailing list thread accompanying this change can be found here: http://lists.xiph.org/pipermail/flac-dev/2013-September/004374.html

On Nov 25 23:56:05, mvanb1 at gmail.com wrote: > Op 25-11-14 om 23:39 schreef Jan Stary: > > Is there a reason the test scripts are calling bash? > > The change from sh to bash was made a little more than a year > ago. The mailing list thread accompanying this change can be > found here: > http://lists.xiph.org/pipermail/flac-dev/2013-September/004374.html How

On Nov 26 01:25:25, hans at stare.cz wrote: > On Nov 25 23:56:05, mvanb1 at gmail.com wrote: > > Op 25-11-14 om 23:39 schreef Jan Stary: > > > Is there a reason the test scripts are calling bash? > > > > The change from sh to bash was made a little more than a year > > ago. The mailing list thread accompanying this change can be > > found here: >

I uploaded the source tarball and binary releases for win32 and redhat 7. Solaris package should be ready tomorrow. See the news item for all the improvements from 1.0.3: http://flac.sourceforge.net/news.html#20020924 Developers, see the new Doxygen-based API docs: http://flac.sourceforge.net/api/index.html Thanks again to all the contributors and testers. Josh

Christian Weisgerber <naddy@mips.inka.de> wrote: > #0 0x0000000040d18810 in FLAC__lpc_compute_residual_from_qlp_coefficients_wide > (data=0x49e4c014, data_len=110, qlp_coeff=0x7f7ffffece70, order=1, > lp_quantization=14, residual=0x4fced000) at lpc.c:745 > 745 residual[i] = > data[i] - (FLAC__int32)((qlp_coeff[0] *

Running the basic (--disable-thorough-tests) test suite, I get these failures round-trip test (rt-1-24-111.raw) encode... Segmentation fault (core dumped) ERROR FAIL: ./test_flac.sh fsd24-01 (--channels=1 --bps=24 -0 -l 16 --lax -m -e -p): encode...ERROR during encode of fsd24-01 FAIL: ./test_streams.sh on alpha and amd64. By contrast, i386 is fine. (All OpenBSD/4.2.) Could be a generic LP64

Christian Weisgerber <naddy@mips.inka.de> wrote: > | # nasm build rule: > | %.lo: %.s Even with gmake, this really works only by accident. Automake generates a competing suffix rule, and gmake apparently gives the rule above a higher priority than the suffix rule (or that just happens to be the evaluation order). Matt, since you seem to understand automake, can you come up with

Matt Zimmerman <mdz@debian.org> wrote: > Aha. In FLAC__fixed_restore_signal, the index variable 'i' is declared > unsigned, then used like so: [...] With the following trivial patch applied, > everything works on Alpha, at least with my test sample. Against 0.9 or CVS? While this clearly fixes a bug, 0.9 still dies for me. #0 0x1600692a8 in

The source release for 1.0.1 is finally up on sourceforge. If you are compiling for x86 make sure to read the note in in the README about automake 1.5. Josh __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com

Currently, if IPv6-enabled rsync is run as --daemon, it will perform a wildcard bind(2) on an AF_INET6 socket and expect that IPv4 traffic will be forwarded to the v6 socket (IPv4 mapped address, RFC2553). This has never worked on OpenBSD which disallows IPv4 mapped addresses for security reasons. On FreeBSD 5.0-CURRENT, where the behavior is subject to configuration, the default was switched to

That sounds like the application param is still used as part of the process though? Would allowing the user to specify the application work in the Solokey case? What is stored in the private keyfile? The documentation says no private key is stored there. So is it just information used to reseed the public/private key? Thanks, Kevin ________________________________________ From: openssh-unix-dev

Hi, So I finally have time to test the u2f support but so far I haven't been very successful, Specifically, current HEAD has SSH_SK_VERSION_MAJOR 0x00040000 and I can't seem to find a matching libfido2 version, current HEAD of Yubico/libfido2 is 0x00020000 Is there a more up to date libfido2 or a particular commit of openssh-portable I should be using? thanks Sean

Hi, I've just found this issue - brackets are eaten by Autoconf. Quadrigraphs [1] may be used instead. This way configure produces correct error. Filipp [1] https://www.gnu.org/software/autoconf/manual/autoconf-2.66/html_node/Quadrigraphs.html diff --git a/configure.ac b/configure.ac index 7379ab35..dcf52230 100644 --- a/configure.ac +++ b/configure.ac @@ -2616,7 +2616,7 @@ if test

I have checked in all the latest into CVS and am going to start the test suite again. if all goes well I will probably release this as beta 10. this one should have all the configure stuff working with the new assembly infrastructure. I have tried to make it as easy as possible to port routines to assembly. all that's really needed now is to write the corresponding routine for a specific

There are problems in the configure option handling code for http streaming that was added to the XMMS plugin for 1.1.2. In configure.c, flac_cfg.stream.proxy_host and other pointers to strings are initialized with pointers to an empty string "". Subsequent code in FLAC_XMMS__init() and flac_configurewin_ok() passes these pointers to g_free(). Since they don't point to memory that

This affects the XMMS plugin. configure.in has this test: AC_CHECK_TYPES(socklen_t, [], []) And src/plugin_xmms/http.c is the only consumer: #ifndef HAVE_SOCKLEN_T typedef unsigned int socklen_t; #endif Together this looks bogus to me. The configure check looks for socklen_t in the default headers. If it isn't found there, socklen_t will be typedef'ed. However, at least on

I'm currently trying to figure out why RC3 oggenc with iconv support will - work, but enter replacement characters into tags instead of converting to UTF-8; - dump core; or - catch an assert(); depending on the locale settings. (On FreeBSD, with Chuguev iconv.) I think I'm getting a handle on the assert(). It's this one: assertion "(!k && !ibl) || (k == (size_t)(-1)

libogg 1.1's included regression tests ("make check") fail at least on alpha: ---------------> ./test_bitwise Small preclipped packing (LSb): ok. Null bit call (LSb): ok. Large preclipped packing (LSb): ok. 32 bit preclipped packing (LSb): ok. Small unclipped packing (LSb): ok. Large unclipped packing (LSb): ok. Single bit unclipped packing (LSb): ok. Testing read past end

I bumped the version number of vorbis-tools and am preparing it for an eventual release in a few days. A changelog of what's new may be found at [1]. Meanwhile, what's in SVN is a "Release Candidate" to find out if anything was broken since version 1.1.1. Report any (or lack of) problems you may find, so we'll be able to put out a new version of vorbis-tools. -Ivo [1]

With the upcoming deprecation of ssh-rsa I was trying to see what keys my version of OpenSSH ( 7.8p1 ) supports. I noticed that "ssh -Q key" does not actually list the suggested algorithms to transition to ( rsa-sha2-256 and rsa-sha2-512 ) even though they are supported. Looking through the code, it looks like an issue with the arguments passed to sshkey_alg_list in ssh.c where it should