Removing -N is a bad idea ... there are all sorts of QA dependencies
with the "broken" PMDA there that I don't want to try and unscramble.
Similarly removing -n for Install/Remove is not that simple.
So I've converged on part of my changes and part of Nathan's idea of
hiding -n namespace to pminfo unless -n appears in the Install/Remove
command line.
I'm close to getting this all passing QA before I post my commits back
to my oss tree ... but Ubuntu 9.10 still has tool chain strangeness and
I've encountered a couple of day one bugs (one in libpcp and one in the
txmon PMDA, if you can believe that). So I still have a bit more work
needed on this front before it is clear ... however the pmdaproc.sh
changes look to be OK now.
On Wed, 2009-11-18 at 09:30 +1100, Nathan Scott wrote:
> ----- "Nathan Scott" <nscott@xxxxxxxxxx> wrote:
> > ----- "Nathan Scott" <nscott@xxxxxxxxxx> wrote:
> > > ----- "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx> wrote:
> > > > ...
> > > > I've seen the same thing with QA 647 where after the mmv PMDA is
> > > > installed, this metric appears (I have an independent pmdaproc.sh
> > > fix
> > > > to make the warning message go away from the Check line) ...
> > >
> > > Ah, I was looking at a similar thing on the train this morning ...
> > > can you send yours? This patch made the problem go away
> > > ...
> >
> > I've pushed my current set of changes into my development tree on oss,
> > want to resolve this one before I tackle QA ... lemme know once you've
> > decided on an approach here (think this is a dynamic-pmns-wide kind
> > of issue, isn't it? i.e. not just affecting MMV?).
>
> I've got to set this stuff aside for a little while - attached patch
> is where I've got up to on this side of things. Haven't attempted to
> completely remove -N from Install/Remove at this stage, as per our IRC
> discussion.
>
> cheers.
>
|