Package: mutt / 2.0.5-4.1+deb11u3
Metadata
Package | Version | Patches format |
---|---|---|
mutt | 2.0.5-4.1+deb11u3 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
debian specific/Muttrc.patch | (download) |
doc/Muttrc.head |
39 37 + 2 - 0 ! |
muttrc * 2009-01-15 myon: refreshed for mutt-1.5.19; drop our list of ignored headers in favor of upstream's new unignore list Signed-off-by: Matteo F. Vescovi <mfvescovi@gmail.com> |
debian specific/882690 use_fqdn_from_etc_mailname.patch | (download) |
init.c |
67 48 + 19 - 0 ! |
--- |
debian specific/use_usr_bin_editor.patch | (download) |
init.c |
2 1 + 1 - 0 ! |
use_usr_bin_editor Even if EDITOR is not set, mutt will always use /usr/bin/editor (which is set by update-alternatives), rather than falling back to vi. |
debian specific/correct_docdir_in_man_page.patch | (download) |
doc/mutt.man |
2 1 + 1 - 0 ! |
correct_docdir_in_man_page Fix the link so it points to the correct docdir and gzipped manual. |
debian specific/document_debian_defaults.patch | (download) |
init.h |
19 19 + 0 - 0 ! |
document_debian_defaults Some customization of the option which are straying from the default only on Debian systems. |
debian specific/467432 write_bcc.patch | (download) |
headers.c |
2 1 + 1 - 0 ! |
467432-write_bcc MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit The purpose of this patch is to alter the behavior of the write_bcc option because exim4, the default SMTP in Debian, does not strip the Bcc headers; by default write_bcc is set so this could cause a privacy leak. The behavior that this patch introduces is: never write the Bcc header when the message is sent, otherwise, if the message is sent to Fcc, then this optin will be evaluated and the Bcc header will be written based on that. Background discussion on this is in the following bugs: http://bugs.debian.org/304718 http://bugs.debian.org/467432 This patch is a slightly modified version of the patch provided by Stefan Vlkel <stefan@bc-bd.org> in the second bug. |
debian specific/566076 build_doc_adjustments.patch | (download) |
doc/Makefile.am |
6 2 + 4 - 0 ! |
566076-build_doc_adjustments Use w3m to build the txt manual. |
debian specific/828751 pinentry gpg2 support.patch | (download) |
contrib/gpg.rc |
26 18 + 8 - 0 ! |
--- |
debian specific/530584 default tmpdir to var tmp.patch | (download) |
init.c |
2 1 + 1 - 0 ! |
[patch 1/2] changed tmpdir default to /var/tmp By default, mutt stores drafts in /tmp/mutt-$HOSTNAME-$UID-$PID-$REV. /tmp is designed to hold data |
debian specific/530584 default tmpdir to var tmp docs.patch | (download) |
doc/manual.html |
4 2 + 2 - 0 ! |
--- |
misc/gpg.rc paths.patch | (download) |
contrib/gpg.rc |
8 2 + 6 - 0 ! |
gpg.rc-paths Use the correct path of pgpewrap. |
misc/smime.rc.patch | (download) |
contrib/smime.rc |
19 10 + 9 - 0 ! |
smime.rc Add CA's provided by ca-certificates to the ones distributed by the default installation of Mutt. Signed-off-by: Matteo F. Vescovi <mfv@debian.org> |
upstream/528233 readonly open.patch | (download) |
attach.c |
5 5 + 0 - 0 ! |
528233-readonly-open Open attachments as read-only so the editor won't be able to modify it; otherwise the user can believe that he/she can edit it and risk to lose his/her work (see upstream bug http://bugs.mutt.org/3261) Debian bugs: #528233, updated in #572203 |
upstream/980924 updated german translation.patch | (download) |
po/de.po |
3463 1844 + 1619 - 0 ! |
--- |
upstream/985152 body color slowness.patch | (download) |
mutt_curses.h |
5 5 + 0 - 0 ! |
[patch] improve body color matching speed by caching future matches. On a *very* long body (or header_partial) lines with multiple color lines that match, performance can be degraded. For instance if there were moderately expensive regexp matches against "A" "B" and "C". A line with: A A A A A B A A C A A A B A A A C The B and C regexps were scanned again after every "A" match, despite that the result would be discarded again for the next A match. Change the color matching to cache the location of each color line match. Discard the cache once the match offset passes that point. |
upstream/Fix seqset iterator when it ends in a comma.patch | (download) |
imap/util.c |
4 1 + 3 - 0 ! |
fix seqset iterator when it ends in a comma. |
upstream/Fix uudecode buffer overflow.patch | (download) |
handler.c |
4 2 + 2 - 0 ! |
fix uudecode buffer overflow. |
upstream/Fix gpgme crash when listing keys in a public key bl.patch | (download) |
crypt-gpgme.c |
18 11 + 7 - 0 ! |
[patch] fix gpgme crash when listing keys in a public key block. The gpgme code handling classic application/pgp assumed each key would have a uid. Change it to check for a missing uid list. Also change it to list every uid (instead of only the first), and to put each one on a "uid" line in the output. The output is only for display, so the format change won't affect other parts of the code. Thanks to Mikko Lehto for the high quality bug report, detailing the exact place of the crash with a reproducing example and a workaround patch. |
upstream/Fix public key block listing for old versions of gpg.patch | (download) |
crypt-gpgme.c |
6 6 + 0 - 0 ! |
[patch] fix public key block listing for old versions of gpgme. Commit 382355a5 accidentally removed the data import for legacy mode, which would cause it to produce empty output. |
upstream/Add a check for key uids in create_recipient_set.patch | (download) |
crypt-gpgme.c |
2 1 + 1 - 0 ! |
[patch] add a check for key->uids in create_recipient_set. For gpgme < 1.11.0, it used this function to create the encryption key |
upstream/Fix rfc2047 base64 decoding to abort on illegal char.patch | (download) |
rfc2047.c |
2 1 + 1 - 0 ! |
fix rfc2047 base64 decoding to abort on illegal characters. |
upstream/Check for NULL userhdrs.patch | (download) |
sendlib.c |
4 2 + 2 - 0 ! |
check for null userhdrs. |
upstream/Fix write_one_header illegal header check.patch | (download) |
sendlib.c |
2 1 + 1 - 0 ! |
fix write_one_header() illegal header check. |