Package: wildmidi
Version: 0.2.3.4-2.1
Severity: wishlist
Tags: upstream

Dear Maintainer,

In February 2012, Chris Ison, made a 0.2.3.5 release and the wildmidi package
in Debian is still at 0.2.3.4 with a few bugs still unresolved and patches.

The 0.2.3.5 release was the last release by Chris, he had just a few more
commits in February and is stopped. His responses stop on Sourceforge, his
commits, his twitter feed. All attempts to contact him have also failed. The
queue of bugs and patches have been piling up as well.

In attempt to fix bugs for myself, I decided to fork his SVN repo and have
created a github repo with his commit history still intact here:
https://github.com/psi29a/wildmidi

Since then, there have been a number of contributors and patches have been
poring in. We've gutted the autotools and replaced it with a cmake system.
We're now able to cleanly, without warnings, build against latest GCC and Clang
on Debian and Ubuntu. We even managed to get wildmidi to compile with Visual
Studio 2010 and run. We're currently working on getting to running again on
OSX.

We're still ABI/API compatible, none of the symbols/exports have changed. You
can drop this in and link against it without any code changes in other
projects.

We've also kept the door open for Chris' return and can give the git repo to
him, or can join or stay where he is and just pull in our changes.

That being said, we propose a switch from old upstream to the new upstream.

I also would like to help with the package's maintenance in Debian.

What can I do here to help. :)

Cheers,
Bret Curtis


-- System Information:
Debian Release: wheezy/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11.0-14-generic (SMP w/8 CPU cores)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to