[Pkg-nagios-devel] Re: Bug#341748: ITP: nagios2 -- A host/service/network monitoring and management system

[sean finney]

hey marc,

sorry for the delay in response, been travelling several timezones
westward in the past couple days...

On Mon, Dec 19, 2005 at 03:16:46PM +0100, Marc Haber wrote:
> I therefore suggest the attached patch to debian/control. With this
> patch, nagios2 does install and cleanly replaces nagios and
> nagios-common.

nagios2-common shouldn't depend on on nagios2, but instead nagios2
should depend on nagios2-common.  i think there was a rationale
for that, but now i'm having a hard time remembering.

> I have also re-worked the package descriptions a bit, putting the
> information important for the local admin first.

thanks for that :)

> - Why does nagios-common depend on fileutils? fileutils currently is
>   only an empty transition package. I'd vouch for removing the
>   fileutils dependency in favor of the already present coreutils
>   dependency.

i believe it was for backwards compatability / backporting.  however,
i don't have a problem removing it... if someone complains we can
always put it back.

> - Shouldn't apache2 be the primary http server depended on?

yes, i suppose so.

> - nagios-text has much stricter depends on nagios-plugins, and
>   installing nagios-text pulls nagios-plugins, nagios-plugins-basic and
>   nagios-plugins-standard. What's the reason for nagios2 only
>   depending on nagios-plugins and not on -basic and -standard?

i'm not sure i follow here.  they should both be the same, depending
on nagios-plugins (>= $vers) | nagios-plugins-basic, where $vers
is the version where the packages were first split.

> - nagios2 doesn't do debconf at all. Is this only "still missing", or
>   did you decide to remove the debconfization?

just an omission... however i'll be somewhat picky about how we
do webserver configuration, so let's talk about it before we
build-in support for that.  if you have other ideas about how
debconf could augment the install/configuration process, feel free
to bring them up.

> - Since nagios2 re-uses /etc/nagios and probably /var/foo/nagios
>   (didn't look), we might get in trouble if the local admin decides to
>   purge nagios after installing nagios2. I'd like to propose going for
>   /etc/nagios2 and /var/foo/nagios2, avoiding conflicts with nagios.

i've never been in this situation, and have to admit that i don't know
what would happen if a 1.x package was purged after a 2.x package was
installed.  might have to do some emperical testing :)

my initial feeling is that all packages should use /etc/nagios, unless
there is a compelling reason why they shouldn't.  otherwise, we risk
scuttling any attempt at a reasonably painless upgrade path.  i don't
feel as strongly about other directories.

>  Package: nagios2
>  Architecture: any
> @@ -41,9 +45,6 @@
>  Replaces: nagios, nagios-text, nagios-pgsql, nagios-mysql
>  Provides: nagios, nagios-text

now that i think about it, shouldn't we have a Conflicts in there too?

On Tue, Dec 20, 2005 at 12:19:02PM +0100, Marc Haber wrote:
> I have created a wiki page, http://wiki.debian.org/PkgNagios2, for
> tracking of development issues. This can later also serve as the
> Nagios2 packages home page (see http://pkg-exim4.alioth.debian.org/).

very nice.  i was wanting to have some kind of web-presence for the
project (pkg-nagios.alioth.debian.org points somewhere currently), but
was not looking forward to having to maintain that.  i think a wiki
is a better option so thanks for that.

On Tue, Dec 20, 2005 at 04:26:35PM +0100, Marc Haber wrote:
> I have written my first lsb'ized init script.
> 
> Would it be ok to branch Nagios2 to commit my changes to svn, or is it
> ok to commit directly to trunk?

as long as you're not going to do any surprise uploads, go ahead and
commit to trunk.  i'll try and keep tabs on the commit messages and
throw any feedback your way in the meantime.

> My plan is to have nagios2 beta packages ready for experimental before
> new year's eve.

sounds great, thanks for all your hard work on this.


	sean

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-nagios-devel/attachments/20051220/7b22a0c4/attachment.pgp