Bug#527566: #527566 mediatomb-daemon: Installation error due to postinst script

2009-06-14 Thread Peter Palfrader
On Tue, 02 Jun 2009, Alban Browaeys wrote:

> And there seems to be a bug in the mv_db is triggers:
> [ -e /var/lib/mediatomb/sqlite3.db ] && \
> cp --preserve /var/lib/mediatomb/sqlite3.db 
> /var/lib/mediatomb/mediatomb.db 
> alsways returns 1 which errors out the postinst. Adding
> "|| return 0"
> at the end of it helps. Probably adding parenthesis around to avoid it 
> applying to the "cp" would be good.

The usual approach for this is to either do:

! [ -e file ] || cp file target

or plain old ifs:
if [ -e file ]; then
cp file target
fi

-- 
   |  .''`.  ** Debian GNU/Linux **
  Peter Palfrader  | : :' :  The  universal
 http://www.palfrader.org/ | `. `'  Operating System
   |   `-http://www.debian.org/



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Processed: tagging 521185

2009-06-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 521185 - sid
Bug#521185: libmyodbc: Creashes with symbol error
Tags were: sid patch
Bug#522968: myodbc: FTBFS: libmyodbc3_r.so: undefined reference to 
`mysql_odbc_escape_string'
Bug#523593: myodbc_3.51.15r409-4+b1(mips/unstable): FTBFS on mips
Bug#527808: myodbc: FTBFS: undefined reference to `mysql_odbc_escape_string'
Tags removed: sid

>
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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#523715: [Debian-med-packaging] Processed: severity of 523715 is serious

2009-06-14 Thread Charles Plessy
Le Sun, Jun 14, 2009 at 10:33:03PM +, Debian Bug Tracking System a écrit :
> > severity 523715 serious

Hello Moritz, Steffen and Philipp,

I will upload soon an update with Barry's patch.

Have a nice day,

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#529023: marked as done (torcs: FTBFS: libtoolize: command not found)

2009-06-14 Thread Debian Bug Tracking System

Your message dated Mon, 15 Jun 2009 04:32:13 +
with message-id 
and subject line Bug#529023: fixed in torcs 1.3.1-2
has caused the Debian Bug report #529023,
regarding torcs: FTBFS: libtoolize: command not found
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
529023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: torcs
Version: 1.3.1-1
Severity: serious

Hi,

There was an error while trying to autobuild your package:

> Automatic build of torcs_1.3.1-1 on nautilus by sbuild/amd64 98
> Build started at 20090515-1906

[...]

> Build-Depends: debhelper (>= 7.0), libgl1-mesa-dev, libplib-dev, 
> freeglut3-dev (>= 2.2.0), libpng12-dev (>= 1.2.8), zlib1g-dev (>= 1.2.1.1), 
> libx11-dev (>= 6.8.2), libxt-dev (>= 6.8.2), libxmu-dev (>= 6.8.2), 
> libxxf86vm-dev (>= 6.8.2), cdbs, libopenal-dev, libalut-dev (>= 1.0.0), 
> libxi-dev, libxrender-dev, libxrandr-dev, autoconf, automake1.9

[...]

> Toolchain package versions: libc6-dev_2.9-12 g++-4.3_4.3.3-9 gcc-4.3_4.3.3-9 
> binutils_2.19.1-1 libstdc++6_4.4.0-4 libstdc++6-4.3-dev_4.3.3-9

[...]

> make[1]: Nothing to be done for `update-config'.
> make[1]: Leaving directory `/build/buildd/torcs-1.3.1'
> cd build-tree/torcs-1.3.1 && libtoolize -c -f
> /bin/sh: libtoolize: command not found
> make: *** [debian/stamp-autotools-files] Error 127
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2

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


Kurt



--- End Message ---
--- Begin Message ---
Source: torcs
Source-Version: 1.3.1-2

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

torcs_1.3.1-2.diff.gz
  to pool/main/t/torcs/torcs_1.3.1-2.diff.gz
torcs_1.3.1-2.dsc
  to pool/main/t/torcs/torcs_1.3.1-2.dsc
