Bugzilla Bug 133293

Guys, could we please get the following packages:
  media-libs/adplug-1.5.1-r2
  media-sound/adplay-1.4-r2
  media-plugins/xmms-adplug-1.1-r1
marked stable on all CC'ed arches? The latest releases (-r1, -r2) fix some
compilation problems for users using libbinio-1.4 (which is currently marked
stable).

As you'll notice, adplay-1.4-r2 and adplug-1.5.1-r2 have been committed to the
tree just earlier today. The only change since -r1 is the removal of a CXXFLAGS
hack in favour of header files patching.

If you don't feel comfortable keywording packages that have been in the tree
for such a short time, please keyword the -r1 versions.

Thanks in advance :)

Should the tests for media-libs/adplug work?  Getting the following on SPARC:

Testing format: Adlib Tracker 1.0 - OK
Testing format: MKJamz Audio File - OK
Testing format: Digital-FM 0.99 - OK
Testing format: Scream Tracker 3.00 - OK
Testing format: Reality ADlib Tracker - OK
Testing format: Bob's Adlib Music - OK
Testing format: Ken Silverman's Music Format - OK
Testing format: Ultima 6 Music - OK
Testing format: eXtra Simple Music - OK
Testing format: DeFy Adlib Tracker - OK
Testing format: TwinTeam (packed S3M) - OK
Testing format: Sierra On-Line EGA MIDI - OK
Testing format: RdosPlay RAW - OK
Testing format: LOUDNESS Sound System - OK
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Testing format: AdLib Tracker 2 - OK
Testing format: LucasArts AdLib MIDI - OK
Testing format: Creative Music Format (CMF MIDI) - OK
Testing format: SNG File Format - OK
Testing format: xad: rat player - FAIL
Testing format: Faust Music Creator - OK
Testing format: BoomTracker 4 - OK
Testing format: DOSBox Raw OPL - OK
Testing format: Surprise! Adlib Tracker 2 (version 9) - OK
Testing format: HSC Adlib Composer / HSC-Tracker - OK
Testing format: Mlat Adlib Tracker - OK
Testing format: Surprise! Adlib Tracker 2 (version 1) - OK
Testing format: AMUSIC Adlib Tracker - OK
/bin/sh: line 1:   776 Bus error               ${dir}$tst
FAIL: playertest
===================
1 of 1 tests failed
===================

hmm, that may be SPARC specific, as i got

==================
All 1 tests passed
==================

on x86 for adplug-1.5.1-r2.

PS: if i should post 'emerge --info' let me know.

I guess they should -- at least they work for me on x86. It looks like the
problem is with the 'EdLib packed (version 4)' format. I'll see about getting
access to one of the Gentoo sparc dev machines so that I can have a closer look
at it.

x86 done

jason: perhaps your box is broken? '/bin/sh: line 1:   776 Bus error           
   ${dir}$tst' looks pretty suspicious, and it works on amd64 as well.

amd64 done

http://primates.ximian.com/~miguel/sparc/SparcLinux.html
Search for SIGBUS there (and no, it's NOT hardware related, maybe it sounds
like it but no).

Results on ppc:

Testing format: Sierra On-Line EGA MIDI - OK
Testing format: RdosPlay RAW - OK
Testing format: LOUDNESS Sound System - OK
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Warning: The player is writing data out of range! (reg = 51, val = fffffff9)
Testing format: AdLib Tracker 2 - OK
Testing format: LucasArts AdLib MIDI - OK
Testing format: Creative Music Format (CMF MIDI) - OK
Testing format: SNG File Format - OK
Testing format: xad: rat player - FAIL
Testing format: Faust Music Creator - OK
Testing format: BoomTracker 4 - OK
Testing format: DOSBox Raw OPL - OK
Testing format: Surprise! Adlib Tracker 2 (version 9) - OK
Testing format: HSC Adlib Composer / HSC-Tracker - OK
Testing format: Mlat Adlib Tracker - OK
Testing format: Surprise! Adlib Tracker 2 (version 1) - OK
Testing format: AMUSIC Adlib Tracker - OK
Testing format: EdLib packed (version 4) - FAIL
Testing format: IMF File Format - OK
Testing format: xad: BMF Adlib Tracker - OK
Testing format: xad: flash player - OK
Testing format: Adlib Visual Composer - OK

Two test fail, and on testing whatever comes after Adlib Visual Composer it
started eating every cpu cycle it can get until after some hours I got tired of
waiting for it to finish and killed it instead.

I had the same test problems with the currently stable version, so I marked it
ppc stable anyway.

It looks like this problem is fixed in the latest version -- 2.0.1.

2.0.1 appears to have fixed the problems with FEATURES="test" here on SPARC as
well as now successfully playing the .D00 files I had in a pile of samples that
xmms-adplug should handle.  Mind if SPARC stablizes this early as the currently
stable version doesn't work so well (if at all)?

By all means, please do so.

Thanks.  It's now stable.

Stable on all arches -- thanks everyone.