Paul Tomblin <[EMAIL PROTECTED]> wrote:
>Debian just marked Debian 4.0 (etch) as stable, so I upgrade my Debian
>3.1 (sarge) colo box to Debian 4.0. Along the way, it upgraded Mailman
>from 2.1.5 to 2.1.9. Just wanted to let anybody else contemplating such
>an upgrade that it went without a hitch. The stage where it says
>"Updating old qfiles" takes rather a long time, but it eventually
>finishes. Mail continues to flow, the web interface works, the archives
>work.
>From my experience with Ubuntu/Debian distributions, just because it
is labelled 2.1.9 does not mean that the distribution was built from
the SourceForge 2.1.9 source tree. As I could not guarantee that the
Ubuntu/Debian package was the real 2.1.9 source, I built a package
from the 2.1.9 source tree.
I tried a build on dapper using a 2.1.9 edgy-backport distribution.
This was supposedly a 2.1.9 source tree. I saw these patch files:
debian/patches/00_stolen_from_HEAD.patch
debian/patches/01_defaults.debian.patch
debian/patches/07_snooze.patch
debian/patches/10_wrapper_uid.patch
debian/patches/11_handle_propfind.patch
debian/patches/15_mailmanctl_daemonize.patch
debian/patches/16_update_debian.patch
debian/patches/20_qmail_to_mailman.debian.patch
debian/patches/21_newlist_help.patch
debian/patches/30_pipermail_threads.patch
debian/patches/32_MIME_fixup.patch
debian/patches/51_nocompile.pyc.patch
debian/patches/52_check_perms_lstat.patch
debian/patches/53_disable_addons.patch
debian/patches/56_fix_de_broken_links.patch
debian/patches/58_fix_es_translation.patch
debian/patches/59_fix_missing_language_crash.patch
debian/patches/61_fix_ru_siteowner.patch
debian/patches/62_new_list_bad_pending_requests.patch
debian/patches/63_update_default_server_language.patch
debian/patches/64_correct_html_nesting.patch
debian/patches/65_handle_templates_directories.patch
debian/patches/66_donot_let_cache_html_pages.patch
debian/patches/67_update_handle_old_versions.patch
debian/patches/70_invalid_utf8_dos.patch
debian/patches/71_date_overflows.patch
debian/patches/72_fblast_add_shebang.patch
debian/patches/74_admin_non-ascii_emails.patch
debian/patches/77_header_folding_in_attachments.patch
debian/patches/78_DeprecationWarning.patch
debian/patches/79_archiver_slash.patch
debian/patches/80_fix_string_search.patch
debian/patches/99_js_templates.patch
I stopped building the process when I discovered that the patch
process had changed from dapper to edgy, and I was not sure how
to handle the changes in dapper. And for most of the patches, there
was no cross-reference to a Debian patch number, so I could not
tell the reason for the patch without close examination of the source
code. I did not do this because I have learned from this mailman-users
list that complete help is not available here for non-standard source
modifications.
I did a build, using the Debian mailman_2.1.5-9ubuntu4.1 distribution
and using the SourceForge 2.1.9 source tree. I saw these patches:
debian/patches/00_stolen_from_HEAD.dpatch
debian/patches/01_defaults.debian.dpatch
debian/patches/02_CAN-2004-1177_driver_css.dpatch
debian/patches/03_CAN-2004-1143.dpatch
debian/patches/04_CAN-2005-0202.dpatch
debian/patches/05_config_list_member_options.dpatch
debian/patches/07_snooze.dpatch
debian/patches/10_wrapper_uid.dpatch
debian/patches/11_handle_propfind.dpatch
debian/patches/12_savannah_wrapper.dpatch
debian/patches/15_mailmanctl_daemonize.dpatch
debian/patches/16_update_debian.dpatch
debian/patches/20_qmail_to_mailman.debian.dpatch
debian/patches/21_newlist_help.dpatch
debian/patches/23_fix_urls.dpatch
debian/patches/30_pipermail_threads.dpatch
debian/patches/31_buggy_queuefiles.dpatch
debian/patches/32_MIME_fixup.dpatch
debian/patches/50_README.EXIM.paths.dpatch
debian/patches/50_README.POSTFIX.dpatch
debian/patches/51_nocompile.pyc.dpatch
debian/patches/52_check_perms_lstat.dpatch
debian/patches/53_disable_addons.dpatch
debian/patches/56_fix_de_broken_links.dpatch
debian/patches/57_fix_missing_da_template.dpatch
debian/patches/58_fix_translations.dpatch
debian/patches/59_fix_missing_language_crash.dpatch
debian/patches/60_french_archtocentry.dpatch
debian/patches/61_fix_ru_siteowner.dpatch
debian/patches/62_new_list_bad_pending_requests.dpatch
debian/patches/63_update_default_server_language.dpatch
debian/patches/64_correct_html_nesting.dpatch
debian/patches/65_donot_add_empty_cc.dpatch
debian/patches/65_handle_templates_directories.dpatch
debian/patches/66_donot_let_cache_html_pages.dpatch
debian/patches/67_update_handle_old_versions.dpatch
debian/patches/68_python24_bouncehandler_datetime.dpatch
debian/patches/68_translation_update_nl.dpatch
debian/patches/70_invalid_utf8_dos.dpatch
debian/patches/71_invalid_date_dos.dpatch
debian/patches/72_mime_None_payload.dpatch
debian/patches/99_js_templates.dpatch
debian/patches/XX_po-debconf_hack.dpatch
debian/patches/handle-from-in-non-ascii.dpatch
debian/patches/security-CVE-2006-2941.dpatch
debian/patches/security-CVE-2006-3636-XSS.dpatch
debian/patches/security-error_log.dpatch
Of the three three security patches added to the 2.1.5 source, two
matched the SourceForge patches and one did not match - the patch
was placed in a different source file. Out of all of these patches,
the only one I kept was
01_defaults.debian
that changes Defaults.py.in in three places:
-IMAGE_LOGOS = '/icons/'
+IMAGE_LOGOS = '/doc/mailman/images/'
-DEFAULT_URL_PATTERN = 'http://%s/mailman/'
+DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
-PIDFILE = os.path.join(DATA_DIR, 'master-qrunner.pid')
+PIDFILE = "/var/run/mailman/mailman.pid"
I kept this patch because I wanted the install to place the resulting
files in the directories where Debian/Ubuntu expected them.
----------------------------------------------------------------------
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory Phone: +1 (630) 252-7277
9700 South Cass Avenue Facsimile:+1 (630) 252-4601
Building 222, Room D209 Internet: [EMAIL PROTECTED]
Argonne, IL 60439-4828 IBMMAIL: I1004994
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
