Bug#373541: (no subject)
Package: python-gnome Version: 1.4.5-4 Severity: important Hi, your package has been detected as generating a python module/extension that may need an upgrade to the new Python Policy[1]. A wiki page [2] explains what has to be done to upgrade your packages to the new Policy. This bug may be a false positive, in that case, please just close the bug. This bug is part of a mass bug filling, and its severity will be raised to serious when python will default to python2.4. Please note that this bug (even not being RC) falls under the 0-day NMU policy. [1] http://lists.debian.org/debian-devel-announce/2006/06/msg9.html [2] http://wiki.debian.org/DebianPython/NewPolicy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373360: (no subject)
Package: python-tclink Version: 3.4.0-2 Severity: important Hi, your package has been detected as generating a python module/extension that may need an upgrade to the new Python Policy[1]. A wiki page [2] explains what has to be done to upgrade your packages to the new Policy. This bug may be a false positive, in that case, please just close the bug. This bug is part of a mass bug filling, and its severity will be raised to serious when python will default to python2.4. Please note that this bug (even not being RC) falls under the 0-day NMU policy. [1] http://lists.debian.org/debian-devel-announce/2006/06/msg9.html [2] http://wiki.debian.org/DebianPython/NewPolicy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373452: (no subject)
Package: libmusicbrainz-2.1 Version: 2.1.2-5 Severity: important Hi, your package has been detected as generating a python module/extension that may need an upgrade to the new Python Policy[1]. A wiki page [2] explains what has to be done to upgrade your packages to the new Policy. This bug may be a false positive, in that case, please just close the bug. This bug is part of a mass bug filling, and its severity will be raised to serious when python will default to python2.4. Please note that this bug (even not being RC) falls under the 0-day NMU policy. [1] http://lists.debian.org/debian-devel-announce/2006/06/msg9.html [2] http://wiki.debian.org/DebianPython/NewPolicy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: sorry for the forgotten subject
Processing commands for [EMAIL PROTECTED]: > # sorry I forgot the Subject line for the mass bug filling > retitle 373401 Python policy transition Bug#373401: (no subject) Changed Bug title. > retitle 373402 Python policy transition Bug#373402: (no subject) Changed Bug title. > retitle 373403 Python policy transition Bug#373403: (no subject) Changed Bug title. > retitle 373404 Python policy transition Bug#373404: (no subject) Changed Bug title. > retitle 373405 Python policy transition Bug#373405: (no subject) Changed Bug title. > retitle 373406 Python policy transition Bug#373406: (no subject) Changed Bug title. > retitle 373407 Python policy transition Bug#373407: (no subject) Changed Bug title. > retitle 373408 Python policy transition Bug#373408: (no subject) Changed Bug title. > retitle 373409 Python policy transition Bug#373409: (no subject) Changed Bug title. > retitle 373410 Python policy transition Bug#373410: (no subject) Changed Bug title. > retitle 373411 Python policy transition Bug#373411: (no subject) Changed Bug title. > retitle 373412 Python policy transition Bug#373412: (no subject) Changed Bug title. > retitle 373413 Python policy transition Bug#373413: (no subject) Changed Bug title. > retitle 373414 Python policy transition Bug#373414: (no subject) Changed Bug title. > retitle 373415 Python policy transition Bug#373415: (no subject) Changed Bug title. > retitle 373418 Python policy transition Bug#373418: (no subject) Changed Bug title. > retitle 373419 Python policy transition Bug#373419: (no subject) Changed Bug title. > retitle 373420 Python policy transition Bug#373420: (no subject) Changed Bug title. > retitle 373421 Python policy transition Bug#373421: (no subject) Changed Bug title. > retitle 373422 Python policy transition Bug#373422: (no subject) Changed Bug title. > retitle 373423 Python policy transition Bug#373423: (no subject) Changed Bug title. > retitle 373424 Python policy transition Bug#373424: (no subject) Changed Bug title. > retitle 373425 Python policy transition Bug#373425: (no subject) Changed Bug title. > retitle 373426 Python policy transition Bug#373426: (no subject) Changed Bug title. > retitle 373427 Python policy transition Bug#373427: (no subject) Changed Bug title. > retitle 373428 Python policy transition Bug#373428: (no subject) Changed Bug title. > retitle 373429 Python policy transition Bug#373429: (no subject) Changed Bug title. > retitle 373430 Python policy transition Bug#373430: (no subject) Changed Bug title. > retitle 373431 Python policy transition Bug#373431: (no subject) Changed Bug title. > retitle 373432 Python policy transition Bug#373432: (no subject) Changed Bug title. > retitle 373433 Python policy transition Bug#373433: (no subject) Changed Bug title. > retitle 373434 Python policy transition Bug#373434: (no subject) Changed Bug title. > retitle 373435 Python policy transition Bug#373435: (no subject) Changed Bug title. > retitle 373436 Python policy transition Bug#373436: (no subject) Changed Bug title. > retitle 373437 Python policy transition Bug#373437: (no subject) Changed Bug title. > retitle 373438 Python policy transition Bug#373438: (no subject) Changed Bug title. > retitle 373439 Python policy transition Bug#373439: (no subject) Changed Bug title. > retitle 373440 Python policy transition Bug#373440: (no subject) Changed Bug title. > retitle 373441 Python policy transition Bug#373441: (no subject) Changed Bug title. > retitle 373442 Python policy transition Bug#373442: (no subject) Changed Bug title. > retitle 373443 Python policy transition Bug#373443: (no subject) Changed Bug title. > retitle 373444 Python policy transition Bug#373444: (no subject) Changed Bug title. > retitle 373445 Python policy transition Bug#373445: (no subject) Changed Bug title. > retitle 373446 Python policy transition Bug#373446: (no subject) Changed Bug title. > retitle 373447 Python policy transition Bug#373447: (no subject) Changed Bug title. > retitle 373448 Python policy transition Bug#373448: (no subject) Changed Bug title. > retitle 373449 Python policy transition Bug#373449: (no subject) Changed Bug title. > retitle 373450 Python policy transition Bug#373450: (no subject) Changed Bug title. > retitle 373451 Python policy transition Bug#373451: (no subject) Changed Bug title. > retitle 373452 Python policy transition Bug#373452: (no subject) Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: sorry for the forgotten subject
Processing commands for [EMAIL PROTECTED]: > # sorry I forgot the Subject line for the mass bug filling > retitle 373503 Python policy transition Bug#373503: (no subject) Changed Bug title. > retitle 373504 Python policy transition Bug#373504: (no subject) Changed Bug title. > retitle 373505 Python policy transition Bug#373505: (no subject) Changed Bug title. > retitle 373506 Python policy transition Bug#373506: (no subject) Changed Bug title. > retitle 373507 Python policy transition Bug#373507: (no subject) Changed Bug title. > retitle 373508 Python policy transition Bug#373508: (no subject) Changed Bug title. > retitle 373509 Python policy transition Bug#373509: (no subject) Changed Bug title. > retitle 373510 Python policy transition Bug#373510: (no subject) Changed Bug title. > retitle 373511 Python policy transition Bug#373511: (no subject) Changed Bug title. > retitle 373512 Python policy transition Bug#373512: (no subject) Changed Bug title. > retitle 373513 Python policy transition Bug#373513: (no subject) Changed Bug title. > retitle 373514 Python policy transition Bug#373514: (no subject) Changed Bug title. > retitle 373515 Python policy transition Bug#373515: (no subject) Changed Bug title. > retitle 373516 Python policy transition Bug#373516: (no subject) Changed Bug title. > retitle 373517 Python policy transition Bug#373517: (no subject) Changed Bug title. > retitle 373518 Python policy transition Bug#373518: (no subject) Changed Bug title. > retitle 373519 Python policy transition Bug#373519: (no subject) Changed Bug title. > retitle 373520 Python policy transition Bug#373520: (no subject) Changed Bug title. > retitle 373521 Python policy transition Bug#373521: (no subject) Changed Bug title. > retitle 373522 Python policy transition Bug#373522: (no subject) Changed Bug title. > retitle 373523 Python policy transition Bug#373523: (no subject) Changed Bug title. > retitle 373524 Python policy transition Bug#373524: (no subject) Changed Bug title. > retitle 373525 Python policy transition Bug#373525: (no subject) Changed Bug title. > retitle 373526 Python policy transition Bug#373526: (no subject) Changed Bug title. > retitle 373527 Python policy transition Bug#373527: (no subject) Changed Bug title. > retitle 373528 Python policy transition Bug#373528: (no subject) Changed Bug title. > retitle 373529 Python policy transition Bug#373529: (no subject) Changed Bug title. > retitle 373530 Python policy transition Bug#373530: (no subject) Changed Bug title. > retitle 373531 Python policy transition Bug#373531: (no subject) Changed Bug title. > retitle 373532 Python policy transition Bug#373532: Python policy transition Changed Bug title. > retitle 373533 Python policy transition Bug#373533: (no subject) Changed Bug title. > retitle 373534 Python policy transition Bug#373534: (no subject) Changed Bug title. > retitle 373535 Python policy transition Bug#373535: (no subject) Changed Bug title. > retitle 373536 Python policy transition Bug#373536: Update for new python policy Changed Bug title. > retitle 373537 Python policy transition Bug#373537: (no subject) Changed Bug title. > retitle 373538 Python policy transition Bug#373538: (no subject) Changed Bug title. > retitle 373539 Python policy transition Bug#373539: (no subject) Changed Bug title. > retitle 373540 Python policy transition Bug#373540: (no subject) Changed Bug title. > retitle 373541 Python policy transition Bug#373541: (no subject) Changed Bug title. > retitle 373542 Python policy transition Bug#373542: (no subject) Changed Bug title. > retitle 373543 Python policy transition Bug#373543: (no subject) Changed Bug title. > retitle 373544 Python policy transition Bug#373544: (no subject) Changed Bug title. > retitle 373545 Python policy transition Bug#373545: (no subject) Changed Bug title. > retitle 373546 Python policy transition Bug#373546: (no subject) Changed Bug title. > retitle 373547 Python policy transition Bug#373547: (no subject) Changed Bug title. > retitle 373548 Python policy transition Bug#373548: (no subject) Changed Bug title. > retitle 373549 Python policy transition Bug#373549: (no subject) Changed Bug title. > retitle 373550 Python policy transition Bug#373550: (no subject) Changed Bug title. > retitle 373551 Python policy transition Bug#373551: (no subject) Changed Bug title. > retitle 373552 Python policy transition Bug#373552: (no subject) Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cutter_1.03-1_amd64.changes ACCEPTED
Accepted: cutter_1.03-1.diff.gz to pool/main/c/cutter/cutter_1.03-1.diff.gz cutter_1.03-1.dsc to pool/main/c/cutter/cutter_1.03-1.dsc cutter_1.03-1_amd64.deb to pool/main/c/cutter/cutter_1.03-1_amd64.deb cutter_1.03.orig.tar.gz to pool/main/c/cutter/cutter_1.03.orig.tar.gz Announcing to debian-devel-changes@lists.debian.org Closing bugs: 372251 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of cutter_1.03-1_amd64.changes
cutter_1.03-1_amd64.changes uploaded successfully to localhost along with the files: cutter_1.03-1.dsc cutter_1.03.orig.tar.gz cutter_1.03-1.diff.gz cutter_1.03-1_amd64.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372251: marked as done (General cleanup: fixing CFLAGS, compiler warnings, lintian errors, ...)
Your message dated Wed, 14 Jun 2006 05:02:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#372251: fixed in cutter 1.03-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: cutter
Severity: normal
Tags: patch
The attached diff fixes the passing of CFLAGS from debian/rules to
the main Makefile. Without this fix, the CFLAGS set in debian/rules
(-Wall -g -O2) are not communicated down.
It also fixes an error in the manpage cutter(8), which produced an
error message in the `man` output.
Futher it updates the FSF address in debian/copyright.
It also cleans up the code a bit, fixing several compiler warnings.
3 correlated ones remain, though they are harmless, and the fix
looks rather stupid to me.
Lastly it updates Standards-Version to 3.7.2, no changes are
required AFAICS.
With this patch cutter is lintian and linda clean again.
HTH,
Christian Aichinger
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500,
'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-rc6-vs2.1.0-pre1-r20050817
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)
diff -Nur cutter-1.02.old/cutter.8 cutter-1.02/cutter.8
--- cutter-1.02.old/cutter.82006-06-09 06:20:02.0 +0200
+++ cutter-1.02/cutter.82006-06-09 07:11:25.0 +0200
@@ -5,7 +5,7 @@
.SH SYNOPSIS
.B cutter
.IR ipaddress1 \ [ \ port1 \ [ \ ipaddress2 \ [ \ port2
-.R ] \ ] \ ]
+\ ] \ ] \ ]
.br
.SH DESCRIPTION
.B Cutter
diff -Nur cutter-1.02.old/cutter.c cutter-1.02/cutter.c
--- cutter-1.02.old/cutter.c2003-06-16 21:35:02.0 +0200
+++ cutter-1.02/cutter.c2006-06-09 06:42:29.0 +0200
@@ -57,6 +57,7 @@
#include
#include
#include
+#include
#define ETHHDR sizeof(struct ethhdr)
#define TCPHDR sizeof(struct tcphdr)
@@ -149,7 +150,6 @@
int getmac(in_addr_t ip, uchar *mac)
{
FILE *id = fopen( "/proc/net/arp", "r" );
- union { uchar c[4]; in_addr_t n; } ipu;
in_addr_t ipn;
int mac0, mac1, mac2, mac3, mac4, mac5;
int hwtype, flags;
@@ -240,7 +240,7 @@
u_short toport
)
{
- int i_result, raw_sock, rtn;
+ int i_result, raw_sock;
in_addr_t gateway_ip;
struct sockaddr_ll myaddr, hisaddr;
struct tpack tpack;
@@ -377,7 +377,7 @@
for ( ; time(0) < tstart + 15; ) { // give the peer 15 seconds to
respond
struct sockaddr_ll gotaddr;
- int addrlen = sizeof(gotaddr);
+ unsigned int addrlen = sizeof(gotaddr);
fd_set readfds;
struct timeval tv;
diff -Nur cutter-1.02.old/debian/control cutter-1.02/debian/control
--- cutter-1.02.old/debian/control 2006-06-09 06:20:02.0 +0200
+++ cutter-1.02/debian/control 2006-06-09 07:14:44.0 +0200
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Blars Blarson <[EMAIL PROTECTED]>
Build-Depends: debhelper (>= 4.0.0)
-Standards-Version: 3.6.1
+Standards-Version: 3.7.2
Package: cutter
Architecture: any
diff -Nur cutter-1.02.old/debian/copyright cutter-1.02/debian/copyright
--- cutter-1.02.old/debian/copyright2006-06-09 06:20:02.0 +0200
+++ cutter-1.02/debian/copyright2006-06-09 07:16:50.0 +0200
@@ -19,9 +19,9 @@
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
- along with this package; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
- 02111-1307, USA.
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
+ 02110-1301 USA
On Debian GNU/Linux systems, the complete text of the GNU General
Public License can be found in `/usr/share/common-licenses/GPL'.
diff -Nur cutter-1.02.old/debian/rules cutter-1.02/debian/rules
--- cutter-1.02.old/debian/rules2006-06-09 06:20:02.0 +0200
+++ cutter-1.02/debian/rules2006-06-09 06:34:53.0 +0200
@@ -33,7 +33,7 @@
dh_testdir
# Add here commands to compile the package.
- $(MAKE)
+ $(MAKE) CFLAGS="$(CFLAGS)"
touch build-stamp
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: cutter
Source-Version: 1.03-1
We believe
Bug#373649: enscript sh and ksh highlighting problem with escaped quotes
Package: enscript
Version: 1.6.4-7
Binary package hint: enscript
Take the following script:
#!/usr/bin/ksh
echo \"foo=bar\"/\"baz=quux\"
echo "and here's some other stuff"
for i in foo bar baz quux
do
echo $i
done
...which I've also attached. In gview, those escaped double-quotes are
handled properly, and syntax hightlighting works. With enscript, using
either sh or ksh highlighting, the first double-quote turns on the
highlighting for "this is quoted stuff", but the rest are ignored until
the first unescaped double-quote is encountered.
The enscript command line was "cat enscriptbug | enscript
--highlight=ksh --color -r -p enscriptbug.ps"
Attached is a patch. I submitted this bug in Malone since it affects
Ubuntu, and found that the package maintainer listed there is an
invalid debian.org address; might want to address that too. Also
submitted to gnu.org, but no response.
--
Shawn McMahon| "I can see the light at the end of the tunnel.
EIV Consulting | And now that I have some light, I can see the
http://www.eiv.com | tunnel needs painting too." - Steve Jackson
diff -Naur enscript-1.6.4.orig/states/hl/ksh.st enscript-1.6.4/states/hl/ksh.st
--- enscript-1.6.4.orig/states/hl/ksh.st2006-06-04 07:53:21.0
-0400
+++ enscript-1.6.4/states/hl/ksh.st 2006-06-04 07:54:24.0 -0400
@@ -34,6 +34,17 @@
reference_face (false);
}
+ /* Ignore escaped quote marks */
+ /\\\"/ {
+language_print ($0);
+ }
+ /\\\'/ {
+language_print ($0);
+ }
+ /\\\`/ {
+language_print ($0);
+ }
+
/* Keywords:
(build-re '(: alias bg break continue cd command eval exec exit export
fc fg getopts hash jobs kill let login newgrp print pwd read readonly
diff -Naur enscript-1.6.4.orig/states/hl/sh.st enscript-1.6.4/states/hl/sh.st
--- enscript-1.6.4.orig/states/hl/sh.st 2006-06-04 07:53:21.0 -0400
+++ enscript-1.6.4/states/hl/sh.st 2006-06-04 07:54:39.0 -0400
@@ -30,6 +30,17 @@
reference_face (false);
}
+ /* Ignore escaped quote marks */
+ /\\\"/ {
+language_print ($0);
+ }
+ /\\\'/ {
+language_print ($0);
+ }
+ /\\\`/ {
+language_print ($0);
+ }
+
/* Keywords. */
/\b(CDPATH|HOME|IFS|MAIL((CHECK)?|(PATH)?)|P(ATH|S(1|2))|SH(ACCT|ELL)|\
break|c(ase|d|ontinue)|do(ne)?|e(cho|lse|sac|val|x(ec|it|port))|f(i|or)|\
pgpsaortJZrvn.pgp
Description: PGP signature
Bug#373672: libjpeg-mmx: CVE-2006-3005: memory exhaustion
Package: libjpeg-mmx
Severity: important
Tags: security patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
CVE-2006-3005: "The JPEG library in media-libs/jpeg before 6b-r7 on
Gentoo Linux is built without the -maxmem feature, which could allow
context-dependent attackers to cause a denial of service (memory
exhaustion) via a crafted JPEG file that exceeds the intended memory
limits."
Although the CVE is Gentoo-specific, Debian's libjpeg-mmx is not built
with --maxmem enabled, making it vulnerable. I have attached a trivial
patch to enable --maxmem to the same limit used in libjpeg62. The
Gentoo bug report mentioned in the CVE [1] contains a more elaborate
patch [2] that limits the maximum amount of allocatable memory to 95% of
physical memory. I believe the second patch is the better solution -
libjpeg62 sets maxmem to 1024MB, and that doesn't help much when mem +
swap is less than 1024 (the sample exploit image attached to the Gentoo
bug starts my computer thrashing).
Neither the Woody nor the Sarge version build with --maxmem and are
vulnerable.
Please mention the CVE in your changelog.
Thanks,
Alec
[1] http://bugs.gentoo.org/show_bug.cgi?id=130889
[2] http://bugs.gentoo.org/attachment.cgi?id=88029&action=view
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEkJN3Aud/2YgchcQRAv7UAKCL3GLZjODa6PbqNNlJe6Wdq0XMxQCfb3j7
Ykn3VKh6AClF8pIAaSBn8/Q=
=Dx7A
-END PGP SIGNATURE-
--- debian/rules2006-06-14 17:04:51.387093389 -0500
+++ debian/rules.new2006-06-14 17:04:46.338577763 -0500
@@ -5,7 +5,7 @@
configure: configure-stamp
configure-stamp:
dh_testdir
- ./configure --prefix=/usr --mandir=\$${prefix}/share/man
--infodir=\$${prefix}/share/info
+ ./configure --prefix=/usr --mandir=\$${prefix}/share/man
--infodir=\$${prefix}/share/info --enable-maxmem=1024
touch configure-stamp
sawfish_1.3+cvs20060518-2_i386.changes REJECTED
Rejected: sawfish_1.3+cvs20060518-2.dsc refers to sawfish_1.3+cvs20060518.orig.tar.gz, but I can't find it in the queue or in the pool. === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of sawfish_1.3+cvs20060518-2_i386.changes
sawfish_1.3+cvs20060518-2_i386.changes uploaded successfully to localhost along with the files: sawfish_1.3+cvs20060518-2.dsc sawfish_1.3+cvs20060518-2.diff.gz sawfish-lisp-source_1.3+cvs20060518-2_all.deb sawfish_1.3+cvs20060518-2_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
