dev-lisp/ecls-16.1.2-r1 eapply_user (or default) must be called in src_prepare()!

[Masn6n0]

I got an error for dev-lisp/ecls-16.1.2-r1:

* ecl-16.1.2.tgz BLAKE2B SHA512 size ;-) ...                                                                     [ ok ]
>>> Unpacking source...
>>> Unpacking ecl-16.1.2.tgz to /var/tmp/portage/dev-lisp/ecls-16.1.2-r1/work
>>> Source unpacked in /var/tmp/portage/dev-lisp/ecls-16.1.2-r1/work
>>> Preparing source in /var/tmp/portage/dev-lisp/ecls-16.1.2-r1/work/ecl-16.1.2 ...
/var/tmp/portage/dev-lisp/ecls-16.1.2-r1/temp/environment: line 1227: epatch: command not found
/var/tmp/portage/dev-lisp/ecls-16.1.2-r1/temp/environment: line 1228: epatch: command not found
 * ERROR: dev-lisp/ecls-16.1.2-r1::sage-on-gentoo failed (prepare phase):
 *   eapply_user (or default) must be called in src_prepare()!
 * 
 * Call stack:
 *            ebuild.sh, line  792:  Called __ebuild_main 'prepare'
 *   phase-functions.sh, line 1068:  Called __dyn_prepare
 *   phase-functions.sh, line  395:  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 '=dev-lisp/ecls-16.1.2-r1::sage-on-gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-lisp/ecls-16.1.2-r1::sage-on-gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-lisp/ecls-16.1.2-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lisp/ecls-16.1.2-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-lisp/ecls-16.1.2-r1/work/ecl-16.1.2'
 * S: '/var/tmp/portage/dev-lisp/ecls-16.1.2-r1/work/ecl-16.1.2'

>>> Failed to emerge dev-lisp/ecls-16.1.2-r1, Log file:

Can I use ecls-16.1.3 from official Gentoo overlay?

[kiwifb]

No, you cannot use ecls 16.1.3 - it does work with maxima but not with sage itself. Sage upstream (me and a few other sage devs are desperately waiting for a new release). I will fix all these issues in the morning in my time zone. Probably changes in eclass inheritance that I didn't notice.

[kiwifb]

It didn't trigger any warnings when I switched to eapi7 and it should have. Thanks for reporting.

[Masn6n0]

sci-chemistry/sage-jmol-bin same error:

 * Jmol-14.2.11_2015.01.20-binary.tar.gz BLAKE2B SHA512 size ;-) ...                                              [ ok ]
>>> Unpacking source...
>>> Unpacking Jmol-14.2.11_2015.01.20-binary.tar.gz to /var/tmp/portage/sci-chemistry/sage-jmol-bin-14.2.11-r1/work
>>> Source unpacked in /var/tmp/portage/sci-chemistry/sage-jmol-bin-14.2.11-r1/work
>>> Preparing source in /var/tmp/portage/sci-chemistry/sage-jmol-bin-14.2.11-r1/work/jmol-14.2.11_2015.01.20 ...
 * ERROR: sci-chemistry/sage-jmol-bin-14.2.11-r1::sage-on-gentoo failed (prepare phase):
 *   eapply_user (or default) must be called in src_prepare()!
 * 
 * Call stack:
 *            ebuild.sh, line  792:  Called __ebuild_main 'prepare'
 *   phase-functions.sh, line 1068:  Called __dyn_prepare
 *   phase-functions.sh, line  395:  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 '=sci-chemistry/sage-jmol-bin-14.2.11-r1::sage-on-gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sci-chemistry/sage-jmol-bin-14.2.11-r1::sage-on-gentoo'`.
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info =sage-jmol-bin-14.2.11
 * The complete build log is located at '/var/tmp/portage/sci-chemistry/sage-jmol-bin-14.2.11-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sci-chemistry/sage-jmol-bin-14.2.11-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sci-chemistry/sage-jmol-bin-14.2.11-r1/work/jmol-14.2.11_2015.01.20'
 * S: '/var/tmp/portage/sci-chemistry/sage-jmol-bin-14.2.11-r1/work/jmol-14.2.11_2015.01.20'

[kiwifb]

The normal course would be a new issue but I'll reopen that one for now. Should repoman catch those? May be too hard.

[kiwifb]

OK, that one should be fixed. I made some clean up the other day where I bumped the EAPI used. I did basic checking but I obviously missed the particular detail, possibly in a number of ebuilds since repoman doesn't catch that particular flaw.

So I am keeping the issue opened for you for any more ebuild you find to be faulty.

[kiwifb]

nauty will need a fix.

[kiwifb]

I think nauty was the last ebuild needing a fix. Re-open if you find another one.