Bug#563357: marked as done (postgresql-8.4: FTBFS on mips: Not all files are installed)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jan 2010 08:37:22 +0100
with message-id <20100122073722.ga2...@piware.de>
and subject line Re: Bug#563357: postgresql-8.4: FTBFS on mips: Not all files 
are installed
has caused the Debian Bug report #563357,
regarding postgresql-8.4: FTBFS on mips: Not all files are installed
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.)


-- 
563357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-8.4
Version: 8.4.2-1
Severity: grave

Hi,

Your package failed to build in mips with the following error:
8<--->8
# verify that all files are installed; ignore manpages, since
# they are handled by dh_installman
missing=`dh_install --sourcedir=debian/tmp --list-missing --no-act 2>&1 | grep 
-v man/man`; \
if [ -n "$missing" ]; then \
echo "Not all files are installed:"; \
echo "$missing"; \
exit 1; \
fi
Not all files are installed:
dpkg: warning: failed to open configuration file '/nonexistent/.dpkg.cfg' for 
reading: Permission denied
dpkg: warning: failed to open configuration file '/nonexistent/.dpkg.cfg' for 
reading: Permission denied
make: *** [common-binary-predeb-arch] Error 1
8<--->8

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


--- End Message ---
--- Begin Message ---
Version: 8.4.2-2

Raphael Geissert [2010-01-02  2:01 -0600]:
> Your package failed to build in mips with the following error:
> 8<--->8
> # verify that all files are installed; ignore manpages, since
> # they are handled by dh_installman
> missing=`dh_install --sourcedir=debian/tmp --list-missing --no-act 2>&1 | 
> grep -v man/man`; \
>   if [ -n "$missing" ]; then \
>   echo "Not all files are installed:"; \
>   echo "$missing"; \
>   exit 1; \
>   fi
> Not all files are installed:
> dpkg: warning: failed to open configuration file '/nonexistent/.dpkg.cfg' for 
> reading: Permission denied

This apparently was a temporary glitch, 8.4.2-2 built fine again.
Closing.

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

--- End Message ---

Processed (with 2 errors): tagging as pending bugs that are closed by packages in NEW

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Fri Jan 22 07:03:40 UTC 2010
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: hdf5
> tags 540875 + pending
Failed to alter tags of Bug 540875: Not altering archived bugs; see unarchive.

> # Source package in NEW: lrzip
> tags 455457 + pending
Bug #455457 [wnpp] ITP: lrzip -- Long Range ZIP - a compression program 
optimised for large files.
Added tag(s) pending.
> # Source package in NEW: liblog4ada
> tags 562942 + pending
Bug #562942 [wnpp] ITP: liblog4ada -- An Ada library for flexible logging
Added tag(s) pending.
> # Source package in NEW: djagios
> tags 559285 + pending
Bug #559285 [wnpp] ITP: djagios -- A package to help configure nagios written 
in Django
Added tag(s) pending.
> # Source package in NEW: alien-arena
> tags 592770 + pending
Failed to alter tags of Bug 592770: Unable to read any bugs successfully.

> # Source package in NEW: alien-arena
> tags 467387 + pending
Bug #467387 [alien-arena] alien-arena: Game fails to start
Added tag(s) pending.
> # Source package in NEW: alien-arena
> tags 552038 + pending
Bug #552038 {Done: Michael Gilbert } [alien-arena] 
Security issue in server code
Added tag(s) pending.
> # Source package in NEW: alien-arena
> tags 513659 + pending
Bug #513659 [alien-arena] alien-arena: bad watch file
Added tag(s) pending.
> # Source package in NEW: alien-arena
> tags 437461 + pending
Bug #437461 [alien-arena] Game crashes after trying to apply changes in video 
settings
Added tag(s) pending.
> # Source package in NEW: duply
> tags 565544 + pending
Bug #565544 [wnpp] ITP: duply -- easy to use frontend to duplicity
Added tag(s) pending.
> # Source package in NEW: rrdtool
> tags 559370 + pending
Bug #559370 [rrdtool] rrdtool: new upstream release available (1.4.2)
Added tag(s) pending.
> # Source package in NEW: rrdtool
> tags 565833 + pending
Bug #565833 [librrd-ruby1.9] librrd-ruby1.9: Please drop the dependency on ruby 
1.9.0
Added tag(s) pending.
> # Source package in NEW: rrdtool
> tags 565835 + pending
Bug #565835 [rrdtool-dbg] rrdtool-dbg: Please drop the dependency on ruby 1.9.0
Added tag(s) pending.
> # Source package in NEW: rrdtool
> tags 550919 + pending
Bug #550919 [rrdtool] rrdtool: manpages /transfered/ s/r/&&/g
Added tag(s) pending.
> # Source package in NEW: zookeeper
> tags 561947 + pending
Bug #561947 [wnpp] RFP: zookeeper -- Information management inside a cluster. 
Part of the hadoop family.
Added tag(s) pending.
> # Source package in NEW: network-manager
> tags 558471 + pending
Bug #558471 [network-manager] network-manager: ships an empty TODO file
Added tag(s) pending.
> # Source package in NEW: network-manager
> tags 549502 + pending
Bug #549502 [network-manager] network-manager: Please port to PolicyKit 1
Added tag(s) pending.
> # Source package in NEW: network-manager
> tags 553320 + pending
Bug #553320 [network-manager] network-manager: i can has 0.8 snapshot plzkthxbai
Added tag(s) pending.
> # Source package in NEW: network-manager
> tags 380626 + pending
Bug #380626 [network-manager] network-manager: Patch to add debugging packages
Bug #518234 [network-manager] network-manager: please provide a -dbg package
Bug #540086 [network-manager] please add a debug package
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) 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#491892: marked as done (This package should not be released with lenny)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jan 2010 08:13:17 +0100
with message-id <201001220813.23...@fortytwo.ch>
and subject line hg-buildpackage: package was removed
has caused the Debian Bug report #491892,
regarding This package should not be released with lenny
to be marked as done.

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

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


-- 
491892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hg-buildpackage
Severity: serious
User: debian...@lists.debian.org
Usertags: npolsr-cleanup

I think that package hg-buildpackage should not be released with
lenny because:

 * It was not released with etch, meaning that its
   absence from the release most likely causes no
   regressions for Debian stable users.
 * It has a low popcon value, indicating that not many
   people already rely on it.
 * No other packages depend on it.
 * It is orphaned.

My suggestions is that this package should
be removed from testing, but kept in Debian for now.

If you object to this reasoning, please speak up in the next
seven days (or better yet, adopt the package and close this
bug with your initial upload).

Gruesse,
-- 
Frank Lichtenheld 
http://www.djpig.de/



--- End Message ---
--- Begin Message ---
Hi,

hg-buildpackage was removed from Debian some time ago, so keeping these bugs 
open doesn't make sense.

cheers
-- vbi

-- 
Protect your privacy - encrypt your email: http://fortytwo.ch/gpg/intro


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

Bug#552874: marked as done (qpopper: FTBFS: popper.c:149: error: conflicting types for 'getline')

[Debian Bug Tracking System]

Your message dated Fri, 22 Jan 2010 07:17:43 +
with message-id 
and subject line Bug#552874: fixed in qpopper 4.0.9.dfsg-1.1
has caused the Debian Bug report #552874,
regarding qpopper: FTBFS: popper.c:149: error: conflicting types for 'getline'
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.)


-- 
552874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qpopper
Version: 4.0.9.dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091028 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

In eglibc <= 2.9, getline was only defined if _GNU_SOURCE was defined.
In eglibc 2.10, getline is always defined (since it became a standard in
POSIX2008). The problem is that your package already has a function
named getline(), which now conflicts with glibc's. You need to rename
your function to something else.
Ubuntu already fixed many occurences of your problem, so it is possible
that an Ubuntu patch is available for your package. Look at the PTS to
find out.

Relevant part:
> gcc -c -I.. -I.. -I. \
>   -I../mmangle -I../common -I/usr/local/ssl/include \
>   -g -O2 -DHAVE_CONFIG_H  -DLINUX -DUNIX popper.c -o popper.o
> popper.c: In function 'qpopper':
> popper.c:149: error: conflicting types for 'getline'
> /usr/include/stdio.h:651: error: previous declaration of 'getline' was here
> popper.c: In function 'tgetline':
> popper.c:613: warning: passing argument 1 of 'getline' from incompatible 
> pointer type
> popper.c:613: warning: passing argument 2 of 'getline' makes pointer from 
> integer without a cast
> popper.c:613: warning: passing argument 3 of 'getline' from incompatible 
> pointer type
> popper.c:613: warning: assignment makes pointer from integer without a cast
> make[2]: *** [popper.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/10/28/qpopper_4.0.9.dfsg-1_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: qpopper
Source-Version: 4.0.9.dfsg-1.1

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

qpopper-drac_4.0.9.dfsg-1.1_i386.deb
  to main/q/qpopper/qpopper-drac_4.0.9.dfsg-1.1_i386.deb
qpopper_4.0.9.dfsg-1.1.diff.gz
  to main/q/qpopper/qpopper_4.0.9.dfsg-1.1.diff.gz
qpopper_4.0.9.dfsg-1.1.dsc
  to main/q/qpopper/qpopper_4.0.9.dfsg-1.1.dsc
qpopper_4.0.9.dfsg-1.1_i386.deb
  to main/q/qpopper/qpopper_4.0.9.dfsg-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 552...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jari Aalto  (supplier of updated qpopper 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, 17 Jan 2010 22:27:20 +0200
Source: qpopper
Binary: qpopper qpopper-drac
Architecture: source i386
Version: 4.0.9.dfsg-1.1
Distribution: unstable
Urgency: low
Maintainer: William Pitcock 
Changed-By: Jari Aalto 
Description: 
 qpopper- Enhanced Post Office Protocol server (POP3)
 qpopper-drac - Qpopper with DRAC Support
Closes: 552874
Changes: 
 qpopper (4.0.9.dfsg-1.1) unstable; urgency=low
 .
   [Jari Aalto]
   * Non-maintainer upload.
   * debian/patches
- (getline): Add patch to fix Gcc 4.4 error: conflicting types for getline
  (RC bug FTBFS serious; Closes: #552874).
Checksums-Sha1: 
 0cd4c7f4a3122f02050388e22b1ed8dcea06da25 1178 qpopper_4.0.9.dfsg-1.1.dsc
 cf4516224cb469eb029b268ae9c8a872ebfbd88b 97054 qpopper_4.0.9.dfsg-1.1.diff.gz
 f74774caf28921ee25f95e59d10dfaf5b3fc6882 414590 qpopper_4.0.9.dfsg-1.1_i386.deb
 d11fc506779e63601feb175a7a

Bug#560485: marked as done (tardy: FTBFS: common/trace.cc:268: error: invalid conversion from 'const char*' to 'char*')

[Debian Bug Tracking System]

Your message dated Fri, 22 Jan 2010 06:47:26 +
with message-id 
and subject line Bug#560485: fixed in tardy 1.12-3.1
has caused the Debian Bug report #560485,
regarding tardy: FTBFS: common/trace.cc:268: error: invalid conversion from 
'const char*' to 'char*'
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.)


-- 
560485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tardy
Version: 1.12-3
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091210 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> x86_64-linux-gnu-g++ -g -O2 -Icommon -Icommon -c common/trace.cc
> common/trace.cc: In function 'void trace_char_real(char*, char*)':
> common/trace.cc:263: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:268: error: invalid conversion from 'const char*' to 'char*'
> common/trace.cc:275: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:283: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc: In function 'void trace_char_unsigned_real(char*, unsigned 
> char*)':
> common/trace.cc:290: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:295: error: invalid conversion from 'const char*' to 'char*'
> common/trace.cc:302: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:310: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc: In function 'void trace_int_real(char*, int*)':
> common/trace.cc:317: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc: In function 'void trace_int_unsigned_real(char*, unsigned 
> int*)':
> common/trace.cc:324: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc: In function 'void trace_long_real(char*, long int*)':
> common/trace.cc:331: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc: In function 'void trace_long_unsigned_real(char*, long 
> unsigned int*)':
> common/trace.cc:338: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc: In function 'void trace_pointer_real(char*, void*)':
> common/trace.cc:348: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:350: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc: In function 'void trace_short_real(char*, short int*)':
> common/trace.cc:357: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc: In function 'void trace_short_unsigned_real(char*, short 
> unsigned int*)':
> common/trace.cc:364: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc: In function 'void trace_string_real(char*, char*)':
> common/trace.cc:374: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:377: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:380: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:412: error: invalid conversion from 'const char*' to 'char*'
> common/trace.cc:414: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:418: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:443: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:446: warning: deprecated conversion from string constant to 
> 'char*'
> common/trace.cc:449: warning: deprecated conversion from string constant to 
> 'char*'
> make[1]: *** [common/trace.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/12/10/tardy_1.12-3_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: tardy
Source-Version: 1.12-3.1

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

Bug#560629: marked as done (freedroid: FTBFS: dh_install: Compatibility levels before 5 are deprecated.)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jan 2010 06:47:13 +
with message-id 
and subject line Bug#560629: fixed in freedroid 1.0.2+cvs040112-1.2
has caused the Debian Bug report #560629,
regarding freedroid: FTBFS: dh_install: Compatibility levels before 5 are 
deprecated.
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.)


