Michael Grigoriev released a new major version of IMMS and subsequently a minor bugfix on 5th Dec 2005. IMMS is decoupled from xmms and currently works with bmp although plans are in the works to develop a plugin for rhythmbox and possibly others, therefroe a package rename is probably in order. I have not tested the current ebuild. Reproducible: Always Steps to Reproduce:
Created attachment 74248 [details] imms-3.0.1.ebuild Added an ebuild based on xmms-imms-2.0.1, made it block on xmms-imms as this replaces it. Added extra deps for torch, gtk+ and libglade and installs immsremote's glade file to /usr/share/imms.
There is a patch on the IMMS website to also add support Audacious (which is the player I use). Perhaps the ebuild could support Audacious in addition to BMP (which is no longer developed) and XMMS.
The ebuild works for version 3.0.2 as well with the proper renaming.
Created attachment 101237 [details] imms-3.0.2.ebuild
I've added an ebuild for imms 3.0.2 with audacious. I didn't test with bmp. There is a weird bug with autoconf (and/or the configure.ac file). There is a sed "script" to remove what was causing grief. What was removed was a test for a bug in certain that caused grief with getting random numbers.
Created attachment 112358 [details] new ebuild for latest beta level for imms (imms-3.1.0_rc2) At least a start on imms-3.1.0_rc2. Note that I ran into a problem with the latest audacious code drop and the link phase of imms. It wasn't finding xmms_show_message. The src_unpack phase has a small "edit" to bypass this problem.
Created attachment 112360 [details] Woops .. wrong file correct ebuild upload
> latest audacious code drop and the link phase of imms. It wasn't finding > xmms_show_message. The src_unpack phase has a small "edit" to bypass this > problem. > Oh .. the code does work, the error is a result from a late binding issue, the missing function is resolved at run-time.
When I try to emerge imms-3.1.0_rc2 (not the wrong one), I got this error: >>> Unpacking source... >>> Unpacking imms-3.1.0-rc2.tar.bz2 to /var/tmp/portage/media-plugins/imms-3.1.0_rc2/work /usr/local/portage/media-plugins/imms/imms-3.1.0_rc2.ebuild: line 39: cd: /var/tmp/portage/media-plugins/imms-3.1.0_rc2/work/imms-3.1.0_rc2-rc2: No such file or directory sed: can't read /var/tmp/portage/media-plugins/imms-3.1.0_rc2/work/imms-3.1.0_rc2-rc2/rules.mk: No such file or directory >>> Source unpacked. >>> Compiling source in /var/tmp/portage/media-plugins/imms-3.1.0_rc2 ... >>> Source compiled. >>> Test phase [not enabled]: media-plugins/imms-3.1.0_rc2 >>> Install imms-3.1.0_rc2 into /var/tmp/portage/media-plugins/imms-3.1.0_rc2/image/ category media-plugins !!! dobin: build/immsd does not exist !!! ERROR: media-plugins/imms-3.1.0_rc2 failed. Call stack: ebuild.sh, line 1614: Called dyn_install ebuild.sh, line 1060: Called qa_call 'src_install' environment, line 3024: Called src_install imms-3.1.0_rc2.ebuild, line 44: Called die !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/media-plugins/imms-3.1.0_rc2/temp/build.log'. !!! This ebuild is from an overlay: '/usr/local/portage'
(In reply to comment #9) > When I try to emerge imms-3.1.0_rc2 (not the wrong one), I got this error: > > >>> Unpacking source... > >>> Unpacking imms-3.1.0-rc2.tar.bz2 to /var/tmp/portage/media-plugins/imms-3.1.0_rc2/work > /usr/local/portage/media-plugins/imms/imms-3.1.0_rc2.ebuild: line 39: cd: > /var/tmp/portage/media-plugins/imms-3.1.0_rc2/work/imms-3.1.0_rc2-rc2: No such > file or directory > sed: can't read > /var/tmp/portage/media-plugins/imms-3.1.0_rc2/work/imms-3.1.0_rc2-rc2/rules.mk: > No such file or directory > >>> Source unpacked. > >>> Compiling source in /var/tmp/portage/media-plugins/imms-3.1.0_rc2 ... > >>> Source compiled. > >>> Test phase [not enabled]: media-plugins/imms-3.1.0_rc2 > > >>> Install imms-3.1.0_rc2 into /var/tmp/portage/media-plugins/imms-3.1.0_rc2/image/ category media-plugins > !!! dobin: build/immsd does not exist > > !!! ERROR: media-plugins/imms-3.1.0_rc2 failed. > Call stack: > ebuild.sh, line 1614: Called dyn_install > ebuild.sh, line 1060: Called qa_call 'src_install' > environment, line 3024: Called src_install > imms-3.1.0_rc2.ebuild, line 44: Called die > > !!! (no error message) > !!! If you need support, post the topmost build error, and the call stack if > relevant. > !!! A complete build log is located at > '/var/tmp/portage/media-plugins/imms-3.1.0_rc2/temp/build.log'. > > !!! This ebuild is from an overlay: '/usr/local/portage' > I changed the ebuild's name from imms-3.1.0_rc2.ebuild to imms-3.1.0.ebuild and now it merges.
I just found this bug after writing an ebuild for imms myself, silly me! I'm attaching my ebuild for imms-3.1.0-rc2 though, which is slightly different from the current one. The building of plugins for audacious and beep have not been tested, I use neither. Other main difference is that the 'optional' components, the analyser and remote control have USE flags. Also attaching a patch for configure.ac that removes the scary 'WARNING' message for 'optional' dependancies/components that aren't installed. I'm not an expert at writing ebuilds, so I'm not claiming this ebuild is 'better'. But I thought I should post it and maybe we can get an ebuild that meets all standards so that imms might actually make it into the tree (maybe, hoping...)
Created attachment 122931 [details] imms 3.1.0-rc2 ebuild
Created attachment 122935 [details, diff] configure.ac patch This patch removes unnecessarily scary 'WARNING' messages for optional components that aren't installed.
I seem to get the issue reported on the imms mailing list whereby sox (as called by the imms analyzer) hangs with 100% CPU [1] [2] [3]. This seems to not occur with media-sound/sox-12.18.2 (but does occur with current stable media-sound/sox-12.17.9). It occurs with versions 3.0.2 and 3.1.0-rc2 of imms. Note that sox version 13.0.0 does not work with imms analyzer as the command-line options for sox (that analyzer uses) have changed. Just thought I'd leave a message in case someone else runs into this trouble. [1] http://lists.luminal.org/message/20060513.031313.99ec6fa8.en.html [2] http://lists.luminal.org/message/20060221.034710.be533cf8.en.html [3] http://lists.luminal.org/message/20060128.175612.734fca4d.en.html
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Heuristics show that no Gentoo developer has commented on your ebuild. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
