Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Feb 2017 15:14:27 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 217072] net-mgmt/nagvis: port update destroys installation!
Message-ID:  <bug-217072-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217072

            Bug ID: 217072
           Summary: net-mgmt/nagvis: port update destroys installation!
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: ohartmann@walstatt.org
                CC: derfi@vei.ru
                CC: derfi@vei.ru
             Flags: maintainer-feedback?(derfi@vei.ru)

In the chain of updating Xorg I had to update serveral ports and by acciden=
t, I
also included net-mgmt/nagvis.

This port stores its etc/ folder under /usr/local/www/nagvis/etc. The folder
contains maps and other crucial configuration stuff. An update, reinstallat=
ion
DESTROYS (or overwrites, but with the very same end result) all content of
maps, automaps!

Other ports store either their local configs in ETCDIR=3D/usr/local/etc or
preserve the configs.

I had a bunch of maps created my own and after this update, everything was
gone, even the customisation of integration of nagvis in net-mgmt/icingaweb=
2.

This is very bad. Even if someone does have a backup, this shouldn't be hap=
pen.

Either the content of this non-standard etc folder should be precious and n=
ot
deleted, or the standard etc folder should be delegated to
/usr/local/etc/nagvis (or whatever is suitable in this case).

Or do I miss something here and made a capital mistake?

oh

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217072-13>