python unmasks, that have changed abi and config revealing another "obscure" package Reproducible: Always Steps to Reproduce: 1. rebuild of all python dependent packages finds broken app-pda/libimobiledevice-1.1.6 2. or emerge =app-pda/libimobiledevice-1.1.6 3. Actual Results: configure: error: Could not link test program to Python. Maybe the main Python library has been installed in some non-standard library path. If so, pass it to configure, via the LDFLAGS environment variable. Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib" ============================================================================ ERROR! You probably have to install the development version of the Python package for your distribution. The exact name of this package varies among them. ============================================================================ While we (humble users) mostly agree about some packages having out of date python support that is not following upstream, we are bit upset that portage tree consistency are always checked *after* bugs reported. I hope 2016 year will be a year of changing minds and moving away of reactive workflow. yes, this means, test ALL (literally) packages. Changes that are potentially touching all reverse deps of python need run of buildbot-like testing. This will also help to find "upstream" broken packages, one may have an excuse about why breakages happen.
Created attachment 418918 [details] build.log
just in case its a stopper for gnome merge.
Created attachment 419262 [details] updated ebuild
Created attachment 421706 [details] build.log of failed emerge I am also experiencing this issue on libimobiledevice-1.2.0. I have attached my build.log. I can provide any other logs if necessary.
This has also begun causing problems with my updates and I am unable to run a system update without excluding many packages. Currently I am having to add the following excludes in order to get my world updates to work, although not completely: --exclude libimobiledevice --exclude libplist --exclude ifuse --exclude libusbmuxd --exclude gvfs --exclude upower-pm-utils --exclude thunar Rather messy and I would like to be able to have this fixed correctly, soon if possible. Thank you.^^
As a work-around you can add app-pda/libimobiledevice -python_targets_python3_3 -python_targets_python3_4 -python_targets_python3_5 to (one of) your package.use file(s).
Happened here @ amd64-gnome-unstable_20160110-213500 too.
commit c60e3d690e7a2254893cd21285d62135660c8405 Author: Mike Gilbert <floppym@gentoo.org> Date: Sun Jan 24 21:20:15 2016 -0500 app-pda/libimobiledevice: Override PYTHON_LDFLAGS in src_configure Works around broken build system. Bug: https://bugs.gentoo.org/567916 Package-Manager: portage-2.2.27_p49 app-pda/libimobiledevice/libimobiledevice-1.1.6-r1.ebuild | 9 +++++++-- app-pda/libimobiledevice/libimobiledevice-1.2.0.ebuild | 9 +++++++-- 2 files changed, 14 insertions(+), 4 deletions(-)
