On Fri, Oct 07, 2016 at 08:47:31AM -0400, yary wrote:
> On Thu, Oct 6, 2016 at 11:48 PM, Foo74 wrote:
> >
> > Thanks for posting the response. Do you know what from the error message
> > shows that it was a -current build? I think I would have spent days
> > figuring that out. :)
>
> Replying t
On Thu, Oct 6, 2016 at 11:48 PM, Foo74 wrote:
>
> Thanks for posting the response. Do you know what from the error message
> shows that it was a -current build? I think I would have spent days figuring
> that out. :)
Replying to list as well- There were two clues. One was how uname -a
reported
>Your package path points to 6.0- release. But your error messages
> indicate you've installed a snapshot of -current, the development
> breach. Use snapshot packages, or install the release.
Thanks! You're right, I had intended to install 6.0 from release, but
ended up getting a snapshot ISO. I'l
I'm installing OpenBSD i386 on a fresh new hard drive, I've set PKG_PATH,
and I can't add packages- my tries give errors about quirks. Trying a
bare "pkg_add quirks" tells me:
# pkg_add quirks
Error from http://mirrors.mit.edu/pub/OpenBSD/6.0/packages/i386/quirks-2.241.tgz
unsigned package
Can't f
4 matches
Mail list logo