Bug#394280: Bug unreproducible

2006-10-31 Thread Christian Perrier
Quoting Nick Dickerson ([EMAIL PROTECTED]):
 I removed and reinstalled bootsplash and am still getting the same error.
 If you need any more info please let me know.
 Nick
 
 Preconfiguring packages ...
 bootsplash failed to preconfigure, with exit status 10
 Selecting previously deselected package bootsplash.
 (Reading database ... 188111 files and directories currently installed.)
 Unpacking bootsplash (from .../bootsplash_3.3-1_i386.deb) ...
 Setting up bootsplash (3.3-1) ...
 dpkg: error processing bootsplash (--configure):
 subprocess post-installation script returned error exit status 10
 Errors were encountered while processing:
 bootsplash
 E: Sub-process /usr/bin/dpkg returned an error code (1)


I actually *don't* understand why this doesn't install
bootsplash-theme-debian. bootsplash *depends* on it so that package
should be installed along with bootsplash alone.

WHat do you use to install it? apt-get?







signature.asc
Description: Digital signature


Bug#396226: [Pkg-samba-maint] Bug#396226: samba: Messes up file permissions when POSIX ACLs are

2006-10-31 Thread Christian Perrier

 Package: samba
 Version: 3.0.23c-1
 Severity: grave
 Justification: renders package unusable

For you probably but up to now, we hadn't much reports that it is for
other users

 
 We are running Samba 3.0.23c on Debian.
 
 Over the weekend, we updated out file server to Debian's kernel 2.6.18.  
 We had previously never run a kernel with ACL support enabled.  Since 
 the upgrade, we are seeing very strange permission behavior.  It appears 
 to berelated to POSIX ACL support in Samba.
 
 It seems that what's happening is this.
 
 We have a number of files that are user/group writable (permissions 0664). 
 When a user that is someone other than the Unix owner of the file writes 
 to it, the permissions switch to 0474 (-r--rwxr--) and an ACL is added 
 with this second user getting read/write permission to it.
 
 Unfortunately, the Unix owner of the file now is locked out of writing 
 to it.
 
 We never had any problem with permissions on these files before using  
 the ACL-enabled kernel.  


Well, first of all, the smb.conf would help a lot, here




signature.asc
Description: Digital signature


Bug#392961: marked as done ([NONFREE-DOC:GFDL] package contains non-free documentation)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 00:02:30 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#392961: fixed in gdb-avr 6.4-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: gdb-avr
Version: 6.4-1
Severity: serious

The package (at least the source) contains GFDL docs with invariant
sections and/or cover texts.

---End Message---
---BeginMessage---
Source: gdb-avr
Source-Version: 6.4-2

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

gdb-avr_6.4-2.diff.gz
  to pool/main/g/gdb-avr/gdb-avr_6.4-2.diff.gz
gdb-avr_6.4-2.dsc
  to pool/main/g/gdb-avr/gdb-avr_6.4-2.dsc
gdb-avr_6.4-2_i386.deb
  to pool/main/g/gdb-avr/gdb-avr_6.4-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.
