Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 581552 - sys-apps/install-xattr-0.5-r1 fails to install
Summary: sys-apps/install-xattr-0.5-r1 fails to install
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Anthony Basile
URL:
Whiteboard:
Keywords:
: 581572 581576 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-04-29 13:05 UTC by Patrick Lauer
Modified: 2016-04-29 18:00 UTC (History)
6 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Lauer gentoo-dev 2016-04-29 13:05:47 UTC
>>> Emerging (1 of 1) sys-apps/install-xattr-0.5-r1::gentoo
 * install-xattr-0.5.tar.bz2 SHA256 SHA512 WHIRLPOOL size  ...        [ ok ]
>>> Unpacking source...
>>> Unpacking install-xattr-0.5.tar.bz2 to /var/tmp/portage/sys-apps/install-xattr-0.5-r1/work
>>> Source unpacked in /var/tmp/portage/sys-apps/install-xattr-0.5-r1/work
>>> Preparing source in /var/tmp/portage/sys-apps/install-xattr-0.5-r1/work/install-xattr ...
 * ERROR: sys-apps/install-xattr-0.5-r1::gentoo failed (prepare p
Comment 1 Patrick Lauer gentoo-dev 2016-04-29 13:06:58 UTC
 * ERROR: sys-apps/install-xattr-0.5-r1::gentoo failed (prepare phase):
 *   eapply_user (or default) must be called in src_prepare()!

Sorry, first paste got cut off ...

Problem is that you can't override src_prepare the way you did, since eapply_user *must* be called
Comment 2 jospezial 2016-04-29 13:48:58 UTC
...or default.

It is in src_compile() where it does not belong I think.
Please test ebuilds before bump to the tree!
Comment 3 jorgicio 2016-04-29 15:51:11 UTC
I confirm the same happens here.

hackenherr:~# emerge -1 install-xattr                                                                                                                                                 [12:43:20]
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-apps/install-xattr-0.5-r1::gentoo
 * install-xattr-0.5.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                                                         [ ok ]
>>> Unpacking source...
>>> Unpacking install-xattr-0.5.tar.bz2 to /var/tmp/portage/sys-apps/install-xattr-0.5-r1/work
>>> Source unpacked in /var/tmp/portage/sys-apps/install-xattr-0.5-r1/work
>>> Preparing source in /var/tmp/portage/sys-apps/install-xattr-0.5-r1/work/install-xattr ...
 * ERROR: sys-apps/install-xattr-0.5-r1::gentoo failed (prepare phase):
 *   eapply_user (or default) must be called in src_prepare()!
 * 
 * Call stack:
 *            ebuild.sh, line 805:  Called __ebuild_main 'prepare'
 *   phase-functions.sh, line 974:  Called __dyn_prepare
 *   phase-functions.sh, line 380:  Called die
 * The specific snippet of code:
 *   		die "eapply_user (or default) must be called in src_prepare()!"
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/install-xattr-0.5-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/install-xattr-0.5-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/work/install-xattr'
 * S: '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/work/install-xattr'

>>> Failed to emerge sys-apps/install-xattr-0.5-r1, Log file:

>>>  '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/temp/build.log'

 * Messages for package sys-apps/install-xattr-0.5-r1:

 * ERROR: sys-apps/install-xattr-0.5-r1::gentoo failed (prepare phase):
 *   eapply_user (or default) must be called in src_prepare()!
 * 
 * Call stack:
 *            ebuild.sh, line 805:  Called __ebuild_main 'prepare'
 *   phase-functions.sh, line 974:  Called __dyn_prepare
 *   phase-functions.sh, line 380:  Called die
 * The specific snippet of code:
 *   		die "eapply_user (or default) must be called in src_prepare()!"
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/install-xattr-0.5-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/install-xattr-0.5-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/work/install-xattr'
 * S: '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/work/install-xattr'
Comment 4 Anthony Basile gentoo-dev 2016-04-29 16:15:43 UTC
(In reply to Patrick Lauer from comment #1)
>  * ERROR: sys-apps/install-xattr-0.5-r1::gentoo failed (prepare phase):
>  *   eapply_user (or default) must be called in src_prepare()!
> 
> Sorry, first paste got cut off ...
> 
> Problem is that you can't override src_prepare the way you did, since
> eapply_user *must* be called

ah yes EAPI=6. sorry man!  this is going to take some getting used to.  i did test with ebuild and it didn't complain, so .... ???
Comment 5 Anthony Basile gentoo-dev 2016-04-29 16:16:52 UTC
(In reply to jospezial from comment #2)
> ...or default.
> 
> It is in src_compile() where it does not belong I think.
> Please test ebuilds before bump to the tree!

what makes you assume that i didn't?  there might be an issue in ebuild.
Comment 6 bwcknr 2016-04-29 16:27:10 UTC
At least over here there is no issue with ebuild itself.
Complains as expected

midgard ~ # ebuild /usr/portage/sys-apps/install-xattr/install-xattr-0.5-r1.ebuild clean install
 * install-xattr-0.5.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                                                                           [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                                                                        [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                                                                      [ ok ]
>>> Unpacking source...
>>> Unpacking install-xattr-0.5.tar.bz2 to /var/tmp/portage/sys-apps/install-xattr-0.5-r1/work
>>> Source unpacked in /var/tmp/portage/sys-apps/install-xattr-0.5-r1/work
>>> Preparing source in /var/tmp/portage/sys-apps/install-xattr-0.5-r1/work/install-xattr ...
 * ERROR: sys-apps/install-xattr-0.5-r1::gentoo failed (prepare phase):
 *   eapply_user (or default) must be called in src_prepare()!
 * 
 * Call stack:
 *            ebuild.sh, line  780:  Called __ebuild_main 'prepare'
 *   phase-functions.sh, line 1005:  Called __dyn_prepare
 *   phase-functions.sh, line  380:  Called die
 * The specific snippet of code:
 *   		die "eapply_user (or default) must be called in src_prepare()!"
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/install-xattr-0.5-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/install-xattr-0.5-r1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/work/install-xattr'
 * S: '/var/tmp/portage/sys-apps/install-xattr-0.5-r1/work/install-xattr'
Comment 7 Anthony Basile gentoo-dev 2016-04-29 16:32:51 UTC
This should be fixed.  Please test 0.5-r1 and -9999 and reopen if its still a problem.
Comment 8 Ben Kohler gentoo-dev 2016-04-29 16:37:48 UTC
*** Bug 581572 has been marked as a duplicate of this bug. ***
Comment 9 Ben Kohler gentoo-dev 2016-04-29 18:00:51 UTC
*** Bug 581576 has been marked as a duplicate of this bug. ***