Closed GoogleCodeExporter closed 9 years ago
The current version of mupen64plus 1.99.4 with many backported patches from
1.99.5 (to be released). See
* https://launchpad.net/ubuntu/+source/mupen64plus
* https://launchpad.net/ubuntu/+source/mupen64plus-audio-sdl
* https://launchpad.net/ubuntu/+source/mupen64plus-core
* https://launchpad.net/ubuntu/+source/mupen64plus-input-sdl
* https://launchpad.net/ubuntu/+source/mupen64plus-rsp-hle
* https://launchpad.net/ubuntu/+source/mupen64plus-rsp-z64
* https://launchpad.net/ubuntu/+source/mupen64plus-ui-console
* https://launchpad.net/ubuntu/+source/mupen64plus-video-arachnoid
* https://launchpad.net/ubuntu/+source/mupen64plus-video-glide64
* https://launchpad.net/ubuntu/+source/mupen64plus-video-rice
* https://launchpad.net/ubuntu/+source/mupen64plus-video-z64
And never snapshots can be found at:
* https://launchpad.net/~sven-eckelmann/+archive/ppa
* https://launchpad.net/~sven-eckelmann/+archive/ppa-mupen64plus
I would think that this makes this ticket invalid.
P.S.: You should also know that no developer here is a Ubuntu developer.
Therefore, we cannot upload mupen64plus to ubuntu directly. The usual procedure
is to upload it to Debian unstable, wait until some ubuntu MOTU developer
decides to sync the Ubuntu universe version of mupen64plus with the Debian
unstable version and then count the days till the next ubuntu release. Ubuntu
will not (there are exceptions) take newer versions of a software and upload it
for a currently stable ubuntu release. Even small patches are an extreme big
problem and will not merged in a stable version (most of the time).
Please contact the Ubuntu MOTU team <ubuntu-motu@lists.ubuntu.com> directly in
case you think differently about the situation.
P.P.S.: The tarball works fine... you just have to use the correct one. The
best way to get a new versions is probably to build it yourself using the
instructions from http://code.google.com/p/mupen64plus/wiki/CompilingFromHg
Original comment by s...@narfation.org
on 22 Feb 2012 at 8:38
Original issue reported on code.google.com by
jkhaywo...@gmail.com
on 20 Feb 2012 at 9:32