Bug#699306: Add usertag

2014-02-18 Thread bastien ROUCARIES
control: user debian...@debian.org
control: usertags -1 license-problem-md5sum-non-free-file

Add usertags


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



Processed: your mail

2014-02-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tag 738601 + pending
Bug #738601 [slapos-node-unofficial] slapos-node-unofficial: fails to upgrade 
from 'testing' - trying to overwrite /usr/share/pyshared/slapos/util.py
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
738601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#738601: marked as done (slapos-node-unofficial: fails to upgrade from 'testing' - trying to overwrite /usr/share/pyshared/slapos/util.py)

2014-02-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Feb 2014 07:48:38 +
with message-id e1wffpy-0003ix...@franck.debian.org
and subject line Bug#738601: fixed in slapos.core 1.0.2.1-3
has caused the Debian Bug report #738601,
regarding slapos-node-unofficial: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/pyshared/slapos/util.py
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.)


-- 
738601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: slapos-node-unofficial
Version: 1.0.2.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Preparing to unpack .../slapos-node-unofficial_1.0.2.1-2_all.deb ...
  Unpacking slapos-node-unofficial (1.0.2.1-2) over (0.35.1-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/slapos-node-unofficial_1.0.2.1-2_all.deb (--unpack):
   trying to overwrite '/usr/share/pyshared/slapos/util.py', which is also in 
package slapos-client 0.35.1-4
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


slapos-node-unofficial_1.0.2.1-2.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: slapos.core
Source-Version: 1.0.2.1-3

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

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 738...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arnaud Fontaine ar...@debian.org (supplier of updated slapos.core 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 18 Feb 2014 16:23:53 +0900
Source: slapos.core
Binary: slapos-client slapos-node-unofficial
Architecture: source all
Version: 1.0.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Arnaud Fontaine ar...@debian.org
Changed-By: Arnaud Fontaine ar...@debian.org
Description: 
 slapos-client - Client-side to request applications with SlapOS
 slapos-node-unofficial - Node-side to deploy applications with SlapOS 
(unofficial)
Closes: 738601
Changes: 
 slapos.core (1.0.2.1-3) unstable; urgency=medium
 .
   * debian/conf/slapos-node-unofficial.cfg:
 + Use default path for supervisord socket to avoid breaking existing
   configuration and it should be in instance directory anyway.
   * debian/control:
 + Add Replaces and Breaks as util.py used only by slapos-node-unofficial
   was wrongly installed in slapos-client before 1.0.2.1-1. Thanks to
   Andreas Beckmann. Closes: #738601.
Checksums-Sha1: 
 a14b975526eac9e773d89c06e57e0e18485c4029 1484 slapos.core_1.0.2.1-3.dsc
 cc9c95dbc6d047f92f8414ce1d3b8783337fc7b8 26588 
slapos.core_1.0.2.1-3.debian.tar.xz
 570a029fd8c989b7640d60d20b9ccf40cfd3d2b4 51186 slapos-client_1.0.2.1-3_all.deb
 d0289580089dff56b5900e5e6f8f25e6ba21bd1e 91246 
slapos-node-unofficial_1.0.2.1-3_all.deb
Checksums-Sha256: 
 3d8515edeb8e296561ce001243ea354a99104afeaec4a7b335af59aedc335c61 1484 
slapos.core_1.0.2.1-3.dsc
 d6eca61935e1c3f3605870f4b4a268a4d9503ca653757be2bec9645d421114f5 26588 
slapos.core_1.0.2.1-3.debian.tar.xz
 8d339bf85a8278bef981d0b800d65b0d7ea14d406bf0b0499baa35250e8a1b28 51186 
slapos-client_1.0.2.1-3_all.deb
 63d0cd9f60ad612bdf57c474b6eadb1674006f61c35abf55a3d739cbc77049bf 91246 
slapos-node-unofficial_1.0.2.1-3_all.deb
Files: 
 37c63443ad87d74f78d540e71e11528a 1484 net optional slapos.core_1.0.2.1-3.dsc
 97e2f3f01c4976c5a5ceddc1967c9322 26588 net optional 
slapos.core_1.0.2.1-3.debian.tar.xz
 5e37c913d30f282175be9455318e3ce2 51186 net optional 
slapos-client_1.0.2.1-3_all.deb
 7ebfb38ef67190ed6d30443a2fef3f7a 91246 net optional 
slapos-node-unofficial_1.0.2.1-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1


Bug#739370: the problem hasn't been resolved

2014-02-18 Thread Andrew Shadura
Hello,

On Tue, 18 Feb 2014 05:37:07 +
Raf Czlonka rafal.czlo...@gmail.com wrote:

 New uploaded version hasn't resolved the issue because both 0.9.4-2
 and 0.9.5-1, and possibly earlier, versions introduced a bug where
 they create '/usr/share/pkg-config-crosswrapper' directory with
 'pkg-config-crosswrapper' shell script inside it.
 
 Whoever installed any of those versions will get into this problem:
 
 dpkg-divert: error: cannot divert directories
 
 Which is correct, since 'dpkg-divert' has the wrong information -
 since 'dpkg-divert' entries are in 'pkgconf.preinst' script,
 diversion takes place *before* the directory gets created so there
 aren't any installation issues. However, upon deinstallation, the
 directory being there, causes an issue with 'dpkg-divert' which
 expects a 'pkg-config-crosswrapper' file, not a directory.
 
 Package version 0.9.5-2 installs just fine on a system where none of
 the above versions were installed, but does not resolve the issues
 introduced by either of the earlier versions of the package.

Yes, that's true; I don't currently know how to solve that issue
properly. I've added a check in preinst script to remove that bogus
directory, but that won't help with removing broken versions of the
package co-installed with pkg-config: the only way to fix them is to
upgrade then to a new version (or to fix the issue manually).

-- 
Cheers,
  Andrew


signature.asc
Description: PGP signature


Bug#733002: marked as done (mariadb-5.5: FTBFS w/bison 3.x)

2014-02-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Feb 2014 09:21:44 +
with message-id e1wfgs4-0006rp...@franck.debian.org
and subject line Bug#733002: fixed in mariadb-5.5 5.5.35-1
has caused the Debian Bug report #733002,
regarding mariadb-5.5: FTBFS w/bison 3.x
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.)


-- 
733002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: mariadb-5.5
Version: 5.5.32-1
Severity: serious
Justification: fails to build from source

Automatic builds of mariadb-5.5 have been failing with errors from
sql_yacc.cc:

  /«PKGBUILDDIR»/builddir/sql/sql_yacc.cc: In function 'int MYSQLparse()':
  /«PKGBUILDDIR»/builddir/sql/sql_yacc.cc:17049:30: error: too few arguments to 
function 'int MYSQLlex(void*, void*)'
 yychar = yylex (yylval);
^
  /«PKGBUILDDIR»/builddir/sql/sql_yacc.cc:64:25: note: declared here
   #define yylex   MYSQLlex
   ^
  /«PKGBUILDDIR»/sql/sql_yacc.yy:75:5: note: in expansion of macro 'yylex'
   int yylex(void *yylval, void *yythd);
   ^
  /«PKGBUILDDIR»/sql/sql_yacc.yy:32:23: error: 'yythd' was not declared in this 
scope
   #define YYTHD ((THD *)yythd)
  [...]

I suspect mariadb will need porting to bison 3.x, which recently
landed in unstable.  Could you please take a look?

Thanks!
---End Message---
---BeginMessage---
Source: mariadb-5.5
Source-Version: 5.5.35-1

We believe that the bug you reported is fixed in the latest version of
mariadb-5.5, which is due to be installed in the Debian FTP archive.

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 733...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Page jamesp...@debian.org (supplier of updated mariadb-5.5 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Feb 2014 16:51:52 +
Source: mariadb-5.5
Binary: libmariadbclient18 libmariadbd-dev libmariadbclient-dev mariadb-common 
mariadb-client-core-5.5 mariadb-client-5.5 mariadb-server-core-5.5 
mariadb-test-5.5 mariadb-server-5.5 mariadb-server mariadb-client mariadb-test
Architecture: source all amd64
Version: 5.5.35-1
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org
Changed-By: James Page jamesp...@debian.org
Description: 
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database development files
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-5.5 - MariaDB database client binaries
 mariadb-client-core-5.5 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-5.5 - MariaDB database server binaries
 mariadb-server-core-5.5 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite (metapackage for the 
lates
 mariadb-test-5.5 - MariaDB database regression test suite
Closes: 732967 733002 734426 735284 736480 737597
Changes: 
 mariadb-5.5 (5.5.35-1) unstable; urgency=low
 .
   [ Otto Kekäläinen ]
   * New upstream release, fixing the following security issues:
 - Buffer overflow in client/mysql.cc (Closes: #737597).
   - CVE-2014-0001
 - http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html
   - CVE-2013-5891
   - CVE-2013-5908
   - CVE-2014-0386
   - CVE-2014-0393
   - CVE-2014-0401
   - CVE-2014-0402
   - CVE-2014-0412
   - CVE-2014-0420
   - CVE-2014-0437
   * Upstream https://mariadb.atlassian.net/browse/MDEV-4902
 fixes compatibility with Bison 3.0 (Closes: #733002)
   * Updated Russian debconf translation (Closes: #734426)
   * Updated Japanese debconf translation (Closes: #735284)
   * Updated French debconf translation (Closes: #736480)
   * Renamed SONAME properly (Closes: #732967)
Checksums-Sha1: 
 aec5b5c77d545f642c49188e5f0551621ffee674 2944 mariadb-5.5_5.5.35-1.dsc
 b0587452283bbe9b27e222ab76e52c9c78fe9222 43926514 

Bug#737597: marked as done (mariadb-5.5: CVE-2014-0001: command-line tool buffer overflow via long server version string)

2014-02-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Feb 2014 09:21:44 +
with message-id e1wfgs4-0006rj...@franck.debian.org
and subject line Bug#737597: fixed in mariadb-5.5 5.5.35-1
has caused the Debian Bug report #737597,
regarding mariadb-5.5: CVE-2014-0001: command-line tool buffer overflow via 
long server version string
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.)


-- 
737597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: mariadb-5.5
Severity: important
Tags: security upstream fixed-upstream

Hi,

the following vulnerability was published for mariadb-5.5.

CVE-2014-0001[0]:
command-line tool buffer overflow via long server version string

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities  Exposures) id in your changelog entry.

For further information see:

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0001
http://security-tracker.debian.org/tracker/CVE-2014-0001
[1] http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/2502.565.64
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1054592

Regards,
Salvatore
---End Message---
---BeginMessage---
Source: mariadb-5.5
Source-Version: 5.5.35-1

We believe that the bug you reported is fixed in the latest version of
mariadb-5.5, which is due to be installed in the Debian FTP archive.

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 737...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Page jamesp...@debian.org (supplier of updated mariadb-5.5 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Feb 2014 16:51:52 +
Source: mariadb-5.5
Binary: libmariadbclient18 libmariadbd-dev libmariadbclient-dev mariadb-common 
mariadb-client-core-5.5 mariadb-client-5.5 mariadb-server-core-5.5 
mariadb-test-5.5 mariadb-server-5.5 mariadb-server mariadb-client mariadb-test
Architecture: source all amd64
Version: 5.5.35-1
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org
Changed-By: James Page jamesp...@debian.org
Description: 
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database development files
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-5.5 - MariaDB database client binaries
 mariadb-client-core-5.5 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-5.5 - MariaDB database server binaries
 mariadb-server-core-5.5 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite (metapackage for the 
lates
 mariadb-test-5.5 - MariaDB database regression test suite
Closes: 732967 733002 734426 735284 736480 737597
Changes: 
 mariadb-5.5 (5.5.35-1) unstable; urgency=low
 .
   [ Otto Kekäläinen ]
   * New upstream release, fixing the following security issues:
 - Buffer overflow in client/mysql.cc (Closes: #737597).
   - CVE-2014-0001
 - http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html
   - CVE-2013-5891
   - CVE-2013-5908
   - CVE-2014-0386
   - CVE-2014-0393
   - CVE-2014-0401
   - CVE-2014-0402
   - CVE-2014-0412
   - CVE-2014-0420
   - CVE-2014-0437
   * Upstream https://mariadb.atlassian.net/browse/MDEV-4902
 fixes compatibility with Bison 3.0 (Closes: #733002)
   * Updated Russian debconf translation (Closes: #734426)
   * Updated Japanese debconf translation (Closes: #735284)
   * Updated French debconf translation (Closes: #736480)
   * Renamed SONAME properly (Closes: #732967)
Checksums-Sha1: 
 aec5b5c77d545f642c49188e5f0551621ffee674 2944 mariadb-5.5_5.5.35-1.dsc
 b0587452283bbe9b27e222ab76e52c9c78fe9222 43926514 
mariadb-5.5_5.5.35.orig.tar.gz
 14278348bab9e3eab57f0adb1bf2cd68962d7e65 177524 
mariadb-5.5_5.5.35-1.debian.tar.xz
 eb470b5c5b205b522f1f0b2d62015c18045c8b1c 11000 mariadb-common_5.5.35-1_all.deb
 

Bug#732967: marked as done (libmariadbclient18: wrong soname)

2014-02-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Feb 2014 09:21:44 +
with message-id e1wfgs4-0006rl...@franck.debian.org
and subject line Bug#732967: fixed in mariadb-5.5 5.5.35-1
has caused the Debian Bug report #732967,
regarding libmariadbclient18: wrong soname
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.)


-- 
732967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libmariadbclient18
Version: 5.5.32-1
Severity: serious

The soname for libmariadbclient is wrong as lintian notices:

package-name-doesnt-match-sonames libmysqlclient18
ldconfig-symlink-missing-for-shlib usr/lib/i386-linux-gnu/libmysqlclient.so.18 
usr/lib/i386-linux-gnu/libmariadbclient.so.18.0.0 libmysqlclient.so.18

Ansgar
---End Message---
---BeginMessage---
Source: mariadb-5.5
Source-Version: 5.5.35-1

We believe that the bug you reported is fixed in the latest version of
mariadb-5.5, which is due to be installed in the Debian FTP archive.

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 732...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Page jamesp...@debian.org (supplier of updated mariadb-5.5 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Feb 2014 16:51:52 +
Source: mariadb-5.5
Binary: libmariadbclient18 libmariadbd-dev libmariadbclient-dev mariadb-common 
mariadb-client-core-5.5 mariadb-client-5.5 mariadb-server-core-5.5 
mariadb-test-5.5 mariadb-server-5.5 mariadb-server mariadb-client mariadb-test
Architecture: source all amd64
Version: 5.5.35-1
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org
Changed-By: James Page jamesp...@debian.org
Description: 
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database development files
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-5.5 - MariaDB database client binaries
 mariadb-client-core-5.5 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-5.5 - MariaDB database server binaries
 mariadb-server-core-5.5 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite (metapackage for the 
lates
 mariadb-test-5.5 - MariaDB database regression test suite
Closes: 732967 733002 734426 735284 736480 737597
Changes: 
 mariadb-5.5 (5.5.35-1) unstable; urgency=low
 .
   [ Otto Kekäläinen ]
   * New upstream release, fixing the following security issues:
 - Buffer overflow in client/mysql.cc (Closes: #737597).
   - CVE-2014-0001
 - http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html
   - CVE-2013-5891
   - CVE-2013-5908
   - CVE-2014-0386
   - CVE-2014-0393
   - CVE-2014-0401
   - CVE-2014-0402
   - CVE-2014-0412
   - CVE-2014-0420
   - CVE-2014-0437
   * Upstream https://mariadb.atlassian.net/browse/MDEV-4902
 fixes compatibility with Bison 3.0 (Closes: #733002)
   * Updated Russian debconf translation (Closes: #734426)
   * Updated Japanese debconf translation (Closes: #735284)
   * Updated French debconf translation (Closes: #736480)
   * Renamed SONAME properly (Closes: #732967)
Checksums-Sha1: 
 aec5b5c77d545f642c49188e5f0551621ffee674 2944 mariadb-5.5_5.5.35-1.dsc
 b0587452283bbe9b27e222ab76e52c9c78fe9222 43926514 
mariadb-5.5_5.5.35.orig.tar.gz
 14278348bab9e3eab57f0adb1bf2cd68962d7e65 177524 
mariadb-5.5_5.5.35-1.debian.tar.xz
 eb470b5c5b205b522f1f0b2d62015c18045c8b1c 11000 mariadb-common_5.5.35-1_all.deb
 42e50fd609f9a6033a27dcb3ea78675baaff4abf 11108 mariadb-server_5.5.35-1_all.deb
 20467e63f62d1e408366a7c75fb9a14369af54b8 10974 mariadb-client_5.5.35-1_all.deb
 da10e116a5d3d1ffdeb0e04eef85207d9755ccd3 10928 mariadb-test_5.5.35-1_all.deb
 8b53d6ebb7d7ae37fbb87c419f89eeedbee16e51 544708 
libmariadbclient18_5.5.35-1_amd64.deb
 cacf36bed74512abd732a162e773ec4f03bd7c99 6870868 
libmariadbd-dev_5.5.35-1_amd64.deb
 

Bug#739140: [Pkg-xfce-devel] Bug#739140: xfce4-notes: Notes fail to save upon exit program

2014-02-18 Thread Orthogonal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 18/02/14 17:10, Yves-Alexis Perez wrote:
 [please keep the bug on CC:] On Tue, Feb 18, 2014 at 04:18:47PM
 +1100, Orthogonal wrote:
 I just tested it in the 'Awesome' window manager, and it worked
 there. I've had other problems when doing things like this in
 xfce before, so the problem seems to be specific to my
 configuration, as opposed to your package. Sorry for that. :)
 
 What do you mean “things like this”? Because xfce4-notes is pretty
 much made for beeing used under Xfce…
 
 Regards,
 
I meant that I seem to have somehow messed up my config files,
dependencies, or something like that. I'm using sid, so maybe that
contributed too. I ran the program from the command line, instead of
the panel, if that means anything.

In any case, the problem is now fixed after I took the following
steps: 1. apt-get dist-upgrade,
2. apt-get purge xfce4-notes xfce4-notes-plugin
3. apt-get install xfce4-notes xfce4-notes-plugin
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTAyG+AAoJEHQEl2F8Ns4axR8H/imKuaEK3T1NomHxrSTcHVyU
y8dcRJEjXadmAYSV7u5icNiazg/fZb352gvTXQQKiMI8Sirj0pRrOmcVmtPe5MAa
srkfJ4jRcnl5+v56U74F/cPY3RLIfkgjDebxlNArbEz7yaZoKQhpL1C7yshoQWhT
fbVIpptcFKiY6zv2tBFZ6+ATEmt6hJWqgzyrRGmVrl+81jaXIiZVwXMebX6N49+1
5sIpWu3Qhfd8iAmiGeSsNI5S5tdEnqYUhA+svnCl9fuFnmvN4W7Z6JniLnebRN/Q
DYQGtU0lYZvn2+ZZpoiMXYSyClIkRO328Ry1f8thSIxUOzE3LJq1vY7rLbLQQvo=
=twXZ
-END PGP SIGNATURE-


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



Processed: unarchiving 724487

2014-02-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 unarchive 724487
Bug #724487 {Done: Rémi Vanicat vani...@debian.org} [src:xmms2] xmms2: FTBFS: 
fatal error: modplug.h: No such file or directory
Unarchived Bug 724487

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
724487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#737448: [src:orthanc ] Sourceless file (minified)

2014-02-18 Thread Sebastien Jodogne

Hello Andreas,


Am I allowed to create symbolic links in the
override_dh_auto_configure sections?


Sure:

override_dh_auto_configure
# either do symlink or use some compression of the source
# files to the place you need here
dh_auto_configure ...



Thanks to your helpful explanations, I think I have solved this bug 
together with the packaging of the new upstream version 0.7.3 of Orthanc 
[1]. The proper Files-Excluded directive is included in the copyright 
file [2], so that there remains only non-minified JavaScript files from 
the source package. Minified JavaScript files are re-generated using 
yui-compressor [3].


However, I would need an independent review to be sure that I have 
properly fixed the package. In particular, I had to introduce the 
+dfsg suffix to the package version: I am unsure whether this is the 
proper way of doing things.


Would you kindly have a look at my modifications, possibly uploading it 
if everything is OK?


Regards,
Sébastien-


[1] 
http://anonscm.debian.org/viewvc/debian-med/trunk/packages/orthanc/trunk/debian/JS/
[2] 
http://anonscm.debian.org/viewvc/debian-med/trunk/packages/orthanc/trunk/debian/copyright?view=markup
[3] 
http://anonscm.debian.org/viewvc/debian-med/trunk/packages/orthanc/trunk/debian/rules?view=markup 
(line 25)



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



Bug#724487: xmms2: FTBFS: fatal error: modplug.h: No such file or directory

2014-02-18 Thread Moritz Mühlenhoff
 Damyan Ivanov d...@debian.org writes:
  Package: src:xmms2
  Version: 0.8+dfsg-6
  Severity: serious
  Justification: FTBFS
 
  xmms2 fails to build in a clean current sid pbuilder chroot:
 [...]
 
 This seem to be related to a change in libmodplug[1], I've asked them
 for precision, and will wrote a patch soon.

This also affects stable, it fails to build from source as well:

h/wheezy/xm/xmms2-0.8+dfsg/src/include', '-I/usr/include/SDL', '-
I/usr/include/libvisual-0.4', '-D_GNU_SOURCE=1', '-D_REENTRANT', 
'../src/clients/vistest/libvisual.c', '-c', '-o', 
'src/clients/vistest/libvisual.c.4.o']
../src/plugins/modplug/modplug.c:12:21: fatal error: modplug.h: Datei oder 
Verzeichnis nicht gefunden
[107/319] c: src/plugins/curl/curl_http.c - 
_build_/src/plugins/curl/curl_http.c.1.o
compilation terminated.
11:13:45 runner ['/usr/bin/gcc', '-g', '-O0', '-Wall', '-Wempty-body', '-
Wformat=2', '-Wformat-nonliteral', '-Wformat-security', '-Wignored-qualifiers', 
'-Wmissing-prototypes', '-Wstrict-prototypes', '-Wtype-limits', '-Wwrite-
strings', '-Wno-format-extra-args', '-Wno-format-zero-length', '-fdiagnostics-
show-option', '-Werror=implicit-function-declaration', '-fPIC', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_/src/include', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/src/include', '-
I/usr/include/glib-2.0', '-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', 
'../src/plugins/curl/curl_http.c', '-c', '-o', 
'src/plugins/curl/curl_http.c.1.o']
[108/319] c: src/plugins/tta/tta.c - _build_/src/plugins/tta/tta.c.1.o
11:13:46 runner ['/usr/bin/gcc', '-g', '-O0', '-Wall', '-Wempty-body', '-
Wformat=2', '-Wformat-nonliteral', '-Wformat-security', '-Wignored-qualifiers', 
'-Wmissing-prototypes', '-Wstrict-prototypes', '-Wtype-limits', '-Wwrite-
strings', '-Wno-format-extra-args', '-Wno-format-zero-length', '-fdiagnostics-
show-option', '-Werror=implicit-function-declaration', '-fPIC', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_/src/include', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/src/include', '-
I/usr/include/glib-2.0', '-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', 
'../src/plugins/tta/tta.c', '-c', '-o', 'src/plugins/tta/tta.c.1.o']
[109/319] c: src/xmms/main.c - _build_/src/xmms/main.c.12.o
11:13:46 runner ['/usr/bin/gcc', '-g', '-O0', '-Wall', '-Wempty-body', '-
Wformat=2', '-Wformat-nonliteral', '-Wformat-security', '-Wignored-qualifiers', 
'-Wmissing-prototypes', '-Wstrict-prototypes', '-Wtype-limits', '-Wwrite-
strings', '-Wno-format-extra-args', '-Wno-format-zero-length', '-fdiagnostics-
show-option', '-Werror=implicit-function-declaration', '-pthread', '-pthread', 
'-pthread', '-pthread', '-pthread', '-pthread', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_/src/xmms', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/src/xmms', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_/src/include', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/src/include', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_/src/includepriv', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/src/includepriv', '-
I/usr/include/glib-2.0', '-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', '-
I/usr/include/valgrind', '-D_SEM_SEMUN_UNDEFINED', '../src/xmms/main.c', '-c', 
'-o', 'src/xmms/main.c.12.o']
../src/plugins/curl/curl_http.c: In function ‘header_handler_contentlength’:
../src/plugins/curl/curl_http.c:536:20: warning: variable ‘data’ set but not 
used [-Wunused-but-set-variable]
Waf: Leaving directory `/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_'
Build failed
 - task failed (exit status 1): 
{task 40762448: c modplug.c - modplug.c.1.o}
['/usr/bin/gcc', '-g', '-O0', '-Wall', '-Wempty-body', '-Wformat=2', '-
Wformat-nonliteral', '-Wformat-security', '-Wignored-qualifiers', '-Wmissing-
prototypes', '-Wstrict-prototypes', '-Wtype-limits', '-Wwrite-strings', '-Wno-
format-extra-args', '-Wno-format-zero-length', '-fdiagnostics-show-option', '-
Werror=implicit-function-declaration', '-fPIC', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/_build_/src/include', '-
I/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg/src/include', '-
I/usr/include/glib-2.0', '-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', 
'../src/plugins/modplug/modplug.c', '-c', '-o', 
'src/plugins/modplug/modplug.c.1.o']
make[1]: *** [override_dh_auto_build] Fehler 1
make[1]: Leaving directory `/home/jmm/scratch/wheezy/xm/xmms2-0.8+dfsg'
make: *** [build] Fehler 2
dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2



I'm attaching a patch for Wheezy (identical with your patch for 

Bug#737448: [src:orthanc ] Sourceless file (minified)

2014-02-18 Thread Andreas Tille
Hi Sebastien,

On Tue, Feb 18, 2014 at 11:27:08AM +0100, Sebastien Jodogne wrote:
 
 
 Thanks to your helpful explanations, I think I have solved this bug
 together with the packaging of the new upstream version 0.7.3 of
 Orthanc [1]. The proper Files-Excluded directive is included in
 the copyright file [2], so that there remains only non-minified
 JavaScript files from the source package. Minified JavaScript files
 are re-generated using yui-compressor [3].
 
 However, I would need an independent review to be sure that I have
 properly fixed the package. In particular, I had to introduce the
 +dfsg suffix to the package version: I am unsure whether this is
 the proper way of doing things.

Without having checked the package this sounds pretty expected since it
is what uscan is doing for you according to best practices when there is
any need to rebuild the package source tarball to follow DFSG.
 
 Would you kindly have a look at my modifications, possibly uploading
 it if everything is OK?

I'm a bit in a hurry today and will be offline tomorrow.  Perhaps
pinging on the list might make sense.

Kind regards

   Andreas. 

-- 
http://fam-tille.de


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



Bug#739409: [ocl-icd-libopencl1] Broken symbols file

2014-02-18 Thread bastien ROUCARIES
Package: ocl-icd-libopencl1
Version: 2.1.3-4
Severity: serious


Your symbols file is broken and allow to install non free package.


12:06:33) _rene_: libopencl-1.1-1) AND libopencl-1.1-1 itself?!
(12:07:04) _rene_: without looking at the source the former sounds like 
dh_shlibdeps' result and the latter one bogus :)
(12:07:21) _rene_: oh, even better:
(12:07:43) jcristau: broucarie: i have no idea what you're trying to say
(12:08:22) _rene_: Depends: [...] libopencl-1.1-1 [!x32], libopencl1 [x32], 
[...]. ocl-icd-libopencl1 | libopencl1 
(12:08:34) _rene_: that's umm. no comment
(12:09:18) jcristau: broucarie: the bug is in ocl-icd-libopencl1ls file is 
broken and allow non free package during upgrade
(12:09:26) jcristau: its symbols file is fucked up
(12:12:37) broucarie: jcristau: How should I report it ? How do you know the 
symbols file is fucked up ?
(12:13:16) jekhor a quitté le salon (quit: Ping timeout: 480 seconds)
(12:14:12) _rene_: by looking at it
(12:14:17) _rene_: libOpenCL.so.1 ocl-icd-libopencl1 #MINVER# | libopencl1
(12:14:17) _rene_: | ocl-icd-libopencl1 #MINVER# | libopencl1, libopencl-1.1-1
(12:14:28) _rene_: note the | libopencl1, libopencl-1.1-1
(12:14:36) _rene_: which is those virtual packages...
(12:15:37) _rene_: and even the | libopencl1 in the fist line. and the third 
(no idea what that means, need to look it up) is | ocl-icd-libopencl1 #MINVER# 
| libopencl1, libopencl-1.2-1
(12:16:01) _rene_: so yes, .symbols is broken, it should not magically allow 
non-free packages
(12:16:08) _rene_: or virtual ones, for that matter

Thank

Bastien


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



Bug#739410: mpd: new version fails to update with apt-get update

2014-02-18 Thread Sharon Kimble
Package: mpd
Version: 0.18.7-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Tried to update to version 0.18.8-1 today and it fails to install giving a dpkg
error code of 1.

Reading changelogs... Done
(Reading database ... 461516 files and directories currently installed.)
Preparing to unpack .../archives/mpd_0.18.8-1_i386.deb ...
/etc/init.d/mpd: 448: /etc/default/mpd: filesystem_charset: not found
[ ok ] Stopping Music Player Daemon: mpd.
/var/lib/dpkg/tmp.ci/preinst: 448: /etc/default/mpd: filesystem_charset: not
found
dpkg: error processing archive /var/cache/apt/archives/mpd_0.18.8-1_i386.deb
(--unpack):
 subprocess new pre-installation script returned error exit status 127
insserv: script vboxdrv: service vboxdrv already provided!
/etc/init.d/mpd: 448: /etc/default/mpd: filesystem_charset: not found
[info] Not starting MPD: disabled by /etc/default/mpd..
Errors were encountered while processing:
 /var/cache/apt/archives/mpd_0.18.8-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

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

Versions of packages mpd depends on:
ii  adduser   3.113+nmu3
ii  init-system-helpers   1.14
ii  libadplug-2.2.1-0 2.2.1+dfsg3-0.1
ii  libao41.1.0-2
ii  libasound21.0.27.2-3
ii  libaudiofile1 0.3.6-2
ii  libavahi-client3  0.6.31-4
ii  libavahi-common3  0.6.31-4
ii  libavcodec54  6:9.11-1
ii  libavformat54 6:9.11-1
ii  libavutil52   6:9.11-1
ii  libbz2-1.01.0.6-5
ii  libc6 2.17-97
ii  libcdio-cdda1 0.83-4.1
ii  libcdio-paranoia1 0.83-4.1
ii  libcdio13 0.83-4.1
ii  libcurl3-gnutls   7.35.0-1
ii  libfaad2  2.7-8
ii  libflac8  1.3.0-2
ii  libfluidsynth11.1.6-2
ii  libgcc1   1:4.8.2-15
ii  libglib2.0-0  2.36.4-1
ii  libgme0   0.5.5-2
ii  libid3tag00.15.1b-10
ii  libiso9660-8  0.83-4.1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.9.5+20130622git7de15e7a-1
ii  libmad0   0.15.1b-8
ii  libmikmod23.1.16-1
ii  libmms0   0.6.2-3
ii  libmodplug1   1:0.8.8.4-4
ii  libmp3lame0   3.99.5+repack1-3
ii  libmpcdec62:0.1~r459-4
ii  libmpdclient2 2.9-1
ii  libmpg123-0   1.16.0-1
ii  libogg0   1.3.1-1
ii  libopenal11:1.14-4
ii  libopus0  1.1-1
ii  libpulse0 4.0-6+b1
ii  libresid-builder0c2a  2.1.1-14
ii  libroar2  1.0~beta11-1
ii  libsamplerate00.1.8-7
ii  libshout3 2.3.1-3
ii  libsidplay2   2.1.1-14
ii  libsidutils0  2.1.1-14
ii  libsndfile1   1.0.25-9
ii  libsqlite3-0  3.8.2-1
ii  libstdc++64.8.2-15
ii  libsystemd-daemon0204-6
ii  libvorbis0a   1.3.2-1.3
ii  libvorbisenc2 1.3.2-1.3
ii  libvorbisfile31.3.2-1.3
ii  libwavpack1   4.70.0-1
ii  libwildmidi1  0.2.3.4-2.1
ii  libwrap0  7.6.q-25
ii  libyajl2  2.0.4-4
ii  libzzip-0-13  0.13.62-2
ii  lsb-base  4.1+Debian12

mpd recommends no packages.

Versions of packages mpd suggests:
ii  ario [mpd-client]1.5.1-1.1
ii  avahi-daemon 0.6.31-4
ii  glurp [mpd-client]   0.12.3-1
pn  icecast2 none
ii  mpc [mpd-client] 0.25-1
ii  ncmpc [mpd-client]   0.17-1
ii  ncmpcpp [mpd-client] 0.5.10-1.1
ii  pulseaudio   4.0-6+b1
ii  qmpdclient [mpd-client]  1.2.2-2

-- Configuration Files:
/etc/default/mpd changed:
filesystem_charset  UTF-8

/etc/init.d/mpd changed:
.. /lib/lsb/init-functions
PATH=/sbin:/bin:/usr/sbin:/usr/bin
NAME=mpd
DESC=Music Player Daemon
DAEMON=/usr/bin/mpd
MPDCONF=/home/boudiccas/.mpd/mpd.conf
START_MPD=false
[ -x $DAEMON ] || exit 0
[ -r /etc/default/$NAME ]  . /etc/default/$NAME
if [ -n $MPD_DEBUG ]; then
set -x
MPD_OPTS=--verbose
fi
DBFILE=$(sed -n 's/^[[:space:]]*db_file[[:space:]]*\?\([^]*\)\\?/\1/p' 
$MPDCONF)

Bug#739410: mpd: new version fails to update with apt-get update

2014-02-18 Thread Max Kellermann
On 2014/02/18 12:31, Sharon Kimble boudic...@talktalk.net wrote:
 Tried to update to version 0.18.8-1 today and it fails to install giving a 
 dpkg
 error code of 1.

It appears your /etc/default/mpd contains garbage that belongs in
/etc/mpd.conf, but I don't see anything in the new package that would
cause garbage to be added to /etc/default/mpd.  Are you sure this was
added by the package and not by yourself?  What does your
/etc/default/mpd look like?


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



Bug#739410: mpd: new version fails to update with apt-get update

2014-02-18 Thread Max Kellermann
On 2014/02/18 13:06, Sharon Kimble boudic...@talktalk.net wrote:
 On Tue, 18 Feb 2014 12:40:23 +0100
 Max Kellermann m...@duempel.org wrote:
 
  On 2014/02/18 12:31, Sharon Kimble boudic...@talktalk.net wrote:
   Tried to update to version 0.18.8-1 today and it fails to install
   giving a dpkg error code of 1.
  
  It appears your /etc/default/mpd contains garbage that belongs in
  /etc/mpd.conf, but I don't see anything in the new package that would
  cause garbage to be added to /etc/default/mpd.  Are you sure this was
  added by the package and not by yourself?  What does your
  /etc/default/mpd look like?
 
 I've attached my /etc/default/mpd = blank, not used, /etc/mpd.conf =
 blank, not used, and /home/$USER/cron/conf/mpd.conf = which is used. 

Not true.  Your /etc/default/mpd is not blank.  It contains the same
data as your mpd.conf, which is a mistake.  This cannot work.

This bug report is bogus, unless you can demonstrate the the package
has wrongfully copied your /etc/mpd.conf to /etc/default/mpd.


-- 
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#738857: mupdf: Stack-based Buffer Overflow in xps_parse_color()

2014-02-18 Thread Debian Bug Tracking System
Processing control commands:

 retitle -1 mupdf: CVE-2014-2013: Stack-based Buffer Overflow in 
 xps_parse_color()
Bug #738857 [mupdf] mupdf: Stack-based Buffer Overflow in xps_parse_color()
Changed Bug title to 'mupdf: CVE-2014-2013: Stack-based Buffer Overflow in 
xps_parse_color()' from 'mupdf: Stack-based Buffer Overflow in 
xps_parse_color()'

-- 
738857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#738857: mupdf: Stack-based Buffer Overflow in xps_parse_color()

2014-02-18 Thread Salvatore Bonaccorso
Control: retitle -1 mupdf: CVE-2014-2013: Stack-based Buffer Overflow in 
xps_parse_color()

Hi,

CVE-2014-2013 was assigned for this issue.

Regards,
Salvatore


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



Bug#739410: marked as done (mpd: new version fails to update with apt-get update)

2014-02-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Feb 2014 13:22:30 +0100
with message-id 20140218122230.ga12...@swift.blarg.de
and subject line Re: Bug#739410: mpd: new version fails to update with apt-get 
update
has caused the Debian Bug report #739410,
regarding mpd: new version fails to update with apt-get update
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.)


-- 
739410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: mpd
Version: 0.18.7-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Tried to update to version 0.18.8-1 today and it fails to install giving a dpkg
error code of 1.

Reading changelogs... Done
(Reading database ... 461516 files and directories currently installed.)
Preparing to unpack .../archives/mpd_0.18.8-1_i386.deb ...
/etc/init.d/mpd: 448: /etc/default/mpd: filesystem_charset: not found
[ ok ] Stopping Music Player Daemon: mpd.
/var/lib/dpkg/tmp.ci/preinst: 448: /etc/default/mpd: filesystem_charset: not
found
dpkg: error processing archive /var/cache/apt/archives/mpd_0.18.8-1_i386.deb
(--unpack):
 subprocess new pre-installation script returned error exit status 127
insserv: script vboxdrv: service vboxdrv already provided!
/etc/init.d/mpd: 448: /etc/default/mpd: filesystem_charset: not found
[info] Not starting MPD: disabled by /etc/default/mpd..
Errors were encountered while processing:
 /var/cache/apt/archives/mpd_0.18.8-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

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

Versions of packages mpd depends on:
ii  adduser   3.113+nmu3
ii  init-system-helpers   1.14
ii  libadplug-2.2.1-0 2.2.1+dfsg3-0.1
ii  libao41.1.0-2
ii  libasound21.0.27.2-3
ii  libaudiofile1 0.3.6-2
ii  libavahi-client3  0.6.31-4
ii  libavahi-common3  0.6.31-4
ii  libavcodec54  6:9.11-1
ii  libavformat54 6:9.11-1
ii  libavutil52   6:9.11-1
ii  libbz2-1.01.0.6-5
ii  libc6 2.17-97
ii  libcdio-cdda1 0.83-4.1
ii  libcdio-paranoia1 0.83-4.1
ii  libcdio13 0.83-4.1
ii  libcurl3-gnutls   7.35.0-1
ii  libfaad2  2.7-8
ii  libflac8  1.3.0-2
ii  libfluidsynth11.1.6-2
ii  libgcc1   1:4.8.2-15
ii  libglib2.0-0  2.36.4-1
ii  libgme0   0.5.5-2
ii  libid3tag00.15.1b-10
ii  libiso9660-8  0.83-4.1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.9.5+20130622git7de15e7a-1
ii  libmad0   0.15.1b-8
ii  libmikmod23.1.16-1
ii  libmms0   0.6.2-3
ii  libmodplug1   1:0.8.8.4-4
ii  libmp3lame0   3.99.5+repack1-3
ii  libmpcdec62:0.1~r459-4
ii  libmpdclient2 2.9-1
ii  libmpg123-0   1.16.0-1
ii  libogg0   1.3.1-1
ii  libopenal11:1.14-4
ii  libopus0  1.1-1
ii  libpulse0 4.0-6+b1
ii  libresid-builder0c2a  2.1.1-14
ii  libroar2  1.0~beta11-1
ii  libsamplerate00.1.8-7
ii  libshout3 2.3.1-3
ii  libsidplay2   2.1.1-14
ii  libsidutils0  2.1.1-14
ii  libsndfile1   1.0.25-9
ii  libsqlite3-0  3.8.2-1
ii  libstdc++64.8.2-15
ii  libsystemd-daemon0204-6
ii  libvorbis0a   1.3.2-1.3
ii  libvorbisenc2 1.3.2-1.3
ii  libvorbisfile31.3.2-1.3
ii  libwavpack1   4.70.0-1
ii  libwildmidi1  0.2.3.4-2.1
ii  libwrap0  7.6.q-25
ii  libyajl2  2.0.4-4
ii  libzzip-0-13  0.13.62-2
ii  lsb-base  4.1+Debian12

mpd recommends no packages.


Bug#739370: the problem hasn't been resolved

2014-02-18 Thread Raf Czlonka
On Tue, Feb 18, 2014 at 08:06:42AM GMT, Andrew Shadura wrote:

 Hello,

Hi,

 Yes, that's true; I don't currently know how to solve that issue
 properly. I've added a check in preinst script to remove that bogus
 directory, but that won't help with removing broken versions of the
 package co-installed with pkg-config: the only way to fix them is to
 upgrade then to a new version (or to fix the issue manually).

Such, such check (like the one below) will only work if the package is
upgraded, not removed. Broken packages can only be fixed by manua
intervention when a user decides to purge them from the system, rather
than trying to install to a newer version.

Something like this would at least allow users to get passed the broken
package state, install the new version and, if they choose to do so,
remove the package from their system using apt/dpkg.

pkgconfwrap=/usr/share/pkg-config-crosswrapper
[ -f $pkgconfwrap/pkg-config-crosswrapper ]  mv 
$pkgconfwrap/pkg-config-crosswrapper ${pkgconfwrap}.orig
[ -d $pkgconfwrap ]  rmdir $pkgconfwrap  mv ${pkgconfwrap}.orig $pkgconfwrap

Variable has been used for brevity but feel free to expand it.

Since both, the script and the directory are created by an earlier
version of 'pkgconf' package, it is safe to assume that '.orig' file
does not exist and the directory is empty, hence the lack of any
additional tests in the above example.

Regards,

Raf


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



Bug#737017: marked as done (libgupnp-1.0-dev: should depend on uuid-dev)

2014-02-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Feb 2014 13:31:58 +0100
with message-id 20140218123153.ga14...@pi.fatal.se
and subject line fixed gupnp dev package in unstable
has caused the Debian Bug report #737017,
regarding libgupnp-1.0-dev: should depend on uuid-dev
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.)


-- 
737017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libgupnp-1.0-dev
Version: 0.20.9-1
Severity: normal
File: /usr/lib/pkgconfig/gupnp-1.0.pc

After installing farstream-0.2's build-dependencies in a chroot:

 archetype(sid-amd64)% pkg-config --cflags  gupnp-igd-1.0 = 0.2 
 Package uuid was not found in the pkg-config search path.
 Perhaps you should add the directory containing `uuid.pc'
 to the PKG_CONFIG_PATH environment variable
 Package 'uuid', required by 'gupnp-1.0', not found

libgupnp-1.0-dev should depend on uuid-dev (which I think Policy
might require in any case, so that static linking works).

Regards,
S

-- System Information:
Debian Release: jessie/sid
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libgupnp-1.0-dev depends on:
ii  gir1.2-gupnp-1.0  0.20.9-1
ii  libgssdp-1.0-dev  0.14.6-1
ii  libgupnp-1.0-40.20.9-1
ii  libsoup2.4-dev2.44.2-1
ii  libxml2-dev   2.9.1+dfsg1-3

Versions of packages libgupnp-1.0-dev recommends:
ii  python  2.7.5-5

Versions of packages libgupnp-1.0-dev suggests:
pn  libgupnp-doc  none

-- no debconf information
---End Message---
---BeginMessage---
Package: libgupnp-1.0-dev
Version: 0.20.10-1

Fixed in latest upload to unstable.---End Message---


Bug#739409: [ocl-icd-libopencl1] Broken symbols file

2014-02-18 Thread Vincent Danjean
severity 739409 normal
thanks

On 18/02/2014 13:24, bastien ROUCARIES wrote:
 Package: ocl-icd-libopencl1
 Version: 2.1.3-4
 Severity: serious
 
 Your symbols file is broken

We will discuss about this below

 and allow to install non free package.

This is by design.

So, I downgraded this bug report for now. I will try to explain
you the situation for this library and we will see if we must
close this bug or fix something in the package.

 12:06:33) _rene_: libopencl-1.1-1) AND libopencl-1.1-1 itself?!
 (12:07:04) _rene_: without looking at the source the former sounds like 
 dh_shlibdeps' result and the latter one bogus :)
 (12:07:21) _rene_: oh, even better:
 (12:07:43) jcristau: broucarie: i have no idea what you're trying to say
 (12:08:22) _rene_: Depends: [...] libopencl-1.1-1 [!x32], libopencl1 [x32], 
 [...]. ocl-icd-libopencl1 | libopencl1

The mention of x32 seems strange to me here. Can you provide
me more context so that I understand it (there is nothing
about x32 in the source package).

 (12:08:34) _rene_: that's umm. no comment
 (12:09:18) jcristau: broucarie: the bug is in ocl-icd-libopencl1ls file is 
 broken and allow non free package during upgrade
 (12:09:26) jcristau: its symbols file is fucked up
 (12:12:37) broucarie: jcristau: How should I report it ? How do you know the 
 symbols file is fucked up ?
 (12:13:16) jekhor a quitté le salon (quit: Ping timeout: 480 seconds)
 (12:14:12) _rene_: by looking at it
 (12:14:17) _rene_: libOpenCL.so.1 ocl-icd-libopencl1 #MINVER# | libopencl1
 (12:14:17) _rene_: | ocl-icd-libopencl1 #MINVER# | libopencl1, libopencl-1.1-1
 (12:14:28) _rene_: note the | libopencl1, libopencl-1.1-1
 (12:14:36) _rene_: which is those virtual packages...
 (12:15:37) _rene_: and even the | libopencl1 in the fist line. and the third 
 (no idea what that means, need to look it up) is | ocl-icd-libopencl1 
 #MINVER# | libopencl1, libopencl-1.2-1
 (12:16:01) _rene_: so yes, .symbols is broken, it should not magically allow 
 non-free packages
 (12:16:08) _rene_: or virtual ones, for that matter

Back to the background.
First, read 
http://anonscm.debian.org/gitweb/?p=collab-maint/ocl-icd.git;a=blob;f=debian/README.Debian;hb=HEAD
It was written a few months ago and should probably be updated a bit
but important information are present.

For this bug report:
* OpenCL is a norm written by a consortium: we have to deal with (bad) design
  of this consortium
* OpenCL implementations are divided in several parts, mainly:
  * libOpenCL : the library applications link against (that load ICDs)
  * ICDs : real OpenCL drivers (to execute code on various hardware)
  libOpenCL is mainly a dispatcher of function calls to one or more
  ICDs
* ICDs in Debian are all currently non-free. I hope to find time to
  finish the packaging of pocl (current state in collab-maint, help
  welcome) so that a free ICD is available
* libOpenCL is provided by non-free OpenCL implementations (mainly AMD,
  NVidia and Intel) but also by an independant free project: ocl-icd
* All libOpenCL library should be equivalent (ie work with any ICD)
  = all packaged ones in Debian provides/conflict with the virtual package 
libopencl1
  but consortium's decision mitigate this (hence the existence of other virtual 
packages, see below)


When you package a OpenCL application with the ocl-icd libOpenCL
packaged in Debian, the goal is to depends on ocl-icd (free implementation)
but also on virtual package as alternative, so that one can use
other (non-free) implementation if they wish. Putting ocl-icd as
the first part of the alternative is done so that, by default,
apt and other tools will install the free alternative (if non-free
is enabled)

The symbol file is written like this (stripping out the comments, adding line 
numbers) :
1: libOpenCL.so.1 #PACKAGE# #MINVER# | libopencl1
2: | #PACKAGE# #MINVER# | libopencl1, libopencl-1.1-1
3: | #PACKAGE# #MINVER# | libopencl1, libopencl-1.2-1
4:  (symver|optional)OPENCL_1.0 1.0 1
5:  (symver|optional)OPENCL_1.1 1.0 1
6:  (symver|optional)OPENCL_1.2 1.0 2

The first line is always added as dependencies in all programs
linked with libOpenCL.so.1 (see #737731). If the consortium have done
correct design, this would be all what is needed.
We depends on the ocl-icd implementation or the virtual package for
user that will want to switch to a non-free implementation.

Line 2 and 3 are here to add the virtual packages libopencl-1.1-1
and libopencl-1.2-1. They are added when a program linked against
libOpenCL use symbols from the 1.0 or 1.1 version of the OpenCL
standard or the 1.2 version (2.0 will probably come soon).
  Note that correct design should have use different sonames. It would
have been easiest as we have to deal with several binaries
implementations (that have different versionning).

Currently, ocl-icd, AMD and Intel (not packaged due to licence)
provides an OpenCL library that deals with OpenCL version 1.0, 1.1 and 1.2.
NVidia only provides symbols for 1.0 and 

Processed: Re: Bug#739409: [ocl-icd-libopencl1] Broken symbols file

2014-02-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 739409 normal
Bug #739409 [ocl-icd-libopencl1] [ocl-icd-libopencl1] Broken symbols file
Severity set to 'normal' from 'serious'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
739409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#739140: marked as done (xfce4-notes: Notes fail to save upon exit program)

2014-02-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Feb 2014 14:14:47 +0100
with message-id 20140218131447.ga6...@scapa.corsac.net
and subject line Re: [Pkg-xfce-devel] Bug#739140: xfce4-notes: Notes fail to 
save upon exit program
has caused the Debian Bug report #739140,
regarding xfce4-notes: Notes fail to save upon exit program
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.)


-- 
739140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: xfce4-notes
Version: 1.7.7-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have found that when I quit the xfce4-notes program, my notes are not saved
when I next start it. If I edit the notes directly in ~/.local/share/notes ,
they are displayed at next entrance, however editing the files in this way
(instead of using the GUI) can get annoying, and can make the package almost
unusable.

Thanks for reading



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

Kernel: Linux 3.5.0-10-generic (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xfce4-notes depends on:
ii  libc6   2.17-96
ii  libcairo2   1.12.16-2
ii  libgdk-pixbuf2.0-0  2.28.2-1
ii  libglib2.0-02.36.4-1
ii  libgtk2.0-0 2.24.22-1
ii  libpango-1.0-0  1.36.0-1
ii  libunique-1.0-0 1.1.6-4
ii  libx11-62:1.6.2-1
ii  libxfce4util6   4.10.1-1
ii  libxfcegui4-4   4.10.0-2
ii  libxfconf-0-2   4.10.0-1

xfce4-notes recommends no packages.

xfce4-notes suggests no packages.

-- no debconf information
---End Message---
---BeginMessage---
On Tue, Feb 18, 2014 at 08:03:55PM +1100, Orthogonal wrote:
 In any case, the problem is now fixed after I took the following
 steps: 1. apt-get dist-upgrade,
 2. apt-get purge xfce4-notes xfce4-notes-plugin
 3. apt-get install xfce4-notes xfce4-notes-plugin

Ok, that looks like an eisenbug then. Closing.

Regards,
-- 
Yves-Alexis Perez---End Message---


Bug#739012: [php-maint] Bug#738832: Segmentation fault in libmagic (src:file) [CVE-2014-1943]

2014-02-18 Thread Lior Kaplan
On Sat, Feb 15, 2014 at 12:48 AM, Lior Kaplan kap...@debian.org wrote:

 The question is: do we want to patch this ourselves, or wait for PHP to
 provide the fix based on the linked commits? I guess the latter would be
 best, unless it will take them too much time.


Fix by upstream (from the PHP 5.4 branch):
http://git.php.net/?p=php-src.git;a=commitdiff;h=89f864c547014646e71862df3664e3ff33d7143d

Kaplan


Bug#739121: Creepy taking over in Debian GIS team maintenance

2014-02-18 Thread Daniel Echeverry
Hi Andreas


2014-02-16 15:48 GMT-05:00 Andreas Tille andr...@an3as.eu:

 Hi,

 I have injected the latest version of creepy into

git://anonscm.debian.org/pkg-grass/creepy.git

 which would fix #739121 since the latest upstream version does not
 depend from python-osmgpsmap any more.

 I would imagine to maintain the package in Debian GIS team since it is
 in the wider sense related to geographic information.  I think we could
 create a task tools or misc where this package could fit in.  So if
 everybody agrees upon this (on one hand the former maintainer Daniel and
 on the other hand the GIS team that this package might fit) I would
 upload the package as is (after about waiting one week).


Cool, I'd like some help to the new upstream release. Currently it has a
lot a problems, for example, it tries to write en /usr/share/creepy , the
new version write a log file and I don't know how to hand that.

Right now I've patched the source code to deny writing in /usr/share/creepy
the problem now is that when creepy tries to write plugins or project,
because it tries to write on /usr/share/creepy

I uploaded the creepy 1.1 with these changes to mentors[1] Could you check
it out? and tell me if I can help you with something


 Kind regards

   Andreas.

 --
 http://fam-tille.de



Regards
Daniel

[1]: http://mentors.debian.net/debian/pool/main/c/creepy/creepy_1.1-1.dsc

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
Linux user: #477840
Debian user
Software libre http://www.rinconinformatico.net


Bug#739370: the problem hasn't been resolved

2014-02-18 Thread Andrew Shadura
Hello,

On 18 February 2014 13:31, Raf Czlonka rafal.czlo...@gmail.com wrote:
 Yes, that's true; I don't currently know how to solve that issue
 properly. I've added a check in preinst script to remove that bogus
 directory, but that won't help with removing broken versions of the
 package co-installed with pkg-config: the only way to fix them is to
 upgrade then to a new version (or to fix the issue manually).

 Such, such check (like the one below) will only work if the package is
 upgraded, not removed. Broken packages can only be fixed by manua
 intervention when a user decides to purge them from the system, rather
 than trying to install to a newer version.

 Something like this would at least allow users to get passed the broken
 package state, install the new version and, if they choose to do so,
 remove the package from their system using apt/dpkg.

Actually, this is exactly what I added in a -3 version: it allows
users to unbreak things by upgrading the package.

-- 
Cheers,
  Andrew


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



Bug#739121: Creepy taking over in Debian GIS team maintenance

2014-02-18 Thread Andreas Tille
Hi Daniel,

On Tue, Feb 18, 2014 at 10:14:36AM -0500, Daniel Echeverry wrote:
 Hi Andreas
 
 
 2014-02-16 15:48 GMT-05:00 Andreas Tille andr...@an3as.eu:
 
  Hi,
 
  I have injected the latest version of creepy into
 
 git://anonscm.debian.org/pkg-grass/creepy.git

Hmmm, seems I missed to check mentors.d.n first ...

  which would fix #739121 since the latest upstream version does not
  depend from python-osmgpsmap any more.
 
  I would imagine to maintain the package in Debian GIS team since it is
  in the wider sense related to geographic information.  I think we could
  create a task tools or misc where this package could fit in.  So if
  everybody agrees upon this (on one hand the former maintainer Daniel and
  on the other hand the GIS team that this package might fit) I would
  upload the package as is (after about waiting one week).
 
 
 Cool, I'd like some help to the new upstream release. Currently it has a
 lot a problems, for example, it tries to write en /usr/share/creepy , the
 new version write a log file and I don't know how to hand that.
 
 Right now I've patched the source code to deny writing in /usr/share/creepy
 the problem now is that when creepy tries to write plugins or project,
 because it tries to write on /usr/share/creepy
 
 I uploaded the creepy 1.1 with these changes to mentors[1] Could you check
 it out? and tell me if I can help you with something

I wonder whether we should merge our efforts first.  Could you agree upon
the reporistory at

   git://anonscm.debian.org/pkg-grass/creepy.git

You get commit permission if you apply for pkg-grass team on alioth.

To my experience it becomes way more simple to work together on a
package when using a VCS rather than sending patches via mail.  It
also enables asking for help at debian-mentors list.

For your problem above:  I think you need to find the code piece that
tries to write to /usr/share/creepy and redirect the write attempts to
/var/lib/creepy.

Kind regards

Andreas.


 [1]: http://mentors.debian.net/debian/pool/main/c/creepy/creepy_1.1-1.dsc

-- 
http://fam-tille.de


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



Bug#739012: [php-maint] Bug#738832: Segmentation fault in libmagic (src:file) [CVE-2014-1943]

2014-02-18 Thread Salvatore Bonaccorso
Hi!

On Tue, Feb 18, 2014 at 04:58:08PM +0200, Lior Kaplan wrote:
 On Sat, Feb 15, 2014 at 12:48 AM, Lior Kaplan kap...@debian.org wrote:
 
  The question is: do we want to patch this ourselves, or wait for PHP to
  provide the fix based on the linked commits? I guess the latter would be
  best, unless it will take them too much time.
 
 
 Fix by upstream (from the PHP 5.4 branch):
 http://git.php.net/?p=php-src.git;a=commitdiff;h=89f864c547014646e71862df3664e3ff33d7143d

Thanks for the update and apologies for not replying earlier to the
bug. In addition Ondřej has already prepared packages for
squeeze-security and wheezy-security which currently are building.

Regards,
Salvatore


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



Bug#728245: severity of 728245 is important

2014-02-18 Thread Alexander Wirt
severity 728245 important
thanks

Hi,

as there are some problems to reproduce this bug in normal environments I
decided to downgrade that bug. Currently it prevents testing migration which
means that a few important security fixes won't get fixed in testing.

If someone disagrees, please speak up.

Alex


-- 
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 728245 is important

2014-02-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 728245 important
Bug #728245 [icinga-cgi] icinga-cgi: fails to install: subprocess installed 
post-installation script returned error exit status 1
Severity set to 'important' from 'serious'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
728245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#739121: Creepy taking over in Debian GIS team maintenance

2014-02-18 Thread Daniel Echeverry
Hi Andreas


2014-02-18 10:41 GMT-05:00 Andreas Tille andr...@an3as.eu:


 I wonder whether we should merge our efforts first.  Could you agree upon
 the reporistory at

git://anonscm.debian.org/pkg-grass/creepy.git

 You get commit permission if you apply for pkg-grass team on alioth.


I sent my  request to join the team :) once  to be accepted, I will make
the commits


 To my experience it becomes way more simple to work together on a
 package when using a VCS rather than sending patches via mail.  It
 also enables asking for help at debian-mentors list.

 For your problem above:  I think you need to find the code piece that
 tries to write to /usr/share/creepy and redirect the write attempts to
 /var/lib/creepy.


Yes you are right, however, the path where plugins, and other projects are
written, must be in the same part where creepy be installed, for this
reason, do not think just patch the code to write in /var/lib solve the
problem.

In fact I have discussed this issue with upstream, which says:

*Regarding 2, its obvious that the user who runs the program has no
permissions to write under /usr/share/creepy , should it be this way ?
Isn't that chowned to the user account in Debian ? If not, then we need to
find a different approach because the program needs to save projects and
plugin configurations, if it does not have the permission to write to that
directory , how could it be done ? *

Coul you give me  a hand? :)


 Kind regards

 Andreas.


  [1]:
 http://mentors.debian.net/debian/pool/main/c/creepy/creepy_1.1-1.dsc

 --
 http://fam-tille.de



Really, thank you very much for your help.

Regards
Daniel


-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
Linux user: #477840
Debian user
Software libre http://www.rinconinformatico.net


Bug#708486: marked as done (automake1.9-doc: Please get rid of install-info call in maint-script)

2014-02-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Feb 2014 16:04:01 +
with message-id e1wfn9n-0007zw...@franck.debian.org
and subject line Bug#708486: fixed in automake1.9-nonfree 1.9.6-1.1
has caused the Debian Bug report #708486,
regarding automake1.9-doc: Please get rid of install-info call in maint-script
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.)


-- 
708486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: automake1.9-doc
Source-Version: 1.9.6-1
Severity: important

Hi!

This packages calls install-info explicitly from a maintainer script [M],
but these are handled now by a trigger. Also as part of the transition
from the dpkg install-info to the GNU install-info [T], dpkg has
carried a compat wrapper, which will be disappearing with the next
dpkg 1.17.0 upload, at which point I'll rise the severity to serious
due to the program not being available at install time by default
anymore.

[M] http://lintian.debian.org/tags/install-info-used-in-maintainer-script.html
[T] http://wiki.debian.org/Transitions/DpkgToGnuInstallInfo

To fix this you should either simply rebuild with a newer debhelper if
using it, and/or remove any explicit install-info call in the
maintainer scripts.

(See also the thread I started in debian-devel [D].)

[D] http://lists.debian.org/debian-devel/2013/05/msg00243.html

Thanks,
Guillem
---End Message---
---BeginMessage---
Source: automake1.9-nonfree
Source-Version: 1.9.6-1.1

We believe that the bug you reported is fixed in the latest version of
automake1.9-nonfree, which is due to be installed in the Debian FTP archive.

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 708...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann a...@debian.org (supplier of updated automake1.9-nonfree 
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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 16 Feb 2014 16:38:04 +0100
Source: automake1.9-nonfree
Binary: automake1.9-doc
Architecture: source all
Version: 1.9.6-1.1
Distribution: unstable
Urgency: medium
Maintainer: Eric Dorland e...@debian.org
Changed-By: Andreas Beckmann a...@debian.org
Description: 
 automake1.9-doc - A tool for generating GNU Standards-compliant Makefiles
Closes: 708486
Changes: 
 automake1.9-nonfree (1.9.6-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild with newer debhelper to remove install-info calls from the
 maintainer scripts.  Add dummy empty prerm to ensure a clean upgrade path
 in case install-info has disappeared.  (Closes: #708486)
Checksums-Sha1: 
 c5879d087408d3a272829bebf7561f9b8cd8dcaa 1838 automake1.9-nonfree_1.9.6-1.1.dsc
 c997c813f838541b4dfb02534fb2d0372be5dda3 4510 
automake1.9-nonfree_1.9.6-1.1.diff.gz
 e153b3d076cadef4e9b0bd1e86c9a085e46389e3 220772 
automake1.9-doc_1.9.6-1.1_all.deb
Checksums-Sha256: 
 ad4d5f46f56cc61dda3b0055102789b9c7c696b676f05a9d6d0f8b4aa11dad95 1838 
automake1.9-nonfree_1.9.6-1.1.dsc
 d527bb208e4b48d16f97e5fac804653353427055422cc0da8ca8d0593c696e25 4510 
automake1.9-nonfree_1.9.6-1.1.diff.gz
 2163d65486fcf30e3adaddf1f0a72797abf3803b1529bcb918c41a9940c8509f 220772 
automake1.9-doc_1.9.6-1.1_all.deb
Files: 
 526f3594a6cb361a0a5fdba8bd97de30 1838 non-free/doc optional 
automake1.9-nonfree_1.9.6-1.1.dsc
 e28433bd84f43c10d5f9422c8ead8511 4510 non-free/doc optional 
automake1.9-nonfree_1.9.6-1.1.diff.gz
 2761ae511898191e605ce61a1261d1ca 220772 non-free/doc optional 
automake1.9-doc_1.9.6-1.1_all.deb

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

iQIcBAEBCAAGBQJTANyuAAoJEF+zP5NZ6e0IDfMP+wf+StNlu+xL4tv/fjAz1NGx
B9r54XdE+SihOHUUA88SBnJ5M2rSqszk3nLGfOgRximIFN1B5AUaec+7FsXH6get
3B/tNmM3Yw+zniuR2haPE0O1B313MVKR24U4KfTHzcEB3nrkQ625WGzwYyv5O0U4
Wkizz7gal4tii/APkAqLgcjdhjdaoZKXehnCDbmfFr2tMIyXTQP7kC0/J8aaHodC
ddR3K2IJcf2NCVGCE0gnYXlvES55HN3YJqflzlMwwY9ftEWxLEv4GZ2pS9y1V27y
++sdt2/26fB+eG4eRJIcnlqx/BKuNYSy3eoFdumcwhnFjtPX3yObY3CT+vbAuyQc
2NFd4JmHkVptuntDdIsV1IrtLa3ruXNhBuKHIXns4UIC2xzy8BNjJ8UW0P06Sg/X
srL4WN3fBiPHmCzi8lqvubAo7xUxxiVmx2KCv8k72c3/MO5nPm12K05WUCiQRp2+
TjXZ18GmOhL/Y5jiuVhLhfPEtICIUK4yNEsFRqQkn1LfztJr3GvqZbq7G6+oixVo

Bug#739121: Creepy taking over in Debian GIS team maintenance

2014-02-18 Thread Andreas Tille
Hi Daniel,

On Tue, Feb 18, 2014 at 11:03:53AM -0500, Daniel Echeverry wrote:
 git://anonscm.debian.org/pkg-grass/creepy.git
 
  You get commit permission if you apply for pkg-grass team on alioth.
 
 
 I sent my  request to join the team :) once  to be accepted, I will make
 the commits

Somebody else just adde you to the project. :-)
 
  To my experience it becomes way more simple to work together on a
  package when using a VCS rather than sending patches via mail.  It
  also enables asking for help at debian-mentors list.
 
  For your problem above:  I think you need to find the code piece that
  tries to write to /usr/share/creepy and redirect the write attempts to
  /var/lib/creepy.
 
 
 Yes you are right, however, the path where plugins, and other projects are
 written, must be in the same part where creepy be installed, for this
 reason, do not think just patch the code to write in /var/lib solve the
 problem.
 
 In fact I have discussed this issue with upstream, which says:
 
 *Regarding 2, its obvious that the user who runs the program has no
 permissions to write under /usr/share/creepy , should it be this way ?
 Isn't that chowned to the user account in Debian ? If not, then we need to
 find a different approach because the program needs to save projects and
 plugin configurations, if it does not have the permission to write to that
 directory , how could it be done ? *
 
 Coul you give me  a hand? :)

I admit I did never dealt with things like this.  I's suggest you finish
the commits and than ask on debian-ment...@lists.debian.org.  This list
is invented for questions like this.  I'm reading it and will comment as
well if I have any clue.

Thanks for your work on this

 Andreas.

-- 
http://fam-tille.de


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



Bug#739118: marked as done (blender: FTBFS on s390x (and other non-official 64-bit architectures))

2014-02-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Feb 2014 16:34:07 +
with message-id e1wfncv-0002xl...@franck.debian.org
and subject line Bug#739118: fixed in blender 2.69-4
has caused the Debian Bug report #739118,
regarding blender: FTBFS on s390x (and other non-official 64-bit architectures)
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.)


-- 
739118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: blender
Version: 2.69-3
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)

Since the default gcc has been upgraded to gcc-4.8, blender fails to
build on s390x, and on a few non-official architectures like ppc64 and
sparc64. This is due to a hardcoded list of architectures with 64-bit
pointers which has to be updated. The patch below fixes the issue:

--- blender-2.69.orig/intern/atomic/atomic_ops.h
+++ blender-2.69/intern/atomic/atomic_ops.h
@@ -61,7 +61,7 @@
 #  endif
 #endif
 
-#if defined(_M_X64) || defined(__amd64__) || defined(__x86_64__)
+#if defined(_M_X64) || defined(__amd64__) || defined(__x86_64__) || 
defined(__s390x__) || defined(__powerpc64__) || (defined(__sparc__)  
defined(__arch64__))
 #  define LG_SIZEOF_PTR 3
 #  define LG_SIZEOF_INT 2
 #else

On the other hand, it might be a good idea to actually detect the size
of a pointer instead of having an hardcoded list. The following code
can be used for that:

| #include stdint.h
| #include limits.h
| 
| #if (UINTPTR_MAX == UINT64_MAX)
| #  define LG_SIZEOF_PTR 3
| #elif (UINTPTR_MAX == UINT32_MAX)
| #  define LG_SIZEOF_PTR 2
| #else
| #  error Can not determine size of a pointer
| #endif
| 
| #if (UINT_MAX == UINT64_MAX)
| #  define LG_SIZEOF_INT 3
| #elif (UINT_MAX == UINT32_MAX)
| #  define LG_SIZEOF_INT 2
| #else
| #  error Can not determine size of a int
| #endif

Or it can probably also be done directly with cmake.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: s390x

Kernel: Linux 3.2.0-4-s390x (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Source: blender
Source-Version: 2.69-4

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

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 739...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matteo F. Vescovi mfvesc...@gmail.com (supplier of updated blender 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Feb 2014 14:36:00 +0100
Source: blender
Binary: blender blender-data blender-dbg
Architecture: source amd64 all
Version: 2.69-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
pkg-multimedia-maintain...@lists.alioth.debian.org
Changed-By: Matteo F. Vescovi mfvesc...@gmail.com
Description: 
 blender- Very fast and versatile 3D modeller/renderer
 blender-data - Very fast and versatile 3D modeller/renderer - data package
 blender-dbg - debug symbols for Blender
Closes: 739118
Changes: 
 blender (2.69-4) unstable; urgency=medium
 .
   * debian/patches/: patchset re-worked
 - 0011-fix_FTBFS_on_armel.patch refreshed
 - 0012-fix_FTBFS_on_unofficial_64bit_archs.patch added
   Thanks to Aurelien Jarno (aurel32) for the hint. (Closes: #739118)
   * debian/control: S-V bump 3.9.4 = 3.9.5 (no changes needed)
Checksums-Sha1: 
 01e09ce504ae4347f356e75a7e4cff37e6fc7304 2691 blender_2.69-4.dsc
 aca16d89761d55bfae7833625de6387c04d92535 40252 blender_2.69-4.debian.tar.xz
 6133f0f8cb0a765d7b8116cce7dce3bcbff156de 18715412 blender_2.69-4_amd64.deb
 9fa9883f39009108a681091fbe7ad75f2846283c 7053658 blender-data_2.69-4_all.deb
 40103acac29152ab402d197acd1482f82c86b895 174002450 blender-dbg_2.69-4_amd64.deb
Checksums-Sha256: 
 2d3de3891cd185bc7b3fb7d87d19ca7d3f7103bdcec6608d5536bc25621eb5e5 2691 
blender_2.69-4.dsc
 20caf656bb98ea17b9b04edb3726b84e94a928046994ef0863022a57d7580598 40252 
blender_2.69-4.debian.tar.xz
 

Bug#732652: testing changed Icedove package

2014-02-18 Thread Ximin Luo
On 18/02/14 06:59, Carsten Schoenert wrote:
 On Mon, Feb 17, 2014 at 08:37:34AM +0100, Carsten Schoenert wrote:
 Hello Mike,

 On Mon, Feb 17, 2014 at 07:20:16AM +0900, Mike Hommey wrote:
 On Sun, Feb 16, 2014 at 04:05:33PM +0100, Carsten Schoenert wrote:
 @Mike
 Because you are deeper inside the whole source of Firefox/Thunderbird,
 do have a idea if the issue in the dependentlibs.list is a bug or do
 we something missing?

 My bet is that you're building with -Wl,--as-needed, and that breaks
 thunderbird's assumptions.

 hmm, quite possible. ,)
 Thanks for the hint, I play around with this option. I thought Christoph
 has taken this option because you use it in Iceweasel too. Anyway, one
 build later we will know more.
 
 Mike, obviously you are right! Thank you!
 
 @Ximin,
 I changed the debian/rules files an rebuild the whole packages. The
 testing yesterday workes like a charm an as expected. I pushed the build
 output once again to the URL I posted before.
 All files with *gbpe22ad0* inside are with changed linker flags.
 
 I think that will be the solution.
 

Hey Carsten, I have just tested e22ad0 and it works fine. :) You can mark this 
bug closed. And I don't even need to re-compile m-g-k. Thanks everyone!

X

-- 
GPG: 4096R/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git


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



Bug#735363: [Pkg-gnupg-maint] Bug#735363: [PATCH] init trustdb before trying to clear it

2014-02-18 Thread Thijs Kinkhorst
On Mon, February 17, 2014 19:43, Daniel Kahn Gillmor wrote:
 On 02/15/2014 01:07 PM, Dominic Hargreaves wrote:
 Control: severity -1 critical
 Justification: makes unrelated software on the system break
  [...]
 On reflection, I'm upgrading the severity of this bug, since it's
 blocking RC (FTBFS) bugs on multiple other packages.

 I think this is the right thing to do for #735363.  thanks for doing it,
 Dominic.

 Could someone familiar with gnupg's internals check Daniel's patch,
 please (or Daniel do you feel confident to upload this without
 further review?)

 I've been running with this patch since January 20th, and it works fine
 for me.  I'm attaching the debdiff here.

 I'm uploading it to DELAYED/2 now, in case the package maintainers want
 to try to resolve this some other way.

I do not object against this upload but would like to know if Werner would
approve of the patch. Werner?


Cheers,
Thijs


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



Bug#730833: u-boot: FTBFS on kfreebsd

2014-02-18 Thread Vagrant Cascadian
Looking for help from the *bsd porters on this... We haven't seen a
successful build of u-boot on kfreebsd since mid-2012...

The short of it is a bunch of header files that aren't present on Debian
GNU/kFreeBSD are required for building u-boot-tools. Upstream u-boot has
essentially copied a bunch of header files from linux sources. The current
best patch we have is to copy *more* header files, but this seems like a bad
idea... Droppping u-boot-tools on kfreebsd-* would be a regression from wheezy.

Help would be appreciated, thanks!

live well,
  vagrant


On Mon, Dec 16, 2013 at 10:09:36AM -0800, Vagrant Cascadian wrote:
 On Mon, Dec 16, 2013 at 08:43:05AM +, Ian Campbell wrote:
  On Fri, 2013-12-13 at 13:18 -0800, Ryan Niebur wrote:
 Shipping a different set of includes (that would get out of sync) from another
 source package for building on non-linux arches seems a bit of a mess, but in
 the short term, ugly though it may be, I'd rather see this applied than see
 u-boot stalled because of kfreebsd... or remove u-boot* from kfreebsd?

  Wait -- the uboot upstream source already contains
  include/linux/types.h, so perhaps upstream just needs to increase the
  set of things which they supply themselves.
 
 Maybe, or rewrite that portion entirely...
 
 Attached is a patch that's hopefully slightly easier to read, which just puts
 the extra files in debian/includes, rather than a patch to includes/debian, 
 and
 patches tools/Makefile to add includes/debian on kfreebsd.
 
 Haven't yet got around to testing that it works...

 From 872a316a055f1847912ce755bb311f014ffd367a Mon Sep 17 00:00:00 2001
 From: Vagrant Cascadian vagr...@debian.org
 Date: Mon, 16 Dec 2013 09:56:48 -0800
 Subject: [PATCH] Fix build on kfreebsd and hurd (Closes: #730833). Patch by
  Ryan Niebur, with slight changes.
 
 ---
  debian/include/asm-generic/bitsperlong.h   |  15 ++
  debian/include/asm-generic/int-ll64.h  |  39 +++
  debian/include/asm-generic/types.h |  15 ++
  debian/include/asm/bitsperlong.h   |  13 +
  debian/include/asm/byteorder.h |   6 +
  debian/include/asm/posix_types.h   |   5 +
  debian/include/asm/posix_types_32.h|  49 
  debian/include/asm/posix_types_64.h|  49 
  debian/include/asm/swab.h  |  61 +
  debian/include/asm/types.h |   6 +
  debian/include/linux/byteorder/little_endian.h | 105 
  debian/include/linux/swab.h| 282 
 +
  .../patches/add_asm_posix_types_header_files.diff  |  25 ++
  debian/patches/series  |   1 +
  14 files changed, 671 insertions(+)
  create mode 100644 debian/include/asm-generic/bitsperlong.h
  create mode 100644 debian/include/asm-generic/int-ll64.h
  create mode 100644 debian/include/asm-generic/types.h
  create mode 100644 debian/include/asm/bitsperlong.h
  create mode 100644 debian/include/asm/byteorder.h
  create mode 100644 debian/include/asm/posix_types.h
  create mode 100644 debian/include/asm/posix_types_32.h
  create mode 100644 debian/include/asm/posix_types_64.h
  create mode 100644 debian/include/asm/swab.h
  create mode 100644 debian/include/asm/types.h
  create mode 100644 debian/include/linux/byteorder/little_endian.h
  create mode 100644 debian/include/linux/swab.h
  create mode 100644 debian/patches/add_asm_posix_types_header_files.diff
 
 diff --git a/debian/include/asm-generic/bitsperlong.h 
 b/debian/include/asm-generic/bitsperlong.h
 new file mode 100644
 index 000..f832c3c
 --- /dev/null
 +++ b/debian/include/asm-generic/bitsperlong.h
 @@ -0,0 +1,15 @@
 +#ifndef __ASM_GENERIC_BITS_PER_LONG
 +#define __ASM_GENERIC_BITS_PER_LONG
 +
 +/*
 + * There seems to be no way of detecting this automatically from user
 + * space, so 64 bit architectures should override this in their
 + * bitsperlong.h. In particular, an architecture that supports
 + * both 32 and 64 bit user space must not rely on CONFIG_64BIT
 + * to decide it, but rather check a compiler provided macro.
 + */
 +#ifndef __BITS_PER_LONG
 +#define __BITS_PER_LONG 32
 +#endif
 +
 +#endif /* __ASM_GENERIC_BITS_PER_LONG */
 diff --git a/debian/include/asm-generic/int-ll64.h 
 b/debian/include/asm-generic/int-ll64.h
 new file mode 100644
 index 000..0ede047
 --- /dev/null
 +++ b/debian/include/asm-generic/int-ll64.h
 @@ -0,0 +1,39 @@
 +/*
 + * asm-generic/int-ll64.h
 + *
 + * Integer declarations for architectures which use long long
 + * for 64-bit types.
 + */
 +
 +#ifndef _ASM_GENERIC_INT_LL64_H
 +#define _ASM_GENERIC_INT_LL64_H
 +
 +#include asm/bitsperlong.h
 +
 +#ifndef __ASSEMBLY__
 +/*
 + * __xx is ok: it doesn't pollute the POSIX namespace. Use these in the
 + * header files exported to user space
 + */
 +
 +typedef __signed__ char __s8;
 +typedef unsigned char __u8;
 +
 +typedef __signed__ short __s16;
 +typedef unsigned short 

Bug#723068: darkice won't start: Cannot connect to server socket err = No such file or directory

2014-02-18 Thread Ying-Chun Liu (PaulLiu)
Hi Maintainer and Bob,

JackDspSource.cpp:216:
 if ((client = jack_client_new(client_name)) == NULL) {
throw Exception( __FILE__, __LINE__, JACK server not running?);
 }

jack_client_new is deprecated, so this bug might related:
http://code.google.com/p/darkice/issues/detail?id=22

And there's a patch in that bug report.

I don't use jack. Please see if the above patches works for you.

Yours,
Paul
-- 
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) paul...@debian.org



signature.asc
Description: OpenPGP digital signature


Bug#735769: Sourceless file

2014-02-18 Thread Gunnar Wolf
Hi Bastien,

I am still not finished fixing this bug (and have not yet tested if my
changes will work fine as they are), but would like your
(+ftpmasters') input on whether what I'm doing is enough — I hope to
avoid needing to repackage upstream's sources. Please refer to my
commit in the Drupal7 repository:

  
http://anonscm.debian.org/gitweb/?p=collab-maint/drupal7.git;a=commitdiff;h=91cdae2a901f275cb156de32515f12fc93e17160;hp=f2aa61e2697d1f3da43097e9549e94aeeb31e6dd

In short: We are already packaging the different libjs-jquery modules
(at a higher version than the one shipped in Drupal7). Yes, we don't
carry the sources for the minified Javascript files, but they *are*
DFSG-free, and they allow for distribution in non-source format (they
are MIT-licensed).

So, am I patching in the right direction? Or would it be preferrable
to do a repack and use +dfsg versions?

Greetings,


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



Bug#735363: [Pkg-gnupg-maint] Bug#735363: [PATCH] init trustdb before trying to clear it

2014-02-18 Thread Werner Koch
On Tue, 18 Feb 2014 09:47, th...@debian.org said:

 I do not object against this upload but would like to know if Werner would
 approve of the patch. Werner?

The patch is quite obvious.  IIRC, it has also been posted to the BTS or
the ML.


Salam-Shalom,

   Werner


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


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



Bug#739188: gnome-orca: python-speechd is gone

2014-02-18 Thread Paul Gevers
On 16-02-14 20:07, Emilio Pozuelo Monfort wrote:
 It is basically done in svn.

Just to check with everybody. Are there any objections uploading the
current svn version + enabling python3-speechd? If not, I will do a
final check and upload if I don't find anything.

Paul




signature.asc
Description: OpenPGP digital signature


Bug#735755: Patch for build failure

2014-02-18 Thread Andreas Moog
Control: tags -1 patch

Hi there,

attached patch would fix this particular build failure, but I think the
package could need a general overhaul, given it has been 7 years since the
last upload ;). The example website (linuxfr.org) doesn't seem to be working
with this software anymore and I personally have no experience at all with
it.

Cheers,
  Andreas
--- wmcoincoin-2.5.1e.orig/platypus/Makefile.am
+++ wmcoincoin-2.5.1e/platypus/Makefile.am
@@ -1,9 +1,8 @@
 bin_PROGRAMS = @WMCOINCOIN_PLAYER@
 EXTRA_PROGRAMS = wmcoincoin_player
 
-LIBS = `imlib2-config --libs`
+LIBS = `imlib2-config --libs` `pkg-config --libs x11`
 
 wmcoincoin_player_SOURCES = fmalloc.c giffunc.c gifread.c wmcoincoin_player.c gif.h
 
 INCLUDES = -I. `imlib2-config --cflags`
--- wmcoincoin-2.5.1e.orig/platypus/Makefile.in
+++ wmcoincoin-2.5.1e/platypus/Makefile.in
@@ -88,7 +88,7 @@
 LIBINTL = @LIBINTL@
 LIBOBJS = @LIBOBJS@
 
-LIBS = `imlib2-config --libs`
+LIBS = `imlib2-config --libs` `pkg-config --libs x11`
 LTLIBICONV = @LTLIBICONV@
 LTLIBINTL = @LTLIBINTL@
 LTLIBOBJS = @LTLIBOBJS@


signature.asc
Description: Digital signature


Processed: Patch for build failure

2014-02-18 Thread Debian Bug Tracking System
Processing control commands:

 tags -1 patch
Bug #735755 [src:wmcoincoin] wmcoincoin: FTBFS: ld: wmcoincoin_player.o: 
undefined reference to symbol 'XGetWindowAttributes'
Added tag(s) patch.

-- 
735755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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#732652: testing changed Icedove package

2014-02-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 732652 pending
Bug #732652 [icedove] icedove does not load libraries from /usr/lib/icedove
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
732652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#732652: testing changed Icedove package

2014-02-18 Thread Carsten Schoenert
tags 732652 pending
thanks

On Tue, Feb 18, 2014 at 05:10:55PM +, Ximin Luo wrote:
 Hey Carsten, I have just tested e22ad0 and it works fine. :) You can
 mark this bug closed. And I don't even need to re-compile m-g-k.
 Thanks everyone!

Excellent! I send my latest patches to Christoph, he will prepare a new
upload to unstable.

Regards
Carsten


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



Bug#730833: u-boot: FTBFS on kfreebsd

2014-02-18 Thread Robert Millan
On 18/02/2014 19:11, Vagrant Cascadian wrote:
 Looking for help from the *bsd porters on this... We haven't seen a
 successful build of u-boot on kfreebsd since mid-2012...
 
 The short of it is a bunch of header files that aren't present on Debian
 GNU/kFreeBSD are required for building u-boot-tools. Upstream u-boot has
 essentially copied a bunch of header files from linux sources. The current
 best patch we have is to copy *more* header files, but this seems like a bad
 idea... Droppping u-boot-tools on kfreebsd-* would be a regression from 
 wheezy.

Are you sure u-boot is supposed to build on anything other than Linux? The kind
of software package that embeds copies of Linux headers is not generally
intended to be portable...

-- 
Robert Millan


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



Bug#730833: u-boot: FTBFS on kfreebsd

2014-02-18 Thread Vagrant Cascadian
On Tue, Feb 18, 2014 at 09:35:09PM +, Robert Millan wrote:
 On 18/02/2014 19:11, Vagrant Cascadian wrote:
  Looking for help from the *bsd porters on this... We haven't seen a
  successful build of u-boot on kfreebsd since mid-2012...
  
  The short of it is a bunch of header files that aren't present on Debian
  GNU/kFreeBSD are required for building u-boot-tools. Upstream u-boot has
  essentially copied a bunch of header files from linux sources. The current
  best patch we have is to copy *more* header files, but this seems like a bad
  idea... Droppping u-boot-tools on kfreebsd-* would be a regression from 
  wheezy.
 
 Are you sure u-boot is supposed to build on anything other than Linux? The 
 kind
 of software package that embeds copies of Linux headers is not generally
 intended to be portable...

Well, u-boot-tools could technically be useable on any architecture. Is it
actually useful? Quite possibly not.

If the best thing is to drop non-linux architectures, I'd be fine with that.
I don't want to drop architectures from the packaging without asking porters
first.


live well,
  vagrant


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



Bug#726799: qgo: deletes a shipped file during upgrades: /usr/share/mime/text/x-sgf.xml

2014-02-18 Thread Yann Dirson
Hi Andreas,

Did you find the time systemtap this issue ?

On Fri, Jan 10, 2014 at 10:41:39PM +0100, Yann Dirson wrote:
 Hi Andreas,
 
 On Fri, Dec 13, 2013 at 11:11:32PM +0100, Yann Dirson wrote:
  On Fri, Dec 13, 2013 at 01:58:31AM +0100, Andreas Beckmann wrote:
   On 2013-12-03 22:30, Yann Dirson wrote:
I'm wondering if that could not be caused by a bug in the mime
trigger, that would have been fixed already.
   
   That would be easier to test - what package is it?
  
  I was thinking about the mime-support trigger, but that package has
  not been changed for 6 months, so the problem must be somewhere else.
  
Can you please retry the test,
   
   reproducible in jessie- sid and wheezy-sid updates to version
   2.0~git-20131123-1
   
and if it still fails, run it while the
following stap script is running:
   
   That may take some time ... I'll need to rerun the piuparts test
   manually in a chroot ... and on a different machine ...
 
 Any news on your side ?


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



Bug#715464: This is still not fixed

2014-02-18 Thread Steaphan Greene
Note, despite the above stated belief, this is still *not* fixed as of
current wheezy+updates.

The above-mentioned patch is still required to make icedove usable in
sawfish on large displays.

I just confirmed this patch still applied cleanly, and allowed me to build
a working icedove_17.0.10-1~deb7u1 package.


Bug#715464: This is still not fixed

2014-02-18 Thread Carsten Schönert
Hello Steaphan,

Am 18.02.2014 23:10, schrieb Steaphan Greene:
 Note, despite the above stated belief, this is still *not* fixed as of
 current wheezy+updates.

that is not difficult to make it clear, obviously.

The release team only allows security related fixes for the current
version 17.0.10 in stable-security. By this the patch is only applied
to the versions in testing and not stable-security.
But we work hardly on the current 24.3.0 version to get it into testing
and finally to stable-security. But this will need some more time.

 
 The above-mentioned patch is still required to make icedove usable in
 sawfish on large displays.
 
 I just confirmed this patch still applied cleanly, and allowed me to
 build a working icedove_17.0.10-1~deb7u1 package.

Fine! Otherwise this would require a backport release. But with a
version 24.3.0 in starting we don't want to make such a backport for
this short time. We fighted the last time a not so simple issue with
needed libraries and symbols for other packages that depended on Icedove.

-- 
Regards
Carsten


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



Bug#715464: This is still not fixed

2014-02-18 Thread Steaphan Greene
Oh, ok.  Makes sense.  Thanks for the clarification.


On Tue, Feb 18, 2014 at 2:25 PM, Carsten Schönert
c.schoen...@t-online.dewrote:

 Hello Steaphan,

 Am 18.02.2014 23:10, schrieb Steaphan Greene:
  Note, despite the above stated belief, this is still *not* fixed as of
  current wheezy+updates.

 that is not difficult to make it clear, obviously.

 The release team only allows security related fixes for the current
 version 17.0.10 in stable-security. By this the patch is only applied
 to the versions in testing and not stable-security.
 But we work hardly on the current 24.3.0 version to get it into testing
 and finally to stable-security. But this will need some more time.

 
  The above-mentioned patch is still required to make icedove usable in
  sawfish on large displays.
 
  I just confirmed this patch still applied cleanly, and allowed me to
  build a working icedove_17.0.10-1~deb7u1 package.

 Fine! Otherwise this would require a backport release. But with a
 version 24.3.0 in starting we don't want to make such a backport for
 this short time. We fighted the last time a not so simple issue with
 needed libraries and symbols for other packages that depended on Icedove.

 --
 Regards
 Carsten



Bug#730833: u-boot: FTBFS on kfreebsd

2014-02-18 Thread Robert Millan
On 18/02/2014 21:54, Vagrant Cascadian wrote:
 On Tue, Feb 18, 2014 at 09:35:09PM +, Robert Millan wrote:
 On 18/02/2014 19:11, Vagrant Cascadian wrote:
 Looking for help from the *bsd porters on this... We haven't seen a
 successful build of u-boot on kfreebsd since mid-2012...

 The short of it is a bunch of header files that aren't present on Debian
 GNU/kFreeBSD are required for building u-boot-tools. Upstream u-boot has
 essentially copied a bunch of header files from linux sources. The current
 best patch we have is to copy *more* header files, but this seems like a bad
 idea... Droppping u-boot-tools on kfreebsd-* would be a regression from 
 wheezy.

 Are you sure u-boot is supposed to build on anything other than Linux? The 
 kind
 of software package that embeds copies of Linux headers is not generally
 intended to be portable...
 
 Well, u-boot-tools could technically be useable on any architecture. Is it
 actually useful? Quite possibly not.
 
 If the best thing is to drop non-linux architectures, I'd be fine with that.
 I don't want to drop architectures from the packaging without asking porters
 first.

I think if upstream doesn't consider it a bug to copy non-portable declarations 
from
Linux headers, it's probably reasonable to consider u-boot as Linux-specific 
software.

Attempting to fight this kind of trend is tends to be very costly, but 
ultimately it's
your call as maintainer to decide whether it's worth it.

We can provide assistance if necessary. In this case, my advice would be to 
figure out
why are those headers being copied in, since this seems to be the root of the 
problem.

-- 
Robert Millan


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



Bug#735898: pavucontrol segmentation fault

2014-02-18 Thread Simone Vellei
Hi John,
yes, you can you try to execute

$ strace -o pavucontrol.log pavucontrol

and attach here pavucontrol.log

-- 
Simone Vellei (henomis)

GPG KEYID: A3D37CF4
GPG FINGERPRINT: 5A79 3A3A 143E 9B37 9B38  FB86 8E45 8B62 A3D3 7CF4


Bug#736105: Sourceless file

2014-02-18 Thread Markus Koschany
Control: owner -1 !

It seems I have found a way to compile the sources. I will prepare an
upload soon.

Markus



signature.asc
Description: OpenPGP digital signature


Processed: Sourceless file

2014-02-18 Thread Debian Bug Tracking System
Processing control commands:

 owner -1 !
Bug #736105 [src:freemind] Sourceless file
Owner recorded as Markus Koschany a...@gambaru.de.

-- 
736105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#736105: Sourceless file

2014-02-18 Thread Markus Koschany
Up-to-date sources are here btw:


http://sourceforge.net/p/freemind/code/ci/master/tree/flash/



signature.asc
Description: OpenPGP digital signature


Bug#739466: When compiled with GTK, Emacs cannot recover from X disconnects

2014-02-18 Thread Dan Jacobson
Package: libgtk-3-0
Version: 3.11.5-1
Severity: grave

CANNOT USE EMACS.

X protocol error: RenderBadPicture (invalid Picture parameter) on protocol 
request 139
When compiled with GTK, Emacs cannot recover from X disconnects.
This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715
For details, see etc/PROBLEMS.

(emacs:2687): GLib-WARNING **: g_main_context_prepare() called recursively from 
within a source's check() or prepare() member.

(emacs:2687): GLib-WARNING **: g_main_context_check() called recursively from 
within a source's check() or prepare() member.
Fatal error 6: Aborted
Backtrace:
emacs[0x8136343]
emacs[0x811db71]
emacs[0x8136397]
emacs[0x80f1350]
emacs[0x80f3373]
emacs[0x80f33db]
/usr/lib/i386-linux-gnu/libX11.so.6(_XError+0x126)[0xb69d5fa6]
/usr/lib/i386-linux-gnu/libX11.so.6(+0x38ca6)[0xb69d2ca6]
/usr/lib/i386-linux-gnu/libX11.so.6(+0x38d5e)[0xb69d2d5e]
/usr/lib/i386-linux-gnu/libX11.so.6(_XEventsQueued+0x68)[0xb69d3798]
/usr/lib/i386-linux-gnu/libX11.so.6(_XFlush+0x44)[0xb69d3a74]
/usr/lib/i386-linux-gnu/libX11.so.6(XFlush+0x2b)[0xb69b4d2b]
/usr/lib/i386-linux-gnu/libX11.so.6(+0x6a97e)[0xb6a0497e]
/usr/lib/i386-linux-gnu/libX11.so.6(_XimFlush+0x10)[0xb6a063b0]
/usr/lib/i386-linux-gnu/libX11.so.6(+0x59232)[0xb69f3232]
/usr/lib/i386-linux-gnu/libX11.so.6(XDestroyIC+0x1f)[0xb69e075f]
emacs[0x81033d0]
emacs[0x80fa99a]
emacs[0x80facc3]
emacs[0x8066082]
emacs[0x80f13b8]
emacs[0x80f3373]
emacs[0x80f33db]
/usr/lib/i386-linux-gnu/libX11.so.6(_XError+0x126)[0xb69d5fa6]
/usr/lib/i386-linux-gnu/libX11.so.6(+0x38ca6)[0xb69d2ca6]
/usr/lib/i386-linux-gnu/libX11.so.6(+0x38d5e)[0xb69d2d5e]
/usr/lib/i386-linux-gnu/libX11.so.6(_XEventsQueued+0x68)[0xb69d3798]
/usr/lib/i386-linux-gnu/libX11.so.6(XPending+0x58)[0xb69c4928]
/usr/lib/i386-linux-gnu/libgdk-3.so.0(+0x4c2ee)[0xb6fc22ee]
/usr/lib/i386-linux-gnu/libgdk-3.so.0(+0x4c547)[0xb6fc2547]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_prepare+0x163)[0xb6b3a8d3]
/lib/i386-linux-gnu/libglib-2.0.so.0(+0x471ff)[0xb6b3b1ff]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_pending+0x36)[0xb6b3b3e6]
/usr/lib/i386-linux-gnu/libgtk-3.so.0(gtk_events_pending+0x21)[0xb72026f1]
emacs[0x80f14e9]
emacs[0x8124339]
emacs[0x8123db5]
emacs[0x816442d]
emacs(re_search_2+0x246)[0x8169646]
emacs(re_search+0x4b)[0x8169eeb]
emacs[0x816288b]


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



Bug#733967: marked as done (denemo: FTBFS against libaubio4)

2014-02-18 Thread Debian Bug Tracking System
Your message dated Wed, 19 Feb 2014 00:18:53 +
with message-id e1wfush-0008fd...@franck.debian.org
and subject line Bug#733967: fixed in denemo 1.1.0-1
has caused the Debian Bug report #733967,
regarding denemo: FTBFS against libaubio4
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.)


-- 
733967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: denemo
Version: 0.9.2-3
Severity: serious

Hi,

Your package FTBFS when rebuilt against libaubio4 (note, the failure
may or mayb not be unrelated to changes in libaubio4).  The tail of the
buildd log says:


pitchrecog.c:322:41: note: each undeclared identifier is reported only once for 
each function it appears in
pitchrecog.c:322:33: error: invalid operands to binary / (have 'unsigned int' 
and 'int *')
   if(onset= sizeof(onset_types)/sizeof(aubio_onsetdetection_type))
 ^
pitchrecog.c:322:11: warning: comparison between pointer and integer [enabled 
by default]
   if(onset= sizeof(onset_types)/sizeof(aubio_onsetdetection_type))
   ^
make[3]: *** [pitchrecog.o] Error 1
make[3]: Leaving directory `/«PKGBUILDDIR»/src'
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
dh_auto_build: make -j1 returned exit code 2
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [build-arch] Error 2


~Niels

[reference] https://buildd.debian.org/status/package.php?p=denemosuite=sid
---End Message---
---BeginMessage---
Source: denemo
Source-Version: 1.1.0-1

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

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 733...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josue Abarca jmasli...@debian.org (supplier of updated denemo 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...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Jan 2014 13:46:43 -0600
Source: denemo
Binary: denemo denemo-data denemo-doc ttf-denemo
Architecture: source amd64 all
Version: 1.1.0-1
Distribution: experimental
Urgency: low
Maintainer: Josue Abarca jmasli...@debian.org
Changed-By: Josue Abarca jmasli...@debian.org
Description: 
 denemo - gtk+ front end to GNU Lilypond
 denemo-data - data for denemo
 denemo-doc - documentation and examples for denemo
 ttf-denemo - music notation symbol fonts for denemo
Closes: 733967
Changes: 
 denemo (1.1.0-1) experimental; urgency=low
 .
   * Imported Upstream version 1.1.0
   * help.c.diff patch updated.
   * Makefile.am.diff patch updated.
   * denemo.conf.diff patch removed, because the original file was deleted
 by upstream in 27adac0.
   * ouput-typo.diff Patch deleted, spelling error fixed upstream.
   * configure.in.diff patch updated.
   * debian/control
 - New build dependency rubberband-dev.
 - Dependency in automake1.11 removed.
 - DM-Upload-Allowed removed, thanks to my previous sponsor.
 - librubberband-dev dependency fixed.
 - New buildependency intltool.
 - Standards updated to 3.9.5, no changes required.
   * debian/rules
 - override_dh_autoreconf added in order to call intltoolize.
 - Removed dh_fixperms override, fixed upstream.
   * add_format_arguments.diff patch added to pass format arguments in
 order to avoid possible security problems and build using Hardening
 Options.
   * debian/denemo.install
 - denemo.conf removed from the list because it was
   deleted upstream.
   * debian/denemo-data.install
 - Added the new denemo_file_update bash script.
   * shebang.diff patch added in order to add the shebang to
 denemo_file_update.sh.
   * remove_sh_extension.diff patch added in order to rename
 denemo_file_update.sh.
   * denemo_file_update.1 man page added.
   * debian/denemo-data.manpages now includes the manpage for
 denemo_file_update.sh.
   * debian/clean Added the auto-generated files m4/intltool.m4,
 po/POTFILES.skip, po/POTFILES.in.
   * update_aubio.diff patch added to make denemo work with
 aubio4 (Closes: 733967).
   * keywords-desktop-entry patch added in order to 

Bug#705906: Not fixable in fsharp

2014-02-18 Thread Christopher James Halse Rogers
reassign 705906 mono-gac
forcemerge 570181 705906

thanks

This is no longer an fsharp bug. You've encountered bug #570181, which
you can work around by installing mono-runtime (or mono-runtime-common,
in experimental) first.

Clearly it's time to fix that longstanding problem :)


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


Processed: Not fixable in fsharp

2014-02-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 705906 mono-gac
Bug #705906 [fsharp] fsharp: fails to install: E: installing Assembly 
/usr/lib/cli/FSharp.Core-4.3/FSharp.Core.dll failed (exit status 29)
Bug #705924 [fsharp] fsharp: fails to install: E: installing Assembly 
/usr/lib/cli/FSharp.Core-4.3/FSharp.Core.dll failed (exit status 29)
Bug reassigned from package 'fsharp' to 'mono-gac'.
Bug reassigned from package 'fsharp' to 'mono-gac'.
No longer marked as found in versions fsharp/3.0.34+dfsg-3 and fsharp/3.0.26-1.
No longer marked as found in versions fsharp/3.0.34+dfsg-3 and fsharp/3.0.26-1.
No longer marked as fixed in versions fsharp/3.0.34+dfsg-1.
No longer marked as fixed in versions fsharp/3.0.34+dfsg-1.
 forcemerge 570181 705906
Bug #570181 [mono-gac] mono-gac: Installing signature-remapped assemblies fails 
unless mono-runtime is configured first
Bug #705924 [mono-gac] fsharp: fails to install: E: installing Assembly 
/usr/lib/cli/FSharp.Core-4.3/FSharp.Core.dll failed (exit status 29)
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Removed indication that 705924 affects libfsharp-compiler-server-shared4.3-cil, 
libfsharp-data-typeproviders4.3-cil, 
libfsharp-compiler-interactive-settings4.3-cil, libfsharp-compiler4.3-cil, and 
libfsharp-build4.3-cil
Removed indication that 705906 affects libfsharp-compiler-server-shared4.3-cil, 
libfsharp-data-typeproviders4.3-cil, 
libfsharp-compiler-interactive-settings4.3-cil, libfsharp-compiler4.3-cil, and 
libfsharp-build4.3-cil
Marked as found in versions mono/2.4.2.3+dfsg-2.
Marked as found in versions mono/2.4.2.3+dfsg-2.
Bug #705906 [mono-gac] fsharp: fails to install: E: installing Assembly 
/usr/lib/cli/FSharp.Core-4.3/FSharp.Core.dll failed (exit status 29)
Merged 570181 705906 705924
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
570181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570181
705906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705906
705924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#693150: iceowl-l10n-fr: Dependency with iceowl-extension is broken.

2014-02-18 Thread Jerome Charaoui
Dear Maintainer,

I have prepared a newer package which can be installed in sid and
provides translations for iceowl-extension.

If you have not the time nor interest to take a look at it, please let
us know so I can try to have the situation adressed by other means.

Thanks,

  -- Jerome



signature.asc
Description: OpenPGP digital signature


Bug#733967: denemo: FTBFS against libaubio4

2014-02-18 Thread Josue Abarca
Hi thanks for the feedback/help,

I backported the patches from Paul to apply them to 1.1.0-1
and uploaded that new version.

Upstream is very close to release a new version, so I will package
that and upload it soon, so we are going to get and use the
complete/original patches from Paul and the latest changes from
upstream.

Thanks to Paul for his patches, thanks to Sebastian for his feedback
and thanks Niels for the report.

-- 
Josué M. Abarca S.


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



Bug#739469: llvm-3.5-tools: uninstallable in sid: Depends: llvm-3.4-dev (= 1:3.5~svn201412-1)

2014-02-18 Thread Andreas Beckmann
Package: llvm-3.5-tools
Version: 1:3.5~svn201412-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

  The following packages have unmet dependencies:
   llvm-3.5-tools : Depends: llvm-3.4-dev (= 1:3.5~svn201412-1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.


Cheers,

Andreas


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



Processed: python-taskflow: unsatisfiable Depends: python-futures (= 2.1.3)

2014-02-18 Thread Debian Bug Tracking System
Processing control commands:

 affects -1 python-taskflow
Bug #739470 [python-taskflow] python-taskflow: unsatisfiable Depends: 
python-futures (= 2.1.3)
Added indication that 739470 affects python-taskflow

-- 
739470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#739470: python-taskflow: unsatisfiable Depends: python-futures (= 2.1.3)

2014-02-18 Thread Andreas Beckmann
Package: python-taskflow
Version: 0.1.2-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 python-taskflow

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

  The following packages have unmet dependencies:
   python-taskflow : Depends: python-futures (= 2.1.3)
  E: Unable to correct problems, you have held broken packages.

A python-futures package is neither in the archive nor in NEW.


Cheers,

Andreas


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



Bug#739471: dpsyco-sudo: modifies conffiles (policy 10.7.3): /etc/sudoers

2014-02-18 Thread Andreas Beckmann
Package: dpsyco-sudo
Version: 1.0.36
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: piuparts
Control: sffects -1 + dpsyco

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

  /etc/sudoers

With the introduction of /etc/sudoers.d dpsyco-sudo should just place
its modifications there.


cheers,

Andreas


dpsyco_1.0.36.log.gz
Description: GNU Zip compressed data


Processed: your mail

2014-02-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tag 728427 + pending
Bug #728427 {Done: Andreas Beckmann a...@debian.org} 
[python-babel-localedata] python-babel-localedata is empty after installing
Ignoring request to alter tags of bug #728427 to the same tags previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
728427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#739473: texlive-publishers, texlive-publishers-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/texlive-doc/latex/pittetd/pittdiss.pit

2014-02-18 Thread Andreas Beckmann
Package: texlive-publishers,texlive-publishers-doc
Version: 2013.20140215-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package texlive-publishers-doc.
  Preparing to unpack .../texlive-publishers-doc_2013.20140215-1_all.deb ...
  Unpacking texlive-publishers-doc (2013.20140215-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/texlive-publishers-doc_2013.20140215-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/doc/texlive-doc/latex/pittetd/pittdiss.pit', 
which is also in package texlive-latex-extra-doc 2013.20131219-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/texlive-publishers-doc_2013.20140215-1_all.deb

  Selecting previously unselected package texlive-publishers.
  Preparing to unpack .../texlive-publishers_2013.20140215-1_all.deb ...
  Unpacking texlive-publishers (2013.20140215-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/texlive-publishers_2013.20140215-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/texlive/texmf-dist/tex/latex/pittetd/pitetd10.clo', which is also 
in package texlive-latex-extra 2013.20131219-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/texlive-publishers_2013.20140215-1_all.deb

The complete lists of conflicting files:

usr/share/doc/texlive-doc/latex/pittetd/achicago.pit
usr/share/doc/texlive-doc/latex/pittetd/pittdiss.pit
usr/share/doc/texlive-doc/latex/pittetd/pittetd.pdf
usr/share/doc/texlive-doc/latex/pittetd/pitthesis.pit

usr/share/texlive/texmf-dist/tex/latex/pittetd/pitetd10.clo
usr/share/texlive/texmf-dist/tex/latex/pittetd/pitetd11.clo
usr/share/texlive/texmf-dist/tex/latex/pittetd/pitetd12.clo
usr/share/texlive/texmf-dist/tex/latex/pittetd/pittetd.cls


cheers,

Andreas


texlive-latex-extra-doc=2013.20131219-1_texlive-publishers-doc=2013.20140215-1.log.gz
Description: GNU Zip compressed data


Bug#739473: texlive-publishers, texlive-publishers-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/texlive-doc/latex/pittetd/pittdiss.pit

2014-02-18 Thread Norbert Preining
On Mi, 19 Feb 2014, Andreas Beckmann wrote:
   Unpacking texlive-publishers-doc (2013.20140215-1) ...
   dpkg: error processing archive 
 /var/cache/apt/archives/texlive-publishers-doc_2013.20140215-1_all.deb 
 (--unpack):
trying to overwrite 
 '/usr/share/doc/texlive-doc/latex/pittetd/pittdiss.pit', which is also in 
 package texlive-latex-extra-doc 2013.20131219-1

Argg, indeed, because the texlive-extra didn't migrate to testing before.

Yes will do another upload soon.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live  Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094



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



Processed: Re: FTBFS on i386: ERROR: Caught a segmentation fault while loading plugin file

2014-02-18 Thread Debian Bug Tracking System
Processing control commands:

 tags -1 unreproducible
Bug #660458 [src:gst-buzztard] FTBFS on i386: ERROR: Caught a segmentation 
fault while loading plugin file
Added tag(s) unreproducible.

-- 
660458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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



Bug#660458: FTBFS on i386: ERROR: Caught a segmentation fault while loading plugin file

2014-02-18 Thread Hideki Yamane
control: tags -1 unreproducible

Hi,

 I've built it with wheezy cowbuilder x 3 and sid cowbuilder x3
 (both on i386 virtualbox), and got no FTBFS.

wheezy build env shows
dh_makeshlibs -plibgstbuzztard-dev
LD_LIBRARY_PATH=debian/libgstbuzztard0/usr/lib:/usr/lib/i386-linux-gnu/libfakeroot:/usr/lib64/libfakeroot:/usr/lib32/libfakeroot
\
dh_gstscancodecs
Called unk_?DSP_Init@@YIXH@Z
Use of uninitialized value $str in hash element at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 609.
Use of uninitialized value $substvar in concatenation (.) or string at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 574.
dh_installdeb -pgstreamer0.10-buzztard
(snip)

 but non-failure with it.

 gregor, can you still reproduce it?


-- 
Hideki Yamane


Bug#739476: ImportError: cannot import name ScopedSession

2014-02-18 Thread Arnaud Fontaine
Source: elixir
Severity: grave
Tags: upstream

Hello,

When trying to import elixir module, I get the following traceback which
makes elixir completely unusable:

import elixir
Traceback (most recent call last):
  File stdin, line 1, in module
  File /usr/lib/pymodules/python2.7/elixir/__init__.py, line 29, in module
from elixir.entity import Entity, EntityBase, EntityMeta, EntityDescriptor, 
\
  File /usr/lib/pymodules/python2.7/elixir/entity.py, line 17, in module
from sqlalchemy.orm import MapperExtension, mapper, object_session, \
ImportError: cannot import name ScopedSession

Also, considering that a security bug, #670919, which is almost two
years old has never been fixed and there has been no upstream release
since 11/2009 (actually around the time a declarative layer has been
implemented in sqlalchemy AFAIU), I'm wondering whether this package
should be kept in the archive at all. What do you think?

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Regards,
-- 
Arnaud Fontaine


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



Bug#737153: OpenCVModules.cmake not installed, causing visp FTBFS

2014-02-18 Thread Nobuhiro Iwamatsu
Hi,

I just upload opencv 2.4.8+dfsg1-2.
This version fixes a problem that can not be build applications using opencv.
But visp has other build error by libusb.h in /usr/include/libfreenect.hpp.
Could you check this problem?

Best regards,
  Nobuhiro

2014-02-16 9:50 GMT+09:00 Nobuhiro Iwamatsu iwama...@nigauri.org:
 Hi, all.

 Sorry about this problem.
 I will fix this today. please wait.

 Best regards,
   Nobuhiro

 2014-02-15 3:30 GMT+09:00 Fabien Spindler fabien.spind...@inria.fr:
 Le 14/02/14 18:36, Rebecca N. Palmer a écrit :

 libopencv-dev doesn't pull in the Java libraries; I don't know if the
 appropriate fix is that it should, or that the cmake script shouldn't be
 looking for them when building C(++).


 I think that the script OpenCVModules.cmake should not look for
 libopencv_java.

 When I build opencv 2.4.8 from source, libopencv_java is not build.

 The error can be simply reproduced using the following CMakeLists.txt

 project(dummy)
 cmake_minimum_required(version 2.8)
 find_package(OpenCV REQUIRED)

 Hope it helps
 Fabien


 --
 debian-science-maintainers mailing list
 debian-science-maintain...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers



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



-- 
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#693150: iceowl-l10n-fr: Dependency with iceowl-extension is broken.

2014-02-18 Thread Guido Günther
On Tue, Feb 18, 2014 at 07:45:53PM -0500, Jerome Charaoui wrote:
 Dear Maintainer,
 
 I have prepared a newer package which can be installed in sid and
 provides translations for iceowl-extension.
 
 If you have not the time nor interest to take a look at it, please let
 us know so I can try to have the situation adressed by other means.

I've said in 20140203171303.ga2...@bogon.m.sigxcpu.org on
debian-mentors that an NMU to experimental would be fine.
Cheers,
 -- Guido


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



Bug#739471: dpsyco-sudo: modifies conffiles (policy 10.7.3): /etc/sudoers

2014-02-18 Thread Ola Lundqvist
Hi Andreas

Thanks. You are right. This was required before, but when /etc/sudoers.d
was introduced this is no longer necessary.

On the other hand dpsyco is not used by many, so maybe we should just
remove the package altogether.

// Ola


On Wed, Feb 19, 2014 at 2:43 AM, Andreas Beckmann a...@debian.org wrote:

 Package: dpsyco-sudo
 Version: 1.0.36
 Severity: serious
 Tags: jessie sid
 User: debian...@lists.debian.org
 Usertags: piuparts
 Control: sffects -1 + dpsyco

 Hi,

 during a test with piuparts I noticed your package modifies conffiles.
 This is forbidden by the policy, see
 http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

 debsums reports modification of the following files,
 from the attached log (scroll to the bottom...):

   /etc/sudoers

 With the introduction of /etc/sudoers.d dpsyco-sudo should just place
 its modifications there.


 cheers,

 Andreas




-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comAnnebergsslingan 37\
|  o...@debian.org   654 65 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---