Beep media player has changed its name (again) to bmp as a tarball...and a version update. The new version is 0.9.6.1. Reproducible: Always Steps to Reproduce:
Created attachment 22715 [details] Beep media player 0.9.6.1 ebuild While they changed versiononing numbers, they also again changed the tarball name to bmp, so it shouldn't be a problem.
You've changed it a bit too much. You can still use the old SRC_URI line, just change $P to bmp-$PV, as $PV refers only to the version number. So you should consider starting over again from a previous ebuild. There's another problem with it, and that is that the ebuild can't find a configure script. I've encountered this problem myself, and it usually means that you need to run autogen.sh. Too bad I don't know how to make it do that.
Created attachment 23255 [details] Updated bmp-0.9.6.1.ebuild Sorry, I originally based it from BMG, as I didn't know the ebuilds were here till I tried to give it to them. I fixed the problems, and used Gentoo's way of doing things.
Created attachment 23276 [details] Improvised ebuild that I used on my system
Ah, cool. I submitted the ebuild I just used on my system for comparison. It's just a quick hack, but it makes extended use of bmp-+ the PV variable instead of just P.
Created attachment 23900 [details, diff] Patch to make ebuild 0.9.6.1able This is a patch I made. It uses MY_P to rename both the SRC_URI and S, instead of doing it two seperate times. It also makes XML optional with the xml use flag as the other ebuild submitted does and adds it to IUSE as well. It keeps the package name the same, unlike the first submitted ebuild, which proposes a change to bmp. Without doing such a change, 1.0.5pre5 will have to be masked or taken out of portage because I don't see how else going from 1.0.5 to 0.9.6.1 would be seen as an upgrade. What's the status of this anyway? 0.9.6.1 is greatly improved IMO over 1.0.5pre5, I don't know why nothing has been done yet.
Reminding message regarding versioning change (as posted on their website) : Project started with 1.0.0-pre[4,5,6] versioning scheme. But this cause trouble with Debian packaging system as it will see the final 1.0.0 version as lower than the -pre versions. For that reason they changed it to 0.9.x with increasing microversion until they hit stable release (1.0.0). SO CURRENT & LATEST IS 0.9.6.1. FYI: 0.9.7 will be released on Feb 1st.
*** Bug 39451 has been marked as a duplicate of this bug. ***
Transfering the blockage for 39452 (bmp-skins-1.0) to this bug (making this the bmp 0.9.6 bug central) from bug 39451
I'm sure people are aware of this, but w/ the goofy version adjustments if we don't split bmp of from beep media player we're going to have fun with version'ing issues... (noting it so I can close out an informal bug on that).
just masking the ebuilds won't force an update. As long as the ebuild exists, portage will think it's validly installed. I'd recommend masking/version-bumping it and deleting the current one so people with it are forced to upgrade to the "lower" version (which is really newer). And we should change media-sound/beep-media-player to media-sound/bmp.
this is already in portage...
