Processed: severity of 367024 is wishlist

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.15
 severity 367024 wishlist
Bug#367024: Licences conflict: Ruby under pure GPL with OpenSSL Licence
Severity set to `wishlist' 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#368570: xdm : cannot start, looks for daemon in wrong directory

2006-05-23 Thread Erwan David
Package: xdm
Version: 1:1.0.1-6
Severity: grave
Justification: renders package unusable

After upgrade xdm does not start. /etc/init.d looks for xdm in
/usr/bin/X11/xdm, but there is no xdm in this directory, it is in
/usr/bin/xdm

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages xdm depends on:
ii  cpp   4:4.0.2-2  The GNU C preprocessor (cpp)
ii  debconf [debconf-2.0] 1.5.0  Debian configuration management sy
ii  libc6 2.3.6-7GNU C Library: Shared libraries
ii  libice6   6.9.0.dfsg.1-6 Inter-Client Exchange library
ii  libpam-modules0.79-3.1   Pluggable Authentication Modules f
ii  libpam-runtime0.79-3.1   Runtime support for the PAM librar
ii  libpam0g  0.79-3.1   Pluggable Authentication Modules l
ii  libselinux1   1.30-1 SELinux shared libraries
ii  libsm66.9.0.dfsg.1-6 X Window System Session Management
ii  libx11-6  6.9.0.dfsg.1-6 X Window System protocol client li
ii  libxau6   6.9.0.dfsg.1-6 X Authentication library
ii  libxaw8   6.9.0.dfsg.1-6 X Athena widget set library
ii  libxdmcp6 6.9.0.dfsg.1-6 X Display Manager Control Protocol
ii  libxext6  6.9.0.dfsg.1-6 X Window System miscellaneous exte
ii  libxinerama1  6.9.0.dfsg.1-6 X Window System multi-head display
ii  libxmu6   6.9.0.dfsg.1-6 X Window System miscellaneous util
ii  libxp66.9.0.dfsg.1-6 X Window System printing extension
ii  libxpm4   6.9.0.dfsg.1-6 X pixmap library
ii  libxt66.9.0.dfsg.1-6 X Toolkit Intrinsics
ii  xbase-clients 6.9.0.dfsg.1-6 miscellaneous X clients

xdm recommends no packages.

-- debconf information:
* shared/default-x-display-manager: xdm
  xdm/stop_running_server_with_children: false
  xdm/daemon_name: /usr/bin/X11/xdm


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



Bug#368572: tulip_2.0.4-1(amd64/unstable): error: cast from 'const GraphObserver*' to 'unsigned int' loses precision

2006-05-23 Thread Frederik Schüler
Package: tulip
Version: 2.0.4-1
Severity: serious

Hello,

There was an error while trying to autobuild your package:


  g++ -DHAVE_CONFIG_H -I. -I../../../../library/tulip/src -I../../.. 
 -I../../../../library/tulip/include -I../../../../thirdparty/gzstream 
 -I../../../.. -D_TULIP_LIB_DIR=\/usr/lib/\ -DNDEBUG -O3 -funroll-loops 
 -pipe -MT Bfs.lo -MD -MP -MF .deps/Bfs.Tpo -c 
 ../../../../library/tulip/src/Bfs.cpp  -fPIC -DPIC -o .libs/Bfs.o
 ../../../../library/tulip/include/tulip/ObservableGraph.h: In member function 
 'size_t std::lessGraphObserver*::operator()(const GraphObserver*, const 
 GraphObserver*) const':
 ../../../../library/tulip/include/tulip/ObservableGraph.h:34: error: cast 
 from 'const GraphObserver*' to 'unsigned int' loses precision
 ../../../../library/tulip/include/tulip/ObservableGraph.h:34: error: cast 
 from 'const GraphObserver*' to 'unsigned int' loses precision
 make[5]: *** [Bfs.lo] Error 1
 make[5]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD/library/tulip/src'
 make[4]: *** [all-recursive] Error 1
 make[4]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD/library/tulip'
 make[3]: *** [all-recursive] Error 1
 make[3]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD/library'
 make[2]: *** [all-recursive] Error 1
 make[2]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD'
 make[1]: *** [all] Error 2
 make[1]: Leaving directory `/build/buildd/tulip-2.0.4/BUILD'
 make: *** [/build/buildd/tulip-2.0.4/stamps/build] Error 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=amd64pkg=tulipver=2.0.4-1

Best regards
Frederik Schueler


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



Bug#368571: sigscheme_0.5.0-1(amd64/unstable): FTBFS: Missing build dependency

2006-05-23 Thread Frederik Schüler
Package: sigscheme
Version: 0.5.0-1
Severity: serious

Hello,

There was an error while trying to autobuild your package:

 ** Using build dependencies supplied by package:
 Build-Depends: debhelper (= 4.0.0)

apparently the package misses a build dependency on ruby:

 checking for ruby... no
 configure: error: please install ruby (http://www.ruby-lang.org/)
 make: *** [configure-stamp] Error 1

A full build log can be found at:
http://buildd.debian.org/build.php?arch=amd64pkg=sigschemever=0.5.0-1

Best regards
Frederik Schueler



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



Bug#347010: marked as done (libgd-ruby: FTBFS: build-depends on removed xlibs-dev)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 00:47:24 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#347010: fixed in libgd-ruby 0.7.4.1-3
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: libgd-ruby
Version: 0.7.4.1-2
Severity: serious

Hello,

  This is a serious bug filed against your package because it
  build-depends on xlibs-dev, which as announced in [1] a while ago, is
  no longer available in sid. This makes your package fail to build from
  source.

[1] http://lists.debian.org/debian-devel-announce/2005/11/msg00022.html

  To fix this bug, you need to update your build-dependencies and
  substitute xlibs-dev for the list of individual X development
  libraries that your package needs to be built. You can find detailed
  information about how to do that in the DependsXlibsDev wiki page [2].

[2] http://wiki.debian.org/DependsXlibsDev

  As indicated by the Release Team [3], the full transition from XFree86
  to Xorg is a release blocker for Etch, which means that Etch will not
  be released until this bug is fixed (or your package removed from
  testing). So, please, try to fix in a timely manner.

[3] http://lists.debian.org/debian-devel-announce/2005/10/msg4.html

  The number of affected packages by the xlibs-dev transition is huge,
  so if you feel like helping with patches or uploads, feel free to
  follow the instructions contained in the wiki page above. A list of
  affected packages can be found here [4].

[4] http://people.debian.org/~adeodato/release-usertag/transition-xlibs-dev

  Finally, if there's a strong reason for which your package should not
  be NMUed, please note so in this bug report. Prospective NMUers will
  read your reasoning, and will decide if it's strong enough to delay
  their upload.

  Thanks for your collaboration!

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org


---End Message---
---BeginMessage---
Source: libgd-ruby
Source-Version: 0.7.4.1-3

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

libgd-ruby1.8_0.7.4.1-3_i386.deb
  to pool/main/libg/libgd-ruby/libgd-ruby1.8_0.7.4.1-3_i386.deb
libgd-ruby_0.7.4.1-3.diff.gz
  to pool/main/libg/libgd-ruby/libgd-ruby_0.7.4.1-3.diff.gz
libgd-ruby_0.7.4.1-3.dsc
  to pool/main/libg/libgd-ruby/libgd-ruby_0.7.4.1-3.dsc



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

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

Debian distribution maintenance software
pp.
akira yamada [EMAIL PROTECTED] (supplier of updated libgd-ruby package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 23 May 2006 16:37:41 +0900
Source: libgd-ruby
Binary: libgd-ruby1.8
Architecture: source i386
Version: 0.7.4.1-3
Distribution: unstable
Urgency: low
Maintainer: akira yamada [EMAIL PROTECTED]
Changed-By: akira yamada [EMAIL PROTECTED]
Description: 
 libgd-ruby1.8 - Extension library to use GD graphics library from Ruby 1.8
Closes: 347010 367919
Changes: 
 libgd-ruby (0.7.4.1-3) unstable; urgency=low
 .
   * FTBFS: build-depends on removed xlibs-dev (Closes: #347010)
   * dropped ruby1.6 support. (Closes: #367919)
Files: 
 1f7e546309b254f10c02f27ca306acad 678 graphics optional libgd-ruby_0.7.4.1-3.dsc
 7c497cd2514d8ebac8cf65a3e6c02703 3308 graphics optional 
libgd-ruby_0.7.4.1-3.diff.gz
 4e259b84ee4408863e35deac9d9a1f45 50468 graphics optional 
libgd-ruby1.8_0.7.4.1-3_i386.deb

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

iD8DBQFEcrzHXzkxpuIT8aARAvQXAJ9vC0RoKkvLwfkh03vOkcqenRJLewCbBySr
NKZXKUFSIPXvOW1LgfxSkQU=
=kyB5
-END PGP SIGNATURE-

---End Message---


Bug#368360: marked as done (courier-authdaemon - fails to remove)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 01:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#368360: fixed in courier-authlib 0.58-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: courier-authdaemon
Version: 0.58-1.0
Severity: grave

| Removing courier-authdaemon ...
| Stopping Courier authentication services: /usr/sbin/authdaemond: line 18: 
/usr/sbin/courierlogger: No such file or directory
| /usr/sbin/authdaemond: line 18: exec: /usr/sbin/courierlogger: cannot 
execute: No such file or directory
| invoke-rc.d: initscript courier-authdaemon, action stop failed.
| dpkg: error processing courier-authdaemon (--purge):
|  subprocess pre-removal script returned error exit status 126
| Starting Courier authentication services: /usr/sbin/authdaemond: line 18: 
/usr/sbin/courierlogger: No such file or directory
| /usr/sbin/authdaemond: line 18: exec: /usr/sbin/courierlogger: cannot 
execute: No such file or directory
| invoke-rc.d: initscript courier-authdaemon, action start failed.
| dpkg: error while cleaning up:
|  subprocess post-installation script returned error exit status 126
| Errors were encountered while processing:
|  courier-authdaemon

Bastian

-- 
Intuition, however illogical, is recognized as a command prerogative.
-- Kirk, Obsession, stardate 3620.7

---End Message---
---BeginMessage---
Source: courier-authlib
Source-Version: 0.58-2

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

courier-authdaemon_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authdaemon_0.58-2_i386.deb
courier-authlib-dev_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-dev_0.58-2_i386.deb
courier-authlib-ldap_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-ldap_0.58-2_i386.deb
courier-authlib-mysql_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-mysql_0.58-2_i386.deb
courier-authlib-pipe_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-pipe_0.58-2_i386.deb
courier-authlib-postgresql_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-postgresql_0.58-2_i386.deb
courier-authlib-userdb_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-userdb_0.58-2_i386.deb
courier-authlib_0.58-2.diff.gz
  to pool/main/c/courier-authlib/courier-authlib_0.58-2.diff.gz
courier-authlib_0.58-2.dsc
  to pool/main/c/courier-authlib/courier-authlib_0.58-2.dsc
courier-authlib_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib_0.58-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.
Stefan Hornburg (Racke) [EMAIL PROTECTED] (supplier of updated 
courier-authlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 23 May 2006 09:43:15 +0200
Source: courier-authlib
Binary: courier-authlib-pipe courier-authlib-mysql courier-authlib-dev 
courier-authlib-ldap courier-authdaemon courier-authlib 
courier-authlib-postgresql courier-authlib-userdb
Architecture: source i386
Version: 0.58-2
Distribution: unstable
Urgency: low
Maintainer: Stefan Hornburg (Racke) [EMAIL PROTECTED]
Changed-By: Stefan Hornburg (Racke) [EMAIL PROTECTED]
Description: 
 courier-authdaemon - Courier authentication daemon
 courier-authlib - Courier authentication library
 courier-authlib-dev - Development libraries for the Courier authentication 
library
 courier-authlib-ldap - LDAP support for the Courier authentication library
 courier-authlib-mysql - MySQL support for the Courier authentication library
 courier-authlib-pipe - External authentication support for the Courier 
authentication li
 courier-authlib-postgresql - PostgreSQL support for the Courier authentication 
library
 courier-authlib-userdb - userdb support for the Courier authentication library
Closes: 368358 368360
Changes: 
 courier-authlib (0.58-2) unstable; urgency=low
 .
   * set ownership of /var/run/courier and /var/run/courier/authdaemon to
 daemon.daemon (Closes: #368358, #368360)
Files: 
 

Bug#368358: marked as done (courier-authdaemon - fails to install)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 01:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#368358: fixed in courier-authlib 0.58-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: courier-authdaemon
Version: 0.58-1.0
Severity: grave

| Setting up courier-authdaemon (0.58-1.0) ...
| Starting Courier authentication services: 
/var/run/courier/authdaemon/pid.lock: No such file or directory
| ll_daemon_start: Resource temporarily unavailable
| invoke-rc.d: initscript courier-authdaemon, action start failed.
| dpkg: error processing courier-authdaemon (--configure):
|  subprocess post-installation script returned error exit status 1
| Errors were encountered while processing:
|  courier-authdaemon

Bastian

-- 
You!  What PLANET is this!
-- McCoy, The City on the Edge of Forever, stardate 3134.0

---End Message---
---BeginMessage---
Source: courier-authlib
Source-Version: 0.58-2

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

courier-authdaemon_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authdaemon_0.58-2_i386.deb
courier-authlib-dev_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-dev_0.58-2_i386.deb
courier-authlib-ldap_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-ldap_0.58-2_i386.deb
courier-authlib-mysql_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-mysql_0.58-2_i386.deb
courier-authlib-pipe_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-pipe_0.58-2_i386.deb
courier-authlib-postgresql_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-postgresql_0.58-2_i386.deb
courier-authlib-userdb_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib-userdb_0.58-2_i386.deb
courier-authlib_0.58-2.diff.gz
  to pool/main/c/courier-authlib/courier-authlib_0.58-2.diff.gz
courier-authlib_0.58-2.dsc
  to pool/main/c/courier-authlib/courier-authlib_0.58-2.dsc
courier-authlib_0.58-2_i386.deb
  to pool/main/c/courier-authlib/courier-authlib_0.58-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.
Stefan Hornburg (Racke) [EMAIL PROTECTED] (supplier of updated 
courier-authlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 23 May 2006 09:43:15 +0200
Source: courier-authlib
Binary: courier-authlib-pipe courier-authlib-mysql courier-authlib-dev 
courier-authlib-ldap courier-authdaemon courier-authlib 
courier-authlib-postgresql courier-authlib-userdb
Architecture: source i386
Version: 0.58-2
Distribution: unstable
Urgency: low
Maintainer: Stefan Hornburg (Racke) [EMAIL PROTECTED]
Changed-By: Stefan Hornburg (Racke) [EMAIL PROTECTED]
Description: 
 courier-authdaemon - Courier authentication daemon
 courier-authlib - Courier authentication library
 courier-authlib-dev - Development libraries for the Courier authentication 
library
 courier-authlib-ldap - LDAP support for the Courier authentication library
 courier-authlib-mysql - MySQL support for the Courier authentication library
 courier-authlib-pipe - External authentication support for the Courier 
authentication li
 courier-authlib-postgresql - PostgreSQL support for the Courier authentication 
library
 courier-authlib-userdb - userdb support for the Courier authentication library
Closes: 368358 368360
Changes: 
 courier-authlib (0.58-2) unstable; urgency=low
 .
   * set ownership of /var/run/courier and /var/run/courier/authdaemon to
 daemon.daemon (Closes: #368358, #368360)
Files: 
 e25ddab5ca9a3d91a09a9227a3b0d71c 950 mail optional courier-authlib_0.58-2.dsc
 cc03f5467696507d29e0c89398476d93 34561 mail optional 
courier-authlib_0.58-2.diff.gz
 4c7c785a7792245105c3c17d4a7db67e 76504 mail optional 
courier-authlib_0.58-2_i386.deb
 158a1de9790c6ae924ffb76cbac1e060 6062 mail optional 
courier-authdaemon_0.58-2_i386.deb
 77508bf3018b76fe8cb6fae6d9d31ea0 94284 mail optional 
courier-authlib-dev_0.58-2_i386.deb
 3059a1486dd1e30a158ee194813a8158 33418 mail optional 

Processed: tagging 367495

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 tags 367495 + pending
Bug#367495: gfpoken: Buttons are missing
There were no tags set.
Tags added: pending


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#368576: r-noncran-lindsey_1.0.20041008-1.1(amd64/unstable): FTBFS: Error: Real constant overflows its kind

2006-05-23 Thread Frederik Schüler
Package: r-noncran-lindsey
Version: 1.0.20041008-1.1
Severity: serious

Hello,

There was an error while trying to autobuild your package:

 gcc -I/usr/share/R/include -I/usr/share/R/include -fpic  -g -O2 
 -std=gnu99 -c dist.c -o dist.o
 gfortran   -fpic  -g -O2 -c gettvc.f -o gettvc.o
  In file gettvc.f:55
 
 tvcov2(n,i)=-1e301  
  1
 Error: Real constant overflows its kind at (1)
  In file gettvc.f:79
 
recx=1e301   
 1
 Error: Real constant overflows its kind at (1)
  In file gettvc.f:84
 
reck=1e301   
 1
 Error: Real constant overflows its kind at (1)
  In file gettvc.f:86
 
 if((recx.ge.1e300).and.(reck.ge.1e300)) ldone=.true.
 1
 Error: Real constant overflows its kind at (1)
 make[1]: *** [gettvc.o] Error 1
 make[1]: Leaving directory 
 `/build/buildd/r-noncran-lindsey-1.0.20041008/build/rmutil/src'
 ERROR: compilation failed for package 'rmutil'
 ** Removing 
 '/build/buildd/r-noncran-lindsey-1.0.20041008/debian/r-noncran-lindsey/usr/lib/R/site-library/rmutil'
 make: *** [install] Error 1

A full build log can be found at:
http://buildd.debian.org/build.php?arch=amd64pkg=r-noncran-lindseyver=1.0.20041008-1.1

the same error is reproducible on i386, thus the severity.


Best regards
Frederik Schueler



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



Bug#368301: marked as done (proftpd binary set trapdoor rpath to /users/frankie)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 01:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#368301: fixed in proftpd 1.3.0-8
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: proftpd
Version: 1.3.0-7
Severity: grave
Tags: security

Hello Francesco,

proftpd include a trapdoor rpath to /users/frankie/...

%chrpath usr/sbin/proftpd
usr/sbin/proftpd: 
RPATH=/users/frankie/debian/mypkgs/proftpd/current/proftpd-1.3.0/debian/tmp/usr/sbin

This rpath allows a user with home directory /users/frankie/ to install
trojaned libraries and wait for proftpd to start.

Cheers,
-- 
Bill. [EMAIL PROTECTED]

Imagine a large red swirl here. 

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

---End Message---
---BeginMessage---
Source: proftpd
Source-Version: 1.3.0-8

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

proftpd-doc_1.3.0-8_all.deb
  to pool/main/p/proftpd/proftpd-doc_1.3.0-8_all.deb
proftpd-ldap_1.3.0-8_all.deb
  to pool/main/p/proftpd/proftpd-ldap_1.3.0-8_all.deb
proftpd-mysql_1.3.0-8_all.deb
  to pool/main/p/proftpd/proftpd-mysql_1.3.0-8_all.deb
proftpd-pgsql_1.3.0-8_all.deb
  to pool/main/p/proftpd/proftpd-pgsql_1.3.0-8_all.deb
proftpd_1.3.0-8.diff.gz
  to pool/main/p/proftpd/proftpd_1.3.0-8.diff.gz
proftpd_1.3.0-8.dsc
  to pool/main/p/proftpd/proftpd_1.3.0-8.dsc
proftpd_1.3.0-8_i386.deb
  to pool/main/p/proftpd/proftpd_1.3.0-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.
Francesco Paolo Lovergine [EMAIL PROTECTED] (supplier of updated proftpd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 22 May 2006 12:22:51 +0200
Source: proftpd
Binary: proftpd proftpd-mysql proftpd-pgsql proftpd-ldap proftpd-doc
Architecture: source all i386
Version: 1.3.0-8
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine [EMAIL PROTECTED]
Changed-By: Francesco Paolo Lovergine [EMAIL PROTECTED]
Description: 
 proftpd- Versatile, virtual-hosting FTP daemon
 proftpd-doc - Versatile, virtual-hosting FTP daemon (Documentation)
 proftpd-ldap - Versatile, virtual-hosting FTP daemon (dummy transitional 
package
 proftpd-mysql - Versatile, virtual-hosting FTP daemon (dummy transitional 
package
 proftpd-pgsql - Versatile, virtual-hosting FTP daemon (dummy transitional 
package
Closes: 368301
Changes: 
 proftpd (1.3.0-8) unstable; urgency=medium
 .
   * New patch for configure.in/configure (remove_rpath) to remove rpath adding
 at libtool installation time.
 (closes: #368301)
   * Updated patch ipv6_cidr_warn.dpatch to the latest version in CVS.
 See http://bugs.proftpd.org/show_bug.cgi?id=2785
Files: 
 91e93e5692a53d5b0437aecf3716751d 893 net optional proftpd_1.3.0-8.dsc
 1f270e9d9807321eb238e7e08ad5ec25 155913 net optional proftpd_1.3.0-8.diff.gz
 e0d2911f94db44c0a2f7362c07e8f2c7 622130 net optional proftpd_1.3.0-8_i386.deb
 6d1f8d28f3f1d4ff7fae094eb0e9bfed 480842 doc optional 
proftpd-doc_1.3.0-8_all.deb
 ecefcb1cca2336d08d5e64a730830d47 161182 net optional 
proftpd-mysql_1.3.0-8_all.deb
 eaeffbfe20c7f2d379fe8e7295f55b65 161184 net optional 
proftpd-pgsql_1.3.0-8_all.deb
 0a7cb39ff03fc3de63dba87e3093fadf 161178 net optional 
proftpd-ldap_1.3.0-8_all.deb

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

iD8DBQFEcsHmpFNRmenyx0cRAt/8AKCkGJN36fcbfcBY77HrGo2EYwJ+sQCfTXXC
S9ysju8gOHAm2Z/RNJeLf0g=
=XFC8
-END PGP SIGNATURE-

---End Message---


Processed: severity of 360992 is important

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 severity 360992 important
Bug#360992: exmap: FTBFS (ppc64): syntax error before numeric constant
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: Fixed in NMU of bluez-pin 0.30-2.1

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tag 363425 + fixed
Bug#363425: Crashes when used with --dbus
Tags were: patch
Tags added: fixed

 quit
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#368580: expect 5.43.0-3 dynamically linked but libexpect missing

2006-05-23 Thread Brian Keck
Package: expect
Version: 5.42.1-1.2
Severity: grave
Justification: renders package unusable


expect 5.43.0-3 is dynamically linked (unlike 5.43.0-2) but lacks
libexpect:

% ar xf /home/debian/pool/main/e/expect/expect_5.43.0-3_i386.deb
% tar xzf data.tgz
% ldd usr/bin/expect 
libexpect5.43.so = not found
...
% ls usr/lib
expect5.43

Brian Keck



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages expect depends on:
ii  libc6 2.3.6-7GNU C Library: Shared libraries
ii  tcl8.48.4.12-1   Tcl (the Tool Command Language) v8

expect recommends no packages.

-- no debconf information


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



Bug#368582: hardinfo - FTBFS: error: arch/this/alsa.h: No such file or directory

2006-05-23 Thread Bastian Blank
Package: hardinfo
Version: 0.4-1
Severity: serious

There was an error while trying to autobuild your package:

 Automatic build of hardinfo_0.4-1 on debian01 by sbuild/s390 85
[...]
 --- Module: computer.c (computer.so)
 gcc -fPIC -pipe -O3  -Wall -g -I/usr/include/gtk-2.0 
 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo 
 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  
   -I. -o computer.so -shared computer.c  -lgtk-x11-2.0 -lgdk-x11-2.0 
 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lfontconfig -lXext -lXrender 
 -lXinerama -lXi -lXrandr -lXcursor -lXfixes -lpango-1.0 -lcairo -lX11 
 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0   \

 computer.c:63:28: error: arch/this/alsa.h: No such file or directory
 computer.c:65:31: error: arch/this/loadavg.h: No such file or directory
 computer.c:66:30: error: arch/this/memory.h: No such file or directory
 computer.c:67:30: error: arch/this/uptime.h: No such file or directory
 computer.c:68:33: error: arch/this/processor.h: No such file or directory
 computer.c:69:26: error: arch/this/os.h: No such file or directory
 computer.c:70:34: error: arch/this/filesystem.h: No such file or directory
 computer.c:71:29: error: arch/this/samba.h: No such file or directory
 computer.c:72:31: error: arch/this/sensors.h: No such file or directory
 computer.c:73:27: error: arch/this/net.h: No such file or directory

Bastian



Processed: severity of 365494 is important

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 severity 365494 important
Bug#365494: lcdproc: Missing orig.tar.gz
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: Fixed in NMU of fvwm95 2.0.43ba-24.1

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tag 365285 + fixed
Bug#365285: fvwm95: please update for X11R7
Tags were: patch
Tags added: fixed

 quit
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#368583: eclipse: Does not work with sun-java5-bin package

2006-05-23 Thread Daniel Franganillo

Subject: eclipse: Does not work with sun-java5-bin package
Package: eclipse
Version: 3.1.2-2
Severity: grave
Justification: renders package unusable

Eclipse's search for a java runtime environment doesnt look in
/usr/lib/jvm/ for sun jre's installed via apt.

Workaround:
1 - Edit /etc/eclipse/java_home
2 - Add /usr/lib/jvm/java-1.5.0 for sun-jre5-bin

Thanks.

-- System Information:
Debian Release: testing/unstable
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
(ignored: LC_ALL set to [EMAIL PROTECTED])

Versions of packages eclipse depends on:
ii  eclipse-jdt   3.1.2-2Java Development Tools plug-ins fo
ii  eclipse-pde   3.1.2-2Plug-in Development Environment to
ii  eclipse-source3.1.2-2Eclipse source code plug-ins

eclipse recommends no packages.

-- no debconf information



Processed: Fixed in NMU of vtwm 5.4.7-2.1

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tag 365286 + fixed
Bug#365286: vtwm: please update for X11R7
Tags were: patch
Tags added: fixed

 quit
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#365533: CVE-2006-1896: Admin command execution

2006-05-23 Thread Thijs Kinkhorst
tags 365533 pending
thanks

On Thu, 2006-05-18 at 05:21 +0200, Moritz Muehlenhoff wrote:
  W.r.t. unstable, I will look into that very soon, we'll need to be
  upgrading to a new upstream aswell. I'll check whether that can be done
  in the short term, if not, I'll prepare a patched package.
 
 Ok, thanks.

Thanks for fixing stable. I've also prepared a fix for sid now. The
difference with the previous version in sid is the same patch as for
sarge, plus I've added a debconf translation.

Problem is that Jeroen announced that he's on a trip through Mexico now,
so I'm left without someone to upload. Maybe the (testing) security team
or any other DD interested in getting this bug fixed, can take a look
and upload?

Please find the updated packages here:
http://www.a-eskwadraat.nl/~kink/phpbb/

Packages have been tested and work here.


thanks,
Thijs


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


Processed: Re: Bug#365533: CVE-2006-1896: Admin command execution

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tags 365533 pending
Bug#365533: CVE-2006-1896: Admin command execution
Tags were: patch security
Tags added: pending

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#368583: eclipse: Does not work with sun-java5-bin package

2006-05-23 Thread Michael Koch
severity 368583 wishlist
thanks

On Tue, May 23, 2006 at 12:14:05PM +0200, Daniel Franganillo wrote:
 Subject: eclipse: Does not work with sun-java5-bin package
 Package: eclipse
 Version: 3.1.2-2
 Severity: grave
 Justification: renders package unusable
 
 Eclipse's search for a java runtime environment doesnt look in
 /usr/lib/jvm/ for sun jre's installed via apt.
 
 Workaround:
 1 - Edit /etc/eclipse/java_home
 2 - Add /usr/lib/jvm/java-1.5.0 for sun-jre5-bin

I would call this renders package unusable. I downgrade this to a
wishlist bugs as supporting non-free software is not our prime goal.
Eclipse works fine with other runtimes. Even with other differently
packaged versions of SUNs JDK.


Cheers,
Michael
-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/


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



Processed: Re: Bug#368583: eclipse: Does not work with sun-java5-bin package

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 368583 wishlist
Bug#368583: eclipse: Does not work with sun-java5-bin package
Severity set to `wishlist' 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#368587: invoke-rc.d: initscript nscd, action stop failed.

2006-05-23 Thread Francesco Paolo Lovergine
Package: nscd
Version: 2.3.6-7
Severity: serious


An invoke-rc.d failure prevents package upgrading. 
You should manage that case in prerm in order to avoid
such a problem, or return 0 in case of failure in the
init script, as well. Most servers in debian do the last, AFAIK.
Feel free to close this report if already properly managed in -9 scripts.


klecker:~$ ps -fe|grep nscd
frankie  14797  4397  0 12:27 pts/17   00:00:00 grep nscd
klecker:~$ sudo /etc/init.d/nscd start
Starting Name Service Cache Daemon: nscd.
klecker:~$ ps -fe|grep nscd
root 14804 1  0 12:27 ?00:00:00 /usr/sbin/nscd
frankie  14812  4397  0 12:27 pts/17   00:00:00 grep nscd
klecker:~$ sudo apt-get -u dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
The following packages will be upgraded:
  nscd
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
30 not fully installed or removed.
Need to get 0B/136kB of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue [Y/n]?
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Reading changelogs... Done
(Reading database ... 164331 files and directories currently installed.)
Preparing to replace nscd 2.3.6-7 (using .../archives/nscd_2.3.6-9_i386.deb) ...
Stopping Name Service Cache Daemon: nscd.
invoke-rc.d: initscript nscd, action stop failed.
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
Stopping Name Service Cache Daemon: nscd.
invoke-rc.d: initscript nscd, action stop failed.
dpkg: error processing /var/cache/apt/archives/nscd_2.3.6-9_i386.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Starting Name Service Cache Daemon: nscd.
Errors were encountered while processing:
 /var/cache/apt/archives/nscd_2.3.6-9_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

Versions of packages nscd depends on:
ii  libc6 2.3.6-9GNU C Library: Shared libraries

nscd recommends no packages.

-- no debconf information


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



Processed: 365533 fixed in sarge

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 close 365533 2.0.13+1-6sarge3
Bug#365533: CVE-2006-1896: Admin command execution
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.0.13+1-6sarge3, send any further explanations 
to Stefan Fritsch [EMAIL PROTECTED]
Removed pending tag.

 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#348778: #348778: ext2prepare corrupts the file system

2006-05-23 Thread Petter Reinholdtsen

tags 348778 + patch
thanks

I got this answer on the ext2resize-devel mailing list:

[Andreas Dilger]
 That's because ext2prepare was never updated to support the new
 ext3 resize inode format.  There was actually a patch posted on
 ext2-devel which may fix this from Takashi Sato, but I haven't had
 time to look at it yet:
 
 [Ext2-devel] [RFC][17/21]ext2resize fix resize_inode format

I found the diff on
URL:http://www.ussg.iu.edu/hypermail/linux/kernel/0604.1/1090.html,
and manually applied it to my copy of the source as the HTML version
didn't apply using patch.

Can you test it and let me know if it solve the problem for you?  I've
tested it and e2fsck no longer complains when I run it on a fresh file
system.

#! /bin/sh /usr/share/dpatch/dpatch-run
## 05_ext3newformat.dpatch
##
## DP: Update to use the new resize-inode format.  Patch from Takashi
## DP: Sato [EMAIL PROTECTED] found on
## DP: URL:http://www.ussg.iu.edu/hypermail/linux/kernel/0604.1/1090.html
## DP: and manually applied.

Summary of this patch:
  [17/21] fix the bug related to the option resize_inode
  - A format of resize-inode in ext2prepare is different from
the one in mke2fs, so ext2prepare fails.  Then I adapt
ext2prepare's to mke2fs's.

--- ext2resize-1.1.19.orig/src/ext2.c
+++ ext2resize-1.1.19/src/ext2.c
@@ -286,6 +286,7 @@
 	}
 }
 
+/* Remind: prototype returns int, but it may return blk_t */
 int ext2_block_iterate(struct ext2_fs *fs, struct ext2_inode *inode,
 		   blk_t block, int action)
 {
@@ -295,6 +296,9 @@
 	int			 count = 0;
 	int			 i;
 	int			 i512perblock = 1  (fs-logsize - 9);
+	unsigned		 long long apb;
+
+	apb = fs-u32perblock;
 
 	if (block == 0 || inode-i_mode == 0)
 		return -1;
@@ -313,114 +317,66 @@
 		}
 	}
 
-	/* Direct blocks for first 12 blocks */
-	for (i = 0, curblock = 0; i  EXT2_NDIR_BLOCKS; i++, curblock++) {
-		if (action == EXT2_ACTION_ADD  !inode-i_block[i]) {
-			size_t new_size = (curblock + 1) * fs-blocksize;
-
-			if (fs-flags  FL_DEBUG)
-printf(add %d as direct block\n, curblock);
-			inode-i_block[i] = block;
-			/* i_blocks is in 512 byte blocks */
-			inode-i_blocks += i512perblock;
-			if (new_size  inode-i_size)
-inode-i_size = new_size;
-
-			inode-i_mtime = time(NULL);
-			ext2_set_block_state(fs, block, 1,
-	 !(fs-flags  FL_ONLINE));
-			return curblock;
-		}
-		if (inode-i_block[i] == block) {
-			if (action == EXT2_ACTION_DELETE) {
-if (fs-flags  FL_DEBUG)
-	printf(del %d as direct block\n,
-	  curblock);
-inode-i_block[i] = 0;
-inode-i_blocks -= i512perblock;
-inode-i_mtime = time(NULL);
-if (!(fs-flags  FL_ONLINE))
-	ext2_set_block_state(fs, block, 0, 1);
-			}
-			return i;
-		}
-		if (inode-i_block[i])
-			count += i512perblock;
-	}
-
-	count += inode-i_block[EXT2_IND_BLOCK] ? i512perblock : 0;
-	count += inode-i_block[EXT2_DIND_BLOCK] ? i512perblock : 0;
-	count += inode-i_block[EXT2_TIND_BLOCK] ? i512perblock : 0;
-
-	if (!inode-i_block[EXT2_IND_BLOCK] ||
-	(count = inode-i_blocks  action != EXT2_ACTION_ADD))
+	if(!inode-i_block[EXT2_DIND_BLOCK]  action != EXT2_ACTION_ADD)
 		return -1;
 
-	bh = ext2_bread(fs, inode-i_block[EXT2_IND_BLOCK]);
-	udata = (__u32 *)bh-data;
+	if (!inode-i_block[EXT2_DIND_BLOCK]) {
+		unsigned long long	 inode_size;
+		blk_t			 dindblk;
 
-	/* Indirect blocks for next 256/512/1024 blocks (for 1k/2k/4k blocks) */
-	for (i = 0; i  fs-u32perblock; i++, curblock++) {
-		if (action == EXT2_ACTION_ADD  !udata[i]) {
-			size_t new_size = (curblock + 1) * fs-blocksize;
-
-			if (fs-flags  FL_DEBUG)
-printf(add %d to ind block %d\n, curblock,
-   inode-i_block[EXT2_IND_BLOCK]);
-			bh-dirty = 1;
-			udata[i] = block;
-			inode-i_blocks += i512perblock;
-			if (new_size  inode-i_size)
-inode-i_size = new_size;
-			inode-i_mtime = time(NULL);
-			ext2_set_block_state(fs, block, 1,
-	 !(fs-flags  FL_ONLINE));
-			ext2_brelse(bh, 0);
-			return curblock;
-		}
-		if (udata[i] == block) {
-			if (action == EXT2_ACTION_DELETE) {
-if (fs-flags  FL_DEBUG)
-	printf(del %d from ind block %d\n,
-	  curblock,
-	  inode-i_block[EXT2_IND_BLOCK]);
-bh-dirty = 1;
-udata[i] = 0;
-inode-i_blocks -= i512perblock;
-inode-i_mtime = time(NULL);
-if (!(fs-flags  FL_ONLINE))
-	ext2_set_block_state(fs, block, 0, 1);
-			}
-			ext2_brelse(bh, 0);
-			return curblock;
-		}
-		if (udata[i]) {
-			count += i512perblock;
-			if (count = inode-i_blocks 
-			action != EXT2_ACTION_ADD)
-return -1;
-		}
+		dindblk = ext2_find_free_block(fs);
+		if(!dindblk)
+			return -1;
+		ext2_set_block_state(fs, dindblk, 1, 1);
+		inode_size = apb*apb + apb + EXT2_NDIR_BLOCKS;
+		inode_size *= fs-blocksize;
+		inode-i_size = inode_size  0x;
+		inode-i_size_high = (inode_size  32)  0x;
+		if(inode-i_size_high) {
+			fs-sb.s_feature_ro_compat |=
+			  EXT2_FEATURE_RO_COMPAT_LARGE_FILE;
+		}
+		inode-i_mtime = 

Processed: Re: #348778: ext2prepare corrupts the file system

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tags 348778 + patch
Bug#348778: ext2prepare corrupts the file system
There were no tags set.
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#368451: Bug#368327: udev won't install, no error message

2006-05-23 Thread Marco d'Itri
I uploaded a new package to http://www.bofh.it/~md/debian/, please check
if it works for you.

BTW, this bug is a race between postinst and udevd so it may not always
manifest even on the same system.

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Processed: pending tag removed by closing for sarge

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tags 365533 pending
Bug#365533: CVE-2006-1896: Admin command execution
Tags were: patch security
Tags added: pending

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: Re: expect 5.43.0-3 dynamically linked but libexpect missing

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tags 368580 fixed
Bug#368580: expect 5.43.0-3 dynamically linked but libexpect missing
There were no tags set.
Tags added: fixed

 merge 368580 368364
Bug#368364: atlas3 - FTBFS: error while loading shared libraries: 
libexpect5.43.so
Bug#368580: expect 5.43.0-3 dynamically linked but libexpect missing
Bug#367618: libexpect5.43.so: cannot open shared object file: No such file or 
directory
Merged 367618 368364 368580.

 quit
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#368580: expect 5.43.0-3 dynamically linked but libexpect missing

2006-05-23 Thread allomber
tags 368580 fixed
merge 368580 368364
quit

On Tue, May 23, 2006 at 07:23:48PM +1000, Brian Keck wrote:
 expect 5.43.0-3 is dynamically linked (unlike 5.43.0-2) but lacks
 libexpect:
 
 % ar xf /home/debian/pool/main/e/expect/expect_5.43.0-3_i386.deb
 % tar xzf data.tgz
 % ldd usr/bin/expect 
 libexpect5.43.so = not found
 ...
 % ls usr/lib
 expect5.43

Hello Brian,

This bug is a duplicate of 368364 which was fixed in expect version
expect_5.43.0-3.1.

Thanks for your bug report,
-- 
Bill. [EMAIL PROTECTED]

Imagine a large red swirl here. 


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



Processed: Re: libgnomeprint2.2-0: GNOME programs crash on print dialog

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 344684 libgnomecups1.0-1
Bug#344684: libgnomeprint2.2-0: GNOME programs crash on print dialog
Bug reassigned from package `libgnomeprint2.2-0' to `libgnomecups1.0-1'.

 severity 344684 serious
Bug#344684: libgnomeprint2.2-0: GNOME programs crash on print dialog
Severity set to `serious' from `normal'

 retitle 344684 insufficient shlibs for libgnomecups1.0-1 since 0.2.0
Bug#344684: libgnomeprint2.2-0: GNOME programs crash on print dialog
Changed Bug title.

 stop
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 344684

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 tags 344684 + pending
Bug#344684: insufficient shlibs for libgnomecups1.0-1 since 0.2.0
There were no tags set.
Tags added: pending


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#368451: Bug#368327: udev won't install, no error message

2006-05-23 Thread Frederik Eaton
Here. It seems to leak directories in /tmp/ still (they are not empty
because they contain a subdirectory called .udev). I don't know what
the syslogd problem is, I get it when trying to install sysklogd as
well. Also, the INTERFACE_NEW=eth1 thing is confusing, I have an eth1
interface but it is not up. The install doesn't fail, which is good,
but as I said when I installed the stable version and then removed it,
after that the unstable version began installing successfully as well,
so I think whatever caused my problem is gone. Since you said it was a
deadlock thing, I also tried doing the installation at different CPU
speeds, still no failure... Also, I made sure that udevd is running. 
Hope this helps.

# dpkg --purge udev
(Reading database ... 38940 files and directories currently installed.)
Removing udev ...

**
* Please reboot your system as soon as possible!
* After removing udev the system may not be fully functional.
**

Purging configuration files for udev ...
dpkg - warning: while removing udev, directory `/etc/udev/rules.d' not empty so 
not removed.
dpkg - warning: while removing udev, directory `/etc/udev' not empty so not 
removed.
# dpkg -i udev_0.092-2_i386.deb
Selecting previously deselected package udev.
(Reading database ... 38826 files and directories currently installed.)
Unpacking udev (from udev_0.092-2_i386.deb) ...

**
* Please purge the hotplug package!
* (/etc/init.d/hotplug has been found on this system)
**

Setting up udev (0.092-2) ...
INTERFACE_NEW=eth1
Populating the new /dev filesystem temporarily mounted on /tmp/udev.rPMRhq/...
rmdir: /tmp/udev.rPMRhq: Directory not empty
WARNING: /tmp/udev.rPMRhq is not empty!
/tmp/udev.rPMRhq:
total 0
Restarting system log daemon.../sbin/syslogd: invalid option -- u
usage: syslogd [-drvh] [-l hostlist] [-m markinterval] [-n] [-p path]
 [-s domainlist] [-f conffile]
 failed!


On Tue, May 23, 2006 at 01:34:36PM +0200, Marco d'Itri wrote:
 I uploaded a new package to http://www.bofh.it/~md/debian/, please check
 if it works for you.
 
 BTW, this bug is a race between postinst and udevd so it may not always
 manifest even on the same system.
 
 -- 
 ciao,
 Marco



-- 
http://ofb.net/~frederik/


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



Bug#368104: marked as done (hplip: Printing and Scanning does not work after upgrade of)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 10:11:42 -0300
with message-id [EMAIL PROTECTED]
and subject line Bug#368104: hplip: Printing and Scanning does not work after 
upgrade of [solved]
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: hplip
Version: 0.9.10-1
Severity: grave
Justification: renders package unusable

*** Please type your report below this line ***

With high probability this is the wrong package.

I have an HP Photosmart 2610 connected per network.

After an apt-get upgrade yesterday (May 18th, 2006) I cannot print and
scan anymore. Since I do not know all packages I have upgraded, here is
a list, which I know were upgrade:

apt-utils
passwd
gnome-utils
libgstreamer0.10-0
tex-common
udev
vim-common

Here are some error messages I get:

%%

hp-toolbox

HP Linux Imaging and Printing System (ver. 0.9.10)
HP Device Manager ver. 6.2

Copyright (c) 2003-6 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

 [ERROR]: Unable to connect to HPLIP I/O. Check and make sure HPLIP is
running.
 [ERROR]: Unable to create client object.

%%
xsane 
[1]   Datenübergabe unterbrochen (broken pipe) xsane
{translation: data transfer interrupted}

%%

sudo /etc/init.d/hplip restart
Stopping HP Linux Printing and Imaging System: hpiod hpssd.
Starting HP Linux Printing and Imaging System: hpiod hpssd failed!

%%

Printing a testpage from localhost:631, it shows the job, but nothing
happens.

Do you have a clue, which package could cause this.

I also remember that gcc was upgrade to version 4.1. But printing worked
after this.

If you need more information, let me know.

Thanks in advance.
Paul Menzel



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

Versions of packages hplip depends on:
ii  adduser   3.87   Add and remove users and
groups
ii  coreutils 5.94-1 The GNU core utilities
ii  cupsys1.1.23-15  Common UNIX Printing
System(tm) -
ii  hplip-data0.9.10-1   HP Linux Printing and
Imaging - da
ii  libc6 2.3.6-7GNU C Library: Shared
libraries
ii  libcupsys21.1.23-15  Common UNIX Printing
System(tm) -
ii  libgcc1   1:4.1.0-4  GCC support library
ii  libsnmp9  5.2.2-3NET SNMP (Simple Network
Managemen
ii  libssl0.9.8   0.9.8b-2   SSL shared libraries
ii  libstdc++64.1.0-4The GNU Standard C++
Library v3
ii  libusb-0.1-4  2:0.1.12-2 userspace USB programming
library
ii  lsb-base  3.1-5  Linux Standard Base 3.1
init scrip
ii  python2.3.5-5An interactive high-level
object-o
ii  python-qt33.15-4 Qt3 bindings for Python
(default v

Versions of packages hplip recommends:
ii  cupsys-client 1.1.23-15  Common UNIX Printing
System(tm) -
ii  hpijs 2.1.9+0.9.10-1 HP Linux Printing and
Imaging - gs
pn  python-reportlab  none (no description available)

-- no debconf information


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
---End Message---
---BeginMessage---
On Tue, 23 May 2006, Paul Menzel wrote:
 Doing a df, I saw that the /var/ partition was totally full. After
 apt-get autoclean and reboot everything works. It looks like the upgrade
 some days took the last bits of that partition ;( Now I also know, why
 there were shown always the same available upgrades the last two days by
 apt.
 
 I am so sorry. Please close this stupid bug-report.

It is not stupid, and now I know to ask about a df when weird things like
that start happening, so no harm done...

I am closing the bug, then.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh
---End 

Bug#344684: marked as done (insufficient shlibs for libgnomecups1.0-1 since 0.2.0)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 05:17:12 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#344684: fixed in libgnomecups 0.2.2-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: libgnomeprint2.2-0
Version: 2.10.3-3
Severity: normal

This problem seems to occur in any application using, I assume, the
GNOME print dialog. I click on print, and, when the print dialog should
appear, the entire application crashes/closes. If run from the command
line, then there is an error message:

symbol lookup error:
/usr/lib/libgnomeprint/2.10.3/modules/libgnomeprintcups.so: undefined
symbol: gnome_cups_printer_get_ppd_async

This has happened in gedit, abiword, evolution and gnumeric - presumably
any package that uses the GNOME print dialog. I have sent this report to
libgnomeprint due to the error message - apologies if this is the wrong
package!

Michael Williamson

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.12-1-k7
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages libgnomeprint2.2-0 depends on:
ii  libart-2.0-2  2.3.17-1   Library of functions for 2D graphi
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libcupsys21.1.23-14  Common UNIX Printing System(tm) - 
ii  libfontconfig12.3.1-2generic font configuration library
ii  libfreetype6  2.1.7-2.4  FreeType 2 font engine, shared lib
ii  libglib2.0-0  2.8.0-1The GLib library of C routines
ii  libgnomecups1.0-1 0.1.14-1   GNOME library for CUPS interaction
ii  libgnomeprint2.2-data 2.10.3-3   The GNOME 2.2 print architecture -
ii  libpango1.0-0 1.8.2-1Layout and rendering of internatio
ii  libpopt0  1.7-5  lib for parsing cmdline parameters
ii  libxml2   2.6.22-1   GNOME XML library
ii  zlib1g1:1.2.3-8  compression library - runtime

-- no debconf information


---End Message---
---BeginMessage---
Source: libgnomecups
Source-Version: 0.2.2-2

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

libgnomecups1.0-1_0.2.2-2_i386.deb
  to pool/main/libg/libgnomecups/libgnomecups1.0-1_0.2.2-2_i386.deb
libgnomecups1.0-dev_0.2.2-2_i386.deb
  to pool/main/libg/libgnomecups/libgnomecups1.0-dev_0.2.2-2_i386.deb
libgnomecups_0.2.2-2.diff.gz
  to pool/main/libg/libgnomecups/libgnomecups_0.2.2-2.diff.gz
libgnomecups_0.2.2-2.dsc
  to pool/main/libg/libgnomecups/libgnomecups_0.2.2-2.dsc



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

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

Debian distribution maintenance software
pp.
Loic Minier [EMAIL PROTECTED] (supplier of updated libgnomecups package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 23 May 2006 13:52:02 +0200
Source: libgnomecups
Binary: libgnomecups1.0-1 libgnomecups1.0-dev
Architecture: source i386
Version: 0.2.2-2
Distribution: unstable
Urgency: low
Maintainer: Ross Burton [EMAIL PROTECTED]
Changed-By: Loic Minier [EMAIL PROTECTED]
Description: 
 libgnomecups1.0-1 - GNOME library for CUPS interaction
 libgnomecups1.0-dev - GNOME library for CUPS interaction (headers)
Closes: 344684
Changes: 
 libgnomecups (0.2.2-2) unstable; urgency=low
 .
   * Set shlibs to = 0.2.0 which saw the last API additions. (Closes: #344684)
 [debian/rules]
   * Bump up Standards-Version to 3.7.2.
 [debian/control, debian/control.in]
Files: 
 7f8a25684b56d21aab3d96218aea325c 1514 - optional libgnomecups_0.2.2-2.dsc
 d1e11bbfd6f9ad5d300fa33315df89e2 3800 - optional libgnomecups_0.2.2-2.diff.gz
 4317880ede2ce659cdee6252481348b9 65638 libs optional 
libgnomecups1.0-1_0.2.2-2_i386.deb
 8030160998ae407a0103d6143414f281 43006 libdevel optional 
libgnomecups1.0-dev_0.2.2-2_i386.deb

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

iD8DBQFEcvkq4VUX8isJIMARAs3tAJ9ib/F4v1YPQ/zZPb7NJfIgooSLqACfRTep

Bug#358493: tagcoll FTBFS: testsuite failures.

2006-05-23 Thread Falk Hueffner
Hi,

I don't think depending on gcc 4.1 without really understanding the
issue is a good idea. There is a good chance that the bug is not
really fixed, but only hidden by circumstances. So it would really be
the best way to go to extract a minimal test case, see whether it's
gcc's or tagcoll's fault, and then make sure it is really fixed.

-- 
Falk


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



Bug#368571: marked as done (sigscheme_0.5.0-1(amd64/unstable): FTBFS: Missing build dependency)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 06:17:06 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#368571: fixed in sigscheme 0.5.0-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: sigscheme
Version: 0.5.0-1
Severity: serious

Hello,

There was an error while trying to autobuild your package:

 ** Using build dependencies supplied by package:
 Build-Depends: debhelper (= 4.0.0)

apparently the package misses a build dependency on ruby:

 checking for ruby... no
 configure: error: please install ruby (http://www.ruby-lang.org/)
 make: *** [configure-stamp] Error 1

A full build log can be found at:
http://buildd.debian.org/build.php?arch=amd64pkg=sigschemever=0.5.0-1

Best regards
Frederik Schueler


---End Message---
---BeginMessage---
Source: sigscheme
Source-Version: 0.5.0-2

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

sigscheme_0.5.0-2.diff.gz
  to pool/main/s/sigscheme/sigscheme_0.5.0-2.diff.gz
sigscheme_0.5.0-2.dsc
  to pool/main/s/sigscheme/sigscheme_0.5.0-2.dsc
sigscheme_0.5.0-2_i386.deb
  to pool/main/s/sigscheme/sigscheme_0.5.0-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.
NIIBE Yutaka [EMAIL PROTECTED] (supplier of updated sigscheme package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 23 May 2006 21:46:41 +0900
Source: sigscheme
Binary: sigscheme
Architecture: source i386
Version: 0.5.0-2
Distribution: unstable
Urgency: low
Maintainer: NIIBE Yutaka [EMAIL PROTECTED]
Changed-By: NIIBE Yutaka [EMAIL PROTECTED]
Description: 
 sigscheme  - A Scheme Interpreter
Closes: 368571
Changes: 
 sigscheme (0.5.0-2) unstable; urgency=low
 .
   * debian/control (Build-Depends): Added ruby.
 Thanks to Frederik Schueler.  Closes: #368571
   * debian/rules (clean): invoke 'distclean' instead of 'clean'.
Files: 
 05d32d46876f243c7479f1d97d90693b 572 interpreters optional 
sigscheme_0.5.0-2.dsc
 055b904afccb49c64dd55b2c86e3929e 3291 interpreters optional 
sigscheme_0.5.0-2.diff.gz
 5e12ec020ced77718dd26f7ee1051f52 145752 interpreters optional 
sigscheme_0.5.0-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEcwjzBB45r3HV9DoRArlwAJ9Iyi6aE7zKVyMT4qpQPZYWi7dicwCeOYsZ
QsJy2Em63xkif1rZ/5esA1w=
=U3Yv
-END PGP SIGNATURE-

---End Message---


Bug#368556: Unable to reproduce

2006-05-23 Thread Filipus Klutiero

Hi,
I'm unable to reproduce this on a i386 Etch. The versions of kooka and 
its direct dependencies are identical to yours, except for libc6 
2.3.6-7, which unlikely explains the difference.


Could you help doing a preliminary triaging to see if this needs 
immediate investigation? Does this crash reproduce for all users on the 
affected system? If so, on how many machines did you see it reproduce? 
If it didn't reproduce on several machines, what makes you think that 
the package is unusable?


Note that a backtrace is always welcome along with a crash report.


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



Bug#368506: x2vnc - FTBFS: cannot overwrite directory

2006-05-23 Thread Ola Lundqvist
Hi

Thanks, I'll look at it asap.

// Ola

On Mon, May 22, 2006 at 08:37:57PM +0200, Bastian Blank wrote:
 Package: x2vnc
 Version: 1.7.1-1
 Severity: serious
 
 There was an error while trying to autobuild your package:
 
  Automatic build of x2vnc_1.7.1-1 on debian-31 by sbuild/s390 85
 [...]
  ** Using build dependencies supplied by package:
  Build-Depends: debhelper (= 4.0.0), libvncauth-dev, libxaw7-dev, xutils, 
  libx11-dev, libxinerama-dev, libxss-dev, x-dev
  make[1]: Leaving directory `/build/buildd/x2vnc-1.7.1'
  mv debian/x2vnc/usr/X11R6/bin debian/x2vnc/usr
  mv: cannot overwrite directory `debian/x2vnc/usr/bin'
  make: *** [install] Error 1
  **
  Build finished at 20060522-1421
  FAILED [dpkg-buildpackage died]
 
 

-- 
 - Ola Lundqvist ---
/  [EMAIL PROTECTED] Annebergsslingan 37  \
|  [EMAIL PROTECTED] 654 65 KARLSTAD  |
|  +46 (0)54-10 14 30  +46 (0)70-332 1551   |
|  http://www.opal.dhs.org UIN/icq: 4912500 |
\  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#368633: partman: LVM automatic partitioning not undoable

2006-05-23 Thread Eric Monson
Package: partman
Severity: critical
Justification: causes serious data loss

I burned a D-I image for a friend (the latest weekly Debian CD as of Mar
12 15:12) and chose to play with it a bit to see if it was clearly
broken in some obvious way or likely okay for out purposes.

Once I had verified enough that I thought the build was fine (and It did
work for the install), I decided to try out the LVM option in the
guided partitioning, since I had never done so before and I wanted to
see what how it would arrange the partitions.  The guided partitioning
page clearly states that you will have a chance to review and undo the
guided partitioning, and is correct for regular partitions, but LVM
occurs immeditely, it seems, and even gpart was unable to restore my
data.  I was able to salvage the python programs I had been working on,
but nothing else.

Since there is almost certainly a reason LVM gets applied immeditely,
most likely that cannot be changed, but I am of the opinion that the
diolog where you can select it should clearly state that the operation
cannot be undone and may well kill working installations.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-eriix
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


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



Bug#368229: marked as done (anjuta: Projects cannot be opened, created or imported, plugin cannot be activated.)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 09:17:08 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#368229: fixed in gnome-build 0.1.3-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: anjuta
Version: 2.0.2-2
Severity: grave
Justification: renders package unusable

Existing Anjuta project files created with Anjuta1 are unusable. The import 
wizard complains that the wrong directory is in use or that Gnome Devel 
Framework does not exist. This is down to a complete inability to enable the 
automake / Project Import plugins - presumablu because of build options in the 
Debian package.

Anjuta is useless without being able to open projects. It cannot even USE a 
project Anjuta2 creates as new - the Project menu is disabled.

Anjuta2 should not have replaced anjuta1 in this state. 

I cannot create a new project for my existing code, I cannot open the existing 
Anjuta project file in my source trees, I cannot import the existing sources 
into a Anjuta2 project. This stinks.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-amd64-k8
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages anjuta depends on:
ii  anjuta-common  2.0.2-2   A GNOME development IDE, for C/C++
ii  libart-2.0-2   2.3.17-1  Library of functions for 2D graphi
ii  libatk1.0-01.11.4-2  The ATK accessibility toolkit
ii  libbonobo2-0   2.14.0-1  Bonobo CORBA interfaces library
ii  libbonoboui2-0 2.14.0-2  The Bonobo UI library
ii  libc6  2.3.6-7   GNU C Library: Shared libraries
ii  libcairo2  1.0.4-2   The Cairo 2D vector graphics libra
ii  libdevhelp-1-0 0.11-4Library providing documentation br
ii  libfontconfig1 2.3.2-5.1 generic font configuration library
ii  libfreetype6   2.2.1-1   FreeType 2 font engine, shared lib
ii  libgbf-1-0 0.1.3-1   GNOME Development Framework - runt
ii  libgcc11:4.1.0-4 GCC support library
ii  libgconf2-42.14.0-1  GNOME configuration database syste
ii  libgdl-1-0 0.6.1-1   GNOME DevTool libraries - developm
ii  libglade2-01:2.5.1-2+b1  library to load .glade files at ru
ii  libglib2.0-0   2.10.2-2  The GLib library of C routines
ii  libgnome-keyring0  0.4.9-1   GNOME keyring services library
ii  libgnome2-02.14.1-2  The GNOME 2 library - runtime file
ii  libgnomecanvas2-0  2.14.0-2  A powerful object-oriented display
ii  libgnomeprint2.2-0 2.12.1-3  The GNOME 2.2 print architecture -
ii  libgnomeprintui2.2-0   2.12.1-3  GNOME 2.2 print architecture User 
ii  libgnomeui-0   2.14.1-1  The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0 2.14.1-2  GNOME virtual file-system (runtime
ii  libgtk2.0-02.8.17-2  The GTK+ graphical user interface 
ii  libice61:1.0.0-3 X11 Inter-Client Exchange library
ii  libncurses55.5-2 Shared libraries for terminal hand
ii  liborbit2  1:2.14.0-1libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0  1.12.1-3  Layout and rendering of internatio
ii  libpcre3   6.4-2 Perl 5 Compatible Regular Expressi
ii  libpng12-0 1.2.8rel-5.1  PNG library - runtime
ii  libpopt0   1.7-5 lib for parsing cmdline parameters
ii  libsm6 1:1.0.0-4 X11 Session Management library
ii  libstdc++6 4.1.0-4   The GNU Standard C++ Library v3
ii  libvte41:0.12.1-1Terminal emulator widget for GTK+ 
ii  libx11-6   2:1.0.0-6 X11 client-side library
ii  libxcursor11.1.5.2-5 X cursor management library
ii  libxext6   1:1.0.0-4 X11 miscellaneous extension librar
ii  libxfixes3 1:3.0.1.2-4   X11 miscellaneous 'fixes' extensio
ii  libxft22.1.8.2-7 FreeType-based font drawing librar
ii  libxi6 1:1.0.0-5 X11 Input extension library
ii  libxinerama1   1:1.0.1-4 X11 Xinerama extension library
ii  libxml2

Bug#368570: marked as done (xdm : cannot start, looks for daemon in wrong directory)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 09:54:24 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#368570: xdm : cannot start, looks for daemon in wrong 
directory
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: xdm
Version: 1:1.0.1-6
Severity: grave
Justification: renders package unusable

After upgrade xdm does not start. /etc/init.d looks for xdm in
/usr/bin/X11/xdm, but there is no xdm in this directory, it is in
/usr/bin/xdm

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages xdm depends on:
ii  cpp   4:4.0.2-2  The GNU C preprocessor (cpp)
ii  debconf [debconf-2.0] 1.5.0  Debian configuration management sy
ii  libc6 2.3.6-7GNU C Library: Shared libraries
ii  libice6   6.9.0.dfsg.1-6 Inter-Client Exchange library
ii  libpam-modules0.79-3.1   Pluggable Authentication Modules f
ii  libpam-runtime0.79-3.1   Runtime support for the PAM librar
ii  libpam0g  0.79-3.1   Pluggable Authentication Modules l
ii  libselinux1   1.30-1 SELinux shared libraries
ii  libsm66.9.0.dfsg.1-6 X Window System Session Management
ii  libx11-6  6.9.0.dfsg.1-6 X Window System protocol client li
ii  libxau6   6.9.0.dfsg.1-6 X Authentication library
ii  libxaw8   6.9.0.dfsg.1-6 X Athena widget set library
ii  libxdmcp6 6.9.0.dfsg.1-6 X Display Manager Control Protocol
ii  libxext6  6.9.0.dfsg.1-6 X Window System miscellaneous exte
ii  libxinerama1  6.9.0.dfsg.1-6 X Window System multi-head display
ii  libxmu6   6.9.0.dfsg.1-6 X Window System miscellaneous util
ii  libxp66.9.0.dfsg.1-6 X Window System printing extension
ii  libxpm4   6.9.0.dfsg.1-6 X pixmap library
ii  libxt66.9.0.dfsg.1-6 X Toolkit Intrinsics
ii  xbase-clients 6.9.0.dfsg.1-6 miscellaneous X clients

xdm recommends no packages.

-- debconf information:
* shared/default-x-display-manager: xdm
  xdm/stop_running_server_with_children: false
  xdm/daemon_name: /usr/bin/X11/xdm

---End Message---
---BeginMessage---
Version: 1:1.0.4-1

On Tue, May 23, 2006 at 08:48:17AM +0200, Erwan David wrote:
 Package: xdm
 Version: 1:1.0.1-6
 Severity: grave
 Justification: renders package unusable

 After upgrade xdm does not start. /etc/init.d looks for xdm in
 /usr/bin/X11/xdm, but there is no xdm in this directory, it is in
 /usr/bin/xdm

Already fixed in the version of xdm in unstable.

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


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


Bug#367518: FTBFS in unstable: UTS Release version does not match the current version

2006-05-23 Thread Steve Langasek
On Tue, May 16, 2006 at 11:52:53AM -0500, Norbert Tretkowski wrote:
 * Martin Michlmayr wrote:
  kernel-image-2.4.27-alpha fails to build in unstable.

 Yes, I know. I have an update ready, but I didn't upload it yet
 because it's seems to be that we're removing 2.4 from etch.

Well, as the alpha kernel maintainer you're free to request removal of the
2.4 kernel packages any time you think it's ready.

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


signature.asc
Description: Digital signature


Processed: tagging 368362

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 tags 368362 + patch
Bug#368362: xmoto: breaks at startup
There were no tags set.
Tags added: patch


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#366965: marked as done (FTBFS on powerpc: invalid parameter combination for AltiVec intrinsic)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 07:47:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#366965: fixed in vlc 0.8.5.debian-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: vlc
Version: 0.8.5-test3.debian-3
Severity: serious

After putting in the Altivec casting patch you're now getting a
different error:

 Automatic build of vlc_0.8.5-test3.debian-3 on test.track.rz.uni-augsburg.de 
 by sbuild/powerpc 0.44
...
 gcc -Wall -I. -O4 -ffast-math -D__X264__ -DHAVE_MALLOC_H -maltivec 
 -mabi=altivec -DARCH_PPC -DSYS_LINUX  -s -fomit-frame-pointer   -c -o 
 common/ppc/pixel.o common/ppc/pixel.c
 common/ppc/pixel.c: In function 'pixel_sad_x4_16x16_altivec':
 common/ppc/pixel.c:707: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:708: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:709: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:710: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:717: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:718: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:719: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:720: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c: In function 'pixel_sad_x3_16x16_altivec':
 common/ppc/pixel.c:817: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:818: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:819: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:825: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:826: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:827: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c: In function 'pixel_sad_x4_16x8_altivec':
 common/ppc/pixel.c:937: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:938: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:939: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:940: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:947: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:948: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:949: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:950: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c: In function 'pixel_sad_x3_16x8_altivec':
 common/ppc/pixel.c:1047: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1048: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1049: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1055: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1056: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1057: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c: In function 'pixel_sad_x4_8x16_altivec':
 common/ppc/pixel.c:1168: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1169: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1170: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1171: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1178: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1179: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1180: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1181: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c: In function 'pixel_sad_x3_8x16_altivec':
 common/ppc/pixel.c:1278: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1279: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1280: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1286: error: invalid parameter combination for AltiVec 
 intrinsic
 common/ppc/pixel.c:1287: error: invalid parameter combination 

Bug#367986: Acknowledgement (sylpheed-gtk1: ..moving mail between folders within Sg1-1.0.6, crashes X.)

2006-05-23 Thread Arnt Karlsen
On Sun, 21 May 2006 19:34:16 -0700, Steve wrote in message 
[EMAIL PROTECTED]:

 On Mon, May 22, 2006 at 03:32:14AM +0200, Arnt Karlsen wrote:
  On Sun, 21 May 2006 17:55:12 -0700, Steve wrote in message 
  [EMAIL PROTECTED]:
 
   Any crash in X is not itself a bug in sylpheed-gtk1 either,
   *unless* sylpheed-gtk1 is allocating an excess of server-side
   memory and triggering the kernel's OOM killer, which doesn't seem
   likely.
 
  ..ok, how do I help you find out?  Running it locally, has it crash 
  X a lot, and get X get sluggish and I see loads around 2 to 6.   
  Running it over ssh, I see nice low loads, around 0.05-0.15.
 
 The xrestop program from the package of the same name should tell you
 whether this is a case of large amounts of memory (or increasing
 amounts of memory) are being eaten on the server by sylpheed.

..ideas on how to make xrestop survive to capture crash data?  
I ssh -X it, and xrestop crashes too, and the ssh link is trashed and
needs resetting. 
Neither xrestop nor sylpheed-gtk1 reports its pid to it, and
I get at least 6 unknown's showing up.  

xrestop - Display: 192.168.1.33:0.0
  Monitoring 23 clients. XErrors: 42
  Pixmaps:   47115K total, Other: 109K total, All:   47225K
total

res-base Wins  GCs Fnts Pxms Misc   Pxm mem  Other   Total   PID
Identifier 18035   121   23   8324602K  4K 
24606K  1261 KDE Desktop 1a0   130   290  206  14519654K
 7K  19661K  1285 kicker 260  2141   223  173   90 2204K
55K   2260K  1348 Error while loading
http://www.google.com/search?num=100hl=enlr=ie=
16069   180  118  335  271K  9K281K  1245 kwin
1c0   131   766   79   19  129K 11K140K   ?  
c2i.net - Sylpheed version 1.0.6 22080   253   56   89 
121K  7K128K  1340 a20 - Konsole 0a020411  
25   44K  2K 46K  1218 kded 2a0   27770   45  
10   31K  6K 38K  1351 KMix 1e01040   27   
5   15K456B 15K  1302 kbluetoothd 100 780  
18   21   12K864B 12K  1226 KDE Keyboard Tool 200 6 
  70   129   11K528B 11K  1303 KOrganizer Reminder
Daemon 2c0 660998K504B  9K  1358
Resize and Rotate 060 760997K528B   
  8K  1357 Keyboard Switch 040 011000B  
   1K  1K   ?   unknown 0c0 31004   
0B192B192B  1232 kaccess 300 21004  
 0B168B168B  1728 knotify 240 21004 
  0B168B168B  1344 konqueror 140 21004  
 0B168B168B  1241 ksmserver 2e0 1100   
00B 48B 48B   ?   xrestop 120 1100  
 00B 48B 48B   ?   unknown 080 110   
000B 48B 48B   ?   unknown 0e0 010
   000B 24B 24B   ?   unknown 020 01  
 0000B 24B 24B   ?   unknown


..sylpheed-gtk1 running locally is waay more sluggish 
than 140kB warrants. Running remotely, it's quick 'n snappy.

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.



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



Bug#368362: xmoto: breaks at startup

2006-05-23 Thread Rasmus Neckelmann

On 5/22/06, Rasmus Neckelmann [EMAIL PROTECTED] wrote:

On 5/21/06, Samuel Mimram [EMAIL PROTECTED] wrote:
  The new level caching system causes xmoto to break for the second time
  its run.


Some people report that the patch I've attached fixes the problem. I
can't verify it myself, so please excuse me if it still won't work. :)

--
Regards,
Rasmus Neckelmann


LevelSrc-amd64fix.patch
Description: Binary data


Bug#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts

2006-05-23 Thread Florian Weimer
Package: postgresql
Version: 7.4.7-6sarge1
Tags: security
Severity: grave

A couple of PostgreSQL issues have been disclosed today:

  http://www.postgresql.org/docs/techdocs.52

My analysis so far:

* CVE-2006-2313

High impact (because UTF-8 is affected and widely used).  Fix is
straightforward as far as UTF-8 is concerned, but will break some
applications which write certain forms of invalid UTF-8 to the
database.  If necessary, a dump and reload to switch to SQL_ASCII on
the server side will fix this.  However, PostgreSQL already rejects
some forms of invalid UTF-8.  Therefore, a change

I don't know the impact on other multibyte encodings; it's probably
necessary to ask upstream.

* CVE-2006-2314

This is the really interesting one.  It's restricted to certain
multi-byte encodings (that's why I think this bug is less severe, all
things considered).  No real fix is possible as long as we preserve
the interface.  The upstream fix outlawing \' breaks tons of legacy
PHP applications, but I have no better idea how to address it. 8-(

On the libpq side, I'd use static __thread instead of static for
the globals.  That way, we gain at least some thread safety.

(Unless someone objects, I'm going to clone this for the various
PostgreSQL packages.)


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



Processed: reassign 368229 to gnome-build

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.19
 reassign 368229 gnome-build
Bug#368229: anjuta: Projects cannot be opened, created or imported, plugin 
cannot be activated.
Bug reassigned from package `anjuta' to `gnome-build'.


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#364920: /etc/reader.conf.d/libetoken is wrong (DEVICENAME incorrect)

2006-05-23 Thread Ludovic Rousseau
Le Monday 22 May 2006 à 00:49:24, Javier Fernández-Sanguino Peña a écrit:
 On Sun, May 21, 2006 at 06:41:58PM +0200, Ludovic Rousseau wrote:
  
  It is removed by postinst now. You could remove the removal and the call
  to /usr/sbin/update-reader.conf once Debian Etch is out.
  
  I also modified the Info.plist file.
  - Only the first reader was used by pcscd because only one
ifdFriendlyName was present.
  - The file was not valid. I added the DTD URL and corrected an array
in /array. You can check the validity using xmllint --valid --noout
Info.plist
 
 I actually sent a fixed version yesterday to 1-DELAYED. That is going to
 overwrite your NMU. Please file separate bugs for the other issues.

Why do you want a new bug report?
- you now know the bug
- you have the patch

-- 
 Dr. Ludovic Rousseau[EMAIL PROTECTED]
 -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --



Bug#366275: xbase-clients: Missing build dependency

2006-05-23 Thread Steve Langasek
reopen 366275
retitle 366275 don't take b-d recommendations from random submitters without 
checking them!
submitter 366275 !
severity 366275 important
quit

   * Add xprint-utils to build-depends. Thanks anonymous someone.
 (closes: #366275)

This was a wrong fix.  The xprint-utils package does not contain any .pc
files, so it cannot possibly be relevant for the build failure shown; and
xprint-utils is not yet built on all architectures, which means that this
build-dep is now causing xbase-clients to FTBFS on release architectures
where it previously had no such problem.

The proper package to build-depend on is libxprintutil-dev.  The
xprint-utils package you now build-depend on does *not* pull in
libxprintutil-dev as a dependency, which means the status of xbase-clients
wrt xprintutils.pc has *not* changed.  Since both xbase-clients 1:7.0.1-1
and 1:7.0.1-2 built fine on the autobuilders (build-depends allowing!), this
bug does not exist, and the original submitter, in addition to having
stupidly misconfigured his email, has also stupidly misconfigured his build
environment.

Don't commit random and untested changes to debian/control on the say-so of
anonymous bug-submitting idiots!

The proper fix here is to pass --disable-xprint to the configure script for
xbdebizzy, so that the package neither fails to build nor builds with
different dependencies in the presence of libxp-dev.

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


signature.asc
Description: Digital signature


Bug#368468: fix pending

2006-05-23 Thread Bastian Venthur
tags 368468 pending
tags 363059 pending
quit

Hi Holmgren,

both bugs are fixed in the upcoming version, which is waiting for my
(usally very fast) sponsor.

Meanwhile you can have a look at the package at:

http://venthur.de/debian/crystalcursors/


Best regards,

Bastian


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



Bug#351693: status of #351693?

2006-05-23 Thread Steve Langasek
On Sat, May 20, 2006 at 10:57:20AM -0700, Rob Browning wrote:

 At this point, my best guess is that this may be a bug in 1.6.7 that
 has been fixed in 1.6.8.  I believe a number of GC and syntax related
 bugs have been fixed since 1.6.7, and I wouldn't be surprised if one
 of those is the culprit.

 Unfortunately, the only way I know of to reproduce this problem is to
 upload a new package for the autobuilders, which isn't a particularly
 friendly debugging process.

guile-1.6 has pleasantly trivial build-dependencies, so you ought to be able
to do a test build of 1.6.8 in merulo's unstable chroot without even needing
to contact debian-admin.

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



Bug#368587: invoke-rc.d: initscript nscd, action stop failed.

2006-05-23 Thread Steve Langasek
On Tue, May 23, 2006 at 12:40:18PM +0200, Francesco Paolo Lovergine wrote:
 klecker:~$ ps -fe|grep nscd
 frankie  14797  4397  0 12:27 pts/17   00:00:00 grep nscd
 klecker:~$ sudo /etc/init.d/nscd start
 Starting Name Service Cache Daemon: nscd.
 klecker:~$ ps -fe|grep nscd
 root 14804 1  0 12:27 ?00:00:00 /usr/sbin/nscd
 frankie  14812  4397  0 12:27 pts/17   00:00:00 grep nscd
 klecker:~$ sudo apt-get -u dist-upgrade
 Reading package lists... Done
 Building dependency tree... Done
 Calculating upgrade... Done
 The following packages will be upgraded:
   nscd
 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 30 not fully installed or removed.
 Need to get 0B/136kB of archives.
 After unpacking 0B of additional disk space will be used.
 Do you want to continue [Y/n]?
 Reading package fields... Done
 Reading package status... Done
 Retrieving bug reports... Done
 Reading changelogs... Done
 (Reading database ... 164331 files and directories currently installed.)
 Preparing to replace nscd 2.3.6-7 (using .../archives/nscd_2.3.6-9_i386.deb) 
 ...
 Stopping Name Service Cache Daemon: nscd.
 invoke-rc.d: initscript nscd, action stop failed.
 dpkg: warning - old pre-removal script returned error exit status 1
 dpkg - trying script from the new package instead ...
 Stopping Name Service Cache Daemon: nscd.
 invoke-rc.d: initscript nscd, action stop failed.
 dpkg: error processing /var/cache/apt/archives/nscd_2.3.6-9_i386.deb 
 (--unpack):
  subprocess new pre-removal script returned error exit status 1
 Starting Name Service Cache Daemon: nscd.
 Errors were encountered while processing:
  /var/cache/apt/archives/nscd_2.3.6-9_i386.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)

If the init script fails to stop the daemon, it is *correct* to fail the
upgrade as well.  We should not leave old versions of daemons silently
running after upgrade, this is a potential security hole.

The real question here is why the init script is failing to stop nscd on
your system.  This may or may not warrant an RC severity; probably not,
since it hasn't been reported before now.

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


signature.asc
Description: Digital signature


Bug#368556: Unable to reproduce

2006-05-23 Thread Alberto Marmodoro
Thanks for your prompt reply. I'm eager to help, even if limited to
working with the laptop I'm writing you even now -a PowerPC iBook G4 by
the way, maybe this can better define the problem.
I' ve been doing a few attempt at the issue.
I can reproduce it consistently with the submitted configuration, but
only under my default user, and even then just when kooka is started
with the usb cable already connected and the scanner on (a
Hewlett-Packard PSC1110 all-in-one printer, working fine under cups and
xscanimage for example). Thus I marked the bug as preventing the package
usage.

A newly created, empty user is able to launch the program without
problems, under the same conditions; I think therefore the cause could be
some config validation issue reading files from ./kde, I' ll investigate
this as soon as I'll have gdb installed.
For now I'm attaching just a strace log. The KDE crash handler report is
The application Kooka (kooka) crashed and caused the signal 6
(SIGABRT)

So long for now; thank you,
--
alberto

On Tue, May 23, 2006 at 11:11:51AM -0400, Filipus Klutiero wrote:
 Hi,
 I'm unable to reproduce this on a i386 Etch. The versions of kooka and 
 its direct dependencies are identical to yours, except for libc6 
 2.3.6-7, which unlikely explains the difference.
 
 Could you help doing a preliminary triaging to see if this needs 
 immediate investigation? Does this crash reproduce for all users on the 
 affected system? If so, on how many machines did you see it reproduce? 
 If it didn't reproduce on several machines, what makes you think that 
 the package is unusable?
 
 Note that a backtrace is always welcome along with a crash report.
 


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



Bug#351693: status of #351693?

2006-05-23 Thread Thomas Bushnell BSG
Steve Langasek [EMAIL PROTECTED] writes:

 On Sat, May 20, 2006 at 10:57:20AM -0700, Rob Browning wrote:

 At this point, my best guess is that this may be a bug in 1.6.7 that
 has been fixed in 1.6.8.  I believe a number of GC and syntax related
 bugs have been fixed since 1.6.7, and I wouldn't be surprised if one
 of those is the culprit.

 Unfortunately, the only way I know of to reproduce this problem is to
 upload a new package for the autobuilders, which isn't a particularly
 friendly debugging process.

 guile-1.6 has pleasantly trivial build-dependencies, so you ought to be able
 to do a test build of 1.6.8 in merulo's unstable chroot without even needing
 to contact debian-admin.

As is mentioned in the bug log, test builds in merulo's unstable
chroot work fine.  The bug does not manifest itself under such
conditions, and is seen only in the buildd environment.

Thomas


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



Bug#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts

2006-05-23 Thread Peter Eisentraut
Florian Weimer wrote:
 (Unless someone objects, I'm going to clone this for the various
 PostgreSQL packages.)

Packages are already being uploaded, so don't waste everyone's time.


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



Bug#368633: partman: LVM automatic partitioning not undoable

2006-05-23 Thread Geert Stappers
Tags 368633 moreinfo
Stop

On Tue, May 23, 2006 at 09:14:55AM -0700, Eric Monson wrote:
 Package: partman
 Severity: critical
 Justification: causes serious data loss
 
 I burned a D-I image for a friend (the latest weekly Debian CD as of Mar

Please confirm that you mean 'MaY' (and not 'MaRch')

 12 15:12) and chose to play with it a bit to see if it was clearly
 broken in some obvious way or likely okay for out purposes.
 
 Once I had verified enough that I thought the build was fine (and It did
 work for the install), I decided to try out the LVM option in the
 guided partitioning, since I had never done so before and I wanted to
 see what how it would arrange the partitions.  The guided partitioning
 page clearly states that you will have a chance to review and undo the
 guided partitioning, and is correct for regular partitions,
 but LVM occurs immeditely,

Hmmm...

 it seems, and even gpart was unable to restore my
 data.  I was able to salvage the python programs I had been working on,
 but nothing else.
 
 Since there is almost certainly a reason LVM gets applied immeditely,

Mmm again immeditely

 most likely that cannot be changed, but I am of the opinion that the
 diolog where you can select it should clearly state that the operation
 cannot be undone and may well kill working installations.


Please tell us more about what you did.

My default is to take the complain serious.
But I make the addition that if have my doubts about it,
so please tell how to reproduce the problem.
(right now is the original poster the one with the problem,
when he can convince other that the problem concerns others
then it more likely he will get help with his problem)


Cheers
Geert Stappers


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



Bug#368531: [Pkg-xen-devel] Bug#368531: Debian Xen kernel-image?

2006-05-23 Thread Torsten Werner

On 5/23/06, Stephane Bortzmeyer [EMAIL PROTECTED] wrote:

There is one? I do not find it in either etch or sid (or on
Alioth). Do I have to recompile a kernel?


$ aptitude search '~nlinux-image.*xen.*'
p   linux-image-2.6-xen-686  - Linux kernel 2.6 image on
PPro/Celeron/PII/
p   linux-image-2.6-xen-k7   - Linux kernel 2.6 image on AMD K7 machines
p   linux-image-2.6-xen-vserver-686  - Linux kernel 2.6 image on
PPro/Celeron/PII/
p   linux-image-2.6.16-1-xen-686 - Linux kernel 2.6.16 image on
PPro/Celeron/P
p   linux-image-2.6.16-1-xen-k7  - Linux kernel 2.6.16 image on
AMD K7 machine
p   linux-image-2.6.16-1-xen-vserver - Linux kernel 2.6.16 image on
PPro/Celeron/P
p   linux-image-xen-686  - Linux kernel image on
PPro/Celeron/PII/PIII
p   linux-image-xen-k7   - Linux kernel image on AMD K7 machines
p   linux-image-xen-vserver-686  - Linux kernel image on
PPro/Celeron/PII/PIII


Regards,
Torsten

--
http://www.twerner42.de/



Processed: Re: Bug#368633: partman: LVM automatic partitioning not undoable

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 Tags 368633 moreinfo
Bug#368633: partman: LVM automatic partitioning not undoable
There were no tags set.
Tags added: moreinfo

 Stop
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#368587: invoke-rc.d: initscript nscd, action stop failed.

2006-05-23 Thread Francesco Paolo Lovergine
On Tue, May 23, 2006 at 09:16:27AM -0700, Steve Langasek wrote:
 On Tue, May 23, 2006 at 12:40:18PM +0200, Francesco Paolo Lovergine wrote:
  klecker:~$ ps -fe|grep nscd
  frankie  14797  4397  0 12:27 pts/17   00:00:00 grep nscd
  klecker:~$ sudo /etc/init.d/nscd start
  Starting Name Service Cache Daemon: nscd.
  klecker:~$ ps -fe|grep nscd
  root 14804 1  0 12:27 ?00:00:00 /usr/sbin/nscd
  frankie  14812  4397  0 12:27 pts/17   00:00:00 grep nscd
  klecker:~$ sudo apt-get -u dist-upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
nscd
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  30 not fully installed or removed.
  Need to get 0B/136kB of archives.
  After unpacking 0B of additional disk space will be used.
  Do you want to continue [Y/n]?
  Reading package fields... Done
  Reading package status... Done
  Retrieving bug reports... Done
  Reading changelogs... Done
  (Reading database ... 164331 files and directories currently installed.)
  Preparing to replace nscd 2.3.6-7 (using 
  .../archives/nscd_2.3.6-9_i386.deb) ...
  Stopping Name Service Cache Daemon: nscd.
  invoke-rc.d: initscript nscd, action stop failed.
  dpkg: warning - old pre-removal script returned error exit status 1
  dpkg - trying script from the new package instead ...
  Stopping Name Service Cache Daemon: nscd.
  invoke-rc.d: initscript nscd, action stop failed.
  dpkg: error processing /var/cache/apt/archives/nscd_2.3.6-9_i386.deb 
  (--unpack):
   subprocess new pre-removal script returned error exit status 1
  Starting Name Service Cache Daemon: nscd.
  Errors were encountered while processing:
   /var/cache/apt/archives/nscd_2.3.6-9_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
 
 If the init script fails to stop the daemon, it is *correct* to fail the
 upgrade as well.  We should not leave old versions of daemons silently
 running after upgrade, this is a potential security hole.
 
 The real question here is why the init script is failing to stop nscd on
 your system.  This may or may not warrant an RC severity; probably not,
 since it hasn't been reported before now.
 

Sorry, but my point is another:

klecker:~$ pgrep start 
klecker:~$ pgrep nscd 
26316
klecker:~$ sudo /etc/init.d/nscd stop 
Stopping Name Service Cache Daemon: nscd.
klecker:~$ pgrep nscd
klecker:~$ sudo /etc/init.d/nscd stop
Stopping Name Service Cache Daemon: nscd.
klecker:~$ echo $?
1

This is incorrect. If the admin stops the daemon for his own reasons,
the upgrade fails as well. Incidentally I think the program has 
also some random issue with stopping (and eventually starting) the daemon (see
#362092 and others).

-- 
Francesco P. Lovergine


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



Processed: [electricsheep #365110] bug closed in 2.6.6-1

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tags 365110 + moreinfo
Bug#365110: electricsheep: 2.6.5-1 fails to start in etch
There were no tags set.
Tags added: moreinfo

 tags 365110 + unreproducible
Bug#365110: electricsheep: 2.6.5-1 fails to start in etch
Tags were: moreinfo
Tags added: unreproducible

 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#365110: [electricsheep #365110] bug closed in 2.6.6-1

2006-05-23 Thread Alexis Sukrieh
tags 365110 + moreinfo
tags 365110 + unreproducible
thanks

Hello, sorry for being so long to answer that report, I really had a lot
to do in real life recently...

I just installed a fresh new etch system (in a vserver) and
installed xscreensaver and electricsheep. I'm surprised, I cannot
reproduce that bug.
Everything goes fine on my etch system.

Anyway, I know that 2.6.5 (the version in etch) is affected by an
upstream bug about memory handling, which has been closed in version
2.6.6.

I installed 2.6.6-1 (the package is going to be uploaded soon,
hopefully) and checked that evrything is ok on etch with this version.

So I suppose that the bug your are experiencing will disappear with
2.6.6-1.

I welcome a report though, if you can grab the source package from my repo,
build it on your etch system and then test it:

deb-src http://www.sukria.net/debian ./
apt-get source electricsheep
cd electricsheep-2.6.6
dpkg-buildpackage -rfakeroot

Thanks for your report.

Regards,

Alexis.


-- 
Alexis Sukrieh [EMAIL PROTECTED]
0x1EE5DD34
Debian   http://www.debian.org
Backup Manager   http://www.backup-manager.org


signature.asc
Description: Digital signature


Bug#358493: tagcoll FTBFS: testsuite failures.

2006-05-23 Thread Enrico Zini
On Tue, May 23, 2006 at 02:52:03PM +0200, Falk Hueffner wrote:

 I don't think depending on gcc 4.1 without really understanding the
 issue is a good idea. There is a good chance that the bug is not
 really fixed, but only hidden by circumstances. So it would really be
 the best way to go to extract a minimal test case, see whether it's
 gcc's or tagcoll's fault, and then make sure it is really fixed.

Yes, but I don't have neither the time nor the motivation to do it.

This is how I see it:

 - The problem only happens on Alpha while it all works fine on other
   architectures.
 - The problem only happens with optimizations turned on, while it all
   works fine with -O0, also on Alpha.
 - It takes at least half an hour to build libtagcoll on escher.
 - I've been working hard on a libtagcoll rewrite, which I'll soon
   upload to experimental.

I would prefer to invest my time in getting the new code into shape,
rewriting the central database and trying to streamline tag submission
reviews.

If you however would like to investigate, the code is still in the sid
dchroot on escher, in the directory ~enrico.  Let me know if you intend
to work on it, so that I won't delete the compilation efforts on escher.


Ciao,

Enrico

-- 
GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini [EMAIL PROTECTED]


signature.asc
Description: Digital signature


Bug#368587: invoke-rc.d: initscript nscd, action stop failed.

2006-05-23 Thread Steve Langasek
On Tue, May 23, 2006 at 10:22:03PM +0200, Francesco Paolo Lovergine wrote:

 Sorry, but my point is another:

 klecker:~$ pgrep start 
 klecker:~$ pgrep nscd 
 26316
 klecker:~$ sudo /etc/init.d/nscd stop 
 Stopping Name Service Cache Daemon: nscd.
 klecker:~$ pgrep nscd
 klecker:~$ sudo /etc/init.d/nscd stop
 Stopping Name Service Cache Daemon: nscd.
 klecker:~$ echo $?
 1

Ah -- that wasn't supported by the transcript you posted, which showed you
explicitly starting the nscd daemon prior to running the upgrade.

Yes, if nscd is not running, the /etc/init.d/nscd stop command must not
fail.

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


signature.asc
Description: Digital signature


Processed: Re: Bug#368556: Unable to reproduce

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 retitle 368556 crashes with SIGABRT on startup with a certain configuration
Bug#368556: kooka: Crash on startup
Changed Bug title.

 severity 368556 important
Bug#368556: crashes with SIGABRT on startup with a certain configuration
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#368556: Unable to reproduce

2006-05-23 Thread Filipus Klutiero

retitle 368556 crashes with SIGABRT on startup with a certain configuration
severity 368556 important
thanks

Thanks for the additional information. I'm downgrading to important 
since this doesn't seem to affect several machines. If other people 
experience this bug, please report.
Alberto, is unplugging the cable/turning the scanner off before kooka 
startup a complete workaround, which lets you use kooka for scanning 
even with this user? Until you can identify which configuration is 
problematic, please report if you're able to reproduce this issue with a 
second user



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



Bug#365465: marked as done (gaphor: contains zope files already in python2.4-zopeinterface)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 14:17:15 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#365465: fixed in gaphor 0.8.1-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---

Package: gaphor
Version: 0.8.1-1
Severity: serious


Gaphor is uninstallable because it contains the following files already
in python2.4-zopeinterface without any Replaces:
  - /usr/lib/python2.4/site-packages/zope/__init__.py
  - /usr/lib/python2.4/site-packages/zope/interface/__init__.py
  - /usr/lib/python2.4/site-packages/zope/interface/_flatten.py
  - /usr/lib/python2.4/site-packages/zope/interface/adapter.py
  - /usr/lib/python2.4/site-packages/zope/interface/advice.py
  - /usr/lib/python2.4/site-packages/zope/interface/declarations.py
  - /usr/lib/python2.4/site-packages/zope/interface/document.py
  - /usr/lib/python2.4/site-packages/zope/interface/exceptions.py
  - /usr/lib/python2.4/site-packages/zope/interface/interface.py
  - /usr/lib/python2.4/site-packages/zope/interface/interfaces.py
  - /usr/lib/python2.4/site-packages/zope/interface/ro.py
  - /usr/lib/python2.4/site-packages/zope/interface/verify.py
  - /usr/lib/python2.4/site-packages/zope/interface/common/__init__.py
  - /usr/lib/python2.4/site-packages/zope/interface/common/idatetime.py
  - /usr/lib/python2.4/site-packages/zope/interface/common/interfaces.py
  - /usr/lib/python2.4/site-packages/zope/interface/common/mapping.py
  - /usr/lib/python2.4/site-packages/zope/interface/common/sequence.py

Regards.

-- 
Marc Dequènes (Duck)


pgpQo02JzGr7d.pgp
Description: PGP signature
---End Message---
---BeginMessage---
Source: gaphor
Source-Version: 0.8.1-2

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

gaphor_0.8.1-2.diff.gz
  to pool/main/g/gaphor/gaphor_0.8.1-2.diff.gz
gaphor_0.8.1-2.dsc
  to pool/main/g/gaphor/gaphor_0.8.1-2.dsc
gaphor_0.8.1-2_all.deb
  to pool/main/g/gaphor/gaphor_0.8.1-2_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.
Cédric Delfosse [EMAIL PROTECTED] (supplier of updated gaphor 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, 13 May 2006 10:08:20 +0200
Source: gaphor
Binary: gaphor
Architecture: source all
Version: 0.8.1-2
Distribution: unstable
Urgency: low
Maintainer: Cédric Delfosse [EMAIL PROTECTED]
Changed-By: Cédric Delfosse [EMAIL PROTECTED]
Description: 
 gaphor - UML modeling tool
Closes: 365465
Changes: 
 gaphor (0.8.1-2) unstable; urgency=low
 .
   * Don't include zope interface stuff in the package, and add to Depends
 python2.4-zopeinterface (Closes: Bug#365465)
   * Standard-Version to 3.7.2
Files: 
 a6c4176987928ea6a2041ca1c792c074 732 devel optional gaphor_0.8.1-2.dsc
 8032fc8ca9c8353ef1d9892ee26dcd4a 6730 devel optional gaphor_0.8.1-2.diff.gz
 fe20efcfb9a809625ea2fc8f883b5a43 280992 devel optional gaphor_0.8.1-2_all.deb

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

iD8DBQFEc21YbmmXPPfovGMRAi0wAJ4sGD6OMzX3y6inIptCrLlRENvdqgCgzFCA
P6owytzeYLgRaxPNfjvDw/U=
=qwXQ
-END PGP SIGNATURE-

---End Message---


Bug#368587: invoke-rc.d: initscript nscd, action stop failed.

2006-05-23 Thread Francesco Paolo Lovergine
On Tue, May 23, 2006 at 02:05:25PM -0700, Steve Langasek wrote:
 On Tue, May 23, 2006 at 10:22:03PM +0200, Francesco Paolo Lovergine wrote:
 
  Sorry, but my point is another:
 
  klecker:~$ pgrep start 
  klecker:~$ pgrep nscd 
  26316
  klecker:~$ sudo /etc/init.d/nscd stop 
  Stopping Name Service Cache Daemon: nscd.
  klecker:~$ pgrep nscd
  klecker:~$ sudo /etc/init.d/nscd stop
  Stopping Name Service Cache Daemon: nscd.
  klecker:~$ echo $?
  1
 
 Ah -- that wasn't supported by the transcript you posted, which showed you
 explicitly starting the nscd daemon prior to running the upgrade.
 
 Yes, if nscd is not running, the /etc/init.d/nscd stop command must not
 fail.
 

Just for note, the failure in stopping nscd in the previous transcript should 
be due to a
persistent cache corruption, see #336310. The daemon dies on assert just after 
starting, or so...

-- 
Francesco P. Lovergine


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



Processed: fix pending

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tags 368468 pending
Bug#368468: FTBFS: Forgot to touch patch-stamp?
Tags were: patch
Tags added: pending

 tags 363059 pending
Bug#363059: crystalcursors: Fails to install, missing dir to create 
alternatives.
There were no tags set.
Tags added: pending

 quit
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: Re: xbase-clients: Missing build dependency

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reopen 366275
Bug#366275: xbase-clients: Missing build dependency
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reopened, originator not changed.

 retitle 366275 don't take b-d recommendations from random submitters without 
 checking them!
Bug#366275: xbase-clients: Missing build dependency
Changed Bug title.

 submitter 366275 !
Bug#366275: don't take b-d recommendations from random submitters without 
checking them!
Changed Bug submitter from Anonymous [EMAIL PROTECTED] to Steve Langasek 
[EMAIL PROTECTED].

 severity 366275 important
Bug#366275: don't take b-d recommendations from random submitters without 
checking them!
Severity set to `important' from `serious'

 quit
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#368667: unmet dependencies: linux-kbuild-2.6.17

2006-05-23 Thread Julien Danjou
Package: linux-headers-2.6.17-rc3-686
Severity: serious
Tags: experimental

Hello,

% apt-get install linux-headers-2.6.17-rc3-686 
The following packages have unmet dependencies:
  linux-headers-2.6.17-rc3-686: Depends: linux-kbuild-2.6.17 but it is
not installable
E: Broken packages

Cheers,
-- 
Julien Danjou
// [EMAIL PROTECTED] http://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD
// Ferns will rule the world.


signature.asc
Description: Digital signature


Processed: tagging 368327, tagging 368451, tagging 368540

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 tags 368327 pending
Bug#368327: udev won't install, no error message
There were no tags set.
Tags added: pending

 tags 368451 pending
Bug#368451: udev: Syntax error reported
There were no tags set.
Tags added: pending

 tags 368540 pending
Bug#368540: udev: breaks booting with an initramfs image on Thinkpad T43 that 
needs special scsi/sata modules
There were no tags set.
Tags added: pending


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#362757: marked as done (Don't migrate to testing)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 15:32:24 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#362757: fixed in xaralx 0.5r1184-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: xaralx
Version: 0.4r804-1
Severity: serious

XaraLX is not yet usable, and until it is so, it should stay out of the
testing distribution.

This bug will be closed when saving and printing etc. works and the
program can be considered stable. Maybe I won't close it before the pure
GPL release, though.

Greetings,
Joachim

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

Versions of packages xaralx depends on:
ii  libc6   2.3.6-6  GNU C Library: Shared libraries
ii  libfreetype62.1.10-3 FreeType 2 font engine, shared lib
ii  libgcc1 1:4.1.0-1GCC support library
ii  libglib2.0-02.10.2-1 The GLib library of C routines
ii  libgtk2.0-0 2.8.16-1 The GTK+ graphical user interface 
ii  libjpeg62   6b-12The Independent JPEG Group's JPEG 
ii  libpango1.0-0   1.12.0-2 Layout and rendering of internatio
ii  libpng12-0  1.2.8rel-5.1 PNG library - runtime
ii  libstdc++6  4.1.0-1  The GNU Standard C++ Library v3
ii  libwxgtk2.6-0   2.6.1.2-0.1  wxWidgets Cross-platform C++ GUI t

xaralx recommends no packages.

-- no debconf information

---End Message---
---BeginMessage---
Source: xaralx
Source-Version: 0.5r1184-1

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

xaralx_0.5r1184-1.diff.gz
  to pool/non-free/x/xaralx/xaralx_0.5r1184-1.diff.gz
xaralx_0.5r1184-1.dsc
  to pool/non-free/x/xaralx/xaralx_0.5r1184-1.dsc
xaralx_0.5r1184-1_i386.deb
  to pool/non-free/x/xaralx/xaralx_0.5r1184-1_i386.deb
xaralx_0.5r1184.orig.tar.gz
  to pool/non-free/x/xaralx/xaralx_0.5r1184.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.
Joachim Breitner [EMAIL PROTECTED] (supplier of updated xaralx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 23 May 2006 22:38:56 +0200
Source: xaralx
Binary: xaralx
Architecture: source i386
Version: 0.5r1184-1
Distribution: unstable
Urgency: low
Maintainer: Joachim Breitner [EMAIL PROTECTED]
Changed-By: Joachim Breitner [EMAIL PROTECTED]
Description: 
 xaralx - versatile vector graphic program
Closes: 362757
Changes: 
 xaralx (0.5r1184-1) unstable; urgency=low
 .
   * New upstream release
   * Useful now, can migrate to testing (Closes: #362757)
   * xpm file now shipped by upstream, dropping imagemagick dependency
Files: 
 031b63246c1605bda4ebffce500f3a4c 835 non-free/graphics optional 
xaralx_0.5r1184-1.dsc
 0fec41f91ea032b0beca6063f46065cb 26070008 non-free/graphics optional 
xaralx_0.5r1184.orig.tar.gz
 f5eb7aee9f9e2b53740194b9c4c4a71c 1061376 non-free/graphics optional 
xaralx_0.5r1184-1.diff.gz
 f24baeec96361abc333ecc7d768dcccb 8633698 non-free/graphics optional 
xaralx_0.5r1184-1_i386.deb

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

iQCVAwUBRHOJcb8Zfhn2SkeXAQJtiQP/T5gJHbJ7W3RcftvrN9kyIy2KryVfSpi8
OOlaEHR+lUlgOcdV6Ohdk2R5X5eOUylpoQq2r+nwaWuAiVF5SDLSVs3OhV010whx
/L0KIiyTMC3oWJIcq0yWlSu0b+Idph0eSjHWuwvEMCRJkmX7ndPoN/10qWTjeHvB
LTI+/wqDiDE=
=RaqZ
-END PGP SIGNATURE-

---End Message---


Processed: your mail

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 Package: anjuta
Unknown command or malformed arguments to command.

 notfound 353057 2.0.2-2
Bug#353057: anjuta: crashes on startup with a SIGSEGV
Bug marked as not found in version 2.0.2-2.

 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#367954: FTBFS: syntax error near unexpected token `else'

2006-05-23 Thread Daniel Stenberg

On Thu, 18 May 2006, Martin Michlmayr wrote:


checking whether strerror_r is declared... yes
checking for a glibc strerror_r API... yes
../../configure: line 29513: syntax error near unexpected token `else'
../../configure: line 29513: `else'


Funnily enough, this bug has been around for quite some time but it seems 
unstable has a sensitive bash version or something. I could cure the problem 
with this (silly) patch:


diff -u -r1.194 -r1.195
--- configure.ac11 May 2006 21:37:58 -  1.194
+++ configure.ac23 May 2006 22:55:46 -  1.195
@@ -1412,7 +1412,8 @@
  AC_MSG_RESULT(no)
 ,
 dnl not invoked when crosscompiling)
-])
+ echo hej
+)
   fi
 else
   dnl and for crosscompilings


--
 -=- Daniel Stenberg -=- http://daniel.haxx.se -=-
  ech`echo xiun|tr nu oc|sed 'sx\([s\x]\)\([\xoi]\)xo un\2\1 is xg'`ol



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



Bug#365110: [electricsheep #365110] bug closed in 2.6.6-1

2006-05-23 Thread Mark Hedges

On Tue, 23 May 2006, Alexis Sukrieh wrote:
 
 I just installed a fresh new etch system (in a vserver) and
 installed xscreensaver and electricsheep. I'm surprised, I cannot
 reproduce that bug.
 Everything goes fine on my etch system.
 
 Anyway, I know that 2.6.5 (the version in etch) is affected by an
 upstream bug about memory handling, which has been closed in version
 2.6.6.
 

That's probably it.  I'm running a mixed etch/sid system with 
kernel 2.6.16 from unstable.

Thanks!

Mark


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



Processed: Re: Bug#368585: glibc-doc: conflict with manpages-dev package

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 368585 serious
Bug#368585: glibc-doc: conflict with manpages-dev package
Severity set to `serious' from `normal'

 reassign 368585 manpages-dev
Bug#368585: glibc-doc: conflict with manpages-dev package
Bug reassigned from package `glibc-doc' to `manpages-dev'.

 merge 365547 368585
Bug#365547: manpages-dev uninstallable because of conflicting file 
sem_destroy.3.gz from glibc-doc
Bug#368585: glibc-doc: conflict with manpages-dev package
Bug#368155: manpages-dev: conflicts with glibc-doc
Bug#368160: manpages-dev: conflicts with glibc-doc
Bug#368281: manpages-dev: conflicts with glibc-doc
Bug#368429: Error processing manpages-dev when upgrading
Merged 365547 368155 368160 368281 368429 368585.

 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#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts

2006-05-23 Thread Peter Eisentraut
Peter Eisentraut wrote:
 Florian Weimer wrote:
  (Unless someone objects, I'm going to clone this for the various
  PostgreSQL packages.)

 Packages are already being uploaded, so don't waste everyone's time.

Correction: packages have already been uploaded, so we only need to wait 
for the security team's approval of the stable upload.

(Yes, there is a secret club that coordinates these things before the 
publication of the security issue.)


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



Bug#366563: marked as done (Kspread losses data)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 19:31:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Should be fixed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: kspread
Version:   1:1.5.0-1+b1
Severity: serious

I'm working a small file in Kspread and suddently I noted that it doesn't save 

all the workshet (only some numbers). This happens when you save data

in OASIS formate (KSpread default). In Kspread format (ksp) this problem

don't happen.

I attached a small example. Try to replicate that problem.


Waldo


teste.ksp
Description: application/kspread
---End Message---
---BeginMessage---

Version: 1:1.5.1-1

This should have been fixed by 1.5.1's upload. Please reopen if you can 
reproduce.
---End Message---


Bug#368229: There is no existing pre-compiled i386 downgrade

2006-05-23 Thread Gnaural
Hi,

I really gave anjuta2 a try, even rebuilt gnome-build
from source, etc., but in the end, I just don't want
to use Anjuta2 until it has at least some basic
Project functionality.

Problem is, I found no pre-compiled way to downgrade
back to my last working version. Seems the current
Testing debs in all the mirrors are actually from the
non-functional anjuta_1.2.4-1+b1_i386.deb batch, and
stable's anjuta_1.2.2-9_i386.deb doesn't work either. 

I remembered last January when both first went sour,
and the precompiled solution was ultimately provided
by  anjuta_1.2.4a-2_i386.deb .

Problem: that deb isn't available on any debian
mirrors, only the source and patch.

Not being in the mood to go through recompiling that
again, I just did an FTP search and found exactly one
existant copy of anjuta_1.2.4a-2_i386.deb -- on an
Ubuntu site, ironically enough. Probably is the debian
one, certainly works enough 
to allow me to program again:
ftp://140.113.168.127/distributions/ubuntu/package/pool/universe/a/anjuta/anjuta_1.2.4a-2_i386.deb

I think the guy that said split Anjuta1 and Anjuta2
was right -- to offer both through apt-get would allow
people with gigantic Projects that are left
dead-in-the-water with Anjuta2 to keep working, and
encourage them to try to start new projects with
Anjuta2. When Debian's Anjuta2 can actually handle
projects, I mean.

Thanks




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



Bug#368531: Debian Xen kernel-image?

2006-05-23 Thread Stephane Bortzmeyer
 Could you please try with a Debian kernel image 

There is one? I do not find it in either etch or sid (or on
Alioth). Do I have to recompile a kernel?




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



Bug#349283: marked as done (tor: Tor security advisory: hidden services can be located quickly)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 14:17:25 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#349283: fixed in tor 0.1.1.20-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: tor
Version: 0.1.0.16-1
Severity: grave
Tags: security
Justification: user security hole

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Source: http://archives.seul.org/or/announce/Jan-2006/msg1.html

Basically an attacker who can run a fast Tor server can find the location of a
hidden service in a matter of hours, possibly even minutes.  This is fixed in
0.1.1.12-alpha, but as this is an alpha release it may contain other bugs.

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

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

iD8DBQFD0s8gqlk5sZw9W7kRArprAKCk6rq93AwexRo3Mnp3ovaPztZTugCfRdZM
noaYhcZw50wxwg4MiKZn5H4=
=RRVR
-END PGP SIGNATURE-


---End Message---
---BeginMessage---
Source: tor
Source-Version: 0.1.1.20-1

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

tor-dbg_0.1.1.20-1_i386.deb
  to pool/main/t/tor/tor-dbg_0.1.1.20-1_i386.deb
tor_0.1.1.20-1.diff.gz
  to pool/main/t/tor/tor_0.1.1.20-1.diff.gz
tor_0.1.1.20-1.dsc
  to pool/main/t/tor/tor_0.1.1.20-1.dsc
tor_0.1.1.20-1_i386.deb
  to pool/main/t/tor/tor_0.1.1.20-1_i386.deb
tor_0.1.1.20.orig.tar.gz
  to pool/main/t/tor/tor_0.1.1.20.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.
Peter Palfrader [EMAIL PROTECTED] (supplier of updated tor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 23 May 2006 20:16:25 +0200
Source: tor
Binary: tor-dbg tor
Architecture: source i386
Version: 0.1.1.20-1
Distribution: unstable
Urgency: low
Maintainer: Peter Palfrader [EMAIL PROTECTED]
Changed-By: Peter Palfrader [EMAIL PROTECTED]
Description: 
 tor- anonymizing overlay network for TCP
 tor-dbg- debugging symbols for Tor
Closes: 338797 349283
Changes: 
 tor (0.1.1.20-1) unstable; urgency=low
 .
   * New upstream stable release: The 0.1.1.x tree is now the new stable
 tree.  Upload to unstable rather than experimental.
 .
 tor (0.1.1.19-rc-1) experimental; urgency=low
 .
   * New upstream version.
   * Remove support for my nodoc DEB_BUILD_OPTIONS variable.  It clutters
 stuff and I haven't used it in ages.
   * Update debian/tor.docs file.
 .
 tor (0.1.1.18-rc-1) experimental; urgency=low
 .
   * New upstream version.
   * update debian/tor.doc:
 - no longer ship INSTALL and README files, they are useless now.
 - doc/stylesheet.css, doc/tor-doc-server.html, doc/tor-doc-unix.html,
   doc/tor-hidden-service.html, doc/tor-switchproxy.html got replaced
   by doc/website/stylesheet.css and doc/website/tor-* which is more
   or less the same, only taken from the website.  Some links are
   probably broken still, but this should get fixed eventually.
 .
 tor (0.1.1.17-rc-1) experimental; urgency=low
 .
   * New upstream version.
   * Forward port patches/07_log_to_file_by_default.
 .
 tor (0.1.1.16-rc-1) experimental; urgency=low
 .
   * New upstream version.
 .
 tor (0.1.1.15-rc-1) experimental; urgency=low
 .
   * New upstream version.
   * Apparently passing --host to configure when not cross-compiling
 is evil now and greatly confuses configure.  So don't do it unless it
 actually differs from --build host.
 .
 tor (0.1.1.14-alpha-1) experimental; urgency=low
 .
   * New upstream version.
   * Include 0.1.0.17 changelog in experimental tree.
   * doc/FAQ is no longer shipped, so remove it from debian/tor.docs.
 .
 tor (0.1.1.13-alpha-1) experimental; urgency=low
 .
   * New upstream version.
   * Forward port patches/02_add_debian_files_in_manpage.
   * Forward port patches/03_tor_manpage_in_section_8.
   * Create /var/run/tor on init script start if 

Bug#367316: nvidia-glx: Works for me, though different OpenGL version string

2006-05-23 Thread Benjamin Kudria
Hi, Ted.  Thanks for the reply.

I uninstalled everything, and then re-installed nvidia-glx and 
nvidia-kernel-2.6.16-1-k7.  They are now versions 1.0.8756-4 and 1.0.8756+1 
respectively.  I didn't compile these myself.  The glxinfo and glxgears 
output is the same.  Any ideas?

Sorry for the late reply, I didn't receive the email, I had to look at the web 
frontend.

Thanks,


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



Bug#368362: xmoto: breaks at startup

2006-05-23 Thread Cyril Brulebois
On Tue, May 23, 2006 at 07:26:26PM +0200, Rasmus Neckelmann wrote:
 Some people report that the patch I've attached fixes the problem. I
 can't verify it myself, so please excuse me if it still won't work. :)
Hi,

I got the same error on ppc, and after having rebuilt the package with
your patch, and deleted ~/.xmoto/LCache, all is working as before.

(In the meanwhile, the workaround about disabling cache was working
too.)

Thanks,

-- 
Cyril Brulebois


signature.asc
Description: Digital signature


Bug#368681: cvs: does not flag conflicted copies anymore

2006-05-23 Thread Henrique de Moraes Holschuh
Package: cvs
Version: 1:1.12.13-2
Severity: grave
Justification: renders package unusable

CVS now cannot detect conflicted merges (C state) anymore, which is bound
to cause all sort of broken commits if people doesn't notice it in time.

I didn't actually *try* to commit a file with merge conflicts, but cvs
update and cvs status both fail to detect the file is full of ,
 and  hunks...

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.17-debian13+bluesmoke+lm85
Locale: LANG=pt_BR.ISO-8859-1, LC_CTYPE=pt_BR.ISO-8859-1 (charmap=ISO-8859-1)

Versions of packages cvs depends on:
ii  debconf [debconf-2.0] 1.5.1  Debian configuration management sy
ii  libc6 2.3.6-9GNU C Library: Shared libraries
ii  libpam-runtime0.79-3.1   Runtime support for the PAM librar
ii  libpam0g  0.79-3.1   Pluggable Authentication Modules l
ii  zlib1g1:1.2.3-11 compression library - runtime

Versions of packages cvs recommends:
ii  info [info-browser] 4.8.dfsg.1-1 Standalone GNU Info documentation 
ii  konqueror [info-browser]4:3.5.2-2+b1 KDE's advanced file manager, web b
ii  netbase 4.25 Basic TCP/IP networking system
ii  pinfo [info-browser]0.6.9-2  An alternative info-file viewer
ii  xemacs21-mule [info-browser 21.4.19-1highly customizable text editor --

-- debconf information excluded

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


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



Bug#368289: Bug#364629: NMU broke configure script in s390 buildd

2006-05-23 Thread Lars Wirzenius
ma, 2006-05-22 kello 18:37 -0500, Gunnar Wolf kirjoitti:
 Thanks for taking care of my poor little package... I'm sure you
 understand why I haven't looked at it much lately :-( Anyway, it seems
 the patch you NMUed created some problems - As I'm still stuck with
 Debconf for a bit, and then have to catch up with at least one month
 of job I put away, could you take a dive into this again?

Yeah, I noticed that. I have no idea what the problem is -- I did build
the package with pbuilder before I uploaded it, so it should build
cleanly. Unfortunately, I'm travelling for another couple of weeks, so I
won't be able to work on this. Hopefully someone else notices the
problem and has time to fix things. My apologizes for messing things up.

-- 
There's a reason why release manager is abbreviated rm.



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



Bug#368633: partman: LVM automatic partitioning not undoable

2006-05-23 Thread ERIIX M. Blaike
On Tue, 2006-05-23 at 21:54 +0200, Geert Stappers wrote: 
 Please confirm that you mean 'MaY' (and not 'MaRch')
Sorry.  Timestamp from the wrong iso.  May 14 16:24 is the timestamp
from the one in question.

 Please tell us more about what you did.

I played around some in the disc, but the important step for
reproduction is simply to choose the LVM option in the guided
partitioning -- Erase entire disk and use LVM -- and you will be left
with, IIRC, /boot and an LVM partition (activated) that has some drives
in it.  The point is that it has already committed the changed partition
table and saved the LVM data into the space left for LVM.  Feel free to
try it, but I would advise doing so only on an emulated disc or on a
drive that has nothing important (or you have a backup of).

(Semi-)Detailed Walkthrough (I'm going along in qemu as I write this):
1: Get to partman (how you get there should be irrelevant)
2: In the guided partitioning, choose Erase entire disk and use LVM
3: Choose any of the partitioning schemes presented (I used seperate
home on my laptop, and have now confirmed all in one partition under
qemu -- I'm sure the many filesystem option will be similar)
4: Choose whatever name you want for the Volume Group
4a: Partition table is thrashed and LVM partition is activated and set
up (data being written even outside the partition table)
5: You can now confirm using fdisk that the partition table has been
changed to the new, LVM-equipped one.  Since the LVM partition was
activated and the VG set up, data in the partition(s) that were where it
now is may no longer exist.

 My default is to take the complain serious.
 But I make the addition that if have my doubts about it,
 so please tell how to reproduce the problem.

Done, but do be careful if you wish to follow the walkthrough.

 (right now is the original poster the one with the problem,
 when he can convince other that the problem concerns others
 then it more likely he will get help with his problem)

Actually, my problem is done and gone.  I lost almost everything on my
laptop due primarilly to my own inattention.  I knew that LVM setup
in partman proper requires saving the partition table and should have
realized from this that the guided partitioning would have to play by
the same rules.  I just don't want anyone else in this situation.



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



Bug#340960: marked as done (--delete-input-file ate my data)

2006-05-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 May 2006 21:32:10 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#340960: fixed in flac 1.1.2-4
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: flac
Severity: grave

  $ flac --delete-input-file -V --best 1_orig.wav
  [...]
  1_orig.wav: 46% complete, ratio=0.3691_orig.wav: WARNING: unexpected EOF; 
expected 536869888 samples, got 246564864 samples
  1_orig.wav: 46% complete, ratio=0.369

After this, 1_orig.wav was deleted.  The resulting file 1_orig.flac *appears* to
be ok, but I have no way to verify it since the old file 1_orig.wav is gone.

The docs say --delete-input-file doesn't cause deletion of input file when an
error occurs.  I would say that unexpected EOF is indeed an error, even though
it's only marked as warning.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL 
set to C)

---End Message---
---BeginMessage---
Source: flac
Source-Version: 1.1.2-4

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

flac_1.1.2-4.diff.gz
  to pool/main/f/flac/flac_1.1.2-4.diff.gz
flac_1.1.2-4.dsc
  to pool/main/f/flac/flac_1.1.2-4.dsc
flac_1.1.2-4_amd64.deb
  to pool/main/f/flac/flac_1.1.2-4_amd64.deb
libflac++-dev_1.1.2-4_amd64.deb
  to pool/main/f/flac/libflac++-dev_1.1.2-4_amd64.deb
libflac++5_1.1.2-4_amd64.deb
  to pool/main/f/flac/libflac++5_1.1.2-4_amd64.deb
libflac-dev_1.1.2-4_amd64.deb
  to pool/main/f/flac/libflac-dev_1.1.2-4_amd64.deb
libflac-doc_1.1.2-4_all.deb
  to pool/main/f/flac/libflac-doc_1.1.2-4_all.deb
libflac7_1.1.2-4_amd64.deb
  to pool/main/f/flac/libflac7_1.1.2-4_amd64.deb
liboggflac++-dev_1.1.2-4_amd64.deb
  to pool/main/f/flac/liboggflac++-dev_1.1.2-4_amd64.deb
liboggflac++2_1.1.2-4_amd64.deb
  to pool/main/f/flac/liboggflac++2_1.1.2-4_amd64.deb
liboggflac-dev_1.1.2-4_amd64.deb
  to pool/main/f/flac/liboggflac-dev_1.1.2-4_amd64.deb
liboggflac3_1.1.2-4_amd64.deb
  to pool/main/f/flac/liboggflac3_1.1.2-4_amd64.deb
xmms-flac_1.1.2-4_amd64.deb
  to pool/main/f/flac/xmms-flac_1.1.2-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.
Joshua Kwan [EMAIL PROTECTED] (supplier of updated flac package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 23 May 2006 21:17:41 -0700
Source: flac
Binary: libflac7 libflac++-dev libflac-doc liboggflac-dev liboggflac3 
libflac-dev libflac++5 xmms-flac liboggflac++-dev liboggflac++2 flac
Architecture: source amd64 all
Version: 1.1.2-4
Distribution: unstable
Urgency: low
Maintainer: Joshua Kwan [EMAIL PROTECTED]
Changed-By: Joshua Kwan [EMAIL PROTECTED]
Description: 
 flac   - Free Lossless Audio Codec - command line tools
 libflac++-dev - Free Lossless Audio Codec - C++ development library
 libflac++5 - Free Lossless Audio Codec - C++ runtime library
 libflac-dev - Free Lossless Audio Codec - C development library
 libflac-doc - Free Lossless Audio Codec - library documentation
 libflac7   - Free Lossless Audio Codec - runtime C library
 liboggflac++-dev - Free Lossless Audio Codec - C++ development library (ogg)
 liboggflac++2 - Free Lossless Audio Codec - C++ runtime library (ogg)
 liboggflac-dev - Free Lossless Audio Codec - C development library (ogg)
 liboggflac3 - Free Lossless Audio Codec - runtime C library (ogg)
 xmms-flac  - Free Lossless Audio Codec - XMMS and Beep input plugin
Closes: 327108 340960 356788
Changes: 
 flac (1.1.2-4) unstable; urgency=low
 .
   * Acknowledge NMU, now that it's snugly in testing. closes: #340960
   * Fix the watch file.
   * Make symlinks for /usr/lib/bmp in xmms-flac to 'provide' bmp-flac,
 since input plugins between the two players are interchangeable.
 closes: #327108, #356788
   * Bump Standards-Version.
   * Fix a goof in the rules that prevented ldconfig from happening in the
 postinst of all 

Processed: Merge

2006-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 368667 grave
Bug#368667: unmet dependencies: linux-kbuild-2.6.17
Severity set to `grave' from `serious'

 tags 368667 - experimental
Bug#368667: unmet dependencies: linux-kbuild-2.6.17
Tags were: experimental
Tags removed: experimental

 reassign 368667 linux-2.6
Bug#368667: unmet dependencies: linux-kbuild-2.6.17
Bug reassigned from package `linux-headers-2.6.17-rc3-686' to `linux-2.6'.

 reassign 368544 linux-2.6
Bug#368544: linux-headers-2.6.17-rc3-amd64-k8: depends on non-existant package 
linux-kbuild-2.6.17
Bug reassigned from package `linux-headers-2.6.17-rc3-amd64-k8' to `linux-2.6'.

 merge 368667 368544
Bug#368544: linux-headers-2.6.17-rc3-amd64-k8: depends on non-existant package 
linux-kbuild-2.6.17
Bug#368667: unmet dependencies: linux-kbuild-2.6.17
Merged 368544 368667.

 found 368544 2.6.16+2.6.17-rc3-0experimental.1
Bug#368544: linux-headers-2.6.17-rc3-amd64-k8: depends on non-existant package 
linux-kbuild-2.6.17
Bug#368667: unmet dependencies: linux-kbuild-2.6.17
Bug marked as found in version 2.6.16+2.6.17-rc3-0experimental.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#368310: upstream; to be fixed in 4.2.1

2006-05-23 Thread Steve M. Robbins
Hi,

Just to note: a new upstream version 4.2.1 is at release candidate
status.  I have alerted upstream about this problem and expect that it
will be addressed in the next upstream release.  I'll leave it until
then.

-Steve



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