Your message dated Tue, 11 Jul 2006 15:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#286780: fixed in gjay 0.2.8.3-5 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: gjay Severity: normal Tags: patch When building 'gjay' on amd64 with gcc-4.0, I get the following error: gcc -c -g -Wall `pkg-config --cflags gtk+-2.0` -o gjay_xmms.o gjay_xmms.c gjay_xmms.c:29: error: static declaration of 'xmms_session' follows non-static declaration gjay.h:46: error: previous declaration of 'xmms_session' was here make[1]: *** [gjay_xmms.o] Error 1 make[1]: Leaving directory `/gjay-0.2.8.3' make: *** [build-stamp] Error 2 With the attached patch 'gjay' can be compiled on amd64 using gcc-4.0. Regards Andreas Jochens diff -urN ../tmp-orig/gjay-0.2.8.3/analysis.h ./analysis.h --- ../tmp-orig/gjay-0.2.8.3/analysis.h 2004-01-20 06:12:25.000000000 +0100 +++ ./analysis.h 2004-12-22 07:39:17.200938912 +0100 @@ -71,11 +71,6 @@ unsigned long data_length; /* length of data */ } waveheaderstruct; - -/* Mutex lock for analysis data */ -extern song * analyze_song; -extern int analyze_percent; - /* Analysis.c */ void analysis_daemon(void); //gboolean analyze(song * s); diff -urN ../tmp-orig/gjay-0.2.8.3/gjay.h ./gjay.h --- ../tmp-orig/gjay-0.2.8.3/gjay.h 2004-01-20 06:12:25.000000000 +0100 +++ ./gjay.h 2004-12-22 07:39:42.434102888 +0100 @@ -43,7 +43,6 @@ /* State */ extern gjay_mode mode; -extern gint xmms_session; /* User options */ extern gint verbosity;
--- End Message ---
--- Begin Message ---Source: gjay Source-Version: 0.2.8.3-5 We believe that the bug you reported is fixed in the latest version of gjay, which is due to be installed in the Debian FTP archive: gjay_0.2.8.3-5.diff.gz to pool/main/g/gjay/gjay_0.2.8.3-5.diff.gz gjay_0.2.8.3-5.dsc to pool/main/g/gjay/gjay_0.2.8.3-5.dsc gjay_0.2.8.3-5_amd64.deb to pool/main/g/gjay/gjay_0.2.8.3-5_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. martin f. krafft <[EMAIL PROTECTED]> (supplier of updated gjay package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Tue, 11 Jul 2006 23:12:56 +0200 Source: gjay Binary: gjay Architecture: source amd64 Version: 0.2.8.3-5 Distribution: unstable Urgency: low Maintainer: martin f. krafft <[EMAIL PROTECTED]> Changed-By: martin f. krafft <[EMAIL PROTECTED]> Description: gjay - An automatic and learning DJ for xmms Closes: 286780 361056 Changes: gjay (0.2.8.3-5) unstable; urgency=low . * Acknowledge NMU by Nathanael Nerode. Also thanks to Andreas Jochens for the patch (closes: Bug#286780). * Converted package to use dpatch. * Integrate patches by Lauri Alanko to fix analysis on amd64, and a buffer overrun (closes: #361056). * Push Standards-Version to 3.7.2; no changes needed. * Push DH compatibility to 5. Files: c6d2eae1fb21349bab1d33e1ccc98db0 601 sound extra gjay_0.2.8.3-5.dsc c54a9ed1370737ce02958c385f82fb05 5601 sound extra gjay_0.2.8.3-5.diff.gz 92f83b36a79a962b55c08faf322a4094 102586 sound extra gjay_0.2.8.3-5_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEtCBQIgvIgzMMSnURAhwxAJ4yTBWngWdWxZEWWMwzpIHaykYg/ACgvKeq bvwR6IuhQQPg4+J5Mt7eNNs= =XqOo -----END PGP SIGNATURE-----
--- End Message ---
