* Matthias Schmitz
> Since this is my first maintainership it is a good idea to have some
> more experienced co-maintainers. And if linpro has nothing against it i
> will keep the code in the upstream svn.
Nothing against that at all, in fact I see it as a big advantage. Much
easier to branch a
Matthias Schmitz <[EMAIL PROTECTED]> writes:
> [...] merge all the candidate changesets from 1.3 and then look
> which debian bugs still unfixed.
That sounds like a good plan.
> (And if there is time left after this - bring a 1.3 deb in
> experimental.)
May work. As far as I know, the plans fo
Hi,
On Thursday 31 January 2008 20:11, Matthias Schmitz wrote:
> > I am under the impression that
> > their work will likely result in a new upstream release (1.2.6) as well
> > as new Debian packages.
> This looks like my plan :-) - merge all the candidate changesets from
> 1.3 and then look whic
Hi,
On Thursday 31 January 2008 23:05, you wrote:
> > Package most things from http://muninexchange.projects.linpro.no, and
> > other sources?
> I think yes. Sometimes we need plugins that arent in munin.
I think so too and suggest to build the munin-plugins-contrib package per
default and stick
Hi,
> Package most things from http://muninexchange.projects.linpro.no, and
> other sources?
I think yes. Sometimes we need plugins that arent in munin.
--
[]'s
José Carlos
Hi all!
Tore Anderson wrote:
glad there's finally some interest in taking over the package from me.
I think there's at least a year since I've had any free time and
motivation to work on Debian packaging, so it's about high time somebody
takes care of it again...
Matthias Schmitz was the first
"Jose Carlos Medeiros" <[EMAIL PROTECTED]> writes:
> Holger, about 'munin-plugins-contrib' its a good idea. As munin
> user I would like something like that.
Package most things from http://muninexchange.projects.linpro.no, and
other sources?
> Well, I think you will be a better maintanership,
Holger Levsen <[EMAIL PROTECTED]> writes:
> So what's the status of 1.3.x?
1.3.x is a development branch, which will result in the release of a
stable version from 1.4.x. 1.4.x should be packaged after 1.2.x.
It's the same odd and even number versioning as the Linux kernel used
to separate from
Hi,
On Monday 28 January 2008 11:46, you wrote:
> 1.2.6 will be part of 1.2.x. ;-)
Hehe. So what's the status of 1.3.x?
> > Is this OFTC or freenode or really another irc network?
> Neither, it's just our (Linpro's) stand-alone interal IRC server. Maybe
> it's time to move the channel elsewher
Hi, All
Holger, about 'munin-plugins-contrib' its a good idea. As munin user
I would like something like that.
Well, I think you will be a better maintanership, because from now
Im a bit busy :(
Then, you can take this ITA to you.
Regards
Jose Carlos
2008/1/28, Holger Levsen <[EMAIL PRO
* Holger Levsen
> Cool. Currently I'm actually mostly interested in bringing 1.2.x in
> (even better) shape, as this is what I use. But then, I'm happy to
> switch to 1.3 if upstream thinks it's ready. (Which I dont believe it
> is, considering it's not even in experimental.)
1.2.6 will be part o
Hi Tore,
On Monday 28 January 2008 09:35, you wrote:
> Matthias Schmitz was the first one to contact me about taking over the
> package, and he's been actively following up on that by taking on lots
> of outstanding work on the 1.2.x branch. My colleague Stig Sandbeck
> Mathisen has also been try
* Holger Levsen
> today I stumbled upon #403341, which has a very simple fix. There are
> quite some similar bugs (simple, with patch) in the debian BTS which
> I would like to help fixing, as I use munin heavily for work, in
> Debian Edu and privatly.
>
> So I like to request access to the upstr
Heya,
> So I like to request access to the upstream SVN, as this is where the debian
> packaging is kept, AIUI.
>
> Jose (as new owner of this bug), what do you think? I cc:ed Bernd, as we
> spoke
> about team maintaining munin in December last year..
Seconded. I'd be happy to maintain the m
Hi,
today I stumbled upon #403341, which has a very simple fix. There are quite
some similar bugs (simple, with patch) in the debian BTS which I would like
to help fixing, as I use munin heavily for work, in Debian Edu and privatly.
So I like to request access to the upstream SVN, as this is w
15 matches
Mail list logo
