Re: [HEADS UP] Planned deprecation of portsnap

[Lars Engels]

On Tue, Aug 04, 2020 at 02:43:20PM -0400, Steve Wills wrote:
> 
> We are planning to deprecate use of portsnap in ports.
> 
> The reasons are as follows (in no particular order):
> 
> * Portsnap doesn't support quarterly branches, even years after 
> quarterly branches were created and changed to the default for non-HEAD 
> packages.
> 
> * Portsnap doesn't seem to save disk space compared to svn or git, if 
> you count the metadata (stored in /var/db/portsnap by default) and you 
> do an apples-to-apples comparison of svn or git without history and 
> ignoring possible ZFS compression. That is, you use "svn export" or git 
> "clone --depth 1", you see this disk usage:
> 
>  342Msvnexport
>  426Mgit
>  477Mportsnap
> 
> * Portsnap also doesn't work offline which git does. With git, you can 
> also easily add the history by running "git pull --unshallow"
> 
> * This migration away from portsnap fits well with the planned migration 
> to git.
> 
> * Also based on the patches we've seen in Bugzilla for some time, usage 
> of portsnap causes folks to too easily accidentally submit patches to 
> Bugzilla which don't apply easily.
> 
> * Since portsnap doesn't support quarterly branches, it often causes 
> users to build on the wrong branch or end up with mismatched packages. 
> That is, they install packages from quarterly via pkg, then want to 
> customize so run portsnap and build from head, which can cause problems, 
> as we often see. Even when this doesn't happen, it adds to 
> troubleshooting to verify that it didn't.
> 
> We are aware people have gotten used to portsnap, but believe:
> 
> * People should be able to easily use svnlite in base or git from pkgs. 
> (Very few people seem to actually use WITHOUT_SVNLITE).
> 
> * There is also the possibility of falling back to fetching a tar or zip 
> from https://cgit-beta.freebsd.org/ports/ although this does make 
> updating harder.
> 
> How it will be done, in order:
> 
> * Update poudriere to use svn by default. This is already done:
> 
>https://github.com/freebsd/poudriere/pull/764
>  
> https://github.com/freebsd/poudriere/commit/bd68f30654e2a8e965fbdc09aad238c8bf5cdc10
> 
> * Update docs not to mention portsnap. This is already in progress:
> 
>https://reviews.freebsd.org/D25800
>https://reviews.freebsd.org/D25801
>https://reviews.freebsd.org/D25803
>https://reviews.freebsd.org/D25805
>https://reviews.freebsd.org/D25808
>https://svnweb.freebsd.org/changeset/base/363798
> 
>Many thanks to the folks who have worked and are working on this!
> 
> * Make WITHOUT_PORTSNAP default in base. Currently not certain when this 
> will happen. May not happen before 13.0, but hopefully it will.
> 
> * Eventually, portsnap servers will see low enough usage they can be 
> disabled.
> 
> We welcome any constructive feedback. All input would be heard, and if 
> the plans need to be amended, we will come back to you with the amended 
> plan in a couple of weeks. This process will take some time and 
> hopefully won't be too disruptive to anyone's usual workflow.
> 

I'm probably fine with this and I think that all of the (now) supported
methods have pros and cons.
To leverage the UX flaws of git and svn(lite) compared to portsnap
having a wrapper script around the two tools would be very appreciated.

Something like

# portsnap-ng --mode git --branch 2020Q2 --destination /ports/2020Q2 fetch 
extract
  The package devel/git does not seem to be installed, do you want to install 
it? (Y/n) _

With sane defaults, so you can just run portsnap fetch extract like
you're used to and this
downloads the latest ports tree to /usr/ports using base svnlite(1).

While we're here: Can we please have a separate user that is used to
checkout the tree? 

Lars


P.S.: Please DO NOT name the wrapper portsnap-ng. :-)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Pkg repository is broken...

[Lars Engels]

