SynCE Version 0.13 just got released: http://sourceforge.net/projects/synce/ Reproducible: Always
While in ebuild Runtime Dependencies >=app-pda/synce-hal-0.13, but not ~app-pda/synce-hal-0.13? i think it causes any problems when new release will come out. In old ebulds dep '>=' (app-pda/synce-hal-0.1) has reason (to make choice for synce-hal-0.2 and synce-hal-0.1 by hand), but in new ebuilds we must use strong versions dependencies.
I think also the ~app-pda/synce-whatever-${PV} is wrong, because upstream fixes get released as synce-whatever-0.13.1, 0.13.2, and so on... probably =app-pda/synce-whatever-${PV}* is the right one
Portage cannot resolve dependencies for synce-0.13 if USE='kde -hal' -- that USEflag combination is invalid anyway since USE='kde' ultimately brings hal in through synce-kpm, etc, etc. I'll throw some suggested patches up shortly...
Created attachment 193061 [details] synce-0.13.ebuild This version of the ebuild only brings in synce-odccm if USE kde and hal are *both* unset.
fixed in CVS, still synce-0.13.ebuild thanks Michael A. Smith if there are new issues open a new bug please