On 11/10/13 10:22 AM, Ralf Corsepius wrote:
On 10/11/2013 04:02 PM, Frank wrote:
> Updated my 19 installation this morning and ran into errors again.
>
> This is from yum's log:
>
>
> Oct 11 09:42:25 psacct-6.6.1-6.fc19.i686: ts_done name in te is
> usbmuxd should be psacct-6.6.1-6.fc19.i686
> Oct 11 09:42:27 kernel-headers-3.11.3-201.fc19.i686: ts_done name in
> te is psacct should be kernel-headers-3.11.3-201.fc19.i686
> Oct 11 09:42:28 libtar-1.2.11-25.fc19.i686: ts_done name in te is
> kernel-headers should be libtar-1.2.11-25.fc19.i686
>
>
>
> [root@localhost log]# rpm -qa | grep usbmuxd
> usbmuxd-1.0.8-10.fc19.i686
> usbmuxd-1.0.8-9.fc19.i686
> [root@localhost log]#
*-10 is in updates-testing, not in updates, so you are mildly cheating
by telling us to be running f19 ;)
/I have been known to cheat :)
/
>
> I can remove rpms reference to the old usbmuxd as I encountered
> similar problems a week or two ago.
>
> Are these packaging problems or what ?
Yes, this is a packaging bug in usbmux* < *-10 [1].
*-10 fixes this bug, however as the bug is in < *-10 (which everybody
has installed), there is hardly anything we can do about it
packaging-wise.
=> upgrading to *-10 will cause everybody to hit this bug and go
through this bumpy and uneasy road.
After upgrading to *-10, try
# rpm -e --noscripts usbmuxd-1.0.8-9.fc19.i686
Yes, as I have run into the problem before that's basically what I
did and the problem is gone again
Cheers