On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote:
> On Monday,  2 March 2020 at 17:58:01 +, marco wrote:
> > On Sun, Mar 01, 2020 at 04:50:59PM -0500, you (Brennan Vincent) sent the 
> > following to [freebsd-current] :
> >> Apparently something has its ABI erroneously listed as FreeBSD:13.0:amd64
> >> instead of FreeBSD:13:amd64.
> >>
> >> ```
> >> $ sudo pkg update -f
> >> Updating FreeBSD repository catalogue...
> >> Fetching meta.conf: 100%163 B   0.2kB/s00:01
> >> Fetching packagesite.txz: 100%6 MiB   6.4MB/s00:01
> >> Processing entries:  72%
> >> pkg: wrong architecture: FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64
> >> pkg: repository FreeBSD contains packages with wrong ABI: 
> >> FreeBSD:13.0:amd64
> >> Processing entries: 100%
> >> Unable to update repository FreeBSD
> >> Error updating repositories!
> >
> > Ran into this very same problem today too.
> > Just learned on #freebsd that the repos are temporarily borked and
> > people are working hard to fix it.
> 
> Any workarounds in the meantime?  This must affect a lot of people,
> including those who use 12-:
> 
>   pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64
>   pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64

Still broken for me on 12.1.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: devel/llvm80 port on 12.1

[Lars Engels]

On Thu, Dec 12, 2019 at 06:06:52PM +0100, Jan Beich wrote:
> Lars Engels  writes:
> 
> > So it looks like on 12.1 the mesa-dri port can use the base llvm instead
> > of the one from ports and save all people running Xorg almost 1 GB of
> > disk space?
> 
> Does the patch in bug 242607 help?

Yes, thank you. It works for me on my Thinkpad T450s with HD Graphics 5500.
I wonder if that's also true for AMD and nvidia users.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: devel/llvm80 port on 12.1

[Lars Engels]

On Thu, Dec 12, 2019 at 10:50:00AM -0500, Kevin P. Neal wrote:
> On Thu, Dec 12, 2019 at 04:42:07PM +0100, Lars Engels wrote:
> > I'm trying reduce the size of the NomadBSD image and the biggest
> > installed package is devel/llvm80 with 848 MiB.
> > llvm80 is a dependency of graphics/mesa-dri which is needed for
> > x11-servers/xorg-server.
>
> As a build dependency or a run-time dependency? If build only then you can
> remove it assuming you are using packages.

mesa-dri's Makefile.common has:

USE+= compiler:c++11-lib

.if ${LLVM_DEFAULT:S,-devel,990,} >= 90
LLVM_DEFAULT=   80
.endif

.if ${ARCH} == aarch64 || ${ARCH} == amd64 || ${ARCH:Marm*} || ${ARCH} == i386 
|| ${ARCH:Mmips*} || ${ARCH:Mpowerpc*}
BUILD_DEPENDS+= llvm${LLVM_DEFAULT}>=3.9.0_4:devel/llvm${LLVM_DEFAULT}
.if ${COMPONENT} != libs
RUN_DEPENDS+=   llvm${LLVM_DEFAULT}>=3.9.0_4:devel/llvm${LLVM_DEFAULT}
.endif
CONFIGURE_ENV+= LLVM_CONFIG=${LOCALBASE}/bin/llvm-config${LLVM_DEFAULT}
LDFLAGS+=   -Wl,-rpath=${LOCALBASE}/llvm${LLVM_DEFAULT}/lib
CONFIGURE_ARGS+=--enable-llvm
.else
CONFIGURE_ARGS+=--disable-llvm
.endif

and Makefile has:


.if ${ARCH} == aarch64 || ${ARCH} == amd64 || ${ARCH:Marm*} || ${ARCH} == i386 
|| ${ARCH:Mmips*} || ${ARCH:Mpowerpc*}
GALLIUM_DRIVERS=SWRAST  # llvmpipe


>
> > Looking at the llvm version of 12.1-RELEASE in base I see that it is the
> > same version like the installed port:
>
> > So it looks like on 12.1 the mesa-dri port can use the base llvm instead
> > of the one from ports and save all people running Xorg almost 1 GB of
> > disk space?
>
> Does the base clang have all the features that the ports/packages clang
> has? They may have left out bits of clang that are not needed for the
> base system.
>
> That may be why the port is required by something graphics related.

That could be. Maybe someone from x11@ knows more.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

devel/llvm80 port on 12.1

[Lars Engels]

I'm trying reduce the size of the NomadBSD image and the biggest
installed package is devel/llvm80 with 848 MiB.
llvm80 is a dependency of graphics/mesa-dri which is needed for
x11-servers/xorg-server.

Looking at the llvm version of 12.1-RELEASE in base I see that it is the
same version like the installed port:

$ /usr/bin/clang --version
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 
8.0.1)
Target: x86_64-unknown-freebsd12.1
Thread model: posix
InstalledDir: /usr/bin

$ /usr/local/llvm80/bin/clang --version
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-portbld-freebsd12.0
Thread model: posix
InstalledDir: /usr/local/llvm80/bin

So it looks like on 12.1 the mesa-dri port can use the base llvm instead
of the one from ports and save all people running Xorg almost 1 GB of
disk space?

-- 
Lars
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Checking you the maintainer of a port?

[Lars Engels]

On Wed, Nov 27, 2019 at 09:07:55PM +, Brooks Davis wrote:
> On Wed, Nov 27, 2019 at 02:05:56PM -0700, Janky Jay, III wrote:
> > Hello,
> > 
> > On 11/27/19 2:03 PM, @lbutlr wrote:
> > > I thought that the maintainer of a port was listed somewhere in the files 
> > > at user/ports//portbase/ but evidently not. What is the easiest 
> > > way to find out, sitting in console on a server without a GUI, to find 
> > > out who the maintainer is? (On my desktop I can just google and launch a 
> > > browser, but that is not possible on most of the servers which do not 
> > > have web clients installed.
> > > 
> > > (Right now I am looking for the maintainer of roundcube, but this is a 
> > > general question.)
> > > 
> > 
> > Please see the "MAINTAINER=" line in the port's "Makefile".
> 
> A slightly more general answer is:
> 
> cd /usr/ports//; make -V MAINTAINER

There's already a target for it:

  make maintainer

in a port's directory.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Looking to port weasyprint

[Lars Engels]

On Mon, May 20, 2019 at 04:00:00PM +0200, Kurt Jaeger wrote:
> Hi!
> 
> > A simple testbuild in poudriere after some cleanup seems to work.
> > I'm testbuilding right now.
> 
> Committed as r502116, print/py-weasyprint, with the following
> description:
> 
> WeasyPrint helps web developers to create PDF documents. It turns simple
> HTML pages into gorgeous PDF.
> 
> WWW: https://weasyprint.org/
> 

Thanks, but it does not work, yet:

$ weasyprint http://weasyprint.org /tmp/weasyprint-website.pdf

Traceback (most recent call last):
  File "/usr/local/bin/weasyprint", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
3241, in 
@_call_aside
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
3225, in _call_aside
f(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
3254, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
583, in _build_master
ws.require(__requires__)
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
900, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'CairoSVG>=1.0.20' distribution was not 
found and is required by WeasyPrint

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Request for commit approval audio/virtual_oss

[Lars Engels]

On Thu, Mar 28, 2019 at 09:31:17PM +0100, Hans Petter Selasky wrote:
> Update virtual_oss to latest version, 1.2.1.
> 
> Among other features and bugfixes virtual_oss now can do simple FIR 
> filtering on the played back or recorded audio.
> 
> Approved by: lme

:-)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Fwd: FreeBSD ports you maintain which are out of date

[Lars Engels]

On Sun, Mar 17, 2019 at 10:48:12AM +, Dima Pasechnik wrote:
> 
> I just got an email from portscout about
> www/squidclamav/ port. Indeed, it has no maintainer:
> https://www.freshports.org/www/squidclamav/
> 
> but the point of this email is a total mystery, probably just an
> error, no? I never touched this port, for sure...
> 
> I think it's OK if once upon a time an email listing all the
> un-maintained ports is sent around,
> but otherwise it's merely spam.
>

You're subscribed to po...@freebsd.org mailing list, so you also receive
portscout's mails to this address. Unmaintained ports have it as
MAINTAINER address.
Portscout only sents out a single mail when it finds a new upstream
version, so it's no spam.
Many ports unmaintained ports have received updates and some even got a
new maintainer because of portscount's mails to this mailing list.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net-mgmt/icingaweb2 fails to build with PHP 7.3

[Lars Engels]

On Sun, Jan 27, 2019 at 02:45:45PM +0100, Stefan Bethke wrote:
> It appears that (older?) versions of icingaweb2 do not work correctly with 
> PHP 7.3. From my poudriere build log:
> > ===>  Staging for icingaweb2-2.6.2_1
> > ===>   Generating temporary packing list
> > /bin/mkdir -p 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/icingaweb2/bash_completion.d/
> > install  -m 0644 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/icingaweb2-2.6.2/etc/bash_completion.d/icingacli
> >   
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/icingaweb2/bash_completion.d
> > (cd /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/icingaweb2-2.6.2 && /bin/rm 
> > -f -r .mailmap changelog.py icingaweb2.spec  bin/license_writer.py packages 
> > test)
> > (/usr/bin/find /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/icingaweb2-2.6.2 
> > -name "*.bak" -delete)
> > /bin/mkdir -p 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2
> > (cd /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/icingaweb2-2.6.2 &&  
> > /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 
> > 2>&1) &&  /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd 
> > '\''$2'\'' && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd 
> > '\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE . 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2)
> > /bin/chmod 755 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/bin/icingacli
> > install -l rs 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/bin/icingacli
> >  /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/bin/icingacli
> > /bin/mkdir -p 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/etc/icingaweb2
> > /bin/mkdir -p 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/icingaweb2/apache
> > (cd 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2 
> > &&  ICINGAWEB_CONFIGDIR=/nonexistent  ./bin/icingacli setup config 
> > webserver apache --path=/icingaweb2  
> > --root=/usr/local/www/icingaweb2/public --config=/usr/local/etc/icingaweb2  
> > --file=/wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/icingaweb2/apache/icingaweb2.conf)
> > 
> > Fatal error: Uncaught ErrorException: "continue" targeting switch is 
> > equivalent to "break". Did you mean to use "continue 2"? in 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/Modules/Module.php:689
> > Stack trace:
> > #0 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/ClassLoader.php(303):
> >  Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}(2, 
> > '"continue" targ...', '/wrkdirs/usr/po...', 689, Array)
> > #1 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/ClassLoader.php(303):
> >  require()
> > #2 [internal function]: 
> > Icinga\Application\ClassLoader->loadClass('Icinga\\Applicat...')
> > #3 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/Modules/Manager.php(227):
> >  spl_autoload_call('Icinga\\Applicat...')
> > #4 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/Application
> >  in 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/Modules/Module.php
> >  on line 689
> > *** Error code 255
> > 
> > Stop.
> > make: stopped in /usr/ports/net-mgmt/icingaweb2
> 
> I’ve also found this Debian issue:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914457
> 
> Are you working on a fix? Otherwise, I might give porting the Debian change 
> as a local patch.
> 
Hi Stefan,

thanks for reporting this. I can work on this in a couple of days. If
you could work on a patch before, I won't be mad at you. :)

Lars
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: vim - GTK2 or GTK3?

[Lars Engels]

On Tue, Jan 01, 2019 at 01:07:24PM -0700, Adam Weinberger wrote:
> I'm curious whether the default Vim port should use GTK2 or GTK3 as
> its UI toolkit, but I use neither so I need input from people here.
> 
> Right now it defaults to GTK2, but I'm suspecting that more people use
> GTK3 these days. I haven't run X in about 10 years, so I don't really
> know one way or the other. If anybody on this list has thoughts about
> GTK2 vs GTK3 (or something else!) as the default, I'd love to hear it.
> 
> The Vim choices are currently a mess, but it'll get better once
> subpackages land.

Firefox and Chromium both depend on GTK3, so it's highly likely that a
typical desktop user has GTK3 installed.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: A potential new porter seeking some clarifications

[Lars Engels]

On Thu, Dec 13, 2018 at 10:41:01PM +0800, Arthur Pirika wrote:
> Hi all! I’m hoping to get into porting for FreeBSD, right now just
> focusing on one package, a plugin for bitlbee, however I’d like to
> extend my hand to maintain other ports in the future once I have more
> knowledge and practice with the system. 

Welcome! :-)
> 
> Before I start, though, I just need some clarifications of things from the 
> porter’s handbook. 
> 
> 1. If I understand correctly, the version of the ports tree as fetched
> by portsnap isn’t the best for working on the tree. I should instead
> make another copy of the tree as an svn checkout? Distfiles, however,
> still go to /usr/ports/distfiles

You can change this by setting DISTDIR variable in /etc/make.conf to a
directory you like. See ports(7) manpage.

> 2. Is it absolutely necessary to use poudriere before submitting a
> port? I’m still getting to grips with how it works, and if I need to
> get comfortable with it first, I’ll do so. 

That really depends on the change's size. Trivial patches can often be
sub-/committed without a poudriere run. portlint -ac, make check-plist
and make package can find potential issues for you.
Bigger changes should be build in poudriere. You don't need to attach
the logs to the PR, though.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upgrade from PHP71 to PHP72 breaks icingaweb2

[Lars Engels]

On Thu, Nov 08, 2018 at 10:06:15PM +0100, Xavier wrote:
> On 08/11/2018 14:17, Lars Engels wrote:
> > Do you see any php related entries in your apache logs?
> > 
> 
> No, just the stack trace on screen
> 

I just encountered the same problem after upgrading from php71 to php72.
I had to also upgrade mod_php71 to mod_php72 and restart Apache
afterwards. Now Icinga Web 2 is up and running again.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upgrade from PHP71 to PHP72 breaks icingaweb2

[Lars Engels]

On Thu, Nov 08, 2018 at 01:02:43PM +0100, Xavier wrote:
> On 08/11/2018 12:57, Xavier wrote:
> > On 07/11/2018 13:09, Lars Engels wrote:
> >> On Wed, Nov 07, 2018 at 08:48:19AM +0100, Guido Falsi wrote:
> >>> On 07/11/18 08:46, Guido Falsi wrote:
> >>>> On 07/11/18 07:24, Xavier wrote:
> >>>>> On 03/11/2018 18:50, Guido Falsi wrote:
> >>>>>> On 03/11/18 18:17, Xavier Humbert wrote:
> >>>>>>> Context FreeBSD 11-STABLE, last pkg upgrade led to update PHP71 to 
> >>>>>>> PHP72.
> >>>>>>> php72-json is installed, but when I launch a navigator, IcingaWeb2
> >>>>>>> crashes with :
> >>>>>>>
> >>>>>>>> Call to undefined function Icinga\Util\json_encode() in
> >>>>>>>> /usr/local/www/icingaweb2/library/Icinga/Util/Json.php:57
> >>>>>>>>
> >>>>>>>
> >>>>>>> Any idea ?
> >>>>>>
> >>>>>> Yess, you need to install the php72-json package which provides the
> >>>>>> json_encode() function.
> >>>>>>
> >>>>>> The port actually depends on it, so something went wrong with your 
> >>>>>> update.
> >>>>>>
> >>>>>> You should try reinstalling it and check that all dependencies install
> >>>>>> successfully.
> >>>>>>
> >>>>>
> >>>>> Thanks for your answer Guido. Unfortunately, as I wrote, php-json *is*
> >>>>> installed, in the correct flavour. And pkg check -Bd succeeds
> >>>>>
> >>>>
> >>>> Is it being loaded?
> >>>>
> >>>> Check for 'ext-20-json.ini' to be present in /usr/local/etc/php and have
> >>>> correct content.
> >>>>
> >>>
> >>> BTW, if you've not tried it a 'pkg install -f php72-json' is worth a try.
> >>
> >> Can you check if you also upgraded the mod_php[57][16] module for
> >> Apache?
> >>
> > 
> > Ah ! I tried already too reinstall php72-json, but not mod_php
> > And it fails :
> > 
> > # pkg install -f mod_php72
> > Updating FreeBSD repository catalogue...
> > FreeBSD repository is up to date.
> > All repositories are up to date.
> > The following 1 package(s) will be affected (of 0 checked):
> > 
> > New packages to be INSTALLED:
> > mod_php72: 7.2.11
> > 
> > Number of packages to be installed: 1
> > 
> > The process will require 5 MiB more space.
> > 1 MiB to be downloaded.
> > 
> > Proceed with this action? [y/N]: y
> > [1/1] Fetching mod_php72-7.2.11.txz: 100%1 MiB   1.2MB/s00:01
> > pkg: cached package mod_php72-7.2.11: size mismatch, fetching from remote
> > Fetching mod_php72-7.2.11.txz: 100%1 MiB   1.2MB/s00:01
> > pkg: cached package mod_php72-7.2.11: size mismatch, cannot continue
> > 
> > I'll investigate that.
> > 
> > Thanks,
> > 
> 
> Well, after pkg update, it installs, but the web is still failing

Do you see any php related entries in your apache logs?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upgrade from PHP71 to PHP72 breaks icingaweb2

[Lars Engels]

On Wed, Nov 07, 2018 at 08:48:19AM +0100, Guido Falsi wrote:
> On 07/11/18 08:46, Guido Falsi wrote:
> > On 07/11/18 07:24, Xavier wrote:
> >> On 03/11/2018 18:50, Guido Falsi wrote:
> >>> On 03/11/18 18:17, Xavier Humbert wrote:
>  Context FreeBSD 11-STABLE, last pkg upgrade led to update PHP71 to PHP72.
>  php72-json is installed, but when I launch a navigator, IcingaWeb2
>  crashes with :
> 
> > Call to undefined function Icinga\Util\json_encode() in
> > /usr/local/www/icingaweb2/library/Icinga/Util/Json.php:57
> >
> 
>  Any idea ?
> >>>
> >>> Yess, you need to install the php72-json package which provides the
> >>> json_encode() function.
> >>>
> >>> The port actually depends on it, so something went wrong with your update.
> >>>
> >>> You should try reinstalling it and check that all dependencies install
> >>> successfully.
> >>>
> >>
> >> Thanks for your answer Guido. Unfortunately, as I wrote, php-json *is*
> >> installed, in the correct flavour. And pkg check -Bd succeeds
> >>
> > 
> > Is it being loaded?
> > 
> > Check for 'ext-20-json.ini' to be present in /usr/local/etc/php and have
> > correct content.
> > 
> 
> BTW, if you've not tried it a 'pkg install -f php72-json' is worth a try.

Can you check if you also upgraded the mod_php[57][16] module for
Apache?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: issue with sudo-1.8.23

[Lars Engels]

On Fri, May 04, 2018 at 07:56:10AM +0200, Lars Engels wrote:
> On Thu, May 03, 2018 at 09:15:14PM +0200, Walter Schwarzenfeld wrote:
> > In this version /var/run/sudo is changed to /run/sudo. If /var/run/sudo 
> > in the pkg-plist causes the problem if a directory /run exists.
> > 
> > But solved, fixed by maintainer.
> 
> Can we please revert this to /var/run?
> /run is some canker coming from systemd
> http://www.h-online.com/open/news/item/Linux-distributions-to-include-run-directory-1219006.htm.

Correction:

http://www.h-online.com/open/news/item/Linux-distributions-to-include-run-directory-1219006.html


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: issue with sudo-1.8.23

[Lars Engels]

On Thu, May 03, 2018 at 09:15:14PM +0200, Walter Schwarzenfeld wrote:
> In this version /var/run/sudo is changed to /run/sudo. If /var/run/sudo 
> in the pkg-plist causes the problem if a directory /run exists.
> 
> But solved, fixed by maintainer.

Can we please revert this to /var/run?
/run is some canker coming from systemd
http://www.h-online.com/open/news/item/Linux-distributions-to-include-run-directory-1219006.htm.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: icingaweb2-module-director-1.4.3

[Lars Engels]

On Wed, Feb 21, 2018 at 01:54:54PM +, Brandon McCorkle wrote:
> Hello,
> 
> I was wondering if you've come across this error in your testing I entered on 
> github?
> 
> https://github.com/Icinga/icingaweb2-module-director/issues/1400

Hi Brandon,

I've not seen this error yet, but I'm about to build a new Icinga 2
server including Web and Director, so I can take a look if I also
encounter the error.

Lars
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: icingaweb2-module-grafana-1.1.10 - urfonts needed?

[Lars Engels]

On Mon, Feb 05, 2018 at 05:03:05PM +, Brandon McCorkle wrote:
> Hello,
> 
>   I think urwfonts needs to be required as well for the module?  I
>   wasn't able to display the legend or labels till it was installed on
>   the graphs in Icinga.  I found a page out there mentioning it as a
>   requirement on Linux.

Thanks for the feedback, Brandon!

I think the right way to fix this is to have the Grafana port itself
depend on urwfonts. The official Grafana docs say:

  Server side image rendering
  
Server side image (png) rendering is a feature that is optional but very
useful when sharing visualizations, for example in alert notifications.

If the image is missing text make sure you have font packages installed.

yum install fontconfig
yum install freetype*
yum install urw-fonts

(http://docs.grafana.org/installation/rpm/)

Batek, what do you think of adding this?

Lars
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Procmail Vulnerabilities check

[Lars Engels]

On Sun, Dec 10, 2017 at 02:58:29PM -0800, Chris H wrote:
> OK I'm puzzled a bit. FreeBSD' motto has always been:
> FreeBSD
> The power to serve!
> 
> but many of the proposed, and recent changes/removals end up more like:
> FreeBSD
> I's castrated!
> 

So, then we should add a web server into our base! Apache? NGINX? Both?
But then, what about PHP? MySQL? PostgreSQL? We want to serve websites,
after all! Let's talk about fileservers. Samba! I could go on...

FreeBSD's power to serve slogan is about delivering the platform to
serve, not all possible server software. It just happens to have a mail
server in base because it always had, that's nothing that needs to be
kept forever. Probably 99% of the users don't use sendmail and the
remaining 1% know how to configure it, so installing them from ports is
a trivial thing for them.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Procmail Vulnerabilities check

[Lars Engels]

On Mon, Dec 11, 2017 at 09:09:39AM +1100, Dave Horsfall wrote:
> On Sun, 10 Dec 2017, Adam Weinberger wrote:
> 
> > DMA is a phenomenal program and is totally sufficient for a large 
> > percentage of our user-base. I wasn’t aware of the lack of .forward 
> > support, and I completely agree that that’s a very detrimental omission.
> 
> What about its spam filtering, such as /etc/mail/access and DNSBLs etc?
> 

pkg install $some_spam_filtering_software_of_your_choice

That's not what belongs into base.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: THANK YOU for flavors!

[Lars Engels]

On Thu, Dec 07, 2017 at 07:51:15AM -0500, Baho Utot wrote:
> 
> 
> On 12/07/17 04:30, Johan Hendriks wrote:
> > Op 07/12/2017 om 00:51 schreef Mel Pilgrim:
> >> In the midst of all the negative noise, I thought I'd post and say
> >> thank you for bring in this feature.  I've been chomping at the bit to
> >> try flavours out since I heard about them.  I started flavouring my
> >> company's internal Ports Tree extension the evening after it landed.
> >>
> >> Flavours are going to reduce 18 server role metaports to 3.
> >> ___
> >> freebsd-ports@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> > Do you have a web page where flavours are explained nicely for non
> > technical FreeBSD users so that they can also see the benefits of
> > flavour. I think it is a little odd that a big change like this is not
> > mentioned in any way on the front page of FreeBSD.
> > I really believe things are better this way albeit i did not read and
> > understand it in a whole. I also believe flavours are nice in a multi
> > server envirement and on the desktop.
> > The negative noice comes from people who USE FreeBSD on a single machine
> > or maybe 2 and are now confronted with there old habbits not working
> > anymore.
> > Give those people a walkthrough how they can run poudriere. Best without
> > out a server but just a oneliner they need to remeber for future
> > updates. They do not want to spend too much time reading and trying to
> > update there system.
> > If FreeBSD has done that i think that was lot less negative noice on the
> > channels.
> > 
> > Secondly I want to thank you all for the great product FreeBSD is and it
> > is a great product thanks to all the time people infest into FreeBSD.
> > So thank you all. But i also hope FreeBSD learns from these big changes.
> > If FreeBSD want a larger userbase, single machine users are there. And
> > they do not want to spend an hour reading through a poudriere man page.
> > They just want to type pgk upgrade, portmaster -d -a, or maybe poudriere
> > update ports for all that matters.
> > 
> 
> users also don't want to wake up to the fact that what worked a few days 
> ago not is working ie fetch/update port repo run synth and then get a " 
> What the fuck has just happened now" only to be put down by the so 
> called folks in charge here for even asking.

I think we all understood your point. Please come back if you have
something new to say.

Thank you!

-- 
Lars
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Flavors *COMPLETELY* break the port system (synth and poudriere are useless)

[Lars Engels]

On Thu, Dec 07, 2017 at 02:14:44PM +0100, Matthias Apitz wrote:
> Sometimes I want to add some port which was not built with poudriere
> directly compiling it on the target laptops and now, ofc, this
> compilation is missing some other packages the concrete port is
> depending on and it tries to build them too, even if they are already as
> built package in my local repo. If I'm not lazy, I watch the building
> and when it goes to look in Internet for some additional source to
> build, I interrupt the 'make install' and look if I could install it from
> the local repo. Boring. Can I direct the make process to look on the
> flight into the local repo to satisfy the needs of the compilation of
> the port?

You can in the port's directory you can run "pkg install -A `make missing`.
That should install missing dependencies as packages. Sometimes there
are no packages for a dependecy then you can skip those:
"pkg install -A `make missing | grep -v -e fooport -e barport`
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Flavors *COMPLETELY* break the port system (synth and poudriere are useless)

[Lars Engels]

On Tue, Dec 05, 2017 at 04:09:06PM -0800, Ultima wrote:
> I wonder if making a simple man page for general users would be wise and
> referencing the fully featured man page in it for more experienced users?
> It seems that many users want a simple route and the current man page is
> simply too intimidating for them to even consider attempting to use. A
> small how to at the bottom like how Bryan suggested would be helpful as
> well. (Maybe leave out the amount of characters used bit =)
> 
> Poudriere is a powerful beast and I personally love it because of this. I
> felt very overwhelmed when I first started using it but not everyone is
> willing to take the time to get up to speed.
> 

I like the idea. Maybe even add it to tldr[1]?
Web version at [2]

[1] https://github.com/tldr-pages/tldr
[2] https://tldr.ostera.io/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Flavors *COMPLETELY* break the port system (synth and poudriere are useless)

[Lars Engels]

On Tue, Dec 05, 2017 at 04:53:07AM -0500, Aryeh Friedman wrote:
> First some background (my typical use cases for ports):
> 
> 0. FreeBSD lilith 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321664: Fri Jul 28
> 23:35:18 EDT 2017 root@lilith:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> 1. Daily routine (current):
> 
>   cd /usr/src
>   svn update (from 11.1-RELEASE)
>   [make -DESTDIR=/ world kernel&& as needed]
> 
>   cd /usr/ports
>   svn update (from HEAD)
>   portmaster -ad
>   [reboot if any Xorg/xfce or stuff in rc.d got modified]
> 
> 2. I maintain devel/aegis (which as per Bug 219284 does not compile with
> anything greater then GCC 5 [I don't have time to figure out how to patch
> it is make it work {the upstream maintainer died a few years ago}]).
> 
> So what happens when I see UPDATING 20171130:
> 
> 1. I decide to try poudriere since it seems to what people are raving
> about.   What a 'ing confusing mess it is use After deciding it
> is over kill I go to option 2

[...]

What's wrong with [1]?

[1] 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-poudriere.html
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: firefox is pretty useless ...

[Lars Engels]

On Tue, Jul 11, 2017 at 09:45:10AM -0500, Bob Willcox wrote:
> On Wed, Jul 05, 2017 at 02:07:29AM -0400, DTD wrote:
> > if you use xfce. By definition it is not a problem that:
> > 
> >1) install a new copy of FreeBSD 10.3
> >2) pkg install xorg
> >3) pkg install xfce
> >4) pkg install firefox
> > 
> > installs a firefox package that does not run. The project seems to do a bit
> > better than this on Windows, but they (I think) have to in that 
> > environment. The
> > official answer to the above is:
> > 
> > --- Comment #1 from Jan Beich  ---
> > Partial upgrades i.e., mixing dependencies from different svn checkouts, 
> > dates
> > of "pkg install" or locking dependencies, are not supported. firefox will
> > refuse to build unless you upgrade sqlite3. Some version requirement are
> > specified in the port's Makefile
> > 
> >$ fgrep sqlite www/firefox/Makefile
> >sqlite3>=3.17.0:databases/sqlite3 \
> >${PYTHON_PKGNAMEPREFIX}sqlite3>0:databases/py-sqlite3 \
> > 
> > "pkg upgrade" may help you resolve this.
> > 
> > The only problem with this 'solution' is that upgrading sqlite requires a
> > cascading series of updates that breaks parts of xfce. Other than that no
> > problem here. So if you use twm firefox is your browser.
> > 
> > The next time I build a system I will try installing firefox first. I got 
> > here 
> > because I wanted to ungrade thunar (xfce's file manager). That upgrade broke
> > the version of firefox that was running (47.somethine). Chasing and fixing 
> > that 
> > chain eventually required a reinstall. Happily (for me) chrome works.
> 
> Hmm, what firefox port are you building/running? I'm running version 54.0
> (firefox-54.0.1_1,1) without any real issues (well, none at this point). I
> don't install or run xfce, but use the ctwm window manager (ctwm-4.0.0,1).
> Perhaps that's the difference.
> 
> I'm also running 10.3:
> FreeBSD luke.immure.com 10.3-STABLE FreeBSD 10.3-STABLE #3 r320754: Thu Jul  
> 6 15:13:13 CDT 2017 b...@luke.immure.com:/usr/obj/usr/src/sys/LUKE  amd64
> 
> As an asside, I recommend running v 54 of firefox in any event. The new
> thread support seems to have significantly improved its performance and
> stability for me (at least).

Yes, it feels much faster even on my venerable Thinkpad X200.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Audacity program appears to be dead

[Lars Engels]

On Sun, Jun 11, 2017 at 09:07:39AM -0700, Kevin Oberman wrote:
> On Sun, Jun 11, 2017 at 12:21 AM, Andrew Johnson 
> wrote:
> 
> > It builds nicely but Audacity has ceased working and produces the
> > following message:
> >
> > % audacity
> > Fatal Error: Mismatch between the program and library build versions
> > detected.
> > The library used 3.0 (wchar_t,compiler with C++ ABI 1002,wx
> > containers,compatible with 2.6,compatible with 2.8),
> > and your program used 3.0 (wchar_t,compiler with C++ ABI 1009,wx
> > containers,compatible with 2.6,compatible with 2.8).
> > Abort (core dumped)
> >
> >
> > == It is possible that this began with my first update that included an
> > edit in audacity/Makefile that was done back on 1/April.
> >
> > There's been a couple more updates in audacity during the past week but
> > the program continues to die with the same Fatal Error message.
> >
> > FreeBSD 10.3-STABLE FreeBSD 10.3-STABLE Sun Jun  4 18:11:09 2017
> > GENERIC  amd64
> >
> 
> I see the same error. I have nor run it is a while, so I have no idea when
> it started.
> 
> Have you notified the maintainer? That and opening a  bug report should be
> your first actions. You can find the maintainer (if any) by running "make
> maintainer" in the port's directory. In this case the maintainer is
> xxjack1...@gmail.com. A bug report can be filed at
> https://bugs.freebsd.org/bugzilla/.

See
http://www.bsdforen.de/threads/audacity-abi-fehler.33577/#post-292112
for a workaround / solution.


pgpTjJ2RqNACf.pgp
Description: PGP signature

Re: 4 issues

[Lars Engels]

On Wed, Apr 05, 2017 at 10:02:15PM -0600, The Doctor wrote:
> Failures on
> 
> devel/protobuf
> 
> misc/seabios
> 
> devel/openmpi
> 
> devel/kBuild
> 
> .
> 
> Are there others seeing failures?

Yes.


pgp1HWMxYGjtG.pgp
Description: PGP signature

Re: Best way to cause synth to ignore rebuilding of a port??

[Lars Engels]

On Wed, Mar 08, 2017 at 04:34:45PM +, Matthew Seaman wrote:
> On 2017/03/08 16:04, Bob Willcox wrote:
> > Note that I haven't tried ver 52 of firefox, but from what I've read it 
> > sounds
> > like all plugins/addons other than flash are no longer supported.
> 
> Make that: all *NPAPI* plugins other than Flash are now unsupported.
> That's stuff like the Java plugin or the OpenH264 Video Codec from Cisco
> (which I seem to have installed and can no-longer remember why.  Some
> sort of video conference thing a long time ago).

The OpenH264 plugin is shipped out of the box.


pgpfNTHFFgE7I.pgp
Description: PGP signature

Re: Lynis and lsof

[Lars Engels]

On Wed, Feb 15, 2017 at 10:41:28AM -0800, Kevin Oberman wrote:
> In that case, a note that lsof should be added to PORTS_MODULES on
> /etc/src.conf. lsof uses several undocumented kernel interfaces that are
> not stable (as they are not intended for external use). As a result, things
> can break if the kernel is updated without lsof also being updated.
> 
> PORTS_MODULES will take case of this for those who build the kernel from
> source. Things get rather messy if you use freebsd-update or packages
> though, as the packaging system sees no reason to make a new lsof package.
> I have no idea how to properly handle this. I simply always build lsof from
> source and lock it so 'pkg upgrade' won't touch it.

That's a good idea. The lsof port should have a pkg-message. I cc'ed
lsof's maintianer.


pgprQzQXQ9eEx.pgp
Description: PGP signature

Re: Lynis and lsof

[Lars Engels]

On Wed, Feb 15, 2017 at 11:33:09AM +0100, Andrea Venturoli wrote:
> Hello.
> 
> security/lynis seems to like having lsof available.
> However sysutils/lsof isn't listed as a dependency (whether optional or 
> not).
> 
> Would it be possible to add it, as a convenience?
> 
> I can provide the patch and/or file a bug report if you'll agree.
> 
>   bye & Thanks
>   av.

Andrea,

thanks for making me aware of this!
I just updated the port to 2.4.1 and added a runtime dependency on lsof.


Lars


pgpmtwBDdt_4a.pgp
Description: PGP signature

Re: Status of synth following expulsion of John Marino?

[Lars Engels]

On Wed, Feb 15, 2017 at 09:26:18AM +, Thomas Mueller wrote:
> Expulsion of John Marino was a shocker to me, caught me by surprise.
> 
> Now my question is what is the status of synth?
> 
> Should I switch from portmaster to synth?
> 
> If synth is deprecated or dropped, after I switch from portmaster to
> synth, then I have to switch back, and this would be a monster mess of
> extra work.
> 
> Not to be inflammatory here, just want to know where I/we stand and
> don't want to go too far off course updating my ports.
> 

Hi Tom,

John wants to keep on working on synth:

https://forums.freebsd.org/threads/59705/


pgprtJvQh3ySm.pgp
Description: PGP signature

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

[Lars Engels]

On Sat, Feb 11, 2017 at 10:15:41AM -0500, scratch65...@att.net wrote:
> On Sat, 11 Feb 2017 15:02:42 +0100, Kurt Jaeger 
> wrote:
> 
> >Hi!
> >
> >> And is the "keeping up with" working, Mark?  Are we regaining
> >> share from Linux?  No.   We're continuing to lose.  
> >
> >How do you measure that ?
> 
> Mostly I compare penetration of servers at web-hosting sites,
> availability of applications, particularly technical ones, and
> favorable mentions in the business and technical press. 
> 
> In all cases, FreeBSD is an afterthought, if it's mentioned at
> all.

Which is mostly because even my grandmother heard of Linux while FreeBSD
is mature and venerable but also mostly unknown even to IT people. It's not
a technical issue in the first place. We just suck at promoting FreeBSD.


pgpJBvhWZzWJc.pgp
Description: PGP signature

Re: Alternatives to rsync

[Lars Engels]

On Mon, Oct 17, 2016 at 09:46:31AM +1100, Greg 'groggy' Lehey wrote:
> On Friday, 14 October 2016 at  8:01:51 +0300, reko.turja--- via freebsd-ports 
> wrote:
> >
> > Greg, I've actually put some thought in making a local port of
> > rsync2. I've done some research on it and it seems to be fairly
> > usable and security patched still.
> 
> Even simpler, use the old version of the current rsync port.  Check
> out with svn, which (svn log) can also tell you when the last rsync 2
> version was.

rsync 2 has a different algorithm for checking if a file changed. The
new one is much faster.


pgp1PMubTZN7A.pgp
Description: PGP signature

Re: Google Code as an upstream is gone

[Lars Engels]

On Wed, Sep 14, 2016 at 10:19:18PM +0200, Mathieu Arnold wrote:
> Hello,
> 
> Google Code has been deprecated[1] since March 2015, and read-only since
> August 2015, giving time to software developers to move their
> development some place else. All the distribution files that still use
> solely googlecode.com as their source have been marked BROKEN today in
> r422140[2], as they are not fetchable.
> 
> Most software have moved to some other place (mostly on github), all you
> have to do is figure out where and update your ports accordingly.
> 
> 1: https://opensource.googleblog.com/2015/03/farewell-to-google-code.html
> 2: https://reviews.freebsd.org/rP422140

For the ports that are affected, can you please drop a short notice to
their maintainers? The phabricator page only shows them when you
manually click on "Load File" for every single port.


pgpH4PptZlieq.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Fri, Aug 26, 2016 at 09:34:32AM +0200, Raul wrote:
> 
> Lars Engels <lars.eng...@0x20.net> escribió:
> 
> >> still with 'libcli-1.9.6_1' installed
> >> removing ssl from USES let it run again
> > Please delete devel/libcli as a workaround.
> 
> Ok so, without libcli and with ssl:
> 
> []
> Performing sanity check of icinga2 configuration:  
> /usr/local/lib/icinga2/libcli.so: Undefined symbol  
> "_ZN6icinga14ConfigCompiler15CollectIncludesERNSt3__16vectorIPNS_10ExpressionENS1_9allocatorIS4_RKNS_6StringESB_SB_"
> []
> 
> with libcli and ssl:
> 
> []
> Performing sanity check of icinga2 configuration:  
> /usr/local/lib/icinga2/libremote.so: Undefined symbol  
> "_ZTVN6icinga18GetScopeExpressionE"
> []
> 
> with libcli and without ssl it works
> 

Meh, thanks!


Upstream now has a patch that I will try.


pgpOYH3_en2C8.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Thu, Aug 25, 2016 at 10:36:06PM +0200, Raul wrote:
> 
> Lars Engels <lars.eng...@0x20.net> escribió:
> 
> >> []
> >> # service icinga2 start
> >> Performing sanity check of icinga2 configuration:
> >> /usr/local/lib/icinga2/libcli.so: Undefined symbol
> >> "_ZN6icinga14ConfigCompiler15CollectIncludesERNSt3__16vectorIPNS_10ExpressionENS1_9allocatorIS4_RKNS_6StringESB_SB_"
> >> FAILED
> >> []
> >
> > This is now fixed.
> 
> I'm sorry to say it but not in my case (openssl-1.0.2_14)

:-/
> 
> []
> Performing sanity check of icinga2 configuration:  
> /usr/local/lib/icinga2/libremote.so: Undefined symbol  
> "_ZTVN6icinga18GetScopeExpressionE"
> []
> 
> still with 'libcli-1.9.6_1' installed
> removing ssl from USES let it run again
> 

Please delete devel/libcli as a workaround.


pgp6ZNyUifNEb.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Tue, Aug 23, 2016 at 09:08:48PM +0200, Raúl wrote:
> Hello!
> 
> grateful for the great work on the ports
> I don't remember last problem upgrading with them, Awesome!
> just a little setback
> 
> upgraded using portmaster, everything went apparently fine
> followed pkg-message to update schema db as I use mysql, also fine
> but when I try to start it I got:
> 
> []
> # service icinga2 start
> Performing sanity check of icinga2 configuration: 
> /usr/local/lib/icinga2/libcli.so: Undefined symbol 
> "_ZN6icinga14ConfigCompiler15CollectIncludesERNSt3__16vectorIPNS_10ExpressionENS1_9allocatorIS4_RKNS_6StringESB_SB_"
> FAILED
> []

This is now fixed.


pgpqBQ1o7ZdnS.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Wed, Aug 24, 2016 at 03:01:53PM +0200, Lars Engels wrote:
> On Wed, Aug 24, 2016 at 02:36:24PM +0200, Raul wrote:
> > 
> > Walter Schwarzenfeld <w.schwarzenf...@utanet.at> escribió:
> > 
> > ...
> > > if I remove USESßssl
> > 
> > I have openssl from ports.
> > 
> > Removed ssl from USES and yes, starts without problem.
> > Basic configuration here, logs are clean and icingaweb2 also likes it.
> 
> Strange. Thank you both for your observations!
> > 
> > Is this a PR case?.
> 
> No, I am the maintainer of the Icinga ports. :) 
> I'll try to find out why this happens.

I do not have *ssl from ports installed, so Icinga 2 uses the SSL
version from base. That's why it works for me.


pgpuA6Y7qyiz2.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Wed, Aug 24, 2016 at 02:36:24PM +0200, Raul wrote:
> 
> Walter Schwarzenfeld  escribió:
> 
> ...
> > if I remove USESßssl
> 
> I have openssl from ports.
> 
> Removed ssl from USES and yes, starts without problem.
> Basic configuration here, logs are clean and icingaweb2 also likes it.

Strange. Thank you both for your observations!
> 
> Is this a PR case?.

No, I am the maintainer of the Icinga ports. :) 
I'll try to find out why this happens.



pgpouJ5ZBbDWC.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Wed, Aug 24, 2016 at 12:17:00PM +0200, Raul wrote:
> 
> Walter Schwarzenfeld  escribió:
> 
> > This error message does not appear if I install devel/libcli.
> > But then:
> 
> Same here.

From your portmaster logfile:

===>   icinga2-2.5.1 depends on shared library: libconfig.so - found 
(/usr/local/lib/libconfig.so)

Can you try to-rebuild libconfig and then icinga2 again?



pgpYajDgxNGsc.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Tue, Aug 23, 2016 at 09:08:48PM +0200, Raúl wrote:
> Hello!
> 
> grateful for the great work on the ports
> I don't remember last problem upgrading with them, Awesome!
> just a little setback
> 
> upgraded using portmaster, everything went apparently fine
> followed pkg-message to update schema db as I use mysql, also fine
> but when I try to start it I got:
> 
> []
> # service icinga2 start
> Performing sanity check of icinga2 configuration: 
> /usr/local/lib/icinga2/libcli.so: Undefined symbol 
> "_ZN6icinga14ConfigCompiler15CollectIncludesERNSt3__16vectorIPNS_10ExpressionENS1_9allocatorIS4_RKNS_6StringESB_SB_"
> FAILED
> []
> 
> Not sure if I'm alone here.
> 
> this box runs 10.3-RELEASE-p6 and make.conf contains
> 
> []
> INSTALL_NODEBUG="YES"
> OPTIONS_UNSET=X11
> OPTIONS_UNSET=GUI
> BATCH=YES
> FORCE_PKG_REGISTER=yes
> WITH_PKGNG=yes
   you can savely remove this
> #WITH_OPENSSL_PORT=yes
> DEFAULT_VERSIONS+=  ssl=openssl
> []

Do you have the output from portmaster?


pgp3elJFpsNwk.pgp
Description: PGP signature

Re: [PATCH] net/relayd - configuration sanity checks à la nginx

[Lars Engels]

On Fri, May 20, 2016 at 02:18:14PM +0200, Damien Fleuriot wrote:
> Hello list,
> 
> 
> Find in the ticket below [1] a splendid patch to net/relayd's rc script so
> that it mimics nginx's behaviour and actually runs a sanity check on its
> configuration file prior to reload or restart.
> 
> In the current state of things, relayd performs no such check and may leave
> an administrator with a service outage.
> 
> 
> Could anyone please take the time to review and commit ?
> 

I did :)


pgp1B7nss3eJN.pgp
Description: PGP signature

Re: Anyone working on audio/mixxx

[Lars Engels]

On Wed, Mar 09, 2016 at 11:18:06PM +0100, Fernando Herrero Carrón wrote:
> Hi,
> 
> audio/mixxx (http://www.mixxx.org) has no maintainer. The project has been
> frozen on version 1.11 for a long time, but now 2.0.0 is out (actually
> december last year). Is anyone working on this port? I would like to help
> with upgrading it.

You could try to update the port yourself. It's usually not too hard and
the docs are excellent:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html

If you encounter any problems, feel free to ask here on ports@ and
someone will help you.

Lars


pgpbE5WLsCOqk.pgp
Description: PGP signature

Re: pkg upgrade issue

[Lars Engels]

On Mon, Feb 22, 2016 at 01:44:53AM -0800, Doug Hardie wrote:
> /etc/pkg/FreeBSD.conf contains (comments removed):
> 
> FreeBSD: {
>   url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
>   mirror_type: "srv",
>   signature_type: "fingerprints",
>   fingerprints: "/usr/share/keys/pkg",
>   enabled: yes
> }
> ~
> That appears to match with your entry below.
> 

But it doesn't match 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest//repo.txz

Do you have some other repository config in /usr/local/etc/pkg/repos?


pgpxUNzhmq5ja.pgp
Description: PGP signature

Re: pkg upgrade issue

[Lars Engels]

On Sun, Feb 21, 2016 at 10:03:14PM -0800, Doug Hardie wrote:
> On a FreeBSD 9.3 P33 system, I don't seem to be able to upgrade packages:
> 
> sermons# pkg upgrade
> Updating repository catalogue
> pkg: 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest//repo.txz:
>  File unavailable (e.g., file not found, no access)
> 

Most probably your repository config is wrong.
Try pkg+http://pkg.FreeBSD.org/${ABI}/latest 


pgpt29eTUYdNl.pgp
Description: PGP signature

Re: Can someone take a look at these PRs?

[Lars Engels]

On Wed, Feb 17, 2016 at 10:49:50PM +0100, Tobias Kortkamp wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206515 (www/dillo2,
> maintainer timeout)

Committed this one.

-- 
Lars


pgpBduc2SsSkT.pgp
Description: PGP signature

Re: graphics/qgis: commit of PR 206834

[Lars Engels]

On Tue, Feb 16, 2016 at 07:18:47AM +0100, Rainer Hurling wrote:
> Hi committers,
> 
> is someone willing to commit bug 206834 [1]?
> 
> It is about activating some features by new options in QGIS and it is 
> maintainer approved (by me).
> 
> Thanks in advance.
> 
> Best regards,
> Rainer Hurling
> 
> 
> [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206834

Hi Rainer,

the commit is in with a MFH request set.

Lars


pgp1JPN2Mt3Nm.pgp
Description: PGP signature

Re: Recent update of security/nettle broke security/keepassx2

[Lars Engels]

On Sun, Feb 14, 2016 at 11:56:25AM -0500, Jason Unovitch wrote:
> On Sun, Feb 14, 2016 at 11:48 AM, Lars Engels <lars.eng...@0x20.net> wrote:
> > On Fri, Feb 12, 2016 at 11:59:26AM -0500, Richard Kuhns wrote:
> >> Apologies; it was apparently libgcrypt, not nettle.
> >>
> >> On 02/12/16 09:29, Richard Kuhns wrote:
> >> > Hi all,
> >> >
> >> > After updating security/nettle, when I try to start keepassx2 I get:
> >> >
> >> > : rjk$~; keepassx
> >> > O j: Assertion `ctx->unused < 64' failed
> >> > (salsa20.c:400:salsa20_do_encrypt_stream)
> >> > Abort trap
> >> >
> >
> > I can confirm this. :-/
> 
> See https://bugs.FreeBSD.org/207042 and by extension
> https://bugs.FreeBSD.org/207107.

