Bug 561618 – app-portage/g-octave-0.4.1-r4 doesn't work with portage python 3.4 module

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Olivier Diotte 2015-09-27 04:13:58 UTC]

# ls /usr/bin/g-octave*
/usr/bin/g-octave  /usr/bin/g-octave-2.7  /usr/bin/g-octave-3.3

# equery files portage | egrep '/python.*/portage/__init__.py$'
/usr/lib64/python2.7/site-packages/portage/__init__.py
/usr/lib64/python3.4/site-packages/portage/__init__.py


Reproducible: Always

Steps to Reproduce:
1. Install g-octave
2. Run 'emerge --config =g-octave-0.4.1-r4' as instructed
Actual Results:  
# emerge --config =g-octave-0.4.1-r4


Configuring pkg...

Traceback (most recent call last):
  File "/usr/bin/g-octave-3.3", line 42, in <module>
    import portage
ImportError: No module named 'portage'
mkdir: cannot create directory ‘’: No such file or directory
 * Extracting g-octave database files to: 
tar: : Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
 * ERROR: app-portage/g-octave-0.4.1-r4::gentoo failed (config phase):
 *   tar failed.
 * 
 * Call stack:
 *     ebuild.sh, line  93:  Called pkg_config
 *   environment, line 2767:  Called die
 * The specific snippet of code:
 *       tar -xzf "${DISTDIR}/${PN}-db-${DB_COMMIT:0:7}.tar.gz" -C "${db}" || die 'tar failed.';
 * 
 * If you need support, post the output of `emerge --info '=app-portage/g-octave-0.4.1-r4::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-portage/g-octave-0.4.1-r4::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/app-portage/g-octave-0.4.1-r4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-portage/g-octave-0.4.1-r4/temp/environment'.
 * Working directory: '/usr/lib64/python2.7/site-packages'
 * S: '/var/tmp/portage/app-portage/g-octave-0.4.1-r4/work/g-octave-0.4.1'



Expected Results:  
The command doesn't fail

[Comment 1 Olivier Diotte 2015-09-27 04:22:32 UTC]

Nevermind, bug is invalid: I hadn't read 2015-07-25-python-targets news item.

[Comment 2 Olivier Diotte 2015-09-27 04:27:28 UTC]

Well… looks like I spoke too fast: it is indeed not compatible with 3.4 (the g_octave module is only in 2.7 and 3.3) although I also hadn't done all the news item required.

[Comment 3 Olivier Diotte 2015-09-27 04:52:51 UTC]

Okay, after removing the package and installing it back (after having set my python3 correctly to 3.4), it all works. I can't emerge 'g-octave/optim-1.2.2' presumably because it is using INT_MAX without including limits.h, but I don't think this is related here.

Sorry for the bogus bug report.