On 2016-11-16, Stuart Longland <stua...@longlandclan.id.au> wrote: > > Ahh okay, I omitted this as I saw this as a userland issue not a kernel > one, and dmesg can be rather long.
It's useful for any issues as it shows exactly what you're running. > The dmesg in full: >> [ using 587952 bytes of bsd ELF symbol table ] >> Copyright (c) 1982, 1986, 1989, 1991, 1993 >> The Regents of the University of California. All rights reserved. >> Copyright (c) 1995-2016 OpenBSD. All rights reserved. http://www.OpenBSD.org >> >> OpenBSD 6.0 (GENERIC) #627: Thu Jul 28 21:15:50 MDT 2016 >> dera...@loongson.openbsd.org:/usr/src/sys/arch/loongson/compile/GENERIC So in your case, you're running 6.0-release, so you need to be using packages from http://$MIRROR/pub/OpenBSD/6.0/packages/mips64el/ >> While you are on, say, a snapshot as of 2016-10-01 the project keeps >> moving. Depending on the point in the release process it takes hours to >> days until _your_ snapshot isn't the current snapshot anymore. >> >> packages(7) keep being built against the current snapshot, not _your_ >> snapshot. Library mismatches between *your* snapshot base system and the >> *projects* current ports happen soon. > > Ahh, so the ports tree is rolling-release and not tied to a particular > release of OpenBSD. This makes sense. The ports tree checked out without a CVS tag is for -current, for 6.0 you need to checkout with -r OPENBSD_6_0 (which gives you 6.0-stable). >> But 404s? Have you checked whether the 404-files are on the servers with >> a different version number possibly? > > I'll have to go over more thoroughly which packages were causing the > download errors, when I saw them my first instinct was: "the ports are > out of date, try updating those first in case they've fixed the download > links". > > Upstream projects sometimes do move things around, and often without > telling people, so didn't see this as being an issue. Packages don't fetch anything from upstream, they are entirely fetched from OpenBSD servers/mirrors. If you are seeing problems installing from packages, please post a transcript of commands+errors (plus show which path you're fetching from, either in /etc/pkg.conf or $PKG_PATH). Ports do fetch from upstream and can be subject to them moving things around, though there is a fallback to an OpenBSD mirror for almost everything. > Right, so openbsd-wip is the "unstable" tree? It's a tree used by some people while they're working on new ports, I don't think it has anything to do with what you're doing. > I grabbed ports from > https://github.com/openbsd/ports/ which I understood to just be ports > CVS mirrored on git. Three reasons I went the git repo: > > 1. I know git well > 2. Using github means I'm not putting so much demand on the OpenBSD > project CVS servers > 3. If I find I need to make changes, I can branch it, and optionally, > export those changes out as patches to be submitted back (e.g. new > ports, fixes, etc) without needing to be on-line at the time. Please don't use this. No conversion tools have yet been fully successful at converting the OpenBSD tree on an ongoing basis. It's regenerated from scratch periodically so is not considered stable, and sometimes you can end up with the checkout not matching the files you would get from cvs. But you shouldn't need to build anything yourself anyway unless you're working on ports yourself (there are a very few cases where licenses don't permit redistribution but I don't think this applies to many things you'd be particularly likely to run on loongson). I think there is probably just some confusion between snapshots (which are regularly updated binaries produced from -current development trees) and release. (The two coincide for a couple of days when the release is tagged; sometimes people familiar with the development process make a copy of this at this point as a "preview", which is OK but they then need to be aware of what's going on with respect to newer snapshots, package builds etc).
