Bug#497056: lsb-base: /lib/lsb/init-functions NON-DSFG Licence ?

[Jari Aalto]

> William Pitcock:
> Every 3 clause BSD license has the same text (excluding the copyright
> notice). Every last one.

Then I have understood the word "notice" wrong to mean like
"announcement", not just "Copyright Line" as it appears.

I had a concern that has been cleared now, but I wish the discussion
would have been kept more professional.

Jari



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

Bug#490329: marked as done (setools: FTBFS: dpkg-gencontrol: failure: install new files list file: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 07:02:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#490329: fixed in setools 3.3.5.ds-1
has caused the Debian Bug report #490329,
regarding setools: FTBFS: dpkg-gencontrol: failure: install new files list 
file: No such file or directory
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
490329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490329
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: setools
Version: 3.3.4.ds-4
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080710 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on
i386.

Relevant part:
> dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
> dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
> dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
> dpkg-gencontrol: failure: install new files list file: No such file or 
> directory
> create_md5sums_fn () { cd $1 ; find . -type f ! -regex './DEBIAN/.*' ! -regex 
> './etc/.*'  -printf '%P\0' | xargs -r0 md5sum > DEBIAN/md5sums ; if [ -z 
> "DEBIAN/md5sums" ] ; then rm -f "DEBIAN/md5sums" ; fi ; } ; create_md5sums_fn 
>  
> /build/user-setools_3.3.4.ds-4-amd64-1H7k3k/setools-3.3.4.ds-4/debian/libseaudit-dev
> make[1]: *** [debian/stamp/binary/libsefs-dev] Error 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/07/10

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: setools
Source-Version: 3.3.5.ds-1

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

libapol-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libapol-dev_3.3.5.ds-1_amd64.deb
libapol4_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libapol4_3.3.5.ds-1_amd64.deb
libpoldiff-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libpoldiff-dev_3.3.5.ds-1_amd64.deb
libpoldiff1_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libpoldiff1_3.3.5.ds-1_amd64.deb
libqpol-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libqpol-dev_3.3.5.ds-1_amd64.deb
libqpol1_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libqpol1_3.3.5.ds-1_amd64.deb
libseaudit-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libseaudit-dev_3.3.5.ds-1_amd64.deb
libseaudit4_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libseaudit4_3.3.5.ds-1_amd64.deb
libsefs-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libsefs-dev_3.3.5.ds-1_amd64.deb
libsefs4_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libsefs4_3.3.5.ds-1_amd64.deb
libsetools-java_3.3.5.ds-1_all.deb
  to pool/main/s/setools/libsetools-java_3.3.5.ds-1_all.deb
libsetools-jni_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libsetools-jni_3.3.5.ds-1_amd64.deb
libsetools-tcl_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libsetools-tcl_3.3.5.ds-1_amd64.deb
python-setools_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/python-setools_3.3.5.ds-1_amd64.deb
setools_3.3.5.ds-1.diff.gz
  to pool/main/s/setools/setools_3.3.5.ds-1.diff.gz
setools_3.3.5.ds-1.dsc
  to pool/main/s/setools/setools_3.3.5.ds-1.dsc
setools_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/setools_3.3.5.ds-1_amd64.deb
setools_3.3.5.ds.orig.tar.gz
  to pool/main/s/setools/setools_3.3.5.ds.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.