Hakan Ardo [EMAIL PROTECTED] (supplier of updated gdb-avr 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: Sun, 29 Oct 2006 17:32:39 +0100
Source: gdb-avr
Binary: gdb-avr
Architecture: source i386
Version: 6.4-2
Distribution: unstable
Urgency: low
Maintainer: Hakan Ardo [EMAIL PROTECTED]
Changed-By: Hakan Ardo [EMAIL PROTECTED]
Description: 
 gdb-avr- The GNU Debugger for avr
Closes: 392961
Changes: 
 gdb-avr (6.4-2) unstable; urgency=low
 .
   * Added suggest gdb-doc (closes: #392961)
Files: 
 b59e96f5f2ff05809780a6076a25287c 751 devel extra gdb-avr_6.4-2.dsc
 60d55dcaaea94a1897cef4a938a0b31e 2020 devel extra gdb-avr_6.4-2.diff.gz
 65ec0df60ccf8ab3c7c19a6547802435 1943038 devel extra gdb-avr_6.4-2_i386.deb

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

iD8DBQFFRvlCAbtddT3jfcARAq59AJoCeyYmEa1eiI1lF4pzhGfFXyzogACgxcNE
RSHH6OaUAntzoIPV7WTX2VA=
=GEAc
-END PGP SIGNATURE-

---End Message---


Bug#395102: marked as done (CVE-2006-5443: WIMS Data Manipulation Vulnerability fixed in new upstream version)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 00:02:42 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#395102: fixed in wims 3.60-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: wims
severity: grave
tags: security

A vulnerability has been found in WIMS (and is fixed in 3.60):

This release fixes a security hole related to variable rights, which 
allowed some kinds of users to alter unauthorized data


Please mention the CVE id in the changelog.

---End Message---
---BeginMessage---
Source: wims
Source-Version: 3.60-1

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

flydraw_3.60-1_i386.deb
  to pool/main/w/wims/flydraw_3.60-1_i386.deb
texgd_3.60-1_i386.deb
  to pool/main/w/wims/texgd_3.60-1_i386.deb
wims-modules_3.60-1_all.deb
  to pool/main/w/wims/wims-modules_3.60-1_all.deb
wims_3.60-1.diff.gz
  to pool/main/w/wims/wims_3.60-1.diff.gz
wims_3.60-1.dsc
  to pool/main/w/wims/wims_3.60-1.dsc
wims_3.60-1_i386.deb
  to pool/main/w/wims/wims_3.60-1_i386.deb
wims_3.60.orig.tar.gz
  to pool/main/w/wims/wims_3.60.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.
Georges Khaznadar [EMAIL PROTECTED] (supplier of updated wims 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: Sun, 29 Oct 2006 12:05:29 +0100
Source: wims
Binary: texgd flydraw wims-modules wims
Architecture: source i386 all
Version: 3.60-1
Distribution: unstable
Urgency: low
Maintainer: Georges Khaznadar [EMAIL PROTECTED]
Changed-By: Georges Khaznadar [EMAIL PROTECTED]
Description: 
 flydraw- Inline drawing tool
 texgd  - Program to convert short TeX formulas to PNG graphics
 wims   - WWW Interactive Mathematics Server (WIMS)
 wims-modules - modules used by the WIMS server
Closes: 395102
Changes: 
 wims (3.60-1) unstable; urgency=low
 .
   * Upgraded to new upstream version.
 Closes: #395102 (CVE-2006-5443)
Files: 
 c5eb65fae0b67dd046fe1878b2bec941 642 web optional wims_3.60-1.dsc
 eb297f6a5b465a086ff046f141698802 12640037 web optional wims_3.60.orig.tar.gz
 ef20d040d42dab477474decdef2ec663 19932 web optional wims_3.60-1.diff.gz
 bb98e3a0db716bf4be1ae68beb1b267b 6593048 web optional wims_3.60-1_i386.deb
 932ec2b12fc9f45595eed98a9dd7891a 40218 graphics optional 
flydraw_3.60-1_i386.deb
 bbf8609e32f0a565a3cf2fe4fd0555bf 20274 graphics optional texgd_3.60-1_i386.deb
 8c3f3cf706e53136e935672c33ad651f 6006616 web optional 
wims-modules_3.60-1_all.deb

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

iD8DBQFFROCMvPbGD26BadIRAq/UAJ9485VrnL6Pjpv6FERJJ2YbK1zddACfYXF7
sBvFGfX36Fdzk6T+3zkmL5Y=
=N79a
-END PGP SIGNATURE-

---End Message---


Bug#359804: marked as done (tix: libTix8.4.so.1 lacks SONAME)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 00:02:34 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#359804: fixed in tix 8.4.0-6
has caused the attached Bug report to be marked as done.

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

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

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

---BeginMessage---
Package: tix
Version: 8.4.0-4
Severity: serious

Hi,

The shared library «/usr/lib/libTix8.4.so.1» included in the tix
package does not have any SONAME defined. This makes other programs
linking against it to miss Depends on tix as in the case of netgen.

regards,
guillem

---End Message---
---BeginMessage---
Source: tix
Source-Version: 8.4.0-6

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

tix-dev_8.4.0-6_i386.deb
  to pool/main/t/tix/tix-dev_8.4.0-6_i386.deb
tix_8.4.0-6.diff.gz
  to pool/main/t/tix/tix_8.4.0-6.diff.gz
tix_8.4.0-6.dsc
  to pool/main/t/tix/tix_8.4.0-6.dsc
tix_8.4.0-6_i386.deb
  to pool/main/t/tix/tix_8.4.0-6_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.
Amaya Rodrigo Sastre [EMAIL PROTECTED] (supplier of updated tix 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, 31 Oct 2006 08:44:36 +0100
Source: tix
Binary: tix tix-dev
Architecture: source i386
Version: 8.4.0-6
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: Amaya Rodrigo Sastre [EMAIL PROTECTED]
Description: 
 tix- The Tix library for Tk -- runtime package
 tix-dev- The Tix library for Tk -- development package
Closes: 359804 360920 366266 374623 394635
Changes: 
 tix (8.4.0-6) unstable; urgency=low
 .
   * QA upload.
   * Install man.macros as /usr/share/tixman.macros. Fix all the manpages
 accordingly. (Closes: #394635).
   * Updated Standards version, to 3.7.2, no changes needed.
   * Ack previous NMUS (Closes: #360920, #366266, #374623, #359804).
   * Created debian/compat, at value 5.
Files: 
 fb2b38ec900b6f82a8fab8315062b5b5 593 libs optional tix_8.4.0-6.dsc
 7fcd84a1a6e27e432cb07284b7a34317 1820202 libs optional tix_8.4.0.orig.tar.gz
 7db35de24f2174c5f65141539e498e3a 27937 libs optional tix_8.4.0-6.diff.gz
 179fe88c7423b978f8a8e7972bae087b 315048 libs optional tix_8.4.0-6_i386.deb
 1634778383a5e147172cdacc92bed8ec 534386 devel optional tix-dev_8.4.0-6_i386.deb

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

iD8DBQFFRv/SNFDtUT/MKpARAgjzAKDcls+swtQt0eH9O8J0nUN8+UrMvACfU/QW
YsqQfBiI703v0W1pAWGcDEg=
=HoaZ
-END PGP SIGNATURE-

---End Message---


Bug#396323: rpncalc - FTBFS: strip: Unable to recognise the format of the input file

2006-10-31 Thread Bastian Blank
Package: rpncalc
Version: 1.36
Severity: serious

There was an error while trying to autobuild your package:

 Automatic build of rpncalc_1.36 on debian-31.osdl.marist.edu by sbuild/s390 85
[...]
 make[1]: Entering directory `/build/buildd/rpncalc-1.36'
 install -d -g root -o root -m 755 
 /build/buildd/rpncalc-1.36/debian/tmp/usr/bin
 install-g root -o root -m 755 -s rpncalc 
 /build/buildd/rpncalc-1.36/debian/tmp/usr/bin
 strip: Unable to recognise the format of the input file 
 `/build/buildd/rpncalc-1.36/debian/tmp/usr/bin/rpncalc'
 install: strip failed
 make[1]: *** [install] Error 1
 make[1]: Leaving directory `/build/buildd/rpncalc-1.36'
 make: *** [binary-arch] Error 2
 **
 Build finished at 20061030-1911
 FAILED [dpkg-buildpackage died]


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



Bug#394928: marked as done (dietlibc - uses old select on powerpc wich is not longer implemented)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 00:17:59 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#394928: fixed in dietlibc 0.30-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: dietlibc
Version: 0.30-2
Severity: grave

dietlibc uses the old select syscall instead of the _newselect one.
select is not longer implemented on powerpc. Just use _newselect
unconditionaly on all linux arches.

Bastian

-- 
Deflector shields just came on, Captain.

---End Message---
---BeginMessage---
Source: dietlibc
Source-Version: 0.30-4

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

dietlibc-doc_0.30-4_all.deb
  to pool/main/d/dietlibc/dietlibc-doc_0.30-4_all.deb
dietlibc_0.30-4.diff.gz
  to pool/main/d/dietlibc/dietlibc_0.30-4.diff.gz
dietlibc_0.30-4.dsc
  to pool/main/d/dietlibc/dietlibc_0.30-4.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.
Gerrit Pape [EMAIL PROTECTED] (supplier of updated dietlibc 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, 31 Oct 2006 07:53:57 +
Source: dietlibc
Binary: dietlibc-doc dietlibc dietlibc-dev
Architecture: all source
Version: 0.30-4
Distribution: unstable
Urgency: high
Maintainer: Gerrit Pape [EMAIL PROTECTED]
Changed-By: Gerrit Pape [EMAIL PROTECTED]
Description: 
 dietlibc-dev - diet libc - a libc optimized for small size
 dietlibc-doc - diet libc documentation - a libc optimized for small size
Closes: 394928
Changes: 
 dietlibc (0.30-4) unstable; urgency=high
 .
   * debian/diff/select.diff: remove again; doesn't work for all archs.
   * debian/diff/ppc-select.diff: new; use syscall _newselect instead of
 select on ppc (closes: #394928).
Files: 
 1ebfa37823efce4fc8576dc626fc9ee2 554 devel optional dietlibc_0.30-4.dsc
 d64ed9e858e35fc88b388631b4625145 13282 devel optional dietlibc_0.30-4.diff.gz
 5a959ffb392f09405dbff57085c339b8 48208 doc optional dietlibc-doc_0.30-4_all.deb

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

iD8DBQFFRwSYGJoyQbxwpv8RAqnEAJ9AGBiXcZntwY9iLvTAfoBaKg1H+gCffkHj
xSpWd3vbh9khZ6ztTDng+L0=
=6OvL
-END PGP SIGNATURE-

---End Message---


Bug#396099: marked as done (CVE-2006-5449: Ingo Folder Name Shell Command Injection Vulnerability)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 00:34:21 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#396099: fixed in ingo1 1.1.2-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: ingo1
tags: security
severity: grave

A vulnerability has been found in ingo:

procmail in Ingo H3 before 1.1.2 Horde module allows remote
authenticated users to execute arbitrary commands via shell
metacharacters in the mailbox destination of a filter rule.


This is fixed in 1.1.2. See
http://secunia.com/advisories/22482
for details.

Please mention the CVE id in the changelog.

---End Message---
---BeginMessage---
Source: ingo1
Source-Version: 1.1.2-1

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

ingo1_1.1.2-1.diff.gz
  to pool/main/i/ingo1/ingo1_1.1.2-1.diff.gz
ingo1_1.1.2-1.dsc
  to pool/main/i/ingo1/ingo1_1.1.2-1.dsc
ingo1_1.1.2-1_all.deb
  to pool/main/i/ingo1/ingo1_1.1.2-1_all.deb
ingo1_1.1.2.orig.tar.gz
  to pool/main/i/ingo1/ingo1_1.1.2.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.
Lionel Elie Mamane [EMAIL PROTECTED] (supplier of updated ingo1 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: RIPEMD160

Format: 1.7
Date: Tue, 31 Oct 2006 09:24:02 +0100
Source: ingo1
Binary: ingo1
Architecture: source all
Version: 1.1.2-1
Distribution: unstable
Urgency: high
Maintainer: Horde Maintainers [EMAIL PROTECTED]
Changed-By: Lionel Elie Mamane [EMAIL PROTECTED]
Description: 
 ingo1  - email filter component for Horde Framework
Closes: 396099
Changes: 
 ingo1 (1.1.2-1) unstable; urgency=high
 .
   * New upstream version:
 - Fix remote autenticated user arbitrary command execution
   via shell metacharacters in mailbox name (closes: #396099)
   This is CVE-2006-5449.
   * Bump up Standards-Version
Files: 
 cc2e3b1faf644d6e13b573ba5eea6f6b 679 web optional ingo1_1.1.2-1.dsc
 dc9dbfe52df5b922ec852b1267df5130 1342239 web optional ingo1_1.1.2.orig.tar.gz
 c02bc0bb40d27eea843aeff94320275b 5149 web optional ingo1_1.1.2-1.diff.gz
 187de2d65c81a44029fc91f460f62845 1394062 web optional ingo1_1.1.2-1_all.deb

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

iEYEAREDAAYFAkVHCF0ACgkQscRzFz57S3O2WQCgwN/eOryNeDV58SXADC7BhJ8r
lJoAnAlurUYtj4jphPWp0bEqc/f6c8Tz
=S0PC
-END PGP SIGNATURE-

---End Message---


Bug#396330: php4-ps - FTBFS: You must run this as root in build target

2006-10-31 Thread Bastian Blank
Package: php4-ps
Version: 1.3.4-1
Severity: serious

There was an error while trying to autobuild your package:

 Automatic build of php4-ps_1.3.4-1 on debian-31.osdl.marist.edu by 
 sbuild/s390 85
[...]
  debian/rules build
 xsltproc --nonet --novalid debian/changelog.xsl package.xml  debian/Changelog
 touch build-stamp
 dh_testdir
 dh_testroot
 dh_testroot: You must run this as root (or use fakeroot).
 make: *** [clean-v4] Error 1
 **
 Build finished at 20061031-0327
 FAILED [dpkg-buildpackage died]


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



Bug#396334: libcommons-jexl-java: FTBFS: Error running jikes compiler

2006-10-31 Thread Julien Danjou
Package: libcommons-jexl-java
Version: 1.0-4
Severity: serious

Hello,

There was a problem while autobuilding your package:

 Automatic build of libcommons-jexl-java_1.0-4 on avidan by sbuild/i386 98
 Build started at 20061031-0825
 **
...
  debian/rules build
 test -x debian/rules
 mkdir -p .
 /usr/bin/make -f debian/rules reverse-config
 make[1]: Entering directory `/build/buildd/libcommons-jexl-java-1.0'
 make[1]: Nothing to be done for `reverse-config'.
 make[1]: Leaving directory `/build/buildd/libcommons-jexl-java-1.0'
 if [ debian/stamp-patched = reverse-patches ]; then rm -f 
 debian/stamp-patched; fi
 patches: debian/patches/01_jar_without_tests.patch
 Trying patch debian/patches/01_jar_without_tests.patch at level 1 ... 0 ... 
 success.
 if [ debian/stamp-patched != reverse-patches ]; then touch 
 debian/stamp-patched; fi
 if [ debian/stamp-patched != reverse-patches ] ; then \
   /usr/bin/make -f debian/rules update-config ; \
   fi
 make[1]: Entering directory `/build/buildd/libcommons-jexl-java-1.0'
 make[1]: Nothing to be done for `update-config'.
 make[1]: Leaving directory `/build/buildd/libcommons-jexl-java-1.0'
 cd .  /usr/lib/jvm/java-gcj//bin/java -classpath 
 /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/junit.jar:/usr/share/java/commons-logging.jar:/usr/lib/jvm/java-gcj//lib/tools.jar
   -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true 
 -Dcompile.optimize=true  -Dbuild.compiler=jikes  -propertyfile 
 /build/buildd/libcommons-jexl-java-1.0/debian/ant.properties jar
 Buildfile: build.xml
 
 init:
 [mkdir] Created dir: /build/buildd/libcommons-jexl-java-1.0/target/lib
 
 get-deps:
 
 compile:
 [mkdir] Created dir: /build/buildd/libcommons-jexl-java-1.0/target/classes
 [javac] Compiling 82 source files to 
 /build/buildd/libcommons-jexl-java-1.0/target/classes
 
 BUILD FAILED
 /build/buildd/libcommons-jexl-java-1.0/build.xml:46: Error running jikes 
 compiler
 
 Total time: 2 seconds
 make: *** [debian/stamp-ant-build] Error 1
 **
 Build finished at 20061031-0827
 FAILED [dpkg-buildpackage died]

-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD



Bug#395047: marked as done (haskell-network - FTBFS: setup-ghc: dist/build/Network_split: getDirectoryContents: does not exist (No such file or directory))

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 01:08:22 -0800
with message-id [EMAIL PROTECTED]
and subject line haskell-network - FTBFS: setup-ghc: dist/build/Network_split: 
getDirectoryContents: does not exist (No such file or 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: haskell-network
Version: 2.0-1
Severity: serious

There was an error while trying to autobuild your package:

 Automatic build of haskell-network_2.0-1 on debian-31 by sbuild/s390 85
[...]
 Preprocessing library network-2.0...
 Building network-2.0...
 setup-ghc: dist/build/Network_split: getDirectoryContents: does not exist (No 
 such file or directory)
 
 make: *** [build-stamp] Error 1
 **
 Build finished at 20061024-0502
 FAILED [dpkg-buildpackage died]

---End Message---
---BeginMessage---
Version: 2.0-2

This bug appears to have been fixed in unstable.

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


Bug#396277: allows creating any file as root

2006-10-31 Thread Steve Kemp
On Mon, Oct 30, 2006 at 10:56:28PM +0100, Marco d'Itri wrote:

 By creating a /tmp/start_thttpd symlink a local attacker will be able to
 create/touch any file as root.

  Thanks for the report.  Once I get a CVE identifier allocated I'll
 handle an update for Sarge.

  Daniel if you have a preferred patch that would be appreciated,
 otherwise I'll come up with a solution and add it to this bug.

Steve
-- 


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



Processed: Re: [Pkg-kde-extras] Bug#396251: digikamimageplugins: No plugins present

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 396251 grave
Bug#396251: digikamimageplugins: No plugins present
Severity set to `grave' from `important'

 tags 396251 pending
Bug#396251: digikamimageplugins: No plugins present
There were no tags set.
Tags added: pending

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


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



Bug#395247: (fwd) Bug#395247: [s390] System clock runs wild (in hercules emulator)

2006-10-31 Thread maximilian attems
could you please have a look at this bug?
thanks

- Forwarded message from Frans Pop [EMAIL PROTECTED] -

X-Original-To: [EMAIL PROTECTED]
X-Original-To: debian-kernel@lists.debian.org
Subject: Bug#395247: [s390] System clock runs wild (in hercules emulator)
Date: Tue, 24 Oct 2006 22:31:54 +0200
From: Frans Pop [EMAIL PROTECTED]
To: [EMAIL PROTECTED]

Package: linux-2.6
Version: 2.6.18-2
Severity: grave

After booting my hercules emulator with 2.6.18, I noticed some errors during 
a packages upgrade, like:
tar: ./config: time stamp 2006-10-27 10:52:22.00126 is 4290.653417 s in the 
future

Further investigation showed that the system clock in running wild:
$ date
Fri Oct 27 05:36:58 CEST 2006
$ date
Fri Oct 27 05:41:40 CEST 2006
$ date
Fri Oct 27 06:25:24 CEST 2006
$ date
Fri Oct 27 09:01:09 CEST 2006
$ date
Fri Oct 27 18:19:04 CEST 2006

These 'date' commands were given within 15-20 minutes or so. Actual time 
when the emulator was started was around 2006-10-24 17:30.

After rebooting the emulator with 2.6.17-9, the problem was gone.

This series from a later boot with 2.6.18, taken within 2 minutes, is even 
crazier.
It shows the clock jumping all over the place (real time Oct 24, 22:30):
$ date
Wed Oct 25 09:10:10 CEST 2006
$ date
Wed Oct 25 08:06:19 CEST 2006
$ date
Wed Oct 25 09:26:43 CEST 2006
$ date
Wed Oct 25 09:32:17 CEST 2006
$ date
Wed Oct 25 09:35:45 CEST 2006
$ date
Wed Oct 25 09:40:40 CEST 2006
$ date
Wed Oct 25 08:32:08 CEST 2006
$ date
Wed Oct 25 09:49:38 CEST 2006
$ date
Wed Oct 25 09:51:44 CEST 2006
$ date
Wed Oct 25 08:41:32 CEST 2006
$ date
Wed Oct 25 08:42:45 CEST 2006
$ date
Wed Oct 25 08:43:59 CEST 2006

I'm running hercules 3.04.1 on an EM64T host system. The system clock on the 
host runs normally.



- End forwarded message -
-- 
maks


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



Bug#396345: tomboy: Tomboy does not start

2006-10-31 Thread Andrey Fedoseev
Package: tomboy
Version: 0.4.1-2
Severity: grave
Justification: renders package unusable


Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Andrey Fedoseev [EMAIL PROTECTED]
To: Debian Bug Tracking System [EMAIL PROTECTED]
Subject: tomboy: Tomboy does not start
Message-ID: [EMAIL PROTECTED]
X-Mailer: reportbug 3.30
Date: Tue, 31 Oct 2006 15:33:02 +0500

Package: tomboy
Version: 0.4.1-2
Severity: grave
Justification: renders package unusable

When trying to run tomboy I get:

[START]
** ERROR **: file threadpool.c: line 990 (mono_thread_pool_init): 
assertion failed: (async_call_klass)
aborting...

=
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=

Stacktrace:

Native stacktrace:

/usr/lib/libmono.so.0 [0xa7df0dd2]
/usr/lib/libmono.so.0 [0xa7dc46ec]
[0xe440]
/lib/tls/i686/cmov/libc.so.6(abort+0x109) [0xa7b7dfb9]
/usr/lib/libglib-2.0.so.0(g_logv+0x454) [0xa7d10114]
/usr/lib/libglib-2.0.so.0(g_log+0x29) [0xa7d10149]
/usr/lib/libglib-2.0.so.0(g_assert_warning+0x77) [0xa7d101c7]
/usr/lib/libmono.so.0 [0xa7e8dd62]
/usr/lib/libmono.so.0(mono_runtime_init+0x23) [0xa7e95505]
/usr/lib/libmono.so.0 [0xa7dc5b74]
/usr/lib/libmono.so.0(mono_main+0x1388) [0xa7de1fe5]
mono [0x8048522]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) 
[0xa7b68ea8]
mono [0x8048471]

Debug info from gdb:

(no debugging symbols found)
Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1481300288 (LWP 18461)]
[New Thread -1484702800 (LWP 18462)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xe410 in __kernel_vsyscall ()
  2 Thread -1484702800 (LWP 18462)  0xe410 in __kernel_vsyscall ()
  1 Thread -1481300288 (LWP 18461)  0xe410 in __kernel_vsyscall ()

Thread 2 (Thread -1484702800 (LWP 18462)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xa7cbf016 in __nanosleep_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xa7ec8b4b in mono_type_full_name () from /usr/lib/libmono.so.0
#3  0xa7cb9240 in start_thread () from 
/lib/tls/i686/cmov/libpthread.so.0
#4  0xa7c1f27e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1481300288 (LWP 18461)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xa7be19a9 in fork () from /lib/tls/i686/cmov/libc.so.6
#2  0xa7cc05b4 in fork () from /lib/tls/i686/cmov/libpthread.so.0
#3  0xa7d320c9 in g_spawn_error_quark () from /usr/lib/libglib-2.0.so.0
#4  0xa7d32c9f in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
#5  0xa7d33115 in g_spawn_command_line_sync () from 
/usr/lib/libglib-2.0.so.0
#6  0xa7df0e9a in mono_debugger_run_finally () from 
/usr/lib/libmono.so.0
#7  0xa7dc46ec in mono_jit_thread_attach () from /usr/lib/libmono.so.0
#8  signal handler called
#9  0xe410 in __kernel_vsyscall ()
#10 0xa7b7c821 in raise () from /lib/tls/i686/cmov/libc.so.6
#11 0xa7b7dfb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#12 0xa7d10114 in g_logv () from /usr/lib/libglib-2.0.so.0
#13 0xa7d10149 in g_log () from /usr/lib/libglib-2.0.so.0
#14 0xa7d101c7 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
#15 0xa7e8dd62 in mono_thread_stop () from /usr/lib/libmono.so.0
#16 0xa7e95505 in mono_runtime_init () from /usr/lib/libmono.so.0
#17 0xa7dc5b74 in mono_jit_thread_attach () from /usr/lib/libmono.so.0
#18 0xa7de1fe5 in mono_main () from /usr/lib/libmono.so.0
#19 0x08048522 in ?? ()
#20 0x0002 in ?? ()
#21 0xafeb23f4 in ?? ()
#22 0xafeb2378 in ?? ()
#23 0x0804854f in ?? ()
#24 0xa7b5ec8c in ?? () from /lib/tls/i686/cmov/libc.so.6
#25 0xafeb2380 in ?? ()
#26 0xafeb23c8 in ?? ()
#27 0xa7b68ea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#28 0xa7b68ea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#29 0x08048471 in ?? ()
#0  0xe410 in __kernel_vsyscall ()

Aborted
[END]

I had tomboy (v0.3xxx) running fine before I updated some packages 
(I don't remember exactly which packages were updated) a couple days 
ago. After that I updated tomboy to 0.4.1-2 and it didn't help.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 

Bug#394211: ganglia-monitor-core: FTBFS, uses PAGE_SHIFT

2006-10-31 Thread Steve McIntyre
On Sun, Oct 29, 2006 at 08:13:43AM +, Stuart Teasdale wrote:

On 29 Oct 2006, at 00:21, Steve McIntyre wrote:

Stu Teasdale wrote:

Cheers. Ideally I'd just uplaod a neer version which is unaffected,
but this seems to have licencing issues as it stands.

Hmmm? Could you clarify that?

The project is BSD licenced, but there seem to be individual files in  
the 3.0 tree that are licenced under GPL and Artistic. I'm trying to  
get upstream to clarify ownership of each source file atm and confirm  
if these licences are in fact acceptible together.

Ouch :-(

OK, thanks for the response...

-- 
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
Is there anybody out there?


signature.asc
Description: Digital signature


Bug#396350: FTBFS: KeyError: 'SYSMIDI':

2006-10-31 Thread Goswin von Brederlow
Package: ardour
Severity: serious
Justification: no longer builds from source

Hi,

building ardour fails with

Checking for C function getmntent()... no
KeyError: 'SYSMIDI':
  File SConstruct, line 724:
SConscript (subdir + '/SConscript')
  File /usr/lib/scons/SCons/Script/SConscript.py, line 557:
return apply(method, args, kw)
  File /usr/lib/scons/SCons/Script/SConscript.py, line 494:
return apply(_SConscript, [self.fs,] + files, {'exports' : exports})
  File /usr/lib/scons/SCons/Script/SConscript.py, line 226:
exec _file_ in call_stack[-1].globals
  File libs/midi++/SConscript, line 35:
if env['SYSMIDI'] == 'CoreMIDI':
  File /usr/lib/scons/SCons/Environment.py, line 295:
return self._dict[key]
make: *** [debian/stamp-scons-build] Error 2

Build log is attached.

MfG
Goswin

-- 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.8-frosties-2
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
 fakeroot debian/rules clean
test -x debian/rules
test `id -u` = 0
for i in ./tools/config.guess   ; do \
if test -e $i.cdbs-orig ; then \
mv $i.cdbs-orig $i ; \
fi ; \
done
# reverse-config must be first
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory `/home/mrvn/build/ardour_0.99.3-1/ardour-0.99.3'
for i in ./tools/config.guess   ; do \
if test -e $i.cdbs-orig ; then \
mv $i.cdbs-orig $i ; \
fi ; \
done
make[1]: Leaving directory `/home/mrvn/build/ardour_0.99.3-1/ardour-0.99.3'
if [ -d . ] ; then \
  cd .  QUILT_PATCHES=patches quilt --quiltrc /dev/null pop -a -R || 
test $? = 2 ; \
fi 
No patch removed
if [ -n patches ] ; then \
  if [ -L ./patches ] ; then \
rm ./patches ; \
  fi ; \
fi
rm -rf ./.pc
rm -f debian/stamp-patch*
dh_clean 
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory `/home/mrvn/build/ardour_0.99.3-1/ardour-0.99.3'
for i in ./tools/config.guess   ; do \
if test -e $i.cdbs-orig ; then \
mv $i.cdbs-orig $i ; \
fi ; \
done
make[1]: Leaving directory `/home/mrvn/build/ardour_0.99.3-1/ardour-0.99.3'
mkdir -p /home/mrvn/build/ardour_0.99.3-1/ardour-0.99.3/debian/tmp/
scons  --clean
scons: Reading SConscript files ...
Checking for C header file alsa/asoundlib.h... no
Checking for C header file 
/System/Library/Frameworks/CoreMIDI.framework/Headers/CoreMIDI.h... no
system triple: x86_64-unknown-linux-gnu

***
detected DIST_TARGET = x86_64
***

Checking for internationalization support ...
Checking for C header file libintl.h... no
Checking for C header file 
/System/Library/Frameworks/CoreAudio.framework/Versions/A/Headers/CoreAudio.h...
 no
Checking for C function posix_memalign()... no
Did not find posix_memalign(), using malloc
Checking for C function getmntent()... no
KeyError: 'SYSMIDI':
  File SConstruct, line 727:
SConscript (subdir + '/SConscript')
  File /usr/lib/scons/SCons/Script/SConscript.py, line 557:
return apply(method, args, kw)
  File /usr/lib/scons/SCons/Script/SConscript.py, line 494:
return apply(_SConscript, [self.fs,] + files, {'exports' : exports})
  File /usr/lib/scons/SCons/Script/SConscript.py, line 226:
exec _file_ in call_stack[-1].globals
  File libs/midi++/SConscript, line 35:
if env['SYSMIDI'] == 'CoreMIDI':
  File /usr/lib/scons/SCons/Environment.py, line 295:
return self._dict[key]
make: [scons-clean] Error 2 (ignored)
rm -rf /home/mrvn/build/ardour_0.99.3-1/ardour-0.99.3/debian/tmp/ 
debian/stamp-scons-build
rm -rf config.log scache.conf .sconf_temp .sconsign.dblite
 debian/rules build
test -x debian/rules
mkdir -p .
# reverse-config must be first
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory `/home/mrvn/build/ardour_0.99.3-1/ardour-0.99.3'
for i in ./tools/config.guess   ; do \
if test -e $i.cdbs-orig ; then \
mv $i.cdbs-orig $i ; \
fi ; \
done
make[1]: Leaving directory `/home/mrvn/build/ardour_0.99.3-1/ardour-0.99.3'
if [ -n patches ] ; then \
  if [ -L ./patches ] ; then : ; else \
(cd .; ln -s 
/home/mrvn/build/ardour_0.99.3-1/ardour-0.99.3/debian/patches patches) ; \
  fi ; \
fi
# quilt exits with 2 as return when there was nothing to do. 
# That's not an error here (but it's usefull to break loops in crude scripts)
cd .  QUILT_PATCHES=patches quilt --quiltrc /dev/null push -a || test $? = 2
Applying patch 22_remove-atomic-impl-sparc.patch
patching file libs/pbd/pbd/atomic.h

Applying patch 30_new-config.guess.patch
patching file tools/config.guess

Applying patch 31_add-O2-to-DEBUG-CFLAGS.patch

Bug#396351: FTBFS: /usr/bin/install: cannot create regular file `/sbin/apcupsd': Permission denied

2006-10-31 Thread Goswin von Brederlow
Package: apcupsd
Version: 3.12.4-1
Severity: serious
Justification: no longer builds from source

Hi,

seems like the make install does not install into debian/apcupsd but into /.
Build log attached.

MfG
Goswin

-- 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.8-frosties-2
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
 fakeroot debian/rules clean
rm -f patch-stamp 
dh_testdir
dh_testroot
rm -f build-arch-stamp build-indep-stamp #CONFIGURE-STAMP#
# Add here commands to clean up after the build process.
/usr/bin/make distclean
make[1]: Entering directory `/home/mrvn/build/apcupsd_3.12.4-1/apcupsd-3.12.4'
make[1]: *** No rule to make target `distclean'.  Stop.
make[1]: Leaving directory `/home/mrvn/build/apcupsd_3.12.4-1/apcupsd-3.12.4'
make: [clean] Error 2 (ignored)
cp -f /usr/share/misc/config.sub config.sub
cp -f /usr/share/misc/config.guess config.guess
dh_clean 
 debian/rules build
test -d debian/patched || install -d debian/patched
applying patch debian/patches/config.guess.dpatch... ok.
applying patch debian/patches/config.sub.dpatch... ok.
applying patch debian/patches/client.c.dpatch... ok.
mv -f patch-stampT patch-stamp
dh_testdir
# Add here commands to configure the package.
#CFLAGS=-Wall -g -O2 -Wl,-z,defs ./configure --host=x86_64-linux-gnu 
--build=x86_64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info
CFLAGS=-Wall -g -O2 -Wl,-z,defs ./configure --prefix=/usr --sbindir=/sbin 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info  
--enable-pthreads --with-libwrap --enable-cgi --enable-usb --enable-net 
--enable-snmp --enable-test --with-cgi-bin=\${prefix}/lib/cgi-bin/apcupsd 
--enable-powerflute --enable-nls --with-catgets --with-pid-dir=/var/run 
--with-log-dir=/var/log --with-lock-dir=/var/lock 
--with-pwrfail-dir=/etc/apcupsd --disable-install-distdir --with-nis-port=3551 
--with-nisip=127.0.0.1 --enable-master-slave 
--with-css-dir=\${prefix}/../etc/apcupsd/
checking for true... /bin/true
checking for false... /bin/false
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether gcc and cc understand -c and -o together... yes
checking for egrep... grep -E
checking whether gcc needs -traditional... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking for library containing strerror... none required
checking for g++... /usr/bin/g++
checking for pthreads... checking for shutdown... /sbin/shutdown
checking for mail... no
configure: WARNING: mail program not found !
checking for wall... /usr/bin/wall
checking for sh... /bin/sh
checking for gmake... no
checking for pmake... /usr/bin/pmake
checking for makedepend... /usr/bin/makedepend
checking for ranlib... /usr/bin/ranlib
checking for libtool... /usr/bin/libtool
checking for etags... no
checking for etags... no
checking for rm... /bin/rm
checking for cp... /bin/cp
checking for echo... /bin/echo
checking for ln... /bin/ln
checking for sed... /bin/sed
checking for ar... /usr/bin/ar
checking for mv... /bin/mv
checking for abort... yes
checking for fork... yes
checking for calloc... yes
checking for getpid... yes
checking for ioctl... yes
checking for kill... yes
checking for rewind... yes
checking for select... yes
checking for setsid... yes
checking for signal... yes
checking for strerror... yes
checking for strncmp... yes
checking for strncpy... yes
checking for tcgetattr... yes
checking for vfprintf... yes
checking for setpgrp... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for nanosleep... yes
checking for usleep... yes
checking for syslog... yes
checking for strftime... yes
checking whether setpgrp takes no argument... yes
checking for socket... yes
using libc's socket
checking for gethostname... yes
using libc's gethostname
checking for socklen_t... yes
checking for gethostbyname... yes
using libc's resolver
checking for gettext... yes
using libc's gettext
checking for inet_addr... yes
using libc's inet_addr
checking for strchr... yes
using libc's strchr
checking for strstr... yes
checking for strcasecmp... yes
checking for memmove... yes
checking for getopt_long... yes
checking for inet_pton... yes
checking for localtime_r... yes

Processed: tagging 393396

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.22
 tags 393396 + pending
Bug#393396: Source package contains non-free IETF RFC/I-D's
Tags were: etch-ignore
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#396352: azureus: fails to start, NoClassDefFoundError (org/eclipse/swt/widgets/Display)

2006-10-31 Thread Carsten Kosthorst
Package: azureus
Version: 2.5.0.0-1
Severity: grave
Justification: renders package unusable

Hi all,

azureus fails to start, giving the following error message:

Exception in thread main java.lang.NoClassDefFoundError:
org/eclipse/swt/widgets/Display
   at org.gudy.azureus2.ui.swt.Main.init(Main.java:147)
   at org.gudy.azureus2.ui.swt.Main.main(Main.java:162)

I reinstalled azureus, libcommons-cli-java, liblog4j1.2-java, libseda-java and
libswt-gtk-3.2-java, but that didn't help.

Also the installation of java-package didn't help.

Bye,

   Carsten

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

Versions of packages azureus depends on:
ii  libcommons-cli-java   1.0-8  API for working with the command l
ii  liblog4j1.2-java  1.2.13-2   Logging library for java
ii  libseda-java  3.0-3  the Staged Event-Driven Architectu
ii  libswt-gtk-3.2-java   3.2.1-1Standard Widget Toolkit for GTK Ja
ii  sun-java5-jre [java2-runtime] 1.5.0-08-1 Sun Java(TM) Runtime Environment (

Versions of packages azureus recommends:
pn  java-package  none (no description available)

-- no debconf information


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



Bug#396360: CVE-2006-4513 Abiword likely vulnerable to integer overflows

2006-10-31 Thread Lubomir Kundrak
Package: abiword
Version: 2.2.7-3sarge2
Tags: security, upstream
Severity: grave 

Abiword likely uses version of VW library (see #396256) vulnerable to
two integer overflow conditions. See CVE text for more details.

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4513

-- 
Lubomir Kundrak (Red Hat Security Response Team)



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



Bug#396256: CVE-2006-4513: wvWare Multiple Integer Overflow Vulnerabilities

2006-10-31 Thread Lubomir Kundrak
This also affects AbiWord package. In contrast to what CVE candidate
CVE-2006-4513 text says, this does _not_ affect KOffice's KWord.

-- 
Lubomir Kundrak (Red Hat Security Response Team)



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



Bug#396359: FTBFS: scons: building terminated because of errors.

2006-10-31 Thread Goswin von Brederlow
Package: cheesetracker
Version: 0.9.9-8
Severity: serious
Justification: no longer builds from source

Hi,

when building cheesetracker it mysteriously fails with

scons: Building targets ...
g++ -o cheesetracker/interface__QT/instrument_edit.o -c 
-I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2 -I/usr/include 
-trigraphs -DPOSIX_ENABLED -O3 -ffast-math -fno-strict-aliasing 
-DLADSPA_ENABLED -DOSS_ENABLED -DJACK_ENABLED -DALSA_ENABLED 
-I/usr/include/alsa -Icommon/ -Icommon/defines/ -I/usr/include/qt3 -DQT_NO_EMIT 
-Icommon -I. -Icommon/defines -Icheesetracker -Icheesetracker/trackercore 
-Icheesetracker/loaders -Icheesetracker/savers -Icheesetracker/interface_binds 
cheesetracker/interface__QT/instrument_edit.cpp
scons: *** [cheesetracker/interface__QT/instrument_edit.o] Error 1
scons: building terminated because of errors.
make: *** [build-stamp] Error 2

Build log is attached.

MfG
Goswin

-- 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.8-frosties-2
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
scons -c
scons: Reading SConscript files ...
Checking for libdl...
Found dlfcn.h in /usr/include
Detecting if PKG-CONFIG is installed... 
0.21
pkg-config found!
Checking for libsigc++-1.2...
1.2.7
libsigc++-1.2 found!
QT Check:
$QTDIR not found, you could define this pointing to a proper QT location if not 
found
I will try to check if you have Qt in a bunch of paths..
Looking for QT 3.x Includes:
/usr/include/qt3
Checking QT version.. 

#define QT_VERSION_STR   3.3.7

Looking for QT 3.x Libraries:
using: -lqt-mt
Looking for QT 3.x 'moc' Binary:
found moc command: moc-qt3
QT was found!

Checking for JACK...
JACK found!
Checking for ALSA...
ALSA found!
Detecting if OSS exists on the system..
OSS was found.
rm: cannot remove `test.cpp': No such file or directory
Dependency check successful, writing cache
detected moc-qt3
scons: done reading SConscript files.
scons: Cleaning targets ...
scons: done cleaning targets.
find . -type f -iname '.sconsign' -exec rm {} \;
rm -f *.pyc test
rm -f config_errors.log detect_cache.py
rm -f .sconsign.dblite 
rm -f cheesetracker/docs/DEADJOE
dh_clean
 debian/rules build
dh_testdir
# Add here commands to configure the package.
#./configure 
--prefix=/home/mrvn/build/cheesetracker_0.9.9-8/cheesetracker-0.9.9/debian/cheesetracker/usr
touch configure-stamp
dh_testdir
# Add here commands to compile the package.
scons
scons: Reading SConscript files ...
Checking for libdl...
Found dlfcn.h in /usr/include
Detecting if PKG-CONFIG is installed... 
0.21
pkg-config found!
Checking for libsigc++-1.2...
1.2.7
libsigc++-1.2 found!
QT Check:
$QTDIR not found, you could define this pointing to a proper QT location if not 
found
I will try to check if you have Qt in a bunch of paths..
Looking for QT 3.x Includes:
/usr/include/qt3
Checking QT version.. 

#define QT_VERSION_STR   3.3.7

Looking for QT 3.x Libraries:
using: -lqt-mt
Looking for QT 3.x 'moc' Binary:
found moc command: moc-qt3
QT was found!

Checking for JACK...
JACK found!
Checking for ALSA...
ALSA found!
Detecting if OSS exists on the system..
OSS was found.
rm: cannot remove `test.cpp': No such file or directory
Dependency check successful, writing cache
detected moc-qt3
scons: done reading SConscript files.
scons: Building targets ...
g++ -o cheesetracker/interface__QT/instrument_edit.o -c 
-I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2 -I/usr/include 
-trigraphs -DPOSIX_ENABLED -O3 -ffast-math -fno-strict-aliasing 
-DLADSPA_ENABLED -DOSS_ENABLED -DJACK_ENABLED -DALSA_ENABLED 
-I/usr/include/alsa -Icommon/ -Icommon/defines/ -I/usr/include/qt3 -DQT_NO_EMIT 
-Icommon -I. -Icommon/defines -Icheesetracker -Icheesetracker/trackercore 
-Icheesetracker/loaders -Icheesetracker/savers -Icheesetracker/interface_binds 
cheesetracker/interface__QT/instrument_edit.cpp
scons: *** [cheesetracker/interface__QT/instrument_edit.o] Error 1
scons: building terminated because of errors.
make: *** [build-stamp] Error 2


Bug#396363: FTBFS: Makefile:69: *** target pattern contains no `%'. Stop.

2006-10-31 Thread Goswin von Brederlow
Package: grace
Version: 1:5.1.20-3
Severity: serious
Justification: no longer builds from source

Hi,

when building grace I get the following error:

make[2]: Entering directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20/src'
Makefile:69: *** target pattern contains no `%'.  Stop.
make[2]: Leaving directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20/src'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
make: *** [common-install-impl] Error 2

Build log is attached.

MfG
Goswin


-- 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.8-frosties-2
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
 fakeroot debian/rules clean
test -x debian/rules
test `id -u` = 0
for i in ./ac-tools/config.guess ./ac-tools/config.sub  ; do \
if test -e $i.cdbs-orig ; then \
mv $i.cdbs-orig $i ; \
fi ; \
done
dh_clean 
/usr/bin/make -C . -k distclean
make[1]: Entering directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
Makefile:7: Make.conf: No such file or directory

Please re-run ./configure

make[1]: *** [Make.conf] Error 1
make[1]: Failed to remake makefile `Make.conf'.
rm -f config.log config.status config.cache config.h Make.conf
make[1]: Leaving directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
make: [makefile-clean] Error 2 (ignored)
rm -f debian/stamp-makefile-build
rm -f debian/stamp-autotools-files
# reverse-config must be first
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
for i in ./ac-tools/config.guess ./ac-tools/config.sub  ; do \
if test -e $i.cdbs-orig ; then \
mv $i.cdbs-orig $i ; \
fi ; \
done
make[1]: Leaving directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
if [ -d . ] ; then \
  cd .  QUILT_PATCHES=patches quilt --quiltrc /dev/null pop -a -R || 
test $? = 2 ; \
fi 
No patch removed
if [ -n patches ] ; then \
  if [ -L ./patches ] ; then \
rm ./patches ; \
  fi ; \
fi
rm -rf ./.pc
rm -f debian/stamp-patch*
rm -f debian/grace*.png
 debian/rules build
test -x debian/rules
mkdir -p .
# reverse-config must be first
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
for i in ./ac-tools/config.guess ./ac-tools/config.sub  ; do \
if test -e $i.cdbs-orig ; then \
mv $i.cdbs-orig $i ; \
fi ; \
done
make[1]: Leaving directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
if [ -n patches ] ; then \
  if [ -L ./patches ] ; then : ; else \
(cd .; ln -s 
/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20/debian/patches patches) ; \
  fi ; \
fi
# quilt exits with 2 as return when there was nothing to do. 
# That's not an error here (but it's usefull to break loops in crude scripts)
cd .  QUILT_PATCHES=patches quilt --quiltrc /dev/null push -a || test $? = 2
No patches in series
touch debian/stamp-patched
/usr/bin/make -f debian/rules update-config
make[1]: Entering directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
if test -e /usr/share/misc/config.guess ; then \
for i in ./ac-tools/config.guess ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination 
/usr/share/misc/config.guess $i ; \
fi ; \
done ; \
fi
if test -e /usr/share/misc/config.sub ; then \
for i in ./ac-tools/config.sub ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination 
/usr/share/misc/config.sub $i ; \
fi ; \
done ; \
fi
make[1]: Leaving directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
# update-config must be last
if test -e /usr/share/misc/config.guess ; then \
for i in ./ac-tools/config.guess ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination 
/usr/share/misc/config.guess $i ; \
fi ; \
done ; \
fi
if test -e /usr/share/misc/config.sub ; then \
for i in ./ac-tools/config.sub ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination 
/usr/share/misc/config.sub $i ; \
fi ; 

Bug#396240: poker-network: FTBFS: ImportError: No module named gtk

2006-10-31 Thread Loic Dachary

Hi,

I'm a little confused as to how to reproduce the problem. 
Could you send me the part you cut (...) ? 
http://buildd.debian.org/build.php?pkg=poker-network does not show this
build. Can I check it from somewhere else ?

Cheers,

Julien Danjou writes:
  Package: poker-network
  Version: 1.0.29-1
  Severity: serious

-- 
+33 1 76 60 72 81  Loic Dachary mailto:[EMAIL PROTECTED]
http://dachary.org/loic/gpg.txt sip:[EMAIL PROTECTED]


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



Bug#389579: only the apache2 version fails to build

2006-10-31 Thread Filipus Klutiero

Matthew Palmer a écrit :


reassign 389579 libapache2-mod-auth-mysql
thanks

On Mon, Oct 30, 2006 at 06:52:45PM -0500, Filipus Klutiero wrote:
 


Matthew Palmer a écrit :
   


On Sun, Oct 29, 2006 at 01:43:47AM -0400, Filipus Klutiero wrote:
 


This bug is against the libapache-mod-auth-mysql source package, not the
binary package, which has no bug.
   

Well then, please assign the bug to the source package, then.  
 


This is what I'm doing.
   



No you're not.


It is what I was doing.


The 'reassign' command only manipulates the value of the
'binary package' attribute of the bug report.  If you view the bugs page for
the libapache-mod-auth-mysql binary package during the time that you've
reassigned the bug to that package, you will see that the bug shows up in
that package's list -- moreover, it does *not* show up in the
libapache2-mod-auth-mysql package's bug list.
 

Determining whether a bug is assigned to a binary package or to a source 
package of the same name can't be done mechanically. As the BTS is 
mechanical, it doesn't represent things perfectly. It also doesn't care 
about being too exact and simply considers that all bugs are assigned to 
a binary package.


 


At the moment
all you're doing is moving the bug to a binary package that, by your own
acknowledgement, does not contain the bug.
 

Reassigning to a binary package and a source package of the same name 
are two mechanically indistinguishable things.
   



Have you tried assigning a bug to a source package which did *not* have a
binary package of the same name?  What was the result?
 


Yes. See #393592.

 


One needs to use context to determine if the bug is against the source or
binary package.
   



Once you've taught the BTS software about context, you may feel free to
fiddle around.  Until then, please leave the bug alone.

No problem, I didn't intend to spend any more time on this. I'm leaving 
you the responsability to handle this bug report (or to fix it :) ).




Bug#396366: duplicity: fails to install

2006-10-31 Thread Paul Brossier
Package: duplicity
Version: 0.4.2-10+b1
Severity: serious 

0.4.2-10+b1 failed to install with the following message:

$ LANG=C sudo dpkg -i /var/cache/apt/archives/duplicity_0.4.2-10+b1_powerpc.deb
(Reading database ... 177360 files and directories currently installed.)
Preparing to replace duplicity 0.4.2-10+b1 (using 
.../duplicity_0.4.2-10+b1_powerpc.deb) ...
INFO: using old version '/usr/bin/python2.3'
Unpacking replacement duplicity ...
Setting up duplicity (0.4.2-10+b1) ...
INFO: using old version '/usr/bin/python2.3'
pycentral: pycentral pkginstall: duplicity needs unavailable runtime (2.3)
pycentral pkginstall: duplicity needs unavailable runtime (2.3)
dpkg: error processing duplicity (--install):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 duplicity

cheers, piem

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-powerpc
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)

Versions of packages duplicity depends on:
ii  gnupg1.4.5-1 GNU privacy guard - a free PGP rep
ii  libc62.3.6.ds1-7 GNU C Library: Shared libraries
ii  librsync10.9.7-1 Library which implements the rsync
ii  python-central   0.5.9   register and build utility for Pyt
ii  python-gnupginterface0.3.2-9 Python interface to GnuPG (GPG)
ii  python2.32.3.5-16An interactive high-level object-o

duplicity recommends no packages.

-- no debconf information


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



Processed: reassign 396366 to python-central

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.8.14
 reassign 396366 python-central
Bug#396366: duplicity: fails to install
Bug reassigned from package `duplicity' to `python-central'.


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#396345: tomboy: Tomboy does not start

2006-10-31 Thread Andrey Fedoseev
В Втр, 31/10/2006 в 07:46 -0800, Dave Beckett пишет:

  Versions of packages tomboy depends on:
 
  ii  libmono-corlib1.0-cil  1.1.13.8-1Mono core library (1.0)
  ii  libmono-system1.0-cil  1.1.13.8-1Mono System libraries (1.0)
  ii  libmono1.0-cil 1.1.17.1-5Mono libraries (1.0)
  ii  mono-runtime   1.1.13.8-1Mono runtime
 
 You seem to be using at least 2 different versions of the core Mono
 libraries which means your system is inconsistent.
 
 Maybe you could try using the latest version 1.1.18
 

I updated all mono related libs to latest version (1.1.18) and now
tomboy works fine. Thanks.

But maybe you should change dependencies to latest mono libs?

-- 
Regards! Andrey Fedoseev
[EMAIL PROTECTED]



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



Bug#392049: Working version of package

2006-10-31 Thread Nicholas J Humfrey
If you recompile the package with a 2.4 kernel, then it works fine  
(as a temporary solution).

My recompiled packages for i386 are available here:

http://www.aelius.com/~njh/debian/


nick.



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



Bug#396374: FTBFS: Makefile:1841: *** multiple target patterns. Stop.

2006-10-31 Thread Goswin von Brederlow
Package: gcc-m68hc1x
Version: 1:3.3.6+3.1+dfsg-1
Severity: serious
Justification: no longer builds from source

Hi,

when building gcc-m68hc1x I get the following error

cd build  /usr/bin/make all-gcc
make[1]: Entering directory 
`/home/mrvn/build/gcc-m68hc1x_1:3.3.6+3.1+dfsg-1/gcc-m68hc1x-3.3.6+3.1+dfsg/build'
Makefile:1841: *** multiple target patterns.  Stop.
make[1]: Leaving directory 
`/home/mrvn/build/gcc-m68hc1x_1:3.3.6+3.1+dfsg-1/gcc-m68hc1x-3.3.6+3.1+dfsg/build'
make: *** [build-stamp] Error 2

Build log is attached.

MfG
Goswin

-- 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.8-frosties-2
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f 
/home/mrvn/build/gcc-m68hc1x_1:3.3.6+3.1+dfsg-1/gcc-m68hc1x-3.3.6+3.1+dfsg/example.tar.gz
rm -rf build
rm -rf src
rm -f build-stamp configure-stamp unpack-stamp
dh_clean
 debian/rules build
tar xjf gcc-3.3.6.tar.bz2
for i in *.diff* ; do \
  cat $i | patch -p0 ; \
done
patching file gcc-3.3.6/ChangeLog.M68HC11
patching file gcc-3.3.6/gcc/ChangeLog.M68HC11
patching file gcc-3.3.6/gcc/collect2.c
patching file gcc-3.3.6/gcc/combine.c
patching file gcc-3.3.6/gcc/config/divmod.c
patching file gcc-3.3.6/gcc/config/m68hc11/m68hc11-crt0.S
patching file gcc-3.3.6/gcc/config/m68hc11/m68hc11-protos.h
patching file gcc-3.3.6/gcc/config/m68hc11/m68hc11.c
patching file gcc-3.3.6/gcc/config/m68hc11/m68hc11.h
patching file gcc-3.3.6/gcc/config/m68hc11/m68hc11.md
patching file gcc-3.3.6/gcc/config/m68hc11/t-m68hc11-gas
patching file gcc-3.3.6/gcc/config/udivmod.c
patching file gcc-3.3.6/gcc/config/udivmodsi4.c
patching file gcc-3.3.6/gcc/cppdefault.c
patching file gcc-3.3.6/gcc/cppdefault.h
patching file gcc-3.3.6/gcc/expmed.c
patching file gcc-3.3.6/gcc/final.c
patching file gcc-3.3.6/gcc/flow.c
patching file gcc-3.3.6/gcc/gcse.c
patching file gcc-3.3.6/gcc/libgcc2.c
patching file gcc-3.3.6/gcc/longlong.h
patching file gcc-3.3.6/gcc/loop.c
patching file gcc-3.3.6/gcc/regrename.c
patching file gcc-3.3.6/gcc/reload.c
patching file gcc-3.3.6/gcc/reload1.c
patching file gcc-3.3.6/gcc/testsuite/ChangeLog.M68HC11
patching file gcc-3.3.6/gcc/testsuite/g++.dg/bprob/bprob.exp
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile/20010327-1.x
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile/920521-1.x
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile/simd-5.x
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/add_opt.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/addshift.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/alloca.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/ashr.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-2411.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20001206.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20010424.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20010920.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20011203.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20020203.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20020206.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20020403.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20020610.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20021015.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-2003-07-04.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-2003-07-30.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20030518.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-20030519.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/b-2005-02-14.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/bclr.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/compile.exp
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/cp.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/di.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/foo.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/fprintf.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/gcc-bug.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/interrupt.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/lshr.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/min.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/orext.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/pr-11813.c
patching file gcc-3.3.6/gcc/testsuite/gcc.c-torture/compile-scz/pr-12572.c
patching file 

Bug#396376: eclipse: doesn't start - java.lang.RuntimeException: Could not find framework

2006-10-31 Thread Ludo

Package: eclipse
Version: 3.1.2-2
Severity: grave
Justification: renders package unusable

When I try to run 'eclipse', it shows me dialog that it couldn't start, and that
I should check a log file in my ~/.eclipse.
Here's the output, with different VM's (changed using /etc/eclipse/java_home):

[EMAIL PROTECTED] ~ $ rm -Rf .eclipse  /dev/null
[EMAIL PROTECTED] ~ $ eclipse
searching for compatible vm...
 testing /usr/lib/kaffe/pthreads...found

[EMAIL PROTECTED] ~ $ cat
.eclipse/org.eclipse.platform_3.1.2/configuration/1162310721134.log
!SESSION Tue Oct 31 17:05:21 GMT+01:00 2006 
!ENTRY org.eclipse.core.launcher 4 0 2006-10-31 17:05:21.526
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.RuntimeException: Could not find framework
  at org.eclipse.core.launcher.Main.getBootPath (Main.java:635)
  at org.eclipse.core.launcher.Main.basicRun (Main.java:272)
  at org.eclipse.core.launcher.Main.run (Main.java:973)
  at org.eclipse.core.launcher.Main.main (Main.java:948)
  at java.lang.reflect.Method.invoke0 (Method.java)
  at java.lang.reflect.Method.invoke (Method.java:255)
  at org.kaffe.jar.ExecJarName.main (ExecJarName.java:64)
  at org.kaffe.jar.ExecJar.main (ExecJar.java:57)


[EMAIL PROTECTED] ~ $ rm -Rf .eclipse  /dev/null
[EMAIL PROTECTED] ~ $ eclipse
searching for compatible vm...
 testing /usr/lib/jvm/java-gcj...found

[EMAIL PROTECTED] ~ $ cat
.eclipse/org.eclipse.platform_3.1.2/configuration/1162310751565.log
!SESSION Tue Oct 31 17:05:51 GMT+01:00 2006 
!ENTRY org.eclipse.core.launcher 4 0 2006-10-31 17:05:51.570
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.RuntimeException: Could not find framework
  at org.eclipse.core.launcher.Main.getBootPath(Main.java:635)
  at org.eclipse.core.launcher.Main.basicRun(Main.java:272)
  at org.eclipse.core.launcher.Main.run(Main.java:973)
  at org.eclipse.core.launcher.Main.main(Main.java:948)


[EMAIL PROTECTED] ~ $ rm -Rf .eclipse  /dev/null
[EMAIL PROTECTED] ~ $ eclipse
searching for compatible vm...
 testing /usr/lib/j2re1.5-sun...found

[EMAIL PROTECTED] ~ $ cat
.eclipse/org.eclipse.platform_3.1.2/configuration/1162310768918.log
!SESSION Tue Oct 31 17:06:08 CET 2006 --
!ENTRY org.eclipse.core.launcher 4 0 2006-10-31 17:06:09.07
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.RuntimeException: Could not find framework
   at org.eclipse.core.launcher.Main.getBootPath(Main.java:635)
   at org.eclipse.core.launcher.Main.basicRun(Main.java:272)
   at org.eclipse.core.launcher.Main.run(Main.java:973)
   at org.eclipse.core.launcher.Main.main(Main.java:948)


The package I have installed (as for other packages, generally
everything should be up-to-date):

dax /etc/eclipse # dpkg -l|grep eclipse
ii  eclipse  3.1.2-2
 Extensible Tool Platform and Java IDE
ii  eclipse-ecj  3.1.2-2
 Eclipse Java compiler and Ant plug-in
ii  eclipse-efj  3.1.2-2
 Eclipse Java code formatter
ii  eclipse-jdt  3.1.2-2
 Java Development Tools plug-ins for Eclipse
ii  eclipse-jdt-common   3.1.2-2
 Java Development Tools plug-ins for Eclipse (common files)
ii  eclipse-jdt-gcj  3.1.2-2
 Java Development Tools plug-ins for Eclipse (GCJ version)
ii  eclipse-pde  3.1.2-2
 Plug-in Development Environment to develop Eclipse plug-ins
ii  eclipse-pde-common   3.1.2-2
 Plug-in Development Environment to develop Eclipse plug-ins (com
ii  eclipse-pde-gcj  3.1.2-2
 Plug-in Development Environment to develop Eclipse plug-ins (GCJ
ii  eclipse-platform 3.1.2-2
 Eclipse platform without plug-ins to develop any language
ii  eclipse-platform-common  3.1.2-2
 Eclipse platform without plug-ins to develop any language (commo
ii  eclipse-platform-gcj 3.1.2-2
 Eclipse platform without plug-ins to develop any language (GCJ v
ii  eclipse-rcp  3.1.2-2
 Eclipse rich client platform
ii  eclipse-rcp-common   3.1.2-2
 Eclipse rich client platform (common files)
ii  eclipse-rcp-gcj  3.1.2-2
 Eclipse rich client platform (GCJ version)
ii  eclipse-sdk  3.1.2-2
 Extensible Tool Platform and Java IDE
ii  eclipse-source   3.1.2-2
 Eclipse source code plug-ins


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


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



Bug#396377: FTBFS: Missing Build-Conflicts with automake*

2006-10-31 Thread Goswin von Brederlow
Package: gnusim8085
Version: 1.2.90-1
Severity: serious
Justification: no longer builds from source

Hi,

when compiling gnusim8085 it fails with the following error:

make[1]: Entering directory 
`/home/mrvn/build/gnusim8085_1.2.90-1/gnusim8085-1.2.90'
cd .  /bin/sh /home/mrvn/build/gnusim8085_1.2.90-1/gnusim8085-1.2.90/missing 
--run aclocal-1.7 
aclocal: macro `AM_PROG_MKDIR_P' required but not defined
aclocal: macro `AM_PROG_MKDIR_P' required but not defined
make[1]: *** [aclocal.m4] Error 1
make[1]: Leaving directory 
`/home/mrvn/build/gnusim8085_1.2.90-1/gnusim8085-1.2.90'
make: *** [build-stamp] Error 2

Cause for this will be one of the installed automake versions, there
is no Build-Depends on automake so buildds normaly woudn't have any
installed. Not sure what version(s) was installed during build so you
have to test each one yourself.

If you can't make the source not run aclocal and automake or make it
use the right aclocal-x.y then you have to Build-Conflict at least
with harmfull versions of automake.

MfG
Goswin

-- 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.8-frosties-2
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp 
# Add here commands to clean up after the build process.
/usr/bin/make distclean
make[1]: Entering directory 
`/home/mrvn/build/gnusim8085_1.2.90-1/gnusim8085-1.2.90'
make[1]: *** No rule to make target `distclean'.  Stop.
make[1]: Leaving directory 
`/home/mrvn/build/gnusim8085_1.2.90-1/gnusim8085-1.2.90'
make: [clean] Error 2 (ignored)
rm -f config.sub
rm -f config.guess
dh_clean 
 debian/rules build
dh_testdir
cp -f /usr/share/misc/config.sub config.sub
cp -f /usr/share/misc/config.guess config.guess
# Add here commands to configure the package.
./configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu --prefix=/usr 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info CFLAGS=-Wall -g 
-O2 LDFLAGS=-Wl,-z,defs
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-linux-gnu-gcc accepts -g... yes
checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of x86_64-linux-gnu-gcc... gcc3
checking for strerror in -lcposix... no
checking for x86_64-linux-gnu-gcc... (cached) x86_64-linux-gnu-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether x86_64-linux-gnu-gcc accepts -g... (cached) yes
checking for x86_64-linux-gnu-gcc option to accept ISO C89... (cached) none 
needed
checking dependency style of x86_64-linux-gnu-gcc... (cached) gcc3
checking for x86_64-linux-gnu-g++... x86_64-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-linux-gnu-g++... gcc3
checking for x86_64-linux-gnu-gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for ld used by x86_64-linux-gnu-gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... nm
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... x86_64-linux-gnu-g++ -E
checking for x86_64-linux-gnu-g77... x86_64-linux-gnu-g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether x86_64-linux-gnu-g77 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse nm output from x86_64-linux-gnu-gcc object... ok
checking for 

Bug#396372: FTBFS: src/autoprofile.h:30:20: error: config.h: No such file or directory

2006-10-31 Thread Goswin von Brederlow
Package: autoprofile
Severity: serious
Justification: no longer builds from source

Hi,

when building autoprofile I get lots of warning like

src/comp_logstats.c:200: warning: implicit declaration of function 'strdup'
src/comp_logstats.c:200: warning: incompatible implicit declaration of built-in 
function 'strdup'

The first kind is bad enough as it tends to declare the wrong types
and the second warning (doesn't always give one) is a sure sign that
you messed up the types. A segfault is a very likely result.

So after lots of those the real error comes:

gcc -O2 -Wall -fpic -g -I../gaim -I../gaim/src -I../.. -I../../src 
-I/usr/include/gaim -I/usr/include/gaim/src -I/usr/include 
-I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include 
-I/usr/include -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/lib/glib-2.0/include 
-I/usr/lib/gtk-2.0/include `pkg-config --cflags gtk+-2.0 gaim` -DHAVE_CONFIG_H 
-c src/comp_logstats_gtk.c -o src/comp_logstats_gtk.o
In file included from src/comp_logstats_gtk.c:24:
src/autoprofile.h:30:20: error: config.h: No such file or directory
make[1]: *** [src/comp_logstats_gtk.o] Error 1
make[1]: Leaving directory `/home/mrvn/build/autoprofile_2.14-2/autoprofile-2.14
'
make: *** [build-stamp] Error 2

Build log is attached.

MfG
Goswin


-- 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.8-frosties-2
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp patch-stamp
/usr/bin/make clean
make[1]: Entering directory 
`/home/mrvn/build/autoprofile_2.14-2/autoprofile-2.14'
rm -rf src/*.o
rm -rf autoprofile.so
make[1]: Leaving directory 
`/home/mrvn/build/autoprofile_2.14-2/autoprofile-2.14'
dh_clean 
dpatch deapply-all
01_gaim_build_bustication not applied to ./ .
 debian/rules build
dpatch apply-all
applying patch 01_gaim_build_bustication to ./ ... ok.
dpatch cat-all  patch-stamp
dh_testdir
/usr/bin/make PREFIX=/usr
make[1]: Entering directory 
`/home/mrvn/build/autoprofile_2.14-2/autoprofile-2.14'
gcc -O2 -Wall -fpic -g -I../gaim -I../gaim/src -I../.. -I../../src 
-I/usr/include/gaim -I/usr/include/gaim/src -I/usr/include 
-I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include 
-I/usr/include -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/lib/glib-2.0/include 
-I/usr/lib/gtk-2.0/include `pkg-config --cflags gtk+-2.0 gaim` -DHAVE_CONFIG_H 
-c src/component.c -o src/component.o
gcc -O2 -Wall -fpic -g -I../gaim -I../gaim/src -I../.. -I../../src 
-I/usr/include/gaim -I/usr/include/gaim/src -I/usr/include 
-I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include 
-I/usr/include -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/lib/glib-2.0/include 
-I/usr/lib/gtk-2.0/include `pkg-config --cflags gtk+-2.0 gaim` -DHAVE_CONFIG_H 
-c src/comp_http.c -o src/comp_http.o
src/comp_http.c: In function 'http_generate':
src/comp_http.c:37: warning: implicit declaration of function 'strdup'
src/comp_http.c:37: warning: incompatible implicit declaration of built-in 
function 'strdup'
src/comp_http.c: In function 'http_refresh_update':
src/comp_http.c:42: warning: incompatible implicit declaration of built-in 
function 'strdup'
src/comp_http.c:45: warning: implicit declaration of function 'gaim_url_fetch'
gcc -O2 -Wall -fpic -g -I../gaim -I../gaim/src -I../.. -I../../src 
-I/usr/include/gaim -I/usr/include/gaim/src -I/usr/include 
-I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include 
-I/usr/include -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/lib/glib-2.0/include 
-I/usr/lib/gtk-2.0/include `pkg-config --cflags gtk+-2.0 gaim` -DHAVE_CONFIG_H 
-c src/comp_textfile.c -o src/comp_textfile.o
src/comp_textfile.c: In function 'text_file_selection':
src/comp_textfile.c:104: warning: implicit declaration of function 'strlen'
src/comp_textfile.c:104: warning: incompatible implicit declaration of built-in 
function 'strlen'
src/comp_textfile.c: In function 'text_file_info_button':
src/comp_textfile.c:130: warning: implicit declaration of function 'strcmp'
gcc -O2 -Wall -fpic -g -I../gaim -I../gaim/src -I../.. -I../../src 
-I/usr/include/gaim -I/usr/include/gaim/src -I/usr/include 
-I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 

Bug#396379: libio-all-perl: FTBFS: failed test (race condition ?)

2006-10-31 Thread Lucas Nussbaum
Package: libio-all-perl
Version: 0.33-3
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000

Hi,

During a rebuild of all packages in etch, I discovered that your package
failed to build on i386.

Relevant parts:
t/synopsis1..ok
t/synopsis2..
#   Failed test in t/synopsis2.t at line 14.
#  got: 't/mydir/file3 - file3 is whee
# '
# expected: 't/mydir/file1 - file1 is fun
# '

#   Failed test in t/synopsis2.t at line 14.
#  got: 't/mydir/file1 - file1 is fun
# '
# expected: 't/mydir/file3 - file3 is whee
# '
# Looks like you failed 2 tests of 10.
dubious
Test returned status 2 (wstat 512, 0x200)
DIED. FAILED tests 2, 4
Failed 2/10 tests, 80.00% okay
t/synopsis3..ok
t/synopsis5..ok
[...]
Failed Test   Stat Wstat Total Fail  Failed  List of Failed
---
t/synopsis2.t2   512102  20.00%  2 4
Failed 1/41 test scripts, 97.56% okay. 2/274 subtests failed, 99.27% okay.
make[1]: *** [test_dynamic] Error 255
make[1]: Leaving directory `/build/root/libio-all-perl-0.33'
make: *** [install-stamp] Error 2

This error was not met at every build. I built your package 4 times, and only 
encountered the error 2 times. The package built fine the two other times.

About the archive rebuilt:
The rebuilt was done on about 60 AMD64 nodes of the Grid'5000 platform,
using a chroot containing an etch i386 environment (not unstable).
Internet was not accessible from the build nodes.

About Grid'5000:
The Grid'5000 project aims at building a highly reconfigurable
experimental Grid platform gathering 9 sites and featuring a total of
5000 CPUs. Its main purpose is to serve as an experimental testbed for
research in Grid Computing.  To learn more about Grid'5000, read
https://www.grid5000.fr/
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


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



Bug#395903: marked as done (FTBFS: cannot open Utils.so)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 09:18:59 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#395903: fixed in hdbc-sqlite3 1.0.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: hdbc-sqlite3
Version: 1.0.1.2
Severity: serious
Justification: no longer builds from source

hdbc-sqlite3 does not build on Alpha:

[...]
Building HDBC-sqlite3-1.0.1.1...
runhugs -98 +o -P/dist/build:/testsrc: testsrc/runtests.hs
runhugs: Error occurred
ERROR ./Database/HDBC/Sqlite3/Utils.hs - Error while importing DLL 
/tmp/hdbc-sqlite3-1.0.1.2/Database/HDBC/Sqlite3/Utils.so:
/tmp/hdbc-sqlite3-1.0.1.2/Database/HDBC/Sqlite3/Utils.so: cannot open shared 
object file: No such file or directory



make[1]: *** [test-hugs] Error 1
make[1]: Leaving directory `/tmp/hdbc-sqlite3-1.0.1.2'

Full log at
http://buildd.debian.org/fetch.cgi?pkg=hdbc-sqlite3arch=alphaver=1.0.1.2stamp=1161896808

Falk


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

---End Message---
---BeginMessage---
Source: hdbc-sqlite3
Source-Version: 1.0.1.3

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

hdbc-sqlite3_1.0.1.3.dsc
  to pool/main/h/hdbc-sqlite3/hdbc-sqlite3_1.0.1.3.dsc
hdbc-sqlite3_1.0.1.3.tar.gz
  to pool/main/h/hdbc-sqlite3/hdbc-sqlite3_1.0.1.3.tar.gz
libghc6-hdbc-sqlite3-dev_1.0.1.3_i386.deb
  to pool/main/h/hdbc-sqlite3/libghc6-hdbc-sqlite3-dev_1.0.1.3_i386.deb
libhugs-hdbc-sqlite3_1.0.1.3_i386.deb
  to pool/main/h/hdbc-sqlite3/libhugs-hdbc-sqlite3_1.0.1.3_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.
John Goerzen [EMAIL PROTECTED] (supplier of updated hdbc-sqlite3 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, 31 Oct 2006 04:57:18 -0600
Source: hdbc-sqlite3
Binary: libghc6-hdbc-sqlite3-dev libhugs-hdbc-sqlite3
Architecture: source i386
Version: 1.0.1.3
Distribution: unstable
Urgency: high
Maintainer: John Goerzen [EMAIL PROTECTED]
Changed-By: John Goerzen [EMAIL PROTECTED]
Description: 
 libghc6-hdbc-sqlite3-dev - Sqlite v3 HDBC (Haskell Database Connectivity) 
Driver for GHC
 libhugs-hdbc-sqlite3 - Sqlite v3 HDBC (Haskell Database Connectivity) Driver 
for Hugs
Closes: 395903
Changes: 
 hdbc-sqlite3 (1.0.1.3) unstable; urgency=high
 .
   * Use CURDIR instead of PWD in Makefile.  Closes: #395903.
Files: 
 9ef95ca24c3e0574f9bf1c5a1d1bba94 768 libs optional hdbc-sqlite3_1.0.1.3.dsc
 8ce517afd74de4dba783db4d12d87dc3 23959 libs optional 
hdbc-sqlite3_1.0.1.3.tar.gz
 025db7bb78d856ced8054c9a9146f99f 40276 libdevel optional 
libghc6-hdbc-sqlite3-dev_1.0.1.3_i386.deb
 abf86ab7b68b1acbb8776359b49ff4a1 14818 libs optional 
libhugs-hdbc-sqlite3_1.0.1.3_i386.deb

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

iD8DBQFFR4F93PeFtIodmh8RAiyoAJ4xCWDU2dl/o7HXlF1cpwc0cG1pYQCfWwvI
Q0yF6XYA2vht1VZ0We7y86c=
=76OE
-END PGP SIGNATURE-

---End Message---


Bug#395247: (fwd) Bug#395247: [s390] System clock runs wild (in hercules emulator)

2006-10-31 Thread Heiko Carstens
This a known bug and is already fixed in the current git tree. AFAIK the patch
is accepted for 2.6.18.2. If you need it earlier, here it is:

http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9f7a745d55527d0d41684b22506a86c4381f7f1

On Tue, Oct 31, 2006 at 11:15:54AM +0100, maximilian attems wrote:
 could you please have a look at this bug?
 thanks
 
 - Forwarded message from Frans Pop [EMAIL PROTECTED] -
 
 X-Original-To: [EMAIL PROTECTED]
 X-Original-To: debian-kernel@lists.debian.org
 Subject: Bug#395247: [s390] System clock runs wild (in hercules emulator)
 Date: Tue, 24 Oct 2006 22:31:54 +0200
 From: Frans Pop [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 
 Package: linux-2.6
 Version: 2.6.18-2
 Severity: grave
 
 After booting my hercules emulator with 2.6.18, I noticed some errors during 
 a packages upgrade, like:
 tar: ./config: time stamp 2006-10-27 10:52:22.00126 is 4290.653417 s in the 
 future
 
 Further investigation showed that the system clock in running wild:
 $ date
 Fri Oct 27 05:36:58 CEST 2006
 $ date
 Fri Oct 27 05:41:40 CEST 2006
 $ date
 Fri Oct 27 06:25:24 CEST 2006
 $ date
 Fri Oct 27 09:01:09 CEST 2006
 $ date
 Fri Oct 27 18:19:04 CEST 2006
 
 These 'date' commands were given within 15-20 minutes or so. Actual time 
 when the emulator was started was around 2006-10-24 17:30.
 
 After rebooting the emulator with 2.6.17-9, the problem was gone.
 
 This series from a later boot with 2.6.18, taken within 2 minutes, is even 
 crazier.
 It shows the clock jumping all over the place (real time Oct 24, 22:30):
 $ date
 Wed Oct 25 09:10:10 CEST 2006
 $ date
 Wed Oct 25 08:06:19 CEST 2006
 $ date
 Wed Oct 25 09:26:43 CEST 2006
 $ date
 Wed Oct 25 09:32:17 CEST 2006
 $ date
 Wed Oct 25 09:35:45 CEST 2006
 $ date
 Wed Oct 25 09:40:40 CEST 2006
 $ date
 Wed Oct 25 08:32:08 CEST 2006
 $ date
 Wed Oct 25 09:49:38 CEST 2006
 $ date
 Wed Oct 25 09:51:44 CEST 2006
 $ date
 Wed Oct 25 08:41:32 CEST 2006
 $ date
 Wed Oct 25 08:42:45 CEST 2006
 $ date
 Wed Oct 25 08:43:59 CEST 2006
 
 I'm running hercules 3.04.1 on an EM64T host system. The system clock on the 
 host runs normally.
 
 
 
 - End forwarded message -
 -- 
 maks


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



Processed: tagging 350754

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.22
 tags 350754 + pending
Bug#350754: mailutils-imap4d: Risk of mailbox corruption by imap4d due to lack 
of multiple access locking?
Tags were: help
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]



Processed: severity of 395079 is serious

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 395079 serious
Bug#395079: grace: missing dependancy on gconf2
Severity set to `serious' from `normal'


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#383481: Must source code be easy to understand to fall under DFSG?

2006-10-31 Thread Goswin von Brederlow
Ola Lundqvist [EMAIL PROTECTED] writes:

 Ok, you are probably right if the person use an automated tool to make
 this obfuscation. (Not sure though, see below).

 However as it is impossible to know if someone use a obfuscation program
 or if the person use a text editor to edit this, I can not see it as
 a violation anyway.

 At least it is a bit harsh to see it as a policy violation just because
 it may be obfuscated.

If you have 'char data[] = { 0xef, 0x45, ... };' and from running a
disassembler it is clear that this was produced with gcc for arm (yes,
that is not too wilde an idea) or some other compiler I think then it
is at least suspect.

Personaly I rather have such a char array under GPL than no driver or
a binary only driver. At least you can perfectly legaly dissasemble
the data and, comment the code and make it readable again.


Ultimately I think the decision is with ftp-master and then you have
to fight hard to reverse that. They usualy make good calls there.

MfG
Goswin


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



Bug#395252: embedded code copies are not RC

2006-10-31 Thread Diego Biurrun
On Sun, Oct 29, 2006 at 12:53:37AM +0200, Moritz Muehlenhoff wrote:
 On Sat, Oct 28, 2006 at 01:08:09PM -0400, Joey Hess wrote:
  Moritz Muehlenhoff wrote:
   
The testing security team tracks probably hundreds of possibly security
relevant code copies in data/embedded-code-copies in their svn repo. As
long as the security teams know about code copies, they can deal with
updates due to them.
   
   No, we have already way too much work and artifially introducing more is
   not a option. For Sarge there was no clean solution, as ffmpeg provided
   only a static libavcodec, but since this exists, there's no reason not
   to use it.
  
  How is mplayer different than the 200 or so other items listed in
  embedded-code-copies? Other than only getting through incoming now. 
 
 Two complexes of code embedding have caused serious trouble for security
 support in Sarge; xpdf and libavcodec. xpdf is resolved for Etch, libavcodec
 is being adressed currently, thus this bug.

Removing the embedded copies of FFmpeg libraries from MPlayer is a bad
idea.

The relationship between MPlayer and FFmpeg is very intimate to say the
least.  MPlayer uses FFmpeg HEAD via a svn:external declaration.  In the
future we will move both to a common repository.  Most FFmpeg developers
work on MPlayer as well.

FFmpeg is highly volatile and fast-moving.  The FFmpeg snapshot in
Debian is two months older than the one in MPlayer 1.0rc1.  This may not
sound much, but it means more than 600 (!) commits to the FFmpeg
repository.

Using the Debian version of FFmpeg in MPlayer would create a beast
entirely different from 1.0rc1.  Several codecs have been added which
were only available through binaries before, many bugs have been fixed
and speed improvements committed.

A H.264 video decoding benchmark done by a fellow developer gives the
following numbers:

self-built custom binary:  13.9 seconds
Debian MPlayer package:14.7 seconds
binary with Debian's FFmpeg:   17.7 seconds

The Debian FFmpeg binary was built against dynamic FFmpeg, the other two
with static FFmpeg.  That's a massive 20% performance degradation..

Using a shared dynamic version of FFmpeg would disable several video
filters, so there would be even more feature loss.

Plus I expect random bugs to creep up.  As mentioned above  FFmpeg is
highly volatile and fast-moving.  Backwards-compatibility is not a
priority.

regards

Diego Biurrun
MPlayer / FFmpeg developer


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



Bug#396277: marked as done (allows creating any file as root)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 11:34:05 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#396277: fixed in thttpd 2.23beta1-5
has caused the attached Bug report to be marked as done.

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

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

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

---BeginMessage---
Package: thttpd
Severity: grave
Tags: security

Insecure use of /tmp in /etc/logrotate.d/thttpd:

if pidof thttpd 21  /dev/null; then
touch /tmp/start_thttpd
fi

By creating a /tmp/start_thttpd symlink a local attacker will be able to
create/touch any file as root.

-- 
ciao,
Marco


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: thttpd
Source-Version: 2.23beta1-5

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

thttpd-util_2.23beta1-5_i386.deb
  to pool/main/t/thttpd/thttpd-util_2.23beta1-5_i386.deb
thttpd_2.23beta1-5.diff.gz
  to pool/main/t/thttpd/thttpd_2.23beta1-5.diff.gz
thttpd_2.23beta1-5.dsc
  to pool/main/t/thttpd/thttpd_2.23beta1-5.dsc
thttpd_2.23beta1-5_i386.deb
  to pool/main/t/thttpd/thttpd_2.23beta1-5_i386.deb



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

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

Debian distribution maintenance software
pp.
Daniel Baumann [EMAIL PROTECTED] (supplier of updated thttpd 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, 31 Oct 2006 20:13:00 +0200
Source: thttpd
Binary: thttpd-util thttpd
Architecture: source i386
Version: 2.23beta1-5
Distribution: unstable
Urgency: high
Maintainer: Daniel Baumann [EMAIL PROTECTED]
Changed-By: Daniel Baumann [EMAIL PROTECTED]
Description: 
 thttpd - tiny/turbo/throttling HTTP server
 thttpd-util - Support utilities for thttpd
Closes: 396277
Changes: 
 thttpd (2.23beta1-5) unstable; urgency=high
 .
   * Applied patch from Steve Kemp [EMAIL PROTECTED] on thttpd.logrotate to 
fix
 the insecure use of temporary files when invoked by logrotate
 [CVE-2006-4248] (Closes: #396277).
Files: 
 001713be9e39d2662b2b43b2bf80cda3 602 web optional thttpd_2.23beta1-5.dsc
 ac9085e9051e8d6d456bd3ebfd447dce 15102 web optional thttpd_2.23beta1-5.diff.gz
 18e7b8b8e80975a13b6ef3b9770cecb6 54482 web optional thttpd_2.23beta1-5_i386.deb
 afd66763ec36d12704919dd511b0eea4 26420 web optional 
thttpd-util_2.23beta1-5_i386.deb

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

iD8DBQFFR6EN+C5cwEsrK54RAiMXAKCyzgZ7Qk5IipkFwLlB2lGsqnIuhwCfQTo+
mNw7zT5nqs/2Eez4KsX40qc=
=Q8CZ
-END PGP SIGNATURE-

---End Message---


Bug#396240: poker-network: FTBFS: ImportError: No module named gtk

2006-10-31 Thread Julien Danjou
On Tue, Oct 31, 2006 at 02:38:33PM +0100, Loic Dachary wrote:
Hello,

 I'm a little confused as to how to reproduce the problem. 
 Could you send me the part you cut (...) ? 
 http://buildd.debian.org/build.php?pkg=poker-network does not show this
 build. Can I check it from somewhere else ?

Sorry, take a look on:

http://people.debian.org/~acid/buildd-logs/failed/poker-network_1.0.29-1_20061030-1910

Cheers,
-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD



Processed: setting severity to release critical

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 354544 grave
Bug#354544: ISAM trap in package upgrade
Bug#354850: mysql-server: upgrade 4.1-5.0 may break installation
Severity set to `grave' from `normal'

 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#396240: poker-network: FTBFS: ImportError: No module named gtk

2006-10-31 Thread Loic Dachary
Julien Danjou writes:
  On Tue, Oct 31, 2006 at 02:38:33PM +0100, Loic Dachary wrote:
  Hello,
  
   I'm a little confused as to how to reproduce the problem. 
   Could you send me the part you cut (...) ? 
   http://buildd.debian.org/build.php?pkg=poker-network does not show this
   build. Can I check it from somewhere else ?
  
  Sorry, take a look on:
  
  http://people.debian.org/~acid/buildd-logs/failed/poker-network_1.0.29-1_20061030-1910

Jesus :-( Something must have changed in the past two days. I'll
re-build using a fresh unstable right now and fix the issue. Thanks for your
help.

Cheers,

-- 
+33 1 76 60 72 81  Loic Dachary mailto:[EMAIL PROTECTED]
http://dachary.org/loic/gpg.txt sip:[EMAIL PROTECTED]


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



Bug#323706: marked as done (gaim: CAN-2005-2103, CAN-2005-2102, AIM/ICQ protocols vulnerability)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 21:17:56 +0100
with message-id [EMAIL PROTECTED]
and subject line This was fixed quite a long time ago.
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: gaim
Version: 1:1.2.1-1.4
Severity: grave
Justification: user security hole

This info from http://www.securityfocus.com/bid/14531. Seems ubuntu have
released usn-168-1 to announce their fix:
http://www.ubuntulinux.org/support/documentation/usn/usn-168-1

CAN-2005-2102 is about an attacker crashing gaim by sending a file over
ICQ with a filename containing invalid UTF-8 characters.

CAN-2005-2103 is about a memory alignment problem in the Gadu library
for the Gadu protocol, of which Gaim has a copy of.


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686-smp
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)

Versions of packages gaim depends on:
ii  gaim-data  1:1.2.1-1.4   multi-protocol instant messaging c

---End Message---
---BeginMessage---
Version: 1:1.4.0-5

gaim  (1:1.4.0-5) unstable; urgency=high

   * This release fixes three remotely-exploitable security issues.
 These will be fixed in 1.5.0, but I'm adding the patches now so
 I don't have to rush to package 1.5.0 when it comes out.
 
   * debian/patches/away-message-CAN-2005-2103.patch:
 - Added
 - Fixes CAN-2005-2103: Away message buffer overflow (arbitrary
   code execution)
   *  debian/patches/libgg-CAN-2005-2370.patch:
 - Added
 - Fixes CAN-2005-2370: Memory alignment bug in libgadu
   *  debian/patches/oscar-CAN-2005-2102.patch:
 - Added
 - Fixes CAN-2005-2102: OSCAR UTF-8 filename remote crash
 
   * debian/control:
 - Remove version from libgtkspell-dev build-depends, since the aspell
   C++ transition was reverted.

 -- Ari Pollak [EMAIL PROTECTED]  Wed, 10 Aug 2005 11:49:26 -0400 

The current version in testing has a much higher version number
than that.

Regards,

// Ola

-- 
 - 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 /
 ---
---End Message---


Bug#394280: Bug unreproducible

2006-10-31 Thread Nick Dickerson
Yes I used apt-get for this. The reason is that I already had bootsplash-theme-debian installed, because I had just removed bootsplash to copy the output so I could send it. I removed both and here is what happens:
# apt-get install bootsplashbootsplash failed to preconfigure, with exit status 10Selecting previously deselected package bootsplash-theme-debian.(Reading database ... 188107 files and directories currently installed.)
Unpacking bootsplash-theme-debian (from .../bootsplash-theme-debian_0.5-6_all.deb) ...Selecting previously deselected package bootsplash.Unpacking bootsplash (from .../bootsplash_3.3-1_i386.deb) ...Setting up bootsplash-theme-debian (
0.5-6) ...Setting up bootsplash (3.3-1) ...dpkg: error processing bootsplash (--configure):subprocess post-installation script returned error exit status 10Errors were encountered while processing:bootsplash
E: Sub-process /usr/bin/dpkg returned an error code (1)Then I also did:# apt-get install -f Reading package lists... DoneBuilding dependency tree... Done0 upgraded, 0 newly installed, 0 to remove and 30 not upgraded.
1 not fully installed or removed.Need to get 0B of archives.After unpacking 0B of additional disk space will be used.Setting up bootsplash (3.3-1) ...dpkg: error processing bootsplash (--configure):
subprocess post-installation script returned error exit status 10Errors were encountered while processing:bootsplashE: Sub-process /usr/bin/dpkg returned an error code (1)
On 10/31/06, Christian Perrier [EMAIL PROTECTED] wrote:
Quoting Nick Dickerson ([EMAIL PROTECTED]): I removed and reinstalled bootsplash and am still getting the same error. If you need any more info please let me know.
 Nick Preconfiguring packages ... bootsplash failed to preconfigure, with exit status 10 Selecting previously deselected package bootsplash. (Reading database ... 188111 files and directories currently installed.)
 Unpacking bootsplash (from .../bootsplash_3.3-1_i386.deb) ... Setting up bootsplash (3.3-1) ... dpkg: error processing bootsplash (--configure): subprocess post-installation script returned error exit status 10
 Errors were encountered while processing: bootsplash E: Sub-process /usr/bin/dpkg returned an error code (1)I actually *don't* understand why this doesn't installbootsplash-theme-debian. bootsplash *depends* on it so that package
should be installed along with bootsplash alone.WHat do you use to install it? apt-get?-BEGIN PGP SIGNATURE-Version: GnuPG v1.4.5 (GNU/Linux)iD8DBQFFRuPO1OXtrMAUPS0RArQEAJ9+iqRxLOWa5Q0NIWoBX5Gqb0UOVACgt5m0
yqzV0IDjyRphnBqxyDauQzQ==yH6i-END PGP SIGNATURE-


Bug#391345: marked as done (aoetools: Postinst fails with missing devices)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 05:47:20 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#391345: fixed in aoetools 11-1.1
has caused the attached Bug report to be marked as done.

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

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

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

---BeginMessage---
Package: aoetools
Version: 11-1
Severity: normal


While trying to upgrade to aoetools 11-1 the postinst fails:
Setting up aoetools (11-1) ...
Starting AoE devices discovery and mounting AoE filesystems: Missing
devices under /dev/etherd/.  Please run
  aoe-mkdevs /dev/etherd
and try again.
invoke-rc.d: initscript aoetools, action start failed.
dpkg: error processing aoetools (--configure):
 subprocess post-installation script returned error exit status 1

I'm running udev if that's of any use. Currently I have no aoe disks
configured.

-- 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.18-dirty
Locale: LANG=et_EE.ISO-8859-15, LC_CTYPE=et_EE.ISO-8859-15 (charmap=ISO-8859-15)

Versions of packages aoetools depends on:
ii  libc62.3.6.ds1-5 GNU C Library: Shared libraries

aoetools recommends no packages.

-- no debconf information

---End Message---
---BeginMessage---
Source: aoetools
Source-Version: 11-1.1

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

aoetools_11-1.1.diff.gz
  to pool/main/a/aoetools/aoetools_11-1.1.diff.gz
aoetools_11-1.1.dsc
  to pool/main/a/aoetools/aoetools_11-1.1.dsc
aoetools_11-1.1_i386.deb
  to pool/main/a/aoetools/aoetools_11-1.1_i386.deb



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

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

Debian distribution maintenance software
pp.
Steinar H. Gunderson [EMAIL PROTECTED] (supplier of updated aoetools 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, 31 Oct 2006 14:25:41 +0100
Source: aoetools
Binary: aoetools
Architecture: source i386
Version: 11-1.1
Distribution: unstable
Urgency: high
Maintainer: David Martínez Moreno [EMAIL PROTECTED]
Changed-By: Steinar H. Gunderson [EMAIL PROTECTED]
Description: 
 aoetools   - tools to assist in using ATA over Ethernet
Closes: 391345
Changes: 
 aoetools (11-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Have the init script opportunistically modprobe aoe, and exit out
 if $INTERFACES == none before checking for /dev/etherd, so that the
 PACKAGE installs cleanly on unconfigured systems; patch from
 Steve Langasek. (Closes: #391345)
Files: 
 3297f3e2f22e196019f4536d6df5faa6 683 admin optional aoetools_11-1.1.dsc
 e1482b7e6cccdcec1fb05fd3a241068d 4589 admin optional aoetools_11-1.1.diff.gz
 26d3786c68eae1af00b497a2129f2dea 20814 admin optional aoetools_11-1.1_i386.deb

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

iQCVAwUBRUdRU37hqgLJpbVOAQLKWgP9EXZW9B4/BySeuW0g6NTQSSB1VXj94L0R
ot4wOuJt7Ak24JczMrThs9CYNF3hi5y02wMbmAG12/cNrlyW0kTyYqO7JRkX+Kov
FEa/v2boKWAEnN+IF3Lt35Mb3tPsSgC4lI0D4wD++AB8RZGWzO0ANlkwXpPwfwwo
nA2wlhB4BTQ=
=/F6S
-END PGP SIGNATURE-

---End Message---


Bug#396410: grdesktop eats all memory and freezes the whole system

2006-10-31 Thread Adalbert Dawid





Package: grdesktop
Version: 0.23-2+b1
Severity: critical
Justification: breaks the whole system

When I launch grdesktop, it eats up the whole memory of my machine 
(1 GB) whithin one or two seconds and freezes the whole system, forcing me 
to do a hard reset. This happens *immediately* after starting grdesktop and
before the grdesktop UI appears. 

I can't say if it is the fault of grdesktop itself, or of rdesktop.
tsclient and rdesktop itself sometimes also freeze the machine, but
this seems to be another bug, because I can't see them eating up the
memory before the freeze happens (of course I could be wrong here, I
don't know for sure).

I really don't know how to find out which component is really
responsible for this bug. It might be rdesktop or grdesktop.

Another curious thing is, that it only happens on one etch machine out of
two (which runs totally stable apart of the grdesktop problem).
On the other one, grdesktop works as expected.

As a side note, I am running the Gnome desktop on a plain X server
without compositing. I am able to reproduce the bug with the nvidia and
the nv driver.

Thanks
Adalbert

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

Versions of packages grdesktop depends on:
ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi
ii libatk1.0-0 1.12.3-1 The ATK accessibility toolkit
ii libbonobo2-0 2.14.0-2 Bonobo CORBA interfaces library
ii libbonoboui2-0 2.14.0-5 The Bonobo UI library
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra
ii libfontconfig1 2.4.1-2 generic font configuration library
ii libgconf2-4 2.16.0-2 GNOME configuration database syste
ii libglib2.0-0 2.12.4-1 The GLib library of C routines
ii libgnome-keyring0 0.4.9-1 GNOME keyring services library
ii libgnome2-0 2.16.0-2 The GNOME 2 library - runtime file
ii libgnomecanvas2-0 2.14.0-2 A powerful object-oriented display
ii libgnomeui-0 2.14.1-2 The GNOME 2 libraries (User Interf
ii libgnomevfs2-0 2.14.2-2+b1 GNOME virtual file-system (runtime
ii libgtk2.0-0 2.8.20-3 The GTK+ graphical user interface 
ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library
ii liborbit2 1:2.14.0-2 libraries for ORBit2 - a CORBA ORB
ii libpango1.0-0 1.14.7-1 Layout and rendering of internatio
ii libpopt0 1.10-3 lib for parsing cmdline parameters
ii libsm6 1:1.0.1-3 X11 Session Management library
ii libx11-6 2:1.0.3-2 X11 client-side library
ii libxcursor1 1.1.7-4 X cursor management library
ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar
ii libxfixes3 1:4.0.1-4 X11 miscellaneous 'fixes' extensio
ii libxi6 1:1.0.1-3 X11 Input extension library
ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library
ii libxml2 2.6.26.dfsg-4 GNOME XML library
ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library
ii libxrender1 1:0.9.1-3 X Rendering Extension client libra
ii rdesktop 1.5.0-1 RDP client for Windows NT/2000 Ter
ii scrollkeeper 0.3.14-11 A free electronic cataloging syste
ii zlib1g 1:1.2.3-13 compression library - runtime

grdesktop recommends no packages.

-- no debconf information






Bug#396363: FTBFS: Makefile:69: *** target pattern contains no `%'. Stop.

2006-10-31 Thread Ionut Georgescu
Have you altered the sources in any way? Please check your building
environment. grace 1:5.1.20-3 build OK on all architectures, including
amd64

http://buildd.debian.org/build.php?arch=pkg=grace

Ionut

On Tue, 2006-10-31 at 13:28 +0100, Goswin von Brederlow wrote:
 Package: grace
 Version: 1:5.1.20-3
 Severity: serious
 Justification: no longer builds from source
 
 Hi,
 
 when building grace I get the following error:
 
 make[2]: Entering directory 
 `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20/src'
 Makefile:69: *** target pattern contains no `%'.  Stop.
 make[2]: Leaving directory 
 `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20/src'
 make[1]: *** [subdirs] Error 1
 make[1]: Leaving directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
 make: *** [common-install-impl] Error 2
 
 Build log is attached.
 
 MfG
   Goswin
 
 
 -- 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.8-frosties-2
 Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)



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



Processed: Re: Bug#396359: FTBFS: scons: building terminated because of errors.

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 package cheesetracker
Ignoring bugs not assigned to: cheesetracker

 tag 396359 moreinfo unreproducible
Bug#396359: FTBFS: scons: building terminated because of errors.
There were no tags set.
Tags added: moreinfo, unreproducible

 severity 396359 important
Bug#396359: FTBFS: scons: building terminated because of errors.
Severity set to `important' from `serious'

 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#396359: FTBFS: scons: building terminated because of errors.

2006-10-31 Thread Wesley J. Landaker
package cheesetracker
tag 396359 moreinfo unreproducible
severity 396359 important
thanks

On Tuesday 31 October 2006 05:00, Goswin von Brederlow wrote:
 Package: cheesetracker
 Version: 0.9.9-8
 Severity: serious
 Justification: no longer builds from source

How were you doing the build? Was it on etch, or unstable? In a pbuilder, or 
not? Any other info you can provide?

I just tried the build here on both an i386 and amd64 system and it had 
absolutely no problems building on any of those combinations.

I am always happy to fix problems, but since this built when I uploaded it, it 
is verified to still build now on multiple releases, systems and 
architectures, and the error you've shown below isn't not reproducable, 
unless I get more info, I can only assume this is a problem with your test 
system. For now I'm downgrading the severity.

 scons: Building targets ...
 g++ -o cheesetracker/interface__QT/instrument_edit.o -c
 -I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2 -I/usr/include
 -trigraphs -DPOSIX_ENABLED -O3 -ffast-math -fno-strict-aliasing
 -DLADSPA_ENABLED -DOSS_ENABLED -DJACK_ENABLED -DALSA_ENABLED
 -I/usr/include/alsa -Icommon/ -Icommon/defines/ -I/usr/include/qt3
 -DQT_NO_EMIT -Icommon -I. -Icommon/defines -Icheesetracker
 -Icheesetracker/trackercore -Icheesetracker/loaders -Icheesetracker/savers
 -Icheesetracker/interface_binds
 cheesetracker/interface__QT/instrument_edit.cpp scons: ***
 [cheesetracker/interface__QT/instrument_edit.o] Error 1 scons: building
 terminated because of errors.
 make: *** [build-stamp] Error 2

-- 
Wesley J. Landaker [EMAIL PROTECTED]


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



Bug#396345: tomboy: Tomboy does not start

2006-10-31 Thread Dave Beckett
Andrey Fedoseev wrote:
 Package: tomboy
 Version: 0.4.1-2
 Severity: grave
 Justification: renders package unusable
 
...


 When trying to run tomboy I get:
 
 [START]
 ** ERROR **: file threadpool.c: line 990 (mono_thread_pool_init): 
 assertion failed: (async_call_klass)
 aborting...
 
 =
 Got a SIGABRT while executing native code. This usually indicates
 a fatal error in the mono runtime or one of the native libraries
 used by your application.
 =
 
 Stacktrace:
 
 Native stacktrace:
 
 /usr/lib/libmono.so.0 [0xa7df0dd2]
 /usr/lib/libmono.so.0 [0xa7dc46ec]
 [0xe440]
 /lib/tls/i686/cmov/libc.so.6(abort+0x109) [0xa7b7dfb9]
 /usr/lib/libglib-2.0.so.0(g_logv+0x454) [0xa7d10114]
 /usr/lib/libglib-2.0.so.0(g_log+0x29) [0xa7d10149]
 /usr/lib/libglib-2.0.so.0(g_assert_warning+0x77) [0xa7d101c7]
 /usr/lib/libmono.so.0 [0xa7e8dd62]
 /usr/lib/libmono.so.0(mono_runtime_init+0x23) [0xa7e95505]
 /usr/lib/libmono.so.0 [0xa7dc5b74]
 /usr/lib/libmono.so.0(mono_main+0x1388) [0xa7de1fe5]
 mono [0x8048522]
 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) 
 [0xa7b68ea8]
 mono [0x8048471]
 
 Debug info from gdb:
 
 (no debugging symbols found)
 Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 [Thread debugging using libthread_db enabled]
 [New Thread -1481300288 (LWP 18461)]
 [New Thread -1484702800 (LWP 18462)]
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 (no debugging symbols found)
 0xe410 in __kernel_vsyscall ()
   2 Thread -1484702800 (LWP 18462)  0xe410 in __kernel_vsyscall ()
   1 Thread -1481300288 (LWP 18461)  0xe410 in __kernel_vsyscall ()
 
 Thread 2 (Thread -1484702800 (LWP 18462)):
 #0  0xe410 in __kernel_vsyscall ()
 #1  0xa7cbf016 in __nanosleep_nocancel ()
from /lib/tls/i686/cmov/libpthread.so.0
 #2  0xa7ec8b4b in mono_type_full_name () from /usr/lib/libmono.so.0
 #3  0xa7cb9240 in start_thread () from 
 /lib/tls/i686/cmov/libpthread.so.0
 #4  0xa7c1f27e in clone () from /lib/tls/i686/cmov/libc.so.6
 
 Thread 1 (Thread -1481300288 (LWP 18461)):
 #0  0xe410 in __kernel_vsyscall ()
 #1  0xa7be19a9 in fork () from /lib/tls/i686/cmov/libc.so.6
 #2  0xa7cc05b4 in fork () from /lib/tls/i686/cmov/libpthread.so.0
 #3  0xa7d320c9 in g_spawn_error_quark () from /usr/lib/libglib-2.0.so.0
 #4  0xa7d32c9f in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
 #5  0xa7d33115 in g_spawn_command_line_sync () from 
 /usr/lib/libglib-2.0.so.0
 #6  0xa7df0e9a in mono_debugger_run_finally () from 
 /usr/lib/libmono.so.0
 #7  0xa7dc46ec in mono_jit_thread_attach () from /usr/lib/libmono.so.0
 #8  signal handler called
 #9  0xe410 in __kernel_vsyscall ()
 #10 0xa7b7c821 in raise () from /lib/tls/i686/cmov/libc.so.6
 #11 0xa7b7dfb9 in abort () from /lib/tls/i686/cmov/libc.so.6
 #12 0xa7d10114 in g_logv () from /usr/lib/libglib-2.0.so.0
 #13 0xa7d10149 in g_log () from /usr/lib/libglib-2.0.so.0
 #14 0xa7d101c7 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
 #15 0xa7e8dd62 in mono_thread_stop () from /usr/lib/libmono.so.0
 #16 0xa7e95505 in mono_runtime_init () from /usr/lib/libmono.so.0
 #17 0xa7dc5b74 in mono_jit_thread_attach () from /usr/lib/libmono.so.0
 #18 0xa7de1fe5 in mono_main () from /usr/lib/libmono.so.0
 #19 0x08048522 in ?? ()
 #20 0x0002 in ?? ()
 #21 0xafeb23f4 in ?? ()
 #22 0xafeb2378 in ?? ()
 #23 0x0804854f in ?? ()
 #24 0xa7b5ec8c in ?? () from /lib/tls/i686/cmov/libc.so.6
 #25 0xafeb2380 in ?? ()
 #26 0xafeb23c8 in ?? ()
 #27 0xa7b68ea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #28 0xa7b68ea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #29 0x08048471 in ?? ()
 #0  0xe410 in __kernel_vsyscall ()
 
 Aborted
 [END]
 
 I had tomboy (v0.3xxx) running fine before I updated some packages 
 (I don't remember exactly which packages were updated) a couple days 
 ago. After that I updated tomboy to 0.4.1-2 and it didn't help.
...

 Versions of packages tomboy depends on:

 ii  libmono-corlib1.0-cil  1.1.13.8-1Mono core library (1.0)
 ii  libmono-system1.0-cil  1.1.13.8-1Mono System libraries (1.0)
 ii  libmono1.0-cil 1.1.17.1-5Mono libraries (1.0)
 ii  mono-runtime   1.1.13.8-1Mono runtime

You seem to be using at least 2 different versions of the core Mono
libraries which means your system is inconsistent.

Maybe you could try using the 

Bug#393606: Preferred fix is upload to experimental

2006-10-31 Thread Øystein Gisnås

Hi,

the very best would be to modify the package so that the version is
determined from what version of evolution -dev packages are installed.
That way, a binNMU would be enough.

If that cannot be done, an upload to experimental would be useful so
that the evolution 2.8 transition could be carried out in a smoother
and safer way.

Cheers,
Øystein Gisnås



Bug#396433: zeroc-ice-java: FTBFS: depends on eclipse-ecj, which is unlikely to get into testing soon.

2006-10-31 Thread Lucas Nussbaum
Package: zeroc-ice-java
Version: 3.1.1-1
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000

Hi,

During a rebuild of all packages in etch, I discovered that your package
failed to build on i386.

Relevant parts:
Checking for source dependency conflicts...
Reading package lists...
Building dependency tree...
E: Couldn't find package eclipse-ecj
apt-get failed.
Package installation failed
Trying to reinstall removed packages:
Trying to uninstall newly installed packages:
Source-dependencies not satisfied; skipping zeroc-ice-java

Your package build-depends on eclipse-ecj, which is very unlikely to get
into testing soon (was removed from testing on 29/09, 7 open RC bugs).
If possible, it would be a good idea to depend on something else so your
package can be built inside testing.

About the archive rebuilt:
The rebuilt was done on about 60 AMD64 nodes of the Grid'5000 platform,
using a chroot containing an etch i386 environment (not unstable).
Internet was not accessible from the build nodes.

About Grid'5000:
The Grid'5000 project aims at building a highly reconfigurable
experimental Grid platform gathering 9 sites and featuring a total of
5000 CPUs. Its main purpose is to serve as an experimental testbed for
research in Grid Computing.  To learn more about Grid'5000, read
https://www.grid5000.fr/
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


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



Bug#394280: Can you debug this with echo lines?

2006-10-31 Thread Ola Lundqvist
Hi

Can you add debug lines to /var/lib/dpkg/info/bootsplash.postinst
to pinpoint on what line you get this problem?

Regards,

// Ola

-- 
 - 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#396435: subversion: FTBFS: test switch_tests.py fails

2006-10-31 Thread Lucas Nussbaum
Package: subversion
Version: 1.4.0-5
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000

Hi,

During a rebuild of all packages in etch, I discovered that your package
failed to build on i386.

Relevant parts:
Running all tests in getopt_tests.py...success
Running all tests in basic_tests.py...success
Running all tests in commit_tests.py...success
Running all tests in update_tests.py...success
Running all tests in switch_tests.py...FAILURE
Running all tests in prop_tests.py...success
Running all tests in schedule_tests.py...success
Running all tests in log_tests.py...success
Running all tests in copy_tests.py...success
[...]
At least one test FAILED, checking
/build/root/subversion-1.4.0/BUILD/tests.log
FAIL:  switch_tests.py 17: refresh the WC file system read-only
attribute 
At least one test was SKIPPED, checking
/build/root/subversion-1.4.0/BUILD/tests.log
SKIP:  utf8_tests.py 1: conversion of paths and logs to/from utf8
SKIP:  svnsync_tests.py 14: verify that unreadable content is not synced
SKIP:  svnsync_tests.py 15: verify that copies from unreadable dirs work
SKIP:  authz_tests.py 1: authz issue #2486 - open root
SKIP:  authz_tests.py 2: authz issue #2486 - open directory
SKIP:  authz_tests.py 3: broken authz files cause errors
SKIP:  authz_tests.py 4: test authz for read operations
SKIP:  authz_tests.py 5: test authz for write operations
SKIP:  authz_tests.py 6: test authz for checkout
SKIP:  authz_tests.py 7: test authz for log and tracing path changes
SKIP:  authz_tests.py 8: test authz for checkout and update
SKIP:  authz_tests.py 9: test authz for export with unreadable subfolder
make[2]: *** [check] Error 1

The full build log is available from 
http://ox.blop.info/bazaar/buildlogs/20061028/

I tried to build several times and encountered the same failure each
time.

About the archive rebuilt:
The rebuilt was done on about 60 AMD64 nodes of the Grid'5000 platform,
using a chroot containing an etch i386 environment (not unstable).
Internet was not accessible from the build nodes.

About Grid'5000:
The Grid'5000 project aims at building a highly reconfigurable
experimental Grid platform gathering 9 sites and featuring a total of
5000 CPUs. Its main purpose is to serve as an experimental testbed for
research in Grid Computing.  To learn more about Grid'5000, read
https://www.grid5000.fr/
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


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



Bug#396419: junitperf: FTBFS: failed tests (race condition ?)

2006-10-31 Thread Lucas Nussbaum
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.996 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.996 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.002 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.999 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.999 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.999 sec
[junit] Testcase: testOneSecondResponse took 0.001 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 0.003 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 1 sec
[junit] Testcase: testOneSecondResponse took 0.004 sec
[junit] Testcase: testOneSecondResponse took 1.004 sec

BUILD FAILED
/build/root/junitperf-1.9.1/build.xml:82: Test 
com.clarkware.junitperf.ExamplePerfTestSuite failed

Total time: 29 seconds
make: *** [debian/stamp-ant-build] Error 1
**
Build finished at 20061031-1802
FAILED [dpkg-buildpackage died]
Purging 
/var/lib/schroot/mount/etch32-636552eb-2ae6-49c5-80a6-bbc7c77457f9/build/root/junitperf-1.9.1

It is important to note that the build did not fail each time: I built it 3 
times, and it failed 2 times. So it is likely to be caused by a race condition 
or something.

About the archive rebuilt:
The rebuilt was done on about 60 AMD64 nodes of the Grid'5000 platform,
using a chroot containing an etch i386 environment (not unstable).
Internet was not accessible from the build nodes.

About Grid'5000:
The Grid'5000 project aims at building a highly reconfigurable
experimental Grid platform gathering 9 sites and featuring a total of
5000 CPUs. Its main purpose is to serve as an experimental testbed for
research in Grid Computing.  To learn more about Grid'5000, read
https://www.grid5000.fr/
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


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



Bug#394953: marked as done (qt4-x11_4.2.1-1(hppa/unstable): FTBFS: missing defines)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 09:26:59 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#394953: fixed in qt4-x11 4.2.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: qt4-x11
Version: 4.2.1-1
Severity: serious

There was an error while trying to autobuild your package:

 Automatic build of qt4-x11_4.2.1-1 on bld-3 by sbuild/hppa 85
 Build started at 20061023-1856

[...]

 ** Using build dependencies supplied by package:
 Build-Depends: debhelper (= 5.0.0), libxext-dev (= 4.3.0.dfsg.1-4), 
 libxrandr-dev (= 4.3.0.dfsg.1-4), x11proto-core-dev, libsm-dev (= 
 4.3.0.dfsg.1-4), libxmu-dev (= 4.3.0.dfsg.1-4), libice-dev (= 
 4.3.0.dfsg.1-4), libx11-dev (= 4.3.0.dfsg.1-4), libxt-dev (= 
 4.3.0.dfsg.1-4), libjpeg62-dev, zlib1g-dev, libmng-dev (= 1.0.3), 
 libpng12-dev, libfreetype6-dev, libmysqlclient15-dev, flex, libpq-dev, 
 libaudio-dev, libcupsys2-dev, xlibmesa-gl-dev | libgl-dev, libglu1-xorg-dev | 
 libglu1-mesa-dev | libglu-dev, libxft-dev, libxrender-dev, libxcursor-dev, 
 cdbs (= 0.4.0), dpatch, libxinerama-dev, libsqlite0-dev, libsqlite3-dev, 
 libdbus-1-dev, libglib2.0-dev

[...]

 /build/buildd/qt4-x11-4.2.1/bin/moc -DQT_SHARED -DQT_BUILD_CORE_LIB 
 -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT 
 -DQT_NO_DEBUG -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
 -I../../mkspecs/linux-g++ -I. -I../../include -I../../include/QtCore -Iglobal 
 -I.moc/release-shared -I.uic/release-shared io/qfilesystemwatcher.h -o 
 .moc/release-shared/moc_qfilesystemwatcher.cpp
 /build/buildd/qt4-x11-4.2.1/bin/moc -DQT_SHARED -DQT_BUILD_CORE_LIB 
 -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT 
 -DQT_NO_DEBUG -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
 -I../../mkspecs/linux-g++ -I. -I../../include -I../../include/QtCore -Iglobal 
 -I.moc/release-shared -I.uic/release-shared io/qfilesystemwatcher.cpp -o 
 .moc/release-shared/qfilesystemwatcher.moc
 g++ -c -pipe -g -I/usr/include/freetype2 -I/usr/include/glib-2.0 
 -I/usr/lib/glib-2.0/include -O2 -fvisibility=hidden 
 -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC  -DQT_SHARED 
 -DQT_BUILD_CORE_LIB -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS 
 -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_NO_DEBUG -D_LARGEFILE64_SOURCE 
 -D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++ -I. -I../../include 
 -I../../include/QtCore -Iglobal -I.moc/release-shared -I.uic/release-shared 
 -o .obj/release-shared/qfilesystemwatcher.o io/qfilesystemwatcher.cpp
 g++ -c -pipe -g -I/usr/include/freetype2 -I/usr/include/glib-2.0 
 -I/usr/lib/glib-2.0/include -O2 -fvisibility=hidden 
 -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC  -DQT_SHARED 
 -DQT_BUILD_CORE_LIB -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS 
 -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_NO_DEBUG -D_LARGEFILE64_SOURCE 
 -D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++ -I. -I../../include 
 -I../../include/QtCore -Iglobal -I.moc/release-shared -I.uic/release-shared 
 -o .obj/release-shared/qfsfileengine_unix.o io/qfsfileengine_unix.cpp
 /build/buildd/qt4-x11-4.2.1/bin/moc -DQT_SHARED -DQT_BUILD_CORE_LIB 
 -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT 
 -DQT_NO_DEBUG -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
 -I../../mkspecs/linux-g++ -I. -I../../include -I../../include/QtCore -Iglobal 
 -I.moc/release-shared -I.uic/release-shared io/qprocess_unix.cpp -o 
 .moc/release-shared/qprocess_unix.moc
 g++ -c -pipe -g -I/usr/include/freetype2 -I/usr/include/glib-2.0 
 -I/usr/lib/glib-2.0/include -O2 -fvisibility=hidden 
 -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC  -DQT_SHARED 
 -DQT_BUILD_CORE_LIB -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS 
 -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_NO_DEBUG -D_LARGEFILE64_SOURCE 
 -D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++ -I. -I../../include 
 -I../../include/QtCore -Iglobal -I.moc/release-shared -I.uic/release-shared 
 -o .obj/release-shared/qprocess_unix.o io/qprocess_unix.cpp
 g++ -c -pipe -g -I/usr/include/freetype2 -I/usr/include/glib-2.0 
 -I/usr/lib/glib-2.0/include -O2 -fvisibility=hidden 
 -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC  -DQT_SHARED 
 -DQT_BUILD_CORE_LIB -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS 
 -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_NO_DEBUG -D_LARGEFILE64_SOURCE 
 -D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++ -I. -I../../include 
 -I../../include/QtCore -Iglobal -I.moc/release-shared -I.uic/release-shared 
 -o .obj/release-shared/qfilesystemwatcher_inotify.o 
 

Bug#395203: #395203 might be caused by a race condition: difficult to reproduce

2006-10-31 Thread Lucas Nussbaum
Hi,

I've tried several times (6 times) to rebuild bzr but couldn't reproduce
the failure. The bug might be caused by a race condition. It would be
great if somebody could audit the tests, but I don't mind if it is preferred
to just ignore this bug...

Lucas


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



Bug#396345: marked as done (tomboy: Tomboy does not start)

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 09:08:14 -0800 (PST)
with message-id [EMAIL PROTECTED]
and subject line Bug#396345: tomboy: Tomboy does not start
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: tomboy
Version: 0.4.1-2
Severity: grave
Justification: renders package unusable


Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Andrey Fedoseev [EMAIL PROTECTED]
To: Debian Bug Tracking System [EMAIL PROTECTED]
Subject: tomboy: Tomboy does not start
Message-ID: [EMAIL PROTECTED]
X-Mailer: reportbug 3.30
Date: Tue, 31 Oct 2006 15:33:02 +0500

Package: tomboy
Version: 0.4.1-2
Severity: grave
Justification: renders package unusable

When trying to run tomboy I get:

[START]
** ERROR **: file threadpool.c: line 990 (mono_thread_pool_init): 
assertion failed: (async_call_klass)
aborting...

=
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=

Stacktrace:

Native stacktrace:

/usr/lib/libmono.so.0 [0xa7df0dd2]
/usr/lib/libmono.so.0 [0xa7dc46ec]
[0xe440]
/lib/tls/i686/cmov/libc.so.6(abort+0x109) [0xa7b7dfb9]
/usr/lib/libglib-2.0.so.0(g_logv+0x454) [0xa7d10114]
/usr/lib/libglib-2.0.so.0(g_log+0x29) [0xa7d10149]
/usr/lib/libglib-2.0.so.0(g_assert_warning+0x77) [0xa7d101c7]
/usr/lib/libmono.so.0 [0xa7e8dd62]
/usr/lib/libmono.so.0(mono_runtime_init+0x23) [0xa7e95505]
/usr/lib/libmono.so.0 [0xa7dc5b74]
/usr/lib/libmono.so.0(mono_main+0x1388) [0xa7de1fe5]
mono [0x8048522]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) 
[0xa7b68ea8]
mono [0x8048471]

Debug info from gdb:

(no debugging symbols found)
Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1481300288 (LWP 18461)]
[New Thread -1484702800 (LWP 18462)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xe410 in __kernel_vsyscall ()
  2 Thread -1484702800 (LWP 18462)  0xe410 in __kernel_vsyscall ()
  1 Thread -1481300288 (LWP 18461)  0xe410 in __kernel_vsyscall ()

Thread 2 (Thread -1484702800 (LWP 18462)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xa7cbf016 in __nanosleep_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xa7ec8b4b in mono_type_full_name () from /usr/lib/libmono.so.0
#3  0xa7cb9240 in start_thread () from 
/lib/tls/i686/cmov/libpthread.so.0
#4  0xa7c1f27e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1481300288 (LWP 18461)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xa7be19a9 in fork () from /lib/tls/i686/cmov/libc.so.6
#2  0xa7cc05b4 in fork () from /lib/tls/i686/cmov/libpthread.so.0
#3  0xa7d320c9 in g_spawn_error_quark () from /usr/lib/libglib-2.0.so.0
#4  0xa7d32c9f in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
#5  0xa7d33115 in g_spawn_command_line_sync () from 
/usr/lib/libglib-2.0.so.0
#6  0xa7df0e9a in mono_debugger_run_finally () from 
/usr/lib/libmono.so.0
#7  0xa7dc46ec in mono_jit_thread_attach () from /usr/lib/libmono.so.0
#8  signal handler called
#9  0xe410 in __kernel_vsyscall ()
#10 0xa7b7c821 in raise () from /lib/tls/i686/cmov/libc.so.6
#11 0xa7b7dfb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#12 0xa7d10114 in g_logv () from /usr/lib/libglib-2.0.so.0
#13 0xa7d10149 in g_log () from /usr/lib/libglib-2.0.so.0
#14 0xa7d101c7 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
#15 0xa7e8dd62 in mono_thread_stop () from /usr/lib/libmono.so.0
#16 0xa7e95505 in mono_runtime_init () from /usr/lib/libmono.so.0
#17 0xa7dc5b74 in mono_jit_thread_attach () from /usr/lib/libmono.so.0
#18 0xa7de1fe5 in mono_main () from /usr/lib/libmono.so.0
#19 0x08048522 in ?? ()
#20 0x0002 in ?? ()
#21 0xafeb23f4 in ?? ()
#22 0xafeb2378 in ?? ()
#23 0x0804854f in ?? ()
#24 0xa7b5ec8c in ?? () from /lib/tls/i686/cmov/libc.so.6
#25 

Bug#396418: cogito: FTBFS: failed tests

2006-10-31 Thread Lucas Nussbaum
Package: cogito
Version: 0.18-1
Severity: serious
Justification: FTBFS on i386, very likely to fail everywhere else
Usertags: grid5000

Hi,

During a rebuild of all packages in etch, I discovered that your package
failed to build on i386.

I tried to build it several times to make sure the issue was not transient. The
package FTBFS each time.

Relevant parts:
Committed as a265e9550297ecc680968d12842096fd443cfd99
Tagged a265e9550297ecc680968d12842096fd443cfd99 as rpn-0.3
updating 'refs/heads/master'
  from 49cadf44c5d6239b41b19f6869b11a62ab251905
  to   a265e9550297ecc680968d12842096fd443cfd99
updating 'refs/tags/rpn-0.3'
  from 
  to   1e2f3d6f74e3ee8cef0085cf4fc330e0ecbc6521
Unpacking 9 objects
refs/heads/master: 49cadf44c5d6239b41b19f6869b11a62ab251905 - 
a265e9550297ecc680968d12842096fd443cfd99
refs/tags/rpn-0.3:  - 
1e2f3d6f74e3ee8cef0085cf4fc330e0ecbc6521
Creating new branch bob: a265e9550297ecc680968d12842096fd443cfd99
Switching to branch bob...
Heads:
boba265e9550297ecc680968d12842096fd443cfd99
 master a265e9550297ecc680968d12842096fd443cfd99
   R public a265e9550297ecc680968d12842096fd443cfd99
bobswork
/build/root/cogito-0.18/cogito-0.18/Documentation/tutorial-script/Playground/Bob/rpn
public  
/build/root/cogito-0.18/cogito-0.18/Documentation/tutorial-script/Playground/Alice/rpn.git
Using hard links
Fetching head...
Fetching objects...
Fetching tags...
unable to fetch tags (non-fatal)
New branch: 29b576f8fa3ba1e93313c7486d69246891230b8a

Applying changes...
Merging 49cadf44c5d6239b41b19f6869b11a62ab251905 - 
29b576f8fa3ba1e93313c7486d69246891230b8a
to a265e9550297ecc680968d12842096fd443cfd99 ...
... Auto-merging rpn.c
CONFLICTS during merge.
... Auto-merging stack.c

Conflicts during merge. Do cg-commit after resolving them.
cg-reset will cancel the merge.

Committed as 4717c27d0b3666bc5037c9b57975d37884c2387d
patching file Makefile
patching file stack.h
M Makefile
M stack.h
Committed as a6a49affb5afdf8a5129437882b486ee435cbbbf
defaulting to local storage area
Using hard links
Fetching head...
Fetching objects...
Fetching tags...
Missing tag rpn-0.1...
Missing tag rpn-0.2...
Missing tag rpn-0.3...
unable to fetch tags (non-fatal)
New branch: a265e9550297ecc680968d12842096fd443cfd99
Cloned to rpn/ (origin 
/build/root/cogito-0.18/cogito-0.18/Documentation/tutorial-script/Playground/Alice/rpn.git
 available as branch origin)
Restoring file rpn.c
patching file Makefile
patching file lexer.c
patching file rpn.c
Adding file lexer.h
M Makefile
M lexer.c
A lexer.h
M rpn.c
Committed as aadff1934aba425738c4280e502b92cfe96d58db
Invalid id: rpn-0.3
Unexpected error 1 on line 205
make[3]: *** [test] Error 1
make[3]: Leaving directory 
`/build/root/cogito-0.18/cogito-0.18/Documentation/tutorial-script'
make[2]: *** [test] Error 2
make[2]: Leaving directory `/build/root/cogito-0.18/cogito-0.18/Documentation'
make[1]: *** [test] Error 2
make[1]: Leaving directory `/build/root/cogito-0.18/cogito-0.18'
make: *** [build-stamp] Error 2
**

About the archive rebuilt:
The rebuilt was done on about 60 AMD64 nodes of the Grid'5000 platform,
using a chroot containing an etch i386 environment (not unstable).
Internet was not accessible from the build nodes.

About Grid'5000:
The Grid'5000 project aims at building a highly reconfigurable
experimental Grid platform gathering 9 sites and featuring a total of
5000 CPUs. Its main purpose is to serve as an experimental testbed for
research in Grid Computing.  To learn more about Grid'5000, read
https://www.grid5000.fr/
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


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



Bug#396277: allows creating any file as root

2006-10-31 Thread Steve Kemp

Daniel

  Please find attached the patch I'm going to use for the security
 update.

  Could you please apply it, or a comparable patch to the version
 in unstable and let us know which version will fix the problem?

Steve
-- 
# The Debian Security Audit Project.
http://www.debian.org/security/audit

[EMAIL PROTECTED]:/tmp$ interdiff thttpd_2.23beta1-3sarge1.diff  
thttpd_2.23beta1-3sarge2.diff
diff -u thttpd-2.23beta1/debian/changelog thttpd-2.23beta1/debian/changelog
--- thttpd-2.23beta1/debian/changelog
+++ thttpd-2.23beta1/debian/changelog
@@ -1,3 +1,11 @@
+thttpd (2.23beta1-3sarge2) stable-security; urgency=high
+
+  * Non-maintainer upload by the Security Team.
+  * Fix the insecure use of temporary files when invoked by logrotate.
+[CVE-2006-4248]
+
+ -- Steve Kemp [EMAIL PROTECTED]  Tue, 31 Oct 2006 17:49:34 +
+
 thttpd (2.23beta1-3sarge1) stable-security; urgency=high

   * Non-maintainer upload by the Security Team
diff -u thttpd-2.23beta1/debian/thttpd.logrotate 
thttpd-2.23beta1/debian/thttpd.logrotate
--- thttpd-2.23beta1/debian/thttpd.logrotate
+++ thttpd-2.23beta1/debian/thttpd.logrotate
@@ -4,15 +4,9 @@
 compress
 missingok
 delaycompress
-prerotate
-   if pidof thttpd 21  /dev/null; then
-   touch /tmp/start_thttpd
-   fi
-endscript
 postrotate
-   if [ -f /tmp/start_thttpd ]; then
+if [ -f /var/run/thttpd.pid ]; then
/etc/init.d/thttpd restart 21  /dev/null
-   rm -f /tmp/start_thttpd
fi
 endscript
 }



signature.asc
Description: Digital signature


Bug#396363: FTBFS: Makefile:69: *** target pattern contains no `%'. Stop.

2006-10-31 Thread Goswin von Brederlow
Ionut Georgescu [EMAIL PROTECTED] writes:

 Have you altered the sources in any way? Please check your building
 environment. grace 1:5.1.20-3 build OK on all architectures, including
 amd64

 http://buildd.debian.org/build.php?arch=pkg=grace

 Ionut

I saw that too and I saw a few more of the same errors in other
packages. I stoped on reporting anymore after recognising that pattern
and you are just unlucky to be at the top of the failed list.

The source is not altered in any way and the build environment is a
up-to-date sid chroot (updated daily after the mirror pusle) but not
neccesarily a clean one (cleaning is done once a day before updates
but not between builds). Building is done with

apt-get --only-source build-dep grace=1:5.1.20-3
apt-get --only-source source grace=1:5.1.20-3
cd */  debuild -us -uc -B

I have no idea what causes this. I would suspect the last make
upload. But packages have been build fine a month after that and now
they fail. The buildd chroots should have had the latest make by then.

Can you reproduce it?

MfG
Goswin


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



Bug#396277: possible fix?

2006-10-31 Thread Kees Cook
Tags: patch

Seems like the tmp file isn't needed at all?  Possible patch attached.

-- 
Kees Cook@outflux.net
diff -u thttpd-2.23beta1/debian/thttpd.logrotate 
thttpd-2.23beta1/debian/thttpd.logrotate
--- thttpd-2.23beta1/debian/thttpd.logrotate
+++ thttpd-2.23beta1/debian/thttpd.logrotate
@@ -4,15 +4,9 @@
 compress
 missingok
 delaycompress
-prerotate
-   if pidof thttpd 21  /dev/null; then
-   touch /tmp/start_thttpd
-   fi
-endscript
 postrotate
-   if [ -f /tmp/start_thttpd ]; then
+   if pidof thttpd 21  /dev/null; then
/etc/init.d/thttpd restart 21  /dev/null
-   rm -f /tmp/start_thttpd
fi
 endscript
 }


Bug#396459: libsdl1.2-dev: Dropping *-dev dependencies breaks package builds too close to release

2006-10-31 Thread Daniel Schepler
Package: libsdl1.2-dev
Version: 1.2.11-6
Severity: serious
Tags: sid

After the recent upload of libsdl1.2-dev downgrading the *-dev dependencies to 
recommends, lots of packages (for example mednafen, missing a libgl-dev 
dependency) have started failing to build from source because they don't 
properly declare those dependencies themselves introduced by their own 
source.  While this is unquestionably a bug in the other packages, the change 
breaks too many packages close to release time, so in my opinion the new 
version of libsdl1.2-dev should not make it into etch.

(Sorry debian-release for not doing X-Debbugs-CC, but kmail still doesn't 
support setting custom headers afaict...)
-- 
Daniel Schepler


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



Processed: this sounds like an ideal candidate for a nmu

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 retitle 394773 minor change needed for compatibility with gaim2.0.0beta4
Bug#394773: Needs to be rebuilt for gaim 2.0.0beta4
Changed Bug title.

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


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



Processed: severity of 391093 is important

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.22
 severity 391093 important
Bug#391093: ntp upgrade from 1:4.2.2+dfsg.2-2 to 1:4.2.2+dfsg.2-3 fails
Bug#391352: Upgrade problem (user ntp does not exist)
Severity set to `important' from `serious'


End of message, stopping processing here.

Please contact me if you need assistance.

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


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



Bug#396435: subversion: FTBFS: test switch_tests.py fails

2006-10-31 Thread Peter Samuelson

[Lucas Nussbaum]
 During a rebuild of all packages in etch, I discovered that your
 package failed to build on i386.

Don't build subversion as root.
Can I close this bug?


signature.asc
Description: Digital signature


Bug#396449: e2defrag - Unable to allocate buffer for inode priorities

2006-10-31 Thread Theodore Tso
Package: defrag
Version: 0.73pjm1-8
Severity: grave

On Wed, Nov 01, 2006 at 01:10:50AM +0800, Andreas Dilger wrote:
  So now it was time to defrag, I used this command:
  thor:~# e2defrag -r /dev/vgraid/data
 
 This program is dangerous to use and any attempts to use it should be
 stopped.  It hasn't been updated in such a long time that it doesn't
 even KNOW that it is dangerous (i.e. it doesn't check the filesystem
 version number or feature flags).

In fact we need to create a Debian bug report indicating that this
package should *NOT* be included when the Debian etch distribution
releases.  

Goswin, I am setting the severity to grave (a release-critical
severity) because defrag right now is almost guaranteed to corrupt the
filesystem if used with modern ext3 filesystems leading to data loss,
and this satisfies the definition of grave.  I believe the correct
answer is either to (a) make defrag refuse to run if any filesystem
features are enabled (at the very least, resize_inode, but some of the
other newer ext3 filesystem features make me nervous with respect to
e2defrag, or (b) since (a) would make e2defrag mostly useless
especially since filesystems with resize inodes are created by default
in etch, and as far as I know upstream abandoned defrag a long time
ago, that we should simply remove e2defrag from etch and probably from
Debian altogether.

If you are interested in doing a huge amount of auditing and testing
of e2defrag with modern ext3 (and soon ext4) filesystems, that's
great, but I suspect that will not at all be trivial, and even making
sure e2defrag won't scramble users' data probably can't be achievable
before etch releases.

Regards,


- Ted


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



Bug#395079: Changing severity of 395079

2006-10-31 Thread Ionut Georgescu
It's been fixed. Upload is on the way.

On Tue, 2006-10-31 at 13:29 +0100, Goswin von Brederlow wrote:
 Failure to install is RC.
 
 
 



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



Bug#395252: embedded code copies are not RC

2006-10-31 Thread Aurélien GÉRÔME
Hi Diego,

On Tue, Oct 31, 2006 at 07:46:01PM +0100, Diego Biurrun wrote:
 Removing the embedded copies of FFmpeg libraries from MPlayer is a bad
 idea.

For the workload on the security team and the overall quality of Debian
(a single source package for whatever produced binary packages),
I strongly disagree.

 The relationship between MPlayer and FFmpeg is very intimate to say the
 least.  MPlayer uses FFmpeg HEAD via a svn:external declaration.  In the
 future we will move both to a common repository.  Most FFmpeg developers
 work on MPlayer as well.

Other software also use ffmpeg. AFAIK, ffmpeg do *not* need mplayer
to work.

 FFmpeg is highly volatile and fast-moving.  The FFmpeg snapshot in
 Debian is two months older than the one in MPlayer 1.0rc1.  This may not
 sound much, but it means more than 600 (!) commits to the FFmpeg
 repository.
 
 Using the Debian version of FFmpeg in MPlayer would create a beast
 entirely different from 1.0rc1.  Several codecs have been added which
 were only available through binaries before, many bugs have been fixed
 and speed improvements committed.

The Debian version can also be updated. I fail to see the issue here.
Samuel Hocevar, the Debian ffmpeg maintainer, is really open-minded
and cooperative.

 A H.264 video decoding benchmark done by a fellow developer gives the
 following numbers:
 
 self-built custom binary:  13.9 seconds
 Debian MPlayer package:14.7 seconds
 binary with Debian's FFmpeg:   17.7 seconds
 
 The Debian FFmpeg binary was built against dynamic FFmpeg, the other two
 with static FFmpeg.  That's a massive 20% performance degradation..
 
 Using a shared dynamic version of FFmpeg would disable several video
 filters, so there would be even more feature loss.

First, on what architecture did you test that? I expect the gap
to be reduced on non-x86 architectures. x86 is a register-starved
architecture and one of those four general purpose registers is used
by PIC code, so dynamic linking can really drop the performance as
your benchmark shows.

Then, I can agree with you that static linking has better performance.
Therefore, what I can recommand is to build mplayer statically, but
with a Debian up-to-date ffmpeg package. I am CCing Samuel Hocevar
to get his opinion on the matter...

 Plus I expect random bugs to creep up.  As mentioned above  FFmpeg is
 highly volatile and fast-moving.  Backwards-compatibility is not a
 priority.

That will *not* happen with an up-to-date ffmpeg package which other
packages might benefit from.

Cheers,
-- 
 .''`.   Aurélien GÉRÔME
: :'  :
`. `'`   Free Software Developer
  `- Unix Sys  Net Admin


signature.asc
Description: Digital signature


Processed: tagging 395961

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.22
 tags 395961 pending
Bug#395961: Please, include GPL exception in debian/copyright
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#396277: allows creating any file as root

2006-10-31 Thread Daniel Baumann
Steve Kemp wrote:
 Daniel
 
   Please find attached the patch I'm going to use for the security
  update.

Thanks.

   Could you please apply it, or a comparable patch to the version
  in unstable and let us know which version will fix the problem?

I'll apply your patch, and upload in about 10 minutes.

(JFTR: thttpd is one of the last packages which contains the old
email-address which I'm not reading during the day, therefore you didn't
get an answer earlier.)

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


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



Processed: severity of 395961 is serious

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.22
 severity 395961 serious
Bug#395961: Please, include GPL exception in debian/copyright
Severity set to `serious' from `wishlist'


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#394773: this sounds like an ideal candidate for a nmu

2006-10-31 Thread peter green
retitle 394773 minor change needed for compatibility with gaim2.0.0beta4
thanks

this sounds like an ideal candidate for a nmu, i've changed that title as it 
misleadingly implied that a binnmu would have fixed this.







Bug#396466: libsdl-mixer1.2-dev: package dependencies disagree with libSDL_mixer.la (over libasound and others)

2006-10-31 Thread Yann Dirson
Package: libsdl-mixer1.2-dev
Version: 1.2.6-1.1+b1
Severity: grave

This bug is strictly similar to libsdl1.2's #396063:

/usr/lib/libSDL_mixer.la refers to many libraries (eg. libasound), which
are not (and should not be) pulled by the package's dependencies.

This makes packages (such as gcompris) not build from source any more.

Note: this particular bug was hidden by libsdl1.2-dev depending on
libasound2-dev, which it now only recommends.  This will trigger many
other FTBFS.

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

Versions of packages libsdl-mixer1.2-dev depends on:
ii  libc6-dev  2.3.6.ds1-4   GNU C Library: Development Librari
ii  libogg-dev 1.1.3-2   Ogg Bitstream Library Development
ii  libsdl-mixer1.21.2.6-1.1+b1  mixer library for Simple DirectMed
ii  libsdl1.2-dev  1.2.11-4  Simple DirectMedia Layer developme
ii  libsmpeg-dev   0.4.5+cvs20030824-1.9 SDL MPEG Player Library - developm
ii  libvorbis-dev  1.1.2.dfsg-1.2The Vorbis General Audio Compressi

libsdl-mixer1.2-dev recommends no packages.

-- no debconf information


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



Bug#295270: Messages cannot be deleted and index file gets corrupted when there isn't enough disk space

2006-10-31 Thread Øystein Gisnås

package evolution-data-server
tags 295270 unreproducible
thanks

2006/10/29, Ben Hutchings [EMAIL PROTECTED]:

The problem appears to be that camel_mbox_summary_sync_mbox() in
camel/providers/local/camel-mbox-summary.c marks changes in the summary
as having been applied to the folder as soon as they have been applied
to the new mbox file, even though an error later on - such as running
out of disk space - will result in the new mbox file being removed.  It
should process all summary updates after updating the mbox file.  (Also,
possibly it should delete the summary files immediately before replacing
the mbox file.)

Fabian, this code is specific to mbox but there may be similar problems
with summary/folder synchronisation for other access methods.


Nice observation. I'm still not able to create a case which reproduces
this, though.

Actually this is the top priority bug in evolution. If anyone could
provide steps to reproduce this consistently, it would be of
tremendous help. It's also interesting to get in touch with users that
experience this more or less regularly.

Thanks,
Øystein



Processed: Re: Bug#295270: Messages cannot be deleted and index file gets corrupted when there isn't enough disk space

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 package evolution-data-server
Ignoring bugs not assigned to: evolution-data-server

 tags 295270 unreproducible
Bug#295270: Messages cannot be deleted and index file gets corrupted when there 
isn't enough disk space
Tags were: help upstream
Bug#347703: Error while Refreshing folder: Summary and folder mismatch, even 
after a sync
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#396352: azureus: incorrect jar specified in /usr/share/java-config/libswt-gtk-3.2-java

2006-10-31 Thread tony mancill
Package: azureus
Version: 2.5.0.0-1
Followup-For: Bug #396352

The problem appears to lie with more recent versions of
libswt-gtk-3.2-java.  The 3.2.1 version of this package ships
/usr/share/java/swt-gtk-3.2.1.jar, but the config file referenced in the
azureus startup script (/usr/bin/azureus) is:

/usr/share/java-config/libswt-3.2-java -
/etc/alternatives/libswt-3.2-java

$ cat /etc/alternatives/libswt-3.2-java
JARS=/usr/share/java/swt-gtk-3.2.jar

Updating /usr/share/java-config/libswt-3.2-java by hand to contain:

JARS=/usr/share/java/swt-gtk-3.2.1.jar

Fixes the problem on my system.

HTH,
tony

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

Versions of packages azureus depends on:
ii  gij-4.0 [java-virtual-mac 4.0.3-2The GNU Java bytecode interpreter
ii  gij-4.1 [java2-runtime]   4.1.1-17   The GNU Java bytecode interpreter
ii  java-gcj-compat   1.0.65-8   Java runtime environment using GIJ
ii  kaffe-pthreads [java-virt 2:1.1.7-4  A POSIX threads enabled version of
ii  libcommons-cli-java   1.0-8  API for working with the command l
ii  liblog4j1.2-java  1.2.13-2   Logging library for java
ii  libseda-java  3.0-3  the Staged Event-Driven Architectu
ii  libswt-gtk-3.2-java   3.2.1-1Standard Widget Toolkit for GTK Ja
ii  sun-j2sdk1.5 [java2-runti 1.5.0+update06 Java(TM) 2 SDK, Standard Edition, 
ii  sun-java5-jre [java2-runt 1.5.0-08-1 Sun Java(TM) Runtime Environment (

Versions of packages azureus recommends:
ii  java-package  0.28   utility for building Java(TM) 2 re

-- no debconf information


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



Processed: Re: Bug#396435: subversion: FTBFS: test switch_tests.py fails

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 396435 important
Bug#396435: subversion: FTBFS: test switch_tests.py fails
Severity set to `important' from `serious'

 retitle 396435 subversion: should be buildable as root (failed test when 
 built as root)
Bug#396435: subversion: FTBFS: test switch_tests.py fails
Changed Bug title.

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


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



Bug#392016: ELOG security audit

2006-10-31 Thread Ulf Harnhammar
Hello,

I have performed a security audit of ELOG and here is what I found:


1) There are some incorrect handling of *printf() calls and format
strings. They lead to ELOG crashing completely, with the potential
of executing arbitrary machine code programs, when a user uploads
and submits as the first attachment in an entry a file called
%n%n%n%n - or similar - which must not be empty.

The attached patch fixes this in two places and many other format
string problems just to be sure.


2) There is a Cross-site Scripting issue when requesting correctly
named but non-existant files for downloading, like with this URL:

http://localhost:8080/demo/123456_789012/%3Cscript%3Ealert(%22XSS%22)%3C/script%3E

The attached patch corrects this by quoting the dangerous characters.


3) There are also Cross-site Scripting issues when creating new
entries with New. If a document sends data to ELOG where the
fields Type and Category contain invalid entries with HTML code,
the resulting error document will print the Type or Category data
as-is with no quoting.

The attached patch corrects this minor problem as well.


I have verified that all three problems exist in Debian unstable,
as well as in the upstream ELOG-2.6.2 version. I haven't checked
any other versions (but the upstream SVN trunk looks like it also
has these bugs).


// Ulf Harnhammar, Debian Security Audit Project
   http://www.debian.org/security/audit/



-- 
___
Surf the Web in a faster, safer and easier way:
Download Opera 9 at http://www.opera.com

Powered by Outblaze


elog.security.patch
Description: Binary data


Bug#396435: subversion: FTBFS: test switch_tests.py fails

2006-10-31 Thread Lucas Nussbaum
severity 396435 important
retitle 396435 subversion: should be buildable as root (failed test when built 
as root)
thanks

On 31/10/06 at 15:52 -0600, Peter Samuelson wrote:
 
 [Lucas Nussbaum]
  During a rebuild of all packages in etch, I discovered that your
  package failed to build on i386.
 
 Don't build subversion as root.
 Can I close this bug?

Not allowing to build as root is a bad idea. You should detect that
the build is running as root and ignore the result of this specific
test, not just fail like that.

I'm going to ignore subversion for all my future tests, but you should
leave that bug open so it won't get reported again by others.
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


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



Bug#395104: running mkdir /usr/lib/haskell-packages/ghc6/lib/MissingPy-0.8.6/ghc-6.6/include allows the package to install fine

2006-10-31 Thread Rafael Kitover

see subject.


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



Bug#395252: embedded code copies are not RC

2006-10-31 Thread A Mennucc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

hi

I would like to add my 2¢ (although Dario's email pretty much says it all)

Here are 3 possible scenarios:

[N] The safest way to linking MPlayer with dynamical FFmpeg would be :
each time there is a MPlayer release, Diego provides us with the correct
SVN release number for FFmpeg, and   both the proper mplayer and
ffmpeg package are uploaded into Debian at the same time.

[O] we forcibly link MPlayer to the older FFmpeg. To do this, we would
need to extensively patch the version of MPlayer in Debian. In practice,
we would break MPlayer, as people expect it to be: many features that
are into 1.0rc1 are due to the new ffmpeg, and they would be lost.

[A] We leave things as they are now. MPlayer links tonew FFmpeg inside
it; ffmpeg outside is left unchanged (...we are near the freeze...).

Some comments:

Sam Hocevar (mantainer of ffmpeg) in March had expressed concerns
similar to that in the bug; I have then contacted him to hear also his
opinion about [N] (I did yet not receive a response).

The problem of [N], as Diego was pointing, is that FFmpeg does not have
a solid API yet.  We cannot exclude that an update of FFmpeg may break
Xine, or other packages. I checked that xine ships a old and patched
FFmpeg library inside, but the Debian package is currently linked to the
external FFmpeg ; whereas the version of FFmpeg that is inside MPlayer
is even newer. I have contacted Siggi Langauf (mantainer of Xine) to
hear his opinion as well (I did yet not receive a response).

The overhead [O] may simply be not worth the (supposed) future benefit
for security. Since the development of FFmpeg is done jointly with the
development of MPlayer , then a security bug in FFmpeg will be fixed in
upstream MPlayer before than in any other package using FFmpeg. In case
[O] , applying the fix would require  sorting also thru our patches (and
we cannot even ask help upstream !). In case [N] , it may be the case
that the fix  is more easier to apply. In case [A] , we have double work
to do (but I will take care of the fix for MPlayer, I promise :-)

So I think that
[O] is not worth the effort: we ruin MPlayer (for sure) for hope of a
(not sure) benefit in security.
(I really want to abide to (4): We will be guided by the needs of our
users and the free software community. )
[N] is too far fetched

So here is my proposal: let us stick with [A], and downgrade this bug
for the time of the Etch release; in a year or so, it may be that FFmpeg
will be stable enough that we really can try [N] for the next release.

a.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFR82c9B/tjjP8QKQRAkLqAJ9wY4dUjlKAWV19O9Z9kdFtoLAnswCfXK0i
DhgvIpEc+oxgkV8rbYfoCRA=
=xpc5
-END PGP SIGNATURE-


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



Bug#396410: grdesktop eats all memory and freezes the whole system

2006-10-31 Thread Steve Langasek
severity 396410 important
tags 396410 unreproducible
thanks

On Tue, Oct 31, 2006 at 03:22:25PM +0100, Adalbert Dawid wrote:

 When I launch grdesktop, it eats up the whole memory of my machine 
 (1 GB) whithin one or two seconds and freezes the whole system, forcing me 
 to do a hard reset. This happens *immediately* after starting grdesktop and
 before the grdesktop UI appears. 

Sorry, I can't reproduce this at all.  I don't think we can consider this a
release-critical bug in grdesktop without some information on how to
reproduce it; and indeed, you mention yourself that it only affects one of
two etch machines you've tried it on.

 As a side note, I am running the Gnome desktop on a plain X server
 without compositing. I am able to reproduce the bug with the nvidia and
 the nv driver.

I'm also running gnome on X without compositing on etch for my test.  This
system uses the i810 driver.

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


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



Processed: Re: Bug#396410: grdesktop eats all memory and freezes the whole system

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 396410 important
Bug#396410: grdesktop eats all memory and freezes the whole system
Severity set to `important' from `critical'

 tags 396410 unreproducible
Bug#396410: grdesktop eats all memory and freezes the whole system
There were no tags set.
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#396471: linux-image-2.6.18-1-parisc64-smp: fails to install

2006-10-31 Thread Frans Pop
Package: linux-image-2.6.18-1-parisc64-smp
Version: 2.6.18-3
Severity: serious

This issue has been reported several times before, but I've not yet seen 
any real response from the kernel team.

Preconfiguring packages ...
Selecting previously deselected package linux-image-2.6.18-1-parisc64-smp.
(Reading database ... 28539 files and directories currently installed.)
Unpacking linux-image-2.6.18-1-parisc64-smp 
(from .../linux-image-2.6.18-1-parisc64-smp_2.6.18-3_hppa.deb) ...
Done.
Selecting previously deselected package linux-image-2.6-parisc64-smp.
Unpacking linux-image-2.6-parisc64-smp 
(from .../linux-image-2.6-parisc64-smp_2.6.18+3_hppa.deb) ...
Setting up linux-image-2.6.18-1-parisc64-smp (2.6.18-3) ...

 Hmm. The package shipped with a symbolic 
link /lib/modules/2.6.18-1-parisc64-smp/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/2.6.18-1-parisc64-smp/source

Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
Missing Required paramater 'Old' 
at /var/lib/dpkg/info/linux-image-2.6.18-1-parisc64-smp.postinst line 
393.
dpkg: error processing linux-image-2.6.18-1-parisc64-smp (--configure):
 subprocess post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of 
linux-image-2.6-parisc64-smp:
 linux-image-2.6-parisc64-smp depends on 
linux-image-2.6.18-1-parisc64-smp; however:
  Package linux-image-2.6.18-1-parisc64-smp is not configured yet.
dpkg: error processing linux-image-2.6-parisc64-smp (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-2.6.18-1-parisc64-smp
 linux-image-2.6-parisc64-smp
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up linux-image-2.6.18-1-parisc64-smp (2.6.18-3) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
Missing Required paramater 'Old' 
at /var/lib/dpkg/info/linux-image-2.6.18-1-parisc64-smp.postinst line 
393.
dpkg: error processing linux-image-2.6.18-1-parisc64-smp (--configure):
 subprocess post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of 
linux-image-2.6-parisc64-smp:
 linux-image-2.6-parisc64-smp depends on 
linux-image-2.6.18-1-parisc64-smp; however:
  Package linux-image-2.6.18-1-parisc64-smp is not configured yet.
dpkg: error processing linux-image-2.6-parisc64-smp (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-2.6.18-1-parisc64-smp
 linux-image-2.6-parisc64-smp
Press return to continue.


pgpDfqj0X5Hsl.pgp
Description: PGP signature


Bug#396466: Acknowledgement (libsdl-mixer1.2-dev: package dependencies disagree with libSDL_mixer.la (over libasound and others))

2006-10-31 Thread Yann Dirson
After checking, a binNMU will be sufficient.


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



Bug#396475: Celestia seg-faults on start-up

2006-10-31 Thread John Halton

Package: celestia
Version: 1.3.2-4
Severity: grave

Celestia crashes on start-up. This applies whether I start from the 
Gnome menus or from command line, and whether I use celestia, 
celestia-gnome or celestia-glut as the command.


Here's the output from running celestia from a terminal window:

nStars: 112524
Initializing ARB vertex programs . . .
Loading ARB vertex program: shaders/diffuse_arb.vp
Loading ARB vertex program: shaders/specular_arb.vp
Loading ARB vertex program: shaders/haze_arb.vp
Loading ARB vertex program: shaders/bumpdiffuse_arb.vp
Loading ARB vertex program: shaders/bumphaze_arb.vp
Loading ARB vertex program: shaders/shadowtex_arb.vp
Loading ARB vertex program: shaders/diffuse_texoff_arb.vp
Loading ARB vertex program: shaders/rings_arb.vp
Loading ARB vertex program: shaders/ringshadow_arb.vp
Loading ARB vertex program: shaders/night_arb.vp
Loading ARB vertex program: shaders/glossmap_arb.vp
All ARB vertex programs loaded successfully.
render path: 3
DCOP aborting (delayed) call from 'anonymous-29184' to 'celestia'
celestia: ERROR: Communication problem with celestia, it probably crashed.

Similar error for celestia-gnome, but less informative - just says 
Segmentation fault at end instead of DCOP aborting... etc.


Running 2.6.18-1-686, Xorg 7.1, ATI graphics card with fglrx driver 
(OpenGL is working).


If you need any more details then please let me know.

Thanks,

John


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



Bug#395252: embedded code copies are not RC

2006-10-31 Thread Moritz Muehlenhoff
A Mennucc wrote:
 The overhead [O] may simply be not worth the (supposed) future benefit
 for security.

It's not theoretical, but a genuine problem that affects us here and
today. We've had the whole mess for CVE-2005-4048, we're currently
encountering it with CVE-2006-4799/CVE-2006-4800 and we'll have it
again other the course of December 2006 until June 2009, the time
Etch will be supported.

 Since the development of FFmpeg is done jointly with the
 development of MPlayer , then a security bug in FFmpeg will be fixed in
 upstream MPlayer before than in any other package using FFmpeg. In case
 [O] , applying the fix would require  sorting also thru our patches (and
 we cannot even ask help upstream !). In case [N] , it may be the case
 that the fix  is more easier to apply. In case [A] , we have double work
 to do (but I will take care of the fix for MPlayer, I promise :-)

For [O] regular security practices would apply, i.e. keeping interfaces
stable, etc. [A] would not only require to roll out updates twice, but
also the need to backport patches to different versions.

 So I think that
 [O] is not worth the effort: we ruin MPlayer (for sure) for hope of a
 (not sure) benefit in security.

I don't buy the argument of a completely crippled MPlayer. E.g. the
libavcodec in Debian supports the native WMV9 from SoC. And the 25% performance
difference mostly apply to the H264 optimization work by Michael and
Loren over the recent weeks, while for most other codecs the difference will
be negligible.

 (I really want to abide to (4): We will be guided by the needs of our
 users and the free software community. )

It may seem suboptimal from an upstream perspective, but from a distribution
perspective a correct implementation gains more weight.

Cheers,
Moritz














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



Bug#395252: embedded code copies are not RC

2006-10-31 Thread A Mennucc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

BTW: I have been assuming that Moritz is reporting the consensus of the
whole security team , and not only his personal opinion... is it so?

whereas Joey reported the opinion of the release people (that was not
opposite to [A])

I personally may embrace option [N]  but I am not so happy about [O]
... and upstream is not either.

Now I really need to hear the opinion of the xine and ffmpeg Debian
people (and also of gstreamer and any other package using ffmpeg) about [N]

a.


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFR9so9B/tjjP8QKQRAvFgAJ9G3aRwe9l8QlwKci3BunVug+O88wCgoeHg
jPE/dMModloRZ8tLFcadg+Y=
=DJYf
-END PGP SIGNATURE-


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



Bug#383158: sbaz: attempt at resolving FTBFS

2006-10-31 Thread Lex Spoon
Kevin Coyner [EMAIL PROTECTED] wrote:
 While not a user of sbaz or scala, I made an attempt anyway at
 fixing this RC bug.  To start the process I took the orig.tar.gz
 file from the Debian archives and applied the diff and simply
 changed the Build dependency from scala-dev (which is not even in
 Debian and according to snapshot.debian.net never was) to scala and
 started to try and build it in pbuilder sid.

Thanks, Kevin.  I overlooked this problem due to faulty mail filters.

scala-dev has been merged into the main scala package now.  I will
fix that dependency, as well as the other unfortunate problems you ran
into.  Your patch will be very helpful for all of this

-Lex


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



Bug#396471: linux-image-2.6.18-1-parisc64-smp: fails to install

2006-10-31 Thread Sven Luther
On Tue, Oct 31, 2006 at 11:54:09PM +0100, Frans Pop wrote:
 Package: linux-image-2.6.18-1-parisc64-smp
 Version: 2.6.18-3
 Severity: serious
 
 This issue has been reported several times before, but I've not yet seen 
 any real response from the kernel team.
 
 Preconfiguring packages ...
 Selecting previously deselected package linux-image-2.6.18-1-parisc64-smp.
 (Reading database ... 28539 files and directories currently installed.)
 Unpacking linux-image-2.6.18-1-parisc64-smp 
 (from .../linux-image-2.6.18-1-parisc64-smp_2.6.18-3_hppa.deb) ...
 Done.
 Selecting previously deselected package linux-image-2.6-parisc64-smp.
 Unpacking linux-image-2.6-parisc64-smp 
 (from .../linux-image-2.6-parisc64-smp_2.6.18+3_hppa.deb) ...
 Setting up linux-image-2.6.18-1-parisc64-smp (2.6.18-3) ...
 
  Hmm. The package shipped with a symbolic 
 link /lib/modules/2.6.18-1-parisc64-smp/source
  However, I can not read the target: No such file or directory
  Therefore, I am deleting /lib/modules/2.6.18-1-parisc64-smp/source
 
 Running depmod.
 Finding valid ramdisk creators.
 Using mkinitramfs-kpkg to build the ramdisk.
 Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
 Missing Required paramater 'Old' 
 at /var/lib/dpkg/info/linux-image-2.6.18-1-parisc64-smp.postinst line 

Thanks Frans for pointing out this bug, which is exactly the same we already
had some discussion a few weeks ago when it was discovered in the powerpc
packages, and where i was flammed by you and Manoj. Another occasion where you
do exactly the things you are continuously reproaching me. I hope you remember
that next time you want to write some bashing of me in bug reports.

This bug is closed by the new kernel-package version, and linux-2.6 only needs
to be rebuilt with it, which is scheduled for -4, and amply discussed here
previously.

Friendly,

Sven Luther


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



Bug#396459: libsdl1.2-dev: Dropping *-dev dependencies breaks package builds too close to release

2006-10-31 Thread Steve Langasek
On Tue, Oct 31, 2006 at 10:12:17PM +0100, Daniel Schepler wrote:

 After the recent upload of libsdl1.2-dev downgrading the *-dev dependencies 
 to 
 recommends, lots of packages (for example mednafen, missing a libgl-dev 
 dependency) have started failing to build from source because they don't 
 properly declare those dependencies themselves introduced by their own 
 source.  While this is unquestionably a bug in the other packages, the change 
 breaks too many packages close to release time, so in my opinion the new 
 version of libsdl1.2-dev should not make it into etch.

As this is a case of exposing RC bugs in those packages, not causing them,
I'm inclined to disagree.  Do you have a sense of how many packages are
actually affected by this change?  I would hope that in this day and age,
the final count of affected packages would be relatively small.

It's known that some other lib packages depending on libsdl1.2-dev need to
be rebuilt in order for the .la change to propagate upwards, but that should
be a trivial case of binNMUing.

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


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



Bug#396466: marked as done (libsdl-mixer1.2-dev: package dependencies disagree with libSDL_mixer.la (over libasound and others))

2006-10-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Oct 2006 15:27:29 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#396466: libsdl-mixer1.2-dev: package dependencies disagree 
with libSDL_mixer.la (over libasound and others)
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: libsdl-mixer1.2-dev
Version: 1.2.6-1.1+b1
Severity: grave

This bug is strictly similar to libsdl1.2's #396063:

/usr/lib/libSDL_mixer.la refers to many libraries (eg. libasound), which
are not (and should not be) pulled by the package's dependencies.

This makes packages (such as gcompris) not build from source any more.

Note: this particular bug was hidden by libsdl1.2-dev depending on
libasound2-dev, which it now only recommends.  This will trigger many
other FTBFS.

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

Versions of packages libsdl-mixer1.2-dev depends on:
ii  libc6-dev  2.3.6.ds1-4   GNU C Library: Development Librari
ii  libogg-dev 1.1.3-2   Ogg Bitstream Library Development
ii  libsdl-mixer1.21.2.6-1.1+b1  mixer library for Simple DirectMed
ii  libsdl1.2-dev  1.2.11-4  Simple DirectMedia Layer developme
ii  libsmpeg-dev   0.4.5+cvs20030824-1.9 SDL MPEG Player Library - developm
ii  libvorbis-dev  1.1.2.dfsg-1.2The Vorbis General Audio Compressi

libsdl-mixer1.2-dev recommends no packages.

-- no debconf information

---End Message---
---BeginMessage---
On Tue, Oct 31, 2006 at 10:50:34PM +0100, Yann Dirson wrote:

 This bug is strictly similar to libsdl1.2's #396063:

 /usr/lib/libSDL_mixer.la refers to many libraries (eg. libasound), which
 are not (and should not be) pulled by the package's dependencies.

 This makes packages (such as gcompris) not build from source any more.

 Note: this particular bug was hidden by libsdl1.2-dev depending on
 libasound2-dev, which it now only recommends.  This will trigger many
 other FTBFS.

BinNMUs have been scheduled on all architectures for this issue, so no
further maintainer action should be required to resolve this bug.

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


Bug#396352: azureus: incorrect jar specified in /usr/share/java-config/libswt-gtk-3.2-java

2006-10-31 Thread Steve Langasek
Hi Tony,

On Tue, Oct 31, 2006 at 02:30:53PM -0800, tony mancill wrote:

 The problem appears to lie with more recent versions of
 libswt-gtk-3.2-java.  The 3.2.1 version of this package ships
 /usr/share/java/swt-gtk-3.2.1.jar, but the config file referenced in the
 azureus startup script (/usr/bin/azureus) is:

 /usr/share/java-config/libswt-3.2-java -
   /etc/alternatives/libswt-3.2-java

 $ cat /etc/alternatives/libswt-3.2-java
 JARS=/usr/share/java/swt-gtk-3.2.jar

 Updating /usr/share/java-config/libswt-3.2-java by hand to contain:

   JARS=/usr/share/java/swt-gtk-3.2.1.jar

 Fixes the problem on my system.

Does this mean the bug should be reassigned to libswt-gtk-3.2-java?

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


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



Bug#394773: this sounds like an ideal candidate for a nmu

2006-10-31 Thread Joshua Kwan
Hi Peter,

On Tue, Oct 31, 2006 at 08:53:01PM -, peter green wrote:
 retitle 394773 minor change needed for compatibility with gaim2.0.0beta4
 thanks
 
 this sounds like an ideal candidate for a nmu, i've changed that title as it 
 misleadingly implied that a binnmu would have fixed this.
 

Upstream is about to push a beta4 fix out. Until then, even if
autoprofile compiles correctly, it will not be 100% functional. I would
rather wait until that fix comes out. I am sorry for not communicating
this in the buglog earlier.

-- 
Joshua Kwan


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



Bug#396480: installation-reports: D-I does not work on ASUS P5W DH de luxe + E6600

2006-10-31 Thread Eric Valette
Package: installation-reports
Severity: grave
Justification: renders package unusable

boot starts, but enter an endless loop resetting the SATA controller when it 
tries to find the disks. Also, dmesg shows spurious irq not handled on this 
hardware. Apparently fixed via the libata upgrade available in 2.6.18.x

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


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



Processed: Re: Bug#396352: azureus: incorrect jar specified in /usr/share/java-config/libswt-gtk-3.2-java

2006-10-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 package azureus
Ignoring bugs not assigned to: azureus

 tag 396352 confirmed pending
Bug#396352: azureus: fails to start, NoClassDefFoundError 
(org/eclipse/swt/widgets/Display)
There were no tags set.
Tags added: confirmed, 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]



  1   2   >