Package: mpack
Version: 1.6-1
Severity: wishlist
Here we see several wishes:
$ echo wow|mpack -o /dev/stdout /dev/stdin
Subject: File exists
i.e., why no stdin, stdout options? Also don't prompt for subject if
stdin is not a terminal.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
> Subject: Re: Bug#768150: bar
Sorry for the bogus subject, it got confused in some copy-paste operations.
I do not know if I have the permission to change it.
Regards,
--
Nicolas George
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "uns
On Fri, 08 Aug 2008, ultrakiller wrote:
> Subject: linux-image-2.6.26-1-686 monitor button does not work in hp nx 6110
> Package: linux-image-2.6.26-1-686
> Severity: normal
hmm
how about providing some info?
like dmesg, last working kernel, first failing kernel!?
--
maks
@Nigel:
For upgrading between version you might take a look at #550321.
This is yet unresolved/not automated in Debian.
Backup/restore only works for backups/restores of the same version AFAIK.
Let's now stick to the subject here ;-)
--
To UNSUBSCRIBE, email to debian-bugs-dist
Sorry for the bad subject line in my last reply. I really was talking
about this bug, not the one I mentioned in my last subject line.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
package: sympa
version: 6.1.1~dfsg-1
Sympa sends email with subject "Listmaster / css_updated" on every update.
The content of the email is:
--snip--
Static CSS files have been updated ; check log file for details
--snap--
Regards
Racke
--
To UNSUBSCRIBE, email to debian
DEBUG: --
DEBUG: Processing email:
DEBUG: [No message id line found]
DEBUG: [No from line found]
DEBUG: [No subject line found]
DEBUG: [No subject line found]
DEBUG: Size: 0
DEBUG: Checking for early match or abort based on
Hi Sascha,
Sascha Silbe wrote:
> If To: contains a non-ASCII character, the Subject: header is RFC2047
> encoded even if it contains only ASCII characters:
>
> === Begin ===
> From: Sascha Silbe
> To: =?UTF-8?q?St=C3=A9phane=20Magnenat?=
> Subject: =?UTF-8?q?Patches=20f
Package: reportbug
Version: 5.0
Severity: wishlist
I'd much rather edit the mail subject in my editor, rather than in a
prompt provided by reportbug. (This holds particularly true when using
--mutt.) Thus, I'd like an option to disable the prompt for a subject.
If set, reportbug sh
Package: mhonarc
Version: 2.6.10-1
Severity: normal
*** Please type your report below this line ***
Mbox (echo =?us-ascii?B?`echo -n "base64 subj"|base64-encode`?=)
------
.....
Subject: =?us-ascii?B?YmFzZTY0IHN1Ymo=?=
.
-
om: [EMAIL PROTECTED] \(Debian Bug Tracking System\)$
* ^Subject: Bug#\/[0-9]*
|echo |mail "[EMAIL PROTECTED]"
# This handles bug reports on which I've had an effect via the control
# bot.
:0
* ^To: Justin Pryzby <[EMAIL PROTECTED]>$
* ^From: [EMAIL PROTECTED] \(Debian Bug Tracking S
, for example, "fails to send
email" or "does not start with -q option specified."
> d
as we intend to fix it later in the editor.
Then we forget to fix it in the editor.
Therefore, if you would allow blank, instead of
>
No subject specified; stopping.
The problem
Package: pootle
Version: 0.10.1-1
Severity: normal
Pootle should use correct encoding for Subject:
current version send
Subject: а аЕаГаИбббаАбаИб аВ Pootle
should send something like this:
Subject: =?UTF-8?B?...?=
-- System Information:
Debian Release: testing/unstable
APT prefers
Sounds reasonable -- thanks
I doubt though that it would be "fixed" in squeeze or wheezy versions
On Tue, 21 May 2013, Jochen Pawletta wrote:
> Package: fail2ban
> Version: 0.8.4-3+squeeze1
> Severity: wishlist
> Hi
> Please add the hostname to the subject of ou
Generate a certificate for a named client. A
>certificate/keypair will be generated for each client
>named on the command line.
>
> When generate is used the additional `--subject-alt-name` argument
> can be used. Th
On samedi 25 avril 2020 00:17:18 CEST you wrote:
> I have packages with patches maintained using gbp-pq, which wraps long
> first lines of commits, indenting the subsequent line with a single space,
> using that full (wrapped) line as the "Subject:".
On the other hand the DEP
It should also be pointed out that gnus internally modifies score
rules. When a user supplies this rule (after hitting "s" in the
*Agent Category* buffer:
(("subject" ("droid" -1 nil s)))
gnus stores it as:
(("((\"subject\" (\"droid\&quo
On Sun, May 20, 2007 at 01:33:08PM +0200, Antoine Cailliau <[EMAIL PROTECTED]>
wrote:
> Subject: iceweasel: Segmentation fault
> Package: iceweasel
> Version: 2.0.0.3-2
> Severity: grave
> Justification: renders package unusable
>
> Since update, iceweasel do no
Thanks for your problem report!
Quoting Gerald Turner :
However newer versions split this information into a separate 'subject'
field, which my XMPP client (Pidgin usually) ignores. It's also absent
from MUC group messages entirely.
True. I will either remove the subject aga
Package: lists.debian.org
Dear listmasters,
it has been a couple of days that the digests I receive are broken: the subject
is not displayed anymore, and the mail headers are moved after the main text.
Here is an example of what happens with mutt, but if bounce the message to a
mailbox opened by
tags 405311 + moreinfo
thanks
On Tuesday 02 January 2007 15:08, Janusz A. Urbanowicz wrote:
> Since sa-exim was enabled in the exim's config, it happens sometimes
> (about once a week on a very busy mail system) that the Subject: line of
> filtered messages is thrashed:
>
&g
wrote:
> retitle 363707 mozilla-thunderbird: long subject line display messed up -
> text gets wrapped if larger than label area
> severity 363707 normal
> thanks
>
> ok #363707 is "mozilla-thunderbird: long subject line display messed
> up - text gets wrapped if lar
Control: tag -1 moreinfo unreproducible
On Wed, 05 Dec 2012, YunQiang Su wrote:
> Then this will happen always and the subject will be longer and longer.
> It will also break the thread.
The only time threading uses the subject is if there aren't any
References: or In-Reply-To: head
* Paul Elliott [130822 04:15]:
> ++From: Paul Elliott
> ++Date: Wed, 21 Aug 2013 02:09:27 -0500
> ++Subject: =?UTF-8?q?harden=20library=20against=20buffer=20overflow=20attack?=
> ++ =?UTF-8?q?s=20on=20sprintf=0Acalls=20to=20sprintf=20with=20'%s'=20in=20fo?=
> +
On Tue, Oct 25, 2011 at 12:05, martin f krafft wrote:
> Package: reportbug
> Version: 6.2.1
> Severity: normal
>
> I just submitted #646571 and that only worked through some magic.
> The problem, which I only noticed much later, was that reportbug
> spawned mutt with a
age (such as php-cgi ...)" sounds awkward.
-php => /usr/bin, php(\d+), php$1-cli, 5, @NO_DEFAULT_DEPS@
+php => /usr/bin, php(\d+), php$1-cli, 5, php-cli
Shouldn't it be "php([\d.]+)" and s/5/7.0/?
Subject: [PATCH 2/6] dh-php5 is replaced by dh-php, and php5-dev by p
Package: debsecan
Version: 0.4.9
Severity: wishlist
Hi,
I have a low-memory host A which has its filesystem rsynced from a
"golden chroot" from another host B. Both copies of the filesystem run
cron, and therefore debsecan.
When debsecan runs in the chroot on B, it gets the subje
Maik Zumstrull schrieb am Wednesday, den 13. May 2009:
Hi,
> I sent the attached mail at 14:01 CET today. As of now (15:55) I have
> not received any reaction, so yes, I think my mails still get dropped.
>
> Maybe during your test, you used a client that enforces the existence
&g
d to wnpp these packages:
> >
<...>
> >
> > Looks like my wnpp reportbug got mangled such that every word in the
> > description is now listed as a wnpp package.
>
> This is because your ITP #543766 has a wrong subject, fixing with this mail
> too.
Shouldn't #
Control: reassign -1 git-buildpackage 0.9.14
Control: retitle -1 gbp-pq should not wrap long subjects
Thanks for following up on this one, that makes sense. In the mean
time, I'll try to keep those subject lines shorter when I control
them. I've reassigned the issue accordingly - no
Control: forcemerge 729995 -1
Control: block 729995 by 729998
On Sun, Dec 29, 2013 at 10:53 PM, slof wrote:
> Subject: gnash: no youtube films wanted to start, only spireling
> startindicator.
Install gnash from wheezy-backports.
http://backports.debian.org/Instructions/
One day,
Note to future bug reporters:
Apparently putting the Bug # at the start of the subject line will cause
submissions to the BTS to go to the bug report with the same # rather than the
package listed at the top of the body of the email.
-- Chris
--
Chris Knadle
chris.kna...@coredump.us
* j...@jbdenis.net wrote:
> Any advance on this subject ?
Since the initscripts are no longer installed by default, I supposed you could
consider it fixed.
I'm working through my backlog slowly, one of the items on my list is to
re-introduce an initscript that will at least mount cg
Subject: Corrected tarballs for Emacs 23.2 and 23.3.
https://lists.gnu.org/archive/html/info-gnu-emacs/2011-08/msg0.html
Subject: Letting the users off the hook
Body: The FSF hereby grants permission to distribute the ...
http://lists.gnu.org/archive/html/emacs-devel/2011-08/msg00035.html
I'm Sorry! This report should have been in the mail body, not in the subject:
When the harddisk is full and ephiphany-browser is closed, the bookmarks get
corrupted (some are missing) or are are lost completely.)
--
"Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX
Subject: upgrade-reports: SDL_ttf (dev) does not work after dist-upgrade
Package: upgrade-reports
Severity: normal
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell
Package: svnmailer
Version: 1.0.8-4
Severity: wishlist
by default svn-mailer lists all the modified files in Subject: and
does allow some configureability. sadly, there is no format to put the
first non empty line of the log, which is rather useful (and really more
than a file list).
--
To
tags 485583 unreproducible
thanks
Hi,
I tried to reproduce your bugreport about mails without subject to
majord...@lists.d.o being dropped. Unfortunatly I can't reproduce the
problem, my mail went through the filter without problems. Is the problem
still existing for you?
Thanks
ion in
their subject line to the control bot, it isn't visible to people
looking at the bug.
It would be useful to also display the Subject: line of a message which
is sent to the control bot address.
Thanks,
Anand
-- System Information:
Debian Release: testing/unstable
APT prefers te
On Tue, 7 Nov 2006 08:58:20 +0100
Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> [ ...60 lines of quoting deleted... ]
>
> Of course the archive is the object of the action, because lzop is
> the subject...
Thanks, very glad we agree.
> ...What is your point?
I add
, line 215, in ?
main()
File "/usr/bin/apt-listchanges", line 195, in main
apt_listchanges.mail_changes(config.email_address, changes, subject)
File "/usr/share/apt-listchanges/apt_listchanges.py", line 314, in
mail_changes
message = email.Messag
Package: rss2email
Version: 2.59-1
Severity: normal
I appear that for long blog titles/subject lines, rss2email screws
up the headers:
Date: Fri, 18 Aug 2006 02:27:11 +0200 (CEST)
From: ...
To: ...
Subject: Carlos Villegas: Insserv reordering and repeated init-scripts
Message-Id
e marked it as forwarded.
When replying to bugs please try to use a Subject line
that describes the bug (like the subject the bug
already has, "Nautilus fails to open LUKS-encrypted USB stick").
Here is what I got in my inbox:
From: tango salsa
Subject: Bug#765308: Bug 765308
whic
@@
to = to.encode("ascii", "replace")
subject = subject.encode("ascii", "replace")
body = body.encode("ascii", "replace")
-
+
+# If quotes are used for this MUA, escape the quotes in the arguments:
+if
Package: bugs.debian.org
Like I mentioned to ow...@bugs, all the PNG attachments I sent (from
122.127.*), cause the message to get dumped. E.g.,
To: sub...@bugs.debian.org
Subject: mess on the screen on the second file
Date: Tue, 30 Jun 2009 01:26:48 +0800
Message-ID: <87fxdjar3b@jidanni.
On Tue, 16 Jun 2009, Matthew Wakeling wrote:
Package: alpine
Version: 2.00+dfsg-2+b1
Severity: normal
Looks like not a Debian version, but okay...
I use alpine with my inbox set to threaded mode. Alpine wrongly assumes that
two messages
with the same subject must belong in the same
, $head->get('Received', 0), "\n";
@all_received = $head->get('Received');
### Print the subject, or the empty string if none:
print "Subject: ", $head->get('Subject',0), "\n";
Both of the print stat
message = email.Message.Message()
message.set_charset(charset)
- subject = unicode(subject.decode(locale.getlocale()[1] or 'ascii',
'replace'))
+subject = unicode(subject.decode(locale.getpreferredencoding() or 'ascii',
'replace'))
messag
Hi again,
two more questions bellow about details I'm unsure about in your
patch.
Kan-Ru Chen wrote (07 Apr 2011 06:55:10 GMT) :
> +add_header() {
> +local subject="$1";
> + echo "Subject: $subject";
> +echo "To: $EMAIL_ADDRESS";
&g
olved.
>
> What would you propose in an NMU? Can you please open a new bug report
> instead?
>
I was replying to 863293 and if you actually looked at the merge request
contents before closing instead of relying solely on the subject (which was
still the original subject before yo
olved.
>
> What would you propose in an NMU? Can you please open a new bug report
> instead?
>
I was replying to 863293 and if you actually looked at the merge request
contents before closing instead of relying solely on the subject (which was
still the original subject before yo
sing '-a' option
In my case, I did the following to solve the problem:
1. added the following line to /etc/cron.d/logcheck
LC_ALL=de_DE.UTF-8
2. changed sendreport() funtion in /usr/sbin/logcheck:
sendreport() {
MAILER=${MAILER:-mutt}
if [ $REBOOT
backport from upstream which avoids
output on stderr.
Sebastian
From: Matteo Corti
Date: Fri, 24 Nov 2023 13:20:59 +0100
Subject: [PATCH] First fix for the STDIN warning on OpenSSL 3.2.0
Applied-Upstream: https://github.com/matteocorti/check_ssl_cert/commit/2c2795860adc165c35f5948116261cb76a94c954
package: bugs.debian.org
473236: Found-In contains '0xab'
644945: Subject contains '0x95'
400153: Fixed-In contains '0xa0'
391560: Subject contains '0xff' '0xf4' '0xff' 0xfd'
107361: Found-In contains '0xa0'
117166:
AB> Actually you already reported the identical issue against wicd-curses
AB> (which likely has the same postrm as it comes from the same source
AB> package) using the very same subject (no package name in subject):
AB> https://bugs.debian.org/724031
OK please merge them for
* Joerg Sommrey <[EMAIL PROTECTED]> [2007-06-10 22:31]:
> If a webcalendar entry contains non-ascii characters, these characters
> are used unmodified in send_reminders.php for the Subject: header and
> thus may violate RFC 2822.
>
> Here is a trivial patch to circumvent thi
Subject: base: sound system failure
Package: base
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell
And here's another aspect of this problem: when I forward a message, the
Subject, Date, From, and To fields are empty in the forwarded message. See
below for an example. Thanks, Andrew.
Original Message
Subject:
Date:
From:
To:
22
Package: kmail
Version: 4.4.4.1
I have reported this to the Kontact maintainers. It is not a serious bug.
To reproduce it, begin composing an email and put a spelling error in the
subject line. From the tools menu, invoke the spell checker. The error will
not be recognized.
--
Nancy
tags 627148 + upstream
forwarded 627148 http://crbug.com/83342
quit
Thomas Renard wrote:
> [Subject: Bug#627148: (no subject)]
[jn: That's just as useless. :) No huge loss --- it just means
readers have to spend time figuring out which bug it is.]
> created upstream bug 83342.
tags 624814 + upstream
forwarded 624814 http://crbug.com/80071
quit
Raza Abbas wrote:
> [Subject: Bug#624814: Filed bug with chromium]
Thanks! Next time, please keep in mind that these appear as emails,
so the subject line can be used to provide valuable context.
> http://code.google
Package: markdown
Version: 1.0.2~b8-3
File: /usr/share/man/man1/markdown.1.gz
A proper NAME item looks like
NAME
cat - concatenate files and print on the standard output
That way
$ apropos markdown
Markdown (3) - (unknown subject)
markdown (1) - (unknown subject
+
> with message-id
>
> and subject line Sandra Tosi shared how to do it.
> has caused the Debian Bug report #878176,
> regarding reportbug: have a way to have a fake/mungled subject in order to
> have $editor start without needing to write subject
> to be marked as done.
ely after the header name (like "Subject:" rather
than "Subject: ") and accounts for line numbers in Vim starting at 1
(not 0).
In case a license statement is necessary: I hereby release the attached
file fold-mail.vim to the public domain.
best regards,
--
Kevin
2:10.0 +0200
> @@ -273,15 +273,19 @@
> rm -f "$RUNMAIL"
> fi
> if [ -f "$MAIL" ] ; then
> -if [ -z "$HOSTNAME" ]; then
> -HOSTNAME="$(uname -n)"
> - fi
> - SUBJECT="CRON-APT complet
MAILTO="$...@%%\?*}"
ARGS="$...@#*\?}"
[ "$ARGS" = "$MAILTO" ] && unset ARGS
MAILTO="$(echo "${MAILTO#mailto:}"; | url_unescape)"
subject=
cc=
bcc=
body=
mutt_commands=
IFS_store="$IFS"
IFS='&'
for arg
Package: reportbug
Version: 3.30
Severity: minor
Hi,
I just tried to file a bug with a subject line of:
Does not recognice unicode apostrophy (’)
but I got:
Please select tags: (one at a time) [none]
Traceback (most recent call last):
File "/usr/bin/reportbug", line 1745, in
Begin forwarded message:
> Resent-From: debian-powe...@lists.debian.org
> From: Dan DeVoto
> Subject: Re: Bug#728936 - Has anyone succeeded in installing Jessie on
> PowerPC?
> Date: December 8, 2013 11:16:29 PM PST
> To: Installer List Debian , Rick Thomas
>
>
Package: apticron
Version: 1.1.27
Severity: normal
Although /etc/apticron/apticron.conf allows setting of the SYSTEM variable
to override the hostname used in apticron mails, it does not make use of
this variable in the mail subject. Further more, it doesn't even use the
FQDN of the server
ossbuild/bootstrap/backport).
>
> --
> Kind regards,
> Luca Boccassi
> Subject: [PATCH 1/5] libsdbus-c++-dev: downgrade Depends on libsdbus-c++-bin
> to Suggests
>
> It is not actually necessary to use the library headers and link against
> the shared object, it's a useful dev
5.0.23 intelligent WHOIS client
Versions of packages fail2ban suggests:
ii mailutils [mailx] 1:2.1+dfsg1-7 GNU mailutils utilities for handli
-- Configuration Files:
/etc/fail2ban/action.d/sendmail-whois-lines.conf changed:
[Definition]
actionstart = printf %%b &
Hello.
This is what I did today. Maybe someone can follow my steps
and arrive at something.
I'm using this $HOME/.procmailrc file:
-
LOGFILE=$HOME/.cache/procmail.log
VERBOSE=yes
:0 h
SUBJECT=|formail -cXSubject:|cat
MYVAR=$SUBJECT
:0
/dev
On Fri, 2005-09-02 at 12:20 -0500, William Vera wrote:
> Thanks David!
>
> You can see the package in:
> http://billy.linuxmerida.org/debian/ninja/
>
> Greetings
Please remember to set the subject of all mail to something reasonable.
It is annoying "no subject" ma
package bazaar
retitle 298987 please add versioned build-dependency on diff
thanks my friend robot
On Fri, Mar 11, 2005 at 12:42:14AM +0100, Norbert Tretkowski said
> subject 298987 please add versioned build-dependency on diff
> thanks
>
> D'uh... I meant diff, not file.
>
Subject: installation-reports: Successful installation under VMWare on XP
Package: installation-reports
Severity: wishlist
Successful installation under VMWare 1.0.2 running on Windows XP
Professional.
-- Package-specific info:
-- System Information:
Debian Release: 4.0
APT prefers stable
retitle 392716 libdspam7-drv-mysql fails purging
severity 392716 serious
thanks
Douglas F. Calvert wrote:
I apologize that there is no subject. Subject should be
libdspam7-drv-mysql fails purging.
I was busy to merge the changes of the NMU back in, but I hadn't time to
completely te
regularly read post gatewayed
put subscribe subject message. Last
Fraser sfraser Beth Epperson beppe particular codearea newsgroup discussing
members regularly read post gatewayed put subscribe subject message.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe"
* bastien ROUCARIES , 2013-08-28, 19:11:
Subject: [lintian] Do you have test case good/bad of this
Please keep in mind that BTS messages appear as emails in a crowded inbox, so
the subject line can be a good place to put valuable context.
Do you have test case for this
No, sorry
Package: openjdk-7-jdk
Version: 7u51-2.4.6~pre1-1
Severity: wishlist
File: /usr/lib/jvm/java-7-openjdk-i386/man/man1/jar.1.gz
$ apropos jar
grepjar (1) - search files in a jar file for a pattern
jar (1) - (unknown subject) <- !
jardetector (1) - binfmt helper
(OK Dudes, I sent a perfectly good
Subject: add a =?utf-8?Q?Google=E2=84=A2?= Translate program #and got back
Subject: Re: Bug#576609: add a =?windows-1252?Q?Google=99?= Translate program
triggering my spam charset alarms!)
Thank you all for taking the time to pick the future winner out of the
reopen 515721
thanks
false close; as the subject of the previous message was new (rather than
an copying the subject line of the bug report), i ment it's a new bug
report, not an addition to the existing one, thus reopening.
--
Address:Daniel Baumann, Burgunderstrasse 3, CH
Subject: openoffice.org: Changelog on lenny/security not available
Package: openoffice.org
Version: 1:2.4.1+dfsg-1+lenny3
Severity: serious
Justification: Policy 4.4
There is no changelog available for openoffice.org's security update in Lenny.
Either from Aptitude or packages.debian.org
Package: python2.5
Version: 2.5.4-1
Severity: normal
from email.mime.text import MIMEText
from email.header import Header
msg = MIMEText('dummy')
h = Header('dummy\nX-Injected-Header: yes')
msg['Subject'] = h
print msg.as_string()
Content-Type: text/plain; charse
Package: reportbug-ng
Version: 0.2007.10.30
Severity: wishlist
Hi Basti,
we already talked about this, this is the wishlist bug so
you don't forget :) Having the package name in the subject
is especially useful when filtering mails on debian-bugs-dist
using the subject.
Kind regards
Package: quota
Version: 3.12-6
Severity: wishlist
Right now when the quota system sends emails, it leaves the subject
empty. It'd be nice if it supplied a descriptive subject line instead,
so I'd see something like "Over quota on /home/whatever" or "Over quota
on /f
Hello Elimar,
Are you native compiling on powerpc, aren't you? The crosscompiling
tag in the subject might lead to confusion, is it OK to rename the
subject without crosscompiling if you are not doing so?
Best regards,
--
Héctor Orón
"Our Sun unleashes tremendous flares expelli
I don't use esmtp any more, so I suggest that if it works for you
that's good enough. Looking back at the bug report, did you notice
that the problem was also with the Subject: header (or absence of
Subject header)? Hence, you may want to redo your tests before closing
the bug.
Hi Joël,
* BERTRAND Joël [2019-04-12 13:07]:
fetchmail: Subject CommonName: *.nerim.net
fetchmail: Subject Alternative Name: *.nerim.net
fetchmail: Subject Alternative Name: nerim.net
fetchmail: Server CommonName mismatch: *.nerim.net != pop.nerim.fr
The certificate is only issued for
Package: libunicode-map-perl
Version: 0.112-12+b3
Severity: minor
File: /usr/share/man/man3/Unicode::Map.3pm.gz
apropos(1) says "unknown subject":
$ apropos Unicode::Map
I18N::Charset (3pm) - IANA Character Set Registry names and Unicode::MapUTF8
(et al.) conversion scheme names
Un
> My recommendation is to use systemd-timesyncd if you want to use
> systemd-time-wait-sync (or disable the use systemd-time-wait-sync.service)
You seem to not have read more than the subject, where I made a
copy-and-paste-o. The entire *text* of the bug report is about
systemd-network
read:03ae Thu. 09:34 [4/7] Steve K Speicher, Arnaud Le Hors,
>> Michael Hausenblas| Erik Wilde, Kevin Page, armin.hal...@csiro.au;
>> ACTION-10: First Editor's Draft is available! (inbox ldpw3wg newinbox unread)
>
> There are several different subjects in the threa
Package: apticron
Version: 1.1.51
Severity: normal
Tags: patch
Hello,
Changes in Bug #621730 mean the number of packages do not get reported in the
subject of the email. MAILX_SUBJECT is defined before NUM_PACKAGES is known.
Moving the custom subject block after the NUM_PACKAGES definition
md64 (x86_64)
Kernel: Linux 4.2.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.6.2-3 (based on LLVM 3.6.2)
--- a/mime.c
+++ b/mime.c
@@ -3129,7 +3129,7 @@
// this will give us the 'main' subject of the
Package: mimedecode
Version: 1.9-4
Severity: normal
It took just somewhat over 4 years for someone to look into this bug :(
I suppose noone's interested in fixing it :(
Michele,
as you already discovered, the expression you used:
SUB=`formail -zx Subject: | mimedecode`
won't
; >> From: Debian FTP Masters
> >> To: 541549-cl...@bugs.debian.org
> >> Cc: bogofilter-tokyocabi...@packages.debian.org
> >> Subject: Bug#541549: fixed
> >>
> >> We believe that the bug you reported is now fixed; the following
> >> changes were
Yes\n" if $requestack==0;
$message .= "Subject: $subject\n"
. "Date: $date\n"
- . "X-BTS-Version: $version\n"
+ . "User-Agent: devscripts bts/$version\n"
. "Message-ID: <$msgid>\n"
g -s 'żółw' -O -o /dev/null
> >
> >$ yes '' | PAGER=cat reportbug reportbug -s 'żółw' -O -o /dev/null
> [snip]
> >(I removed some info not relevant here) except for the subject a bit
> >weird, it worked fine.
> That's really awkward: m
Package: ftp.debian.org
Severity: wishlist
Currently, the done mail melanie sends out, has 'Fixed' as subject.
This could be changed to something like:
"Removed {sourcepackage} source and binaries from {-s value}"
when -S nor -c nor -b nor -a are specified, where sour
Please ignore. I replied to the wrong message.
-Original Message-
From: [EMAIL PROTECTED], [EMAIL PROTECTED]
Date: Thursday, Jun 23, 2005 9:03 am
Subject: Re: Bug#315523: [wish] Support for aditional kernel parameters
I can stop by tomorrow morning and take care of this. I do need to
Package: rss2email
Severity: normal
When you get a title like this:
http://example.net/";>link
r2e generates invalid email because it uses html2text, which first
results in
"""link [1]
[1] http://example.net/""";
which is then copied into the subject v
201 - 300 of 8138 matches
Mail list logo
