On Tue, 26 Jan 2016 18:54:07 -0700 Ian Lepore wrote
> If someone with the same problem finds this thread on a search engine
> next week, they're sure going to wish you had said what the fix was, or
> linked to the forum post you found that fixed it.
>
> -- Ian
That's a really good point, Ian. I
If someone with the same problem finds this thread on a search engine
next week, they're sure going to wish you had said what the fix was, or
linked to the forum post you found that fixed it.
-- Ian
On Tue, 2016-01-26 at 17:00 -0800, Chris H wrote:
> Never mind. I was able to find a quick answer
Never mind. I was able to find a quick answer in the FreeBSD forums.
Thanks!
On Tue, 26 Jan 2016 12:27:05 -0800 "Chris H" wrote
> Greetings,
> I just updated one of my -CURRENT boxes that was ~8 mos. out. I
> (re)built the ports/packages locally, to reinstall/upgrade the box.
> I *did* read th
Greetings,
I just updated one of my -CURRENT boxes that was ~8 mos. out. I
(re)built the ports/packages locally, to reinstall/upgrade the box.
I *did* read the entry in UPDATING, regarding the switch from jpeg
to turbo-jpeg. But given the build process was somewhat automated,
I may have overlooked
