On Sun, Dec 09, 2012 at 02:01:21PM +0000, Stuart Henderson wrote: > Sorry I've not got time for a detailed answer to the whole mail right now, > but updating one port to -current without also updating dependencies > is often going to fail (especially for things like this which have > many dep's).
I realize the probability of success is inversely proportional to the number of deps. Recently I did get gdb 7.5 working on mips64el stable after I mentioned gdb losing its mind unwinding the stack and somebody mentioned 7.5 works. Luckily the port from current builds cleanly. > Since 5.2 there has been quite a lot of cleanup of system > headers, so various ports have had workarounds removed so they're > unlikely to build on 5.2 without a lot of extra work. This is why > developers will often recommend just moving to -current; and that way > if the problem still exists, you will be running the same OS/package > version that others can easily obtain themselves making it easier to > work on a fix. I do run current on Loongson because I'm not using it constantly and can afford to monkey around with it occasionally but on this box I don't want to have to upgrade if I can avoid it, until 5.3 comes out. At this point I'm trying to set up all the stuff I need and then just use it. > On OpenBSD -current always ought to be (and in general is) at least as > reliable as -stable (and often more so). The naming "-stable" is intended > to imply "stable api" / "very conservative changes only" rather than > "stable" as in reliable. This is not necessarily the same meanings as > given to the words in some other OS. Thanks, I realize that too. I look at it as the difference between changing as little as possible and low admin cost on a stable system while still having an excellent upgrade and patching path, with current being a state of the art system but one that requires frequent upgrades if anything goes wrong. I want to get this particular box doing what I want then to spend as little time managing it as possible. > > Things I'd point out, > > - if this was an upgrade rather than new installation, make sure all > packages were upgraded together; mixing and matching between versions > rarely works well It is a new 5.2 install. > - the symptoms might suggest some kind of X/display driver type of > problem, so more information about hardware (dmesg) might be helpful I don't think so since everything else works flawlessly as usual. I just installed OO on a Solaris box and it gets me past this issue so I'll wait for 5.3 to come out and then try libreoffice again. Thanks alot for taking the time to explain things. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary / \ http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
