Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

>> >> If there are security related patches or things needed to be fixed, >> that the package works as it should, you can simple run pkg_add -iu > > You can do this *if* you have a source of updated packages, e.g. via > mtier's openup, or packages that you've built yourself. Thanks for

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

On 2017-11-09, Christoph R. Murauer wrote: > If I understood your question correct ... > >> Running: OpenBSD6.2-release >> >> Goal: To run a secure and functional web server. >> (the server is currently up and running and used by >> the public at large) > > If you apply the patches

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

Sorry, typo. Meaned pkg_delete -a

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

> Thanks for your replay Christoph. > > Please correct me if I'm wrong, but as I understand things, this only > works if one is following OpenBSD-current. I am running -release. > This is an in-use production server; I don't feel wise running > -current. If you install for example OpenBSD 6.2

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

On Thu, Nov 09, 2017 at 02:04:39PM -0500, Jeff wrote: > Is this a rational solution to the problem? I'm somewhat regretting > going this route as, unlike with pkg_add, building some ports from the > tree pulls in more dependencies than via pkg_add (I am assuming that > these are build dependencies

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

On Thu, November 9, 2017 4:54 pm, Jeff wrote: > On Thu, 9 Nov 2017 22:06:43 +0100 > "Christoph R. Murauer" wrote: > >> If I understood your question correct ... >> >> > Running: OpenBSD6.2-release >> > >> > Goal: To run a secure and functional web server. >> > (the server is

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

On Thu, 9 Nov 2017 22:06:43 +0100 "Christoph R. Murauer" wrote: > If I understood your question correct ... > > > Running: OpenBSD6.2-release > > > > Goal: To run a secure and functional web server. > > (the server is currently up and running and used by > > the public at large) >

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

If I understood your question correct ... > Running: OpenBSD6.2-release > > Goal: To run a secure and functional web server. > (the server is currently up and running and used by > the public at large) If you apply the patches from the errata page using syspatch(8) (if you are on i386 / amd64)

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

Jeff writes: > I do not imply that openbsd.org recommends waiting for the next release > and not patching software. I personally use openup from m:tier, they provide updated packages as errata are released. https://www.mtier.org/solutions/apps/openup/ Allan

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

On Thu, 2017-11-09 at 14:52 -0500, Jeff wrote: > Is it not worth it to update ports in this way; meaning, > is it better to simply wait for OpenBSD6.3 and stick with > binary packages? > > The openbsd.org site says: > The ports tree is meant for

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

On Thu, 9 Nov 2017 14:04:39 -0500 Jeff wrote: > Is it not worth it to update ports in this way; meaning, is it better > to simply wait for OpenBSD6.3 and stick with binary packages only > (as recommended on the openbsd.org site)? It is has been pointed out to me that my

Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

On 11/9/2017 2:04 PM, Jeff wrote: > Hello all, > > [...] > > Also, is there an easy/sane way to remove packages that were only > required for building once the ports have been updated? You could use: $ pkg_info -t to show packages which are not required by any other packages

Keeping up to date with ports and putting ports/pobj on wxallowed filesystem

Hello all, Is this the sane/correct thing to do? What is the impact? Running: OpenBSD6.2-release Goal: To run a secure and functional web server. (the server is currently up and running and used by the public at large) Previously: Only installing needed packages as binaries via pkg_add. Now: