Bug#410610: marked as done (ttf-mph-2b-damase: contains glyphs from a non-free font)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2007 06:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410610: fixed in ttf-mph-2b-damase 001.000.dfsg.1-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: ttf-mph-2b-damase
Version: 001.000-1
Severity: serious
Justification: contains non-free glyphs

The attached messages indicate that some of the glyphs in
ttf-mph-2b-damase will need to be stripped.

This may or may not be possible with the latest fontforge:

(12:07:52) pabs: oh, yeah, I should probably update the debian package
to remove the Sylheti glyphs, are you able to do that and send me a new
copy? I'd have to do it with fontforge and I don't know if it would be
able to preserve all the font features you used
(12:08:49) mark: I don't have a font application that supports plane 1,
so it would ruin the font if I did it. I had to send it out to James
Kass for the p1 support.
(12:09:03) pabs: oh, hmm
(12:09:21) mark: But I didn't use any special features that would be
ruined, I don't think
(12:10:29) pabs: ok, well, I'll try with fontforge, we'll see though :)
(12:10:58) mark: ok

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
--- Begin Message ---
Everyone -

> Mark Williamson <[EMAIL PROTECTED]> is the author and he released it
> into the public domain...

Far be it from me to discourage development of free fonts, but I don't think
Mark has the rights to release it into the public domain. In a quick look at
the font, I saw many font styles I recognised - including ones that are not
currently under free licenses. For example, the Sylheti Nagri glyphs are an
identical copy (node for node, coordinate for coordinate) of the Sylheti
font available from http://www.sylheti.org.uk/page5.html. That font is
freeware, but is not under public domain, or any FLOSS license.

I hate to sound like the font police, but this font is not legal, as it
contains copyrighted material from other fonts without any acknowledgement.
I'm not at all implying that Mark intentionally intended to breach
copyright, as it is particularly common in South Asia to find fonts that
have been copied with the copyright stripped out, replaced with public
domain. Mark may have copied glyphs from one of those fonts. I just think
someone ought to do a little more research to be sure that all the contents
are truly free. It may even be that some of Mark's sources could be
convinced to release OFL versions of their fonts!

If we want to get the typographic community's support behind free and open
source fonts, we have to prove to them that we honour copyright. Otherwise
all our arguments fall flat, and designers will run from FLOSS and the OFLB
like the plague. 

V.

-
Victor Gaultney
SIL International


--- End Message ---
--- Begin Message ---
On Sun, 2007-02-11 at 15:17 +, Victor Gaultney wrote:

> > Mark Williamson <[EMAIL PROTECTED]> is the author and he released it
> > into the public domain...
> 
> Far be it from me to discourage development of free fonts, but I don't think
> Mark has the rights to release it into the public domain.

(11:53:52) mark: I don't remember copying that font. I suppose it's
possible, I know I used it for information about the script
(11:54:32) mark: But if necessary, Sylheti can be removed from the font,
or new glyphs can be designed. Simply "recognizing font styles" doesn't
imply any sort of breach of copyright
(11:56:30) mark: The Latin, Hebrew, Greek, Cyrillic, Arabic glyphs are
all original, as are the Glagolitic, Gothic, Linear B, Cypriot, because
I actually still have the designs for all of those
(11:57:01) mark: The other ones, I'd have to check to make sure
(11:57:06) mark: But I was sure the entire font was my work
(11:57:25) mark: One sec
(11:58:38) mark: ok... the arabic glyphs are original, but in most apps
if you type them it will show up as your system's default arabic font
because there aren't OpenType tables for it
(12:02:32) mark: but after a cursory look, it appears eveything's
original (most of the ranges are typified by uneven contours because I
didn't "finish" the glyph outlines off)
(12:02:41) mark: except for Sylheti
(12:03:46) pabs: thanks for the info, I'll let you know of any more
questions
(12:03:50) mark: ok :-)

> If we want to get the typographic community's support behind free and open
> source fonts, we have to prove to them that we honour copyright. Otherwise
> all our arguments fall flat, and designers will run from FLOSS and the OFLB
> like the plague. 

Indeed.

-- 
bye,
pa

Bug#410871: marked as done (postfix: Postfix 2.3.7-1 install broken on unstable)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2007 05:47:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410871: fixed in postfix 2.3.7-2
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: postfix
Version: 2.3.7-1
Severity: serious


Postfix 2.3.7-1 is broken on the unstable, could not be installed:

Setting up postfix (2.3.7-1) ...
dpkg: error processing postfix (--configure):
 subprocess post-installation script returned error exit status 20
Errors were encountered while processing:
 postfix
E: Sub-process /usr/bin/dpkg returned an error code (1)
 A package failed to install.  Trying to recover:
Setting up postfix (2.3.7-1) ...
dpkg: error processing postfix (--configure):
 subprocess post-installation script returned error exit status 20
Errors were encountered while processing:
 postfix

Someone else seems to have the same issue (dutch forum):
http://gathering.tweakers.net/forum/list_messages/1197751

When I run /var/lib/dpkg/info/postfix.postinst configure it just exits
like that with no debug:

exit 20/var/lib/dpkg/info/postfix.postinst configure

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.2-grsec
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages postfix depends on:
ii  adduser   3.102  Add and remove users and groups
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  dpkg  1.13.25package maintenance system for Deb
ii  libc6 2.3.6.ds1-11   GNU C Library: Shared libraries
ii  libdb4.3  4.3.29-7   Berkeley v4.3 Database Libraries [
ii  libsasl2-22.1.22.dfsg1-8 Authentication abstraction library
ii  libssl0.9.8   0.9.8c-4   SSL shared libraries
ii  lsb-base  3.1-23 Linux Standard Base 3.1 init scrip
ii  netbase   4.29   Basic TCP/IP networking system
ii  ssl-cert  1.0.14 Simple debconf wrapper for openssl

Versions of packages postfix recommends:
ii  mailx [mail-read 1:8.1.2-0.20050715cvs-1 A simple mail user agent
ii  mutt [mail-reade 1.5.13-1.1  text-based mailreader supporting M

-- debconf information excluded

--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 2.3.7-2

We believe that the bug you reported is fixed in the latest version of
postfix, which is due to be installed in the Debian FTP archive:

postfix-cdb_2.3.7-2_i386.deb
  to pool/main/p/postfix/postfix-cdb_2.3.7-2_i386.deb
postfix-dev_2.3.7-2_all.deb
  to pool/main/p/postfix/postfix-dev_2.3.7-2_all.deb
postfix-doc_2.3.7-2_all.deb
  to pool/main/p/postfix/postfix-doc_2.3.7-2_all.deb
postfix-ldap_2.3.7-2_i386.deb
  to pool/main/p/postfix/postfix-ldap_2.3.7-2_i386.deb
postfix-mysql_2.3.7-2_i386.deb
  to pool/main/p/postfix/postfix-mysql_2.3.7-2_i386.deb
postfix-pcre_2.3.7-2_i386.deb
  to pool/main/p/postfix/postfix-pcre_2.3.7-2_i386.deb
postfix-pgsql_2.3.7-2_i386.deb
  to pool/main/p/postfix/postfix-pgsql_2.3.7-2_i386.deb
postfix_2.3.7-2.diff.gz
  to pool/main/p/postfix/postfix_2.3.7-2.diff.gz
postfix_2.3.7-2.dsc
  to pool/main/p/postfix/postfix_2.3.7-2.dsc
postfix_2.3.7-2_i386.deb
  to pool/main/p/postfix/postfix_2.3.7-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
LaMont Jones <[EMAIL PROTECTED]> (supplier of updated postfix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 13 Feb 2007 21:47:27 -0700
Source: postfix
Binary: postfix-pcre postfix postfix-pgsql postfix-doc postfix-ldap postfix-cdb 
postfix-dev postfix-mysql
Architecture: all i386 source 
Version: 2.3.7-2
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones <[EMAIL PROTECTED]>
Changed-By: LaMont Jones <[EMAIL PROTECTED]>
Description: 
 postfix- A high-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-dev - Postfix 

Bug#410754: marked as done (version `GLIBC_2.4' not found (required by /usr/bin/rar))

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2007 05:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410754: fixed in rar 1:3.7b1-2
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: rar
Version: 1:3.7b1-1
Severity: grave
Justification: renders package unusable

rar 3.7b1 which came from 
ftp://ftp.us.debian.org/debian/pool/non-free/r/rar/rar_3.7b1-1_i386.deb
fails to start with the following error:
/usr/bin/rar: /lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by 
/usr/bin/rar)

Until there is glibc 2.4 in debian, debian rar package should provide 
statically linked binary (called 'rar_static' 
in the upstream distribution).

Max

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages rar depends on:
ii  libc6   2.3.6.ds1-11 GNU C Library: Shared libraries
ii  libgcc1 1:4.1.1-21   GCC support library
ii  libstdc++6  4.1.1-21 The GNU Standard C++ Library v3

rar recommends no packages.

-- debconf-show failed

--- End Message ---
--- Begin Message ---
Source: rar
Source-Version: 1:3.7b1-2

We believe that the bug you reported is fixed in the latest version of
rar, which is due to be installed in the Debian FTP archive:

rar_3.7b1-2.diff.gz
  to pool/non-free/r/rar/rar_3.7b1-2.diff.gz
rar_3.7b1-2.dsc
  to pool/non-free/r/rar/rar_3.7b1-2.dsc
rar_3.7b1-2_i386.deb
  to pool/non-free/r/rar/rar_3.7b1-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Meredith <[EMAIL PROTECTED]> (supplier of updated rar package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 14 Feb 2007 05:04:48 +
Source: rar
Binary: rar
Architecture: source i386
Version: 1:3.7b1-2
Distribution: unstable
Urgency: high
Maintainer: Martin Meredith <[EMAIL PROTECTED]>
Changed-By: Martin Meredith <[EMAIL PROTECTED]>
Description: 
 rar- Archiver for .rar files
Closes: 410754
Changes: 
 rar (1:3.7b1-2) unstable; urgency=high
 .
   * Install rar_static instead of rar as rar binary (Closes: 410754)
Files: 
 d65810215b97fa92e6bcefdeeac05b07 568 non-free/utils optional rar_3.7b1-2.dsc
 bbb3795be605fbed6fcb43977315d38a 7770 non-free/utils optional 
rar_3.7b1-2.diff.gz
 25541de1fdaa57356af53dc3fc9889c3 506198 non-free/utils optional 
rar_3.7b1-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF0p212tp5zXiKP0wRAtOrAJ93YLAmWB86IbvXEbroZIEuRgSVYQCfb9Y7
EA+oe/3qH7uumYjqIhVlRvg=
=SPmT
-END PGP SIGNATURE-

--- End Message ---

Bug#410871: postfix: work arround the error

[Kam-Ming Siu]

Package: postfix
Version: 2.3.7-1
Followup-For: Bug #410871

Installed xinetd can solve this problem. 

And I found that line 212 of postfix.postinst stop the script. Trace it down, 
confmodule returns a message, the message is 

'20 Unsupported command "restarting" (full line was "Restarting internet
superserver: inetd* Not starting internet superserver: no services
enabled.") received from confmodule.'

I don't know the usage of debconf, I guess this is something changed in
debconf, such that cause this problem.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20
Locale: LANG=zh_HK.UTF-8, LC_CTYPE=zh_HK.UTF-8 (charmap=UTF-8)

Versions of packages postfix depends on:
ii  adduser   3.102  Add and remove users and groups
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  dpkg  1.13.25package maintenance system for Deb
ii  libc6 2.3.6.ds1-11   GNU C Library: Shared libraries
ii  libdb4.3  4.3.29-7   Berkeley v4.3 Database Libraries [
ii  libsasl2-22.1.22.dfsg1-8 Authentication abstraction library
ii  libssl0.9.8   0.9.8c-4   SSL shared libraries
ii  lsb-base  3.1-23 Linux Standard Base 3.1 init scrip
ii  netbase   4.29   Basic TCP/IP networking system
ii  ssl-cert  1.0.14 Simple debconf wrapper for openssl

Versions of packages postfix recommends:
ii  icedove [mail-reader]1.5.0.9.dfsg1-1 free/unbranded thunderbird mail cl

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#409878: marked as done (nginx_0.5.11-1(ia64/unstable): FTBFS: compile errors)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2007 04:32:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#409878: fixed in nginx 0.5.12-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: nginx
Version: 0.5.11-1
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of nginx_0.5.11-1 on caballero by sbuild/ia64 98
> Build started at 20070206-0034

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 5), autotools-dev, libpcre3-dev, zlib1g-dev

[...]

>   -o objs/src/core/ngx_times.o \
>   src/core/ngx_times.c
> gcc -c -O -pipe  -O -W -Wall -Wpointer-arith -Wno-unused-parameter 
> -Wno-unused-function -Wunused-variable -Wunused-value -Werror -g  -I src/core 
> -I src/event -I src/event/modules -I src/os/unix -I objs \
>   -o objs/src/core/ngx_shmtx.o \
>   src/core/ngx_shmtx.c
> src/core/ngx_shmtx.c:38:73: error: macro "ngx_open_file" requires 4 
> arguments, but only 3 given
> src/core/ngx_shmtx.c: In function 'ngx_shmtx_create':
> src/core/ngx_shmtx.c:38: error: 'ngx_open_file' undeclared (first use in this 
> function)
> src/core/ngx_shmtx.c:38: error: (Each undeclared identifier is reported only 
> once
> src/core/ngx_shmtx.c:38: error: for each function it appears in.)
> make[2]: *** [objs/src/core/ngx_shmtx.o] Error 1
> make[2]: Leaving directory `/build/buildd/nginx-0.5.11'
> make[1]: *** [build] Error 2
> make[1]: Leaving directory `/build/buildd/nginx-0.5.11'
> make: *** [build] Error 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=ia64&pkg=nginx&ver=0.5.11-1


--- End Message ---
--- Begin Message ---
Source: nginx
Source-Version: 0.5.12-1

We believe that the bug you reported is fixed in the latest version of
nginx, which is due to be installed in the Debian FTP archive:

nginx_0.5.12-1.diff.gz
  to pool/main/n/nginx/nginx_0.5.12-1.diff.gz
nginx_0.5.12-1.dsc
  to pool/main/n/nginx/nginx_0.5.12-1.dsc
nginx_0.5.12-1_i386.deb
  to pool/main/n/nginx/nginx_0.5.12-1_i386.deb
nginx_0.5.12.orig.tar.gz
  to pool/main/n/nginx/nginx_0.5.12.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jose Parrella <[EMAIL PROTECTED]> (supplier of updated nginx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 12 Feb 2007 19:37:07 -0400
Source: nginx
Binary: nginx
Architecture: source i386
Version: 0.5.12-1
Distribution: unstable
Urgency: low
Maintainer: Jose Parrella <[EMAIL PROTECTED]>
Changed-By: Jose Parrella <[EMAIL PROTECTED]>
Description: 
 nginx  - small, but very powerful and efficient web server
Closes: 409878
Changes: 
 nginx (0.5.12-1) unstable; urgency=low
 .
   * New upstream version fixes FTBFS problems in non-x86 archs
 (Closes: #409878)
Files: 
 2389fb56586f79e9869ae0c4d59b2a18 598 web optional nginx_0.5.12-1.dsc
 5712f5d8eb215733fbafd59aeccab118 455485 web optional nginx_0.5.12.orig.tar.gz
 2f275674574817ad0155c42f808e1963 5637 web optional nginx_0.5.12-1.diff.gz
 af98fc5441b710b4811ced6e82958af4 192038 web optional nginx_0.5.12-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFF0oz4ipBneRiAKDwRAjV7AKCPJCOZNG0LF8lCUrEv9xBH8DX/lgCfUMvX
9BAfN6dV9P7KUE6R9ACcTLU=
=xt29
-END PGP SIGNATURE-

--- End Message ---

Bug#410830: upstart version 0.3.5 seems to work

[Brian M. Carlson]

I'm not the original submitter, but I experienced the same problem[0].
I built and installed 0.3.5, and it works very nicely.  Even
Ctrl-Alt-Del works.  The machine now shuts down and boots without a
hitch.

[0] Of course, it happened at the most inconvenient time.

-- 
Brian M. Carlson / Brian with Sandals: Houston, Texas, US
Before emailing: http://crustytoothpaste.ath.cx/~bmc/me/contact/email
There is no We: http://crustytoothpaste.ath.cx/~bmc/writings/tinw
OpenPGP: RSA v3 2048 560553E7: FE82 7C9F EB21 5436 2F96 25BA 927B 0A51


signature.asc
Description: Digital signature

Processed: tagging 410497

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 410497 + pending
Bug#410497: sparc32 kernel is too big, fails to boot
There were no tags set.
Tags added: pending

>
End of message, 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]

Bug#400835: marked as done (r-omegahat-ggobi: dead link in copyright + empty package?)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2007 03:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#400835: fixed in rggobi 2.1.4-2-1etch1
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: r-omegahat-ggobi
Version: 2.1.4-2-1
Severity: normal

The copyright file refers to http://www.omegahat.org/Rggobi.
That link doesn't work for more; I presume it's dead.

Hmm, maybe there are bigger problems: The package list doesn't seem to include 
any "real" files.
$ dpkg -L r-omegahat-ggobi
/.
/usr
/usr/lib
/usr/lib/R
/usr/lib/R/site-library
/usr/share
/usr/share/doc
/usr/share/doc/r-omegahat-ggobi
/usr/share/doc/r-omegahat-ggobi/copyright
/usr/share/doc/r-omegahat-ggobi/changelog.Debian.gz
$ find /usr/lib/R/ -name '*gobi*'
# got nothing

>From within R, library("ggobi") got nothing (it's not entirely clear
what name to try).  Neither did r-omegahat-ggobi, nor Rggobi.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages r-omegahat-ggobi depends on:
ii  ggobi   2.1.4-1  Data visualization system for high
ii  r-base-core 2.4.0.20061103-1 GNU R core of statistical computin
ii  r-cran-rgtk22.8.6-1  GNU R binding for Gtk2

r-omegahat-ggobi recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: rggobi
Source-Version: 2.1.4-2-1etch1

We believe that the bug you reported is fixed in the latest version of
rggobi, which is due to be installed in the Debian FTP archive:

r-omegahat-ggobi_2.1.4-2-1etch1_i386.deb
  to pool/main/r/rggobi/r-omegahat-ggobi_2.1.4-2-1etch1_i386.deb
rggobi_2.1.4-2-1etch1.diff.gz
  to pool/main/r/rggobi/rggobi_2.1.4-2-1etch1.diff.gz
rggobi_2.1.4-2-1etch1.dsc
  to pool/main/r/rggobi/rggobi_2.1.4-2-1etch1.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dirk Eddelbuettel <[EMAIL PROTECTED]> (supplier of updated rggobi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 13 Feb 2007 20:52:42 -0600
Source: rggobi
Binary: r-omegahat-ggobi
Architecture: source i386
Version: 2.1.4-2-1etch1
Distribution: testing-proposed-updates
Urgency: medium
Maintainer: Dirk Eddelbuettel <[EMAIL PROTECTED]>
Changed-By: Dirk Eddelbuettel <[EMAIL PROTECTED]>
Description: 
 r-omegahat-ggobi - GNU R package for the GGobi data visualization system
Closes: 400835
Changes: 
 rggobi (2.1.4-2-1etch1) testing-proposed-updates; urgency=medium
 .
   * Backport of the change in 2.1.4-2-2 (of 28 Nov 2006) -- this change
 is minimal and affects only debian/rules where two 'overriding' variables
 need to be set so that the cdbs stanza /usr/share/R/debian/r-cran.mk
 can be used correctly on this package from the Omagehat (and not CRAN)
 upstream repository.  I also added one lintian cleanup (see below).
 .
   * Thanks for Ben Burton for suggesting it, and for Steve Langasek to give
 it an initial thumbs-up.  This package should go into testing as the
 freeze caught the badly broken (i.e. empty) version 2.1.4-2-1.
 .
   * debian/control: Remove Depends: entry as ggobi_2.1.4 has correct shlibs
 .
   * The original changelog entry from 2.1.4-2.2 follows.
 .
   * debian/rules: Also reset $debRlib for non-CRAN package (Closes: #400835)
Files: 
 067f3c8ff283a612dbea9c22b4ce7e65 673 math optional rggobi_2.1.4-2-1etch1.dsc
 ad3d59e36b2f0333e9b7bef24b4356c1 5453 math optional 
rggobi_2.1.4-2-1etch1.diff.gz
 823c349d683e050e30bfbfc5e82f52d8 459860 math optional 
r-omegahat-ggobi_2.1.4-2-1etch1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF0n3eCZSR95Gw07cRAgsKAJ93riQeRDOJaftVM7dbSdZjJVHoDACcCNnO
y+CwPCq98Qn1JIPpvVDSeZg=
=JoPU
-END PGP SIGNATURE-

--- End Message ---

Bug#410871: postfix: Postfix 2.3.7-1 install broken on unstable

[Alexandre Ahmim-Richard]

Steve Langasek wrote:

Is this a new install of the package, or an upgrade?



Originaly it was an upgrade, but in that case it is a "new install" 
because I tried to remove postfix, flush all files and directory concerned.



Your report apparently excluded all debconf information, but this is almost
certainly a problem related to debconf and those values may be relevant to
understanding this bug.  Can you please forward this information?  The
output of "reportbug --debconf --template postfix" should be sufficient.



OK, I attached it to this email.




When I run /var/lib/dpkg/info/postfix.postinst configure it just exits
like that with no debug:



exit 20/var/lib/dpkg/info/postfix.postinst configure


Please edit /var/lib/dpkg/info/postfix.postinst to add "set -x" as the
second line, and then try running it manually and capture the output.



I attached the output to this email, with this usefull debug we can see 
that the script ends on:
+ RET='20 Unsupported command "restarting" (full line was "Restarting 
internet superserver: inetd* Not starting internet superserver: no 
services enabled.") received from confmodule.'

+ case ${_db_internal_line%%[   ]*} in
+ return 20

I do not run any daemon through inetd, do I have to use postfix with it 
? I don't think so, postfix can run properly without inetd.


This script should detect it and do not ask to restart inetd. If i 
comment out the line 176 to 178 the script ends properly and postfix 
runs perfectly :


if [ -x /usr/sbin/update-inetd ]; then
update-inetd --disable smtp
fi

I think the "if [ -x /usr/sbin/update-inetd ]" clause is not adapted 
here, I think it should grep if the smtp service is activated in inetd.conf.


Anyway, thanks for the help !
I hope it'll be fixed on the next release. :)
--
Alexandre Ahmim-Richard
-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.2-grsec
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages postfix depends on:
ii  adduser   3.102  Add and remove users and groups
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  dpkg  1.13.25package maintenance system for Deb
ii  libc6 2.3.6.ds1-11   GNU C Library: Shared libraries
ii  libdb4.3  4.3.29-7   Berkeley v4.3 Database Libraries [
ii  libsasl2-22.1.22.dfsg1-8 Authentication abstraction library
ii  libssl0.9.8   0.9.8c-4   SSL shared libraries
ii  lsb-base  3.1-23 Linux Standard Base 3.1 init scrip
ii  netbase   4.29   Basic TCP/IP networking system
ii  ssl-cert  1.0.14 Simple debconf wrapper for openssl

Versions of packages postfix recommends:
ii  mailx [mail-read 1:8.1.2-0.20050715cvs-1 A simple mail user agent
ii  mutt [mail-reade 1.5.13-1.1  text-based mailreader supporting M

-- debconf information:
  postfix/master_upgrade_warning:
  postfix/db_upgrade_warning: true
* postfix/mailname: valheru
  postfix/tlsmgr_upgrade_warning:
  postfix/dynamicmaps_upgrade_warning:
  postfix/recipient_delim: +
* postfix/main_mailer_type: Local only
  postfix/transport_map_warning:
* postfix/append_dot_mydomain: false
  postfix/relayhost:
  postfix/procmail: false
  postfix/bad_recipient_delimiter:
* postfix/chattr: false
* postfix/root_address: NONE
  postfix/rfc1035_violation: false
  postfix/mydomain_warning:
  postfix/mynetworks: 127.0.0.0/8, 192.168.1.0/24, 192.168.2.0/24, 
82.230.253.116
* postfix/destinations: valheru, localhost.localdomain, clope.net, 
valheru.clope.net, localhost, gforge.esiea.fr
  postfix/nqmgr_upgrade_warning:
  postfix/not_configured:
  postfix/mailbox_limit: 0
  postfix/protocols: ipv4
+ . /usr/share/debconf/confmodule
++ '[' '!' '' ']'
++ PERL_DL_NONLAZY=1
++ export PERL_DL_NONLAZY
++ '[' '' ']'
++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/postfix.postinst 
configure
+ . /usr/share/debconf/confmodule
++ '[' '!' 1 ']'
++ '[' -z '' ']'
++ exec
++ '[' '' ']'
++ exec
++ DEBCONF_REDIR=1
++ export DEBCONF_REDIR
+ CHROOT=/var/spool/postfix
+ config_directory=/etc/postfix
+ . /usr/share/postfix/postinst.functions
+++ lsb_release -is
+++ echo Debian
++ DISTRO=Debian
+ umask 022
+ '[' configure = configure ']'
+ ldconfig
+ case "$1" in
+ OLDVERSION=
+ CHANGES=
+ NEWALIASES=y
+ update-rc.d postfix defaults
+ '[' -x /usr/sbin/update-inetd ']'
+ update-inetd --disable smtp
+ ldconfig
+ dpkg-divert --package postfix --remove --rename --divert 
/usr/share/man/man8/smtpd.real.8.gz /usr/share/man/man8/smtpd.8.gz
+ '[' -d /etc/postfix/sasl ']'
+ cd /etc/postfix/sasl
+ for file in smtp smtpd
+ '[' -r sasl-smtp.conf ']'
+ for file in smtp smtpd
+ '[' -r sasl-smtpd.conf ']'
+ cd /var/spool/postfix
+ makedir private root:root 700
+ '[' '!' -

Bug#410821: mysql-server-5.0: mysqld dies with '*** glibc detected *** double free or corruption (!prev): 0x08dd1dd0 ***'

[Steve Langasek]

On Tue, Feb 13, 2007 at 06:46:22PM +0100, Jonas Meurer wrote:
> I already did this 'stack trace':

> [ copied the 0x... hex digits to mysqld.stack]
> # cp /usr/share/doc/mysql-server-5.0/mysqld.sym.gz
> # gzip -d mysqld.sym.gz
> # resolve_stack_dump -s mysqld.sym -n mysqld.stack
> 0x81c0649 handle_segfault + 681
> 0xb7cfb947 _end + -1352585609
> 0xb7cfd0c9 _end + -1352579591
> 0xb7d30fda _end + -1352366838
> 0xb7d3889f _end + -1352335921
> 0xb7d38942 _end + -1352335758
> 0x8484df3 free_root + 67
> 0x81dbc5d _Z16dispatch_command19enum_server_commandP3THDPcj + 509
> 0x81dd188 _Z10do_commandP3THD + 136
> 0x81ddb94 handle_one_connection + 2308
> 0xb7f640bd _end + -1350060563
> 0xb7d9e93e _end + -1351917970

Could you try running mysqld under valgrind?  It's likely in this scenario
that the bug lies far away from the point where glibc detects it; valgrind
is usually the best way to find out where that is.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Downgrade

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 409841 important
Bug#409841: /usr/bin/oocalc: openoffice.org-calc freezes after editing a single 
cell
Severity set to `important' from `grave'

> 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: Re: Bug#410703: SIGINT corrupts storage file

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 410703 important
Bug#410703: SIGINT corrupts storage file
Severity set to `important' from `grave'

> 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]

Bug#409841: Downgrade

[Philippe Cloutier]

severity 409841 important
thanks

Downgrading while waiting for evidence of grave severity from submitter.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410703: SIGINT corrupts storage file

[Steve Langasek]

severity 410703 important
thanks

On Tue, Feb 13, 2007 at 10:30:03AM +, martin f krafft wrote:
> also sprach Steve Langasek <[EMAIL PROTECTED]> [2007.02.13.0204 +]:
> > Could you clarify how this is "data loss"?  Does the
> > reinitialization step do anything except for populating a new
> > cache of the remote state?

> Yes, it resets the local cache to zero, meaning that all remote
> files will be overwritten. The only other alternative is to set the
> cache to "full" meaning that only changes from now on will be
> overwritten, or to initialise the cache from the remote, losing all
> local changes.

> But my mind's not set on grave. I'd be happy if you thought this was
> important only.

Ok.  It sounds to me like the real data loss that happens here is of the
sync state, to the extent that this constitutes persistent data.  That's
inconvenient and annoying because it leaves the user with manual work to be
done to restore the site to a 100% syncable state, but any data loss beyond
that would be the result of user error, not a direct consequence of this
bug.

So I'm going ahead and downgrading.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410866: marked as done (Upgrading destar rewrites /etc/asterisk/destar_cfg.py if it's already present.)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 17:10:46 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410866: Upgrading destar rewrites 
/etc/asterisk/destar_cfg.py if it's already present.
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: destar
Version: 0.2.0-3
Severity: grave

The file /etc/asterisk/destar_cfg.py contains configuration information
modified by the user, rewriting it with an example will cause its data loss.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8)

--- End Message ---
--- Begin Message ---
On Tue, Feb 13, 2007 at 04:34:01PM -0500, Alejandro Rios P. wrote:
> Package: destar
> Version: 0.2.0-3
> Severity: grave

> The file /etc/asterisk/destar_cfg.py contains configuration information
> modified by the user, rewriting it with an example will cause its data loss.

Nothing in the destar package automatically rewrites this config file.  It
is marked as a conffile under the control of the Debian package, and the
only adjustments made to the file in the maintainer scripts are to change
the file owner.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/
--- End Message ---

Bug#410871: postfix: Postfix 2.3.7-1 install broken on unstable

[Steve Langasek]

On Wed, Feb 14, 2007 at 02:06:51AM +0100, Alexandre Ahmim-Richard wrote:
> Postfix 2.3.7-1 is broken on the unstable, could not be installed:

> Setting up postfix (2.3.7-1) ...
> dpkg: error processing postfix (--configure):
>  subprocess post-installation script returned error exit status 20
> Errors were encountered while processing:
>  postfix
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>  A package failed to install.  Trying to recover:
> Setting up postfix (2.3.7-1) ...
> dpkg: error processing postfix (--configure):
>  subprocess post-installation script returned error exit status 20
> Errors were encountered while processing:
>  postfix

Is this a new install of the package, or an upgrade?

Your report apparently excluded all debconf information, but this is almost
certainly a problem related to debconf and those values may be relevant to
understanding this bug.  Can you please forward this information?  The
output of "reportbug --debconf --template postfix" should be sufficient.

> Someone else seems to have the same issue (dutch forum):
> http://gathering.tweakers.net/forum/list_messages/1197751

> When I run /var/lib/dpkg/info/postfix.postinst configure it just exits
> like that with no debug:

> exit 20/var/lib/dpkg/info/postfix.postinst configure

Please edit /var/lib/dpkg/info/postfix.postinst to add "set -x" as the
second line, and then try running it manually and capture the output.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: tagging 410850, bug 410850 is forwarded to http://bugs.kde.org/show_bug.cgi?id=138499

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 410850 + upstream
Bug#410850: CVE-2006-6980: magnatune shell escapes
Tags were: patch security
Tags added: upstream

> forwarded 410850 http://bugs.kde.org/show_bug.cgi?id=138499
Bug#410850: CVE-2006-6980: magnatune shell escapes
Noted your statement that Bug has been forwarded to 
http://bugs.kde.org/show_bug.cgi?id=138499.

>
End of message, 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]

Bug#410871: postfix: Postfix 2.3.7-1 install broken on unstable

[Alexandre Ahmim-Richard]

Package: postfix
Version: 2.3.7-1
Severity: serious


Postfix 2.3.7-1 is broken on the unstable, could not be installed:

Setting up postfix (2.3.7-1) ...
dpkg: error processing postfix (--configure):
 subprocess post-installation script returned error exit status 20
Errors were encountered while processing:
 postfix
E: Sub-process /usr/bin/dpkg returned an error code (1)
 A package failed to install.  Trying to recover:
Setting up postfix (2.3.7-1) ...
dpkg: error processing postfix (--configure):
 subprocess post-installation script returned error exit status 20
Errors were encountered while processing:
 postfix

Someone else seems to have the same issue (dutch forum):
http://gathering.tweakers.net/forum/list_messages/1197751

When I run /var/lib/dpkg/info/postfix.postinst configure it just exits
like that with no debug:

exit 20/var/lib/dpkg/info/postfix.postinst configure

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.2-grsec
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages postfix depends on:
ii  adduser   3.102  Add and remove users and groups
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  dpkg  1.13.25package maintenance system for Deb
ii  libc6 2.3.6.ds1-11   GNU C Library: Shared libraries
ii  libdb4.3  4.3.29-7   Berkeley v4.3 Database Libraries [
ii  libsasl2-22.1.22.dfsg1-8 Authentication abstraction library
ii  libssl0.9.8   0.9.8c-4   SSL shared libraries
ii  lsb-base  3.1-23 Linux Standard Base 3.1 init scrip
ii  netbase   4.29   Basic TCP/IP networking system
ii  ssl-cert  1.0.14 Simple debconf wrapper for openssl

Versions of packages postfix recommends:
ii  mailx [mail-read 1:8.1.2-0.20050715cvs-1 A simple mail user agent
ii  mutt [mail-reade 1.5.13-1.1  text-based mailreader supporting M

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410833: Patch for bug

[Stephen Gran]

This is a Works For Me(TM) patch for this bug.  There look to be plenty
of other compiler warnings left over that need to be fixed, but as this
is a targetted fix, I left them for now.

--- avscan-1.3.1-openssl.orig/avscan/avscanop.c
+++ avscan-1.3.1-openssl/avscan/avscanop.c
@@ -218,6 +218,7 @@
 )
 {
gint status2;
+unsigned int cl_options = CL_SCAN_STDOPT;
gchar *s;
struct stat stat_buf;
ClamAVData *d = (ClamAVData *)g_malloc0(
@@ -297,9 +298,10 @@
return(NULL);
}

-   status2 = cl_loaddbdir(
+   status2 = cl_load(
d->database_path,
-   &d->database, &d->database_entries
+   &d->database, &d->database_entries,
+cl_options
);
}
else
@@ -314,9 +316,10 @@
return(NULL);
}

-   status2 = cl_loaddb(
+   status2 = cl_load(
d->database_path,
-   &d->database, &d->database_entries
+   &d->database, &d->database_entries,
+cl_options
);
}
if((status2 != 0) || (d->database == NULL) || (d->database_entries <= 
0))
@@ -564,9 +567,6 @@
status = 59;
break;
  case CL_EZIP:
-   status = 59;
-   break;
- case CL_EMALFZIP:
status = 51;
break;
  case CL_EGZIP:
@@ -656,6 +656,7 @@
struct dirent *dent;
struct stat stat_buf;
DIR *dp;
+unsigned int cl_options = CL_SCAN_STDOPT;


/* Interrupted? */
if(*stop_count > 0)
@@ -738,14 +739,16 @@
 #else
if(FALSE)
 #endif
-   status2 = cl_loaddbdir(
+   status2 = cl_load(
d->database_path,
-   &d->database, &d->database_entries
+   &d->database, &d->database_entries,
+cl_options
);
else
-   status2 = cl_loaddb(
+   status2 = cl_load(
d->database_path,
-   &d->database, &d->database_entries
+   &d->database, &d->database_entries,
+cl_options
);
if((status2 != 0) || (d->database == NULL) ||
   (d->database_entries <= 0)
only in patch2:
unchanged:
--- avscan-1.3.1-openssl.orig/avscan/windb.c
+++ avscan-1.3.1-openssl/avscan/windb.c
@@ -222,7 +222,7 @@
 static gint WinDBGetPatternStatsFindIterate(
 win_struct *win,
const gchar *name,
-struct cl_node *clam_pnode,
+struct cl_engine *clam_pnode,
 guint8 **pattern_rtn,
 gint *pattern_length_rtn,
 gulong *last_updated_time_rtn,
@@ -246,15 +246,18 @@
if(clam_pnode == NULL)
return(1);

+   if(clam_pnode->root != NULL) {
/* Iterate through Extended Boyer-Moore list */
-   if(clam_pnode->bm_suffix != NULL)
+
+struct cli_matcher *root = *clam_pnode->root;
+   if(root->bm_suffix != NULL)
{
gint i;
struct cli_bm_patt *pattern;

-   for(i = 0; clam_pnode->bm_suffix[i] != NULL; i++)
+   for(i = 0; root->bm_suffix[i] != NULL; i++)
{
-   for(pattern = clam_pnode->bm_suffix[i];
+   for(pattern = root->bm_suffix[i];
pattern != NULL;
pattern = pattern->next
)
@@ -290,16 +293,17 @@
}

/* Extended Aho-Corasick */
-   if(clam_pnode->ac_nodes > 0)
+
+   if(root->ac_nodes > 0)
{
gint i;
struct cli_ac_node *clam_ac_node;

/* Iterate through Extended Aho-Corasick list */
-   for(i = 0; i < clam_pnode->ac_nodes; i++)
+   for(i = 0; i < root->ac_nodes; i++)
{
/* Get this Extended Aho-Corasick node */
-   clam_ac_node = clam_pnode->ac_nodetable[i];
+   clam_ac_node = root->ac_nodetable[i];
if((clam_ac_node != NULL) ?
(clam_ac_node->list != NULL) : FALSE
)
@@ -477,6 +481,7 @@
}
}
}
+}

 #undef PROCESS_FIND

@@ -655,20 +660,23 @@
  } \
 }

+   if(clam_pnode->root != NULL) {
/* Iterate through Extended Boyer-Moore list */
-   if((clam_pnode->bm_suffix != NULL) && (win->stop_count == 0))
+
+struct cli_matcher *root = *clam_pnode->root;
+   if((root->bm_suffix != NULL) && (win->stop_count == 0))
{
gchar *pattern_label;
struct cli_bm_patt *pattern;
GtkCTreeNode *node, *pnode2;

   for(i = 0; clam_pnode->bm_suffix[i] != NULL; i++)
+   for(i = 0; root->bm_suffix[i] != NULL; i++)

Bug#370186: hal: HAL keeps CD drive spinning constantly

[Steve Langasek]

On Tue, Feb 13, 2007 at 12:57:57PM +0100, Daniel Schepler wrote:
> On Tuesday 13 February 2007 02:16:24 am you wrote:
> > I've cc:ed everyone who followed up to this bug report reporting the same
> > symptoms.  Daniel, Jürgen, could you please post the model info for your
> > CDROMs as returned in the info.product string in lshal's output, so that it
> > can be used in the future to provide a more refined override that might
> > even be worth enabling by default in the package?

> My drive's model is "HL-DT-ST DVD-RW GCA-4080N".  And I can confirm that the 
> instructions posted to the bug are working for me.

Cool, let's go ahead and include that in the patch as well.  Updated patch
attached, and updated version again uploaded to gluck.

Sjoerd, I guess this means we have a complete set of model info for those
users that have reported the problem, so if you would prefer to enable the
overrides by default for these three models, that seems like it would be a
decent option too.  (I would recommend making this override a conffile under
/etc/ still, since some users may have updated firmware for these devices
that doesn't suffer from the bug and want to override in the other
direction.)

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/
diff -u hal-0.5.8.1/debian/README.Debian hal-0.5.8.1/debian/README.Debian
--- hal-0.5.8.1/debian/README.Debian
+++ hal-0.5.8.1/debian/README.Debian
@@ -13 +13,13 @@
- -- Sjoerd Simons <[EMAIL PROTECTED]>
+
+ Some CD and DVD drives, such as the GDR8162B model found in some Dell 
+ laptops, do not correctly handle media status inquiries and incorrectly
+ spin up the drive when they should not.  Since hal regularly polls CD
+ drives for media changes, this results in increased power consumption and
+ mechanical wear and tear on such drives, which remain spinning constantly
+ while hal is running.
+
+ If you have a CD/DVD drive exhibiting this problem, you can copy
+ /usr/share/doc/hal/examples/no-cd-media-check.fdi to /etc/hal/fdi/policy/ to
+ disable media checks for your drive.  This file disables media checks for
+ all CD drives on the system, and also includes an example config for
+ disabling media checks only on a specific drive.
diff -u hal-0.5.8.1/debian/changelog hal-0.5.8.1/debian/changelog
--- hal-0.5.8.1/debian/changelog
+++ hal-0.5.8.1/debian/changelog
@@ -1,3 +1,13 @@
+hal (0.5.8.1-6.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * High-urgency upload for RC bugfix.
+  * Provide /usr/share/doc/hal/examples/no-cd-media-check.fdi as an example
+for disabling CD ROM media checks, and document this in README.Debian, as
+a workaround for CD drives with broken firmware.  Closes: #370186.
+
+ -- Steve Langasek <[EMAIL PROTECTED]>  Mon, 12 Feb 2007 16:42:29 -0800
+
 hal (0.5.8.1-6) unstable; urgency=low
 
   * debian/patches/19_sonypi_support.patch
only in patch2:
unchanged:
--- hal-0.5.8.1.orig/debian/hal.examples
+++ hal-0.5.8.1/debian/hal.examples
@@ -0,0 +1 @@
+debian/no-cd-media-check.fdi
only in patch2:
unchanged:
--- hal-0.5.8.1.orig/debian/no-cd-media-check.fdi
+++ hal-0.5.8.1/debian/no-cd-media-check.fdi
@@ -0,0 +1,41 @@
+ 
+
+
+
+
+
+  
+
+  
+
+  
+
+
+  
+
+  
+
+  
+  
+
+  
+
+  
+  
+
+  
+
+  
+
+
+

Bug#410866: Upgrading destar rewrites /etc/asterisk/destar_cfg.py if it's already present.

[Alejandro Rios P.]

Package: destar
Version: 0.2.0-3
Severity: grave

The file /etc/asterisk/destar_cfg.py contains configuration information
modified by the user, rewriting it with an example will cause its data loss.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: tagging 410833

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.27
> tags 410833 + confirmed
Bug#410833: FTBFS: error: 'CL_EMALFZIP' undeclared
Tags were: sid
Tags added: confirmed

>
End of message, 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]

Bug#409636: patch for this bug

[Stephen Gran]

This is a Works For Me (TM) patch.  I notice there are plenty of other
compiler warnings that should be fixed, but as this is just a targetted
bug fix patch, I let them be for now.

--- klamav-0.38.orig/src/dbviewer.cpp
+++ klamav-0.38/src/dbviewer.cpp
@@ -788,7 +788,8 @@

 unsigned int ret= 0;
 unsigned int no = 0;
-struct cl_node *root = NULL;
+struct cl_engine *root = NULL;
+unsigned int cl_options = CL_SCAN_STDOPT;
 QStringList lastDownloadPaths;
 QString dbdir;
 QString db;
@@ -799,7 +800,7 @@
 dbdir = lastDownloadPaths.first();


-ret = cl_loaddbdir((const char *)dbdir, &root, &no);
+ret = cl_load((const char *)dbdir, &root, &no, cl_options);
 //kdDebug() << "no " << no << endl;
 cl_free(root);
 return no;
only in patch2:
unchanged:
--- klamav-0.38.orig/src/klammail/clamdmail.c
+++ klamav-0.38/src/klammail/clamdmail.c
@@ -94,9 +94,10 @@
 unsigned long int size = 0;
 long double mb;
 const char *virname;
-struct cl_node *root = NULL;
+struct cl_engine *root = NULL;
 struct cl_limits limits;
 struct stat sb;
+unsigned int cl_options = CL_SCAN_STDOPT;



@@ -192,13 +193,13 @@
 stat(getargc(opt, 'd'), &sb);
 switch(sb.st_mode & S_IFMT) {
 case S_IFREG:
-if((ret = cl_loaddb(getargc(opt, 'd'), 
&root, &no))) {
+if((ret = cl_load(getargc(opt, 'd'), 
&root, &no, cl_options))) {
 mprintf("@%s\n", 
cl_strerror(ret));
 return 50;
 }
 break;
 case S_IFDIR:
-if((ret = cl_loaddbdir(getargc(opt, 
'd'), &root, &no))) {
+if((ret = cl_load(getargc(opt, 'd'), 
&root, &no, cl_options))) {
 mprintf("@%s\n", 
cl_strerror(ret));
 return 50;
 }
only in patch2:
unchanged:
--- klamav-0.38.orig/src/freshklam.cpp
+++ klamav-0.38/src/freshklam.cpp
@@ -821,7 +821,8 @@
 QString  Freshklam::getCurrentDBDir(){
 unsigned int ret= 0;
 unsigned int no = 0;
-struct cl_node *root = NULL;
+struct cl_engine *root = NULL;
+unsigned int cl_options = CL_SCAN_STDOPT;
 QStringList lastDownloadPaths;
 QString dbdir;
 QString db;
@@ -835,7 +836,7 @@


 if (dbdir != dir_combo->url()){
-ret = cl_loaddbdir((const char *)dir_combo->url(), &root, &no);
+ret = cl_load((const char *)dir_combo->url(), &root, &no, cl_options);
 kdDebug() << "ret " << ret << endl;
 if (no == 0){
 db = dbdir;

-- 
 -
|   ,''`.Stephen Gran |
|  : :' :[EMAIL PROTECTED] |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Bug#353853: marked as done (gnobog_0.4.3-2.2(m68k/unstable/poseidon): fails to build from source)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 23:00:49 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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: gnobog
Version: 0.4.3-2.2
Severity: important


gnobog fails to build from source on m68k and sparc. It looks to me like
you've been bitten by timestamp skew. If you're unfamiliar with that,
search /usr/share/doc/autotools-dev/README.Debian.gz for "skew."

Here are selected excerpts from the buildd log.


| Automatic build of gnobog_0.4.3-2.2 on poseidon by sbuild/m68k 85
| Build started at 20060220-2318
| **

 [...]

| ** Using build dependencies supplied by package:
| Build-Depends: debhelper, docbook-utils, libglade-gnome0-dev, 
libgtkxmhtml-dev, libzvt-dev

 [...]

| Checking correctness of source dependencies...
| Toolchain package versions: libc6-dev_2.3.6-1 
linux-kernel-headers_2.6.13+0rc3-2 gcc-4.0_4.0.2-9 g++-4.0_4.0.2-9 
binutils_2.16.1cvs20060117-1 libstdc++6-4.0-dev_4.0.2-9 libstdc++6_4.0.2-9

 [...]

| make[1]: Entering directory `/build/buildd/gnobog-0.4.3'
| cd . && /build/buildd/gnobog-0.4.3/missing automake-1.4 --gnu Makefile
| WARNING: `automake-1.4' is needed, and you do not seem to have it handy on 
your
|  system.  You might have modified some files without having the
|  proper tools for further handling them.  Check the `README' file,
|  it often tells you about the needed prerequirements for installing
|  this package.  You may also peek at any GNU archive site, in case
|  some other package would contain this missing `automake-1.4' program.
| make[1]: *** [Makefile.in] Error 1
| make[1]: Leaving directory `/build/buildd/gnobog-0.4.3'
| make: *** [build-stamp] Error 2
| **
| Build finished at 20060221-0155
| FAILED [dpkg-buildpackage died]


A full buildd log is available at 


Other buildd logs may be available at 


--
Stephen R. Marenka If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>

--- End Message ---
--- Begin Message ---
gnobog has been removed from the archive because it's orphaned and
only works with GNOME 1.

-- 
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---

Bug#410830: upstart-compat-sysv: Upstart fails in the middle of boot with "Invalid message received"

[Michael Biebl]

Jan Hudec wrote:
> Hello,
> 
> I forgot to point out, that the system where I experienced this bug is AMD64.
> So if the problem can't be reproduced on i386, it may quite likely be
> a 64-bit related error.
> 
> I can do some debugging if you tell me what what would be needed to know.
> 

As I'm going to upload 0.3.5-1 soon, could you please test if you can
reproduce this problem with 0.3.5-1
Add "deb-src http://debs.michaelbiebl.de unstable main" to
/etc/apt/sources.list,
run "apt-get update && apt-get build-dep upstart && apt-get source -b
upstart" and install the resulting debs.
(Sorry for the inconvenience, I don't have a x64 machine to build the
packages myself).


Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#410695: zope2.7 causqe upgrade failure

[Bill Allombert]

On Mon, Feb 12, 2007 at 05:42:31PM -0800, Steve Langasek wrote:
> On Mon, Feb 12, 2007 at 06:53:53PM +0100, Bill Allombert wrote:
> > Package: upgrade-reports
> > Severity: serious
> 
> > The piuparts run below:
> 
> > /usr/sbin/piuparts -a -d sarge -d etch gnupg xawtv k3d-dev libcnumx0-dev 
> > mozilla-opensc xmms-coverviewer makeself koffice-i18n-nn kview 
> > libmcardplugin gij-3.4 gimp-dimage-color libast2-dev libaal-dev caudium-dev 
> > libcvsservice0 tex-guy linuxdoc-tools-latex snort-common multipath-tools 
> > isic libpam-pwdfile libotr1-dev libglib2-ruby haskelldb-bin cyrus21-imapd 
> > bsign scalapack-lam-test pyching freeswan dict-freedict-spa-eng xfaces 
> > libtie-cache-perl zope2.7-mimetypesregistry libdmsocket-0.32.5-0-dev 
> > attal-themes-medieval kde-i18n-srlatin dircproxy pica glimmer kappfinder 
> > kde-i18n-eu 9menu selflinux-pdf libgtksourceview-doc
> 
> Is there a smaller minimal set of packages that can be used to reproduce the
> problem?
Try this one:

k3d-dev kview libaal-dev caudium-dev libcvsservice0 snort-common
libpam-pwdfile cyrus21-imapd zope2.7-mimetypesregistry

> This looks like an apt bug to me (and isn't the first time I've seen it).

Any pointer ?

> If we know zope2.7 is going to be removed in addition to python2.3, why is
> zope2.7 not removed first, avoiding the need to --force-depends?
> 
> Does piuparts use apt-get or aptitude in its upgrade test, and does that
> make a difference in the outcome?

piuparts use apt-get. I did not try aptitude.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large blue swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#389386: marked as done (malsync_2.2.0-2: FTBFS: incompatible with new pilot-link API)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 23:03:38 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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: malsync
Version: 2.2.0-2
Severity: serious

The current malsync package doesn't build with libpisock9 in unstable:

[...]
cc -Wall -g -DMALSYNC -I./mal/common -I./mal/client/common 
-I./pilot-link-0.11.7/include -I./mal/client/unix   -c -o malsync.o malsync.c
malsync.c: In function 'readAndUseDeviceInfoDatabase':
malsync.c:380: warning: pointer targets in passing argument 6 of 
'dlp_ReadRecordByIndex' differ in signedness
malsync.c:380: error: too many arguments to function 'dlp_ReadRecordByIndex'
malsync.c: In function 'readDeviceUserConfig32':
malsync.c:676: error: too many arguments to function 'dlp_ReadRecordByIndex'
malsync.c: In function 'readDeviceUserConfig31':
malsync.c:708: error: too many arguments to function 'dlp_ReadRecordByIndex'
malsync.c: In function 'writeDeviceUserConfig':
malsync.c:761: error: too many arguments to function 'dlp_ReadRecordByIndex'
malsync.c: In function 'getRecordBase':
malsync.c:1057: warning: passing argument 3 of 'dlp_ReadNextModifiedRec' from 
incompatible pointer type
malsync.c:1057: error: too many arguments to function 'dlp_ReadNextModifiedRec'
malsync.c:1061: warning: passing argument 4 of 'dlp_ReadRecordByIndex' from 
incompatible pointer type
malsync.c:1061: error: too many arguments to function 'dlp_ReadRecordByIndex'
malsync.c: In function 'Connect':
malsync.c:1376: warning: 'pilot_connect' is deprecated (declared at 
/usr/include/pi-header.h:28)
malsync.c: In function 'fill_in_versioninfo':
malsync.c:1620: error: too many arguments to function 'dlp_ReadRecordByIndex'
make[1]: *** [malsync.o] Error 1
[...]

A full build log can be found at
.

Please update your package for this new API.  Because the pilot-link
transition is unfortunately linked to the dbus transition, malsync will be
removed from testing until this is resolved.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/

--- End Message ---
--- Begin Message ---
This package has now been removed.
-- 
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---

Bug#410859: liboil0.3: wrongly assumes that all Intel chips support CP14 timestamp

[Aurelien Jarno]

Package: liboil0.3
Version: 0.3.10-1
Severity: grave
Tags: patch

All programs linked with liboil0.3 are causing a SIGILL on an IXP4xx
XScale CPU. This is due to the following code in liboil/liboilcpu.c:

   switch(arm_implementer) {
 case 0x69: /* Intel */
   /* assume that all Intel chips support CP14 timestamp */
   _oil_profile_stamp = oil_profile_stamp_xscale;

I don't know how to detect if an Intel CPU has support for CP14 
timestamp, therefore I suggests to disable this detection for now. Here
is the patch I used:

--- liboil-0.3.10.orig/liboil/liboilcpu.c
+++ liboil-0.3.10/liboil/liboilcpu.c
@@ -644,7 +644,7 @@
   switch(arm_implementer) {
 case 0x69: /* Intel */
   /* assume that all Intel chips support CP14 timestamp */
-  _oil_profile_stamp = oil_profile_stamp_xscale;
+  /* _oil_profile_stamp = oil_profile_stamp_xscale; */
   break;
 case 0x41: /* ARM */
   /* ARM chips are known to not have timestamping available from 

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: arm (armv5tel)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-ixp4xx
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages liboil0.3 depends on:
ii  libc62.3.6.ds1-10 GNU C Library: Shared libraries

liboil0.3 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#408948: Status update

[Josselin Mouette]

Le mardi 13 février 2007 à 10:46 +0100, Loïc Minier a écrit :
> Hi,
> 
>  Log of an IRC conversation on the status of this bug is attached.  In
>  short, it might be easier to workaround this problem at the nautilus
>  level, it's way riskier at the gnome-vfs2 level.
> 
>  Tentative patch for nautilus which didn't work is attached.

I think it doesn't work because .desktop files get a very special
treatment in nautilus. I think they should simply not be considered as
desktop files unless they are holding the correct extension. Such a
specific change shouldn't break anything.

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Bug#318567: marked as done (xbox-cromwell: FTBFS with gcc-4.0: pointer targets in assignment differ in signedness)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 22:54:49 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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: xbox-cromwell
Severity: serious
Version: 2.40-1

>From my build log, using pbuilder in an i386 chroot:

...
make[6]: Entering directory 
`/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/etherboot/arch/i386/core'
gcc -O2 -mcpu=pentium -Werror 
-I/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/etherboot/include 
-I/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/etherboot/arch/i386/include
-Wstrict-prototypes -fomit-frame-pointer -pipe -Ui386 
-fno-zero-initialized-in-bss 
-I/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/include 
-I/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/fs/cdrom 
-I/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/drivers/video 
-I/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/lib/eeprom 
-I/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/lib/misc -o 
/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/obj/xbox.o -c xbox.c
`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
cc1: warnings being treated as errors
xbox.c: In function 'find_cmdline':
xbox.c:167: warning: pointer targets in assignment differ in signedness
xbox.c: In function 'parse_elf_boot_notes':
xbox.c:189: warning: pointer targets in assignment differ in signedness
xbox.c:190: warning: pointer targets in assignment differ in signedness
make[6]: *** [xbox.o] Error 1
make[6]: Leaving directory 
`/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/etherboot/arch/i386/core'
make[5]: *** [first_rule] Error 2
make[5]: Leaving directory 
`/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/etherboot/arch/i386/core'
make[4]: *** [_subdir_core] Error 2
make[4]: Leaving directory 
`/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/etherboot/arch/i386'
make[3]: *** [_subdir_i386] Error 2
make[3]: Leaving directory 
`/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/etherboot/arch'
make[2]: *** [_subdir_arch] Error 2
make[2]: Leaving directory 
`/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell/etherboot'
make[1]: *** [_dir_etherboot] Error 2
make[1]: Leaving directory `/tmp/buildd/xbox-cromwell-2.40/build-tree/cromwell'
make: *** [debian/stamp-makefile-build] Error 2

-- System Information:
Debian Release: testing/unstable
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-9-amd64-k8
Locale: LANG=en, LC_CTYPE=en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)

-- 
Daniel Schepler  "Please don't disillusion me.  I
[EMAIL PROTECTED]haven't had breakfast yet."
 -- Orson Scott Card

--- End Message ---
--- Begin Message ---
This package has been removed from the archive: orphaned, few popcon
installs, buggy

-- 
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---

Processed: severity of 410817 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.27
> # hardware-specific regression
> severity 410817 important
Bug#410817: linux-image-2.6.18-3-686: new megaraid driver fails to detect 
logical drive
Severity set to `important' from `critical'

>
End of message, 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]

Bug#410834: FTBFS: 'cl_loaddbdir' was not declared in this scope

[Stephen Gran]

Here's a Works For Me (TM) patch:

--- dansguardian-2.8.0.6-antivirus-6.4.4.1.orig/ClamAV.cpp
+++ dansguardian-2.8.0.6-antivirus-6.4.4.1/ClamAV.cpp
@@ -54,9 +54,36 @@
 #endif
   root = NULL;
 }
-  if ((ret = cl_loaddbdir (dbdir, &root, &no)))
+  unsigned int cl_options = CL_ARCHIVE | CL_MAIL | CL_OLE2
+#ifdef CL_SCAN_PE
+| CL_SCAN_PE
+#else
+#warning "CL_SCAN_PE scan flag not supported"
+#endif
+#ifdef CL_SCAN_HTML
+| CL_SCAN_HTML
+#else
+#warning "CL_SCAN_HTML scan flag not supported"
+#endif
+#ifdef CL_SCAN_BLOCKBROKEN
+| (o.cl_detect_broken == 1 ? CL_SCAN_BLOCKBROKEN : 0)
+#else
+#warning "CL_SCAN_BLOCKBROKEN scan flag not supported"
+#endif
+#ifdef CL_SCAN_BLOCKENCRYPTED
+| (o.cl_block_encrypted == 1 ? CL_SCAN_BLOCKENCRYPTED : 0)
+#else
+#ifdef CL_ENCRYPTED
+| (o.cl_block_encrypted == 1 ? CL_ENCRYPTED : 0)
+#else
+#warning "CL_ENCRYPTED/CL_SCAN_BLOCKENCRYPTED scan flags not supported"
+#endif
+#endif
+;
+
+  if ((ret = cl_load (dbdir, &root, &no, cl_options)))
 {
-  syslog (LOG_ERR, "Error loading ClamAV DB: %s", cl_perror (ret));
+  syslog (LOG_ERR, "Error loading ClamAV DB: %s", cl_strerror (ret));
   return ret;
 }
   else
only in patch2:
unchanged:
--- dansguardian-2.8.0.6-antivirus-6.4.4.1.orig/ClamAV.hpp
+++ dansguardian-2.8.0.6-antivirus-6.4.4.1/ClamAV.hpp
@@ -39,7 +39,7 @@
 private:
   const char *virname;
   const char *err_str;
-  struct cl_node *root;
+  struct cl_engine *root;
   struct cl_limits limits;
   struct cl_stat dbstat;

-- 
 -
|   ,''`.Stephen Gran |
|  : :' :[EMAIL PROTECTED] |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Bug#405958: marked as done (FTBFS: libmal-dev is not in Debian anymore (removal of jpilot-syncmal requested))

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 23:02:50 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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: jpilot-syncmal
Severity: serious
Justification: Policy 7.6

jpilot-syncmal 0.73 has a Build-Depends: libmal-dev (>= 0.42-1) but
libmal-dev has been removed from Debian on my request, see #394544

I now file a RC bug (this one) and a request to remove jpilot-syncmal
(#405946).

jpilot-syncmal should not be distributed in Etch and can be removed from
testing until it is completely removed also from unstable.

thanks

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (90, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

--- End Message ---
--- Begin Message ---
This package has been removed because it can no longer be built.
-- 
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---

Bug#387964: marked as done (Uninstallable due to unmet dep on python (< 2.4))

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 22:59:42 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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: xkeysw-config
Severity: serious
Version: 1.1-1.3

Hi

Your package is not installable due to a dependency on python (< 2.4) which is
not available in unstable anymore. The package might need an update for the
python transition.

Cheers

Luk

-- 
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint:   D5AF 25FB 316B 53BB 08E7   F999 E544 DE07 9B7C 328D



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
This package has been removed from the archive because it's
uninstallable, has few users and the maintainer is not active.

-- 
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---

Processed: severity of 410843 is serious

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.27
> severity 410843 serious
Bug#410843: spamassassin: URI parsing causes local DoS
Severity set to `serious' from `important'

>
End of message, 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]

Bug#334647: marked as done (emacs-color-theme: standalone or in emacs-goodies-el package?)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 22:58:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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: emacs-color-themes
Version: 6.5.4-1
Severity: normal

Hi,

Emails to you have been bouncing, so I figured you might see this...

What do you want to do about color-themes?  Keep this package or add the
file to emacs-goodies-el as suggested in http://bugs.debian.org/144420 ?

I'm about ready to add it to emacs-goodies-el and might just do that
anyway with the added initialization via customization .

Thanks,
Peter

--- End Message ---
--- Begin Message ---
superseded by emacs-goodies-el; orphaned
-- 
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---

Processed: Downgrade

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 410727 important
Bug#410727: kaffeine crashes attempting to play videos
Severity set to `important' from `grave'

> 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]

Bug#410727: kaffeine crashes attempting to play videos

[Steve Langasek]

On Tue, Feb 13, 2007 at 12:19:26PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> > What video type you try to play ? i tried avi files without any crash.

> Try to open with konqueror www.tn.com.ar . After some buffering, a stream of 
> video will apair.
> Right-click over the video and select "Open in an external program, kaffeine" 
> (or something alike, I have a spanish instalation).

> Once again, after some buffering, the video will appear. Close Kaffeine's 
> window. After some seconds, a KDE error message appears.

In fact, when I visit this website with konqueror/kaffeine, I don't get any
video at all, only audio.  Opening the same audio stream in a stand-alone
kaffeine window works; closing the kaffeine window works.

Closing konqueror afterwards gives me a KDE crash screen, but that hardly
seems grave, since it only happens on shutdown.

The behavior is the same testing on either amd64 or i386.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/

Bug#407494: marked as done (caudium: failes to start)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 22:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#407494: fixed in caudium 2:1.4.9.1-2
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: caudium
Version: 2:1.4.9.1-1
Severity: grave
Justification: renders package unusable


When pike loads the caudium module it crashes with SIGSEGV


cd /usr/lib/caudium; strace -f ./start-caudium --gdb


open("/usr/lib/caudium/lib/7.6.93", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 9
fstat64(9, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
fcntl64(9, F_SETFD, FD_CLOEXEC) = 0
fstatfs(9, {f_type="EXT2_SUPER_MAGIC", f_bsize=4096, f_blocks=12015586, 
f_bfree=11693033, f_bavail=11082665, f_files=6111232, 
f_ffree=6048542,
 f_fsid={0, 0}, f_namelen=255, f_frsize=4096}) = 0
getdents64(9, /* 4 entries */, 4096)= 112
getdents64(9, /* 0 entries */, 4096)= 0
close(9)= 0
stat64("/usr/lib/caudium/lib/7.6.93/_Caudium.so", {st_mode=S_IFREG|0644, 
st_size=77752, ...}) = 0
gettimeofday({1169152985, 817787}, NULL) = 0
stat64("/usr/lib/caudium/lib/7.6.93/_Caudium.so", {st_mode=S_IFREG|0644, 
st_size=77752, ...}) = 0
open("/usr/lib/caudium/lib/7.6.93/_Caudium.so", O_RDONLY) = 9
read(9, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\%\0\000"..., 512) = 
512
fstat64(9, {st_mode=S_IFREG|0644, st_size=77752, ...}) = 0
mmap2(NULL, 76976, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 9, 0) = 
0xa7963000
mmap2(0xa7975000, 4096, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 9, 0x12) = 0xa7975000
close(9)= 0
gettimeofday({1169152985, 818941}, NULL) = 0
gettimeofday({1169152985, 819232}, NULL) = 0
gettimeofday({1169152985, 819342}, NULL) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Process 11251 detached

complete log:
http://han.pp.se/bug-caudium-strace-start-then-sigsegv.txt


apt-get source caudium pike7.6
enable debug, 
install debug package

cd /usr/lib/caudium ; ./start-caudium --gdb

/usr/lib/pike/7.6.93/lib/master.pike:349:
object(/usr/lib/pike/7.6.93/lib/master.pike)->compile_string("/*\n * 
Caudium - An extensible World Wide Web server\n * Copyright 
\251 20
00-2005 The Caudium Group\n * Copyright \251 
1994-200"+[11947],"/usr/lib/caudium/etc/modules/Cache.pmod/Manager.pike",0,Cache.Manager,0,
UNDEFINED)
/usr/lib/pike/7.6.93/lib/master.pike:827:

object(/usr/lib/pike/7.6.93/lib/master.pike)->low_findprog("/usr/lib/caudium/etc/modules/Cache.pmod/Manager",".pike",0,UNDEFINED)
/usr/lib/pike/7.6.93/lib/master.pike:936:

object(/usr/lib/pike/7.6.93/lib/master.pike)->findprog("/usr/lib/caudium/etc/modules/Cache.pmod/Manager",".pike",0,UNDEFINED)
/usr/lib/pike/7.6.93/lib/master.pike:972:

object(/usr/lib/pike/7.6.93/lib/master.pike)->low_cast_to_program("/usr/lib/caudium/etc/modules/Cache.pmod/Manager",0,0,UNDEFINED)
/usr/lib/pike/7.6.93/lib/master.pike:1364: 
object(/usr/lib/pike/7.6.93/lib/master.pike:1185)->low_ind("Manager",UNDEFINED)
/usr/lib/pike/7.6.93/lib/master.pike:1421: 
object(/usr/lib/pike/7.6.93/lib/master.pike:1185)->ind("Manager")
/usr/lib/pike/7.6.93/lib/master.pike:1445: 
object(/usr/lib/pike/7.6.93/lib/master.pike:1185)->`[]("Manager")
/usr/lib/pike/7.6.93/lib/master.pike:1595: 
object(/usr/lib/pike/7.6.93/lib/master.pike:1535)->ind("Manager")
/usr/lib/pike/7.6.93/lib/master.pike:1633: 
object(/usr/lib/pike/7.6.93/lib/master.pike:1535)->`[]("Manager")
/usr/lib/pike/7.6.93/lib/master.pike:349:
object(/usr/lib/pike/7.6.93/lib/master.pike)->compile_string("/*\n * 
Caudium - An extensible World Wide Web server\n * Copyright 
\251 20
00-2005 The 
Caudi"+[24242],"/usr/lib/caudium/base_server/caudiumloader.pike",UNDEFINED,/usr/lib/caudium/base_server/caudiumloader,0,UNDE
FINED)
/usr/lib/pike/7.6.93/lib/master.pike:827:

object(/usr/lib/pike/7.6.93/lib/master.pike)->low_findprog("/usr/lib/caudium/base_server/caudiumloader",".pike",UNDEFINED,UNDEFINED)
/usr/lib/pike/7.6.93/lib/master.pike:936:

object(/usr/lib/pike/7.6.93/lib/master.pike)->findprog("/usr/lib/caudium/base_server/caudiumloader",".pike",UNDEFINED,UNDEFINED)
/usr/lib/pike/7.6.93/lib/master.pike:972:

object(/usr/lib/pike/7.6.93/lib/master.pike)->low_cast_to_program("/usr/lib/caudium/base_server/caudiumloader","/usr/lib/pike/7.6.93/lib
/master.pike",UNDEFINED,UNDEFINED)
/usr/lib/pike/7.6.93/lib/master.pike:1006:

object(/usr/lib/pike/7.6.93/lib/master.pike)->cast_to_program("/usr/lib/caudium/base_serve

Processed: found 410850 in 1.4.5-2

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> found 410850 1.4.5-2
Bug#410850: CVE-2006-6980: magnatune shell escapes
Bug marked as found in version 1.4.5-2.

>
End of message, 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]

Bug#410817: linux-image-2.6.18-3-686: new megaraid driver fails to detect logical drive

[Slávek Banko]

Try to use module megaraid_mbox, instead of module megaraid.

Slavek


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410850: misleading CVE

[Kees Cook]

BTW, the CVE is misleading, there are ruby script fixes needed as well 
as the unzip bug.  Attached is a patch for the ruby fixes, which appear 
to be in upstream 1.4.5 already.

-- 
Kees Cook@outflux.net
diff -Nur amarok-1.4.3/amarok/src/scripts/databasescripts/backupDatabase.rb amarok-1.4.3.new/amarok/src/scripts/databasescripts/backupDatabase.rb
--- amarok-1.4.3/amarok/src/scripts/databasescripts/backupDatabase.rb	2006-09-04 19:42:40.0 -0700
+++ amarok-1.4.3.new/amarok/src/scripts/databasescripts/backupDatabase.rb	2007-02-13 13:39:04.198770848 -0800
@@ -37,14 +37,12 @@
 destination = $*[0] + "/"
 
 unless FileTest.directory?( destination )
-error = "Error: Save destination must be a directory"
-`dcop amarok playlist popupMessage '#{error}'`
+system("dcop", "amarok", "playlist", "popupMessage", "Error: Save destination must be a directory")
 exit( 1 )
 end
 
 unless FileTest.writable_real?( destination )
-error = "Error: Destination directory not writable."
-`dcop amarok playlist popupMessage '#{error}'`
+system("dcop", "amarok", "playlist", "popupMessage", "Error: Destination directory not writeable.")
 exit( 1 )
 end
 
@@ -68,14 +66,11 @@
 db   = `dcop amarok script readConfig MySqlDbName`.chomp!()
 user = `dcop amarok script readConfig MySqlUser`.chomp!()
 pass = `dcop amarok script readConfig MySqlPassword`.chomp!()
-`mysqldump -u #{user} -p#{pass} #{db} > #{dest}`
+system("mysqldump", "-u", user, "-p", pass, db, "-r", dest);
 
 when "2" # postgres
-error = "Sorry, postgresql database backups have not been implemented"
-`dcop amarok playlist popupMessage #{error}`
+system("dcop", "amarok", "playlist", "popupMessage", "Sorry, postgresql database backups have not been implemented.")
 exit( 1 )
 end
 
-message = "Database backup saved to: #{destination}/#{filename}"
-`dcop amarok playlist popupMessage '#{message}'`
-
+system("dcop", "amarok", "playlist", "popupMessage", "Database backup saved to: #{destination}/#{filename}")
diff -Nur amarok-1.4.3/amarok/src/scripts/databasescripts/databaseScripts.rb amarok-1.4.3.new/amarok/src/scripts/databasescripts/databaseScripts.rb
--- amarok-1.4.3/amarok/src/scripts/databasescripts/databaseScripts.rb	2006-09-04 19:42:40.0 -0700
+++ amarok-1.4.3.new/amarok/src/scripts/databasescripts/databaseScripts.rb	2007-02-13 13:39:04.198770848 -0800
@@ -16,7 +16,7 @@
 require 'Korundum'
 rescue LoadError
 error = 'Korundum (KDE bindings for ruby) from kdebindings v3.4 is required for this script.'
-`dcop amarok playlist popupMessage "DatabaseScripts: #{error}"`
+system("dcop", "amarok", "playlist", "popupMessage", "DatabaseScripts: #{error}")
 exit
 end
 
@@ -103,7 +103,7 @@
 filename = File.dirname( File.expand_path( __FILE__ ) ) + "/staleStatistics.rb"
 end
 
-`ruby "#{filename}" "#{arg}"`
+system("ruby", filename, arg)
 
 done( 0 )
 end
diff -Nur amarok-1.4.3/amarok/src/scripts/databasescripts/redoPodcasts.rb amarok-1.4.3.new/amarok/src/scripts/databasescripts/redoPodcasts.rb
--- amarok-1.4.3/amarok/src/scripts/databasescripts/redoPodcasts.rb	2006-09-04 19:42:40.0 -0700
+++ amarok-1.4.3.new/amarok/src/scripts/databasescripts/redoPodcasts.rb	2007-02-13 13:39:04.198770848 -0800
@@ -12,6 +12,6 @@
 
 podcasts.each do |channel|
 print "Adding podcast: #{channel}\n"
-`dcop amarok playlistbrowser addPodcast #{channel}`
+system("dcop", "amarok", "playlistbrowser", "addPodcast", channel)
 end
 print "Done.\n"
diff -Nur amarok-1.4.3/amarok/src/scripts/databasescripts/staleAlbums.rb amarok-1.4.3.new/amarok/src/scripts/databasescripts/staleAlbums.rb
--- amarok-1.4.3/amarok/src/scripts/databasescripts/staleAlbums.rb	2006-09-04 19:42:40.0 -0700
+++ amarok-1.4.3.new/amarok/src/scripts/databasescripts/staleAlbums.rb	2007-02-13 13:39:04.202771047 -0800
@@ -5,30 +5,36 @@
 # (c) 2006 Roland Gigler <[EMAIL PROTECTED]>
 # License: GNU General Public License V2
 
-`dcop amarok playlist shortStatusMessage "Removing stale 'album' entries from the database"`
+class String
+def shellquote
+return "'" + self.gsub("'", "'''") + "'"
+end
+end
+
+system("dcop", "amarok", "playlist", "shortStatusMessage", "Removing stale 'album' entries from the database")
 
-qresult = `dcop amarok collection query "SELECT id FROM album;"`
+qresult = `dcop amarok collection query #{"SELECT id FROM album;".shellquote}`
 result = qresult.split( "\n" )
 
 i = 0
 
 result.each do |id|
 print "Checking: #{id}, "
-qresult2 = `dcop amarok collection query "SELECT COUNT(*) FROM tags where album = #{id};"`
+qresult2 = `dcop amarok collection query #{"SELECT COUNT(*) FROM tags where album = #{id};".shellquote}`
 count = qresult2.chomp()
 printf "count: %s", count
 if  count == "0"
 i = i + 1
-	qresult3 = `dcop amarok

Bug#408245: ipvsadm: diff for NMU version 1.24+1.21-1.4

[Mohammed Adnène Trojette]

Hi,

Attached is the diff for my ipvsadm 1.24+1.21-1.4 NMU.
-- 
Mohammed Adnène Trojette
diff -u ipvsadm-1.24+1.21/debian/copyright ipvsadm-1.24+1.21/debian/copyright
--- ipvsadm-1.24+1.21/debian/copyright
+++ ipvsadm-1.24+1.21/debian/copyright
@@ -21,7 +21,7 @@
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software 
-   Foundation, Inc., 59 Temple Place - Suite 330, Boston,
-   MA 02111-1307, USA.
-   
+   Foundation, Inc., 51 Franklin St, 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 -u ipvsadm-1.24+1.21/debian/ipvsadm.postinst ipvsadm-1.24+1.21/debian/ipvsadm.postinst
--- ipvsadm-1.24+1.21/debian/ipvsadm.postinst
+++ ipvsadm-1.24+1.21/debian/ipvsadm.postinst
@@ -12,6 +12,19 @@
 	db_get ipvsadm/daemon_method; DAEMON="$RET"
 	db_get ipvsadm/daemon_multicast_interface; IFACE="$RET"
 
+if which ipvsadm &>/dev/null; then
+# Regardless of if ipvs is built into the kernel or built as a module,
+# if it is part of the kernel at all, it will be available after this
+ipvsadm -L -n >& /dev/null || true
+fi
+
+if [ ! -f "/proc/net/ip_vs_conn" ]; then
+db_fset ipvsadm/kernel_does_not_support_ipvs seen false
+db_input high ipvsadm/kernel_does_not_support_ipvs || true
+db_go
+exit 0
+fi
+
 	if [ "$DAEMON" = "none" ]; then
 	cat > $IPVSADM_CONFIG <& /dev/null # Regardless of if ipvs is built the kernel or
-
-if [ ! -f "/proc/net/ip_vs_conn" ]; then
-db_fset ipvsadm/kernel_does_not_support_ipvs seen false
-db_input high ipvsadm/kernel_does_not_support_ipvs || true
-db_go
-exit 0
-fi
-
 if [ -f $IPVSADM_CONFIG ]; then
 . $IPVSADM_CONFIG
 
diff -u ipvsadm-1.24+1.21/debian/changelog ipvsadm-1.24+1.21/debian/changelog
--- ipvsadm-1.24+1.21/debian/changelog
+++ ipvsadm-1.24+1.21/debian/changelog
@@ -1,3 +1,17 @@
+ipvsadm (1.24+1.21-1.4) unstable; urgency=high
+  
+  * Non-maintainer upload.
+
+  [ Pierre Habouzit ]
+  * Move ipvs detection into the postinst, so that we can rely on the ipvsadm
+tool, guard that call to avoid any problems. (Closes: #408245).
+
+  [ Mohammed Adnène Trojette ]
+  * High urgency for RC bug fixing.
+  * Update FSF address in debian/copyright.
+
+ -- Mohammed Adnène Trojette <[EMAIL PROTECTED]>  Tue, 13 Feb 2007 19:12:11 +0100
+
 ipvsadm (1.24+1.21-1.3) unstable; urgency=low
 
   * Non-maintainer upload

Bug#410821: Which data loss?

[Philippe Cloutier]

Justification: causes non-serious data loss


Which data loss does this cause?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410823: closed by Christian Perrier <[EMAIL PROTECTED]> (Re: Bug#410823: samba: smbd segfaults during startup)

[Steve Langasek]

On Tue, Feb 13, 2007 at 09:26:38PM +0100, Fabien COUTANT wrote:
> 1/ if "guest" has been disabled from "passdb backend", smbd should *not*
>crash with a segfault when guest is still written inside, but instead
>ignore it or show an explanatory error message;  testparm should also
>report it (it still doesn't).

the value of "passdb backend" is a freeform text value, whose allowed values
are extended by the addition of plugins.  It's improbable that testparm will
vet these values.

> 2/ The changelog provided in the Debian package doesn't give any rationale,
>only the fact it was removed.

Christian referred to the upstream samba changelog, not to the Debian
package's changelog.  The upstream changelog isn't included in the Debian
binary packages.

> 3/ by reading the changelog I see that some upgrade *should* have
>*silently* removed the incriminated "guest" value. (a) it didn't, and
>(b) it shouldn't be done silently but instead clearly advertised since
>it's important functionality removal.

No, it's not important functionality removal.  The 'guest' backend was an
obsolete no-op before sarge's release.  So a silent upgrade is the correct
behavior.

If there are cases where the guest value is not being automatically removed
when it should be, we want to know about that so we can fix it.  What
version were you upgrading from?

> 4/ "passdb backend = tdbsam guest" was working fine for me.  Is the new
>version supposed to behave the same, i.e. provide the same access right
>policy, with "guest" removed ?

Yes, as I mentioned the 'guest' backend is long obsolete.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#408245: marked as done (ipvsadm: installation fails)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 21:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#408245: fixed in ipvsadm 1.24+1.21-1.4
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: ipvsadm
Version: 1.24+1.21-1.3
Severity: serious
Usertags: grid5000 piuparts

Hi,

During a piuparts run over all the packages in etch, I ran into a
problem with your package:

Preconfiguring packages ...
ipvsadm failed to preconfigure, with exit status 127
Selecting previously deselected package ipvsadm.
(Reading database ... 12450 files and directories currently installed.)
Unpacking ipvsadm (from .../ipvsadm_1.24+1.21-1.3_i386.deb) ...
Setting up ipvsadm (1.24+1.21-1.3) ...
dpkg: error processing ipvsadm (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 ipvsadm
E: Sub-process /usr/bin/dpkg returned an error code (1)

I could easily reproduce the problem outside of piuparts, but couldn't
determine the reason for it.
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |

--- End Message ---
--- Begin Message ---
Source: ipvsadm
Source-Version: 1.24+1.21-1.4

We believe that the bug you reported is fixed in the latest version of
ipvsadm, which is due to be installed in the Debian FTP archive:

ipvsadm_1.24+1.21-1.4.diff.gz
  to pool/main/i/ipvsadm/ipvsadm_1.24+1.21-1.4.diff.gz
ipvsadm_1.24+1.21-1.4.dsc
  to pool/main/i/ipvsadm/ipvsadm_1.24+1.21-1.4.dsc
ipvsadm_1.24+1.21-1.4_i386.deb
  to pool/main/i/ipvsadm/ipvsadm_1.24+1.21-1.4_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mohammed Adnène Trojette <[EMAIL PROTECTED]> (supplier of updated ipvsadm 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 13 Feb 2007 19:12:11 +0100
Source: ipvsadm
Binary: ipvsadm
Architecture: source i386
Version: 1.24+1.21-1.4
Distribution: unstable
Urgency: high
Maintainer: Joerg Wendland <[EMAIL PROTECTED]>
Changed-By: Mohammed Adnène Trojette <[EMAIL PROTECTED]>
Description: 
 ipvsadm- Linux Virtual Server support programs
Closes: 408245
Changes: 
 ipvsadm (1.24+1.21-1.4) unstable; urgency=high
 .
   * Non-maintainer upload.
 .
   [ Pierre Habouzit ]
   * Move ipvs detection into the postinst, so that we can rely on the ipvsadm
 tool, guard that call to avoid any problems. (Closes: #408245).
 .
   [ Mohammed Adnène Trojette ]
   * High urgency for RC bug fixing.
   * Update FSF address in debian/copyright.
Files: 
 faf4d6b4493ff1c6370719376dfbe206 614 net extra ipvsadm_1.24+1.21-1.4.dsc
 a3b3db24aa2597b57678123c3b728cbd 31922 net extra ipvsadm_1.24+1.21-1.4.diff.gz
 d53851fb086c6362dbb4591ab21cc95b 47498 net extra ipvsadm_1.24+1.21-1.4_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF0ihwOU3FkQ7XBOoRAhj9AKC2U7DfQ7jqA8ah9/vwDDmq7VYF5wCeNuG9
J/bWc9+5S1KVWV3bh0zfY4o=
=MK1j
-END PGP SIGNATURE-

--- End Message ---

Processed: reassign 410850 to amarok, found 410850 in 1.4.4-2

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.27
> # ESPELL
> reassign 410850 amarok
Bug#410850: CVE-2006-6980: magnatune shell escapes
Bug reassigned from package `amarok' to `amarok'.

> found 410850 1.4.4-2
Bug#410850: CVE-2006-6980: magnatune shell escapes
Bug marked as found in version 1.4.4-2.

>
End of message, 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: Re: Bug#410850: Acknowledgement (CVE-2006-6980: magnatune shell escapes)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 410850 amarok
Bug#410850: CVE-2006-6980: magnatune shell escapes
Bug reassigned from package `amarok' to `amarok'.

> --
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: reassign 410850 to amarok

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> reassign 410850 amarok
Bug#410850: CVE-2006-6980: magnatune shell escapes
Warning: Unknown package 'amarock'
Bug reassigned from package `amarock' to `amarok'.

>
End of message, 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: found 410803 in 1:4.0.5-7

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.27
> found 410803 1:4.0.5-7
Bug#410803: twiki: postinst relies on data in /usr/share/doc
Bug marked as found in version 1:4.0.5-7.

>
End of message, 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]

Bug#410850: CVE-2006-6980: magnatune shell escapes

[Kees Cook]

Package: amarock
Version: 1.4.4-2
Severity: grave
Tags: patch, security

CVE-2006-6980 says[1]:

"The ruby handlers in Amarok do not properly quote text in certain 
contexts, probably including construction of an unzip command line, 
which allows attackers to execute arbitrary commands via shell 
metacharacters."

There is an open KDE bug report[2], and SuSE has patched this 
problem.  I'm working on extracting the patches now...


[1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6979
[2] http://bugs.kde.org/show_bug.cgi?id=138499

-- 
Kees Cook@outflux.net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410824: marked as done (upgrade fails: sed: -e expression #1, char 120: unterminated `s' command)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 20:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410824: fixed in ntlmaps 0.9.9.0.1-6
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: ntlmaps
Version: 0.9.9.0.1-5
Severity: grave
Justification: renders package unusable


# apt-get upgrade
[...]
Setting up ntlmaps (0.9.9.0.1-5) ...
sed: -e expression #1, char 120: unterminated `s' command
dpkg: error processing ntlmaps (--configure):
 subprocess post-installation script returned error exit status 1
[...]

regards,
-mika-

--- End Message ---
--- Begin Message ---
Source: ntlmaps
Source-Version: 0.9.9.0.1-6

We believe that the bug you reported is fixed in the latest version of
ntlmaps, which is due to be installed in the Debian FTP archive:

ntlmaps_0.9.9.0.1-6.diff.gz
  to pool/main/n/ntlmaps/ntlmaps_0.9.9.0.1-6.diff.gz
ntlmaps_0.9.9.0.1-6.dsc
  to pool/main/n/ntlmaps/ntlmaps_0.9.9.0.1-6.dsc
ntlmaps_0.9.9.0.1-6_all.deb
  to pool/main/n/ntlmaps/ntlmaps_0.9.9.0.1-6_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Watson <[EMAIL PROTECTED]> (supplier of updated ntlmaps package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 13 Feb 2007 20:23:55 +
Source: ntlmaps
Binary: ntlmaps
Architecture: source all
Version: 0.9.9.0.1-6
Distribution: unstable
Urgency: low
Maintainer: David Watson <[EMAIL PROTECTED]>
Changed-By: David Watson <[EMAIL PROTECTED]>
Description: 
 ntlmaps- NTLM Authorization Proxy Server
Closes: 410824
Changes: 
 ntlmaps (0.9.9.0.1-6) unstable; urgency=low
 .
   * Fix sed usage in postinst (properly). Closes: #410824.
Files: 
 c588833e4ad1d1a6c9cc8d657bf0df3e 641 web optional ntlmaps_0.9.9.0.1-6.dsc
 43cf9b54a112d3de8493c1279b8eb5ff 17300 web optional ntlmaps_0.9.9.0.1-6.diff.gz
 54fa90959ad9c9a32f398c426c5de503 66792 web optional ntlmaps_0.9.9.0.1-6_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF0h7jDeh5nqfWrnkRAhIkAJ9dDKX+3aFXgT3iRl3yhPV7sjEBswCeM1zy
V0qBruUqASYSyPyf1cdHgrY=
=j0G4
-END PGP SIGNATURE-

--- End Message ---

Bug#410823: closed by Christian Perrier <[EMAIL PROTECTED]> (Re: Bug#410823: samba: smbd segfaults during startup)

[Fabien COUTANT]

> Date: Tue, 13 Feb 2007 19:47:35 +0100
> From: Christian Perrier <[EMAIL PROTECTED]>
> Subject: Re: Bug#410823: samba: smbd segfaults during startup
(cut)
> Please change "passdb backend" to "tdbsam" alone. See Samba Changelog
> for rationale.

1/ if "guest" has been disabled from "passdb backend", smbd should *not*
   crash with a segfault when guest is still written inside, but instead
   ignore it or show an explanatory error message;  testparm should also
   report it (it still doesn't).
2/ The changelog provided in the Debian package doesn't give any rationale,
   only the fact it was removed.
3/ by reading the changelog I see that some upgrade *should* have
   *silently* removed the incriminated "guest" value. (a) it didn't, and
   (b) it shouldn't be done silently but instead clearly advertised since
   it's important functionality removal.
4/ "passdb backend = tdbsam guest" was working fine for me.  Is the new
   version supposed to behave the same, i.e. provide the same access right
   policy, with "guest" removed ?

-- 
Hope this helps,
Fabien.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410833: FTBFS: error: 'CL_EMALFZIP' undeclared

[Martin Michlmayr]

Package: avscan
Version: 1.3.1-openssl-1
Severity: serious
Tags: sid

This package fails to compile in sid (but not in etch):

> Automatic build of avscan_1.3.1-openssl-1 on coconut0 by sbuild/ia64 0.49
...
> Compiling module avscanop.o
> avscanop.c: In function 'AVScanOPClamAVInit':
> avscanop.c:300: warning: implicit declaration of function 'cl_loaddbdir'
> avscanop.c:317: warning: implicit declaration of function 'cl_loaddb'
> avscanop.c: In function 'AVScanOPClamAVScanFile':
> avscanop.c:569: error: 'CL_EMALFZIP' undeclared (first use in this function)
> avscanop.c:569: error: (Each undeclared identifier is reported only once
> avscanop.c:569: error: for each function it appears in.)
> make[2]: *** [avscanop.o] Error 1
> make[2]: Leaving directory `/build/tbm/avscan-1.3.1-openssl/avscan'

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410835: FTBFS: Could not find module `MissingH.AnyDBM'

[Martin Michlmayr]

Package: hdbc-missingh
Version: 1.0.1.1
Severity: serious
Tags: sid

This package fails to compile in sid (but not in etch):

> Automatic build of hdbc-missingh_1.0.1.1 on coconut0 by sbuild/ia64 0.49
...
> configure: No greencard found
> Running: ./setup build
> 
> MissingH/AnyDBM/HDBCDBM.hs:38:7:
> Could not find module `MissingH.AnyDBM':
>   Use -v to see a list of the files searched for.
> Preprocessing library HDBC-MissingH-1.0.1.0...
> Preprocessing executables for HDBC-MissingH-1.0.1.0...
> Building HDBC-MissingH-1.0.1.0...
> ./setup build files: 256 at /usr/share/haskell-devscripts//Dh_Haskell.pm line 
> 138,  line 1.
> make: *** [install] Error 9
> **
> Build finished at 20070205-2308

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410834: FTBFS: 'cl_loaddbdir' was not declared in this scope

[Martin Michlmayr]

Package: dansguardian
Version: 2.8.0.6-antivirus-6.4.4.1-1
Severity: serious
Tags: sid

This package fails to compile in sid (but not in etch):

> Automatic build of dansguardian_2.8.0.6-antivirus-6.4.4.1-1 on coconut0 by 
> sbuild/ia64 0.49
...
> make[1]: Entering directory 
> `/build/tbm/dansguardian-2.8.0.6-antivirus-6.4.4.1'
> g++ -DUSE_SOCKLEN_TYPE  -O2 -Wall -I/usr/include -c ClamAV.cpp
> ClamAV.cpp: In member function 'virtual int ClamEngine::loadEngine()':
> ClamAV.cpp:57: error: 'cl_loaddbdir' was not declared in this scope
> ClamAV.cpp:59: error: 'cl_perror' was not declared in this scope
> make[1]: *** [ClamAV.o] Error 1
> make[1]: Leaving directory `/build/tbm/dansguardian-2.8.0.6-antivirus-6.4.4.1'

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410838: FTBFS: Could not find module `MissingH.Path'

[Martin Michlmayr]

Package: darcs-buildpackage
Version: 0.5.10
Severity: serious
Tags: sid

This package fails to compile in sid (but not in etch):

> Automatic build of darcs-buildpackage_0.5.10 on coconut0 by sbuild/ia64 0.49
...
> configure: No c2hs found
> configure: No cpphs found
> configure: No greencard found
> ./setup build
> 
> Darcs.hs:12:7:
> Could not find module `MissingH.Path':
>   Use -v to see a list of the files searched for.
> Preprocessing executables for darcs-buildpackage-0.5.3...
> Building darcs-buildpackage-0.5.3...
> make[1]: *** [all] Error 1
> make[1]: Leaving directory `/build/tbm/darcs-buildpackage-0.5.10'
> make: *** [build-stamp] Error 2

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410348: marked as done (libsplashy0-dev: missing dependency on libsplashy0)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 19:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410348: fixed in splashy 0.3.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: libsplashy0-dev
Version: 0.3.0
Severity: serious

Hi,

This package does not Depend on libsplashy0, so applications cannot
link to the shared library.

regards,
guillem

--- End Message ---
--- Begin Message ---
Source: splashy
Source-Version: 0.3.1

We believe that the bug you reported is fixed in the latest version of
splashy, which is due to be installed in the Debian FTP archive:

libsplashy0-dev_0.3.1_i386.deb
  to pool/main/s/splashy/libsplashy0-dev_0.3.1_i386.deb
libsplashy0_0.3.1_i386.deb
  to pool/main/s/splashy/libsplashy0_0.3.1_i386.deb
splashy_0.3.1.dsc
  to pool/main/s/splashy/splashy_0.3.1.dsc
splashy_0.3.1.tar.gz
  to pool/main/s/splashy/splashy_0.3.1.tar.gz
splashy_0.3.1_i386.deb
  to pool/main/s/splashy/splashy_0.3.1_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tim Dijkstra <[EMAIL PROTECTED]> (supplier of updated splashy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 13 Feb 2007 17:12:15 +0100
Source: splashy
Binary: libsplashy0-dev splashy libsplashy0
Architecture: source i386
Version: 0.3.1
Distribution: unstable
Urgency: low
Maintainer: Splashy Devel <[EMAIL PROTECTED]>
Changed-By: Tim Dijkstra <[EMAIL PROTECTED]>
Description: 
 libsplashy0 - Library to draw splash screen on boot, shutdown, resume or suspen
 libsplashy0-dev - Library to draw splash screen on boot, shutdown, resume or 
suspen
 splashy- A complete user-space boot splash system
Closes: 410348 410395 410662
Changes: 
 splashy (0.3.1) unstable; urgency=low
 .
   [ Otavio Salvador ]
   * Disable JPEG support since doesn't make sense since we already do for
 GIF and PNG:
 - debian/control: libsplashy0 doesn't need libdirectfb-extra anymore;
 - src/Makefile.am:
   . remove jpeg com directfb-config calls;
   . remove JPEG symbols from DFBHACK variable;
 - themes/default:
   . convert all jpeg files to png;
   . themes.xml changed according;
 - Makefile.am: change theme files according;
 - scripts/initramfs-tools/hooks/libsplashy.in: remove jpeg library;
   * debian/rules: create make-snapshot target to be easier to make
 development snapshots;
 .
   [ Tim Dijkstra ]
   * Add libsplashy to the depends of libsplashy-dev (closes: #410348)
   * Fix 64bit build (Use socklen_t instead of size_t) (closes: #410395)
   * Make init script trigger on (no)splash on the kernel command line
 (closes: #410662)
   * Remove GIF support too.
   * Add a suspend.png image.
Files: 
 026571c8911fb6e2f2ddf6903d719669 796 graphics optional splashy_0.3.1.dsc
 8db53b0e91f8236b53a3db9f52a2e18b 1578267 graphics optional splashy_0.3.1.tar.gz
 10a134a02a365e2b178b6611c90e47c1 2047192 graphics optional 
splashy_0.3.1_i386.deb
 24ccfb3622132e6ec58cf0631b32f62e 24670 libs optional libsplashy0_0.3.1_i386.deb
 6037df9c9ed3202751abdd267b84485b 26192 libdevel optional 
libsplashy0-dev_0.3.1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF0efRLqiZQEml+FURAgfqAKCyQodOwhFSBx5g84B3y8igS7lFJQCfdtq3
x3CmObuWqP9OOOyVPh8gGzM=
=InAC
-END PGP SIGNATURE-

--- End Message ---

Bug#410830: upstart-compat-sysv: Upstart fails in the middle of boot with "Invalid message received"

[Michael Biebl]

Hi Jan,

could you please send all files (tarred) in /etc/event.d and if
available the syslog and /var/log/boot file.

Cheers,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#410830: upstart-compat-sysv: Upstart fails in the middle of boot with "Invalid message received"

[Jan Hudec]

Hello,

I forgot to point out, that the system where I experienced this bug is AMD64.
So if the problem can't be reproduced on i386, it may quite likely be
a 64-bit related error.

I can do some debugging if you tell me what what would be needed to know.

-- 
 Jan 'Bulb' Hudec <[EMAIL 
PROTECTED]>


signature.asc
Description: Digital signature

Bug#410395: marked as done (splashy: FTBFS: passing argument 3 of 'accept' from incompatible pointer type)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 19:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410395: fixed in splashy 0.3.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: splashy
Version: 0.3.0
Severity: serious

Hi,

Your package is failing to build on 64 bit arches with the following
error:
cc1: warnings being treated as errors
splashy_functions.c: In function 'spl_read_socket':
splashy_functions.c:542: warning: passing argument 3 of 'accept' from 
incompatible pointer type
splashy_functions.c:547: warning: passing argument 5 of 'getsockopt' from 
incompatible pointer type
make[3]: *** [splashy-splashy_functions.o] Error 1


Kurt


--- End Message ---
--- Begin Message ---
Source: splashy
Source-Version: 0.3.1

We believe that the bug you reported is fixed in the latest version of
splashy, which is due to be installed in the Debian FTP archive:

libsplashy0-dev_0.3.1_i386.deb
  to pool/main/s/splashy/libsplashy0-dev_0.3.1_i386.deb
libsplashy0_0.3.1_i386.deb
  to pool/main/s/splashy/libsplashy0_0.3.1_i386.deb
splashy_0.3.1.dsc
  to pool/main/s/splashy/splashy_0.3.1.dsc
splashy_0.3.1.tar.gz
  to pool/main/s/splashy/splashy_0.3.1.tar.gz
splashy_0.3.1_i386.deb
  to pool/main/s/splashy/splashy_0.3.1_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tim Dijkstra <[EMAIL PROTECTED]> (supplier of updated splashy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 13 Feb 2007 17:12:15 +0100
Source: splashy
Binary: libsplashy0-dev splashy libsplashy0
Architecture: source i386
Version: 0.3.1
Distribution: unstable
Urgency: low
Maintainer: Splashy Devel <[EMAIL PROTECTED]>
Changed-By: Tim Dijkstra <[EMAIL PROTECTED]>
Description: 
 libsplashy0 - Library to draw splash screen on boot, shutdown, resume or suspen
 libsplashy0-dev - Library to draw splash screen on boot, shutdown, resume or 
suspen
 splashy- A complete user-space boot splash system
Closes: 410348 410395 410662
Changes: 
 splashy (0.3.1) unstable; urgency=low
 .
   [ Otavio Salvador ]
   * Disable JPEG support since doesn't make sense since we already do for
 GIF and PNG:
 - debian/control: libsplashy0 doesn't need libdirectfb-extra anymore;
 - src/Makefile.am:
   . remove jpeg com directfb-config calls;
   . remove JPEG symbols from DFBHACK variable;
 - themes/default:
   . convert all jpeg files to png;
   . themes.xml changed according;
 - Makefile.am: change theme files according;
 - scripts/initramfs-tools/hooks/libsplashy.in: remove jpeg library;
   * debian/rules: create make-snapshot target to be easier to make
 development snapshots;
 .
   [ Tim Dijkstra ]
   * Add libsplashy to the depends of libsplashy-dev (closes: #410348)
   * Fix 64bit build (Use socklen_t instead of size_t) (closes: #410395)
   * Make init script trigger on (no)splash on the kernel command line
 (closes: #410662)
   * Remove GIF support too.
   * Add a suspend.png image.
Files: 
 026571c8911fb6e2f2ddf6903d719669 796 graphics optional splashy_0.3.1.dsc
 8db53b0e91f8236b53a3db9f52a2e18b 1578267 graphics optional splashy_0.3.1.tar.gz
 10a134a02a365e2b178b6611c90e47c1 2047192 graphics optional 
splashy_0.3.1_i386.deb
 24ccfb3622132e6ec58cf0631b32f62e 24670 libs optional libsplashy0_0.3.1_i386.deb
 6037df9c9ed3202751abdd267b84485b 26192 libdevel optional 
libsplashy0-dev_0.3.1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF0efRLqiZQEml+FURAgfqAKCyQodOwhFSBx5g84B3y8igS7lFJQCfdtq3
x3CmObuWqP9OOOyVPh8gGzM=
=InAC
-END PGP SIGNATURE-

--- End Message ---

Bug#410830: upstart-compat-sysv: Upstart fails in the middle of boot with "Invalid message received"

[Jan Hudec]

Package: upstart-compat-sysv
Version: 0.3.2-1
Severity: critical
Justification: breaks the whole system

After running rcS.d scripts, the boot process halts with:

init: Error while handling control message: Invalid message received

After this no further activity occurs. Pressing Ctrl-Alt-Del causes more of
these messages.

I found that the message occurs when the /etc/event.d/rc-default task issues
'telinit 2'. I placed echo both before and after the statement and the
message was printed between them.

It seems likely that the shutdown program causes the same problem when
invoked in the /etc/event.d/control-alt-delete task (the task causes it and
there is nothing else in the event).

The system information below reflects the faulty configuration -- I send this
message from system brought up via init=/bin/bash.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (100, 
'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=C, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)

Versions of packages upstart-compat-sysv depends on:
ii  initscripts 2.86.ds1-38  Scripts for initializing and shutt
ii  libc6   2.3.6.ds1-11 GNU C Library: Shared libraries
ii  sysv-rc 2.86.ds1-38  System-V-like runlevel change mech
ii  sysvinit-utils  2.86.ds1-38  System-V-like utilities
ii  upstart 0.3.2-1  event-based init daemon

upstart-compat-sysv recommends no packages.

-- no debconf information
-- 
 Jan 'Bulb' Hudec <[EMAIL 
PROTECTED]>


signature.asc
Description: Digital signature

Bug#410823: marked as done (samba: smbd segfaults during startup)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 19:47:35 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410823: samba: smbd segfaults during startup
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: samba
Version: 3.0.24-2
Severity: grave
Justification: renders package unusable

After upgrading samba (3.0.23d-4) to 3.0.24-2, smbd doesn't restart !
I receive a "Panic or segfault in Samba" mail, and /var/log/samba/log.smbd
contains at the end:
---
[2007/02/13 18:15:36, 0] smbd/server.c:main(847)
  smbd version 3.0.24 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/02/13 18:15:36, 0] passdb/pdb_interface.c:make_pdb_method_name(174)
  No builtin nor plugin backend for tdbsam guest found
[2007/02/13 18:15:36, 0] lib/util.c:smb_panic(1599)
  PANIC (pid 13686): pdb_get_methods_reload: failed to get pdb methods for
backend tdbsam guest

[2007/02/13 18:15:36, 0] lib/util.c:log_stack_trace(1706)
  BACKTRACE: 7 stack frames:
   #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822bf23]
   #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c016]
   #2 /usr/sbin/smbd [0x81eae01]
   #3 /usr/sbin/smbd(initialize_password_db+0xe) [0x81eae4e]
   #4 /usr/sbin/smbd(main+0x591) [0x82c28b1]
   #5 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0x419dfea8]
   #6 /usr/sbin/smbd [0x8082b21]
[2007/02/13 18:15:36, 0] lib/util.c:smb_panic(1607)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 13686]
[2007/02/13 18:15:36, 0] lib/util.c:smb_panic(1615)
  smb_panic(): action returned status 0
[2007/02/13 18:15:36, 0] lib/fault.c:dump_core(173)
  dumping core in /var/log/samba/cores/smbd
---

My configuration was perfectly working with previous version.  I'm now
reverting to previous version because I *need* something working.
Sadly, Debian mirrors don't keep the previous version in this case of
harmful upgrade, but by chance I did burn some binary DVDs recently.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages samba depends on:
ii  debconf  1.5.11  Debian configuration management sy
ii  libacl1  2.2.41-1Access control list shared library
ii  libattr1 2.4.32-1Extended attribute shared library
ii  libc62.3.6.ds1-10GNU C Library: Shared libraries
ii  libcomer 1.39+1.40-WIP-2006.11.14+dfsg-1 common error description library
ii  libcupsy 1.2.7-4 Common UNIX Printing System(tm) - 
ii  libgnutl 1.4.4-3 the GNU TLS library - runtime libr
ii  libkrb53 1.4.4-6 MIT Kerberos runtime libraries
ii  libldap2 2.1.30-13.2 OpenLDAP libraries
ii  libpam-m 0.79-4  Pluggable Authentication Modules f
ii  libpam-r 0.79-4  Runtime support for the PAM librar
ii  libpam0g 0.79-4  Pluggable Authentication Modules l
ii  libpopt0 1.10-3  lib for parsing cmdline parameters
ii  logrotat 3.7.1-3 Log rotation utility
ii  lsb-base 3.1-22  Linux Standard Base 3.1 init scrip
ii  netbase  4.29Basic TCP/IP networking system
ii  procps   1:3.2.7-3   /proc file system utilities
ii  samba-co 3.0.24-2Samba common files used by both th
ii  zlib1g   1:1.2.3-13  compression library - runtime

Versions of packages samba recommends:
pn  smbldap-tools  (no description available)

-- debconf information:
* samba/run_mode: daemons
  samba/tdbsam: false
  samba/generate_smbpasswd: true

-- 
Hope this helps,
Fabien.

--- End Message ---
--- Begin Message ---
Version: 3.0.24-2

Quoting Fabien COUTANT ([EMAIL PROTECTED]):
> Package: samba
> Version: 3.0.24-2
> Severity: grave
> Justification: renders package unusable
> 
> After upgrading samba (3.0.23d-4) to 3.0.24-2, smbd doesn't restart !
> I receive a "Panic or segfault in Samba" mail, and /var/log/samba/log.smbd
> contains at the end:
> ---
> [2007/02/13 18:15:36, 0] smbd/server.c:main(847)
>   smbd version 3.0.24 started.
>   Copyright Andrew Tridgell and the S

Processed: Re: Bug#410806: linux-image-2.6.18-4-xen-686: kernel panic on XEN P III Xeon

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 410806 normal
Bug#410806: linux-image-2.6.18-4-xen-686: kernel panic on XEN P III Xeon
Severity set to `normal' from `critical'

> 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]

Bug#410807: linux-image-2.6.18-4-xen-686: kernel panic on XEON P III XEN /xen/core/evtchn.c

[Bastian Blank]

severity 410807 normal
thanks

On Tue, Feb 13, 2007 at 02:56:39PM +0100, Radek Antoniuk wrote:
> Justification: breaks the whole system

No.

Bastian

-- 
Respect is a rational process
-- McCoy, "The Galileo Seven", stardate 2822.3


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410824: upgrade fails: sed: -e expression #1, char 120: unterminated `s' command

[Michael Prokop]

Package: ntlmaps
Version: 0.9.9.0.1-5
Severity: grave
Justification: renders package unusable


# apt-get upgrade
[...]
Setting up ntlmaps (0.9.9.0.1-5) ...
sed: -e expression #1, char 120: unterminated `s' command
dpkg: error processing ntlmaps (--configure):
 subprocess post-installation script returned error exit status 1
[...]

regards,
-mika-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410821: mysql-server-5.0: mysqld dies with '*** glibc detected *** double free or corruption (!prev): 0x08dd1dd0 ***'

[Jonas Meurer]

Package: mysql-server-5.0
Version: 5.0.32-3
Severity: grave
Justification: causes non-serious data loss


Hello,

Since yesterday, we do have mysql crashs on one of our servers running 
debian/etch.

We had this crash once yesterday night, and once today.

The error log in /var/log/syslog is:
Feb 13 17:02:32 merkur86 mysqld[15652]: *** glibc detected *** double free or 
corruption (!prev): 0x08b26088 ***
Feb 13 17:02:32 merkur86 mysqld[15652]: mysqld got signal 6;
Feb 13 17:02:32 merkur86 mysqld[15652]: This could be because you hit a bug. It 
is also possible that this binary
Feb 13 17:02:32 merkur86 mysqld[15652]: or one of the libraries it was linked 
against is corrupt, improperly built,
Feb 13 17:02:32 merkur86 mysqld[15652]: or misconfigured. This error can also 
be caused by malfunctioning hardware.
Feb 13 17:02:32 merkur86 mysqld[15652]: We will try our best to scrape up some 
info that will hopefully help diagnose
Feb 13 17:02:32 merkur86 mysqld[15652]: the problem, but since we have already 
crashed, something is definitely wrong
Feb 13 17:02:32 merkur86 mysqld[15652]: and this may fail.
Feb 13 17:02:32 merkur86 mysqld[15652]:
Feb 13 17:02:32 merkur86 mysqld[15652]: key_buffer_size=16777216
Feb 13 17:02:32 merkur86 mysqld[15652]: read_buffer_size=131072
Feb 13 17:02:32 merkur86 mysqld[15652]: max_used_connections=16
Feb 13 17:02:32 merkur86 mysqld[15652]: max_connections=100
Feb 13 17:02:32 merkur86 mysqld[15652]: threads_connected=14
Feb 13 17:02:32 merkur86 mysqld[15652]: It is possible that mysqld could use up 
to
Feb 13 17:02:32 merkur86 mysqld[15652]: key_buffer_size + (read_buffer_size + 
sort_buffer_size)*max_connections = 233983 K
Feb 13 17:02:32 merkur86 mysqld[15652]: bytes of memory
Feb 13 17:02:32 merkur86 mysqld[15652]: Hope that's ok; if not, decrease some 
variables in the equation.
Feb 13 17:02:32 merkur86 mysqld[15652]:
Feb 13 17:02:32 merkur86 mysqld[15652]: thd=0x8b186d0
Feb 13 17:02:32 merkur86 mysqld[15652]: Attempting backtrace. You can use the 
following information to find out
Feb 13 17:02:32 merkur86 mysqld[15652]: where mysqld died. If you see no 
messages after this, something went
Feb 13 17:02:32 merkur86 mysqld[15652]: terribly wrong...
Feb 13 17:02:32 merkur86 mysqld[15652]: Cannot determine thread, fp=0xb0e78558, 
backtrace may not be correct.
Feb 13 17:02:32 merkur86 mysqld[15652]: Stack range sanity check OK, backtrace 
follows:
Feb 13 17:02:32 merkur86 mysqld[15652]: 0x81c0649
Feb 13 17:02:32 merkur86 mysqld[15652]: 0xb7cfb947
Feb 13 17:02:32 merkur86 mysqld[15652]: 0xb7cfd0c9
Feb 13 17:02:32 merkur86 mysqld[15652]: 0xb7d30fda
Feb 13 17:02:32 merkur86 mysqld[15652]: 0xb7d3889f
Feb 13 17:02:32 merkur86 mysqld[15652]: 0xb7d38942
Feb 13 17:02:32 merkur86 mysqld[15652]: 0x8484df3
Feb 13 17:02:32 merkur86 mysqld[15652]: 0x81dbc5d
Feb 13 17:02:32 merkur86 mysqld[15652]: 0x81dd188
Feb 13 17:02:32 merkur86 mysqld[15652]: 0x81ddb94
Feb 13 17:02:32 merkur86 mysqld[15652]: 0xb7f640bd
Feb 13 17:02:32 merkur86 mysqld[15652]: 0xb7d9e93e
Feb 13 17:02:32 merkur86 mysqld[15652]: New value of fp=(nil) failed sanity 
check, terminating stack trace!
Feb 13 17:02:32 merkur86 mysqld[15652]: Please read 
http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow 
instructions on how to resolve the stack trace. Resolved
Feb 13 17:02:32 merkur86 mysqld[15652]: stack trace is much more helpful in 
diagnosing the problem, so please do
Feb 13 17:02:32 merkur86 mysqld[15652]: resolve it
Feb 13 17:02:32 merkur86 mysqld[15652]: Trying to get some variables.
Feb 13 17:02:32 merkur86 mysqld[15652]: Some pointers may be invalid and cause 
the dump to abort...
Feb 13 17:02:32 merkur86 mysqld[15652]: thd->query at (nil)  is invalid pointer
Feb 13 17:02:32 merkur86 mysqld[15652]: thd->thread_id=66
Feb 13 17:02:32 merkur86 mysqld[15652]: The manual page at 
http://www.mysql.com/doc/en/Crashing.html contains
Feb 13 17:02:32 merkur86 mysqld[15652]: information that should help you find 
out what is causing the crash.

I already did this 'stack trace':

[ copied the 0x... hex digits to mysqld.stack]
# cp /usr/share/doc/mysql-server-5.0/mysqld.sym.gz
# gzip -d mysqld.sym.gz
# resolve_stack_dump -s mysqld.sym -n mysqld.stack
0x81c0649 handle_segfault + 681
0xb7cfb947 _end + -1352585609
0xb7cfd0c9 _end + -1352579591
0xb7d30fda _end + -1352366838
0xb7d3889f _end + -1352335921
0xb7d38942 _end + -1352335758
0x8484df3 free_root + 67
0x81dbc5d _Z16dispatch_command19enum_server_commandP3THDPcj + 509
0x81dd188 _Z10do_commandP3THD + 136
0x81ddb94 handle_one_connection + 2308
0xb7f640bd _end + -1350060563
0xb7d9e93e _end + -1351917970

We do have a mysql backup script running every 30 Minutes. Maybe this
one is the reason for the crash, but regardless whatever the reason
may be, mysqld should not crash ever.

See the script mysql-backup.sh attached.

...
 jonas

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked t

Processed: Re: Bug#410815: ppc daily netinst CD (12-Feb-07) missing ibmveth module

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 410815 wishlist
Bug#410815: ppc daily netinst CD (12-Feb-07) missing ibmveth module
Severity set to `wishlist' from `grave'

> reassign 410815 linux-kernel-di-powerpc-2.6
Bug#410815: ppc daily netinst CD (12-Feb-07) missing ibmveth module
Bug reassigned from package `cdrom' to `linux-kernel-di-powerpc-2.6'.

> tags 410815 pending
Bug#410815: ppc daily netinst CD (12-Feb-07) missing ibmveth module
There were no tags set.
Tags added: pending

> 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]

Bug#410815: ppc daily netinst CD (12-Feb-07) missing ibmveth module

[Frans Pop]

severity 410815 wishlist
reassign 410815 linux-kernel-di-powerpc-2.6
tags 410815 pending
thanks

On Tuesday 13 February 2007 17:35, Cort, Tom wrote:
> Severity: grave

This does not even come close to being grave. It is merely a request to 
support this driver in installations so that your particular hardware or 
configuration can be supported. I.e: wishlist.

> As far as I can tell, the daily build network install CD for Debian/ppc
> 4.0 (etch) from 12-Feb-07 does not include the ibmveth module (ibm
> virtual ethernet driver; i.e. CONFIG_IBMVETH). This affects anyone
> using POWER5 virtualization with virtual ethernet. It makes it
> impossible to do a network install on a logical partition.

The module seems to be available in linux-image-2.6.18-4-powerpc64 and 
thus can be added to the kernel udebs for powerpc64. I have added it to 
the nic-extra-modules udeb and it will be included in the next upload.

Cheers,
FJP


pgpvnRnsR7XgT.pgp
Description: PGP signature

Bug#410806: linux-image-2.6.18-4-xen-686: kernel panic on XEN P III Xeon

[Bastian Blank]

severity 410806 normal
thanks

On Tue, Feb 13, 2007 at 02:54:52PM +0100, Radek Antoniuk wrote:
> Justification: breaks the whole system

No. It is no regression, no oops and the system does not stop logging.

Bastian

-- 
The more complex the mind, the greater the need for the simplicity of play.
-- Kirk, "Shore Leave", stardate 3025.8


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410823: samba: smbd segfaults during startup

[Fabien COUTANT]

Package: samba
Version: 3.0.24-2
Severity: grave
Justification: renders package unusable

After upgrading samba (3.0.23d-4) to 3.0.24-2, smbd doesn't restart !
I receive a "Panic or segfault in Samba" mail, and /var/log/samba/log.smbd
contains at the end:
---
[2007/02/13 18:15:36, 0] smbd/server.c:main(847)
  smbd version 3.0.24 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/02/13 18:15:36, 0] passdb/pdb_interface.c:make_pdb_method_name(174)
  No builtin nor plugin backend for tdbsam guest found
[2007/02/13 18:15:36, 0] lib/util.c:smb_panic(1599)
  PANIC (pid 13686): pdb_get_methods_reload: failed to get pdb methods for
backend tdbsam guest

[2007/02/13 18:15:36, 0] lib/util.c:log_stack_trace(1706)
  BACKTRACE: 7 stack frames:
   #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822bf23]
   #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c016]
   #2 /usr/sbin/smbd [0x81eae01]
   #3 /usr/sbin/smbd(initialize_password_db+0xe) [0x81eae4e]
   #4 /usr/sbin/smbd(main+0x591) [0x82c28b1]
   #5 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0x419dfea8]
   #6 /usr/sbin/smbd [0x8082b21]
[2007/02/13 18:15:36, 0] lib/util.c:smb_panic(1607)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 13686]
[2007/02/13 18:15:36, 0] lib/util.c:smb_panic(1615)
  smb_panic(): action returned status 0
[2007/02/13 18:15:36, 0] lib/fault.c:dump_core(173)
  dumping core in /var/log/samba/cores/smbd
---

My configuration was perfectly working with previous version.  I'm now
reverting to previous version because I *need* something working.
Sadly, Debian mirrors don't keep the previous version in this case of
harmful upgrade, but by chance I did burn some binary DVDs recently.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages samba depends on:
ii  debconf  1.5.11  Debian configuration management sy
ii  libacl1  2.2.41-1Access control list shared library
ii  libattr1 2.4.32-1Extended attribute shared library
ii  libc62.3.6.ds1-10GNU C Library: Shared libraries
ii  libcomer 1.39+1.40-WIP-2006.11.14+dfsg-1 common error description library
ii  libcupsy 1.2.7-4 Common UNIX Printing System(tm) - 
ii  libgnutl 1.4.4-3 the GNU TLS library - runtime libr
ii  libkrb53 1.4.4-6 MIT Kerberos runtime libraries
ii  libldap2 2.1.30-13.2 OpenLDAP libraries
ii  libpam-m 0.79-4  Pluggable Authentication Modules f
ii  libpam-r 0.79-4  Runtime support for the PAM librar
ii  libpam0g 0.79-4  Pluggable Authentication Modules l
ii  libpopt0 1.10-3  lib for parsing cmdline parameters
ii  logrotat 3.7.1-3 Log rotation utility
ii  lsb-base 3.1-22  Linux Standard Base 3.1 init scrip
ii  netbase  4.29Basic TCP/IP networking system
ii  procps   1:3.2.7-3   /proc file system utilities
ii  samba-co 3.0.24-2Samba common files used by both th
ii  zlib1g   1:1.2.3-13  compression library - runtime

Versions of packages samba recommends:
pn  smbldap-tools  (no description available)

-- debconf information:
* samba/run_mode: daemons
  samba/tdbsam: false
  samba/generate_smbpasswd: true

-- 
Hope this helps,
Fabien.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#410807: linux-image-2.6.18-4-xen-686: kernel panic on XEON P III XEN /xen/core/evtchn.c

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 410807 normal
Bug#410807: linux-image-2.6.18-4-xen-686: kernel panic on XEON P III XEN 
/xen/core/evtchn.c
Severity set to `normal' from `critical'

> 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]

Bug#410817: linux-image-2.6.18-3-686: new megaraid driver fails to detect logical drive

[Mark Weaver]

Package: linux-image-2.6.18-3-686
Version: 2.6.18-7
Severity: critical
Justification: breaks the whole system

This is the relevant portion of dmesg from the sarge kernel:

Feb 11 06:52:03 clap kernel: Linux version 2.6.8-3-686-smp ([EMAIL PROTECTED]) (
gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP Tue Dec 5 23:17:50 UTC 2006
Feb 11 06:52:03 clap kernel: SCSI subsystem initialized
Feb 11 06:52:03 clap kernel: ACPI: PCI interrupt :01:02.0[A] -> GSI 17 (leve
l, low) -> IRQ 193
Feb 11 06:52:03 clap kernel: megaraid: found 0x101e:0x1960:bus 1:slot 2:func 0
Feb 11 06:52:03 clap kernel: scsi0:Found MegaRAID controller at 0xf8829000, IRQ:
193
Feb 11 06:52:03 clap kernel: megaraid: [6.62:1.03] detected 1 logical drives.
Feb 11 06:52:03 clap kernel: megaraid: supports extended CDBs.
Feb 11 06:52:03 clap kernel: megaraid: channel[0] is raid.
Feb 11 06:52:03 clap kernel: megaraid: channel[1] is raid.
Feb 11 06:52:03 clap kernel: megaraid: channel[2] is raid.
Feb 11 06:52:03 clap kernel: megaraid: channel[3] is raid.
Feb 11 06:52:03 clap kernel: scsi0 : LSI Logic MegaRAID 6.62 254 commands 16 tar
gs 7 chans 7 luns
Feb 11 06:52:03 clap kernel: scsi0: scanning scsi channel 0 for logical drives.
Feb 11 06:52:03 clap kernel:   Vendor: MegaRAID  Model: LD 0 RAID1  228G  Rev: 6
.62
Feb 11 06:52:03 clap kernel:   Type:   Direct-Access  ANSI S
CSI revision: 02
Feb 11 06:52:03 clap kernel: SCSI device sda: 468697088 512-byte hdwr sectors (2
39973 MB)
Feb 11 06:52:03 clap kernel: sda: asking for cache data failed
Feb 11 06:52:03 clap kernel: sda: assuming drive cache: write through
Feb 11 06:52:03 clap kernel:  /dev/scsi/host0/bus0/target0/lun0: p1
Feb 11 06:52:03 clap kernel: Attached scsi disk sda at scsi0, channel 0, id 0, l
un 0
Feb 11 06:52:03 clap kernel: scsi0: scanning scsi channel 1 for logical drives.
Feb 11 06:52:03 clap kernel: scsi0: scanning scsi channel 2 for logical drives.
Feb 11 06:52:03 clap kernel: scsi0: scanning scsi channel 4 [P0] for physical de
vices.
Feb 11 06:52:03 clap kernel: scsi0: scanning scsi channel 5 [P1] for physical de
vices.
Feb 11 06:52:03 clap kernel: scsi0: scanning scsi channel 6 [P2] for physical de
vices.
Feb 11 06:52:03 clap kernel: scsi0: scanning scsi channel 7 [P3] for physical de
vices.

And this is from the etch kernel:
Feb 11 00:35:24 clap kernel: megaraid: 2.20.4.9 (Release Date: Sun Jul 16 12:27:
22 EST 2006)
Feb 11 00:35:24 clap kernel: megaraid: probe new device 0x101e:0x1960:0x1028:0x0
511: bus 1:slot 2:func 0
Feb 11 00:35:24 clap kernel: ACPI: PCI Interrupt :01:02.0[A] -> GSI 17 (leve
l, low) -> IRQ 177
Feb 11 00:35:24 clap kernel: megaraid: fw version:[6.62] bios version:[1.03]
Feb 11 00:35:24 clap kernel: scsi0 : LSI Logic MegaRAID driver
Feb 11 00:35:24 clap kernel: scsi[0]: scanning scsi channel 0 [Phy 0] for non-ra
id devices
Feb 11 00:35:24 clap kernel: scsi[0]: scanning scsi channel 1 [Phy 1] for non-ra
id devices
Feb 11 00:35:24 clap kernel: e1000: :00:02.0: e1000_probe: (PCI:33MHz:32-bit
) 00:c0:9f:29:68:31
Feb 11 00:35:24 clap kernel: scsi[0]: scanning scsi channel 2 [Phy 2] for non-ra
id devices
Feb 11 00:35:24 clap kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
 Connection
Feb 11 00:35:24 clap kernel: ACPI: PCI Interrupt :00:04.0[A] -> GSI 25 (leve
l, low) -> IRQ 193
Feb 11 00:35:24 clap kernel: scsi[0]: scanning scsi channel 3 [Phy 3] for non-ra
id devices
Feb 11 00:35:24 clap kernel: scsi[0]: scanning scsi channel 4 [virtual] for logi
cal drives

I have stuck an  IDE boot drive in the machine (it is in a hosting center
and I don't have any other similarly broken machines), so I can now reboot 
it remotely for experimental purposes if required, and am happy to collect
any information required.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-3-686-smp
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.18-3-686 depends on:
ii  coreutils 5.97-5 The GNU core utilities
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85e  tools for generating an initramfs
ii  module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-3-686 recommends:
pn  libc6-i686 (no description available)

-- debconf information:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686:
  linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/kimage-is-a-directory:
  linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true
  linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true
  linux-image-2.6.18-

Bug#410815: ppc daily netinst CD (12-Feb-07) missing ibmveth module

[Cort, Tom]

Package: cdrom
Version: 4.0
Severity: grave

As far as I can tell, the daily build network install CD for Debian/ppc 4.0
(etch) from 12-Feb-07 does not include the ibmveth module (ibm virtual
ethernet driver; i.e. CONFIG_IBMVETH). This affects anyone using POWER5
virtualization with virtual ethernet. It makes it impossible to do a network
install on a logical partition.

Boot the CD using 'expert64'
Select 'Execute a shell'
~ # modprobe ibmveth
FATAL: Module ibmveth not found.
~ # ifconfig eth0 up
SIOCGIFFLAGS: No such device

Please include the driver on the network install CD.


smime.p7s
Description: S/MIME cryptographic signature

Bug#410727: kaffeine crashes attempting to play videos

[Lisandro Damián Nicanor Pérez Meyer]

> What video type you try to play ? i tried avi files without any crash.

Try to open with konqueror www.tn.com.ar . After some buffering, a stream of 
video will apair.
Right-click over the video and select "Open in an external program, kaffeine" 
(or something alike, I have a spanish instalation).

Once again, after some buffering, the video will appear. Close Kaffeine's 
window. After some seconds, a KDE error message appears.

Regards, Lisandro.

-- 
¿Qué vamos a hacer esta noche Cerebro?
-Lo mismo que todas las noches Pinky...
¡¡¡tratar de conquistar el mundo!!!
  Pinky y Cerebro. Narf.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/

Bug#410807: linux-image-2.6.18-4-xen-686: kernel panic on XEON P III XEN /xen/core/evtchn.c

[Radek Antoniuk]

Package: linux-image-2.6.18-4-xen-686
Version: 2.6.18.dfsg.1-10
Severity: critical
Justification: breaks the whole system



esx kernel: [ cut here ]
 esx kernel: kernel BUG at drivers/xen/core/evtchn.c:481!
 esx kernel: invalid opcode:  [#1]
 esx kernel: SMP
 esx kernel: CPU:1
 esx kernel: EIP is at retrigger+0x1f/0x35
 esx kernel: eax:    ebx: 0208   ecx: 0049   edx: f55f6000
 esx kernel: esi: c0318c20   edi: 0129   ebp:    esp: c039feb0
 esx kernel: ds: 007b   es: 007b   ss: 0069
 esx kernel: Process xenwatch (pid: 17, ti=c039e000 task=c0ea3550 
task.ti=c039e000)
 esx kernel: Stack: c013b259 c0318c20 0129 c0318c48 c013afaf e4952ec0 
 
 esx kernel: e4952ec0 c02170d8  c02174b8 c0210647 0010  
020c
 esx kernel: 020b   e7d2d176 c02e67a4 ee566000  
0002
 esx kernel: Call Trace:
 esx kernel: Code: ee 85 f6 75 96 58 5a 5b 5e 5f 5d c3 0f b7 0c 85 40 b8 37 c0 
8b 15 84 19 2d c0 85 c9 74 1d 0f a3 8a 80 08 00 00 19 c0 85 c0 75 08 <0f> 0b e1 
01 a0 1a 2b c0 f0 0f ab 8a 00 08 00 00 b8 01 00 00 00
 esx kernel: EIP: [] retrigger+0x1f/0x35 SS:ESP 0069:c039feb0



-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-xen-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.18-4-xen-686 depends on:
ii  initramfs-tools 0.85etools for generating an initramfs
ii  linux-modules-2.6.18-4- 2.6.18.dfsg.1-10 Linux 2.6.18 modules on i686

Versions of packages linux-image-2.6.18-4-xen-686 recommends:
ii  libc6-xen   2.3.6.ds1-11 GNU C Library: Shared libraries [X

-- debconf-show failed


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: tagging 410403

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.27
> tags 410403 + patch
Bug#410403: kismet: FTBFS on 64 it arches: gpsmap.cc:2249: error: cast from 
'void*' to 'int' loses precision
There were no tags set.
Tags added: patch

>
End of message, 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]

Bug#410806: linux-image-2.6.18-4-xen-686: kernel panic on XEN P III Xeon

[Radek Antoniuk]

Package: linux-image-2.6.18-4-xen-686
Version: 2.6.18.dfsg.1-10
Severity: critical
Justification: breaks the whole system

Feb 13 14:16:20 esx2 kernel: audit(1171372541.586:27): dev=vif13.0 prom=256 
old_prom=0 auid=4294967295
Feb 13 14:16:20 esx2 kernel: ADDRCONF(NETDEV_UP): vif13.0: link is not ready
Feb 13 14:16:22 esx2 kernel: [ cut here ]
Feb 13 14:16:22 esx2 kernel: kernel BUG at mm/memory.c:2239!
Feb 13 14:16:22 esx2 kernel: invalid opcode:  [#1]
Feb 13 14:16:22 esx2 kernel: SMP
Feb 13 14:16:22 esx2 kernel: Modules linked in: ip_conntrack nfnetlink x25 
appletalk ipx p8023 rose netrom ax25 xt_physdev ip
table_filter ip_tables x_tables bridge netloop ipv6 dm_snapshot dm_mirror 
dm_mod ide_disk tsdev psmouse i2c_i801 serio_raw fl
oppy e752x_edac edac_mc i2c_core pcspkr evdev serial_core shpchp pci_hotplug 
rtc sg ext3 jbd mbcache ide_cd sd_mod cdrom piix
 generic megaraid_mbox scsi_mod megaraid_mm ehci_hcd e1000 ide_core uhci_hcd 
usbcore thermal processor fan
Feb 13 14:16:22 esx2 kernel: CPU:2
Feb 13 14:16:22 esx2 kernel: EIP:0061:[]Not tainted VLI
Feb 13 14:16:22 esx2 kernel: EFLAGS: 00210202   (2.6.18-4-xen-686 #1)
Feb 13 14:16:22 esx2 kernel: EIP is at __handle_mm_fault+0x5ea/0xfa3
Feb 13 14:16:22 esx2 kernel: eax: c02e5cb4   ebx:    ecx:    
edx: 0c78
Feb 13 14:16:22 esx2 kernel: esi: c0332e8c   edi: c0332e8c   ebp:    
esp: c9d91d40
Feb 13 14:16:22 esx2 kernel: ds: 007b   es: 007b   ss: 0069
Feb 13 14:16:22 esx2 kernel: Process xc_save (pid: 24083, ti=c9d9 
task=e2196aa0 task.ti=c9d9)
Feb 13 14:16:22 esx2 kernel: Stack: c0f804c4 c01666ac b7f8f000 c0332e8c 
c9eade40   
Feb 13 14:16:22 esx2 kernel:   c089adf8 
c0743c78 0013 000a c0b2f768
Feb 13 14:16:22 esx2 kernel:000a c013c3ca  0c78 
c011315c 0001 001f 8000
Feb 13 14:16:22 esx2 kernel: Call Trace:
Feb 13 14:16:22 esx2 kernel:  [] __link_path_walk+0xbe4/0xd1d
Feb 13 14:16:22 esx2 kernel:  [] init_bio+0x9/0xd3
Feb 13 14:16:22 esx2 kernel:  [] find_get_page+0x37/0x3c
Feb 13 14:16:22 esx2 kernel:  [] __kmap_atomic+0xe7/0x150
Feb 13 14:16:22 esx2 kernel:  [] kmap_atomic+0x11/0x14
Feb 13 14:16:22 esx2 kernel:  [] dput+0x1a/0x11b
Feb 13 14:16:22 esx2 kernel:  [] find_get_page+0x37/0x3c
Feb 13 14:16:22 esx2 kernel:  [] filemap_nopage+0x19c/0x312
Feb 13 14:16:22 esx2 kernel:  [] __put_user_4+0x12/0x18
Feb 13 14:16:22 esx2 kernel:  [] init_bio+0x9/0xd3
Feb 13 14:16:22 esx2 kernel:  [] do_page_fault+0x6af/0xb76
Feb 13 14:16:22 esx2 kernel:  [] free_hot_cold_page+0xc1/0x126
Feb 13 14:16:22 esx2 kernel:  [] do_page_fault+0x0/0xb76
Feb 13 14:16:22 esx2 kernel:  [] error_code+0x2b/0x30
Feb 13 14:16:22 esx2 kernel:  [] __get_user_4+0x11/0x17
Feb 13 14:16:22 esx2 kernel:  [] privcmd_ioctl+0x2e6/0x36d
Feb 13 14:16:22 esx2 kernel:  [] vma_prio_tree_insert+0x17/0x2a
Feb 13 14:16:22 esx2 kernel:  [] vma_link+0xa2/0xbe
Feb 13 14:16:22 esx2 kernel:  [] do_ioctl+0x47/0x5d
Feb 13 14:16:22 esx2 kernel:  [] vfs_ioctl+0x24a/0x25c
Feb 13 14:16:22 esx2 kernel:  [] sys_ioctl+0x48/0x5f
Feb 13 14:16:22 esx2 kernel:  [] syscall_call+0x7/0xb
Feb 13 14:16:22 esx2 kernel: Code: b0 01 8b 74 24 48 86 06 e9 73 09 00 00 89 e8 
e8 13 a0 ff ff eb ea 8b 7c 24 0c c7 84 24 e4
00 00 00 02 00 00 00 f6 47 19 04 74 08 <0f> 0b bf 08 4c 19 2a c0 8b 54 24 0c 8b 
42 4c 85 c0 75 12 c7 44
Feb 13 14:16:22 esx2 kernel: EIP: [] __handle_mm_fault+0x5ea/0xfa3 
SS:ESP 0069:c9d91d40
Feb 13 14:16:24 esx2 kernel:  <6>ADDRCONF(NETDEV_CHANGE): vif13.0: link becomes 
ready
Feb 13 14:16:24 esx2 kernel: xenbr0: port 3(vif13.0) entering learning state
Feb 13 14:16:24 esx2 kernel: xenbr0: topology change detected, propagating
Feb 13 14:16:24 esx2 kernel: xenbr0: port 3(vif13.0) entering forwarding state
Feb 13 14:16:32 esx2 kernel: xenbr1: port 4(vif6.0) entering disabled state
Feb 13 14:16:32 esx2 kernel: device vif6.0 left promiscuous mode
Feb 13 14:16:32 esx2 kernel: audit(1171372592.989:28): dev=vif6.0 prom=0 
old_prom=256 auid=4294967295
Feb 13 14:16:32 esx2 kernel: xenbr1: port 4(vif6.0) entering disabled state
Feb 13 14:16:42 esx2 kernel: xenbr1: port 5(vif7.0) entering disabled state
Feb 13 14:16:42 esx2 kernel: device vif7.0 left promiscuous mode
Feb 13 14:16:42 esx2 kernel: audit(1171372602.302:29): dev=vif7.0 prom=0 
old_prom=256 auid=4294967295
Feb 13 14:16:42 esx2 kernel: xenbr1: port 5(vif7.0) entering disabled state



-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-xen-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.18-4-xen-686 depends on:
ii  initramfs-tools 0.85etools for generating an initramfs
ii  linux-modules-2.6.18-4- 2.6.18.dfsg.1-10 Linux 2.6.18 modules on i686

Versions of packages linux-image-2.6.18-4-xen-686 recom

Bug#410794: kmail: Imap messages become blank

[Pierre Habouzit]

severity 410794 important
thanks

On Tue, Feb 13, 2007 at 12:09:40PM +, Laurence Abbott wrote:
> Package: kmail
> Version: 4:3.5.5.dfsg.1-6
> Severity: grave
> Justification: causes non-serious data loss

  Sorry there is no data loss, it's merely a local index corruption. A
woraround is to move the blank message in an other _IMAP_ folder of the
same server, and move it back. The message won't it blank anymore.

  The message on the imap server _is_ not altered at all. Changing the
serverity accordingly.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgprF5TBcxiQ7.pgp
Description: PGP signature

Processed: Re: Bug#410794: kmail: Imap messages become blank

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 410794 important
Bug#410794: kmail: Imap messages become blank
Severity set to `important' from `grave'

> 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]

Bug#410794: further info

[Laz]

If I remove an IMAP account with a blank message and then add it again, 
the blank message reappears.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410803: twiki: postinst relies on data in /usr/share/doc

[Gerfried Fuchs]

Package: twiki
Version: 1:4.0.5-8
Severity: serious
Justification: Policy 12.3

Hi!

 While translating the debconf po file to german I stumbled upon this
problem that the postinst script unpacks data from /usr/share/doc.
Please be made aware of this passage from the policy:

#v+
 Packages must not require the existence of any files in
 `/usr/share/doc/' in order to function [1].  Any files that are
 referenced by programs but are also useful as stand alone
 documentation should be installed under `/usr/share//' with
 symbolic links from `/usr/share/doc/'.
#v-

 So please move the starter kit to /usr/share/twiki and symlink it from
the doc directory, if you really want to have it available from there,
too - and don't forget to change the tar extract line in the postinst
script.

 Thanks in advance,
Alfie
-- 
had somebody wanted to kill (or inflict maximum damage) to the project, he
couldn't have done any better than the current DPL
-- Thibaut Varene
<[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#383791: marked as done (checkstyle: source code missing for emma.jar?)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 15:15:42 +0100
with message-id <[EMAIL PROTECTED]>
and subject line checkstyle: source code missing for emma.jar?
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: checkstyle
Version: 4.1-1
Severity: serious
Justification: breaks DFSG #2

I just noticed that checkstyle_4.1.orig.tar.gz includes

checkstyle-src-4.1/lib/emma.jar

which according to

unzip -l checkstyle-src-4.1/lib/emma.jar

includes e.g.

com/vladium/emma/instr/InstrProcessorST.class

but I couldn't find source code for this file anywhere in debian. I'm
not sure but I think this violates DFSG #2 and at least
http://release.debian.org/etch_rc_policy.txt says 

 "All content in main and contrib must meet the DFSG, both in
  .debs and in the source (including the .orig.tar.gz)"

If the build process does not need emma.jar you probably could just
remove it? Otherwise I think you should include the sources as well.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.32sauna0
Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1)

--- End Message ---
--- Begin Message ---
Version: 4.1+dfsg-1


There was a typo in debian/changelog so the the bug got not closed
automatically.



Cheers,
Michael
-- 
 .''`.  | Michael Koch <[EMAIL PROTECTED]>
: :' :  | Free Java Developer 
`. `'   |
  `-| 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 483B
--- End Message ---

Processed: tagging 410754

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.27
> tags 410754 upstream
Bug#410754: version `GLIBC_2.4' not found (required by /usr/bin/rar)
There were no tags set.
Tags added: upstream

>
End of message, 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]

Bug#409242: causes kernel oops

[Adriaan Peeters]

Hi,

I have encountered these oopses as well, on a xen kernel. I now upgraded
to the stable 8.0.0 release and have not yet seen the error.

-- 
Adriaan Peeters


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410794: kmail: Imap messages become blank

[Laurence Abbott]

Package: kmail
Version: 4:3.5.5.dfsg.1-6
Severity: grave
Justification: causes non-serious data loss


Sometimes an IMAP message becomes blank, i.e. shows no content. Using a
different IMAP client shows that the content is still there. Looks like
kmail is caching the messages locally and not storing the content.

This seems to happen for messages which are currently being viewed in
kmail: going back to kmail later and the message is blank. However, this
doesn't happen every time: it has probably happened to 5 messages so far
but has only been happening in the past few weeks.

If view the source of the messages in kmail, the blank messages have
lost the majority of the headers too.

One message which had an attachment gave me a zero-byte file when I
tried to save the attachment. A couple of minutes later, the whole
message had blanked.

This is for IMAP accounts which were set up before DIMAP was introduced:
I've juse removed the account and added it again so it is definitely
IMAP and not DIMAP to see if it cures it.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (850, 'testing'), (800, 'stable'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.18-1
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages kmail depends on:
ii  kdebase-kio-plugins4:3.5.5a.dfsg.1-5 core I/O slaves for KDE
ii  kdelibs4c2a4:3.5.5a.dfsg.1-5 core libraries and binaries for al
ii  kdepim-kio-plugins 4:3.5.5.dfsg.1-6  KDE pim I/O Slaves
ii  libart-2.0-2   2.3.17-1  Library of functions for 2D graphi
ii  libaudio2  1.8-2 The Network Audio System (NAS). (s
ii  libc6  2.3.6.ds1-10  GNU C Library: Shared libraries
ii  libfontconfig1 2.4.2-1   generic font configuration library
ii  libfreetype6   2.2.1-5   FreeType 2 font engine, shared lib
ii  libgcc11:4.1.1-21GCC support library
ii  libice61:1.0.1-2 X11 Inter-Client Exchange library
ii  libidn11   0.6.5-1   GNU libidn library, implementation
ii  libjpeg62  6b-13 The Independent JPEG Group's JPEG 
ii  libkcal2b  4:3.5.5.dfsg.1-6  KDE calendaring library
ii  libkdepim1a4:3.5.5.dfsg.1-6  KDE PIM library
ii  libkleopatra1  4:3.5.5.dfsg.1-6  KDE GnuPG interface libraries
ii  libkmime2  4:3.5.5.dfsg.1-6  KDE MIME interface library
ii  libkpimidentities1 4:3.5.5.dfsg.1-6  KDE PIM user identity information 
ii  libksieve0 4:3.5.5.dfsg.1-6  KDE mail/news message filtering li
ii  libmimelib1c2a 4:3.5.5.dfsg.1-6  KDE mime library
ii  libpng12-0 1.2.15~beta5-1PNG library - runtime
ii  libqt3-mt  3:3.3.7-3 Qt GUI Library (Threaded runtime v
ii  libsm6 1:1.0.1-3 X11 Session Management library
ii  libstdc++6 4.1.1-21  The GNU Standard C++ Library v3
ii  libx11-6   2:1.0.3-5 X11 client-side library
ii  libxcursor11.1.7-4   X cursor management library
ii  libxext6   1:1.0.1-2 X11 miscellaneous extension librar
ii  libxft22.1.8.2-8 FreeType-based font drawing librar
ii  libxi6 1:1.0.1-4 X11 Input extension library
ii  libxinerama1   1:1.0.1-4.1   X11 Xinerama extension library
ii  libxrandr2 2:1.1.0.2-5   X11 RandR extension library
ii  libxrender11:0.9.1-3 X Rendering Extension client libra
ii  libxt6 1:1.0.2-2 X11 toolkit intrinsics library
ii  perl   5.8.8-7   Larry Wall's Practical Extraction 
ii  zlib1g 1:1.2.3-13compression library - runtime

Versions of packages kmail recommends:
ii  procmail  3.22-16Versatile e-mail processor

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#370186: hal: HAL keeps CD drive spinning constantly

[Daniel Schepler]

On Tuesday 13 February 2007 02:16:24 am you wrote:
> I've cc:ed everyone who followed up to this bug report reporting the same
> symptoms.  Daniel, Jürgen, could you please post the model info for your
> CDROMs as returned in the info.product string in lshal's output, so that it
> can be used in the future to provide a more refined override that might
> even be worth enabling by default in the package?

My drive's model is "HL-DT-ST DVD-RW GCA-4080N".  And I can confirm that the 
instructions posted to the bug are working for me.
-- 
Daniel Schepler

Bug#407799: desktop-base: /etc/defaults/kdm.d/10_desktop_base overrides configured login desktop without warning on upgrade

[Fathi Boudra]

hi,

> Can someone please explain why this bug is only marked as fixed in
> experimental?  Please upload a fix to unstable so that it will get real
> user testing and can be considered for etch.

It must be uploded to unstable.

> I see there has also been further discussion in the bug log about whether
> disabling the KDE override is the appropriate fix.  Is this debate still
> ongoing?

The debate is finished. Changes were done in kdebase 3.5.5a.dfsg.1-6 to fix 
the issue: if kdm theme is modified, we don't use overrides.
We don't need to disable anymore KDM override file provided in desktop-base by 
default.

> Is there any code in progress to support this alternate solution 
> on an etch timescale?

Remaining issue is the position of the swirl on the default wallpaper... not a 
critical issue, i agree.

cheers,

Fathi


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410740: marked as done (x11-common: please conflict with opera (<< 9.10-20061214.6))

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 10:32:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410740: fixed in xorg 1:7.1.0-12
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: x11-common
Version: 1:7.1.0-11
Severity: serious

Please add opera (<< 9.10-20061214.6) to the list of packages conflicted
with by x11-common for the /usr/X11R6/bin transition.  It's been brought to
my attention on IRC that this version of the third-party opera package fixes
the binary path.

Obviously opera itself is not a Debian package, but I'm marking this as
'serious' because this is the single greatest remaining source of complaints
about our X upgrade, and I think we should fix this for the benefit of our
users given how nasty the failure mode is when the upgrade breaks in the
middle.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/

--- End Message ---
--- Begin Message ---
Source: xorg
Source-Version: 1:7.1.0-12

We believe that the bug you reported is fixed in the latest version of
xorg, which is due to be installed in the Debian FTP archive:

libglu1-xorg-dev_7.1.0-12_all.deb
  to pool/main/x/xorg/libglu1-xorg-dev_7.1.0-12_all.deb
libglu1-xorg_7.1.0-12_all.deb
  to pool/main/x/xorg/libglu1-xorg_7.1.0-12_all.deb
x-window-system-core_7.1.0-12_all.deb
  to pool/main/x/xorg/x-window-system-core_7.1.0-12_all.deb
x-window-system_7.1.0-12_all.deb
  to pool/main/x/xorg/x-window-system_7.1.0-12_all.deb
x11-common_7.1.0-12_i386.deb
  to pool/main/x/xorg/x11-common_7.1.0-12_i386.deb
xlibmesa-dri_7.1.0-12_all.deb
  to pool/main/x/xorg/xlibmesa-dri_7.1.0-12_all.deb
xlibmesa-gl-dev_7.1.0-12_all.deb
  to pool/main/x/xorg/xlibmesa-gl-dev_7.1.0-12_all.deb
xlibmesa-gl_7.1.0-12_all.deb
  to pool/main/x/xorg/xlibmesa-gl_7.1.0-12_all.deb
xlibmesa-glu_7.1.0-12_all.deb
  to pool/main/x/xorg/xlibmesa-glu_7.1.0-12_all.deb
xlibs-data_7.1.0-12_all.deb
  to pool/main/x/xorg/xlibs-data_7.1.0-12_all.deb
xlibs-static-dev_7.1.0-12_all.deb
  to pool/main/x/xorg/xlibs-static-dev_7.1.0-12_all.deb
xorg-dev_7.1.0-12_all.deb
  to pool/main/x/xorg/xorg-dev_7.1.0-12_all.deb
xorg_7.1.0-12.dsc
  to pool/main/x/xorg/xorg_7.1.0-12.dsc
xorg_7.1.0-12.tar.gz
  to pool/main/x/xorg/xorg_7.1.0-12.tar.gz
xorg_7.1.0-12_all.deb
  to pool/main/x/xorg/xorg_7.1.0-12_all.deb
xserver-xfree86_7.1.0-12_all.deb
  to pool/main/x/xorg/xserver-xfree86_7.1.0-12_all.deb
xserver-xorg-input-all_7.1.0-12_i386.deb
  to pool/main/x/xorg/xserver-xorg-input-all_7.1.0-12_i386.deb
xserver-xorg-video-all_7.1.0-12_i386.deb
  to pool/main/x/xorg/xserver-xorg-video-all_7.1.0-12_i386.deb
xserver-xorg_7.1.0-12_all.deb
  to pool/main/x/xorg/xserver-xorg_7.1.0-12_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Cristau <[EMAIL PROTECTED]> (supplier of updated xorg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 13 Feb 2007 11:12:46 +0100
Source: xorg
Binary: x-window-system xlibs-static-dev xlibmesa-dri xserver-xorg-video-all 
xserver-xorg xorg-dev xserver-xorg-input-all libglu1-xorg-dev xlibmesa-glu 
xlibmesa-gl x11-common xserver-xfree86 xlibmesa-gl-dev x-window-system-core 
libglu1-xorg xlibs-data xorg
Architecture: source all i386
Version: 1:7.1.0-12
Distribution: unstable
Urgency: high
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau <[EMAIL PROTECTED]>
Description: 
 libglu1-xorg - transitional package for Debian etch
 libglu1-xorg-dev - transitional package for Debian etch
 x-window-system - transitional package for Debian etch
 x-window-system-core - transitional package for Debian etch
 x11-common - X Window System (X.Org) infrastructure
 xlibmesa-dri - transitional package for Debian etch
 xlibmesa-gl - transitional package for Debian etch
 xlibmesa-gl-dev - transitional package for Debian etch
 xlibmesa-glu - transitional package for Debian etch
 xlibs-data - transitional package for X11 client data
 xlibs-static-de

Bug#370186: hal: HAL keeps CD drive spinning constantly

[Steve Langasek]

On Tue, Feb 13, 2007 at 11:20:06AM +0100, Juergen Lueters wrote:
> info.product = 'HL-DT-ST DVDRAM GSA-4080N'  (string)

Thanks, let's include this as another example in the fdi file.  Updated
patch attached, NMU replaced on gluck with this new version.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/
diff -u hal-0.5.8.1/debian/README.Debian hal-0.5.8.1/debian/README.Debian
--- hal-0.5.8.1/debian/README.Debian
+++ hal-0.5.8.1/debian/README.Debian
@@ -13 +13,13 @@
- -- Sjoerd Simons <[EMAIL PROTECTED]>
+
+ Some CD and DVD drives, such as the GDR8162B model found in some Dell 
+ laptops, do not correctly handle media status inquiries and incorrectly
+ spin up the drive when they should not.  Since hal regularly polls CD
+ drives for media changes, this results in increased power consumption and
+ mechanical wear and tear on such drives, which remain spinning constantly
+ while hal is running.
+
+ If you have a CD/DVD drive exhibiting this problem, you can copy
+ /usr/share/doc/hal/examples/no-cd-media-check.fdi to /etc/hal/fdi/policy/ to
+ disable media checks for your drive.  This file disables media checks for
+ all CD drives on the system, and also includes an example config for
+ disabling media checks only on a specific drive.
diff -u hal-0.5.8.1/debian/changelog hal-0.5.8.1/debian/changelog
--- hal-0.5.8.1/debian/changelog
+++ hal-0.5.8.1/debian/changelog
@@ -1,3 +1,13 @@
+hal (0.5.8.1-6.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * High-urgency upload for RC bugfix.
+  * Provide /usr/share/doc/hal/examples/no-cd-media-check.fdi as an example
+for disabling CD ROM media checks, and document this in README.Debian, as
+a workaround for CD drives with broken firmware.  Closes: #370186.
+
+ -- Steve Langasek <[EMAIL PROTECTED]>  Mon, 12 Feb 2007 16:42:29 -0800
+
 hal (0.5.8.1-6) unstable; urgency=low
 
   * debian/patches/19_sonypi_support.patch
only in patch2:
unchanged:
--- hal-0.5.8.1.orig/debian/hal.examples
+++ hal-0.5.8.1/debian/hal.examples
@@ -0,0 +1 @@
+debian/no-cd-media-check.fdi
only in patch2:
unchanged:
--- hal-0.5.8.1.orig/debian/no-cd-media-check.fdi
+++ hal-0.5.8.1/debian/no-cd-media-check.fdi
@@ -0,0 +1,36 @@
+ 
+
+
+
+
+
+  
+
+  
+
+  
+
+
+  
+
+  
+
+  
+  
+
+  
+
+  
+
+
+

Bug#410703: SIGINT corrupts storage file

[martin f krafft]

also sprach Steve Langasek <[EMAIL PROTECTED]> [2007.02.13.0204 +]:
> Could you clarify how this is "data loss"?  Does the
> reinitialization step do anything except for populating a new
> cache of the remote state?

Yes, it resets the local cache to zero, meaning that all remote
files will be overwritten. The only other alternative is to set the
cache to "full" meaning that only changes from now on will be
overwritten, or to initialise the cache from the remote, losing all
local changes.

But my mind's not set on grave. I'd be happy if you thought this was
important only.

-- 
 .''`.   martin f. krafft <[EMAIL PROTECTED]>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems


signature.asc
Description: Digital signature (GPG/PGP)

Bug#410727: kaffeine crashes attempting to play videos

[Fathi Boudra]

hi,

could you add some debugging package to produce a better backtrace:
* kaffeine-dbg
* kdelibs-dbg
* libxine1-dbg
* qt-x11-free-dbg

What video type you try to play ? i tried avi files without any crash.

cheers,

Fathi


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410405: knutclient: FTBFS on 64 bit arches: ambiguous operator

[Arnaud Quette]

Hi Dan,

can you have a look at this bug (failed to build):
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410405

thanks,
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#370186: hal: HAL keeps CD drive spinning constantly

[Juergen Lueters]

info.product = 'HL-DT-ST DVDRAM GSA-4080N'  (string)

Regards

Jürgen

-- 

Bug#410403: Here's a patch.

[Brandon Barnes]

tags 410403 +patch

First, I should warn you that I'm only a somewhat experienced
programmer. I pecked at the code a little bit, and it seems that the
code in question is never actually used. The integer that is being
assigned to is only mentioned twice in the whole code, once to declare,
and once to assign. Never to use.

So, here's a patch to remove the offending code:

--
diff gpsmap-old.cc gpsmap.cc
2245d2244
< int thread_status;
2249d2247
<   thread_status = reinterpret_cast(tmp);
--

Alternatively, if this code actually is used, such as in a future
version, you can change the "int" to a "long". As I understand
"reinterpret_cast", you can change from a pointer to a integral type, as
long as the integral type is large enough to hold the pointer. "long"
would work fine on both 32-bit and 64-bit platforms.

-Brandon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410288: marked as done (courier-mta: lockmail.1.gz and preline.1.gz alternatives not removed on package removal)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2007 10:02:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410288: fixed in courier 0.53.3-5
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: courier-mta
Version: 0.47-4sarge5
Severity: serious
Tags: patch
Justification: Appendix F

The prerm script of courier-mta does not remove two manpage
alternatives.  The following patch corrects the problem:

--- courier-mta.prerm.orig  2007-02-09 10:24:09.896439231 +
+++ courier-mta.prerm   2007-02-09 10:27:47.419548587 +
@@ -20,6 +20,8 @@
 if [ "$1" = "upgrade" -o "$1" = "remove" ]; then
for binary in lockmail preline; do
update-alternatives --remove $binary /usr/bin/$binary
+   update-alternatives --remove $binary.1 \
+   /usr/share/man/man1/$binary.courier.1.gz
done
 fi
 

Regards,

Tim Cutts

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages courier-mta depends on:
ii  courier-authdaemon0.47-4sarge5   Courier Mail Server - Authenticati
ii  courier-base  0.47-4sarge5   Courier Mail Server - Base system
ii  libc6 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an
ii  libgcc1   1:3.4.3-13sarge1   GCC support library
ii  libgdbm3  1.8.3-2GNU dbm database routines (runtime
ii  libperl5.85.8.4-8sarge5  Shared Perl library
ii  libstdc++51:3.3.5-13 The GNU Standard C++ Library v3

-- debconf information:
  courier-mta/dsnfrom: [EMAIL PROTECTED]
  courier-mta/defaultdomain: deskpro16107.dynamic.sanger.ac.uk

--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 0.53.3-5

We believe that the bug you reported is fixed in the latest version of
courier, which is due to be installed in the Debian FTP archive:

courier-base_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-base_0.53.3-5_i386.deb
courier-doc_0.53.3-5_all.deb
  to pool/main/c/courier/courier-doc_0.53.3-5_all.deb
courier-faxmail_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-faxmail_0.53.3-5_i386.deb
courier-imap-ssl_4.1.1.20060828-5_i386.deb
  to pool/main/c/courier/courier-imap-ssl_4.1.1.20060828-5_i386.deb
courier-imap_4.1.1.20060828-5_i386.deb
  to pool/main/c/courier/courier-imap_4.1.1.20060828-5_i386.deb
courier-ldap_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-ldap_0.53.3-5_i386.deb
courier-maildrop_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-maildrop_0.53.3-5_i386.deb
courier-mlm_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-mlm_0.53.3-5_i386.deb
courier-mta-ssl_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-mta-ssl_0.53.3-5_i386.deb
courier-mta_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-mta_0.53.3-5_i386.deb
courier-pcp_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-pcp_0.53.3-5_i386.deb
courier-pop-ssl_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-pop-ssl_0.53.3-5_i386.deb
courier-pop_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-pop_0.53.3-5_i386.deb
courier-ssl_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-ssl_0.53.3-5_i386.deb
courier-webadmin_0.53.3-5_i386.deb
  to pool/main/c/courier/courier-webadmin_0.53.3-5_i386.deb
courier_0.53.3-5.diff.gz
  to pool/main/c/courier/courier_0.53.3-5.diff.gz
courier_0.53.3-5.dsc
  to pool/main/c/courier/courier_0.53.3-5.dsc
sqwebmail_0.53.3-5_i386.deb
  to pool/main/c/courier/sqwebmail_0.53.3-5_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefan Hornburg (Racke) <[EMAIL PROTECTED]> (supplier of updated courier 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 13 Feb 2007 08:18:47 +0100
Source: courier
Binary: courier-mlm courier-ldap courier-faxmail courier-pcp courier-maildrop 
courier-imap courier-mta-ssl courier-pop-ssl courier-base sqwebmail courier-ssl 
courier-pop courier-mta courier-webadmin courier-imap-ssl courier-doc
Architecture: source i386 all
Version: 0.53.3-5

Bug#408948: Status update

[Loïc Minier]

Hi,

 Log of an IRC conversation on the status of this bug is attached.  In
 short, it might be easier to workaround this problem at the nautilus
 level, it's way riskier at the gnome-vfs2 level.

 Tentative patch for nautilus which didn't work is attached.

Bye,
-- 
Loïc Minier <[EMAIL PROTECTED]>
10:16 < HE> lool: Hmmm, I don't see a discussion about #408948. Is soemone 
working on that bug?
10:31 < lool> HE: I tried to, but the gnome-vfs2 side of things seem very risky 
to change, so I thought I would patch nautilus as a started; I wrote a 
preliminary patch which didn't work, but this made we wonder about a huge 
problem of the suggested fix: it might break all files without extensions or 
which have currently working non-recognized extensions
10:32 < lool> HE: In short, the proposed approach is to check that the data 
maps to a mime type which is the same than the MIME type of the file extensions
10:32 < lool> HE: But you *must* fail when the extension has no corresponding 
mime type (such as ".jpg ")
10:33 < lool> HE: But that would break for files named without extension 
("foo") or files named with weird extensions which seem logical for the user 
(foo.text, foo.dissertation, foo.notes, foo.readme, foo.clob)
10:33 < lool> HE: So, when I realized I might be breaking opening of a lot of 
files, I gave up to think about it a little
10:34 < lool> That, and my tentative patch didn't work :)
10:34 < lool> HE: Both security issues can be handled in the same area of 
nautilus, and I think this would lower the gnome-vfs side of things
10:35 < lool> HE: Oh, did I mention upstream isn't maintaining gnome-vfs2 
anymore?
10:35 < HE> lool: It isn't?
10:35 < HE> lool: I seem to be a bit out of the loop wrt Gnome stuff.
10:35 < HE> lool: Has it shown to be too useful?
10:36 < lool> HE: There was a massive debunk of the POSIX semantics mapping by 
Alex and he's been working hard on a glib level replacement
10:37 < lool> But obviously, gnome-vfs2 is going to stay for a little while 
before apps are rewritten; and upstream is probably still taking patches
10:37 < HE> lool: Well, gnome-vfs being gnome-something was always a weirdo 
idea, but changing that sounds like something you would do when moving to 
glib3...
10:37 < lool> I doubt they are intereted in adding disruptive security checks 
like #408948 proposes :-/
Index: debian/changelog
===
--- debian/changelog (révision 8527)
+++ debian/changelog (copie de travail)
@@ -1,8 +1,15 @@
-nautilus (2.14.3-8) UNRELEASED; urgency=low
+nautilus (2.14.3-8) unstable; urgency=medium
 
   * Add a get-orig-source target to retrieve the upstream tarball.
+  * SECURITY: New patch, 20_warn-unknown-file-extension, to warn when opening
+files for which we could compute a MIME type based on file magic, but
+where the file extension has no associated MIME type; this should best be
+done in gnome-vfs2, see #408948, GNOME #405052, and Novell #258503, but
+meanwhile this lowers the impact of the bug.  This would also need some
+specialized UI instead of the generic warning message, but we don't have
+infrastructure to translate UI additions at the Debian level for now.
 
- -- Loic Minier <[EMAIL PROTECTED]>  Sat, 13 Jan 2007 23:33:58 +0100
+ -- Loic Minier <[EMAIL PROTECTED]>  Wed,  7 Feb 2007 11:52:53 +0100
 
 nautilus (2.14.3-7) unstable; urgency=medium
 
Index: debian/patches/20_warn-unknown-file-extension.patch
===
--- debian/patches/20_warn-unknown-file-extension.patch (révision 0)
+++ debian/patches/20_warn-unknown-file-extension.patch (révision 0)
@@ -0,0 +1,17 @@
+diff -Nur nautilus-2.14.3/src/file-manager/fm-directory-view.c nautilus-2.14.3.new/src/file-manager/fm-directory-view.c
+--- nautilus-2.14.3/src/file-manager/fm-directory-view.c	2007-02-07 11:43:37.0 +0100
 nautilus-2.14.3.new/src/file-manager/fm-directory-view.c	2007-02-07 11:46:23.0 +0100
+@@ -5008,9 +5008,10 @@
+ 			(mime_type);
+ 		guessed_default_app = gnome_vfs_mime_get_default_application
+ 			(guessed_mime_type);
+-		if (default_app != NULL &&
+-		guessed_default_app != NULL &&
+-		!gnome_vfs_mime_application_equal (default_app, guessed_default_app)) {
++		if ((default_app != NULL && guessed_default_app == NULL) ||
++			(default_app != NULL &&
++			 guessed_default_app != NULL &&
++			 !gnome_vfs_mime_application_equal (default_app, guessed_default_app))) {
+ 			if (warn_on_mismatch) {
+ warn_mismatched_mime_types (view, file);
+ 			}

Bug#410754: Testing Works.

[Steve Langasek]

On Mon, Feb 12, 2007 at 11:34:49PM -0800, Brandon Barnes wrote:
> The version in testing (3.5.1-1) does not seem to have this bug. Neither
> does 3.6.0-1 (the one that is just about to get kicked out of
> unstable). Just thought I'd share that.

> Linking statically is one option. The other would be to stick with
> 3.6.* . Does 3.7 offer anything worth adding all of that space?

It's the only upstream fix offered for the grave security holes.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410288: courier-mta: lockmail.1.gz and preline.1.gz alternatives not removed on package removal

[Stefan Hornburg (Racke)]

Steve Langasek wrote:

On Mon, Feb 12, 2007 at 03:48:53PM +0100, Stefan Hornburg (Racke) wrote:

I confirm that installing and removing courier-mta leads to dangling
symlinks for the manpages.



However, I couldn't see any mistake in the update-alternatives directives
used in the maintainer scripts.


I did, at last.  It's subtle:

diff -u courier-0.53.3/debian/changelog courier-0.53.3/debian/changelog
--- courier-0.53.3/debian/changelog
+++ courier-0.53.3/debian/changelog
@@ -1,3 +1,12 @@
+courier (0.53.3-4.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * High-urgency upload for RC bugfix.
+  * Use the *alternative* name, not the *generic* name, when removing
+alternatives.  Closes: #410288.
+
+ -- Steve Langasek <[EMAIL PROTECTED]>  Mon, 12 Feb 2007 17:19:11 -0800
+
 courier (0.53.3-4) unstable; urgency=medium
 
   * updated Portuguese translation of Debconf templates (Closes: #409422,

diff -u courier-0.53.3/debian/courier-mta.prerm 
courier-0.53.3/debian/courier-mta.prerm
--- courier-0.53.3/debian/courier-mta.prerm
+++ courier-0.53.3/debian/courier-mta.prerm
@@ -19,7 +19,7 @@
 
 if [ "$1" = "upgrade" -o "$1" = "remove" ]; then

for binary in lockmail preline; do
-   update-alternatives --remove $binary /usr/bin/$binary
+   update-alternatives --remove $binary /usr/bin/${binary}.courier
done
 fi
 
I'm not sure why update-alternatives doesn't just error out when called with

a --remove argument that doesn't correctly correspond to any existing
alternatives, but nevertheless, this was a wrong invocation of u-a --remove.


Duh. I did this in other prerm scripts, but apparently missed that one.
After all, the manpage should document that in a much better way.
Anyway, thank you very much for solving this problem!



Stefan, please let me know if you need me to NMU for this, otherwise I'll
leave it in your hands.



I'll upload fixed packages today.

Bye
Racke

--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]