Bug#752639: marked as done (php-imlib is licensed under the PHP license and is not PHP)
Your message dated Wed, 25 Jun 2014 23:16:48 -0700 with message-id 20140626061648.gb15...@virgil.dodds.net and subject line Re: php-imlib is licensed under the PHP license and is not PHP has caused the Debian Bug report #752639, regarding php-imlib is licensed under the PHP license and is not PHP 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.) -- 752639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: php-gearman Severity: serious User: paul...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks From the REJECT faq: / | You have a PHP add-on package (any php script/app/thing, not PHP | itself) and it's licensed only under the standard PHP license. That | license, up to the 3.x which is actually out, is not really usable for | anything else than PHP itself. I've mailed our -legal list about that | and got only one response, which basically supported my view on this. | Basically this license talks only about PHP, the PHP Group, and includes | Zend Engine, so its not applicable to anything else. And even worse, | older versions include the nice ad-clause. | | One good solution here is to suggest a license change to your upstream, | as they clearly wanted a free one. LGPL or BSD seems to be what they | want. \ Sorry this made it through NEW, Hope you're well, and thanks for your work, Paul -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- This bug is invalid. The license of php-imlib, as documented in debian/copyright, is: This software is made available under the terms of the GNU LGPL. On Debian GNU/Linux systems, the complete text of the GNU Lesser General Public License can be found in /usr/share/common-licenses/LGPL-2.1. The software may also be distributed and modified under the terms of version 2.02 of the PHP License, as follows: That distributing php-imlib under the terms of the PHP License would require someone to make a false statement about php-imlib does not make this unsuitable for main. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature ---End Message---
Processed: severity of 738489 is important
Processing commands for cont...@bugs.debian.org: severity 738489 important Bug #738489 [hash-slinger] hash-slinger: tlsa and openpgpkey scripts break on non-existent files (root.key, dlv.isc.org.key, ca-bundle.crt) Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 738489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738489 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#751034: marked as done (roboptim-core: FTBFS - whitespace difference makes tests fails)
Your message dated Thu, 26 Jun 2014 07:23:44 + with message-id e1x0424-00074x...@franck.debian.org and subject line Bug#751034: fixed in roboptim-core 2.0-7 has caused the Debian Bug report #751034, regarding roboptim-core: FTBFS - whitespace difference makes tests fails 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.) -- 751034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: roboptim-core Version: 2.0-6 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] Running 1 test case... Numeric quadratic function A = [5,5]((1.1,1.2,1.3,1.4,1.5), (1.2,2.2,2.3,2.4,2.5), (1.3,2.3,3.3,3.4,3.5), (1.4,2.4,3.4,4.4,4.5), (1.5,2.5,3.5,4.5,5.5)) B = [5](2.1,4.3,6.5,8.7, 0) f(x) = [1](304.234) J(x) = [1,5]((18.15,31.76,44.29,54.75,51.25)) G(x) = [5](18.15,31.76,44.29,54.75,51.25) H(x) = [5,5]((1.1,1.2,1.3,1.4,1.5), (1.2,2.2,2.3,2.4,2.5), (1.3,2.3,3.3,3.4,3.5), (1.4,2.4,3.4,4.4,4.5), (1.5,2.5,3.5,4.5,5.5)) /srv/jenkins-slave/workspace/sid-goto-cc-roboptim-core/roboptim-core-2.0/tests/numeric-quadratic-function.cc(71): error in numeric_quadratic_function: check output-match_pattern () failed. Mismatch at position 180 ... 0) ... ...0) f(... *** 1 failure detected in test suite Master Test Suite Further test suite failures follow. In all cases it seems there are differences in whitespace only. The full build log is attached. Best, Michael roboptim-core-build-log.txt.gz Description: application/gunzip pgp3EyLJYqaTr.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: roboptim-core Source-Version: 2.0-7 We believe that the bug you reported is fixed in the latest version of roboptim-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 751...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Moulard thomas.moul...@gmail.com (supplier of updated roboptim-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: SHA256 Format: 1.8 Date: Thu, 26 Jun 2014 11:10:52 +0900 Source: roboptim-core Binary: libroboptim-core-dev libroboptim-core2 libroboptim-core2-plugin-base libroboptim-core2-dbg libroboptim-core-doc Architecture: source amd64 all Version: 2.0-7 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Thomas Moulard thomas.moul...@gmail.com Description: libroboptim-core-dev - numerical optimization library - development files libroboptim-core-doc - numerical optimization library - documentation libroboptim-core2 - numerical optimization library libroboptim-core2-dbg - numerical optimization library - debugging symbols libroboptim-core2-plugin-base - numerical optimization library - core plug-ins Closes: 741852 741855 751034 Changes: roboptim-core (2.0-7) unstable; urgency=medium . * debian/control: add branch information to Vcs-Git field (Closes: #741852) * Disable output check in fragile tests (Closes: #751034, #741855) * debian/control: bump Standards-Version to 3.9.5 * Update d/watch to check gpg signature Checksums-Sha1: 6872d18d4bc4bdf735256691419ecceaa2d7b0ea 2371 roboptim-core_2.0-7.dsc ec2a7e55351450637bb1db65c797ceef5587f13f 32624 roboptim-core_2.0-7.debian.tar.xz b02dcd96ef2c537dbb07eace876d102f47218b6c 35848 libroboptim-core-dev_2.0-7_amd64.deb 22d1a35f571ca278dc6dfa1a40e5f3813e3567de 64804 libroboptim-core2_2.0-7_amd64.deb 117d36b920dd72b47f782ccc6016a884f07fe064 30008 libroboptim-core2-plugin-base_2.0-7_amd64.deb a1f3c79c5c0d154dbd2131c43ea7ab4a09067490 2038626 libroboptim-core2-dbg_2.0-7_amd64.deb f61095bbf35cba9f3954df4e98e391540f481173 321024 libroboptim-core-doc_2.0-7_all.deb Checksums-Sha256: 49a7aaada9b99ad9a9b9d20e42d0f10f472f5f22d2f201767c69f3ce37e70bad 2371 roboptim-core_2.0-7.dsc 5ae213acbcefbf19aea27bd7605e1ddb402591d554d9aed45bfd06b3d52b6f2e 32624 roboptim-core_2.0-7.debian.tar.xz 83cc901733f6f5042ef0b5608f265872e0b0efe75a91f49b3d84920e26c6ad44 35848
Bug#728196: [Pkg-php-pecl] Bug#728196: Bug#728196: php-gearman is licensed under the PHP license, and is not php
Hi, On Tue, Jun 24, 2014 at 5:14 PM, Ondřej Surý ond...@sury.org wrote: Control: reassign -1 ftp.debian.org Control: retitle -1 Reassess PHP License usage for PHP PECL extensions Hi Paul and rest of FTP Masters, I am reassigning this bug to FTP Masters to solve it in between FTP Masters. Please note that Paul's interpretation would effectively lead to full removal of PHP from the Debian archive - see the list of affected packages in the bug (and in my previous email from May 27). I concur that the PHP License 3.01 should not be used for random software written *in* PHP language, but I don't agree that this clause should be used for packages published on pear.php.net (PEAR libraries) and pecl.php.net (PHP extensions). I think the REJECT FAQ has to be changed and the interpretation needs to be changed to allow PECL extensions and PEAR libraries to be licensed under PHP License 3.01. I agree with Ondřej. the REJECT FAQ (PHP License) has outdated, that refer to PHP License 3.0 [0]. [0] https://lists.debian.org/debian-legal/2005/08/msg00128.html For the details: https://lists.debian.org/debian-legal/2006/02/msg00017.html https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332606 Regards, Prach -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751668: marked as done (libocas: Error in upstream license version)
Your message dated Thu, 26 Jun 2014 07:51:22 + with message-id e1x04so-0003qv...@franck.debian.org and subject line Bug#751668: fixed in libocas 0.93-2 has caused the Debian Bug report #751668, regarding libocas: Error in upstream license version 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.) -- 751668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libocas Version: 0.93-1 Severity: serious Justification: Policy 12.5 debian/copyright states that the upstream license is GPL-3+, when in fact it is GPL-3. ---End Message--- ---BeginMessage--- Source: libocas Source-Version: 0.93-2 We believe that the bug you reported is fixed in the latest version of libocas, 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 751...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Kastner deb...@kvr.at (supplier of updated libocas 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: Wed, 19 Feb 2014 15:33:14 +0100 Source: libocas Binary: libocas-dev libocas0 libocas-dbg libocas-tools Architecture: source amd64 Version: 0.93-2 Distribution: unstable Urgency: low Maintainer: Christian Kastner deb...@kvr.at Changed-By: Christian Kastner deb...@kvr.at Description: libocas-dbg - Debugging symbols for LIBOCAS libocas-dev - Development libraries and header files for LIBOCAS libocas-tools - Standalone applications implementing the OCAS solver libocas0 - OCAS solver for training linear SVM classifiers Closes: 751668 Changes: libocas (0.93-2) unstable; urgency=low . * debian/copyright: - Corrected upstream license version from GPL-3+ to GPL-3. Thanks to Vincent Cheng for catching this. Closes: #751668 * debian/control: - Bumped Standards-Version to 3.9.5 (no changes required) - Bumped debhelper dependency to 9 - Demoted libocas0's Recommends for libocas-tools to Suggests, so packages depending only on the library don't pull in the tools. * debian/compat: - Bumped debhelper compatibility level to recommended level 9 * debian/copyright: - Refreshed to machine-readable copyright format 1.0 * debian/rules: - Use DEB_CFLAGS_MAINT_APPEND, as recommended, instead of CFLAGS * debian/patches (modified): - 0001-Properly-build-shared-and-static-libraries-programs Include CPPFLAGS to avoid hardening flag warnings * debian/source/lintian-overrides: - Added override for debian-watch-may-check-gpg-signature * debian/libocas-tools.lintian-overrides: - Added override for arch-dep-package-has-big-usr-share Checksums-Sha1: 3c3f33f7a65d5bb26a7676dff89c41588aabae7f 1968 libocas_0.93-2.dsc bef03690df2b5b3481170701b03bf836d0c82697 5832 libocas_0.93-2.debian.tar.xz 1e8c5e4f44a690702d4ee52f7ff8093253c70c2f 17110 libocas-dev_0.93-2_amd64.deb 251b688115dbc6109946dd7214d2a341321d7d46 18598 libocas0_0.93-2_amd64.deb 88c6530b29cbe167d3c7c0ae3255c840c7e2f5ba 100998 libocas-dbg_0.93-2_amd64.deb 9284e599bb485e8069e467da5061887a05f9c0d9 3213334 libocas-tools_0.93-2_amd64.deb Checksums-Sha256: 8689da60dc410ad8fe0cbd2d34e3ce3ef4b49b791730af0cdc49f0e1302e7823 1968 libocas_0.93-2.dsc 505aca61f7ae61a524b83b8d9a49c41bfe49fde75c2910e39118c494b957b9ee 5832 libocas_0.93-2.debian.tar.xz 1b82a85e7dbce65ae5b512cdb67c44192848a7b5774c6656143b342b20dc2cbe 17110 libocas-dev_0.93-2_amd64.deb 173ed3acc0e98d554f688075bc083d4c8d38002e91fa3a8309d11f5f4fef4b13 18598 libocas0_0.93-2_amd64.deb aa2c28f5e90cd0d08fce43ecfa70b242f289793da2079b4783444f3ebf980810 100998 libocas-dbg_0.93-2_amd64.deb f2cb2392efb277e6343997f08e2c3930229eab7f9a948b5d83ef4a6c2086906e 3213334 libocas-tools_0.93-2_amd64.deb Files: 18ea7b3703f65768e70efafcf5836501 17110 libdevel optional libocas-dev_0.93-2_amd64.deb 8419a712fdf22f58019a0c6a923d85ab 18598 libs optional libocas0_0.93-2_amd64.deb 802990a94ab67d891c6814894d9c081e 100998 debug extra libocas-dbg_0.93-2_amd64.deb 8ec90bb855dff7681bc48eb89fbbf7c0 3213334 science optional libocas-tools_0.93-2_amd64.deb d1a41585a3b2fb6edb08320d55a75ae9 1968 libs optional
Bug#752749: [cpl-plugin-xshoo-calib] uninstallable: wrong directory name in wget command in postinst
Package: cpl-plugin-xshoo-calib
Version: 2.5.0+dfsg-1
Severity: serious
--- Please enter the report below this line. ---
in the postinst script, the package attempts to download
ftp://ftp.eso.org/pub/dfs/pipelines/${PIPELINE}/${KIT}.tar.gz
which after variable substitution becomes
ftp://ftp.eso.org/pub/dfs/pipelines/xshoo/xshoo-kit-2.5.0.tar.gz
while the correct URL would be
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-2.5.0.tar.gz
This makes the package uninstallable. This bug has been present for several
releases of the package, I am surprised nobody filed this bugreport before.
The fix appears trivial.
Bye
Giacomo
--- System information. ---
Architecture: amd64
Kernel: Linux 3.14.5-jak
Debian Release: jessie/sid
500 all liveusb.info
401 unstablewww.deb-multimedia.org
401 unstablemi.mirror.garr.it
401 unstableftp.debian.org
401 unstabledownload.jitsi.org
399 stable dl.google.com
399 stable deb.opera.com
10 experimentalftp.debian.org
10 experimentalcdn.debian.net
--- Package information. ---
Depends (Version) | Installed
===-+-===
cpl-plugin-xshoo| 2.5.0+dfsg-1
wget| 1.15-1+b1
Package's Recommends field is empty.
Package's Suggests field is empty.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751700: vdkbuilder2: FTBFS - libvdkxdb2-dev has been removed
Probably related to the disappearance of vdkxdb2, the package vdkbuilder2 isn't even installable in sid any more: the dependency on libvdkxdb2-2c2 is not satisfied. -Ralf. -- Ralf Treinen Laboratoire Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.pps.univ-paris-diderot.fr/~treinen/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748918: marked as done (postgrey fails to start)
Your message dated Thu, 26 Jun 2014 10:52:22 +0200 with message-id 20140626085222.ga6...@sym.noone.org and subject line Re: Bug#748918: postgrey fails to start has caused the Debian Bug report #748918, regarding postgrey fails to start to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 748918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: postgrey Version: 1.34-1.1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, A fresh install of postgrey on two Wheezy machines fails to start. Much like was the case in debian bug #722136, starting the postgrey daemon on the command line reveals the same failure mode: $ sudo postgrey --inet 10023 2014/05/22-19:09:07 postgrey (type Net::Server::Multiplex) starting! pid(15633) Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 Binding to TCP port 10023 on host 127.0.0.1 with IPv4 Insecure dependency in bind while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 202. Applying the same patch, https://github.com/yasuhirokimura/postgrey/commit/9673b54064691a5b9c295ffea340d8a1f9ee1cb8, fixes this problem for me. I wonder if the changes introduced with perl-base 5.14.2-21+deb7u1 created the problem, but I haven't found a perl-base 5.14.2-21 package to install to see if the problem goes away. -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (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 postgrey depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii libberkeleydb-perl 0.51-1 ii libnet-dns-perl0.66-2+b2 ii libnet-server-perl 2.006-1+deb7u1 ii perl 5.14.2-21+deb7u1 ii ucf3.0025+nmu3 Versions of packages postgrey recommends: ii libnet-rblclient-perl 0.5-2 ii libparse-syslog-perl 1.10-2 ii postfix2.9.6-2 postgrey suggests no packages. -- debconf information: postgrey/1.32-3_changeport: ---End Message--- ---BeginMessage--- Version: 1.34-1.2 Control: tag -1 + unreproducible moreinfo Hi Geoff, thanks for the report. Geoff Crompton wrote: Package: postgrey Version: 1.34-1.1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, A fresh install of postgrey on two Wheezy machines fails to start. Much like was the case in debian bug #722136, starting the postgrey daemon on the command line reveals the same failure mode: $ sudo postgrey --inet 10023 2014/05/22-19:09:07 postgrey (type Net::Server::Multiplex) starting! pid(15633) Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 Binding to TCP port 10023 on host 127.0.0.1 with IPv4 Insecure dependency in bind while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 202. Applying the same patch, https://github.com/yasuhirokimura/postgrey/commit/9673b54064691a5b9c295ffea340d8a1f9ee1cb8, fixes this problem for me. In that case this bug report is _the_ same issue as in #722136. Because #722136 has been fixed by applying exactly the patch you mentioned above. Closing this bug for the version in Testing and Unstable, but leaving it open in Wheezy for now. I wonder if the changes introduced with perl-base 5.14.2-21+deb7u1 created the problem, but I haven't found a perl-base 5.14.2-21 package to install to see if the problem goes away. You can find it http://snapshot.debian.org/package/perl/5.14.2-21/ A first glance at /usr/share/doc/perl/changelog.Debian.gz of 5.14.2-21+deb7u1 didn't reveal any changes which _obviously_ cause such breakage. But it would be nice if you could check if the perl stable update broke postgrey. I also can't reproduce this issue with my postgrey installations running under Wheezy (and with perl 5.14.2-21+deb7u1). Do you have any third-party APT repositories in your sources.list which may have updated some dependencies of postgrey? Can you run the which-pkg-broke tool from the debian-goodies package like this: $ which-pkg-broke postgrey and send the output to the bug report? Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126
Bug#728196: [Pkg-php-pecl] Bug#728196: Bug#728196: Bug#728196: php-gearman is licensed under the PHP license, and is not php
On Thu, Jun 26, 2014, at 09:41, Prach Pongpanich wrote: Hi, On Tue, Jun 24, 2014 at 5:14 PM, Ondřej Surý ond...@sury.org wrote: Control: reassign -1 ftp.debian.org Control: retitle -1 Reassess PHP License usage for PHP PECL extensions Hi Paul and rest of FTP Masters, I am reassigning this bug to FTP Masters to solve it in between FTP Masters. Please note that Paul's interpretation would effectively lead to full removal of PHP from the Debian archive - see the list of affected packages in the bug (and in my previous email from May 27). I concur that the PHP License 3.01 should not be used for random software written *in* PHP language, but I don't agree that this clause should be used for packages published on pear.php.net (PEAR libraries) and pecl.php.net (PHP extensions). I think the REJECT FAQ has to be changed and the interpretation needs to be changed to allow PECL extensions and PEAR libraries to be licensed under PHP License 3.01. 3.0 and 3.01 is almost identical and I did have a long chat with FTP Masters and the conclusion was that PHP License in any version cannot be used for anything not copyrighted by PHP Group, e.g. basically anything not PHP itself. f.e. php-json is fine because it is a copy of ext/json/ with some modifications, but most of the other random software authored by random people is not. So you either need to convince upstream authors to use some more appropriate license, or you need to show that the software in fact comes from the PHP Group (that might be in fact the case in some packages). O. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 670681, retitle 670681 to postgrey: stop action of init script does not work
Processing commands for cont...@bugs.debian.org: # same issue on our Wheezy postgrey installation, reproducible tags 670681 + confirmed Bug #670681 [postgrey] /etc/init.d/postgrey script doesn't work properly Added tag(s) confirmed. retitle 670681 postgrey: stop action of init script does not work Bug #670681 [postgrey] /etc/init.d/postgrey script doesn't work properly Changed Bug title to 'postgrey: stop action of init script does not work' from '/etc/init.d/postgrey script doesn't work properly' thanks Stopping processing here. Please contact me if you need assistance. -- 670681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670681 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#670681: /etc/init.d/postgrey script doesn't work properly
Processing control commands: tag -1 + confirmed Bug #670681 [postgrey] postgrey: stop action of init script does not work Ignoring request to alter tags of bug #670681 to the same tags previously set -- 670681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670681 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#670681: /etc/init.d/postgrey script doesn't work properly
Control: tag -1 + confirmed Hi, Andreas Metzler wrote: FYI this totally broke greylisting for me after upgrading to wheezy and migrating to a new server as service postgrey restart did not restart the daemon and therefore did not apply the configuration changes I made which were necessary for a working postgrey installation. While I disagree with totally broke greylisting... I am therefore upgrading the bug-severity (rationale makes the package in question unusable or mostly so). ... or makes the package in question unusable or mostly so (which is a reason for grave, but not for serious btw.), I do agree with RC-severity and can confirm the issue. :-) I'll look into the patch and will likely do an NMU for Sid as a start. I may look into a stable update for Wheezy later, too. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748918: postgrey fails to start
Control: tag -1 - moreinfo Hi, Axel Beckert wrote: A fresh install of postgrey on two Wheezy machines fails to start. [...] I also can't reproduce this issue with my postgrey installations running under Wheezy (and with perl 5.14.2-21+deb7u1). Do you have any third-party APT repositories in your sources.list which may have updated some dependencies of postgrey? Can you run the which-pkg-broke tool from the debian-goodies package like this: $ which-pkg-broke postgrey Sorry, this is unnecessary on fresh installs. No need to check this. Will check in a VM with a virgin Wheezy if I can reproduce the issue there. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- 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#748918: postgrey fails to start
Processing control commands:
tag -1 - moreinfo
Bug #748918 {Done: Axel Beckert a...@debian.org} [postgrey] postgrey fails to
start
Ignoring request to alter tags of bug #748918 to the same tags previously set
--
748918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748918
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#748918: postgrey fails to start
Processing control commands:
tag -1 - moreinfo
Bug #748918 {Done: Axel Beckert a...@debian.org} [postgrey] postgrey fails to
start
Ignoring request to alter tags of bug #748918 to the same tags previously set
--
748918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748918
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#670681: /etc/init.d/postgrey script doesn't work properly
Control: found -1 1.34-1.2 Axel Beckert wrote: [...] can confirm the issue. :-) ... in Wheezy as well as in Jessie and Sid. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- 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#670681: /etc/init.d/postgrey script doesn't work properly
Processing control commands: found -1 1.34-1.2 Bug #670681 [postgrey] postgrey: stop action of init script does not work Marked as found in versions postgrey/1.34-1.2. -- 670681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670681 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#752449: openimageio: FTBFS on powerpc and s390x: Package pdftex.def Error: File `figures/flip.jpg' not found
tag 752449 + patch
thanks
On Mon, Jun 23, 2014 at 05:51:22PM +0200, Emilio Pozuelo Monfort wrote:
Package: src:openimageio
Version: 1.4.9~dfsg0-2
Severity: serious
openimageio 1.4.9~dfsg0-2 seems much better build-wise than 1.4.9~dfsg0-1.
Still, it failed to build on powerpc and s390x:
! Package pdftex.def Error: File `figures/flip.jpg' not found.
See the pdftex.def package documentation for explanation.
Type H return for immediate help.
...
l.382 ...egraphics[width=1.25in]{figures/flip.jpg}
\\
! == Fatal error occurred, no output PDF file produced!
Transcript written on openimageio.log.
make[2]: *** [openimageio.pdf] Error 1
See
https://buildd.debian.org/status/logs.php?pkg=openimageiover=1.4.9~dfsg0-2suite=sid
All these platforms are big endian. In most of the case it means a
pointer is casted to do a type conversion. This is also the case there,
in the atomic_exchange_and_add() function. A pointer to long long is
cast to a pointer to int. In practice the cast is not even needed, so I
also removed it in the int case.
Note that the issue also concerns little endian platform, though it only
affects negative values and values greater than 2**31.
--- openimageio-1.4.10~dfsg0.orig/src/include/OpenImageIO/thread.h
+++ openimageio-1.4.10~dfsg0/src/include/OpenImageIO/thread.h
@@ -220,7 +220,7 @@ atomic_exchange_and_add (volatile int *a
#ifdef NOTHREADS
int r = *at; *at += x; return r;
#elif defined(OIIO_USE_GCC_NEW_ATOMICS)
-return __atomic_fetch_add ((int *)at, x, __ATOMIC_SEQ_CST);
+return __atomic_fetch_add (at, x, __ATOMIC_SEQ_CST);
#elif defined(USE_GCC_ATOMICS)
return __sync_fetch_and_add ((int *)at, x);
#elif defined(_MSC_VER)
@@ -239,7 +239,7 @@ atomic_exchange_and_add (volatile long l
#ifdef NOTHREADS
long long r = *at; *at += x; return r;
#elif defined(OIIO_USE_GCC_NEW_ATOMICS)
-return __atomic_fetch_add ((int *)at, x, __ATOMIC_SEQ_CST);
+return __atomic_fetch_add (at, x, __ATOMIC_SEQ_CST);
#elif defined(USE_GCC_ATOMICS)
return __sync_fetch_and_add (at, x);
#elif defined(_MSC_VER)
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752749: marked as done ([cpl-plugin-xshoo-calib] uninstallable: wrong directory name in wget command in postinst)
Your message dated Thu, 26 Jun 2014 09:50:01 +
with message-id e1x06jd-00037c...@franck.debian.org
and subject line Bug#752749: fixed in cpl-plugin-xshoo 2.5.0+dfsg-2
has caused the Debian Bug report #752749,
regarding [cpl-plugin-xshoo-calib] uninstallable: wrong directory name in wget
command in postinst
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.)
--
752749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: cpl-plugin-xshoo-calib
Version: 2.5.0+dfsg-1
Severity: serious
--- Please enter the report below this line. ---
in the postinst script, the package attempts to download
ftp://ftp.eso.org/pub/dfs/pipelines/${PIPELINE}/${KIT}.tar.gz
which after variable substitution becomes
ftp://ftp.eso.org/pub/dfs/pipelines/xshoo/xshoo-kit-2.5.0.tar.gz
while the correct URL would be
ftp://ftp.eso.org/pub/dfs/pipelines/xshooter/xshoo-kit-2.5.0.tar.gz
This makes the package uninstallable. This bug has been present for several
releases of the package, I am surprised nobody filed this bugreport before.
The fix appears trivial.
Bye
Giacomo
--- System information. ---
Architecture: amd64
Kernel: Linux 3.14.5-jak
Debian Release: jessie/sid
500 all liveusb.info
401 unstablewww.deb-multimedia.org
401 unstablemi.mirror.garr.it
401 unstableftp.debian.org
401 unstabledownload.jitsi.org
399 stable dl.google.com
399 stable deb.opera.com
10 experimentalftp.debian.org
10 experimentalcdn.debian.net
--- Package information. ---
Depends (Version) | Installed
===-+-===
cpl-plugin-xshoo| 2.5.0+dfsg-1
wget| 1.15-1+b1
Package's Recommends field is empty.
Package's Suggests field is empty.
---End Message---
---BeginMessage---
Source: cpl-plugin-xshoo
Source-Version: 2.5.0+dfsg-2
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-xshoo, 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 752...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher deb...@liska.ath.cx (supplier of updated cpl-plugin-xshoo
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: Thu, 26 Jun 2014 11:23:14 +0200
Source: cpl-plugin-xshoo
Binary: cpl-plugin-xshoo cpl-plugin-xshoo-doc cpl-plugin-xshoo-calib
Architecture: source all amd64
Version: 2.5.0+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Maintainers
debian-astro-maintain...@lists.alioth.debian.org
Changed-By: Ole Streicher deb...@liska.ath.cx
Description:
cpl-plugin-xshoo - ESO data reduction pipeline for XSHOOTER
cpl-plugin-xshoo-calib - ESO data reduction pipeline calibration data
downloader for XSHOO
cpl-plugin-xshoo-doc - ESO data reduction pipeline documentation for XSHOOTER
Closes: 752749
Changes:
cpl-plugin-xshoo (2.5.0+dfsg-2) unstable; urgency=low
.
* Fix directory name for calibration files download. Closes: #752749
Checksums-Sha1:
fd018f5d34e42ec08be62d0747eba095ec1a2bb6 2354 cpl-plugin-xshoo_2.5.0+dfsg-2.dsc
71532af93d60290d1f07927cdd2b41d8ea8b0cd4 9704
cpl-plugin-xshoo_2.5.0+dfsg-2.debian.tar.xz
26a5e314b905bd78517f671d9a2f851215329c0f 218260
cpl-plugin-xshoo-doc_2.5.0+dfsg-2_all.deb
8d1d9bcd2f073141e9fb428ede2ac9cd7ade83e9 62754
cpl-plugin-xshoo-calib_2.5.0+dfsg-2_all.deb
75d6faa2936b46340e32afe07bc2579a0f6cb0f8 1096978
cpl-plugin-xshoo_2.5.0+dfsg-2_amd64.deb
Checksums-Sha256:
96cbb56430f995298855e5a2f87d096131ddfa92473f49c9ecb3542c5317f6a0 2354
cpl-plugin-xshoo_2.5.0+dfsg-2.dsc
a8a8ce2716582c2fb133eb1605bf97a2c0620f85da9a2b98b9a13301991a6c8c 9704
cpl-plugin-xshoo_2.5.0+dfsg-2.debian.tar.xz
9f54a850f776c724d792fef4b49462e725161d3b16527432a0dd9777f6c2862f 218260
cpl-plugin-xshoo-doc_2.5.0+dfsg-2_all.deb
ccd7b6069ec726174055eae2e6de3fbfdceac6932d33c15a744dd4df3c9d618b 62754
cpl-plugin-xshoo-calib_2.5.0+dfsg-2_all.deb
5642b87c8b56e216fd2d2b14973737f3dc2830efb3128f7750f4a58cf93939e1 1096978
cpl-plugin-xshoo_2.5.0+dfsg-2_amd64.deb
Files:
Processed: tecnoballz: FTBFS: make[4]: *** No rule to make target 'supervisor.c', needed by 'supervisor.o'. Stop.
Processing control commands: owner -1 ! Bug #750249 [src:tecnoballz] tecnoballz: FTBFS: make[4]: *** No rule to make target 'supervisor.c', needed by 'supervisor.o'. Stop. Owner recorded as Markus Koschany a...@gambaru.de. -- 750249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750249 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#750249: tecnoballz: FTBFS: make[4]: *** No rule to make target 'supervisor.c', needed by 'supervisor.o'. Stop.
Control: owner -1 ! I'm taking care of this bug. Perhaps I can fix some more in this process. Markus signature.asc Description: OpenPGP digital signature
Bug#746916: NMU debdiff for soprano_2.9.4+dfsg-1.1
On Wed, 2014-06-25 14:12:17 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: On Wednesday 25 June 2014 22:30:34 Aníbal Monsalve Salazar wrote: debdiff soprano_2.9.4+dfsg-1.dsc soprano_2.9.4+dfsg-1.1.dsc diff -Nru soprano-2.9.4+dfsg/debian/changelog soprano-2.9.4+dfsg/debian/changelog --- soprano-2.9.4+dfsg/debian/changelog 2013-11-04 15:13:52.0 + +++ soprano-2.9.4+dfsg/debian/changelog 2014-06-24 10:47:30.0 +0100 @@ -1,3 +1,13 @@ +soprano (2.9.4+dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Update symbols file. +Patch by Sphinx Jiang yishan...@gmail.com. +Work done for Debian GSOC2014. +Closes: #746916. This doesn't seems to be a patch generated by pkgkde-symbolshelper. I'm not even sure if it was done with build logs of all archs available or just one arch. Symbols need to be managed differently, it's not just a matter of building in one arch and diffing. You can take a look at [0] [0] http://pkg-kde.alioth.debian.org/symbolfiles.html Even after completing those steps you need to push to the archive and see what FTBFS, as (AFAIU) not all archs have already switched to gcc 4.9. So it's not strange to need more than one upload to fix the issue. I would recommend letting the maintainer solve this with time (maybe even waiting for a new upstream release, except if the package is holding a transition). Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ Hello Lisandro and Sphinx, I tested the patch by building soprano on three arches: mips, mipsel and amd64. I think Sphinx did the same on mips64el and maybe other arches but I'm not sure. Yesterday, I uploaded soprano_2.9.4+dfsg-1.1 to delayed/2 and today I moved it to delayed/10. Please let me know what would you like me to do. :-) Regards, Aníbal signature.asc Description: Digital signature
Bug#728196: Sources licensed under PHP License and not being PHP are not distributable
Hi everyone, I should have done this earlier before cloning the bugs, so here's some more background on the bugs filled. I did have a quite long and extensive chat with FTP Masters and our conclusion was that PHP License (any version) is suitable only for software that comes directly from PHP Group, that basically means only PHP (src:php5) itself. We have several options to do here: 1. Ask upstream to re-license the software to different free license - BSD or MIT/Expat is the closest one. 2. Show that the software in question does come from PHP Group, f.e. software based on src:php5 sources. Most notable example is src:php-json which is copy of ext/json/ adapted to libjson-c-dev instead of the included JSON-IS-EVIL library. 3. We remove the source packages from Debian. One more note: PHP is *not* compatible with GPL[1]. If you have sources that combine PHP-licensed source with GPL-licenced source the result is not distributable. That includes linking GPL library to PHP licenced source (e.g. libreadline as most notable example of GPL library). While doing the copyright research I have found two such examples and Ansgar was that kind that he filled: #752625 and #752627 Full list of bugs filled under this: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=ondrej%40debian.orgtag=php-license-3.01 If you feel to dispute this please take your *well-formed* and *well-thought* arguments to debian-legal. Ondrej [1] https://www.gnu.org/licenses/license-list.html#PHP-3.01 -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752760: freemind: Impossible to open .mm files created with older version
Package: freemind Version: 0.9.0+dfsg2-1 Severity: grave Justification: renders package unusable Dear Maintainer, It is impossible to open .mm files created with an older version of freemind (0.8.1 in my case) with 0.9.0 version, i have this error with all files : Error while parsing file:freemind.main.XMLParseException: XML Parse Exception during parsing of a map element at line 1: Expected: = This bug is resolved in new upstream version 1.0.1 (see http://sourceforge.net/p/freemind/bugs/1147/) : I checked the 1.0.1 zip binaries for any operating system - max from their website. Regards, Sébastien KALT -- Package-specific info: [debug] /usr/bin/freemind: Found JAVA_HOME = '/usr/lib/jvm/java-7-openjdk-amd64' [debug] /usr/bin/freemind: Found JAVA_CMD = '/usr/lib/jvm/java-7-openjdk-amd64/bin/java' DEBUG: Freemind parameters are ''. DEBUG: Linux plume 3.15-1.slh.2-aptosid-amd64 #1 SMP PREEMPT Fri Jun 20 04:15:04 UTC 2014 x86_64 GNU/Linux DEBUG: LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3. 2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Debian Description:Debian GNU/Linux unstable (sid) Release:unstable Codename: sid DEBUG: The following DEB packages are installed: ii freemind0.9.0+dfsg2-1 allJava Program for creating and viewing Mindmaps ii freemind-doc0.9.0+dfsg2-1 all Documentation for FreeMind ii freemind-plugins-help 0.9.0+dfsg2-1 allJava Plugin for FreeMind to show an extended online help ii freemind-plugins-svg0.9.0+dfsg2-1 allJava Plugin for FreeMind to export Mindmaps to SVG and PDF DEBUG: Link '/usr/bin/freemind' resolved to '/usr/share/freemind/freemind.sh'. DEBUG: Freemind Directory is '/usr/share/freemind'. DEBUG: Calling: '/usr/lib/jvm/java-7-openjdk-amd64/bin/java -Dgnu.java.awt.peer.gtk.Graphics=Graphics2D -Dfreemind.base.dir=/usr/share/freemind -cp ::/usr/share/freemind/lib/freemind.jar:/usr/share/java/SimplyHTML.jar:/usr/share/java/gnu-regexp.jar:/usr/share/java/jibx-run-1.1.6a.jar:/usr/share/java/xpp3.jar:/usr/share/freemind/lib/bindings.jar:/usr/share/java/forms.jar:/usr/share/freemind freemind.main.FreeMindStarter '. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (980, 'unstable'), (970, 'testing'), (960, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.15-1.slh.2-aptosid-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages freemind depends on: ii default-jre 2:1.7-52 ii libjgoodies-forms-java 1.6.0-4 ii libjibx1.1-java 1.1.6a-4 ii simplyhtml 0.16.08-1 Versions of packages freemind recommends: ii freemind-doc 0.9.0+dfsg2-1 ii java-wrappers 0.1.28 ii xdg-utils 1.1.0~rc1+git20111210-7.1 Versions of packages freemind suggests: pn freemind-browser none ii freemind-plugins-help0.9.0+dfsg2-1 pn freemind-plugins-script none ii freemind-plugins-svg 0.9.0+dfsg2-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747030: marked as done (dragonegg: ICE on simple program with gcc-4.7 4.7.3-13 and gcc-4.8 4.8.2-21)
Your message dated Thu, 26 Jun 2014 11:00:07 +
with message-id e1x07pt-0001yv...@franck.debian.org
and subject line Bug#747030: fixed in dragonegg 3.4-1
has caused the Debian Bug report #747030,
regarding dragonegg: ICE on simple program with gcc-4.7 4.7.3-13 and gcc-4.8
4.8.2-21
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.)
--
747030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: dragonegg-4.8
Version: 3.3-2
Severity: grave
Justification: renders package unusable
ypig:~ cat ice.i
int d;
int main (void)
{
return d;
}
ypig:~ /usr/bin/llvm-gcc-4.8 -c ice.i
var_decl 0x7f3bfa622260 d
type integer_type 0x7f3bfa6155e8 int public SI
size integer_cst 0x7f3bfa6180c0 constant 32
unit size integer_cst 0x7f3bfa6180e0 constant 4
align 32 symtab 0 alias set 0 canonical type 0x7f3bfa6155e8 precision
32 min integer_cst 0x7f3bfa618060 -2147483648 max integer_cst 0x7f3bfa618080
2147483647
pointer_to_this pointer_type 0x7f3bfa61d2a0
asm_written used public static common SI file ice.i line 1 col 5 size
integer_cst 0x7f3bfa6180c0 32 unit size integer_cst 0x7f3bfa6180e0 4
align 32 context translation_unit_decl 0x7f3bfa72c000 D.1725
(mem/c:SI (symbol_ref:DI (d) var_decl 0x7f3bfa622260 d) [0 d+0 S4 A32])
chain function_decl 0x7f3bfa72a000 main
pointer_type 0x7f3c01b9f0e3*** WARNING *** there are active plugins, do not
report this as a bug unless you can reproduce it without enabling any plugins.
Event| Plugins
PLUGIN_FINISH_UNIT | dragonegg
PLUGIN_FINISH| dragonegg
PLUGIN_START_UNIT| dragonegg
PLUGIN_ALL_IPA_PASSES_END| dragonegg
ice.i: In function ‘main’:
ice.i:4:3: internal compiler error: Segmentation fault
return d;
^
gcc-4.8.real: internal compiler error: Segmentation fault (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions.
In particular, this makes an autoconf-generated configure script
fail very early:
checking whether we are cross compiling... configure: error: in
`/tmp/mpfrtests-vlefevre-6206/obj':
configure: error: cannot run C compiled programs.
(this test is not specific to MPFR, it's just an autoconf test).
This makes llvm-gcc unusable in practice.
-- 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-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dragonegg-4.8 depends on:
ii libc6 2.18-5
ii libffi6 3.1~rc1+r3.0.13-12
ii libgcc1 1:4.9.0-2
ii libllvm3.3 1:3.3-16
ii libstdc++6 4.9.0-2
Versions of packages dragonegg-4.8 recommends:
ii g++-4.8 4.8.2-21
ii gcc-4.8 4.8.2-21
dragonegg-4.8 suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: dragonegg
Source-Version: 3.4-1
We believe that the bug you reported is fixed in the latest version of
dragonegg, 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 747...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru sylves...@debian.org (supplier of updated dragonegg 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, 22 Jun 2014 16:35:33 -0700
Source: dragonegg
Binary: dragonegg llvm-gcc
Architecture: source amd64
Version: 3.4-1
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org
Changed-By: Sylvestre Ledru sylves...@debian.org
Description:
dragonegg - GCC plugin that uses LLVM for optimization and code generation
llvm-gcc - C front end for LLVM C/C++ compiler
Closes: 735754 747030 751302
Changes:
dragonegg (3.4-1) unstable; urgency=medium
.
* New upstream version (Closes: #747030)
* Only support a single version of gcc
*
Bug#735754: marked as done (dragonegg: FTBFS: ABIHack.inc:1666:36: error: 'TARGET_CPU_DEFAULT_max' was not declared in this scope)
Your message dated Thu, 26 Jun 2014 11:00:07 + with message-id e1x07pt-0001yr...@franck.debian.org and subject line Bug#735754: fixed in dragonegg 3.4-1 has caused the Debian Bug report #735754, regarding dragonegg: FTBFS: ABIHack.inc:1666:36: error: 'TARGET_CPU_DEFAULT_max' was not declared in this scope 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.) -- 735754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: dragonegg Version: 3.3-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140114 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' gcc-4.8 --version /dev/null /usr/lib/llvm-3.3/bin/llvm-config --version /dev/null Compiling utils/TargetInfo.cpp g++-4.8 -c \ -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -MD -MP -DIN_GCC -DLLVM_VERSION=\3.3\ -DTARGET_TRIPLE=\x86_64-linux-gnu\ -DGCC_MAJOR=4 -DGCC_MINOR=8 -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include -isystem/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include -DDISABLE_VERSION_CHECK -DENABLE_BUILD_WITH_CXX -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra -fvisibility=hidden -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2 -fomit-frame-pointer -fvisibility-inlines-hidden -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual /«PKGBUILDDIR»/utils/TargetInfo.cpp Linking TargetInfo g++-4.8 -o TargetInfo TargetInfo.o -lLLVMSupport \ -L/usr/lib/llvm-3.3/lib -lpthread -lffi -ldl -lm -L/usr/lib/llvm-3.3/lib -Wl,-z,relro Compiling Aliasing.cpp g++-4.8 -c -I/«PKGBUILDDIR»/include/x86 -I/«PKGBUILDDIR»/include/linux -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -MD -MP -DIN_GCC -DLLVM_VERSION=\3.3\ -DTARGET_TRIPLE=\x86_64-linux-gnu\ -DGCC_MAJOR=4 -DGCC_MINOR=8 -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include -isystem/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include -DDISABLE_VERSION_CHECK -DENABLE_BUILD_WITH_CXX -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra -fvisibility=hidden -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2 -fomit-frame-pointer -fvisibility-inlines-hidden -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual /«PKGBUILDDIR»/src/Aliasing.cpp Compiling Backend.cpp g++-4.8 -c -I/«PKGBUILDDIR»/include/x86 -I/«PKGBUILDDIR»/include/linux -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -MD -MP -DIN_GCC -DLLVM_VERSION=\3.3\ -DTARGET_TRIPLE=\x86_64-linux-gnu\ -DGCC_MAJOR=4 -DGCC_MINOR=8 -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include -isystem/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/include -DDISABLE_VERSION_CHECK -DENABLE_BUILD_WITH_CXX -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wextra -fvisibility=hidden -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2 -fomit-frame-pointer -fvisibility-inlines-hidden -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual /«PKGBUILDDIR»/src/Backend.cpp In file included from /usr/lib/llvm-3.3/include/llvm/CodeGen/Passes.h:19:0, from /usr/lib/llvm-3.3/include/llvm/CodeGen/MachinePassRegistry.h:21, from /usr/lib/llvm-3.3/include/llvm/CodeGen/RegAllocRegistry.h:18, from /«PKGBUILDDIR»/src/Backend.cpp:37: /usr/lib/llvm-3.3/include/llvm/Target/TargetMachine.h:251:16: warning: unused parameter 'StartAfter' [-Wunused-parameter] virtual bool addPassesToEmitFile(PassManagerBase , ^ /usr/lib/llvm-3.3/include/llvm/Target/TargetMachine.h:251:16: warning: unused parameter 'StopAfter' [-Wunused-parameter] Compiling Cache.cpp g++-4.8 -c -I/«PKGBUILDDIR»/include/x86 -I/«PKGBUILDDIR»/include/linux -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-3.3/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
Bug#746916: NMU debdiff for soprano_2.9.4+dfsg-1.1
Hi Lisandro and Aníbal, I test the patch on mips64el, amd64 and i386, and when changing I kept the symbols won't affect other archs. If anything I could do, please let me know. Regards, Sphinx 2014-06-26 18:30 GMT+08:00 Aníbal Monsalve Salazar ani...@debian.org: On Wed, 2014-06-25 14:12:17 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: On Wednesday 25 June 2014 22:30:34 Aníbal Monsalve Salazar wrote: debdiff soprano_2.9.4+dfsg-1.dsc soprano_2.9.4+dfsg-1.1.dsc diff -Nru soprano-2.9.4+dfsg/debian/changelog soprano-2.9.4+dfsg/debian/changelog --- soprano-2.9.4+dfsg/debian/changelog 2013-11-04 15:13:52.0 + +++ soprano-2.9.4+dfsg/debian/changelog 2014-06-24 10:47:30.0 +0100 @@ -1,3 +1,13 @@ +soprano (2.9.4+dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Update symbols file. +Patch by Sphinx Jiang yishan...@gmail.com. +Work done for Debian GSOC2014. +Closes: #746916. This doesn't seems to be a patch generated by pkgkde-symbolshelper. I'm not even sure if it was done with build logs of all archs available or just one arch. Symbols need to be managed differently, it's not just a matter of building in one arch and diffing. You can take a look at [0] [0] http://pkg-kde.alioth.debian.org/symbolfiles.html Even after completing those steps you need to push to the archive and see what FTBFS, as (AFAIU) not all archs have already switched to gcc 4.9. So it's not strange to need more than one upload to fix the issue. I would recommend letting the maintainer solve this with time (maybe even waiting for a new upstream release, except if the package is holding a transition). Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ Hello Lisandro and Sphinx, I tested the patch by building soprano on three arches: mips, mipsel and amd64. I think Sphinx did the same on mips64el and maybe other arches but I'm not sure. Yesterday, I uploaded soprano_2.9.4+dfsg-1.1 to delayed/2 and today I moved it to delayed/10. Please let me know what would you like me to do. :-) Regards, Aníbal
Bug#752762: load-module module-alsa-sink freezes display
Package: pulseaudio Version: 5.0-2 Severity: grave I simply uncommented the line #load-module module-alsa-sink in /etc/pulse/default.pa and resarted pulseaudio to completely freeze my X. Mouse was still working but I wasn't able to focus on any window, let alone type into one or log out. After a reboot I noticed that with that setting my whole X sessions starts up, but the screen remains blank. According to syslog the module failed to load: Jun 26 12:54:57 feivel pulseaudio[3128]: [pulseaudio] module.c: Failed to load module module-alsa-sink (argument: ): initialization failed. But that IMO hardly qualifies as a reason for the display to disappear. It'd also be interesting to know why the module failed, but there doesn't seem to be anything in the logs. I tried using this module in an attempt to figure out why my sound doesn't work correctly, or in other words, not at all when using the defaults. Finally I'm not sure about the severity, but you can (and I did) lose data because of the loss of the X session. Michael -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pulseaudio depends on: ii adduser 3.113+nmu3 ii libasound21.0.27.2-4 ii libasound2-plugins1.0.27-2.1 ii libc6 2.19-4 ii libcap2 1:2.22-1.2 ii libdbus-1-3 1.8.4-1 ii libfftw3-single3 3.3.4-1 ii libgcc1 1:4.9.0-7 ii libice6 2:1.0.8-2 ii libltdl7 2.4.2-1.7 ii liborc-0.4-0 1:0.4.21-1 ii libpulse0 5.0-2 ii libsamplerate00.1.8-7 ii libsm62:1.2.1-2 ii libsndfile1 1.0.25-9 ii libspeexdsp1 1.2~rc1.1-1 ii libstdc++64.9.0-7 ii libsystemd-login0 204-12 ii libtdb1 1.3.0-1.1 ii libudev1 204-12 ii libwebrtc-audio-processing-0 0.1-2 ii libx11-6 2:1.6.2-2 ii libx11-xcb1 2:1.6.2-2 ii libxcb1 1.10-3 ii libxtst6 2:1.2.2-1 ii lsb-base 4.1+Debian13 ii udev 204-12 Versions of packages pulseaudio recommends: ii pulseaudio-module-x11 5.0-2 ii rtkit 0.11-1 Versions of packages pulseaudio suggests: ii paman 0.9.4-1 ii paprefs 0.9.10-1 ii pavucontrol 2.0-2 ii pavumeter 0.9.3-4 ii pulseaudio-utils 5.0-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752107: marked as done (mke2fs apparently lacks large file support)
Your message dated Thu, 26 Jun 2014 11:51:17 + with message-id e1x08cz-00089r...@franck.debian.org and subject line Bug#752107: fixed in e2fsprogs 1.42.10-1.1 has caused the Debian Bug report #752107, regarding mke2fs apparently lacks large file support 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.) -- 752107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libguestfs Version: 1:1.26.3 Severity: serious Justification: fails to build from source (but built successfully in the past) After the recent binutils fix, it still fails on mips and mipsel. ---End Message--- ---BeginMessage--- Source: e2fsprogs Source-Version: 1.42.10-1.1 We believe that the bug you reported is fixed in the latest version of e2fsprogs, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen ben...@debian.org (supplier of updated e2fsprogs 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: Sat, 21 Jun 2014 12:57:25 +0200 Source: e2fsprogs Binary: e2fsck-static libcomerr2 comerr-dev libss2 ss-dev e2fsprogs-udeb e2fslibs e2fslibs-dev e2fsprogs e2fsprogs-dbg e2fslibs-dbg libcomerr2-dbg libss2-dbg Architecture: source amd64 Version: 1.42.10-1.1 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen ben...@debian.org Changed-By: Hilko Bengen ben...@debian.org Description: comerr-dev - common error description library - headers and static libraries e2fsck-static - statically-linked version of the ext2/ext3/ext4 filesystem checke e2fslibs - ext2/ext3/ext4 file system libraries e2fslibs-dbg - debugging information for e2fslibs e2fslibs-dev - ext2/ext3/ext4 file system libraries - headers and static librari e2fsprogs - ext2/ext3/ext4 file system utilities e2fsprogs-dbg - debugging information for e2fsprogs e2fsprogs-udeb - stripped-down versions of e2fsprogs, for debian-installer (udeb) libcomerr2 - common error description library libcomerr2-dbg - debugging information for libcomerr2 libss2 - command-line interface parsing library libss2-dbg - debugging information for libss2 ss-dev - command-line interface parsing library - headers and static libra Closes: 752107 Changes: e2fsprogs (1.42.10-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add patch from upstream git that fixes creating filesystems in files larger than 2GB on 32 bit architectures (Closes: #752107) Checksums-Sha1: 8b39ef0ab374897f38098029df112904d02e61b1 1914 e2fsprogs_1.42.10-1.1.dsc 46bd56c8fb8ae8e2d7c18e50602978fbd9374ae0 63896 e2fsprogs_1.42.10-1.1.debian.tar.xz c825ca0a7613b9c0b90a6eab99b2f3ff2dfc2814 246688 e2fsck-static_1.42.10-1.1_amd64.deb 010ef30e36240b23cd893215399c4d494f17ad9d 58808 libcomerr2_1.42.10-1.1_amd64.deb e3578fc7f3f93b7fb29c06cfb798bcf8043e8e51 62938 libss2_1.42.10-1.1_amd64.deb 73e41a2c98206cd81a66196064a90823cf0e4a34 181876 e2fslibs_1.42.10-1.1_amd64.deb 9a86574d9f6c227d3cd060d0d87f05749c1d4c1e 202080 e2fslibs-dev_1.42.10-1.1_amd64.deb 4b3f9900043bf661a91d8ff69046ffb26cc36b2e 676340 e2fsprogs_1.42.10-1.1_amd64.deb 86de349e96ebe3f528b9f4663e4ba4ab35a74016 949720 e2fsprogs-dbg_1.42.10-1.1_amd64.deb 92c6223420b20ec35b97628580795a4d7769f017 316920 e2fslibs-dbg_1.42.10-1.1_amd64.deb c59ab39aa5be2e77c4d09c3c3cf6c790229a0176 62118 libcomerr2-dbg_1.42.10-1.1_amd64.deb ea76cfa0131277f7472d77b3694e145ea0e45279 73806 libss2-dbg_1.42.10-1.1_amd64.deb 3f52e6cf974ac8b5c94c6065e89faf105f7d58b4 38300 comerr-dev_2.1-1.42.10-1.1_amd64.deb 40ed399189e9452a5cf22e64bb4a8d44ba470e34 16870 ss-dev_2.0-1.42.10-1.1_amd64.deb 5d1a4e1478772d09e4f18332416bdfe180d4ce70 255220 e2fsprogs-udeb_1.42.10-1.1_amd64.udeb Checksums-Sha256: 35060c30b5a5136ad83727e118d7e26bb975d697c9172204a4039f4af9e7de6c 1914 e2fsprogs_1.42.10-1.1.dsc f8b09ab3f526d1d76c8ce1185f21d358014f2752874e9083cab2162a60721ba8 63896 e2fsprogs_1.42.10-1.1.debian.tar.xz 7683120168f384d6f4886d6bfa7579f9806079c8489018be3d2973dea792fdea 246688 e2fsck-static_1.42.10-1.1_amd64.deb
Bug#752449: marked as done (openimageio: FTBFS on powerpc and s390x: Package pdftex.def Error: File `figures/flip.jpg' not found)
Your message dated Thu, 26 Jun 2014 11:51:52 +
with message-id e1x08dy-0008ke...@franck.debian.org
and subject line Bug#752449: fixed in openimageio 1.4.10~dfsg0-2
has caused the Debian Bug report #752449,
regarding openimageio: FTBFS on powerpc and s390x: Package pdftex.def Error:
File `figures/flip.jpg' not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
752449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:openimageio
Version: 1.4.9~dfsg0-2
Severity: serious
openimageio 1.4.9~dfsg0-2 seems much better build-wise than 1.4.9~dfsg0-1.
Still, it failed to build on powerpc and s390x:
! Package pdftex.def Error: File `figures/flip.jpg' not found.
See the pdftex.def package documentation for explanation.
Type H return for immediate help.
...
l.382 ...egraphics[width=1.25in]{figures/flip.jpg}
\\
! == Fatal error occurred, no output PDF file produced!
Transcript written on openimageio.log.
make[2]: *** [openimageio.pdf] Error 1
See
https://buildd.debian.org/status/logs.php?pkg=openimageiover=1.4.9~dfsg0-2suite=sid
Emilio
---End Message---
---BeginMessage---
Source: openimageio
Source-Version: 1.4.10~dfsg0-2
We believe that the bug you reported is fixed in the latest version of
openimageio, 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 752...@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 openimageio
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: Thu, 26 Jun 2014 12:07:22 +0200
Source: openimageio
Binary: libopenimageio1.4 libopenimageio-dev openimageio-tools
Architecture: source amd64
Version: 1.4.10~dfsg0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers
pkg-phototools-de...@lists.alioth.debian.org
Changed-By: Matteo F. Vescovi mfvesc...@gmail.com
Description:
libopenimageio-dev - Library for reading and writing images - development
libopenimageio1.4 - Library for reading and writing images - runtime
openimageio-tools - Library for reading and writing images - command line tools
Closes: 752449
Changes:
openimageio (1.4.10~dfsg0-2) unstable; urgency=medium
.
* debian/patches/: patchset updated
- 0003-Fix_FTBFS_big-endian.patch added (Closes: #752449)
Checksums-Sha1:
cf8c824cff813643d87e8688835c05cb1383b53d 2683 openimageio_1.4.10~dfsg0-2.dsc
e3964c2099474354e4dedab7b245075233bc020b 17396
openimageio_1.4.10~dfsg0-2.debian.tar.xz
98985c6ee42e7f01ba4a5e51f23e309d1da4cbd5 1390994
libopenimageio1.4_1.4.10~dfsg0-2_amd64.deb
160175b25b7638e8451331970ab71929dce04b82 1462574
libopenimageio-dev_1.4.10~dfsg0-2_amd64.deb
354db236eb2baa65341aa40a56fd7baab45ca9e8 380024
openimageio-tools_1.4.10~dfsg0-2_amd64.deb
Checksums-Sha256:
7a505557f3128aef968de82fb151871d06441449dd74230e64e8a1c2ef9cf036 2683
openimageio_1.4.10~dfsg0-2.dsc
e5d667076e332f0a99e4dfc26f5cf65152a9d4f86782c1d9433b96a9c4cd2d83 17396
openimageio_1.4.10~dfsg0-2.debian.tar.xz
398aac372e08382e3e588c14b6407a3fef5d7def7d5d30ce1d6af2608e5a55c7 1390994
libopenimageio1.4_1.4.10~dfsg0-2_amd64.deb
8051d2bd55f112b61b9cff6188adb2e4fb7cec3ca3b1f20e916d04039946a6a6 1462574
libopenimageio-dev_1.4.10~dfsg0-2_amd64.deb
2e54b182e8966d0d653c440ad5d683b8556828374c62cc0a7478699c4b2b 380024
openimageio-tools_1.4.10~dfsg0-2_amd64.deb
Files:
e963c7239c0ff11e70476e3fb1ba0bee 1390994 libs extra
libopenimageio1.4_1.4.10~dfsg0-2_amd64.deb
7ab8e36b2123177ae6aa7a551e4f8ab1 1462574 libdevel extra
libopenimageio-dev_1.4.10~dfsg0-2_amd64.deb
0dd176247194cc10088ff13659604147 380024 graphics extra
openimageio-tools_1.4.10~dfsg0-2_amd64.deb
50ef42a455e6a72c00aa55ed168a11fe 2683 libs extra openimageio_1.4.10~dfsg0-2.dsc
6dcc4d63c52f82d9e47f2b083dd00f41 17396 libs extra
openimageio_1.4.10~dfsg0-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Debian powered!
Bug#752614: Sources licensed under PHP License and not being PHP are not distributable
Hi Ondřej, On Do 26 Jun 2014 13:00:12 CEST, Ondřej Surý wrote: I did have a quite long and extensive chat with FTP Masters and our conclusion was that PHP License (any version) is suitable only for software that comes directly from PHP Group, that basically means only PHP (src:php5) itself. Can you provide some evidence why you think this applies to smarty3? Smarty3 is licensed under LGPL-2.1+ so I am hesitant to belief that this bug actually affects Smarty3. Please enlighten me! Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpMgdT2iPBYf.pgp Description: Digitale PGP-Signatur
Bug#752614: Sources licensed under PHP License and not being PHP are not distributable
On Thu, Jun 26, 2014, at 13:52, Mike Gabriel wrote: Hi Ondřej, On Do 26 Jun 2014 13:00:12 CEST, Ondřej Surý wrote: I did have a quite long and extensive chat with FTP Masters and our conclusion was that PHP License (any version) is suitable only for software that comes directly from PHP Group, that basically means only PHP (src:php5) itself. Can you provide some evidence why you think this applies to smarty3? Smarty3 is licensed under LGPL-2.1+ so I am hesitant to belief that this bug actually affects Smarty3. Files: development/lexer/LexerGenerator/Lexer.php Copyright: 2006, Gregory Beaver License: PHP License 3.01, http://www.php.net/license/3_01.txt This source file is subject to version 3.01 of the PHP license that is available through the world-wide-web at the following URI: http://www.php.net/license/3_01.txt. If you did not receive a copy of the PHP License and are unable to obtain it through the web, please send a note to lice...@php.net so we can mail you a copy immediately. Files: development/lexer/Exception.php Copyright: 2006, Gregory Beaver License: PHP License 3.0, http://www.php.net/license/3_0.txt This source file is subject to version 3.0 of the PHP license that is available through the world-wide-web at the following URI: http://www.php.net/license/3_0.txt. If you did not receive a copy of the PHP License and are unable to obtain it through the web, please send a note to lice...@php.net so we can mail you a copy immediately. And two more undocumented: -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752614: Sources licensed under PHP License and not being PHP are not distributable
On Thu, Jun 26, 2014, at 13:56, Ondřej Surý wrote: On Thu, Jun 26, 2014, at 13:52, Mike Gabriel wrote: Hi Ondřej, On Do 26 Jun 2014 13:00:12 CEST, Ondřej Surý wrote: I did have a quite long and extensive chat with FTP Masters and our conclusion was that PHP License (any version) is suitable only for software that comes directly from PHP Group, that basically means only PHP (src:php5) itself. Can you provide some evidence why you think this applies to smarty3? Smarty3 is licensed under LGPL-2.1+ so I am hesitant to belief that this bug actually affects Smarty3. Files: development/lexer/LexerGenerator/Lexer.php Copyright: 2006, Gregory Beaver License: PHP License 3.01, http://www.php.net/license/3_01.txt This source file is subject to version 3.01 of the PHP license that is available through the world-wide-web at the following URI: http://www.php.net/license/3_01.txt. If you did not receive a copy of the PHP License and are unable to obtain it through the web, please send a note to lice...@php.net so we can mail you a copy immediately. Files: development/lexer/Exception.php Copyright: 2006, Gregory Beaver License: PHP License 3.0, http://www.php.net/license/3_0.txt This source file is subject to version 3.0 of the PHP license that is available through the world-wide-web at the following URI: http://www.php.net/license/3_0.txt. If you did not receive a copy of the PHP License and are unable to obtain it through the web, please send a note to lice...@php.net so we can mail you a copy immediately. And two more undocumented: ./development/lexer/ParserGenerator/State.php: * @license http://www.php.net/license/3_01.txt PHP License 3.01 ./development/lexer/ParserGenerator/Parser.php: * @license http://www.php.net/license/3_01.txt PHP License 3.01 Cheers, -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752532: Sources licensed under PHP License and not being PHP are not distributable
On Thu, Jun 26, 2014 at 01:00:12PM +0200, Ondřej Surý wrote: 3. We remove the source packages from Debian. Can you kindly explain why? Is the PHP license is non-free? If so, why? If not - let's lower the bugs severity. I see only *one* reply from debian-legal here: https://lists.debian.org/debian-legal/2005/08/threads.html#00128 And this reply is not strictly suggests to do such (insane) thing. --8-- So, looking at such packages in NEW - what do you guys suggest to do? *I* tend to go and kick them out. I would probably let it pass --8-- Most authors will ignore such artifical license issues, coming from the Debian, especially as this is not a problem for other distributions. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707901: marked as done (guile-db: please migrate to guile-2.0)
Your message dated Thu, 26 Jun 2014 12:10:29 + with message-id e1x08vz-0004tm...@franck.debian.org and subject line Bug#752516: Removed package(s) from unstable has caused the Debian Bug report #707901, regarding guile-db: please migrate to guile-2.0 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.) -- 707901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: guile-db Version: 0.1-4.1 Now that the freeze is over, I'm finally planning to remove guile-1.6 (and possibly guile-1.8) from Debian soon. Please consider updating to guile-2.0. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 ---End Message--- ---BeginMessage--- Version: 0.1-4.1+rm Dear submitter, as the package guile-db has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/752516 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#750325: Test failures in Template::Plugin::LaTex ?
On 06/25/2014 11:11 PM, Chris Travers wrote: On Wed, Jun 25, 2014 at 1:01 PM, RJ Clay j...@rocasa.us wrote: There has been a bug reported in Debian on the package for the Template::Plugin::LaTex module (libtemplate-plugin-latex-perl [1]), failing to build from source (FTBFS) due to test failures. A transcript for the build attempt is included in the bug report, but it appears to be 'Can't exec xelatex' type errors in showing up LaTex.Driver. I've been testing it on two systems; both with Perl v5.18.2. Where the tests passed; it has liblatex-driver-perl at v0.12-1, liblatex-encode-perl at v0.08-2, liblatex-table-perl at v1.0.6-2, and libtemplate-perl at v2.24-1.1. Where it failed (on Debian Jessie); liblatex-driver-perl at v0.200.4-1, liblatex-encode-perl at v0.091.5-1, liblatex-table-perl at v1.0.6-2, and libtemplate-perl at v2.24-1.1+b1 (amd64). (to successfully run the tests, you need to have XeTeX, PDFLatex, and a bunch of TexLive packages installed), and you can only install interactively. As another found; if the texlive-xetex package is installed, the xelatex related errors appear to be taken care of (but there are still other errors). Which makes me wonder if there's a missing package dependancy... (perhaps in liblatex-driver-perl...) I am hoping to put some time this weekend into redoing the installation and test cases so that it runs better on smoke testers, and passes tests on all systems which minimally meet the requirements for operation. If I can be of help with that, please let me know. RJ Clay -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752614: Sources licensed under PHP License and not being PHP are not distributable
Hi Ondřej On Do 26 Jun 2014 13:56:34 CEST, Ondřej Surý wrote: On Thu, Jun 26, 2014, at 13:56, Ondřej Surý wrote: On Thu, Jun 26, 2014, at 13:52, Mike Gabriel wrote: Hi Ondřej, On Do 26 Jun 2014 13:00:12 CEST, Ondřej Surý wrote: I did have a quite long and extensive chat with FTP Masters and our conclusion was that PHP License (any version) is suitable only for software that comes directly from PHP Group, that basically means only PHP (src:php5) itself. Can you provide some evidence why you think this applies to smarty3? Smarty3 is licensed under LGPL-2.1+ so I am hesitant to belief that this bug actually affects Smarty3. Files: development/lexer/LexerGenerator/Lexer.php Copyright: 2006, Gregory Beaver License: PHP License 3.01, http://www.php.net/license/3_01.txt This source file is subject to version 3.01 of the PHP license that is available through the world-wide-web at the following URI: http://www.php.net/license/3_01.txt. If you did not receive a copy of the PHP License and are unable to obtain it through the web, please send a note to lice...@php.net so we can mail you a copy immediately. Files: development/lexer/Exception.php Copyright: 2006, Gregory Beaver License: PHP License 3.0, http://www.php.net/license/3_0.txt This source file is subject to version 3.0 of the PHP license that is available through the world-wide-web at the following URI: http://www.php.net/license/3_0.txt. If you did not receive a copy of the PHP License and are unable to obtain it through the web, please send a note to lice...@php.net so we can mail you a copy immediately. And two more undocumented: ./development/lexer/ParserGenerator/State.php: * @license http://www.php.net/license/3_01.txt PHP License 3.01 ./development/lexer/ParserGenerator/Parser.php: * @license http://www.php.net/license/3_01.txt PHP License 3.01 Cheers, Ah dang... my Git working copy was on the squeeze branch... I get what you are up to... Actually, I guess you have spotted three embedded libraries, as well. Will take a look at that next week. light+love Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpAFHlr_oy10.pgp Description: Digitale PGP-Signatur
Bug#746918: NMU debdiff for taglib_1.9.1-2.1
debdiff taglib_1.9.1-2.dsc taglib_1.9.1-2.1.dsc diff -Nru taglib-1.9.1/debian/changelog taglib-1.9.1/debian/changelog --- taglib-1.9.1/debian/changelog 2013-11-04 14:20:34.0 + +++ taglib-1.9.1/debian/changelog 2014-06-26 13:16:09.0 +0100 @@ -1,3 +1,14 @@ +taglib (1.9.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix multiple FTBTSes by changing symbol file on mips64el architecture. +Tested on mips, mipsel, mips64el, amd64, i386. +Patch by Sphinx Jiang yishan...@gmail.com. +Work done for Debian GSOC2014. +Closes: #746918. + + -- Anibal Monsalve Salazar ani...@debian.org Thu, 26 Jun 2014 13:15:27 +0100 + taglib (1.9.1-2) unstable; urgency=low * Fix multiple FTBFSes by confirming symbol files on more architectures. diff -Nru taglib-1.9.1/debian/libtag1-vanilla.symbols taglib-1.9.1/debian/libtag1-vanilla.symbols --- taglib-1.9.1/debian/libtag1-vanilla.symbols 2013-11-04 14:10:16.0 + +++ taglib-1.9.1/debian/libtag1-vanilla.symbols 2014-06-26 13:07:59.0 +0100 @@ -298,8 +298,8 @@ _ZN6TagLib3ASF4File14MetadataObject4guidEv@Base 1.6-2~ _ZN6TagLib3ASF4File14MetadataObject5parseEPS1_j@Base 1.6-2~ _ZN6TagLib3ASF4File14MetadataObject6renderEPS1_@Base 1.6-2~ - (optional=private|arch=!ia64 !powerpc !s390x !sparc)_ZN6TagLib3ASF4File14MetadataObjectC1Ev@Base 1.9.1 - (optional=private|arch=!ia64 !powerpc !s390x !sparc)_ZN6TagLib3ASF4File14MetadataObjectC2Ev@Base 1.9.1 + (optional=private|arch=!amd64 !i386 !ia64 !mips64 !mips64el !powerpc !s390x !sparc)_ZN6TagLib3ASF4File14MetadataObjectC1Ev@Base 1.9.1 + (optional=private|arch=!amd64 !i386 !ia64 !mips64 !mips64el !powerpc !s390x !sparc)_ZN6TagLib3ASF4File14MetadataObjectC2Ev@Base 1.9.1 _ZN6TagLib3ASF4File14MetadataObjectD0Ev@Base 1.7-2~ _ZN6TagLib3ASF4File14MetadataObjectD1Ev@Base 1.7-2~ _ZN6TagLib3ASF4File14MetadataObjectD2Ev@Base 1.7-2~ @@ -311,16 +311,16 @@ _ZN6TagLib3ASF4File21HeaderExtensionObject4guidEv@Base 1.6-2~ _ZN6TagLib3ASF4File21HeaderExtensionObject5parseEPS1_j@Base 1.6-2~ _ZN6TagLib3ASF4File21HeaderExtensionObject6renderEPS1_@Base 1.6-2~ - (optional=private|arch=!ia64 !powerpc !s390x !sparc)_ZN6TagLib3ASF4File21HeaderExtensionObjectC1Ev@Base 1.9.1 - (optional=private|arch=!ia64 !powerpc !s390x !sparc)_ZN6TagLib3ASF4File21HeaderExtensionObjectC2Ev@Base 1.9.1 + (optional=private|arch=!amd64 !i386 !ia64 !mips64 !mips64el !powerpc !s390x !sparc)_ZN6TagLib3ASF4File21HeaderExtensionObjectC1Ev@Base 1.9.1 + (optional=private|arch=!amd64 !i386 !ia64 !mips64 !mips64el !powerpc !s390x !sparc)_ZN6TagLib3ASF4File21HeaderExtensionObjectC2Ev@Base 1.9.1 _ZN6TagLib3ASF4File21HeaderExtensionObjectD0Ev@Base 1.7-2~ _ZN6TagLib3ASF4File21HeaderExtensionObjectD1Ev@Base 1.7-2~ _ZN6TagLib3ASF4File21HeaderExtensionObjectD2Ev@Base 1.7-2~ _ZN6TagLib3ASF4File21MetadataLibraryObject4guidEv@Base 1.6-2~ _ZN6TagLib3ASF4File21MetadataLibraryObject5parseEPS1_j@Base 1.6-2~ _ZN6TagLib3ASF4File21MetadataLibraryObject6renderEPS1_@Base 1.6-2~ - (optional=private|arch=!ia64 !powerpc !s390x !sparc)_ZN6TagLib3ASF4File21MetadataLibraryObjectC1Ev@Base 1.9.1 - (optional=private|arch=!ia64 !powerpc !s390x !sparc)_ZN6TagLib3ASF4File21MetadataLibraryObjectC2Ev@Base 1.9.1 + (optional=private|arch=!amd64 !i386 !ia64 !mips64 !mips64el !powerpc !s390x !sparc)_ZN6TagLib3ASF4File21MetadataLibraryObjectC1Ev@Base 1.9.1 + (optional=private|arch=!amd64 !i386 !ia64 !mips64 !mips64el !powerpc !s390x !sparc)_ZN6TagLib3ASF4File21MetadataLibraryObjectC2Ev@Base 1.9.1 _ZN6TagLib3ASF4File21MetadataLibraryObjectD0Ev@Base 1.7-2~ _ZN6TagLib3ASF4File21MetadataLibraryObjectD1Ev@Base 1.7-2~ _ZN6TagLib3ASF4File21MetadataLibraryObjectD2Ev@Base 1.7-2~ @@ -339,8 +339,8 @@ _ZN6TagLib3ASF4File32ExtendedContentDescriptionObject4guidEv@Base 1.6-2~ _ZN6TagLib3ASF4File32ExtendedContentDescriptionObject5parseEPS1_j@Base 1.6-2~ _ZN6TagLib3ASF4File32ExtendedContentDescriptionObject6renderEPS1_@Base 1.6-2~ - (optional=private|arch=!ia64 !powerpc !s390x !sparc)_ZN6TagLib3ASF4File32ExtendedContentDescriptionObjectC1Ev@Base 1.9.1 - (optional=private|arch=!ia64 !powerpc !s390x !sparc)_ZN6TagLib3ASF4File32ExtendedContentDescriptionObjectC2Ev@Base 1.9.1 + (optional=private|arch=!amd64 !i386 !ia64 !mips64 !mips64el !powerpc !s390x !sparc)_ZN6TagLib3ASF4File32ExtendedContentDescriptionObjectC1Ev@Base 1.9.1 + (optional=private|arch=!amd64 !i386 !ia64 !mips64 !mips64el !powerpc !s390x !sparc)_ZN6TagLib3ASF4File32ExtendedContentDescriptionObjectC2Ev@Base 1.9.1 _ZN6TagLib3ASF4File32ExtendedContentDescriptionObjectD0Ev@Base 1.7-2~ _ZN6TagLib3ASF4File32ExtendedContentDescriptionObjectD1Ev@Base 1.7-2~ _ZN6TagLib3ASF4File32ExtendedContentDescriptionObjectD2Ev@Base 1.7-2~ @@ -581,9 +581,6 @@ _ZN6TagLib3Mod8FileBaseC1EPNS_8IOStreamE@Base 1.8 _ZN6TagLib3Mod8FileBaseC2EPKc@Base 1.8 _ZN6TagLib3Mod8FileBaseC2EPNS_8IOStreamE@Base 1.8 - _ZN6TagLib3Mod8FileBaseD0Ev@Base 1.8 -
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Thursday 26 June 2014 12:45:51 Yunqiang Su wrote: On Thu, Jun 26, 2014 at 12:35 PM, Lisandro Damián Nicanor Pérez perezme...@gmail.com wrote: Note: I'm sending yuou a copy because I mistakenly sent it to the original bug reporter. On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote: I refreshed this patch for mips64el Yunqiang: again, when we are talking about symbols files, a simple patch for just one arch is not enough. The best way to solve this is to let mips64[el] build logs be available trough debian-ports. Yes, of course, while we are still waiting for the debian-ports guys to let us in. For now, you can get the buildlog from http://mips64el.debian.net/debian/buildlog Ah, that's a good workaround, thanks! -- Compartir las cosas buenas es una necesidad fácil de satisfacer. Compartir las cosas malas es una necesidad mayor, pero mucho mas difícil de satisfacer. Sin embargo, es el compartir las cosas malas lo que mas nos une como hermanos. Lisandro Damián Nicanor Pérez Meyer Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#733405: marked as done (lasi: FTBFS: drawGlyph.cpp:9:30: fatal error: freetype/ftoutln.h: No such file or directory)
Your message dated Thu, 26 Jun 2014 12:51:32 + with message-id e1x099i-00074q...@franck.debian.org and subject line Bug#733405: fixed in lasi 1.1.0-1.1 has caused the Debian Bug report #733405, regarding lasi: FTBFS: drawGlyph.cpp:9:30: fatal error: freetype/ftoutln.h: No such file or directory 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.) -- 733405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lasi Version: 1.1.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. On the new 2.5 version the headers are located at '/usr/include/freetype2/ftglyph.h' instead of '/usr/include/freetype2/freetype/ftglyph.h' like in previous versions. Relevant part (hopefully): make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 1 [ 33%] Building CXX object src/CMakeFiles/LASi.dir/drawGlyph.o cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src /usr/bin/g++ -DLASi_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/«PKGBUILDDIR»/include -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu-pthread -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -o CMakeFiles/LASi.dir/drawGlyph.o -c /«PKGBUILDDIR»/src/drawGlyph.cpp /«PKGBUILDDIR»/src/drawGlyph.cpp:9:30: fatal error: freetype/ftoutln.h: No such file or directory #include freetype/ftoutln.h ^ compilation terminated. make[3]: *** [src/CMakeFiles/LASi.dir/drawGlyph.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/12/26/lasi_1.1.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: lasi Source-Version: 1.1.0-1.1 We believe that the bug you reported is fixed in the latest version of lasi, 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. Angel Abad an...@debian.org (supplier of updated lasi 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: Thu, 19 Jun 2014 13:36:38 +0200 Source: lasi Binary: liblasi0 liblasi-dev Architecture: source amd64 Version: 1.1.0-1.1 Distribution: unstable Urgency: medium Maintainer: Andrew Ross andrewr...@users.sourceforge.net Changed-By: Angel Abad an...@debian.org Description: liblasi-dev - development files and documentation for the LASi library liblasi0 - creation of PostScript documents containing Unicode symbols Closes: 733405 Changes: lasi (1.1.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Use 3.0 (quilt) format * debian/patches/fix-freetype-ftbfs (Closes: #733405): - Include Freetype headers in recommended way, fix FTBFS Checksums-Sha1: 03d10a425305d689623b8d8819200d2cc4f853d5 1376 lasi_1.1.0-1.1.dsc 261aa25c7bfa6bf50a972becf23c00cceea8e113 4600 lasi_1.1.0-1.1.debian.tar.xz 631c83c1ad4651c6b8be269f0105eb48a5d4f6a8 33932 liblasi0_1.1.0-1.1_amd64.deb 2d2772fafd69577c3268c99fa1338b35415478b2 83996 liblasi-dev_1.1.0-1.1_amd64.deb Checksums-Sha256: 5d5503afaab70a01a790086d273b526c444781c4b4dbecb6ebe191a4508bce51 1376 lasi_1.1.0-1.1.dsc
Bug#750382: works for me on mips
I tested the package on a MIPS system and it built successfully. All the tests passed. Here is part of the log: make[4]: Leaving directory '/root/lhasa/lhasa-0.2.0+git/test' make check-TESTS make[4]: Entering directory '/root/lhasa/lhasa-0.2.0+git/test' make[5]: Entering directory '/root/lhasa/lhasa-0.2.0+git/test' PASS: test-crc16 PASS: test-basic-reader PASS: test-decoder PASS: test-decompress PASS: test-file-headers PASS: test-list-output PASS: test-crc-output PASS: test-print PASS: test-dry-run PASS: test-extract make[6]: Entering directory '/root/lhasa/lhasa-0.2.0+git/test' make[6]: Nothing to be done for 'all'. make[6]: Leaving directory '/root/lhasa/lhasa-0.2.0+git/test' Testsuite summary for Lhasa 0.2.0 # TOTAL: 10 # PASS: 10 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 make[5]: Leaving directory '/root/lhasa/lhasa-0.2.0+git/test' make[4]: Leaving directory '/root/lhasa/lhasa-0.2.0+git/test' make[3]: Leaving directory '/root/lhasa/lhasa-0.2.0+git/test' make[3]: Entering directory '/root/lhasa/lhasa-0.2.0+git' make[3]: Leaving directory '/root/lhasa/lhasa-0.2.0+git' make[2]: Leaving directory '/root/lhasa/lhasa-0.2.0+git' make[1]: Leaving directory '/root/lhasa/lhasa-0.2.0+git' fakeroot debian/rules binary prefix=/usr dh binary --parallel I think we should try to build this one again through the auto-building system on MIPS. If it fails again, I'll look into the differences to find where the problem is. Plamen signature.asc Description: Digital signature
Processed: bug 752646 is forwarded to http://pear.php.net/bugs/bug.php?id=20315
Processing commands for cont...@bugs.debian.org: forwarded 752646 http://pear.php.net/bugs/bug.php?id=20315 Bug #752646 [php-net-whois] php-net-whois is licensed under the PHP license and is not PHP Set Bug forwarded-to-address to 'http://pear.php.net/bugs/bug.php?id=20315'. thanks Stopping processing here. Please contact me if you need assistance. -- 752646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752646 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: bug 752642 is forwarded to https://pear.php.net/bugs/bug.php?id=20316
Processing commands for cont...@bugs.debian.org: forwarded 752642 https://pear.php.net/bugs/bug.php?id=20316 Bug #752642 [php-net-imap] php-net-imap is licensed under the PHP license and is not PHP Set Bug forwarded-to-address to 'https://pear.php.net/bugs/bug.php?id=20316'. thanks Stopping processing here. Please contact me if you need assistance. -- 752642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752642 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: bug 752641 is forwarded to https://pear.php.net/bugs/bug.php?id=20317
Processing commands for cont...@bugs.debian.org: forwarded 752641 https://pear.php.net/bugs/bug.php?id=20317 Bug #752641 [php-net-ftp] php-net-ftp is licensed under the PHP license and is not PHP Set Bug forwarded-to-address to 'https://pear.php.net/bugs/bug.php?id=20317'. thanks Stopping processing here. Please contact me if you need assistance. -- 752641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752641 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: bug 752632 is forwarded to https://pear.php.net/bugs/bug.php?id=20318
Processing commands for cont...@bugs.debian.org: forwarded 752632 https://pear.php.net/bugs/bug.php?id=20318 Bug #752632 [php-cache] php-cache is licensed under the PHP license and is not PHP Set Bug forwarded-to-address to 'https://pear.php.net/bugs/bug.php?id=20318'. thanks Stopping processing here. Please contact me if you need assistance. -- 752632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752632 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#746916: NMU debdiff for soprano_2.9.4+dfsg-1.1
Hi! allow me to re ask one question in a different way. On Thursday 26 June 2014 20:30:36 Aníbal Monsalve Salazar wrote: [snip] This doesn't seems to be a patch generated by pkgkde-symbolshelper. Was this diff generated with this tool? Applying patches not generated with it could lead us to a big headache in future uploads. Check that this tool keeps a lists of archs involved in the symbols. The best way to generate this is to get all the build logs from different archs together and apply it. Check http://pkg-kde.alioth.debian.org/symbolfiles.html for more info. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#746916: NMU debdiff for soprano_2.9.4+dfsg-1.1
On Thursday 26 June 2014 10:29:54 you wrote: Hi! allow me to re ask one question in a different way. On Thursday 26 June 2014 20:30:36 Aníbal Monsalve Salazar wrote: [snip] This doesn't seems to be a patch generated by pkgkde-symbolshelper. Was this diff generated with this tool? Applying patches not generated with it could lead us to a big headache in future uploads. Check that this tool keeps a lists of archs involved in the symbols. The best way to generate this is to get all the build logs from different archs together and apply it. Check http://pkg-kde.alioth.debian.org/symbolfiles.html for more info. Tip: better use getbuildlogs from the devscripts package to get all the build logs, as it will also get the ones from debian-ports. Tip 2: I haven't yet heard of maxy, he might want to wait for something else to arrive before fixing this. -- 16: De quien es Internet * De DIOS dado que todas las cosas del mundo le pertenecen Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#752762: load-module module-alsa-sink freezes display
Control: tags -1 moreinfo unreproducible Hi Michael, On Thu, Jun 26, 2014 at 7:24 AM, Michael Meskes mes...@debian.org wrote: Package: pulseaudio Version: 5.0-2 Severity: grave I simply uncommented the line #load-module module-alsa-sink in /etc/pulse/default.pa and resarted pulseaudio to completely freeze my X. Mouse was still working but I wasn't able to focus on any window, let alone type into one or log out. After a reboot I noticed that with that setting my whole X sessions starts up, but the screen remains blank. This looks bad, but I cannot reproduce it. According to syslog the module failed to load: Jun 26 12:54:57 feivel pulseaudio[3128]: [pulseaudio] module.c: Failed to load module module-alsa-sink (argument: ): initialization failed. Yes, this is expected, because that module needs the card details to load. Is this message shown only once, or repeatedly? Does the log say afterwards: [pulseaudio] main.c: Module load failed. [pulseaudio] main.c: Failed to initialize daemon. ? But that IMO hardly qualifies as a reason for the display to disappear. It'd also be interesting to know why the module failed, but there doesn't seem to be anything in the logs. Indeed. What DE/WM are you using? Were there sounds being played at the moment? This error is weird, because the module load failure should just cause pulseaudio to exit. Perhaps something caused PA to respawn repeatedly? I tried using this module in an attempt to figure out why my sound doesn't work correctly, or in other words, not at all when using the defaults. For this, try using pavucontrol. There you can see if your card is actually being picked up. Finally I'm not sure about the severity, but you can (and I did) lose data because of the loss of the X session. This does look bad so I'm not downgrading it yet. -- Saludos, Felipe Sateler -- 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#752762: load-module module-alsa-sink freezes display
Processing control commands: tags -1 moreinfo unreproducible Bug #752762 [pulseaudio] load-module module-alsa-sink freezes display Added tag(s) unreproducible and moreinfo. -- 752762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752762 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#670681: /etc/init.d/postgrey script doesn't work properly
Hi, Nye Liu wrote: /etc/init.d/postgrey passes --name to start-stop-daemon, but start-stop-daemon apparently expects a full path (/usr/sbin/postgrey vs postgrey) However, start-stop-daemon is also limited to 15 characters So stop/reload do NOT work at all. Yes. That's the core of the issue. --- /etc/init.d/postgrey-dist 2012-04-27 16:58:30.0 -0700 +++ /etc/init.d/postgrey 2012-04-27 17:05:53.0 -0700 @@ -23,6 +23,7 @@ PATH=/sbin:/bin:/usr/sbin:/usr/bin DAEMON=/usr/sbin/postgrey NAME=postgrey +SSNAME=`echo $DAEMON | cut -c -15` DESC=postfix greylisting daemon PIDFILE=/var/run/$NAME.pid @@ -51,7 +52,7 @@ start) log_daemon_msg Starting $DESC $NAME if start-stop-daemon --start --oknodo --quiet \ - --pidfile $PIDFILE --name $NAME \ + --pidfile $PIDFILE --name $SSNAME \ --startas $DAEMON -- $POSTGREY_OPTS $POSTGREY_TEXT_OPT then log_end_msg 0 @@ -63,7 +64,7 @@ stop) log_daemon_msg Stopping $DESC $NAME if start-stop-daemon --stop --oknodo --quiet \ - --pidfile $PIDFILE --name $NAME + --pidfile $PIDFILE --name $SSNAME then log_end_msg 0 else @@ -75,7 +76,7 @@ reload|force-reload) log_action_begin_msg Reloading $DESC configuration... if start-stop-daemon --stop --signal 1 --quiet \ - --pidfile $PIDFILE --name $NAME + --pidfile $PIDFILE --name $SSNAME then log_action_end_msg 0 else The stop and restart actions of an init script with this patch work fine for any postgrey process started with the same script. Contrary to my expectations, it though can't stop a process started by the current (i.e. buggy) init script. I currently don't know why this doesn't work. This patch also has another disadvantage (which was not known at the time the patch was written, so that's not a fault of the patch or its author :-), namely that since 1.35 upstream writes postgrey and the beginning of the arguments into that comm field: https://github.com/schweikert/postgrey/commit/d496dfbc13412fda9d72dc1c1eb6506c84265543 So the above variant will need to be changed with the next upstream release anyways... Olaf Zaplinski wrote: Patch did not work for me. What worked was this change of init script: # line 80 - replaced --pidfile $PIDFILE --name $SSNAME # with --pidfile $PIDFILE Works, too, but also fails to stop a postgrey daemon which was started by the previous version of the init script. In comparison to Nye Liu's solution, this one at least throws an error in this case and would likely continue to work unmodified with the recent new upstream release 1.35. So I currently tend to this solution, but I'll first need to check if it has other implications. Another variant would be to use -u postgrey given that no other process runs under the user postgrey. But according to its man page, postgreyreport runs under the postgrey user by default, too, and if it's running while the init script tries to stop the postgrey daemon, that script would be killed, too. Not perfect either... Leoš Bitto wrote on 12 Sep 2013: The patch supplied by Nye Liu fixes this issue for me on a system running Debian stable (wheezy). However, on another system which is updated to Debian testing (jessie) the startup script does not work at all - it just prints green [ok] but postgrey is actually not started! The latter may be a different issue, maybe https://bugs.debian.org/748918 (postgrey fails to start on Wheezy, fixed in Sid in November 2013, but unclear under which circumstances it shows up on Wheezy, too) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749974: status of upgrading maitreya to use wxwidgets3.0
I have been notified that wxwidgets2.8 support is going away to be replace with wxwidgets3.0. This effects maitreya because the version in unstable links to 2.8 libraries. I notified the upstream and he accepted the bug and produced a new upstream =7.0.6 I had difficluty building a version of this upstream at first because one dependancy libwxsqlite3-3.0-dev is not in unstable yet. For my testing purposes on my test system I solved this on my system by grabbing the source in experimental from the Debian packages website https://www.debian.org/distrib/packages I then built this package for debian using debuild. I installed it, which allowed my to build/run my potential upgrade package using debuild. I did crude testing on this program and found that it basicly works, but on one particular menu item, it pops up an error window. This new bug did not exist in the old verion 7.0.5. (i reverted and tested for it.) I have notified the upstream and am waiting to hear back. I hope this keeps every one informed of the status of this bug and attempts to address it. -- Paul Elliott 1(512)837-1096 pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117 signature.asc Description: Digital signature
Bug#739190: Add conflict with systemd-sysv
Hi, AFAICT, this bug only affects systems where systemd-sysv is installed. Setting its severity to grave will cause its removal from testing if no quick action is taken (as currently stated on the PTS) which is not fair for those still using (plain) sysvinit. (Really) Fixing this bug shall require upstream fixing systemd-sysv which is probably not due soon I bet ;-). I'm afraid that unfortunately netenv users will probably have to choose between netenv xor systemd-sysv at some point but for the moment (and probably beyond), it seems to me that an acceptable temporary fix would be to add a conflict with systemd-sysv to avoid the package removal and keeping this bug around as a reminder. Arnaud, what do you think about it? phep -- 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
Processing commands for cont...@bugs.debian.org: severity 739190 important Bug #739190 [netenv] netenv doesn't come up initializing via systemd Severity set to 'important' from 'grave' End of message, stopping processing here. Please contact me if you need assistance. -- 739190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739190 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: initramfs-tools: Shell spawned despite panic=0
Processing control commands: found -1 0.115 Bug #751488 [initramfs-tools] initramfs-tools: Shell spawned despite panic=0 Marked as found in versions initramfs-tools/0.115. -- 751488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751488 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#751488: initramfs-tools: Shell spawned despite panic=0
Control: found -1 0.115 This bug is still present in the latest available version. Regards, Lukas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745902: marked as done (libvarnishapi-dev: 'struct VSC_C_main' not defined)
Your message dated Thu, 26 Jun 2014 15:55:25 +
with message-id e1x0c1f-0003e9...@franck.debian.org
and subject line Bug#745902: fixed in varnish 4.0.1-1
has caused the Debian Bug report #745902,
regarding libvarnishapi-dev: 'struct VSC_C_main' not defined
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.)
--
745902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libvarnishapi-dev
Version: 4.0.0-1
Severity: serious
Hi,
/usr/include/varnish/vapi/vsc.h includes the following function:
struct VSC_C_main *VSC_Main(const struct VSM_data *vd,
struct VSM_fantom *fantom);
struct VSC_C_main is not defined in any of the headers shipped in
/usr/include/. Instead, it is defined in
/usr/share/varnish/include/common/common.h.
I'm not sure what the files in /usr/share/varnish/include/ are supposed
to be used for but they are fairly unusable. For example, common.h
includes /usr/share/varnish/include/vas.h which unconditionally defines
assert(), thus conflicting with /usr/include/assert.h. Also, the files
in /usr/share/ redefine various things which are also defined in headers
in /usr/include/, for example:
In file included from /usr/share/varnish/include/common/common.h:42:0,
from varnish.c:35:
/usr/include/varnish/vapi/vsc_int.h:34:6: error: nested redefinition of 'enum
VSC_level_e'
enum VSC_level_e {
^
/usr/include/varnish/vapi/vsc_int.h:34:6: error: redeclaration of 'enum
VSC_level_e'
In file included from /usr/include/varnish/vapi/vsc.h:38:0,
from varnish.c:32:
/usr/include/varnish/vapi/vsc_int.h:34:6: note: originally defined here
enum VSC_level_e {
^
That's the point where I stopped trying to migrate code in collectd to
varnish 4.
I think it's fine to have the code in /usr/share/ conflict with
/usr/include/. After all, /usr/share/ seems to be used for Varnish
modules only. However, /usr/include/ needs to be self-containing.
Thanks,
Sebastian
--
Sebastian tokkee Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/
Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: varnish
Source-Version: 4.0.1-1
We believe that the bug you reported is fixed in the latest version of
varnish, 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 745...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stig Sandbeck Mathisen s...@debian.org (supplier of updated varnish 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: Thu, 26 Jun 2014 16:24:43 CEST
Source: varnish
Binary: varnish varnish-doc libvarnishapi1 libvarnishapi-dev varnish-dbg
Architecture: amd64 all source
Version: 4.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Varnish Package Maintainers
pkg-varnish-de...@lists.alioth.debian.org
Changed-By: Stig Sandbeck Mathisen s...@debian.org
Description:
varnish - state of the art, high-performance web accelerator
varnish-doc - documentation for Varnish Cache
libvarnishapi1 - shared libraries for Varnish
libvarnishapi-dev - development files for Varnish
varnish-dbg - debugging symbols for varnish
Closes: 745902
Changes:
varnish (4.0.1-1) unstable; urgency=medium
.
* Imported upstream release 4.0.1
* [5bdad65] Ensure header files end up in /usr/include/varnish
(Closes: #745902)
* [91747ac] Remove backported patch included in this release
Checksums-Sha256:
66f0aef72619f16c87e93784ffcb205e0156a8e21c9704a4d9365972f8b55b8d 520954
varnish_4.0.1-1_amd64.deb
c52e6e6794d427e96ad4b8aaba226114f4d99c92b49210c5895896c5788a2337 292552
varnish-doc_4.0.1-1_all.deb
3bc5c3ce16dfb7bc513393a42322755eeab48289f1d1eca5800bc5ed2ff70ac5 91160
libvarnishapi1_4.0.1-1_amd64.deb
cf5f594d2c947ee7dc548d5432f2c420b557e1a388f0aa4b8256280cab7c1b8e 91690
libvarnishapi-dev_4.0.1-1_amd64.deb
957eeca5a3609e7fef1e3e37f5a98e92db1a698663297271b8be065701c84952 1365684
varnish-dbg_4.0.1-1_amd64.deb
Bug#713672: (no subject)
Hi, This bugs is avoiding xca to be compiled in ppc64el platform. If you could accept the attached patch,the ppc64el team would appreciate. Thank you, Breno -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735832: (no subject)
Hi, We are facing the same problem reported by this bug on ppc64el bootstrap. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733355: (no subject)
We are finding the same problem during ppc64el bootstrap. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750001: freedink-dfarc: Please update to wxwidgets3.0
Control: severy 750001 normal thanks Hi, wxGlade does not support wxWidgets 3 because upstream says so: https://bitbucket.org/agriggio/wxglade/commits/acbfabfba67bc795a6ccecaabda933ecb0d0f63d#chg-wxglade.py For instance it adds wxTHICK_FRAME by itself, in the .wxg and the generated .cpp. Can you add to your list the packages that depend on wxPython (apt-rdepends counts 70) to get a clearer understanding of the situation. Please don't change the severity of this bug until then. You'll get a bug dependency on wxglade, I'll be able to depend on it. Good news about MXE. I think you don't have to worry about bugs on 2.8 - if upstream doesn't want to fix bugs, you could recommend (not enforce) impacted people to upgrade? - Sylvain On Thu, Jun 26, 2014 at 02:12:47AM +0100, Olly Betts wrote: # blocks the on-going wxwidgets3.0 transition severity 750001 serious thanks On Sat, May 31, 2014 at 04:23:12PM +0200, b...@debian.org wrote: I (as upstream) do not wish to update to wxWidgets2.8 yet because wxGlade (used to generate the *_Base.cpp files) doesn't support it, and because MXE (for the Windows cross-build) doesn't seem to either (though it builds 2.9 already). In what way does wxGlade not handle the patched code? The changes I made in that area were just updating things which were deprecated in 2.8 and have been removed in 3.0; if wxGlade doesn't handle them, it's likely broken for wx2.8 too. As upstream, you don't have to drop wx2.8 support to add wx3.0 support (the patch I sent should work with both), but FWIW MXE appears to support wx3.0: https://github.com/mxe/mxe/blob/master/src/wxwidgets.mk So while such a move is planned, it's too early to make it. Please consider supporting both 2.8 and 3.0 in Jessie (as with 2.6/2.8). It will also make backports easier. It's really not feasible to support two different wx releases in Jessie - there are only two people in the wx team who have been at all active in recent times. Since there's no upstream interest in wx2.8, and a number of packages actually require wx3.0, wx3.0 is the sane choice. Having 2.6 and 2.8 in a release together didn't work out well - bugs in 2.6 just piled up because upstream weren't interested. That's not what we want in a large and complex library package. Last, I (as package maintainer) would object to Debian diverging from upstream, especially with forwarded:no patches, so no NMU please. Since you are upstream maintainer, we can now consider the patch as forwarded. The patch I sent doesn't break compatibility with wx2.8 - I did a test build to verify this. Note that in wx2.8 wxTHICK_FRAME is just defined to wxRESIZE_BORDER, so changing wxRESIZE_BORDER|wxTHICK_FRAME to wxRESIZE_BORDER makes no different to behaviour. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670681: NMU for RC bug in postgrey
Control: tag -1 + pending Hi Antonio, Antonio Radici wrote: if you have time it would be great if you could prepare an NMU for the patch at the existing release This sentence of yours was originally meant for #748918 which arose to being already fixed in Sid and Jessie. Me closing #748918 in Sid and Jessie bumped the autoremoval date from tomorrow to 11th of July. The cvurrent autoremoval is triggered by #670681 which has been upped to RC severity on Saturday IIRC. I've prepared an NMU to fix #670681. See the git commit at http://anonscm.debian.org/gitweb/?p=collab-maint/postgrey.git;a=commitdiff;h=0f28b7d153ea42de08054f542e81deb4c04631e6 (I pushed it to a newly created nmu branch which I'll merge and remove as soon as the package hits the archive.) This seems to also fix #630353 which is likely a follow up error of #670681 (or vice versa; they're at least related). I hope this NMU is ok for you, too. If so, please tell me and I'll upload it more or less immediately. If I don't hear from you, I'll upload it to DELAYED/2 -- probably tomorrow. and then I can add you as co-maintainer and we can work on the 1.35 packaging (there is already a git, you just need to be on collab-maint). On the long run we should run postgrey using a team rather than a single person (me), that should make things easier in terms of maintainership and uploads. Having worked through the package and bugs, I may start working on importing 1.35 and modernising the packaging a little bit on my own. But I'll do that in a separate branch for now, so you can review it in case you're not happy about e.g. source format 3.0 (quilt) or a dh style debian/rules file. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 signature.asc Description: Digital signature
Processed: NMU for RC bug in postgrey
Processing control commands: tag -1 + pending Bug #670681 [postgrey] postgrey: stop action of init script does not work Added tag(s) pending. -- 670681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670681 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#752610: lynx: Can connect to CVE-2014-1959 test site
On 2014-06-25 Kurt Roeckx k...@roeckx.be wrote: Package: lynx-cur, libgnutls26 Severity: serious Tags: security Hi, There is a test site for checking the gnutls bug: https://gnutls.notary.icsi.berkeley.edu/ I can connect to it and get the message: If you see this without getting a certificate error you are vulnerable against the GnuTLS bug [...] Hello Kurt, afaiui this site checks for CVE-2014-0092, not CVE-2014-1959, and indeed an important difference comes up when comparing gnutls-cli -p 443 gnutls.notary.icsi.berkeley.edu --x509cafile \ /etc/ssl/certs/ca-certificates.crt with libgnutls26_2.12.20-8 and libgnutls26_2.12.20-8+deb7u1. The older unfixed version connects successfully and trust the certificate, the newer one does not. Also for reference reproducing the issue on current sid/testing requires downgrading libtasn1-6 to = 3.2-1. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752610: lynx: Can connect to CVE-2014-1959 test site
On Thu, Jun 26, 2014 at 07:58:04PM +0200, Andreas Metzler wrote: On 2014-06-25 Kurt Roeckx k...@roeckx.be wrote: Package: lynx-cur, libgnutls26 Severity: serious Tags: security Hi, There is a test site for checking the gnutls bug: https://gnutls.notary.icsi.berkeley.edu/ I can connect to it and get the message: If you see this without getting a certificate error you are vulnerable against the GnuTLS bug [...] Hello Kurt, afaiui this site checks for CVE-2014-0092, not CVE-2014-1959, and You're right, wrong CVE. indeed an important difference comes up when comparing gnutls-cli -p 443 gnutls.notary.icsi.berkeley.edu --x509cafile \ /etc/ssl/certs/ca-certificates.crt with libgnutls26_2.12.20-8 and libgnutls26_2.12.20-8+deb7u1. The older unfixed version connects successfully and trust the certificate, the newer one does not. As said, I can reproduce it with +deb7u2. Also for reference reproducing the issue on current sid/testing requires downgrading libtasn1-6 to = 3.2-1. I can reproduce it with 3.6-3 in testing and libtasn1-3 2.13-2 in stable. I also understand that not everbody can reproduce it. I can't reproduce it on at least 2 different systems but not on a 3rd. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710195: [Pkg-libvirt-maintainers] Processed: Re: Bug#710195 closed by Guido Günther a...@sigxcpu.org (Bug#710195: fixed in libvirt 1.2.4-1)
On 2014-05-17 15:09:00 [+0200], Guido Günther wrote: which dependency are you still seeing? -- Guido I think he meant: From b19ba46d6a9c3b67a8a70457ed1970924bb97489 Mon Sep 17 00:00:00 2001 From: Sebastian Andrzej Siewior sebast...@breakpoint.cc Date: Thu, 26 Jun 2014 20:08:04 +0200 Subject: [PATCH] drop libhal dependency last piece of #710195 Signed-off-by: Sebastian Andrzej Siewior sebast...@breakpoint.cc --- debian/changelog | 6 ++ debian/control | 1 - 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 3868cc6..3da0075 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +libvirt (1.2.4-4) UNRELEASED; urgency=low + + * Remove last piece of hal (Closes: #710195) + + -- Sebastian Andrzej Siewior sebast...@breakpoint.cc Thu, 26 Jun 2014 20:06:54 +0200 + libvirt (1.2.4-3) unstable; urgency=medium * [b0b7359] Don't pretend kFreeBSD supports linux only features. So far we diff --git a/debian/control b/debian/control index e20a0b1..dbfb930 100644 --- a/debian/control +++ b/debian/control @@ -22,7 +22,6 @@ Uploaders: Guido Günther a...@sigxcpu.org, Laurent Léonard laurent@open-mind libdevmapper-dev [linux-any], uuid-dev, libudev-dev [linux-any], - libhal-dev [!linux-any], libpciaccess-dev, kmod [linux-any], policykit-1 (= 0.105-4~), -- 2.0.0 Sebastian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tecnoballz: FTBFS: make[4]: *** No rule to make target 'supervisor.c', needed by 'supervisor.o'. Stop.
Processing control commands: tags -1 patch Bug #750249 [src:tecnoballz] tecnoballz: FTBFS: make[4]: *** No rule to make target 'supervisor.c', needed by 'supervisor.o'. Stop. Added tag(s) patch. -- 750249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750249 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#750249: tecnoballz: FTBFS: make[4]: *** No rule to make target 'supervisor.c', needed by 'supervisor.o'. Stop.
Control: tags -1 patch New revision with patch: http://mentors.debian.net/debian/pool/main/t/tecnoballz/tecnoballz_0.92-6.dsc signature.asc Description: OpenPGP digital signature
Bug#752821: sshmenu: not installable in sid
Package: sshmenu Version: 3.18-2 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hello, sshmenu is not installable in sid, at least since 2014-04-05 : No package matches the dependency libgtk2-ruby of package sshmenu (=3.18-2) -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 729251 to gstreamer0.10-ffmpeg
Processing commands for cont...@bugs.debian.org: reassign 729251 gstreamer0.10-ffmpeg Bug #729251 [src:gstreamer0.10-ffmpeg] gstreamer0.10-ffmpeg: uninstallable with libav 9 Bug reassigned from package 'src:gstreamer0.10-ffmpeg' to 'gstreamer0.10-ffmpeg'. No longer marked as found in versions gstreamer0.10-ffmpeg/0.10.13-5. Ignoring request to alter fixed versions of bug #729251 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 729251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729251 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: found 729251 in 0.10.13-5
Processing commands for cont...@bugs.debian.org: found 729251 0.10.13-5 Bug #729251 [gstreamer0.10-ffmpeg] gstreamer0.10-ffmpeg: uninstallable with libav 9 Marked as found in versions gstreamer0.10-ffmpeg/0.10.13-5. thanks Stopping processing here. Please contact me if you need assistance. -- 729251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729251 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#752823: buddycloud-server: not installable in sid
Package: buddycloud-server Version: 0.3.5-2 Severity: grave User: trei...@debian.org Usertags: edos-uninstallable Hi, buddycloud-server is not installable in sid on any architecture, for different reasons (see below). This is the case at least since 2014-04-05. Architectures: amd64, armel, armhf, i386 Version: 0.3.5-2 No package matches the dependency libicu48 (= 4.8-1) of package node-node-stringprep (=0.1.5-1) Dependency chain from buddycloud-server (=0.3.5-2) to node-node-stringprep (=0.1.5-1): Package buddycloud-server (=0.3.5-2) depends on node-node-stringprep Architectures: mipsel Version: 0.3.5-2 No package matches the dependency node-node-expat of package buddycloud-server (=0.3.5-2) Architectures: hurd-i386, mips, powerpc, s390x Version: 0.3.5-2 No package matches the dependency nodejs (= 0.6.19~dfsg1-3~) of package buddycloud-server (=0.3.5-2) Architectures: kfreebsd-amd64, kfreebsd-i386 Version: 0.3.5-2 No package matches the dependency node-node-stringprep of package buddycloud-server (=0.3.5-2) -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752636: marked as done (php-igbinary is licensed under the PHP license and is not PHP)
Your message dated Thu, 26 Jun 2014 21:54:21 +0200 with message-id cafx5sbxmwmtzbxnjmcobzwnbjynz0ja6c3fd_b1uip-1_w7...@mail.gmail.com and subject line closing has caused the Debian Bug report #752636, regarding php-igbinary is licensed under the PHP license and is not PHP 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.) -- 752636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: php-gearman Severity: serious User: paul...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks From the REJECT faq: / | You have a PHP add-on package (any php script/app/thing, not PHP | itself) and it's licensed only under the standard PHP license. That | license, up to the 3.x which is actually out, is not really usable for | anything else than PHP itself. I've mailed our -legal list about that | and got only one response, which basically supported my view on this. | Basically this license talks only about PHP, the PHP Group, and includes | Zend Engine, so its not applicable to anything else. And even worse, | older versions include the nice ad-clause. | | One good solution here is to suggest a license change to your upstream, | as they clearly wanted a free one. LGPL or BSD seems to be what they | want. \ Sorry this made it through NEW, Hope you're well, and thanks for your work, Paul -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Actually closing the bug ;-) Regards Mathieu Parent---End Message---
Bug#752823: [Pkg-javascript-devel] Bug#752823: buddycloud-server: not installable in sid
Quoting Ralf Treinen (2014-06-26 21:36:05) Hi, buddycloud-server is not installable in sid on any architecture, for different reasons (see below). This is the case at least since 2014-04-05. Right. Thanks for reporting this. I am aware of it, however - I do intend to try get it back in working condition, hopefully before the freeze. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#710195: [Pkg-libvirt-maintainers] Processed: Re: Bug#710195 closed by Guido Günther a...@sigxcpu.org (Bug#710195: fixed in libvirt 1.2.4-1)
On Thu, Jun 26, 2014 at 08:23:15PM +0200, Sebastian Andrzej Siewior wrote: On 2014-05-17 15:09:00 [+0200], Guido Günther wrote: which dependency are you still seeing? -- Guido I think he meant: From b19ba46d6a9c3b67a8a70457ed1970924bb97489 Mon Sep 17 00:00:00 2001 From: Sebastian Andrzej Siewior sebast...@breakpoint.cc Date: Thu, 26 Jun 2014 20:08:04 +0200 Subject: [PATCH] drop libhal dependency last piece of #710195 Already in VCS as 9321997cddf7bb5b030d6328d9db67eb4f5830f6 since May. Cheers, -- Guido Signed-off-by: Sebastian Andrzej Siewior sebast...@breakpoint.cc --- debian/changelog | 6 ++ debian/control | 1 - 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 3868cc6..3da0075 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +libvirt (1.2.4-4) UNRELEASED; urgency=low + + * Remove last piece of hal (Closes: #710195) + + -- Sebastian Andrzej Siewior sebast...@breakpoint.cc Thu, 26 Jun 2014 20:06:54 +0200 + libvirt (1.2.4-3) unstable; urgency=medium * [b0b7359] Don't pretend kFreeBSD supports linux only features. So far we diff --git a/debian/control b/debian/control index e20a0b1..dbfb930 100644 --- a/debian/control +++ b/debian/control @@ -22,7 +22,6 @@ Uploaders: Guido Günther a...@sigxcpu.org, Laurent Léonard laurent@open-mind libdevmapper-dev [linux-any], uuid-dev, libudev-dev [linux-any], - libhal-dev [!linux-any], libpciaccess-dev, kmod [linux-any], policykit-1 (= 0.105-4~), -- 2.0.0 Sebastian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710195: [Pkg-libvirt-maintainers] Processed: Re: Bug#710195 closed by Guido Günther a...@sigxcpu.org (Bug#710195: fixed in libvirt 1.2.4-1)
Am 26.06.2014 21:54, schrieb Guido Günther: On Thu, Jun 26, 2014 at 08:23:15PM +0200, Sebastian Andrzej Siewior wrote: On 2014-05-17 15:09:00 [+0200], Guido Günther wrote: which dependency are you still seeing? -- Guido I think he meant: From b19ba46d6a9c3b67a8a70457ed1970924bb97489 Mon Sep 17 00:00:00 2001 From: Sebastian Andrzej Siewior sebast...@breakpoint.cc Date: Thu, 26 Jun 2014 20:08:04 +0200 Subject: [PATCH] drop libhal dependency last piece of #710195 Already in VCS as 9321997cddf7bb5b030d6328d9db67eb4f5830f6 since May. Cheers, Correct. I was looking at the released package, which still has the libhal-dev b-dep. I didn't check the VCS. Once 1.2.4-4 is uploaded, everything is fine. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#752830: libgdbm3: ships /usr/share/info/gdbm.info.gz which isn't versioned
Package: libgdbm3 Version: 1.8.3-12 Severity: serious libgdbm3 ships /usr/share/info/gdbm.info.gz, which isn't versioned (e.g. libgdbm3.info.gz or a versioned folder would be ok). This violates Policy 8.2.: If your package contains files whose names do not change with each change in the library shared object version, you must not put them in the shared library package. I noticed this because gdbm.info.gz contains the texinfo version in the beginning (as is normal for info files) and thus the file may differ in different architectures if it gets built against different texinfo versions, causing problems with multiarch as we have seen on #752465. Since gdbm.info.gz is a manual for developers, it could be moved to libgdbm-dev, solving this. The manpages are there already so that seems like an appropriate place. Thanks, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752835: gecko-mediaplayer: build-depends on xulrunner-dev which is gone
Source: gecko-mediaplayer Severity: serious gecko-mediaplayer build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752836: gnash: build-depends on xulrunner-dev which is gone
Source: gnash Severity: serious gnash build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752843: packagekit: build-depends on xulrunner-dev which is gone
Source: packagekit Severity: serious packagekit build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752838: icedtea-web: build-depends on xulrunner-dev which is gone
Source: icedtea-web Severity: serious icedtea-web build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752840: npapi-vlc: build-depends on xulrunner-dev which is gone
Source: npapi-vlc Severity: serious npapi-vlc build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752837: kiwix: build-depends on xulrunner-dev which is gone
Source: kiwix Severity: serious kiwix build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752844: spice-xpi: build-depends on xulrunner-dev which is gone
Source: spice-xpi Severity: serious spice-xpi build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752839: mozilla-gnome-keyring: build-depends on xulrunner-dev which is gone
Source: mozilla-gnome-keyring Severity: serious mozilla-gnome-keyring build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752841: openvrml: build-depends on xulrunner-dev which is gone
Source: openvrml Severity: serious openvrml build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752842: stylish: build-depends on xulrunner-dev which is gone
Source: stylish Severity: serious stylish build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752834: gnome-chemistry-utils: build-depends on xulrunner-dev which is gone
Source: gnome-chemistry-utils Severity: serious gnome-chemistry-utils build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752843: marked as done (packagekit: build-depends on xulrunner-dev which is gone)
Your message dated Fri, 27 Jun 2014 00:23:40 +0200 with message-id CAKNHny_2VfnSg6T1fYM+LWjgR7faP=h4yx3zgda4zu7d1u8...@mail.gmail.com and subject line Re: Bug#752843: packagekit: build-depends on xulrunner-dev which is gone has caused the Debian Bug report #752843, regarding packagekit: build-depends on xulrunner-dev which is gone 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.) -- 752843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: packagekit Severity: serious packagekit build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio ---End Message--- ---BeginMessage--- 2014-06-27 0:09 GMT+02:00 po...@debian.org: Source: packagekit Severity: serious packagekit build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Sure you have the latest version of PK? ;-) Because Pk already depends on iceweasel-dev instead of xulrunner. (check the changelog) Cheers, Matthias P.S: Feel free to reopen in case I overlooked something and this isn't the case... -- I welcome VSRE emails. See http://vsre.info/---End Message---
Bug#752845: policyd-weight: recent libnet-dns-perl upgrade has broken policyd-weight.
Package: policyd-weight Version: 0.1.15.2-7 Severity: grave Justification: renders package unusable Policyd started generating bogus scores. After a restart it generates errors like this: postfix/policyd-weight[26689]: warning: child: err: Undefined subroutine main::dn_expand called at /usr/sbin/policyd-weight line 3590, GEN33 line 26.#012 that results in the mail getting refused. main::dn_expand is from: use Net::DNS::Packet qw(dn_expand); The dn_expand() in /usr/lib/perl5/Net/DNS/Packet.pm is commented out. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages policyd-weight depends on: ii adduser 3.113+nmu3 ii libio-socket-inet6-perl 2.72-1 ii libnet-dns-perl 0.77-3 ii libnet-ip-perl 1.26-1 ii lsb-base 4.1+Debian13 ii perl 5.18.2-4 Versions of packages policyd-weight recommends: ii perl [libsys-syslog-perl] 5.18.2-4 policyd-weight suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752835: marked as done (gecko-mediaplayer: build-depends on xulrunner-dev which is gone)
Your message dated Fri, 27 Jun 2014 00:33:25 +0200 with message-id 20140626223325.ga21...@ramacher.at and subject line Re: Bug#752835: gecko-mediaplayer: build-depends on xulrunner-dev which is gone has caused the Debian Bug report #752835, regarding gecko-mediaplayer: build-depends on xulrunner-dev which is gone 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.) -- 752835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gecko-mediaplayer Severity: serious gecko-mediaplayer build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. Emilio ---End Message--- ---BeginMessage--- Version: 1.0.9-2 On 2014-06-27 00:09:08, po...@debian.org wrote: Source: gecko-mediaplayer Severity: serious gecko-mediaplayer build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. gecko-mediaplayer (1.0.9-2) unstable; urgency=medium * debian/control: Switch from xulrunner-dev to iceweasel-dev. * debian/patches/np_loadds.patch: Define NP_LOADDS if it does not exist to prevent build failures against iceweasel = 30. -- Sebastian Ramacher sramac...@debian.org Wed, 18 Jun 2014 11:25:22 +0200 Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message---
Bug#752836: gnash: build-depends on xulrunner-dev which is gone
On Fri, Jun 27, 2014 at 12:09 AM, po...@debian.org wrote: gnash build-depends on xulrunner-dev, which is no longer built by src:iceweasel. If you use it for libxul or mozilla-plugin, that is now in iceweasel-dev. If you were using mozilla-js, you may want to look at src:mozjs24. gnash will soon build-depend on npapi-sdk-dev, in NEW queue at the moment. It should probably be recommended as better mozilla-plugin.pc replacement. -- G..e -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 752629
Processing commands for cont...@bugs.debian.org: tags 752629 + fixed-upstream Bug #752629 [ming] ming is licensed under the PHP license and is not PHP Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 752629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752629 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#752636: Only one small file, probably not copyrightable
Processing control commands:
reopen -1
Bug #752636 {Done: Mathieu Parent math.par...@gmail.com} [php-igbinary]
php-igbinary is licensed under the PHP license and is not PHP
Bug reopened
Ignoring request to alter fixed versions of bug #752636 to the same values
previously set
--
752636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752636
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#752636: Only one small file, probably not copyrightable
Control: reopen -1 On Wed, Jun 25, 2014 at 08:37:58PM +0200, Mathieu Parent wrote: Only one file (apc_serializer.h, 80 lines long) is under the PHP license. As this is an header file, I mark this bug as closed. If someone wants to reopen, please explain. I'd need an explaination about closing it: if a file is a header and/or is = 80 lines long, is it not significant for licensing purposes? Also, as this file comes from php-apc, this bug relates to https://bugs.debian.org/752530. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752851: dragonegg 3.4-1 installation fails: tries to overwrite a file in dragonegg-4.8 3.3-2
Package: dragonegg Version: 3.4-1 Severity: grave Justification: renders package unusable When trying to upgrade dragonegg: Preparing to unpack .../dragonegg_3.4-1_amd64.deb ... Unpacking dragonegg (3.4-1) over (3.3-2) ... dpkg: error processing archive /var/cache/apt/archives/dragonegg_3.4-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/gcc/x86_64-linux-gnu/4.8/plugin/dragonegg.so', which is also in package dragonegg-4.8 3.3-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/dragonegg_3.4-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dragonegg depends on: ii dragonegg-4.7 3.3-2 dragonegg recommends no packages. dragonegg suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Thu, Jun 26, 2014 at 8:50 PM, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: On Thursday 26 June 2014 12:45:51 Yunqiang Su wrote: On Thu, Jun 26, 2014 at 12:35 PM, Lisandro Damián Nicanor Pérez perezme...@gmail.com wrote: Note: I'm sending yuou a copy because I mistakenly sent it to the original bug reporter. On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote: I refreshed this patch for mips64el Yunqiang: again, when we are talking about symbols files, a simple patch for just one arch is not enough. The best way to solve this is to let mips64[el] build logs be available trough debian-ports. Yes, of course, while we are still waiting for the debian-ports guys to let us in. For now, you can get the buildlog from http://mips64el.debian.net/debian/buildlog Ah, that's a good workaround, thanks! I noticed that your new upload ftbfs on mips64el again. I think that we should make sure that the packages build successfully on any archs, so we can get the full symbols list on all of these archs. If they ftbfs, it will cost us much more time on get the full list of symbols. -- Compartir las cosas buenas es una necesidad fácil de satisfacer. Compartir las cosas malas es una necesidad mayor, pero mucho mas difícil de satisfacer. Sin embargo, es el compartir las cosas malas lo que mas nos une como hermanos. Lisandro Damián Nicanor Pérez Meyer Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -- Yunqiang Su -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747736: FTBFS: Test ruby2.1 failed. Exiting.
tags 747736 + unreproducible thanks Hi, I have attempted to build this package on a clean chroot, and found no problem (and thus would like to confirm with you whether this RC bug report can be closed). What I found in your failure build log is that all of the failing tests I checked mention: 1) Error: HTTPAccess2::TestClient#test_agent_name: Errno::EADDRINUSE: Address already in use - listen(2) Now, the tests bind to a port in localhost — The setup_server function in test_http-access2.rb begins with: def setup_server @server = WEBrick::HTTPServer.new( :BindAddress = localhost, :Logger = @logger, :Port = 0, :AccessLog = [], :DocumentRoot = File.dirname(File.expand_path(__FILE__)) ) @serverport = @server.config[:Port] I do feel odd the fact that it declares :Port = 0 — But then again, it fails to make the build fail either in my regular work environment or in a clean chroot. signature.asc Description: Digital signature
Processed: Re: FTBFS: Test ruby2.1 failed. Exiting.
Processing commands for cont...@bugs.debian.org:
tags 747736 + unreproducible
Bug #747736 {Done: Antonio Terceiro terce...@debian.org}
[src:ruby-httpclient] FTBFS: Test ruby2.1 failed. Exiting.
Added tag(s) unreproducible.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
747736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747736
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#752591: Alternative explanation for bug 752591
Hi all,
Having been bitten by this bug, and having read Michael Biebl's
explanation, I tried to make my system bootable again by blacklisting
the sg module. To my surprise, this didn't work at all!
Digging a bit further, I think I came up with an alternative
explanation. I don't think that kmod-builtin being faster than modprobe
do. The bug was caused in commit [1] by changing
RUN+=kmod sg
to
RUN{builtin}=kmod load sg
In particular, the operator was changed from += to =.
IMHO, that is the actual cause for this bug: whenever a scsi_device
appears, the RUN clause of the generic module loading rule
ENV{MODALIAS}==?*, RUN{builtin}=kmod load $env{MODALIAS}
at /lib/udev/rules.d/80-drivers.rules:5, which would have loaded sd_mod,
is overwritten by the RUN clause of the sg-specific rule.
The fix would simply be to change the RUN clause of the sg-specific rule
from
RUN{builtin}=kmod load sg
to
RUN{builtin}+=kmod load sg
This change fixes the problem on my system.
What do you think?
Tommaso Colombo
[1]
http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=f11a2ddeb6a43f99179f2f9d322ee08cb41db5b0
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Friday 27 June 2014 09:32:59 Yunqiang Su wrote: [snip] Ah, that's a good workaround, thanks! I noticed that your new upload ftbfs on mips64el again. I think that we should make sure that the packages build successfully on any archs, so we can get the full symbols list on all of these archs. Sadly that's expected. I filled #736640 and it seemed solved, but I'm now finding that it must not be the case, although I really need to carefully test it and check that it's not pkgkde-tools' symbolshelper that doesn't knows how to handle more diff in the same buildlog (although I really doubt it). Anyway it has always been like this: if you ship more than one lib in the same source package, you might not get all the symbols changes needed in the same build and thus you might still get symbols changing. If you take a look at [0] you can see that I uploaded it two more times after closing this bug. You can rest assured that I'm taking a look at buildds, and that's why I insist in making mips64[el] available in debian-ports as soon as possible, it really makes my job much easier. [0] http://metadata.ftp-master.debian.org/changelogs//main/q/qtdeclarative-opensource-src/qtdeclarative-opensource-src_5.3.1-1_changelog -- No pienses que estoy loco, es sólo una manera de actuar De mí - Charly García Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