Thank you!


pgpmy7fUcCaS4.pgp
Description: PGP signature

Re: Recent update of security/nettle broke security/keepassx2

[Lars Engels]

On Fri, Feb 12, 2016 at 11:59:26AM -0500, Richard Kuhns wrote:
> Apologies; it was apparently libgcrypt, not nettle.
> 
> On 02/12/16 09:29, Richard Kuhns wrote:
> > Hi all,
> > 
> > After updating security/nettle, when I try to start keepassx2 I get:
> > 
> > : rjk$~; keepassx
> > O j: Assertion `ctx->unused < 64' failed
> > (salsa20.c:400:salsa20_do_encrypt_stream)
> > Abort trap
> > 

I can confirm this. :-/


pgpwfEx1HKVEE.pgp
Description: PGP signature

Re: Removing documentation

[Lars Engels]

On Wed, Feb 10, 2016 at 01:15:58PM -0800, Kevin Oberman wrote:
> On Mon, Feb 8, 2016 at 1:55 AM, John Marino  wrote:
> 
> > On 2/8/2016 10:30 AM, Mathias Picker wrote:
> > > Am Montag, den 08.02.2016, 08:35 +0100 schrieb John Marino:
> > > While I like the ideas of synth, and hoped I could use it to just build
> > > my 3-8 ports with modified options, on first look I found many things
> > > suggesting that it's not yet ready:
> > >
> > > - shows uninteresting eye candy instead of build
> >
> > Every single port has it's own build log with far more detail that a
> > source build provides (similar to poudriere)
> >
> > > - stops at every conf file version mismatch requiring me to start make
> > > config by hand, and then to re-run when it discovers the next mismatch.
> > > I mean, WTF?
> >
> > This is incorrect.  It lists *ALL* the configuration mismatches at once.
> >  This is actually a huge "pro" for synth; no other tool detects this
> > mismatches.  It is far worse to have cached options that do not match
> > the current port.  The port can be misbuilt and it's a major pain to
> > troubleshoot.  All build tools should be doing this.  Are you really
> > proposing that a tool build a port with a bad configuration file?  You
> > should be thanking Synth for alerting to a problem you obviously didn't
> > know you had.
> >
> > Also, once you fix it, then configuration problems are rare, they occur
> > when the port changes.
> >
> 
> OK. I have been playing with synth and I must say that I find it
> impressive. Not that I am ready to put it into  "production", but
> impressive, none the less. Maybe after a bit more testing and updating all
> ports after moving from 10 to 11 (which will not be too soon). Still, it is
> way better than poudriere for my limited purposes. I will certainly use it
> for that, even if I still use portmaster for my "development" system.
> 
> The stale configuration file issue has me a bit confused. The man page does
> not make it clear just what makes a config "stale". All of my ports are up
> to date as of 11:00 UTC this morning. As far as I know, all of the configs
> are "current", although the actual config run may have been for a much
> older version. "synth status shows 46 cases. I looked at one
> (sysutils/tmux) and the options listed by "make showconfig" are no
> different from those in the current Makefile, so I don't understand why
> they are stale.
> 
> I also have found at least one thing portmster can do that synth can't, but
> I expect pkg can, so I won't complain about it until I have tried using pkg
> to list all top-level ports (nothing depends on them) to use to re-install
> all ports. I could list all ports, it's just that this is a much longer
> list and portmaster did the job nicely with a simple example in the man
> page.

You need to uncomment the "leaf" alias in /usr/local/etc/pkg.conf

leaf  'query -e "%a == 0" "%n-%v"'

Then "pkg leaf" works like pkg_cutleaves(8) or the portmaster option.



pgp7fz14CNcgV.pgp
Description: PGP signature

Re: Removing documentation

[Lars Engels]

On Wed, Feb 10, 2016 at 10:40:44AM +0100, John Marino wrote:
> On 2/10/2016 10:37 AM, Lars Engels wrote:
> > On Tue, Feb 09, 2016 at 06:28:11PM +0100, John Marino wrote:
> >> On 2/9/2016 4:15 PM, Lars Engels wrote:
> >>>
> >>> root@fbsd01:~ # synth status
> >>> Querying system about current package installations.
> >>> Stand by, comparing installed packages against the ports tree.
> >>> Stand by, building pkg(8) first ... Failed!!  (Synth must exit)
> >>> Unfortunately, the system upgrade failed.
> >>
> >> Do you have a file called /var/log/synth/ports-mgmt___pkg.log ?  If so,
> >> does it provide clues?
> > 
> > So it's missing the proxy variables.
> > 
> 
> okay, so internally it's only installing resolv.conf in the builder
> environment.  Where are these proxy variables defined?  When I
> understand what's needed, I can give you a patch to try (if required)

resolv.conf doesn't work in that proxy scenario. DNS requests are
handled by the proxy server.

I set
HTTP_PROXY=http://proxyserver:; export HTTP_PROXY
http_proxy=http://proxyserver:; export http_proxy
ftp_proxy=http://proxyserver:; export FTP_PROXY
ftp_proxy=http://proxyserver:; export ftp_proxy

NO_PROXY="localhost,127.0.0.1,..."; export NO_PROXY

in /etc/profile and
:setenv=MAIL=/var/mail/$,BLOCKSIZE=K,HTTP_PROXY=http\c//proxyserver\c,FTP_PROXY=http\c//proxyserver\c,NO_PROXY=localhost\054127.0.0.1\054...:\

in /etc/login.conf



pgpKuGecm22cx.pgp
Description: PGP signature

Re: Removing documentation

[Lars Engels]

My rather short experience:

Synth configuration profile: LiveSystem
===
   [A] Ports directory/usr/ports
   [B] Packages directory /var/synth/live_packages
   [C] Distfiles directory/usr/ports/distfiles
   [D] Port options directory /var/db/ports
   [E] Build logs directory   /var/log/synth
   [F] Build base directory   /usr/obj/synth-live
   [G] System root directory  /
   [H] Compiler cache directory   disabled
   [I] Num. concurrent builders   6
   [J] Max. jobs per builder  4
   [K] Use tmpfs for work areatrue
   [L] Use tmpfs for /usr/local   true
   [M] Display using ncurses  true
   [N] Fetch prebuilt packagestrue

   [>]   Switch/create profiles
   [RET] Exit

Press key of selection:
root@fbsd01:~ # synth status
Querying system about current package installations.
Stand by, comparing installed packages against the ports tree.
Stand by, building pkg(8) first ... Failed!!  (Synth must exit)
Unfortunately, the system upgrade failed.
root@fbsd01:~ # uname -a
FreeBSD fbsd01 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14 01:32:46 
UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  
amd64
root@fbsd01:~ #


Not a very verbose message why it actually failed.
I need a proxy server to access the internet. Could this be the problem?
*_[pP][rR][oO][xX][yY] env vars are all set, though.


pgpCiYdOtis8M.pgp
Description: PGP signature

Re: Removing documentation

[Lars Engels]

On Wed, Feb 10, 2016 at 11:16:10AM +0100, John Marino wrote:
> On 2/10/2016 11:09 AM, Lars Engels wrote:
> > On Wed, Feb 10, 2016 at 10:40:44AM +0100, John Marino wrote:
> >> On 2/10/2016 10:37 AM, Lars Engels wrote:
> >>> On Tue, Feb 09, 2016 at 06:28:11PM +0100, John Marino wrote:
> >>>> On 2/9/2016 4:15 PM, Lars Engels wrote:
> >>>>>
> >>>>> root@fbsd01:~ # synth status
> >>>>> Querying system about current package installations.
> >>>>> Stand by, comparing installed packages against the ports tree.
> >>>>> Stand by, building pkg(8) first ... Failed!!  (Synth must exit)
> >>>>> Unfortunately, the system upgrade failed.
> >>>>
> >>>> Do you have a file called /var/log/synth/ports-mgmt___pkg.log ?  If so,
> >>>> does it provide clues?
> >>>
> >>> So it's missing the proxy variables.
> >>>
> >>
> >> okay, so internally it's only installing resolv.conf in the builder
> >> environment.  Where are these proxy variables defined?  When I
> >> understand what's needed, I can give you a patch to try (if required)
> > 
> > resolv.conf doesn't work in that proxy scenario. DNS requests are
> > handled by the proxy server.
> > 
> > I set
> > HTTP_PROXY=http://proxyserver:; export HTTP_PROXY
> > http_proxy=http://proxyserver:; export http_proxy
> > ftp_proxy=http://proxyserver:; export FTP_PROXY
> > ftp_proxy=http://proxyserver:; export ftp_proxy
> > 
> > NO_PROXY="localhost,127.0.0.1,..."; export NO_PROXY
> > 
> > in /etc/profile and
> > :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,HTTP_PROXY=http\c//proxyserver\c,FTP_PROXY=http\c//proxyserver\c,NO_PROXY=localhost\054127.0.0.1\054...:\
> > 
> > in /etc/login.conf
> > 
> 
> wow, okay, so basically these 4 variables would have to be present in
> the builder environment then?
> 
> I'll have to think about this.  I'll probably have to add a feature like
> a file like "/usr/local/etc/synth/-environment which will
> append user environment variables to the stock ones.
> 
> That's not exactly a 1-line change, but would that solve this issue?

That should work, yes.


pgpieLkC5c1Qe.pgp
Description: PGP signature

Re: Removing documentation

[Lars Engels]

On Tue, Feb 09, 2016 at 06:28:11PM +0100, John Marino wrote:
> On 2/9/2016 4:15 PM, Lars Engels wrote:
> > 
> > root@fbsd01:~ # synth status
> > Querying system about current package installations.
> > Stand by, comparing installed packages against the ports tree.
> > Stand by, building pkg(8) first ... Failed!!  (Synth must exit)
> > Unfortunately, the system upgrade failed.
> 
> Do you have a file called /var/log/synth/ports-mgmt___pkg.log ?  If so,
> does it provide clues?
> 
> John

=> pkg-1.6.3.tar.xz doesn't seem to exist in /distfiles/.
=> Attempting to fetch http://files.etoilebsd.net/pkg/pkg-1.6.3.tar.xz
fetch: http://files.etoilebsd.net/pkg/pkg-1.6.3.tar.xz: No address record
=> Attempting to fetch 
http://distcache.FreeBSD.org/local-distfiles/portmgr/pkg-1.6.3.tar.xz
fetch: http://distcache.FreeBSD.org/local-distfiles/portmgr/pkg-1.6.3.tar.xz: 
No address record
=> Attempting to fetch 
http://distcache.us-east.FreeBSD.org/local-distfiles/portmgr/pkg-1.6.3.tar.xz
fetch: 
http://distcache.us-east.FreeBSD.org/local-distfiles/portmgr/pkg-1.6.3.tar.xz: 
No address record
=> Attempting to fetch 
http://distcache.eu.FreeBSD.org/local-distfiles/portmgr/pkg-1.6.3.tar.xz
fetch: 
http://distcache.eu.FreeBSD.org/local-distfiles/portmgr/pkg-1.6.3.tar.xz: No 
address record
=> Attempting to fetch 
http://distcache.us-west.FreeBSD.org/local-distfiles/portmgr/pkg-1.6.3.tar.xz
fetch: 
http://distcache.us-west.FreeBSD.org/local-distfiles/portmgr/pkg-1.6.3.tar.xz: 
No address record
=> Attempting to fetch http://mirror.shatow.net/freebsd/pkg/pkg-1.6.3.tar.xz
fetch: http://mirror.shatow.net/freebsd/pkg/pkg-1.6.3.tar.xz: No address record
=> Attempting to fetch 
http://distcache.FreeBSD.org/ports-distfiles/pkg-1.6.3.tar.xz
fetch: http://distcache.FreeBSD.org/ports-distfiles/pkg-1.6.3.tar.xz: No 
address record
=> Couldn't fetch it - please try to retrieve this
=> port manually into /distfiles/ and try again.


So it's missing the proxy variables.


pgpb4YOGt1H9b.pgp
Description: PGP signature

Re: pkg : option to exclude some files from checksum ?

[Lars Engels]

On Mon, Nov 02, 2015 at 12:35:10AM +0100, Xavier wrote:
> Hi folks,
> 
> I noticed that some ports are complaining in daily check that a checksum 
> has changed.
> 
> Example : f-prot which checksums virus definitions, which obviously changes.
> 
> Is there some macro/option in Makefile to not checksum this file ?
> 
> I hope my point is clear enough...
> 
> TIA,
> 
> Xav

make -DNO_CHECKSUM should work


pgpjnxgal6Wn1.pgp
Description: PGP signature

security/vpnc: Redistribution is not allowed if linked against OpenSSL

[Lars Engels]

The vpnc port has the following:


LEGAL_TEXT= Redistribution is not allowed if linked against OpenSSL

.if ${PORT_OPTIONS:MSSL}
NO_PACKAGE= binary linked against OpenSSL must not be redistributed
CFLAGS+=-DOPENSSL_GPL_VIOLATION


Could anyone explain why this is an issue?



pgpDIGYBIe6Ou.pgp
Description: PGP signature

Re: distfiles cleaner

[Lars Engels]

On Mon, Oct 19, 2015 at 02:16:37PM +0200, Julian H. Stacey wrote:
> Hi ports@
> What is the modern equivalent of this obsolete stuff please ?
> 
> http://www.freebsd.org/cgi/man.cgi?query=portsclean=1=0=FreeBSD+9.0-RELEASE+and+Ports
>   portsclean --distclean
>   Clean out all the distfiles that are not referenced by any
>   port in the ports tree.
> 
> https://wiki.freebsd.org/portupgrade
>   Portupgrade (aka pkgtools)
>   last edited 2012-08-01

Try distviper from sysutils/bsdadminscripts.


pgpK3VsjPGPwL.pgp
Description: PGP signature

Re: icingaweb2 port ?

[Lars Engels]

On Mon, Oct 05, 2015 at 01:14:01PM +0200, Lars Engels wrote:
> On Sun, Oct 04, 2015 at 02:27:53PM +0200, Kurt Jaeger wrote:
> > Hi!
> > 
> > Is anyone working on an icingaweb2 port, now that they released 2.0.0 ?
> > 
> > https://github.com/Icinga/icingaweb2
> 
> Yes, I do.
> 
> Installing it manually already works, now I need to create a port.


Done: http://www.freshports.org/net-mgmt/icingaweb2


pgpDlKvoIlobI.pgp
Description: PGP signature

Re: icingaweb2 port ?

[Lars Engels]

On Sun, Oct 04, 2015 at 02:27:53PM +0200, Kurt Jaeger wrote:
> Hi!
> 
> Is anyone working on an icingaweb2 port, now that they released 2.0.0 ?
> 
> https://github.com/Icinga/icingaweb2

Yes, I do.

Installing it manually already works, now I need to create a port.


pgpgMMNoahUvQ.pgp
Description: PGP signature

Re: Icinga Web 2

[Lars Engels]

On Thu, Jul 30, 2015 at 10:48:44AM +0200, Kurt Jaeger wrote:
 Hi!
 
  We are deploying a new monitoring host and testing Icinga2, so far it
  looks good.
  
  Although Icinga Web 2 is not yet production ready I would like to know
  if there are plans to make a port for it in due time? I am trying it out
  now and apart from changing a myriad of paths it should not be difficult.
 
 If you can provide a rough draft of a port, I'd look into it.

I managed to run a previous snapshot from git. But it's a bit hackish,
not well documented and you need to change a bit of the paths. If time
permits I'll make a port of it.


pgps_TYjAwt7R.pgp
Description: PGP signature

Re: net-mgmt/pnp and nagios4

[Lars Engels]

On Fri, Jul 24, 2015 at 11:35:05AM +0200, Marko Cupać wrote:
 Hi,
 
 Is it possible to run pnp4nagios with nagios4 on FreeBSD? I see that
 their documentation page states that PNP4Nagios Broker Module
 npcdmod.o is not compatible with Nagios Core 4.x. However, I plan to
 use Bulk Mode with NPCD, or maybe even Bulk or Synchronous mode.
 Those should have no problem with nagios4.
 
 Building pnp in poudriere pulls in nagios, but I already have nagios4
 installed. Could pnp port be modified so that one can choose nagios
 version?

Hi Marko,

it would probably be possible to add a pnp-nagios4 slave port to pnp.
You could copy the pnp-icinga port and change the dependency to
net-mgmt/nagios4.

Lars


pgpPCtvSq92xr.pgp
Description: PGP signature

Re: FreeBSD Port: security/samhain

[Lars Engels]

On Wed, Jun 10, 2015 at 11:59:02AM +0200, Ryder Dain wrote:
 Hello,
 
 I’d really like to see this port returned to the tree, updated and
 packaged for use. It’s currently at 3.1.6, now builds with clang, and
 needs only a couple tweaks to make it FreeBSD-friendly.
 
 Is there any chance this can happen? I’d be more than happy to take
 over port maintenance.
 

Yes, please send patches for an updated version.


pgpVZVez74lHB.pgp
Description: PGP signature

Re: FreeBSD Port: icinga2-2.3.3_1

[Lars Engels]

On Thu, Apr 23, 2015 at 05:55:37PM +0200, Ruud Boon wrote:
 Hi!
 
 Thanks again for maintaining the freebsd ports. 
 Do you have any plans of upgrading to icinga2-2.4 soon?
 I got some issues that probably are fixed with the update.
 

Thanks for reminding me of the new version. I just updated the port.

Lars


pgpcd0t5Qz_dw.pgp
Description: PGP signature

Re: FreeBSD Port: pnp-icinga-0.6.21_1

[Lars Engels]

On Wed, Apr 22, 2015 at 01:53:53PM +0200, Ruud Boon wrote:
 Hi,
 
 I’m working with icinga2 and would like to add the pnp grapher.
 Is it possible to add an option for icinga2 support. Currently when
 installing it also install icinga1.
 
 All the best.
 Ruud

Currently, if you want to use Icinga's classic web interface with
Icinga 2, you also need Icinga 1.x port. Or don't you use this?

But I can take a look if it's possible for pnp to optionally depend on Icinga 2.


pgp4XG6b_Exue.pgp
Description: PGP signature

Re: Share your pkg aliases

[Lars Engels]

On Thu, Apr 02, 2015 at 10:19:10PM +0200, Baptiste Daroussin wrote:
 Hi,
 
 For pkg 1.5.0 we do plan to provide a default pkg.conf full of useful aliases,
 of course this is subjective, if you think you have added some useful aliases
 into your pkg.conf please share those so we can add them directly into the 
 next
 release.

myports: rquery -e '%m = l...@freebsd.org' %o,  # Show ports maintained by me
unmaintained: query -e '%m = po...@freebsd.org' %o, # Show unmaintained ports
csearch: search -U -c, # Search a port's short description



pgp6pV8wA4MSc.pgp
Description: PGP signature

Re: How does the Additional FreeBSD Contributors page work?

[Lars Engels]

On Thu, Jan 01, 2015 at 06:05:38PM -0800, Chris H wrote:
 Greetings, and Happy New Year!
 
 I was reading through the Porters Handbook today, and
 while reading 3.6. Submitting the New Port, I noticed
 the link at the end to 8. Additional FreeBSD Contributors
 (https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/contrib-additional.html).
 Being a maintainer of ~35 ports
 (https://www.freebsd.org/cgi/ports.cgi?query=portmaster@stype=maintainer)
 (tho ~5 are still waiting to be committed), I thought I'd see
 if I was listed. But discovered I wasn't. Given that maintainers
 of 1 port, and as little as 1mos. tenure are listed. I assumed that
 I must have misunderstood what the page represents.
 Would anyone be willing to clarify? Or am I simply blacklisted? ;)
 
 Thanks, and again, Happy New Year, to all!
 
 --Chris

Chris,

I added you to the list. Thanks a lot for your contributions.

Lars


pgppu7SiNXZrW.pgp
Description: PGP signature

Re: Giving Up Maintainership

[Lars Engels]

On Mon, Dec 15, 2014 at 11:22:17PM +0200, Raphael Kubo da Costa wrote:
 Guido Falsi madpi...@freebsd.org writes:
 
  Unluckily upgrading it will be a problem since new version depends on
  Python QT5 libraries.
 
  So I take a chance to ask:
 
  Is there any active work on creating ports for these?
 
  Who should I talk about this to?
 
 I don't think anyone is working on this at the moment. If you're willing
 to do it, please keep kde@ in the loop, as we maintain the existing
 PyQt4 ports and will probably end up either maintaining or touching the
 Qt5 ports a lot.

The PC-BSD guys (cc'ed) are switching their tools to Qt5.


pgp77R2STKLjA.pgp
Description: PGP signature

Re: graphics/qgis: bug 192605 obsolete after r372306

[Lars Engels]

On Sun, Nov 09, 2014 at 03:34:41PM +0100, Rainer Hurling wrote:
 After newest commits for graphics/qgis (r372306, followed by r372316,
 r372341), Bugzilla 192605 [1] should be obsolete.
 
 It would be nice, if someone with a commit bit could close it, thanks.
 
 
 [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192605

Done. Thanks for reporting this!


pgptvsVVU9Fzr.pgp
Description: PGP signature

Re: net-mgmt/icinga2: Icinga Web is not working: Error: Could not read object configuration data!

[Lars Engels]

On Fri, Oct 31, 2014 at 07:55:04PM +0100, O. Hartmann wrote:
 
 On CURRENT (most recent), I run net-mgmt/icinga2. Setup ran smooth, I also 
 set up the IDO
 for PostgreSQL. Checking whether icinga2 logs data to the PostgreSQL database 
 resulted
 positive.
 
 I try to install/configure a Web Interface a sdescribed in the Icinga2 docs. 
 IDO is a
 prerequiste for Icinga Web (I'm not using Icinga Web 2!).
 
 For that purpose, I installed net/mgmt/icinga (which contains the web 
 interface). I made
 the proper changes to /usr/local/etc/icinga/cgi.cfg as reported in this HowTo:
 http://lists.freebsd.org/pipermail/freebsd-ports/2014-June/093372.html. 
 Please see also
 https://forums.freebsd.org/threads/icinga2-network-monitoring.47106/. Via
 icinga2-enable-feature I also enabled all requested modules as described in 
 the Icinga2
 docs.
 
 So far. Having doen EXACTLY as suggested, I do not get any kind of 
 Webinterface. The web
 browser (Mozilla Firefox) reports always: Error: Could not read object 
 configuration data!
 
 There is something missing.
 
 Is someone using Icinga2 with the classical Web and has followed these 
 instructions and
 gets a different result?
 

Hi Oliver,

on a clean system, I just followed (my own) CFT instructions you also
used. I didn't encounter a problem. The only typo in the list is that
this:
cp /usr/local/share/examples/icinga/apache22/icinga.conf-sample 
/usr/local/etc/apache2/Includes/icinga.conf


 
should be apache22

Apart from this, there wasn't anything that didn't work. I used
pkg install apache22 icinga icinga2 though and didn't need to copy the
.cfg-sample file as the icinga port does this by itself now.

Can you please check all file and directory locations you changed in
icinga/cgi.cfg? I guess the status_file line leads to a non-existing
status.dat.


Please also CC me on any questions you have regarding icinga[2] and
FreeBSD as I maintain both ports.


Lars


pgpm7nd68Kf6M.pgp
Description: PGP signature

Re: PKG not quite ready for prime time

[Lars Engels]

On Sat, Oct 11, 2014 at 12:15:54AM +0200, Michelle Sullivan wrote:
 Mark Felder wrote:
  On Fri, Oct 10, 2014, at 14:47, Bryan Drewery wrote:

  On 10/10/2014 1:12 PM, scratch65...@att.net wrote:
  
  On Fri, 10 Oct 2014 12:57:42 -0500, Brian Drewery wrote:
 

  find /usr/share/keys/pkg -exec sha256 {} +
  
  No such file

  That's your problem. You are missing the signature fingerprints to
  compare against. As such Pkg is refusing to do anything to prevent MITM
  attacks.
 
  You are missing this:
  https://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc
 
  freebsd-update can provide it.
 
 
  
 
  Ahh, good point. This is better advice. Even if your system was
  supposedly fully up to date freebsd-update would detect this is missing
  and repair it as it was part of an SA. This is better advice than my
  manual creation method :-)

 
 Didn't on mine, I ran into the same problem - though it wasn't a show
 stopper for me as I was trying to use my own repo - which also failed
 using the docs...  and nothing in the debug gave any clues or additional
 information to the problem.  Fortunately, I can read/write code, so I
 fixed things myself.

Thanks for creating an PR.


pgpuYQLYjI3tQ.pgp
Description: PGP signature

Re: [package - 91amd64-quarterly] build failure mail

[Lars Engels]

On Wed, Sep 24, 2014 at 01:36:31PM +0300, Vitaly Magerya wrote:
 On 2014-09-24 08:37, pkg-fall...@freebsd.org wrote:
  You are receiving this mail as a port that you maintain
  is failing to build on the FreeBSD package build server.
  Please investigate the failure and submit a PR to fix
  build.
 
  Maintainer: vmage...@gmail.com
  Last committer: olg...@freebsd.org
  Ident:  $FreeBSD: branches/2014Q3/editors/wordgrinder/Makefile 
  357277 2014-06-10 07:39:01Z olgeni $
  Log URL:
  http://beefy2.isc.freebsd.org/data/91amd64-quarterly/2014-09-24_01h22m09s/logs/wordgrinder-0.3.3.log
  Build URL:  
  http://beefy2.isc.freebsd.org/build.html?mastername=91amd64-quarterlybuild=2014-09-24_01h22m09s
  Log:
 
   Building editors/wordgrinder
  build started at Wed Sep 24 05:37:27 UTC 2014
  port directory: /usr/ports/editors/wordgrinder
  building for: FreeBSD 91amd64-quarterly-job-16 9.1-RELEASE-p17 FreeBSD 
  9.1-RELEASE-p17 amd64
  maintained by: vmage...@gmail.com
  Makefile ident:  $FreeBSD: branches/2014Q3/editors/wordgrinder/Makefile 
  357277 2014-06-10 07:39:01Z olgeni $
  Poudriere version: 3.1-pre
  Host OSVERSION: 1100027
  Jail OSVERSION: 901000
 
 Folks, what should I do to not receive these messages? I've already 
 updated the port (long time ago), but I still get mail about build 
 failures in the quarterly branch.

You should nag the committer who committed the patch to fix the build
that he merges the change back to the quartely branch.


pgpnelH4RxxGE.pgp
Description: PGP signature

Re: [HEADSUP] pkg(8) is now the only package management tool

[Lars Engels]

On Wed, Sep 03, 2014 at 05:17:48PM +0200, Michelle Sullivan wrote:
 Mathieu Arnold wrote:
  +--On 3 septembre 2014 16:36:29 +0200 Michelle Sullivan
  miche...@sorbs.net wrote:
  | Mathieu Arnold wrote:
  | I still don't see what you have to say about what EOL mean, it's *End Of
  | Life* meaning after, it is dead, and won't exist any more.
  | 
  |   
  | Ahh so all those Windows XP servers are dead and don't work anymore...
 
  Not at all, but you don't update them any more.
 

 Actually you do, but it does nothing... just like freebsd-update on any
 EOL release...
 
 Microsoft didn't release a patch that would change the base system so
 you can no longer install any software... They just stopped providing
 updates, then later stopped providing security updates.

Same for FreeBSD and pkg_*. Stay with status quo, use pkg_* with the
last tagged version of the ports tree that works with pkg_* or switch to
pkg and be happy like the rest of us.



pgpb1nE97LRTd.pgp
Description: PGP signature

Re: chromium iconify-resurrect

[Lars Engels]

On Mon, Sep 01, 2014 at 06:02:53PM -0700, Russell L. Carter wrote:
 Greetings,
 
 I am curious if this is a problem that anyone else is seeing.
 chromium 37.0.2062.94, current r269700M
 
 Start up chromium, then immediately iconify it. Then try bringing it
 back again.  All I get (after a delay of several seconds) is a white
 canvas in the correct size.  Chromium does respond to window manager
 commands (fvwm close, no destroy needed, in my case).
 

Yup, same on PC-BSD.


pgpYwqmO1SHjE.pgp
Description: PGP signature

Re: pkg-1.3 comment and questions

[Lars Engels]

On Fri, Jul 25, 2014 at 08:57:00AM -0400, Richard Kuhns wrote:
 Hello,
 
 First the comment: I've also noticed that checking for out-of-date
 packages now takes 3 to 5 times longer than it used to. I've never used
 an INDEX before, as it didn't seem to offer me anything I needed/wanted.
 Is it considered (almost) a requirement now?
 
 Second, how do I delete a single package that has dependencies without
 deleting the dependencies? For example, UPDATING says
 
 libevent1 has been replaced by libevent2 via the compatibility layer.
   All applications that used libevent1 must be rebuilt.
 
   Please remove libevent1 before upgrading, by running:
 pkg delete libevent
 
 If I try 'pkg delete libevent', pkg wants to delete no only libevent but
 every other package that requires libevent. It's as if the recursive
 flag is now on by default and I can't find any way to turn it off. 'pkg
 help delete' doesn't offer anything.
 
 I don't have a pkg.conf file installed anywhere (that I can find, anyway).
 

pkg delete -f libevent

will only delete the libevent package.


pgpsZlPyrDWWl.pgp
Description: PGP signature

[PATCHES] Extend service(8) and rc(8) was: Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

[Lars Engels]

On Fri, Jul 18, 2014 at 12:10:34PM -0700, Adrian Chadd wrote:
 Hi!
 
 
 On 18 July 2014 07:28, Lars Engels lars.eng...@0x20.net wrote:
  On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
  On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
 
   On 07/17/14 13:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
   wrote:
Hi!
   
3) The binary packages need to work out of the box
4) .. which means, when you do things like pkg install apache, it
can't just be installed and not be enabled, because that's a bit of a
problem;
   
   
No. Please NEVER do that! The user must be able to edit the files and
start the service by himself.
   
Cool, so what's the single line command needed to type in to start a
given package service?
  
   Aren't sysrc(8) and service(8) for this kind of stuff?
  
 
  They sure are.
 
  Well, pkg install $service ; sysrc ${service}_enable=YES would do.
  Although some services have different names than the packge, which is sort
  of annoying.
 
  I hacked up a solution for service(8):
 
  http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch
 
  The patch adds the following directives to service(8):
 
  enable: Grabs an rc script's rcvar value and runs sysrc foo_enable=YES
  disable: The opposite of enable
  rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
sysrc -x foo_enable
 
  The nice thing about is that you can use one of the new directives on
  one line with the old ones, as long as the new are the first argument:
 
  # service syslogd enable
  # service apache24 disable stop
  # service apache24 rcdelete stop
  # service nginx enable start
 
 
  So after installing a package, to start and enable a daemon permanently
  all you have to run is
  # service foo enable start
 
  Lars
 
  P.S.: Thansk to Devin for his hard work on sysrc!
 
 Having a way for sysrc and service to know what particular options and
 services are exposed by a given package or installed thing would be
 nice. Right now the namespace is very flat and it's not obvious in all
 instances what needs to happen to make it useful and what the options
 are.
 
 Oh, hm, I'd like to know what options there are for controlling the
 installed apache24 package, let's see...
 
 I remember IRIX having that command to list services, stop them and
 start them, configure them enabled and disabled. Solaris grew
 something like that with Solaris 10 and after the initial learning
 curve it was great. Hving something like that would be 100% awesome.

I've updated the patch and extended it a little:

https://phabric.freebsd.org/D451

It can now print the rc options for a service.
It needs however to have the options listed as comments between the
KEYWORDS section and the sourcing of /etc/rc.subr.


And I've made some changes to rc.subr itself:

https://phabric.freebsd.org/D452

So now you can use

# service sshd describe
Secure Shell Daemon

and

# service sshd extracommands
configtest keygen reload


Sorry for the mess in phabricator's SUMMARY. I will learn the markup
syntax later...


Lars


pgpwjm22pgrSF.pgp
Description: PGP signature

Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

[Lars Engels]

On Thu, Jul 17, 2014 at 01:00:03PM -0700, Adrian Chadd wrote:
 On 17 July 2014 12:57, Andreas Nilsson andrn...@gmail.com wrote:
 
 
 
  On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd adr...@freebsd.org wrote:
 
  Hi!
 
  3) The binary packages need to work out of the box
  4) .. which means, when you do things like pkg install apache, it
  can't just be installed and not be enabled, because that's a bit of a
  problem;
 
  I disagree on this. For network services on linux ( apart from ssh ), I want
  that started very seldom. But I do want the package installed so that when I
  need it, it is there. Having it autostart as part of being installed is
  breaking KISS and in some way unix philosophy: I asked for something to be
  installed, not installed and autostarted.
 
 That's cool. We can disagree on that. But the fact that you have to
 edit a file to enable things and hope you get the right start entry in
 /etc/rc.conf or /usr/local/etc/rc.conf, or wherever you put it is, is
 a pain.

No, Sir! No need to edit anything:

root@testjail: # pkg install apache24
Updating repository catalogue
The following 5 packages will be installed:

Installing pcre: 8.33
Installing gdbm: 1.10
Installing db42: 4.2.52_5
Installing apr: 1.4.8.1.5.3
Installing apache24: 2.4.6_1

The installation will require 47 MB more space

5 MB to be downloaded

Proceed with installing packages [y/N]: y
gdbm-1.10.txz 100%   83KB  83.2KB/s  83.2KB/s   00:00
db42-4.2.52_5.txz 100% 1457KB   1.4MB/s   1.4MB/s   00:00
apr-1.4.8.1.5.3.txz 100%  390KB 389.5KB/s 389.5KB/s   00:00
apache24-2.4.6_1.txz 100% 3649KB   3.6MB/s   3.6MB/s   00:00
Checking integrity... done
[1/5] Installing pcre-8.33... done
[2/5] Installing gdbm-1.10... done
[3/5] Installing db42-4.2.52_5... done
[4/5] Installing apr-1.4.8.1.5.3... done
[5/5] Installing apache24-2.4.6_1...=== Creating users and/or groups.
Using existing group 'www'.
Using existing user 'www'.
/usr/local/share/examples/apache24/httpd.conf -
/usr/local/etc/apache24/httpd.conf
 done
To run apache www server from startup, add apache24_enable=yes
in your /etc/rc.conf. Extra options can be found in startup script.

Your hostname must be resolvable using at least 1 mechanism in
/etc/nsswitch.conf typically DNS or /etc/hosts or apache might
have issues starting depending on the modules you are using.

root@testjail: # sysrc apache24_enable=yes
apache24_enable:  - yes

root@testjail: # service apache24 start
Performing sanity check on apache24 configuration:
AH00557: httpd: apr_sockaddr_info_get() failed for testjail
AH00558: httpd: Could not reliably determine the server's fully
qualified domain name, using 127.0.0.1. Set the 'ServerName' directive
globally to suppress this message
Syntax OK
Starting apache24.
AH00557: httpd: apr_sockaddr_info_get() failed for testjail
AH00558: httpd: Could not reliably determine the server's fully
qualified domain name, using 127.0.0.1. Set the 'ServerName' directive
globally to suppress this message
root@testjail: #


That's 3 commands to enter. Admittedly 2 more than on some OS that
blindly starts any service you install, but 2 steps more logical and
even a newbie can do this.

What could be done is that pkg looks for rc scripts in a package,
extracts the enable line and prints a message how to enable the script /
daemon permanently.

Like: 
- To start the script apache24 once run service apache24 onestart.
- To start the script apache24 at boot time run sysrc apache24_enable=yes
- The script apache24 has the following optional settings for /etc/rc.conf:
apache24_profiles (str): Set to  by default.
 Define your profiles here.
apache24limits_enable (bool):Set to NO by default.
Set it to yes to run `limits $limits_args`
just before apache starts.
apache24_flags (str):Set to  by default.
Extra flags passed to start command.
apache24limits_args (str):   Default to -e -C daemon
Arguments of pre-start limits run.
apache24_http_accept_enable (bool): Set to NO by default.
Set to yes to check for accf_http kernel
module on start up and load if not loaded.
apache24_fib (str): Set an altered default network view for apache





pgpIEpFVOIfJI.pgp
Description: PGP signature

Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

[Lars Engels]

On Fri, Jul 18, 2014 at 02:10:25PM +0200, Lars Engels wrote:
 On Thu, Jul 17, 2014 at 01:00:03PM -0700, Adrian Chadd wrote:
  On 17 July 2014 12:57, Andreas Nilsson andrn...@gmail.com wrote:
  
  
  
   On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd adr...@freebsd.org wrote:
  
   Hi!
  
   3) The binary packages need to work out of the box
   4) .. which means, when you do things like pkg install apache, it
   can't just be installed and not be enabled, because that's a bit of a
   problem;
  
   I disagree on this. For network services on linux ( apart from ssh ), I 
   want
   that started very seldom. But I do want the package installed so that 
   when I
   need it, it is there. Having it autostart as part of being installed is
   breaking KISS and in some way unix philosophy: I asked for something to be
   installed, not installed and autostarted.
  
  That's cool. We can disagree on that. But the fact that you have to
  edit a file to enable things and hope you get the right start entry in
  /etc/rc.conf or /usr/local/etc/rc.conf, or wherever you put it is, is
  a pain.
 
 No, Sir! No need to edit anything:
 
 root@testjail: # pkg install apache24
 Updating repository catalogue
 The following 5 packages will be installed:
 
 Installing pcre: 8.33
 Installing gdbm: 1.10
 Installing db42: 4.2.52_5
 Installing apr: 1.4.8.1.5.3
 Installing apache24: 2.4.6_1
 
 The installation will require 47 MB more space
 
 5 MB to be downloaded
 
 Proceed with installing packages [y/N]: y
 gdbm-1.10.txz 100%   83KB  83.2KB/s  83.2KB/s   00:00
 db42-4.2.52_5.txz 100% 1457KB   1.4MB/s   1.4MB/s   00:00
 apr-1.4.8.1.5.3.txz 100%  390KB 389.5KB/s 389.5KB/s   00:00
 apache24-2.4.6_1.txz 100% 3649KB   3.6MB/s   3.6MB/s   00:00
 Checking integrity... done
 [1/5] Installing pcre-8.33... done
 [2/5] Installing gdbm-1.10... done
 [3/5] Installing db42-4.2.52_5... done
 [4/5] Installing apr-1.4.8.1.5.3... done
 [5/5] Installing apache24-2.4.6_1...=== Creating users and/or groups.
 Using existing group 'www'.
 Using existing user 'www'.
 /usr/local/share/examples/apache24/httpd.conf -
 /usr/local/etc/apache24/httpd.conf
  done
 To run apache www server from startup, add apache24_enable=yes
 in your /etc/rc.conf. Extra options can be found in startup script.
 
 Your hostname must be resolvable using at least 1 mechanism in
 /etc/nsswitch.conf typically DNS or /etc/hosts or apache might
 have issues starting depending on the modules you are using.
 
 root@testjail: # sysrc apache24_enable=yes
 apache24_enable:  - yes
 
 root@testjail: # service apache24 start
 Performing sanity check on apache24 configuration:
 AH00557: httpd: apr_sockaddr_info_get() failed for testjail
 AH00558: httpd: Could not reliably determine the server's fully
 qualified domain name, using 127.0.0.1. Set the 'ServerName' directive
 globally to suppress this message
 Syntax OK
 Starting apache24.
 AH00557: httpd: apr_sockaddr_info_get() failed for testjail
 AH00558: httpd: Could not reliably determine the server's fully
 qualified domain name, using 127.0.0.1. Set the 'ServerName' directive
 globally to suppress this message
 root@testjail: #
 
 
 That's 3 commands to enter. Admittedly 2 more than on some OS that
 blindly starts any service you install, but 2 steps more logical and
 even a newbie can do this.
 
 What could be done is that pkg looks for rc scripts in a package,
 extracts the enable line and prints a message how to enable the script /
 daemon permanently.
 
 Like: 
 - To start the script apache24 once run service apache24 onestart.
 - To start the script apache24 at boot time run sysrc apache24_enable=yes
 - The script apache24 has the following optional settings for /etc/rc.conf:
 apache24_profiles (str): Set to  by default.
  Define your profiles here.
 apache24limits_enable (bool):Set to NO by default.
 Set it to yes to run `limits $limits_args`
 just before apache starts.
 apache24_flags (str):Set to  by default.
 Extra flags passed to start command.
 apache24limits_args (str):   Default to -e -C daemon
 Arguments of pre-start limits run.
 apache24_http_accept_enable (bool): Set to NO by default.
 Set to yes to check for accf_http kernel
 module on start up and load if not loaded.
 apache24_fib (str): Set an altered default network view for apache
 
 
 

Sorry for no reading the whole thread first. This was already suggested
in another part of the thread.


pgp5bG5Xyw8GZ.pgp
Description: PGP signature

Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

[Lars Engels]

On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
 On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
 
  On 07/17/14 13:12, Adrian Chadd wrote:
   On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
   On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
  wrote:
   Hi!
  
   3) The binary packages need to work out of the box
   4) .. which means, when you do things like pkg install apache, it
   can't just be installed and not be enabled, because that's a bit of a
   problem;
  
  
   No. Please NEVER do that! The user must be able to edit the files and
   start the service by himself.
  
   Cool, so what's the single line command needed to type in to start a
   given package service?
 
  Aren't sysrc(8) and service(8) for this kind of stuff?
 
 
 They sure are.
 
 Well, pkg install $service ; sysrc ${service}_enable=YES would do.
 Although some services have different names than the packge, which is sort
 of annoying.

I hacked up a solution for service(8):

http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch

The patch adds the following directives to service(8):

enable: Grabs an rc script's rcvar value and runs sysrc foo_enable=YES
disable: The opposite of enable
rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
  sysrc -x foo_enable

The nice thing about is that you can use one of the new directives on
one line with the old ones, as long as the new are the first argument:

# service syslogd enable
# service apache24 disable stop
# service apache24 rcdelete stop
# service nginx enable start


So after installing a package, to start and enable a daemon permanently
all you have to run is
# service foo enable start

Lars

P.S.: Thansk to Devin for his hard work on sysrc!


pgpXcgD203Myq.pgp
Description: PGP signature

Re: pkg-devel goes mad on 11-CURRENT with last repository update

[Lars Engels]

On Thu, Jul 17, 2014 at 12:11:19AM +0400, Lev Serebryakov wrote:
 Hello, FreeBSD.
 
  I'm using 11-CURRENT (amd64) on my laptop and trying hard to use binary
  packages with pkg-devel. But attempt to upgrade installed packages goes
  crazy today. It trys to install ALL versions of gcc, ALL versions of
  subversion and many other unneeded packages!
 
  I'm using latest pkg-devel 1.3.0.r1.
 
  List of packages installed (pkg info output) and pkg upgrade output are
  attached.
 
  (THREES installed versions of gcc is another sad story, of course).
 

Please try pkg-devel RC2. It should be fixed there.


pgpoiU4DZY3cB.pgp
Description: PGP signature

Re: bugzilla cleanup for sysinstall PR's

[Lars Engels]

On Sat, Jul 12, 2014 at 07:40:32AM -0400, Fbsd8 wrote:
 FYI, There are over 100 PR's with sysinstall in the pr title.
 sysinstall is officially dead and will not be receiving any
 fixs since bsdinstall replaced it. Time is due to remove all those
 pr's targeted at sysinstall.

Wrong mailing list. 


pgpT2IVDu8dWF.pgp
Description: PGP signature

Re: [CFT]: net-mgmt/icinga2

[Lars Engels]

On Sat, Jun 28, 2014 at 09:49:52PM -0600, Warren Block wrote:
 I've just been setting this up, and had a question and a couple of notes.
 
 Originally, I just installed icinga2.  The icinga2 port does not depend on 
 icinga, but appears to need it.  Is this really a dependency, or are the 
 two ports meant to be separate?

Icinga 2 itself doesn't need a web interface to work. The Icinga 1 port
includes the classic (cgi) web interface which can be used for Icinga 2,
so it's not a hard dependency.
When I find the time I'm going to create a new port for the classic web
interface.

 
 The icinga.conf-sample does not appear to be installed anywhere by the 
 current port.  It can be found in the staging directory,
 stage/usr/local/share/examples/icinga/apache22/.

It's installed by the Icinga 1 port. From pkg-plist:
%%PORTEXAMPLESEXAMPLESDIR%%/apache22/icinga.conf-sample

Maybe you have NO_PORTEXAMPLES set?

 
 The embedded documentation shown is for 1.11, and it's not clear whether 
 the Javascript client for icinga 2 is available, or whether it will make 
 the CGI interface unnecessary.  Actually, given the config file, and both 
 versions installed, the older version might be the one that is running.  I 
 have not experimented with it much yet.

Yes, the classic web interface still links to the Icinga 1 docs. I think
this should be fixed upstream, so I created a bug report.

Apart from the Classic UI there are two other interfaces for Icinga.
Icinga Web and Icinga Web 2.x. The former isn't too good and will be
deprecated eventually.  The latter is much more straight forward but
isn't ready for production yet.

 
 Thank you for your work on this!

Thanks for testing it. :)


pgpSIjRqmLUtj.pgp
Description: PGP signature

Re: [CFT]: net-mgmt/icinga2

[Lars Engels]

On Thu, Jun 19, 2014 at 03:51:20PM +0200, Marco Steinbach wrote:
 Lars Engels wrote on 18.06.2014 16:36:
  Hey folks,
  
  I proudly present a CFT for the shiny new monitoring software Icinga 2,
  a completely rewritten, multi-threaded, flexible and scalable successor
  to Icinga 1.
  Although it is completely new it still can run with your Icinga / Nagios
  plugins and addons.
  
  To use Icinga 2 with the Classic Web interface do the following:
  
  % Download and extract shar file 
  
  # fetch -o /tmp http://bsd-geek.de/FreeBSD/icinga2_1.shar
  # cd /usr/ports  sh /tmp/icinga2_1.shar
  
  % Install net-mgmt/icinga2
  % Install net-mgmt/icinga 
  % Install www/apache22
  
  % Configure Apache and Icinga Classic Web
  
  # cp /usr/local/share/examples/icinga/apache22/icinga.conf-sample 
  /usr/local/etc/apache2/Includes/icinga.conf
  # cp /usr/local/etc/icinga/cgi.cfg-sample /usr/local/etc/icinga/cgi.cfg
  
  % Make changes to cgi.cfg:
  
  standalone_installation=1
  object_cache_file=/var/cache/icinga2/objects.cache
  status_file=/var/cache/icinga2/status.dat
  command_file=/var/run/icinga2/cmd/icinga2.cmd
  log_file=/var/log/icinga2/compat/icinga.log
  log_archive_path=/var/log/icinga2/compat/archives
  
  % Create a basic auth file 
  
  # htpasswd -c -s /usr/local/etc/icinga/htpasswd.users icingaadmin
   (enter some password)
  
  % Enable Apache and Icinga 2
  
  # sysrc apache22_enable=YES
  # sysrc icinga2_enable=YES
  
  % Enable additional Icinga 2 features
  
  # icinga2-enable-feature checker command compatlog icingastatus livestatus 
  mainlog notification statusdata
  
  % Start Apache and Icinga 2
  
  # service apache22 start
  # service icinga2 start
  
  % Check /var/log/icinga2/icinga2.log and error.log for any errors
  % Browse to http://localhost/icinga
  % Log in as icingaadmin
  
  % Read http://docs.icinga.org/icinga2/latest/doc/module/icinga2/toc
  
  % (Hopefully) have fun!
  
  Please share your experience with me. :)
 
 # uname -a
 FreeBSD jail008.c0c0.intra 9.3-BETA2 FreeBSD 9.3-BETA2 #0 r267346:
 # which flex
 /usr/bin/flex
 # flex --version
 flex version 2.5.4
 
 # make
 [...]
 -- Found FLEX: /usr/bin/flex version 2.5.4 (Required is at least version 
 2.5.31)
 [...]
 [  3%] [FLEX][class_lexer] Building scanner with flex /usr/bin/flex 
 version 2.5.4
 class_lexer.ll, line 92: unrecognized %option: reentrant
 class_lexer.ll, line 93: unrecognized %option: bison-bridge
 class_lexer.ll, line 94: unrecognized %option: unistd
 *** [tools/mkclass/class_lexer.cc] Error code 1
 1 error
 *** [tools/mkclass/CMakeFiles/mkclass.dir/all] Error code 2
 [  3%] Built target execvpe
 1 error
 *** [all] Error code 2
 1 error
 
 
 Depending on flex from ports (flex-2.5.39_1) fixes this from me.
 
 .if ${OSVERSION}  133
 BUILD_DEPENDS+= flex=2.5.31:${PORTSDIR}/textproc/flex
 CMAKE_ARGS+=-DFLEX_EXECUTABLE:STRING=${LOCALBASE}/bin/flex
 CXXFLAGS+=  -I${LOCALBASE}/include/flex
 .endif
 
 MfG CoCo
 

Good catch, thanks for this!

I just updated the shar file and also added WWW to pkg-descr.

Lars




pgpeH9GtAjAX4.pgp
Description: PGP signature

Re: [CFT]: net-mgmt/icinga2

[Lars Engels]

On Thu, Jun 19, 2014 at 05:27:29PM +0200, Marco Steinbach wrote:
 Lars Engels wrote on 19.06.2014 16:08:
  On Thu, Jun 19, 2014 at 03:51:20PM +0200, Marco Steinbach wrote:
  Lars Engels wrote on 18.06.2014 16:36:
  Hey folks,
 
 [Icinga2 port, patch]
 
  
  Good catch, thanks for this!
  
  I just updated the shar file and also added WWW to pkg-descr.
  
 
 This patch tries to make Icinga2 only link to what database client the 
 user selected, instead of linking to whatever database client cmake 
 stumbles over in addition to the users selection.
 
 MfG CoCo
 

Perfect, thank you! I'll try to get this patch upstream.
Meanwhile I updated the sharfile.


pgpyiEpuGyv5D.pgp
Description: PGP signature

[CFT]: net-mgmt/icinga2

[Lars Engels]

Hey folks,

I proudly present a CFT for the shiny new monitoring software Icinga 2,
a completely rewritten, multi-threaded, flexible and scalable successor
to Icinga 1.
Although it is completely new it still can run with your Icinga / Nagios
plugins and addons.

To use Icinga 2 with the Classic Web interface do the following:

% Download and extract shar file 

# fetch -o /tmp http://bsd-geek.de/FreeBSD/icinga2_1.shar
# cd /usr/ports  sh /tmp/icinga2_1.shar

% Install net-mgmt/icinga2
% Install net-mgmt/icinga 
% Install www/apache22

% Configure Apache and Icinga Classic Web

# cp /usr/local/share/examples/icinga/apache22/icinga.conf-sample 
/usr/local/etc/apache2/Includes/icinga.conf
# cp /usr/local/etc/icinga/cgi.cfg-sample /usr/local/etc/icinga/cgi.cfg

% Make changes to cgi.cfg:

standalone_installation=1
object_cache_file=/var/cache/icinga2/objects.cache
status_file=/var/cache/icinga2/status.dat
command_file=/var/run/icinga2/cmd/icinga2.cmd
log_file=/var/log/icinga2/compat/icinga.log
log_archive_path=/var/log/icinga2/compat/archives

% Create a basic auth file 

# htpasswd -c -s /usr/local/etc/icinga/htpasswd.users icingaadmin
 (enter some password)

% Enable Apache and Icinga 2

# sysrc apache22_enable=YES
# sysrc icinga2_enable=YES

% Enable additional Icinga 2 features

# icinga2-enable-feature checker command compatlog icingastatus livestatus 
mainlog notification statusdata

% Start Apache and Icinga 2

# service apache22 start
# service icinga2 start

% Check /var/log/icinga2/icinga2.log and error.log for any errors
% Browse to http://localhost/icinga
% Log in as icingaadmin

% Read http://docs.icinga.org/icinga2/latest/doc/module/icinga2/toc

% (Hopefully) have fun!

Please share your experience with me. :)


Lars


pgpX0JR7eLs6z.pgp
Description: PGP signature

Re: [CFT]: net-mgmt/icinga2

[Lars Engels]

On Wed, Jun 18, 2014 at 09:10:46PM +0200, Kurt Jaeger wrote:
 Hi!
 
   Although it is completely new it still can run with your Icinga / Nagios
   plugins and addons.
   
   To use Icinga 2 with the Classic Web interface do the following:
  
  Is it able to run standalone, without net-mgmt/icinga ?
  Or is that not recommended ?
 
 The reason I'm asking: The is a new deployment and I want to
 start without legacy setups from the start.

Icinga 2 doesn't depend on Icinga 1 but the net-mgmt/icinga port
includes the Classic Web interface. I plan to separate it, so you don't
need the icinga1 port. But it doesn't hurt, both ports do not conflict
with each other.


pgpv9yvyoQBFF.pgp
Description: PGP signature

Re: [CFT]: net-mgmt/icinga2

[Lars Engels]

On Wed, Jun 18, 2014 at 09:36:09PM +0200, Lars Engels wrote:
 On Wed, Jun 18, 2014 at 09:10:46PM +0200, Kurt Jaeger wrote:
  Hi!
  
Although it is completely new it still can run with your Icinga / Nagios
plugins and addons.

To use Icinga 2 with the Classic Web interface do the following:
   
   Is it able to run standalone, without net-mgmt/icinga ?
   Or is that not recommended ?
  
  The reason I'm asking: The is a new deployment and I want to
  start without legacy setups from the start.
 
 Icinga 2 doesn't depend on Icinga 1 but the net-mgmt/icinga port
 includes the Classic Web interface. I plan to separate it, so you don't
 need the icinga1 port. But it doesn't hurt, both ports do not conflict
 with each other.

To ease a migration from 1.x to 2, there's a migration script:

https://github.com/Icinga/icinga2-migration

But I haven't tried this one, yet.


pgpEMoZFiQMAN.pgp
Description: PGP signature

Re: pkg add: howto force the installation of a binary package?

[Lars Engels]

On Sat, Apr 12, 2014 at 05:24:12PM +0200, O. Hartmann wrote:
 
 Since this ever-fragile FreeBSD port editors/libreoffice fails on 11-CURRENT 
 and
 9.2-STABLE to compile (it fails on fours systems running the named flavours 
 of OS), I try
 to install the binary package via pkg add. But, very funny, I receive always 
 the error:
 
 pkg: Missing dependency matching Origin: 'net/openldap24-client' Version: 
 '2.4.39'
 
 The port in question is already installed, but I have 
 
 pkg info -ox openldap
 openldap-sasl-client-2.4.39 net/openldap24-sasl-client
 
 This is fun. I tried to find the magical force knob in pkg-add to override 
 such
 (insane) restrictions, but I didn't find any.
 
 Is there a regular way to install the port by force without checking for the 
 dependency?
 It seems that pkgng allows only installations of ports that do not dare to 
 have different
 options than the standard defined in the binary package expectations?
 
 Thanks in advance for your suggestions,
 
 Oliver
 
 P.S. Please CC me.

From pkg-add(8)

 -M  Force the installation of the package with missing dependencies.



pgpfbjPfwb2Qq.pgp
Description: PGP signature

Re: New port, what's next?

[Lars Engels]

On Thu, Apr 10, 2014 at 08:37:45PM +0200, John Marino wrote:
 On 4/10/2014 20:28, Baptiste Daroussin wrote:
  On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote:
 
  On 10/04/2014 18:53, Helmut Schneider wrote:
  I created a new port, Typo3-LTS. The tgz contains
 
  - Makefile
  - distinfo
  - pkg-plist
  - pkg-descr
  - a diff from www/typo3
 
  The file has ~150kB so I assume it's to big for a PR.
 
  I assume the bulk of that is the pkg-plist. The largest pkg-plist
  in the ports tree is 4M. In my opinion huge plists should be dynamically
  generated, but in your case I'd just I'd just temp-host the file
  somewhere and file a PR with a link and a checksum.
 
  Autoplist are harmful! and should be avoided as much as possible, I know 
  python
  and ruby has it but I m really not happy about that
  
  autoplist is dangerous because we have no way to control that what is 
  package is
  what the maintainer expect to be packaged! therefore we often end up with
  unoticed problems
 
 Yes, but 6,000 - 20,000 line plists are unwieldy to say the least.
 And the danger can be mitigated by the maintainer by reviewing the
 internal temporary package list, ideally on multiple platforms.  Also
 some plists are really hard to make manually if there are many options
 or if the plist morphs depending on the combination of options.
 
 yes, a safety net is removed with a generated plist but it has it's
 place.  The maintainer just has to be vigilant.
 

Can't we teach the ports system to handle pkg-plist.gz?


pgpVQZOwTagy4.pgp
Description: PGP signature

Re: reason 23 why we've moved to linux

[Lars Engels]

On Tue, Mar 25, 2014 at 03:29:23PM +0900, Randy Bush wrote:
 
 
 Royce Williams ro...@tycho.org wrote:
  
  Colin, adding you to this thread with proposed patch (two options) for
  freebsd-update, below.
  
  On Sat, Mar 22, 2014 at 10:49 AM, Randy Bush ra...@psg.com wrote:
   Honest question, have you been building things from source under
   debian's ports or are you using their version of pkg?
  
   the latter
  
   and i have two 9 systems where i try to use freebsd-update.  also a
   time-consuming rabbit hole leading nowhere pleasant.  e.g.
  
   # freebsd-update upgrade -r 9.2-RELEASE-p3
   Looking up update.FreeBSD.org mirrors... 5 mirrors found.
   Fetching metadata signature for 9.2-RELEASE from update5.freebsd.org... 
   done.
   Fetching metadata index... done.
   Inspecting system... done.
  
   The following components of FreeBSD seem to be installed:
   kernel/generic world/base world/doc world/games world/lib32
  
   The following components of FreeBSD do not seem to be installed:
  
   Does this look reasonable (y/n)? y
  
   Fetching metadata signature for 9.2-RELEASE-p3 from 
   update5.freebsd.org... failed.
   Fetching metadata signature for 9.2-RELEASE-p3 from 
   update2.freebsd.org... failed.
   Fetching metadata signature for 9.2-RELEASE-p3 from 
   update3.freebsd.org... failed.
   Fetching metadata signature for 9.2-RELEASE-p3 from 
   update4.freebsd.org... failed.
   Fetching metadata signature for 9.2-RELEASE-p3 from 
   update6.freebsd.org... failed.
   No mirrors remaining, giving up.
  
  Randy, you're not the first to specify a patch level in the target
  release version for freebsd-update.  This failure mode could be more
  friendly.
 
 raid0.dfw.rg.net:/root# freebsd-update upgrade -r 9.2-RELEASE
 freebsd-update: Cannot upgrade from 9.2-RELEASE to itself
 raid0.dfw.rg.net:/root# freebsd-update upgrade   
 freebsd-update: Release target must be specified via -r option.

You're using it wrong.

Use freebsd-update fetch install to update staying in the currently
running RELEASE branch. So you just get security updates and errata.

Use freebsd-update upgrade -r 10.0-RELEASE followed by two
freebsd-update install to upgrade to a newer release version.
I admit that the two cals of freebsd-update install are consfusing.
The first run installs the new kernel. Then you should reboot the new
kernel and the second installs the new world.
If I'd written freebsd-update I would have called it installkernel and
installworld to avoid confusion. But apart from that freebsd-update(8)
just works...




pgpotSmHN_acc.pgp
Description: PGP signature

Re: New port cad/fritzing

[Lars Engels]

On Wed, Nov 07, 2012 at 03:34:35PM -0200, Sergio de Almeida Lenzi wrote:
 Em Qua, 2012-11-07 às 21:37 +1000, Robert Backhaus escreveu:
 
  I had not problems building, but when I run, I get error messages:
  
  Dialog: Sorry, we have a problem with the swapping mechanism. Fritzing
  still works, but you won't be able to change parts properties
  
  While loading bin: core parts, a dialog that says Unable to find
  the following 112 parts, and a list starting with
  '3234DBDC00PotnetionmetModuleId' at parts/core/basic_poti.fzp'
  
  When closing that window (The 'OK' button is unavailable, because it
  is way off the bottom of the screen), we get printed to the console: 
  7 times:
  QPainter::begin: Paint device returned engine == 0, type: 2
  QPainter::end: Painter not active, aborted
  about 42 times:
  libpng error: PNG file corrupted by ASCII conversion
  
  The program then opens, but, as there are no parts, I can't do much.
  
  
 
 Ok..  
 
 I will build a system from ground zero (xorg, qt) and will test 
 hope by tomorrow I will have a clue...

Sergio,

I updated your port to the latest version of Fritzing:

http://bsd-geek.de/FreeBSD/fritzing-0.8.7b.shar.xz

Unfortunately it's still showing the errors on startup and isn't usable.
Did you find out how to solve the problem?

Lars




pgpkqRVXfcmMW.pgp
Description: PGP signature

Re: [FreeBSD-Ports-Announce] Time to bid farewell to the old pkg_ tools

[Lars Engels]

Am 2014-02-06 14:05, schrieb Daniel Nebdal:
On Thu, Feb 6, 2014 at 1:45 PM, Matthias Apitz g...@unixarea.de 
wrote:
El día Thursday, February 06, 2014 a las 01:27:50PM +0100, Julian H. 
Stacey escribió:



Michel Talon wrote:

 The old package system was total =
 crap,

local.sqlite is also crap, breaks decades of accessibility by find  
grep

 other text pipe / search tools.


Since many years I have always compiled my (i.e. the ports I need)
from CVS or now SVN ports tree on some fast baquery maschine. After
compiling I just did something like:

# mkdir PKG
# cd PKG
# pkg_create -Rnb `cd /var/db/pkg ; ls -C1`

and moved the resulting ~1500 packages to my laptops or smaller
netbooks. Until today I'm still using the old pkg_info/_add/_create
tools and skipped pkgng until today.

Will the above procedure work fine too in the future?

Why not keep the old methods unchanged in place as today?

Thanks

matthias




The recommended way to do that is to set up poudriere. It's a
different tool, but easy enough to work with, and it has certain
benefits [1].

Obviously, that's neither a yes nor a no - and in short I don't
know how pkg supports that specific use.


[1] It's smarter about building in parallel, so it should be faster.
It also handles compiling upgraded packages better - the logic is
about the same as in portmaster/portupgrade, though building each port
in a clean jail (with dependencies installed from the packages it has
already created) reduces the risk of  contamination from old versions
on the host (typically automake scripts detecting some installed and
not-yet upgraded library that's not set as a dependency ... at least
that has happened to me a few times).
It also creates a pkg repository with the packages, so if you have
network access (nfs or http) you can use pkg to do installs or
upgrades on the client machines (especially upgrades are very smooth
like that).


And it supports devel/ccache out of the box. Just install ccache, create
/var/cache/ccache and uncomment CCACHE_DIR=/var/cache/ccache in 
poudriere.conf


The ports compile much faster with ccache enabled.



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: mrxvt-devel does not show non-ascii character before end of line

[Lars Engels]

Am 2014-01-24 21:42, schrieb José García Juanino:

Hello,

after upgrade from 9.2 to 10.0 and rebuild the ports, mrxvt multi tab
terminal shows a strange issue: when you type an non-ascii character, 
it is

hidden from terminal unless you type another new character just behind.
Indeed, the exact bug is that mrxvt will not show any non-ascii 
character
before end of line. To reproduce this issue, you can type the following 
in

mrxt terminal, built from ports with the default options:

$ echo añ   myfile
$ cat myfile
a
### ñ is not shown

(substitute spanish ñ by any other non-ascii character and you will get 
the

same issue).

mrxvt is rather ancient and not mantained by upstream, but actually is 
the
best multi tab terminal. But with this annoyed bug, I think it should 
be
definitively deprecated. Any idea to fix this bug, or some proposal on 
a
good multi tab terminal? (ignoring  kde or gnome related terminals, as 
they

need huge and complex dependencies).



Have you tried reporting this upstream?


Lars
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: What is the problem with ports PR reaction delays?

[Lars Engels]

Am 2014-01-25 05:30, schrieb Aryeh Friedman:
On Fri, Jan 24, 2014 at 11:16 PM, Alfred Perlstein 
alf...@freebsd.orgwrote:





(maybe there is some great ports system that I'm not aware of that 
makes

this all as easy github, but I somehow doubt that.)



Nice to be able to plug something other then petitecloud as a possible
solution to this... namely as far I can tell from previous discussions 
and
such that the port system is nothing more then a very large DAG 
(directed
acyc. graph) the author of devel/cook (and devel/aegis) wrote an 
incredible

paper showing why Make (in any form) will never be upto the task (
http://aegis.sourceforge.net/auug97.pdf )... there are several 
solutions
that use this paper as their foundation in the ports system 
(devel/cook,
devel/cons, devel/scons)...  don't get me wrong the actual building of 
each
port should be delegated to whatever build scripts it uses the idea is 
only
that the entire port system be considered as a single graph... side 
note we

use devel/cook and devel/aegis to maintain and build petitecloud on.


Aryeh,

would you please stop spamming about petitecloud in _every single_ mail 
you're

sending to some list?

Thank you.

Lars
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing

[Lars Engels]

Am 2013-12-17 23:33, schrieb John Marino:

Over the months I've seen several ports users copy a failure log and
mail it to ports@, usually without even saying hello.  I've tried to
discourage that behavior but other members of this mail list encourage
this method of bypassing writing PRs.  One user even proudly boasted
that sending email to ports@ is faster than writing a PR so of course 
he

was going to do that instead.



That only shows how badly GNATS sucks and that it's much more 
uncomfortable to

use than writing a mail.
I totally agree that error need to be tracked in an error tracker where 
reports
don't get lost, you have a proper history etc. pp. but GNATS is just 
ancient and

should have died in a fire a long time ago.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

pkg.freebsd.org behind proxy doesn't work

[Lars Engels]

Hi all,

how can I use the official pkg.freebsd.org mirror behind a corporate 
proxy server?


With 10.0-RC1, pkg-1.2.3 and the stock /etc/pkg/FreeBSD.conf I get:

# pkg update
Updating repository catalogue
pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/digests.txz: 
Service Unavailable

pkg: Unable to find catalogs


So apparently the proxy doesn't do SRV lookups. I don't administer the 
proxy, so changing

that is not an option.
What can I do to use our official repository?

Lars

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Output change of 'pkg info' after 1.2.

[Lars Engels]

Am 2013-12-05 17:54, schrieb Yasuhiro KIMURA:

From: Baptiste Daroussin b...@freebsd.org
Subject: Re: Output change of 'pkg info' after 1.2.
Date: Thu, 5 Dec 2013 17:24:09 +0100


On Thu, Dec 05, 2013 at 04:36:00PM +0100, Michael Gmelin wrote:

On Fri, 06 Dec 2013 00:13:38 +0900 (JST)
Yasuhiro KIMURA y...@utahime.org wrote:

 I noticed that output of 'pkg info' changed after version 1.2.

 If I remember correctly, 1.1.x behaved as following:

 - 'pkg info -q pkg-name' outputs package name with version.
 - 'pkg info pkg-name' outputs package name with version, and comment.
 - 'pkg info -f pkg-name' outputs full information.

 But 1.2.1 works as following:

 - 'pkg info -q pkg-name' outputs nothing.
 - Both 'pkg info pkg-name' and 'pkg info -f pkg-name' outputs full
   information.

Just tested, pkg 1.1.4 vs. 1.2.1

pkg info -q pkg-name is identical on both, but -f vs no parameter
definitely changed and this seems like a bug to me.



It is not a bug, but intended as requested by a lot of users. To mimic 
the

pkg_info behaviour.

pkg info -q shows nothing on purpose as well as pkg info -q is used by 
the
scripts like portmaster or by the ports tree and only the return value 
is

checked
0 means something was found 1 means nothing was found.


Thank you for explanation.

Then I have one question. Is there any way to get same output as
'pkg info pkg-name' of 1.1.x? I tried some combination of options but
could not find proper one.



1.1.4 doesn't behave like you describe, but here's a universal way:

root@fbsd01:~ # pkg info pkg
pkg-1.1.4_8

root@fbsd01:~ # pkg info icinga
icinga-1.9.3_2

root@fbsd01:~ # pkg query '%n-%v' icinga
icinga-1.9.3_2

root@fbsd01:~ # pkg query '%n-%v %c' icinga
icinga-1.9.3_2 Enterprise grade open source monitoring system based on 
Nagios


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Official FreeBSD Binary Packages now available for pkgng

[Lars Engels]

On Thu, Oct 31, 2013 at 05:22:44PM -0500, Bryan Drewery wrote:
 On 10/31/2013 4:54 PM, Freddie Cash wrote:
  On Thu, Oct 31, 2013 at 2:39 PM, Mehmet Erol Sanliturk 
  m.e.sanlit...@gmail.com wrote:
  
  On Thu, Oct 31, 2013 at 4:58 PM, Bryan Drewery bdrew...@freebsd.org
  wrote:
 
  At present , the packages information and themselves are available from ,
  such as :
 
  ftp://ftp1.freebsd.org/pub/FreeBSD/ports/amd64/
 
  It seems that new pkg compatible packages will not be exposed to the
  Internet such as
 
 
  http://avalon.dragonflybsd.org/dports/
  http://pkg.wolfpond.org/
  http://mirror.exonetric.net/pub/pkgng/
 
 
  This will be a very significant inconvenience for the possible users
  because without an installed FreeBSD , they will not be able to see what
  are the available packages there .
 
  
  ???From the original message:
  Mirrors you may use instead of the global
  pkg.FreeBSD.orghttp://pkg.freebsd.org/
  :
  
  pkg.eu.FreeBSD.org http://pkg.eu.freebsd.org/
  pkg.us-east.FreeBSD.org http://pkg.us-east.freebsd.org/
  pkg.us-west.FreeBSD.org http://pkg.us-west.freebsd.org/
  
  
  pkg.freebsd.org is, basically, an alias for the above (and any other
  mirrors that come online) and the pkg(1) tool will pick a local mirror
  based on the DNS response for pkg.freebsd.org.
  
  However, you are free to manually enter any of the above mirrors into your
  pkg.conf.
  
  And, you are free to browse any of the above mirrors via HTTP in any web
  browser.
  
  It's not nearly as convenient as just browsing pkg.freebsd.org, but it's
  still possible to do so.
 
 These are still SRV hosts as well. The real hosts can be found with
 
 dig SRV _http._tcp.HOST HOST being the host from above lists.
 

Please add this to pkg.conf(5) as this it not intuitive and the syntax
is a bit cumbersome.


pgp1Mr54VuCiZ.pgp
Description: PGP signature

Re: Official FreeBSD Binary Packages now available for pkgng

[Lars Engels]

On Sun, Nov 03, 2013 at 12:36:54AM +0200, Kimmo Paasiala wrote:
 On Sun, Nov 3, 2013 at 12:34 AM, Lars Engels lars.eng...@0x20.net wrote:
  On Thu, Oct 31, 2013 at 05:22:44PM -0500, Bryan Drewery wrote:
  On 10/31/2013 4:54 PM, Freddie Cash wrote:
   On Thu, Oct 31, 2013 at 2:39 PM, Mehmet Erol Sanliturk 
   m.e.sanlit...@gmail.com wrote:
  
   On Thu, Oct 31, 2013 at 4:58 PM, Bryan Drewery bdrew...@freebsd.org
   wrote:
  
   At present , the packages information and themselves are available from 
   ,
   such as :
  
   ftp://ftp1.freebsd.org/pub/FreeBSD/ports/amd64/
  
   It seems that new pkg compatible packages will not be exposed to the
   Internet such as
  
  
   http://avalon.dragonflybsd.org/dports/
   http://pkg.wolfpond.org/
   http://mirror.exonetric.net/pub/pkgng/
  
  
   This will be a very significant inconvenience for the possible users
   because without an installed FreeBSD , they will not be able to see what
   are the available packages there .
  
  
   ???From the original message:
   Mirrors you may use instead of the global
   pkg.FreeBSD.orghttp://pkg.freebsd.org/
   :
  
   pkg.eu.FreeBSD.org http://pkg.eu.freebsd.org/
   pkg.us-east.FreeBSD.org http://pkg.us-east.freebsd.org/
   pkg.us-west.FreeBSD.org http://pkg.us-west.freebsd.org/
  
  
   pkg.freebsd.org is, basically, an alias for the above (and any other
   mirrors that come online) and the pkg(1) tool will pick a local mirror
   based on the DNS response for pkg.freebsd.org.
  
   However, you are free to manually enter any of the above mirrors into 
   your
   pkg.conf.
  
   And, you are free to browse any of the above mirrors via HTTP in any web
   browser.
  
   It's not nearly as convenient as just browsing pkg.freebsd.org, but it's
   still possible to do so.
 
  These are still SRV hosts as well. The real hosts can be found with
 
  dig SRV _http._tcp.HOST HOST being the host from above lists.
 
 
  Please add this to pkg.conf(5) as this it not intuitive and the syntax
  is a bit cumbersome.
 
 
 You will never have to know that syntax unless you're one of the few
 that are behind a very restrictive firewall/proxy. The pkg client does
 all this SRV record magic internally to find out a suitable mirror.
 

Right, but I actually happen to fall into that group at work. ;-)


pgpkmsSrY0uIi.pgp
Description: PGP signature

Re: Finding abandoned ports

[Lars Engels]

Am 30.10.2013 15:02, schrieb Alex Laurie:

Hello all,

Only really just getting into FreeBSD but I am inspired to help out. 
I'm

not a developer or anything. However I do like to install and update
things. I though one area I may be able to help out is in the ports 
side of
things. I have been through the Porters handbook and thought I would 
try
updating some out of date ports to cut my teeth so to speak. Looking 
around

I don't seem to see anywhere with abandoned ports that need some love.

Any help or pointers?



You can start by finding out which installed ports are unmaintained, 
give

them some love and maybe become a maintainer. See

http://lists.freebsd.org/pipermail/freebsd-ports/2012-December/079880.html

for details.


Lars
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org