Bug#625947: many CPANPLUS... - (unknown subject)
Package: perl-doc Version: 5.12.3-6 Severity: wishlist Many unknown subject, in contrast to other perl man pages. $ apropos cpan|grep unknown CPANPLUS::Backend (3perl) - (unknown subject) CPANPLUS::Backend::RV (3perl) - (unknown subject) CPANPLUS::Config (3perl) - (unknown subject) CPANPLUS::Config::System (3perl) - (unknown subject) CPANPLUS::Configure (3perl) - (unknown subject) CPANPLUS::Dist (3perl) - (unknown subject) ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663055: (no subject)
Any advance on this subject ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#822643: (no subject)
reportbug warn me with No subject found in message. Please edit again. but allows me to send it anyway, with 'y'. It should keep the previous subject.
Bug#890652: (no subject)
owner ! thanks
Bug#525849: (no subject)
Bug#306362: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#306216: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#306404: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#306172: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#306185: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#306328: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416204: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489032: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499851: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459127: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#112211: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400837: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295755: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#99324: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#99324: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#99324: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#92845: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#78447: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#339056: (no subject)
Sorry for that -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362911: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#30126: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262737: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464402: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#858445: Wrong subject
I submitted the bug with the wrong subject, sorry for that.
Bug#631944: comb man pages for bad apropos and notify each maintainer
Package: man-db Severity: wishlist I got a great idea that of course cannot be run by we little users with only part of the entire Debian installed. The idea is to comb the man pages with $ apropos .|grep unknown\ subject|tail tnameserv (1)- (unknown subject) jar (1) - (unknown subject) javaws (1) - (unknown subject) lunar (1)- (unknown subject) operator (7) - (unknown subject) sigevent (7) - (unknown subject) Tk::Tcl-perl (3pm) - (unknown subject) Term::UI::History (3perl) - (unknown subject) Unicode::Map (3pm) - (unknown subject) xorg.conf (5)- (unknown subject) and send bug reports about each offending page. E.g., for the latter: Package: xserver-xorg-core Version: 2:1.10.2-2 Severity: minor File: /usr/share/man/man5/xorg.conf.5.gz Dear sir, your man page causes apropos(1) to come up with unknown subject: $ apropos xorg.conf xorg.conf (5)- (unknown subject) Please fix it forthwith. Yours Truly, the Debian Man Page Team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#395496: pootle send registration email Subject without encoding
Nicolas François wrote: On Fri, Oct 27, 2006 at 03:36:56PM +0400, Max Kosmach wrote: Pootle should use correct encoding for Subject: current version send Subject: а аЕаГаИбббаАбаИб аВ Pootle should send something like this: Subject: =?UTF-8?B?...?= I patched my own server. It now sends an email with the following Subject: Subject: =?utf-8?b?0KDQtdCz0LjRgdGC0YDQsNGG0LjRjyDQsiBQb290bGU=?= (I attach the registration email) Yes, Subject is ok now -- With MBR Max CCSA/CCSE
Bug#1028356: procmail: Variable set with stdin pipe action fails leaving empty variable
Package: procmail Version: 3.24-1 Severity: normal I am very happy to see procmail upstream is now active again! Excellent news! I am a long time user and have quite a few mail filtering rules. The recent upgrade to 3.24 broke using a pipe action to set a variable using stdin. Reverting to 3.22 restores correct functioning. For example due to UTF-8 subject encoding one might find a subject with this contrived and constructed example. Subject: =?utf-8?q?test-list_post_from_rwp=40proulx=2Ecom_require?= =?utf-8?q?s_approval?= I use the following idiomatic procmail expression to decode that subject and place it into a SUBJECT variable. This following from my .procmailrc file. # If the subject is encoded and needs decoding then... # extract the subject, decode it, store in the SUBJECT variable. :0h * ^Subject:.*=\? SUBJECT=|formail -cXSubject: | perl -MEncode -pe 'Encode::from_to($_,"MIME-Header","UTF-8");' # Store all remaining cases of Subject: into $SUBJECT. # E - only execute this recipe if previous recipe was not executed. :0hE SUBJECT=|formail -cXSubject: # Here forward SUBJECT contains the decoded text. # Match it using the variable ?? syntax. # * SUBJECT ?? ^Subject: blah blah blah Then I use it like this following to handle Mailman messages. :0 * ^X-BeenThere: * SUBJECT ?? ^Subject: .*mailing list memberships reminder$ mailman-reminders/ :0 * ^X-List-Administrivia: yes { :0 * 1^0 SUBJECT ?? ^Subject: Auto-discard notification * 1^0 SUBJECT ?? ^Subject: El envio a [-a-zA-Z0-9]+ de.*precisa.*de.*aprobacion * 1^0 SUBJECT ?? ^Subject: Uncaught bounce notification * 1^0 SUBJECT ?? ^Subject: [-a-zA-Z0-9]+ post from * 1^0 SUBJECT ?? ^Subject: [-a-zA-Z0-9]+ subscription notification * 1^0 SUBJECT ?? ^Subject: [-a-zA-Z0-9]+ unsubscribe notification list-administrivia/ } Unfortunately in 3.24 this functionality is broken. I see in the Testing migration "excuses" this "Too young, only 4 of 5 days old". Should severity be "important" in order to keep Testing from breaking? Some experiments show to try to bound the condition. It's around the use of stdin to the sub-process. This following works. This does not use stdin. SUBJECT=|echo hello SUBJECT=|echo hello | tee /tmp/pt.rwp.debug SUBJECT=|sh -c "echo hello | tee /tmp/pt.rwp.debug" But this fails. (Using a cat| pipe to ensure $SHELLMETAS are seen.) This fails to process stdin. SUBJECT=|tee /tmp/pt.rwp.debug SUBJECT=|cat | tee /tmp/pt.rwp.debug SUBJECT=|sh -c "tee /tmp/pt.rwp.debug" SUBJECT=|sh -c "cat | tee /tmp/pt.rwp.debug" Thank you for maintaining procmail! :-) Bob -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages procmail depends on: ii libc6 2.36-8 Versions of packages procmail recommends: ii postfix [mail-transport-agent] 3.7.3-2+b1 procmail suggests no packages. -- no debconf information
Bug#487019: Please implement mode to ignore character encodings
Joey Schulze [EMAIL PROTECTED] writes: Could this be related to whether or not there are non-ASCII characters in the subject? Since the subject was 'diff' or 'subject' I doubt it. Mhem. printf 'äöü\n' | LANG=C ./mailx -s foobar $recipient will also drop the Subject line. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491180: Oops, wrong subject
The subject line was a copy/paste error, but everything else is correct. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298987: subject change
subject 298987 please add versioned build-dependency on diff thanks D'uh... I meant diff, not file. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474142: Subject: ITP: pdf2djvu -- PDF to DjVu converter
Subject: ITP: pdf2djvu -- PDF to DjVu converter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502329: Wrong subject
Excuse me, i've mistaken with the subject. If it is modifiable, please set it to something suitable. Something like default/apcupsd problem. -- sergio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585031: Patch
# diff /usr/share/perl5/MIME/Entity.pm /usr/share/perl5/MIME/Entity.pm.orig 264c264 subject to auto-submitted --- subject to -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627148: (no subject)
(sorry for the subject stuff, leave it empty for now) created upstream bug 83342. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#347976: reportbug: no subject specified; stopping
Package: reportbug Version: 3.18 Severity: wishlist Can there please be a way to avoid No subject specified; stopping. You see I want to fill in any subject and any X-Debbugs-CC's in the editor. Indeed, I'd be happy to fill in everything asked instead in the editor. I feel dorky having to give it Subject: a to proceed. One could alias reportbug=reportbug --subject=FIXME IN THE EDITOR etc. but dorky. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#242516: (no subject)
tags 242516 +fixed-upstream thanks This will be fixed as of 2.0.0. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341615: (no subject)
this bug is for the package mldonkey-server -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#252142: (no subject)
forward? https://savannah.gnu.org/bugs/?func=detailitemitem_id=15354 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343658: (no subject)
Thanks, this patch has solved the problem -- Pozdrawiam Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343677: (no subject)
Could you comment on this bug? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291628: (no subject)
I have seen this message too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337581: (no subject)
These 2 bugs are related. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#241530: (no subject)
Also seeing this problem in version 2.0pl5-11 which shipped with woody. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337068: (no subject)
I think this happens when the file doesn't exist. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338007: (no subject)
fixed in upcoming fetchmail 6.2.9-rc8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343423: (no subject)
This problem isn't specific to being run under /usr/bin/screen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#155334: (no subject)
Bugs #155334 and #316001 are related. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#155334: (no subject)
Bugs #160225, #155334 and #316001 are related. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303651: (no subject)
test -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303651: (no subject)
test -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345112: (no subject)
mysql and openssh also have this problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326971: (no subject)
Have you contacted upstream regarding this bug? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317511: (no subject)
Is there anything we can do about this bug? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392910: (no subject)
Severity: normal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390133: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388452: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#389270: (no subject)
Insufficient information to debug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400482: (no subject)
Sorry, I closed the wrong bug ;-) Re-openning... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#306171: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#306586: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#71879: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#128950: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#210243: subject discussion honoring Editors
50169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346629: (no subject)
:) Yes Amaya is working on it :) Regards Nico -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328165: (no subject)
Tag: moreinfo Is this only the case for ONE of your archives? or all of them? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494108: (no subject)
Fixed upstream by 6b8ec864; availability will be from pam_mount 1.0. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495177: (no subject)
Fixed upstream by commit b2d33430; availability will be from pam_mount 1.0. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496619: (no subject)
seconded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494107: (no subject)
Note: This is not in 0.44 but scheduled for the next. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#173277: (no subject)
Maybe it should say Continue [in simulation mode]?... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300759: (no subject)
Also remove Super cow insider jokes from --help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493314: (no subject)
reassign 493314 python-m2crypto thanks -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493234: (no subject)
Not a dup of #492333. Fixed upstream in v0.44-1-g795bd9d. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451561: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499851: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499925: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499879: (no subject)
It might depend on module loading order as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487842: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441975: (no subject)
tags 441975 - unreproducible reopen 441975 thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460184: (no subject)
See http://en.wiktionary.org/wiki/conformant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Unidentified subject!
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368665: (no subject)
tag 368665 patch thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411532: (no subject)
tag 411532 patch thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452610: (no subject)
What is still holding up this change? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#279399: (no subject)
This is probably the same as this upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=162638 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296211: (no subject)
reopen 296211 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#285390: (no subject)
You might find this inspiring: http://www.dpkg.org/ConffileHandling -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301301: (no subject)
eggtrayicon.c is Copyright (C) 2002 Anders Carlsson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#218262: (no subject)
Not fixed (at least for me) in rhythmbox 0.8.8-6. -James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298633: (no subject)
Correction: Server is running Debian Sid. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290796: (no subject)
Tags 290796 patch Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#302625: (no subject)
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#302631: (no subject)
changelog should note that this bug is also close -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#304254: (no subject)
/etc/cnews/whoami is also an improper conffile -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299531: (no subject)
merge 299756 299531 thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]