Sponsored people

2003-01-25 Thread Martin Michlmayr
Joey asked how many sponsored people there are at the moment and since
I didn't know I asked Colin for an estimate.  Colin did a great job,
and came up with a list of 191 people.  While I (and he) thought this
was a high number, it's actually accurate (take or give a few).  Now I
wouldn't be surprised if some of those 191 people weren't active
anymore... I just wanted to mention this here to show that this is
actually a serious issue.  While I don't have time right now, I will
go through this list of people at some point to find inactive people
and orphan their packages.

In the meantime, I have added the following to the README in
klecker:/org/qa.debian.org/mia:


Sponsored people who are inactive
-

A major problem are sponsored people are are inactive.  They are even
harder to pin down than inactive developers since no echelon information
is not available about them, their contact details are not available on
db.debian.org, etc.  One strategy which might be useful to find out about
their current status is to contact the developer who has actually uploaded
the package.  After all, they are responsible for the upload and should
know what happened to the person they sponsored.  Furthermore, one can
check http://nm.debian.org and see the status of the person in the NM
process.  The site also lists the Application Manager of the applicant and
he might have more information.

One problem is that there is no list of sponsored people.  Colin Watson
has used the following scripts as a starting point to find sponsored
people:

  grep-available -rFMaintainer -nsMaintainer . > maintainers

  (gpg --no-default-keyring --keyring ./debian-keyring.gpg --list-keys; \
   gpg --no-default-keyring --keyring ./debian-keyring.pgp --list-keys) \
| grep -v '^\[.*\]$' | grep . | sort -u > keyring-maintainers

  perl -e 'open K, "keyring-maintainers";
   while () { $k{$_} = 1; }
   close K;
   open M, "maintainers";
   while () { print unless $k{$_}; }
   close M;' > sponsored-maintainers

However, this is only an approximation.  It's still necessary to go through
the file by hand and remove the ones who use different e-mail addresses from
the ones in their GPG keys.  Thus, most of the work is weeding through the
sponsored-maintainers file and comparing it more intelligently to
keyring-maintainers.  Once a current listing of sponsored people has been
made with this method, one can start checking the status of all sponsored
people against http://nm.debian.org/ and see who's left, or which applicants
who are "on hold" in the NM process have packages in the archive.

-- 
Martin Michlmayr
[EMAIL PROTECTED]



Bug#178394: qa.debian.org: find out problems before cron.monthly does

2003-01-25 Thread Dan Jacobson
Package: qa.debian.org
Version: unavailable; reported 2003-01-26
Severity: minor

sorry but here's some examples of somethings maybe packages should
check: things that won't be discovered until cron.monthly does.

e.g. the HylaFAX folks never thought i wouldn't even have faxed once
this month.

the Nautilus people had some other problem... i don't really know
what Nautilus is all about but i seem to have it installed :-)

both i have probably reported and perhaps are fixed already... next
time i do apt-zip i will know...

anyways the point is: maybe in the lintian or policy areas, such
problems could be caught before cron.monthly catches them and sends
worrisome messages to the user.

From: [EMAIL PROTECTED] (Anacron)
To: [EMAIL PROTECTED]
Subject: Anacron job 'cron.monthly'

/etc/cron.monthly/hylafax:
awk: /tmp/fileah3jWf:267: fatal: cannot open file 
`/var/spool/hylafax/log/xferfaxlog' for reading (No such file or directory)
Null message body; hope that's ok
awk: /tmp/fileMjGeyC:300: fatal: cannot open file 
`/var/spool/hylafax/log/xferfaxlog' for reading (No such file or directory)
Null message body; hope that's ok
/etc/cron.monthly/scrollkeeper:
/usr/share/omf/nautilus/nautilus-quick-reference-es.omf:5: error: Input is not 
proper UTF-8, indicate encoding !
  Referencia R嫚ida de Nautilus
  ^
/usr/share/omf/nautilus/nautilus-quick-reference-es.omf:5: error: Bytes: 0xE1 
0x70 0x69 0x64
  Referencia R嫚ida de Nautilus
  ^
/usr/share/omf/nautilus/nautilus-quick-reference-ko.omf:5: error: Input is not 
proper UTF-8, indicate encoding !
  喻⼂楝蝶 緒艇 紫遺蜓
  ^
/usr/share/omf/nautilus/nautilus-quick-reference-ko.omf:5: error: Bytes: 0xB3 
0xEB 0xC6 0xBF
  喻⼂楝蝶 緒艇 紫遺蜓
  ^
/usr/share/omf/nautilus/nautilus-user-manual-es.omf:8: error: Input is not 
proper UTF-8, indicate encoding !
  GNOME|N�cleo del Escritorio
   ^
/usr/share/omf/nautilus/nautilus-user-manual-es.omf:8: error: Bytes: 0xFA 0x63 
0x6C 0x65
  GNOME|N�cleo del Escritorio
   ^
/usr/share/omf/nautilus/nautilus-user-manual-ko.omf:5: error: Input is not 
proper UTF-8, indicate encoding !
  喻⼂楝蝶 餌辨濠 撲貲憮
  ^
/usr/share/omf/nautilus/nautilus-user-manual-ko.omf:5: error: Bytes: 0xB3 0xEB 
0xC6 0xBF
  喻⼂楝蝶 餌辨濠 撲貲憮
  ^
=
btw, those lines look Chinese to me of course here in gnus with my locale.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux debian 2.4.19-k7 #1 Sun Oct 6 20:29:56 EST 2002 i686
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5