On 4/26/2014 11:37, John Marino wrote: > On 4/26/2014 10:56, Zachary Crownover wrote: >> Another case of a package conflict that pkgng is incapable of resolving >> related to updates of KDE packages. Again, the necessary actions is to >> take the confliting packages and sudo pkg delete -f packagename, >> followed by pkg upgrade, again. What's preventing pkgng from >> intelligence on this matter and a sense of dependency/conflict >> resolution? Is this something that aims to be addressed by next release? > > I already said a new solver is coming with pkgng 1.3 (the next release). > That remains true. > > I don't know which package you are referring to, but if it really did > require something like that, there would have been an entry in UPDATING > -- one that doesn't require that but reassigns origins, etc. > > Did you look for an UPDATING entry? >
Ok, this is a perfect example of why not to put critical information only in the subject title. See updating: > 20140403: > AFFECTS: users of net/kdnssd > AUTHOR: [email protected] > > KDE SC ports have been updated to 4.12.4. kdnssd package has been renamed > to match upstream naming. pkgng users need to update package origin > manually: > > # pkg set -o net/kdnssd:net/zeroconf-ioslave Did you see this updating entry? John