-- 
560629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freedroid
Version: 1.0.2+cvs040112-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091210 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory 
> `/build/user-freedroid_1.0.2+cvs040112-1.1-amd64-VbmyoX/freedroid-1.0.2+cvs040112'
> make[3]: Nothing to be done for `install-exec-am'.
> mkdir -m 0755 -p -- 
> /build/user-freedroid_1.0.2+cvs040112-1.1-amd64-VbmyoX/freedroid-1.0.2+cvs040112/debian/tmp/usr/share/man/man6
>  /usr/bin/install -c -m 644 ./freedroid.6 
> /build/user-freedroid_1.0.2+cvs040112-1.1-amd64-VbmyoX/freedroid-1.0.2+cvs040112/debian/tmp/usr/share/man/man6/freedroid.6
> make[3]: Leaving directory 
> `/build/user-freedroid_1.0.2+cvs040112-1.1-amd64-VbmyoX/freedroid-1.0.2+cvs040112'
> make[2]: Leaving directory 
> `/build/user-freedroid_1.0.2+cvs040112-1.1-amd64-VbmyoX/freedroid-1.0.2+cvs040112'
> make[1]: Leaving directory 
> `/build/user-freedroid_1.0.2+cvs040112-1.1-amd64-VbmyoX/freedroid-1.0.2+cvs040112'
> test -z "`dh_install --sourcedir=debian/tmp --list-missing 2>&1 | tee 
> /dev/stderr`"
> dh_install: Compatibility levels before 5 are deprecated.
> make: *** [install] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/12/10/freedroid_1.0.2+cvs040112-1.1_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: freedroid
Source-Version: 1.0.2+cvs040112-1.2

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

freedroid-data_1.0.2+cvs040112-1.2_all.deb
  to main/f/freedroid/freedroid-data_1.0.2+cvs040112-1.2_all.deb
freedroid_1.0.2+cvs040112-1.2.diff.gz
  to main/f/freedroid/freedroid_1.0.2+cvs040112-1.2.diff.gz
freedroid_1.0.2+cvs040112-1.2.dsc
  to main/f/freedroid/freedroid_1.0.2+cvs040112-1.2.dsc
freedroid_1.0.2+cvs040112-1.2_i386.deb
  to main/f/freedroid/freedroid_1.0.2+cvs040112-1.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 560...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jari Aalto  (supplier of updated freedroid 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, 17 Jan 2010 01:03:51 +0200
Source: freedroid
Binary: freedroid freedroid-data
Architecture: source i386 all
Version: 1.0.2+cvs040112-1.2
Distribution: unstable
Urgency: low
Maintainer: Yann Dirson 
Changed-By: Jari Aalto 
Description: 
 freedroid  - A clone of Paradroid - a strategic shoot-em up
 freedroid-data - Data files for freedroid - a strategic shoot-em up
Closes: 560629
Changes: 
 freedroid (1.0.2+cvs040112-1.2) unstable; urgency=low
 .
   [Jari Aalto]
   * Non-maintainer upload.
   * debian/compat
 - Update from 4 to 7 (RC bug FTBFS serious; Closes: #560629).
   * debian/control
 - (Build-Depends): update debhelper to 7.
 - (Package freedroid::Depends): Change ${Source-Version} to 
${source:Version}
   (E; lintian).
Checksums-Sha1: 
 d55c6c2fa6d8f5d6a3648a6eb9282b3e7c6fe9e7 1098 freedroid_1.0.2+cvs040112-1.2.dsc
 42cf597816969ac80f514f8fbba2c0fceb372b40 19575 
freedroid_1.0.2+cvs040112-1.2.diff.gz
 e258a55c4d4aaaf7f57f631fad53fe7a06dfccb8 140136 
freedroid_1.0.2+

Bug#566211: Exact log

[Craig Small]

On Fri, Jan 22, 2010 at 01:38:54AM +, Glen wrote:
>Setting up procps (1:3.2.7-11) ...
>invoke-rc.d: not a symlink: "/etc/rc3.d/S30procps"
>invoke-rc.d: dangling symlink: "/etc/rc3.d/S30procps"
>invoke-rc.d: not a symlink: "/etc/rcS.d/S30procps"
>invoke-rc.d: dangling symlink: "/etc/rcS.d/S30procps"
Looks like you have some local modifications.
Can you show me the following?
ls -l /etc/rc3.d/S30procps
ls -l /etc/rcS.d/S30procps

 - Craig
-- 
Craig Small  GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
http://www.enc.com.au/ csmall at : enc.com.au
http://www.debian.org/  Debian GNU/Linux, software should be Free 



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

Bug#562946: fails to install -- update

[Deepak Tripathi]

Hi Stefano,

I am able to reproduce the bug, Please find the steps for reproduce it,

1) uninstall libtre4 from your system
2) try to install crm14 from apt. it will break while installation.





Thanks
dk

On Fri, Jan 22, 2010 at 3:01 AM, Stefano Zacchiroli  wrote:

> On Mon, Jan 04, 2010 at 10:21:00PM +0530, Deepak Tripathi wrote:
> > I have installed in my system, Yes this package need to be build-dep on
> > libtre4 . After installing libtre4, i am able to install package
> > successfully.
>
> Again, the build-dep or dep on libtre4 has nothing to do with the bug
> reported by Holger. The bug is above a (still to be explained) failure
> in the pre-installation script of crm114. That, as far as we can tell
> from the information collected thus far, has nothing to with libtre4.
>
> I'm unable to reproduce the bug (yet), but looking at the preinst it is
> likely to be the "exit 1" explicitly mentioned in the debconf config
> script.
>
> Cheers.
>
> --
> Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
> z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
> Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
> sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
>



-- 
Deepak Tripathi
E3 71V3 8Y C063 (We Live By Code)
http://deepaktripathi.blogspot.com

Bug#542975: pathfinder and wvstreams update (Re: Bug#542975: pathfinder: FTBFS)

[Hideki Yamane]

Hi Patrick,

 I made a diff for pathfinder (only debian directory).
 Could you review it, please?

 If both of you would find no problem with it, please upload to repository.
 
http://mentors.debian.net/debian/pool/main/p/pathfinder/pathfinder_1.1.3-0.1.dsc
 > Steffen


diff -urN pathfinder-0.2.4/debian/changelog pathfinder-1.1.3/debian/changelog
--- pathfinder-0.2.4/debian/changelog   2010-01-21 07:36:04.0 +0900
+++ pathfinder-1.1.3/debian/changelog   2010-01-21 11:34:25.0 +0900
@@ -1,3 +1,32 @@
+pathfinder (1.1.3-0.1) unstable; urgency=low
+
+  * NMU with maintainer's ACK.
+  * New upstream release
+- fix "FTBFS: iwvdbuslistener.h:13:24: error: wvcallback.h: No such file or
+  directory" to use the new WvDBus in WvStreams (Closes: #542975)
+- Include stdint.h for GCC 4.4 compatibility.  (Closes: #505053)
+- Remove the send-interface lines from the DBUS configuration. 
+  (Closes: #510696)
+  * debian/control: 
+- Standards-Version: 3.8.3 
+- libpathfinder-dev: add Depends: ${misc:Depends}
+- Build-Depends: "libldap2-dev", deal with cmake complains about 
+  "LDAP Development packages"
+- set "Build-Depends: libwvstreams-dev (>= 4.6.1)", to use package
+  that enabled --with-dbus option
+- add Homepage: field
+  * debian/rules:
+- properly remove CMake"F"iles in clean target and fix clean lines order.
+  * debian/pathfinderd.prerm:
+- add "set -e"
+  * debian/copyright
+- add my name and specify GPL version 2
+  * debian/watch: add it. 
+  * debian/pathfinderd.{default,dirs,init,postrm}
+- merge from SVN r200:r203, remove unnecessary "--test" argument and more.
+
+ -- Hideki Yamane (Debian-JP)   Thu, 21 Jan 2010 
11:34:05 +0900
+
 pathfinder (0.2.4-4) unstable; urgency=low
 
   * Fix the diff, so that it doesn't include all of the CMake garbage.
diff -urN pathfinder-0.2.4/debian/control pathfinder-1.1.3/debian/control
--- pathfinder-0.2.4/debian/control 2010-01-21 07:36:04.0 +0900
+++ pathfinder-1.1.3/debian/control 2010-01-21 11:34:01.0 +0900
@@ -2,8 +2,9 @@
 Section: utils
 Priority: optional
 Maintainer: Patrick Patterson 
-Build-Depends: cmake, debhelper (>= 5), libdbus-1-dev, libnss3-dev, 
libwvstreams-dev (>=4.4.1), pkg-config, libboost-dev, libssl-dev
-Standards-Version: 3.7.3
+Build-Depends: cmake, debhelper (>= 5), libdbus-1-dev, libnss3-dev, 
libwvstreams-dev (>=4.6.1), pkg-config, libboost-dev, libssl-dev, libldap2-dev
+Standards-Version: 3.8.3
+Homepage: http://code.google.com/p/pathfinder-pki/
 
 Package: pathfinderd
 Architecture: any
@@ -67,6 +68,7 @@
 Package: libpathfinder-dev
 Architecture: any
 Section: libdevel
+Depends: ${misc:Depends}
 Provides: libpathfinder-1-dev
 Description: Development files for pathfinder
  Pathfinder is designed to provide a mechanism for any program to perform
diff -urN pathfinder-0.2.4/debian/copyright pathfinder-1.1.3/debian/copyright
--- pathfinder-0.2.4/debian/copyright   2010-01-21 07:36:04.0 +0900
+++ pathfinder-1.1.3/debian/copyright   2010-01-21 07:06:22.0 +0900
@@ -36,5 +36,6 @@
 
 
 The Debian packaging is (C) 2007, Patrick Patterson  and
-is licensed under the GPL, see `/usr/share/common-licenses/GPL'.
+(C) 2010 Hideki Yamane , is licensed under the GPL 
+Version2, see `/usr/share/common-licenses/GPL-2'.
 
diff -urN pathfinder-0.2.4/debian/pathfinderd.default 
pathfinder-1.1.3/debian/pathfinderd.default
--- pathfinder-0.2.4/debian/pathfinderd.default 2010-01-21 07:36:04.0 
+0900
+++ pathfinder-1.1.3/debian/pathfinderd.default 2010-01-21 07:06:22.0 
+0900
@@ -1,5 +1,5 @@
 # Defaults for pathfinder initscript
-# sourced by /etc/init.d/pathfinder
+# sourced by /etc/init.d/pathfinderd
 # installed at /etc/default/pathfinder by the maintainer scripts
 
 #
diff -urN pathfinder-0.2.4/debian/pathfinderd.dirs 
pathfinder-1.1.3/debian/pathfinderd.dirs
--- pathfinder-0.2.4/debian/pathfinderd.dirs1970-01-01 09:00:00.0 
+0900
+++ pathfinder-1.1.3/debian/pathfinderd.dirs2010-01-21 07:06:22.0 
+0900
@@ -0,0 +1 @@
+var/cache/pathfinder/crls
diff -urN pathfinder-0.2.4/debian/pathfinderd.init 
pathfinder-1.1.3/debian/pathfinderd.init
--- pathfinder-0.2.4/debian/pathfinderd.init2010-01-21 07:36:04.0 
+0900
+++ pathfinder-1.1.3/debian/pathfinderd.init2010-01-21 07:06:22.0 
+0900
@@ -80,18 +80,18 @@
#   just the same as "restart" except that it does nothing if the
#   daemon isn't already running.
# check wether $DAEMON is running. If so, restart
-   start-stop-daemon --stop --test --quiet --pidfile \
+   start-stop-daemon --stop --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON \
&& $0 restart \
|| exit 0
;;
   restart)
 log_begin_msg "Restarting $DESC: "
-   start-stop-daemon --stop --test--quiet --pidfile \
-   /var/run/$NAME.pid --exec $DAEMON
+   start-stop-daemon --stop --quie

Processed: severity of 566208 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 566208 important
Bug #566208 [linux-image-2.6.26-2-486] linux-image-2.6.26-2-486: e_powersaver 
causes constant lockups
Severity set to 'important' from 'critical'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#566211: Exact log

[Glen]

Here is an excerpt from the setup log:

Setting up procps (1:3.2.7-11) ...
invoke-rc.d: not a symlink: "/etc/rc3.d/S30procps"
invoke-rc.d: dangling symlink: "/etc/rc3.d/S30procps"
invoke-rc.d: not a symlink: "/etc/rcS.d/S30procps"
invoke-rc.d: dangling symlink: "/etc/rcS.d/S30procps"
dpkg: error processing procps (--configure):
 subprocess post-installation script returned error exit status 102
Processing triggers for menu ...
Errors were encountered while processing:
 procps
E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#566211: procps: Installation/Removal scripts give install-rc.d issues with symlinks

[TGP1994]

Package: procps
Version: 1:3.2.7-11
Severity: grave
Justification: renders package unusable



-- System Information:
Debian Release: 5.0.3
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages procps depends on:
ii  libc6 2.7-18lenny2   GNU C Library: Shared libraries
ii  libncurses5   5.7+20081213-1 shared libraries for terminal hand
ii  lsb-base  3.2-20 Linux Standard Base 3.2 init scrip

Versions of packages procps recommends:
ii  psmisc22.6-1 Utilities that use the proc filesy

procps suggests no packages.

-- no debconf information

I get several errors from install-rc.d when I try to install procps, mentioning 
"dangling" symlinks. I've tried everything to get it working.



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

Bug#566192: initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30

[Steve Langasek]

reassign 566192 mdadm
severity 566192 grave
thanks

On Thu, Jan 21, 2010 at 09:52:08PM +0100, Louis Richard Pirlet wrote:
> I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the system
> over the new kernel. I still can boot it from the old 2.6.26 kernel.
> 
> My root disk is  on a mirror raid based on 2 SCSI disk. The boot process
> stopsand gives a message to the effect that the file system is unavailable.
> 
> I have an extended knowledge on hardware (I used to be a DEC/Compaq/HP
> harware support engineer on pdp11/VAX/alpha under VMS and Tru64). I have
> no indepth knowledge of the linux system.
> 
> I think there is a problem with the initramfs-tools because there is no
> mdadm.conf describing my md devices... In fact there is no mdadm directory
> under etc in the initrd.img-2.6.30.2.686 created by the upgrade.

Inclusion of mdadm.conf in initramfs is the responsibility of the mdadm
hook, not of initramfs-tools itself.  Reassigning.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature

Processed: Re: Bug#566192: initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 566192 mdadm
Bug #566192 [initramfs-tools] initramfs-tools: md0 device not recognized at 
boot after upgrade to kernel 2.6.30
Bug reassigned from package 'initramfs-tools' to 'mdadm'.
Bug No longer marked as found in versions initramfs-tools/0.93.4.
> severity 566192 grave
Bug #566192 [mdadm] initramfs-tools: md0 device not recognized at boot after 
upgrade to kernel 2.6.30
Severity set to 'grave' from 'critical'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#566192: initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30

[martin f krafft]

also sprach Louis Richard Pirlet  [2010.01.22.0952 +1300]:
> I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the
> system over the new kernel. I still can boot it from the old
> 2.6.26 kernel.
> 
> My root disk is  on a mirror raid based on 2 SCSI disk. The boot
> process stopsand gives a message to the effect that the file
> system is unavailable.

Have you tried the rootdelay parameter?

> I think there is a problem with the initramfs-tools because there
> is no mdadm.conf describing my md devices... In fact there is no
> mdadm directory under etc in the initrd.img-2.6.30.2.686 created
> by the upgrade.

This is not good but mdadm's initramfs is designed to work anyway.
Once your system boots, it would be good to find out what's going
on. Is there an /etc/mdadm/mdadm.conf there?

-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

Bug#563882: git-core FTBFS on ia64: t1001-read-tree-m-2way.sh test fails

[Jonathan Nieder]

Hi Anders,

Thanks for your work on this.

Anders Kaseorg wrote:

> Now that Git 1.6.6.1 is out, I propose we build git-core 1.6.6.1-1 with 
> the patch I posted above , which lets 
> the two tests in question expect to fail on ia64 only.

>From the log, it looks like git read-tree is working fine, so some of
the other tests that use 'git diff --no-index' might be expected to
fail, too.  The build log stops at t1001.  Do we want to suppress
t4002, t4011, t4013, t4018, t4033, and t4044 as well?

No Itanium porters have arrived to help.  Who would confirm then that
the result was sane enough for people to use?  As a user, I would
rather use a v1.6.5 build that works (does it still?) than a v1.6.6
that cannot even pass the early tests in the test suite.

> Then ia64 users 
> can have a package to test this with more easily,

Given access to an ia64 to test on, I would gladly test this myself.
All it takes is downloading git from http://git-scm.com or the Debian
archive, running ‘make test’, and then looking around a little when it
fails.

I don’t think this is what autobuilders are for.

If we want to use buildds instead, the thing to do would be to change
'$(MAKE) $(TEST)' to '$(MAKE) -k $(TEST)' in debian/rules.  Then the
build fails, so we are not screwing over the Itanium users, but at
least all the tests are run.

> have to wait for us to find an ia64 user and convince them to care (which 
> we’ve all been unable to do for several weeks).

Actually, we don’t need an ia64 user, just a Debian Developer.
http://db.debian.org/machines.cgi?host=merulo

> As far as I can tell, this test failure was triggered by some kind of 
> change on the buildd and is not a real regression from the version in 
> testing, given that it was observed with an earlier version in Ubuntu.  

By the way, is there a build log for this available?

> The only other option I see is to disable the ia64 architecture entirely 
> for git-core, given that we’re effectively unable to support it.

This is the right solution, unless someone out there cares.  Personally,
I would rather build a package from source so I can diagnose problems
as they come than find myself using a version that is both untested and
known not to work.

Besides, even if we ignore the errors, they would constitute a grave bug
that would prevent migration of git to testing, no?

Just my two cents,
Jonathan



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

Bug#566208: linux-image-2.6.26-2-486: e_powersaver causes constant lockups

[Ross Vandegrift]

Package: linux-image-2.6.26-2-486
Version: 2.6.26-19lenny2
Severity: critical
Justification: breaks the whole system

After upgrading linux-image-2.6.26-2-486 from 17lenny1 to 19lenny2, I
started experiencing 100% reproducable system lockups on a VIA C7
system.  No errors in the logs, no oops, no BUG, nothing - just a hard
lock.  No keyboard LED response and no sysrq functionality worked.

Sometimes the system wouldn't complete the boot process without
freezing.  Sometimes it would last three minutes or so before
freezing.  I could reproduce the lockup with "cat /dev/zero > file".
Every time, within 10 seconds, the system would freeze.

After a lot of trial, error, and searching, I discovered that the
e_powersaver module was being loaded and the lockups went away if I
unloaded it.

The kernel build help text indicates that the module shouldn't ever be
used, and is highly dangerous:

 This adds the CPUFreq driver for VIA C7 processors.  However, this
 driver does not have any safeguards to prevent operating the CPU out
 of spec and is thus considered dangerous.  Please use the regular ACPI
 cpufreq driver, enabled by CONFIG_X86_ACPI_CPUFREQ.

I have blacklisted this module and suspect that it should be
blacklisted by default.  It seems possible that Debian bug #563941 is
related to this issue as well, but there's not enough info in the
report for me to be sure.

Thanks,
Ross

-- Package-specific info:
** Version:
Linux version 2.6.26-2-486 (Debian 2.6.26-19lenny2) (da...@debian.org) (gcc 
version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 Wed Nov 4 20:19:07 
UTC 2009

** Command line:
root=LABEL=root ro 

** Not tainted

** Kernel log:
[   13.058778] udevd version 125 started
[   13.061147] usb 2-1: new low speed USB device using uhci_hcd and address 2
[   13.303392] usb 2-1: configuration #1 chosen from 1 choice
[   13.308441] usb 2-1: New USB device found, idVendor=051d, idProduct=0002
[   13.308522] usb 2-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[   13.308596] usb 2-1: Product: Back-UPS XS 1300 LCD FW:836.H7 .D USB FW:H7 
[   13.308667] usb 2-1: Manufacturer: American Power Conversion
[   13.308736] usb 2-1: SerialNumber: 8B0749R09108  
[   17.063851] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   17.111770] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   17.171321] Linux agpgart interface v0.103
[   17.321713] agpgart: Detected VIA P4M900 chipset
[   17.324789] agpgart: AGP aperture is 32M @ 0xfc00
[   19.291607] Initializing USB Mass Storage driver...
[   19.400611] scsi4 : SCSI emulation for USB Mass Storage devices
[   19.401000] scsi5 : SCSI emulation for USB Mass Storage devices
[   19.401232] usbcore: registered new interface driver usb-storage
[   19.401305] USB Mass Storage support registered.
[   19.461227] usb-storage: device found at 4
[   19.461238] usb-storage: waiting for device to settle before scanning
[   19.464808] usb-storage: device found at 2
[   19.464815] usb-storage: waiting for device to settle before scanning
[   19.832163] input: Power Button (FF) as /class/input/input1
[   19.863234] ACPI: Power Button (FF) [PWRF]
[   19.863598] input: Sleep Button (CM) as /class/input/input2
[   19.888589] ACPI: Sleep Button (CM) [SLPB]
[   19.60] input: Power Button (CM) as /class/input/input3
[   19.921730] ACPI: Power Button (CM) [PWRB]
[   22.914126] input: PC Speaker as /class/input/input4
[   23.138478] Error: Driver 'pcspkr' is already registered, aborting...
[   23.248778] ACPI: PCI Interrupt :80:01.0[A] -> GSI 17 (level, low) -> 
IRQ 17
[   23.248968] PCI: Setting latency timer of device :80:01.0 to 64
[   24.460310] usb-storage: device scan complete
[   24.461172] scsi 5:0:0:0: Direct-Access Generic  Flash Disk   8.07 
PQ: 0 ANSI: 2
[   24.475496] sd 5:0:0:0: [sde] 1978368 512-byte hardware sectors (1013 MB)
[   24.476243] sd 5:0:0:0: [sde] Write Protect is off
[   24.476321] sd 5:0:0:0: [sde] Mode Sense: 03 00 00 00
[   24.476330] sd 5:0:0:0: [sde] Assuming drive cache: write through
[   24.479494] sd 5:0:0:0: [sde] 1978368 512-byte hardware sectors (1013 MB)
[   24.480239] sd 5:0:0:0: [sde] Write Protect is off
[   24.480318] sd 5:0:0:0: [sde] Mode Sense: 03 00 00 00
[   24.480326] sd 5:0:0:0: [sde] Assuming drive cache: write through
[   24.480414]  sde:<7>usb-storage: device scan complete
[   24.522804] scsi 4:0:0:0: Direct-Access Seagate  FreeAgent0132 
PQ: 0 ANSI: 4
[   24.706237]  sde1
[   24.706650] sd 5:0:0:0: [sde] Attached SCSI removable disk
[   24.710798] sd 4:0:0:0: [sdf] 3907029168 512-byte hardware sectors (2000399 
MB)
[   24.711555] sd 4:0:0:0: [sdf] Write Protect is off
[   24.711646] sd 4:0:0:0: [sdf] Mode Sense: 2d 08 00 00
[   24.711654] sd 4:0:0:0: [sdf] Assuming drive cache: write through
[   24.712930] sd 4:0:0:0: [sdf] 3907029168 512-byte hardware sectors (2000399 
MB)
[   24.714540] sd 4:0:0:0: [sdf] Write Protect is off
[   24.714628] sd 4:0:0:0: [sdf] Mod

Bug#562307: marked as done (sgml-base-doc: FTBFS: Nonexistent build-dependency: tetex-bin)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jan 2010 00:32:15 +
with message-id 
and subject line Bug#562307: fixed in sgml-base-doc 1.99.1
has caused the Debian Bug report #562307,
regarding sgml-base-doc: FTBFS: Nonexistent build-dependency: tetex-bin
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.)


-- 
562307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sgml-base-doc
Version: 1.16
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091213 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> ** Using build dependencies supplied by package:
> Build-Depends-Indep: debhelper (>= 4.1), debiandoc-sgml, libpaperg, sp, 
> tetex-bin, tetex-extra
> 
> ┌──┐
> │ Install build dependencies  
>  │
> └──┘
> 
> Checking for already installed source dependencies...
> debhelper: missing
> Using default version 7.4.10
> debiandoc-sgml: missing
> libpaperg: missing
> sp: missing
> tetex-bin: missing
> tetex-extra: missing
> Checking for source dependency conflicts...
> E: Package tetex-bin has no installation candidate

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/12/13/sgml-base-doc_1.16_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: sgml-base-doc
Source-Version: 1.99.1

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

sgml-base-doc_1.99.1.dsc
  to main/s/sgml-base-doc/sgml-base-doc_1.99.1.dsc
sgml-base-doc_1.99.1.tar.gz
  to main/s/sgml-base-doc/sgml-base-doc_1.99.1.tar.gz
sgml-base-doc_1.99.1_all.deb
  to main/s/sgml-base-doc/sgml-base-doc_1.99.1_all.deb



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

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

Debian distribution maintenance software
pp.
Daniel Leidert (dale)  (supplier of updated 
sgml-base-doc 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: Fri, 22 Jan 2010 01:18:03 +0100
Source: sgml-base-doc
Binary: sgml-base-doc
Architecture: source all
Version: 1.99.1
Distribution: unstable
Urgency: low
Maintainer: Debian XML/SGML Group 
Changed-By: Daniel Leidert (dale) 
Description: 
 sgml-base-doc - Documentation for sgml-base
Closes: 562307
Changes: 
 sgml-base-doc (1.99.1) unstable; urgency=low
 .
   * Upload to unstable to fix FTBFS.
   * debian/control (Standards-Version): Bumped to 3.8.3.
 (Build-Depends): Increased for dh level 7.
 (Depends): Fixed debhelper-but-no-misc-depends.
   * debian/compat: Bumped to 7.
   * debian/rules: Adjusted for dh level 7.
 .
 sgml-base-doc (1.99.0) experimental; urgency=low
 .
   * Makefile: Dropped build system. debian/rules and debhelper are enough.
 .
   * debian/compat: Increased compatibility level to 5.
   * debian/control: Added Vcs*, Homepage and DM-Upload-Allowed fields.
 (Uploaders): Added myself.
 (Build-Depends-Indep): Moved debhelper to Build-Depends. Replaced tetex*
 packages by texlive packages (closes: #562307).
 (Standards-Version): Bumped to 3.8.2.
   * debian/rules: Rewritten in parts. Now contains all stuff from the
 Makefile. Added a check target.
   * debian/sgml-base-doc.doc-base (Document): Fixed. Thanks to lintian.
   * debian/sgml-base-doc.README.Debian: Renamed to debian/README.Debian.
Checksums-Sha1: 
 6a5e1747b8bc9c11ec7522ee6312ae60ff581e9c 1194 sgml-base-doc_1.99.1.dsc
 8db3103555bf7626e2916caf87f059

Bug#565318: [Pkg-bluetooth-maintainers] Bug#565318: Bug#565318: obexd-server thought as the new implementation of the old obex-data-server

[Nobuhiro Iwamatsu]

Hi , all.

2010/1/15 Andrea Veri :
> On Fri, 15 Jan 2010, Filippo Giunchedi wrote:
>
>> On Thu, Jan 14, 2010 at 08:26:15PM +0100, Andrea Veri wrote:
>> > The old obexd maintainer did a transition between obexd-server and
>> > obex-data-server thinking that they bot ship the same D-Bus API but this is
>> > not right. They are different packages and as far as I know no package is
>> > currently using obexd-server to work at the moment. (e.g no GNOME package
>> > does yet)
>>
>> As stated in the changelog, the conflict is because obexd and 
>> obex-data-server
>> both register as services on org.openobex dbus name, and this still stands
>> AFAICT.
>
> yes, and that's why the conflict will stay where it is.
>
>
>> > The great problem is that obexd-server conflicts with obex-data-server 
>> > which
>> > means that quite all the devices that should use obex-data-server (like 
>> > many
>> > functionalities of gnome-bluetooth and more) are now completely unusable.
>>
>> which interface gnome-bluetooth uses? obexd or ods? it should properly depend
>> on one of those of course. Also note that obexd has been splitted into client
>> and server exactly to not make g-b directly conflict with ods. (IOW, g-b
>> depends on obexd-client but recommends obexd-server which in turn conflicts
>> with ods)
>
> g-bluetooth uses obex-data-server to work and as far as I know no
> GNOME package is currently (and will use) obexd-server to work.
> obexd-server looks broken upstream-side since they started using
> org.openobex without providing a new namespace, and that will take any
> device requesting org.openbox not finding it and therefore failing.
> (like the issues g-bluetooth was having while browsing mobile phones
> with obexd-server)
>
>
>> > This bug needs to be fixed ASAP, I'm CCing Joss so that we can help out
>> > fixing this issue. If you don't have enough time for this we will try to
>> > think about a working solution and then upload a fixed package.
>>
>> I have no interest (nor time) right now, feel free to adopt/NMU.
>
> obexd got adopted already, let's hope the new maintainer will have
> this fixed. :)
>

I contacted upstream of obex-data-server.
obex-data-server was made in GoSC/2007 under mentoring of
Marcel Holtmann, bluez and obexd maintainer.

He was ordered  DBUS name to orig.openobex to set it to Marcel.
And Marcel made obexd in this back. However, Marcel seems to have made DBUS name
same value at this time.
Marcel seems to have directed him to change it, but said that he did
not want to change it.

I understood that they did not want to change DBUS-name each other.
I think that we have to take the method how user cannot install
obex-data-serve and obexd in
at the same time in Debian.

How do you think abaout this idea?

Best regards,
  Nobuhiro
-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6



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

Bug#566206: python2.5: ftbfs on lenny

[Michael Gilbert]

On Fri, 22 Jan 2010 01:12:21 +0100 Matthias Klose wrote:

> On 22.01.2010 01:01, Michael Gilbert wrote:
> > package: python2.5
> > version: 2.5.2-15
> > severity: serious
> >
> > hi, python2.5 fails to build from source on lenny.  i am working on
> > fixing the expat security issues, so i am considering disabling the
> > failing pybench test in order to get it to build.  do you see any issue
> > with doing so?  see build error below.
> 
> no, as long as the testsuite runs.
> 
> however I'd like to know why this fails ... or what setup problem for this 
> machines lets the calibration fail.

i just did a clean 5.0.3 lenny install (in virtualbox) because i
thought i may have inadvertently broken something in my standard lenny
vm (also in virtualbox).  but the build failed anyway. it could be an
issue with virtualbox, but that seems unlikely.

i tried running the pybench test independently of the package build, and
it succeeded.  odd.

mike



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

Bug#566206: python2.5: ftbfs on lenny

[Matthias Klose]

On 22.01.2010 01:01, Michael Gilbert wrote:

package: python2.5
version: 2.5.2-15
severity: serious

hi, python2.5 fails to build from source on lenny.  i am working on
fixing the expat security issues, so i am considering disabling the
failing pybench test in order to get it to build.  do you see any issue
with doing so?  see build error below.


no, as long as the testsuite runs.

however I'd like to know why this fails ... or what setup problem for this 
machines lets the calibration fail.




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

Processed: Re: Bug#566206: Acknowledgement (python2.5: ftbfs on lenny)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 566206 2.5.4-3
Bug #566206 [python2.5] python2.5: ftbfs on lenny
Ignoring request to alter found versions of bug #566206 to the same values 
previously set
> thanks
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#566206: python2.5: ftbfs on lenny

[Michael Gilbert]

package: python2.5
version: 2.5.2-15
severity: serious

hi, python2.5 fails to build from source on lenny.  i am working on
fixing the expat security issues, so i am considering disabling the
failing pybench test in order to get it to build.  do you see any issue
with doing so?  see build error below.

best wishes,
mike



BEGIN pybench static
cd /home/zero79/source/python2.5/python2.5-2.5.2/build-static \
  && time ./python ../Tools/pybench/pybench.py -f run1.pybench
---
PYBENCH 2.0
---
* using Python 2.5.2
* disabled garbage collection
* system check interval set to maximum: 2147483647
* using timer: time.time

Creating benchmark: run1.pybench (rounds=10, warp=10)

Calibrating tests. Please wait...

* Internal Error (use --debug to display the traceback)


real0m3.427s
user0m2.708s
sys 0m0.708s
make: *** [stamp-pybench] Error 1
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
debuild: fatal error at line 1319:
dpkg-buildpackage -rfakeroot -D -us -uc failed



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

Processed: Re: Bug#566189: openoffice.org: Openoffice crashes on startup

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 566189 Thorsten Behrens 
Bug #566189 [openoffice.org] openoffice.org: Openoffice crashes on startup
Set Bug forwarded-to-address to 'Thorsten Behrens '.
> retitle 566189 openoffice.org: Openoffice crashes on startup with 
> DeploymentException
Bug #566189 [openoffice.org] openoffice.org: Openoffice crashes on startup
Changed Bug title to 'openoffice.org: Openoffice crashes on startup with 
DeploymentException' from 'openoffice.org: Openoffice crashes on startup'
> thanks
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#566189: openoffice.org: Openoffice crashes on startup

[Rene Engelhard]

forwarded 566189 Thorsten Behrens 
retitle 566189 openoffice.org: Openoffice crashes on startup with 
DeploymentException
thanks

Hi,

On Fri, Jan 22, 2010 at 12:09:25AM +0100, Rene Engelhard wrote:
> 
> On Thu, Jan 21, 2010 at 10:38:48PM +0100, Ferry Toth wrote:
> > After upgrading today from openoffice.org (1:3.1.1-8) to 1:3.1.1-14, 
> > Openoffice crashes immediately on startup.
> > 
> > Starting from the command line lets me pick the document type, then crashes 
> > as well with:
> > 
> > terminate called after throwing an instance of 
> > 'com::sun::star::deployment::DeploymentException'
> > 
> > Deleting .openoffice.org did not help.
> 
> We just had the same case on IRC and it turned out to be a corrupt
> file. 

... which according to upstream is a real bug. (set fwd)

> He removed the whole directory 
> (com.sun.star.comp.deployment.component.PackageRegistryBackend; you can also 
> remove everything below cache if you wish)
> and then it works. (Of course if you want all the extensions then you
> need to reinstall the packages; ignore the errors about not existing 
> extensions
> before unpacking, they're expected in this case)

Use this hackaround for now.

> I'll now try to debootstrap an old squeeze wizth 1:3.1.1-8, install
> OOo with some extensions and upgrade...

Interestingly I can't reproduce this in a 1:3.1.1-8->1:3.1.1-14 upgrade
(installed: openoffice.org openoffice.org-sdbc-postgresql)

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  r...@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70



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

Processed: subversion Debian ci: r1077 - in src/1.6.x/debian: . patches

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 561516 pending
Bug #561516 [src:subversion] subversion: FTBFS with gcj 4.4: 
subversion/bindings/javahl/include/*$*: No such file or directory
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#566204: src:banshee-extension-mirage: FTBFS: Package requirements were not met

[Cyril Brulebois]

Package: src:banshee-extension-mirage
Version: 0.5.0-2
Severity: serious
Justification: FTBFS

Hi,

your package FTBFS this way:
| checking pkg-config is at least version 0.9.0... yes
| configure: error: Package requirements (banshee-1-thickclient >= 1.3.2) were 
not met:
| 
| Package taglib-sharp was not found in the pkg-config search path.
| Perhaps you should add the directory containing `taglib-sharp.pc'
| to the PKG_CONFIG_PATH environment variable
| Package 'taglib-sharp', required by 'Banshee Core', not found
| 
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
| 
| Alternatively, you may set the environment variables BANSHEE_CFLAGS
| and BANSHEE_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
| 
| make: *** [debian/stamp-autotools-configure] Error 1

