Fails when binhost reports a 404:
!! Error fetching binhost package info from 'http://builds.developer.core-os.net/sdk/amd64/668.0.0/pkgs/'
Traceback (most recent call last):
File "/usr/lib/python-exec/python2.7/emerge", line 50, in <module>
retval = emerge_main()
File "/usr/lib64/python2.7/site-packages/_emerge/main.py", line 1154, in emerge_main
return run_action(emerge_config)
File "/usr/lib64/python2.7/site-packages/_emerge/actions.py", line 2818, in run_action
getbinpkgs="--getbinpkg" in emerge_config.opts)
File "/usr/lib64/python2.7/site-packages/portage/dbapi/bintree.py", line 633, in populate
self._populate(getbinpkgs)
File "/usr/lib64/python2.7/site-packages/portage/dbapi/bintree.py", line 1034, in _populate
_encodings["stdio"], errors="replace"))
TypeError: coercing to Unicode: need string or buffer, HTTPError found
The wrapper for `foo-config` style scripts updated `$PATH` so it could
call the real script by name instead of full path. However this means
that calls to shell utilities like `sed` may use the board's version
instead of the build host's. This hasn't been a problem in the past
because the board and host happened to be compatible but this may not
always be true.
In other news, come on people, switch to pkg-config already.
Refreshing eclasses and profiles can potentially introduce surprises but
the only notable change I see are fixing the sse2 flag for OpenSSL and
changing SLOTs for cross compilers.
Until recently Gentoo used stand-alone USE flags like `sse2` to toggle
optional CPU features. This has changed to USE_EXPAND style flags like
`cpu_flags_x86_sse2`. Our OpenSSL ebuild pulled in this change in commit
a9285ef530f88a1373c1459c4e20ca1065b24a91 but at the time the profiles
weren't updated to match, resulting in turning off sse2 for our OpenSSL
build.
Cross compiler ebuilds now always act as if the `multislot` USE flag was
on, allowing minor versions to be installed in parallel. e.g.:
- cross-*/gcc-4.8.3: SLOT changes from `4.8` to `4.8.3`
- cross-*/binutils-2.24-r3: SLOT changes from `0` to `2.24`
The new slot for binutils change may require adding a call to
`binutils-config`, similar to `gcc-config`, the next time we upgrade
binutils but for now nothing needs to change.
Packages updated:
eclass
licenses
profiles
scripts