torcs_1.3.1-2_powerpc.deb
  to pool/main/t/torcs/torcs_1.3.1-2_powerpc.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 529...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rudy Godoy  (supplier of updated torcs 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 14 Jun 2009 22:13:04 -0500
Source: torcs
Binary: torcs
Architecture: source powerpc
Version: 1.3.1-2
Distribution: unstable
Urgency: low
Maintainer: Rudy Godoy 
Changed-By: Rudy Godoy 
Description: 
 torcs  - 3D racing cars simulator game using OpenGL
Closes: 465459 529023
Changes: 
 torcs (1.3.1-2) unstable; urgency=low
 .
   * Add dependency on libtool (Closes: #529023)
   * Updated link for tutorial on manpage (Closes: #465459)
Checksums-Sha1: 
 7338e54c1f9ebbb6650980a0aa41481ebd93f70e 1275 torcs_1.3.1-2.dsc
 ccb8570e014101cf14d1aa7bc4aed98a4ccfc253 7916 torcs_1.3.1-2.diff.gz
 1a52742a0291d52eb44cdeff19599a82720b9165 11022086 torcs_1.3.1-2_powerpc.deb
Checksums-Sha256: 
 e843d97b6daf4818ebb29d21c91ada0c8a454ae814225dca67acf88a0c6893ec 1275 
torcs_1.3.1-2.dsc
 e6f51b0da7b4ec1d92f185588119d64e86ad270a2d6002862ed81237836799b1 7916 
torcs_1.3.1-2.diff.gz
 daecc3957d35f46c0a6c3cecc4ff98129a0e6ef44362c00cf05ac9409aaa24c9 11022086 
torcs_1.3.1-2_powerpc.deb
Files: 
 ae68a89a55dc68f39695f52a081874cb 1275 games optional torcs_1.3.1-2.dsc
 45c9c64fafd03482fca9a8cf9b238254 7916 games optional torcs_1.3.1-2.diff.gz
 b0b2f488eb0fec8324a6520d8462b005 11022086 games optional 
torcs_1.3.1-2_powerpc.deb

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

iEYEARECAAYFAko1yjsACgkQVQ8aADQzvSHMQgCfTHYlnX/ubOgd/kLaeXYMPHda
FywAoIae6x3t51SwSSdM6w3BhDzH1hk+
=01LJ
-END PGP SIGNATURE-


--- End Message ---


Bug#528635: marked as done (depends on plib1.8.4c2 which is unavailable)

2009-06-14 Thread Debian Bug Tracking System

Your message dated Mon, 15 Jun 2009 03:18:40 +
with message-id 
and subject line Bug#528635: fixed in flightgear 1.9.1-1
has caused the Debian Bug report #528635,
regarding depends on plib1.8.4c2 which is unavailable
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
528635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flightgear
Version: 1.0.0-3+b1
Severity: serious

Hi,

flightgear depends on plib1.8.4c2 package which is unavailable.

Regards,
Raf

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.29-2-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages flightgear depends on:
ii  fgfs-base  1.0.0-2   Flight Gear Flight Simulator -- ba
ii  freeglut3  2.4.0-6.1 OpenGL Utility Toolkit
ii  libalut0   1.1.0-2   OpenAL Utility Toolkit
ii  libc6  2.9-12GNU C Library: Shared libraries
ii  libgcc11:4.4.0-4 GCC support library
ii  libgl1-mesa-glx [libgl 7.4.1-1   A free implementation of the OpenG
ii  libglu1-mesa [libglu1] 7.4.1-1   The OpenGL utility library (GLU)
ii  libice62:1.0.5-1 X11 Inter-Client Exchange library
ii  libjpeg62  6b-14 The Independent JPEG Group's JPEG 
ii  libopenal1 1:1.7.411-1   Software implementation of the Ope
ii  libsm6 2:1.1.0-2 X11 Session Management library
ii  libstdc++6 4.4.0-4   The GNU Standard C++ Library v3
ii  libx11-6   2:1.2.1-1 X11 client-side library
ii  libxext6   2:1.0.4-1 X11 miscellaneous extension librar
ii  libxi6 2:1.2.1-2 X11 Input extension library
ii  libxmu62:1.0.4-1 X11 miscellaneous utility library
ii  libxt6 1:1.0.5-3 X11 toolkit intrinsics library
ii  plib1.8.4c21.8.4-11  Portability Libraries: Run-time pa
ii  simgear1.0.0   1.0.0-4+b1Simulator Construction Gear -- sha
ii  zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime

flightgear recommends no packages.

flightgear suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: flightgear
Source-Version: 1.9.1-1

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

flightgear_1.9.1-1.diff.gz
  to pool/main/f/flightgear/flightgear_1.9.1-1.diff.gz
flightgear_1.9.1-1.dsc
  to pool/main/f/flightgear/flightgear_1.9.1-1.dsc
flightgear_1.9.1-1_i386.deb
  to pool/main/f/flightgear/flightgear_1.9.1-1_i386.deb
flightgear_1.9.1.orig.tar.gz
  to pool/main/f/flightgear/flightgear_1.9.1.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 528...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ove Kaaven  (supplier of updated flightgear 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 14 Jun 2009 21:35:48 +0200
Source: flightgear
Binary: flightgear
Architecture: source i386
Version: 1.9.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian FlightGear Crew 
Changed-By: Ove Kaaven 
Description: 
 flightgear - Flight Gear Flight Simulator
Closes: 510387 528635 529110
Changes: 
 flightgear (1.9.1-1) unstable; urgency=low
 .
   * New upstream release. Closes: #510387.
   * Updated debian/control and things for FlightGear 1.9.1.
 This includes depending on plib 1.8.5. Closes: #528635.
   * Added Vcs-Browser and Vcs-Svn fields to debian/control.
   * Converted debian/watch to version 3. Closes: #529110.
Checksums-Sha1: 
 73a524105ffb7b9ec628367096357e41de123bd3 1613 flightgear_1.9.1-1.dsc
 db1a6478164eabaab7c5ecf05bb011b573bb8659 2246411 flightgear_1.9.1.orig.tar.gz
 fc29c002c82f9655bdcf898ffa7a57f125a7ae8e 10726 flightgear_1.9.1-1.diff.gz
 cbd4dee5e6eb78c1bcdf53981b94332d0

Bug#533128: gliv: segfault with Gdk-CRITICAL

2009-06-14 Thread TheGZeus
Package: gliv
Version: 1.9.5-1
Severity: grave
Justification: renders package unusable

Immediate segfault with error message:
(gliv:6112): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion
`atom != GDK_NONE' failed

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

Kernel: Linux 2.6.30-0.slh.2-sidux-686 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gliv depends on:
ii  libatk1.0-0   1.26.0-1   The ATK accessibility toolkit
ii  libc6 2.9-14 GNU C Library: Shared libraries
ii  libcairo2 1.8.6-2+b1 The Cairo 2D vector graphics libra
ii  libfontconfig12.6.0-4generic font configuration library
ii  libgl1-mesa-glx [libgl1]  7.4.1-1A free implementation of the OpenG
ii  libglib2.0-0  2.20.3-1   The GLib library of C routines
ii  libglu1-mesa [libglu1]7.4.1-1The OpenGL utility library (GLU)
ii  libgtk2.0-0   2.16.2-1   The GTK+ graphical user interface 
ii  libgtkglext1  1.2.0-1OpenGL Extension to GTK+ (shared l
ii  libice6   2:1.0.5-1  X11 Inter-Client Exchange library
ii  libpango1.0-0 1.24.2-1   Layout and rendering of internatio
ii  libsm62:1.1.0-2  X11 Session Management library
ii  libx11-6  2:1.2.1-1  X11 client-side library
ii  libxcursor1   1:1.1.9-1  X cursor management library
ii  libxext6  2:1.0.4-1  X11 miscellaneous extension librar
ii  libxi62:1.2.1-2  X11 Input extension library
ii  libxinerama1  2:1.0.3-2  X11 Xinerama extension library
ii  libxmu6   2:1.0.4-1  X11 miscellaneous utility library
ii  libxrandr22:1.3.0-2  X11 RandR extension library
ii  libxrender1   1:0.9.4-2  X Rendering Extension client libra
ii  libxt61:1.0.5-3  X11 toolkit intrinsics library

gliv recommends no packages.

gliv suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#533021: sitecopy: OK after reinstalling according to your recommendations

2009-06-14 Thread roger crettol
Package: sitecopy
Severity: normal

Yes, the version number was mine, I used checkinstall. The installed sources 
were of version 0.16.6-2.

I am new to reportbug and I didn't do anything to suppress dependency 
information.

To fix, added entries for unstable in my /etc/apt/sources.list file.
Then I re-installed libneon27-gnutls from unstable, and sitecopy from testing, 
and, YES, it works OK.

I've been using debian since 30r1 days, and reinstalled from scratch this 
spring. I suspect I'll have to look at the APT
documentation again, and figure out about assigning priorities to the various 
targets. On my old setup, I hat an
/etc/apt/preferences file, but I haven't had on on my current setup.

Thanks for your kind reply to this (no)bug report.

-rg-




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

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

Versions of packages sitecopy depends on:
ii  libc6 2.9-12 GNU C Library: Shared libraries
ii  libneon27-gnutls  0.28.4-3   An HTTP and WebDAV client library 

sitecopy recommends no packages.

sitecopy suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#533021: sitecopy: After reading your reply and reinstalling, it's OK

2009-06-14 Thread roger crettol
Package: sitecopy
Severity: normal

Hi Sandro !

* The version was created while using checkinstall, so the extra numbering is 
mine.
* apt-get source retrieved the following files :
  sitecopy_0.16.6-2.diff.gz, sitecopy_0.16.6-2.dsc
  So I assumed this would be for a 0.16.6-2 version
* I'll try to get a hand on this unstable neon library. Thanks for the hint.
  (added entries for the unstable target in /etc/apt/sources.list)
  Installed libneon27-gnutls from unstable and sitecopy from testing.
  Checked that sitecopy works (with -d socket,ftp) -- successful

* Yes I have used and am using reportbug. I didtn't to anything consciously to 
suppress dependency information,
  but I am reporting a bug for the first time.

* I'll have to look at apt-doc again, I guess. I've used debian since 3.0.r1  
before I re-installed from scratch this spring.
  I used an /etc/apt/preferences file to give the different targets a priority. 
I had no such file on my current setup.

Thanks for looking at the bug report and your patient answer.

-rg-
 


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

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

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#533122: ruby1.8-dev: FTBFS with newer ruby ?

2009-06-14 Thread Dirk Eddelbuettel

Package: ruby1.8-dev
Version: 1.8.7.72-3.1
Severity: serious

Hi, I maintain a package with Swig-generated interfaces for which I also
provide ruby builds. I had just done a release a few days ago, it worked
fine:

dh_installdirs -pquantlib-ruby  usr/share/quantlib-ruby
(cd Ruby && \
CXX="g++"   \
CFLAGS="-O2 -Wall -Wno-strict-aliasing" 
\
CXXFLAGS="-O2 -Wall -Wno-strict-aliasing"   
\
ruby setup.rb install   \

--prefix=/tmp/buildd/quantlib-swig-0.9.7/debian/quantlib-ruby/usr --debian  
)
creating Makefile
make[1]: Entering directory `/tmp/buildd/quantlib-swig-0.9.7/Ruby'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/tmp/buildd/quantlib-swig-0.9.7/Ruby'
./QuantLibc.so -> 
/tmp/buildd/quantlib-swig-0.9.7/debian/quantlib-ruby/usr/lib/ruby/1.8/i486-linux/QuantLibc.so
chmod 0555 
/tmp/buildd/quantlib-swig-0.9.7/debian/quantlib-ruby/usr/lib/ruby/1.8/i486-linux/QuantLibc.so
./QuantLib.rb -> 
/tmp/buildd/quantlib-swig-0.9.7/debian/quantlib-ruby/usr/lib/ruby/1.8/QuantLib.rb
chmod 0555 
/tmp/buildd/quantlib-swig-0.9.7/debian/quantlib-ruby/usr/lib/ruby/1.8/QuantLib.rb
chmod 644 debian/quantlib-ruby/usr/lib/ruby/1.8/QuantLib.rb

That was using the versions

Get:33 http://ftp.us.debian.org unstable/main libruby1.8 1.8.7.72-3.1 [1672kB]
Get:34 http://ftp.us.debian.org unstable/main ruby1.8 1.8.7.72-3.1 [283kB]
Get:35 http://ftp.us.debian.org unstable/main ruby 4.2 [20.6kB]
Get:36 http://ftp.us.debian.org unstable/main ruby1.8-dev 1.8.7.72-3.1 [826kB]


Now, however, using what is in unstable, ie 

Get:33 http://ftp.us.debian.org unstable/main libruby1.8 1.8.7.173-1 [1679kB]
Get:34 http://ftp.us.debian.org unstable/main ruby1.8 1.8.7.173-1 [290kB]
Get:35 http://ftp.us.debian.org unstable/main ruby 4.2 [20.6kB]
Get:36 http://ftp.us.debian.org unstable/main ruby1.8-dev 1.8.7.173-1 [835kB]

I end up with


(cd Ruby && ruby setup.rb test  )
creating Makefile
make[1]: Entering directory `/tmp/buildd/quantlib-swig-0.9.7/Ruby'
make[1]: *** No rule to make target `Makefile', needed by `QuantLibc.so'.  Stop.
make[1]: Leaving directory `/tmp/buildd/quantlib-swig-0.9.7/Ruby'
/tmp/buildd/quantlib-swig-0.9.7/Ruby/QuantLib.rb:18:in `require': no such file 
to load -- QuantLibc (LoadError)
from /tmp/buildd/quantlib-swig-0.9.7/Ruby/QuantLib.rb:18
from ./dates.rb:18:in `require'
from ./dates.rb:18
from ./QuantLibTestSuite.rb:23:in `require'
from ./QuantLibTestSuite.rb:23
from setup.rb:134:in `load'
from setup.rb:134
from setup.rb:70:in `call'
from setup.rb:70:in `execute'
from setup.rb:173
Testing QuantLib-Ruby 0.9.7...
make: *** [test-stamp] Error 1

Same for the install target.

Or is this something that requires upstream changes in setup.rb ?

Thanks in advance for your help,  Dirk



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

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

Versions of packages ruby1.8-dev depends on:
ii  libc6-dev   2.9-12   GNU C Library: Development Librari
ii  libruby1.8  1.8.7.72-3.1 Libraries necessary to run Ruby 1.

Versions of packages ruby1.8-dev recommends:
ii  ruby1.8 1.8.7.72-3.1 Interpreter of object-oriented scr

ruby1.8-dev suggests no packages.

-- no debconf information


-- 
Three out of two people have difficulties with fractions.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#530572: pinot_0.93-1(mips/unstable): FTBFS on mips - undefined reference

2009-06-14 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

On Sun, Jun 14, 2009 at 07:36:32PM +0800, Fabrice Colin wrote:
>On Sat, Jun 13, 2009 at 11:57 PM, Jonas Smedegaard wrote:
>> Unfortunately my first attempt didn't work out as intended.
>>
>> Haven't found time to verify yet, but seems to be that I should set
>> CPPFLAGS instead of CFLAGS (they are handled separately in CDBS
>> packaging tool).
>>
>> Perhaps your upstream autotools setting should be similarly adjusted?
>>
>Try CXXFLAGS, it will be picked up by configure and used at build time.
>I have had reports the fix in SVN r1635 fixed the issue, but if you
>have a log for me to look into, let me know.

Whoops - you are right (CPPFLAGS are for the preprocessor).

Anyway, it seems to work, looking at both my own build logs and those of 
the powerpc build daemon.

Build logs are here: https://buildd.debian.org/pkg.cgi?pkg=pinot

And here: https://buildd.debian.org/~luk/status/package.php?p=pinot

Both links found here: http://packages.qa.debian.org/p/pinot.html


Kind regards,

  - Jonas

- -- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAko1ewgACgkQn7DbMsAkQLjhjgCeJz5bVsIJeVYcZWsEG/0YDKP7
NLIAniN0gE3KtI+iFi4NY6XlHWgip19t
=pHxL
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#527518: marked as done (umview: FTBFS: Cannot find linux/dirent.h)

2009-06-14 Thread Debian Bug Tracking System

Your message dated Sun, 14 Jun 2009 21:34:35 +
with message-id 
and subject line Bug#527518: fixed in umview 0.6-1
has caused the Debian Bug report #527518,
regarding umview: FTBFS: Cannot find linux/dirent.h
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
527518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: umview
Version: 0.5-2
Severity: serious

From my pbuilder build log:

...
/bin/sh ../libtool --tag=CC   --mode=compile cc -DHAVE_CONFIG_H -I. -I..  
-I../include   -g -O2 -g -Wall -O2 -c -o libumlib_la-libummod.lo `test -f 
'libummod.c' || echo './'`libummod.c
 cc -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -g -Wall -O2 -c libummod.c  
-fPIC -DPIC -o .libs/libumlib_la-libummod.o
libummod.c:28:26: error: linux/dirent.h: No such file or directory
libummod.c:34: warning: 'struct dirent' declared inside parameter list
libummod.c:34: warning: its scope is only this definition or declaration, which 
is probably not what you want
libummod.c:39: warning: 'struct dirent64' declared inside parameter list
make[3]: *** [libumlib_la-libummod.lo] Error 1
make[3]: Leaving directory `/tmp/buildd/umview-0.5/um_lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/umview-0.5'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/umview-0.5'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
-- 
Daniel Schepler



--- End Message ---
--- Begin Message ---
Source: umview
Source-Version: 0.6-1

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

libumlib-dev_0.6-1_amd64.deb
  to pool/main/u/umview/libumlib-dev_0.6-1_amd64.deb
libumlib0_0.6-1_amd64.deb
  to pool/main/u/umview/libumlib0_0.6-1_amd64.deb
umview-mod-umdevtap_0.6-1_amd64.deb
  to pool/main/u/umview/umview-mod-umdevtap_0.6-1_amd64.deb
umview-mod-umlwip_0.6-1_amd64.deb
  to pool/main/u/umview/umview-mod-umlwip_0.6-1_amd64.deb
umview-mod-viewfs_0.6-1_amd64.deb
  to pool/main/u/umview/umview-mod-viewfs_0.6-1_amd64.deb
umview_0.6-1.diff.gz
  to pool/main/u/umview/umview_0.6-1.diff.gz
umview_0.6-1.dsc
  to pool/main/u/umview/umview_0.6-1.dsc
umview_0.6-1_amd64.deb
  to pool/main/u/umview/umview_0.6-1_amd64.deb
umview_0.6.orig.tar.gz
  to pool/main/u/umview/umview_0.6.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 527...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ludovico Gardenghi  (supplier of updated umview 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Jun 2009 20:49:41 +0200
Source: umview
Binary: umview libumlib0 libumlib-dev umview-mod-umlwip umview-mod-umdevtap 
umview-mod-viewfs
Architecture: source amd64
Version: 0.6-1
Distribution: unstable
Urgency: low
Maintainer: Debian VSquare Team 
Changed-By: Ludovico Gardenghi 
Description: 
 libumlib-dev - View-OS in user space - Development files
 libumlib0  - View-OS in user space - Support library for modules
 umview - View-OS in user space - Core and base modules
 umview-mod-umdevtap - View-OS in user space - Virtual TUN/TAP module
 umview-mod-umlwip - View-OS in user space - LWIPv6 gateway module
 umview-mod-viewfs - View-OS in user space - Filesystem mangling modules
Closes: 527518
Changes: 
 umview (0.6-1) unstable; urgency=low
 .
   [ Filippo Giunchedi ]
   * Add DM-Upload-Allowed field
 .
   [ Ludovico Gardenghi ]
   * New upstream release
 + Fix "FTBFS: Cannot find linux/dirent.h" (new upstream corrects the
   path name and includes a .h with the needed definitions which are no
   more accessible.) (Closes: #527518)
   * Update standard-version to 3.8.1 (no changes needed).
   * Added missing misc:Depends to libumlib-dev.
   * Changed gar...@acheronte.it with gar...@debian.org.
   * Fixed versionless license file names.
Checksums-Sha1: 
 1ff879cc42767f820a7692f82fa034870c8d1452 1728 umview_0.6-1.dsc
 8a89b1e07b1ec01a59bffc2fa9d41992c08f2c29 629090 umview_0.6.orig.tar.gz
 f4777b1ae7473644eb65b0bc9d71e40750c84f0e 3537 umview_0.6-1.diff.gz
 8d0bba055420eb3

Bug#531614: Two security issues

2009-06-14 Thread Moritz Muehlenhoff
On Fri, Jun 12, 2009 at 09:50:22PM -0700, Cameron Dale wrote:
> On Tue, Jun 2, 2009 at 11:45 AM, Moritz Muehlenhoff wrote:
> > The following security issues have been reported against torrentflux:
> >
> > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-6584
> > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-6585
> 
> Thanks for the report. I think I looked into these issues when they
> first came up.
> 
> Anyway, I looked into them now and I don't believe that the
> torrentflux in Debian is affected. This vulnerability is due to the
> upstream's default directory layout of storing the downloads directory
> under the html directory, so that downloaded php files will be
> executed by the web server. In the Debian package's installation, the
> downloads are stored in /var/cache/torrentflux while the html/php
> files are served from /usr/share/torrentflux/www, so the webserver
> will never execute downloaded files.
> 
> Since both reports stem from the ability to execute php files in the
> downloads directory, both do not affect the Debian torrentflux
> installation.
> 
> If you think I made a mistake, please reopen this report.

Thanks, I'll add this to the Debian Security Tracker.

Cheers,
Moritz



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#530470: marked as done (Fails to build -- attempts to access file in /usr/share/icons)

2009-06-14 Thread Debian Bug Tracking System

Your message dated Sun, 14 Jun 2009 21:33:17 +
with message-id 
and subject line Bug#530470: fixed in licq 1.3.6-2
has caused the Debian Bug report #530470,
regarding Fails to build -- attempts to access file in /usr/share/icons
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
530470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: licq
Severity: serious
Justification: no longer builds from source

Hi,

I was unable to build this package.  Here's the end of the
build log:

make[2]: Leaving directory `/licq-1.3.6/po'
make[2]: Entering directory `/licq-1.3.6'
make[3]: Entering directory `/licq-1.3.6'
make[3]: Nothing to be done for `install-exec-am'.
--
Licq daemon installed successfully.

For more help on running Licq and using plugins, see doc/README.
See HINTS for some Licq advanced features.
Protocol plugins are also found in the plugins/ directory.

!!
**
*** Now enter the plugins directory and build the GUI plugin.*
*** If you want the default Qt GUI go to plugins/qt-gui. *
*** Unoffical GTK+ interfaces are available from www.licq.org.   *
*** You must do this in order to have a graphical interface! *
**
!!
--
make[3]: Leaving directory `/licq-1.3.6'
make[2]: Leaving directory `/licq-1.3.6'
make[1]: Leaving directory `/licq-1.3.6'
mkdir -p debian/licq/usr/share/pixmaps
convert /usr/share/icons/crystalsvg/32x32/apps/licq.png 
debian/licq/usr/share/pixmaps/licq.xpm
convert: unable to open image 
`/usr/share/icons/crystalsvg/32x32/apps/licq.png': No such file or directory @ 
blob.c/OpenBlob/2439.
convert: unable to open file `/usr/share/icons/crystalsvg/32x32/apps/licq.png' 
@ png.c/ReadPNGImage/2854.
convert: missing an image filename `debian/licq/usr/share/pixmaps/licq.xpm' @ 
convert.c/ConvertImageCommand/2775.
make: *** [install-licq-common] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
debuild: fatal error at line 1324:



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

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


--- End Message ---
--- Begin Message ---
Source: licq
Source-Version: 1.3.6-2

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

licq-dev_1.3.6-2_all.deb
  to pool/main/l/licq/licq-dev_1.3.6-2_all.deb
licq-plugin-autoreply_1.3.6-2_amd64.deb
  to pool/main/l/licq/licq-plugin-autoreply_1.3.6-2_amd64.deb
licq-plugin-console_1.3.6-2_amd64.deb
  to pool/main/l/licq/licq-plugin-console_1.3.6-2_amd64.deb
licq-plugin-forwarder_1.3.6-2_amd64.deb
  to pool/main/l/licq/licq-plugin-forwarder_1.3.6-2_amd64.deb
licq-plugin-kde_1.3.6-2_amd64.deb
  to pool/main/l/licq/licq-plugin-kde_1.3.6-2_amd64.deb
licq-plugin-msn_1.3.6-2_amd64.deb
  to pool/main/l/licq/licq-plugin-msn_1.3.6-2_amd64.deb
licq-plugin-osd_1.3.6-2_amd64.deb
  to pool/main/l/licq/licq-plugin-osd_1.3.6-2_amd64.deb
licq-plugin-qt_1.3.6-2_amd64.deb
  to pool/main/l/licq/licq-plugin-qt_1.3.6-2_amd64.deb
licq-plugin-rms_1.3.6-2_amd64.deb
  to pool/main/l/licq/licq-plugin-rms_1.3.6-2_amd64.deb
licq_1.3.6-2.diff.gz
  to pool/main/l/licq/licq_1.3.6-2.diff.gz
licq_1.3.6-2.dsc
  to pool/main/l/licq/licq_1.3.6-2.dsc
licq_1.3.6-2_amd64.deb
  to pool/main/l/licq/licq_1.3.6-2_amd64.deb



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 530...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jan Hauke Rahm  (supplier of updated licq 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 14 Jun 2009 17:

Bug#524588: Temporary removal of pythonmagick from testing?

2009-06-14 Thread Luk Claes
Hi

pythonmagick is blocking the imagemagick transition (and some
transitions waiting for this to finish). I heard from Bernd (bzed) that
uploading the new upstream version to fix the outstanding RC bugs still
needs some work (patching to get it build with python2.5?).

So I wanted to request if removing it from testing for now would be an
option?

Cheers

Luk



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#532656: [Pkg-octave-devel] Bug#532656: Bug#532656: Bug#532656: octave3.2_3.2.0-1(mips/unstable): FTBFS on mips. Segfault in regression test.

2009-06-14 Thread Rafael Laboissiere
* Rafael Laboissiere  [2009-06-14 15:39]:

> * Rafael Laboissiere  [2009-06-14 12:25]:
> 
> > I think that the different values of x_max and x_min explain the bug on
> > the mips system.  I guess that this is caused by the following lines in
> > pr-output.cc (function set_format):
> > 
> >   int x_max = max_abs == 0.0
> >
> > ? 0 : static_cast (floor (log10 (max_abs) + 1.0)); 
> >
> > 
> >
> >   int x_min = min_abs == 0.0
> >
> > ? 0 : static_cast (floor (log10 (min_abs) + 1.0)); 
> >
> 
> I meant lines 854 to 858 in pr-output.cc, in function 
> set_format (const Complex& c, int& r_fw, int& i_fw)

I think I found the cause of the bug.  The simple program:

///
#include 
#include 

int
main (void)
{
std::cerr << static_cast (floor (log10 (0.0/0.0))) << std::endl;
return 0;
}
///

when compiled on mips yields 2147483647, while on amd64 and i386 it
yields -2147483648.  This explains the different behavior on both
architectures.

Now, I am wondering whether the code in set_format() makes sense.  The
function reads:

///
static void
set_format (const Complex& c, int& r_fw, int& i_fw)
{
  // [snip]

  double rp = c.real ();
  double ip = c.imag ();

  bool inf_or_nan = (xisinf (c) || xisnan (c));

  bool int_only = (D_NINT (rp) == rp && D_NINT (ip) == ip);

  double r_abs = rp < 0.0 ? -rp : rp;
  double i_abs = ip < 0.0 ? -ip : ip;

   
  int r_x = r_abs == 0.0 
? 0 : static_cast (floor (log10 (r_abs) + 1.0));

  // [snip]
///

When r_abs is NaN (as in the bug-triggering case) what is the sense of
computing log10 (r_abs) and propagating the result?  I am probably
missing something but it seems just pure chance that r_x ends up being
negative on amd64 and i386, what does not trigger the bug.

-- 
Rafael



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#532736: CVE-2009-1391: Buffer overflow in Compress::Raw::Zlib

2009-06-14 Thread Niko Tyni
On Sat, Jun 13, 2009 at 10:43:55PM +0300, Niko Tyni wrote:
 
> Security team: I'm attaching proposed debdiffs for stable updates.
> Do you agree that this fix is sufficient? Shall I go ahead and upload?

Update: I've got confirmation from upstream that the one line fix should be
fine. Just say the word and I'll upload.
-- 
Niko Tyni   nt...@debian.org



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Processed: tagging as pending bugs that are closed by packages in NEW

2009-06-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # Sun Jun 14 20:04:47 UTC 2009
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: gfm
> tags 532606 + pending
Bug#532606: ITP: gfm -- Texas Instruments hand-helds file manipulation program 
for X
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 498293 + pending
Bug#498293: linux-image-2.6.26-1-686: mos7840 USB serial driver fails to work 
and causes kernel OOPS with 2.6.26-4
Tags were: fixed-upstream upstream
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 524699 + pending
Bug#524699: e1000e: random kernel oopses
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 521553 + pending
Bug#521553: Staging drivers contain non-free firmware
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 526836 + pending
Bug#526836: linux-image-2.6-r5k-cobalt: Please include modules for scsi host 
adapters like aic7xxx or 53c8xx!
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 508426 + pending
Bug#508426: [bluez-utils] doesn't work after hibernate/resume (needs restart)
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 521829 + pending
Bug#521829: linux-image-2.6.26-1-sparc64: loop is not a module. loop-aes is 
useless.
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 529785 + pending
Bug#529785: [regression] the entire bluetooth stack needs a restart after resume
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 431500 + pending
Bug#431500: please include pata_jmicron
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 506964 + pending
Bug#506964: linux-image-2.6.26-1-686: radeonfb suspend/resume for Acer 
Travelmate 29X
Tags were: patch
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 513695 + pending
Bug#513695: fetchmail: race in MSG_PEEK.
Tags were: patch upstream moreinfo
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 527056 + pending
Bug#527056: linux-image-2.6.29-2-686: e100 ethernet controller gets defunct 
after a normal reboot
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 531804 + pending
Bug#531804: linux-image-2.6.29-2-amd64: Fails to mount reiserfs partitions 
(/home and /usr) suggesting a manual fsck
There were no tags set.
Tags added: pending

> # Source package in NEW: linux-2.6
> tags 458493 + pending
Bug#458493: linux-image-2.6 and JMicron IDE controller
There were no tags set.
Tags added: pending

> # Source package in NEW: concordance
> tags 512597 + pending
Bug#512597: ITP: concordance -- set of utilities and libraries for the 
configuration of Logitech Harmony remotes
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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#533088: gnome-python-desktop_2.24.1-1+b3(mips/unstable): FTBFS on mips.

2009-06-14 Thread Peter De Schrijver
Package: gnome-python-desktop
Version: 2.24.1-1+b3
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of gnome-python-desktop_2.24.1-1+b3 on mayr by sbuild/mips 
> 99.999
> Build started at 20090612-1233

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 5.0.37.2), gnome-pkg-tools (>= 0.10), 
> python-support (>= 0.6), autotools-dev, quilt, dpkg-dev (>= 1.13.19), 
> python-all-dev (>= 2.5), python-gtk2-dev (>= 2.10.3), python-gnome2-dev (>= 
> 2.10.0), python-cairo-dev, libglib2.0-dev (>= 2.6.0), libgtk2.0-dev (>= 2.4), 
> librsvg2-dev (>= 2.13.93), libgtop2-dev (>= 2.13.0), libwnck-dev (>= 2.19.3), 
> libpanel-applet2-dev (>= 2.13.4), libtotem-plparser-dev (>= 1.4.0), 
> libgnomeprint2.2-dev (>= 2.2.0), libgnomeprintui2.2-dev (>= 2.2), 
> libgtksourceview-dev (>= 1.1.90), libnautilus-burn-dev (>= 2.15.3), 
> libgnome-media-dev (>= 2.10.0), libgconf2-dev (>= 2.10.0), libmetacity-dev 
> (>= 1:2.21.5), libgnome-keyring-dev (>= 0.5.0), libgnome-desktop-dev (>= 
> 2.10.0), libecal1.2-dev (>= 1.4.0), libebook1.2-dev (>= 1.4.0), bug-buddy (>= 
> 2.16) [!hurd-i386]

[...]

>  gcc -DHAVE_CONFIG_H -I. -I../../gnomeapplet -I.. -I/usr/include/python2.5 
> -I/usr/include/python2.5 -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 
> -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -D_REENTRANT 
> -I/usr/include/panel-2.0 -I/usr/include/gconf/2 -I/usr/include/gtk-2.0 
> -I/usr/include/libbonoboui-2.0 -I/usr/include/orbit-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 
> -I/usr/include/libxml2 -I/usr/include/libbonobo-2.0 
> -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libgnome-2.0 
> -I/usr/include/bonobo-activation-2.0 -I/usr/include/gail-1.0 
> -I/usr/include/libart-2.0 -I/usr/include/gnome-vfs-2.0 
> -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gnome-python-2.0 -g -O2 -Wall 
> -g -O2 -std=c9x -fno-strict-aliasing -MT gnomeapplet_la-appletmodule.lo -MD 
> -MP -MF .deps/gnomeapplet_la-appletmodule.Tpo -c 
> ../../gnomeapplet/appletmodule.c  -fPIC -DPIC -o 
> .libs/gnomeapplet_la-appletmodule.o
> ../../gnomeapplet/appletmodule.c:13:38: error: libgnomeui/gnome-ui-init.h: No 
> such file or directory
> ../../gnomeapplet/appletmodule.c: In function 'initgnomeapplet':
> ../../gnomeapplet/appletmodule.c:92: error: 'LIBGNOMEUI_MODULE' undeclared 
> (first use in this function)
> ../../gnomeapplet/appletmodule.c:92: error: (Each undeclared identifier is 
> reported only once
> ../../gnomeapplet/appletmodule.c:92: error: for each function it appears in.)
> make[3]: *** [gnomeapplet_la-appletmodule.lo] Error 1
> make[3]: Leaving directory 
> `/build/buildd/gnome-python-desktop-2.24.1/build-2.5/gnomeapplet'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory 
> `/build/buildd/gnome-python-desktop-2.24.1/build-2.5'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory 
> `/build/buildd/gnome-python-desktop-2.24.1/build-2.5'
> make: *** [build-2.5/build-stamp] Error 2
> rm build-2.5/configure-stamp
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=mips&pkg=gnome-python-desktop&ver=2.24.1-1+b3




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#527065: marked as done (owned and unowned files after purge (policy 6.8 + 10.7.3))

2009-06-14 Thread Debian Bug Tracking System

Your message dated Sun, 14 Jun 2009 16:47:10 +
with message-id 
and subject line Bug#527065: fixed in util-vserver 0.30.216~r2772-7
has caused the Debian Bug report #527065,
regarding owned and unowned files after purge (policy 6.8 + 10.7.3)
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
527065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-vserver
Version: 0.30.216~r2772-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts piuparts.d.o

Hi, 

during a test with piuparts I noticed your package left owned and 
unowned files on the system after purge, which is a violation of policy 6.8 
and 10.7.3:

http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3

From the attached log (scroll to the bottom...):

0m33.9s ERROR: FAIL: Package purging left files on system:
  /etc/vservers  owned by: util-vserver
  /etc/vservers/.defaultsowned by: util-vserver
  /etc/vservers/.defaults/apps   owned by: util-vserver
  /etc/vservers/.defaults/apps/vunifyowned by: util-vserver
  /etc/vservers/.defaults/apps/vunify/hash   owned by: util-vserver
  /etc/vservers/.defaults/apps/vunify/hash/00not owned
  /var/lib/vservers  owned by: util-vserver
  /var/lib/vservers/.hashnot owned


regards,
Holger
Start: 2009-04-08 04:25:25 UTC

Package: util-vserver
Priority: optional
Section: net
Installed-Size: 2928
Maintainer: Micah Anderson 
Architecture: amd64
Version: 0.30.216~r2772-6
Replaces: vserver
Depends: libbeecrypt6, libc6 (>= 2.7-1), iproute, net-tools, make, debconf, util-linux (>= 2.13.1.1-1)
Recommends: binutils, debootstrap
Suggests: linux-image-2.6 (>= 2.6.16-17), vlan, iptables, wget, procps, module-init-tools, yum
Conflicts: vpopmail-bin, vserver
Filename: pool/main/u/util-vserver/util-vserver_0.30.216~r2772-6_amd64.deb
Size: 577120
MD5sum: e66c938552c7abea81217c2c7bcc755c
SHA1: c9585f97a4205ef23f842a6d3eedb2de2d198b90
SHA256: 91aa6859a598b6950adc2bccffd70f486f2ca368c16f462a5f19ec30f2c57895
Description: user-space tools for Linux-VServer virtual private servers
 The util-vserver project provides the user-space tools for creating and
 managing the virtualization technology known as Linux-Vserver guests.
 Linux-Vserver guests are a significantly advanced jail mechanism running
 inside a host GNU-Linux server. Linux-Vserver guests can be used to
 securely partition resources such as processes, memory, network; logically
 separate services or run entirely different distributions all on a single
 system. Virtual private servers are separated from each other through security
 contexts, and as a result are completely unaware of each other, or of the
 host itself.
 .
 http://linux-vserver.org/
 http://ftp.linux-vserver.org/pub/utils/util-vserver/
Homepage: http://savannah.nongnu.org/projects/util-vserver/
Tag: admin::virtualization, hardware::emulation, implemented-in::c, interface::commandline, network::server, role::program, scope::utility

Executing: sudo /org/piuparts.debian.org/sbin/piuparts --no-symlinks --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz util-vserver
Guessed: debian
0m0.0s INFO: --
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: --
0m0.0s INFO: piuparts version 0.36~20090408 starting up.
0m0.0s INFO: Command line arguments: /org/piuparts.debian.org/sbin/piuparts --no-symlinks --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz util-vserver
0m0.0s INFO: Running on: Linux piatti 2.6.29.1-dsa-amd64 #2 SMP Sun Apr 5 00:16:11 CEST 2009 x86_64
0m0.0s DEBUG: Created temporary directory /org/piuparts.debian.org/tmp/tmp5z5lQn
0m0.0s DEBUG: Unpacking sid.tar.gz into /org/piuparts.debian.org/tmp/tmp5z5lQn
0m0.0s DEBUG: Starting command: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmp5z5lQn', '-zxf', 'sid.tar.gz']
0m3.6s DEBUG: Command ok: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmp5z5lQn', '-zxf', 'sid.tar.gz']
0m3.6s DEBUG: Created policy-rc.d and chmodded it.
0m3.6s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmp5z5lQn', 'apt-get', 'update']
0m18.2s DUMP: 
  Get:1 http://ftp.fi.debian.org sid 

Bug#527065: util-vserver: diff for NMU version 0.30.216~r2772-6.1

2009-06-14 Thread Micah Anderson
* Andrew Lee  [2009-06-14 12:57-0400]:
> Hi Micah,
> 
> Micah Anderson wrote:
> > Hi Andrew,
> > I appreciate the help with the package, although typically a NMU is done
> > after a patch is not being applied, so sending a patch and doing a 2-day
> > NMU at the same time is a little aggressive. I'm also wondering how you
> > can do this NMU because as far as I can tell you aren't yet a DD :)
> 
> Sorry for the unclear message. I do not want aggressive. I just
> reproduce other DD does for NMU. Please let me know the proper way if I
> did this wrong. I guess you may smelled that I am in NM process so that
> my AM would sponsor the upload. :)

No problem at all. The bug is a RC bug and I have not reacted to it in a
timely manner. Doing the NMU with a 2-day delay is fine, for this
bug. 

> > I have been working on a new version of util-vserver to upload, with a
> > newer snapshot, so I was delaying this fix until that was
> > finished. However I can upload this fix to resolve the RC bug.
> 
> I see. My attention was to solve the RC bug for next point release. It
> would be great if you accept this NMU for me.

I've uploaded a new package with that fix, thanks for sending the patch!

> > In any case, what would be even better than doing NMUs would be if you
> > would join the Alioth team and help with the util-vserver packaging
> > effort, its an open team, although nobody has helped on it so far and I
> > would appreciate the help!
> 
> Thanks for your invitation. I've sent the request on Alioth. Please
> update me for the new version of util-vserver with a newer snapshot via
> alioth.

I have accepted your request on Alioth. 

micah


signature.asc
Description: Digital signature


Bug#527065: util-vserver: diff for NMU version 0.30.216~r2772-6.1

2009-06-14 Thread Andrew Lee
Hi Micah,

Micah Anderson wrote:
> Hi Andrew,
> I appreciate the help with the package, although typically a NMU is done
> after a patch is not being applied, so sending a patch and doing a 2-day
> NMU at the same time is a little aggressive. I'm also wondering how you
> can do this NMU because as far as I can tell you aren't yet a DD :)

Sorry for the unclear message. I do not want aggressive. I just
reproduce other DD does for NMU. Please let me know the proper way if I
did this wrong. I guess you may smelled that I am in NM process so that
my AM would sponsor the upload. :)

> I have been working on a new version of util-vserver to upload, with a
> newer snapshot, so I was delaying this fix until that was
> finished. However I can upload this fix to resolve the RC bug.

I see. My attention was to solve the RC bug for next point release. It
would be great if you accept this NMU for me.

> In any case, what would be even better than doing NMUs would be if you
> would join the Alioth team and help with the util-vserver packaging
> effort, its an open team, although nobody has helped on it so far and I
> would appreciate the help!

Thanks for your invitation. I've sent the request on Alioth. Please
update me for the new version of util-vserver with a newer snapshot via
alioth.

Cheers,

-Andrew



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#533017: $* is no longer supported at /usr/lib/sympa/bin/parser.pl line 65.

2009-06-14 Thread Olivier Berger
On Sat, Jun 13, 2009 at 08:32:17PM +0200, Hadmut Danisch wrote:
> 
> running sympa or sympa perl scripts, e.g. 
> /etc/init.d/sympa start
> or the sympa.pl reports
> 
> $* is no longer supported at /usr/lib/sympa/bin/parser.pl line 65.
> 
> 
> looks as if sympa is not compatible with latest perl versions. 
> 

Looks like a regression, as this was previously fixed by upstream... see 
#501154 for details.

My 2 cents,



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#529783: marked as done (rt-tests and xenomai-runtime: error when trying to install together)

2009-06-14 Thread Debian Bug Tracking System

Your message dated Sun, 14 Jun 2009 15:39:51 +
with message-id 
and subject line Bug#529783: fixed in rt-tests 0.39-2
has caused the Debian Bug report #529783,
regarding rt-tests and xenomai-runtime: error when trying to install together
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
529783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xenomai-runtime,rt-tests
Version: xenomai-runtime/2.4.4-3
Version: rt-tests/0.39-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2009-05-21
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  libxenomai1 rt-tests xenomai-runtime
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package libxenomai1.
(Reading database ... 8136 files and directories currently installed.)
Unpacking libxenomai1 (from .../libxenomai1_2.4.4-3_amd64.deb) ...
Selecting previously deselected package rt-tests.
Unpacking rt-tests (from .../rt-tests_0.39-1_amd64.deb) ...
Selecting previously deselected package xenomai-runtime.
Unpacking xenomai-runtime (from .../xenomai-runtime_2.4.4-3_amd64.deb) ...
dpkg: error processing 
/var/cache/apt/archives/xenomai-runtime_2.4.4-3_amd64.deb (--unpack):
 trying to overwrite `/usr/bin/cyclictest', which is also in package rt-tests
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/xenomai-runtime_2.4.4-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail. Possible
solutions are to have the two packages conflict, to rename the common
file in one of the two packages, or to remove the file from one
package and have this package depend on the other package. File
diversions or a Replace relation are another possibility.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):


  usr/bin/cyclictest
  

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package.

-Ralf.


--- End Message ---
--- Begin Message ---
Source: rt-tests
Source-Version: 0.39-2

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

rt-tests_0.39-2.diff.gz
  to pool/main/r/rt-tests/rt-tests_0.39-2.diff.gz
rt-tests_0.39-2.dsc
  to pool/main/r/rt-tests/rt-tests_0.39-2.dsc
rt-tests_0.39-2_i386.deb
  to pool/main/r/rt-tests/rt-tests_0.39-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 529...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Uwe Kleine-König  (supplier of updated rt-tests 
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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 11 May 2009 00:18:37 +0200
Source: rt-tests
Binary: rt-tests
Architecture: source i386
Version: 0.39-2
Distribution: unstable
Urgency: low
Maintainer: Uwe Kleine-König 
Changed-By: Uwe Kleine-König 
Description: 
 rt-tests   - Test programs for rt kernels
Closes: 529783
Changes: 
 rt-tests (0.39-2) unstable; urgency=low
 .
   * add VCS URL to control
   * conflict with xenomai-runtime (Closes: #529783)
Checksums-Sha1: 
 44619e51ac1e653611c2e242ee169ce2d8d25e3d 1071 rt-tests_0.39-2.dsc
 38b20d18b6de37f19083de54b9d05ea988d851ab 1516 rt-tests_0.39-2.diff.gz
 8e45ff23b103b759ac65799022987f3064fbd071 42928 rt-tests_0.39-2_i386.deb
Checksums-Sha256: 
 5b47f1d564d369ce3ac45a4859d22639c469b87bc054ff96dfb53dea6ee2aaac 1071 
rt-tests_0.39-2.dsc
 db51415079c8052f2dc1fce8b86b3c6e76692f4e768c1ced8beceaffac89b957 1516 
rt-tests_0.39-2.diff.gz
 343ba86c5b1b4411a2dede7e8e8d2f0c25a3566c04e4799e5959c5154b482b81 42928 
rt-tests_0.39-2_i386.deb
Files: 
 02bc231cd624a3fcd9e965a21cba3d1d 1071 mis

Bug#531522: [Pkg-openmpi-maintainers] Bug#531522: Bug#531419: mpicc segfaults when called by fakeroot

2009-06-14 Thread Steve M. Robbins
On Sun, Jun 14, 2009 at 05:10:46PM +0200, Manuel Prinz wrote:
> Hi everyone!
> 
> On Fri, June 12, 2009 11:10 pm, Jeff Squyres wrote:
> > Agreed.  We thought that stat() was safe to call in the malloc init
> > hook -- it seems to be in most other places, at least.

Jeff, I agree that one would expect stat() to be safe; my comment
about "crafty things" wasn't intended as a judgement call on this
approach.  I think the code is pretty clever, but it's a hard problem
when you are operating with no clear rules about what is permitted in
the init hook.  :-)


> Unfortunately, I will not be able to use the internet for a week from now.
> This means that I can't help fixing the issue. I'm very sorry about that!
> 
> I hope Sylvestre can take over. If one wants to (or can) work out a fix,
> feel free to NMU. 

If Sylvestre wants to upload a fix, that's perfect.

Otherwise, I can easily convert my "#if 0" hack into a patch that
checks for an environment variable.  Jeff previously suggested
setting OMPI_MCA_disable_memory_allocator; is that the variable we
want to use?


Regards,
-Steve


signature.asc
Description: Digital signature


Bug#527065: util-vserver: diff for NMU version 0.30.216~r2772-6.1

2009-06-14 Thread Micah Anderson

Hi Andrew,

* Andrew Lee  [2009-06-13 02:40-0400]:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> tags 527065 +patch
> thanks
> 
> Dear maintainer,
> 
> I've prepared an NMU for util-vserver (versioned as 0.30.216~r2772-6.1).
> And it will be uploaded to DELAYED/02. Please free to tell me if I should
> delay it longer.

I appreciate the help with the package, although typically a NMU is done
after a patch is not being applied, so sending a patch and doing a 2-day
NMU at the same time is a little aggressive. I'm also wondering how you
can do this NMU because as far as I can tell you aren't yet a DD :)

I have been working on a new version of util-vserver to upload, with a
newer snapshot, so I was delaying this fix until that was
finished. However I can upload this fix to resolve the RC bug.

In any case, what would be even better than doing NMUs would be if you
would join the Alioth team and help with the util-vserver packaging
effort, its an open team, although nobody has helped on it so far and I
would appreciate the help!

Micah


signature.asc
Description: Digital signature


Bug#532920: Use security=tomoyo args

2009-06-14 Thread hito
Ritesh,
// also CC-ed Tetsuo Handa, he is main developer of TOMOYO Linux.

Maybe, ccs-auditd is not related ccs-editpolicy problem.
Please Try;
# /usr/lib/ccs/tomoyo_init_policy.sh
in your TOMOYO enabled environemnts, and reboot it.

You can use ccs-editpolicy commands... could you?
// That is heuristic guess from my experience...

 *** below are not ccs-editpolicy problems. ***

These are upstreams bug{,s}.
ccs-auditd(that is log collector of {grant,reject}_log in sysfs)
is not use in LSM ver. That is superfluous.

// See below, Kentaro Takeda (LSM version TOMOYO Linux's
// upstream dev team member) said in Japanese,
// "grant_log and reject_log does not exists 2.x series now".
// 
http://sourceforge.jp/projects/tomoyo/lists/archive/dev/2007-August/000523.html

ccs-auditd({grant,reject}_log) features were not implemented for LSM,
root problem is another thing.

IMHO, we have 2 points,

1) ccs-auditd has programing bug, that cry
   "Can't open /sys/kernel/security/tomoyo/grant_log for reading." eternaly.
   This is bad behavior.
   But, ccs-auditd and sysfs {grant,reject}_log are close set.

Notes: for some embeded environments(such as under 32MB memorys), the
*_log feature too big and rich.
So, ccstools can works without grant_log features

2) ccs-tools is unfriendly for LSM TOMOYO, its upstream problem.
   Current ccs-tools includes below stuffs:
 - ccs-auditd, that is
 - A lot of 1.6.x(non LSM version) documents.
 - mixed and confusable settings.
   They are misleading someone into confusion.

Now, I consult these ccstools(userland) problems to upstream authors.
Please wait sometimes..., and update packages when upstream commits. > henrich

Regards,



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#531522: [Pkg-openmpi-maintainers] Bug#531522: Bug#531419: mpicc segfaults when called by fakeroot

2009-06-14 Thread Manuel Prinz
Hi everyone!

On Fri, June 12, 2009 11:10 pm, Jeff Squyres wrote:
> Agreed.  We thought that stat() was safe to call in the malloc init
> hook -- it seems to be in most other places, at least.
>
> If there's some other safe way to check that stat() is *not* safe,
> that would be great.

Unfortunately, I will not be able to use the internet for a week from now.
This means that I can't help fixing the issue. I'm very sorry about that!

I hope Sylvestre can take over. If one wants to (or can) work out a fix,
feel free to NMU. I'm OK with 0-day NMUs for this case. The release team
also needs to be informed about the upload to schedule rebuilds again.
Sylvestre should be able to upload, though he is not a DD yet. But I guess
you guys can work it out.

I'm sorry for the situation and the delay it may cause! I will get back to
it as soon as I am back again.

Best regards
Manuel




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#532920: Use security=tomoyo args

2009-06-14 Thread Ritesh Raj Sarraf
Hito,

I see a lot of these messages in syslogd.

Jun 13 23:35:10 learner ccs-auditd: Can't open 
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 13 23:37:03 learner ccs-auditd: Can't open 
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 13 23:37:25 learner ccs-auditd: Can't open 
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 13 23:41:03 learner ccs-auditd: Can't open 
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 13 23:41:19 learner ccs-auditd: Can't open 
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 13 23:42:54 learner ccs-auditd: Can't open 
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 14 20:10:45 learner ccs-auditd: Can't open 
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 14 20:15:46 learner ccs-auditd: Can't open 
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 14 20:19:09 learner ccs-auditd: Can't open 
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 14 20:20:42 learner kernel: [  632.875114]  /sbin/init 
/etc/init.d/rc /sbin/startpar /etc/init.d/ssh /sbin/start-stop-daemon 
/usr/sbin/sshd /usr/sbin/sshd /bin/bash /usr/bin/sudo /usr/lib/ccs/editpolicy 
( /usr/lib/ccs/editpolicy ) is not permitted to update policies.


I think the problem is here:

openlog("ccs-auditd", 0,  LOG_USER);
for (i = 0; i < CCS_AUDITD_MAX_FILES; i++) {
fd_in[i] = open(procfile_path[i], O_RDONLY);
if (fd_in[i] == EOF) {
syslog(LOG_WARNING, "Can't open %s for reading.\n",
   procfile_path[i]);
return 1;
}
}

Looking at this, I wonder why and how it returned 0...

Am I doing something wrong that grant_log is not listed under sysfs ?

Ritesh


On Sunday 14 Jun 2009 20:21:57 Ritesh Raj Sarraf wrote:
> Hi Hito,
>
> On Sunday 14 Jun 2009 19:31:16 h...@kugutsu.org wrote:
> > Hi Ritesh,
> >
> > Did you set security=tomoyo to your kernel boot args?
> >
> > In 2.6.30s TOMOYO Linux (TOMOYO 2.x, a.k.a LSM version), that is LSM
> > implementations.
>
> Yes. I did add security=tomoyo in the kernel command line. The same was
> mentioned in the TOMOYO howto on the website.
>
> Here's the dmesg output.
>
> r...@learner:~$ dmesg | grep -i tomo
> [0.00] Kernel command line: root=/dev/mapper/VolGrpSDA4-ROOT ro
> audit=1 quiet vga=788 splash security=tomoyo
> [0.000999] TOMOYO Linux initialized
> [3.185069] Calling /sbin/tomoyo-init to load policy. Please wait.
> [4.075277] TOMOYO: 2.2.0   2009/04/01
>
> As you can see, tomoyo framework is getting initialized.
>
>
> The problem is with the ccs-auditd daemon. It fails to start.
> While there are some minor problems with the ccs-auditd init script, but
> for now, ccs-auditd itself is problematic. It doesn't start.
>
> Point to note:
> * As I said in the previous post to this bug report, I suspect the bug
> could be in here:
>
> [pid  6369] open("/sys/kernel/security/tomoyo/grant_log", O_RDONLY|
> O_LARGEFILE) = -1 ENOENT (No such file or directory)
> [pid  6369] brk(0)  = 0x8e69000
> [pid  6369] brk(0x8e8a000)  = 0x8e8a000
> [pid  6369] time(NULL)  = 1244990746
> [pid  6369] open("/etc/localtime", O_RDONLY) = 0
> [pid  6369] fstat64(0, {st_mode=S_IFREG|0644, st_size=265, ...}) = 0
>
> There is no grant_log under sysfs. Now is its unavailability fatal ?
>
> * Secondly, your ccs-auditd is exiting with wrong codes.
>
> r...@learner:~$ sudo ccs-auditd /dev/null /var/log/tomoyo/reject_log.txt
> r...@learner:~$ echo $?
> 0
>
> While you need to confirm my question in the previous point (grant_log
> being fatal or not), ccs-auditd should not return 0 during a failure.
>
> * And if grant_log is not fatal then I don't know why running the
> editpolicy command fails.
>
> r...@learner:~$ sudo ccs-editpolicy
> You need to register this program to /sys/kernel/security/tomoyo/manager to
> run this program.
> r...@learner:~$ ls /sys/kernel/security/tomoyo/
> domain_policy  exception_policy  manager  meminfo  profile  self_domain
> version
>
>
> Hope this helps. Please let me know if you need any more information.
>
> Ritesh

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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


Bug#532920: Use security=tomoyo args

2009-06-14 Thread Ritesh Raj Sarraf
Hi Hito,

On Sunday 14 Jun 2009 19:31:16 h...@kugutsu.org wrote:
> Hi Ritesh,
>
> Did you set security=tomoyo to your kernel boot args?
>
> In 2.6.30s TOMOYO Linux (TOMOYO 2.x, a.k.a LSM version), that is LSM
> implementations.
>

Yes. I did add security=tomoyo in the kernel command line. The same was 
mentioned in the TOMOYO howto on the website.

Here's the dmesg output.

r...@learner:~$ dmesg | grep -i tomo
[0.00] Kernel command line: root=/dev/mapper/VolGrpSDA4-ROOT ro 
audit=1 quiet vga=788 splash security=tomoyo
[0.000999] TOMOYO Linux initialized
[3.185069] Calling /sbin/tomoyo-init to load policy. Please wait.
[4.075277] TOMOYO: 2.2.0   2009/04/01

As you can see, tomoyo framework is getting initialized.


The problem is with the ccs-auditd daemon. It fails to start.
While there are some minor problems with the ccs-auditd init script, but for 
now, ccs-auditd itself is problematic. It doesn't start.

Point to note:
* As I said in the previous post to this bug report, I suspect the bug could 
be in here:

[pid  6369] open("/sys/kernel/security/tomoyo/grant_log", O_RDONLY|
O_LARGEFILE) = -1 ENOENT (No such file or directory)
[pid  6369] brk(0)  = 0x8e69000
[pid  6369] brk(0x8e8a000)  = 0x8e8a000
[pid  6369] time(NULL)  = 1244990746
[pid  6369] open("/etc/localtime", O_RDONLY) = 0
[pid  6369] fstat64(0, {st_mode=S_IFREG|0644, st_size=265, ...}) = 0

There is no grant_log under sysfs. Now is its unavailability fatal ?

* Secondly, your ccs-auditd is exiting with wrong codes.

r...@learner:~$ sudo ccs-auditd /dev/null /var/log/tomoyo/reject_log.txt
r...@learner:~$ echo $?
0

While you need to confirm my question in the previous point (grant_log being 
fatal or not), ccs-auditd should not return 0 during a failure.

* And if grant_log is not fatal then I don't know why running the editpolicy 
command fails.

r...@learner:~$ sudo ccs-editpolicy
You need to register this program to /sys/kernel/security/tomoyo/manager to 
run this program.
r...@learner:~$ ls /sys/kernel/security/tomoyo/
domain_policy  exception_policy  manager  meminfo  profile  self_domain  
version


Hope this helps. Please let me know if you need any more information.

Ritesh
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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


Bug#533033: marked as done (gcc-4.4: gcc and g++ do not find their cc1 and cc1plus binaries)

2009-06-14 Thread Debian Bug Tracking System

Your message dated Sun, 14 Jun 2009 10:49:06 -0400
with message-id <4a350de2.5090...@debian.org>
and subject line Re: Bug#533033: gcc-4.4: gcc and g++ do not find their cc1 and 
cc1plus binaries
has caused the Debian Bug report #533033,
regarding gcc-4.4: gcc and g++ do not find their cc1 and cc1plus binaries
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
533033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.4
Version: 4.4.0-6
Severity: grave
Justification: renders package unusable

gcc-4.4 and g++-4.4 cannot find their cc1 and cc1plus binaries
(respectively) - I am currently still working with 4.4.0-4 - as it seems
the only package version usable (I tested with 4.4.0-1, -3, -4, -5 and
-6) but all other than -1 seem not to find their files.

I did an strace run on 4.4.0-6 of the command

  gcc-4.4 --help=optimizers"


[...]
close(3)= 0
stat("/usr/lib/gcc/x86_64-linux-gnu/4.4.0/cc1", 0x7fff61a86a80) = -1 ENOENT (No 
such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/4.4.0/cc1", 0x7fff61a86a80) = -1 ENOENT (No 
such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/cc1", 0x7fff61a86a80) = -1 ENOENT (No such 
file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/4.4.0/cc1", 0x7fff61a86a80) = -1 ENOENT (No 
such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/cc1", 0x7fff61a86a80) = -1 ENOENT (No such 
file or directory)
stat("/usr/libexec/gcc/x86_64-linux-gnu/4.4.0/cc1", 0x7fff61a86a80) = -1 ENOENT 
(No such file or directory)
stat("/usr/libexec/gcc/x86_64-linux-gnu/cc1", 0x7fff61a86a80) = -1 ENOENT (No 
such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/4.4.0/cc1", 0x7fff61a86a80) = -1 ENOENT (No 
such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/cc1", 0x7fff61a86a80) = -1 ENOENT (No such 
file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/4.4.0/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/4.4.0/cc1",
 0x7fff61a86a80) = -1 ENOENT (No such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/4.4.0/../../../../x86_64-linux-gnu/bin/cc1",
 0x7fff61a86a80) = -1 ENOENT (No such file or directory)
vfork(gcc-4.4: error trying to exec 'cc1': execvp: No such file or directory
) = 24385
[...]


the cc1 binary is located in /usr/lib/gcc/x86_64-linux-gnu/4.4 where
only the symlink /usr/lib/gcc/x86_64-linux-gnu/4.4.1 points to.

The only files in the path /usr/lib/gcc/x86_64-linux-gnu/4.4.0 is:

  $ ls -l /usr/lib/gcc/x86_64-linux-gnu/4.4.0
  total 4
  drwxr-xr-x 2 root root 4096 2009-01-12 16:17 finclude

Anyone else having seen this?

Kind regards,
Marcus Fritzsch


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

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

Versions of packages gcc-4.4 depends on:
ii  binutils  2.19.1-1   The GNU assembler, linker and bina
ii  cpp-4.4   4.4.0-6The GNU C preprocessor
ii  gcc-4.4-base  4.4.0-6The GNU Compiler Collection (base 
ii  libc6 2.9-13 GNU C Library: Shared libraries
ii  libgcc1   1:4.4.0-6  GCC support library
ii  libgomp1  4.4.0-6GCC OpenMP (GOMP) support library

Versions of packages gcc-4.4 recommends:
ii  libc6-dev 2.9-13 GNU C Library: Development Librari

Versions of packages gcc-4.4 suggests:
pn  gcc-4.4-doc(no description available)
ii  gcc-4.4-locales   4.4.0-4The GNU C compiler (native languag
ii  gcc-4.4-multilib  4.4.0-6The GNU C compiler (multilib files
pn  libgcc1-dbg(no description available)
pn  libgomp1-dbg   (no description available)
ii  libmudflap0-4.4-dev   4.4.0-6GCC mudflap support libraries (dev
ii  libmudflap0-dbg   4.4.0-6GCC mudflap shared support librari

-- no debconf information


--- End Message ---
--- Begin Message ---
Marcus Fritzsch schrieb:
> Anyone else having seen this?

apparently not. if you are unsure, then don't file a RC report. this looks like
a local issue. please reopen if you are able to reproduce this on another
machine with an appropriate severity.


--- End Message ---


Processed: fixed as stated by submitter

2009-06-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 521373 0.2.27-1
Bug#521373: gimageview: Opening preferences causes segfault
Bug marked as found in version 0.2.27-1.

> fixed 521373 0.2.27-2
Bug#521373: gimageview: Opening preferences causes segfault
Bug marked as fixed in version 0.2.27-2.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#521553: marked as done (Staging drivers contain non-free firmware)

2009-06-14 Thread Debian Bug Tracking System

Your message dated Sun, 14 Jun 2009 13:45:09 +
with message-id 
and subject line Bug#521553: fixed in linux-2.6 2.6.30-1
has caused the Debian Bug report #521553,
regarding Staging drivers contain non-free firmware
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
521553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.29
Severity: serious

[cc-ed to debian-eeepc-devel as the affected network controller is uused in
several eeepc models]

Hi,

The file drivers/staging/rt2860/common/firmware.h contains the following
text:

/*
 Copyright (c) 2007, Ralink Technology Corporation
 All rights reserved.

 Redistribution.  Redistribution and use in binary form, without
 modification, are permitted provided that the following conditions are
 met:

* Redistributions must reproduce the above copyright notice and the
following disclaimer in the documentation and/or other materials
provided with the distribution.
* Neither the name of Ralink Technology Corporation nor the names of its
suppliers may be used to endorse or promote products derived from this
software without specific prior written permission.
* No reverse engineering, decompilation, or disassembly of this software
is permitted.

 Limited patent license. Ralink Technology Corporation grants a world-wide,
 royalty-free, non-exclusive license under patents it now or hereafter
 owns or controls to make, have made, use, import, offer to sell and
 sell ("Utilize") this software, but solely to the extent that any
 such patent is necessary to Utilize the software alone, or in
 combination with an operating system licensed under an approved Open
 Source license as listed by the Open Source Initiative at
 http://opensource.org/licenses.  The patent license shall not apply to
 any other combinations which include this software.  No hardware per
 se is licensed hereunder.

 DISCLAIMER.  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
 CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
 BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
 FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
 COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
 INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
 BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
 OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
 ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
 TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
 USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
 DAMAGE.
*/
/* AUTO GEN PLEASE DO NOT MODIFY IT */

(followed by a big array of bytes)

This fails several of the DFSG:

Redistribution is allowed only without modification. This breaks the "Derived
Works" requirement.

"No reverse engineering, decompilation, or disassembly of this software is
permitted." breaks the "No Discrimination Against Fields of Endeavor"
requirement.

There is no source code so it breaks the "Source Code" requirement. The byte
array is just a C equivalent of the binary image. It is explicitly prohibited
to decompile the image, suggesting it is a result of some compilation from e.g.
some source code (which is not provided).


Thanks,
dam


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

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


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.30-1

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

linux-2.6_2.6.30-1.diff.gz
  to pool/main/l/linux-2.6/linux-2.6_2.6.30-1.diff.gz
linux-2.6_2.6.30-1.dsc
  to pool/main/l/linux-2.6/linux-2.6_2.6.30-1.dsc
linux-2.6_2.6.30.orig.tar.gz
  to pool/main/l/linux-2.6/linux-2.6_2.6.30.orig.tar.gz
linux-doc-2.6.30_2.6.30-1_all.deb
  to pool/main/l/linux-2.6/linux-doc-2.6.30_2.6.30-1_all.deb
linux-headers-2.6.30-1-all-powerpc_2.6.30-1_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.30-1-all-powerpc_2.6.30-1_powerpc.deb
linux-headers-2.6.30-1-all_2.6.30-1_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.30-1-all_

Bug#532920: Use security=tomoyo args

2009-06-14 Thread hito
Hi Ritesh,

Did you set security=tomoyo to your kernel boot args?

In 2.6.30s TOMOYO Linux (TOMOYO 2.x, a.k.a LSM version), that is LSM
implementations.

Default LSM modules are SELinux, we must set activate LSM mods in kopts.

Regards,



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#532656: [Pkg-octave-devel] Bug#532656: Bug#532656: octave3.2_3.2.0-1(mips/unstable): FTBFS on mips. Segfault in regression test.

2009-06-14 Thread Rafael Laboissiere
* Rafael Laboissiere  [2009-06-14 12:25]:

> I think that the different values of x_max and x_min explain the bug on
> the mips system.  I guess that this is caused by the following lines in
> pr-output.cc (function set_format):
> 
>   int x_max = max_abs == 0.0  
>  
> ? 0 : static_cast (floor (log10 (max_abs) + 1.0));   
>  
>   
>  
>   int x_min = min_abs == 0.0  
>  
> ? 0 : static_cast (floor (log10 (min_abs) + 1.0));   
>  

I meant lines 854 to 858 in pr-output.cc, in function 
set_format (const Complex& c, int& r_fw, int& i_fw)

-- 
Rafael



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#530572: pinot_0.93-1(mips/unstable): FTBFS on mips - undefined reference

2009-06-14 Thread Fabrice Colin
On Sat, Jun 13, 2009 at 11:57 PM, Jonas Smedegaard wrote:
> Unfortunately my first attempt didn't work out as intended.
>
> Haven't found time to verify yet, but seems to be that I should set
> CPPFLAGS instead of CFLAGS (they are handled separately in CDBS
> packaging tool).
>
> Perhaps your upstream autotools setting should be similarly adjusted?
>
Try CXXFLAGS, it will be picked up by configure and used at build time.
I have had reports the fix in SVN r1635 fixed the issue, but if you
have a log for me to look into, let me know.

Fabrice



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#533054: python-kde3: segmentation faults when python program imports dcopext libraries

2009-06-14 Thread Barchan
Package: python-kde3
Version: 3.16.1-1
Severity: serious


Python programs segfault when import dcopext module.

$ python2.5
Python 2.5.4 (r254:67916, Feb 17 2009, 20:16:45)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import dcopext
zsh: segmentation fault (core dumped)  python2.5


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

Kernel: Linux 2.6.29-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-kde3 depends on:
ii  kdelibs4c2a  4:3.5.10.dfsg.1-2   core libraries and binaries for al
ii  libc62.9-14  GNU C Library: Shared libraries
ii  libgcc1  1:4.4.0-6   GCC support library
ii  libqt3-mt3:3.3.8really3.3.7-0ubuntu9 Qt GUI Library (Threaded runtime v
ii  libstdc++6   4.4.0-6 The GNU Standard C++ Library v3
ii  libx11-6 2:1.2.1-1   X11 client-side library
ii  libxext6 2:1.0.4-1   X11 miscellaneous extension librar
ii  python   2.5.4-2 An interactive high-level object-o
ii  python-centr 0.6.11  register and build utility for Pyt
ii  python-qt3   3.18-2  Qt3 bindings for Python

ii  python-sip4  4.8-1   Python/C++ bindings generator 
runtime library

python-kde3 recommends no packages.

python-kde3 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#532656: [Pkg-octave-devel] Bug#532656: octave3.2_3.2.0-1(mips/unstable): FTBFS on mips. Segfault in regression test.

2009-06-14 Thread Rafael Laboissiere
* Rafael Laboissiere  [2009-06-13 09:15]:

> So, even if log2 returns a wrong value, the bug happens elsewhere. At any
> rate, the following works as expected:
> 
> complex (NaN, NaN)
> complex (0, NaN)
> complex (NaN, Inf)
> 
> I am puzzled with this problem and I cannot really debug it, since I am
> not versed in GDB.  The bug arises at line 1442 of pr-output.cc, in
> function pr_complex():
> 
> pr_imag_float (os, i, i_fw); 


I think I found the culprit but I am stuck with the debugging (see
below). If I set a breakpoint at line 703 of pr-output.cc, I see the
following when I launch "complex(NaN,0)" at the octave prompt under gdb:

Breakpoint 4, set_complex_format (x_max=2147483647, x_min=0, 
r_x=2147483647, inf_or_nan=true, int_only=0, 
r_...@0x7facdd70, i_...@0x7facdd74) at pr-output.cc:703
703   int prec = Voutput_precision;

On my amd64 system I see the following, instead:

Breakpoint 6, set_complex_format (x_max=0, x_min=-2147483648, 
r_x=-2147483648, inf_or_nan=true, int_only=0, 
r_...@0x7fffd1dd6afc, i_...@0x7fffd1dd6af8) at pr-output.cc:703
703   int prec = Voutput_precision;

I think that the different values of x_max and x_min explain the bug on
the mips system.  I guess that this is caused by the following lines in
pr-output.cc (function set_format):

  int x_max = max_abs == 0.0
   
? 0 : static_cast (floor (log10 (max_abs) + 1.0)); 
   

   
  int x_min = min_abs == 0.0
   
? 0 : static_cast (floor (log10 (min_abs) + 1.0)); 
   
 
However, I cannot debug the problem because the variables are not
visible from gdb and many things seem to be inlined.

Would it be possible to write a simple C++ test program that would expose
the problem on mips?

-- 
Rafael



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Processed: tagging 521553

2009-06-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> tags 521553 + pending
Bug#521553: Staging drivers contain non-free firmware
Tags were: pending
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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org