Full build logs available at:
  
https://buildd.debian.org/status/package.php?p=banshee-extension-mirage&suite=unstable

Might be arch-specific somehow, or just the Build-Depended-on packages
may have changed lately.

Mraw,
KiBi.



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

Bug#566203: wicd 1.7 fails to start

[Guilherme]

Package: wicd
Version: 1.7.0-2
Severity: grave
Justification: renders package unusable

Hello,

I even reported it to the wicd guys but they told me that the problem is in the 
Debian packages:

https://bugs.launchpad.net/wicd/+bug/510589

Thank you.


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

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

Versions of packages wicd depends on:
ii  wicd-daemon   1.7.0-2wired and wireless network manager
ii  wicd-gtk [wicd-client]1.7.0-2wired and wireless network manager

wicd recommends no packages.

wicd suggests no packages.

-- debconf information:
* wicd/users:



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

Bug#566189: openoffice.org: Openoffice crashes on startup

[Rene Engelhard]

Hi,

On Thu, Jan 21, 2010 at 10:38:48PM +0100, Ferry Toth wrote:
> After upgrading today from openoffice.org (1:3.1.1-8) to 1:3.1.1-14, 
> Openoffice crashes immediately on startup.
> 
> Starting from the command line lets me pick the document type, then crashes 
> as well with:
> 
> terminate called after throwing an instance of 
> 'com::sun::star::deployment::DeploymentException'
> 
> Deleting .openoffice.org did not help.

We just had the same case on IRC and it turned out to be a corrupt
file. 

2:13 < _rene_> crashes after/when reading this:
22:13 < _rene_> 15252 
open("/var/spool/openoffice/uno_packages/cache/registry/com.sun.star.comp.
22:13 < _rene_> deployment.component.PackageRegistryBackend/Linux_x86_.rdb", 
O_RDWR) = 56
22:13 < _rene_> try to remove it
22:13 < _rene_> (and then reinstall all extension packages)

He removed the whole directory 
(com.sun.star.comp.deployment.component.PackageRegistryBackend; you can also 
remove everything below cache if you wish)
and then it works. (Of course if you want all the extensions then you
need to reinstall the packages; ignore the errors about not existing extensions
before unpacking, they're expected in this case)

I'll now try to debootstrap an old squeeze wizth 1:3.1.1-8, install
OOo with some extensions and upgrade...

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  r...@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70



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

Bug#561347: flumotion: uses non-essential package in pre-rtupdate script

[Jakub Wilk]

* Stefano Zacchiroli , 2010-01-21, 23:21:

flumotion is using /usr/bin/python in the pre-rtupdate script. Since
this script is run in the preinst of the python package, it is not
guaranteed that the /usr/bin/python symlink exists or that it points
to an existing file.

You should use only the essential packages in the pre-rtupdate
script; otherwise it's likely that flumotion will break next update
of the default version of Python.


Just for the sake of providing more information to this bug log: can you
please be more specific?

In fact /usr/share/python/runtime.d/flumotion.rtupdate does not use
directly python, but it does use invoke-rc.d on flumotion. In turn
/etc/init.d/flumotion does not invoke directly python, but will
eventually invoke /usr/sbin/flumotion which is a #!/usr/bin/python.

I believe that invocation path (which is of course buggy!) is what you
were referring to, confirmation would be appreciate, also to be sure I'm
not missing some other run path


Indeed I was referring to this particular run path and I'm not aware of 
other ones.


Sorry for being not specific enough in my initial report.

--
Jakub Wilk


signature.asc
Description: Digital signature

Bug#528115: gallery2: contains non-free material

[Jan Wagner]

Hi Michael,

On Saturday, 24. October 2009, Michael Schultheiss wrote:
> Luk Claes wrote:
> > What's the status of this RC bug report?
> 
> I've done the equivalent fix for gallery - I need to do a similar fix
> for gallery2 as well.
 
any progress here?

Thanks and with kind regards, Jan.
-- 
Never write mail to , you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y 
--END GEEK CODE BLOCK--


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

Bug#553534: Solution is pending

[Mats Erik Andersson]

package durep
tags 553534 + pending
thanks

This is just to inform any reader and potential hard working
bug squasher, that there is a pending solution to this bug.
A package was uploaded to mentors.debian.net on January, 20th,
and now it awaits evaluation.


Best regards,
-- 
Mats Erik Andersson, fil. dr


signature.asc
Description: Digital signature

Processed: Solution is pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> package durep
Limiting to bugs with field 'package' containing at least one of 'durep'
Limit currently set to 'package':'durep'

> tags 553534 + pending
Bug #553534 [durep] durep: dir-or-file-in-var-www /var/www/durep/bar.png and 
two others
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562946: fails to install -- update

[Jan Wagner]

Hi Deepak,

On Monday, 4. January 2010, Deepak Tripathi wrote:
> I have installed in my system, Yes this package need to be build-dep on
> libtre4 . After installing libtre4, i am able to install package
> successfully.
> 
> debian:~/Debian_project/ruby/libterm# dpkg -l | grep "libtre4"
> ii  libtre4  0.7.6-2regexp
> matching library with approximate mat
> debian:~/Debian_project/ruby/libterm#

any progress here so far?

Thanks and with kind regards, Jan.
-- 
Never write mail to , you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y 
--END GEEK CODE BLOCK--


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

Bug#560442: marked as done (tigr-glimmer: FTBFS: gene.cc:449: error: invalid conversion from 'const char*' to 'char*')

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 22:32:20 +
with message-id 
and subject line Bug#560442: fixed in tigr-glimmer 3.02-2
has caused the Debian Bug report #560442,
regarding tigr-glimmer: FTBFS: gene.cc:449: error: invalid conversion from 
'const char*' to 'char*'
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.)


