fvwm-themes 0.7.0 has been released, it depends on >=x11-wm/fvwm-2.5.8 Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 21309 [details] Ebuild for fvwm-themes-0.7.0 up to date ebuild for fvwm-themes-0.7.0 ,fvwm-themes-extra will be provided as additional package.
Created attachment 21310 [details, diff] gentoo patch for fvwm-themes 0.7.0. this patch is needed in order to install.I just renamed the patch used in 0.6.2.
when I try to bump the patch and the ebuild, and emerge, I get: checking for FvwmM4... /usr/lib/fvwm/2.5.8/FvwmM4 configure: error: You have fvwm-2.5.8, which is not up to date You need at least fvwm-2.5.8 Any ideas here are appreciated.
I have the same problem as Brandon Hale on my machine, which is running ~x86.
It works fine here with fvwm-2.5.8-r2. Why the ebuild is not in the portage already?
Because me (the responsible developer) was unable to sucessfully test this ebuild due to the error I've posted in an earlier comment, and confirmed by another. I do my best to confirm that all ebuilds I add work as expected. Here I cannot say this is the case. HTH, --tseng
how can I help to fix this bug ?
should be fixed.
I believe that the bug is in the following code segment (from line 4864 onward in the configure script) # Hopefully this "sort" is portable (after many tries using awk and expr) if (echo $REQUIRED_FVWM_VERSION; echo $FVWM_VERSION) \ | sed 's/\./ /g' | uniq | sort -n +0 -1 +1 -2 +2 -3 -c 2>/dev/null; then : # fvwm version is ok else { { echo "$as_me:$LINENO: error: You have fvwm-$FVWM_VERSION, which is not up to date You need at least fvwm-$REQUIRED_FVWM_VERSION" >&5 echo "$as_me: error: You have fvwm-$FVWM_VERSION, which is not up to date You need at least fvwm-$REQUIRED_FVWM_VERSION" >&2;} { (exit 1); exit 1; }; } fi By commenting it out, I was able to get fvwm-themes to install. Since portage already handles the dependency testing, maybe we can remove the above code segment from the configure script from now on ?
