Bug 295176 – x11-misc/xmobar-0.9.2-r1 merge error

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description LeNsTR 2009-11-30 11:29:06 UTC]

* Messages for package x11-misc/xmobar-0.9.2-r1:

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 * 
 *   /usr/portage/x11-misc/xmobar/files/xmobar-0.9.2-*
 *   ( xmobar-0.9.2-* )
 * ERROR: x11-misc/xmobar-0.9.2-r1 failed:
 *   Cannot find $EPATCH_SOURCE!
 * 
 * Call stack:
 *     ebuild.sh, line   49:  Called src_unpack
 *   environment, line 3130:  Called base_src_unpack
 *   environment, line  387:  Called base_src_util 'all'
 *   environment, line  432:  Called base_src_util 'unpack' 'autopatch'
 *   environment, line  426:  Called epatch '/usr/portage/x11-misc/xmobar/files/xmobar-0.9.2-*'
 *   environment, line 1467:  Called die
 * The specific snippet of code:
 *                   die "Cannot find \$EPATCH_SOURCE!";
 * 
 * If you need support, post the output of 'emerge --info =x11-misc/xmobar-0.9.2-r1',
 * the complete build log and the output of 'emerge -pqv =x11-misc/xmobar-0.9.2-r1'.
 * The complete build log is located at '/var/tmp/portage/x11-misc/xmobar-0.9.2-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-misc/xmobar-0.9.2-r1/temp/environment'.
 * S: '/var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work/xmobar-0.9.2'


Reproducible: Always

[Comment 1 lucapost 2009-12-01 12:29:23 UTC]

the same problem here

[Comment 2 Eric Johnson 2009-12-02 07:04:00 UTC]

same issue

[Comment 3 Damian Nadales 2009-12-02 08:28:15 UTC]

(In reply to comment #2)
> same issue
Same problem as well.

[Comment 4 Ryan Funduk 2009-12-02 17:22:08 UTC]

For those from google, you might have luck with this temporary fix: `emerge "<xmobar-0.9.2-r1"`

Someone please correct me if I'm wrong, but it seems to work for me.

[Comment 5 Ryan Funduk 2009-12-02 19:56:52 UTC]

Actually, I may have a better solution:

You can edit the ebuild file (x11-misc/xmobar/xmobar-0.9.2-r1.ebuild) and remove the line (around line 30 or so) that contains a cabal setting: --constraint=base<4

Followed by `ebuild xmobar*.ebuild digest` and rerun the emerge.

[Comment 6 Eric Johnson 2009-12-03 23:52:13 UTC]

(In reply to comment #5)
> You can edit the ebuild file (x11-misc/xmobar/xmobar-0.9.2-r1.ebuild) and
> remove the line (around line 30 or so) that contains a cabal setting:
> --constraint=base<4

It compiled successfully, but only after I commented line 29:

PATCHES=("${FILESDIR}/${P}-*")

Commenting out the line avoids the real problem - that the "files" directory containing the patch files is missing/wasn't distributed from portage repo.

[Comment 7 Lennart Kolmodin (RETIRED) 2009-12-14 23:06:42 UTC]

Thanks for the report guys!

It was a missing patch, solving a high CPU usage.

Please reopen if the problem doesn't go away.

[Comment 8 Damian Nadales 2009-12-15 11:13:07 UTC]

I think the dependency on dev-haskell/x11-xft is missing. I'm getting the following error:

[1 of 1] Compiling Main             ( /var/tmp/paludis/x11-misc-xmobar-0.9.2-r1/work/xmobar-0.9.2/Setup.lhs, /var/tmp/paludis/x11-misc-xmobar-0.9.2-r1/work/xmobar-0.9.2/Setup.o )
Linking setup ...
Configuring xmobar-0.9.2...
setup: At least the following dependencies are missing:
X11-xft >=0.2, hinotify -any

!!! ERROR in x11-misc/xmobar-0.9.2-r1::gentoo:
!!! In cabal-configure at line 956
!!! setup configure failed

[Comment 9 Eric Johnson 2010-01-03 22:14:46 UTC]

(In reply to comment #7)
> Thanks for the report guys!
> 
> It was a missing patch, solving a high CPU usage.
> 
> Please reopen if the problem doesn't go away.
> 

The patch file issue has been resolved. However, the line with the unrecognized flag still exists. Commenting out this line (as referenced in comment #5) does the trick.

>>> Unpacking xmobar-0.9.2.tar.gz to /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work
 * Applying xmobar-0.9.2-cpu-high-load.patch ...                                                                                                                   [ ok ]
>>> Source unpacked in /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work
>>> Compiling source in /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work/xmobar-0.9.2 ...
 * Using cabal-1.2.3.0.
[1 of 1] Compiling Main             ( /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work/xmobar-0.9.2/Setup.lhs, /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work/xmobar-0.9.2/Setup.o )
Linking setup ...
setup: Unrecognised flags:
 --constraint=base<4
 * 
 * ERROR: x11-misc/xmobar-0.9.2-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3126:  Called cabal_src_compile
 *             environment, line  666:  Called cabal-configure
 *             environment, line  592:  Called die
 * The specific snippet of code:
 *       ./setup configure --ghc --prefix=/usr --with-compiler="$(ghc-getghc)" --with-hc-pkg="$(ghc-getghcpkg)" --prefix=/usr --libdir=/usr/$(get_libdir) --libsubdir=${P}/ghc-$(ghc-version) --datadir=/usr/share/ --datasubdir=${P}/ghc-$(ghc-version) ${cabalconf} ${CABAL_CONFIGURE_FLAGS} "$@" || die "setup configure failed"
 *  The die message:
 *   setup configure failed