-- 
560442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tigr-glimmer
Version: 3.02-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091210 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory 
> `/build/user-tigr-glimmer_3.02-1-amd64-rqE7SK/tigr-glimmer-3.02/src/Common'
> @@@  delcher.cc @
> @@@  fasta.cc @
> @@@  gene.cc @
> gene.cc: In member function 'void PWM_t::Print(FILE*)':
> gene.cc:264: warning: deprecated conversion from string constant to 'char*'
> gene.cc: In function 'int Char_Sub(char)':
> gene.cc:449: error: invalid conversion from 'const char*' to 'char*'
> make[3]: *** [gene.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/12/10/tigr-glimmer_3.02-1_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: tigr-glimmer
Source-Version: 3.02-2

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

tigr-glimmer_3.02-2.diff.gz
  to main/t/tigr-glimmer/tigr-glimmer_3.02-2.diff.gz
tigr-glimmer_3.02-2.dsc
  to main/t/tigr-glimmer/tigr-glimmer_3.02-2.dsc
tigr-glimmer_3.02-2_amd64.deb
  to main/t/tigr-glimmer/tigr-glimmer_3.02-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 560...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated tigr-glimmer 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: Thu, 21 Jan 2010 22:52:45 +0100
Source: tigr-glimmer
Binary: tigr-glimmer
Architecture: source amd64
Version: 3.02-2
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description: 
 tigr-glimmer - Gene detection in archea and bacteria
Closes: 560442
Changes: 
 tigr-glimmer (3.02-2) unstable; urgency=low
 .
   * debian/control:
 - Fixed Vcs-Svn (missing svn/)
 - Updated Standards-Version to 3.8.1 (no changes needed)
 - Standards-Version: 3.8.3 (no changes needed)
 - debhelper (>= 7)
   * Fixed E-Mail address of upstream author in debian/copyright
   * Fix FTBFS on amd64
 Closes: #560442
   * Added README.source
Checksums-Sha1: 
 b568e7d6cd98d60e72507c62eb930ebecc716acf 1382 tigr-glimmer_3.02-2.dsc
 10f525fecdc7ed3a3c9152fa4b4b6f033aa45a97 19189 tigr-glimmer_3.02-2.diff.gz
 4a3932d166507f7246ffe4b9dc2d21d76ef322cb 441648 tigr-glimmer_3.02-2_amd64.deb
Checksums-Sha256: 
 e2d0d1f41b9fddf4271c000f080d0bd015f6d44ccb2ee82491a429700062d263 1382 
tigr-glimmer_3.02-2.dsc
 e682b0748dee7b07ef2aa95dbecb7a59ea1ca33f7d0d581e6fdb8f691412e5da 19189 
tigr-glimmer_3.02-2.diff.gz
 9f65b42c18b5232e8f2de3fc76b79e819190826d4905a05c99b22d0922287ec2 441648 
tigr-glimmer_3.02-2_amd64.deb
Files: 
 a67f05012fb43b0fc086fcb557f7697a 1382 science optional tigr-glimmer_3.02-2.dsc
 f1a6b47b6ad3b7a97914595a5409ffe3 19189 science optional 
tigr-glimmer_3.02-2.diff.gz
 4b4792cab32a4c699bc071c6689a515e 441648 science optional 
tigr-glimmer_3.02-2_amd64.deb

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

iEYEARECAAYFAktY0egACgkQYDBbMcCf01rdhACg

Bug#526207: marked as done (FTBFS with GCC 4.4: missing #include)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 23:32:26 +0100
with message-id <20100121223226.ga25...@usha.takhisis.invalid>
and subject line Re: Bug#526207: FTBFS with GCC 4.4: missing #include
has caused the Debian Bug report #526207,
regarding FTBFS with GCC 4.4: missing #include
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.)


-- 
526207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jaula
Version: 1.4.0-2
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.4
Tags: patch

Your package fails to build with GCC 4.4, which has cleaned up some more
C++ headers.  You always have to #include headers directly and cannot
rely for things to be included indirectly.

You can reproduce this problem with gcc-snapshot from unstable or
gcc-4.4 from experimental.

> Automatic build of jaula_1.4.0-2 on em64t by sbuild/amd64 0.53
...
> libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT 
> jaula_lexan.lo -MD -MP -MF .deps/jaula_lexan.Tpo -c jaula_lexan.cc  -fPIC 
> -DPIC -o .libs/jaula_lexan.o
> jaula_lexan.cc: In member function 'int jaulaFlexLexer::yyinput()':
> jaula_lexan.cc:1505: error: 'EOF' was not declared in this scope
> make[4]: *** [jaula_lexan.lo] Error 1
> make[4]: Leaving directory `/build/tbm/jaula-1.4.0/jaula'

The patch below will work.  However, since the other #include
statements are wrapped in an #ifdef statement you may want to do this
for this #include too.

--- jaula/jaula_lexan.ll~   2009-04-29 20:55:20.0 +
+++ jaula/jaula_lexan.ll2009-04-29 20:56:24.0 +
@@ -50,6 +50,8 @@
 #endif
 }
 
+#include 
+
 #ifdef HAVE_SSTREAM
 #include 
 #endif

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


--- End Message ---
--- Begin Message ---
tags 526207 + unreproducible
thanks

On Wed, Apr 29, 2009 at 11:01:08PM +0200, Martin Michlmayr wrote:
> Your package fails to build with GCC 4.4, which has cleaned up some more
> C++ headers.  You always have to #include headers directly and cannot
> rely for things to be included indirectly.

> > libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT 
> > jaula_lexan.lo -MD -MP -MF .deps/jaula_lexan.Tpo -c jaula_lexan.cc  -fPIC 
> > -DPIC -o .libs/jaula_lexan.o
> > jaula_lexan.cc: In member function 'int jaulaFlexLexer::yyinput()':
> > jaula_lexan.cc:1505: error: 'EOF' was not declared in this scope
> > make[4]: *** [jaula_lexan.lo] Error 1
> > make[4]: Leaving directory `/build/tbm/jaula-1.4.0/jaula'

I'm closing this bug as no longer reproducible. The package builds fine
with current gcc in unstable (tested in fresh cowbuilder). I've
investigated a bit the reason, and apparently recent flex adds 
among standard C headers, thus avoiding the need of specifying it
explicitly.

Cheers.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime

--- End Message ---

Processed: Re: Bug#526207: FTBFS with GCC 4.4: missing #include

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 526207 + unreproducible
Bug #526207 [jaula] FTBFS with GCC 4.4: missing #include
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#564233: fim FTBFS on i386

[Stefano Zacchiroli]

On Thu, Jan 21, 2010 at 11:18:17PM +0100, Michele Martone wrote:
> I don't have the rights to upload the fixed package myself, but I 
> indeed have a sponsor (Moritz, in CC), now aware about the
> new package, which I uploaded on a space of mine:

OK, now it is clear.
In case Moritz is busy, feel free to ping me for sponsorship.

Cheers.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime



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

Bug#561347: flumotion: uses non-essential package in pre-rtupdate script

[Stefano Zacchiroli]

On Wed, Dec 16, 2009 at 02:00:16PM +0100, Jakub Wilk wrote:
> flumotion is using /usr/bin/python in the pre-rtupdate script. Since
> this script is run in the preinst of the python package, it is not
> guaranteed that the /usr/bin/python symlink exists or that it points
> to an existing file.
> 
> You should use only the essential packages in the pre-rtupdate
> script; otherwise it's likely that flumotion will break next update
> of the default version of Python.

Just for the sake of providing more information to this bug log: can you
please be more specific?

In fact /usr/share/python/runtime.d/flumotion.rtupdate does not use
directly python, but it does use invoke-rc.d on flumotion. In turn
/etc/init.d/flumotion does not invoke directly python, but will
eventually invoke /usr/sbin/flumotion which is a #!/usr/bin/python.

I believe that invocation path (which is of course buggy!) is what you
were referring to, confirmation would be appreciate, also to be sure I'm
not missing some other run path

Cheers.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime



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

Bug#564233: fim FTBFS on i386

[Michele Martone]

On 20100...@22:48, Stefano Zacchiroli wrote:
> On Thu, Jan 21, 2010 at 03:46:31AM +0100, Michele Martone wrote:
> > thank you for the patch.
> > I just applied this patch the fim repositories, and it will fix this
> > bug in a forthcoming fim upload.
> 
> Sorry to bother, but this bug is RC and is 3 week-old, can you explain
> what prevents you from uploading a fixed package right away?
> 
> Thanks for having integrated the patch.
> Cheers.

Hi,

I don't have the rights to upload the fixed package myself, but I 
indeed have a sponsor (Moritz, in CC), now aware about the
new package, which I uploaded on a space of mine:

 http://claudius.ce.uniroma2.it/~martone/tmp/fim_0.3-beta-prerelease-1.2.diff.gz
 
http://claudius.ce.uniroma2.it/~martone/tmp/fim_0.3-beta-prerelease-1.2_i386.changes
 http://claudius.ce.uniroma2.it/~martone/tmp/fim_0.3-beta-prerelease.orig.tar.gz
 http://claudius.ce.uniroma2.it/~martone/tmp/fim_0.3-beta-prerelease-1.2.dsc
 
http://claudius.ce.uniroma2.it/~martone/tmp/fim_0.3-beta-prerelease-1.2_i386.deb

Cheers,
 Michele



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

Processed: severity of 566195 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # alpha is no release arch
> severity 566195 important
Bug #566195 [gcc-4.4] gcc-4.4: Miscompilation at -O2 on alpha
Severity set to 'important' from 'grave'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Processed: flim: diff for NMU version 1:1.14.9-4.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 562846 + patch pending
Bug #562846 [flim] flim: metamail package no longer exists
Added tag(s) pending and patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#562846: flim: diff for NMU version 1:1.14.9-4.1

[Stefano Zacchiroli]

tags 562846 + patch pending
thanks

Dear maintainer,

I've prepared an NMU for flim (versioned as 1:1.14.9-4.1) and uploaded
it to DELAYED/2, according to devref §5.11.1.

The patch simply drops the Recommends on metamail, it does not remove
the base64-* variables as that should be handled upstream. Still,
metamail was a Recommends only, so the variables were superfluous
already at worst, not harmful (or there was another bug before already,
unrelated to this one).

Regards.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
diff -u flim-1.14.9/debian/control flim-1.14.9/debian/control
--- flim-1.14.9/debian/control
+++ flim-1.14.9/debian/control
@@ -10,7 +10,6 @@
 Package: flim
 Architecture: all
 Depends: emacs | emacsen, apel (>= 10.7)
-Recommends: metamail
 Suggests: semi, wl | wl-beta
 Conflicts: tm, semi-gnus (<< 1:6.10.13), flim1.13
 Replaces: flim1.13
diff -u flim-1.14.9/debian/changelog flim-1.14.9/debian/changelog
--- flim-1.14.9/debian/changelog
+++ flim-1.14.9/debian/changelog
@@ -1,3 +1,10 @@
+flim (1:1.14.9-4.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Drop Recommends on metamail, which is now gone (Closes: #562846)
+
+ -- Stefano Zacchiroli   Thu, 21 Jan 2010 22:53:30 +0100
+
 flim (1:1.14.9-4) unstable; urgency=low
 
   * debian/emacsen-install: Don't fail with xemacs21-nomule.

Bug#566192: initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30

[Louis Richard Pirlet]

Package: initramfs-tools
Version: 0.93.4
Severity: critical
Justification: breaks the whole system

I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the system over 
the new kernel. I still can boot it from the old 2.6.26 kernel.

My root disk is  on a mirror raid based on 2 SCSI disk. The boot process 
stopsand gives a message to the effect that the file system is unavailable.

I have an extended knowledge on hardware (I used to be a DEC/Compaq/HP harware 
support engineer on pdp11/VAX/alpha under VMS and Tru64). I have no indepth 
knowledge of the linux system.

I think there is a problem with the initramfs-tools because there is no 
mdadm.conf describing my md devices... In fact there is no mdadm directory 
under etc in the initrd.img-2.6.30.2.686 created by the upgrade.


-- Package-specific info:
-- /proc/cmdline
root=/dev/md0 ro

-- /proc/filesystems
ext3
ext2
reiserfs
xfs
jfs
msdos
vfat
ntfs
minix
hfs
hfsplus
qnx4
ufs

-- lsmod
Module  Size  Used by
nls_utf81760  0 
nls_cp437   5568  0 
ufs64804  0 
qnx47812  0 
hfsplus66212  0 
hfs37124  0 
minix  23972  0 
ntfs  185792  0 
vfat9184  0 
msdos   6944  0 
fat40896  2 vfat,msdos
jfs   148812  0 
nls_base6820  8 nls_utf8,nls_cp437,hfsplus,hfs,ntfs,vfat,fat,jfs
xfs   457976  0 
reiserfs  189888  0 
ext2   54504  0 
ppdev   6500  0 
lp  8164  0 
cpufreq_userspace   3172  0 
cpufreq_conservative 5960  0 
cpufreq_stats   3776  0 
cpufreq_ondemand6476  0 
cpufreq_powersave   1856  0 
freq_table  4224  2 cpufreq_stats,cpufreq_ondemand
ipv6  235364  14 
binfmt_misc 7528  1 
loop   12748  0 
mt20xx 10824  1 
tea5767 6020  0 
tda9887 9348  1 
tda829012164  0 
tuner  21960  0 
msp340025260  0 
bttv  148116  0 
snd_via82xx20664  1 
videodev   27520  3 tuner,msp3400,bttv
snd_ac97_codec 88484  1 snd_via82xx
v4l1_compat12260  1 videodev
firmware_class  6816  1 bttv
ac97_bus1728  1 snd_ac97_codec
ir_common  39620  1 bttv
snd_pcm62596  2 snd_via82xx,snd_ac97_codec
compat_ioctl32  1312  1 bttv
snd_page_alloc  7816  2 snd_via82xx,snd_pcm
i2c_algo_bit5188  1 bttv
snd_mpu401_uart 6368  1 snd_via82xx
v4l2_common10240  3 tuner,msp3400,bttv
videobuf_dma_sg11140  1 bttv
i2c_viapro  6836  0 
snd_seq_midi5728  0 
videobuf_core  16100  2 bttv,videobuf_dma_sg
via_ircc   15764  0 
snd_seq_midi_event  6432  1 snd_seq_midi
snd_rawmidi18528  2 snd_mpu401_uart,snd_seq_midi
btcx_risc   4264  1 bttv
snd_seq41456  2 snd_seq_midi,snd_seq_midi_event
snd_timer  17800  2 snd_pcm,snd_seq
snd_seq_device  6380  3 snd_seq_midi,snd_rawmidi,snd_seq
tveeprom   10980  1 bttv
irda   95512  1 via_ircc
parport_pc 22500  1 
parport30988  3 ppdev,lp,parport_pc
psmouse32336  0 
ns558   3712  0 
gameport   10700  3 snd_via82xx,ns558
snd45604  10 
snd_via82xx,snd_ac97_codec,snd_pcm,snd_mpu401_uart,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
serio_raw   4740  0 
soundcore   6368  1 snd
crc_ccitt   2080  1 irda
pcspkr  2432  0 
button  6096  0 
shpchp 25528  0 
i2c_core   19828  11 
mt20xx,tea5767,tda9887,tda8290,tuner,msp3400,bttv,i2c_algo_bit,v4l2_common,i2c_viapro,tveeprom
pci_hotplug23460  1 shpchp
via_agp 7744  1 
agpgart28776  1 via_agp
evdev   8000  7 
ext3  105512  2 
jbd39444  1 ext3
mbcache 7108  2 ext2,ext3
raid456   117264  1 
async_xor   3520  1 raid456
async_memcpy2304  1 raid456
async_tx6316  3 raid456,async_xor,async_memcpy
xor14696  2 raid456,async_xor
raid1  18016  2 
md_mod 67068  5 raid456,raid1
ide_cd_mod 27652  0 
cdrom  30176  1 ide_cd_mod
ide_disk   10496  0 
ata_generic 4676  0 
libata140416  1 ata_generic
dock8304  1 libata
sd_mod 22200  16 
via82cxxx   6948  0 [permane

Bug#564233: fim FTBFS on i386

[Stefano Zacchiroli]

On Thu, Jan 21, 2010 at 03:46:31AM +0100, Michele Martone wrote:
> thank you for the patch.
> I just applied this patch the fim repositories, and it will fix this
> bug in a forthcoming fim upload.

Sorry to bother, but this bug is RC and is 3 week-old, can you explain
what prevents you from uploading a fixed package right away?

Thanks for having integrated the patch.
Cheers.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime



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

Bug#566189: openoffice.org: Openoffice crashes on startup

[Ferry Toth]

Package: openoffice.org
Version: 1:3.1.1-14
Severity: grave
Justification: renders package unusable

After upgrading today from openoffice.org (1:3.1.1-8) to 1:3.1.1-14, Openoffice 
crashes immediately on startup.

Starting from the command line lets me pick the document type, then crashes as 
well with:

terminate called after throwing an instance of 
'com::sun::star::deployment::DeploymentException'

Deleting .openoffice.org did not help.

Ferry


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

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

Versions of packages openoffice.org depends on:
ii  liblucene2-java  2.9.1+ds1-2 Full-text search engine library fo
ii  openoffice.org-base  1:3.1.1-14  full-featured office productivity 
ii  openoffice.org-calc  1:3.1.1-14  full-featured office productivity 
ii  openoffice.org-core  1:3.1.1-14  full-featured office productivity 
ii  openoffice.org-draw  1:3.1.1-14  full-featured office productivity 
ii  openoffice.org-filter-mobile 1:3.1.1-14  full-featured office productivity 
ii  openoffice.org-impress   1:3.1.1-14  full-featured office productivity 
ii  openoffice.org-java-common   1:3.1.1-14  full-featured office productivity 
ii  openoffice.org-math  1:3.1.1-14  full-featured office productivity 
ii  openoffice.org-officebean1:3.1.1-14  full-featured office productivity 
ii  openoffice.org-report-builde 1:3.1.1-14  OpenOffice.org extension for build
ii  openoffice.org-writer1:3.1.1-14  full-featured office productivity 
ii  ttf-dejavu   2.30-2  Metapackage to pull in ttf-dejavu-

Versions of packages openoffice.org recommends:
ii  openoffice.org-filter- 1:3.1.1-14full-featured office productivity 
ii  ttf-liberation 1.05.2.20091019-4 Fonts with the same metrics as Tim
ii  ttf-mscorefonts-instal 3.0   Installer for Microsoft TrueType c

Versions of packages openoffice.org suggests:
ii  cups-bsd  1.4.2-4Common UNIX Printing System(tm) - 
ii  default-jre [java5-runtim 1.6-34 Standard Java or Java compatible R
ii  gstreamer0.10-ffmpeg  0.10.9-3   FFmpeg plugin for GStreamer
ii  gstreamer0.10-plugins-bad 0.10.17-1  GStreamer plugins from the "bad" s
ii  gstreamer0.10-plugins-bas 0.10.25-7  GStreamer plugins from the "base" 
ii  gstreamer0.10-plugins-goo 0.10.17-1  GStreamer plugins from the "good" 
ii  gstreamer0.10-plugins-ugl 0.10.13-2  GStreamer plugins from the "ugly" 
pn  hunspell-dictionary(no description available)
ii  iceweasel 3.5.6-1lightweight web browser based on M
ii  imagemagick   7:6.5.8.3-1image manipulation programs
ii  libgl1-mesa-glx [libgl1]  7.6.1-1A free implementation of the OpenG
ii  libpaper-utils1.1.23+nmu1library for handling paper charact
ii  libsane   1.0.20-13  API library for scanners
ii  libxrender1   1:0.9.5-1  X Rendering Extension client libra
ii  menu  2.1.42 generates programs menu for all me
ii  myspell-de-de [myspell-di 20091006-3 German dictionary for myspell
ii  myspell-en-us [myspell-di 1:3.2.0~beta-1 English_american dictionary for my
ii  myspell-fr-gut [myspell-d 1:1.0-27   The French dictionary for myspell 
ii  myspell-nl [myspell-dicti 1:1.10-4   Dutch dictionary for MySpell and H
pn  openclipart-openoffice.or  (no description available)
ii  openjdk-6-jre [java5-runt 6b17~pre3-1OpenJDK Java runtime, using Hotspo
ii  openoffice.org-gnome  1:3.1.1-14 full-featured office productivity 
ii  openoffice.org-help-en-us 1:3.1.1-14 full-featured office productivity 
ii  openoffice.org-help-nl [o 1:3.1.1-14 full-featured office productivity 
ii  openoffice.org-hyphenatio 1:3.2.0~beta-1 German hyphenation patterns for Op
ii  openoffice.org-hyphenatio 2.4-6  US English hyphenation patterns fo
ii  openoffice.org-kde1:3.1.1-14 full-featured office productivity 
ii  openoffice.org-l10n-nl [o 1:3.1.1-14 full-featured office productivity 
ii  openoffice.org-thesaurus- 1:3.2.0~beta-1 English Thesaurus for OpenOffice.o
ii  pstoedit  3.45-8 PostScript and PDF files to editab
ii  sun-java6-jre [java5-runt 6-16-1 Sun Java(TM) Runtime Environment (
ii  unixodbc  2.2.11-21  ODBC tools libraries

Versions of packages openoffice.org-core depends on:
ii  fontconfig 2.8.0-2   generic font configuration library
ii  libc6  2.10.2-2  GNU C Library: Shared libraries
ii  libcairo2  1.8.8-2   The Cairo 2D vector graphics libra
ii  libcurl3-gnutls7.19.7-1  Multi-protocol file

Bug#552856: marked as done (timps: FTBFS: stdio.h:397:66: error: macro "dprintf" passed 3 arguments, but takes just 2)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 21:40:16 +
with message-id 
and subject line Bug#552856: fixed in timps 0.25-4
has caused the Debian Bug report #552856,
regarding timps: FTBFS: stdio.h:397:66: error: macro "dprintf" passed 3 
arguments, but takes just 2
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.)


-- 
552856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: timps
Version: 0.25-3
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091028 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I. -I../../libmx/include 
> -I../../include -I/usr/local/include/libnbio -I/usr/include/libnbio
> -fno-strict-aliasing -Wall -g  -c net.c
> In file included from net.c:42:
> /usr/include/stdio.h:397:66: error: macro "dprintf" passed 3 arguments, but 
> takes just 2
> make[3]: *** [net.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/10/28/timps_0.25-3_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: timps
Source-Version: 0.25-4

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

timps_0.25-4.diff.gz
  to main/t/timps/timps_0.25-4.diff.gz
timps_0.25-4.dsc
  to main/t/timps/timps_0.25-4.dsc
timps_0.25-4_amd64.deb
  to main/t/timps/timps_0.25-4_amd64.deb



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

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

Debian distribution maintenance software
pp.
Eric Warmenhoven  (supplier of updated timps 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: Thu, 21 Jan 2010 11:37:15 -0800
Source: timps
Binary: timps
Architecture: source amd64
Version: 0.25-4
Distribution: unstable
Urgency: low
Maintainer: Eric Warmenhoven 
Changed-By: Eric Warmenhoven 
Description: 
 timps  - Transparent Instant Messaging Proxy Server
Closes: 536260 552856 553865
Changes: 
 timps (0.25-4) unstable; urgency=low
 .
   * Build fix: 'dprintf' macro also defined by stdio as a function.
 Closes: #552856.
   * Change Build-Depends from 'libreadline5-dev | libreadline-dev' to just
 'libreadline-dev'. Closes: #553865.
   * Update config.guess, config.sub from autotools-dev. Closes: #536260.
Checksums-Sha1: 
 f2e42fbdbbe6c21bcff06bdaaf4c45d0dea148e7 994 timps_0.25-4.dsc
 47d9bdd1ef3cbe9d97e21c7ce7da98c71d2724fa 19889 timps_0.25-4.diff.gz
 5cec873eec031c09d5561b13a13f1e0cd99aab2b 68656 timps_0.25-4_amd64.deb
Checksums-Sha256: 
 d8a1ea7691fa4ef6285b4d4eb2c8e293a877a989ddd67d88a990ac5a2f9bce35 994 
timps_0.25-4.dsc
 6ffd68dbddf7b897d57e050c4fd7f0bf778a5398d62bc2b6f593a3f70e8e8f85 19889 
timps_0.25-4.diff.gz
 c6b24aeaa126fc3db7d387a6c52844a74e8a89693fd8982c74081a2d79a02c88 68656 
timps_0.25-4_amd64.deb
Files: 
 68a1ce98d6deca4ab45d4ee9a111586b 994 net extra timps_0.25-4.dsc
 b00b59865e85688b9269ffb526d735d9 19889 net extra timps_0.25-4.diff.gz
 d2fe6407185217283ddd88fcacb65d73 68656 net extra timps_0.25-4_amd64.deb

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

iEYEARECAAYFAktYsmUACgkQBLcxcFStIbUQCgCdFU51qt99VP0Lk4NXRuQtCXom
2q4AnjDKtz2whE8qUGoUtMLr3//m7aLb
=oYzl
-END PGP SIGNATURE-


--- End Message ---

Bug#566097: marked as done (quassel-data-kde4 and quassel-data: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 21:39:28 +
with message-id 
and subject line Bug#566097: fixed in quassel 0.5.1-3
has caused the Debian Bug report #566097,
regarding quassel-data-kde4 and quassel-data: 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.)


-- 
566097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: quassel-data,quassel-data-kde4
Version: quassel-data/0.5.1-2
Version: quassel-data-kde4/0.5.1-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2010-01-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!
  quassel-data quassel-data-kde4
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407148
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407760
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407149
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package quassel-data.
(Reading database ... 10458 files and directories currently installed.)
Unpacking quassel-data (from .../quassel-data_0.5.1-2_all.deb) ...
Selecting previously deselected package quassel-data-kde4.
Unpacking quassel-data-kde4 (from .../quassel-data-kde4_0.5.1-2_all.deb) ...
dpkg: error processing 
/var/cache/apt/archives/quassel-data-kde4_0.5.1-2_all.deb (--unpack):
 trying to overwrite '/usr/share/icons/hicolor/48x48/apps/quassel.png', which 
is also in package quassel-data 0:0.5.1-2
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/quassel-data-kde4_0.5.1-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

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/share/icons/hicolor/48x48/apps/quassel.png
  /usr/share/pixmaps/quassel.png

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.

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


--- End Message ---
--- Begin Message ---
Source: quassel
Source-Version: 0.5.1-3

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

quassel-client-kde4_0.5.1-3_i386.deb
  to main/q/quassel/quassel-client-kde4_0.5.1-3_i386.deb
quassel-client_0.5.1-3_i386.deb
  to main/q/quassel/quassel-client_0.5.1-3_i386.deb
quassel-core_0.5.1-3_i386.deb
  to main/q/quassel/quassel-core_0.5.1-3_i386.deb
quassel-data-kde4_0.5.1-3_all.deb
  to main/q/quassel/quassel-data-kde4_0.5.1-3_all.deb
quassel-data_0.5.1-3_all.deb
  to main/q/quassel/quassel-data_0.5.1-3_all.deb
quassel-kde4_0.5.1-3_i386.deb
  to main/q/quassel/quassel-kde4_0.5.1-3_i386.deb
quassel_0.5.1-3.diff.gz
  to main/q/quassel/quassel_0.5.1-3.diff.gz
quassel_0.5.1-3.dsc
  to main/q/quassel/quassel_0.5.1-3.dsc
quassel_0.5.1-3_i386.deb
  to main/q/quassel/quassel_0.5.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 566...@bugs.debian.org,
and the maintainer will reope

Processed: Re: Bug#550092: dia2code: Segmentation Fault into 64 bits systems

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 550092 + unreproducible
Bug #550092 [dia2code] dia2code: Segmentation Fault into 64 bits systems
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562946: fails to install -- update

[Stefano Zacchiroli]

On Mon, Jan 04, 2010 at 10:21:00PM +0530, Deepak Tripathi wrote:
> I have installed in my system, Yes this package need to be build-dep on
> libtre4 . After installing libtre4, i am able to install package
> successfully.

Again, the build-dep or dep on libtre4 has nothing to do with the bug
reported by Holger. The bug is above a (still to be explained) failure
in the pre-installation script of crm114. That, as far as we can tell
from the information collected thus far, has nothing to with libtre4.

I'm unable to reproduce the bug (yet), but looking at the preinst it is
likely to be the "exit 1" explicitly mentioned in the debconf config
script.

Cheers.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime



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

Bug#566069: marked as done (src:gdal: FTBFS: several failed mv calls)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 21:36:19 +
with message-id 
and subject line Bug#566069: fixed in gdal 1.6.3-3
has caused the Debian Bug report #566069,
regarding src:gdal: FTBFS: several failed mv calls
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.)


-- 
566069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gdal
Version: 1.6.3-2
Severity: serious
Justification: FTBFS

Hi,

your package FTBFS on a bunch of buildds (kfreebsd-*, powerpc, s390, and
sparc at least):
| make[1]: Leaving directory 
`/build/buildd-gdal_1.6.3-2-kfreebsd-amd64-AqNU_r/gdal-1.6.3'
| # a temporary workaround for doxygen problem #564243 
| cd man/man1 && \
|   for i in `find . -name "*_*"`; do basename=`basename 
$i`; mv $basename `echo $basename|sed -e 's/__/_/'`; done
| mv: `gdalinfo_8c.1' and `gdalinfo_8c.1' are the same file
| mv: `gdalallregister_8cpp.1' and `gdalallregister_8cpp.1' are the same file
| mv: `jdemdataset_8cpp.1' and `jdemdataset_8cpp.1' are the same file
| mv: `_sPolyExtended.1' and `_sPolyExtended.1' are the same file
| mv: `GeoTransform_Transformer.1' and `GeoTransform_Transformer.1' are the 
same file
| make: *** [build-stamp] Error 1

