Bug#767563: marked as done (unblock: qt4-perl/4.8.4-1.2)
Your message dated Sat, 01 Nov 2014 08:05:12 +0100 with message-id 54548628.8050...@thykier.net and subject line Re: Bug#767563: unblock: qt4-perl/4.8.4-1.2 has caused the Debian Bug report #767563, regarding unblock: qt4-perl/4.8.4-1.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package qt4-perl Fix for RC bug #765681 Explanation for easy patch navigation: There are three patches added in this upload to solve the bug: qtcore4.pmupdate.diff updates the file qtcore/lib/QtCore.pm to the current upstream content. The changes end up being related to the bug. The second hunk of the patch (+@@ -1417,9 +1420,9 @@) solves the observable QtCore.pm problem described in #765681: defined(@array) is deprecated at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtCore4.pm line 1420. (Maybe you should just omit the defined()?) defined(@array) is deprecated at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtCore4.pm line 1421. (Maybe you should just omit the defined()?) defined(@array) is deprecated at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtCore4.pm line 1422. (Maybe you should just omit the defined()?) This alone is enough to cause a failure. The other hunks of the patch resolve an overloading problem that appears once the other issues are resolved (mentioned in the KDE bug: https://bugs.kde.org/show_bug.cgi?id=340518#c3 Subroutine Qt::GlobalSpace::_UTOLOAD redefined at /usr/lib/i386-linux-gnu/perl5/5.20/QtCore4.pm line 1304. Subroutine Qt::GlobalSpace::_UTOLOAD redefined at /usr/lib/i386-linux-gnu/perl5/5.20/QtCore4.pm line 1304. Subroutine Qt::Widget::_UTOLOAD redefined at /usr/lib/i386-linux-gnu/perl5/5.20/QtCore4.pm line 1304. Subroutine Qt::Widget::_UTOLOAD redefined at /usr/lib/i386-linux-gnu/perl5/5.20/QtCore4.pm line 1304. debian/patches/perl5.20.diff from Ubuntu (cjwatson) resolves the other observable issue described in the Debian bug: SvREFCNT_inc is not exported by the Devel::Peek module Can't continue after import errors at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtGui4.pm line 25. BEGIN failed--compilation aborted at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtGui4.pm line 25. Finally, Red Hat identified some additional incompatibility (see the referenced Red Hat bug in the patch for details that are solved by backporting the upstream commit in debian/patches/additionalperl5.20.diff. It took a bit of stitching together, but the test case provided in the bug now works correctly. unblock qt4-perl/4.8.4-1.2 diff -Nru qt4-perl-4.8.4/debian/changelog qt4-perl-4.8.4/debian/changelog --- qt4-perl-4.8.4/debian/changelog 2014-08-04 08:20:09.0 -0400 +++ qt4-perl-4.8.4/debian/changelog 2014-10-31 22:54:49.0 -0400 @@ -1,3 +1,15 @@ +qt4-perl (4.8.4-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix perl 5.20 incompatiblities (Closes: #765681) +- Add debian/patches/qtcore4.pmupdate.diff to update QtCore.pm to current + upstream for perl 5.18 compatibility +- Add debian/patches/perl5.20.diff from Ubuntu for basic perl 5.20 compat +- Add debian/patches/additionalperl5.20.diff from upstream to resolve the + final issue + + -- Scott Kitterman sc...@kitterman.com Fri, 31 Oct 2014 02:41:03 -0400 + qt4-perl (4.8.4-1.1) unstable; urgency=medium [ gregor herrmann ] diff -Nru qt4-perl-4.8.4/debian/patches/additionalperl5.20.diff qt4-perl-4.8.4/debian/patches/additionalperl5.20.diff --- qt4-perl-4.8.4/debian/patches/additionalperl5.20.diff 1969-12-31 19:00:00.0 -0500 +++ qt4-perl-4.8.4/debian/patches/additionalperl5.20.diff 2014-10-31 22:20:32.0 -0400 @@ -0,0 +1,33 @@ +commit 1b665848e178301344386717c658386d160d222a +Author: Chris Burel chrisbu...@gmail.com +Date: Fri Oct 31 11:23:18 2014 -0700 + +Use a copy of the Qt::AutoLoad::AUTOLOAD variable. + +This appears to be a change in Perl's behavior. The way the operator +overloading in PerlQt works is that it first tries to find an operator method +on the class itself, and then next it tries to find one in the so-called +QGlobalSpace, which is a place defined by the smoke library for global Qt +functions. Perl passes the underlying XS code the full package and function +being called, which PerlQt splits into 2 strings, one for the package name, and +one for the method name. PerlQt
Bug#767580: unblock: python-virtualenv/1.11.6+ds-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock This is a pre-emptive unblock request, 1.11.6+ds-1 isn't in unstable. Either it needs an unblock, or an extra-short migration. RC bug fix, removing (unused) convenience libraries that weren't tracked in debian/copyright. Patch attached. unblock python-virtualenv/1.11.6+ds-1 SR Index: debian/changelog === --- debian/changelog(revision 31340) +++ debian/changelog(working copy) @@ -1,3 +1,16 @@ +python-virtualenv (1.11.6+ds-1) UNRELEASED; urgency=medium + + [ Daniele Tricoli ] + * Repack source package to remove embedded copy of python-pip-whl and +python-setuptools-whl (Closes: #751233) + * debian/rules: +- Don't override dh_auto_configure to remove embedded wheels since + they are removed from source package + * debian/watch: +- Add dversionmangle option + + -- Stefano Rivera stefa...@debian.org Fri, 31 Oct 2014 17:59:34 -0700 + python-virtualenv (1.11.6-2) unstable; urgency=medium * d/patches/use-wheels.patch: Ignore EEXIST when creating the Index: debian/copyright === --- debian/copyright(revision 31340) +++ debian/copyright(working copy) @@ -1,6 +1,9 @@ Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: virtualenv Source: https://github.com/pypa/virtualenv + The pristine upstream source contains convenience copies of python-pip-whl and + python-setuptools-whl. +Files-Excluded: virtualenv_support/*.whl Files: * Copyright: 2007, Ian Bicking and Contributors, @@ -16,15 +19,7 @@ 2012 Barry Warsaw ba...@python.org License: Expat -Files: virtualenv_support/pip-* -Copyright: 2008-2013 The pip developers License: Expat - -Files: virtualenv_support/setuptools-* -Copyright: Phillip J. Eby -License: PSF-2 or Zope-2.1 - -License: Expat Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including @@ -43,94 +38,3 @@ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. - -License: PSF-2 - 1. This LICENSE AGREEMENT is between the Python Software Foundation - (PSF), and the Individual or Organization (Licensee) accessing and - otherwise using Python 2.3 software in source or binary form and its - associated documentation. - . - 2. Subject to the terms and conditions of this License Agreement, PSF - hereby grants Licensee a nonexclusive, royalty-free, world-wide - license to reproduce, analyze, test, perform and/or display publicly, - prepare derivative works, distribute, and otherwise use Python 2.3 - alone or in any derivative version, provided, however, that PSF's - License Agreement and PSF's notice of copyright, i.e., Copyright (c) - 2001, 2002 Python Software Foundation; All Rights Reserved are - retained in Python 2.3 alone or in any derivative version prepared by - Licensee. - . - 3. In the event Licensee prepares a derivative work that is based on - or incorporates Python 2.3 or any part thereof, and wants to make - the derivative work available to others as provided herein, then - Licensee hereby agrees to include in any such work a brief summary of - the changes made to Python 2.3. - . - 4. PSF is making Python 2.3 available to Licensee on an AS IS - basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR - IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND - DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS - FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 2.3 WILL NOT - INFRINGE ANY THIRD PARTY RIGHTS. - . - 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON - 2.3 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS - A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 2.3, - OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. - . - 6. This License Agreement will automatically terminate upon a material - breach of its terms and conditions. - . - 7. Nothing in this License Agreement shall be deemed to create any - relationship of agency, partnership, or joint venture between PSF and - Licensee. This License Agreement does not grant permission to use PSF - trademarks or trade name in a trademark sense to endorse or promote - products or services of Licensee, or any third party. - . - 8. By copying, installing or otherwise using Python 2.3, Licensee - agrees to be bound by the terms and conditions of this License - Agreement. - -License: Zope-2.1 - A copyright notice accompanies this license document that - identifies the copyright holders. - . - This license has
Bug#767580: unblock: python-virtualenv/1.11.6+ds-1
Control: tags -1 confirmed On 2014-11-01 09:55, Stefano Rivera wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock This is a pre-emptive unblock request, 1.11.6+ds-1 isn't in unstable. Either it needs an unblock, or an extra-short migration. RC bug fix, removing (unused) convenience libraries that weren't tracked in debian/copyright. Patch attached. unblock python-virtualenv/1.11.6+ds-1 SR Hi, Looks reasonable, please upload it and let me know once it has been accepted. ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5454a4ab.8040...@thykier.net
Processed: Re: Bug#767580: unblock: python-virtualenv/1.11.6+ds-1
Processing control commands: tags -1 confirmed Bug #767580 [release.debian.org] unblock: python-virtualenv/1.11.6+ds-1 Added tag(s) confirmed. -- 767580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b767580.14148432322.transcr...@bugs.debian.org
Bug#767587: please prevent auto-removal of mysql-workbench from testing
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org I just got the following notice mysql-workbench 6.2.3+dfsg-6 is marked for autoremoval from testing on 2014-12-01 It (build-)depends on packages with these RC bugs: 765664: mariadb-5.5: Multiple security fixes from October 2014 CPU could affect MariaDB which makes me worry whether mysql-workbench will be part of Jessie. Mysql-workbench depends on virtual-mysql-client provided by * mariadb-client-10.0 * mariadb-client-5.5 * mysql-client-5.5 * mysql-client-5.6 * percona-xtradb-cluster-client-5.5 I think it is a bit harsh to remove mysql-workbench from testing (merely) due to problems in one of the alternatives providing client for MySQL connectivity. Besides client package is probably not even affected by the security issues... What can we do to avoid auto-removal of mysql-workbench from Jessie? Please advise. -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B --- It is a fine thing to be honest, but it is also very important to be right. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#757575: marked as done (transition: libgcrypt20)
Your message dated Sat, 1 Nov 2014 10:16:08 + with message-id 20141101101607.gd9...@lupin.home.powdarrmonkey.net and subject line Re: Bug#757575: transition: libgcrypt20 has caused the Debian Bug report #757575, regarding transition: libgcrypt20 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.) -- 757575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello, I would like to make sure that we only ship one gcrypt version in jessie and am therefore opening the transition tracker now. libgcrypt20 is mostly API compatible to libgcrypt11. The main reason why we have versioned -dev packages is that libgnutls26 is one of the packages which cannot work with the old API. libgnutls26 should not be shipped in jessie so I envision that it should be possible to make major parts of this transition by bin-NMUs since I will be able to make libgcrypt11-dev a dummy package depending on libgcrypt20-dev after libgnutls26 has been dropped. libgcrypt11's upstream support will end on 2016-12-31. I will do some test builds to find out more. Ben file: title = libgcrypt20; is_affected = .depends ~ libgcrypt11 | .depends ~ libgcrypt20 | .depends ~ libgcrypt11-dev | .depends ~ libgcrypt20-dev | .depends ~ libgcrypt-dev; is_good = .depends ~ libgcrypt20; is_bad = .depends ~ libgcrypt11; -- `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' ---End Message--- ---BeginMessage--- On Sat, Aug 09, 2014 at 03:48:10PM +0200, Andreas Metzler wrote: I would like to make sure that we only ship one gcrypt version in jessie and am therefore opening the transition tracker now. libgcrypt20 is mostly API compatible to libgcrypt11. The main reason libgcrypt11 left Jessie this morning, and libgcrypt20 successfully migrated. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature ---End Message---
Bug#748535: marked as done (transition: gnutls28)
Your message dated Sat, 1 Nov 2014 10:14:51 + with message-id 20141101101451.gc9...@lupin.home.powdarrmonkey.net and subject line Re: Bug#748535: transition: gnutls28 has caused the Debian Bug report #748535, regarding transition: gnutls28 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.) -- 748535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello, I would like to ship jessie without GnuTLS 2.x (gnutls26) as it is dead upstream and _old_. The last upstream release was in February 2013, marking the end of a multi-year series of bugfix-only releases. Transitioning to GnuTLS 3.x is possible nowadays because GMP has switched to LGPLv3+/GPLv2+. Relevant bugs (as reported so far) are usertagged https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gnutls3;users=ametz...@debian.org. The newer gnutls version is mostly API compatible, only a handful (less than 5) packages showed build-breakage due to removed functions in my test. (Sadly openldap is one of the candidates (ITS#7430 aka ITS#6359). Almost all breakage is due to gnutls switching from gcrypt to nettle, breaking the assumption the -lgcrypt works if -lgnutls does. While there is a obvious solution to this problem (Package: libgnutls-dev / Depends: libgnutls28-dev, libgcrypt20-dev | libgcrypt11-dev) it is probably not the right one to actually ship. Most of this gcrypt usage superfluous, only adapting gcrypt behavior on the assumption that it is used by gnutls. Of the rest, a big part is only using and handful of gcrypt functions (typicall md5 or sha1) and would do well with doing this with the GnuTLS crypto API instead of adding another dependency. I am not sure how to go about this I am looking at packages one at a time. Perhaps it would be better to do a big move like this: #1 Let libgnutls-dev depend on libgnutls28-dev, libgcrypt20-dev | libgcrypt11-dev. #2 Rebuild everything, transition to testing. #3 Get rid of unnecessary gcrypt usage one at a time, add libgcrypt20-dev dependency where really necessary #4 Drop libgnutls-dev's dependency on gcrypt. While this looks good, I expect there will be some #2a Some packages break, they build successfully but break at runtime cu Andreas Ben file: title = gnutls28; is_affected = .depends ~ libgnutls26 | .depends ~ libgnutls-dev | .depends ~ libgnutlsxx27 | .depends ~ libgnutls28 | .depends ~ libgnutls28-dev | .depends ~ libgnutlsxx28; is_good = .depends ~ libgnutls28 | .depends ~ libgnutls28-dev | .depends ~ libgnutlsxx28; is_bad = .depends ~ libgnutls26 | .depends ~ libgnutls-dev | .depends ~ libgnutlsxx27; -- `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' signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On Sun, May 18, 2014 at 08:52:53AM +0200, Andreas Metzler wrote: I would like to ship jessie without GnuTLS 2.x (gnutls26) as it is dead upstream and _old_. The last upstream release was in February 2013, marking the end of a multi-year series of bugfix-only releases. gnutls26 left Jessie this morning, and gnutls28 successfully migrated. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature ---End Message---
Bug#767587: please prevent auto-removal of mysql-workbench from testing
Hi Dmitry, On Sat, Nov 01, 2014 at 03:27:07AM -0700, Dmitry Smirnov wrote: I just got the following notice mysql-workbench 6.2.3+dfsg-6 is marked for autoremoval from testing on 2014-12-01 It (build-)depends on packages with these RC bugs: 765664: mariadb-5.5: Multiple security fixes from October 2014 CPU could affect MariaDB which makes me worry whether mysql-workbench will be part of Jessie. Mysql-workbench depends on virtual-mysql-client provided by * mariadb-client-10.0 * mariadb-client-5.5 * mysql-client-5.5 * mysql-client-5.6 * percona-xtradb-cluster-client-5.5 I think it is a bit harsh to remove mysql-workbench from testing (merely) due to problems in one of the alternatives providing client for MySQL connectivity. Besides client package is probably not even affected by the security issues... What can we do to avoid auto-removal of mysql-workbench from Jessie? This is a bug in the auto-removal system. I expect mariadb-5.5 to be removed before 2014-12-01, solving the issue in this case, but if you get the second notification about this auto-removal, please ping this bug, and I'll prevent the auto-removal manually. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101113350.ga25...@ugent.be
Bug#767467: unblock: libapache2-mod-nss/1.0.10-2
On 31.10.2014 23:10, Niels Thykier wrote: On 2014-10-31 10:28, Timo Aaltonen wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libapache2-mod-nss [...] Hi Timo, Sorry, I had missed that you uploaded libapache2-mod-nss today. I have decided to age this package so it only needs 2 days. That said, I got a couple of remarks: * The 1.0.10-1 upload does not mention CVE-2014-3566 in d/changelog despite upstream listing it in their upstream. * We want the full debdiff between unstable and testing, as that is what we are approving. ok, diff attached -- t diff --git a/ChangeLog b/ChangeLog index d40ce8b..97bf4b6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2014-10-16 Rob Crittenden rcrit...@redhat.com +* Add support for enabling TLS v1.2 +* Don't enable SSL 3 by default (CVE-2014-3566) +* Improve protocol testing + 2014-02-20 Rob Crittenden rcrit...@redhat.com * Sync with Fedora builds which were basicaly the defacto upstream. * Add nss_pcache man page diff --git a/Makefile.am b/Makefile.am index 5a94c2f..986048d 100644 --- a/Makefile.am +++ b/Makefile.am @@ -1,4 +1,4 @@ -VERSION = 1.0.9 +VERSION = 1.0.10 ## This is the shared library to be built lib_LTLIBRARIES = libmodnss.la diff --git a/README b/README index 8581698..542e114 100644 --- a/README +++ b/README @@ -122,4 +122,4 @@ TESTING From the source tree run: - % make test + % make check diff --git a/debian/changelog b/debian/changelog index cd4f1c1..d027154 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,18 @@ +libapache2-mod-nss (1.0.10-2) unstable; urgency=medium + + * rules: Don't enable the module by default. + + -- Timo Aaltonen tjaal...@debian.org Tue, 28 Oct 2014 15:11:45 +0200 + +libapache2-mod-nss (1.0.10-1) unstable; urgency=medium + + * mod_nss-conf.patch: Fix IfModule header so it'll actually load when +the module is enabled. + * gencert: Revert back to default legacy db's. + * Update project homepage and watch file to match. + + -- Timo Aaltonen tjaal...@debian.org Tue, 21 Oct 2014 18:52:59 +0300 + libapache2-mod-nss (1.0.9-1) unstable; urgency=medium * New upstream release diff --git a/debian/control b/debian/control index bd6b8e1..c621cc6 100644 --- a/debian/control +++ b/debian/control @@ -13,7 +13,7 @@ Build-Depends: libnss3-dev, pkg-config Standards-Version: 3.9.5 -Homepage: http://directory.fedoraproject.org +Homepage: http://fedorahosted.org/mod_nss Vcs-Git: git://anonscm.debian.org/pkg-fedora-ds/libapache2-mod-nss.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-fedora-ds/libapache2-mod-nss.git diff --git a/debian/copyright b/debian/copyright index b0bd62a..818e21e 100644 --- a/debian/copyright +++ b/debian/copyright @@ -1,6 +1,6 @@ Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ UPstream-name: mod_nss -Source: http://directory.fedoraproject.org/sources/ +Source: http://fedorahosted.org/mod_nss Files: * Copyright: 2001-2004 The Apache Software Foundation diff --git a/debian/libapache2-mod-nss.postinst b/debian/libapache2-mod-nss.postinst index dccc887..c586db3 100644 --- a/debian/libapache2-mod-nss.postinst +++ b/debian/libapache2-mod-nss.postinst @@ -4,7 +4,7 @@ set -e CERTDIR=/etc/apache2/nssdb if [ $1 = configure ]; then -if [ ! -e $CERTDIR/key4.db ]; then +if [ ! -e $CERTDIR/key3.db ]; then /usr/share/libapache2-mod-nss/gencert \ $CERTDIR $CERTDIR/install.log 21 echo libapache2-mod-nss certificate database generated. diff --git a/debian/patches/mod_nss-conf.patch b/debian/patches/mod_nss-conf.patch index bb1d4aa..d3a6480 100644 --- a/debian/patches/mod_nss-conf.patch +++ b/debian/patches/mod_nss-conf.patch @@ -1,7 +1,7 @@ --- a/nss.conf.in +++ b/nss.conf.in @@ -1,3 +1,4 @@ -+IfModule mod_nss ++IfModule mod_nss.c # # This is the Apache server configuration file providing SSL support using. # the mod_nss plugin. It contains the configuration directives to instruct diff --git a/debian/patches/mod_nss-gencert.patch b/debian/patches/mod_nss-gencert.patch index 0da316d..c2b2f4d 100644 --- a/debian/patches/mod_nss-gencert.patch +++ b/debian/patches/mod_nss-gencert.patch @@ -1,6 +1,6 @@ --- a/gencert.in +++ b/gencert.in -@@ -83,14 +83,13 @@ fi +@@ -83,12 +83,11 @@ fi DEST=$1 @@ -13,65 +13,8 @@ -echo is httptest +echo Generating new server certificate and key database. echo # --$CERTUTIL -N -d $DEST -f $DEST/pw.txt -+$CERTUTIL -N -d sql:$DEST -f $DEST/pw.txt + $CERTUTIL -N -d $DEST -f $DEST/pw.txt - echo - echo # -@@ -102,7 +101,7 @@ let CERTSERIAL=CERTSERIAL+1 - # y 10 y - basic constraints: CA cert - # 5 6 7 9 n - SSL, S/MIME, Object signing CA - echo -e
Re: Bug#767411: torque: should not be released with jessie
Hi Julien, On Fri, Oct 31, 2014 at 02:07:25PM +0100, Julien Cristau wrote: On Thu, Oct 30, 2014 at 22:27:53 +0100, Salvatore Bonaccorso wrote: pbs-drmaa as reverse dependency of torque is easy as it is a leaf package. The more complicated one would be openmpi which would need to drop the build dependency on libtorque2-dev. The reason for this dependency was in https://bugs.debian.org/592887 , which needs to be dropped again. There's two solutions here. One is to drop torque support from openmpi; the other is to keep the torque source package but only build the libtorque library, as I'm assuming the security issues are on the torque server side. Though that's only useful is that library can still talk to newer torque version. Given Dominique's reply on #767411, from my POV I think the best solution would be to remove torque completely for jessie (i.e. first drop support from openmpi to be able to remove the package and remaining reverse dependencies). Alastair, could you please take care of updating openmpi to drop the torque support? Regards, Salvatore signature.asc Description: Digital signature
Re: libotr transition started by mistake :-/
Hi, Niels Thykier wrote (30 Oct 2014 22:05:20 GMT) : On 2014-10-29 17:09, intrigeri wrote: Plan A -- ship Jessie with libotr 4.1, drop the version check temporarily = 1. Patch libotr to loosen this version check on Jessie: assuming the no API/ABI break assumption is true, this should work just fine. I suspect this will be the least intrusive method assuming the no ABI/API assertion holds. I'll check this the best I can (I'll try my best with the readelf command you provided and also will generate shlibs files for both 4.0 and 4.1, and compare what's in there). I'll also test, as a practical usecase, that e.g. pidgin-otr built against libotr 4.0 works fine with libotr 4.1. 2. For Jessie+1, re-add the version check, and get proper shlibs support so that we get proper transition handling next time. As I recall, we generally prefer libraries do not have unnecessary strictly equal runtime version checks, since they tend to be wrong. Proper use of shlibs (or symbols) and SONAME bumping (with package renaming) makes such checks redundant (for Debian maintained reverse dependencies). Actually, the way I understand the code, what we have here is not a strictly equal runtime version check, but rather runtime version greater or equal to the build-time one, which is better in that it doesn't require binNMUs. But anyway, for Jessie+1 I'll add shlibs support, so indeed this check will be redundant; and then, my understanding is that it'll also become fully harmless. I generally agree with plan A (with the a minor remark mentioned above). OK, I'll do that. Thanks! Please also prepare a debdiff between libotr/4.1.0-1 and the proposed version[1] and send it to us (to this thread), so we can review the additional changes we will accept. Sure, will do. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/85d296ly1t@boum.org
Re: inconsistent versions of M-A: same packages
[ Fixed CC and M-F-T addresses, and bounced to debian-release. ] Hi! On Sat, 2014-11-01 at 11:45:56 +0100, Marc Glisse wrote: sorry for the naive question, but is there a plan for massively rebuilding all Multi-Arch: same packages that have inconsistent version numbers across architectures before releasing Jessie? That's something for the release-team and build admins. I understand that in testing or unstable, rebuilding for all platforms every time a single one needs a rebuild is costly. And there may be solutions in future versions of dpkg/apt to accept multiarch co-installations that differ only by a rebuild. But in the mean time, for a stable release like Jessie, it would be nice to be able to take advantage of the good work some maintainers have put into adapting their packages to M-A. I was planning to propose a minimal fix in dpkg to the release-team, after the current version has migrated. Of course if it is not accepted, then targetted rebuilds might be needed instead, or a decision to ignore it. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101121711.ga14...@gaara.hadrons.org
Bug#767641: unblock: espeakup/1:0.71-17
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello,
unblock espeakup/1:0.71-17
I'd like to upload the attached changes to the espeakup package, to fix
bug #767595:
“
While using speakup with espeakup, not all keypresses get spoken, e.g.
^ doesn't get spoken at all. Worse, requesting character-by-character
reading of the screen doesn't speak it either. This can be fixed by
telling espeak to say-as tts:char in SSML.
”
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'),
(500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff --git a/debian/changelog b/debian/changelog
index e6a0fa8..f85afc3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+espeakup (1:0.71-17) UNRELEASED; urgency=medium
+
+ * patches/spell: Fix spelling keystrokes and char-by-char echo
+(Closes: #767595)
+
+ -- Samuel Thibault sthiba...@debian.org Sat, 01 Nov 2014 12:35:08 +0100
+
espeakup (1:0.71-16) unstable; urgency=medium
* po/el.po: Greek translation (Closes: #685552)
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..da3f5a7
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+spell
diff --git a/debian/patches/spell b/debian/patches/spell
new file mode 100644
index 000..304b832
--- /dev/null
+++ b/debian/patches/spell
@@ -0,0 +1,24 @@
+--- a/synth.c
b/synth.c
+@@ -121,7 +121,19 @@ espeak_ERROR speak_text(struct synth_t *
+ {
+ espeak_ERROR rc;
+
+- rc = espeak_Synth(s-buf, s-len + 1, 0, POS_CHARACTER, 0, 0, NULL,
+-NULL);
++ if (s-len == 1)
++ {
++ char *buf;
++ int n;
++ n = asprintf(buf, say-as
interpret-as=\tts:char\%c/say-as, s-buf[0]);
++ rc = espeak_Synth(buf, n + 1, 0, POS_CHARACTER, 0, espeakSSML,
NULL,
++NULL);
++ free(buf);
++ }
++ else
++ {
++ rc = espeak_Synth(s-buf, s-len + 1, 0, POS_CHARACTER, 0, 0,
NULL,
++NULL);
++ }
+ return rc;
+ }
Please Allow unifont/1:7.0.06-1 (Unstable) to Migrate to Testing
Dear Release Team, I am the maintainer of GNU Unifont, both upstream (http://savannah.gnu.org/projects/unifont) and on Debian. You've asked that people not email you unblocking requests unless necessary. In this case, a release of Unifont that I packaged on 24 October (unifont/1:7.0.06-1) shows an override problem that might prevent its automatic migration into Testing (https://qa.debian.org/debcheck.php?dist=unstablepackage=unifont). I request that you let unifont/1:7.0.06-1 migrate in spite of that, with the understanding that I will sort the issue out with the FTP Masters in the near future. I filed an override bug for the FTP Masters on 24 October to change the priority of unifont-bin, but have gotten no reply from them (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766699). The version of Unifont in Testing (unifont/1:7.0.03-1) is not suitable for Jessie because it uses liggd-gd2-noxpm-perl, which was removed from Testing this summer. That library is now replaced by libgd-perl. I only learned of that when I packaged unifont/1:7.0.05-1 on 19 October. Because libgd-perl has priority extra, I changed the priority of unifont-bin from optional to extra to conform to Section 2.5 of the Policy Manual. unifont-bin contains programs to modify Unifont and to rebuild it from source files. Fewer than 200 systems report having it installed on popcon (https://qa.debian.org/popcon.php?package=unifont); most users just want to use the resulting fonts. If you allow the Unstable version of Unifont to migrate to Testing in two days (when it is 10 days old), the version in Testing will be replaced and that problem will take care of itself. The only other alternatives I can see if unifont-bin must remain with priority optional are changing the priority of ligd-perl from extra to optional, or stripping Unifont of its Perl scripts that manipulate PNG images. I can do the latter if you want, but I think it would be a shame to cripple the Debian version of Unifont by removing its ability to handle PNG images. Apart from having complete coverage of the Unicode 7.0 Basic Multilingual Plane, Unifont 7.0.x adds 25 Supplemental Multilingual Plane (Unicode Plane 1) scripts that have no other representation in Debian fonts (at least as of when they were added to Unifont), according to https://wiki.debian.org/Fonts/UnicodeCoverage. Four of these were added in the very latest release, unifont/1:7.0.06-1: - Old Permic - Ornamental Dingbats - Geometric Shapes Extended - Supplemental Arrows-C If you have any other suggestions for getting this latest release into Testing, please let me know. Thank you, Paul Hardy -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJqvfD_yAVsmpdjgsBjmwSbB4yWP7OpxqUt=5d0azivevse...@mail.gmail.com
Bug#767643: unblock: vite/1.2+svn1430-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock unblock vite/1.2+svn1430-2 Hello, I would like to upload the attach changes, which fix bug #767451: “ vite has a library package directly specified as build dependency. This can be problematic e.g. in the (rare) case they bump SONAME, but in general specifying directly a library as build dependency is useless (its -dev will install the latest version of it). Attached a patch that removes libqt4-opengl, as it is installed by libqt4-opengl-dev already. ” Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel RK Some PC speakers are actually buzzers in some cases rather than RK real loudspeakers which give a squark rather than a beep. DW They're not _that_ bad. Even on most recent hardware, mp3s played DW through the PC speaker are relatively recognisable :) -+- lkml -+- Index: control === --- control (révision 1431) +++ control (copie de travail) @@ -4,12 +4,12 @@ Maintainer: Samuel Thibault sthiba...@debian.org Build-Depends: debhelper (= 7.0.50), cmake, - libqt4-dev (= 4:4.6), libqt4-opengl, libqt4-opengl-dev, + libqt4-dev (= 4:4.6), libqt4-opengl-dev, texlive-latex-base, texlive-latex-recommended, texlive-latex-extra, libotf-trace-dev, texlive-fonts-recommended, ghostscript, zlib1g-dev, hardening-wrapper -Standards-Version: 3.9.5 +Standards-Version: 3.9.6 Homepage: http://vite.gforge.inria.fr/ Vcs-Browser: http://gforge.inria.fr/plugins/scmsvn/viewcvs.php/package/?root=vite Vcs-Svn: svn://scm.gforge.inria.fr/svn/vite/package Index: changelog === --- changelog (révision 1431) +++ changelog (copie de travail) @@ -1,3 +1,11 @@ +vite (1.2+svn1430-2) UNRELEASED; urgency=medium + + * control: remove spurious libqt4-opengl build-dependency, already pulled by +libqt4-opengl-dev (Closes: Bug#767451). + * Bump Standards-Version to 3.9.6 (no changes). + + -- Samuel Thibault sthiba...@debian.org Fri, 19 Sep 2014 17:53:45 +0200 + vite (1.2+svn1430-1) unstable; urgency=medium * New upstream snapshot.
Re: Please Allow unifont/1:7.0.06-1 (Unstable) to Migrate to Testing
On 2014-11-01 16:56, Paul Hardy wrote: Dear Release Team, Hi, I am the maintainer of GNU Unifont, both upstream (http://savannah.gnu.org/projects/unifont) and on Debian. You've asked that people not email you unblocking requests unless necessary. Rather than emails, please file bugs for unblock requests. Bugs are easier to track and can be tagged in the BTS. In this case, a release of Unifont that I packaged on 24 October (unifont/1:7.0.06-1) shows an override problem that might prevent its automatic migration into Testing (https://qa.debian.org/debcheck.php?dist=unstablepackage=unifont). I request that you let unifont/1:7.0.06-1 migrate in spite of that, with the understanding that I will sort the issue out with the FTP Masters in the near future. I filed an override bug for the FTP Masters on 24 October to change the priority of unifont-bin, but have gotten no reply from them (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766699). [...] Thank you, Paul Hardy The problem mentioned is not a blocker for migration on its own. I see nothing beyond age currently blocking the migration of unifont/1:7.0.06-1. At this rate, it should become valid tomorrow night (UTC). ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/545504b7.3000...@thykier.net
Bug#767645: unblock: starpu/1.1.3+dfsg-3 and starpu-contrib/1.1.3+dfsg-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
unblock starpu/1.1.3+dfsg-3
unblock starpu-contrib/1.1.3+dfsg-3
Hello,
I would like to upload the attached changes: when I added libsocl
to main/starpu, I forgot to add the conflict with the version from
contrib/starpu-contrib, libsocl-contrib (since they ship exactly the
same library, with different support).
This fixes Bug#767557.
Samuel
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'),
(500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- debian/changelog(.../unstable/debian) (révision 13479)
+++ debian/changelog(.../jessie/debian) (copie de travail)
@@ -1,3 +1,11 @@
+starpu (1.1.3+dfsg-3) UNRELEASED; urgency=medium
+
+ * control: Make libsocl-1.1-1 and libsocl-contrib-1.1-1 conflict/provide each
+other (Closes: Bug#767557).
+ * Bump Standards-Version to 3.9.6 (no changes).
+
+ -- Samuel Thibault sthiba...@debian.org Fri, 19 Sep 2014 17:51:54 +0200
+
starpu (1.1.3+dfsg-2) unstable; urgency=medium
* control: Make libstarpu-1.1-7 Replace libstarpu-1.1-6: the soname bump
--- debian/rules(.../unstable/debian) (révision 13479)
+++ debian/rules(.../jessie/debian) (copie de travail)
@@ -65,6 +65,7 @@
sed -i 's/Package: libsocl-contrib/Package: libsocl/' debian/control
sed -i '/Depends/s/ libstarpu-contrib/ libstarpu/g' debian/control
sed -i 's/Conflicts: libstarpu/Conflicts: libstarpu-contrib/'
debian/control
+ sed -i 's/Conflicts: libsocl/Conflicts: libsocl-contrib/' debian/control
sed -i 's/Conflicts: starpu/Conflicts: starpu-contrib/' debian/control
sed -i 's/^Provides:/#Provides:/' debian/control
sed -i 's/^Architecture: amd64 i386/Architecture: any/' debian/control
@@ -87,6 +88,7 @@
sed -i 's/Package: libsocl/Package: libsocl-contrib/' debian/control
sed -i '/Depends/s/ libstarpu/ libstarpu-contrib/g' debian/control
sed -i 's/Conflicts: libstarpu-contrib/Conflicts: libstarpu/'
debian/control
+ sed -i 's/Conflicts: libsocl-contrib/Conflicts: libsocl/' debian/control
sed -i 's/Conflicts: starpu-contrib/Conflicts: starpu/' debian/control
sed -i 's/^#Provides:/Provides:/' debian/control
sed -i 's/^ gcc-$(GCC_VERSION), g++-$(GCC_VERSION),
gfortran-$(GCC_VERSION), gcc-$(GCC_VERSION)-plugin-dev,/#
gcc-$(GCC_VERSION), g++-$(GCC_VERSION), gfortran-$(GCC_VERSION),
gcc-$(GCC_VERSION)-plugin-dev,/' debian/control
--- debian/control (.../unstable/debian) (révision 13479)
+++ debian/control (.../jessie/debian) (copie de travail)
@@ -23,7 +23,7 @@
help2man,
# nvidia-cuda-toolkit,
#Build-Conflicts: gcc-4.9, g++-4.9, hardening-wrapper
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
Section: libs
Homepage: http://starpu.gforge.inria.fr/
Vcs-Svn: svn://scm.gforge.inria.fr/svn/starpu/debian/unstable
@@ -153,6 +153,8 @@
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
+Conflicts: libsocl-contrib-1.1-1
+#Provides: libsocl-1.1-1
Description: Task scheduler for heterogeneous multicore machines
StarPU is a runtime system that offers support for heterogeneous
multicore machines. While many efforts are devoted to design efficient
--- debian/changelog2014-09-15 00:03:16.0 +0200
+++ debian/changelog2014-11-01 17:12:10.481340400 +0100
@@ -1,3 +1,11 @@
+starpu-contrib (1.1.3+dfsg-3) UNRELEASED; urgency=medium
+
+ * control: Make libsocl-1.1-1 and libsocl-contrib-1.1-1 conflict/provide each
+other (Closes: Bug#767557).
+ * Bump Standards-Version to 3.9.6 (no changes).
+
+ -- Samuel Thibault sthiba...@debian.org Fri, 19 Sep 2014 17:51:54 +0200
+
starpu-contrib (1.1.3+dfsg-2) unstable; urgency=medium
* control: Make libstarpu-1.1-7 Replace libstarpu-1.1-6: the soname bump
--- debian/rules2014-06-19 16:11:25.0 +0200
+++ debian/rules2014-11-01 17:04:41.533058704 +0100
@@ -65,6 +65,7 @@
sed -i 's/Package: libsocl-contrib/Package: libsocl/' debian/control
sed -i '/Depends/s/ libstarpu-contrib/ libstarpu/g' debian/control
sed -i 's/Conflicts: libstarpu/Conflicts: libstarpu-contrib/'
debian/control
+ sed -i 's/Conflicts: libsocl/Conflicts: libsocl-contrib/' debian/control
sed -i 's/Conflicts: starpu/Conflicts: starpu-contrib/' debian/control
sed -i 's/^Provides:/#Provides:/' debian/control
sed -i 's/^Architecture: amd64 i386/Architecture: any/' debian/control
@@ -87,6 +88,7 @@
sed -i 's/Package: libsocl/Package: libsocl-contrib/' debian/control
sed -i '/Depends/s/
Re: Please Allow unifont/1:7.0.06-1 (Unstable) to Migrate to Testing
Niels, On Sat, Nov 1, 2014 at 9:05 AM, Niels Thykier ni...@thykier.net wrote: Rather than emails, please file bugs for unblock requests. Bugs are easier to track and can be tagged in the BTS. Okay. I wasn't sure whether or not this situation would block migration but didn't want to take a chance. The problem mentioned is not a blocker for migration on its own. I see nothing beyond age currently blocking the migration of unifont/1:7.0.06-1. At this rate, it should become valid tomorrow night (UTC). ~Niels Great. No need to file something in the BTS then. Thanks for the light-speed reply! Paul -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJqvfD94ph0snS_no+v=yfafbinnguzcrsrnvvtwaj5yv4f...@mail.gmail.com
Uploading linux (3.16.7-1)
I intend to upload linux version 3.16.7-1 to unstable on Sunday or Monday. This will include at least: - Stable update 3.16.7 - Many security fixes - New hardware support - OvisLink WN-200USB wifi adapter - PWM-controlled LEDs including those on the Cubox-i - Thunderbolt hotplug for Apple computers - i.MX6 RTC - i.MX6 USB host (already enabled, now included in installer) - S3C2410 I2C controller (already enabled, now built-in as needed for Arndale board) - Olimex A20-OLinuXino-LIME board - Various drivers for Nokia N900 - USB EHCI and OHCI drivers for arm64 - MTD drivers for armhf (and most other architectures) - Armada 370 PCI and NAND controllers - Various drivers for Netgear ReadyNAS 102/104 - UBNT E200 board (EdgeRouter/EdgeRouter Pro 8 port) - Octeon serial port - Various other bug fixes There will be an ABI bump to 3.16-4. Also, the 486 flavour on i386 will be renamed to 586, as it has not worked on 486 processors since we enabled CONFIG_CC_STACKPROTECTOR in 2.6.31-1~experimental.1 (pre-squeeze). I have already updated the kernel selection code in base-installer, and the manual, to reflect this change. Ben. -- Ben Hutchings Kids! Bringing about Armageddon can be dangerous. Do not attempt it in your own home. - Terry Pratchett and Neil Gaiman, `Good Omens' signature.asc Description: This is a digitally signed message part
pjproject 2.1 = 2.3
Hi, I'd like to get your permission to update the version of pjproject to version 2.3 for the purpose of using upstream versions and avoiding embeded copies. pjproject (a.k.a pjsip, http://www.pjsip.org/) is a multimedia communication library written in C and has had a reputation of only allowing static linking. The version we have in the archive is 2.1.0.0.ast20130823-1. This is was a fork of the upstream code base that was mainly intended to allow dynamic linking. It was merged into the upstream code base after the release of 2.2 and hence 2.3 (release at September) is the first upstream release that supports dynamic linking. Note that due to the addition of an extra library (libpjsua2-2), it will have to fo through NEW. Reverse dependencies: * sflphone: There is currently a single embedded copy of pjproject in the package sflphone. Building it dynamically seems to require very little changes and the package does pass initial smoke tests. It is currently built with Upstream version 2.2.1. I don't think it is a good idea to try to build it with a basterdised 2.1 version (I have tried and failed, but I didn't try very hard). sflphone 4.9 will be support using system copy of pjproject - they are aware of the problem and it's not a change we'll have to support forever. * Asterisk: Seems to work well with both the old and the new version. The python bindings (if added) would allow running more tests in the Asterisk test-suite. I have not yet uploaded the package. The changes could be found in branch master-2.3 of the package pjproject: http://anonscm.debian.org/cgit/pkg-voip/pjproject.git/log/?h=master-2.3 Built packages could be found at https://people.debian.org/~tzafrir/pj23/ Should I proceed to upload it to Unstable? Are there any changes required? -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best tzaf...@debian.org|| friend -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101171005.gb5...@lemon.cohens.org.il
Re: libotr transition started by mistake :-/
Hi,
[It's probably too late already, but if you prefer I can move this
discussion to a dedicated bug filed against release.d.o.]
Here's my analysis of the potential ABI/API breakage in libotr
4.0-4.1, and attached the debdiff (implementing plan A) that I could
upload to sid (and then request to be aged or unblocked so that it
migrates to testing eventually).
Functions added to context.h
otrl_context_find_recent_instance
-
ConnContext * otrl_context_find_recent_instance(ConnContext * context,
otrl_instag_t recent_instag);
This one is not modified at all in context.c
otrl_context_find_recent_secure_instance
ConnContext * otrl_context_find_recent_secure_instance(ConnContext * context);
This one is slightly changed in context.c. Ignoring the typo fix in
a comment, the change is:
- if (context-msgstate != OTRL_MSGSTATE_PLAINTEXT) return 1;
+ if (c_iter-msgstate != OTRL_MSGSTATE_PLAINTEXT) return 1;
I doubt this breaks the API or ABI.
Function added to both mem.c and mem.h
==
int otrl_mem_differ(const unsigned char *buf1, const unsigned char *buf2,
size_t len);
My (limited) understanding is that adding a function does not break
the API nor ABI.
readelf
===
I've diff'ed the output of the following command run on the one hand
on current Jessie (libotr 4.0.0-3) and current sid (libotr 4.1.0-1):
readelf -Ws /usr/lib/libotr.so.5 | awk '{print $8}' | sort
The result is that two symbols were added in 4.1:
gcry_mpi_snew@GCRYPT_1.6
otrl_mem_differ
The full output lines from readelf -Ws, regarding the added or modified
functions, is:
* 4.0:
117: 7a50 123 FUNCGLOBAL DEFAULT 11
otrl_context_find_recent_instance
185: 7b20 292 FUNCGLOBAL DEFAULT 11
otrl_context_find_recent_secure_instance
* 4.1:
118: 7af0 123 FUNCGLOBAL DEFAULT 11
otrl_context_find_recent_instance
181: bd50 100 FUNCGLOBAL DEFAULT 11 otrl_mem_differ
187: 7bc0 292 FUNCGLOBAL DEFAULT 11
otrl_context_find_recent_secure_instance
I lack the background to tell if the differences seen in the 1st (Num)
and 2nd (Value) columns matter. Do they indicate ABI breakage?
symbols
===
I've extracted the libotr5 binary packages from Jessie and sid, and
then run:
dpkg-gensymbols -v4.0.0 -plibotr5 -P/tmp/intrigeri/4.0-extracted -Osymbols
dpkg-gensymbols -v4.1.0 -plibotr5 -P/tmp/intrigeri/4.1-extracted -Osymbols
The second command tells me:
--- symbols (libotr5_4.1.0_amd64)
+++ dpkg-gensymbolsjwu_Lf 2014-11-01 17:42:21.409469548 +0100
@@ -51,6 +51,7 @@
otrl_instag_read_FILEp@Base 4.0.0
otrl_instag_write@Base 4.0.0
otrl_instag_write_FILEp@Base 4.0.0
+ otrl_mem_differ@Base 4.1.0
otrl_mem_init@Base 4.0.0
otrl_message_abort_smp@Base 4.0.0
otrl_message_disconnect@Base 4.0.0
... which seems to confirm the fact that there was no
API/ABI breakage.
Applications built against libotr 4.0 and running with 4.1
==
* pidgin-otr 4.0.1-1 rebuilt in a Jessie chroot: works fine on
current sid
= seems to confirm that applications built against the old version
still work fine with the new one.
The attached patch
==
I've gone with the smallest possible change (removing one single
line), and left the warning be printed on stderr, in the hope it may
help debugging issues in case something is wrong with this analysis.
If the RT prefers, I can drop the warning too.
I've successfully tested the resulting libotr5 binary package with:
* pidgin-otr 4.0.1-1 built in a Jessie chroot (against libotr 4.0)
* pidgin-otr 4.0.1-1 from sid (that was built against libotr 4.1)
... but I could not directly test the actual intended effect of the
patch (it would require building an _older_ version of libotr with
this patch, building a package against the new version, and running it
with the patched old version). This leads me to think that perhaps
this patch may not be as useful as I used to think.
Conclusion
==
Unless the differences I've found in readelf output indicate ABI
breakage, it seems equally safe to either:
* upload with the attached debdiff to sid, wait for it to build on
all architectures, and then let it migrate to testing;
* just let libotr migrate to testing as is (my current understanding
is that it should fix two RC bugs, without introducing any new
breakage).
So, whatever the release team feels more comfortable with :)
[Regarding the plans for Jessie+1, I've filed #767652 so we (pkg-otr
team) don't forget about it.]
Cheers,
--
intrigeri
diff -Nru libotr-4.1.0/debian/changelog libotr-4.1.0/debian/changelog
--- libotr-4.1.0/debian/changelog 2014-10-21 22:26:51.0 +0200
+++
Re: pjproject 2.1 = 2.3
Hi, On Sat, Nov 01, 2014 at 06:10:05PM +0100, Tzafrir Cohen wrote: I'd like to get your permission to update the version of pjproject to version 2.3 for the purpose of using upstream versions and avoiding embeded copies. pjproject (a.k.a pjsip, http://www.pjsip.org/) is a multimedia communication library written in C and has had a reputation of only allowing static linking. The version we have in the archive is 2.1.0.0.ast20130823-1. This is was a fork of the upstream code base that was mainly intended to allow dynamic linking. It was merged into the upstream code base after the release of 2.2 and hence 2.3 (release at September) is the first upstream release that supports dynamic linking. Note that due to the addition of an extra library (libpjsua2-2), it will have to fo through NEW. Unless you can persuade me otherwise, I think it's too late for this. Getting rid of embedded copies is a nice goal, but the disruption is too great at this stage. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101180556.ga3...@lupin.home.powdarrmonkey.net
Re: libotr transition started by mistake :-/
On Sat, Nov 1, 2014 at 16:50:54 +0100, intrigeri wrote: But anyway, for Jessie+1 I'll add shlibs support, so indeed this check will be redundant; and then, my understanding is that it'll also become fully harmless. It'd be better if this didn't wait until jessie+1. Please let me know off-list if you'd like help on this. (and no, it won't be harmless) Cheers, Julien signature.asc Description: Digital signature
Re: Bug#767411: torque: should not be released with jessie
On Sat, Nov 1, 2014 at 16:46:12 +0100, Salvatore Bonaccorso wrote: Hi Julien, On Fri, Oct 31, 2014 at 02:07:25PM +0100, Julien Cristau wrote: On Thu, Oct 30, 2014 at 22:27:53 +0100, Salvatore Bonaccorso wrote: pbs-drmaa as reverse dependency of torque is easy as it is a leaf package. The more complicated one would be openmpi which would need to drop the build dependency on libtorque2-dev. The reason for this dependency was in https://bugs.debian.org/592887 , which needs to be dropped again. There's two solutions here. One is to drop torque support from openmpi; the other is to keep the torque source package but only build the libtorque library, as I'm assuming the security issues are on the torque server side. Though that's only useful is that library can still talk to newer torque version. Given Dominique's reply on #767411, from my POV I think the best solution would be to remove torque completely for jessie (i.e. first drop support from openmpi to be able to remove the package and remaining reverse dependencies). I don't know how much of that reply applies to the library... Cheers, Julien signature.asc Description: Digital signature
Bug#767587: please prevent auto-removal of mysql-workbench from testing
On Sat, Nov 1, 2014 at 03:27:07 -0700, Dmitry Smirnov wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org I just got the following notice mysql-workbench 6.2.3+dfsg-6 is marked for autoremoval from testing on 2014-12-01 It (build-)depends on packages with these RC bugs: 765664: mariadb-5.5: Multiple security fixes from October 2014 CPU could affect MariaDB which makes me worry whether mysql-workbench will be part of Jessie. Mysql-workbench depends on virtual-mysql-client provided by * mariadb-client-10.0 * mariadb-client-5.5 * mysql-client-5.5 * mysql-client-5.6 * percona-xtradb-cluster-client-5.5 A dependency on a virtual package with multiple providers and no real alternative is a serious bug in mysql-workbench. Please make the dependency mysql-client | virtual-mysql-client. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#767411: torque: should not be released with jessie
On Sat, Nov 1, 2014 at 11:46 AM, Salvatore Bonaccorso wrote: Given Dominique's reply on #767411, from my POV I think the best solution would be to remove torque completely for jessie (i.e. first drop support from openmpi to be able to remove the package and remaining reverse dependencies). 4 wheezy DSAs doesn't necessarily sound that horrible, so I don't think we're clearly at the point where torque should be considered unsupportable. Maybe the patch backports were an incredible amount of work? The package does clearly need to be orphaned, so someone can step up post-jessie to get the package in sync with upstream. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CANTw=MNGM0XsNCWTAGe5FEO05sfiX6y91Hm2M=630sy14wb...@mail.gmail.com
Re: inconsistent versions of M-A: same packages
On Sat, Nov 1, 2014 at 13:17:11 +0100, Guillem Jover wrote: [ Fixed CC and M-F-T addresses, and bounced to debian-release. ] Hi! On Sat, 2014-11-01 at 11:45:56 +0100, Marc Glisse wrote: sorry for the naive question, but is there a plan for massively rebuilding all Multi-Arch: same packages that have inconsistent version numbers across architectures before releasing Jessie? That's something for the release-team and build admins. As far as I'm concerned I'm happy to schedule rebuilds if i386 and amd64 aren't in sync. Any other archs I'm not going to touch. Cheers, Julien signature.asc Description: Digital signature
Bug#767661: openssl: new upstream release 1.0.2 for jessie
Package: release.debian.org Severity: normal Hi, I would like to upload the new upstream release of openssl 1.0.2 to unstable to get it into jessie. I know I'm a little late with this. It's actually not released yet, but it should be real soon now. (It's been in experimental for a while.) This version should be compatible with the 1.0.1 version. I don't expect anything to break moving from 1.0.1 to 1.0.2. The main reason I want to have 1.0.2 in jessie is to be able to support openssl for the lifetime of jessie. 1.0.1 will not be supported for the lifetime of jessie, while 1.0.2 should be supported long enough to even cover the TLS version of jessie if there is going to be an LTS version. Kurt -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101190834.ga10...@roeckx.be
Bug#767587: please prevent auto-removal of mysql-workbench from testing
On Sat, 1 Nov 2014 19:12:15 Julien Cristau wrote: A dependency on a virtual package with multiple providers and no real alternative is a serious bug in mysql-workbench. Please make the dependency mysql-client | virtual-mysql-client. What makes you think it is a serious bug? It would be serious in case of Build-Depends on virtual package without alternative but mysql-workbench (binary package) Depends on just virtual-mysql-client because there is no preference regarding which client package to use at run time... I've realised that virtual-mysql-client can be demoted to Recommends -- please advise if that change warrants an unblock in which case I will upload to unstable. Thank you. -- All the best, Dmitry Smirnov. --- Believing is easier than thinking. Hence so many more believers than thinkers. -- Bruce Calvert signature.asc Description: This is a digitally signed message part.
Bug#767663: openssl: completly drop SSLv3 support in jessie
Package: release.debian.org Severity: normal Hi, SSLv3 has been disabled in jessie already, at least for normal usage. But there is a way to explictly create a socket that only support SSLv3 and I would like to disable that too. This is done by the functions SSLv3_method(), SSLv3_server_method() and SSLv3_client_method(). There are 2 methods of actually doing this: - Make the function return NULL. This will then result in a failure later. - Remove the functions making things fail at for instance link time. I do not want to support SSLv3 in jessie. Kurt -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101192121.ga25...@roeckx.be
Re: Bug#767411: torque: should not be released with jessie
On Sat, Nov 01, 2014 at 02:30:02PM -0400, Michael Gilbert wrote: On Sat, Nov 1, 2014 at 11:46 AM, Salvatore Bonaccorso wrote: Given Dominique's reply on #767411, from my POV I think the best solution would be to remove torque completely for jessie (i.e. first drop support from openmpi to be able to remove the package and remaining reverse dependencies). 4 wheezy DSAs doesn't necessarily sound that horrible, so I don't think we're clearly at the point where torque should be considered unsupportable. Maybe the patch backports were an incredible amount of work? Well, but the 2.4 branch is already no longer unsupported upstream and we shouldn't knowingly introduce it into a release which will be supported for five more years. The package does clearly need to be orphaned, so someone can step up post-jessie to get the package in sync with upstream. As written by Dominique that's no possible for license reasons. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101195005.GA2660@pisco.westfalen.local
Bug#767587: please prevent auto-removal of mysql-workbench from testing
On Sun, Nov 2, 2014 at 06:22:52 +1100, Dmitry Smirnov wrote: On Sat, 1 Nov 2014 19:12:15 Julien Cristau wrote: A dependency on a virtual package with multiple providers and no real alternative is a serious bug in mysql-workbench. Please make the dependency mysql-client | virtual-mysql-client. What makes you think it is a serious bug? It would be serious in case of Build-Depends on virtual package without alternative but mysql-workbench (binary package) Depends on just virtual-mysql-client because there is no preference regarding which client package to use at run time... There *has* to be a preference (preferrably a common one across the archive). Otherwise the package manager gets to choose a random provider, which is the worst possible outcome. I've realised that virtual-mysql-client can be demoted to Recommends -- please advise if that change warrants an unblock in which case I will upload to unstable. Thank you. Not if it stays virtual-only. Cheers, Julien signature.asc Description: Digital signature
Bug#767674: unblock: haproxy/1.5.8-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! I would like to upload haproxy 1.5.8 in unstable. This would solve #767670. There are other fixes included in 1.5.7 and 1.5.8 as well as support to disable globally SSLv3. The default configuration file now does that. Find the debdiff attached. unblock haproxy/1.5.8-1 - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUVToyAAoJEJWkL+g1NSX5w0MP/1hBNJQKktASza+gjeMLQjZS YZQcLWIP6pgKIQxaI0XKQOo0UgK/ofy1eA3ouFhzGdhp15cocqT9jVXoq9na1WEv wP08c93iU1iBI4GyXH5/ka2+ND0l6X6N9c8CT7YIVA6fBa8gdooo80HpZTYmabtA VHXBbeKLu72OFUDuO6iblGTJ+cRzSv/klL2jAYAU9EC1DKJiTc6gjDkqO89xn5MU jQVGloEllYTXQ6VlgkDS56PgcScFn7i8xVRory8Ph4kaHQQmz6WYJJs6bOE8qyon /5w+Rj1Z0v9ydXXQZNULl60CU9qVh2iA9RiN8vbjKoTO+Ri7kgIQNSR64LKsdv2g 2efYXTJO2bwfYpxIq2y+J1rJvRzuZioBbvuIV0E0muCUEskh4CbVC++pFSpR8bUp bv3zpx/Mi7i/zVOBYtlIxkDQ+XlmA81gTIqjK8fp6ceeeK/YS+bZpv4A+xQT2avL aqdK8nnKCvbn/tSggEBb1PmHCbwHrX0XqJCWcbBFvZWFUii2X9TNsFbfiPc4J8+X ZqfuR7zuXew25x0wbbcBR7FVnOlvAM+ozN3LBJL68WMnB+jz3MtGg/M8kTXK8hon UuGnWnh2ttY1Imw2DRDrzeFXL5sF/jyBcZ+rXN/ei5kuslPRnle++nKrGTbayjPI zOVtJ5S9tLmWB42MOk/Q =3GWB -END PGP SIGNATURE- CHANGELOG | 15 README | 4 +- VERDATE| 2 +- VERSION| 2 +- debian/changelog | 21 ++ debian/haproxy.cfg | 1 + doc/configuration.txt | 91 --- examples/haproxy.spec | 8 +- include/types/global.h | 2 + src/buffer.c | 5 ++ src/dumpstats.c| 3 + src/proto_http.c | 5 +- src/proto_tcp.c| 25 +-- src/regex.c| 2 +- src/ssl_sock.c | 195 - 15 files changed, 338 insertions(+), 43 deletions(-) diff --git a/CHANGELOG b/CHANGELOG index 418dada3727f..5c45b7e44565 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,6 +1,21 @@ ChangeLog : === +2014/10/31 : 1.5.8 +- BUG/MAJOR: buffer: check the space left is enough or not when input data in a buffer is wrapped +- BUG/BUILD: revert accidental change in the makefile from latest SSL fix + +2014/10/30 : 1.5.7 +- BUG/MEDIUM: regex: fix pcre_study error handling +- BUG/MINOR: log: fix request flags when keep-alive is enabled +- MINOR: ssl: add fetchs 'ssl_c_der' and 'ssl_f_der' to return DER formatted certs +- MINOR: ssl: add statement to force some ssl options in global. +- BUG/MINOR: ssl: correctly initialize ssl ctx for invalid certificates +- BUG/MEDIUM: http: don't dump debug headers on MSG_ERROR +- BUG/MAJOR: cli: explicitly call cli_release_handler() upon error +- BUG/MEDIUM: tcp: fix outgoing polling based on proxy protocol +- BUG/MEDIUM: tcp: don't use SO_ORIGINAL_DST on non-AF_INET sockets + 2014/10/18 : 1.5.6 - BUG/MEDIUM: systemd: set KillMode to 'mixed' - MINOR: systemd: Check configuration before start diff --git a/README b/README index d111b4344087..2dd8e832ef62 100644 --- a/README +++ b/README @@ -1,9 +1,9 @@ -- HAProxy how-to -- - version 1.5.6 + version 1.5.8 willy tarreau - 2014/10/18 + 2014/10/31 1) How to build it diff --git a/VERDATE b/VERDATE index 4fa775a2bb6f..3953fe55fa40 100644 --- a/VERDATE +++ b/VERDATE @@ -1,2 +1,2 @@ $Format:%ci$ -2014/10/18 +2014/10/31 diff --git a/VERSION b/VERSION index eac1e0ada6d8..1cc9c180e266 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -1.5.6 +1.5.8 diff --git a/debian/changelog b/debian/changelog index 7e7bbb4de908..ede628a86187 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,24 @@ +haproxy (1.5.8-1) unstable; urgency=medium + + * New upstream stable release including the following fixes: + + + BUG/MAJOR: buffer: check the space left is enough or not when input + data in a buffer is wrapped + + BUG/MINOR: ssl: correctly initialize ssl ctx for invalid certificates + + BUG/MEDIUM: tcp: don't use SO_ORIGINAL_DST on non-AF_INET sockets + + BUG/MEDIUM: regex: fix pcre_study error handling + + BUG/MEDIUM: tcp: fix outgoing polling based on proxy protocol + + BUG/MINOR: log: fix request flags when keep-alive is enabled + + BUG/MAJOR: cli: explicitly call cli_release_handler() upon error + + BUG/MEDIUM: http: don't dump debug headers on
Bug#767587: please prevent auto-removal of mysql-workbench from testing
On Sat, 1 Nov 2014 20:49:39 Julien Cristau wrote: There *has* to be a preference (preferrably a common one across the archive). Otherwise the package manager gets to choose a random provider, which is the worst possible outcome. I do not understand why there has to be a preference. I understand behaviour of package manager and I've deliberately chosen not to have a preference. I do not see any benefits of having prefered client package in this case. Why do you insist that virtual-only dependency is wrong? It is hardly a worst possible outcome when all alternatives are equally suitable. I've realised that virtual-mysql-client can be demoted to Recommends -- please advise if that change warrants an unblock in which case I will upload to unstable. Thank you. Not if it stays virtual-only. Would you be satisfied if I add an alternative as follows? virtual-mysql-client | mysql-client Thanks. -- All the best, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part.
Bug#767587: please prevent auto-removal of mysql-workbench from testing
On Sun, Nov 2, 2014 at 07:01:35 +1100, Dmitry Smirnov wrote: On Sat, 1 Nov 2014 20:49:39 Julien Cristau wrote: There *has* to be a preference (preferrably a common one across the archive). Otherwise the package manager gets to choose a random provider, which is the worst possible outcome. I do not understand why there has to be a preference. I understand behaviour of package manager and I've deliberately chosen not to have a preference. I do not see any benefits of having prefered client package in this case. Why do you insist that virtual-only dependency is wrong? It is hardly a worst possible outcome when all alternatives are equally suitable. But they're clearly not. The default mysql client is the mysql-client package. Why do you insist that it isn't? I've realised that virtual-mysql-client can be demoted to Recommends -- please advise if that change warrants an unblock in which case I will upload to unstable. Thank you. Not if it stays virtual-only. Would you be satisfied if I add an alternative as follows? virtual-mysql-client | mysql-client Absolutely not. Cheers, Julien signature.asc Description: Digital signature
Bug#767674: unblock: haproxy/1.5.8-1
Control: tag -1 moreinfo Hi, On Sat, Nov 01, 2014 at 08:53:22PM +0100, Vincent Bernat wrote: I would like to upload haproxy 1.5.8 in unstable. This would solve #767670. There are other fixes included in 1.5.7 and 1.5.8 as well as support to disable globally SSLv3. The default configuration file now does that. Ok, but I can't unblock it until you've uploaded it. Please ping this bug when that's happened. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101201908.gb3...@lupin.home.powdarrmonkey.net
Processed: Re: Bug#767674: unblock: haproxy/1.5.8-1
Processing control commands: tag -1 moreinfo Bug #767674 [release.debian.org] unblock: haproxy/1.5.8-1 Added tag(s) moreinfo. -- 767674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b767674.141487315815775.transcr...@bugs.debian.org
Bug#767693: unblock: hwloc/1.10.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock unblock hwloc/1.10.0-3 Hello, I would like to apply the attached to hwloc, to fix Bug#767687: the hwloc package was not depending on at least the same version of libhwloc5, and thus not working. Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash diff --git a/debian/changelog b/debian/changelog index dafa1de..8dc4c5d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +hwloc (1.10.0-3) UNRELEASED; urgency=medium + + * Make packages depend on at least the same version of libhwloc5. +Closes: #767687. + + -- Samuel Thibault sthiba...@debian.org Sat, 01 Nov 2014 22:00:53 +0100 + hwloc (1.10.0-2) unstable; urgency=medium * control: diff --git a/debian/rules b/debian/rules index 1b36d0e..1052c18 100755 --- a/debian/rules +++ b/debian/rules @@ -94,7 +94,7 @@ binary-arch: install dh_strip dh_compress dh_fixperms - dh_makeshlibs + dh_makeshlibs -V dh_installdeb dh_shlibdeps dh_gencontrol
Bug#767587: please prevent auto-removal of mysql-workbench from testing
On Sat, 1 Nov 2014 21:08:56 Julien Cristau wrote: It is hardly a worst possible outcome when all alternatives are equally suitable. But they're clearly not. Let's distinguish generic statement from the particular case please. From mysql-workbench prospective there might be no difference in which client package to use. Let's consider hypothetical example: M-W uses `mysql` command line client only to check DB connectivity (in fact it is not how M-W really checks connectivity). All packages providing virtual-mysql-client have `mysql` executable taking exactly the same command line options and capable to connect to any server. Why prefer a particular client? Here you're failing to answer my questions... The default mysql client is the mysql-client package. Why do you insist that it isn't? I've never claimed otherwise. I merely see little reason to prefer default client. But I would agree if you'd say that it would be a good idea to recommend mysql-client as first alternative archive-wide to ensure that it is always a default client. However it would hardly explain why you consider lack of such alternative as serious bug. I've realised that virtual-mysql-client can be demoted to Recommends -- please advise if that change warrants an unblock in which case I will upload to unstable. Thank you. Not if it stays virtual-only. C'mon, why does it matter in Recommends as much as you say it matters in Depends? I'm OK to upload M-W to unstable with Recommends: mysql-client | virtual-mysql-client instead of Depends: virtual-mysql-client I'm willing to comply because you insist, not because I'm convinced. IMHO this issue is not worth arguing and I recognise (however little) benefit from defaulting to default mysql-client client even if it makes no functional difference for recommending package. If you believe it's better -- that is enough for me. Please advise if I shall proceed with upload. Thanks. -- Cheers, Dmitry Smirnov. --- Science embraces facts and debates opinion; religion embraces opinion and debates the facts. -- Tom Heehler, The Well-Spoken Thesaurus. signature.asc Description: This is a digitally signed message part.
Bug#767580: unblock: python-virtualenv/1.11.6+ds-1
Hi Niels (2014.11.01_11:15:23_+0200) Looks reasonable, please upload it and let me know once it has been accepted. Uploaded (with a minor tweak to debian/watch), and the upload has been accepted. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141101214135.gp3...@bach.rivera.co.za
Bug#767694: unblock: gnustep-gui/0.24.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock (or reduce age-days) package gnustep-gui, it fixes RC
bugs #754825 and #755823. (It's being held by gnustep-base/1.24.7-1
which I believe is due to migrate without your intervention on
November 5th.)
Debdiff attached.
unblock gnustep-gui/0.24.0-3
diff --git a/debian/changelog b/debian/changelog
index 85ccf2b..3626063 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+gnustep-gui (0.24.0-3) unstable; urgency=medium
+
+ * debian/patches/xib-loading.patch: New; fixes a crash with XIB
+decoding/loading (Closes: #754825).
+ * debian/patches/gorm-loading.patch: New; fixes a crash in Gorm
+loading (Closes: #755823).
+ * debian/patches/series: Update.
+ * debian/control.m4 (Standards-Version): Bump to 3.9.6; no changes
+needed.
+ * debian/control: Regenerate.
+
+ -- Yavor Doganov ya...@gnu.org Tue, 28 Oct 2014 09:39:18 +0200
+
gnustep-gui (0.24.0-2) unstable; urgency=medium
* Upload to unstable.
diff --git a/debian/control b/debian/control
index 0fe9e0d..2398c52 100644
--- a/debian/control
+++ b/debian/control
@@ -4,7 +4,7 @@ Priority: optional
Maintainer: Debian GNUstep maintainers pkg-gnustep-maintain...@lists.alioth.debian.org
Uploaders: Gürkan Sengün gur...@phys.ethz.ch,
Yavor Doganov ya...@gnu.org
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
Build-Depends: debhelper (= 9),
m4,
libgnustep-base-dev (= 1.24.6),
diff --git a/debian/control.m4 b/debian/control.m4
index 4f80e2d..5b33272 100644
--- a/debian/control.m4
+++ b/debian/control.m4
@@ -4,7 +4,7 @@ Priority: optional
Maintainer: Debian GNUstep maintainers pkg-gnustep-maintain...@lists.alioth.debian.org
Uploaders: Gürkan Sengün gur...@phys.ethz.ch,
Yavor Doganov ya...@gnu.org
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
Build-Depends: debhelper (= 9),
m4,
libgnustep-base-dev (= V_BASE),
diff --git a/debian/patches/gorm-loading.patch b/debian/patches/gorm-loading.patch
new file mode 100644
index 000..82530ab
--- /dev/null
+++ b/debian/patches/gorm-loading.patch
@@ -0,0 +1,18 @@
+Description: Fix crash in Gorm loading.
+Bug: http://savannah.gnu.org/bugs/index.php?42782
+Bug-Debian: http://bugs.debian.org/755823
+Origin: upstream, commit: r38005
+Last-Update: 2014-10-28
+---
+
+--- gnustep-gui.orig/Source/GSGormLoading.m
gnustep-gui/Source/GSGormLoading.m
+@@ -892,7 +892,7 @@
+ // decode the defer flag...
+ [coder decodeValueOfObjCType: @encode(BOOL) at: _deferFlag];
+ _autoPositionMask = GSWindowAutoPositionNone;
+- _screenRect = [[_object screen] frame];
++ _screenRect = [[obj screen] frame];
+ }
+
+ // FIXME: The designated initializer logic for NSWindow is in the initWithCoder: method of
diff --git a/debian/patches/series b/debian/patches/series
index 56c0e09..b5eb35d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,3 @@
+gorm-loading.patch
+xib-loading.patch
info-direntry.patch
diff --git a/debian/patches/xib-loading.patch b/debian/patches/xib-loading.patch
new file mode 100644
index 000..1caf686
--- /dev/null
+++ b/debian/patches/xib-loading.patch
@@ -0,0 +1,93 @@
+Description: Fix crash in XIB loading.
+Bug: http://savannah.gnu.org/bugs/index.php?42717
+Bug-Debian: http://bugs.debian.org/754825
+Origin: upstream, commit: r38003
+Last-Update: 2014-07-24
+---
+
+--- gnustep-gui-0.24.0.orig/Source/NSBox.m
gnustep-gui-0.24.0/Source/NSBox.m
+@@ -572,6 +572,10 @@
+
+ [self setBorderType: borderType];
+ }
++ else
++{
++ _border_type = NSGrooveBorder;
++}
+ if ([aDecoder containsValueForKey: @NSTitlePosition])
+ {
+ NSTitlePosition titlePosition = [aDecoder decodeIntForKey:
+@@ -579,6 +583,10 @@
+
+ [self setTitlePosition: titlePosition];
+ }
++ else
++{
++ _title_position = NSAtTop;
++}
+ if ([aDecoder containsValueForKey: @NSTransparent])
+ {
+ // On Apple this is always NO, we keep it for old GNUstep archives
+@@ -598,12 +606,27 @@
+
+ ASSIGN(_cell, titleCell);
+ }
++ else
++{
++ _cell = [[NSCell alloc] initTextCell: @Title];
++ [_cell setAlignment: NSCenterTextAlignment];
++ [_cell setBordered: NO];
++ [_cell setEditable: NO];
++ [self setTitleFont: [NSFont systemFontOfSize:
++[NSFont smallSystemFontSize]]];
++}
+ if ([aDecoder containsValueForKey: @NSContentView])
+ {
+ NSView *contentView = [aDecoder decodeObjectForKey: @NSContentView];
+
+ [self setContentView: contentView];
+ }
++ else
++{
++ NSView *cv = [NSView new];
++ [self setContentView: cv];
++ RELEASE(cv);
++}
+ }
+
Re: libotr transition started by mistake :-/
On 2014-11-01 16:50, intrigeri wrote: As I recall, we generally prefer libraries do not have unnecessary strictly equal runtime version checks, since they tend to be wrong. Proper use of shlibs (or symbols) and SONAME bumping (with package renaming) makes such checks redundant (for Debian maintained reverse dependencies). Actually, the way I understand the code, what we have here is not a strictly equal runtime version check, but rather runtime version greater or equal to the build-time one, which is better in that it doesn't require binNMUs. For reference, should a check would still be wrong with symbols files. If libotr had been using symbols files, a reverse dependency could build against 4.1.0, but only have a dependency on = 4.0.0 (provided that they did not use the otrl_mem_differ symbol). Combine that with the case where libotr/4.0.0 is in testing, libotr/4.1.0 is stalled in sid and the reverse dependency migrates to testing = reverse dependency is now broken in testing due to no fault of its own. It would now require binNMU in testing simply to get rebuilt with a built-against 4.0.0 marker. ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5455586d.7050...@thykier.net
Bug#767695: unblock: smcroute/2.0.0-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package smcroute The package in smcroute is RC buggy (#766915: smcroute does not start). adsb already added an age-days 2 smcroute/2.0.0-3 hint on 2014-10-30, but I just uploaded a fix for the autopkgtests, so at least the version number in the hint needs to be updated. This is why I am contacting you. The debdiff since the already hinted version is: --- 8 - diff -Nru smcroute-2.0.0/debian/changelog smcroute-2.0.0/debian/changelog --- smcroute-2.0.0/debian/changelog 2014-10-30 16:11:16.0 +0100 +++ smcroute-2.0.0/debian/changelog 2014-11-01 21:00:11.0 +0100 @@ -1,3 +1,11 @@ +smcroute (2.0.0-4) unstable; urgency=medium + + * Fix autopkgtest: Add missing smcroute test dependency, missing comma, and +missing allow-stderr (Closes: #767592). Thanks to Martin Pitt +martin.p...@ubuntu.com for providing the patch. + + -- Micha Lenk mi...@debian.org Sat, 01 Nov 2014 20:55:08 +0100 + smcroute (2.0.0-3) unstable; urgency=medium * Add Testsuite: autopkgtest to debian/control, on behalf of a traveling diff -Nru smcroute-2.0.0/debian/tests/control smcroute-2.0.0/debian/tests/control --- smcroute-2.0.0/debian/tests/control 2014-10-30 00:30:58.0 +0100 +++ smcroute-2.0.0/debian/tests/control 2014-11-01 21:00:11.0 +0100 @@ -1,3 +1,3 @@ Tests: daemon-init-scripts mr-cache-ipv4 mr-cache-ipv6 -Restrictions: needs-root isolation-machine -Depends: libipc-system-simple-perl procps +Restrictions: needs-root isolation-machine allow-stderr +Depends: @, libipc-system-simple-perl, procps --- 8 - The debdiff since the version 2.0.0-1 that is available in testing is attached. If you agree, please pick from the following what ever hint you find most appropriate (I would take the age-days hint): unblock smcroute/2.0.0-4 age-days 2 smcroute/2.0.0-4 Thanks in advance, Micha diff -Nru smcroute-2.0.0/debian/changelog smcroute-2.0.0/debian/changelog --- smcroute-2.0.0/debian/changelog 2014-10-03 10:56:12.0 +0200 +++ smcroute-2.0.0/debian/changelog 2014-11-01 21:00:11.0 +0100 @@ -1,3 +1,30 @@ +smcroute (2.0.0-4) unstable; urgency=medium + + * Fix autopkgtest: Add missing smcroute test dependency, missing comma, and +missing allow-stderr (Closes: #767592). Thanks to Martin Pitt +martin.p...@ubuntu.com for providing the patch. + + -- Micha Lenk mi...@debian.org Sat, 01 Nov 2014 20:55:08 +0100 + +smcroute (2.0.0-3) unstable; urgency=medium + + * Add Testsuite: autopkgtest to debian/control, on behalf of a traveling +Micha + + -- Joachim Breitner nome...@debian.org Thu, 30 Oct 2014 16:11:03 +0100 + +smcroute (2.0.0-2) unstable; urgency=medium + + * Delete debian/smcroute.dirs because package builds also without it. + * Install binaries to /usr/sbin to make init script working again +(Closes: #766915). + * Add patch 0001-Fix-issue-10-Loop-forever-on-command-if-daemon-not-r.patch +to fix hanging init script on stop in case the daemon isn't running. + * Add some Autopkgtests covering daemon start stop via System V init scripts, +addition and removal of static multicast routes. + + -- Micha Lenk mi...@debian.org Thu, 30 Oct 2014 00:27:59 +0100 + smcroute (2.0.0-1) unstable; urgency=low * New upstream version, does build again on FreeBSD (closes: #763381). diff -Nru smcroute-2.0.0/debian/control smcroute-2.0.0/debian/control --- smcroute-2.0.0/debian/control 2014-10-01 22:44:34.0 +0200 +++ smcroute-2.0.0/debian/control 2014-11-01 21:00:11.0 +0100 @@ -7,6 +7,7 @@ Homepage: http://troglobit.com/smcroute.html Vcs-Browser: http://source.lenk.info/git/pkg-smcroute.git Vcs-Git: git://source.lenk.info/git/pkg-smcroute.git +Testsuite: autopkgtest Package: smcroute Architecture: any diff -Nru smcroute-2.0.0/debian/patches/0001-Fix-issue-10-Loop-forever-on-command-if-daemon-not-r.patch smcroute-2.0.0/debian/patches/0001-Fix-issue-10-Loop-forever-on-command-if-daemon-not-r.patch --- smcroute-2.0.0/debian/patches/0001-Fix-issue-10-Loop-forever-on-command-if-daemon-not-r.patch 1970-01-01 01:00:00.0 +0100 +++ smcroute-2.0.0/debian/patches/0001-Fix-issue-10-Loop-forever-on-command-if-daemon-not-r.patch 2014-11-01 21:00:11.0 +0100 @@ -0,0 +1,31 @@ +From: Joachim Nilsson troglo...@gmail.com +Date: Mon, 27 Oct 2014 01:32:54 +0100 +Subject: [PATCH] Fix issue #10: Loop forever on command if daemon not running. +Origin: https://github.com/troglobit/smcroute/commit/d6280e64b27d5a4bd7f37dac36b455f4ae5f9ab3 +Bug: https://github.com/troglobit/smcroute/issues/10 + +Signed-off-by: Joachim Nilsson troglo...@gmail.com +--- + smcroute.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/smcroute.c b/smcroute.c +index 1aeb133..7bd3c72 100644 +--- a/smcroute.c b/smcroute.c +@@ -573,10 +573,11 @@ int main(int
Bug#767580: marked as done (unblock: python-virtualenv/1.11.6+ds-1)
Your message dated Sat, 01 Nov 2014 22:52:55 +0100 with message-id 54555637.6040...@thykier.net and subject line Re: Bug#767580: unblock: python-virtualenv/1.11.6+ds-1 has caused the Debian Bug report #767580, regarding unblock: python-virtualenv/1.11.6+ds-1 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.) -- 767580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock This is a pre-emptive unblock request, 1.11.6+ds-1 isn't in unstable. Either it needs an unblock, or an extra-short migration. RC bug fix, removing (unused) convenience libraries that weren't tracked in debian/copyright. Patch attached. unblock python-virtualenv/1.11.6+ds-1 SR Index: debian/changelog === --- debian/changelog(revision 31340) +++ debian/changelog(working copy) @@ -1,3 +1,16 @@ +python-virtualenv (1.11.6+ds-1) UNRELEASED; urgency=medium + + [ Daniele Tricoli ] + * Repack source package to remove embedded copy of python-pip-whl and +python-setuptools-whl (Closes: #751233) + * debian/rules: +- Don't override dh_auto_configure to remove embedded wheels since + they are removed from source package + * debian/watch: +- Add dversionmangle option + + -- Stefano Rivera stefa...@debian.org Fri, 31 Oct 2014 17:59:34 -0700 + python-virtualenv (1.11.6-2) unstable; urgency=medium * d/patches/use-wheels.patch: Ignore EEXIST when creating the Index: debian/copyright === --- debian/copyright(revision 31340) +++ debian/copyright(working copy) @@ -1,6 +1,9 @@ Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: virtualenv Source: https://github.com/pypa/virtualenv + The pristine upstream source contains convenience copies of python-pip-whl and + python-setuptools-whl. +Files-Excluded: virtualenv_support/*.whl Files: * Copyright: 2007, Ian Bicking and Contributors, @@ -16,15 +19,7 @@ 2012 Barry Warsaw ba...@python.org License: Expat -Files: virtualenv_support/pip-* -Copyright: 2008-2013 The pip developers License: Expat - -Files: virtualenv_support/setuptools-* -Copyright: Phillip J. Eby -License: PSF-2 or Zope-2.1 - -License: Expat Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including @@ -43,94 +38,3 @@ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. - -License: PSF-2 - 1. This LICENSE AGREEMENT is between the Python Software Foundation - (PSF), and the Individual or Organization (Licensee) accessing and - otherwise using Python 2.3 software in source or binary form and its - associated documentation. - . - 2. Subject to the terms and conditions of this License Agreement, PSF - hereby grants Licensee a nonexclusive, royalty-free, world-wide - license to reproduce, analyze, test, perform and/or display publicly, - prepare derivative works, distribute, and otherwise use Python 2.3 - alone or in any derivative version, provided, however, that PSF's - License Agreement and PSF's notice of copyright, i.e., Copyright (c) - 2001, 2002 Python Software Foundation; All Rights Reserved are - retained in Python 2.3 alone or in any derivative version prepared by - Licensee. - . - 3. In the event Licensee prepares a derivative work that is based on - or incorporates Python 2.3 or any part thereof, and wants to make - the derivative work available to others as provided herein, then - Licensee hereby agrees to include in any such work a brief summary of - the changes made to Python 2.3. - . - 4. PSF is making Python 2.3 available to Licensee on an AS IS - basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR - IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND - DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS - FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 2.3 WILL NOT - INFRINGE ANY THIRD PARTY RIGHTS. - . - 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON - 2.3 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS - A RESULT OF MODIFYING, DISTRIBUTING, OR
Bug#767700: unblock: pdns/3.4.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, upstream asked me nicely to update pdns to their just released bug-fix release (3.4.0 - 3.4.1). 3.4.1 has, depending on how you count, two or three bug fixes. From upstreams changelog: - honor SOA-EDIT while considering empty IXFR fallback, This fixes slaving of signed zones to IXFR-aware slaves like NSD or BIND. - Use transaction for pdnssec increase-serial (fixes partially modified zones after a failed increase-serial) - Don't empty ordername during pdnssec increase-serial (fixes broken DNSSEC zones after increase-serial) Also included: - upstream applied a patch that I had previously included in 3.4.0-2. - security status polling feature I also noticed that the shipped pdns.conf was quite out of date, so I resynced that (my oversight for 3.4.0). I'm attaching a regular debdiff between 3.4.0-2 (in testing) and 3.4.1-1, plus a diff between 3.4.0-2 with the previously mentioned patch already applied (reduces the diff by a bit). Please consider unblocking pdns 3.4.1-1 (it's not yet built everywhere): unblock pdns/3.4.1-1 Thanks, Christian diff -Nru pdns-3.4.0/build-scripts/redhat/pdns-server-test.spec pdns-3.4.1/build-scripts/redhat/pdns-server-test.spec --- pdns-3.4.0/build-scripts/redhat/pdns-server-test.spec 2014-09-30 11:23:37.0 +0200 +++ pdns-3.4.1/build-scripts/redhat/pdns-server-test.spec 2014-10-30 11:18:22.0 +0100 @@ -9,7 +9,7 @@ Epoch: 0 License:GPL Group: System/Servers -Source: http://downloads.powerdns.com/releases/pdns-3.4.0.tar.bz2 +Source: http://downloads.powerdns.com/releases/pdns-3.4.1.tar.bz2 BuildRequires: autoconf automake BuildRequires: gcc gcc-c++ @@ -30,7 +30,7 @@ PowerDNS testbuild %prep -%setup -q -n pdns-3.4.0 +%setup -q -n pdns-3.4.1 %build %configure \ diff -Nru pdns-3.4.0/configure pdns-3.4.1/configure --- pdns-3.4.0/configure 2014-09-30 11:23:48.0 +0200 +++ pdns-3.4.1/configure 2014-10-30 11:18:31.0 +0100 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.69 for pdns 3.4.0. +# Generated by GNU Autoconf 2.69 for pdns 3.4.1. # # # Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc. @@ -587,8 +587,8 @@ # Identity of this package. PACKAGE_NAME='pdns' PACKAGE_TARNAME='pdns' -PACKAGE_VERSION='3.4.0' -PACKAGE_STRING='pdns 3.4.0' +PACKAGE_VERSION='3.4.1' +PACKAGE_STRING='pdns 3.4.1' PACKAGE_BUGREPORT='' PACKAGE_URL='' @@ -1471,7 +1471,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat _ACEOF -\`configure' configures pdns 3.4.0 to adapt to many kinds of systems. +\`configure' configures pdns 3.4.1 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1541,7 +1541,7 @@ if test -n $ac_init_help; then case $ac_init_help in - short | recursive ) echo Configuration of pdns 3.4.0:;; + short | recursive ) echo Configuration of pdns 3.4.1:;; esac cat \_ACEOF @@ -1737,7 +1737,7 @@ test -n $ac_init_help exit $ac_status if $ac_init_version; then cat \_ACEOF -pdns configure 3.4.0 +pdns configure 3.4.1 generated by GNU Autoconf 2.69 Copyright (C) 2012 Free Software Foundation, Inc. @@ -2344,7 +2344,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by pdns $as_me 3.4.0, which was +It was created by pdns $as_me 3.4.1, which was generated by GNU Autoconf 2.69. Invocation command line was $ $0 $@ @@ -3167,7 +3167,7 @@ # Define the identity of the package. PACKAGE='pdns' - VERSION='3.4.0' + VERSION='3.4.1' cat confdefs.h _ACEOF @@ -21020,7 +21020,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log= -This file was extended by pdns $as_me 3.4.0, which was +This file was extended by pdns $as_me 3.4.1, which was generated by GNU Autoconf 2.69. Invocation command line was CONFIG_FILES= $CONFIG_FILES @@ -21086,7 +21086,7 @@ cat $CONFIG_STATUS _ACEOF || ac_write_fail=1 ac_cs_config=`$as_echo $ac_configure_args | sed 's/^ //; s/[\\\`\$]//g'` ac_cs_version=\\ -pdns config.status 3.4.0 +pdns config.status 3.4.1 configured by $0, generated by GNU Autoconf 2.69, with options \\\$ac_cs_config\\ diff -Nru pdns-3.4.0/configure.ac pdns-3.4.1/configure.ac --- pdns-3.4.0/configure.ac 2014-09-30 11:23:37.0 +0200 +++ pdns-3.4.1/configure.ac 2014-10-30 11:18:22.0 +0100 @@ -1,7 +1,7 @@ AC_PREREQ([2.61]) dnl The following lines may be patched by set-version-auth. -AC_INIT([pdns], [3.4.0]) +AC_INIT([pdns], [3.4.1]) AC_SUBST([DIST_HOST], [jenk...@autotest.powerdns.com]) dnl End patch area. diff -Nru
Bug#767705: unblock: inetutils/2:1.9.2.39.3a460-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi! Please unblock or reduce age-days for package inetutils so that it can migrate before the freeze, it fixes a security issue, an instance of CVE-2014-3634. unblock inetutils/2:1.9.2.39.3a460-3 Thanks, Guillem -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141102001615.ga10...@gaara.hadrons.org
Bug#767706: unblock: debsig-verify/0.13
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock or reduce age-days for package debsig-verify so that it can migrate before the freeze. It fixes the code so that it now checks for errors returned by relevant library and system calls, either directly or by switching to the more tested code from libdpkg. This is particularly important given that debsig-verify is one of the pieces in the packaging toolchain that might be exposed to untrusted binary .deb packages. In addition this version adds a new functional testsuite, which is run during the build. unblock debsig-verify/0.13 Thanks, Guillem -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141102002313.ga30...@gaara.hadrons.org
Bug#767674: unblock: haproxy/1.5.8-1
❦ 1 novembre 2014 20:19 GMT, Jonathan Wiltshire j...@debian.org : I would like to upload haproxy 1.5.8 in unstable. This would solve #767670. There are other fixes included in 1.5.7 and 1.5.8 as well as support to disable globally SSLv3. The default configuration file now does that. Ok, but I can't unblock it until you've uploaded it. Please ping this bug when that's happened. Hi! It is now uploaded in unstable. Thanks! -- Keep it right when you make it faster. - The Elements of Programming Style (Kernighan Plauger) signature.asc Description: PGP signature
Bug#767708: unblock: lcd4linux/0.11.0~svn1200-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi Release Team, Please unblock or reduce age-day for package lcd4linux. This upload fixes a severity important bug which affects both upgrades and new installs of this package. Debdiff attached (please ignore lcd4conf.conf file which was inadvertently left in debian directory when uploading; can reupload with file removed if required). unblock lcd4linux/0.11.0~svn1200-3 Thanks, Jon diff -Nru --exclude '*lcd4conf.conf' lcd4linux-0.11.0~svn1200/debian/changelog lcd4linux-0.11.0~svn1200/debian/changelog --- lcd4linux-0.11.0~svn1200/debian/changelog 2014-10-09 11:38:13.0 +0100 +++ lcd4linux-0.11.0~svn1200/debian/changelog 2014-11-01 20:16:22.0 + @@ -1,3 +1,12 @@ +lcd4linux (0.11.0~svn1200-3) unstable; urgency=medium + + * ACK libtool-bin NMU +- Thanks to Matthias Klose! + * Install modified lcd4linux.sample.conf as dummy lcd4linux.conf file to +satisfy startup checks (Closes: 758057) + + -- Jonathan McCrohan jmccro...@gmail.com Sat, 01 Nov 2014 20:16:22 + + lcd4linux (0.11.0~svn1200-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru --exclude '*lcd4conf.conf' lcd4linux-0.11.0~svn1200/debian/rules lcd4linux-0.11.0~svn1200/debian/rules --- lcd4linux-0.11.0~svn1200/debian/rules 2014-04-14 23:57:07.0 +0100 +++ lcd4linux-0.11.0~svn1200/debian/rules 2014-11-01 20:15:38.0 + @@ -20,6 +20,22 @@ override_dh_installman: dh_installman debian/lcd4linux.8 +override_dh_install: + dh_install + sed -e 1c lcd4linux debian sample config \ + -e 2d \ + -e 3a This is a dummy config file using the NULL driver. \ + -e 3a Please amend this file as required by your specific LCD device. \ + -e s@#Display 'NULL'@Display 'NULL'@ \ + -e s@Display 'ACool'@#Display 'ACool'@ \ + -e s@Layout 'TestLayer'@#Layout 'TestLayer'@ \ + -e s@#Layout 'Default'@Layout 'Default'@ \ + lcd4linux.conf.sample debian/lcd4linux/etc/lcd4linux.conf + chmod 600 debian/lcd4linux/etc/lcd4linux.conf + +override_dh_fixperms: + dh_fixperms -X debian/lcd4linux/etc/lcd4linux.conf + %: dh $@ --with autotools_dev --with systemd
Bug#767714: nmu: lhapdf_5.9.1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu lhapdf_5.9.1-3 . arm64 . -m Rebuild against octave 3.8 The lhapdf package on arm64 was actually built against octave 3.8, unfortunately it's not installable because octave declares Breaks: octave-lhapdf (= 5.9.1-3). This binnmu will bring the binary version of the package on arm64 into line with other architectures and hence avoid the breaks. I did consider trying to explain this in the binnmu changelog reason but I decided it was probablly less confusing to users just to use the same binnmu changelog reason as on the other architectures. -- System Information: Debian Release: 6.0.3 APT prefers oldstable-proposed-updates APT policy: (500, 'oldstable-proposed-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141102021958.26742.99114.reportbug@localhost
Bug#767718: unblock: clamtk/5.11-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package clamtk
This new upstream version includes one important bug fix to properly escape
the filename used in the right-click menu with Nautilus. It also provides
improved documentation and updated translations.
The simplified signature updating UI and Update Assistant are improvements it
would be nice to get in. I particularly like that the code base gets smaller.
Less to go wrong.
I have the package ready to upload, but I'd like a pre-review so I don't block
up unstable with this if it's not appropriate for Jessie.
unblock clamtk/5.11-1
diff -Nru clamtk-5.10/CHANGES clamtk-5.11/CHANGES
--- clamtk-5.10/CHANGES 2014-10-02 17:38:54.0 -0400
+++ clamtk-5.11/CHANGES 2014-10-31 05:54:14.0 -0400
@@ -1,5 +1,16 @@
CHANGELOG for ClamTk:
+5.11 - Oct 31 2014
+-
+* Fix for clamtk.py to right-click scan files with
+ special characters
+* Minor improvements to the Update dialog; the new benefit
+ is one-click signature updating vice two
+* Minor updates to help documentation (PUAs)
+* Minor improvement in Update Assistant
+* Updated language files: German (de), Brazilian
+ Portuguese (pt_BR), Bulgarian (bg)
+
5.10 - Oct 2 2014
--
* Display total number of signatures properly. Thanks, Natalia!
@@ -190,17 +201,17 @@
4.44 - Dec 22 2012
--
* Update gvfs directory location, which moved from
- /home/$user/.gvfs to /run/user/$user/gvfs. This is
- standard now with Ubuntu 12.10 and Fedora 17
+ /home/$user/.gvfs to /run/user/$user/gvfs. This is
+ standard now with Ubuntu 12.10 and Fedora 17
* Add missing ignore-gvfs-mounts option to scheduled
- scans. Thanks, Matthew!
+ scans. Thanks, Matthew!
* Copy bytecode.cld when changing to manual updates.
* Updated Finnish (fi) language file. Thanks, Jiri!
4.43 - Dec 2 2012
--
* Begin using Keyword entry in .desktop file
- (Launchpad #1050803)
+ (Launchpad #1050803)
* Added Afrikaans (af) language file. Thanks, Dawid!
* Added Marathi (mr) language file. Thanks, Shashank!
* Updated Greek (el_GR) language file. Thanks, Sterios!
diff -Nru clamtk-5.10/clamtk.py clamtk-5.11/clamtk.py
--- clamtk-5.10/clamtk.py 2013-12-29 20:44:40.0 -0500
+++ clamtk-5.11/clamtk.py 2014-10-23 17:32:00.0 -0400
@@ -14,6 +14,7 @@
import os
import urllib
+import re
import locale
locale.setlocale(locale.LC_ALL, '')
@@ -27,6 +28,7 @@
def _open_scanner(self, file):
filename = urllib.unquote(file.get_uri()[7:])
+filename = re.escape(filename)
#os.chdir(filename)
os.system('clamtk %s ' % filename)
diff -Nru clamtk-5.10/debian/changelog clamtk-5.11/debian/changelog
--- clamtk-5.10/debian/changelog 2014-10-08 00:01:36.0 -0400
+++ clamtk-5.11/debian/changelog 2014-11-02 00:57:45.0 -0400
@@ -1,3 +1,9 @@
+clamtk (5.11-1) UNRELEASED; urgency=medium
+
+ * New upstream version
+
+ -- Scott Kitterman sc...@kitterman.com Sun, 02 Nov 2014 00:57:45 -0400
+
clamtk (5.10-1) unstable; urgency=medium
* Import new upstream version
diff -Nru clamtk-5.10/debian/.git-dpm clamtk-5.11/debian/.git-dpm
--- clamtk-5.10/debian/.git-dpm 2014-10-07 23:59:45.0 -0400
+++ clamtk-5.11/debian/.git-dpm 2014-11-02 00:57:45.0 -0400
@@ -1,8 +1,8 @@
# see git-dpm(1) from git-dpm package
-0282a3b6bf5d6453ac616b38e18e9fcc49202efa
-0282a3b6bf5d6453ac616b38e18e9fcc49202efa
-06a28307b5d2c7019084ff0470df8d6b819ca871
-06a28307b5d2c7019084ff0470df8d6b819ca871
-clamtk_5.10.orig.tar.gz
-19398c0b685954fb67fe9526b3667cdcca627f7d
-895308
+31399a3a6839f9867a7ef0aef73faaa7fd1643cc
+31399a3a6839f9867a7ef0aef73faaa7fd1643cc
+be123d01e20aac2974f78799bd5fe950855cdf5b
+be123d01e20aac2974f78799bd5fe950855cdf5b
+clamtk_5.11.orig.tar.gz
+150a079d81facda2246546fd7bbf8b22d0c15112
+894160
diff -Nru clamtk-5.10/debian/patches/0001-Add-Konqueror-Dolphin-service-menu-support-by-copyin.patch clamtk-5.11/debian/patches/0001-Add-Konqueror-Dolphin-service-menu-support-by-copyin.patch
--- clamtk-5.10/debian/patches/0001-Add-Konqueror-Dolphin-service-menu-support-by-copyin.patch 2014-10-07 23:59:45.0 -0400
+++ clamtk-5.11/debian/patches/0001-Add-Konqueror-Dolphin-service-menu-support-by-copyin.patch 2014-11-02 00:57:45.0 -0400
@@ -1,4 +1,4 @@
-From 0282a3b6bf5d6453ac616b38e18e9fcc49202efa Mon Sep 17 00:00:00 2001
+From 31399a3a6839f9867a7ef0aef73faaa7fd1643cc Mon Sep 17 00:00:00 2001
From: Scott Kitterman sc...@kitterman.com
Date: Sat, 30 Aug 2014 12:48:15 -0400
Subject: =?UTF-8?q?Add=20Konqueror/Dolphin=20service=20menu=20support=20by?=
diff -Nru clamtk-5.10/help/C/clamtk/pua-preferences.page clamtk-5.11/help/C/clamtk/pua-preferences.page
--- clamtk-5.10/help/C/clamtk/pua-preferences.page 2014-05-25
