Your message dated Tue, 08 Sep 2009 00:04:04 +0200
with message-id <[email protected]>
and subject line This is to be closed
has caused the Debian Bug report #349919,
regarding dak: jennifer as patched in this package (not upstream) dies on
maintainer names with a ', '
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
349919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=349919
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dak
Version: 1.0-8
Severity: normal
Hi,
jennifer dies in the following way for a maintainer name with a ',':
Traceback (most recent call last):
File "/usr/bin/jennifer", line 1160, in process_it
action();
File "/usr/bin/jennifer", line 1029, in action
Katie.do_reject(0, reject_message);
File "/usr/lib/python2.3/site-packages/katie.py", line 652, in do_reject
utils.send_mail(reject_mail_message);
File "/usr/lib/python2.3/site-packages/utils.py", line 398, in send_mail
(rfc822_maint, rfc2047_maint, name, email) = fix_maintainer(item.strip())
File "/usr/lib/python2.3/site-packages/utils.py", line 361, in fix_maintainer
raise ParseMaintError, "No @ found in email address part."
ParseMaintError: No @ found in email address part.
It occured to me with a backport of mpich_1.2.7 where the maintainer
name is 'Adam C. Powell, IV <[email protected]>' (with a ',').
If I do not mistake, the problem comes from the following lines in
utils.py
--------------------------------------------------------------------
+ # Fields to check. Here the order is important because Bcc
+ # will be the last changed field
+ fields = ["To", "Bcc", "Cc"]
+ for field in fields:
+ # Check each field
+ value = message_raw.get(field, None)
+ if value != None:
+ match = [];
+ for item in value.split(","):
+ (rfc822_maint, rfc2047_maint, name, email) =
fix_maintainer(item.strip())
+ if email not in whitelist:
+ print "Skipping %s since it's not in %s" % (item,
Cnf["Dinstall::MailWhiteList"])
+ continue
+ match.append(item)
+ # Doesn't have any mail in whitelist so remove the header
+ if len(match) == 0:
+ del message_raw[field]
+ else:
+ message_raw.replace_header(field, string.join(match,
", "))
+
--------------------------------------------------------------------
that have been added specifically to the packaging of dak and do not
exist upstream.
I do not know yet how to fix this excepted with the obvious workaround
that is to remove any ',' in maintainer's names.
Thanks,
Frederic Lehobey
-- System Information:
Debian Release: 3.1
Architecture: sparc (sparc64)
Kernel: Linux 2.6.8-2-sparc64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages dak depends on:
ii apt [libapt-pkg-libc6.3-5-3 0.5.28.6 Advanced front-end for dpkg
ii apt-utils 0.5.28.6 APT utility programs
ii bzip2 1.0.2-7 high-quality block-sorting file co
ii debconf 1.4.30.13 Debian configuration management sy
ii dpkg-dev 1.10.28 Package building tools for Debian
ii exim4-daemon-light [mail-tr 4.50-8 lightweight exim MTA (v4) daemon
ii gnupg 1.4.1-1 GNU privacy guard - a free PGP rep
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libgcc1 1:3.4.3-13 GCC support library
ii libstdc++5 1:3.3.5-13 The GNU Standard C++ Library v3
ii python 2.3.5-2 An interactive high-level object-o
ii python-apt 0.5.10 Python interface to libapt-pkg
ii python-ldap 2.0.4-1 A LDAP interface module for Python
ii python-pygresql 1:3.6.1-1 PostgreSQL module for Python
ii ucf 1.17 Update Configuration File: preserv
-- debconf information:
* dak/username: deb-dak
* dak/groupname: debadmin
* dak/hostname: localhost.localdomain
* dak/path: /var/lib/dak
* dak/setup:
* dak/archivename: archive FDL (abonde)
--- End Message ---
--- Begin Message ---
The package is removed and this bug no longer applies. (Alternatively it has
been fixed in whatever is current on ftpmaster.d.o). Thus closing it
--- End Message ---