Full build logs:
  https://buildd.debian.org/status/package.php?p=gdal&suite=unstable

I guess you may want to store the result of `echo|sed` in a variable and
check for equality with $basename before trying to rename?

Mraw,
KiBi.


--- End Message ---
--- Begin Message ---
Source: gdal
Source-Version: 1.6.3-3

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

gdal-bin_1.6.3-3_i386.deb
  to main/g/gdal/gdal-bin_1.6.3-3_i386.deb
gdal_1.6.3-3.diff.gz
  to main/g/gdal/gdal_1.6.3-3.diff.gz
gdal_1.6.3-3.dsc
  to main/g/gdal/gdal_1.6.3-3.dsc
libgdal-doc_1.6.3-3_all.deb
  to main/g/gdal/libgdal-doc_1.6.3-3_all.deb
libgdal-perl_1.6.3-3_i386.deb
  to main/g/gdal/libgdal-perl_1.6.3-3_i386.deb
libgdal-ruby1.8_1.6.3-3_i386.deb
  to main/g/gdal/libgdal-ruby1.8_1.6.3-3_i386.deb
libgdal-ruby_1.6.3-3_i386.deb
  to main/g/gdal/libgdal-ruby_1.6.3-3_i386.deb
libgdal1-1.6.0_1.6.3-3_i386.deb
  to main/g/gdal/libgdal1-1.6.0_1.6.3-3_i386.deb
libgdal1-dev_1.6.3-3_i386.deb
  to main/g/gdal/libgdal1-dev_1.6.3-3_i386.deb
python-gdal_1.6.3-3_i386.deb
  to main/g/gdal/python-gdal_1.6.3-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 566...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated gdal 
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: Thu, 21 Jan 2010 18:21:18 +0100
Source: gdal
Binary: libgdal1-1.6.0 libgdal1-dev libgdal-doc gdal-bin python-gdal 
libgdal-perl libgdal-ruby1.8 libgdal-ruby
Architecture: source i386 all
Version: 1.6.3-3
Distribution: unstable
Urgency: low
Maintainer: Debian GIS Project 
Changed-By: Francesco Paolo Lovergine 
Description: 
 gdal-bin   - Geospatial Data Abstraction Library - Utility programs
 libgdal-doc - Documentation for the Geospatial Data Abstraction Library
 libgdal-perl - Perl bindings to the Geospatial Data Abstraction Library
 libgdal-ruby - Ruby bindings to the Geospatial Data Abstraction Library
 libgdal-ruby1.8 - Ruby 1.8 bindings to the Geospatial Data Abstraction Library
 libgdal1-1.6.0 - Geospatial Data Abstraction Library
 libgdal1-dev - Geospatial Data Abstraction Library - Development files
 python-gdal - Python bindings to the Geospatial Data Abstraction Library
