Maintainer of xosd and perlipq MIA?

[Sven Hoexter]

Hi all,
I've submitted a patch for #495246 (xosd) and #494224 (perlipq)
and it really looks like both package maintainers are MIA.

For xosd that's pmhahn@... with the last maintainer upload
in 2004 followed by 5 NMUs in the last years. According to qa.d.o
it's still not set to O.

perlipq just hat the initial upload by dirson@... in 2004
and a NMU July this year to fix a Perl 5.10 FTBFS.

I think both packages should be at least be set to O. perlipq can maybe
even removed from Debian (about 50 installations in popcon).

Cheers,
Sven


--
To UNSUBSCRIBE, email to debian-qa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Dmitry E. Oboukhov-6]

On 21:14 Sat 23 Aug     , Sven Hoexter wrote:
SH> Hi all,
SH> I've submitted a patch for #495246 (xosd) and #494224 (perlipq)
SH> and it really looks like both package maintainers are MIA.

Philipp took my patches for mytop in May. Mail him.

SH> For xosd that's pmhahn@... with the last maintainer upload
SH> in 2004 followed by 5 NMUs in the last years. According to qa.d.o
SH> it's still not set to O.

SH> perlipq just hat the initial upload by dirson@... in 2004
SH> and a NMU July this year to fix a Perl 5.10 FTBFS.

SH> I think both packages should be at least be set to O. perlipq can maybe
SH> even removed from Debian (about 50 installations in popcon).

--
... mpd paused: Accept - Feelings

. ''`. Dmitry E. Oboukhov
: :’  : unera@...
`. `~’ GPGKey: 1024D / F8E26537 2006-11-21
  `- 1B23 D4F8 8EC0 D902 0555  E438 AB8C 00CF F8E2 6537

[Thomas Viehmann]

Hi Sven,

thanks for looking into QA and fixing RC bugs!

Sven Hoexter wrote:
> I've submitted a patch for #495246 (xosd) and #494224 (perlipq)
> and it really looks like both package maintainers are MIA.
>
> For xosd that's pmhahn@... with the last maintainer upload
> in 2004 followed by 5 NMUs in the last years. According to qa.d.o
> it's still not set to O.
So I mainly looked at this one, it looks like it could use fixing and
possibly orphaning.
That said, your proposed NMU is quite involved for an NMU during freeze.
You might want to check your changelog paragraph with the release team
and have them say yes or no to whether they want each item fixed during
the freeze. If you do that, and you don't hear from the maintainer in
the next week, I'll sponsor your NMU (assuming that it survives my
attempts at testing it). Note, though, that your proposed NMU is quite
extensive in scope, possibly even stretching the instructions in the
developer's reference.
As for the orphaning, I would recommend getting the experts for the
BaPaSe involved (randomly CCing Barry, hi!).

Similar comments probably apply for the other package.

Kind regards

T.
--
Thomas Viehmann, http://thomas.viehmann.net/


--
To UNSUBSCRIBE, email to debian-qa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...