Hi Christoph, thanks, long due update indeed, I will take a look ASAP.
Did you check the code in the new version complies with the DFSG ? Best, piem On 11/15/2017 06:46 PM, Christoph Biedl wrote: > retitle 775341 chuck: new upstream version 1.3.5.2 available > tags 775341 patch > thanks > >> There is a new upstream version available: 1.3.5.0 >> http://chuck.cs.princeton.edu/release/ > > Now it's already 1.3.5.2 ... > > Somebody asked me about the efforts needed to bring chuck to the latest > upstream version in order to benefit from new features. Turns out it's > not *that* difficult. So in order to avoid work is done twice, the diff > on debian/ is attached. For the upstream tarball, use uscan or plain > wget on the upstream server and rename. > > While declared a NMU, this diff goes far beyond that: > > * Packaging has been modernized in every regard, also the previous > modifications went upstream, were no longer needed, or could be > worked around by a .install file. > * Two commits were cherry-picked that fix obvious bugs, reported by gcc. > * Repacking no longer happens as I fail to see why the affected files > are not dfsg compliant, I might be wrong. > * Support for OSS was removed upstream, so here as well. The Linux > kernel will drop it soon. > * Support for pulse(audio) was added. > * The examples/ directory is now shipped in a separate -data package as > suggested by lintian, to avoid huge amounts of arch-independent > data in a arch-dependent package. > > Status: Builds, and the pulse version works fine. > > Things to do: > > # Blocker > > * Review license status of each and every file, update > debian/copyright where required. > > # Upstream > > * Ask upstream for license clarification of src/util_sndfile.c and > some more since it seems the chuck license was prepended > automatically. > * Ask upstream to fix the FSF address in the license statements. > * Ask upstream to use trusted certificates on their web server, then > switch to secure URLs in debian/control and elsewhere. > * Bring the typo fixes upstream. There are more in comments. > > # Packaging > > * Perhaps there are nicer ways to write debian/rules > * Is there really the need for three chuck binaries? > * Are there more applications to build for, see <src/makefile.*>? > * Something else worth to be cherry-picked from upstream git at > <https://github.com/ccrma/chuck>? > > Cheers, > > Christoph >
signature.asc
Description: OpenPGP digital signature