Closes: 566069
Changes: 
 gdal (1.6.3-3) unstable; urgency=low
 .
   * Fixed previous dirty workaroud debian/rules for working Doxygen versions.
 (closes: #566069)
Checksums-Sha1: 
 b08d54486d2945c3cc3b79fec41a4642a858e022 1775 gdal_1.6.3-3.dsc
 18505671c056bc9b21dd73ee9e7b88adc3b6356a 87652 gdal_1.6.3-3.diff.gz
 ce3073065231ba920dc291b42d266650ff8518b6 2918124 
libgdal1-1.6.0_1.6.3-3_i386.deb
 2cb44db1bef905883088de970d4218856e4c6acf 3621266 libgdal1-dev_1.6.3-3_i386.deb
 23e673d15e71d11899a10204a6139dd5f012c5bc 193280 gdal-bin_1.6.3-3_i386.deb
 ce6d7d2a2f864a2baea6c51cd7860d27e53137c2 333620 python-gdal_1.6.3-3_

Bug#550092: dia2code: Segmentation Fault into 64 bits systems

[Stefano Zacchiroli]

tags 550092 + unreproducible
thanks

On Sat, Jan 16, 2010 at 06:29:07PM +0200, George Danchev wrote:
> Could you please give some more information how to reproduce it:
> (since I'm unable to reproduce on amd64)

Same here, hence tagging as unreproducible.

Cheers.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime



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

Bug#542269: #542269 -- newlib-mingw32 and mingw32-runtime: error when trying to install together

[Ralf Treinen]

I filed bug #542269 with severity=serious 3 months ago, but I cannot
find any trace of progress in the BTS. Is anyone looking at this bug?

-Ralf.



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

Bug#553887: directvnc: should this package be removed?

[Loris Boillet]

Upstream is alive again! A new version of directvnc has been released (0.7.6), 
and 
I uploaded a package of it to mentors.debian.net. It closes 5 bugs and a bunch 
of 
lintian warnings; it's now waiting for a sponsor to be uploaded to debian. I 
guess 
this should allow this bug to be closed (when/if the package is uploaded)?

Cheers,

Loris



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

Processed: Re: Bug#502889: docbook support unmaintained upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 502889 python-moin: docbook plugin broken and unmaintained upstream
Bug #502889 [moin] python-xml removal: please drop/replace (build) 
dependencies/recommends
Changed Bug title to 'python-moin: docbook plugin broken and unmaintained 
upstream' from 'python-xml removal: please drop/replace (build) 
dependencies/recommends'
> severity 502889 minor
Bug #502889 [moin] python-moin: docbook plugin broken and unmaintained upstream
Severity set to 'minor' from 'serious'

> tags 502889 wontfix
Bug #502889 [moin] python-moin: docbook plugin broken and unmaintained upstream
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#502889: docbook support unmaintained upstream

[Jonas Smedegaard]

retitle 502889 python-moin: docbook plugin broken and unmaintained upstream
severity 502889 minor
tags 502889 wontfix
thanks


Hi all,

On Fri, Nov 20, 2009 at 11:07:59AM +0100, Thomas Waldmann wrote:

Moin,


:-)

There would be three alternatives: 1. drop docbook feature.  2. 
embed a copy of python-xml in moin package.  3. keep using the 
current python-xml which has almost no bugs.


1 -> will automatically happen at moin 2.0 if noone ports docbook stuff
from 1.9 to 2.0 (and maintains it in 2.0).

2 -> likely possible, we have quite some stuff in MoinMoin/support/
anyway.


We should *not* stuff code into python-moin that is being abandoned by 
its Debian package maintainers.


(and btw I feel that your choice of naming unsupported code as "support" 
is misleading - often such dir is named "contrib", i.e. contributed from 
others without being endorsed, maintained or supported by you).


A comparable area for Debian is our "non-free" packages, which we offer 
without guarantees or security promises.  But even then it makes little 
sense for me to ship something that is considered broken by its latest 
contributor.




3 -> least work


Since Stefano calls the docbook plugin broken and Frank Li writes that 
his patches still has major bugs, keeping python-xml package alive (or 
stuffing it into moin package) won't solve the real issue.



If the issue stay as it is, my favorite scenario would be (1) (drop 
docbook support).


For 1.9, that would be rather unexpected (and for some moin docbook 
users quite disruptive).


I fail to understand that: Is docbook working properly with 1.9?


For Debian, the python-moin package now only suggests python-xml and 
Frank Lin have provided a patch so that docbook plugin is only tried if 
python-xml exist.  This means users are free to try grab an old or 
unofficial python-xml and keep docbook alive, and on the other hand 
python-moin do not stall the process of killing official Debian support 
for python-xml.


I have thus lowered severity of this bug, and (due to none of us 
discussing here offering to step up as _maintainer_ of the docbook 
plugin) tagged it as wontfix.


For the record I too would be happy to see someone taking the challenge 
of adopting the docbook plugin and pouring love into it as new upstream 
author of it.



Kind regards,

 - Jonas

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

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: Digital signature

Processed: Re: git-core FTBFS on ia64: t1001-read-tree-m-2way.sh test fails

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 563882 +patch
Bug #563882 [git-core] git-core FTBFS on ia64: t1001-read-tree-m-2way.sh test 
fails
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#563882: git-core FTBFS on ia64: t1001-read-tree-m-2way.sh test fails

[Anders Kaseorg]

tags 563882 +patch
thanks

On Sat, 9 Jan 2010, Jonathan Nieder wrote:
> To test this hypothesis, it would be nice to use a copy of git built 
> with DEB_BUILD_OPTIONS=nocheck to compare
> […]

Thanks for looking at this, Jonathan.

Now that Git 1.6.6.1 is out, I propose we build git-core 1.6.6.1-1 with 
the patch I posted above , which lets 
the two tests in question expect to fail on ia64 only.  Then ia64 users 
can have a package to test this with more easily, and non-ia64 users don’t 
have to wait for us to find an ia64 user and convince them to care (which 
we’ve all been unable to do for several weeks).

As far as I can tell, this test failure was triggered by some kind of 
change on the buildd and is not a real regression from the version in 
testing, given that it was observed with an earlier version in Ubuntu.  
So even for ia64 users, if there are any, this should not cause any more 
problems than already exist.

The only other option I see is to disable the ia64 architecture entirely 
for git-core, given that we’re effectively unable to support it.  But I 
think patching the test suite is less unfortunate.

Anders



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

Bug#566022: marked as done (mysql-server: mysqld fails to start)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 20:25:32 +0100
with message-id <4b58aa2c.9020...@adv-solutions.net>
and subject line [Fwd: Bug#566022: mysql-server: mysqld fails to start]
has caused the Debian Bug report #566022,
regarding mysql-server: mysqld fails to start
to be marked as done.

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

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


-- 
566022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-server
Version: 5.1.41
Severity: grave
Justification: renders package unusable



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

Kernel: Linux 2.6.31.4-xen (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

When starting mysql through "/etc/init.d/mysql start" gives the foloxxing 
output :

/etc/init.d/mysql start
/usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
Starting MySQL database server: mysqld/usr/sbin/mysqld: symbol lookup error: 
/usr/sbin/mysqld: undefined symbol: sort_order_hebrew�general_ci
/usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 ./usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: 
sort_order_hebrew�general_ci
 failed!

and does not start.


--- End Message ---
--- Begin Message ---
User acknowledged resolution after upgrading some other components.

 Original Message 
Subject:Bug#566022: mysql-server: mysqld fails to start
Resent-Date:Thu, 21 Jan 2010 11:48:05 +, Thu, 21 Jan 2010 11:48:07
+
Resent-From:Moi même 
Resent-To:  debian-bugs-d...@lists.debian.org
Resent-CC:  Debian MySQL Maintainers

Date:   Thu, 21 Jan 2010 12:43:31 +0100
From:   Moi même 
Reply-To:   jp.po...@izzop.net, 566...@bugs.debian.org
To: José Luis Tallón 
CC: stor...@club-internet.fr , 566...@bugs.debian.org
References: <20100120181159.8413.81804.report...@k2000.jpp.fr>
<4b576ff1.4010...@adv-solutions.net>



Hello,

objdump -T /usr/sbin/mysqld  | grep sort_order_hebrew
00b637c0 gDO .data  0100  Base
sort_order_hebrew_general_ci

But after the last nightly update the mysql server starts again.

Thanks for you quick answer.

Regards

JP Pozzi


Le mercredi 20 janvier 2010 à 22:04 +0100, José Luis Tallón a écrit :
> stor...@club-internet.fr wrote:
> > Package: mysql-server
> > Version: 5.1.41
> > Severity: grave
> > Justification: renders package unusable
> >   
> Please provide the output from the command below:
>  $ objdump -T /usr/sbin/mysqld  | grep sort_order_hebrew
> 
> 
> It might as well be some kind of problem during upgrade ... I assume
> this happened after upgrading and not on a new install, right?
> 
> Else, it seems the build somehow got corrupted or maybe gcc is producing
> a damaged executable [cfr #554207]

Bug#552915: python-clientform: uses /usr/share/python/python.mk without sufficient build-dep

[Jakub Wilk]

clone 552915 -1
severity -1 important
tags -1 =
found -1 0.2.10-2
found -1 0.2.10-2.1
retitle -1 python-clientform: uses /usr/share/python/python.mk without 
sufficient build-dep
thanks

* Olausson, Bjoern , 2010-01-21, 01:24:

At first I had to remove /usr/share/python/python.mk:

debian/rules:6: /usr/share/python/python.mk: No such file or directory


That line was added there for a reason, so removing it was not a correct 
solution to your problem.


--
Jakub Wilk


signature.asc
Description: Digital signature

Bug#563402: RFH: Bug#563402: ia32-libs broken on ia64

[Goswin von Brederlow]

dann frazier  writes:

> On Thu, Jan 21, 2010 at 06:30:14PM +0100, Goswin von Brederlow wrote:
>> Hi,
>> 
>> lacking any access to ia64 I'm wondering if any porter can help with
>> Bug#563402. Is there actualy something wrong in ia32-libs (and then
>> what) or is merulo[1] just not capable of running 32bit x86 binaries?
>
> It should have x86 support in hardware - but, something is certainly
> wrong.
>
> da...@krebs:~$ file /tmp/hello
> /tmp/hello: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped
> da...@krebs:~$ dpkg -l ia32-libs
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name  Version
> Description
> +++-=-=-==
> ii  ia32-libs 20090808
> ia32 shared libraries for use on amd64 and ia64 systems
> da...@krebs:~$ /tmp/hello
> -bash: /tmp/hello: No such file or directory
> da...@krebs:~$ LD_LIBRARY_PATH=/lib32 /lib32/ld-2.9.so /tmp/hello
> Hello, world!
>
> -- 
> dann frazier

Oh, I see what the problem is (after unpacking the deb instead of
looking just at the file list):

lrwxrwxrwx 1 mrvn mrvn 18 Jan 21 20:20 lib/ld-linux.so.2 -> /lib32/ld-2.3.2.so

-rwxr-xr-x 1 mrvn mrvn 115K Jul 27 21:09 lib32/ld-2.9.so*
lrwxrwxrwx 1 mrvn mrvn9 Jan 21 20:20 lib32/ld-linux.so.2 -> ld-2.9.so*

Been a long time since that link was updated. That should be

lrwxrwxrwx 1 root root 20 Oct 29 09:53 lib/ld-linux.so.2 -> 
/lib32/ld-linux.so.2*

like the libc6-i386 has on amd64 so it works for in libc6 version.

MfG
Goswin



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

Processed: python-clientform: uses /usr/share/python/python.mk without sufficient build-dep

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 552915 -1
Bug#552915: python-clientform: FTBFS: mv: cannot stat 
`debian/python-clientform//usr/lib/python2.4/site-packages/ClientForm-0.2.10-py2.4.egg-info':
 No such file or directory
Bug 552915 cloned as bug 566177.

> severity -1 important
Bug #566177 {Done: Jakub Wilk } [src:python-clientform] 
python-clientform: FTBFS: mv: cannot stat 
`debian/python-clientform//usr/lib/python2.4/site-packages/ClientForm-0.2.10-py2.4.egg-info':
 No such file or directory
Severity set to 'important' from 'serious'

> tags -1 =
Bug #566177 {Done: Jakub Wilk } [src:python-clientform] 
python-clientform: FTBFS: mv: cannot stat 
`debian/python-clientform//usr/lib/python2.4/site-packages/ClientForm-0.2.10-py2.4.egg-info':
 No such file or directory
Removed tag(s) patch.
> found -1 0.2.10-2
Bug #566177 {Done: Jakub Wilk } [src:python-clientform] 
python-clientform: FTBFS: mv: cannot stat 
`debian/python-clientform//usr/lib/python2.4/site-packages/ClientForm-0.2.10-py2.4.egg-info':
 No such file or directory
Bug No longer marked as fixed in versions python-clientform/0.2.10-2.1 and 
reopened.
> found -1 0.2.10-2.1
Bug #566177 [src:python-clientform] python-clientform: FTBFS: mv: cannot stat 
`debian/python-clientform//usr/lib/python2.4/site-packages/ClientForm-0.2.10-py2.4.egg-info':
 No such file or directory
Bug Marked as found in versions python-clientform/0.2.10-2.1.
> retitle -1 python-clientform: uses /usr/share/python/python.mk without 
> sufficient build-dep
Bug #566177 [src:python-clientform] python-clientform: FTBFS: mv: cannot stat 
`debian/python-clientform//usr/lib/python2.4/site-packages/ClientForm-0.2.10-py2.4.egg-info':
 No such file or directory
Changed Bug title to 'python-clientform: uses /usr/share/python/python.mk 
without sufficient build-dep' from 'python-clientform: FTBFS: mv: cannot stat 
`debian/python-clientform//usr/lib/python2.4/site-packages/ClientForm-0.2.10-py2.4.egg-info':
 No such file or directory'
> thanks
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#566161: fsprotect: uninstallable in sid, depends on kernel component

[Julien Cristau]

On Thu, Jan 21, 2010 at 20:18:18 +0200, Stefanos Harhalakis wrote:

> Hello,
> 
> On Thursday 21 of January 2010, Julien Cristau wrote:
> > fsprotect depends on aufs-modules which is not in sid (and soon not in
> > testing).  Besides, to quote one of the kernel maintainers, "User-space
> > packages should never depend on kernel components, because the kernel
> > might be provided from outside the system (e.g. for a chroot'd
> > environment)".  Please remove this dependency (fsprotect is being
> > removed from testing temporarily because of this, to let the 2.6.32
> > kernel into squeeze).
> 
> So you suggest that fsprotect should perform run-time detection of aufs 
> instead?
> 
Well, it should do that in any case, since having aufs-modules installed
has never guaranteed that the running kernel has aufs.

Cheers,
Julien



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

Bug#563402: RFH: Bug#563402: ia32-libs broken on ia64

[dann frazier]

On Thu, Jan 21, 2010 at 06:30:14PM +0100, Goswin von Brederlow wrote:
> Hi,
> 
> lacking any access to ia64 I'm wondering if any porter can help with
> Bug#563402. Is there actualy something wrong in ia32-libs (and then
> what) or is merulo[1] just not capable of running 32bit x86 binaries?

It should have x86 support in hardware - but, something is certainly
wrong.

da...@krebs:~$ file /tmp/hello
/tmp/hello: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped
da...@krebs:~$ dpkg -l ia32-libs
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version
Description
+++-=-=-==
ii  ia32-libs 20090808
ia32 shared libraries for use on amd64 and ia64 systems
da...@krebs:~$ /tmp/hello
-bash: /tmp/hello: No such file or directory
da...@krebs:~$ LD_LIBRARY_PATH=/lib32 /lib32/ld-2.9.so /tmp/hello
Hello, world!

-- 
dann frazier




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

Bug#542842: Code similar to hlint

[Marco Túlio Gontijo e Silva]

Hi.

Wouldn't a line like:

DEB_SETUP_GHC6_CONFIGURE_ARGS := $(shell test -e 
/usr/lib/ghc-$(GHC6_VERSION)/libHSrts_thr.a && echo -f-threaded)

in rules would fix it?

Greetings.
-- 
marcot
http://marcot.iaaeee.org/





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

Bug#566161: fsprotect: uninstallable in sid, depends on kernel component

[Stefanos Harhalakis]

Hello,

On Thursday 21 of January 2010, Julien Cristau wrote:
> fsprotect depends on aufs-modules which is not in sid (and soon not in
> testing).  Besides, to quote one of the kernel maintainers, "User-space
> packages should never depend on kernel components, because the kernel
> might be provided from outside the system (e.g. for a chroot'd
> environment)".  Please remove this dependency (fsprotect is being
> removed from testing temporarily because of this, to let the 2.6.32
> kernel into squeeze).

So you suggest that fsprotect should perform run-time detection of aufs 
instead?




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

Bug#559646: [Pkg-haskell-maintainers] Bug#559646: closed by Marco Túlio Gontijo e Silva (No buildd errors found)

[Marco Túlio Gontijo e Silva]

Hi KiBi.

Qui, 2010-01-21 às 18:38 +0100, Cyril Brulebois escreveu: 
> Debian Bug Tracking System  (21/01/2010):
> > There seems to be no problem with building this package at:
> > 
> > https://buildd.debian.org/status/package.php?suite=unstable&p=haskell-configfile
> 
> There were issues, see the “all N” links, I guess the issue was in a
> build-depended-on package, which got fixed in the meanwhile, and your
> package then got given back (probably through -release@).

Sure, I didn't mean that there was never a problem.

Greetings.
(...)
-- 
marcot
http://marcot.iaaeee.org/




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

Bug#565129: marked as done (krb5-multidev and heimdal-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 12:48:11 -0500 (EST)
with message-id <20100121174811.3d32e4...@carter-zimmerman.suchdamage.org>
and subject line Oops not marked fixed
has caused the Debian Bug report #565129,
regarding krb5-multidev and heimdal-dev: 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.)


-- 
565129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: heimdal-dev,krb5-multidev
Version: heimdal-dev/1.3.1.rc2.dfsg.1-1
Version: krb5-multidev/1.8+dfsg~alpha1-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2010-01-13
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!
  libdb4.8 libgssrpc4 libkdb5-4 libkadm5srv7 libsqlite3-0 libc-dev-bin
  linux-libc-dev libc6-dev comerr-dev krb5-multidev libroken18-heimdal
  libasn1-8-heimdal libwind0-heimdal libhx509-5-heimdal libkrb5-26-heimdal
  libheimntlm0-heimdal libgssapi2-heimdal libhdb9-heimdal
  libkadm5clnt7-heimdal libkadm5srv8-heimdal libkafs0-heimdal heimdal-multidev
  heimdal-dev
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5406847
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407760
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5406895
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package libdb4.8.
(Reading database ... 10447 files and directories currently installed.)
Unpacking libdb4.8 (from .../libdb4.8_4.8.26-1_amd64.deb) ...
Selecting previously deselected package libgssrpc4.
Unpacking libgssrpc4 (from .../libgssrpc4_1.8+dfsg~alpha1-2_amd64.deb) ...
Selecting previously deselected package libkdb5-4.
Unpacking libkdb5-4 (from .../libkdb5-4_1.8+dfsg~alpha1-2_amd64.deb) ...
Selecting previously deselected package libkadm5srv7.
Unpacking libkadm5srv7 (from .../libkadm5srv7_1.8+dfsg~alpha1-2_amd64.deb) ...
Selecting previously deselected package libsqlite3-0.
Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.21-2_amd64.deb) ...
Selecting previously deselected package libc-dev-bin.
Unpacking libc-dev-bin (from .../libc-dev-bin_2.10.2-5_amd64.deb) ...
Selecting previously deselected package linux-libc-dev.
Unpacking linux-libc-dev (from .../linux-libc-dev_2.6.32-5_amd64.deb) ...
Selecting previously deselected package libc6-dev.
Unpacking libc6-dev (from .../libc6-dev_2.10.2-5_amd64.deb) ...
Selecting previously deselected package comerr-dev.
Unpacking comerr-dev (from .../comerr-dev_2.1-1.41.9-1_amd64.deb) ...
Selecting previously deselected package krb5-multidev.
Unpacking krb5-multidev (from .../krb5-multidev_1.8+dfsg~alpha1-2_amd64.deb) ...
Selecting previously deselected package libroken18-heimdal.
Unpacking libroken18-heimdal (from 
.../libroken18-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libasn1-8-heimdal.
Unpacking libasn1-8-heimdal (from 
.../libasn1-8-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libwind0-heimdal.
Unpacking libwind0-heimdal (from 
.../libwind0-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libhx509-5-heimdal.
Unpacking libhx509-5-heimdal (from 
.../libhx509-5-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libkrb5-26-heimdal.
Unpacking libkrb5-26-heimdal (from 
.../libkrb5-26-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libheimntlm0-heimdal.
Unpacking libheimntlm0-heimdal (from 
.../libheimntlm0-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libgssapi2-heimdal.
Unpacking libgssapi2-heimdal (from 
.../libgssapi2-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libhdb9-heimdal.
Unpacking libhdb9-heimdal (from 
.../libhdb9-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libkadm5clnt7-heimdal.
Unpacking libkadm5clnt7-heimdal (from 
.../libkadm5clnt7-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libkadm5s

Bug#564566: marked as done (libkadm5clnt7: SONAME conflict with Heimdal)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 12:50:37 -0500 (EST)
with message-id <20100121175037.cd6834...@carter-zimmerman.suchdamage.org>
and subject line updating fixed
has caused the Debian Bug report #564566,
regarding libkadm5clnt7: SONAME conflict with Heimdal
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.)


-- 
564566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkadm5clnt7
Version: 1.8+dfsg~alpha1-1
Severity: important

Hi,

Unpacking libkadm5clnt7 (from .../libkadm5clnt7_1.8+dfsg~alpha1-1_amd64.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libkadm5clnt7_1.8+dfsg~alpha1-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/libkadm5clnt.so.7', which is also in package 
libkadm5clnt7-heimdal 0:1.3.1.rc2.dfsg.1-1

Gabor

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

Kernel: Linux 2.6.32.3 (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/dash

Versions of packages libkadm5clnt7 depends on:
ii  libc6 2.10.2-5   Embedded GNU C Library: Shared lib
ii  libcomerr21.41.9-1   common error description library
pn  libgssapi-krb5-2   (no description available)
pn  libgssrpc4 (no description available)
pn  libk5crypto3   (no description available)
pn  libkrb5-3  (no description available)
pn  libkrb5support0(no description available)

libkadm5clnt7 recommends no packages.

Versions of packages libkadm5clnt7 suggests:
pn  krb5-doc   (no description available)
pn  krb5-user  (no description available)


--- End Message ---
--- Begin Message ---
source: krb5
source-version: 1.8+dfsg~alpha1-3

This was marked in the changelog; not sure why it was not closed.

--- End Message ---

Bug#564666: marked as done (krb5-multidev and heimdal-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 12:50:37 -0500 (EST)
with message-id <20100121175037.cd6834...@carter-zimmerman.suchdamage.org>
and subject line updating fixed
has caused the Debian Bug report #564566,
regarding krb5-multidev and heimdal-dev: 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.)


-- 
564566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: heimdal-dev,krb5-multidev
Version: heimdal-dev/1.3.1.rc2.dfsg.1-1
Version: krb5-multidev/1.8+dfsg~alpha1-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2010-01-11
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!
  libdb4.8 libgssrpc4 libkdb5-4 libkadm5srv7 libsqlite3-0 libc-dev-bin
  linux-libc-dev libc6-dev comerr-dev krb5-multidev libroken18-heimdal
  libasn1-8-heimdal libwind0-heimdal libhx509-5-heimdal libkrb5-26-heimdal
  libheimntlm0-heimdal libgssapi2-heimdal libhdb9-heimdal
  libkadm5clnt7-heimdal libkadm5srv8-heimdal libkafs0-heimdal heimdal-multidev
  heimdal-dev
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5408409
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407760
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407203
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package libdb4.8.
(Reading database ... 10445 files and directories currently installed.)
Unpacking libdb4.8 (from .../libdb4.8_4.8.26-1_amd64.deb) ...
Selecting previously deselected package libgssrpc4.
Unpacking libgssrpc4 (from .../libgssrpc4_1.8+dfsg~alpha1-1_amd64.deb) ...
Selecting previously deselected package libkdb5-4.
Unpacking libkdb5-4 (from .../libkdb5-4_1.8+dfsg~alpha1-1_amd64.deb) ...
Selecting previously deselected package libkadm5srv7.
Unpacking libkadm5srv7 (from .../libkadm5srv7_1.8+dfsg~alpha1-1_amd64.deb) ...
Selecting previously deselected package libsqlite3-0.
Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.21-2_amd64.deb) ...
Selecting previously deselected package libc-dev-bin.
Unpacking libc-dev-bin (from .../libc-dev-bin_2.10.2-5_amd64.deb) ...
Selecting previously deselected package linux-libc-dev.
Unpacking linux-libc-dev (from .../linux-libc-dev_2.6.32-5_amd64.deb) ...
Selecting previously deselected package libc6-dev.
Unpacking libc6-dev (from .../libc6-dev_2.10.2-5_amd64.deb) ...
Selecting previously deselected package comerr-dev.
Unpacking comerr-dev (from .../comerr-dev_2.1-1.41.9-1_amd64.deb) ...
Selecting previously deselected package krb5-multidev.
Unpacking krb5-multidev (from .../krb5-multidev_1.8+dfsg~alpha1-1_amd64.deb) ...
Selecting previously deselected package libroken18-heimdal.
Unpacking libroken18-heimdal (from 
.../libroken18-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libasn1-8-heimdal.
Unpacking libasn1-8-heimdal (from 
.../libasn1-8-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libwind0-heimdal.
Unpacking libwind0-heimdal (from 
.../libwind0-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libhx509-5-heimdal.
Unpacking libhx509-5-heimdal (from 
.../libhx509-5-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libkrb5-26-heimdal.
Unpacking libkrb5-26-heimdal (from 
.../libkrb5-26-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libheimntlm0-heimdal.
Unpacking libheimntlm0-heimdal (from 
.../libheimntlm0-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libgssapi2-heimdal.
Unpacking libgssapi2-heimdal (from 
.../libgssapi2-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libhdb9-heimdal.
Unpacking libhdb9-heimdal (from 
.../libhdb9-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libkadm5clnt7-heimdal.
Unpacking libkadm5clnt7-heimdal (from 
.../libkadm5clnt7-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libkadm5srv8-hei

Bug#565132: marked as done (krb5-multidev and heimdal-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 12:48:11 -0500 (EST)
with message-id <20100121174811.3d32e4...@carter-zimmerman.suchdamage.org>
and subject line Oops not marked fixed
has caused the Debian Bug report #565129,
regarding krb5-multidev and heimdal-dev: 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.)


-- 
565129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: heimdal-dev,krb5-multidev
Version: heimdal-dev/1.3.1.rc2.dfsg.1-1
Version: krb5-multidev/1.8+dfsg~alpha1-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2010-01-13
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!
  libdb4.8 libgssrpc4 libkdb5-4 libkadm5srv7 libsqlite3-0 libc-dev-bin
  linux-libc-dev libc6-dev comerr-dev krb5-multidev libroken18-heimdal
  libasn1-8-heimdal libwind0-heimdal libhx509-5-heimdal libkrb5-26-heimdal
  libheimntlm0-heimdal libgssapi2-heimdal libhdb9-heimdal
  libkadm5clnt7-heimdal libkadm5srv8-heimdal libkafs0-heimdal heimdal-multidev
  heimdal-dev
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5406847
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407760
W: cowdancer: unsupported operation flock, read-only open and 
fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5406895
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package libdb4.8.
(Reading database ... 10447 files and directories currently installed.)
Unpacking libdb4.8 (from .../libdb4.8_4.8.26-1_amd64.deb) ...
Selecting previously deselected package libgssrpc4.
Unpacking libgssrpc4 (from .../libgssrpc4_1.8+dfsg~alpha1-2_amd64.deb) ...
Selecting previously deselected package libkdb5-4.
Unpacking libkdb5-4 (from .../libkdb5-4_1.8+dfsg~alpha1-2_amd64.deb) ...
Selecting previously deselected package libkadm5srv7.
Unpacking libkadm5srv7 (from .../libkadm5srv7_1.8+dfsg~alpha1-2_amd64.deb) ...
Selecting previously deselected package libsqlite3-0.
Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.21-2_amd64.deb) ...
Selecting previously deselected package libc-dev-bin.
Unpacking libc-dev-bin (from .../libc-dev-bin_2.10.2-5_amd64.deb) ...
Selecting previously deselected package linux-libc-dev.
Unpacking linux-libc-dev (from .../linux-libc-dev_2.6.32-5_amd64.deb) ...
Selecting previously deselected package libc6-dev.
Unpacking libc6-dev (from .../libc6-dev_2.10.2-5_amd64.deb) ...
Selecting previously deselected package comerr-dev.
Unpacking comerr-dev (from .../comerr-dev_2.1-1.41.9-1_amd64.deb) ...
Selecting previously deselected package krb5-multidev.
Unpacking krb5-multidev (from .../krb5-multidev_1.8+dfsg~alpha1-2_amd64.deb) ...
Selecting previously deselected package libroken18-heimdal.
Unpacking libroken18-heimdal (from 
.../libroken18-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libasn1-8-heimdal.
Unpacking libasn1-8-heimdal (from 
.../libasn1-8-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libwind0-heimdal.
Unpacking libwind0-heimdal (from 
.../libwind0-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libhx509-5-heimdal.
Unpacking libhx509-5-heimdal (from 
.../libhx509-5-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libkrb5-26-heimdal.
Unpacking libkrb5-26-heimdal (from 
.../libkrb5-26-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libheimntlm0-heimdal.
Unpacking libheimntlm0-heimdal (from 
.../libheimntlm0-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libgssapi2-heimdal.
Unpacking libgssapi2-heimdal (from 
.../libgssapi2-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libhdb9-heimdal.
Unpacking libhdb9-heimdal (from 
.../libhdb9-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libkadm5clnt7-heimdal.
Unpacking libkadm5clnt7-heimdal (from 
.../libkadm5clnt7-heimdal_1.3.1.rc2.dfsg.1-1_amd64.deb) ...
Selecting previously deselected package libkadm5s

Bug#559646: closed by Marco Túlio Gontijo e Silva (No buildd errors found)

[Cyril Brulebois]

Debian Bug Tracking System  (21/01/2010):
> There seems to be no problem with building this package at:
> 
> https://buildd.debian.org/status/package.php?suite=unstable&p=haskell-configfile

There were issues, see the “all N” links, I guess the issue was in a
build-depended-on package, which got fixed in the meanwhile, and your
package then got given back (probably through -release@).

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#566161: fsprotect: uninstallable in sid, depends on kernel component

[Julien Cristau]

Package: fsprotect
Version: 1.0.4
Severity: serious
Justification: uninstallable

fsprotect depends on aufs-modules which is not in sid (and soon not in
testing).  Besides, to quote one of the kernel maintainers, "User-space
packages should never depend on kernel components, because the kernel
might be provided from outside the system (e.g. for a chroot'd
environment)".  Please remove this dependency (fsprotect is being
removed from testing temporarily because of this, to let the 2.6.32
kernel into squeeze).

Cheers,
Julien



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

Bug#563402: RFH: Bug#563402: ia32-libs broken on ia64

[Goswin von Brederlow]

Hi,

lacking any access to ia64 I'm wondering if any porter can help with
Bug#563402. Is there actualy something wrong in ia32-libs (and then
what) or is merulo[1] just not capable of running 32bit x86 binaries?

MfG
Goswin

--
[1] https://db.debian.org/machines.cgi?host=3Dmerulo



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

Bug#559646: marked as done (FTBFS: no package matching `regex-posix-0.93.1' was found)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 15:17:19 -0200
with message-id <1264094239.3988.71.ca...@zezinho>
and subject line No buildd errors found
has caused the Debian Bug report #559646,
regarding FTBFS: no package matching `regex-posix-0.93.1' was 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.)


-- 
559646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: haskell-configfile
Version: 1.0.5-3
Severity: serious
Justification: FTBFS

Your package FTBFS:
| debian/hlibrary.setup build
| Preprocessing library ConfigFile-1.0.5...
| Preprocessing executables for ConfigFile-1.0.5...
| Building ConfigFile-1.0.5...
| [1 of 4] Compiling Data.ConfigFile.Lexer ( src/Data/ConfigFile/Lexer.hs, 
dist/build/Data/ConfigFile/Lexer.o )
| [2 of 4] Compiling Data.ConfigFile.Types ( src/Data/ConfigFile/Types.hs, 
dist/build/Data/ConfigFile/Types.o )
| [3 of 4] Compiling Data.ConfigFile.Parser ( src/Data/ConfigFile/Parser.hs, 
dist/build/Data/ConfigFile/Parser.o )
| Failed to load interface for `Text.Regex.Posix.ByteString':
|   no package matching `regex-posix-0.93.1' was found
| make: *** [build-ghc6-stamp] Error 1

Build logs at the usual place:
  
https://buildd.debian.org/status/package.php?suite=unstable&p=haskell-configfile

Mraw,
KiBi.


--- End Message ---
--- Begin Message ---
Hi.

There seems to be no problem with building this package at:

https://buildd.debian.org/status/package.php?suite=unstable&p=haskell-configfile

Greetings.
-- 
marcot
http://marcot.iaaeee.org/



--- End Message ---

Processed: found 558983 in 0.6DrMattDestruction-8

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 558983 0.6DrMattDestruction-8
Bug #558983 [xmms2] FTBFS [hppa] - configure failure
Bug Marked as found in versions xmms2/0.6DrMattDestruction-8.
> thanks
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#565213: apt-listbugs: can't install because it's not installed

[Julian Andres Klode]

Am Donnerstag, den 14.01.2010, 18:40 +0100 schrieb David Kalnischkies:
> Hi Jörgen Tegnér, Francesco Poli & Michael Prokop,
> 
> First of all: Thanks for the reports!
> 
> 2010/1/14 Michael Prokop :
> > * Francesco Poli  [20100114 16:37]:
> > It's not just about .disabled files, it also affects any manually
> > modified configuration files (resulting in e.g. *.dpkg-dist) - files
> > that shouldn't be considered at all.
> And sorry (again) for the breakage - it seems i "like" to break
> the "simple but not too obviously" things quite regular... :(
> 
> But yes, in an act of reducing code copies i had created a
> GetListOfFilesInDir method which is a bit to "nice" it seems -
> if no extension for the partfiles is required (as it is for conf and
> preferences, not for sources and trusted) the code copies previously
> discarded all filenames including a dot - the new method doesn't do
> it...
> my bad -- through this was partly done on propose:
> I am regular confused about which part files need a extension and
> which doesn't need one so a single rule (preferable: all a valid
> extension)
> will hopefully established sometime in the future
> (not now, we need a fair and long transition for this...).
> 
> To cut it short, i will sit down and rewrite it a bit so it has the
> old behavior (expect that configfiles will be accepted also with .conf
> -
> any suggestions for preferences ?)
Complete proposal:
/etc/apt/apt.conf.d/*.conf
/etc/apt/preferences.d/*.preferences
/etc/apt/sources.list.d/*.list
In fact, we could implement this now and start deprecating files without
extensions, printing a warning for them; like done for
the /etc/modprobe.d/*.conf migration.

The run-parts(8) algorithm we currently use is really not the best way
to filter files defined by users. In fact, APT2 used the same rules as
APT, but those are a bit to strict and not really easy to understand for
the average user. I thus changed it in 
http://git.debian.org/?p=users/jak/apt2.git;a=commit;h=05f525c4aefc
to just ignore files with the suffix ~. Now I believe we should do
something else.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.





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

Bug#562322: marked as done (libmatheval: FTBFS: libtool: link: cannot find the library `/usr/lib/libltdl.la' or unhandled argument `/usr/lib/libltdl.la')

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2010 16:17:31 +
with message-id 
and subject line Bug#562322: fixed in libmatheval 1.1.7-1+nmu1
has caused the Debian Bug report #562322,
regarding libmatheval: FTBFS: libtool: link: cannot find the library 
`/usr/lib/libltdl.la' or unhandled argument `/usr/lib/libltdl.la'
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.)


-- 
562322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmatheval
Version: 1.1.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091213 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory 
> `/build/user-libmatheval_1.1.7-1-amd64-r7ORs8/libmatheval-1.1.7/tests'
> if x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../lib 
> -I.. -I../lib-Wall -g -O2 -MT matheval-matheval.o -MD -MP -MF 
> ".deps/matheval-matheval.Tpo" -c -o matheval-matheval.o `test -f 'matheval.c' 
> || echo './'`matheval.c; \
>   then mv -f ".deps/matheval-matheval.Tpo" ".deps/matheval-matheval.Po"; 
> else rm -f ".deps/matheval-matheval.Tpo"; exit 1; fi
> /bin/bash ../libtool --tag=CC --mode=link x86_64-linux-gnu-gcc -std=gnu99  
> -Wall -g -O2   -o matheval -lguile -lguile-ltdl -lcrypt -lm -ldl 
> matheval-matheval.o ../lib/libmatheval.la 
> mkdir .libs
> libtool: link: cannot find the library `/usr/lib/libltdl.la' or unhandled 
> argument `/usr/lib/libltdl.la'
> make[3]: *** [matheval] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/12/13/libmatheval_1.1.7-1_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: libmatheval
Source-Version: 1.1.7-1+nmu1

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

libmatheval1-dev_1.1.7-1+nmu1_amd64.deb
  to main/libm/libmatheval/libmatheval1-dev_1.1.7-1+nmu1_amd64.deb
libmatheval1_1.1.7-1+nmu1_amd64.deb
  to main/libm/libmatheval/libmatheval1_1.1.7-1+nmu1_amd64.deb
libmatheval_1.1.7-1+nmu1.diff.gz
  to main/libm/libmatheval/libmatheval_1.1.7-1+nmu1.diff.gz
libmatheval_1.1.7-1+nmu1.dsc
  to main/libm/libmatheval/libmatheval_1.1.7-1+nmu1.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 562...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ulises Vitulli  (supplier of updated libmatheval 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: Mon, 18 Jan 2010 14:07:24 -0300
Source: libmatheval
Binary: libmatheval1-dev libmatheval1
Architecture: source amd64
Version: 1.1.7-1+nmu1
Distribution: unstable
Urgency: low
Maintainer: Miguel Gea Milvaques 
Changed-By: Ulises Vitulli 
Description: 
 libmatheval1 - GNU library for evaluating symbolic mathematical expressions 
(run
 libmatheval1-dev - GNU library for evaluating symbolic mathematical 
expressions (dev
Closes: 562322
Changes: 
 libmatheval (1.1.7-1+nmu1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Added missing dependency (Closes: #562322).
Checksums-Sha1: 
 26139552af80f108ecd9d83e5511871a3b4a54ab 1776 libmatheval_1.1.7-1+nmu1.dsc
 65425165b08edef02c35e104e810ec8e709702b8 11735 libmatheval_1.1.7-1+nmu1.diff.gz
 c66f8b447d9a3af20f07e19e78cec5c45daeb3e0 49010 
libmatheval1-dev_1.1.7-1+nmu1_amd64.deb
 8422de44f14046edc37270d4eb48957d033c86d3 23546 
libmatheval1_1.1.7-1+nmu1_amd64.deb
Checksums-Sha256: 
 34c87b78642752b93859e3f5bf41d26b4844e9491d2c3649406d8c4c28c0be28 1776 
libmatheval_1.1.7-1+nmu1.dsc
 53fde14e144ae1c69398ad32f6ce6356b43cdb59a4f3868d9b8d224c725333aa 11735 
libmatheval_1.1.7-1+nmu1

Bug#564966: kq-data: contains unlicensed music

[Kalle Olavi Niemitalo]

Kalle Olavi Niemitalo  writes:

> Even if the demoscene musicians who made these files are happy to
> let people copy them, it still does not mean modifying them is
> allowed, as Debian would require for packages in main.

Apparently, at least some of them can be distributed unmodified,
although perhaps not as part of a game:
http://modarchive.org/index.php?terms-upload
http://modarchive.org/index.php?faq-licensing

  aa_arofl.xm
md5sum d4d31cc9bd75d6ec24cc36aeb5b7ada2 in KQ and at The Mod Archive
md5sum bff61a1508c83d004e9f799cd32846c5 at the composer's site
"Archons of Light" by Nils Ingvarsson (aka ArchAngel)
http://modarchive.org/module.php?32610
http://www.archangel-music.se/portfolio/music/

  comeback.mod
md5sum ab92587defb8fefc78118860be618892
"Come Back To Me" by Ole Skåra (aka Zany/Iris)
5th place in Gathering '95 4chmus competition
http://modarchive.org/module.php?122874

  enfero.xm
md5sum f671ebb39bcc222ea9d219327b4d57ac
"Theme from Enfero" by AwEmAn/LIS (aka Neo)
http://modarchive.org/module.php?42125

  eranasp.mod
md5sum 2b857a0717e5438ae3154b78a53e0a44
"erana-j.kyd" by Jesper Kyd
http://modarchive.org/module.php?42353
http://amp.dascene.net/downmod.php?index=36860

  infanita.mod
md5sum ca178016ffaa310a7ff170ae007d8000 in KQ and at The Mod Archive
md5sum b842dd41473f8c5a06053dae798da060 at Amiga Music Preservation
"infanita" by Bjorn Lynne (aka Dr. Awesome)
http://modarchive.org/module.php?45620
http://amp.dascene.net/downmod.php?index=19440
http://www.shockwave-sound.com/xt_cart_add.php?vid=8119

  into61.s3m
md5sum df8b70766102fd45acca5e5d133e41da
".61" by Yoav Pasovsky (aka Paso/Esteem)
http://modarchive.org/module.php?164773

  land.mod
md5sum 4ce7387cf12b44ab01c23ef32274eb85 in KQ and at The Mod Archive
md5sum 13d67a0e9e23a93917eab5b6aabe2c33 at Amiga Music Preservation
"sahara" by Bjorn Lynne (aka Dr. Awesome)
http://modarchive.org/module.php?54239
http://amp.dascene.net/downmod.php?index=19524

  oxford.s3m
md5sum 8c0e75d5ca111475934a221539b4088a in KQ
md5sum d340254df0d54d5f73a039424d62f7d1 at The Mod Archive
"Oxford-Suite" by NEMO/4$orcerers
mentions being "based on ED ALLEYNE's E-Voiline Virtuosity"
http://modarchive.org/module.php?51585

  town.mod
md5sum 304a7e3800f1ff47585883f3ba8c014c in KQ
md5sum 599dbd0dd8a49687ee264ff74ab4f19b at The Mod Archive
md5sum 47c31ac6f729ca09ad53a1ad31471858 at Amiga Music Preservation
"old england" by Bjorn Lynne (aka Dr. Awesome)
http://modarchive.org/module.php?89342
http://amp.dascene.net/downmod.php?index=19567

Still, even if the Mod Archive license is valid, these could go
in non-free at best.

No license found for:

  dag_4.xm
md5sum 480b0d0203756c2a24f5a4fcf17e07a1
"Daggerfall 4"

  rain.s3m
md5sum f729b301e9152b9b09096a64a72b314b
"Rain..."

  toroia.s3m
md5sum ec48fe61e03a73b366ed6f0e89ce332c
"FF2: Toroia Castle"
mentions "Original by Nobuo Uematsu"

  waterw.xm
md5sum 86d79241eeea5736e74c92d57b62182f
"WaterWorld" by TRAFO/Extreme Mods Club


pgpJ1W1JCojhS.pgp
Description: PGP signature

Bug#560246: Diagnostics for fiaif

[Mats Erik Andersson]

Hello Greg Kochanski,

have your problem with Fiaif been settled? If not let me
suggest some means for diagnosing your difficulties.
In a probably related report #560008, the only solution
was to downgrade Fiaif. 

First off, that entry [FIAIF_ZONE_MISS_INTD] concerns traffic generated
by CUPS as it broadcasts to its local segment about its presence.

Your problem is that forwarding between network segments is not
properly working. What output do you get from this?

  $ sysctl -a  2> /dev/null  | grep 'ipv4.*\.forward'

You should at least get value 1 for 'eth1' and for 'eth2'.
If this is not the case, issue

  # sysctl net.ipv4.conf.eth1.forwarding=1
  # sysctl net.ipv4.conf.eth2.forwarding=1

and test your inter-ubuntu connection.

In the following I suppose you have some knowledge of 'iptables'.
Otherwise, please tell me to rephrase my explanations.

The next test is to issue print-outs similar to

  # iptables -nvL FORWARD

by using successively progressing targets in place of 'FORWARD'
that will appear in the netfilter rules printed from a previous command.

In the output, do you find the expected ACCEPT-rules that use
'state RELATED,ESTABLISHED'. Does the DROP policy at the table head
claim many blocked packages? That would indicate that the desireable
forwarding rule is never reached.

General questions:

   Are eth1 and eth2 assigned to the same networks as before the
   upgrade? I am considering the possibility that udev have made
   other assignment decisions of some unknown reason.

   Have you double checked the definitions you feed into Fiaif?

The difficulty is that your problem report leaves very large
room for guessing, and small aid in determining the cause.


Kind regards,

-- 
Mats Erik Andersson, fil. dr


signature.asc
Description: Digital signature

Bug#566142: sudosh3: "code quality is terrible", says debian-devel ITP review

[Simon McVittie]

Package: sudosh3
Version: 3.2.0-1
Severity: grave
Tags: security
Justification: during replay, reads up to 8MB into an 8KB buffer

You don't seem to have responded to Adam Borowski's mail wondering why this
package should be in Debian, and commenting on its quality. In particular,
he notes a trivial buffer overflow during replay.

In http://lists.debian.org/debian-devel/2010/01/msg00317.html he writes:
> >  sudosh allows complete session logging of shells run under sudo.
> >  Individual sudo commands are still logged as normal but running a shell
> >  under sudosh records the entire session as well as session timings for
> >  complete playback later.
> 
> Uhm, it appears to be an one-trick pony which tries to replicate what ttyrec
> does, except that it's usage is sharply limited, it spits out several files
> instead of one, and the code quality is terrible.  Just one example:
> 
> In replay.c, it does sscanf("... %i ...", &b) to an int, makes a sanity
> check, rejecting values of b more than 8MB -- comparing it as a _signed_
> value.  Then, it does read(fd, buffer, (size_t)b).  (size_t is unsigned).
> 
> But after a second reading of the code, you don't need to go that far.  The
> check against overflow was for 8MB, and size of the static buffer is 8192
> bytes...
> 
> 
> Also,
> > * License : Open Software License version 2.0 (non free)
> 
> Is there any need for non-free tools where better free equivalents already
> exist?  Try ttyrec, my termrec, script -t (not as well suited for this
> task), RealLog, nh_recorder or one of many others...

Regards,
Simon


signature.asc
Description: Digital signature

Bug#566136: zope-zms: Depends only on unavailable zope versions

[Adam D. Barratt]

Package: zope-zms
Version: 1:2.11.1-03-1
Severity: serious

Hi,

zope-zms depends on one of zope2.9 | zope2.10. However, as zope2.10 has been 
removed, the package is now
uninstallable in unstable as none of the listed zope versions are in the 
archive.


Regards,

Adam 





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

Bug#566135: zope-replacesupport: Depends only on unavailable zope versions

[Adam D. Barratt]

Package: zope-replacesupport
Version: 1.0.3-4
Severity: serious

Hi,

zope-replacesupport depends on one of  zope2.9 | zope2.10. However, as 
zope2.10 has been removed, the package is now
uninstallable in unstable as none of the listed zope versions are in the 
archive.


Regards,

Adam 





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

Bug#566134: zope-ploneformgen: Depends only on unavailable zope versions

[Adam D. Barratt]

Package: zope-ploneformgen
Version: 1.2.7-1
Severity: serious

Hi,

zope-ploneformgen depends on one of zope2.7 | zope2.8 | zope2.9 | zope2.10 |
zope3.0. However, as zope2.10 has been removed, the package is now
uninstallable in unstable as none of the listed zope versions are in the
archive.

Regards,

Adam 





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

Bug#562575: installation-reports: testing on iso-cd weekly build of powerpc of 100118 shows same behaviour

[Adrian Zaugg]

Package: installation-reports
Severity: normal


The CD image of testing weekly builds of Jan, 18th 2010 shows the same 
behaviour:
Looping with segmentation fault, "INFO: kbd-mode: setting console mode to 
Unicode (UTF-8)" 

Upgrading to testing from Lenny is not concerned, the current 2.6.30 kernel of 
testing does
boot without this error.


-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/powerpc/iso-cd/debian-testing-powerpc-CD-1.iso
Date: 21st January 2010

Machine: Apple PowerBook G4 12"

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Installation fails. See above for details.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.



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

Bug#566133: zope-maildrophost: Depends only on unavailable zope versions

[Adam D. Barratt]

Package: zope-maildrophost
Version: 2.2-1
Severity: serious

Hi,

zope-maildrophost depends on one of zope2.8 | zope2.9 | zope2.10. However, 
as zope2.10 has been removed, the package is now uninstallable in unstable 
as none of the listed zope versions are in the archive.


Regards,

Adam 





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

Bug#566132: zope-externaleditor: Depends on only unavailable zope versions

[Adam D. Barratt]

Package: zope-externaleditor
Version: 0.9.3-3
Severity: serious

Hi,

zope-externaleditor depends on one of zope2.8 | zope2.9 | zope2.10. However, 
as zope2.10 has been removed, the package is now uninstallable in unstable 
as none of the listed zope versions are in the archive.


Regards,

Adam 





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

Bug#566131: zope-docfindertab: Depends on no available zope versions

[Adam D. Barratt]

Package: zope-docfindertab
Version: 1.0.2-1
Severity: serious

Hi,

zope-docfindertab depends on one of zope2.7 | zope2.8 | zope2.9 | zope2.10. 
However, as zope2.10 has been removed, the package is now uninstallable in 
unstable as none of the listed zope versions are in the archive.


Regards,

Adam 





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

Bug#566127: zope-atextensions: Depends on no available zope versions

[Adam D. Barratt]

Package: zope-atextensions
Version: 0.9.2-2
Severity: serious

Hi,

zope-atextensions depends on one of zope2.7 | zope2.8 | zope2.9 | zope2.10 | 
zope3.0. However, as zope2.10 has been removed, the package is now 
uninstallable in unstable as none of the listed zope versions are in the 
archive.


Regards,

Adam 





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

Bug#566130: zope-cmfbibliographyat: Uninstallable due to zope2.10 removal

[Adam D. Barratt]

Package: zope-cmfbibliographyat
Version: 0.8.0-3
Severity: serious

Hi,

zope-cmfbibliographyatdepends on one of zope2.7 | zope2.8 | zope2.9 | 
zope2.10 |

zope3.0. However, as zope2.10 has been removed, the package is now
uninstallable in unstable as none of the listed zope versions are in the
archive.

Regards,

Adam 





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

Bug#566128: squishdot: Depends on removed zope2.10

[Adam D. Barratt]

Package: squishdot
Version: 1.5.0-6
Severity: serious

Hi,

squishdot depends on one of zope2.10 | zope2.9 | zope2.8 | zope2.7. However, 
with the removal of zope2.10 from the archive, it is now uninstallable, as 
none of the listed packages are in Debian.


Regards,

Adam 





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

Bug#563402: [Pkg-ia32-libs-maintainers] Bug#563402: ia32-libs broken on ia64

[Giuseppe Iuculano]

Hi,

sorry for late reply.

Il 18/01/2010 10:00, Goswin von Brederlow ha scritto:
> That is a bit odd. I do see /lib/ld-linux.so.2 and /usr/bin/ldd in
> ia32-libs:ia64 so that should work.
> 
> What kind of ia64 CPU do you have? Is it old enough to still have the
> i386 emulation hardware? Newer ia64 afaik don't have that anymore and
> can't execute i386 code. Maybe your hardware just doesn't support it.

I tried that in a porterbox, merulo[1]:

$ cat /proc/cpuinfo
processor  : 0
vendor : GenuineIntel
arch   : IA-64
family : 31
model  : 2
model name : Madison up to 9M cache
revision   : 1
archrev: 0
features   : branchlong
cpu number : 0
cpu regs   : 4
cpu MHz: 1600.003
itc MHz: 1600.003320
BogoMIPS   : 2392.06
siblings   : 1
physical id: 0

processor  : 1
vendor : GenuineIntel
arch   : IA-64
family : 31
model  : 2
model name : Madison up to 9M cache
revision   : 1
archrev: 0
features   : branchlong
cpu number : 0
cpu regs   : 4
cpu MHz: 1600.003
itc MHz: 1600.003320
BogoMIPS   : 2392.06
siblings   : 1
physical id: 1


[1] https://db.debian.org/machines.cgi?host=merulo

Cheers,
Giuseppe.



signature.asc
Description: OpenPGP digital signature

Processed: non-stable RCs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # reason for FTBFS appeared post-lenny
> tags 526547 + squeeze sid
Bug #526547 [libnoise] libnoise: FTBFS: undefined reference to `main'
Added tag(s) sid and squeeze.
> tags 526558 + squeeze sid
Bug #526558 {Done: Eric Warmenhoven } [timps] timps: 
FTBFS: 'INT_MIN' undeclared here
Added tag(s) sid and squeeze.
> tags 526563 + squeeze sid
Bug #526563 {Done: Daniel Baumann } [trousers] trousers: 
FTBFS: Invalid libtool wrapper script
Added tag(s) sid and squeeze.
> tags 526568 + squeeze sid
Bug #526568 {Done: Damyan Ivanov } [firebird2.0] firebird2.0: 
FTBFS: autoconf errors
Added tag(s) sid and squeeze.
> tags 526576 + squeeze sid
Bug #526576 {Done: edmo...@debian.org (Robert S. Edmonds)} [python-pypcap] 
python-pypcap: FTBFS: deferencing pointer to incomplete type
Added tag(s) sid and squeeze.
>
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#562259: NMU fix

[Jo Shields]

tags 562259 patch
thanks

A fix for this bug (and some others) has been attached and uploaded to
the DELAYED queue.
reverted:
--- libkarma-0.0.6/patch
+++ libkarma-0.0.6.orig/patch
@@ -1,25 +0,0 @@
-diff -u libkarma-0.0.6/debian/control libkarma-0.0.6/debian/control
 libkarma-0.0.6/debian/control
-+++ libkarma-0.0.6/debian/control
-@@ -2,7 +2,7 @@
- Priority: extra
- Maintainer: Joe Nahmias 
- Build-Depends: debhelper (>= 6), dpatch, zlib1g-dev, libtagc0-dev, libusb-dev
--Build-Depends-Indep: cli-common-dev (>= 0.4.4), mono-gmcs (>= 1.0) | 
c-sharp-2.0-compiler, libmono2.0-cil
-+Build-Depends-Indep: cli-common-dev (>= 0.4.4), mono-devel | 
c-sharp-2.0-compiler, libmono2.0-cil
- Standards-Version: 3.8.0
- Section: libs
- Homepage: http://www.freakysoft.de/html/libkarma/
-diff -u libkarma-0.0.6/debian/rules libkarma-0.0.6/debian/rules
 libkarma-0.0.6/debian/rules
-+++ libkarma-0.0.6/debian/rules
-@@ -30,7 +30,7 @@
-   touch $@
- build-indep: patch
-   dh_testdir
--  $(MAKE) karma-sharp
-+  $(MAKE) karma-sharp MCS=/usr/bin/csc
-   touch $@
- 
- clean: clean-patched unpatch
-diff -u libkarma-0.0.6/debian/changelog libkarma-0.0.6/debian/changelog
diff -u libkarma-0.0.6/debian/rules libkarma-0.0.6/debian/rules
--- libkarma-0.0.6/debian/rules
+++ libkarma-0.0.6/debian/rules
@@ -30,7 +30,7 @@
touch $@
 build-indep: patch
dh_testdir
-   $(MAKE) karma-sharp MCS=/usr/bin/csc
+   $(MAKE) karma-sharp MCS=/usr/bin/mono-csc
touch $@
 
 clean: clean-patched unpatch
@@ -47,13 +47,13 @@
dh_testdir
dh_testroot
dh_installdirs
-   cd src && $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install
-   cd tools && $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install
+   cd src && $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install VERSION=0.0.6
+   cd tools && $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install VERSION=0.0.6
 install-indep: build-indep
dh_testdir
dh_testroot
dh_installdirs
-   cd karma-sharp && $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install
+   cd karma-sharp && $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install 
VERSION=0.0.6
 
 binary-indep: export DH_OPTIONS := -i
 binary-indep: build-indep install-indep
diff -u libkarma-0.0.6/debian/control libkarma-0.0.6/debian/control
--- libkarma-0.0.6/debian/control
+++ libkarma-0.0.6/debian/control
@@ -1,7 +1,7 @@
 Source: libkarma
 Priority: extra
 Maintainer: Joe Nahmias 
-Build-Depends: debhelper (>= 6), dpatch, zlib1g-dev, libtagc0-dev, libusb-dev, 
mono-devel (>= 2.0.1)
+Build-Depends: debhelper (>= 6), dpatch, zlib1g-dev, libtagc0-dev, libusb-dev, 
mono-devel (>= 2.4.2.3)
 Build-Depends-Indep: cli-common-dev (>= 0.4.4), libmono2.0-cil (>= 2.0.1)
 Standards-Version: 3.8.0
 Section: libs
@@ -64,0 +65,12 @@
+Package: libkarma-cil-dev
+Section: libs
+Architecture: all
+Depends: libkarma-cil (= ${binary:Version}), ${misc:Depends}
+Replaces: libkarma-cil (<< 0.0.6-4.3)
+Description: Rio Karma access library [CLI library development files]
+ Also known as karma-sharp, this is a CLI library (.dll) that
+ provides (read/write) access to the Rio Karma music player using
+ either the usb (with OMFS) or network (PEARL) interface.
+ .
+ This package contains development files for the karma-sharp library used for
+ compilation.
diff -u libkarma-0.0.6/debian/libkarma-cil.install 
libkarma-0.0.6/debian/libkarma-cil.install
--- libkarma-0.0.6/debian/libkarma-cil.install
+++ libkarma-0.0.6/debian/libkarma-cil.install
@@ -2 +1,0 @@
-usr/lib/pkgconfig/*
diff -u libkarma-0.0.6/debian/changelog libkarma-0.0.6/debian/changelog
--- libkarma-0.0.6/debian/changelog
+++ libkarma-0.0.6/debian/changelog
@@ -1,3 +1,16 @@
+libkarma (0.0.6-4.3) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/control:
++ Bump mono-devel version to 2.4.2.3 for mono-csc
++ Create -cil-dev package containing pcfiles
+  * debian/rules:
++ Use MCS=/usr/bin/mono-csc instead of /usr/bin/csc (Closes: #562259)
++ Add VERSION=0.0.6 to karma-sharp $(MAKE) invocations to ensure
+  Version: field of .pc file is populated (Closes: #551049)
+
+ -- Chow Loong Jin   Thu, 21 Jan 2010 19:31:18 +0800
+
 libkarma (0.0.6-4.2) unstable; urgency=low
 
   * Non-maintainer upload.
only in patch2:
unchanged:
--- libkarma-0.0.6.orig/debian/libkarma-cil-dev.install
+++ libkarma-0.0.6/debian/libkarma-cil-dev.install
@@ -0,0 +1 @@
+usr/lib/pkgconfig/*

Processed: NMU fix

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 562259 patch
Bug #562259 [src:libkarma] libkarma: FTBFS: make[2]: /usr/bin/csc: Command not 
found
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Processed: closing 564255

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # meh
> close 564255 2:1.7.4-2
Bug#564255: xserver-xorg: X server does not start with segfault.
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug#564203: xserver-xorg-video-nv broken with xserver 1.7
Bug#565189: xinit: Segfaults on start up
Bug marked as fixed in version 2:1.7.4-2, send any further explanations to 
"stor...@club-internet.fr" 

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

Processed: limit source to dahdi-tools, tagging 564381

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #dahdi-tools (1:2.2.1-1) UNRELEASED; urgency=low
> #
> #  * New upstream release (Closes: #536257, #564381).
> #
> limit source dahdi-tools
Limiting to bugs with field 'source' containing at least one of 'dahdi-tools'
Limit currently set to 'source':'dahdi-tools'

> tags 564381 + pending
Bug #564381 [src:dahdi-tools] dahdi-tools: FTBFS: asciidoc: FAILED: README: 
line 233: undefined filter attribute in command
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed (with 1 errors): reassign 564255 to xserver-xorg-core, closing 564255

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 564255 xserver-xorg-core 2:1.7.0-1
Bug #564255 {Done: Brice Goglin } [xserver-xorg-video-nv] 
xserver-xorg: X server does not start with segfault.
Bug #564203 {Done: Brice Goglin } [xserver-xorg-video-nv] 
xserver-xorg-video-nv broken with xserver 1.7
Bug #565189 {Done: Brice Goglin } [xserver-xorg-video-nv] 
xinit: Segfaults on start up
Bug reassigned from package 'xserver-xorg-video-nv' to 'xserver-xorg-core'.
Bug reassigned from package 'xserver-xorg-video-nv' to 'xserver-xorg-core'.
Bug reassigned from package 'xserver-xorg-video-nv' to 'xserver-xorg-core'.
Bug No longer marked as found in versions xserver-xorg-video-nv/1:2.1.15-1.
Bug No longer marked as found in versions xserver-xorg-video-nv/1:2.1.15-1.
Bug No longer marked as found in versions xserver-xorg-video-nv/1:2.1.15-1.
Bug No longer marked as fixed in versions xorg-server/2:1.7.4-2.
Bug No longer marked as fixed in versions xorg-server/2:1.7.4-2.
Bug No longer marked as fixed in versions xorg-server/2:1.7.4-2.
Bug #564255 {Done: Brice Goglin } [xserver-xorg-core] 
xserver-xorg: X server does not start with segfault.
Bug #564203 {Done: Brice Goglin } [xserver-xorg-core] 
xserver-xorg-video-nv broken with xserver 1.7
Bug #565189 {Done: Brice Goglin } [xserver-xorg-core] 
xinit: Segfaults on start up
Bug Marked as found in versions xorg-server/2:1.7.0-1.
Bug Marked as found in versions xorg-server/2:1.7.0-1.
Bug Marked as found in versions xorg-server/2:1.7.0-1.
> close 564255 xorg-server/2:1.7.4-2
Unknown command or malformed arguments to command.

> thanks
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#536973: postgresql-plproxy: FTBFS: make[1]: *** No rule to make target `/usr/lib/postgresql/8.4/lib/pgxs/src/makefiles/pgxs.mk'. Stop.

[Christoph Berg]

Re: Lucas Nussbaum 2009-07-14 <20090714130949.ga26...@xanadu.blop.info>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2009/07/13/postgresql-plproxy_2.0.8-1_lsid64.buildlog

Hi,

is there a chance of getting this fixed soonish?

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: Digital signature

Bug#564415: Any updates? - Thunderbird 3.0.1 has just been released

[Gal]

Hi,

It would be great if you could update Icedove 3.0, even thought its
experimental.
I just saw that Mozilla has released version 3.0.1. currently I'm using
the3.0~rc2-2 with apt pin, since 3.0-2 doesn't work.