On Wed, Jul 09, 2014 at 07:14:15PM +0100, Stuart Henderson wrote: > On 2014/07/09 19:09, Juan Francisco Cantero Hurtado wrote: > > On Wed, Jul 09, 2014 at 05:11:10AM -0500, Ed Ahlsen-Girard wrote: > > > After upgrading to the July 8 snapshot I duly ran sysmerge, then > > > pkg_add -u, and received this at the end of the output (preceding > > > output was normal): > > > > > > [gcc-4.6.4p7].libs-gcc-4.6.4p4->gcc-4.8.3p0: internal conflict between > > > gcc-4.8.3p0 and gcc-4.6.4p7 > > > Can't install [gcj-4.6.4p4]gcj-4.8.3p0: can't resolve gcc-4.8.3p0 > > > Can't install pdftk-2.02->2.02p0: can't resolve gcj-4.8.3p0 > > > py-Pillow-2.4.0->2.4.0: ok > > > Read shared items: ok > > > Couldn't find updates for .libs-gcc-4.6.4p4, pdftk-2.02 > > > Extracted 54077243 from 610265976 > > > > pkg_delete pdftk > > pkg_delete -a > > pkg_add pdftk > > Before trying this, it would be useful to investigate to try and work > out why it's happening, so that the actual problem can be fixed... > > Tarring up a copy of /var/db/pkg might be a good start.
I vaguely remember running into something like that at some point in my experiment. If it happens again, starting from a pristine install, I'm interested. Otherwise, it's a bug I probably fixed.
