similar to: build / release engineers' todo

This just seen on vorbis-dev@xiph.org: > The code went 'gold' tonight. Vorbis 1.0 is in CVS and it's time to > hand off to release engineering. > > I've updated the vendor strind in the libvorbis code, but all other > instances of version number need to be updated as well. I know this > is set in a million places, for autoconf, debian, redhat, Mac and Win

Hello folks, So as it turns out (having gotten sucked into virtualization development at Red Hat) I'm now actually pretty well set up to handle some amount of Windows build system maintenance and binary builds for relases. Of course simply having the tools (and not having even tried to use them since.. oh around 1998) doesn't mean I know what I'm doing. I know we have Win32 capable

Chris, re the DLL additions: In a word, *no*. That much Win32 specific code does not belong in a lib that's pure math and totally platform agnostic. It may be appropriate, assuming it's necessary, to add this in the win32 specific SDKs, but it has no business in the core libvorbis. Please move it out to a more appropriate place as soon as you possibly can. Secondly: I'd like to

Yes, the gitlab instance is the correct upstream development repository. We maintain a mirror at github for the convenience of developers there. Cheers, Ralph On Mon, 2020-06-29 at 21:27 +0000, Ellen Johnson wrote: > Hi Ralph and libvorbis developers, > I thought the vorbis gitlab project was the main development site ( > https://gitlab.xiph.org/xiph/vorbis) because that's what

Hi Ralph, Thank you for your reply! For context -- we consider reported CVEs as bugs even if it's in a third-party library we use (such as libvorbis). We first determine if the CVE is something that would impact our customer workflows. In this case because of our use of libvorbis for audio I/O, it does impact our customers so we need to resolve the CVE as soon as possible. In the

Contained in tonight's last commit: Fixed a link-crossing bug in libvorbis (total time was reset to -1 at the link boundary until the next packet with a frame number arrived) Implemented instantaneous bitrate capability in libvorbis; added ov_bitrate_instant() to interface. I know I talked about a different interface to this with the Sonique folks a few months ago... I couldn't remember

Hi there, I maintain the libvorbis, libogg and vorbis-tool package for Fink <http://finkproject.org/ >. Recently I had time to wonder about those again. In particular, since I was informed libsndfile self-tests fails with 1.2.0, but not with a version dubbed 1.2.1rc1 somebody sent me. Also trunk seems to contain security fixes. In https://trac.xiph.org/browser/trunk/vorbis/CHANGES

This is a linux from scratch based on the 2.4.13 kernel. I'm using a GCC 2.95.3, autoconf 2.52, and automake 1.5. Libvorbis compilation fails with a Signal 11 error as shown below. I had the same results with 2.4.12, 2.4.10, and 2.4.9. I've compiled hundreds of other packages without getting this error, and I've even tried changing the memory. This is my configure line, I used

This is a linux from scratch based on the 2.4.13 kernel. I'm using a GCC 2.95.3, autoconf 2.52, and automake 1.5. Libvorbis compilation fails with a Signal 11 error as shown below. I had the same results with 2.4.12, 2.4.10, and 2.4.9. I've compiled hundreds of other packages without getting this error, and I've even tried changing the memory. This is my configure line, I used

Hi Ralph, Again, thanks so much for doing all this! Plus thanks to all the folks who contributed to the new release! Quick clarifying question -- Isn't CVE-2018-10392 (looks like it’s fixed in https://gitlab.xiph.org/xiph/vorbis/-/issues/2335) also included in new version 1.3.7? If so can you please add it to release notes? (I asked the same question in

Two weeks have passed with no bugs filed against the release candidate, so we have officially tagged it as 1.2.2 final. Following is the official release announcement: Xiph.Org is pleased to announce the release of libvorbis-1.2.2. This full release is code-identical to the preceeding 1.2.2-rc1 release candidate. 1.2.2 is primarily a bugfix release to push out many fixes, some of which have

Two weeks have passed with no bugs filed against the release candidate, so we have officially tagged it as 1.2.2 final. Following is the official release announcement: Xiph.Org is pleased to announce the release of libvorbis-1.2.2. This full release is code-identical to the preceeding 1.2.2-rc1 release candidate. 1.2.2 is primarily a bugfix release to push out many fixes, some of which have

Well, this is a bit stronger than a proposal; this is "what I plan to do unless people see obvious flaws I missed"... The text comment header is the second (of three) header packets that begin a Vorbis bitstream. It is meant for short, text comments, not arbitrary metadata; arbitrary metadata will be put in a metadata stream, likely an XML stream type. We've discussed this in

A new libvorbis release is now available. http://downloads.xiph.org/releases/vorbis/libvorbis-1.2.0.tar.bz2 http://downloads.xiph.org/releases/vorbis/libvorbis-1.2.0.tar.gz http://downloads.xiph.org/releases/vorbis/libvorbis-1.2.0.zip This release fixes some robustness issues with corrupt streams, including a security issue. Also new in this release is support for multiplexed streams in

Seems we've gone back to the -L/path/to/libvorbis/ -lvorbis missing while building libvorbisfile :( it appears that. libvorbisfile_la_LIBADD = libvorbis.la and libvorbisenc_la_LIBADD = libvorbis.la have gone missing from vorbis/lib/makefile.am Dave --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list,

All, Monty has made some improvements to the vorbis reference implementation, and we're ready to do a new release. Please sanity check the release candidate at http://people.xiph.org/~giles/2007/libvorbis-1.2.0rc2.tar.bz2 And let us know if there are any problems. The plan is to make an official release on Wednesday. Changes since the 1.1.2 release: * new ov_fopen() convenience

Tonight's commits so far: I finally wrote up the result of the comment header specification discussion. It's in the doc/ directory now. I plan on doing work in the libvorbis comment handling tonight to bring it up to date and make the interface more useful. gif->png conversion of the images in the docs Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg

Hello -- Some wav files have been crashing the stuff I checked out from cvs last night. Is this happening to anyone else? Red Hat Linux release 7.3 (Valhalla) Kernel 2.4.18-5 on an i686 gcc-2.96-110 glibc-2.2.5-36 Encoding "04_imiuta.wav" to "04_imiuta.ogg" at quality 1.00 [100.0%] [ 0m00s remaining] \Segmentation fault Program received signal

I'm pleased to announce the release of libvorbis and vorbis-tools 1.1.1. These releases include some bug and documentation fixes, but no new encoder modes. However, oggenc from this release now properly supports the new CBR engine introduced in libvorbis 1.1.0 but the 1.1.1 release of both libraries is required for things to work properly. Not that there was never a 1.1.0 release of

I'm pleased to announce the release of libvorbis and vorbis-tools 1.1.1. These releases include some bug and documentation fixes, but no new encoder modes. However, oggenc from this release now properly supports the new CBR engine introduced in libvorbis 1.1.0 but the 1.1.1 release of both libraries is required for things to work properly. Not that there was never a 1.1.0 release of