On 02/16/17 10:48, poma wrote:
> In the meantime, you can try to upgrade to the latest 'libimobiledevice',
> to see if that changes anything regarding the issue;
> See:
> "RPM Packages of the latest available (from source) version of
libimobiledevice"
>
https://github.com/RPM-Outpost/libimobiledevice
>
> Download and build:
> $ git
clonehttps://github.com/RPM-Outpost/libimobiledevice.git
> $ cd libimobiledevice/
>
> $ sed -i 's/python2-Cython/Cython/' *
>
> $ ./create-packages.sh
>
> $ ls -1 RPMs/x86_64/
> libimobiledevice-1.2.1-git.2017.01.18.fc24.x86_64.rpm
> libimobiledevice-debuginfo-1.2.1-git.2017.01.18.fc24.x86_64.rpm
> libimobiledevice-devel-1.2.1-git.2017.01.18.fc24.x86_64.rpm
> libimobiledevice-utils-1.2.1-git.2017.01.18.fc24.x86_64.rpm
>
+
And that routine produced:
[bobg@box10 libimobiledevice]$ ls -1
RPMs/x86_64/
libimobiledevice-1.2.1-git.2017.01.18.fc25.x86_64.rpm
libimobiledevice-debuginfo-1.2.1-git.2017.01.18.fc25.x86_64.rpm
libimobiledevice-devel-1.2.1-git.2017.01.18.fc25.x86_64.rpm
libimobiledevice-utils-1.2.1-git.2017.01.18.fc25.x86_64.rpm
This process is new to me. Did the
script install these rpm's or should I
do it?