Manoj Srivastava <[EMAIL PROTECTED]> (supplier of updated setools 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.8
Date: Sat, 30 Aug 2008 01:02:34 -0500
Source: setools
Binary: setools libsefs4 libsefs-dev libseaudit4 libseaud

Bug#421085: FTBFS: scanlogd.c:181: error: 'CLK_TCK' undeclared

[Solar Designer]

Debian fixed this bug incorrectly.  CLOCKS_PER_SEC is not a correct
substitute for CLK_TCK.  Please see:

http://www.openwall.com/lists/xvendor/2006/04/17/1

To make matters worse, the glibc documentation is buggy:

http://sources.redhat.com/bugzilla/show_bug.cgi?id=2636

For scanlogd, the correct fix is to update to 2.2.6 - which, by the way,
was already out by the time Debian wrongly "fixed" the bug.

I find it likely that many other Debian packages have introduced similar
bugs, though (blindly replacing CLK_TCK with CLOCKS_PER_SEC).

Alexander



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

Bug#492776: marked as done (FTBFS: version of libsepol is incompatible with SETools)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 07:02:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#492776: fixed in setools 3.3.5.ds-1
has caused the Debian Bug report #492776,
regarding FTBFS: version of libsepol is incompatible with SETools
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
492776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492776
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: setools
Version: 3.3.4.ds-4
Severity: serious

Hi,

the package FTBFS in a sid chroot:
checking correct libsepol expand behavior... configure: error: this version of 
libsepol is incompatible with SETools
make[1]: *** [debian/stamp/conf/setools] Error 1

Cheers,
Torsten


--- End Message ---
--- Begin Message ---
Source: setools
Source-Version: 3.3.5.ds-1

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

libapol-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libapol-dev_3.3.5.ds-1_amd64.deb
libapol4_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libapol4_3.3.5.ds-1_amd64.deb
libpoldiff-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libpoldiff-dev_3.3.5.ds-1_amd64.deb
libpoldiff1_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libpoldiff1_3.3.5.ds-1_amd64.deb
libqpol-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libqpol-dev_3.3.5.ds-1_amd64.deb
libqpol1_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libqpol1_3.3.5.ds-1_amd64.deb
libseaudit-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libseaudit-dev_3.3.5.ds-1_amd64.deb
libseaudit4_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libseaudit4_3.3.5.ds-1_amd64.deb
libsefs-dev_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libsefs-dev_3.3.5.ds-1_amd64.deb
libsefs4_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libsefs4_3.3.5.ds-1_amd64.deb
libsetools-java_3.3.5.ds-1_all.deb
  to pool/main/s/setools/libsetools-java_3.3.5.ds-1_all.deb
libsetools-jni_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libsetools-jni_3.3.5.ds-1_amd64.deb
libsetools-tcl_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/libsetools-tcl_3.3.5.ds-1_amd64.deb
python-setools_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/python-setools_3.3.5.ds-1_amd64.deb
setools_3.3.5.ds-1.diff.gz
  to pool/main/s/setools/setools_3.3.5.ds-1.diff.gz
setools_3.3.5.ds-1.dsc
  to pool/main/s/setools/setools_3.3.5.ds-1.dsc
setools_3.3.5.ds-1_amd64.deb
  to pool/main/s/setools/setools_3.3.5.ds-1_amd64.deb
setools_3.3.5.ds.orig.tar.gz
  to pool/main/s/setools/setools_3.3.5.ds.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.
Manoj Srivastava <[EMAIL PROTECTED]> (supplier of updated setools 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.8
Date: Sat, 30 Aug 2008 01:02:34 -0500
Source: setools
Binary: setools libsefs4 libsefs-dev libseaudit4 libseaudit-dev libapol4 
libapol-dev libpoldiff1 libpoldiff-dev libqpol1 libqpol-dev libsetools-jni 
libsetools-java libsetools-tcl python-setools
Architecture: source amd64 all
Version: 3.3.5.ds-1
Distribution: unstable
Urgency: high
Maintainer: Manoj Srivastava <[EMAIL PROTECTED]>
Changed-By: Manoj Srivastava <[EMAIL PROTECTED]>
Description: 
 libapol-dev - Security Enhanced Linux policy analysis development
 libapol4   - Security Enhanced Linux policy analysis library
 libpoldiff-dev - Security Enhanced Linux semantic policy differences 
development
 libpoldiff1 - Security Enhanced Linux semantic policy differences library
 libqpol-dev - Security Enhanced Linux policy abstraction development
 libqpol1   - Security Enhanced Linux policy abstraction library
 libseaudit-dev - Security Enhanced Linux audit message parser development
 libseaudit4 - Security Enhanced Linux audit message parsing library
 libsefs-dev - Security Enhanced Linux file context management development
 libsefs4   - Security Enhanced Linux file context management
 libsetools-java - SETools Java bindings (architecture-independent)
 libsetools-jni - SETools Java bindings (architecture-dependent)
 libsetools-tcl - SETools Tcl bindings
 python-setools - SETools Python bindings
 setools- tools for Security Enhanced Linux 

Bug#497145: rosegarden_1:1.7.1-1(sparc/unstable): FTBFS on sparc, cpp_type_traits.h:328: error: expected `{' before ';' token

[Martin Zobel-Helas]

Package: rosegarden
Version: 1:1.7.1-1
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of rosegarden_1:1.7.1-1 on lebrun by sbuild/sparc 98
> Build started at 20080830-0921

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>> 5.0.0), cmake, kdelibs4-dev, libasound2-dev (>= 
> 1.0.0), libjack-dev, ladspa-sdk, liblrdf0-dev, liblircclient-dev, dssi-dev 
> (>= 0.4), liblo0-dev (>= 0.7), libxft-dev, dpatch, fftw3-dev

[...]

>  from 
> /build/buildd/rosegarden-1.7.1/src/base/NotationTypes.h:20,
>  from 
> /build/buildd/rosegarden-1.7.1/src/gui/editors/notation/NotationChord.h:22,
>  from 
> /build/buildd/rosegarden-1.7.1/src/gui/editors/notation/NotationChord.cpp:19:
> /usr/include/c++/4.3/bits/cpp_type_traits.h:328: error: expected `{' before 
> ';' token
> /usr/include/c++/4.3/bits/stl_algobase.h: In function 'void 
> std::fill(_ForwardIterator, _ForwardIterator, const _Tp&) [with 
> _ForwardIterator = std::_Bit_type*, _Tp = int]':
> /usr/include/c++/4.3/bits/stl_bvector.h:368:   instantiated from here
> /usr/include/c++/4.3/bits/stl_algobase.h:731: error: no matching function for 
> call to '__fill_a(std::_Bit_type*, std::_Bit_type*, const int&)'
> make[3]: *** 
> [RGbuild/CMakeFiles/RosegardenExtended.dir/gui/editors/notation/NotationChord.o]
>  Error 1
> make[3]: Leaving directory `/build/buildd/rosegarden-1.7.1'
> make[2]: *** [RGbuild/CMakeFiles/RosegardenExtended.dir/all] Error 2
> make[2]: Leaving directory `/build/buildd/rosegarden-1.7.1'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/rosegarden-1.7.1'
> make: *** [build-stamp] Error 2
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2

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




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

Bug#493262: marked as done (ov511-source: Obsolete driver?)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:29:33 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ov511 has been removed from Debian, closing #493262
has caused the Debian Bug report #493262,
regarding ov511-source: Obsolete driver?
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
493262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493262
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: ov511-source
Version: Obsolete package?
Severity: serious

ov511 hasn't been uploaded since 2006-11-01 and there's a bug report that
it fails to compile with 2.6.19 and 2.6.22. (And very likely with current
kernels, but I haven't tried it myself)

I'm filing this bug since ov511 has been merged into the regular kernel
and is prevent in current kernel images:

[EMAIL PROTECTED]:~$ dpkg -L linux-image-2.6.26-1-686 | grep ov511
/lib/modules/2.6.26-1-686/kernel/drivers/media/video/ov511.ko

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/media/video/ov511.c;h=9edaca4371d7cedb5903d324e531eb4f16469a38;hb=HEAD

Unless I'm missing something ov511 should be removed from Lenny
and the archive.

Cheers,
Moritz

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash


--- End Message ---
--- Begin Message ---
Version: 2.32-3+rm

The ov511 package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/496822 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

--- End Message ---

Bug#483411: marked as done (postgresql-tablelog: Fix dependencies for postgresql-8.3)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:35:02 +0100
with message-id <[EMAIL PROTECTED]>
and subject line postgresql-tablelog has been removed from Debian, closing 
#483411
has caused the Debian Bug report #483411,
regarding postgresql-tablelog: Fix dependencies for postgresql-8.3
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
483411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483411
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: postgresql-tablelog
Severity: serious
Version: 0.4.4-1

Hi!

postgresql-8.2 will go away in Lenny/unstable soon [1]. Please update
the dependencies of this package for postgresql-8.3.

Thanks,

Martin

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483405

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.4.4-1+rm

The postgresql-tablelog package has been removed from Debian testing, unstable 
and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/495642 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

--- End Message ---

Bug#433928: marked as done (postgresql-tablelog: missing provisions for PostgreSQL major version upgrades)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:35:10 +0100
with message-id <[EMAIL PROTECTED]>
and subject line postgresql-tablelog has been removed from Debian, closing 
#433928
has caused the Debian Bug report #433928,
regarding postgresql-tablelog: missing provisions for PostgreSQL major version 
upgrades
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
433928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433928
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: postgresql-tablelog
Version: 0.4.4-1
Severity: serious

In order to allow major version upgrades of PostgreSQL (and following
related conventions), this (binary) package should be named
postgresql-8.2-tablelog.  Also, your build dependencies must specify
the major version to build with unambiguously; you can't just list
a set of choices.

--- End Message ---
--- Begin Message ---
Version: 0.4.4-1+rm

The postgresql-tablelog package has been removed from Debian testing, unstable 
and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/495642 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

--- End Message ---

Bug#460363: marked as done (postgresql-tablelog: FTBFS: Makefile:7: /usr/lib/pgxs/src/makefiles/pgxs.mk: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:35:12 +0100
with message-id <[EMAIL PROTECTED]>
and subject line postgresql-tablelog has been removed from Debian, closing 
#460363
has caused the Debian Bug report #460363,
regarding postgresql-tablelog: FTBFS: Makefile:7: 
/usr/lib/pgxs/src/makefiles/pgxs.mk: No such file or directory
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
460363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460363
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: postgresql-tablelog
version: 0.4.4-1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080111 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

Relevant part:

 > dpkg-source: building postgresql-tablelog in postgresql-tablelog_0.4.4-1.dsc
 >  debian/rules build
 > dh_testdir
 > touch configure-stamp
 > dh_testdir
 > # Add here commands to compile the package.
 > /usr/bin/make USE_PGXS=1
 > make[1]: Entering directory `/build/user/postgresql-tablelog-0.4.4'
 > Makefile:7: /usr/lib/pgxs/src/makefiles/pgxs.mk: No such file or directory
 > make[1]: *** No rule to make target `/usr/lib/pgxs/src/makefiles/pgxs.mk'.  
 > Stop.
 > make[1]: Leaving directory `/build/user/postgresql-tablelog-0.4.4'
 > make: *** [build-stamp] Error 2
 > dpkg-buildpackage: failure: debian/rules build gave error exit status 2

The full build log is available from:
http://people.debian.org/~lucas/logs/2008/01/11

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Version: 0.4.4-1+rm

The postgresql-tablelog package has been removed from Debian testing, unstable 
and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/495642 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

--- End Message ---

Bug#494262: marked as done (postgresql-tablelog: should this package be removed?)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:35:19 +0100
with message-id <[EMAIL PROTECTED]>
and subject line postgresql-tablelog has been removed from Debian, closing 
#494262
has caused the Debian Bug report #494262,
regarding postgresql-tablelog: should this package be removed?
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
494262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494262
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: postgresql-tablelog
Version: 0.4.4-1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-removal

Dear Maintainer,

While reviewing some packages, your package came up as a possible
candidate for removal from Debian, because:

  * Long standing RC bugs with no activity
  * Never included in a stable release
  * Very small user base according to popcon data

If you think that it should be orphaned instead of being removed from
Debian, please reply to this bug and tell so.

If you disagree and want to continue to maintain this package, please
just close this bug and do an upload also fixing the other issues.

If you agree that it should be removed, send the following commands to 
[EMAIL PROTECTED] (replace nn with this bug's number):

severity nn normal
reassign nn ftp.debian.org
retitle nn RM:  -- RoM;  
thanks

For more information, see
http://wiki.debian.org/ftpmaster_Removals
http://ftp-master.debian.org/removals.txt

Thank you,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.4.4-1+rm

The postgresql-tablelog package has been removed from Debian testing, unstable 
and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/495642 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

--- End Message ---

Bug#479158: marked as done (perlftlib_1.2-16+b1(sparc/unstable): FTBFS on sparc, error: static declaration of 'XS_FreeType_TT_Get_Glyph_Pixmap' follows non-static declaration)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:49:46 +0100
with message-id <[EMAIL PROTECTED]>
and subject line perlftlib has been removed from Debian, closing #479158
has caused the Debian Bug report #479158,
regarding perlftlib_1.2-16+b1(sparc/unstable): FTBFS on sparc, error: static 
declaration of 'XS_FreeType_TT_Get_Glyph_Pixmap' follows non-static declaration
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
479158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479158
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: perlftlib
Version: 1.2-16+b1
Severity: serious
user [EMAIL PROTECTED]
usertag perl-5.10-ftbfs

There was an error while trying to autobuild your package:

> Automatic build of perlftlib_1.2-16+b1 on lebrun by sbuild/sparc 98
> Build started at 20080503-1113

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 5), libttf-dev, perl (>= 5.8)

[...]

cc -c  -I/usr/include/freetype -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -O2 -g   -DVERSION=\"1.2\" -DXS_VERSION=\"1.2\" -fPIC
+"-I/usr/lib/perl/5.10/CORE"   FreeType.c
FreeType.c: In function 'XS_FreeType_TT_Get_Glyph_Bitmap':
FreeType.c:1271: error: static declaration of 'XS_FreeType_TT_Get_Glyph_Pixmap' 
follows non-static declaration
FreeType.c:1270: error: previous declaration of 
'XS_FreeType_TT_Get_Glyph_Pixmap' was here
FreeType.c: In function 'XS_FreeType_TT_Get_Glyph_Pixmap':
FreeType.c:1317: error: static declaration of 'XS_FreeType_TT_New_Outline' 
follows non-static declaration
FreeType.c:1316: error: previous declaration of 'XS_FreeType_TT_New_Outline' 
was here
FreeType.c:1345: error: static declaration of 'XS_FreeType_TT_Done_Outline' 
follows non-static declaration
FreeType.c:1344: error: previous declaration of 'XS_FreeType_TT_Done_Outline' 
was here
FreeType.c:1368: error: static declaration of 'XS_FreeType_TT_Copy_Outline' 
follows non-static declaration
FreeType.c:1367: error: previous declaration of 'XS_FreeType_TT_Copy_Outline' 
was here
FreeType.c:1402: error: static declaration of 
'XS_FreeType_TT_Get_Outline_Bitmap' follows non-static declaration
FreeType.c:1401: error: previous declaration of 
'XS_FreeType_TT_Get_Outline_Bitmap' was here
FreeType.c: In function 'XS_FreeType_TT_Get_Outline_Bitmap':
FreeType.c:1454: error: static declaration of 
'XS_FreeType_TT_Get_Outline_Pixmap' follows non-static declaration
FreeType.c:1453: error: previous declaration of 
'XS_FreeType_TT_Get_Outline_Pixmap' was here
FreeType.c: In function 'XS_FreeType_TT_Get_Outline_Pixmap':
FreeType.c:1506: error: static declaration of 'XS_FreeType_TT_Get_Outline_BBox' 
follows non-static declaration
FreeType.c:1505: error: previous declaration of 
'XS_FreeType_TT_Get_Outline_BBox' was here
FreeType.c:1539: error: static declaration of 
'XS_FreeType_TT_Transform_Outline' follows non-static declaration
FreeType.c:1538: error: previous declaration of 
'XS_FreeType_TT_Transform_Outline' was here
FreeType.c:1580: error: static declaration of 
'XS_FreeType_TT_Translate_Outline' follows non-static declaration
FreeType.c:1579: error: previous declaration of 
'XS_FreeType_TT_Translate_Outline' was here
FreeType.c:1612: error: static declaration of 'XS_FreeType_TT_Transform_Vector' 
follows non-static declaration
FreeType.c:1611: error: previous declaration of 
'XS_FreeType_TT_Transform_Vector' was here
FreeType.c:1648: error: static declaration of 
'XS_FreeType_TT_Get_CharMap_Count' follows non-static declaration
FreeType.c:1647: error: previous declaration of 
'XS_FreeType_TT_Get_CharMap_Count' was here
FreeType.c:1682: error: static declaration of 'XS_FreeType_TT_Get_CharMap_ID' 
follows non-static declaration
FreeType.c:1681: error: previous declaration of 'XS_FreeType_TT_Get_CharMap_ID' 
was here
FreeType.c:1723: error: static declaration of 'XS_FreeType_TT_Get_CharMap' 
follows non-static declaration
FreeType.c:1722: error: previous declaration of 'XS_FreeType_TT_Get_CharMap' 
was here
FreeType.c:1762: error: static declaration of 'XS_FreeType_TT_Char_Index' 
follows non-static declaration
FreeType.c:1761: error: previous declaration of 'XS_FreeType_TT_Char_Index' was 
here
FreeType.c:1797: error: static declaration of 'XS_FreeType_TT_Get_Name_Count' 
follows non-static declaration
FreeType.c:1796: error: previous declaration of 'XS_FreeType_TT_Get_Name_Count' 
was here
FreeType.c:1831: error: static declaration of 'XS_FreeType_TT_Get_Name_ID' 
follows non-static declaration
FreeType.c:1830: error: previous declarat

Bug#466773: marked as done (perlftlib: FTBFS with Perl 5.10 (compile error))

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:49:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line perlftlib has been removed from Debian, closing #133170
has caused the Debian Bug report #133170,
regarding perlftlib: FTBFS with Perl 5.10 (compile error)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
133170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=133170
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: perlftlib
Version: 1.2-16
Severity: important
User: [EMAIL PROTECTED]
Usertags: perl-5.10-transition

This package fails to build with Perl 5.10 (currently in experimental).
>From the build log:

cc -c  -I/usr/include/freetype -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -O2   -DVERSION=\"1.2\" -DXS_VERSION=\"1.2\" -fPIC 
"-I/usr/lib/perl/5.10/CORE"   FreeType.c
FreeType.c: In function 'XS_FreeType_TT_Done_FreeType':
FreeType.c:437: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Raster_Gray_Palette':
FreeType.c:476: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Open_Face':
FreeType.c:521: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Open_Collection':
FreeType.c:561: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Face_Properties':
FreeType.c:599: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Flush_Face':
FreeType.c:637: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Close_Face':
FreeType.c:671: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_New_Instance':
FreeType.c:706: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_Resolutions':
FreeType.c:745: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_CharSize':
FreeType.c:780: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_CharSizes':
FreeType.c:816: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_PointSize':
FreeType.c:851: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_PixelSizes':
FreeType.c:888: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_Transform_Flags':
FreeType.c:924: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Instance_Metrics':
FreeType.c:959: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Done_Instance':
FreeType.c:1006: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_New_Glyph':
FreeType.c:1041: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Done_Glyph':
FreeType.c:1078: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Load_Glyph':
FreeType.c:1115: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c:1126: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Glyph_Outline':
FreeType.c:1161: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Glyph_Metrics':
FreeType.c:1199: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Glyph_Bitmap':
FreeType.c:1247: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c:1272: error: static declaration of 'XS_FreeType_TT_Get_Glyph_Pixmap' 
follows non-static decla

Bug#133170: marked as done (libft-perl: Port to libfreetype6, libttf2 is now "old")

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:49:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line perlftlib has been removed from Debian, closing #133170
has caused the Debian Bug report #133170,
regarding libft-perl: Port to libfreetype6, libttf2 is now "old"
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
133170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=133170
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libft-perl
Version: 1.2-11
Severity: wishlist

Oldlibs are ugly, bad, ugly!
Could this solve fttools crashes as a side effect?


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux jkohen 2.4.17 #1 sáb ene 5 06:36:54 ART 2002 i586
Locale: LANG=es_AR, LC_CTYPE=es_AR

Versions of packages libft-perl depends on:
ii  libc6  2.2.5-3   GNU C Library: Shared libraries an
ii  libttf21.4pre.20011029-1 FreeType 1, The FREE TrueType Font
hi  perl   5.6.1-5   Larry Wall's Practical Extraction 
hi  perl-base [perlapi-5.6 5.6.1-5   The Pathologically Eclectic Rubbis

-- 
Javier Kohen <[EMAIL PROTECTED]>
Jabber: blashyrkh [EMAIL PROTECTED]
ICQ: blashyrkh #2361802
http://www.jkohen.com.ar/


pgps7e8uMyxd8.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.2-16+rm

The perlftlib package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/279824 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

--- End Message ---

Bug#466773: marked as done (perlftlib: FTBFS with Perl 5.10 (compile error))

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:49:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line perlftlib has been removed from Debian, closing #466773
has caused the Debian Bug report #466773,
regarding perlftlib: FTBFS with Perl 5.10 (compile error)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
466773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466773
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: perlftlib
Version: 1.2-16
Severity: important
User: [EMAIL PROTECTED]
Usertags: perl-5.10-transition

This package fails to build with Perl 5.10 (currently in experimental).
>From the build log:

cc -c  -I/usr/include/freetype -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -O2   -DVERSION=\"1.2\" -DXS_VERSION=\"1.2\" -fPIC 
"-I/usr/lib/perl/5.10/CORE"   FreeType.c
FreeType.c: In function 'XS_FreeType_TT_Done_FreeType':
FreeType.c:437: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Raster_Gray_Palette':
FreeType.c:476: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Open_Face':
FreeType.c:521: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Open_Collection':
FreeType.c:561: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Face_Properties':
FreeType.c:599: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Flush_Face':
FreeType.c:637: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Close_Face':
FreeType.c:671: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_New_Instance':
FreeType.c:706: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_Resolutions':
FreeType.c:745: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_CharSize':
FreeType.c:780: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_CharSizes':
FreeType.c:816: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_PointSize':
FreeType.c:851: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_PixelSizes':
FreeType.c:888: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Set_Instance_Transform_Flags':
FreeType.c:924: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Instance_Metrics':
FreeType.c:959: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Done_Instance':
FreeType.c:1006: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_New_Glyph':
FreeType.c:1041: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Done_Glyph':
FreeType.c:1078: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Load_Glyph':
FreeType.c:1115: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c:1126: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Glyph_Outline':
FreeType.c:1161: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Glyph_Metrics':
FreeType.c:1199: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c: In function 'XS_FreeType_TT_Get_Glyph_Bitmap':
FreeType.c:1247: warning: passing argument 3 of 'Perl_sv_2pv_flags' from 
incompatible pointer type
FreeType.c:1272: error: static declaration of 'XS_FreeType_TT_Get_Glyph_Pixmap' 
follows non-static decla

Bug#133170: marked as done (libft-perl: Port to libfreetype6, libttf2 is now "old")

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 09:49:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line perlftlib has been removed from Debian, closing #466773
has caused the Debian Bug report #466773,
regarding libft-perl: Port to libfreetype6, libttf2 is now "old"
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
466773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466773
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libft-perl
Version: 1.2-11
Severity: wishlist

Oldlibs are ugly, bad, ugly!
Could this solve fttools crashes as a side effect?


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux jkohen 2.4.17 #1 sáb ene 5 06:36:54 ART 2002 i586
Locale: LANG=es_AR, LC_CTYPE=es_AR

Versions of packages libft-perl depends on:
ii  libc6  2.2.5-3   GNU C Library: Shared libraries an
ii  libttf21.4pre.20011029-1 FreeType 1, The FREE TrueType Font
hi  perl   5.6.1-5   Larry Wall's Practical Extraction 
hi  perl-base [perlapi-5.6 5.6.1-5   The Pathologically Eclectic Rubbis

-- 
Javier Kohen <[EMAIL PROTECTED]>
Jabber: blashyrkh [EMAIL PROTECTED]
ICQ: blashyrkh #2361802
http://www.jkohen.com.ar/


pgpkjCEGvrsiJ.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.2-16+rm

The perlftlib package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/279824 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

--- End Message ---

Bug#334028: Get the attention of your ladies

[vy]

Studies show that chicks like large packages http://www.tiermake.com/



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

Bug#493599: removing udns from lenny?

[Luk Claes]

Thadeu Lima de Souza Cascardo wrote:
> On Fri, Aug 29, 2008 at 08:46:00PM +0200, Thomas Viehmann wrote:
>> Hi,
>>
>> udns has the recent DNS problem in a pretty bad way (i.e. no random, not
>> even query IDs vs. not enough). And there is no indication that anyone
>> is working on getting it solved at the moment. (Last upstream release is
>> Jan 2007, the  upstream mailing list archives have 2007 no activity
>> since the announcement of that, too.)
>> As udns is not in wide use across our archive, with only two packages
>> using it, it might be good to not release it with lenny.
>> For the two packages:
>> - jabberd2 is not in testing,
>> - libapache2-mod-defensible can be compiled without udns.
>>
>> Even better would be fixing, but I think this might be involved (based
>> on the "our design doesn't allow for port randomization") ...
>> Opinions?
>>
>> Kind regards
>>
>> T.
>> -- 
>> Thomas Viehmann, http://thomas.viehmann.net/
>>
>>
> 
> Hello.
> 
> This bug is likely a WONTFIX for the reasons already pointed out,
...
> However, I think udns should still be left out of stable, since the
> upstream author has requested this from me in the last release, because
> he believes the software is still experimental (mainly the library
> API/ABI).

removal hint added

Cheers

Luk



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

Bug#497019: nvidia-kernel-legacy-96xx-2.6.26-1-686: should provide nvidia-kernel-legacy-96xx-96.43.07 so that nvidia-glx-legacy-96xx would be installable

[Nyizsnyik Ferenc]

Just for information:

nvidia-kernel-legacy-96xx-2.6.26-1-686 still provides
nvidia-kernel-legacy-96xx-1.0.9639, which should have been changed to
nvidia-kernel-legacy-96xx-96.43.07.

-- 
Nyizsa.
http://nyizsa.uni.cc




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

Bug#494031: Non-deterministic build failures

[Ondrej Certik]

Hi Jurij!

On Sat, Aug 30, 2008 at 8:17 AM, Jurij Smakov <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've now tried to build paraview 5 times with the proposed patch on
> sparc. 2 times package build succeeded, 3 other times it failed with
> different errors in different places. At this point I have no idea
> what makes the build non-deterministic. I don't think it's hardware
> issue, because I did not see any problems while building other
> packages.

First, thanks very much for figuring out the patch. I myself am
finishing my thesis now, so I cannot get to it in the next couple
days. Could anyone try it too please?

I hope it's a hardware failure. So maybe let's apply the patch, upload and see?

Ondrej



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

Processed: i'd also put my bets on hardware or kernel (settings)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 496967 important
Bug#496967: general: System completely blocks any input
Severity set to `important' from `grave'

> tags 496967 +unreproducible
Bug#496967: general: System completely blocks any input
There were no tags set.
Tags added: unreproducible

> tags 496967 +moreinfo
Bug#496967: general: System completely blocks any input
Tags were: unreproducible
Tags added: moreinfo

> 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#497042: [Pkg-mediawiki-devel] Bug#497042: mediawiki: populateCategory.php script fails with PostgreSQL

[Romain Beauxis]

severity 497042 important
thanks

Le Friday 29 August 2008 15:18:33 Jaume Sabater, vous avez écrit :
> Package: mediawiki
> Version: 1:1.13.0-1
> Severity: grave
> Justification: renders package unusable

Well, not really, mysql users and fresh postgresql users can still use the 
package..

> Using PostgreSQL 8.3.3 and Mediawiki 1.13. Upgraded from Mediawiki 1.12
> to 1.13. Had to execute the populateCategory.php script inside
> maintenance due to the changes made by upstream in the software, so that
> new category and categorylinks tables are populated.
>
> When doing so, it fails and leaves the pages plenty of corrupted
> information, displaying tons of links/pages that should not be there.
> Please note the segmentation fault at the end. The update.php executed
> before also ended in a segmentation fault error, but seemed to work
> fine.

Ok, this issue seems to come from a custom debian patch.

Could you try with the original file, attached with this mail ?


Romain


DatabasePostgres.php
Description: application/php

Processed: Re: [Pkg-mediawiki-devel] Bug#497042: mediawiki: populateCategory.php script fails with PostgreSQL

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 497042 important
Bug#497042: mediawiki: populateCategory.php script fails with PostgreSQL
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#493599: removing udns from lenny?

[Thomas Viehmann]

Package: libapache2-mod-defensible
Severity: serious
Version: 1.4-2

Hi Julien,

Debian tries to drop udns from lenny, your package is the only
dependency in testing. Could you rebuild without udns, please?
If you are busy, don't hesitate to reply if you prefer to have the
upload done for you.

Kind regards

T.

Background:
[in udns bug #493599]:
> [udev-maintainer Thadeu Lima de Souza Cascardo]
>> However, I think udns should still be left out of stable, since the
>> upstream author has requested this from me in the last release, because
>> he believes the software is still experimental (mainly the library
>> API/ABI).
> 
> removal hint added
> 
> Cheers
> 
> Luk
-- 
Thomas Viehmann, http://thomas.viehmann.net/



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

Bug#497110: boot loader installation failed when dmraid=true

[Giuseppe Iuculano]

Frans Pop ha scritto:
> First thing that needs to be determined is what exactly has changed to add 
> this "p". Is it a change in dmraid, or in libparted, or elsewhere?
> When we know that we can check where changes are needed.
> Do you have any idea yourself where this "p" comes from?

I don't know where this "p" comes from, this is an ls -la after partitions (from
network shell installer)

# ls -la /dev/mapper
drwxr-xr-x2 root root  140 Aug 30 11:05 .
drwxr-xr-x   10 root root 2820 Aug 30 11:05 ..
crw-rw1 root root  10,  60 Aug 30 11:01 control
brw---1 root root 254,   0 Aug 30 11:06 sil_aiahbgbgaaaj
brw---1 root root 254,   1 Aug 30 11:10 sil_aiahbgbgaaajp1
brw---1 root root 254,   2 Aug 30 11:05 sil_aiahbgbgaaajp2
brw---1 root root 254,   3 Aug 30 11:05 sil_aiahbgbgaaajp5


But in the next reboot , from network shell installer:

~ # ls -la /dev/mapper
drwxr-xr-x2 root root  120 Aug 30 11:27 .
drwxr-xr-x9 root root 2900 Aug 30 11:27 ..
crw-rw1 root root  10,  60 Aug 30 11:27 control
brw---1 root root 254,   0 Aug 30 11:27 sil_aiahbgbgaaaj
brw---1 root root 254,   1 Aug 30 11:27 sil_aiahbgbgaaaj1
brw---1 root root 254,   2 Aug 30 11:27 sil_aiahbgbgaaaj5




Giuseppe Iuculano



signature.asc
Description: OpenPGP digital signature

Bug#495257: Possible upgrade solution

[Matthew Johnson]

I've just asked upstream to comment on this issue.

In the mean time, would this be a possible solution:

can the postinst of the new package force a restart of all the services
(possibly including gdm et al to restart user sessions) which depend on
the system bus?

It's a bit ugly, but a. if this is an etch->lenny upgrade they will
probably all be restarted anyway and b. it's still better than an actual
reboot.

We could have one of those debconf questions like libc6 has.

Matt

--
Matthew Johnson


signature.asc
Description: Digital signature

Bug#492235: havp: diff for NMU version 0.88-1.1 (updated)

[morph]

tags 487598 + patch
tags 492235 + patch
tags 492236 + patch
tags 496034 + patch
thanks

Hi,

Attached is the diff for my havp 0.88-1.1 NMU, updated to add the GPLv2+
boilerplate to debian/copyright
diff -u havp-0.88/debian/havp.init havp-0.88/debian/havp.init
--- havp-0.88/debian/havp.init
+++ havp-0.88/debian/havp.init
@@ -43,6 +43,9 @@
 		chown -R havp:havp $havp_mountpoint
 		echo "done"
 fi
+	echo -n "Cleaning up $havp_mountpoint"...
+	find $havp_mountpoint/ -type f -delete
+	echo " done"
 	echo -n "Starting $DESC: "
 	start-stop-daemon --start --quiet --pidfile $PIDFILE \
 		--exec $DAEMON -- $DAEMON_OPTS
@@ -56,6 +59,10 @@
 		echo "$NAME."
 	fi
 
+	echo -n "Cleaning up $havp_mountpoint"...
+	find $havp_mountpoint/ -type f -delete
+	echo " done"
+
 if [ x"$USE_LOOPBACK" = x"true" ] && [ "`mount | grep ^$havp_loopback`" ]; then
 		echo -n "Unmounting $havp_mountpoint ..."
 		umount $havp_mountpoint
diff -u havp-0.88/debian/havp.templates havp-0.88/debian/havp.templates
--- havp-0.88/debian/havp.templates
+++ havp-0.88/debian/havp.templates
@@ -72,6 +72,12 @@
  Чтобы использовать HAVP, вы можете смонтировать файловую систему, содержащую /var/spool/havp, с параметром "mand", или создать файловую систему loopback только для HAVP и смонтировать её в /var/spool/havp.
  .
  Если вы не знаете что делать, согласитесь на создание файловой системы loopback.
+Description-sv.UTF-8: Vill du skapa ett loopback-filsystem för spoolning?
+ HAVP kräver att filsystemet där temporära filer sparas vid scanning kan hantera låsningar. Många av de vanliga linux-filsystemen klarar detta men aktiverar det inte som standard.
+ .
+ För att använda HAVP så kan du antingen montera filsystemet som innehållet /var/spool/havp med inställningen "mand" eller skapa ett loopback-filsystem som monteras på /var/spool/havp och som endast kan användas av HAVP.
+ .
+ Om du är osäker så ska du välja det här alternativet och skapa ett loopback-filsystem.
 Description-ta.UTF-8: சுற்றி மீளும் உருளை கோப்பு அமைப்பு ஒன்று உருவாக்க வேண்டுமா?
  ஹெஏவிபி(HAVP) க்கு அதன் தற்காலிக கோப்புகளை வருடலின் போது சேமிக்கும் கோப்பு அமைப்பு கட்டாயமாக பூட்டும் ஆதரவு உள்ளதாக இருக்க வேண்டும். பல லீனக்ஸ் கோப்பு அமைப்புகள் இதை ஆதரித்தாலும் இதை முன்னிருப்பாக செயல் படுத்துவதில்லை.
  .
@@ -106,4 +112,6 @@
 Description-ru.UTF-8: Размер файловой системы Loopback:
  Введите размер (в мегабайтах) создаваемой файловой системы loopback.
+Description-sv.UTF-8: Storlek på loopback-filsystemet:
+ Ange storleken för loopback-filsystemet (i megabyte).
 Description-ta.UTF-8: சுற்றி மீளும் உருளை கோப்பு அமைப்பின் அளவு:
  சுற்றி மீளும் உருளை கோப்பு அமைப்பு உருவாக்க அதன் அளவை குறிப்பிடுக.
diff -u havp-0.88/debian/copyright havp-0.88/debian/copyright
--- havp-0.88/debian/copyright
+++ havp-0.88/debian/copyright
@@ -8,4 +8,26 @@
+Copyright:
+
+Copyright (C) 2005 by Christian Hilgers
+
 License:
 
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+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., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
+
 This software is licensed under the GNU GPL. On Debian GNU/Linux systems, you
 can find the license under /usr/share/common-licenses/GPL
+
+These files have different copyright notices:
+  havp/params.h:Copyright (C) 2005 by Peter Sebald / Christian Hilgers
+  havp/params.cpp:  Copyright (C) 2005 by Peter Sebald / Christian Hilgers
reverted:
--- havp-0.88/debian/havp.docs
+++ havp-0.88.orig/debian/havp.docs
@@ -1 +0,0 @@
-INSTALL
diff -u havp-0.88/debian/rules havp-0.88/debian/rules
--- havp-0.88/debian/rules
+++ havp-0.88/debian/rules
@@ -53,9 +53,12 @@
 	rm -f build-stamp config.status
 
 	# Add here commands to clean up after the build process.
-	-$(MAKE) clean
+	[ ! -f Makefile ] || $(MAKE) clean
 	rm -f config.sub config.guess config.status config.log
 
+	rm -f havp/Makefile Makefile havp/default.h etc/havp/havp.config \
+	  havp.1 havp/scanners/Makefile
+
 	# and make sure that templates are up-to-date
 	debconf-updatepo
 	po2debconf debian/havp.templates.master > debian/havp.templates
@@ -89,7 +92,7 @@
 	dh_installdocs
 	dh_installexamples
 	dh_installlogrotate
-	dh_installinit
+	dh_installinit --error-handler=init_error
 	dh_installman havp.1
 	dh_link
 	dh_strip
diff -u havp-0.88/debian/changelog havp-0.88/debian/changelog
--- havp-0.88/debian/changelog
+++ havp-0.88/debian/changelog
@@ -1,3 +1,30 @@
+havp (0.88-1.1) unstable; urgency=medium

Processed: havp: diff for NMU version 0.88-1.1 (updated)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 487598 + patch
Bug#487598: [INTL:sv] Swedish translation of debconf templates
Tags were: patch l10n
Tags added: patch

> tags 492235 + patch
Bug#492235: havp: does not delete temp files
Tags were: patch
Tags added: patch

> tags 492236 + patch
Bug#492236: havp: can't install if port 8080 in use
Tags were: patch
Tags added: patch

> tags 496034 + patch
Bug#496034: CVE-2008-3688: DoS by infinite loop
Tags were: patch security
Tags added: patch

> 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#495214: ipsec-tools in unstable fixes RC bug

[Thomas Viehmann]

Hi,

apparently, #495214: CVE-2008-3651: memory leak is fixed in unstable by
virtue of the new upstream release without the maintainer knowing /
noting it in the changelog.

The new upstream release has a largish diff to the version in testing,
does the release team want the version from unstable or a backported fix?

Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/



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

Bug#494031: Please try building paraview

[Jurij Smakov]

Hi,

I've proposed a patch [0] to fix an RC bug in paraview [1] (FTBFS on 
sparc). Unfortunately, after applying the patch, the package build 
fails in random places for me (not related to the initial problem) in 
roughly half of the build attempts (in the other half the package is 
built successfully). It might be some weird issue with the build 
system or toolchain, there is also a chance that my hardware is broken 
(even though until now I was not able to notice any problems while 
building other packages). If you have a chance and a reasonably fast 
sparc box (it takes about 6 hours to build on my SunBlade1000), please 
try building paraview from sid with the patch [0], preferrably a few 
times, and report if you encounter any failures.

[0] 
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=63;filename=paraview.patch;att=2;bug=494031
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494031

Thanks.
-- 
Jurij Smakov   [EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/  KeyID: C99E03CC



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

Bug#361925: Organic solutions to your size problems

[ray]

Guys with bigger packages get more luck http://www.tiercape.com/



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

Bug#497164: please drop udns (build-) dependency

[Thomas Viehmann]

Package: libapache2-mod-defensible
Severity: serious
Version: 1.4-2

Hi Julien,

Debian tries to drop udns from lenny, your package is the only
dependency in testing. Could you rebuild without udns, please?
If you are busy, don't hesitate to reply if you prefer to have the
upload done for you.

Kind regards

T.

Background:
[in udns bug #493599]:
> [udev-maintainer Thadeu Lima de Souza Cascardo]
>> However, I think udns should still be left out of stable, since the
>> upstream author has requested this from me in the last release, because
>> he believes the software is still experimental (mainly the library
>> API/ABI).
> 
> removal hint added
> 
> Cheers
> 
> Luk
-- 
Thomas Viehmann, http://thomas.viehmann.net/




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

Bug#493599: removing udns from lenny?

[Thomas Viehmann]

Luk Claes wrote:
>> This bug is likely a WONTFIX for the reasons already pointed out,
> ...
>> However, I think udns should still be left out of stable, since the
>> upstream author has requested this from me in the last release, because
>> he believes the software is still experimental (mainly the library
>> API/ABI).
> 
> removal hint added
I filed #497164 for libapache2-mod-defensible.

Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/



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

Bug#497168: grub-installer cant change grub settings

[Bolee Menee]

Package: grub-installer
Version: 1.32
Severity: grave

When I install Debian on computer with other operation system, and
want to setup grub not on main boot section but only on Linux
partition (hd0,4) to use bootmanager from other OS, If user mistakenly
choose wrong partition (in my case it was (hd0,3) ) he will get error
message, after it will be possible to go back to menu and try again
steps, But it will be not possible to install grub at all (on right
partition).

I suggest that grub-installer should detect possible Linux partitions
for installing and show them to user. Or at least show partition list
on page where user must enter partition number. And the best if it
will also allow to reset grub partition if its not possible to install
to what user enter.

I am using expert install from 28.08.2008
debian-testing-i386-netinst.iso in Graphic and Text modes, tried both
grub and grub2. System was successfully installed only after reboot
and new install with correct (hd0,4) settings. Ubuntu also have this
problem. I can try again to re-install system if it will be needed for
testing.



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

Bug#497110: boot loader installation failed when dmraid=true

[Frans Pop]

(No need to CC me on replies.)

On Saturday 30 August 2008, Giuseppe Iuculano wrote:
> Frans Pop ha scritto:
> > First thing that needs to be determined is what exactly has changed
> > to add this "p". Is it a change in dmraid, or in libparted, or
> > elsewhere? When we know that we can check where changes are needed.
> > Do you have any idea yourself where this "p" comes from?
>
> I don't know where this "p" comes from,

Well, I assume that the "p" stands for "partition". It is a somewhat 
common separator. The question is why it is showing up suddenly now and 
what is responsible for adding it.

> this is an ls -la after partitions (from network shell installer)
[...]
> But in the next reboot , from network shell installer:

What exactly do you mean by "network shell installer"? That is not really 
a meaningfull term for us. If this is some Debian Installer image, then 
please specify exactly what image you were using (full URL of the image 
you downloaded is good).

I guess the two boots were with the exact same version of the installer 
and the same boot options? If that is the case then something is really 
broken.

Exactly at what point of the installation did you do the 'ls -la'? Was 
this before or after partitioning? The best point to do it would be after 
hardware (disk) detection, but before partitioning.

Obviously we cannot really support something that is so unpredictable. 
From the info so far I would say that the problem is either in dmraid or 
maybe in the device-mapper (either user space or kernel).

I suggest that you try to determine what causes the difference by saving 
and carefully comparing the output of dmesg, various dmraid commands, 
maybe info available in /proc/, the output of fdisk -l for the underlying 
real devices, etc.

What is also suspicious is the missing partition 2, which I suspect is an 
extended partition.



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

Bug#492414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492414

[Nicolas Adenis-Lamarre]

for information,
on the svn version (future 0.5.0), the bug where fixed like that :

http://svn.tuxfamily.org/viewvc.cgi/trunk/src/states/StateMainMenu.cpp?root=xmoto_xmoto&view=diff&r1=2408&r2=2409

Nicolas

2008/8/25 Julien Cristau <[EMAIL PROTECTED]>

> On Mon, Aug 25, 2008 at 17:10:25 +0200, Julien Cristau wrote:
>
> > Looking at frame 3:
> > #3  0x080f83a5 in StateMainMenu::updateStats (this=0x8872d10)
> > at states/StateMainMenu.cpp:700
> > 700   v_totalPlayedTime = atoi(pDb->getResult(v_result, 8, 0, 2));
> >
> > (gdb) p pDb->getResult(v_result, 8, 0, 2)
> > $3 = 0x0
> >
> The attached patch was enough to make xmoto start without segfaulting
> here.
>
> Cheers,
> Julien
>

Processed: setting package to havp, tagging 496034, tagging 487598, tagging 492236, tagging 492235

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.35
> # via tagpending
> #
> # havp (0.88-1.1) unstable; urgency=medium
> #
> #  * debian/havp.init
> #- added cleanup for temporary files under /var/spool/havp; thanks to
> #  Alberto for the report; Closes: #492235
> #  * debian/{havp.prerm,havp.postinst,rules}
> #- modified to skip errors on service start/stop; thanks to Alberto for 
> the
> #  report; Closes: #492236
> #  * debian/patches/05_bts496034_CVE-2008-3688_fix_infinite_retry.dpatch
> #- added to fix CVE-2008-3688, DoS by connecting to a non-responsive 
> server,
> #  generating an infinite loop; thanks to Steffen Joeris for the report;
> #  Closes: #496034
> #  * debian/po/sv.po
> #- added Swedish translation of debconf templates; thanks to Martin Bagge;
> #  Closes: #487598
> #
> package havp
Ignoring bugs not assigned to: havp

> tags 496034 + pending
Bug#496034: CVE-2008-3688: DoS by infinite loop
Tags were: patch security
Tags added: pending

> tags 487598 + pending
Bug#487598: [INTL:sv] Swedish translation of debconf templates
Tags were: patch l10n
Tags added: pending

> tags 492236 + pending
Bug#492236: havp: can't install if port 8080 in use
Tags were: patch
Tags added: pending

> tags 492235 + pending
Bug#492235: havp: does not delete temp files
Tags were: patch
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#492235: setting package to havp, tagging 496034, tagging 487598, tagging 492236, tagging 492235

[Thomas Viehmann]

# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending 
#
# havp (0.88-1.1) unstable; urgency=medium
#
#  * debian/havp.init
#- added cleanup for temporary files under /var/spool/havp; thanks to
#  Alberto for the report; Closes: #492235
#  * debian/{havp.prerm,havp.postinst,rules}
#- modified to skip errors on service start/stop; thanks to Alberto for the
#  report; Closes: #492236
#  * debian/patches/05_bts496034_CVE-2008-3688_fix_infinite_retry.dpatch
#- added to fix CVE-2008-3688, DoS by connecting to a non-responsive server,
#  generating an infinite loop; thanks to Steffen Joeris for the report;
#  Closes: #496034
#  * debian/po/sv.po
#- added Swedish translation of debconf templates; thanks to Martin Bagge;
#  Closes: #487598
#

package havp
tags 496034 + pending
tags 487598 + pending
tags 492236 + pending
tags 492235 + pending




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

Bug#497130: Obsolete package: functionality has moved to perl-modules

[Niko Tyni]

On Fri, Aug 29, 2008 at 10:58:28PM -0500, Manoj Srivastava wrote:
> Package: libfile-temp-perl
> Version: 0.20-1
> Severity: serious

> As of perl 5.10, this functionality is now provided in
>  perl-modules, and thus this package is obsolete, and should be
>  removed from the release.  Since this package does not exist in
>  stable/oldstable, there will be no upgfrade issues.

I'm not the libfile-temp-perl maintainer, but please note:

- perl-modules has provided libfile-temp-perl since 5.6.1. See #98977.
- perl-modules currently only has File::Temp 0.18, so
  libfile-temp-perl provides a newer version (0.20)
- there are two packages with versioned dependencies (that aren't
  satisfied by a Provides field) on libfile-temp-perl:
  * Package: svk
Depends: [...], libfile-temp-perl (>> 0.17)
Build-Depends-Indep: [...], libfile-temp-perl (>> 0.17)
  * libpar-perl: bogus version 0.05 in the dependency, filed as #497170

While there's probably no need to have a newer File::Temp as a separate
package, both svk and libpar-perl need to be changed first and I don't
think this should be considered release critical.
-- 
Niko Tyni   [EMAIL PROTECTED]



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

Bug#497175: apticron: please check whether /var/lib/aptitude/pkgstates exists before grepping in it or redirect stderr to /dev/null

[Carsten Hey]

Package: apticron
Severity: grave
Version: 1.1.22
Tags: patch

The following line causes a mail to be send every night when
/var/lib/aptitude/pkgstates does not exist:

  APTITUDE_HOLDS=`grep "^State: 2" -B 2 /var/lib/aptitude/pkgstates |grep 
"^Package: .*$" |cut -d" " -f 2`

A possible fix is to change the line into:

  APTITUDE_HOLDS=`grep "^State: 2" -B 2 /var/lib/aptitude/pkgstates |grep 
"^Package: .*$" |cut -d" " -f 2` 2>/dev/null

According to the changelog this bug was introduced in version 1.1.22.


Regards,
Carsten



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

Bug#495257: [Pkg-utopia-maintainers] Bug#495257: dbus: System bus must not be restarted during package upgrades

[Sjoerd Simons]

retitle 495257 dbus should not use connection on restart
severity 495257 important
thanks,

On Fri, Aug 15, 2008 at 06:59:55PM +0100, Sam Morris wrote:
> Package: dbus
> Version: 1.2.1-3
> Severity: serious
> 
> Yesterday I upgraded my system and during the process the system dbus
> daemon was restarted. This caused a variety of interesting and amusing
> things to happen to my system, including gnome-power-manager dieing,
> network-manager dieing, the gnome panel dieing, and rhythmbox freezing
> up and chewing 100% of the CPU.
> 
> The bugs I filed upstream are:
> 
> http://bugzilla.gnome.org/show_bug.cgi?id=547932
> http://bugzilla.gnome.org/show_bug.cgi?id=547850
> http://bugzilla.gnome.org/show_bug.cgi?id=547851
> http://bugzilla.gnome.org/show_bug.cgi?id=547849
> 
> In the last of these, the NetworkManager developers were quite clear
> that distributions must *not* restart the dbus system bus, ever:
> 
> "Distros should not be restarting the bus on upgrade of the dbus package.  NM
> supports bus reconnections when it's been kicked off because of doing
> something bad, but does not support bus reconnections if dbus itself goes
> away."

> and
> 
> "the user wouldn't need to scratch his/her head if the distro did not restart
> the dbus service on a package upgrade.  the bus is _not_ meant to be
> restarted on-the-fly.  this is also the view of upstream dbus maintainers and
> has always been the view of upstream dbus maintainers.  there are way too
> many pieces here on the bus that NM talks to, and the code for doing state
> resynchronization after a bus restart would be hugely prohibitive when the
> bus should just not be restarted in the first place."
> 
> A dbus developer also cited a mailing list thread
> 
> where it was stated,
> 
> "I don't think we should really try to support this.  Restarting D-BUS
> should be viewed like trying to live-restart a new kernel.  There's so
> many complicated issues in it, and it'll be a rarely-tested code path.
> Right now it's a bug that the Fedora D-BUS and NetworkManager RPM
> scripts restart after a package upgrade."
> 
> Given the amount of crashes, freezes and general random weird behaviour
> that occurs when the system dbus daemon is restarted, it is clear that
> dbus clients simply can not handle the daemon being restarted. Since the
> upstreams of both dbus clients, and of dbus itself, say that this should
> not be done, and are not interested in accepting patches to make things
> work, we really shouldn't be doing it.

The only reason why D-Bus restarts in a stable debian version, is security
updates. Where it does not make sense to wait imho. Also for something like
network-manager, we restart that on dbus upgrade, so the user-experience should
just be a network reconnection (if he's on wireless), which is what it nicely
does on my system.

I do regard programs not coping gracefully with a dbus-daemon crash or restart
as being buggy and fixed several of them over the years. For most things it's
not that hard to fix.

If you want a real solution, then dbus should support restarting/reloading
itself in place like init does. If you want to claim that d-bus should be
treated like the kernel, please make it part of the kernel :)

Also like michiel said further on in the thread, upgrades from etch to lenny
will always restart dbus. So for etch->lenny we can't fix this anyway.
Hopefully for lenny+1 there will be a better solution.

  Sjoerd
-- 
Reality is just a crutch for people who can't handle science fiction.



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

Bug#496034: marked as done (CVE-2008-3688: DoS by infinite loop)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 13:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#496034: fixed in havp 0.88-1.1
has caused the Debian Bug report #496034,
regarding CVE-2008-3688: DoS by infinite loop
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
496034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496034
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: havp
Severity: grave
Tags: security, patch
Justification: user security hole

Hi,
the following CVE (Common Vulnerabilities & Exposures) id was
published for havp.

CVE-2008-3688[0]:
| sockethandler.cpp in HTTP Antivirus Proxy (HAVP) 0.88 allows remote
| attackers to cause a denial of service (hang) by connecting to a
| non-responsive server, which triggers an infinite loop due to an
| uninitialized variable.

You'll find a patch here[1].

If you fix the vulnerability please also make sure to include the
CVE id in your changelog entry.

Cheers
Steffen

For further information see:

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3688
http://security-tracker.debian.net/tracker/CVE-2008-3688
[1] http://bugs.endian.it/view.php?id=1129


--- End Message ---
--- Begin Message ---
Source: havp
Source-Version: 0.88-1.1

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

havp_0.88-1.1.diff.gz
  to pool/main/h/havp/havp_0.88-1.1.diff.gz
havp_0.88-1.1.dsc
  to pool/main/h/havp/havp_0.88-1.1.dsc
havp_0.88-1.1_amd64.deb
  to pool/main/h/havp/havp_0.88-1.1_amd64.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.
Sandro Tosi <[EMAIL PROTECTED]> (supplier of updated havp 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.8
Date: Sat, 30 Aug 2008 10:58:54 +0200
Source: havp
Binary: havp
Architecture: source amd64
Version: 0.88-1.1
Distribution: unstable
Urgency: medium
Maintainer: Rene Mayrhofer <[EMAIL PROTECTED]>
Changed-By: Sandro Tosi <[EMAIL PROTECTED]>
Description: 
 havp   - HTTP Anti Virus Proxy
Closes: 487598 492235 492236 496034
Changes: 
 havp (0.88-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/havp.init
 - added cleanup for temporary files under /var/spool/havp; thanks to
   Alberto for the report; Closes: #492235
   * debian/{havp.prerm,havp.postinst,rules}
 - modified to skip errors on service start/stop; thanks to Alberto for the
   report; Closes: #492236
   * debian/rules
 - added removal for generated files
 - clean run only if Makefile is present
   * debian/patches/05_bts496034_CVE-2008-3688_fix_infinite_retry.dpatch
 - added to fix CVE-2008-3688, DoS by connecting to a non-responsive server,
   generating an infinite loop; thanks to Steffen Joeris for the report;
   Closes: #496034
   * debian/po/sv.po
 - added Swedish translation of debconf templates; thanks to Martin Bagge;
   Closes: #487598
   * debian/copyright
 - added copyright notices
 - added GPLv2+ license boilerplate
   * debian/havp.docs
 - removed since it installed only INSTALL file
Checksums-Sha1: 
 eb2d05cfa6317cf95fd375a141d2e5b43df15e94 1016 havp_0.88-1.1.dsc
 3a01ab17299cd4accd00a9a9c6c05653dd101e92 22746 havp_0.88-1.1.diff.gz
 c725cb54a7afb17e6b4d163d5ab17e27811e3ad0 156118 havp_0.88-1.1_amd64.deb
Checksums-Sha256: 
 10c79914db6544d657391995b4bb987a592e5342e2dbd102286f46a71aeae509 1016 
havp_0.88-1.1.dsc
 959bd0751d7f3de436e0745fec1b3a40fbe53c60405f38cf352e56251df67493 22746 
havp_0.88-1.1.diff.gz
 fcf790c33780c98b401a7649f0578b485d522e8ca9d028660dc1e63238fa7184 156118 
havp_0.88-1.1_amd64.deb
Files: 
 df12836f586e29950a22b4da173f8b80 1016 net optional havp_0.88-1.1.dsc
 d3cff96d023303e45e89f341be67dc4b 22746 net optional havp_0.88-1.1.diff.gz
 d891f4f25a0c81969850b4506114f2cb 156118 net optional havp_0.88-1.1_amd64.deb

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

iEYEARECAAYFAki5QNcACgkQriZpaaIa1PnncwCfcWNNoEjHdtvYYSFDQwubJ4yU
hkMAnRmm9h8/BI3YU1iju7+ctNQriUYr
=6e0y
-END PGP SIGNATURE-


--- End Message ---

Bug#495351: Works fine for me

[Martin Guy]

I just tried this, on a Thecus N2100 (armv5te) running sid and with a
tripwire set on misaligned data accesses (echo 5 >
/proc/cpu/alignment). Although the installation was very noisy,
spewing warnings while recompiling common-lisp-controller three times,
it turned out ok:

n2100:/home/martin/arm# ecl
;;; Loading #P"/usr/lib/ecl/cmp.fas"
;;; Loading #P"/usr/lib/ecl/sysfun.lsp"
ECL (Embeddable Common-Lisp) 0.9j (CVS 2008-02-16 11:33)
Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya
Copyright (C) 1993 Giuseppe Attardi
Copyright (C) 2000 Juan J. Garcia-Ripoll
ECL is free software, and you are welcome to redistribute it
under certain conditions; see file 'Copyright' for details.
Type :h for Help.  Top level.
> (+ 1 2)
3
>

I gather it used to have problems with gcc-4.2. Have you apt-get
update/dist-upgraded lately?



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

Bug#492235: marked as done (havp: does not delete temp files)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 13:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#492235: fixed in havp 0.88-1.1
has caused the Debian Bug report #492235,
regarding havp: does not delete temp files
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
492235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492235
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---

Package: havp
Version: 0.88-1
Severity: grave

havp generates a lot of temp files on inside the
lookback-mounted /var/spool/havp directory. These
temporary files are not deleted even after rebooting,
so the 'disk' gets filled in a few months, which
results in a DoS.
I think the init script should do some kind of cleaning
to prevent this (assuming you restart havp on a regular
basis).




--- End Message ---
--- Begin Message ---
Source: havp
Source-Version: 0.88-1.1

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

havp_0.88-1.1.diff.gz
  to pool/main/h/havp/havp_0.88-1.1.diff.gz
havp_0.88-1.1.dsc
  to pool/main/h/havp/havp_0.88-1.1.dsc
havp_0.88-1.1_amd64.deb
  to pool/main/h/havp/havp_0.88-1.1_amd64.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.
Sandro Tosi <[EMAIL PROTECTED]> (supplier of updated havp 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.8
Date: Sat, 30 Aug 2008 10:58:54 +0200
Source: havp
Binary: havp
Architecture: source amd64
Version: 0.88-1.1
Distribution: unstable
Urgency: medium
Maintainer: Rene Mayrhofer <[EMAIL PROTECTED]>
Changed-By: Sandro Tosi <[EMAIL PROTECTED]>
Description: 
 havp   - HTTP Anti Virus Proxy
Closes: 487598 492235 492236 496034
Changes: 
 havp (0.88-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/havp.init
 - added cleanup for temporary files under /var/spool/havp; thanks to
   Alberto for the report; Closes: #492235
   * debian/{havp.prerm,havp.postinst,rules}
 - modified to skip errors on service start/stop; thanks to Alberto for the
   report; Closes: #492236
   * debian/rules
 - added removal for generated files
 - clean run only if Makefile is present
   * debian/patches/05_bts496034_CVE-2008-3688_fix_infinite_retry.dpatch
 - added to fix CVE-2008-3688, DoS by connecting to a non-responsive server,
   generating an infinite loop; thanks to Steffen Joeris for the report;
   Closes: #496034
   * debian/po/sv.po
 - added Swedish translation of debconf templates; thanks to Martin Bagge;
   Closes: #487598
   * debian/copyright
 - added copyright notices
 - added GPLv2+ license boilerplate
   * debian/havp.docs
 - removed since it installed only INSTALL file
Checksums-Sha1: 
 eb2d05cfa6317cf95fd375a141d2e5b43df15e94 1016 havp_0.88-1.1.dsc
 3a01ab17299cd4accd00a9a9c6c05653dd101e92 22746 havp_0.88-1.1.diff.gz
 c725cb54a7afb17e6b4d163d5ab17e27811e3ad0 156118 havp_0.88-1.1_amd64.deb
Checksums-Sha256: 
 10c79914db6544d657391995b4bb987a592e5342e2dbd102286f46a71aeae509 1016 
havp_0.88-1.1.dsc
 959bd0751d7f3de436e0745fec1b3a40fbe53c60405f38cf352e56251df67493 22746 
havp_0.88-1.1.diff.gz
 fcf790c33780c98b401a7649f0578b485d522e8ca9d028660dc1e63238fa7184 156118 
havp_0.88-1.1_amd64.deb
Files: 
 df12836f586e29950a22b4da173f8b80 1016 net optional havp_0.88-1.1.dsc
 d3cff96d023303e45e89f341be67dc4b 22746 net optional havp_0.88-1.1.diff.gz
 d891f4f25a0c81969850b4506114f2cb 156118 net optional havp_0.88-1.1_amd64.deb

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

iEYEARECAAYFAki5QNcACgkQriZpaaIa1PnncwCfcWNNoEjHdtvYYSFDQwubJ4yU
hkMAnRmm9h8/BI3YU1iju7+ctNQriUYr
=6e0y
-END PGP SIGNATURE-


--- End Message ---

Bug#496381: Patch to fix this issue

[Vincent Bernat]

OoO La  nuit ayant déjà  recouvert d'encre ce  jour du vendredi  29 août
2008, vers 23:50, David Symons <[EMAIL PROTECTED]> disait :

>> Here is a patch to fix this issue.

> Hi Vincent,

> Thanks for the patch.  I've incorporated it and uploaded here:

> - URL: http://mentors.debian.net/debian/pool/main/p/plait
> - Source repository: deb-src http://mentors.debian.net/debian unstable main 
> contrib non-free
> - dget http://mentors.debian.net/debian/pool/main/p/plait/plait_1.5.2-2.dsc

> Please tell me if I am breaching etiquette/protocol in any way.

If you want, you can set urgency=high since this fixes a security issue.
-- 
 /* After several hours of tedious analysis, the following hash
  * function won.  Do not mess with it... -DaveM
  */
2.2.16 /usr/src/linux/fs/buffer.c


pgpDPfq8J0WOB.pgp
Description: PGP signature

Processed (with 5 errors): Re: [Pkg-utopia-maintainers] Bug#495257: dbus: System bus must not be restarted during package upgrades

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 495257 dbus should not use connection on restart
Bug#495257: dbus: System bus must not be restarted during package upgrades
Changed Bug title to `dbus should not use connection on restart' from `dbus: 
System bus must not be restarted during package upgrades'.

> severity 495257 important
Bug#495257: dbus should not use connection on restart
Severity set to `important' from `serious'

> thanks,
Unknown command or malformed arguments to command.

> On Fri, Aug 15, 2008 at 06:59:55PM +0100, Sam Morris wrote:
Unknown command or malformed arguments to command.

> > Package: dbus
Unknown command or malformed arguments to command.

> > Version: 1.2.1-3
Unknown command or malformed arguments to command.

> > Severity: serious
Unknown command or malformed arguments to command.

Too many unknown commands, stopping 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#494140: marked as done (Upgrade to sshfs 2.1 bugfix release)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 13:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#494140: fixed in sshfs-fuse 2.1-1
has caused the Debian Bug report #494140,
regarding Upgrade to sshfs 2.1 bugfix release
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
494140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494140
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: sshfs
Version: 2.0-2
Severity: grave
Justification: causes non-serious data loss

There is a new 2.1 release, containing bugfixes. Among the fixes are:
*Fix bug in caching which could cause file corruption for append mode writes.
Så a data loss bug, hence the grave severity of the bug.

The new release also fixes the statvfs call, making for example df work.

Regards, Thue

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sshfs depends on:
ii  fuse-utils2.7.3-4Filesystem in USErspace (utilities
ii  libc6 2.7-10 GNU C Library: Shared libraries
ii  libfuse2  2.7.3-4Filesystem in USErspace library
ii  libglib2.0-0  2.16.4-2   The GLib library of C routines
ii  openssh-client1:4.7p1-12 secure shell client, an rlogin/rsh

sshfs recommends no packages.

sshfs suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: sshfs-fuse
Source-Version: 2.1-1

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

sshfs-fuse_2.1-1.diff.gz
  to pool/main/s/sshfs-fuse/sshfs-fuse_2.1-1.diff.gz
sshfs-fuse_2.1-1.dsc
  to pool/main/s/sshfs-fuse/sshfs-fuse_2.1-1.dsc
sshfs-fuse_2.1.orig.tar.gz
  to pool/main/s/sshfs-fuse/sshfs-fuse_2.1.orig.tar.gz
sshfs_2.1-1_i386.deb
  to pool/main/s/sshfs-fuse/sshfs_2.1-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.
Bartosz Fenski <[EMAIL PROTECTED]> (supplier of updated sshfs-fuse 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.8
Date: Sat, 30 Aug 2008 12:32:58 +0200
Source: sshfs-fuse
Binary: sshfs
Architecture: source i386
Version: 2.1-1
Distribution: unstable
Urgency: low
Maintainer: Bartosz Fenski <[EMAIL PROTECTED]>
Changed-By: Bartosz Fenski <[EMAIL PROTECTED]>
Description: 
 sshfs  - filesystem client based on SSH File Transfer Protocol
Closes: 494140
Changes: 
 sshfs-fuse (2.1-1) unstable; urgency=low
 .
   * New upstream release
 - Fix bug in caching which could cause file corruption for append mode
   writes; thanks to Thue Janus Kristensen for the report; (Closes: #494140)
   * debian/watch
 - added
   * thanks to Sandro Tosi for preparing that upload
Checksums-Sha1: 
 98ddbf0931b26be8376a2a4175382232280a137f 1058 sshfs-fuse_2.1-1.dsc
 c4e38fa8d4cec89af09cccae08a9f1bd96f452d4 115228 sshfs-fuse_2.1.orig.tar.gz
 871f0783cbbbe8573b684e1d95a17047bbab0697 26072 sshfs-fuse_2.1-1.diff.gz
 2f5fc7f9ff769180c20638601ca36780b5ac66c3 40310 sshfs_2.1-1_i386.deb
Checksums-Sha256: 
 5841ac4ca552ae152bab20357b25a60327b0ad0054a8ccdcf8a9296308b32ecc 1058 
sshfs-fuse_2.1-1.dsc
 1234fae4686f41b343e9785b4de16dae4049ab1b4d8ba28e8479eccc1bc2d233 115228 
sshfs-fuse_2.1.orig.tar.gz
 10d24b1972ee8381cbed8883f4df4dbd0bea6d4193310c97d44dd4b1b8b65593 26072 
sshfs-fuse_2.1-1.diff.gz
 b9aa95fdb4d253478a1f06334be21f8e6ad3b04be24e3f358837c50fc8947e5c 40310 
sshfs_2.1-1_i386.deb
Files: 
 8bb67bfa86572d687e74a5ed2ab8fadc 1058 utils optional sshfs-fuse_2.1-1.dsc
 997a419b6d0ad32a516823f8746b75c7 115228 utils optional 
sshfs-fuse_2.1.orig.tar.gz
 fd3ab5cd00fc8f0429d65ab95cbc028b 26072 utils optional sshfs-fuse_2.1-1.diff.gz
 8abfe139668c11cef4e02986f24e5c90 40310 utils optional sshfs_2.1-1_i386.deb

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

iEYEARECAAYFAki5QAsACgkQhQui3hP+/EA5JwCeL0DGCGFRwH7KSrxp5U2Ge1SF
2qUAn26orlCSHC/x

Bug#496381: Patch to fix this issue

[David Symons]

Hi Vincent,

On Sat, 2008-08-30 at 15:46 +0200, Vincent Bernat wrote:
> If you want, you can set urgency=high since this fixes a security issue.

Done - and reuploaded to mentors.d.n.

Cheers, David.
-- 
David Symons
Armidale NSW Australia
http://www.liberatedcomputing.net


signature.asc
Description: This is a digitally signed message part

Bug#491655: marked as done (audacious: log file spammed with tuple_get_int assertion failure message)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 14:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#491655: fixed in audacious 1.5.1-4
has caused the Debian Bug report #491655,
regarding audacious: log file spammed with tuple_get_int assertion failure 
message
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
491655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491655
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: audacious
Version: 1.5.1-1
Severity: critical
Justification: causes serious data loss

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The audacious log file in ~/.config/audacious/log is growing out of
control with the following error:

tuple_get_int: assertion `tuple != NULL' failed

I don't know if this would normally qualify as a critical bug, but
as it causes the logfile to grow extremely quicly it can fill up the
home partition very quickly, leading to loss of data.

Please let me know if I can provide any additional information.

- -- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages audacious depends on:
ii  audacious-plugins 1.5.1-2Base plugins for audacious
ii  dbus  1.2.1-2simple interprocess messaging syst
ii  gtk2-engines-pixbuf   2.12.11-2  Pixbuf-based theme for GTK+ 2.x
ii  libatk1.0-0   1.22.0-1   The ATK accessibility toolkit
ii  libaudclient1 1.5.1-2audacious dbus remote control libr
ii  libc6 2.7-12 GNU C Library: Shared libraries
ii  libcairo2 1.6.4-6The Cairo 2D vector graphics libra
ii  libdbus-1-3   1.2.1-2simple interprocess messaging syst
ii  libdbus-glib-1-2  0.76-1 simple interprocess messaging syst
ii  libglib2.0-0  2.16.4-2   The GLib library of C routines
ii  libgtk2.0-0   2.12.11-2  The GTK+ graphical user interface 
ii  libice6   2:1.0.4-1  X11 Inter-Client Exchange library
ii  libmcs1   0.7.1-1Abstraction library to store confi
ii  libmowgli10.6.1-1a high performance development fra
ii  libpango1.0-0 1.20.5-1   Layout and rendering of internatio
ii  libsamplerate00.1.4-1audio rate conversion library
ii  libsm62:1.0.3-2  X11 Session Management library
ii  libx11-6  2:1.1.4-2  X11 client-side library

Versions of packages audacious recommends:
ii  audacious-plugins-extra   1.5.1-2Various extra plugins for audaciou
ii  unzip 5.52-11De-archiver for .zip files

audacious suggests no packages.

- -- no debconf information

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

iEYEARECAAYFAkiEMFMACgkQBPYwh6bSSDeoMACfZRhb+QDZp1YFdA+L4qlzfWEi
zCwAoJl0CuwyDIonUQvbtUR88JOAKeIm
=V/tR
-END PGP SIGNATURE-


--- End Message ---
--- Begin Message ---
Source: audacious
Source-Version: 1.5.1-4

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

audacious-dbg_1.5.1-4_amd64.deb
  to pool/main/a/audacious/audacious-dbg_1.5.1-4_amd64.deb
audacious-dev_1.5.1-4_amd64.deb
  to pool/main/a/audacious/audacious-dev_1.5.1-4_amd64.deb
audacious_1.5.1-4.diff.gz
  to pool/main/a/audacious/audacious_1.5.1-4.diff.gz
audacious_1.5.1-4.dsc
  to pool/main/a/audacious/audacious_1.5.1-4.dsc
audacious_1.5.1-4_amd64.deb
  to pool/main/a/audacious/audacious_1.5.1-4_amd64.deb
libaudclient1_1.5.1-4_amd64.deb
  to pool/main/a/audacious/libaudclient1_1.5.1-4_amd64.deb
libaudid3tag1_1.5.1-4_amd64.deb
  to pool/main/a/audacious/libaudid3tag1_1.5.1-4_amd64.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.
William Pitcock <[EMAIL PROTECTED]> (supplier of updated audacious 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])


-

Bug#480801: remove gluezilla from testing?

[Thomas Viehmann]

Hi,

gluezilla has not been getting the attention necessary to fix #480801.
It has been obvious that this will be RC for 3.5 months and is RC for
2.5 months.
As gluezilla never was released with Debian and has no reverse
dependencies, it might be a good candidate to be removed from lenny.

Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/



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

Bug#481642: Appears to be caused by a circular dependency

[Steve Cotton]

There's a circular dependency between Qt.pm and Qt/debug.pm.
Combining that with this complex autoloader seems to be the source
of the problem.

Forcing the debug module to load before main module works:
  perl -MQt::debug ./aclock.pl
  perl -MQt::debug -MQt ./aclock.pl
the following fails:
  perl -MQt -MQt::debug ./aclock.pl

Breaking the circular dependency by removing either module's "use"
statement makes the module work.

  However, removing it from the debug.pm file means that
  attempting to turn debugging on with either of
perl -MQt::debug ./aclock.pl
perl -MQt::debug=verbose ./aclock.pl
  crashes.

  Removing it from the main Qt.pm sounds wrong but seems ok -
  Qt.pm checks the debugging module's variables, but uses fully
  qualified names to do it.  (patch attached)

I haven't understood how this packages's autoloading code does
what it's supposed to, but my cargo cult can get cargo to land.

Steve
Sat Aug 30 05:05:40 BST 2008  Steve Cotton <[EMAIL PROTECTED]>
  * 481642 - break circular dependency between Qt.pm and Qt/debug.pm
diff -rN -u old-libqt-perl-3.008/PerlQt/Qt.pm new-libqt-perl-3.008/PerlQt/Qt.pm
--- old-libqt-perl-3.008/PerlQt/Qt.pm	2008-08-30 15:47:44.0 +0100
+++ new-libqt-perl-3.008/PerlQt/Qt.pm	2008-08-30 15:47:44.0 +0100
@@ -398,7 +398,6 @@
 package Qt::_internal;
 
 use strict;
-use Qt::debug();
 
 our $Classes;
 our %CppName;

Bug#491984: [EMAIL PROTECTED]

[Raphael Champeimont (Almacha)]

Hi,

It seems to me that the Liberation Mono font (from package
ttf-liberation) has the same width as Luxi Mono, so it could be a better
replacement than DejaVu Mono. I have just used kfontview to see that, so
maybe I'm wrong.

Almacha



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

Bug#497164: marked as done (please drop udns (build-) dependency)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 14:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#497164: fixed in libapache2-mod-defensible 1.4-3
has caused the Debian Bug report #497164,
regarding please drop udns (build-) dependency
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
497164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497164
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libapache2-mod-defensible
Severity: serious
Version: 1.4-2

Hi Julien,

Debian tries to drop udns from lenny, your package is the only
dependency in testing. Could you rebuild without udns, please?
If you are busy, don't hesitate to reply if you prefer to have the
upload done for you.

Kind regards

T.

Background:
[in udns bug #493599]:
> [udev-maintainer Thadeu Lima de Souza Cascardo]
>> However, I think udns should still be left out of stable, since the
>> upstream author has requested this from me in the last release, because
>> he believes the software is still experimental (mainly the library
>> API/ABI).
> 
> removal hint added
> 
> Cheers
> 
> Luk
-- 
Thomas Viehmann, http://thomas.viehmann.net/



--- End Message ---
--- Begin Message ---
Source: libapache2-mod-defensible
Source-Version: 1.4-3

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

libapache2-mod-defensible_1.4-3.diff.gz
  to 
pool/main/liba/libapache2-mod-defensible/libapache2-mod-defensible_1.4-3.diff.gz
libapache2-mod-defensible_1.4-3.dsc
  to 
pool/main/liba/libapache2-mod-defensible/libapache2-mod-defensible_1.4-3.dsc
libapache2-mod-defensible_1.4-3_amd64.deb
  to 
pool/main/liba/libapache2-mod-defensible/libapache2-mod-defensible_1.4-3_amd64.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 Danjou <[EMAIL PROTECTED]> (supplier of updated 
libapache2-mod-defensible 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.8
Date: Sat, 30 Aug 2008 16:22:46 +0200
Source: libapache2-mod-defensible
Binary: libapache2-mod-defensible
Architecture: source amd64
Version: 1.4-3
Distribution: unstable
Urgency: low
Maintainer: Julien Danjou <[EMAIL PROTECTED]>
Changed-By: Julien Danjou <[EMAIL PROTECTED]>
Description: 
 libapache2-mod-defensible - module for Apache2 which provides DNSBL usage
Closes: 497164
Changes: 
 libapache2-mod-defensible (1.4-3) unstable; urgency=low
 .
   * Rebuild without udns support (Closes: #497164)
   * Bump standard version
   * Trust path set by dpkg in prerm
   * Fix copyright
Checksums-Sha1: 
 1930babb0ad21e0fadd51323a77f6fc34af66382 1108 
libapache2-mod-defensible_1.4-3.dsc
 957005b46292a8e3e8667b6fb75790d6ddd21374 2302 
libapache2-mod-defensible_1.4-3.diff.gz
 d95d5ffeada4fe379c8e29845dcdd0f653437e30 6842 
libapache2-mod-defensible_1.4-3_amd64.deb
Checksums-Sha256: 
 4f38eea3cc9e2f61b44a684a001d5badce1dcae1a877f551c3f1db6c9dc52107 1108 
libapache2-mod-defensible_1.4-3.dsc
 1b01e8cf1e51d55887031c5cb9b4b36a841264a5cb48ac56e3a61b3ea49d3ec3 2302 
libapache2-mod-defensible_1.4-3.diff.gz
 ace9bf5f07bd94384289a58c41e12879c7f2f32dafc0113aad2af38381cf9e5b 6842 
libapache2-mod-defensible_1.4-3_amd64.deb
Files: 
 dee225962a35f4905d3abf03af2dcdd0 1108 web extra 
libapache2-mod-defensible_1.4-3.dsc
 54ebf6679cf559f5a357b06fb6321bec 2302 web extra 
libapache2-mod-defensible_1.4-3.diff.gz
 24454738d38791ca560501650a69c6b2 6842 web extra 
libapache2-mod-defensible_1.4-3_amd64.deb

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

iEYEARECAAYFAki5WA0ACgkQpGK1HsL+5c2qhACcDJktr0+6FssBQOYPHpGATL9r
rLsAnRm7097E9z0j/0UvNVbNAc8WW7NC
=hBat
-END PGP SIGNATURE-


--- End Message ---

Bug#484535: remove piespy from lenny?

[Thomas Viehmann]

Hi,

piespy has an RC bug open (#484535) for one week less than three months.
It has seen no maintainer attention (only one hint by Michael Vogt that
it only runs properly with non-free software). Popcon installed is 15.

As it never has been released with Debian, it might be good to remove it
from lenny.

Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/



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

Processed (with 1 errors): does not affect Debian and as such is not RC

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 495116 important
Unknown tag/s: important.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny 
lenny-ignore.

Bug#495116: makejail must use ldconfig.real by default
There were no tags set.
Tags added: 

> 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#495116: does not affect Debian and as such is not RC

[Thomas Viehmann]

tag 495116 important
thanks

Hi,

I propose to lower the severity of this bug to important.
The bug only occurs on Debian, as such it does not matter for the Debian
release.

Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/



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

Bug#496381: Patch to fix this issue

[Vincent Bernat]

OoO Vers  la fin  de l'après-midi  du samedi 30  août 2008,  vers 16:12,
David Symons <[EMAIL PROTECTED]> disait :

>> If you want, you can set urgency=high since this fixes a security issue.

> Done - and reuploaded to mentors.d.n.

OK, uploaded.
-- 
panic("IRQ, you lose...");
2.2.16 /usr/src/linux/arch/mips/sgi/kernel/indy_int.c


pgp4Y7T8l7glu.pgp
Description: PGP signature

Processed: severity of 495116 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.35
> severity 495116 important
Bug#495116: makejail must use ldconfig.real by default
Severity set to `important' from `serious'

>
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#496381: marked as done (The possibility of attack with the help of symlinks in some Debian packages)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 15:47:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#496381: fixed in plait 1.5.2-2
has caused the Debian Bug report #496381,
regarding The possibility of attack with the help of symlinks in some Debian 
packages
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
496381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496381
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: plait
Severity: grave

Hi, maintainer!

This message about the error concerns a few packages  at  once.   I've
tested all the packages (for Lenny) on my Debian mirror.  All  scripts
of packages (marked as executable) were tested.

In some packages I've discovered scripts with errors which may be used
by a user for damaging important system files or user's files.

For example if a script uses in its work a temp file which is  created
in /tmp directory, then every user can create symlink  with  the  same
name in this directory in order to  destroy  or  rewrite  some  system
or user file.  Symlink attack may also  lead  not  only  to  the  data
desctruction but to denial of service as well.

Even if you create files or directories with help of function 'RANDOM'
or pid(), then your system is not protected. Attacker can create many
symlinks in order to destroy your data or create 'denial  of  service'
for your package scripts.

Even if you make rm(dir) for files/directories, then  your  system  is
not protected. Attacker can permanently create symlinks.

This list is created with the help of script.  This list is sorted  by
hand. Howewer in some cases mistake is possible.

Please, Be understanding to possible mistakes. :)

I set Severity into grave for this bug. The table of discovered
problems is below.

Discussion of this bug you can see in debian-devel@:
http://lists.debian.org/debian-devel/2008/08/msg00271.html

Binary-package: r-base-core-ra (1.1.1-1)
file: /usr/lib/Ra/lib/R/bin/javareconf
Binary-package: rccp (0.9-2)
file: /usr/lib/rccp/delqueueask
Binary-package: mafft (6.240-1)
file: /usr/bin/mafft-homologs
Binary-package: openoffice.org-common (1:2.4.1-6)
file: /usr/lib/openoffice/program/senddoc
Binary-package: crossfire-maps (1.11.0-1)
file: /usr/share/games/crossfire/maps/Info/combine.pl
Binary-package: sgml2x (1.0.0-11.1)
file: /usr/bin/rlatex
Binary-package: liguidsoap (0.3.6-4)
file: /var/lib/liguidsoap/liguidsoap.py
Binary-package: citadel-server (7.37-1)
file: /usr/lib/citadel-server/migrate_aliases.sh
Binary-package: ampache (3.4.1-1)
file: /usr/share/ampache/www/locale/base/gather-messages.sh
Binary-package: xen-utils-3.2-1 (3.2.1-2)
file: /usr/lib/xen-3.2-1/bin/qemu-dm.debug
Binary-package: dtc-common (0.29.6-1)
file: /usr/share/dtc/admin/accesslog.php
file: /usr/share/dtc/admin/sa-wrapper
Binary-package: honeyd-common (1.5c-3)
file: /usr/share/honeyd/scripts/test.sh
Binary-package: lustre-tests (1.6.5-1)
file: /usr/lib/lustre/tests/runiozone
Binary-package: linuxtrade (3.65-8+b4)
file: /usr/share/linuxtrade/bin/linuxtrade.bwkvol
file: /usr/share/linuxtrade/bin/linuxtrade.wn
file: /usr/share/linuxtrade/bin/moneyam.helper
Binary-package: freevo (1.8.1-0)
file: /usr/bin/freevo.real
Binary-package: fml (4.0.3.dfsg-2)
file: /usr/share/fml/libexec/mead.pl
Binary-package: rkhunter (1.3.2-3)
file: /usr/bin/rkhunter
Binary-package: openswan (1:2.4.12+dfsg-1.1)
file: /usr/lib/ipsec/livetest
Binary-package: linux-patch-openswan (1:2.4.12+dfsg-1.1)
file: /usr/src/kernel-patches/all/openswan/packaging/utils/maysnap
file: /usr/src/kernel-patches/all/openswan/packaging/utils/maytest
Binary-package: aptoncd (0.1-1.1)
file: /usr/share/aptoncd/xmlfile.py
Binary-package: cdcontrol (1.90-1.1)
file: /usr/lib/cdcontrol/writtercontrol
Binary-package: newsgate (1.6-23)
file: /usr/bin/mkmailpost
Binary-package: gpsdrive-scripts (2.10~pre4-3)
file: /usr/bin/geo-code
Binary-package: impose+ (0.2-11)
file: /usr/bin/impose
Binary-package: mgt (2.31-5)
file: /usr/games/mailgo
Binary-package: audiolink (0.05-1)
file: /usr/bin/audiolink
Binary-package: ibackup (2.27-4.1)
file: /usr/bin/ibackup
Binary-package: emacspeak (26.0-3)
file: /usr/share/emacs/site-lisp/emacspeak/etc/extract-table.pl
Binary-package: bk2site (1:1.1.9-3.1)
file: /usr/lib/cgi-bin/bk2site/redirect.pl
Binary-package: datafreedom-perl (0.1.7-1)
file: /usr/bin/dfxml-invoice
Binary-package: emacs-jabber (0.7.91-1)
file: /usr/lib/emacsen-common/packages/install/emacs-jabber

Processed: fixed 496124 in 1.3.33-3.1

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.35
> # This was fixed long ago. Why was it reported now?
> fixed 496124 1.3.33-3.1
Bug#496124: swig1.3: build-dependencies not satisfiable on amd64 sid+testing
Bug marked as fixed in version 1.3.33-3.1.

>
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#496124: fixed 496124 in 1.3.33-3.1

[Margarita Manterola]

# Automatically generated email from bts, devscripts version 2.10.35
# This was fixed long ago. Why was it reported now?
fixed 496124 1.3.33-3.1




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

Bug#497110: boot loader installation failed when dmraid=true

[Frans Pop]

On Saturday 30 August 2008, Giuseppe Iuculano wrote:
> after partitioning:
>
> ~ # ls -la /dev/mapper
> drwxr-xr-x2 root root  140 Aug 30 13:17 .
> drwxr-xr-x   10 root root 2820 Aug 30 13:17 ..
> crw-rw1 root root  10,  60 Aug 30 13:11 control
> brw---1 root root 254,   0 Aug 30 13:17 sil_aiahbgbgaaaj
> brw---1 root root 254,   1 Aug 30 13:17 sil_aiahbgbgaaajp1
> brw---1 root root 254,   2 Aug 30 13:17 sil_aiahbgbgaaajp2
> brw---1 root root 254,   3 Aug 30 13:17 sil_aiahbgbgaaajp5

OK, so it is the partitioning step that is causing the problem.

I suspect now that libparted is most likely to be the cause of the problem,
especially as after a reboot existing partitions are by dmraid detected
as you would expect (without the "p").
But another possibility is that you are just not following the correct
procedure. Support for dmraid is far from perfect and things will *only*
work if you follow the documented procedure.

How did you do the partitioning? Did you *exactly* follow the instructions
that are given in the "Partitioning" section of the SataRAID wiki page [1]?

Did the partman screens look like the examples that are given there?
Screenshots before and after doing the "Write changes in SATA RAID
partitioning to disk" step would be nice too.

Please send the /var/log/partman (gzipped!) after you do the partitioning.

> I selected the first ext3 entry, below serial ata raid (mirror), I had an
> out of memory:

The out of memory should not happen, but selecting the "first" partition
is *wrong*. It is not conform the procedure on the wiki page!

> Installation terminated, in the next reboot grub started, but there is
> an issue. Installer set root (sil_aiahbgbgaaaj).
>
> Replacing with root (hd0,0) fixes it.

We can look at this later. Let's concentrate first on the partitioning
problem.

Cheers,
FJP

[1] http://wiki.debian.org/DebianInstaller/SataRaid



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

Bug#492282: "seahorse-agent --execute" leaks file descriptors

[Josselin Mouette]

Le mercredi 27 août 2008 à 23:54 +0200, Thijs Kinkhorst a écrit :
> > I’ve patched seahorse in our svn to set FD_CLOEXEC on the agent socket.
> > Other open fds seem to be pipes opened by gpgme to talk to gpg that are
> > not closed after use. AIUI this is not a security issue.
> 
> This bug has been pending for a month now - is something blocking the fix?

No, it was just sitting on my hard disk /o\

-- 
 .''`.
: :' :  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#495351: Problem is specific to debian rootfs in maemo chroot and is not present in Debian proper

[Martin Guy]

I've tried this on armv5te and armv4t hardware under armel-sid under
gdb and not, and in all cases it works fine, so I suggets closing this bug.

For further details of the specific failing environment, see
http://sourceforge.net/mailarchive/[EMAIL PROTECTED]&forum_name=ecls-list

M



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

Bug#496124: marked as done (swig1.3: build-dependencies not satisfiable on amd64 sid+testing)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 14:34:22 -0300
with message-id <[EMAIL PROTECTED]>
and subject line This bug was fixed in April
has caused the Debian Bug report #496124,
regarding swig1.3: build-dependencies not satisfiable on amd64 sid+testing
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
496124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496124
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: swig1.3
Version: 1.3.33-3
Severity: serious

The build-dependencies of your package cannot be satisfied on amd64
even by taking sid and testing binary packages together :

swig1.3 (= 1.3.33-3): FAILED
binary: swig
The following constraints cannot be satisfied:
  swig1.3 (= 1.3.33-3) build-depends on python-dev (<< 2.5) {NOT AVAILABLE}

This means that even migration of any other packages to testing will not make
the package compilable inside testing.

-Ralf.
-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/bash


--- End Message ---
--- Begin Message ---
Version: 1.3.35-3.1

This bug was fixed with the upload done in April by Torsten Werner.  It
should be fixed in lenny when the ia64 auto-builder builds it, now that
guile-1.8-dev has been fixed.

[Sending this in a -done message and the correct version now]

-- 
 Bessos,(o_
Marga.  (\)_

--- End Message ---

Bug#480801: [pkg-mono-group] Bug#480801: remove gluezilla from testing?

[Mirco Bauer]

On Sat, 2008-08-30 at 16:43 +0200, Thomas Viehmann wrote:
> Hi,
> 
> gluezilla has not been getting the attention necessary to fix #480801.
> It has been obvious that this will be RC for 3.5 months and is RC for
> 2.5 months.
> As gluezilla never was released with Debian and has no reverse
> dependencies, it might be a good candidate to be removed from lenny.
> 
> Kind regards

I tried to port gluezilla to xulrunner 1.9 but I failed.
There is a package in mono (libmono-mozilla0.2-cil) that recommends
gluezilla. Nothing in debian would use that though, as it's the wrapper
library to implement the WebControl class part of the WinForms
implementation in Mono, e.g. it's only used by Windows applications that
target MS .NET.

So I have no objections to see gluezilla being removed from testing.

> 
> T.
-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer[EMAIL PROTECTED]  http://www.meebey.net/
PEAR Developer[EMAIL PROTECTED] http://pear.php.net/
Debian Developer  [EMAIL PROTECTED]  http://www.debian.org/


signature.asc
Description: This is a digitally signed message part

Bug#492282: marked as done ("seahorse-agent --execute" leaks file descriptors)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 17:32:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#492282: fixed in seahorse 2.22.3-2
has caused the Debian Bug report #492282,
regarding "seahorse-agent --execute" leaks file descriptors
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
492282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492282
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: seahorse
Version: 2.22.3-1
Severity: normal
Tags: security

Seahorse leaks file descriptors to processes started with "seahorse-agent
--execute", including the gpg agent listening socket. For the default setup,
this means that all processes started from the desktop inherit those FDs and can
possibly use them. This can be a security issue because the FDs are also
inherited to processes started with su as a different user which normally would
not have access to gpg key and gpg agent socket.

Seahorse should use fcntl to set FD_CLOEXEC on its FDs.


PS: LVM complains about the open FDs, too:

$ su
Password:
# lvs
File descriptor 8 left open
File descriptor 9 left open
File descriptor 13 left open
...


PPS: You can use filan from the socat package to display information about the
open FDs.


--- End Message ---
--- Begin Message ---
Source: seahorse
Source-Version: 2.22.3-2

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

seahorse_2.22.3-2.diff.gz
  to pool/main/s/seahorse/seahorse_2.22.3-2.diff.gz
seahorse_2.22.3-2.dsc
  to pool/main/s/seahorse/seahorse_2.22.3-2.dsc
seahorse_2.22.3-2_amd64.deb
  to pool/main/s/seahorse/seahorse_2.22.3-2_amd64.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.
Josselin Mouette <[EMAIL PROTECTED]> (supplier of updated seahorse 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.8
Date: Sat, 30 Aug 2008 18:56:42 +0200
Source: seahorse
Binary: seahorse
Architecture: source amd64
Version: 2.22.3-2
Distribution: unstable
Urgency: low
Maintainer: Jose Carlos Garcia Sogo <[EMAIL PROTECTED]>
Changed-By: Josselin Mouette <[EMAIL PROTECTED]>
Description: 
 seahorse   - GNOME front end for GnuPG
Closes: 492282
Changes: 
 seahorse (2.22.3-2) unstable; urgency=low
 .
   * 02_close_fds.patch: set close-on-exec flag on the agent socket's
 file descriptor to avoid leaking it to spawned processes.
 Closes: #492282.
Checksums-Sha1: 
 8a7092c4ec3d52484a7b30fed41ada1f4cec 1712 seahorse_2.22.3-2.dsc
 11ef7660b868ea571ae5c90f6f882c6a05f54385 36433 seahorse_2.22.3-2.diff.gz
 d539752fdca3705f5d58e0284b504f583f6a7c73 4431982 seahorse_2.22.3-2_amd64.deb
Checksums-Sha256: 
 019e5f13b7ebd527940e7ec644363550a141d9b2ae6459a6deffae02da474e01 1712 
seahorse_2.22.3-2.dsc
 63db251f7ec63884755de80bbafc2d337a585d6bcbcbf948407ae531aac92a84 36433 
seahorse_2.22.3-2.diff.gz
 1ed3b783d19d300312c163a0e1557d2ebd5153cd6e45a88981d512c8e3d6ebb9 4431982 
seahorse_2.22.3-2_amd64.deb
Files: 
 24b9393e10f9d97e8483c67310a176e8 1712 gnome optional seahorse_2.22.3-2.dsc
 643d26e2d7c99dd6ceebd1800097f858 36433 gnome optional seahorse_2.22.3-2.diff.gz
 f5df320b1fe30450e48e9b57a00bfe16 4431982 gnome optional 
seahorse_2.22.3-2_amd64.deb

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

iD8DBQFIuYDtrSla4ddfhTMRAoEsAJ0SAfxptCUDeCQsjz7HBpYZ02NW9QCeL16v
mLjc8m+u8x3k6edKDH31SyM=
=CQov
-END PGP SIGNATURE-


--- End Message ---

Bug#488467: Bug#397924: Subject: Re:libtrash: new upstream version 3.2 available

[Margarita Manterola]

On Wed, Jul 2, 2008 at 7:43 PM, José Luis Tallón
<[EMAIL PROTECTED]> wrote:
> I asked Mike Hommey <[EMAIL PROTECTED]>, who showed interest and submitted
> a patch to upload a new version.
> However, he refused to sponsor any upload, given that he has run out of
> time to devote to this issue by reviewing libtrash 2.4's code and
> creating the patch.
>
> Any takers (willing sponsors) appreciated.

It would be interesting to know where your version to-be-sponsored is.

However, please remember that we are in a freeze right now, and that
your package has an RC bug reported to it.

Thus, applying the patch provided by Mike and uploading a version that
is not a full re-write, but has this bug fixed is the current
priority.

-- 
Besos,
Marga



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

Bug#497019: marked as done (nvidia-kernel-legacy-96xx-2.6.26-1-686: should provide nvidia-kernel-legacy-96xx-96.43.07 so that nvidia-glx-legacy-96xx would be installable)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 18:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#497019: fixed in nvidia-graphics-legacy-96xx-modules-i386 
96.43.07+2
has caused the Debian Bug report #497019,
regarding nvidia-kernel-legacy-96xx-2.6.26-1-686: should provide 
nvidia-kernel-legacy-96xx-96.43.07 so that nvidia-glx-legacy-96xx would be 
installable
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
497019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497019
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: nvidia-kernel-legacy-96xx-2.6.26-1-686
Version: 96.43.07+1
Severity: grave
Justification: renders package unusable

Currently nvidia-kernel-legacy-96xx-2.6.26-1-686 is unusable because
nvidia-glx-legacy-96xx cannot be installed together with it.

Indeed, nvidia-glx-legacy-96xx depends on nvidia-kernel-legacy-96xx-96.43.07
which is not installable and is not provided in any way by
nvidia-kernel-legacy-96xx-2.6.26-1-686.

nvidia-kernel-legacy-96xx-2.6.26-1-686 should either
provide nvidia-kernel-legacy-96xx-96.43.07 (this solution does not look
ideal) or you must change the dependency of nvidia-glx-legacy-96xx
to something other, perhaps, by introducing a virtual package.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (900, 'testing'), (100, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nvidia-kernel-legacy-96xx-2.6.26-1-686 depends on:
ii  linux-image-2.6.26-1-686 2.6.26-3Linux 2.6.26 image on PPro/Celeron
ii  nvidia-kernel-common 20051028+1+nmu2 NVIDIA binary kernel module common

nvidia-kernel-legacy-96xx-2.6.26-1-686 recommends no packages.

nvidia-kernel-legacy-96xx-2.6.26-1-686 suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-legacy-96xx-modules-i386
Source-Version: 96.43.07+2

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-legacy-96xx-modules-i386, which is due to be installed in the 
Debian FTP archive:

nvidia-graphics-legacy-96xx-modules-i386_96.43.07+2.dsc
  to 
pool/non-free/n/nvidia-graphics-legacy-96xx-modules-i386/nvidia-graphics-legacy-96xx-modules-i386_96.43.07+2.dsc
nvidia-graphics-legacy-96xx-modules-i386_96.43.07+2.tar.gz
  to 
pool/non-free/n/nvidia-graphics-legacy-96xx-modules-i386/nvidia-graphics-legacy-96xx-modules-i386_96.43.07+2.tar.gz
nvidia-kernel-legacy-96xx-2.6-686-bigmem_96.43.07+2_i386.deb
  to 
pool/non-free/n/nvidia-graphics-legacy-96xx-modules-i386/nvidia-kernel-legacy-96xx-2.6-686-bigmem_96.43.07+2_i386.deb
nvidia-kernel-legacy-96xx-2.6-686_96.43.07+2_i386.deb
  to 
pool/non-free/n/nvidia-graphics-legacy-96xx-modules-i386/nvidia-kernel-legacy-96xx-2.6-686_96.43.07+2_i386.deb
nvidia-kernel-legacy-96xx-2.6-openvz-686_96.43.07+2_i386.deb
  to 
pool/non-free/n/nvidia-graphics-legacy-96xx-modules-i386/nvidia-kernel-legacy-96xx-2.6-openvz-686_96.43.07+2_i386.deb
nvidia-kernel-legacy-96xx-2.6.26-1-686-bigmem_96.43.07+2_i386.deb
  to 
pool/non-free/n/nvidia-graphics-legacy-96xx-modules-i386/nvidia-kernel-legacy-96xx-2.6.26-1-686-bigmem_96.43.07+2_i386.deb
nvidia-kernel-legacy-96xx-2.6.26-1-686_96.43.07+2_i386.deb
  to 
pool/non-free/n/nvidia-graphics-legacy-96xx-modules-i386/nvidia-kernel-legacy-96xx-2.6.26-1-686_96.43.07+2_i386.deb
nvidia-kernel-legacy-96xx-2.6.26-1-openvz-686_96.43.07+2_i386.deb
  to 
pool/non-free/n/nvidia-graphics-legacy-96xx-modules-i386/nvidia-kernel-legacy-96xx-2.6.26-1-openvz-686_96.43.07+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.
Randall Donald <[EMAIL PROTECTED]> (supplier of updated 
nvidia-graphics-legacy-96xx-modules-i386 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.8
Date: Sun, 24 Aug 2008 16:51:16 -0700
Source: nvidia-graphics-legacy-96xx-modules-i386
Binary: nvidia-kernel-legacy-96xx-2.6.26-1-686 
nvidia-kernel-legacy-96xx-2.6-686 nvidia-kernel-legacy-96xx-2.6.26-1-openvz-686 
nvidia-kernel-legacy-96xx-2.6

Bug#490217: marked as done (python-dns vulnerable to CVE-2008-1447 DNS source port guessable)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 19:01:21 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#490217: fixed in python-dns 2.3.0-5.2+etch1
has caused the Debian Bug report #490217,
regarding python-dns vulnerable to CVE-2008-1447 DNS source port guessable
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
490217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490217
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: python-dns
Version: 2.3.0-5.1
Severity: grave
Tags: security
Justification: user security hole

CVE-2008-1447, which deals with DNS reply poisoning that
is possible due to DNS clients sending DNS requests on
predictable UDP source ports, is a security issue that
also applies to python-dns, as it does not implement the
recommended UDP port randomization... example:

Note lack of port randomization in code:
def sendUDPRequest(self, server):
"refactor me"
self.response=None
self.socketInit(socket.AF_INET, socket.SOCK_DGRAM)
for self.ns in server:
try:
# TODO. Handle timeouts &c correctly (RFC)
#self.s.connect((self.ns, self.port))
self.conn()
self.time_start=time.time()
if not self.async:
self.s.send(self.request)
self.response=self.processUDPReply()
#except socket.error:
except None:
continue
break
if not self.response:
if not self.async:
raise DNSError,'no working nameservers found'

In [25]: import DNS
In [26]: d=DNS.DnsRequest(name='www.google.com', server='208.80.142.5', 
port=53)
In [27]: r=d.req() 
In [28]: r=d.req()

In [29]: r=d.req()

In [30]: r=d.req()
(etc)

Yields, with "tcpdump udp port 53":
15:27:15.912894 IP baekdudaegan.metacarta.com.43661 > 
eiger.metacarta.com.domain:  0+ A? www.google.com. (32)
15:27:17.224843 IP baekdudaegan.metacarta.com.43662 > 
eiger.metacarta.com.domain:  0+ A? www.google.com. (32)
15:27:18.344731 IP baekdudaegan.metacarta.com.43663 > 
eiger.metacarta.com.domain:  0+ A? www.google.com. (32)
15:27:18.952729 IP baekdudaegan.metacarta.com.43664 > 
eiger.metacarta.com.domain:  0+ A? www.google.com. (32)
15:27:19.384802 IP baekdudaegan.metacarta.com.43665 > 
eiger.metacarta.com.domain:  0+ A? www.google.com. (32)
15:27:19.752853 IP baekdudaegan.metacarta.com.43666 > 
eiger.metacarta.com.domain:  0+ A? www.google.com. (32)
15:27:20.120819 IP baekdudaegan.metacarta.com.43667 > 
eiger.metacarta.com.domain:  0+ A? www.google.com. (32)
15:27:22.680866 IP baekdudaegan.metacarta.com.43668 > 
eiger.metacarta.com.domain:  0+ A? www.google.com. (32)
15:27:23.416775 IP baekdudaegan.metacarta.com.43669 > 
eiger.metacarta.com.domain:  0+ A? www.google.com. (32)


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages python-dns depends on:
ii  python2.4.4-2An interactive high-level object-o
ii  python-support0.5.6  automated rebuilding support for p

python-dns recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: python-dns
Source-Version: 2.3.0-5.2+etch1

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

python-dns_2.3.0-5.2+etch1.diff.gz
  to pool/main/p/python-dns/python-dns_2.3.0-5.2+etch1.diff.gz
python-dns_2.3.0-5.2+etch1.dsc
  to pool/main/p/python-dns/python-dns_2.3.0-5.2+etch1.dsc
python-dns_2.3.0-5.2+etch1_all.deb
  to pool/main/p/python-dns/python-dns_2.3.0-5.2+etch1_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.
[EMAIL PROTECTED] (supplier of updated python-dns 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: Sat, 26 Jul 2008 21:46:00 -0400
Source: python-dns
Binary: python-dns
Architecture: source al

Bug#494213: Intent to NMU

[Margarita Manterola]

Hi!

I have prepared an NMU that applies the patch provided by Peter De Wachter
and makes mrwtoppm correctly build from source.

I'm attaching the interdiff output, which includes the patch and the
debian/changelog entry, nothing else.

I'll be uploading directly to unstable, according to the 0-day NMU policy.

This package is in serious need of some love.  It's outdated, give several
lintian warnings, etc.  The last upload was in 2004.  I'm not fixing any of
the minor issues of the package due to the freeze.  But after lenny is
realease, something should be done about it.

-- 
Besos,  ,''`.
   Marga   : :' :
   `. `' 
 `-  
diff -u mrwtoppm-0.1.1/debian/changelog mrwtoppm-0.1.1/debian/changelog
--- mrwtoppm-0.1.1/debian/changelog
+++ mrwtoppm-0.1.1/debian/changelog
@@ -1,3 +1,11 @@
+mrwtoppm (0.1.1-2.1) unstable; urgency=low
+
+  * Non-maintainer upload to fix Failure To Build From Source.
+  * Applied patch from Peter De Wachter <[EMAIL PROTECTED]> removing
+unnecesary declaration of extern cmsAdaptMatrixToD50.
+
+ -- Margarita Manterola <[EMAIL PROTECTED]>  Sat, 30 Aug 2008 17:46:03 +
+
 mrwtoppm (0.1.1-2) unstable; urgency=low
 
   * Remove ctest.1 and gtest.1 manpages, the binaries are not included anyway.
only in patch2:
unchanged:
--- mrwtoppm-0.1.1.orig/src/libmri/MRI_GenMRIStFConverter.c
+++ mrwtoppm-0.1.1/src/libmri/MRI_GenMRIStFConverter.c
@@ -61,8 +61,6 @@
 	out->n[2] = in->n[0] * mat->v[2].n[0] + in->n[1] * mat->v[2].n[1] + in->n[2] * mat->v[2].n[2];
 }
 
-extern BOOL cmsAdaptMatrixToD50 (LPMAT3 r, LPcmsCIExyY source);
-
 void
 createXYZtoRGBmat(LPMAT3 mat, const MRI *mri)
 {

Bug#494930: gnash_0.8.3-5(sparc/unstable): FTBFS on sparc

[Petter Reinholdtsen]

This gnash build issue on sparc keep the latest gnash package out of
Lenny.  Is there work going on to fix it?  One idea to work around the
GCC bug is to use -O0 on sparc to disable optimization, hopefully
avoiding the compiler bug.

Happy hacking,
-- 
Petter Reinholdtsen



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

Bug#494930: gnash_0.8.3-5(sparc/unstable): FTBFS on sparc

[Martin Zobel-Helas]

Hi, 

On Sat Aug 30, 2008 at 20:54:51 +0200, Petter Reinholdtsen wrote:
> This gnash build issue on sparc keep the latest gnash package out of
> Lenny.  Is there work going on to fix it?  One idea to work around the
> GCC bug is to use -O0 on sparc to disable optimization, hopefully
> avoiding the compiler bug.

i am looking into it ATM as sparc buildd maintainer and porter.

-- 
 Martin Zobel-Helas <[EMAIL PROTECTED]>  |  Debian Release Team Member
 Debian & GNU/Linux Developer   |   Debian Listmaster
 Public key http://zobel.ftbfs.de/5d64f870.asc   -   KeyID: 5D64 F870
 GPG Fingerprint:  5DB3 1301 375A A50F 07E7  302F 493E FB8E 5D64 F870




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

Bug#494168: [EMAIL PROTECTED]

[Petter Reinholdtsen]

This RC bug seem to be present in unstable and testing, and the
proposed fix has only been uploaded into experimental.  Is there work
going on to upload a fix for Lenny?  Was the error library version
skew, or something else?  The messages in BTS was confusing to me, and
I am unsure if this issue is handled or not.

Happy hacking,
-- 
Petter Reinholdtsen



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

Bug#497131: [jcc] Please add ${python:Depends} to Depends field

[Jeff Breidenbach]

Thanks! NMU uploads are fine, or I'll get to this when I can.



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

Bug#496799: [pkg-horde] Bug#496799: imp4: cyrus.php file missing

[Ola Lundqvist]

severity 496799 wishlist
tags 496799 wontfix
thanks

Hi Pascual

I have investigated this some more. The reason for this problem is that
you have set "cyrus" as the quota driver. This driver no longer exists.
If you set "imap" instead in the servers.php file it will work just fine.

Therefore I'm downgrading this bug now to a wishlist and a wontfix.
The reason for the wishlist is that it could have been good with an automatic
upgrade rewrite for this case.

The wontfix is for that such an automatic upgrade thing is too dangerous
and will not be implemented.

Best regards,

// Ola

On Wed, Aug 27, 2008 at 02:20:13PM +0200, pmunoz wrote:
> Package: imp4
> Version: 4.2-1
> Severity: grave
> Justification: renders package unusable
> 
> The file /usr/share/horde3/imp/lib/Quota/cyrus.php has been removed from
> horde3 (checked hord3 CVS website, stating courier.php and cyrus.php have
> been merged somehow).
> 
> However some imp functions still use cyrus.php.
> 
> Symlinking cyrus.php to imap.php within the same directory solves the 
> situation.
> 
> -- System Information:
> Debian Release: lenny/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: i386 (i686)
> 
> Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages imp4 depends on:
> ii  horde3   3.2.1+debian0-2 horde web application framework
> ii  php-mail-mime1.5.2-0.1   PHP PEAR module for creating 
> MIME 
> ii  php5-imap5.2.6-3 IMAP module for php5
> 
> imp4 recommends no packages.
> 
> Versions of packages imp4 suggests:
> ii  aspell  0.60.6-1 GNU Aspell spell-checker
> pn  imapproxy  (no description available)
> ii  ingo1   1.2-1email filter component for Horde 
> F
> ii  ispell  3.1.20.0-4.4 International Ispell (an 
> interacti
> ii  kronolith2  2.2-1calendar component for Horde 
> Frame
> ii  turba2  2.2.1-1  contact management component for 
> h
> 
> -- no debconf information
> 
> 
> 
> ___
> pkg-horde-hackers mailing list
> [EMAIL PROTECTED]
> http://lists.alioth.debian.org/mailman/listinfo/pkg-horde-hackers
> 

-- 
 - Ola Lundqvist ---
/  [EMAIL PROTECTED] Annebergsslingan 37  \
|  [EMAIL PROTECTED]  654 65 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---



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

Bug#496332: [pylucene] still FTBFS

[Jeff Breidenbach]

Thanks! NMU uploads are fine, or I'll get to this when I can.



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

Processed: Re: [pkg-horde] Bug#496799: imp4: cyrus.php file missing

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 496799 wishlist
Bug#496799: imp4: cyrus.php file missing
Severity set to `wishlist' from `grave'

> tags 496799 wontfix
Bug#496799: imp4: cyrus.php file missing
There were no tags set.
Tags added: wontfix

> 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: severity of 497168 is normal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.35
> severity 497168 normal
Bug#497168: grub-installer cant change grub settings
Severity set to `normal' from `grave'

>
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#496900: rt2500-source: RT2500 fails to connect on kernel 2.6.26-1-amd64

[Ben Hutchings]

rt2500 still works for me on i386.  What authentication type, if any,
are you using?  Also, are you certain that the rt2500 driver is being
used and not the rt2500pci driver that is part of the standard kernel?

"readlink /sys/class/net/$name/device/driver" (substituting the name of
the interface for $name) will show you the driver name.

Ben.





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

Processed: severity of 496900 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.29~bpo40+1
> severity 496900 important
Bug#496900: rt2500-source: RT2500 fails to connect on kernel 2.6.26-1-amd64
Severity set to `important' from `serious'

>
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: tagging 496900

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.29~bpo40+1
> tags 496900 unreproducible moreinfo
Bug#496900: rt2500-source: RT2500 fails to connect on kernel 2.6.26-1-amd64
There were no tags set.
Tags added: unreproducible, moreinfo

>
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#497110: boot loader installation failed when dmraid=true

[Giuseppe Iuculano]

Frans Pop ha scritto:
> But another possibility is that you are just not following the correct
> procedure. Support for dmraid is far from perfect and things will *only*
> work if you follow the documented procedure.
> 
> How did you do the partitioning? Did you *exactly* follow the instructions
> that are given in the "Partitioning" section of the SataRAID wiki page [1]?
> 
> Did the partman screens look like the examples that are given there?
> Screenshots before and after doing the "Write changes in SATA RAID
> partitioning to disk" step would be nice too.
> 
> Please send the /var/log/partman (gzipped!) after you do the partitioning.

Ok, some other test.


- First test

Partition disk:
http://sd6.iuculano.it/dmraid-testing/partman1-1.png

Choose free space and create a new partition:
http://sd6.iuculano.it/dmraid-testing/partman1-2.png
http://sd6.iuculano.it/dmraid-testing/partman1-3.png

Unfortunately I got an out of memory.

You can find partman and sylog log here:
http://sd6.iuculano.it/dmraid-testing/log1.tar.gz


- Second test

Partition disk:

This time I choose "Automatically partition the free space", "all files in one
partition" and I got:
http://sd6.iuculano.it/dmraid-testing/partman2-1.png
http://sd6.iuculano.it/dmraid-testing/partman2-2.png

I selected "finish partitioning and write changes to disk and I got the bad
device with "p", and no grub support.

brw---1 root root 254,   0 Aug 30 18:14 sil_aiahbgbgaaaj
brw---1 root root 254,   1 Aug 30 18:16 sil_aiahbgbgaaajp1
brw---1 root root 254,   2 Aug 30 18:14 sil_aiahbgbgaaajp2
brw---1 root root 254,   3 Aug 30 18:14 sil_aiahbgbgaaajp5


the second test log is here: http://sd6.iuculano.it/dmraid-testing/log2.tar.gz

- Third test (as wiki procedure but with "Automatically partition the free 
space")

As the second, but this time I selected "Write changes in SATA RAID partitioning
to disk", and I got:
http://sd6.iuculano.it/dmraid-testing/partman3-1.png

# ls -la /dev/mapper
drwxr-xr-x2 root root  180 Aug 30 18:50 .
drwxr-xr-x   10 root root 2860 Aug 30 18:50 ..
crw-rw1 root root  10,  60 Aug 30 18:42 control
brw---1 root root 254,   0 Aug 30 18:43 sil_aiahbgbgaaaj
brw---1 root root 254,   4 Aug 30 18:56 sil_aiahbgbgaaaj1
brw---1 root root 254,   5 Aug 30 18:56 sil_aiahbgbgaaaj5
brw---1 root root 254,   1 Aug 30 19:02 sil_aiahbgbgaaajp1
brw---1 root root 254,   2 Aug 30 19:02 sil_aiahbgbgaaajp2
brw---1 root root 254,   3 Aug 30 18:43 sil_aiahbgbgaaajp5

I selected partition #1 below sil_aiahbgbgaaaj1 (partion #1) and I set it for
ext3 /  :

http://sd6.iuculano.it/dmraid-testing/partman3-2.png

Now I selected sil_aiahbgbgaaaj5 (partition #5) and pressed enter:
http://sd6.iuculano.it/dmraid-testing/partman3-3.png
http://sd6.iuculano.it/dmraid-testing/partman3-4.png

Now I got:
http://sd6.iuculano.it/dmraid-testing/partman3-5.png

I selected Free space and create a new partition, set it as swap area:
http://sd6.iuculano.it/dmraid-testing/partman3-6.png

Now I selected "finish partitioning and write changes to disk
http://sd6.iuculano.it/dmraid-testing/partman3-7.png

Installed base system: OK

This time, I can install grub. Installation terminated successfully


- Fourth test

As the first, but I increased virtual machine memory to 512MB (In first test was
256MB).
Same out of memory.



In conclusion, If I try to follow wiki procedure I can't create new partition,
but only "Automatically partition the free space", otherwise I got an out of 
memory


Giuseppe.



signature.asc
Description: OpenPGP digital signature

Bug#494221: netmrg: FTBFS: *** [zero.rrd] Segmentation fault

[Sandro Tosi]

Hi,
I tried to replicate this FTBFS (but I'm on AMD64) but here it builds
fine in an up-to-date pbuilder chroot (I'm attaching hte build log for
reference).

Could it be that the recent upload[1] (just the day before this bug
was filled) of rrdtool have fixed it (for example linking to updated
libraries)?

Sandro

[1] http://packages.qa.debian.org/r/rrdtool.html

-- 
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


netmrg_0.20-2_amd64.build.bz2
Description: BZip2 compressed data

Bug#480801: [pkg-mono-group] Bug#480801: remove gluezilla from testing?

[Luk Claes]

Mirco Bauer wrote:
> On Sat, 2008-08-30 at 16:43 +0200, Thomas Viehmann wrote:
>> Hi,
>>
>> gluezilla has not been getting the attention necessary to fix #480801.
>> It has been obvious that this will be RC for 3.5 months and is RC for
>> 2.5 months.
>> As gluezilla never was released with Debian and has no reverse
>> dependencies, it might be a good candidate to be removed from lenny.
>>
>> Kind regards
> 
> I tried to port gluezilla to xulrunner 1.9 but I failed.
> There is a package in mono (libmono-mozilla0.2-cil) that recommends
> gluezilla. Nothing in debian would use that though, as it's the wrapper
> library to implement the WebControl class part of the WinForms
> implementation in Mono, e.g. it's only used by Windows applications that
> target MS .NET.
> 
> So I have no objections to see gluezilla being removed from testing.

Ok, removal hint added.

Cheers

Luk



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

Bug#494213: Intent to NMU

[Guus Sliepen]

On Sat, Aug 30, 2008 at 03:51:19PM -0300, Margarita Manterola wrote:

> I have prepared an NMU that applies the patch provided by Peter De Wachter
> and makes mrwtoppm correctly build from source.
> 
> I'm attaching the interdiff output, which includes the patch and the
> debian/changelog entry, nothing else.
> 
> I'll be uploading directly to unstable, according to the 0-day NMU policy.
> 
> This package is in serious need of some love.  It's outdated, give several
> lintian warnings, etc.  The last upload was in 2004.  I'm not fixing any of
> the minor issues of the package due to the freeze.  But after lenny is
> realease, something should be done about it.

Thanks. I currently do not have too much time, and there are other RC bugs that
I'm fixing at the moment. I think after Lenny, mrwtoppm should be removed,
since upstream is not working on it anymore, and since dcraw (and the
gimp-dcraw package) package can also convert DiMAGE RAW files. 

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen <[EMAIL PROTECTED]>


signature.asc
Description: Digital signature

Bug#495968: remove gpicview from lenny?

[Thomas Viehmann]

Hi,

based on the maintainer's comments in the bug log, it seems dubious
whether the bug #495968 (insecure /tmp file vulnerability) is fixed in
time for lenny. Given that it has never been released with Debian
before, it would be better to remove gpicview from lenny for now than to
risk releasing the vulnerable package.

Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/



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

Processed: severity of 490746 is normal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 
> 2.10.26ubuntu7~hardy1
> severity 490746 normal
Bug#490746: It FTBFS with gcc 4.3 in i386 arch
Severity set to `normal' from `serious'

>
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#495154: marked as done (RM: tmsnc -- ROM; project discontinued upstream)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 22:03:49 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#495154: fixed
has caused the Debian Bug report #495154,
regarding RM: tmsnc -- ROM; project discontinued upstream
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
495154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495154
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: tmsnc
Severity: serious

According to upstream [1]:

Project discontinued!

A replacement application for TMSNC is being developed here:
http://www.fama-im.org

Fama adds improved stability, flexibility (with support for other
protocols), full UTF-8 support and much more. You may still download old
releases of TMSNC, however there is no maintenence of the code. Give
Fama a chance instead.

Fama is already packaged in Debian [2]

[1] http://tmsnc.sourceforge.net/
[2] http://packages.debian.org/fama


--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 tmsnc |  0.3.2-1.1 | source, alpha, amd64, arm, armel, hppa, hurd-i386, 
i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

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

Debian distribution maintenance software
pp.
Thomas Viehmann (the ftpmaster behind the curtain)

--- End Message ---

Bug#496370: marked as done (The possibility of attack with the help of symlinks in some Debian packages)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 23:39:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fml has been removed from Debian, closing #496370
has caused the Debian Bug report #496370,
regarding The possibility of attack with the help of symlinks in some Debian 
packages
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
496370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496370
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fml
Severity: grave

Hi, maintainer!

This message about the error concerns a few packages  at  once.   I've
tested all the packages (for Lenny) on my Debian mirror.  All  scripts
of packages (marked as executable) were tested.

In some packages I've discovered scripts with errors which may be used
by a user for damaging important system files or user's files.

For example if a script uses in its work a temp file which is  created
in /tmp directory, then every user can create symlink  with  the  same
name in this directory in order to  destroy  or  rewrite  some  system
or user file.  Symlink attack may also  lead  not  only  to  the  data
desctruction but to denial of service as well.

Even if you create files or directories with help of function 'RANDOM'
or pid(), then your system is not protected. Attacker can create many
symlinks in order to destroy your data or create 'denial  of  service'
for your package scripts.

Even if you make rm(dir) for files/directories, then  your  system  is
not protected. Attacker can permanently create symlinks.

This list is created with the help of script.  This list is sorted  by
hand. Howewer in some cases mistake is possible.

Please, Be understanding to possible mistakes. :)

I set Severity into grave for this bug. The table of discovered
problems is below.

Discussion of this bug you can see in debian-devel@:
http://lists.debian.org/debian-devel/2008/08/msg00271.html

Binary-package: r-base-core-ra (1.1.1-1)
file: /usr/lib/Ra/lib/R/bin/javareconf
Binary-package: rccp (0.9-2)
file: /usr/lib/rccp/delqueueask
Binary-package: mafft (6.240-1)
file: /usr/bin/mafft-homologs
Binary-package: openoffice.org-common (1:2.4.1-6)
file: /usr/lib/openoffice/program/senddoc
Binary-package: crossfire-maps (1.11.0-1)
file: /usr/share/games/crossfire/maps/Info/combine.pl
Binary-package: sgml2x (1.0.0-11.1)
file: /usr/bin/rlatex
Binary-package: liguidsoap (0.3.6-4)
file: /var/lib/liguidsoap/liguidsoap.py
Binary-package: citadel-server (7.37-1)
file: /usr/lib/citadel-server/migrate_aliases.sh
Binary-package: ampache (3.4.1-1)
file: /usr/share/ampache/www/locale/base/gather-messages.sh
Binary-package: xen-utils-3.2-1 (3.2.1-2)
file: /usr/lib/xen-3.2-1/bin/qemu-dm.debug
Binary-package: dtc-common (0.29.6-1)
file: /usr/share/dtc/admin/accesslog.php
file: /usr/share/dtc/admin/sa-wrapper
Binary-package: honeyd-common (1.5c-3)
file: /usr/share/honeyd/scripts/test.sh
Binary-package: lustre-tests (1.6.5-1)
file: /usr/lib/lustre/tests/runiozone
Binary-package: linuxtrade (3.65-8+b4)
file: /usr/share/linuxtrade/bin/linuxtrade.bwkvol
file: /usr/share/linuxtrade/bin/linuxtrade.wn
file: /usr/share/linuxtrade/bin/moneyam.helper
Binary-package: freevo (1.8.1-0)
file: /usr/bin/freevo.real
Binary-package: fml (4.0.3.dfsg-2)
file: /usr/share/fml/libexec/mead.pl
Binary-package: rkhunter (1.3.2-3)
file: /usr/bin/rkhunter
Binary-package: openswan (1:2.4.12+dfsg-1.1)
file: /usr/lib/ipsec/livetest
Binary-package: linux-patch-openswan (1:2.4.12+dfsg-1.1)
file: /usr/src/kernel-patches/all/openswan/packaging/utils/maysnap
file: /usr/src/kernel-patches/all/openswan/packaging/utils/maytest
Binary-package: aptoncd (0.1-1.1)
file: /usr/share/aptoncd/xmlfile.py
Binary-package: cdcontrol (1.90-1.1)
file: /usr/lib/cdcontrol/writtercontrol
Binary-package: newsgate (1.6-23)
file: /usr/bin/mkmailpost
Binary-package: gpsdrive-scripts (2.10~pre4-3)
file: /usr/bin/geo-code
Binary-package: impose+ (0.2-11)
file: /usr/bin/impose
Binary-package: mgt (2.31-5)
file: /usr/games/mailgo
Binary-package: audiolink (0.05-1)
file: /usr/bin/audiolink
Binary-package: ibackup (2.27-4.1)
file: /usr/bin/ibackup
Binary-package: emacspeak (26.0-3)
file: /usr/share/emacs/site-lisp/emacspeak/etc/extract-table.pl
Binary-package: bk2site (1:1.1.9-3.1)
file: /usr/lib/cgi-bin/bk2site/redirect.pl
Binary-package: datafreedom-perl (0.1.7-1)
file: /usr/bin/dfxml-invoice
Binary-package: emacs-jabber (0.7.91-1)
file: /usr/lib/emacsen-common/packages/install

Bug#489992: marked as done (php-timezonedb is now useless and should not be part of lenny)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 23:42:10 +0100
with message-id <[EMAIL PROTECTED]>
and subject line php-timezonedb has been removed from Debian, closing #489992
has caused the Debian Bug report #489992,
regarding php-timezonedb is now useless and should not be part of lenny
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
489992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489992
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Source: php-timezonedb
Version: 2008.3-1
Severity: serious

Now that a version of the php5 package has migrated to testing this package is 
completely useless.

If I find no other use for it in some time I'll request it's removal.
The severity is just to make it RC bogus and thus avoid migrating to lenny as 
soon as a removal hint is added.

Cheers,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 2008.3-1+rm

The php-timezonedb package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/496985 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

--- End Message ---

Bug#496437: marked as done (The possibility of attack with the help of symlinks in some Debian packages)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 23:43:53 +0100
with message-id <[EMAIL PROTECTED]>
and subject line newsgate has been removed from Debian, closing #496437
has caused the Debian Bug report #496437,
regarding The possibility of attack with the help of symlinks in some Debian 
packages
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
496437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496437
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: newsgate
Severity: grave

Hi, maintainer!

This message about the error concerns a few packages  at  once.   I've
tested all the packages (for Lenny) on my Debian mirror.  All  scripts
of packages (marked as executable) were tested.

In some packages I've discovered scripts with errors which may be used
by a user for damaging important system files or user's files.

For example if a script uses in its work a temp file which is  created
in /tmp directory, then every user can create symlink  with  the  same
name in this directory in order to  destroy  or  rewrite  some  system
or user file.  Symlink attack may also  lead  not  only  to  the  data
desctruction but to denial of service as well.

Even if you create files or directories with help of function 'RANDOM'
or pid(), then your system is not protected. Attacker can create many
symlinks in order to destroy your data or create 'denial  of  service'
for your package scripts.

Even if you make rm(dir) for files/directories, then  your  system  is
not protected. Attacker can permanently create symlinks.

This list is created with the help of script.  This list is sorted  by
hand. Howewer in some cases mistake is possible.

Please, Be understanding to possible mistakes. :)

I set Severity into grave for this bug. The table of discovered
problems is below.

Discussion of this bug you can see in debian-devel@:
http://lists.debian.org/debian-devel/2008/08/msg00271.html

Binary-package: r-base-core-ra (1.1.1-1)
file: /usr/lib/Ra/lib/R/bin/javareconf
Binary-package: rccp (0.9-2)
file: /usr/lib/rccp/delqueueask
Binary-package: mafft (6.240-1)
file: /usr/bin/mafft-homologs
Binary-package: openoffice.org-common (1:2.4.1-6)
file: /usr/lib/openoffice/program/senddoc
Binary-package: crossfire-maps (1.11.0-1)
file: /usr/share/games/crossfire/maps/Info/combine.pl
Binary-package: sgml2x (1.0.0-11.1)
file: /usr/bin/rlatex
Binary-package: liguidsoap (0.3.6-4)
file: /var/lib/liguidsoap/liguidsoap.py
Binary-package: citadel-server (7.37-1)
file: /usr/lib/citadel-server/migrate_aliases.sh
Binary-package: ampache (3.4.1-1)
file: /usr/share/ampache/www/locale/base/gather-messages.sh
Binary-package: xen-utils-3.2-1 (3.2.1-2)
file: /usr/lib/xen-3.2-1/bin/qemu-dm.debug
Binary-package: dtc-common (0.29.6-1)
file: /usr/share/dtc/admin/accesslog.php
file: /usr/share/dtc/admin/sa-wrapper
Binary-package: honeyd-common (1.5c-3)
file: /usr/share/honeyd/scripts/test.sh
Binary-package: lustre-tests (1.6.5-1)
file: /usr/lib/lustre/tests/runiozone
Binary-package: linuxtrade (3.65-8+b4)
file: /usr/share/linuxtrade/bin/linuxtrade.bwkvol
file: /usr/share/linuxtrade/bin/linuxtrade.wn
file: /usr/share/linuxtrade/bin/moneyam.helper
Binary-package: freevo (1.8.1-0)
file: /usr/bin/freevo.real
Binary-package: fml (4.0.3.dfsg-2)
file: /usr/share/fml/libexec/mead.pl
Binary-package: rkhunter (1.3.2-3)
file: /usr/bin/rkhunter
Binary-package: openswan (1:2.4.12+dfsg-1.1)
file: /usr/lib/ipsec/livetest
Binary-package: linux-patch-openswan (1:2.4.12+dfsg-1.1)
file: /usr/src/kernel-patches/all/openswan/packaging/utils/maysnap
file: /usr/src/kernel-patches/all/openswan/packaging/utils/maytest
Binary-package: aptoncd (0.1-1.1)
file: /usr/share/aptoncd/xmlfile.py
Binary-package: cdcontrol (1.90-1.1)
file: /usr/lib/cdcontrol/writtercontrol
Binary-package: newsgate (1.6-23)
file: /usr/bin/mkmailpost
Binary-package: gpsdrive-scripts (2.10~pre4-3)
file: /usr/bin/geo-code
Binary-package: impose+ (0.2-11)
file: /usr/bin/impose
Binary-package: mgt (2.31-5)
file: /usr/games/mailgo
Binary-package: audiolink (0.05-1)
file: /usr/bin/audiolink
Binary-package: ibackup (2.27-4.1)
file: /usr/bin/ibackup
Binary-package: emacspeak (26.0-3)
file: /usr/share/emacs/site-lisp/emacspeak/etc/extract-table.pl
Binary-package: bk2site (1:1.1.9-3.1)
file: /usr/lib/cgi-bin/bk2site/redirect.pl
Binary-package: datafreedom-perl (0.1.7-1)
file: /usr/bin/dfxml-invoice
Binary-package: emacs-jabber (0.7.91-1)
file: /usr/lib/emacsen-common/packag

Bug#497216: wordpress: CVE-2008-3747 information leak, does not always force ssl

[Nico Golde]

Package: wordpress
Severity: grave
Tags: security patch

Hi,
the following CVE (Common Vulnerabilities & Exposures) id was
published for wordpress.

CVE-2008-3747[0]:
| The (1) get_edit_post_link and (2) get_edit_comment_link functions in
| wp-includes/link-template.php in WordPress before 2.6.1 do not force
| SSL communication in the intended situations, which might allow remote
| attackers to gain administrative access by sniffing the network for a
| cookie.

If you fix the vulnerability please also make sure to include the
CVE id in your changelog entry.

There is a patch on: 
http://trac.wordpress.org/attachment/ticket/7359/edit_links_ssl.diff

Please ping me via private mail if you need a sponsor for 
the upload.

For further information see:

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3747
http://security-tracker.debian.net/tracker/CVE-2008-3747

-- 
Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.


pgpvgniqwfm7t.pgp
Description: PGP signature

Bug#497219: dhcp3-server-ldap: Unable to authenticate to LDAP with valid account

[Mark Pavlichuk]

Package: dhcp3-server-ldap
Version: 3.1.1-3
Severity: grave
Tags: security
Justification: user security hole

I'm getting this error message :

Connecting to LDAP server amd64:389
Error: Cannot login into ldap server amd64:389: Success
Configuration file errors encountered -- exiting

and when I enter an incorrect password it works.  This seems to match bug 
#484261 that apparently was previously
fixed.  I guess the patch wasn't reapplied to this version? 

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dhcp3-server-ldap depends on:
ii  debianutils   2.30   Miscellaneous utilities specific t
ii  dhcp3-common  3.1.1-3common files used by all the dhcp3
ii  dhcp3-server  3.1.1-3DHCP server for automatic IP addre
ii  libc6 2.7-13 GNU C Library: Shared libraries
ii  libldap-2.4-2 2.4.10-3   OpenLDAP libraries
ii  libssl0.9.8   0.9.8g-13  SSL shared libraries

dhcp3-server-ldap recommends no packages.

dhcp3-server-ldap suggests no packages.

-- no debconf information



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

Bug#497131: marked as done ([jcc] Please add ${python:Depends} to Depends field)

[Debian Bug Tracking System]

Your message dated Sun, 31 Aug 2008 01:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#497131: fixed in jcc 1.9-8
has caused the Debian Bug report #497131,
regarding [jcc] Please add ${python:Depends} to Depends field
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
497131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497131
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: jcc
Version: 1.9-7.1
Severity: grave
Justification: Render package unusable
tags: patch

Hello,

Trying to use 'python -m' with jcc fails do to a lack dependencies
that should be added if  ${python:Depends} was present at
Depends field:

Here is the error in a clean sid environment: 
 > python -m jcc
 > Traceback (most recent call last):
 > File "/usr/lib/python2.5/runpy.py", line 87, in run_module
 >  raise ImportError("No module named " + mod_name)
 >  ImportError: No module named jcc


Adding ${python:Depends} var, rebuild the package and reinstall solve
this problem.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_SV.UTF-8, LC_CTYPE=es_SV.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages jcc depends on:
ii  libc6 2.7-13 GNU C Library: Shared libraries
ii  libgcc1   1:4.3.1-9  GCC support library
ii  libstdc++64.3.1-9The GNU Standard C++ Library v3
ii  openjdk-6-jdk 6b11-6 OpenJDK Development Kit (JDK)

jcc recommends no packages.

jcc suggests no packages.

-- no debconf information



Cheers
-- 
Rene Mauricio Mayorga   |  jabber: [EMAIL PROTECTED]
http://rmayorga.org |  
--
08B6 58AB A691 DD56 C30B  8D37 8040 19FA A209 C305


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: jcc
Source-Version: 1.9-8

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

jcc_1.9-8.diff.gz
  to pool/main/j/jcc/jcc_1.9-8.diff.gz
jcc_1.9-8.dsc
  to pool/main/j/jcc/jcc_1.9-8.dsc
jcc_1.9-8_i386.deb
  to pool/main/j/jcc/jcc_1.9-8_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.
Jeff Breidenbach <[EMAIL PROTECTED]> (supplier of updated jcc 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.8
Date: Sat, 30 Aug 2008 18:31:31 -0700
Source: jcc
Binary: jcc
Architecture: source i386
Version: 1.9-8
Distribution: unstable
Urgency: low
Maintainer: Jeff Breidenbach <[EMAIL PROTECTED]>
Changed-By: Jeff Breidenbach <[EMAIL PROTECTED]>
Description: 
 jcc- code generator producing a Python extension from Java classes
Closes: 497131
Changes: 
 jcc (1.9-8) unstable; urgency=low
 .
   * Add ${python:Depends} (closes: 497131)
Checksums-Sha1: 
 622500604ffa9fb3e0cc0f669c7b1770e271bee4 989 jcc_1.9-8.dsc
 3362f8b0423352b56d05c95c54f4ac8ea315da24 4637 jcc_1.9-8.diff.gz
 6945703a9cfb35c566ca433c24ab5aaa625ede10 186332 jcc_1.9-8_i386.deb
Checksums-Sha256: 
 ba9e5d8f6a00377e5fd14256007a0eb45788ac9652dc4858f1c17fe2b897b8aa 989 
jcc_1.9-8.dsc
 e64d903ac76eb07f7873cc9b3588ee77f7b230504254c45b2bb1997fb29c481e 4637 
jcc_1.9-8.diff.gz
 64f927a9c1688a5502574b05470eacb5267005742afa0718578229f9d679d440 186332 
jcc_1.9-8_i386.deb
Files: 
 8776a9a491318f43c0065444e91f5a63 989 python extra jcc_1.9-8.dsc
 5da38f1c7a7f986300bcb57942724559 4637 python extra jcc_1.9-8.diff.gz
 9792a881ce99d34f377fd7817062c1c0 186332 python extra jcc_1.9-8_i386.deb

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

iD8DBQFIufWXazfo3TSzaFYRAlFqAJ9ggJMMFV5PjyV6rgehx7n5He7N8QCeLeh9
DYU3ZAcMa3mTxOGAFEj7I3M=
=T3aF
-END PGP SIGNATURE-


--- End Message ---

Bug#497225: gnome-alsamixer: Dead upstream package without maintainer bug fixes is security risk

[Osamu Aoki]

Package: gnome-alsamixer
Version: 0.9.7~cvs.20060916.ds.1-2
Severity: grave
Tags: security
Justification: user security hole

I am filing this bug to discuss removal of this package from leny.

1. The upstream is dead.
   Last release 2006-08-06 (CVS)
   Current Gnome distribution does not include this software.
2. gnome-alsamixer does not identify new hardwares correctly.
   I have HDA Intel but gnome-alsamixer show it as Sigmatel 
3. The better alsa mixer support functionality is in GNOME-Applets.
   New gnome-volume-control does better job.
4. No dependency requireis this package in lenny.
5. There are 2 bugs marked upstream.
   The maintainer did not look into these bugs. 
   (I think one of it is just warning, so it may be OK ...)

I know current maintainer took effort for lenny:
 http://packages.qa.debian.org/g/gnome-alsamixer.html

I think having unmaintained package our archive with no added benefits
is bad idea for security review.

If my asessment is wrong, maintainer can close this bug.

But I think it is time to request removal.

(Or maintainer to upload transition package and hint it to
debian-release to include it to lenny)

Thans for your work and best regards,

Osamu

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnome-alsamixer depends on:
ii  gconf2 2.22.0-1  GNOME configuration database syste
ii  libart-2.0-2   2.3.20-2  Library of functions for 2D graphi
ii  libasound2 1.0.16-2  ALSA library
ii  libatk1.0-01.22.0-1  The ATK accessibility toolkit
ii  libbonobo2-0   2.22.0-1  Bonobo CORBA interfaces library
ii  libbonoboui2-0 2.22.0-1  The Bonobo UI library
ii  libc6  2.7-13GNU C Library: Shared libraries
ii  libcairo2  1.6.4-6   The Cairo 2D vector graphics libra
ii  libgconf2-42.22.0-1  GNOME configuration database syste
ii  libglib2.0-0   2.16.5-1  The GLib library of C routines
ii  libgnome2-02.20.1.1-1The GNOME 2 library - runtime file
ii  libgnomecanvas2-0  2.20.1.1-1A powerful object-oriented display
ii  libgnomeui-0   2.20.1.1-1The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0 1:2.22.0-4GNOME Virtual File System (runtime
ii  libgtk2.0-02.12.11-3 The GTK+ graphical user interface 
ii  libice62:1.0.4-1 X11 Inter-Client Exchange library
ii  liborbit2  1:2.14.13-0.1 libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0  1.20.5-2  Layout and rendering of internatio
ii  libpopt0   1.14-4lib for parsing cmdline parameters
ii  libsm6 2:1.0.3-2 X11 Session Management library

gnome-alsamixer recommends no packages.

gnome-alsamixer suggests no packages.

-- no debconf information



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

Bug#496332: pylucene: diff for NMU version 2.3.1-1.1

[Rene Mayorga]

Hi Jeff,

Attached is the diff for my pylucene 2.3.1-1.1 NMU.

but there is still a blocking bug to avoid FTFBS with whit this
package(#497131)

I'm passing this bug report to my AM, so the package could be NMUed soon
:)

Cheers
--
René Mayorga
diff -Nru /tmp/tFHIF4djQ4/pylucene-2.3.1/debian/changelog /tmp/loHZh1Gq1l/pylucene-2.3.1/debian/changelog
--- /tmp/tFHIF4djQ4/pylucene-2.3.1/debian/changelog	2008-08-30 22:25:20.0 -0400
+++ /tmp/loHZh1Gq1l/pylucene-2.3.1/debian/changelog	2008-08-30 22:25:20.0 -0400
@@ -1,3 +1,10 @@
+pylucene (2.3.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Adding python-all-dev and python-all to B-D (Closes: #496332)
+  
+ -- Rene Mayorga <[EMAIL PROTECTED]>  Sat, 30 Aug 2008 19:55:25 -0600
+
 pylucene (2.3.1-1) unstable; urgency=low
 
   * Initial release (closes: 490254)
diff -Nru /tmp/tFHIF4djQ4/pylucene-2.3.1/debian/control /tmp/loHZh1Gq1l/pylucene-2.3.1/debian/control
--- /tmp/tFHIF4djQ4/pylucene-2.3.1/debian/control	2008-08-30 22:25:20.0 -0400
+++ /tmp/loHZh1Gq1l/pylucene-2.3.1/debian/control	2008-08-30 22:25:20.0 -0400
@@ -2,7 +2,7 @@
 Section: text
 Priority: extra
 Maintainer: Jeff Breidenbach <[EMAIL PROTECTED]>
-Build-Depends: cdbs, debhelper (>= 5), jcc, openjdk-6-jdk, ant
+Build-Depends: cdbs, debhelper (>= 5), jcc, openjdk-6-jdk, ant, python-all-dev, python-all
 Standards-Version: 3.7.3
 
 Package: pylucene


signature.asc
Description: Digital signature

Bug#497226: brasero: Burn button disabled. No indication of why.

[Chris Capon]

Package: brasero
Version: 0.8.0-2
Severity: grave
Justification: renders package unusable


When selecting a .iso file to burn to a rewritable DVD, the Burn button is 
greyed out and can not be 
clicked.  There is no information displayed as to why the button is disabled.

Either the button should be enabled or there should be a message indicating the 
reason it is disabled.


To reproduce this bug:

1) Either start Brasero directly and select "Burn image" or use Nautilus, right 
click on a .iso file and 
select "Open with Brasero Disc Burning".

2) Image Burning Setup dialog appears.

Select a disc to write to: shows the systems DVD-RW drive, disk is in.
Size: 4.4 GB free.
Status: "the medium can be recorded (automatic blanking required)"
Number of copies: is greyed out - set to 1
Path: set to the image file.  It is a prepared .iso 2.2 GB in size.
Image type: "Let brasero choose (safest)".  There are no other options in the 
dropdown.

Cancel button is lit and can be clicked.
Burn button is greyed out and can not be clicked.

There are no additional messages explaining why Burn is disabled.


Right clicking in Nautilus and selecting "Open with CD/DVD Creator" instead, 
successfully burns the 
same .iso image to the same disk and drive.

Brasero is capable of erasing the disk using Tools/Erase.



-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 
'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages brasero depends on:
ii  gconf2 2.22.0-1  GNOME configuration database syste
ii  genisoimage9:1.1.8-1+b1  Creates ISO-9660 CD-ROM filesystem
ii  gstreamer0.10-plugins- 0.10.19-2 GStreamer plugins from the "base" 
ii  libart-2.0-2   2.3.20-2  Library of functions for 2D graphi
ii  libatk1.0-01.22.0-1  The ATK accessibility toolkit
ii  libbeagle1 0.3.5-1+b1library for accessing beagle using
ii  libbonobo2-0   2.22.0-1  Bonobo CORBA interfaces library
ii  libbonoboui2-0 2.22.0-1  The Bonobo UI library
ii  libc6  2.7-13GNU C Library: Shared libraries
ii  libcairo2  1.6.4-6   The Cairo 2D vector graphics libra
ii  libdbus-1-31.2.1-3   simple interprocess messaging syst
ii  libdbus-glib-1-2   0.76-1simple interprocess messaging syst
ii  libfontconfig1 2.6.0-1   generic font configuration library
ii  libfreetype6   2.3.7-2   FreeType 2 font engine, shared lib
ii  libgconf2-42.22.0-1  GNOME configuration database syste
ii  libglib2.0-0   2.16.4-2  The GLib library of C routines
ii  libgnome2-02.20.1.1-1The GNOME 2 library - runtime file
ii  libgnomecanvas2-0  2.20.1.1-1A powerful object-oriented display
ii  libgnomeui-0   2.20.1.1-1The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0 1:2.22.0-4GNOME Virtual File System (runtime
ii  libgstreamer-plugins-b 0.10.19-2 GStreamer libraries from the "base
ii  libgstreamer0.10-0 0.10.19-3 Core GStreamer libraries and eleme
ii  libgtk2.0-02.12.11-3 The GTK+ graphical user interface 
ii  libhal10.5.11-3  Hardware Abstraction Layer - share
ii  libice62:1.0.4-1 X11 Inter-Client Exchange library
ii  liborbit2  1:2.14.13-0.1 libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0  1.20.5-1  Layout and rendering of internatio
ii  libpixman-1-0  0.10.0-2  pixel-manipulation library for X a
ii  libpng12-0 1.2.27-1  PNG library - runtime
ii  libpopt0   1.14-4lib for parsing cmdline parameters
ii  libsm6 2:1.0.3-2 X11 Session Management library
ii  libtotem-plparser102.22.3-1  Totem Playlist Parser library - ru
ii  libx11-6   2:1.1.4-2 X11 client-side library
ii  libxcb-render-util00.2.1+git1-1  utility libraries for X C Binding 
ii  libxcb-render0 1.1-1.1   X C Binding, render extension
ii  libxcb11.1-1.1   X C Binding
ii  libxml22.6.32.dfsg-3 GNOME XML library
ii  libxrender11:0.9.4-2 X Rendering Extension client libra
ii  wodim  9:1.1.8-1+b1  command line CD/DVD writing tool
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages brasero recommends:
ii  gnome-mount   0.7-2  wrapper for (un)mounting and eject
ii  gstreamer0.10-plugins-bad 0.10.7-2   GStreamer plugins from the "bad" s
ii  g

Bug#490963: iceweasel is not saving my bookmark changes

[Eric Dorland]

* Chip Salzenberg ([EMAIL PROTECTED]) wrote:
> Package: iceweasel
> Version: 3.0~rc2-2
> Severity: important
> 
> I have disabled all extensions.  Nevertheless, when I make changes to my
> bookmarks - adding a new bookmark or even adding a new separator - those
> changes are not saved when I quit and restart iceweasel.
> 
> Strangely, one kind of change *is* saved: if I rearrange the order of
> folders in my bookmark toolbar, the rearrangement is saved.

What are the permissions on the files under ~/.mozilla/firefox?

-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]



signature.asc
Description: Digital signature

Bug#491524: marked as done (iceweasel: new upstream point release (2.0.0.16) fixes some security issues)

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 23:40:29 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in stable
has caused the Debian Bug report #491524,
regarding iceweasel: new upstream point release (2.0.0.16) fixes some security 
issues
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
491524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491524
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: iceweasel
Version: 2.0.0.15-0etch1
Severity: grave
Tags: security
Justification: user security hole

firefox 2.0.0.16 is now available [1].  this release fixes CVE-2008-2785 
and CVE-2008-2933 [2].  please update the package in stable.

thanks for the hard work.

[1] http://www.mozilla.com/en-US/firefox/all-older.html
[2] http://lwn.net/Articles/290491/

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-6-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages iceweasel depends on:
ii  debianutils   2.30   Miscellaneous utilities specific t
ii  fontconfig2.6.0-1generic font configuration library
ii  libc6 2.7-12 GNU C Library: Shared libraries
ii  libgcc1   1:4.3.1-6  GCC support library
ii  libglib2.0-0  2.16.4-2   The GLib library of C routines
ii  libgtk2.0-0   2.12.11-1  The GTK+ graphical user interface 
ii  libnspr4-0d   4.7.1-3NetScape Portable Runtime Library
ii  libstdc++64.3.1-6The GNU Standard C++ Library v3
ii  procps1:3.2.7-8  /proc file system utilities
ii  psmisc22.6-1 Utilities that use the proc filesy
pn  xulrunner-1.9  (no description available)

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
ii  latex-xft-fonts   0.1-8  Xft-compatible versions of some La
ii  libkrb53  1.6.dfsg.4~beta1-3 MIT Kerberos runtime libraries
pn  mozplugger (no description available)
pn  ttf-mathematica4.1 (no description available)
pn  xfonts-mathml  (no description available)
pn  xprint (no description available)
pn  xulrunner-1.9-gnome-s  (no description available)


--- End Message ---
--- Begin Message ---
Version: 2.0.0.16-0etch1

Already fixed.

-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]



signature.asc
Description: Digital signature
--- End Message ---

Bug#493310: marked as done (iceweasel: fails to start (after initial start))

[Debian Bug Tracking System]

Your message dated Sat, 30 Aug 2008 23:44:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#493310: iceweasel: fails to start (after initial start)
has caused the Debian Bug report #493310,
regarding iceweasel: fails to start (after initial start)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
493310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493310
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: iceweasel
Version: 3.0.1-1
Severity: grave

The first time I start iceweasel, everything seems to work fine.  The
next time I try to start it (and subsequent times after that), I get either:
  Error: in (function call): procedure or syntax required but got: Error: 
fatal: looped fatal error
or:
  Error: in guard: symbol required but got: Error: fatal: looped fatal error

If I remove the ~/.mozilla directory, then it starts fine again the
first time, but after that, I get the same error.

Everything worked fine with iceweasel 3.0~rc2-1 and xulrunner 1.9~rc2-2.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24.2 (PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages iceweasel depends on:
ii  debianutils   2.17.3 Miscellaneous utilities specific t
ii  fontconfig2.5.0-2generic font configuration library
ii  libc6 2.7-4  GNU C Library: Shared libraries
ii  libgcc1   1:4.3.1-8  GCC support library
ii  libglib2.0-0  2.16.5-1   The GLib library of C routines
ii  libgtk2.0-0   2.12.11-3  The GTK+ graphical user interface 
ii  libnspr4-0d   4.7.1-3NetScape Portable Runtime Library
ii  libstdc++64.3.1-8The GNU Standard C++ Library v3
ii  procps1:3.2.7-3  /proc file system utilities
ii  psmisc22.3-1 Utilities that use the proc filesy
ii  xulrunner-1.9 1.9.0.1-1  XUL + XPCOM application runner

iceweasel recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
* Hubert Chathi ([EMAIL PROTECTED]) wrote:
> On Sat, 2 Aug 2008 18:32:22 +0200 Mike Hommey <[EMAIL PROTECTED]> wrote:
> 
> > On Sat, Aug 02, 2008 at 11:32:10AM -0400, Hubert Chathi wrote:
> > > Yes, I use uim.
> > 
> > Does it work better if you disable it ?
> 
> OK, I tried removing uim-gtk2.0, and upgrading uim* to the latest
> version in unstable, and it in both cases, it works properly.  So,
> since this bug won't be in lenny (with all packages updated), I'll
> leave it up to you to decide whether to leave this bug open.  It just
> seems strange that starting iceweasel with no ~/.mozilla directory
> makes it work, while starting iceweasel with a ~/.mozilla directory
> fails.

Sounds like it should be closed to me.

-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]



signature.asc
Description: Digital signature
--- End Message ---