Bug#865971: stable-pu: package tbdialout/1.7.2-2
On 27/06/17 08:54, Adam D. Barratt wrote: > On 2017-06-27 7:14, Daniel Pocock wrote: >> I'm planning a blog about the click-to-dial capabilities of various >> packages in stretch (Firefox, Thunderbird, Evolution) and I'd prefer to >> do that after this update becomes available to users. Can this be made >> available in stretch-updates or will it need to wait for the next point >> release? > > I'm struggling to see how a normal severity bug in a browser extension > qualifies for stable-updates. If I understand the policy correctly, stable-updates is suitable for data (rather than code) changes. This update changes one byte of configuration data and no code. I changed the severity of the bug to important because without the fix, every user who installs the package has to visit the preferences screen, but with the fix, most users can apt install the package and it just works immediately. > >> Do I need to specify stretch-updates as the distribution in >> the changelog? > > No. For one thing, that's not how stable-updates works, and even if you > did then the upload should end up in the pu-new queue anyway and then p-u. > OK, thanks. Please just let me know when you make a final decision about the upload and I'm happy to revise it again if necessary. Regards, Daniel
Bug#865971: stable-pu: package tbdialout/1.7.2-2
On 27/06/17 05:05, Cyril Brulebois wrote: > Daniel Pocock <dan...@pocock.pro> (2017-06-26): >> Thanks for the feedback, I've made those changes now too >> >> Regards, >> >> Daniel > >> diff -Nru tbdialout-1.7.2/debian/changelog tbdialout-1.7.2/debian/changelog >> --- tbdialout-1.7.2/debian/changelog 2014-05-02 18:58:02.0 +0200 >> +++ tbdialout-1.7.2/debian/changelog 2017-06-26 08:51:10.0 +0200 >> @@ -1,3 +1,12 @@ >> +tbdialout (1.7.2-1+deb9u1) stretch; urgency=medium >> + >> + * Include leading plus symbol with tel: URI scheme. (Closes: #865961) >> + * Remove Dm-Upload-Allowed. >> + * Add missing detalls to debian/copyright >> + * Update watch file. >> + >> + -- Daniel Pocock <dan...@pocock.pro> Mon, 26 Jun 2017 08:51:10 +0200 > > While the tel:/+ fix and copyright update look reasonable for stable, > I'm much less convinced by the DMUA/watch update in stable. DMUA isn't > much relevant since SRMs have the final say on what gets into stretch, > and packaging a new upstream release usually happens from unstable… > (And I'd assume tracker.debian.org and friends use metadata from > unstable and/or experimental.) > > I'll leave others a chance to comment on this, and I think it would be > best to wait a bit since the fix landed in unstable not so long ago. > Those changes were all on the unstable packaging branch in my repository. I didn't think they would have any adverse impact on stable so I just left them in place when making the build for stable. If you want me to remove those things please tell me and I will do so. I'm planning a blog about the click-to-dial capabilities of various packages in stretch (Firefox, Thunderbird, Evolution) and I'd prefer to do that after this update becomes available to users. Can this be made available in stretch-updates or will it need to wait for the next point release? Do I need to specify stretch-updates as the distribution in the changelog? Regards, Daniel signature.asc Description: OpenPGP digital signature
Bug#865971: stable-pu: package tbdialout/1.7.2-2
On 26/06/17 13:25, Adam D. Barratt wrote: > On 2017-06-26 12:11, Daniel Pocock wrote: >> Control: tags -1 - moreinfo >> >> On 26/06/17 11:31, Adam D. Barratt wrote: >> >>> >>> The debdiff is obviously not what you're proposing uploading to stable: >>> >>> +tbdialout (1.7.2-2) unstable; urgency=low >>> >>> Please can we have a debdiff of what you're actually proposing to >>> upload, as built and tested on stable? >>> >> >> >> Please find the revised debdiff attached > > Thanks. However, the changelog distribution should be "stretch", as > that's preferred over "stable", and the changelog appears not to mention > any of the changes you've made other than the "+". > Thanks for the feedback, I've made those changes now too Regards, Daniel diff -Nru tbdialout-1.7.2/debian/changelog tbdialout-1.7.2/debian/changelog --- tbdialout-1.7.2/debian/changelog2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/changelog2017-06-26 08:51:10.0 +0200 @@ -1,3 +1,12 @@ +tbdialout (1.7.2-1+deb9u1) stretch; urgency=medium + + * Include leading plus symbol with tel: URI scheme. (Closes: #865961) + * Remove Dm-Upload-Allowed. + * Add missing detalls to debian/copyright + * Update watch file. + + -- Daniel Pocock <dan...@pocock.pro> Mon, 26 Jun 2017 08:51:10 +0200 + tbdialout (1.7.2-1) unstable; urgency=low * Initial packaging. (Closes: #746687) diff -Nru tbdialout-1.7.2/debian/control tbdialout-1.7.2/debian/control --- tbdialout-1.7.2/debian/control 2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/control 2017-06-26 08:51:10.0 +0200 @@ -5,7 +5,6 @@ Uploaders: Daniel Pocock <dan...@pocock.pro> Build-Depends: debhelper (>= 9), mozilla-devscripts (>= 0.19~) Build-Depends-Indep: zip -DM-Upload-Allowed: yes Standards-Version: 3.9.5 Vcs-Git: git://git.debian.org/pkg-mozext/tbdialout.git Vcs-Browser: http://git.debian.org/?p=pkg-mozext/tbdialout.git;a=summary diff -Nru tbdialout-1.7.2/debian/copyright tbdialout-1.7.2/debian/copyright --- tbdialout-1.7.2/debian/copyright2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/copyright2014-06-12 17:29:46.0 +0200 @@ -10,6 +10,17 @@ Copyright: 2010, Nickolay Ponomarev <asquee...@gmail.com> License: MPL-1.1 +Files: content/options.js content/options.xul content/overlay.js content/thunderbirdOverlay.xul +Copyright: 2010-2011, Chris Hastie <ch...@oak-wood.co.uk> +License: MPL-1.1 or GPL-2.0 or LGPL-2.1 + On Debian systems, the full text of the GNU General Public + License version 2 can be found in the file + `/usr/share/common-licenses/GPL-2'. + . + On Debian systems, the full text of the GNU Lesser General Public + License version 2.1 can be found in the file + `/usr/share/common-licenses/LGPL-2.1'. + Files: debian/* Copyright: 2014, Daniel Pocock http://danielpocock.com License: MPL-1.1 diff -Nru tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch --- tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch 2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch 2017-06-26 08:43:20.0 +0200 @@ -1,13 +1,16 @@ diff --git a/defaults/preferences/tbdialout.js b/defaults/preferences/tbdialout.js -index af5c78f..9e509f1 100644 +index af5c78f..2ec3bcd 100644 --- a/defaults/preferences/tbdialout.js +++ b/defaults/preferences/tbdialout.js -@@ -1,4 +1,4 @@ +@@ -1,6 +1,6 @@ -pref( "extensions.tbdialout.proto", "callto:" ); +pref( "extensions.tbdialout.proto", "tel:" ); pref( "extensions.tbdialout.prefix", "" ); - pref( "extensions.tbdialout.plus", "" ); +-pref( "extensions.tbdialout.plus", "" ); ++pref( "extensions.tbdialout.plus", "+" ); pref( "extensions.tbdialout.tbbuttonadded", false ); + pref( "extensions.tbdialout.customurl", "" ); + pref( "extensions.tbdialout.customuser", "" ); @@ -15,4 +15,4 @@ pref( "extensions.tbdialout.ami.host", "" ); pref( "extensions.tbdialout.ami.port", 5038 ); pref( "extensions.tbdialout.ami.user", "" ); diff -Nru tbdialout-1.7.2/debian/watch tbdialout-1.7.2/debian/watch --- tbdialout-1.7.2/debian/watch2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/watch2015-10-01 21:26:13.0 +0200 @@ -1,3 +1,4 @@ version=3 -opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/TBDialOut-$1\.tar\.gz/ \ +opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/TBDialOut-$1\.tar\.gz/,\ +uversionmangle=s/pre/~/ \ https://github.com/tipichris/TBDialOut/tags .*/v?(\d\S*)\.tar\.gz
Bug#865971: stable-pu: package tbdialout/1.7.2-2
Control: tags -1 - moreinfo On 26/06/17 11:31, Adam D. Barratt wrote: > > The debdiff is obviously not what you're proposing uploading to stable: > > +tbdialout (1.7.2-2) unstable; urgency=low > > Please can we have a debdiff of what you're actually proposing to > upload, as built and tested on stable? > Please find the revised debdiff attached diff -Nru tbdialout-1.7.2/debian/changelog tbdialout-1.7.2/debian/changelog --- tbdialout-1.7.2/debian/changelog2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/changelog2017-06-26 08:51:10.0 +0200 @@ -1,3 +1,9 @@ +tbdialout (1.7.2-1+deb9u1) stable; urgency=medium + + * Include leading plus symbol with tel: URI scheme. (Closes: #865961) + + -- Daniel Pocock <dan...@pocock.pro> Mon, 26 Jun 2017 08:51:10 +0200 + tbdialout (1.7.2-1) unstable; urgency=low * Initial packaging. (Closes: #746687) diff -Nru tbdialout-1.7.2/debian/control tbdialout-1.7.2/debian/control --- tbdialout-1.7.2/debian/control 2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/control 2017-06-26 08:51:10.0 +0200 @@ -5,7 +5,6 @@ Uploaders: Daniel Pocock <dan...@pocock.pro> Build-Depends: debhelper (>= 9), mozilla-devscripts (>= 0.19~) Build-Depends-Indep: zip -DM-Upload-Allowed: yes Standards-Version: 3.9.5 Vcs-Git: git://git.debian.org/pkg-mozext/tbdialout.git Vcs-Browser: http://git.debian.org/?p=pkg-mozext/tbdialout.git;a=summary diff -Nru tbdialout-1.7.2/debian/copyright tbdialout-1.7.2/debian/copyright --- tbdialout-1.7.2/debian/copyright2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/copyright2014-06-12 17:29:46.0 +0200 @@ -10,6 +10,17 @@ Copyright: 2010, Nickolay Ponomarev <asquee...@gmail.com> License: MPL-1.1 +Files: content/options.js content/options.xul content/overlay.js content/thunderbirdOverlay.xul +Copyright: 2010-2011, Chris Hastie <ch...@oak-wood.co.uk> +License: MPL-1.1 or GPL-2.0 or LGPL-2.1 + On Debian systems, the full text of the GNU General Public + License version 2 can be found in the file + `/usr/share/common-licenses/GPL-2'. + . + On Debian systems, the full text of the GNU Lesser General Public + License version 2.1 can be found in the file + `/usr/share/common-licenses/LGPL-2.1'. + Files: debian/* Copyright: 2014, Daniel Pocock http://danielpocock.com License: MPL-1.1 diff -Nru tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch --- tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch 2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch 2017-06-26 08:43:20.0 +0200 @@ -1,13 +1,16 @@ diff --git a/defaults/preferences/tbdialout.js b/defaults/preferences/tbdialout.js -index af5c78f..9e509f1 100644 +index af5c78f..2ec3bcd 100644 --- a/defaults/preferences/tbdialout.js +++ b/defaults/preferences/tbdialout.js -@@ -1,4 +1,4 @@ +@@ -1,6 +1,6 @@ -pref( "extensions.tbdialout.proto", "callto:" ); +pref( "extensions.tbdialout.proto", "tel:" ); pref( "extensions.tbdialout.prefix", "" ); - pref( "extensions.tbdialout.plus", "" ); +-pref( "extensions.tbdialout.plus", "" ); ++pref( "extensions.tbdialout.plus", "+" ); pref( "extensions.tbdialout.tbbuttonadded", false ); + pref( "extensions.tbdialout.customurl", "" ); + pref( "extensions.tbdialout.customuser", "" ); @@ -15,4 +15,4 @@ pref( "extensions.tbdialout.ami.host", "" ); pref( "extensions.tbdialout.ami.port", 5038 ); pref( "extensions.tbdialout.ami.user", "" ); diff -Nru tbdialout-1.7.2/debian/watch tbdialout-1.7.2/debian/watch --- tbdialout-1.7.2/debian/watch2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/watch2015-10-01 21:26:13.0 +0200 @@ -1,3 +1,4 @@ version=3 -opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/TBDialOut-$1\.tar\.gz/ \ +opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/TBDialOut-$1\.tar\.gz/,\ +uversionmangle=s/pre/~/ \ https://github.com/tipichris/TBDialOut/tags .*/v?(\d\S*)\.tar\.gz
Bug#865971: stable-pu: package tbdialout/1.7.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Adding a '+' to the default settings for this plugin makes it work seamlessly with no user attempt to configure it. Without the '+', if it sees a phone number +1234567000 it creates the URI tel:1234567000 which is not a valid tel: URI as per RFC 3966[1] With the '+' in the default preferences, it creates the correct URI, tel:+1234567000 The relevant bug report is 865961[2] The debdiff includes other minor changes: - remove obsolete Dm-Upload-Allowed from debian/control - update debian/copyright - update debian/watch Regards, Daniel 1. http://www.faqs.org/rfcs/rfc3966.html 2. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865961 diff -Nru tbdialout-1.7.2/debian/changelog tbdialout-1.7.2/debian/changelog --- tbdialout-1.7.2/debian/changelog2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/changelog2017-06-26 08:51:10.0 +0200 @@ -1,3 +1,9 @@ +tbdialout (1.7.2-2) unstable; urgency=low + + * Include leading plus symbol with tel: URI scheme. (Closes: #865961) + + -- Daniel Pocock <dan...@pocock.pro> Mon, 26 Jun 2017 08:51:10 +0200 + tbdialout (1.7.2-1) unstable; urgency=low * Initial packaging. (Closes: #746687) diff -Nru tbdialout-1.7.2/debian/control tbdialout-1.7.2/debian/control --- tbdialout-1.7.2/debian/control 2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/control 2017-06-26 08:51:10.0 +0200 @@ -5,7 +5,6 @@ Uploaders: Daniel Pocock <dan...@pocock.pro> Build-Depends: debhelper (>= 9), mozilla-devscripts (>= 0.19~) Build-Depends-Indep: zip -DM-Upload-Allowed: yes Standards-Version: 3.9.5 Vcs-Git: git://git.debian.org/pkg-mozext/tbdialout.git Vcs-Browser: http://git.debian.org/?p=pkg-mozext/tbdialout.git;a=summary diff -Nru tbdialout-1.7.2/debian/copyright tbdialout-1.7.2/debian/copyright --- tbdialout-1.7.2/debian/copyright2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/copyright2014-06-12 17:29:46.0 +0200 @@ -10,6 +10,17 @@ Copyright: 2010, Nickolay Ponomarev <asquee...@gmail.com> License: MPL-1.1 +Files: content/options.js content/options.xul content/overlay.js content/thunderbirdOverlay.xul +Copyright: 2010-2011, Chris Hastie <ch...@oak-wood.co.uk> +License: MPL-1.1 or GPL-2.0 or LGPL-2.1 + On Debian systems, the full text of the GNU General Public + License version 2 can be found in the file + `/usr/share/common-licenses/GPL-2'. + . + On Debian systems, the full text of the GNU Lesser General Public + License version 2.1 can be found in the file + `/usr/share/common-licenses/LGPL-2.1'. + Files: debian/* Copyright: 2014, Daniel Pocock http://danielpocock.com License: MPL-1.1 diff -Nru tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch --- tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch 2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/patches/0002_default_proto_tel_uri.patch 2017-06-26 08:43:20.0 +0200 @@ -1,13 +1,16 @@ diff --git a/defaults/preferences/tbdialout.js b/defaults/preferences/tbdialout.js -index af5c78f..9e509f1 100644 +index af5c78f..2ec3bcd 100644 --- a/defaults/preferences/tbdialout.js +++ b/defaults/preferences/tbdialout.js -@@ -1,4 +1,4 @@ +@@ -1,6 +1,6 @@ -pref( "extensions.tbdialout.proto", "callto:" ); +pref( "extensions.tbdialout.proto", "tel:" ); pref( "extensions.tbdialout.prefix", "" ); - pref( "extensions.tbdialout.plus", "" ); +-pref( "extensions.tbdialout.plus", "" ); ++pref( "extensions.tbdialout.plus", "+" ); pref( "extensions.tbdialout.tbbuttonadded", false ); + pref( "extensions.tbdialout.customurl", "" ); + pref( "extensions.tbdialout.customuser", "" ); @@ -15,4 +15,4 @@ pref( "extensions.tbdialout.ami.host", "" ); pref( "extensions.tbdialout.ami.port", 5038 ); pref( "extensions.tbdialout.ami.user", "" ); diff -Nru tbdialout-1.7.2/debian/watch tbdialout-1.7.2/debian/watch --- tbdialout-1.7.2/debian/watch2014-05-02 18:58:02.0 +0200 +++ tbdialout-1.7.2/debian/watch2015-10-01 21:26:13.0 +0200 @@ -1,3 +1,4 @@ version=3 -opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/TBDialOut-$1\.tar\.gz/ \ +opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/TBDialOut-$1\.tar\.gz/,\ +uversionmangle=s/pre/~/ \ https://github.com/tipichris/TBDialOut/tags .*/v?(\d\S*)\.tar\.gz
Bug#861409: unblock: postbooks-updater/2.4.0-3
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
This fixes the RC bug 861408[1] by using the proposed patch.
Regards,
Daniel
1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861408
diff -Nru postbooks-updater-2.4.0/debian/changelog
postbooks-updater-2.4.0/debian/changelog
--- postbooks-updater-2.4.0/debian/changelog2017-01-17 18:10:24.0
+0100
+++ postbooks-updater-2.4.0/debian/changelog2017-04-28 15:55:22.0
+0200
@@ -1,3 +1,9 @@
+postbooks-updater (2.4.0-3) unstable; urgency=medium
+
+ * Update for libqt5sql5-psql (Closes: #861408)
+
+ -- Daniel Pocock <dan...@pocock.pro> Fri, 28 Apr 2017 15:55:22 +0200
+
postbooks-updater (2.4.0-2) unstable; urgency=medium
* Build for unstable.
diff -Nru postbooks-updater-2.4.0/debian/control
postbooks-updater-2.4.0/debian/control
--- postbooks-updater-2.4.0/debian/control 2017-01-17 15:29:04.0
+0100
+++ postbooks-updater-2.4.0/debian/control 2017-04-28 15:42:33.0
+0200
@@ -11,7 +11,7 @@
Package: postbooks-updater
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libqt4-sql-psql
+Depends: ${shlibs:Depends}, ${misc:Depends}, libqt5sql5-psql
Description: multi-user accounting / CRM / ERP suite (database update manager)
A full-featured, fully-integrated business management system, the core of
the award winning xTuple ERP Suite. Built with the open source PostgreSQL
Bug#860376: unblock: resiprocate/1:1.11.0~beta1-2
On 16/04/17 09:42, Niels Thykier wrote: > Control: tags -1 moreinfo > > Andreas Beckmann: >> On Sat, 15 Apr 2017 13:21:05 +0200 Daniel Pocock <dan...@pocock.pro> wrote: >>> This fixes the RC bug 856874[1] by using the proposed patch. >> >> That patch misses Breaks+Replaces! >> >> Andreas >> > > Andreas, thanks for catching that. > > Daniel, can we have that included as well? > Thanks for the feedback, uploaded resiprocate_1.11.0~beta1-3_amd64.changes with breaks/replaces added. Regards, Daniel
Bug#860376: unblock: resiprocate/1:1.11.0~beta1-2
Control: tags -1 -moreinfo On 15/04/17 17:55, Ivo De Decker wrote: > Control: tags -1 moreinfo confirmed > > Hi Daniel, > > On Sat, Apr 15, 2017 at 01:21:05PM +0200, Daniel Pocock wrote: >> Subject: unblock: resiprocate/1:1.11.0~beta1-2 > >> This fixes the RC bug 856874[1] by using the proposed patch. > > The upload doesn't seem to be in the archive. If this was meant as a > pre-approval request, I'm happy to approve the upload. > Thanks Ivo, request was for pre-approval > There is an NMU in deferred with (probably) the same patch, but I can't > unblock that one yet, as it will only get into the archive in 3 days (unless > someone reschedules it, with your approval). > Micah, thanks for building that, I've uploaded my own build so it will go through without the delay. Sorry I didn't announce this on the bug report before you made a build. Regards, Daniel
Bug#852395: unblock: gssproxy/0.5.1-2
On 05/03/17 19:42, Niels Thykier wrote: > On Sat, 04 Feb 2017 09:58:00 + Niels Thykier <ni...@thykier.net> wrote: >> Daniel Pocock: >>> [...] >>> >>> Upstream is not really supporting rpc.svcgssd any more, they actually >>> disabled it in the build so people can still have it as a transitional >>> measure in stretch. >>> >>> People shouldn't be using it in any new installations. Offering them >>> gssproxy is a very sensible thing to do. >>> >>> Regards, >>> >>> Daniel >>> >> Debian kernel team <debian-ker...@lists.debian.org> >> Ok, follow up questions: >> >> * Do you have an upstream reference to the state of rpc.svcgssd? http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=24b5d60d7f0a514310df810e3eb27b72f665febf "svcgssd: Disable support for the rpcsec_gss server by default At this point the gssproxy is better option than the svcgssd so the support is off by default. Use --enable-svcgss to re-enable the support" but it looks like it may not be completely abandoned, there have been other commits that mention gssd recently. >> >> * Can we provide both rpc.svcgssd and gssproxy in Debian (with the >>admin choosing) or is it an "xor"? >> I think there are two questions: a) can they both exist in different packages that conflict with each other? I'm guessing that will probably be yes. b) can they both be installed simultaneously? Possibly not (can anybody on the linux-nfs list answer?) >> * If this package is unblocked, are there any changes needed in >>nfs-common needed to support gssproxy? (source upload, binNMU or >>"just works with no further changes") >> I don't have time to investigate that right now, if anybody else has time to look more closely that would be great. Regards, Daniel
Bug#852395: unblock: gssproxy/0.5.1-2
On 04/02/17 10:50, Niels Thykier wrote: > Control: tags -1 moreinfo > > CC'ing the maintainer of nfs-common and the reporter of #848306. > > Robbie Harwood: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: unblock >> >> Please unblock package gssproxy >> >> gssproxy has been 10 days in unstable, and allowing it to migrate will fix >> bug#848306 (severity: important) in nfs-common. gssproxy is a new package in >> unstable (so no debdiff is included), and would have made the freeze had I >> not >> made a mistake documenting copyright. >> >> Thanks. >> >> unblock gssproxy/0.5.1-2 >> >> [...] > Hi, > > Thanks for bringing this up. > > Is this migration from rpc.svcgssd to gssproxy so important (release > critical) that it ought to be granted an exception? And if so, why is it > that important (despite #848306 not being release critical)? Upstream is not really supporting rpc.svcgssd any more, they actually disabled it in the build so people can still have it as a transitional measure in stretch. People shouldn't be using it in any new installations. Offering them gssproxy is a very sensible thing to do. Regards, Daniel
Bug#824341: wheezy-pu: update xen-utils-4.1 with patch to boot jessie/grub2 VMs
On 14/05/16 19:35, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Sat, 2016-05-14 at 19:10 +0200, Daniel Pocock wrote: >> If somebody is still running wheezy for their dom0 (host) environment >> and they are using jessie or other systems with grub2 in their VMs, they >> can't boot their VM. >> >> A rather trivial 1-line fix in the dom0 (host) system fixes the problem. >> >> Please advise if the release team would accept an upload to old-stable >> adding the following 1-line patch: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=783346;filename=GrubConf.py-jessie.patch;att=1 > > Given that xen-utils-4.1 only exists on architectures that are covered > by wheezy-lts, is there a good reason not to handle the change via that > route? We're working towards EOLing wheezy now so generally aren't > taking new updates. > If I understand the LTS wiki correctly, users don't need to make any extra effort to get the package from LTS, so I think that strategy sounds fine Can anybody else comment, is there any reason not to do it this way? This appears to be the page with LTS instructions for releasing the fix: https://wiki.debian.org/LTS/Development
Bug#824341: wheezy-pu: update xen-utils-4.1 with patch to boot jessie/grub2 VMs
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu X-Debbugs-CC: pkg-xen-de...@lists.alioth.debian.org If somebody is still running wheezy for their dom0 (host) environment and they are using jessie or other systems with grub2 in their VMs, they can't boot their VM. A rather trivial 1-line fix in the dom0 (host) system fixes the problem. Please advise if the release team would accept an upload to old-stable adding the following 1-line patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=783346;filename=GrubConf.py-jessie.patch;att=1 The bug report with the patch and discussion is: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783346 Note that if people are using XCP, they are stuck on wheezy for their dom0 because XCP was not included[1] in jessie, so they can't solve this issue by simply upgrading the host. Regards, Daniel 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740517
Bug#791403: pu: ganglia-modules-linux/1.3.6-2
On 20/10/15 21:08, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Sat, 2015-07-04 at 17:53 +0200, Daniel Pocock wrote: >> In any case, I've now gone and made a branch for jessie and built a >> package, there is a debdiff attached > > Please go ahead; sorry for the delay. > Thanks, I just uploaded ganglia-modules-linux_1.3.6-1+deb8u1_amd64.changes Regards, Daniel
Re: testing migration errors about libqt4-webkit
On 14/09/15 17:34, Lisandro Damián Nicanor Pérez Meyer wrote: > On Monday 14 September 2015 10:12:40 Daniel Pocock wrote: >> https://release.debian.org/migration/testing.pl?package=postbooks tells >> me that my package didn't migrate to testing because "libqt4-webkit is >> not available in Debian" >> >> I unpacked the binary package[1] with "dpkg -e ..." and looking inside >> the control file, libqt4-webkit is not mentioned anywhere. It only >> depends on libqtwebkit4 (>= 2.1.0~2011week13) >> >> The source package has a build dependency on libqtwebkit-dev >> >> Furthermore, the update_excuses page[2] doesn't mention libqt-webkit4 at >> all. >> >> Is there some special logic around the migration of qtwebkit reverse >> dependencies now? Or is there some bug in the migration process? > > Nothing strange on our side, I would ask the Release Team about this :-/ > > Can anybody in the release team comment on this? 1. http://ftp.us.debian.org/debian/pool/main/p/postbooks/postbooks_4.9.1-3_amd64.deb 2. https://release.debian.org/britney/update_excuses.html 3. https://packages.qa.debian.org/p/postbooks.html
Re: testing migration errors about libqt4-webkit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 14/09/15 19:05, Niels Thykier wrote: > On 2015-09-14 17:54, Daniel Pocock wrote: >> >> >> On 14/09/15 17:34, Lisandro Damián Nicanor Pérez Meyer wrote: >>> On Monday 14 September 2015 10:12:40 Daniel Pocock wrote: >>>> https://release.debian.org/migration/testing.pl?package=postbooks >>>> tells me that my package didn't migrate to testing because >>>> "libqt4-webkit is not available in Debian" >>>> >>>> I unpacked the binary package[1] with "dpkg -e ..." and >>>> looking inside the control file, libqt4-webkit is not >>>> mentioned anywhere. It only depends on libqtwebkit4 (>= >>>> 2.1.0~2011week13) >>>> >>>> The source package has a build dependency on libqtwebkit-dev >>>> >>>> Furthermore, the update_excuses page[2] doesn't mention >>>> libqt-webkit4 at all. >>>> >>>> Is there some special logic around the migration of qtwebkit >>>> reverse dependencies now? Or is there some bug in the >>>> migration process? >>> >>> Nothing strange on our side, I would ask the Release Team about >>> this :-/ >>> >>> >> >> Can anybody in the release team comment on this? >> >> [...] > > I have no clue why testing.pl concludes that postbooks depends on > libqt4-webkit. However, that is a red herring. Sadly, it is not > the most reliable/accurate service. > Ok, thanks for confirming that, is there anywhere I should report this issue as a bug? The page itself only has Björn's email address. > The issue is that migrating postbooks would make postbooks-updater > uninstallable on amd64. I have tried to add an easy hint to make > Britney migrate postbooks together with postbooks-updater (without > having checked if it will work). They were all built together and I even ran them on my production database, so I'm hoping they are working together When I update these packages in future, do I need to contact the release team to add a hint or is there anything I can do to streamline this process? > If it does not migrate tonight, we will revisit it. Please note > that the migration mails are set only once a day (next in 22 hours > from now), so please use dak or rmadision if you want to know > before then. > > Thanks, ~Niels > > > > -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV9v+vAAoJEOm1uwJp1aqDb7MQAMT60RxIKBRrguuox/jTKxUV WSm5o5EfyUqU8NxSFf8o5cx7s6akFnwCHnktJ8IGRb3MVfkT/M5zeo8lpMF/EC/a D3z4Df0phnVQrVz99xO+yBBwMBAXtmXMRDPb945NX1GTZ83g2r3Fi4wWvGwjLNpf iTkLpnW+MJX6/SVqHPI5iejF8YHKhp9K4jUYkjlxQQPBjkDFxr2XLuiJ2vUm3AJ5 I7SF1B3jStQr3eaByY1CBic9N5LETAUv7lzlPDTwoz37bzb7Vuy4xUJTjXOxb0uw xvwGa4/CWJaRI68LgAILTbc5HWA4XECur09kISyCdrE6X5/PTTnkouIIiGqeqkoy 1qN6FsyoEoETKGPOtrnFvrhhChN5oZThxLNUxaUJCRfNal1IdG7F6PwKwXmIjdYq x28bWqYI0pgOv9HrGtfSVRNICMQRUZmvKTLVUH8l9C7KjdS27nT+Jw8tMVDk1n13 OSV2cilRAtrfA5W28T6v75Uk+09EX3p/TfTgZ9wk94QUH1pgyAlf9l/IAbqVjTxG pc6f8NPoTZCZq+X6HBW7gX92/wFvjBBtVkubCqrMvwJZ8WiebRBqM2Ycmn4QgoCY F0CpfW59jsnX7qnzHGIHyuXWV1CxmKZrYQFpZm9nAb01lrlDCk/6yeloy4PwRkTe +QFq4EoprDbmukkyn6n4 =iuI5 -END PGP SIGNATURE-
Re: testing migration errors about libqt4-webkit
On 14/09/15 19:17, Adam D. Barratt wrote:
> On 2015-09-14 16:54, Daniel Pocock wrote:
>> On 14/09/15 17:34, Lisandro Damián Nicanor Pérez Meyer wrote:
>>> On Monday 14 September 2015 10:12:40 Daniel Pocock wrote:
>>>> https://release.debian.org/migration/testing.pl?package=postbooks tells
>>>> me that my package didn't migrate to testing because "libqt4-webkit is
>>>> not available in Debian"
>
> Well, it also says "Updating postbooks makes 1 non-depending packages
> uninstallable on amd64: postbooks-updater", which is more relevant.
>
>>>> I unpacked the binary package[1] with "dpkg -e ..." and looking inside
>>>> the control file, libqt4-webkit is not mentioned anywhere. It only
>>>> depends on libqtwebkit4 (>= 2.1.0~2011week13)
> [...]
>
> I'm not sure why it's getting the package name wrong, other than because
> the script needs rewriting from scratch (to handle multiple
> architectures (at least amd64), deal sensibly with extra-source-only,
> notice that the package is being auto-hinted, etc). If you want to know
> what's going on with britney, I'd suggest looking at output that's
> generated by britney (i.e. britney logs and/or grep-excuses).
>
Currently, the "Check why" link on packages.qa.debian.org/postbooks
takes me to the testing.pl link above. If that testing.pl script has a
lot of known issues, then maybe the "Check why" link should be removed?
> It's possible / probable that the "not available in Debian" is due to
> the fact that (as it says) the script only checks binary dependencies on
> i386, and postbooks doesn't build there.
>
Where did you see that? The buildd suggests it was built successfully
on i386:
https://buildd.debian.org/status/fetch.php?pkg=postbooks=i386=4.9.1-3=1441624363
>> Can anybody in the release team comment on this?
>
> I have to admit that I'm failing to spot what the exact issue is, other
> than postbooks and postbooks-updater want to migrate to testing at the
> same time but don't have an explicit dependency relationship (and I
> believe that Niels has added a hint to achieve that while I was checking
> things and writing this reply).
>
postbooks-updater has
- a build dependency on the dev package from postbooks, debian/control
explicitly states:
libxtuplecommon-dev (>= 4.9.1)
- a runtime dependency on one of the shared libs from postbooks, it is
added in debian/control by ${shlibs:Depends}
postbooks binary itself suggests postbooks-updater
Do I need to update the postbooks-updater package to use something more
than just ${shlibs:Depends} ?
Bug#791403: follow-up #791403
Hi Adam, Can you please let me know about this bug #791403, can I go ahead and upload the fix based on the debdiff submitted on 4 July? Regards, Daniel https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791403
Bug#791403: pu: ganglia-modules-linux/1.3.6-2
tags 791403 = jessie
stop
On 04/07/15 15:08, Adam D. Barratt wrote:
user release.debian@packages.debian.org
usertags 791403 = pu
tags 791403 = jessie moreinfo
thanks
On Sat, 2015-07-04 at 14:17 +0200, Daniel Pocock wrote:
Package: release.debian.org
User: release.debian@packages.debian.org
UserTags: unblock
This is a proposed upload to stable for jessie.
Then it's not an unblock request.
Sorry about that, I had actually look at a couple of other bugs in the
BTS and they had unblock so I copied it. I won't do it again.
It resolves a problem
that causes dist-upgrade to fail.
Here is the patch that is added:
https://anonscm.debian.org/cgit/pkg-monitoring/ganglia-modules-linux.git/commit/?id=29c5f380aa46d2b1b678a63c1daa5054d119f066
and the changelog entry from the unstable upload:
https://anonscm.debian.org/cgit/pkg-monitoring/ganglia-modules-linux.git/commit/?id=80641de7ace1a93adf02a9088f4da7c13d32d771
Neither of those is a debdiff of a package which has been built and
tested on jessie, which is what is always requested for such updates.
(See
https://lists.debian.org/debian-devel-announce/2015/05/msg5.html for
example.)
I didn't want to go to the effort of making a branch for jessie and
building it that way without getting some initial feedback that it may
be acceptable to the release team. I am also keen to make sure I'm
really doing the right thing in postinst and postrm, I would welcome any
other opinions on that.
In any case, I've now gone and made a branch for jessie and built a
package, there is a debdiff attached
I looked at the email in that link, it mentions the +deb8u1 suffix. If
the stable update is identical to the version that was uploaded to
unstable then is it necessary to use a suffix?
Regards,
Daniel
diff -Nru ganglia-modules-linux-1.3.6/debian/changelog
ganglia-modules-linux-1.3.6/debian/changelog
--- ganglia-modules-linux-1.3.6/debian/changelog2014-12-07
18:15:02.0 +0100
+++ ganglia-modules-linux-1.3.6/debian/changelog2015-07-04
17:41:35.0 +0200
@@ -1,3 +1,9 @@
+ganglia-modules-linux (1.3.6-1+deb8u1) stable; urgency=medium
+
+ * Only restart service if already running. (Closes: #790951)
+
+ -- Daniel Pocock dan...@pocock.pro Sat, 04 Jul 2015 17:38:20 +0200
+
ganglia-modules-linux (1.3.6-1) unstable; urgency=low
* New upstream release.
diff -Nru ganglia-modules-linux-1.3.6/debian/postinst
ganglia-modules-linux-1.3.6/debian/postinst
--- ganglia-modules-linux-1.3.6/debian/postinst 2012-04-10 17:57:22.0
+0200
+++ ganglia-modules-linux-1.3.6/debian/postinst 2015-07-04 17:37:02.0
+0200
@@ -20,11 +20,19 @@
case $1 in
configure)
+INIT_GMOND=/etc/init.d/ganglia-monitor
if which invoke-rc.d /dev/null 21; then
- invoke-rc.d ganglia-monitor restart
+ invoke-rc.d ganglia-monitor status /dev/null 21 \
+ invoke-rc.d ganglia-monitor restart
else
- /etc/init.d/ganglia-monitor restart
+ [ -x ${INIT_GMOND} ] \
+ ${INIT_GMOND} status /dev/null 21 \
+ ${INIT_GMOND} restart
fi
+# call `true' to conceal the return status of the gmond restart
+# as we don't want an unrelated error in gmond to suggest
+# that the dpkg operation has completely failed
+true
;;
abort-upgrade|abort-remove|abort-deconfigure)
diff -Nru ganglia-modules-linux-1.3.6/debian/postrm
ganglia-modules-linux-1.3.6/debian/postrm
--- ganglia-modules-linux-1.3.6/debian/postrm 2012-04-21 15:40:20.0
+0200
+++ ganglia-modules-linux-1.3.6/debian/postrm 2015-07-04 17:37:02.0
+0200
@@ -22,18 +22,18 @@
case $1 in
purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
INIT_GMOND=/etc/init.d/ganglia-monitor
-if [ -x ${INIT_GMOND} ];
-then
- if which invoke-rc.d /dev/null 21; then
+if which invoke-rc.d /dev/null 21; then
+ invoke-rc.d ganglia-monitor status /dev/null 21 \
invoke-rc.d ganglia-monitor restart
- else
-${INIT_GMOND} restart
- fi
- # call `true' to conceal the return status of the gmond restart
- # as we don't want an unrelated error in gmond to suggest
- # that the dpkg operation has completely failed
- true
+else
+[ -x ${INIT_GMOND} ] \
+ ${INIT_GMOND} status /dev/null 21 \
+ ${INIT_GMOND} restart
fi
+# call `true' to conceal the return status of the gmond restart
+# as we don't want an unrelated error in gmond to suggest
+# that the dpkg operation has completely failed
+true
;;
*)
Bug#791403: pu: ganglia-modules-linux/1.3.6-2
Package: release.debian.org User: release.debian@packages.debian.org UserTags: unblock This is a proposed upload to stable for jessie. It resolves a problem that causes dist-upgrade to fail. Here is the patch that is added: https://anonscm.debian.org/cgit/pkg-monitoring/ganglia-modules-linux.git/commit/?id=29c5f380aa46d2b1b678a63c1daa5054d119f066 and the changelog entry from the unstable upload: https://anonscm.debian.org/cgit/pkg-monitoring/ganglia-modules-linux.git/commit/?id=80641de7ace1a93adf02a9088f4da7c13d32d771 The main reason for this request: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790951 The general issue of plugin package service restarts is discussed in this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790949 -- 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/5597cec9.4050...@pocock.pro
Bug#781147: unblock: resiprocate/1.9.7-5
Package: release.debian.org
User: release.debian@packages.debian.org
UserTags: unblock
This is a proposed upload to unstable for jessie
The main reason for this unblock request:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780979
and also helps resolve:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780980
The main reason for fixing 780979 is that the assert() can lead to a
crash of the process, as described in the bug report.
These fixes come from the master branch upstream:
https://github.com/resiprocate/resiprocate/commits/master
diff -Nru resiprocate-1.9.7/debian/changelog resiprocate-1.9.7/debian/changelog
--- resiprocate-1.9.7/debian/changelog 2014-12-10 07:28:30.0 +0100
+++ resiprocate-1.9.7/debian/changelog 2015-03-22 20:02:23.0 +0100
@@ -1,3 +1,11 @@
+resiprocate (1:1.9.7-5) unstable; urgency=medium
+
+ * Make ensureWritable more tolerant. (Closes: #780979)
+ * Stop logging errors when TLS is shut down cleanly by peer.
+(Closes: #780980)
+
+ -- Daniel Pocock dan...@pocock.pro Sun, 22 Mar 2015 19:30:31 +0100
+
resiprocate (1:1.9.7-4) unstable; urgency=medium
* Use SSLv23_method instead of TLSv1_method and
diff -Nru resiprocate-1.9.7/debian/patches/0003-log-tls-clean-shutdown.patch
resiprocate-1.9.7/debian/patches/0003-log-tls-clean-shutdown.patch
--- resiprocate-1.9.7/debian/patches/0003-log-tls-clean-shutdown.patch
1970-01-01 01:00:00.0 +0100
+++ resiprocate-1.9.7/debian/patches/0003-log-tls-clean-shutdown.patch
2015-03-22 19:43:14.0 +0100
@@ -0,0 +1,30 @@
+diff --git a/resip/stack/ssl/TlsConnection.cxx
b/resip/stack/ssl/TlsConnection.cxx
+index c3537aa..fb80323 100644
+--- a/resip/stack/ssl/TlsConnection.cxx
b/resip/stack/ssl/TlsConnection.cxx
+@@ -445,6 +445,12 @@ TlsConnection::read(char* buf, int count )
+ return 0;
+ }
+ break;
++ case SSL_ERROR_ZERO_RETURN:
++ {
++DebugLog( Got SSL_ERROR_ZERO_RETURN (TLS shutdown by peer));
++return -1;
++ }
++ break;
+ default:
+ {
+ handleOpenSSLErrorQueue(bytesRead, err, SSL_read);
+@@ -532,6 +538,12 @@ TlsConnection::write( const char* buf, int count )
+ return 0;
+ }
+ break;
++ case SSL_ERROR_ZERO_RETURN:
++ {
++DebugLog( Got SSL_ERROR_ZERO_RETURN (TLS shutdown by peer));
++return -1;
++ }
++ break;
+ default:
+ {
+ handleOpenSSLErrorQueue(ret, err, SSL_write);
diff -Nru
resiprocate-1.9.7/debian/patches/0004-make-ensureWritable-more-tolerant.patch
resiprocate-1.9.7/debian/patches/0004-make-ensureWritable-more-tolerant.patch
---
resiprocate-1.9.7/debian/patches/0004-make-ensureWritable-more-tolerant.patch
1970-01-01 01:00:00.0 +0100
+++
resiprocate-1.9.7/debian/patches/0004-make-ensureWritable-more-tolerant.patch
2015-03-22 19:43:14.0 +0100
@@ -0,0 +1,55 @@
+diff --git a/resip/stack/Connection.cxx b/resip/stack/Connection.cxx
+index 567c105..1f01ecc 100644
+--- a/resip/stack/Connection.cxx
b/resip/stack/Connection.cxx
+@@ -88,13 +88,35 @@ Connection::performWrite()
+ {
+if(transportWrite())
+{
+- assert(mInWritable);
+- getConnectionManager().removeFromWritable(this);
+- mInWritable = false;
+- return 0; // What does this transportWrite() mean?
++ // If we get here it means:
++ // a. on a previous invocation, SSL_do_handshake wanted to write
++ // (SSL_ERROR_WANT_WRITE)
++ // b. now the handshake is complete or it wants to read
++ if(mInWritable)
++ {
++ getConnectionManager().removeFromWritable(this);
++ mInWritable = false;
++ }
++ else
++ {
++ WarningLog(performWrite invoked while not in write set);
++ }
++ return 0; // Q. What does this transportWrite() mean?
++// A. It makes the TLS handshake move along after it
++//was waiting in the write set.
++ }
++
++ // If the TLS handshake returned SSL_ERROR_WANT_WRITE again
++ // then we could get here without really having something to write
++ // so just return, remaining in the write set.
++ if(mOutstandingSends.empty())
++ {
++ // FIXME: this needs to be more elaborate with respect
++ // to TLS handshaking but it doesn't appear we can do that
++ // without ABI breakage.
++ return 0;
+}
+
+- assert(!mOutstandingSends.empty());
+switch(mOutstandingSends.front()-command)
+{
+case SendData::CloseConnection:
+@@ -272,7 +294,8 @@ Connection::ensureWritable()
+ {
+if(!mInWritable)
+{
+- assert(!mOutstandingSends.empty());
++ //assert(!mOutstandingSends.empty()); // empty during TLS handshake
++ // therefore must be careful to check mOutstandingSends later
+ getConnectionManager().addToWritable(this);
+ mInWritable = true
Bug#781010: unblock: simpleid/0.8.1-14
Control: tags -1 -moreinfo On 25/03/15 20:52, Niels Thykier wrote: Control: tags -1 confirmed moreinfo On 2015-03-24 17:31, Daniel Pocock wrote: Control: tags -1 -moreinfo [...] Attached - please tell me if I should upload 0.8.1-14 to unstable Ack, please upload it to unstable and let us remove the moreinfo tag once it has been accepted. Uploaded and accepted -- 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/551327d7.4020...@pocock.pro
Bug#781147: unblock: resiprocate/1.9.7-5
Control: tags -1 -moreinfo On 25/03/15 20:50, Niels Thykier wrote: Control: tags -1 confirmed moreinfo On 2015-03-25 09:23, Daniel Pocock wrote: Package: release.debian.org User: release.debian@packages.debian.org UserTags: unblock This is a proposed upload to unstable for jessie The main reason for this unblock request: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780979 and also helps resolve: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780980 The main reason for fixing 780979 is that the assert() can lead to a crash of the process, as described in the bug report. These fixes come from the master branch upstream: https://github.com/resiprocate/resiprocate/commits/master Seems reasonable, please upload it to unstable and remove the moreinfo tag once it has been accepted. Thanks, uploaded and accepted -- 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/55132b3d.2070...@pocock.pro
Bug#781010: unblock: simpleid/0.8.1-14
Control: tags -1 -moreinfo
On 24/03/15 16:05, Niels Thykier wrote:
Control: tags -1 moreinfo
On 2015-03-23 08:55, Daniel Pocock wrote:
Package: release.debian.org
User: release.debian@packages.debian.org
UserTags: unblock
I'm proposing to update the simpleid package using the patch contained
in this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718483
Direct link to the patch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=718483.diff;att=1;bug=718483
I would also propose a couple of other small fixes,
- uploader email address s/pocock.com.au/pocock.pro
- home page URL http://www.simpleid.org
Please let me know if all of the above is likely to be accepted at this
stage in the freeze and if so I will build a package and send a debdiff
for approval.
Hi Daniel,
Can you please provide a full debdiff all the changes you wish to include.
Attached - please tell me if I should upload 0.8.1-14 to unstable
diff -u simpleid-0.8.1/debian/README.Debian simpleid-0.8.1/debian/README.Debian
--- simpleid-0.8.1/debian/README.Debian
+++ simpleid-0.8.1/debian/README.Debian
@@ -9,7 +9,7 @@
To start quickly, you MUST:
- a) edit /etc/simpleid/config.php and
+ a) edit /etc/simpleid/config.inc and
set SIMPLEID_BASE_URL to YOUR domain name
b) copy the sample identity to /var/lib/simpleid/identities
diff -u simpleid-0.8.1/debian/simpleid.install
simpleid-0.8.1/debian/simpleid.install
--- simpleid-0.8.1/debian/simpleid.install
+++ simpleid-0.8.1/debian/simpleid.install
@@ -3 +3 @@
-debian/conf/* etc/simpleid
+debian/conf/config.inc etc/simpleid
diff -u simpleid-0.8.1/debian/simpleid.links
simpleid-0.8.1/debian/simpleid.links
--- simpleid-0.8.1/debian/simpleid.links
+++ simpleid-0.8.1/debian/simpleid.links
@@ -1,3 +1,2 @@
etc/simpleid/config.inc usr/share/simpleid/www/config.inc
-etc/simpleid/apache.conf etc/apache2/conf.d/simpleid.conf
usr/share/javascript/jquery/jquery.min.js usr/share/simpleid/www/html/jquery.js
diff -u simpleid-0.8.1/debian/changelog simpleid-0.8.1/debian/changelog
--- simpleid-0.8.1/debian/changelog
+++ simpleid-0.8.1/debian/changelog
@@ -1,3 +1,13 @@
+simpleid (0.8.1-14) unstable; urgency=low
+
+ * Apache 2.4 transition. (Closes: #718483)
+ * Update uploader email address.
+ * Update home page URL.
+ * Update VCS URLs.
+ * Correct config filename in README.Debian.
+
+ -- Daniel Pocock dan...@pocock.pro Tue, 24 Mar 2015 17:14:40 +0100
+
simpleid (0.8.1-13) unstable; urgency=low
* Revert to 1.0 source format
diff -u simpleid-0.8.1/debian/control simpleid-0.8.1/debian/control
--- simpleid-0.8.1/debian/control
+++ simpleid-0.8.1/debian/control
@@ -2,17 +2,20 @@
Section: web
Priority: extra
Maintainer: Debian Authentication Maintainers
pkg-auth-maintain...@lists.alioth.debian.org
-Uploaders: Daniel Pocock dan...@pocock.com.au
-Build-Depends: debhelper (= 8), cdbs (= 0.4.89)
+Uploaders: Daniel Pocock dan...@pocock.pro
+Build-Depends: debhelper (= 8), cdbs (= 0.4.89), dh-apache2 | apache2-dev
Standards-Version: 3.9.3
-Homepage: http://simpleid.sourceforge.net/
-Vcs-Git: git://git.debian.org/pkg-auth/simpleid.git
-Vcs-Browser: http://git.debian.org/?p=pkg-auth/simpleid.git;a=summary
+Homepage: http://www.simpleid.org/
+Vcs-Git: git://anonscm.debian.org/pkg-auth/simpleid.git
+Vcs-Browser: http://anonscm.debian.org/cgit/pkg-auth/simpleid.git
Package: simpleid
Architecture: all
-Depends: debconf | debconf-2.0, apache2 | lighttpd | httpd,
- libapache2-mod-php5, libjs-jquery, ${misc:Depends}
+Pre-Depends: dpkg (= 1.15.7.2)
+Depends: debconf | debconf-2.0,
+ libapache2-mod-php5 | libapache2-mod-php5filter | php5-cgi | php5-fpm |
php5,
+ libjs-jquery, ${misc:Depends}
+Recommends: ${misc:Recommends}
Description: simple OpenID provider implemented in PHP
SimpleID is a simple, personal OpenID provider written in PHP. OpenID
is a way to provide for a single digital identity across the Internet.
diff -u simpleid-0.8.1/debian/rules simpleid-0.8.1/debian/rules
--- simpleid-0.8.1/debian/rules
+++ simpleid-0.8.1/debian/rules
@@ -8,7 +8,7 @@
DEB_INSTALL_CHANGELOGS_ALL = simpleid/CHANGELOG.txt
-SIMPLEID_WEB_CONF = etc/simpleid/apache.conf
+SIMPLEID_WEB_CONF = etc/apache2/conf-available/simpleid.conf
binary-install/simpleid::
echo -n ?php define('SIMPLEID_VERSION', '$(DEB_VERSION)'); ?
debian/simpleid/usr/share/simpleid/www/version.inc.php
@@ -18,6 +18,7 @@
chmod 0750 debian/simpleid/var/lib/simpleid/identities
chown www-data.www-data debian/simpleid/var/lib/simpleid/cache
debian/simpleid/var/lib/simpleid/store
chmod 0770 debian/simpleid/var/lib/simpleid/cache
debian/simpleid/var/lib/simpleid/store
+ dh_apache2
echo 'Directory /usr/share/simpleid/www'
debian/simpleid/$(SIMPLEID_WEB_CONF)
cat simpleid/www/.htaccess.dist debian/simpleid/$(SIMPLEID_WEB_CONF)
echo '/Directory' debian/simpleid/$(SIMPLEID_WEB_CONF)
reverted:
--- simpleid
Bug#781010: unblock: simpleid/0.8.1-14
Package: release.debian.org User: release.debian@packages.debian.org UserTags: unblock I'm proposing to update the simpleid package using the patch contained in this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718483 Direct link to the patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=718483.diff;att=1;bug=718483 I would also propose a couple of other small fixes, - uploader email address s/pocock.com.au/pocock.pro - home page URL http://www.simpleid.org Please let me know if all of the above is likely to be accepted at this stage in the freeze and if so I will build a package and send a debdiff for approval. -- 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/550fc6f1.2020...@pocock.pro
Bug#777047: pu: vpim
On 04/02/15 20:32, Adam D. Barratt wrote: Control: tags -1 -moreinfo +confirmed On Wed, 2015-02-04 at 16:16 +0100, Daniel Pocock wrote: On 04/02/15 14:58, Adam D. Barratt wrote: Control: tags -1 + moreinfo On 2015-02-04 13:02, Daniel Pocock wrote: [...] The package vpim in wheezy is broken, wheezy has Ruby 1.9 but the package installs files for Ruby 1.8. Here is the bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682772 [...] +vpim (0.695-1.1+deb7u1) wheezy-proposed-updates; urgency=medium The version number needs to be lower than the package in testing - convention would be 0.695-1.1~deb7u1. I'd also appreciate confirmation that the resulting package has been tested on wheezy. I've fixed the version in the changelog and attach a revised debdiff Please go ahead. dput complained that wheezy-proposed-updates wasn't a valid codename, it ran successfully when I changed this to stable-proposed-updates Please let me know if this is correct or if there is any other action I need to take. Regards, Daniel -- 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/54d280cc.5010...@pocock.pro
Bug#777047: pu: vpim
Package: release.debian.org Tags: wheezy User: release.debian@packages.debian.org UserTags: unblock The package vpim in wheezy is broken, wheezy has Ruby 1.9 but the package installs files for Ruby 1.8. Here is the bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682772 The package was fixed with an NMU for jessie, this should also be uploaded to wheezy-proposed-updates Please confirm if I can upload the jessie version to wheezy-proposed-updates I've asked DSA to install it to ullmann.debian.org, please add it to wheezy-updates if possible to make that easier. Please let me know if I have written the changelog entry correctly or if I need to change anything else. diff -u vpim-0.695/debian/rules vpim-0.695/debian/rules --- vpim-0.695/debian/rules +++ vpim-0.695/debian/rules @@ -28,12 +28,13 @@ installdoc = install -g root -o root -m 644 build: - ruby setup.rb config --installdirs=std - ruby setup.rb setup + dh_ruby --setuprb --build touch stamp-build clean: debclean + dh_ruby --setuprb --clean ruby setup.rb distclean + rm -f debian/vpim.substvars rm -f stamp-build debclean: @@ -44,6 +45,9 @@ binary-arch: # Nothing to be done here +export DH_RUBY_IGNORE_TESTS=require-rubygems +export DH_RUBY_USE_DH_AUTO_INSTALL_DESTDIR=yes + binary-indep: debclean test -f stamp-build || $(MAKE) -f debian/rules build $(installbin) -d debian/tmp/DEBIAN @@ -56,7 +60,7 @@ $(installdoc) debian/copyright debian/tmp/usr/share/doc/$(package)/ $(installdoc) debian/README.Debian debian/tmp/usr/share/doc/$(package)/ # - ruby setup.rb install --prefix=debian/tmp + dh_ruby --setuprb --install debian/tmp $(installdoc) CHANGES debian/tmp/usr/share/doc/$(package)/changelog $(installdoc) samples/README.mutt debian/tmp/usr/share/doc/$(package)/ $(installdoc) README debian/tmp/usr/share/doc/$(package)/ diff -u vpim-0.695/debian/control vpim-0.695/debian/control --- vpim-0.695/debian/control +++ vpim-0.695/debian/control @@ -2,14 +2,15 @@ Section: libs Priority: optional Maintainer: Joey Schulze j...@debian.org -Build-Depends: ruby, ruby1.8 +Build-Depends: gem2deb Standards-Version: 3.8.0 +XS-Ruby-Versions: all Package: vpim Architecture: all Section: libs Priority: optional -Depends: ruby, ruby1.8 +Depends: ruby Suggests: facter Description: Ruby support for vCard and iCalendar This package provides calendaring, scheduling, and contact support diff -u vpim-0.695/debian/changelog vpim-0.695/debian/changelog --- vpim-0.695/debian/changelog +++ vpim-0.695/debian/changelog @@ -1,3 +1,22 @@ +vpim (0.695-1.1+deb7u1) wheezy-proposed-updates; urgency=medium + + * Non-maintainer upload. + * Backport the fix uploaded to jessie for #682772 + + -- Daniel Pocock dan...@pocock.pro Tue, 03 Feb 2015 20:37:43 +0100 + +vpim (0.695-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Port to Ruby 1.9+ (Closes: #682772) +- debian/control: change Build-Depends to gem2deb; drop dependency on + ruby1.8 +- debian/rules: change build to call `dh_ruby --setuprb` instead of + manually calling `ruby setup.rb`. This will make sure the package will + install code that is available for all Ruby interpreters. + + -- Antonio Terceiro terce...@debian.org Wed, 15 Jan 2014 13:30:44 +0100 + vpim (0.695-1) unstable; urgency=low * New upstream release
Bug#777047: pu: vpim
On 04/02/15 14:58, Adam D. Barratt wrote: Control: tags -1 + moreinfo On 2015-02-04 13:02, Daniel Pocock wrote: Package: release.debian.org Tags: wheezy User: release.debian@packages.debian.org UserTags: unblock Nope, that would be pu. I already noticed that and fixed it with an email to control@ The package vpim in wheezy is broken, wheezy has Ruby 1.9 but the package installs files for Ruby 1.8. Here is the bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682772 The package was fixed with an NMU for jessie, this should also be uploaded to wheezy-proposed-updates Please confirm if I can upload the jessie version to wheezy-proposed-updates Under other circumstances and given the nature of the changes and the package's maintenance history and popcon, I'd be more inclined to suggest removal instead tbh. (I follow -qa@, so I'm aware of why you're currently taking an interest in the package.) I've had some communication with upstream and contributed some fixes to his repository already[1] and I've helped him get it to build with travis-ci[2] so it will be easier to get the project back on track. I don't know a lot about Ruby and would defer to somebody more experienced with that ecosystem and Ruby packaging to advise whether it is better to work with the vpim code base or to start the process of packaging some other iCalendar library for Ruby For the immediate requirement (DMD) vpim appears sufficient, I attach a sample of my testing I've asked DSA to install it to ullmann.debian.org, please add it to wheezy-updates if possible to make that easier. From previous interactions and some discussion on IRC I don't believe that's likely to be a requirement in practice. If it becomes an issue then we can re-visit it later. Please let me know if I have written the changelog entry correctly or if I need to change anything else. +vpim (0.695-1.1+deb7u1) wheezy-proposed-updates; urgency=medium The version number needs to be lower than the package in testing - convention would be 0.695-1.1~deb7u1. I'd also appreciate confirmation that the resulting package has been tested on wheezy. I've fixed the version in the changelog and attach a revised debdiff The attached test output was generated running dmd.cgi on a wheezy machine. 1. https://github.com/sam-github/vpim/commits/master 2. https://travis-ci.org/sam-github/vpim $ ./dmd.cgi (offline mode: enter name=value pairs on standard input) email1=dan...@pocock.pro format=ics Content-type: text/calendar Content-Disposition: attachment; filename=dmd.ics BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Ensemble Independent//vPim 0.695//EN CALSCALE:Gregorian BEGIN:VTODO SUMMARY:jabberd2: RC bug needs fixing: #742894: Incomplete debian/copyright [was: Uploading package(s)] DESCRIPTION:jabberd2: RC bug needs fixing: #742894: Incomplete debian/copyr ight [was: Uploading package(s)] URL:http://bugs.debian.org/742894 ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO SUMMARY:ck: Migration: Has been trying to migrate for 278 days DESCRIPTION:ck: Migration: Has been trying to migrate for 278 days URL:http://qa.debian.org/excuses.php?package=ck ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO SUMMARY:jabberd2: Migration: Not in testing for 272 days DESCRIPTION:jabberd2: Migration: Not in testing for 272 days URL:http://qa.debian.org/excuses.php?package=jabberd2 ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO SUMMARY:qpid-tools: Migration: Not in testing for 227 days DESCRIPTION:qpid-tools: Migration: Not in testing for 227 days URL:http://qa.debian.org/excuses.php?package=qpid-tools ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO SUMMARY:sipml5: Migration: Not in testing for 79 days DESCRIPTION:sipml5: Migration: Not in testing for 79 days URL:http://qa.debian.org/excuses.php?package=sipml5 ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO SUMMARY:syslog-nagios-bridge: Migration: Not in testing for 42 days DESCRIPTION:syslog-nagios-bridge: Migration: Not in testing for 42 days URL:http://qa.debian.org/excuses.php?package=syslog-nagios-bridge ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO SUMMARY:qpid-proton: New version: ready for upload DESCRIPTION:qpid-proton: New version: ready for upload URL:http://git.debian.org/?p=pkg-middleware/qpid-proton.git ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO SUMMARY:jabberd2: New version: ready for upload DESCRIPTION:jabberd2: New version: ready for upload URL:http://anonscm.debian.org/gitweb/?p=pkg-xmpp/jabberd2.git ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO SUMMARY:jssip: New version available: 0.6.17 DESCRIPTION:jssip: New version available: 0.6.17 URL: ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO SUMMARY:postbooks-schema-demo: New version available: 4.8.1 DESCRIPTION:postbooks-schema-demo: New version available: 4.8.1 URL: ORGANIZER:debian...@lists.debian.org END:VTODO BEGIN:VTODO
Bug#772634: resiprocate 1:1.9.7-4 build failure on mips
The build completed on most platforms: https://buildd.debian.org/status/package.php?p=resiprocatesuite=unstable On MIPS it fails with an error from make: make[6]: *** [Headers.lo] Error 1 make[6]: *** Waiting for unfinished jobs Makefile:952: recipe for target 'Headers.lo' failed make[6]: Leaving directory '/«PKGBUILDDIR»/resip/stack' make[5]: *** [all-recursive] Error 1 I never saw this error before on MIPS or any other build, it is not something that is changed by the patch, can you please start it again? -- 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/5488133a.50...@pocock.pro
Bug#772634: resiprocate 1:1.9.7-4 build failure on s390x
The build completed on most platforms: https://buildd.debian.org/status/package.php?p=resiprocatesuite=unstable On s390x one of the unit tests fails ../../../build-aux/test-driver: line 107: 32745 Aborted $@ $log_file 21 FAIL: testTimer PASS: testTuple PASS: testUri PASS: testWsCookieContext PASS: testSocketFunc make[7]: Entering directory '/«PKGBUILDDIR»/resip/stack/test' make[7]: Nothing to be done for 'all'. make[7]: Leaving directory '/«PKGBUILDDIR»/resip/stack/test' Testsuite summary for resiprocate 1.9.7 make[6]: *** [test-suite.log] Error 1 # TOTAL: 31 # PASS: 30 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 I never saw this error before on s390x or any other build, it is not something that is changed by the patch, can you please start it again? I had a look at the code: https://github.com/resiprocate/resiprocate/blob/master/resip/stack/test/testTime.cxx Is there anything that has changed recently on s390x? The 1.9.8-1 build on Sunday did not have a problem with testTime: https://buildd.debian.org/status/fetch.php?pkg=resiprocatearch=s390xver=1.9.8-1stamp=1417977960 -- 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/548814d1.3080...@pocock.pro
Bug#772634: resiprocate 1:1.9.7-4 build failure on mips
It has failed again with a compiler error: https://buildd.debian.org/status/fetch.php?pkg=resiprocatearch=mipsver=1%3A1.9.7-4stamp=1418208861 ssl/Security.cxx: In member function 'virtual void resip::Security::preload()': ssl/Security.cxx:264:1: internal compiler error: Segmentation fault } ^ Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.9/README.Bugs for instructions. The patch does not change Security.cxx and the earlier build progress beyond this point. -- 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/54882b66.1010...@pocock.pro
Bug#772634: unblock: resiprocate/1.9.7-2
Package: release.debian.org
User: release.debian@packages.debian.org
UserTags: unblock
This is a proposed upload to testing-proposed-updates
It is a far more concise and targeted fix than the upstream 1.9.8
release discussed previously.
The main reason for this unblock request:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772632
based on the outcome of discussion on the debian-security list:
https://lists.debian.org/debian-security/2014/12/msg00032.html
This update enables TLS v1.1 and v1.2 when acting as a server and
enables v1.1 when acting as a client.
This is achieved by using the generic SSLv23_method instead of the
discouraged TLSv1_method. This approach ensures that if the OpenSSL
maintainers add or remove protocol versions because of future
vulnerabilities, this package will benefit from those changes without
needing to be patched further or recompiled.
The (much smaller) debdiff is attached, it was generated with filterdiff
to remove autotools stuff:
debdiff resiprocate_1.9.7-1.dsc resiprocate_1.9.7-2.dsc | filterdiff -x
'*/aclocal.m4' -x '*/config.*' -x '*/configure' -x '*/depcomp' -x
'*/*.in' -x '*/install-sh' -x '*/ltmain.sh' -x '*/m4/*' -x '*/missing'
-x '*/resiprocate.spec' /tmp/resiprocate-1.9.7-2.debdiff
diff -Nru resiprocate-1.9.7/debian/changelog resiprocate-1.9.7/debian/changelog
--- resiprocate-1.9.7/debian/changelog 2014-05-31 12:51:11.0 +0200
+++ resiprocate-1.9.7/debian/changelog 2014-12-09 11:56:59.0 +0100
@@ -1,3 +1,10 @@
+resiprocate (1.9.7-2) testing-proposed-updates; urgency=medium
+
+ * Use SSLv23_method instead of TLSv1_method and
+avoid TLS 1.2 when acting as client. (Closes: #772632)
+
+ -- Daniel Pocock dan...@pocock.pro Tue, 09 Dec 2014 11:34:48 +0100
+
resiprocate (1.9.7-1) unstable; urgency=medium
* New upstream release.
diff -Nru resiprocate-1.9.7/debian/patches/0001-use-SSLv23_method.patch
resiprocate-1.9.7/debian/patches/0001-use-SSLv23_method.patch
--- resiprocate-1.9.7/debian/patches/0001-use-SSLv23_method.patch
1970-01-01 01:00:00.0 +0100
+++ resiprocate-1.9.7/debian/patches/0001-use-SSLv23_method.patch
2014-12-09 11:30:51.0 +0100
@@ -0,0 +1,50 @@
+diff --git a/repro/ReproRunner.cxx b/repro/ReproRunner.cxx
+index 929392b..a2f09de 100644
+--- a/repro/ReproRunner.cxx
b/repro/ReproRunner.cxx
+@@ -1338,6 +1338,7 @@ ReproRunner::addTransports(bool
allTransportsSpecifyRecordRoute)
+ wsCookieContextFactory.reset(new
BasicWsCookieContextFactory(infoCookieName, extraCookieName, macCookieName));
+}
+
++ SecurityTypes::SSLType defaultSSLType = SecurityTypes::SSLv23;
+try
+{
+ // Check if advanced transport settings are provided
+@@ -1448,7 +1449,7 @@ ReproRunner::addTransports(bool
allTransportsSpecifyRecordRoute)
+ ipAddr, // interface to bind to
+ tlsDomain,
+ Data::Empty, // private key passphrase -
not currently used
+- SecurityTypes::TLSv1, // sslType
++ defaultSSLType, // sslType
+ 0,// transport flags
+ tlsCertificate, tlsPrivateKey,
+ cvm, // tls client verification mode
+@@ -1576,8 +1577,8 @@ ReproRunner::addTransports(bool
allTransportsSpecifyRecordRoute)
+ }
+ if (tlsPort)
+ {
+-if (mUseV4) mSipStack-addTransport(TLS, tlsPort, V4,
StunEnabled, Data::Empty, tlsDomain, Data::Empty, SecurityTypes::TLSv1, 0,
tlsCertificate, tlsPrivateKey, cvm, useEmailAsSIP);
+-if (mUseV6) mSipStack-addTransport(TLS, tlsPort, V6,
StunEnabled, Data::Empty, tlsDomain, Data::Empty, SecurityTypes::TLSv1, 0,
tlsCertificate, tlsPrivateKey, cvm, useEmailAsSIP);
++if (mUseV4) mSipStack-addTransport(TLS, tlsPort, V4,
StunEnabled, Data::Empty, tlsDomain, Data::Empty, defaultSSLType, 0,
tlsCertificate, tlsPrivateKey, cvm, useEmailAsSIP);
++if (mUseV6) mSipStack-addTransport(TLS, tlsPort, V6,
StunEnabled, Data::Empty, tlsDomain, Data::Empty, defaultSSLType, 0,
tlsCertificate, tlsPrivateKey, cvm, useEmailAsSIP);
+ }
+ if (wsPort)
+ {
+@@ -1586,13 +1587,13 @@ ReproRunner::addTransports(bool
allTransportsSpecifyRecordRoute)
+ }
+ if (wssPort)
+ {
+-if (mUseV4) mSipStack-addTransport(WSS, wssPort, V4,
StunEnabled, Data::Empty, tlsDomain, Data::Empty, SecurityTypes::TLSv1, 0,
tlsCertificate, tlsPrivateKey, cvm, useEmailAsSIP, basicWsConnectionValidator,
wsCookieContextFactory);
+-if (mUseV6) mSipStack-addTransport(WSS, wssPort, V6,
StunEnabled, Data::Empty, tlsDomain, Data::Empty, SecurityTypes::TLSv1, 0,
tlsCertificate, tlsPrivateKey, cvm, useEmailAsSIP, basicWsConnectionValidator,
wsCookieContextFactory
Bug#772634: resiprocate_1.9.7-2_amd64.changes REJECTED
On 09/12/14 14:04, Debian FTP Masters wrote: Version check failed: Your upload included the source package resiprocate, version 1.9.7-2, however unstable already has version 1.9.8-1. Uploads to unstable must have a higher version than present in unstable. Hi FTP team, Please assist me - I need to upload 1.9.7-2 to unstable as discussed with the release team Regards, Daniel -- 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/5486f43c.1010...@pocock.pro
Bug#772634: resiprocate_1.9.7-2_amd64.changes REJECTED
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/12/14 14:27, Holger Levsen wrote: Hi Daniel, On Dienstag, 9. Dezember 2014, Daniel Pocock wrote: Your upload included the source package resiprocate, version 1.9.7-2, however unstable already has version 1.9.8-1. Please assist me - I need to upload 1.9.7-2 to unstable as discussed with the release team You need to use an epoch (so 0:1.9.7-2 or maybe 1:1.9.7-2) or 1.9.8really1.9.7-1 - pick your poison :) And check with dpkg --compare-versions before uploading. Thanks for the feedback Holger. I tried this: resiprocate (1:1.9.7-2) unstable; urgency=medium and received a Processing email but no accepted/rejected notification -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJUhzq4AAoJEOm1uwJp1aqDzfsP/3XPPOecqCcoRjYJGOENyl8E d6uqzwAlT7k2j76d4Rzosg9JmtlkEmsCaOx4zi/iwPsO1DRAukyaHakpQxByGV9T BUtygzSQjigHooSY82dL/Ban602enZLFA6WowRBDZMQe1pIwJjToJ1eXUhJVw3gB AQbPrlToE/J5gh1J/Yuop5N5MA6+fhqiyVXk7MD+jTozW2tQXjeJJzPX1R7Fi53W BLRznUHYZ/B9YBRmHWp3SptVCOucwnbnfGEeXhx41XXnT9wXJEVxpbImCi9xVi46 UFCsJfRVP2tX09dxXtAN51nVx0cLleL+eFJVPeCv5BTooZIJKOEDXifL8bRKP9Nz g90R1/fCuffJbEWCKHVCgIO9uSXU617Ckex7PjBB6FeQvK1/GhVfMQHONtiRhZlZ WuSKql2/YiMfrpK5f+JFlq75aNN52H+qBRNGxjfYD+YexqF4chglx6bvNf5dDj6k WrTVBfViXC3qQry/L+mJEykaHZmDJZzInNF4CYv89fjyrt9xEaXM8aF6AjTEoRQe otEZqfevyqfzaoZd4Ap/47s5lMgWRQlhDFUKnSdV2RKP3KqO29D7ktGSaSyN4SOn IHdhiV8ZpBah56kM9uShafAICa7Q+UktgBYLOnDcrlh+zl5+iLwaqII3eE4Z6l1Q 4Q1nxz5hFUMfi/2pBNo7 =aP3z -END PGP SIGNATURE- -- 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/54873abb.1080...@pocock.pro
Bug#772634: resiprocate_1.9.7-2_amd64.changes REJECTED
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/12/14 19:20, Julien Cristau wrote: On Tue, Dec 9, 2014 at 19:08:59 +0100, Daniel Pocock wrote: On 09/12/14 14:27, Holger Levsen wrote: Hi Daniel, On Dienstag, 9. Dezember 2014, Daniel Pocock wrote: Your upload included the source package resiprocate, version 1.9.7-2, however unstable already has version 1.9.8-1. Please assist me - I need to upload 1.9.7-2 to unstable as discussed with the release team You need to use an epoch (so 0:1.9.7-2 or maybe 1:1.9.7-2) or 1.9.8really1.9.7-1 - pick your poison :) And check with dpkg --compare-versions before uploading. Thanks for the feedback Holger. I tried this: resiprocate (1:1.9.7-2) unstable; urgency=medium and received a Processing email but no accepted/rejected notification Dec 9 18:07:17 processing /resiprocate_1.9.7-2_amd64.changes Dec 9 18:07:17 /resiprocate_1.9.7-2_amd64.changes is already present on target host: Dec 9 18:07:17 sipdialer_1.9.7-2_amd64.deb Dec 9 18:07:17 Job resiprocate_1.9.7-2_amd64.changes removed. Don't reuse the same debian revision. That was another attempt to upload the same 1:1.9.7-2 artifacts I notice that it didn't put the epoch in the filenames but it is in the changes file 1:1.9.7-2 was originally uploaded at 14:01 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJUhz4bAAoJEOm1uwJp1aqDbXUP/23HOqzlMNNjyDnlOjdK2VNM deltGTPQkerVSIMUp93YuTADnK3DphMPu9h28INRSrMeuXE5n1J4Z8Edimiu7ajH UqRdLUXyGxuOwCxqFCye49jgda0JV1wVI5+tNjzr7j3/owF0Xrt3RlpHoJyZ+dCR wud1U/3QtQSJhCOEWC0E9fMrBOkcRDJdZSmIo6shqRLYCEbtE1fXKSbgH7fG9S+N n3hHKvqOC2XEG7Mu3jymYIdr9bQzvZwC2yGIZLtR79KoC7GjBOzx1M2XvZ7DI+a0 Zf7y7vIWYoC7RkI5RXEXNCQrM2kZpoQ41oMQM7b9v3mC16J5dr4Hk+4gY+kQ9eK9 /SVYAel4VQ1JtYloAA28HMhorQVRelm6HsV93gOmfTpdwcG4Bd6R6jMFh1nVRtFj KptFrZRjgaRMKMG4NuonQtwgythsrRTCcryvSB87Pgu0cyFtnNZv3b9JURQRFbFQ dCv3nhFZd/R2Al7ffdlwNsa9qSC0qptm9lrFZ24Eg2SDATuXyPmUXhTev4/D6kob gcIxZ0l5Unc4kMhPQT9hVK+KEjW5EGTI6Vn2VzC3QzskRV+MSmUIHevp+gjbqowC 1MDO8H+YTyeeAG2Mc2aQaxZ5POFP8QT7GYAVR7qh1arFrNlqn5Wyi99VG/URJbNl zPINT1dsOgnJYhd1H1FK =btHz -END PGP SIGNATURE- -- 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/54873e1b.9090...@pocock.pro
Bug#772634: resiprocate_1.9.7-2_amd64.changes REJECTED
Control: tags -1 - moreinfo On 09/12/14 20:08, Ivo De Decker wrote: Hi Daniel, On Tue, Dec 09, 2014 at 07:23:23PM +0100, Daniel Pocock wrote: Dec 9 18:07:17 processing /resiprocate_1.9.7-2_amd64.changes Dec 9 18:07:17 /resiprocate_1.9.7-2_amd64.changes is already present on target host: Dec 9 18:07:17 sipdialer_1.9.7-2_amd64.deb Dec 9 18:07:17 Job resiprocate_1.9.7-2_amd64.changes removed. Don't reuse the same debian revision. That was another attempt to upload the same 1:1.9.7-2 artifacts I notice that it didn't put the epoch in the filenames but it is in the changes file 1:1.9.7-2 was originally uploaded at 14:01 Julien suggested to try again with 1:1.9.7-3. Some tools get confused when there is both a 1.9.7-2 and a 1:1.9.7-2 (with the same filenames, as the epoch is not in the filename). Uploading -3 should avoid that issue. Also, if you want to upload 1.9.8 to experimental, it's probably best to version it as 1:1.9.8-2 to avoid the same issue. Ok, thanks for the feedback, 1:1.9.7-3 has been uploaded signed by the other key and I've pushed the subkey with the extended expiry. -- 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/5487585d.8060...@pocock.pro
Bug#772487: SSL 3.0 and older ciphers selected in applications
Hi all, I've made some changes to TLS code in reSIProcate - setting OpenSSL's SSL_OP_NO_SSLv3 by default when using SSLv23_method() - adding configuration options to override the options to SSL_CTX_set_options (as it is possible there will be some user with old VoIP hardware out there who wants SSL v3) - making the cipher list configurable in repro.config The release team didn't feel these things justify an unblock request[1]. Can anybody comment on this? Looking at the CVE details[2], it appears that some packages still support SSL v3 while I've heard many people just want to turn it off. Is it important for application developers to try and minimize the use of SSL v3 and older ciphers or will these things be phased out by changing the options centrally in the OpenSSL packages? I felt that by putting control of these things in the libresip API and the repro.config file it would help avoid situations where the package needs to be recompiled to deal with security patching and therefore reduce the burden on the security updates process. If it will help the release team, is there anybody from the security team who could review the changes in my debdiff? Regards, Daniel 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772487 2. https://security-tracker.debian.org/tracker/CVE-2014-3566 -- 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/54855e6d.9000...@pocock.pro
Bug#772487: unblock: resiprocate/1.9.8-1
On 07/12/14 22:08, Ivo De Decker wrote: tags 772487 wontfix thanks Hi, On Sun, Dec 07, 2014 at 07:13:35PM +0100, Daniel Pocock wrote: The debdiff is about 900 lines but this includes a lot of comments as I've explained what I was doing throughout the security code and about 30% of that is a new test case, testSecurity.cxx, to validate the new config string parsing. This type of change is not appropriate at this stage of the freeze. Sorry, but I have to deny this one. Can you please clarify what you mean by this type of change? This is very relevant to the security of the package when used on the public Internet, especially given the expected support lifetime of jessie. Not everybody uses it that way however so I didn't mark the repro bug as RC but I've filed an RC bug against libresiprocate because somebody using SSLv23_method may want the choice to eliminate SSL v3. I made the upstream release 1.9.8 myself (I am also one of the upstream developers) including only the changes necessary to resolve the issue and make the package more future-proof within jessie. I made these changes in such a way that it is ABI compatible and there is no need for a transition or recompilation of other packages. -- 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/54855fb7.8030...@pocock.pro
Bug#772487: SSL 3.0 and older ciphers selected in applications
On 08/12/14 10:20, Adam D. Barratt wrote: On Mon, 2014-12-08 at 09:16 +0100, Daniel Pocock wrote: [...] If it will help the release team, is there anybody from the security team who could review the changes in my debdiff? Note that debian-secur...@lists.debian.org is not a contact address for the security team. (Also I don't see anything in the nack mail that says it was related to being unable to review the debdiff.) I wasn't suggesting that was the cause for the nack email although I remember some discussion around the wheezy release that the size of diffs is considered a factor in unblock requests. I understand that sometimes the security team have made decisions about what should go through to stable, e.g. for the browser version updates and the security team are also getting involved if some vulnerability is found in future so I value their opinion on this particular case. The WebSocket transport (which includes TLS support) in packages like reSIProcate, Kamailio and Asterisk needs to remain interoperable with the browsers and the server side also needs to remain secure throughout the life of jessie so there are a range of reasons I'm asking about this. -- 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/54856fa5.8020...@pocock.pro
Bug#772487: SSL 3.0 and older ciphers selected in applications
On 08/12/14 11:12, Kurt Roeckx wrote: On Mon, Dec 08, 2014 at 09:16:45AM +0100, Daniel Pocock wrote: Hi all, I've made some changes to TLS code in reSIProcate - setting OpenSSL's SSL_OP_NO_SSLv3 by default when using SSLv23_method() This has no effect in jessie. SSLv2 and SSLv3 are disabled if you use the SSLv23_* methods. The only way to enable SSLv3 is to use the SSLv3_* methods. You should always use the SSLv23 method as those are the only that support more than 1 protocol version. Can you please clarify that - if somebody explicitly calls SSL_CTX_clear_options with SSL_OP_NO_SSLv3 will they get back support for SSLv3 in SSLv23_method? I would love to see people stopping the SSLv3 methods, and they have been removed in experimental. I'm also working on only having the SSLv23 method available. In VoIP, this is not so trivial. People have devices like IP phones and ISDN gateways to use on their LAN. Some of the older ones may not support anything more than SSL v3 very well. If these devices are used on a private VLAN then the risk of using old crypto is not the same as the risk on the public Internet so I prefer to give these people config options to support their hardware but disabled by default. Just one other point: if somebody is trying sending the client hello using SSL v2 record layer but indicating support for TLS v1.0, should TLSv1_method or SSLv23_method accept that? There is an example of it here: https://issues.asterisk.org/jira/browse/ASTERISK-13845 and it looks something like this: Secure Sockets Layer SSLv2 Record Layer: Client Hello ... Version: TLS 1.0 (0x0301) ... I've noticed that the reSIProcate code using TLSv1_method refuses to accept connections from peers like that. Should SSLv23_method support that even with v2 and v3 disabled? -- 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/54858094.6070...@pocock.pro
Bug#772487: SSL 3.0 and older ciphers selected in applications
On 08/12/14 12:36, Kurt Roeckx wrote: On Mon, Dec 08, 2014 at 11:42:28AM +0100, Daniel Pocock wrote: On 08/12/14 11:12, Kurt Roeckx wrote: On Mon, Dec 08, 2014 at 09:16:45AM +0100, Daniel Pocock wrote: Hi all, I've made some changes to TLS code in reSIProcate - setting OpenSSL's SSL_OP_NO_SSLv3 by default when using SSLv23_method() This has no effect in jessie. SSLv2 and SSLv3 are disabled if you use the SSLv23_* methods. The only way to enable SSLv3 is to use the SSLv3_* methods. You should always use the SSLv23 method as those are the only that support more than 1 protocol version. Can you please clarify that - if somebody explicitly calls SSL_CTX_clear_options with SSL_OP_NO_SSLv3 will they get back support for SSLv3 in SSLv23_method? No, the library doesn't support SSLv3 in combination with the SSLv23 method. Setting or clearing SSL_OP_NO_SSLv3 doesn't have any effect. Thanks for confirming that. I would love to see people stopping the SSLv3 methods, and they have been removed in experimental. I'm also working on only having the SSLv23 method available. In VoIP, this is not so trivial. People have devices like IP phones and ISDN gateways to use on their LAN. Some of the older ones may not support anything more than SSL v3 very well. If these devices are used on a private VLAN then the risk of using old crypto is not the same as the risk on the public Internet so I prefer to give these people config options to support their hardware but disabled by default. So why use SSL at all? Only for cases where people may already have it configured that way. It is not an issue for my own personal use cases. Just one other point: if somebody is trying sending the client hello using SSL v2 record layer but indicating support for TLS v1.0, should TLSv1_method or SSLv23_method accept that? I would expect that both should support that. With TLSv1_method and reSIProcate/OpenSSL on wheezy it fails with error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Error code = 336130315 file=s3_pkt.c line=348 There is an example of it here: https://issues.asterisk.org/jira/browse/ASTERISK-13845 and it looks something like this: Secure Sockets Layer SSLv2 Record Layer: Client Hello ... Version: TLS 1.0 (0x0301) ... I've noticed that the reSIProcate code using TLSv1_method refuses to accept connections from peers like that. Should SSLv23_method support that even with v2 and v3 disabled? Yes it should. -- 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/54859797.6070...@pocock.pro
Bug#772487: SSL 3.0 and older ciphers selected in applications
On 08/12/14 13:53, Kurt Roeckx wrote: On Mon, Dec 08, 2014 at 01:20:39PM +0100, Daniel Pocock wrote: Just one other point: if somebody is trying sending the client hello using SSL v2 record layer but indicating support for TLS v1.0, should TLSv1_method or SSLv23_method accept that? I would expect that both should support that. With TLSv1_method and reSIProcate/OpenSSL on wheezy it fails with error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Error code = 336130315 file=s3_pkt.c line=348 So I start an s_server with: openssl s_server -tls1 And then: openssl s_client: TLSv1 openssl s_client -tls1: TLSv1 I tried the s_server and s_client on both jessie and wheezy. This should just work. If both sides drop the -tls1 of course changes to TLSv1.2. But it really should always work, and if doesn't I'd argue that's a bug. But you say that it sends an SSLv2 compatible client hello. By default it shouldn't be doing that unless you change the ciphers suite to include SSLv2 ciphers and aren't using any extentions, and as far as I know you currently can't disable extentions in either wheez or jessie. It is the opposite - the remote system is sending the SSLv2 compatible client hello. The Debian/repro system is the server side. I have no idea what technology is in use in the remote/client system. If my server socket is using TLSv1_method it is rejecting the connection and logging those errors on my server: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Error code = 336130315 file=s3_pkt.c line=348 My server then sends TCP RST to the client -- 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/5485a904.4090...@pocock.pro
Bug#772487: SSL 3.0 and older ciphers selected in applications
On 08/12/14 18:58, Kurt Roeckx wrote: On Mon, Dec 08, 2014 at 02:35:00PM +0100, Daniel Pocock wrote: I have no idea what technology is in use in the remote/client system. If my server socket is using TLSv1_method it is rejecting the connection and logging those errors on my server: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Error code = 336130315 file=s3_pkt.c line=348 My server then sends TCP RST to the client So I can actually reproduce this with the s_client from squeeze, since that still generates an SSLv2 compatible client hello. That does fail talking to any server using the TLSv1 method but works talking to the SSLv23 method. Since I'm actually going to remove support for the TLSv1 method I don't intend to fix this. Will the TLSv1 method be removed in jessie or while jessie is still supported? If so, then applications like repro that use it by default will need to be patched. -- 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/5485ec69.2030...@pocock.pro
Bug#772487: SSL 3.0 and older ciphers selected in applications
On 08/12/14 19:25, Kurt Roeckx wrote: On Mon, Dec 08, 2014 at 07:22:33PM +0100, Daniel Pocock wrote: Will the TLSv1 method be removed in jessie or while jessie is still supported? This is something post jessie. Is it something that is going to happen with Ubuntu releases next year (e.g. April 2015)? If so, it means that the repro package in jessie won't talk to a repro package in Ubuntu. -- 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/5485f12e.9090...@pocock.pro
Bug#772487: SSL 3.0 and older ciphers selected in applications
On 08/12/14 20:06, Kurt Roeckx wrote: On Mon, Dec 08, 2014 at 07:42:54PM +0100, Daniel Pocock wrote: Is it something that is going to happen with Ubuntu releases next year (e.g. April 2015)? If so, it means that the repro package in jessie won't talk to a repro package in Ubuntu. I think there is some misunderstanding. People have been using methods like SSLv3_* and TLSv1_* while they should use SSLv23_*. SSLv3_* only support SSL 3.0, TLSv1_* only support TLS 1.0, it does not support SSL 3.0 or TLS 1.1. SSLv23_* on the other hand supports all versions supported by library (but see below). The intention is to drop all methods that only support 1 protocol version and instead have only methods that support all versions (SSLv23). The library in jessie supports TLS 1.0 to TLS 1.2. However the the SSLv3 methods still exist in jessie so you can still talk SSL 3.0 in jessie. However the SSLv23 methods do not support SSL 3.0 in jessie anymore. They still supports SSL 3.0 in wheezy. That means if one side uses SSLv3_* and the the verion in jessie or later use SSLv23_* they will not talk to each other. And there are packages that have been fixed to stop using the SSLv3_* methods in jessie and they will not talk to the version in wheezy. The versie in wheezy really should also get fixed to use the SSLv23_* method. The SSLv3_* method has been removed in experimental and the TLSv1_* method will also be removed post jessie but I have no timeframe for that. But everybody really should only use the SSLv23_* methods. But the removal of the TLSv1_* methods should not cause any issue if you replace it by the SSLv23_* methods since there currently are no plans to drop support for TLS 1.0. What we have right now in jessie (and wheezy) is hard-coded to use TLSv1_method. The v1.9.8-1 upload to unstable, which will also propagate to the next Ubuntu and will also be uploaded to Fedora very soon, uses SSLv23_method If I understand your reply correctly, the version in Ubuntu and Fedora will still talk TLS 1.0 with the version now waiting in jessie? Do you believe it would be reasonable for me to request a smaller unblock that just changes the call TLSv1_method to SSLv23_method? -- 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/5485f961.8080...@pocock.pro
Bug#772487: SSL 3.0 and older ciphers selected in applications
On 08/12/14 21:16, Kurt Roeckx wrote: On Mon, Dec 08, 2014 at 08:17:53PM +0100, Daniel Pocock wrote: If I understand your reply correctly, the version in Ubuntu and Fedora will still talk TLS 1.0 with the version now waiting in jessie? Yes. Do you believe it would be reasonable for me to request a smaller unblock that just changes the call TLSv1_method to SSLv23_method? That depends on wether it's acting as client or server. If it's acting as server I say yes. If it's acting as client I suggest you also have a way to turn off TLS 1.2. I understand that it needs to be able to talk to many different things and TLS 1.2 has has been breaking things it shouldn't and you already indicated problems with some products. But maybe it just needs to be used for a while with the SSLv23 method to see if there are problems or not. It plays a few roles: a) repro acts as a WebSocket server (for WebRTC) b) in federated SIP, repro acts as both server and client c) in a phone system, repro acts as server (e.g. my home phone system has some Polycom desk phones, Jitsi with JDK1.7 and Lumicall on Android as clients) d) people use the reSIProcate library in all kinds of products where it is client (e.g. in Counterpath softphones) or server (e.g. in some commercial Session Border Controllers). All of these use cases are supported by the Debian packages. For the SIP proxy, repro, the smallest possible change to use SSLv23 as default would involve touching 6 lines of code in repro/ReproRunner.cxx, replacing SecurityTypes::TLSv1 with SecurityTypes::SSLv23 on each. As well as changing the server behavior, this also has the effect of enabling TLS 1.2 when acting as client in a federated SIP connection. For other uses of the library it is up to the developer to select SSLv23 when they call SipStack::addTransport -- 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/548609e1.7040...@pocock.pro
Bug#772483: unblock: avis/1.2.2-4
Package: release.debian.org
User: release.debian@packages.debian.org
UserTags: unblock
This has just been uploaded to unstable
The main reason for this unblock request:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772188
It introduces a patch under debian/patches to remove bashisms from a
script in the package.
The debdiff is attached
diff -Nru avis-1.2.2/debian/changelog avis-1.2.2/debian/changelog
--- avis-1.2.2/debian/changelog 2014-09-14 21:20:39.0 +0200
+++ avis-1.2.2/debian/changelog 2014-12-07 08:56:49.0 +0100
@@ -1,3 +1,9 @@
+avis (1.2.2-4) unstable; urgency=medium
+
+ * Add patch for bashisms in avisd. (Closes: #772188)
+
+ -- Daniel Pocock dan...@pocock.pro Sun, 07 Dec 2014 08:56:15 +0100
+
avis (1.2.2-3) unstable; urgency=low
* Update VCS URLs.
diff -Nru avis-1.2.2/debian/patches/0003-avis-no-bashisms.patch
avis-1.2.2/debian/patches/0003-avis-no-bashisms.patch
--- avis-1.2.2/debian/patches/0003-avis-no-bashisms.patch 1970-01-01
01:00:00.0 +0100
+++ avis-1.2.2/debian/patches/0003-avis-no-bashisms.patch 2014-12-07
08:53:19.0 +0100
@@ -0,0 +1,36 @@
+diff --git a/server/bin/avisd b/server/bin/avisd
+index 0b76fdb..02bdfd2 100755
+--- a/server/bin/avisd
b/server/bin/avisd
+@@ -20,20 +20,18 @@ fi
+
+ usage ()
+ {
+- local NL=$'\x0a'
+- local help=\
+- Usage: $0 [-h] [-v] [-vv] [-p port] [-c file] $NL\
+-[-daemon] [-pidfile file] [-logfile file] $NL\
++ cat EOF
++ Usage: $0 [-h] [-v] [-vv] [-p port] [-c file]
++[-daemon] [-pidfile file] [-logfile file]
+
+- -h : This text$NL\
+- -v and -vv : Increase verbosity$NL\
+- -p port : Set port to listen on$NL\
+- -c file : Load config from file$NL\
+- -daemon : Run as daemon$NL\
+- -pidfile file: Output process ID to file$NL\
+- -logfile file: Log output to file (only with -daemon)$NL
+-
+- echo $help 2
++ -h : This text
++ -v and -vv : Increase verbosity
++ -p port : Set port to listen on
++ -c file : Load config from file
++ -daemon : Run as daemon
++ -pidfile file: Output process ID to file
++ -logfile file: Log output to file (only with -daemon)
++EOF
+ }
+
+ while [ $# -gt 0 ]; do
diff -Nru avis-1.2.2/debian/patches/series avis-1.2.2/debian/patches/series
--- avis-1.2.2/debian/patches/series2013-08-08 14:22:46.0 +0200
+++ avis-1.2.2/debian/patches/series2014-12-07 08:54:38.0 +0100
@@ -1,2 +1,3 @@
0001-Use-regular-Jar-task-instead-of-JarX.patch
0002-Look-for-JAR-in-correct-location.patch
+0003-avis-no-bashisms.patch
Bug#772484: unblock: ganglia-modules-linux/1.3.6-1
Package: release.debian.org User: release.debian@packages.debian.org UserTags: unblock This has just been uploaded to unstable The main reason for this unblock request: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772481 The upstream 1.3.6 just changes one line, using b_avail instead of b_free This returns the free space in a way that people are more likely to expect. The debdiff excludes autotools stuff, exact command used: debdiff ganglia-modules-linux_1.3.5-1.dsc ganglia-modules-linux_1.3.6-1.dsc | filterdiff -x '*/aclocal.m4' -x '*/config.*' -x '*/configure' -x '*/depcomp' -x '*/*.in' -x '*/install-sh' -x '*/ltmain.sh' -x '*/m4/*' -x '*/missing' /tmp/ganglia-modules-linux-1.3.6-1.debdiff diff -Nru ganglia-modules-linux-1.3.5/configure ganglia-modules-linux-1.3.6/configure diff -Nru ganglia-modules-linux-1.3.5/configure.ac ganglia-modules-linux-1.3.6/configure.ac --- ganglia-modules-linux-1.3.5/configure.ac2014-11-30 13:59:08.0 +0100 +++ ganglia-modules-linux-1.3.6/configure.ac2014-12-07 18:09:32.0 +0100 @@ -14,7 +14,7 @@ dnlYou should have received a copy of the GNU General Public License dnlalong with this program. If not, see http://www.gnu.org/licenses/. -AC_INIT(ganglia-modules-linux,1.3.5) +AC_INIT(ganglia-modules-linux,1.3.6) AC_CONFIG_SRCDIR(example/mod_example.c) AM_INIT_AUTOMAKE diff -Nru ganglia-modules-linux-1.3.5/debian/changelog ganglia-modules-linux-1.3.6/debian/changelog --- ganglia-modules-linux-1.3.5/debian/changelog2014-11-30 14:13:26.0 +0100 +++ ganglia-modules-linux-1.3.6/debian/changelog2014-12-07 18:15:02.0 +0100 @@ -1,3 +1,10 @@ +ganglia-modules-linux (1.3.6-1) unstable; urgency=low + + * New upstream release. + * Use b_avail instead of b_free for free space. (Closes: #772481) + + -- Daniel Pocock dan...@pocock.pro Sun, 07 Dec 2014 18:14:22 +0100 + ganglia-modules-linux (1.3.5-1) unstable; urgency=low * New upstream release. diff -Nru ganglia-modules-linux-1.3.5/fs/mod_fs.c ganglia-modules-linux-1.3.6/fs/mod_fs.c --- ganglia-modules-linux-1.3.5/fs/mod_fs.c 2014-11-30 13:57:39.0 +0100 +++ ganglia-modules-linux-1.3.6/fs/mod_fs.c 2014-11-30 16:12:19.0 +0100 @@ -146,7 +146,7 @@ } total_blocks = svfs.f_blocks; -blocks_free = svfs.f_bfree; +blocks_free = svfs.f_bavail; val.f = (float)100.0 * blocks_free / total_blocks; return val;
Bug#772487: unblock: resiprocate/1.9.8-1
Package: release.debian.org User: release.debian@packages.debian.org UserTags: unblock This has just been uploaded to unstable The main reason for this unblock request: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772480 This improves administrative control (in the /etc/repro/repro.config) over the TLS options. It means that during the life of jessie (up to perhaps 2017/2018) if more ciphers or protocols become vulnerable the administrator can disable them just by changing the config. The update enables TLS v1.1 and v1.2 while disabling SSL v3.0 by default. The configuration options also let the administrator bring back SSL v3.0 if really needed. The debdiff is about 900 lines but this includes a lot of comments as I've explained what I was doing throughout the security code and about 30% of that is a new test case, testSecurity.cxx, to validate the new config string parsing. The debdiff is attached, it was generated with filterdiff to remove autotools stuff: debdiff resiprocate_1.9.7-1.dsc resiprocate_1.9.8-1.dsc | filterdiff -x '*/aclocal.m4' -x '*/config.*' -x '*/configure' -x '*/depcomp' -x '*/*.in' -x '*/install-sh' -x '*/ltmain.sh' -x '*/m4/*' -x '*/missing' -x '*/repro/repro.config' -x '*/resiprocate.spec' /tmp/resiprocate-1.9.8-1.debdiff diff -Nru resiprocate-1.9.7/ChangeLog resiprocate-1.9.8/ChangeLog --- resiprocate-1.9.7/ChangeLog 2014-05-31 12:47:51.0 +0200 +++ resiprocate-1.9.8/ChangeLog 2014-12-07 17:48:36.0 +0100 @@ -1,4 +1,11 @@ = Release Notes v 1.9 = +==1.9.8 Changes== +resip/stack: add static fields on BaseSecurity for setting OpenSSL CTX options +resip/stack: explicitly disable SSLv2 and SSLv3 by default when using SSLv23 +resip/stack: allow application to provide OpenSSL certificate verification callback +repro: change default OpenSSL method from TLSv1_method to SSLv23_method (enables TLS v1.1 and v1.2) +repro: add configuration options OpenSSLCTXSetOptions and OpenSSLCTXClearOptions to control OpenSSL CTX options +repro: add configuration OpenSSLCipherList to manually configure the OpenSSL cipher list ==1.9.7 Changes== rpm: Indicate that b2bua package is obsolete resip/stack: TlsConnection: correctly handle OpenSSL error queue after SSL_read diff -Nru resiprocate-1.9.7/configure resiprocate-1.9.8/configure diff -Nru resiprocate-1.9.7/configure.ac resiprocate-1.9.8/configure.ac --- resiprocate-1.9.7/configure.ac 2014-05-31 12:47:51.0 +0200 +++ resiprocate-1.9.8/configure.ac 2014-12-07 17:48:36.0 +0100 @@ -1,5 +1,5 @@ -AC_INIT(resiprocate,1.9.7) +AC_INIT(resiprocate,1.9.8) AC_CONFIG_SRCDIR(repro/repro.cxx) SO_RELEASE=`echo $PACKAGE_VERSION | cut -f1,2 -d.` diff -Nru resiprocate-1.9.7/debian/changelog resiprocate-1.9.8/debian/changelog --- resiprocate-1.9.7/debian/changelog 2014-05-31 12:51:11.0 +0200 +++ resiprocate-1.9.8/debian/changelog 2014-12-07 18:08:40.0 +0100 @@ -1,3 +1,10 @@ +resiprocate (1.9.8-1) unstable; urgency=medium + + * New upstream release. + * Improve administrative control over TLS. (Closes: #772480) + + -- Daniel Pocock dan...@pocock.pro Sun, 07 Dec 2014 18:08:04 +0100 + resiprocate (1.9.7-1) unstable; urgency=medium * New upstream release. diff -Nru resiprocate-1.9.7/debian/conf/repro.config resiprocate-1.9.8/debian/conf/repro.config --- resiprocate-1.9.7/debian/conf/repro.config 2014-05-31 12:47:22.0 +0200 +++ resiprocate-1.9.8/debian/conf/repro.config 2014-12-07 18:31:38.0 +0100 @@ -89,6 +89,24 @@ #SIP messages coming from the peer TLSClientVerification = None +# The SSL or TLS connection mode to use +# SSL v2 and v3 are deprecated and SSL v2 is particularly insecure +# and should be avoided. +# TLSv1 was the default up to and including reSIProcate v1.9.7. +# With the setting TLSv1, only TLS v1.0 could be used +# and not TLS v1.1 or newer versions. +# The value SSLv23 works as a catch-all and gives the potential +# to allow all the SSL and TLS versions. Despite the name SSLv23, it +# does not allow SSL v2.0 or v3.0 if the SSL_CTX_set_options method is used +# to prohibit them. +# See the page https://www.openssl.org/docs/ssl/SSL_CTX_new.html +# for a more detailed discussion of how repro will behave when +# using the values SSLv23 or TLSv1 here. +# For optimal security and compatibility, set SSLv23 here and make sure +# that the parameter OpenSSLCTXSetOptions (later in repro.config) +# contains the values SSL_OP_NO_SSLv2 and SSL_OP_NO_SSLv3 +TLSConnectionMethod = SSLv23 + # Whether we accept the subjectAltName email address as if it was a SIP # address (when checking the validity of a client certificate) # Very few commercial CAs offer support for SIP addresses in subjectAltName @@ -109,6 +127,7 @@ # TransportNumTlsCertificate = TLSCertificate - only for TLS, DTLS or WSS # TransportNumTlsPrivateKey = TLSPrivateKey - only for TLS, DTLS or WSS # TransportNumTlsClientVerification = 'None'|'Optional'|'Mandatory' - default
Bug#769138: unblock: dlz-ldap-enum/1.0.3-1 - uploaded
Control: -1 - moreinfo
The bind9 package was fixed (now includes the required header file
dlz_dlopen.h)
I've uploaded dlz-ldap-enum v1.0.3-1 to sid and it builds OK now using
the new bind9 dev package, please approve the unblock.
https://buildd.debian.org/status/package.php?p=dlz-ldap-enumsuite=unstable
The debdiff is attached
The debdiff excludes autotools files and also one renamed file (an
embedded copy of the dlz_dlopen.h from bind 9.8.x, not used in the build
any more)
$ debdiff dlz-ldap-enum_1.0.2-2.dsc dlz-ldap-enum_1.0.3-1.dsc |
filterdiff -x '*/aclocal.m4' -x '*/config.*' -x '*/configure' -x
'*/depcomp' -x '*/*.in' -x '*/install-sh' -x '*/ltmain.sh' -x '*/m4/*'
-x '*/missing' -x '*/*dlz_dlopen.h' /tmp/dlz-ldap-enum-1.0.3-1.debdiff
diff -Nru dlz-ldap-enum-1.0.2/aclocal.m4 dlz-ldap-enum-1.0.3/aclocal.m4
diff -Nru dlz-ldap-enum-1.0.2/bind98_dlz_dlopen.h
dlz-ldap-enum-1.0.3/bind98_dlz_dlopen.h
diff -Nru dlz-ldap-enum-1.0.2/config.h.in dlz-ldap-enum-1.0.3/config.h.in
diff -Nru dlz-ldap-enum-1.0.2/config.sub dlz-ldap-enum-1.0.3/config.sub
diff -Nru dlz-ldap-enum-1.0.2/configure dlz-ldap-enum-1.0.3/configure
diff -Nru dlz-ldap-enum-1.0.2/configure.ac dlz-ldap-enum-1.0.3/configure.ac
--- dlz-ldap-enum-1.0.2/configure.ac2012-05-17 23:41:39.0 +0200
+++ dlz-ldap-enum-1.0.3/configure.ac2014-11-11 17:29:34.0 +0100
@@ -1,10 +1,10 @@
dnldlz-ldap-enum: bind9 DLZ module for using an LDAP database to answer
dnl ENUM queries over DNS
-dnlCopyright (C) 2012 Daniel Pocock
+dnlCopyright (C) 2012-2014 Daniel Pocock
dnl
dnlPlease see the COPYING file for license terms
-AC_INIT(dlz-ldap-enum,1.0.2)
+AC_INIT(dlz-ldap-enum,1.0.3)
AC_CONFIG_SRCDIR(dlz_ldap_enum_driver.c)
AM_INIT_AUTOMAKE
@@ -19,6 +19,11 @@
AC_PROG_LIBTOOL
+AC_ARG_ENABLE(bind99,
+[ --enable-bind99 Enable building for bind9 9.9.x and later],
+ [AC_DEFINE([BIND_9_9], , [Indicates we are compiling for bind9 9.9 or
later])],
+ [])
+
AC_OUTPUT(Makefile)
diff -Nru dlz-ldap-enum-1.0.2/debian/changelog
dlz-ldap-enum-1.0.3/debian/changelog
--- dlz-ldap-enum-1.0.2/debian/changelog2014-09-14 10:27:58.0
+0200
+++ dlz-ldap-enum-1.0.3/debian/changelog2014-11-11 17:47:04.0
+0100
@@ -1,3 +1,10 @@
+dlz-ldap-enum (1.0.3-1) unstable; urgency=medium
+
+ * New upstream release.
+ * dlz_lookup function updated for bind9 9.9.x. (Closes: #769134)
+
+ -- Daniel Pocock dan...@pocock.pro Tue, 11 Nov 2014 17:38:11 +0100
+
dlz-ldap-enum (1.0.2-2) unstable; urgency=low
* Update maintainer and VCS details.
diff -Nru dlz-ldap-enum-1.0.2/debian/rules dlz-ldap-enum-1.0.3/debian/rules
--- dlz-ldap-enum-1.0.2/debian/rules2014-10-26 07:06:43.0 +0100
+++ dlz-ldap-enum-1.0.3/debian/rules2014-11-11 17:37:10.0 +0100
@@ -11,10 +11,7 @@
# Add here any variable or target overrides you need.
-DLZ_DLOPEN_H=/usr/include/dns/dlz_dlopen.h
-ifeq ($(readlink $(DLZ_DLOPEN_H)),)
-CPPFLAGS:=-DUSE_COPIED_DLZ_DLOPEN_H
-endif
+DEB_CONFIGURE_EXTRA_FLAGS = --enable-bind99
binary-fixup/dlz-ldap-enum::
sed -i /dependency_libs/ s/'.*'/''/ `find debian/dlz-ldap-enum -name
'*.la'`
diff -Nru dlz-ldap-enum-1.0.2/depcomp dlz-ldap-enum-1.0.3/depcomp
diff -Nru dlz-ldap-enum-1.0.2/dlz_dlopen.h dlz-ldap-enum-1.0.3/dlz_dlopen.h
diff -Nru dlz-ldap-enum-1.0.2/dlz_ldap_enum_driver.c
dlz-ldap-enum-1.0.3/dlz_ldap_enum_driver.c
--- dlz-ldap-enum-1.0.2/dlz_ldap_enum_driver.c 2012-05-17 16:36:27.0
+0200
+++ dlz-ldap-enum-1.0.3/dlz_ldap_enum_driver.c 2014-11-11 17:29:34.0
+0100
@@ -117,6 +117,10 @@
int default_ttl;
} ldap_instance_t;
+#ifdef BIND_9_9
+isc_mem_t *ns_g_mctx = NULL;
+#endif
+
/*
* Private methods
*/
@@ -998,8 +1002,15 @@
}
isc_result_t
+#ifndef BIND_9_9
dlz_lookup(const char *zone, const char *name,
void *dbdata, dns_sdlzlookup_t *lookup)
+#else
+dlz_lookup(const char *zone, const char *name,
+void *dbdata, dns_sdlzlookup_t *lookup,
+dns_clientinfomethods_t *methods,
+dns_clientinfo_t *clientinfo)
+#endif
{
isc_result_t result;
@@ -1023,6 +1034,14 @@
int protocol;
int method;
+ result = isc_mem_create(0, 0, ns_g_mctx);
+ if (result != ISC_R_SUCCESS) {
+ isc_log_write(dns_lctx, DNS_LOGCATEGORY_DATABASE,
+ DNS_LOGMODULE_DLZ, ISC_LOG_ERROR,
+ Memory init failed);
+ return (result);
+ }
+
#ifdef ISC_PLATFORM_USETHREADS
/* if multi-threaded, we need a few extra variables. */
int dbcount;
diff -Nru dlz-ldap-enum-1.0.2/dlz_ldap_enum_driver.h
dlz-ldap-enum-1.0.3/dlz_ldap_enum_driver.h
--- dlz-ldap-enum-1.0.2/dlz_ldap_enum_driver.h 2012-05-17 16:45:21.0
+0200
+++ dlz-ldap-enum-1.0.3/dlz_ldap_enum_driver.h 2014-11-11 17:29:34.0
+0100
@@ -40,10 +40,13 @@
#include dns/dlz_dlopen.h
#else
Bug#771524: unblock: ganglia-modules-linux/1.3.5-1
Package: release.debian.org
User: release.debian@packages.debian.org
UserTags: unblock
This has just been uploaded to unstable
The main reason for this unblock request:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771521
It is based on new upstream release 1.3.5 which tidies up some other
small things too:
- clarification of original license terms in copyright (some code
started as BSD, project is GPL)
- remove a #ifdef LINUX (the package is only intended for Linux, as the
name implies)
- add a metric for percentage free
The debdiff excludes autotools stuff, exact command used:
debdiff ganglia-modules-linux_1.3.4-7.dsc
ganglia-modules-linux_1.3.5-1.dsc | filterdiff -x '*/aclocal.m4' -x
'*/config.*' -x '*/configure' -x '*/depcomp' -x '*/*.in' -x
'*/install-sh' -x '*/ltmain.sh' -x '*/m4/*' -x '*/missing'
/tmp/ganglia-modules-linux-1.3.5-1.debdiff
diff -Nru ganglia-modules-linux-1.3.4/aclocal.m4
ganglia-modules-linux-1.3.5/aclocal.m4
diff -Nru ganglia-modules-linux-1.3.4/config.guess
ganglia-modules-linux-1.3.5/config.guess
diff -Nru ganglia-modules-linux-1.3.4/config.sub
ganglia-modules-linux-1.3.5/config.sub
diff -Nru ganglia-modules-linux-1.3.4/configure
ganglia-modules-linux-1.3.5/configure
diff -Nru ganglia-modules-linux-1.3.4/configure.ac
ganglia-modules-linux-1.3.5/configure.ac
--- ganglia-modules-linux-1.3.4/configure.ac2012-04-10 18:50:07.0
+0200
+++ ganglia-modules-linux-1.3.5/configure.ac2014-11-30 13:59:08.0
+0100
@@ -14,7 +14,7 @@
dnlYou should have received a copy of the GNU General Public License
dnlalong with this program. If not, see http://www.gnu.org/licenses/.
-AC_INIT(ganglia-modules-linux,1.3.4)
+AC_INIT(ganglia-modules-linux,1.3.5)
AC_CONFIG_SRCDIR(example/mod_example.c)
AM_INIT_AUTOMAKE
diff -Nru ganglia-modules-linux-1.3.4/COPYING
ganglia-modules-linux-1.3.5/COPYING
--- ganglia-modules-linux-1.3.4/COPYING 2012-03-11 08:15:45.0 +0100
+++ ganglia-modules-linux-1.3.5/COPYING 2012-04-13 12:59:08.0 +0200
@@ -1,5 +1,7 @@
-
ganglia-modules-linux: modules for collecting metrics on Linux
+Copyright (C) 2007 Brad Nicholes, Novell (BSD license)
+Copyright (C) 2008 JB Kim (BSD license)
Copyright (C) 2011 Daniel Pocock
This program is free software: you can redistribute it and/or modify
@@ -25,11 +27,11 @@
example module) have been copied as-is from the main Ganglia
distribution and retain the original BSD-like copyright
- the contents of the `multicpu' directory are loosely based on
- the module contributed to the main Ganglia distribution by
- Brad Nicholes (bnicholes novell.com)
+ the module contributed (under a BSD license) to the main Ganglia
+ distribution by Brad Nicholes (bnicholes novell.com)
- the contents of the `io' directory are based on the
- module contributed to the Ganglia mailing list by JB Kim
- (jbremnant gmail.com) adapted to resemble the metric names
+ module contributed to the Ganglia mailing list (under a BSD license)
+ by JB Kim (jbremnant gmail.com) adapted to resemble the metric names
used in ganglia-modules-solaris
- the modules implement the Ganglia metric module interface.
Ganglia is distributed under a BSD-like license at http://ganglia.info
diff -Nru ganglia-modules-linux-1.3.4/debian/changelog
ganglia-modules-linux-1.3.5/debian/changelog
--- ganglia-modules-linux-1.3.4/debian/changelog2014-09-14
10:22:01.0 +0200
+++ ganglia-modules-linux-1.3.5/debian/changelog2014-11-30
14:13:26.0 +0100
@@ -1,3 +1,11 @@
+ganglia-modules-linux (1.3.5-1) unstable; urgency=low
+
+ * New upstream release.
+ * Add a free space percentage metric.
+ * Fix truncation of name for root filesystem metric. (Closes: #771521)
+
+ -- Daniel Pocock dan...@pocock.pro Sun, 30 Nov 2014 14:04:33 +0100
+
ganglia-modules-linux (1.3.4-7) unstable; urgency=low
* Migrate from collab-maint to pkg-monitoring.
diff -Nru ganglia-modules-linux-1.3.4/depcomp
ganglia-modules-linux-1.3.5/depcomp
diff -Nru ganglia-modules-linux-1.3.4/example/Makefile.in
ganglia-modules-linux-1.3.5/example/Makefile.in
diff -Nru ganglia-modules-linux-1.3.4/fs/Makefile.in
ganglia-modules-linux-1.3.5/fs/Makefile.in
diff -Nru ganglia-modules-linux-1.3.4/fs/mod_fs.c
ganglia-modules-linux-1.3.5/fs/mod_fs.c
--- ganglia-modules-linux-1.3.4/fs/mod_fs.c 2012-03-11 08:15:45.0
+0100
+++ ganglia-modules-linux-1.3.5/fs/mod_fs.c 2014-11-30 13:57:39.0
+0100
@@ -128,6 +128,31 @@
}
+static g_val_t fs_free_func (fs_info_t *fs)
+{
+g_val_t val;
+
+struct statvfs svfs;
+unsigned long blocksize;
+fsblkcnt_t blocks_free;
+fsblkcnt_t total_blocks;
+
+val.f = (float) NAN;
+
+if (statvfs(fs-mount_point, svfs)) {
+/* Ignore funky devices
Bug#769583: unblock: bind9/ 9.9.5 with patch or 9.9.6?
On 21/11/14 18:58, Niels Thykier wrote:
On 2014-11-17 23:43, LaMont Jones wrote:
[...]
Again, without actually looking at it, I'm inclined to agree. 87k
lines this late in the process is too many.
I'll get a patch together for 9.9.5, but it may be wednesday before I have
it uploaded to sid, and a diff sent to you guys.
lamont
Hi LaMont,
Any news on this upload? :)
~Niels
Hi LaMont,
I've prepared an NMU, the debdiff is attached and I am happy to upload
it if you like
Regards,
Daniel
diff -u bind9-9.9.5.dfsg/debian/changelog bind9-9.9.5.dfsg/debian/changelog
--- bind9-9.9.5.dfsg/debian/changelog
+++ bind9-9.9.5.dfsg/debian/changelog
@@ -1,3 +1,10 @@
+bind9 (1:9.9.5.dfsg-5.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Ensure dlz_dlopen.h is installed. (Closes: #769117)
+
+ -- Daniel Pocock dan...@pocock.pro Fri, 28 Nov 2014 07:49:27 +0100
+
bind9 (1:9.9.5.dfsg-5) unstable; urgency=medium
* Avoid libnsl dependency on non-linux architectures. Closes: #766430
diff -u bind9-9.9.5.dfsg/debian/rules bind9-9.9.5.dfsg/debian/rules
--- bind9-9.9.5.dfsg/debian/rules
+++ bind9-9.9.5.dfsg/debian/rules
@@ -126,6 +126,7 @@
dh_installdirs
$(MAKE) -C export install DESTDIR=`pwd`/debian/bind9
$(MAKE) install DESTDIR=`pwd`/debian/bind9
+ install -m 644 -o root -g root ./lib/dns/include/dns/dlz_dlopen.h
debian/bind9/usr/include/dns/dlz_dlopen.h
rm -rf debian/bind9/usr/etc
find debian/bind9 -name \*.la -execdir rm -f {} \;
mkdir -p debian/bind9/lib/$(DEB_HOST_MULTIARCH)
Bug#771304: unblock: jscommunicator/2.0.3-1
Package: release.debian.org
User: release.debian@packages.debian.org
UserTags: unblock
The main reason for this unblock request:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771299
This ensures that users can mix-and-match JSCommunicator with newer
versions of JsSIP. This is the change to JSCommManager.js in the debdiff.
The debdiff also includes changes to the debian/copyright and upstream
AUTHORS files to add the translators.
diff -Nru jscommunicator-2.0.1/AUTHORS jscommunicator-2.0.3/AUTHORS
--- jscommunicator-2.0.1/AUTHORS2014-11-08 20:03:43.0 +0100
+++ jscommunicator-2.0.3/AUTHORS2014-11-28 11:06:08.0 +0100
@@ -1,12 +1,20 @@
-Daniel Pocock danielpocock.com
-Juliana Louback julianalouback.com
-Christian Henz github.com/chenz
-Jeroen Massar jeroen.massar.ch
-elprincipe github.com/elprincipe
-Yehuda Korotkin github.com/yedako
+Daniel Pocock http://danielpocock.com
+Juliana Louback http://julianalouback.com
+Christian Henz https://github.com/chenz
+Jeroen Massar http://jeroen.massar.ch
+elprincipe https://github.com/elprincipe
+Yehuda Korotkin https://github.com/yedako
Carla Araos carlaaraos.com
-aavia github.com/aavia
-mirazusman github.com/mirazusman
-tehilazi github.com/tehilazi
-Matías A. Bellone github.com/toote
-tami4 github.com/tami4
+aavia https://github.com/aavia
+mirazusman https://github.com/mirazusman
+tehilazi https://github.com/tehilazi
+Matías A. Bellone https://github.com/toote
+tami4 https://github.com/tami4
+Christian Henz chrh...@gmx.de
+Dariusz Dwornikowski dariusz.dwornikow...@cs.put.poznan.pl
+Ivan Masár heli...@centrum.sk
+Martin Hristov martinhris...@abv.bg
+Matías A. Bellone matiasbellone+l...@gmail.com
+Miguel Ángel Molina ssl...@gmail.com
+Thomas Vincent tho...@vinc-net.fr
+timothymctim timothymc...@users.noreply.github.com
diff -Nru jscommunicator-2.0.1/debian/changelog
jscommunicator-2.0.3/debian/changelog
--- jscommunicator-2.0.1/debian/changelog 2014-11-08 22:18:54.0
+0100
+++ jscommunicator-2.0.3/debian/changelog 2014-11-28 12:22:24.0
+0100
@@ -1,3 +1,11 @@
+jscommunicator (2.0.3-1) unstable; urgency=high
+
+ * New upstream release.
+ * Support for JsSIP 'confirmed' event. (Closes: #771299)
+ * Update copyright, add translators.
+
+ -- Daniel Pocock dan...@pocock.pro Fri, 28 Nov 2014 11:09:40 +0100
+
jscommunicator (2.0.1-1) unstable; urgency=medium
* New upstream release.
diff -Nru jscommunicator-2.0.1/debian/copyright
jscommunicator-2.0.3/debian/copyright
--- jscommunicator-2.0.1/debian/copyright 2014-11-05 22:09:49.0
+0100
+++ jscommunicator-2.0.3/debian/copyright 2014-11-28 12:25:48.0
+0100
@@ -7,6 +7,27 @@
2014, Juliana Louback http://julianalouback.com
License: GPL-2+
+Files: internationalization/*
+Copyright: 2014, Christian Henz https://github.com/chenz
+ 2014, Jeroen Massar http://jeroen.massar.ch
+ 2014, elprincipe https://github.com/elprincipe
+ 2014, Yehuda Korotkin https://github.com/yedako
+ 2014, Carla Araos http://carlaaraos.com
+ 2014, aavia https://github.com/aavia
+ 2014, mirazusman https://github.com/mirazusman
+ 2014, tehilazi https://github.com/tehilazi
+ 2014, Matías A. Bellone https://github.com/toote
+ 2014, tami4 https://github.com/tami4
+ 2014, Christian Henz chrh...@gmx.de
+ 2014, Dariusz Dwornikowski dariusz.dwornikow...@cs.put.poznan.pl
+ 2014, Ivan Masár heli...@centrum.sk
+ 2014, Martin Hristov martinhris...@abv.bg
+ 2014, Matías A. Bellone matiasbellone+l...@gmail.com
+ 2014, Miguel Ángel Molina ssl...@gmail.com
+ 2014, Thomas Vincent tho...@vinc-net.fr
+ 2014, timothymctim timothymc...@users.noreply.github.com
+License: GPL-2+
+
Files: parseuri.js
Copyright: 2007, Steven Levithan stevenlevithan.com
License: MIT
diff -Nru jscommunicator-2.0.1/JSCommManager.js
jscommunicator-2.0.3/JSCommManager.js
--- jscommunicator-2.0.1/JSCommManager.js 2014-11-08 20:03:43.0
+0100
+++ jscommunicator-2.0.3/JSCommManager.js 2014-11-28 11:06:08.0
+0100
@@ -380,11 +380,18 @@
Arbiter.publish(jsc/ua/idle, null, {async:true});
});
-call.on('started', function(e) {
+var handleConfirmed = function(e) {
JSCommUI.session_connect(call, e);
// Signal that a call connected
Arbiter.publish(jsc/call/connected, null, {async:true});
-});
+};
+// The 'started' event was generated by JsSIP 0.4.0
+// whereas later versions send 'accepted' and 'confirmed' events
+// Discussed in https://github.com/versatica/JsSIP/issues/239
+// One of these two lines will log an error but it proceeds anyway
+console.log('only one of the event handlers confirmed or started will
be registered and the other generates a log error which can be ignored');
+call.on('confirmed
Bug#771304: unblock: jscommunicator/2.0.3-1
Control: tags -1 - moreinfo
On 28/11/14 14:58, Adam D. Barratt wrote:
Control: tags -1 + moreinfo
On 2014-11-28 11:37, Daniel Pocock wrote:
The main reason for this unblock request:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771299
This ensures that users can mix-and-match JSCommunicator with newer
versions of JsSIP. This is the change to JSCommManager.js in the
debdiff.
This appears to be a request for pre-approval, rather than an actual
unblock at this point. Please make sure you mention that in future, to
save confusion.
A quick on the diff:
+log: { level: debug }
Is that intentional? It's not mentioned and doesn't seem an obvious
consequence of the other changes.
Yes, this ensures that newer versions of JsSIP log their SIP messages to
the JavaScript console, maintaining existing behavior. The existing
version of JsSIP in Debian is logging everything be default even without
that setting.
I've just made the upload to unstable.
--
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/54788215.6050...@pocock.pro
Bug#768933: unblock: jscommunicator
On 21/11/14 17:35, Niels Thykier wrote: Control: tags -1 moreinfo On 2014-11-10 18:37, Daniel Pocock wrote: [...] I understand there are policies for the freeze Hi, I believe some of this was debated over IRC on the same day you sent your mail. I will not comment on those parts. [...] Furthermore, JSCommunicator 2.x has not changed from an API user perspective. The only dependent package is drupal7-mod-drucall and I have updated that so everything works together and gives Debian users the optimal experience. If JSCommunicator changes API in backwards incompatible manner, then you should have done this before the transition freeze. That was two months before the freeze itself. Is this upload of JSCommunicator breaking the API? No, it does not break the API, it simply adds some extra API features (new options in config.js). The main API is async messaging through ArbiterJS and that hasn't changed at all. It is the browsers that have been tweaking the API and implementation details of WebRTC. JsSIP abstracts some of that and I built JSCommunicator on top of JsSIP with the aim of abstracting it even further so that web developers have something stable to work with. Would you prefer to have jscommunicator at its current version (1.1.1-1) in Jessie or do you feel that we would be better off without it? [...] If Debian policy brings us to the point where people are actively talking about removing WebRTC capabilities from testing less than a week into the freeze then the policy is not working in the best interest of Debian's mission or openness in general. [...] My counter argument is: It is not in the best interest of Debian's mission or openness in general for the Debian release to drag on for months, because the freeze policy is ignored. See Squeeze Freeze and Wheezy Freeze. I agree and I remember the wheezy freeze well. I uploaded this as soon as reasonably possible after new dependencies entered the archive in October. If it wasn't for that I would have uploaded in August, the same time this code went live on rtc.debian.org -- 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/546f856a.5030...@pocock.pro
Bug#769122: [Pkg-middleware-maintainers] Bug#768617: Bug#768617: qpid-proton: FTBFS in jessie: build-dependency not installable: libsslcommon2-dev
On 11/11/14 15:11, Lucas Nussbaum wrote: On 11/11/14 at 08:07 -0500, Darryl L. Pierce wrote: I've fixed the cause for this by updating the dependency from libsslcommon2 to libssl in 0.7-7. How do I get this update in the build stream for Jessie? Hi Darryl, Get the fix in unstable, keeping changes to a minimum. Then request an unblock. See https://lists.debian.org/debian-devel-announce/2014/11/msg3.html Thanks! Lucas Lucas, thanks for reporting the issue, Darryl fixed it and I'm sponsoring the upload right now This upload is based on the last debdiff in the unblock request #769122 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769122#71 diff -Nru qpid-proton-0.7/debian/changelog qpid-proton-0.7/debian/changelog --- qpid-proton-0.7/debian/changelog2014-06-02 22:05:32.0 +0200 +++ qpid-proton-0.7/debian/changelog2014-11-17 11:25:04.0 +0100 @@ -1,3 +1,11 @@ +qpid-proton (0.7-2) unstable; urgency=low + + * Change dependency from libsslcommon2-dev to libssl-dev. (Closes: #768617) + * Bumped Standards-Version to 3.9.6. + * Added support for dh_python2. + + -- Darryl L. Pierce dpie...@redhat.com Wed, 12 Nov 2014 15:58:45 -0500 + qpid-proton (0.7-1) unstable; urgency=low * Initial release. (Closes: #732302) diff -Nru qpid-proton-0.7/debian/control qpid-proton-0.7/debian/control --- qpid-proton-0.7/debian/control 2014-06-02 22:57:51.0 +0200 +++ qpid-proton-0.7/debian/control 2014-11-17 11:24:19.0 +0100 @@ -9,11 +9,12 @@ pkg-config, doxygen, uuid-dev, - libsslcommon2-dev, + libssl-dev, + dh-python, python-epydoc, python (=2.6.6-3~), python-dev (=2.6.6-3~) -Standards-Version: 3.9.3 +Standards-Version: 3.9.6 Homepage: http://qpid.apache.org/proton Vcs-Browser: http://git.debian.org/?p=pkg-middleware/qpid-proton.git Vcs-Git: git://git.debian.org/git/pkg-middleware/qpid-proton.git diff -Nru qpid-proton-0.7/debian/rules qpid-proton-0.7/debian/rules --- qpid-proton-0.7/debian/rules2014-06-02 22:49:30.0 +0200 +++ qpid-proton-0.7/debian/rules2014-11-17 11:16:22.0 +0100 @@ -22,7 +22,7 @@ export DH_ALWAYS_EXCLUDE=LICENSE %: - dh $@ + dh $@ --with python2 override_dh_auto_configure: dh_auto_configure -- -DPROTON_DISABLE_RPATH=true -DNOBUILD_RUBY=on -DSYSINSTALL_BINDINGS=on
Bug#769583: unblock: bind9/ 9.9.5 with patch or 9.9.6?
On 17/11/14 20:06, Niels Thykier wrote: On 2014-11-17 19:19, LaMont Jones wrote: [...] Generally speaking, I have found the fix-level updates to bind to be very safe and sane, although sometimes they are somewhat large. I have not looked at 9.9.6 yet, but I expect it's in the same vein. It is rare to see them do anything in a fix-release than, well, fix things. I would recommend 9.9.6 for the upstream fixes. If that's good, I should be able to upload it tonight. lamont Hi LaMont, Please note that the release team do not pre-approve changes without seeing a concrete debdiff. In the particular case, it has been suggested that the final changes compared to testing will be 87 000 (or more) lines. Unless 97+% of this is pure documentational/auto-generated changes, which can be filtered out and turn this into a sanely reviewable diff, I find it unlikely that we can approve of these changes. Hi LaMont, I suspect this is the final word on it from the release team and we may have to stick with 9.9.5. Here is the patch I submitted in the RC bug, it is one line: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=12;filename=install_dlz_dlopen.patch;att=1;bug=769117 It has already been tested, it correctly installs the missing header and then my package builds too. Is it OK for you to add this and make the debdiff or would you like me to do it as an NMU? Regards, Daniel -- 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/546a540d.4020...@pocock.pro
Bug#769782: rm: sipml5 from testing
Package: release.debian.org User: release.debian@packages.debian.org UserTags: rm I just orphaned sipml5 and made an upload to sid changing maintainer to Debian QA Please remove from the testing/jessie distribution, it can hang around in sid a bit longer to see if anybody wants to take over. -- 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/546897e4.90...@pocock.pro
Bug#769583: unblock: bind9/ 9.9.5 with patch or 9.9.6?
On 16 November 2014 16:58:47 CET, Jonathan Wiltshire j...@debian.org wrote: Control: tag -1 moreinfo On Fri, Nov 14, 2014 at 07:28:02PM +0100, Daniel Pocock wrote: I understand the release team would usually prefer to see the one line fix for debian/rules against the existing package and I'm happy to NMU if the maintainers aren't able to provide that in the next couple of days. However, does anybody feel there is a strong enough case to jump directly to the latest version, 9.9.6, does the security team have any opinion on this package and its upstream changelog? Did you get any responses from elsewhere to this? Not yet, I'll follow up after the weekend. If no response, I'm happy to NMU the one line fix to copy the missing header into the dev package, please advise if that would be OK for the release team. -- http://danielpocock.com -- 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/33c1282b-f4f8-4846-921a-4fdef3670...@pocock.pro
Bug#768930: unblock: pynag and syslog-nagios-bridge
On 14/11/14 12:33, Julien Cristau wrote: On Tue, Nov 11, 2014 at 22:05:49 +0100, Niels Thykier wrote: On 2014-11-11 19:24, Clint Byrum wrote: Excerpts from Daniel Pocock's message of 2014-11-11 00:59:36 -0800: On 11/11/14 06:05, Clint Byrum wrote: [...] I think we should unblock 0.9.1. Release team have been a bit reluctant to unblock whole new versions without any justification at all In this case though, maybe they can accept that there was a good reason why it wasn't in testing before the freeze: [...] The upload only missed being in testing by 3 days, and fixes a number of issues. We don't want to ship with an old API. Seems like an easy unblock this early in the freeze. Honestly, no - the arguments present are really not all that interesting. In fact, they are a-dime-a-dozen right now. In particular, my argument for rejecting pynag/0.9.1 is that the diff is simply too large to reasonably comprehend. I've added rm hints for both packages. Hi Julien, I had offered to NMU the fix against pynag 0.8.9 and was just waiting for Clint to respond to that Please do not remove the packages Regards, Daniel -- 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/5465ef06.6030...@pocock.pro
Bug#769583: unblock: bind9/ 9.9.5 with patch or 9.9.6?
Package: release.debian.org X-Debbugs-CC: secur...@debian.org,lam...@debian.org,mgilb...@debian.org User: release.debian@packages.debian.org UserTags: unblock testing currently has bind9 version 1:9.9.5.dfsg-5 Upstream released 9.9.6 fixing some bugs with an impact on compatibility and at least one appears to be security related Corrected bugs in the handling of wildcard records by the DNSSEC validator: invalid wildcard expansions could be treated as valid if signed, and valid wildcard expansions in NSEC3 opt-out ranges had the AD bit set incorrectly in responses. [RT #37093] [RT #37072] Full upstream changelogs: https://kb.isc.org/article/AA-01210/0/BIND-9.9.6-Release-Notes.html I haven't made a debdiff but looking at the list of things in the changelog it probably isn't trivial. There is also one outstanding RC issue in bind9 that can be fixed with a one line patch against the existing package or it is fixed upstream by the 9.9.6 release, missing dlz_dlopen.h header file: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769117 I understand the release team would usually prefer to see the one line fix for debian/rules against the existing package and I'm happy to NMU if the maintainers aren't able to provide that in the next couple of days. However, does anybody feel there is a strong enough case to jump directly to the latest version, 9.9.6, does the security team have any opinion on this package and its upstream changelog? Looking at the upstream support lifecycle, bind9 9.9.x appears to be supported until June 2017, this appears OK for the support lifecycle of jessie: http://www.isc.org/downloads/software-support-policy/ -- 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/546649b2.9030...@pocock.pro
Bug#769138: unblock request for bind9
This is the related unblock request for bind9 itself: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769583 -- 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/54665125.2020...@pocock.pro
Bug#768930: unblock: pynag and syslog-nagios-bridge
On 11/11/14 06:05, Clint Byrum wrote: Excerpts from Daniel Pocock's message of 2014-11-10 12:19:19 -0800: On 10/11/14 20:56, Niels Thykier wrote: Control: tags -1 moreinfo On Mon, 10 Nov 2014 10:31:03 +0100 Daniel Pocock dan...@pocock.pro wrote: Package: release.debian.org syslog-nagios-bridge requires pynag 0.9.1+, older versions have a bug in check result file generation: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768928 I added a constraint in syslog-nagios-bridge well before the freeze so it would not propagate to testing until pynag 0.9.1 was uploaded: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763378 Note that the pynag upload in unstable is also cleaning out minified jquery and other things that make the package more compliant with Debian policy [...] Hi, I am afraid I will have to reject this request in its current form. The changes to pynag is beyond what can be reasonably reviewed and indeed it is not a targeted fix for #768928. The changes to syslog-nagios-bridge are reasonable and I could accept them, but I understand it is of no use without pynag as well. Can you please provide a targeted fix for pynag? This (just a few lines) could be dropped into debian/patches/checkresult_fix.patch https://github.com/pynag/pynag/commit/3aad1176bca4b2f39c2c851396d30647efbf2bed Clint, would you be happy to upload 0.8.9 with that or would you like me to NMU perhaps? Or is there any reason why the whole 0.9.1 should be considered for jessie? I think we should unblock 0.9.1. Release team have been a bit reluctant to unblock whole new versions without any justification at all In this case though, maybe they can accept that there was a good reason why it wasn't in testing before the freeze: a) 0.9.1 was tagged 5 August b) I sent a private email to Palli on 14 August about the bug and uploading 0.9.1 c) sent follow up and commented on the bug tracker 29 September https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763378#10 d) noticed Palli's email bouncing on 3 November, you then made the upload immediately, also removing some jquery artifacts to make it more dfsg compliant e) syslog-nagios-bridge is the only dependent package that I know of and I have been testing that against pynag v0.9.1 locally. Do you know of any other packages using pynag as a dependency? It appears that a range of issues were fixed upstream in 0.9.0 and 0.9.1 - do you know if any of these issues justify an unblock for 0.9.1 or maybe the collection of all these issues together justifies an unblock? https://github.com/pynag/pynag/issues?q=is%3Aissue+is%3Aclosed -- 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/5461cff8.4000...@pocock.pro
Bug#769138: unblock: dlz-ldap-enum/1.0.3-1
, + void *dbdata, + void **versionp); + +/* + * dlz_closeversion() is optional, but must be supplied if you supply + * a dlz_newversion() function + */ +typedef void dlz_dlopen_closeversion_t (const char *zone, + isc_boolean_t commit, + void *dbdata, + void **versionp); + +/* + * dlz_dlopen_configure() is optional, but must be supplied if you + * want to support dynamic updates + */ +typedef isc_result_t dlz_dlopen_configure_t (dns_view_t *view, +void *dbdata); + +/* + * dlz_dlopen_ssumatch() is optional, but must be supplied if you want + * to support dynamic updates + */ +typedef isc_boolean_t dlz_dlopen_ssumatch_t (const char *signer, +const char *name, +const char *tcpaddr, +const char *type, +const char *key, +isc_uint32_t keydatalen, +unsigned char *keydata, +void *dbdata); + +/* + * dlz_dlopen_addrdataset() is optional, but must be supplied if you + * want to support dynamic updates + */ +typedef isc_result_t dlz_dlopen_addrdataset_t (const char *name, + const char *rdatastr, + void *dbdata, + void *version); + +/* + * dlz_dlopen_subrdataset() is optional, but must be supplied if you + * want to support dynamic updates + */ +typedef isc_result_t dlz_dlopen_subrdataset_t (const char *name, + const char *rdatastr, + void *dbdata, + void *version); + +/* + * dlz_dlopen_delrdataset() is optional, but must be supplied if you + * want to support dynamic updates + */ +typedef isc_result_t dlz_dlopen_delrdataset_t (const char *name, + const char *type, + void *dbdata, + void *version); + +ISC_LANG_ENDDECLS + +#endif diff -Nru dlz-ldap-enum-1.0.2/config.h.in dlz-ldap-enum-1.0.3/config.h.in --- dlz-ldap-enum-1.0.2/config.h.in 2012-05-17 23:42:59.0 +0200 +++ dlz-ldap-enum-1.0.3/config.h.in 2014-11-11 17:30:58.0 +0100 @@ -1,5 +1,8 @@ /* config.h.in. Generated from configure.ac by autoheader. */ +/* Indicates we are compiling for bind9 9.9 or later */ +#undef BIND_9_9 + /* Define to 1 if you have the dlfcn.h header file. */ #undef HAVE_DLFCN_H diff -Nru dlz-ldap-enum-1.0.2/config.sub dlz-ldap-enum-1.0.3/config.sub diff -Nru dlz-ldap-enum-1.0.2/configure dlz-ldap-enum-1.0.3/configure diff -Nru dlz-ldap-enum-1.0.2/configure.ac dlz-ldap-enum-1.0.3/configure.ac --- dlz-ldap-enum-1.0.2/configure.ac2012-05-17 23:41:39.0 +0200 +++ dlz-ldap-enum-1.0.3/configure.ac2014-11-11 17:29:34.0 +0100 @@ -1,10 +1,10 @@ dnldlz-ldap-enum: bind9 DLZ module for using an LDAP database to answer dnl ENUM queries over DNS -dnlCopyright (C) 2012 Daniel Pocock +dnlCopyright (C) 2012-2014 Daniel Pocock dnl dnlPlease see the COPYING file for license terms -AC_INIT(dlz-ldap-enum,1.0.2) +AC_INIT(dlz-ldap-enum,1.0.3) AC_CONFIG_SRCDIR(dlz_ldap_enum_driver.c) AM_INIT_AUTOMAKE @@ -19,6 +19,11 @@ AC_PROG_LIBTOOL +AC_ARG_ENABLE(bind99, +[ --enable-bind99 Enable building for bind9 9.9.x and later], + [AC_DEFINE([BIND_9_9], , [Indicates we are compiling for bind9 9.9 or later])], + []) + AC_OUTPUT(Makefile) diff -Nru dlz-ldap-enum-1.0.2/debian/changelog dlz-ldap-enum-1.0.3/debian/changelog --- dlz-ldap-enum-1.0.2/debian/changelog2014-09-14 10:27:58.0 +0200 +++ dlz-ldap-enum-1.0.3/debian/changelog2014-11-11 17:47:04.0 +0100 @@ -1,3 +1,10 @@ +dlz-ldap-enum (1.0.3-1) unstable; urgency=medium + + * New upstream release. + * dlz_lookup function updated for bind9 9.9.x. (Closes: #769134) + + -- Daniel Pocock dan...@pocock.pro Tue, 11 Nov 2014 17:38:11 +0100 + dlz-ldap-enum (1.0.2-2) unstable; urgency=low * Update maintainer and VCS details. diff -Nru dlz-ldap-enum-1.0.2/debian/rules dlz-ldap-enum-1.0.3/debian/rules --- dlz-ldap-enum-1.0.2/debian/rules2014-10-26 07:06:43.0 +0100 +++ dlz-ldap-enum-1.0.3/debian/rules2014-11-11 17:37:10.0 +0100 @@ -11,10 +11,7 @@ # Add here any variable or target overrides you need. -DLZ_DLOPEN_H=/usr/include/dns/dlz_dlopen.h -ifeq ($(readlink $(DLZ_DLOPEN_H)),) -CPPFLAGS
Bug#768930: unblock: pynag and syslog-nagios-bridge
On 11/11/14 22:19, Clint Byrum wrote: Excerpts from Niels Thykier's message of 2014-11-11 13:05:49 -0800: On 2014-11-11 19:24, Clint Byrum wrote: Excerpts from Daniel Pocock's message of 2014-11-11 00:59:36 -0800: On 11/11/14 06:05, Clint Byrum wrote: [...] I think we should unblock 0.9.1. Release team have been a bit reluctant to unblock whole new versions without any justification at all In this case though, maybe they can accept that there was a good reason why it wasn't in testing before the freeze: [...] The upload only missed being in testing by 3 days, and fixes a number of issues. We don't want to ship with an old API. Seems like an easy unblock this early in the freeze. Honestly, no - the arguments present are really not all that interesting. In fact, they are a-dime-a-dozen right now. In particular, my argument for rejecting pynag/0.9.1 is that the diff is simply too large to reasonably comprehend. Who exactly are we affecting negatively by unblocking this package? Because we're going to waste a number of pynag users' time by not unblocking it and witholding the fixes and new features, as well as wasting the syslog-nagios-bridge maintainers' time by requiring them to backport to the old API, so I want to understand the reason we want to do that. For me, it is not about backporting, it is actually a fault in the 0.8.9 release but it is also very easily fixed by the patch I proposed. The type of person who uses PyNag will probably have no trouble getting 0.9.1 and later versions from jessie-backports if the release team can't do an unblock for the new version. -- 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/54627f17.9060...@pocock.pro
Bug#768931: unblock: drupal7-mod-jqueryi18nproperties
Package: release.debian.org
The upload to unstable fixes a small but essential bug:
bugs.debian.org/768502
--- drupal7-mod-jqueryi18nproperties-1.0.0/debian/changelog
2014-10-10 18:10:58.0 +0200
+++ drupal7-mod-jqueryi18nproperties-1.1/debian/changelog
2014-11-07 22:34:12.0 +0100
@@ -1,3 +1,16 @@
+drupal7-mod-jqueryi18nproperties (1.1-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Correct mismatched PHP function name. (Closes: #768502)
+
+ -- Daniel Pocock dan...@pocock.pro Fri, 07 Nov 2014 22:33:14 +0100
+
+drupal7-mod-jqueryi18nproperties (1.0.0-2) unstable; urgency=low
+
+ * Update for standards-version 3.9.6
+
+ -- Daniel Pocock dan...@pocock.pro Fri, 10 Oct 2014 14:46:24 +0200
+
drupal7-mod-jqueryi18nproperties (1.0.0-1) unstable; urgency=low
* Initial packaging (Closes: #759539)
diff -Nru drupal7-mod-jqueryi18nproperties-1.0.0/debian/changelog
drupal7-mod-jqueryi18nproperties-1.1/debian/changelog
--- drupal7-mod-jqueryi18nproperties-1.0.0/debian/changelog 2014-10-10
18:10:58.0 +0200
+++ drupal7-mod-jqueryi18nproperties-1.1/debian/changelog 2014-11-07
22:34:12.0 +0100
@@ -1,3 +1,16 @@
+drupal7-mod-jqueryi18nproperties (1.1-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Correct mismatched PHP function name. (Closes: #768502)
+
+ -- Daniel Pocock dan...@pocock.pro Fri, 07 Nov 2014 22:33:14 +0100
+
+drupal7-mod-jqueryi18nproperties (1.0.0-2) unstable; urgency=low
+
+ * Update for standards-version 3.9.6
+
+ -- Daniel Pocock dan...@pocock.pro Fri, 10 Oct 2014 14:46:24 +0200
+
drupal7-mod-jqueryi18nproperties (1.0.0-1) unstable; urgency=low
* Initial packaging (Closes: #759539)
diff -Nru drupal7-mod-jqueryi18nproperties-1.0.0/debian/control
drupal7-mod-jqueryi18nproperties-1.1/debian/control
--- drupal7-mod-jqueryi18nproperties-1.0.0/debian/control 2014-10-10
18:10:58.0 +0200
+++ drupal7-mod-jqueryi18nproperties-1.1/debian/control 2014-11-07
22:32:48.0 +0100
@@ -4,7 +4,7 @@
Maintainer: Debian Javascript Maintainers
pkg-javascript-de...@lists.alioth.debian.org
Uploaders: Daniel Pocock dan...@pocock.pro
Build-Depends: debhelper (= 9)
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
Homepage:
https://github.com/jquery-i18n-properties/drupal-mod-jqueryi18nproperties
Vcs-Browser:
https://github.com/jquery-i18n-properties/drupal-mod-jqueryi18nproperties
Vcs-Git:
https://github.com/jquery-i18n-properties/drupal-mod-jqueryi18nproperties
diff -Nru drupal7-mod-jqueryi18nproperties-1.0.0/jqueryi18nproperties.module
drupal7-mod-jqueryi18nproperties-1.1/jqueryi18nproperties.module
--- drupal7-mod-jqueryi18nproperties-1.0.0/jqueryi18nproperties.module
2014-08-27 23:05:12.0 +0200
+++ drupal7-mod-jqueryi18nproperties-1.1/jqueryi18nproperties.module
2014-11-07 20:44:13.0 +0100
@@ -24,7 +24,7 @@
* An associative array whose keys are internal names of libraries
* and whose values are describing each library.
*/
-function jssip_libraries_info() {
+function jqueryi18nproperties_libraries_info() {
$libraries['jqueryi18nproperties'] = array(
'name' = 'jQuery-i18n-properties',
'vendor url' =
'https://github.com/jquery-i18n-properties/jquery-i18n-properties',
Bug#768932: unblock: drupal7-mod-fontawesome
Package: release.debian.org The normal fonts-font-awesome package installs a range of files The original drupal7-mod-fontawesome only symlinked the css files into drupal7, the latest upload in unstable symlinks the remaining css files into drupal7 so they can also be used by other dependencies http://bugs.debian.org/768630 --- drupal7-mod-fontawesome-1.0/debian/changelog2014-08-28 13:46:17.0 +0200 +++ drupal7-mod-fontawesome-1.0/debian/changelog2014-11-08 20:28:27.0 +0100 @@ -1,3 +1,9 @@ +drupal7-mod-fontawesome (1.0-2) unstable; urgency=medium + + * Symlink the rest of Font Awesome into Drupal. (Closes: #768630) + + -- Daniel Pocock dan...@pocock.pro Sat, 08 Nov 2014 20:19:33 +0100 + drupal7-mod-fontawesome (1.0-1) unstable; urgency=low * Initial packaging (Closes: #759547) diff -Nru drupal7-mod-fontawesome-1.0/debian/changelog drupal7-mod-fontawesome-1.0/debian/changelog --- drupal7-mod-fontawesome-1.0/debian/changelog2014-08-28 13:46:17.0 +0200 +++ drupal7-mod-fontawesome-1.0/debian/changelog2014-11-08 20:28:27.0 +0100 @@ -1,3 +1,9 @@ +drupal7-mod-fontawesome (1.0-2) unstable; urgency=medium + + * Symlink the rest of Font Awesome into Drupal. (Closes: #768630) + + -- Daniel Pocock dan...@pocock.pro Sat, 08 Nov 2014 20:19:33 +0100 + drupal7-mod-fontawesome (1.0-1) unstable; urgency=low * Initial packaging (Closes: #759547) diff -Nru drupal7-mod-fontawesome-1.0/debian/control drupal7-mod-fontawesome-1.0/debian/control --- drupal7-mod-fontawesome-1.0/debian/control 2014-08-28 13:30:27.0 +0200 +++ drupal7-mod-fontawesome-1.0/debian/control 2014-11-08 20:18:29.0 +0100 @@ -4,7 +4,7 @@ Maintainer: Debian Javascript Maintainers pkg-javascript-de...@lists.alioth.debian.org Uploaders: Daniel Pocock dan...@pocock.pro Build-Depends: debhelper (= 9) -Standards-Version: 3.9.5 +Standards-Version: 3.9.6 Homepage: https://www.drupal.org/project/fontawesome Vcs-Browser: https://github.com/dpocock/drupal-mod-fontawesome Vcs-Git: https://github.com/dpocock/drupal-mod-fontawesome diff -Nru drupal7-mod-fontawesome-1.0/debian/drupal7-mod-fontawesome.links drupal7-mod-fontawesome-1.0/debian/drupal7-mod-fontawesome.links --- drupal7-mod-fontawesome-1.0/debian/drupal7-mod-fontawesome.links 2014-08-28 13:37:52.0 +0200 +++ drupal7-mod-fontawesome-1.0/debian/drupal7-mod-fontawesome.links 2014-11-08 20:12:17.0 +0100 @@ -1 +1,4 @@ /usr/share/fonts-font-awesome/css usr/share/drupal7/libraries/fontawesome/css +/usr/share/fonts-font-awesome/fonts usr/share/drupal7/libraries/fontawesome/fonts +/usr/share/fonts-font-awesome/less usr/share/drupal7/libraries/fontawesome/less +/usr/share/fonts-font-awesome/scss usr/share/drupal7/libraries/fontawesome/scss diff -Nru drupal7-mod-fontawesome-1.0/debian/README.source drupal7-mod-fontawesome-1.0/debian/README.source --- drupal7-mod-fontawesome-1.0/debian/README.source1970-01-01 01:00:00.0 +0100 +++ drupal7-mod-fontawesome-1.0/debian/README.source2014-11-08 20:09:14.0 +0100 @@ -0,0 +1,10 @@ + +It can be helpful to create tags in the Debian format, e.g: + + git tag -m 'Upstream 7.x v1.0' upstream/1.0 7.x-1.0 + +and then build the package: + + git-buildpackage --git-upstream-branch=7.x-1.x --git-debian-branch=debian -rfakeroot + +
Bug#768933: unblock: jscommunicator
Package: release.debian.org
Bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768363
- this corrects the version in the constraint to depend on
fonts-font-awesome 4.1.0~dfsg
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768632
- this ensures compatibility with older versions of jQuery found in
Debian / drupal7 package
This is a new upstream release (from 1.1.1 to 2.0.1). WebRTC is a fast
moving technology and it is in the best interests of users to offer the
latest version of the package. Browser vendors assure
This package has not been updated in unstable for a few months because
related dependencies were in the FTP new queue
(drupal7-mod-jqueryi18nproperties and drupal7-mod-fontawesome) until
just before the freeze and so I have only been able to test all these
packages together as a set over the last few days. If I had uploaded
earlier it would have broken the drucall package.
There will also be an unblock request for drupal7-mod-drucall which is
based on jscommunicator
--- jscommunicator-1.1.1/debian/changelog 2014-02-12
16:08:06.0 +0100
+++ jscommunicator-2.0.1/debian/changelog 2014-11-08
22:18:54.0 +0100
@@ -1,3 +1,22 @@
+jscommunicator (2.0.1-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Support for older jQuery versions. (Closes: #768632)
+
+ -- Daniel Pocock dan...@pocock.pro Sat, 08 Nov 2014 22:17:56 +0100
+
+jscommunicator (2.0.0-2) unstable; urgency=medium
+
+ * Relax fonts-font-awesome dependency version. (Closes: #768363)
+
+ -- Daniel Pocock dan...@pocock.pro Thu, 06 Nov 2014 20:44:01 +0100
+
+jscommunicator (2.0.0-1) unstable; urgency=medium
+
+ * New upstream release.
+
+ -- Daniel Pocock dan...@pocock.pro Wed, 05 Nov 2014 22:07:58 +0100
+
jscommunicator (1.1.1-1) unstable; urgency=low
* New upstream release
diff -Nru jscommunicator-1.1.1/AUTHORS jscommunicator-2.0.1/AUTHORS
--- jscommunicator-1.1.1/AUTHORS1970-01-01 01:00:00.0 +0100
+++ jscommunicator-2.0.1/AUTHORS2014-11-08 20:03:43.0 +0100
@@ -0,0 +1,12 @@
+Daniel Pocock danielpocock.com
+Juliana Louback julianalouback.com
+Christian Henz github.com/chenz
+Jeroen Massar jeroen.massar.ch
+elprincipe github.com/elprincipe
+Yehuda Korotkin github.com/yedako
+Carla Araos carlaaraos.com
+aavia github.com/aavia
+mirazusman github.com/mirazusman
+tehilazi github.com/tehilazi
+Matías A. Bellone github.com/toote
+tami4 github.com/tami4
diff -Nru jscommunicator-1.1.1/available_languages.xml
jscommunicator-2.0.1/available_languages.xml
--- jscommunicator-1.1.1/available_languages.xml1970-01-01
01:00:00.0 +0100
+++ jscommunicator-2.0.1/available_languages.xml2014-11-08
20:03:43.0 +0100
@@ -0,0 +1,39 @@
+?xml version=1.0 encoding=UTF-8?
+list
+language
+displayБългарски/display
+codebg/code
+/language
+language
+displayDeutsch/display
+codede/code
+/language
+language
+displayEnglish/display
+codeen/code
+/language
+language
+displayEspañol/display
+codees/code
+/language
+language
+displayFrançais/display
+codefr/code
+/language
+language
+displayעברית/display
+codehe/code
+/language
+language
+displayPolski/display
+codepl/code
+/language
+language
+displayPortuguês/display
+codept/code
+/language
+language
+displayslovenčina/display
+codesk/code
+/language
+/list
diff -Nru jscommunicator-1.1.1/code_grabber jscommunicator-2.0.1/code_grabber
--- jscommunicator-1.1.1/code_grabber 1970-01-01 01:00:00.0 +0100
+++ jscommunicator-2.0.1/code_grabber 2014-11-08 20:03:43.0 +0100
@@ -0,0 +1,21 @@
+#!/bin/sh
+
+wget http://code.jquery.com/jquery-1.7.2.min.js -O jquery.js
+wget https://freephonebox.net/JsSIP.js -O JsSIP.js
+wget http://arbiterjs.com/Arbiter.js -O Arbiter.js
+wget
https://jquery-i18n-properties.googlecode.com/files/jquery.i18n.properties-min-1.0.9.js
-O jquery.i18n.properties.js
+
+mkdir -p font-awesome/css
+mkdir -p font-awesome/fonts
+
+mkdir -p temp
+wget -P temp http://jqueryui.com/resources/download/jquery-ui-1.10.4.zip
+unzip -d temp temp/jquery-ui-1.10.4.zip
+cp temp/jquery-ui-1.10.4/js/jquery-ui-1.10.4.min.js jquery-ui.js
+cp temp/jquery-ui-1.10.4/css/ui-lightness/jquery-ui-1.10.4.css jquery-ui.css
+
+wget -P temp
http://fortawesome.github.io/Font-Awesome/assets/font-awesome-4.1.0.zip
+unzip -d temp temp/font-awesome-4.1.0.zip
+cp temp/font-awesome-4.1.0/css/font-awesome.min.css
font-awesome/css/font-awesome.min.css
+cp -a temp/font-awesome-4.1.0/fonts/. font-awesome/fonts
+rm -r temp
diff -Nru jscommunicator-1.1.1/config-sample.js
jscommunicator-2.0.1/config-sample.js
--- jscommunicator-1.1.1/config-sample.js 2014-02-06 22:48:30.0
+0100
+++ jscommunicator-2.0.1/config-sample.js 2014-11-08 20:03:43.0
+0100
@@ -16,7 +16,7 @@
websocket: {
servers: 'wss://ws1.example.org',
connection_recovery_min_interval: 2,
-connection_recovery_max_interval: 30
Bug#768935: unblock: drupal7-mod-drucall
Package: release.debian.org
drupal7-mod-drucall is closely related to the jscommunicator package
This version updates the package with the latest content, including
language files, from jscommunicator. The jscommunicator unblock request
links to various bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768363
- this corrects the version in the constraint to depend on
fonts-font-awesome 4.1.0~dfsg
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768632
- this ensures compatibility with older versions of jQuery found in Debian /
drupal7 package
This is a new upstream release from 2.0.0 to 2.2. WebRTC is a fast
moving technology and it is in the best interests of users to offer the
latest version of the package. Browser vendors assure people that the
technology is still under development and users should not be too
surprised at this change in version.
This package has not been updated in unstable for a few months because
new dependencies were in the FTP new queue
(drupal7-mod-jqueryi18nproperties and drupal7-mod-fontawesome) until
just before the freeze and so I have only been able to test all these
packages together with the latest jscommunicator as a set over the last
few days.
diff -Nru drupal7-mod-drucall-2.0.1/debian/changelog
drupal7-mod-drucall-2.1/debian/changelog
--- drupal7-mod-drucall-2.0.1/debian/changelog 2014-02-04
21:30:57.0 +0100
+++ drupal7-mod-drucall-2.1/debian/changelog2014-11-06
20:05:11.0 +0100
@@ -1,3 +1,10 @@
+drupal7-mod-drucall (2.1-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Sync content with JSCommunicator. (Closes: #768354)
+
+ -- Daniel Pocock dan...@pocock.pro Thu, 06 Nov 2014 19:33:06 +0100
+
drupal7-mod-drucall (2.0.1-1) unstable; urgency=low
* New upstream release
diff -Nru drupal7-mod-drucall-2.0.1/available_languages.xml
drupal7-mod-drucall-2.1/available_languages.xml
--- drupal7-mod-drucall-2.0.1/available_languages.xml 1970-01-01
01:00:00.0 +0100
+++ drupal7-mod-drucall-2.1/available_languages.xml 2014-11-06
19:08:37.0 +0100
@@ -0,0 +1,39 @@
+?xml version=1.0 encoding=UTF-8?
+list
+language
+displayБългарски/display
+codebg/code
+/language
+language
+displayDeutsch/display
+codede/code
+/language
+language
+displayEnglish/display
+codeen/code
+/language
+language
+displayEspañol/display
+codees/code
+/language
+language
+displayFrançais/display
+codefr/code
+/language
+language
+displayעברית/display
+codehe/code
+/language
+language
+displayPolski/display
+codepl/code
+/language
+language
+displayPortuguês/display
+codept/code
+/language
+language
+displayslovenčina/display
+codesk/code
+/language
+/list
diff -Nru drupal7-mod-drucall-2.0.1/debian/changelog
drupal7-mod-drucall-2.1/debian/changelog
--- drupal7-mod-drucall-2.0.1/debian/changelog 2014-02-04 21:30:57.0
+0100
+++ drupal7-mod-drucall-2.1/debian/changelog2014-11-06 20:05:11.0
+0100
@@ -1,3 +1,10 @@
+drupal7-mod-drucall (2.1-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Sync content with JSCommunicator. (Closes: #768354)
+
+ -- Daniel Pocock dan...@pocock.pro Thu, 06 Nov 2014 19:33:06 +0100
+
drupal7-mod-drucall (2.0.1-1) unstable; urgency=low
* New upstream release
diff -Nru drupal7-mod-drucall-2.0.1/debian/control
drupal7-mod-drucall-2.1/debian/control
--- drupal7-mod-drucall-2.0.1/debian/control2014-01-24 13:04:00.0
+0100
+++ drupal7-mod-drucall-2.1/debian/control 2014-11-06 20:06:51.0
+0100
@@ -2,17 +2,17 @@
Section: web
Priority: optional
Maintainer: Debian Javascript Maintainers
pkg-javascript-de...@lists.alioth.debian.org
-Uploaders: Daniel Pocock dan...@pocock.com.au
+Uploaders: Daniel Pocock dan...@pocock.pro
Build-Depends: debhelper (= 9)
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
Homepage: http://www.drucall.org
-Vcs-Browser: http://git.debian.org/?p=pkg-javascript/drupal7-mod-drucall.git
-Vcs-Git: git://git.debian.org/git/pkg-javascript/drupal7-mod-drucall.git
+Vcs-Browser:
https://anonscm.debian.org/cgit/pkg-javascript/drupal7-mod-drucall.git
+Vcs-Git: git://anonscm.debian.org/pkg-javascript/drupal7-mod-drucall.git
Package: drupal7-mod-drucall
Architecture: all
Multi-Arch: foreign
-Depends: ${misc:Depends}, drupal7-mod-jscommunicator
+Depends: ${misc:Depends}, drupal7-mod-jscommunicator (= 1.1)
Recommends: javascript-common
Suggests: repro (= 1.9.0), resiprocate-turn-server | rfc5766-turn-server
Description: WebRTC SIP module for the Drupal CMS
diff -Nru drupal7-mod-drucall-2.0.1/drucall.admin.inc
drupal7-mod-drucall-2.1/drucall.admin.inc
--- drupal7-mod-drucall-2.0.1/drucall.admin.inc 2014-02-04 21:27:37.0
+0100
+++ drupal7-mod-drucall-2.1/drucall.admin.inc 2014-11-06 19:08:37.0
+0100
@@ -33,6 +33,20 @@
'#description' = t('Whether or not to show a button allowing a video
call.'),
);
+ $form
Bug#768933: unblock: jscommunicator
Control: tags -1 -wontfix On 10/11/14 17:42, Niels Thykier wrote: Control: tags -1 moreinfo wontfix On 2014-11-10 11:04, Daniel Pocock wrote: Package: release.debian.org Bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768363 - this corrects the version in the constraint to depend on fonts-font-awesome 4.1.0~dfsg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768632 - this ensures compatibility with older versions of jQuery found in Debian / drupal7 package This is a new upstream release (from 1.1.1 to 2.0.1). WebRTC is a fast moving technology and it is in the best interests of users to offer the latest version of the package. Browser vendors assure This package has not been updated in unstable for a few months because related dependencies were in the FTP new queue (drupal7-mod-jqueryi18nproperties and drupal7-mod-fontawesome) until just before the freeze and so I have only been able to test all these packages together as a set over the last few days. If I had uploaded earlier it would have broken the drucall package. There will also be an unblock request for drupal7-mod-drucall which is based on jscommunicator [...] Hi, I am afraid that I have to decline your request, since the changes are incompatible with the freeze policy. Based on your explain, it sounds like jscommunicator is more suited for -backports. I understand there are policies for the freeze At the bottom (yes, I read the whole policy), it states For packages which missed the freeze only for reasons outside of the control of the maintainers, we might be generous, but you need to contact us on your own. So I have contacted you by doing the necessary work and sending the release team fully documented unblock requests. In this case, reasons outside my control were the related packages stuck in the NEW queue since I uploaded them in August. I attach the original notifications from the uploads. They were only accepted by the FTP masters on 10 and 11 October, which is exactly when I was departing for a lengthy trip, which included several free software/Debian related activities, just getting back home a day before the freeze. As mentioned already, this package is closely related to an emerging feature in the browser packages, iceweasel and chromium. Both of those packages were updated to newer versions during the wheezy freeze[1] and both of them were updated during the various wheezy updates too, not just through backports. Please tell me which justification was used for updating browser packages in stable to newer versions (rather than just cherry-picking fixes) and whether that can be extrapolated to packages like jscommunicator that have a close relationship to browser features like WebRTC that are changing. Furthermore, JSCommunicator 2.x has not changed from an API user perspective. The only dependent package is drupal7-mod-drucall and I have updated that so everything works together and gives Debian users the optimal experience. Would you prefer to have jscommunicator at its current version (1.1.1-1) in Jessie or do you feel that we would be better off without it? Actually, I think the world would be better off without Microsoft and Skype. If Debian policy brings us to the point where people are actively talking about removing WebRTC capabilities from testing less than a week into the freeze then the policy is not working in the best interest of Debian's mission or openness in general. 1. http://metadata.ftp-master.debian.org/changelogs//main/c/chromium-browser/chromium-browser_37.0.2062.120-1~deb7u1_changelog ---BeginMessage--- binary:drupal7-mod-fontawesome is NEW. source:drupal7-mod-fontawesome is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html ---End Message--- ---BeginMessage--- binary:drupal7-mod-jqueryi18nproperties is NEW. source:drupal7-mod-jqueryi18nproperties is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html ---End Message---
Bug#768933: rtc.debian.org using jscommunicator 2.x since August
Just another observation - the same jscommunicator v2.x code was already deployed on rtc.debian.org in August before DebConf14. -- 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/5460fafd.1030...@pocock.pro
Bug#768933: without i18n diff
diff -Nru jscommunicator-1.1.1/AUTHORS jscommunicator-2.0.1/AUTHORS
--- jscommunicator-1.1.1/AUTHORS1970-01-01 01:00:00.0 +0100
+++ jscommunicator-2.0.1/AUTHORS2014-11-08 20:03:43.0 +0100
@@ -0,0 +1,12 @@
+Daniel Pocock danielpocock.com
+Juliana Louback julianalouback.com
+Christian Henz github.com/chenz
+Jeroen Massar jeroen.massar.ch
+elprincipe github.com/elprincipe
+Yehuda Korotkin github.com/yedako
+Carla Araos carlaaraos.com
+aavia github.com/aavia
+mirazusman github.com/mirazusman
+tehilazi github.com/tehilazi
+Matías A. Bellone github.com/toote
+tami4 github.com/tami4
diff -Nru jscommunicator-1.1.1/available_languages.xml
jscommunicator-2.0.1/available_languages.xml
--- jscommunicator-1.1.1/available_languages.xml1970-01-01
01:00:00.0 +0100
+++ jscommunicator-2.0.1/available_languages.xml2014-11-08
20:03:43.0 +0100
@@ -0,0 +1,39 @@
+?xml version=1.0 encoding=UTF-8?
+list
+language
+displayБългарски/display
+codebg/code
+/language
+language
+displayDeutsch/display
+codede/code
+/language
+language
+displayEnglish/display
+codeen/code
+/language
+language
+displayEspañol/display
+codees/code
+/language
+language
+displayFrançais/display
+codefr/code
+/language
+language
+displayעברית/display
+codehe/code
+/language
+language
+displayPolski/display
+codepl/code
+/language
+language
+displayPortuguês/display
+codept/code
+/language
+language
+displayslovenčina/display
+codesk/code
+/language
+/list
diff -Nru jscommunicator-1.1.1/code_grabber jscommunicator-2.0.1/code_grabber
--- jscommunicator-1.1.1/code_grabber 1970-01-01 01:00:00.0 +0100
+++ jscommunicator-2.0.1/code_grabber 2014-11-08 20:03:43.0 +0100
@@ -0,0 +1,21 @@
+#!/bin/sh
+
+wget http://code.jquery.com/jquery-1.7.2.min.js -O jquery.js
+wget https://freephonebox.net/JsSIP.js -O JsSIP.js
+wget http://arbiterjs.com/Arbiter.js -O Arbiter.js
+wget
https://jquery-i18n-properties.googlecode.com/files/jquery.i18n.properties-min-1.0.9.js
-O jquery.i18n.properties.js
+
+mkdir -p font-awesome/css
+mkdir -p font-awesome/fonts
+
+mkdir -p temp
+wget -P temp http://jqueryui.com/resources/download/jquery-ui-1.10.4.zip
+unzip -d temp temp/jquery-ui-1.10.4.zip
+cp temp/jquery-ui-1.10.4/js/jquery-ui-1.10.4.min.js jquery-ui.js
+cp temp/jquery-ui-1.10.4/css/ui-lightness/jquery-ui-1.10.4.css jquery-ui.css
+
+wget -P temp
http://fortawesome.github.io/Font-Awesome/assets/font-awesome-4.1.0.zip
+unzip -d temp temp/font-awesome-4.1.0.zip
+cp temp/font-awesome-4.1.0/css/font-awesome.min.css
font-awesome/css/font-awesome.min.css
+cp -a temp/font-awesome-4.1.0/fonts/. font-awesome/fonts
+rm -r temp
diff -Nru jscommunicator-1.1.1/config-sample.js
jscommunicator-2.0.1/config-sample.js
--- jscommunicator-1.1.1/config-sample.js 2014-02-06 22:48:30.0
+0100
+++ jscommunicator-2.0.1/config-sample.js 2014-11-08 20:03:43.0
+0100
@@ -16,7 +16,7 @@
websocket: {
servers: 'wss://ws1.example.org',
connection_recovery_min_interval: 2,
-connection_recovery_max_interval: 30,
+connection_recovery_max_interval: 30
},
// User identity
@@ -29,7 +29,7 @@
uri: 'sip:b...@example.org',
sip_auth_user: 'bob',
sip_auth_password: 'bob',
-sip_auth_user_full_uri: true, // Whether to use full URI or just
+sip_auth_user_full_uri: true// Whether to use full URI or just
// the user part to construct the auth user
},
@@ -38,14 +38,14 @@
on_startup: true, // Register when websocket link starts?
expiry: 3600, // Registration expiry (seconds)
user_control: false,// Show button for user to (de)register
-server: null, // Registration server
+server: null // Registration server
},
dialing : {
auto_dial : {
default_destination : 'alice', // A name or full URI
on_startup: false, // Whether to wait for user to click dial
- use_video: true,// Whether to auto-dial with video
+ use_video: true // Whether to auto-dial with video
},
edit_destination: true, // Whether the user may edit the destination
show_destination: true, // Whether the user can see the destination
@@ -53,11 +53,18 @@
video_dialing: true, // Whether to offer a video call button
prefer_video: false, // If user presses Enter to dial, use video?
no_answer_timeout: 60, // How long to wait for answer (seconds)
+clear_dialbox: false // Whether to clear dialbox after
call/attempted call
+ },
+
+ chat : {
+enable: true // Whether to show chat functions
},
session : {
show_dtmf_pad : true,// Whether to show a DTMF dialpad during calls
dtmf_duration : 160, // Duration (ms) to signal a DTMF
Bug#768935: debdiff without i18n
diff -Nru drupal7-mod-drucall-2.0.1/available_languages.xml
drupal7-mod-drucall-2.1/available_languages.xml
--- drupal7-mod-drucall-2.0.1/available_languages.xml 1970-01-01
01:00:00.0 +0100
+++ drupal7-mod-drucall-2.1/available_languages.xml 2014-11-06
19:08:37.0 +0100
@@ -0,0 +1,39 @@
+?xml version=1.0 encoding=UTF-8?
+list
+language
+displayБългарски/display
+codebg/code
+/language
+language
+displayDeutsch/display
+codede/code
+/language
+language
+displayEnglish/display
+codeen/code
+/language
+language
+displayEspañol/display
+codees/code
+/language
+language
+displayFrançais/display
+codefr/code
+/language
+language
+displayעברית/display
+codehe/code
+/language
+language
+displayPolski/display
+codepl/code
+/language
+language
+displayPortuguês/display
+codept/code
+/language
+language
+displayslovenčina/display
+codesk/code
+/language
+/list
diff -Nru drupal7-mod-drucall-2.0.1/debian/changelog
drupal7-mod-drucall-2.1/debian/changelog
--- drupal7-mod-drucall-2.0.1/debian/changelog 2014-02-04 21:30:57.0
+0100
+++ drupal7-mod-drucall-2.1/debian/changelog2014-11-06 20:05:11.0
+0100
@@ -1,3 +1,10 @@
+drupal7-mod-drucall (2.1-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Sync content with JSCommunicator. (Closes: #768354)
+
+ -- Daniel Pocock dan...@pocock.pro Thu, 06 Nov 2014 19:33:06 +0100
+
drupal7-mod-drucall (2.0.1-1) unstable; urgency=low
* New upstream release
diff -Nru drupal7-mod-drucall-2.0.1/debian/control
drupal7-mod-drucall-2.1/debian/control
--- drupal7-mod-drucall-2.0.1/debian/control2014-01-24 13:04:00.0
+0100
+++ drupal7-mod-drucall-2.1/debian/control 2014-11-06 20:06:51.0
+0100
@@ -2,17 +2,17 @@
Section: web
Priority: optional
Maintainer: Debian Javascript Maintainers
pkg-javascript-de...@lists.alioth.debian.org
-Uploaders: Daniel Pocock dan...@pocock.com.au
+Uploaders: Daniel Pocock dan...@pocock.pro
Build-Depends: debhelper (= 9)
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
Homepage: http://www.drucall.org
-Vcs-Browser: http://git.debian.org/?p=pkg-javascript/drupal7-mod-drucall.git
-Vcs-Git: git://git.debian.org/git/pkg-javascript/drupal7-mod-drucall.git
+Vcs-Browser:
https://anonscm.debian.org/cgit/pkg-javascript/drupal7-mod-drucall.git
+Vcs-Git: git://anonscm.debian.org/pkg-javascript/drupal7-mod-drucall.git
Package: drupal7-mod-drucall
Architecture: all
Multi-Arch: foreign
-Depends: ${misc:Depends}, drupal7-mod-jscommunicator
+Depends: ${misc:Depends}, drupal7-mod-jscommunicator (= 1.1)
Recommends: javascript-common
Suggests: repro (= 1.9.0), resiprocate-turn-server | rfc5766-turn-server
Description: WebRTC SIP module for the Drupal CMS
diff -Nru drupal7-mod-drucall-2.0.1/drucall.admin.inc
drupal7-mod-drucall-2.1/drucall.admin.inc
--- drupal7-mod-drucall-2.0.1/drucall.admin.inc 2014-02-04 21:27:37.0
+0100
+++ drupal7-mod-drucall-2.1/drucall.admin.inc 2014-11-06 19:08:37.0
+0100
@@ -33,6 +33,20 @@
'#description' = t('Whether or not to show a button allowing a video
call.'),
);
+ $form['enable_chat'] = array(
+'#type' = 'checkbox',
+'#title' = t('Show chat panel'),
+'#default_value' = variable_get('enable_chat', true),
+'#description' = t('Whether or not to show the chat messaging facility.'),
+ );
+
+ $form['enable_dtmf_pad'] = array(
+'#type' = 'checkbox',
+'#title' = t('Show DTMF panel in-call'),
+'#default_value' = variable_get('enable_dtmf_pad', true),
+'#description' = t('Whether or not to show a DTMF dialing pad during
calls.'),
+ );
+
$form['display_name'] = array(
'#type' = 'textfield',
'#title' = t('Display name for caller'),
@@ -140,6 +154,8 @@
variable_set('default_destination',
$form_state['values']['default_destination']);
variable_set('enable_audio', $form_state['values']['enable_audio']);
variable_set('enable_video', $form_state['values']['enable_video']);
+ variable_set('enable_chat', $form_state['values']['enable_chat']);
+ variable_set('enable_dtmf_pad', $form_state['values']['enable_dtmf_pad']);
variable_set('display_name', $form_state['values']['display_name']);
variable_set('from_uri', $form_state['values']['from_uri']);
variable_set('auth_user', $form_state['values']['auth_user']);
diff -Nru drupal7-mod-drucall-2.0.1/drucall.info
drupal7-mod-drucall-2.1/drucall.info
--- drupal7-mod-drucall-2.0.1/drucall.info 2014-02-04 21:27:37.0
+0100
+++ drupal7-mod-drucall-2.1/drucall.info2014-11-06 19:13:05.0
+0100
@@ -2,8 +2,13 @@
description = WebRTC SIP client for Drupal.
package = DruCall
core = 7.x
-dependencies[] = jssip
dependencies[] = jscommunicator
-dependencies[] = arbiterjs
configure = admin/config/drucall/settings
+
+; Information added by Drupal.org packaging script on 2014-11-06
+version = 7.x-2.1
+core = 7.x
+project = drucall
Bug#768930: unblock: pynag and syslog-nagios-bridge
On 10/11/14 20:56, Niels Thykier wrote: Control: tags -1 moreinfo On Mon, 10 Nov 2014 10:31:03 +0100 Daniel Pocock dan...@pocock.pro wrote: Package: release.debian.org syslog-nagios-bridge requires pynag 0.9.1+, older versions have a bug in check result file generation: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768928 I added a constraint in syslog-nagios-bridge well before the freeze so it would not propagate to testing until pynag 0.9.1 was uploaded: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763378 Note that the pynag upload in unstable is also cleaning out minified jquery and other things that make the package more compliant with Debian policy [...] Hi, I am afraid I will have to reject this request in its current form. The changes to pynag is beyond what can be reasonably reviewed and indeed it is not a targeted fix for #768928. The changes to syslog-nagios-bridge are reasonable and I could accept them, but I understand it is of no use without pynag as well. Can you please provide a targeted fix for pynag? This (just a few lines) could be dropped into debian/patches/checkresult_fix.patch https://github.com/pynag/pynag/commit/3aad1176bca4b2f39c2c851396d30647efbf2bed Clint, would you be happy to upload 0.8.9 with that or would you like me to NMU perhaps? Or is there any reason why the whole 0.9.1 should be considered for jessie? -- 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/54611dc7.6070...@pocock.pro
Bug#745475: broken auto-removal logic
Package: release.debian.org
Severity: serious
This autoremoval appears to be incorrect - the dependency on nagios3 can
also be satisfied by icinga
This dependency was changed in the most recent upload
On 22/04/14 06:39, Debian testing autoremoval watch wrote:
ganglia-nagios-bridge 1.1.0-2 is marked for autoremoval from testing on
2014-05-10
It (build-)depends on packages with these RC bugs:
737441: nagios3: [src:nagios3] Sourceless file (minified) (jquery)
http://anonscm.debian.org/gitweb/?p=pkg-monitoring/ganglia-nagios-bridge.git;a=blob;f=debian/control;h=bdaf436511e7f0897fb812249a94d65c2b748448;hb=HEAD
Depends: ${misc:Depends}, python, nagios3 | icinga
--
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/53561268.7050...@pocock.pro
Bug#738616: removing newer libasio-dev (v1.10) from unstable
Package: release.debian.org We would like the version of libasio-dev in unstable to revert to the version currently in testing (1.4.8-2) Can you please remove the v1.10.1-1 libasio-dev from unstable or let me know what action to take, e.g. should I upload a 1.4.8-3 package? Also, could you please comment on whether we should plan a transition for asio 1.10 to enter jessie? Markus is maintaining the package, reSIProcate is the only build dependency we know of and if there are no others then a formal transition probably isn't required. Is there an equivalent of apt-cache rdepends that can help us locate any other packages with a build dependency on libasio-dev? As it is a header library, no packages declare a runtime dependency on it. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52f9f0fe.10...@pocock.pro
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 11/02/14 11:49, Julien Cristau wrote: On Tue, Feb 11, 2014 at 10:44:30 +0100, Daniel Pocock wrote: Package: release.debian.org We would like the version of libasio-dev in unstable to revert to the version currently in testing (1.4.8-2) You might want to explain why. API changes make it incompatible Fedora and EPEL still carry 1.4.8 which is widely used by dependencies such as those mentioned below Can you please remove the v1.10.1-1 libasio-dev from unstable or let me know what action to take, e.g. should I upload a 1.4.8-3 package? No, we can't do that. And you shouldn't do that. What you can do is use an epoch to make the version number go backwards. Ok, I will do that and upload later today Also, could you please comment on whether we should plan a transition for asio 1.10 to enter jessie? Markus is maintaining the package, reSIProcate is the only build dependency we know of and if there are no others then a formal transition probably isn't required. Is there an equivalent of apt-cache rdepends that can help us locate any other packages with a build dependency on libasio-dev? As it is a header library, no packages declare a runtime dependency on it. wget -qO- http://ftp.debian.org/debian/dists/sid/main/source/Sources.gz | zcat | grep-dctrl -FBuild-Depends -sPackage libasio-dev Adjusting for contrib and non-free left as an exercise for the reader. Thanks for that feedback Looks like the following three packages are impacted by this build dependency: src:abiword src:ball src:resiprocate All those packages need patching to work with the new version of asio due to API changes Does the release team have any preference for making this a formal transition or we should just work it out informally between the maintainers of these packages? Markus, please have a brief look at https://wiki.debian.org/Teams/ReleaseTeam/Transitions -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fa04fa.7090...@pocock.pro
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 11/02/14 13:44, Markus Wanner wrote: On 02/11/2014 01:40 PM, Julien Cristau wrote: Please try to avoid versioned -dev packages. Unless you really really have to keep both versions around for years. Why is that? Keep in mind this is a headers-only library, i.e. it only ever ships with a -dev (and a -doc) package. There's no other way multiple versions of this library can be installed on a system. Julien, Fedora and EPEL6 still have 1.4.8 as well. We don't know how widely it is used in things that are not packaged (e.g. in private code that people run on Debian) If we release a versions libasio1.4-dev package and libasio1.10-dev concurrently in jessie it will mean people can transition more slowly but nothing will really break -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fa1e69.6030...@pocock.pro
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 11/02/14 14:03, Julien Cristau wrote: On Tue, Feb 11, 2014 at 13:58:17 +0100, Daniel Pocock wrote: On 11/02/14 13:44, Markus Wanner wrote: On 02/11/2014 01:40 PM, Julien Cristau wrote: Please try to avoid versioned -dev packages. Unless you really really have to keep both versions around for years. Why is that? Keep in mind this is a headers-only library, i.e. it only ever ships with a -dev (and a -doc) package. There's no other way multiple versions of this library can be installed on a system. Julien, Fedora and EPEL6 still have 1.4.8 as well. We don't know how widely it is used in things that are not packaged (e.g. in private code that people run on Debian) That's irrelevant, as far as I'm concerned. Not exactly - upstreams may be less likely to adapt their code for v1.10 and that means we end up having to make more local patches or leaving things out of Debian However, I'll check with the Fedora maintainer for asio-devel, maybe Fedora 21 can carry v1.10 If we release a versions libasio1.4-dev package and libasio1.10-dev concurrently in jessie it will mean people can transition more slowly but nothing will really break And if you don't they can still use the old version, either through the old package or through an unpackaged local version. Shipping libraries in Debian only makes sense if Debian packages use them, IMO. At the moment, there are 3 proper packages using the old version of libasio-dev and none of the upstreams have shown enthusiasm for the new version My feeling is that abiword and reSIProcate will continue using libasio1.4-dev in jessie while any new project will hopefully start with libasio-dev 1.10 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fa290d.9090...@pocock.pro
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 11/02/14 15:26, Andreas Beckmann wrote: On 2014-02-11 13:10, Markus Wanner wrote: On 02/11/2014 01:01 PM, Andreas Beckmann wrote: Or if you want to avoid using epochs, reupload 1.4.8 using as 1.10.really.1.4.8 as the upstream version, and upload 1.10 as 1.10.release to experimental. Once you upload upstream 1.11 you are back to normal version numbers without having used an epoch inbetween. Given that we are likely to switch to separate libasio1.4-dev and libasio1.10-dev packages, I think the epoch approach is less confusing, overall. Since it seems you need to introduce libasio1.4-dev anyway, it should be possible to fix this version mess without .really. versions and without using epochs. All it needs is a trip through NEW. Let me know if I should look into preparing a patch ... I already made an upload using epoch It is 1:1.4.8-3 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fa368b.3030...@pocock.pro
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 11/02/14 15:41, Daniel Pocock wrote: On 11/02/14 15:26, Andreas Beckmann wrote: On 2014-02-11 13:10, Markus Wanner wrote: On 02/11/2014 01:01 PM, Andreas Beckmann wrote: Or if you want to avoid using epochs, reupload 1.4.8 using as 1.10.really.1.4.8 as the upstream version, and upload 1.10 as 1.10.release to experimental. Once you upload upstream 1.11 you are back to normal version numbers without having used an epoch inbetween. Given that we are likely to switch to separate libasio1.4-dev and libasio1.10-dev packages, I think the epoch approach is less confusing, overall. Since it seems you need to introduce libasio1.4-dev anyway, it should be possible to fix this version mess without .really. versions and without using epochs. All it needs is a trip through NEW. Let me know if I should look into preparing a patch ... I already made an upload using epoch It is 1:1.4.8-3 I notice the upload hasn't actually built http://packages.qa.debian.org/a/asio.html reports that it is still 1.10.1-1 in unstable and no link to the build logs Has anybody else tried something else to deal with this package transition or reversion to 1.4.8? Or did I do something wrong when adding the epoch? -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fa8c3a.5060...@pocock.com.au
Bug#738616: removing newer libasio-dev (v1.10) from unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/02/14 22:18, Markus Wanner wrote: Daniel, On 02/11/2014 09:46 PM, Daniel Pocock wrote: Has anybody else tried something else to deal with this package transition or reversion to 1.4.8? Or did I do something wrong when adding the epoch? I think you did just fine, but PTS is lagging behind. See here: http://metadata.ftp-master.debian.org/changelogs/main/a/asio/asio_1.4.8-3_changelog I notice that everything seemed to fall into place shortly after sending that email - my reSIProcate packages are building now Does this allow us to close this bug? And at least degrade #738613 to non-serious? (Otherwise, your upload won't migrate to testing, either, I guess.) We should mark 738613 fixed in the new version I think On 02/11/2014 01:40 PM, Julien Cristau wrote: Please try to avoid versioned -dev packages. Unless you really really have to keep both versions around for years. Rethinking that, I agree. For effectively two debian packages (abiword and resiprocate, disregarding ball) that rely on libasio-dev, it's hardly worth the effort of maintaining two separate versions. The other point being that (this variant of) asio being a headers-only library doesn't change the fact that any -dev package is only used during a build, but not when running any program (binary). In other words, just like any other -dev package, an upgrade of it won't ever break a compiled binary. At the worst, it leads to an FTBFS (as 1.10.1 does for both, BTW). It is an awkward question - if the API change is mild and the new version is better in every way then killing of the old version (with enough time for a transition) is fair enough If there are any question marks over stability of the new version or if it is so much work that the packagers of resiprocate and abiword can't easily fix it, then the pain of keeping an old version libasio1.4-dev may be much less As a reSIProcate upstream, * We just released 1.9.0 with a dependency on asio 1.4.x * I'm happy to look at asio version for our 1.10.x release cycle. * only one part of reSIProcate uses asio, so I could also split the package upstream, reduce the scope for future conflicts like this -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJS+pWGAAoJEOm1uwJp1aqDITYQALlGaQpOyNJw3Vz3JtXd+us/ JDUBV94PZqhZSC4KVZeNSMY6n1jQufHpvbkVapXJDO4GgiCp4yWU/NtEVjCP07sl 8+YjJcLep783kI2YVkjm1Fo+6JeVXdQfE827663/h58jEX1U9Lk7bEhdM26u7VdQ n4JyY2GFS8BXO9sLAxopoo8xcT6RWW0GnZlvcjO0GuF1tXrLVII3BJBCCvxmSUkA MWu7FL6fUFI/JgGejQbiOl60i7GtlzCHlwlp0o3uBSvU1s6rQMoR+0J0Dbw9c5Og qi2mdF2N9dXeVA86EErWTvyobPcjI0Wg3uQSizIsLoK9uD79CKPqcA23bGfqie7x 5dv9ZOcY8Hpxm2S3V5UPmZvyKTNI4A6AbG1N+X2HnlUVK5++NkMsMb5QRW3y6oQ9 YD03EvFQfyAjIC8A1T4n0poTpxUM3rl9uyCqziZsEWOzbgjJaLOvwhsqAO7JHx3y sRFpSWn1J24blji270PJx4w/b3ZBD0zbXj6lhZDCNW9R3uqoVvxKwB5LyPlQKvTe bZ/z3/ZNByTlytlsN+ZVim9V3q/7tDsKqBL5QIqHcl1D+4ez5Nw9IPnE1iGtakBm l4Wx4JkYxfRdSLEgtXVZCWsD6Pte2Ftsj8eGKm8EwkdXmWjp5hW7Xm9XDbXMgrTT YKZ2l9NBfFqAdh6Ve8r+ =lMdP -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fa9586.4070...@pocock.com.au
Bug#725671: different source packages, co-ordinated release to jessie
Package: release.debian.org PostBooks has multiple source packages. Specifically, there is src:postbooks (the client) and src:postbooks-schema-(empty|quickstart|demo) The client can only be used with the matching postbooks-schema version Is there an automated way to ensure these packages (and future updates) all propagate to jessie together or not at all? -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52526f5f.4020...@pocock.com.au
Bug#725424: Fwd: [pkg-xtuple-maintainers] postbooks 4.0.2-6 MIGRATED to testing
On 05/10/13 20:34, Adam D. Barratt wrote: On Sat, 2013-10-05 at 21:21 +0300, Andrei POPESCU wrote: On Sb, 05 oct 13, 19:08:10, Daniel Pocock wrote: Package: release Thankfully there isn't an actual package in the archive with that name, or the maintainers would probably be rather confused by the bug. Why did 4.0.2-6 migrate to testing after I uploaded 4.1.0-2 today? http://packages.qa.debian.org/p/postbooks.html It didn't. It migrated to testing _yesterday_; specifically, as a result of the 2200UTC britney run yesterday, which would then have become visible on mirrors as a result of today's 0152 dinstall. Ok, I only got the email much later - thanks for explaining that sequence of events The script is run once a day, so will see packages that appeared in testing in the 0152 dinstall (from the 2200 britney run) and the 1352 dinstall (from the the 1000 britney run). 4.0.2-6 is not suitable for jessie, it doesn't give a good impression of the package and I would prefer that it is removed and that users wait for 4.1.0 to propagate It's been in testing for a couple of dinstalls already, and there's one more before the next britney run. We can indeed remove the package, but there's no way we can know if any testing user has installed it in the meantime. There is nothing critically broken about it, but if users install it, they will need to make some effort (maybe 20 minutes or more) to manually run the tool for upgrading their database to 4.1 when the 4.1 package hits jessie. Things like the desktop icon are missing and 4.1 includes some improved popups for errors that might otherwise generate bug reports. So if it is not a significant effort, please remove from jessie, but people who have installed it already won't be left high and dry, I'll be happy to help them with any issues they encounter when 4.1 propagates. I had opened an RC bug against 4.0.2-6 to keep it from propagating, I only closed it after uploading 4.1.0-2 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725380 That bug was opened at 2105UTC yesterday. The RC bug list generated by the BTS for the relevant britney run was prepared at 1800UTC, so did not contain the bug. In general, a this shouldn't migrate bug probably wants filing before the package reaches 9/10 days. I had been waiting for the next version to come out of NEW (it generates an extra binary pkg) and hadn't realised this until the last minute -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52505f1a.1030...@pocock.com.au
Re: Roll call for porters of architectures in sid and testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I'm particularly keen to see communication packages working on as many architectures as possible because otherwise two-way communications opportunities are missed if some users are excluded. In short, I'm not formally volunteering, but if people have trouble with any VoIP or communications packages on any of the ports, please hassle me, I'll try to help. I'm also very happy to accept feedback and patches from porters when wearing my upstream developer hat, so if people have trouble with any of my packages on ports, please contact me. Regards, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJSO2GLAAoJEOm1uwJp1aqDrDwQAJWC2L3hHQvlLInXeN9YxfEk cqx9+qNnnT1Tl9Pj2x0kLYxYyxyI0guhpqPH/nxjD6KOyfSLiecmtyfgjqSW9y7x KnrB4OicgXLla5hpSnk5iLOg5WVDRajR/LznsnR+abCUCP/7ltAqmu3CMY6ZrOYH HHk9IgfkOoL1tJSabhBXEdSHS6EXB4raMYRKgRzp55iJtmr+704VnmP6KVMxYjPz q4253QRgf/MhcAl2WMiH/iCOJIyEENmaMnlkMNcASVk11uVhUhYhSnUfWlRm//q3 V5vIca/DR7UVnlSiFblEK1Ir1kLBamhCKOVQD98hYt00Fho3yK35udJtKYukei+C ILeEV9odlUT3LJUbdw0nP3K9zn58x8YHP26HscsaDltNyYQWLGf5EeJUWqyxHVwZ mHEQlNppsT8jZMjvo6BoafNxQvVTvBrYqyDXNvloLBDRh38Ppcb6z5Qng2akyRC9 I9TLFwDE7lzP1lFs3IDKuGTSFLgHve7ZgKIEmlj3JioVjME8yyvl/Z7SSFGWooAQ ykBnq7SYrmQBqWXbJw1BpCl6l8JoLYIVqq4wgsm7Gjd5XFs6FwwFoaDxumHorl90 PP2Yw+RZJDLwePsnFAmONo06/dbCNLgyyQAuENwYS50MJGp6uBl/YPxtB6dqvezL RIwweOQnSBmZ8/k16xIX =s7HC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/523b618c.4020...@pocock.com.au
Bug#717420: update reSIProcate in stable from 1.8.5 - 1.8.12
On 21/07/13 20:15, Adam D. Barratt wrote: On Sat, 2013-07-20 at 20:26 +0200, Daniel Pocock wrote: Package: release.debian.org Severity: important Nope. Bugs in packages may have all kinds of severities, requests to update packages in stable are normal at best. (It would also be helpful if you used reportbug or otherwise normalised the usertags and titles when making such requests.) For the record, I had to dig the mail to which I'm replying out of a BTS mbox; it never reached the debian-release list, presumably due to the size of the diff. Ok, if I submit something like this again, I'll include a link to the git web diff We've found that versions of reSIProcate 1.8.11-4 are not reliable on non-Intel platforms. Does anyone actually use the package on such architectures? I don't know However, I understand it is important to ensure people have a positive experience with Debian and even if just one person tries this package on PowerPC or S/390 I wouldn't want to knowingly let them waste time on a flawed version of the package. In particular, essential code such as the MD5 implementation was not being compiled the right way for big endian systems. The code may appear to compile and run but as soon as a user tries to engage in a DIGEST authentication they will find that it fails to operate correctly. [...] A long list of other bug fixes is also included, several of them eliminate bugs that can cause a crash The cumulative effect of all bug fixes on the 1.8.x release branch brings a significant improvement in quality and convenience for end users. The _filtered_ diffstat is 189 files changed, 5819 insertions(+), 2235 A lot of that is because the autotools artifacts (e.g. Makefile.in) are quite big and have been regenerated on each release Other things can also be ignored, for example, there are lots of XML files for the Windows build system (Visual Studio) but those are ignored on Linux builds. All the changes in those files are ignored. I could provide a diff that eliminates changes in such files. deletions(-) and adds two new packages. We'd need a lot of convincing that the latter is worth doing, rather than just proving updates via backports (fwiw, I'm only aware of one occasion where a new package was introduced to a release once it was stable, and that was openssh-blacklist via security.d.o, which is a somewhat different situation). That is because I diffed the tag for the wheezy package against the tag on the unstable package If you are comfortable with the basic aim of updating this package, then I will merge the 1.8.12 upstream release with the original wheezy packaging artifacts and submit a more precise diff for final approval. The set of packages will then remain the same, no new package will be added. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ed1d9c.60...@pocock.com.au
Bug#704215: unblock: resiprocate - built against newer boost-dev
Package: release.debian.org Severity: normal I've found that one of the binaries, resiprocate-turn-server, needs to be built again with the latest gcc and boost-dev or it fails to run The root cause appears to be this issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654425 and the bug report concerning the impact on my package is: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704213 Please confirm if I should do the upload with a new version number (1.8.5-4), or if there is some other way to force it to be rebuilt for the existing version? If I upload a new version, there will be no changes except a changelog entry. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5155a3b5.7020...@pocock.com.au
Bug#704215: debdiff
No changes to code, just a rebuild on a machine with latest wheezy boost headers Here is the full debdiff: $ debdiff resiprocate_1.8.5-3.dsc resiprocate_1.8.5-4.dsc diff -Nru resiprocate-1.8.5/debian/changelog resiprocate-1.8.5/debian/changelog --- resiprocate-1.8.5/debian/changelog 2013-03-21 20:31:23.0 +0100 +++ resiprocate-1.8.5/debian/changelog 2013-03-29 16:17:37.0 +0100 @@ -1,3 +1,9 @@ +resiprocate (1.8.5-4) unstable; urgency=low + + * rebuild with latest boost headers (Closes: #704213) + + -- Daniel Pocock dan...@pocock.com.au Fri, 29 Mar 2013 15:15:27 + + resiprocate (1.8.5-3) unstable; urgency=low * log an error if TLS mappings file missing (Closes: #703644) -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5155b322.5020...@pocock.com.au
Bug#704215: unblock: resiprocate - built against newer boost-dev
On 29/03/13 17:56, Axel Beckert wrote: Hi, Daniel Pocock wrote: Please confirm if I should do the upload with a new version number (1.8.5-4), You seem to have uploaded that already, but I haven't seen any confirmation on debian-release for that. Despite... or if there is some other way to force it to be rebuilt for the existing version? ... there is a very common way to do such rebuilds called Binary NMU or binnmu for short. Why didn't you wait for the confirmation you requested? Axel, I'm sorry for the misunderstanding, I didn't realise that a positive confirmation was always needed to upload to unstable. Due to the holiday weekend, I won't be spending a lot of time at my desk and did the upload proactively so that the issue can be fixed and not hold up the release. I believe the binNMU would also be suitable in this case, as there is no change to the source or packaging artifacts. I'm quite happy for the release team to prefer a binNMU for 1.8.5-3 and not unblock 1.8.5-4. On 29/03/13 17:37, Evgeni Golov wrote: On 03/29/2013 03:22 PM, Daniel Pocock wrote: I've found that one of the binaries, resiprocate-turn-server, needs to be built again with the latest gcc and boost-dev or it fails to run Why was/is this not handled by a binNMU? Are there other packages (theoretically) affected? As for the impact on other packages: I would say there is a definite possibility that packages would have this bug if the following conditions exist: a) package compiled with gcc 4.7 b) libboost-dev 1.46 was present on the build machine at the time of compile The problem would only be observed in a binary when it first tries to use a thread. - reTurnServer starts a thread at startup, so the problem is noticed immediately. Binaries that only start threads some time later may not stop so obviously. - reTurnServer has a catch-block that catches exceptions and logs an error. Binaries that don't have such a catch block may appear to just stop mysteriously without any immediate clues about the problem. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5155d192.6070...@pocock.com.au
Bug#704215: unblock: resiprocate - built against newer boost-dev
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 29/03/13 20:37, Julien Cristau wrote: On Fri, Mar 29, 2013 at 18:38:26 +0100, Daniel Pocock wrote: Axel, I'm sorry for the misunderstanding, I didn't realise that a positive confirmation was always needed to upload to unstable. Due to the holiday weekend, I won't be spending a lot of time at my desk and did the upload proactively so that the issue can be fixed and not hold up the release. Don't worry, there's 0 chance of resiprocate holding up the release. These issues don't even impact my own use of the packages, I only share them in the hope that the wider user base will benefit from it. There are obviously many people out their in IT who keep their knowledge, bug fixes, etc to themselves and see it as a way of making a living. I've always had the impression that Debian strives to be the opposite of that, bringing people solutions openly, and that is all I've tried to do here when I discovered a problem today (on a public holiday too incidentally) and provided a detailed analysis, identification of the root cause and comments on how other packages may be impacted. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJRVfwuAAoJEOm1uwJp1aqDcWMP/1ZuiCVwUYbTkctEIcV8sn1D M7J7oNzcvTW2Sg25wnGMV9JadTR5cvRHRmAEI5r8Zt2hCSSuNZbRmPqyw80AYMU5 JgOIfVOKw7IIq2FTVpHt4EnBpZE+1C6jqfDJlsxSAatYv1Hi9ONF3kra7gyhK4wg FgDAbeP5Q5peO1hJ+OUrG/qp7KZR5BHX6JlYRHtJgQYxeUH2U1DuYbsdu2mCJZZf Yn4XGyhkw1wvGO1OE6apMae9Q2JhKOCLLMDw1TBINJTbPLfvqY2FBbYbHq65JF8u yQ/SBoIJ+izCvj2eWqd97ssarVCwECGXvu03ToAsf/qVGjOapiyrHJcgeYctrkVx OlPqlA2cKYFHWW3LKkP6YhhC92iGqzOttoOy5A7UIvtHnBEc6e3pqUCneeTfY5mS uMDY9LkQku6kq6PW8oCxpb+3nKLJu/OOfBl42aW9C4Yi/rjtMSn/i2oy/d41u6ua AgLyZEXHw8kNf5zhbsp3bk/6UTLIMwEKUyDGvFaeXoFTF/tkoIC87d/1+EmnfekN cumg4sa3EM9iBjIG6e4B5i++Cfwcj9tHP65sMh2IWmTK3xTrZuWrMtpYFhR9VFja 6jhwQeyrMXRiETzeQw/GMtYeFWFjo37aowErJ4eDUGQzQjwSbzGe8Pg4XZoFsEDO 8kLQhQ7ja7PGedOXooP9 =QDw0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5155fc2e.4060...@pocock.com.au
Bug#703650: unblock: resiprocate - added missing error message, more sane TLS config
Package: release.debian.org
Severity: normal
A user reported a problem with the default TLS config upstream, it is
fixed by this debdiff
diff -Nru resiprocate-1.8.5/debian/changelog resiprocate-1.8.5/debian/changelog
--- resiprocate-1.8.5/debian/changelog 2013-03-17 12:33:44.0 +0100
+++ resiprocate-1.8.5/debian/changelog 2013-03-21 20:31:23.0 +0100
@@ -1,3 +1,9 @@
+resiprocate (1.8.5-3) unstable; urgency=low
+
+ * log an error if TLS mappings file missing (Closes: #703644)
+
+ -- Daniel Pocock dan...@pocock.com.au Thu, 21 Mar 2013 20:12:33 +0100
+
resiprocate (1.8.5-2) unstable; urgency=low
* Remove proxy-auth headers after validating them (Closes: #697341)
diff -Nru resiprocate-1.8.5/debian/conf/repro.config
resiprocate-1.8.5/debian/conf/repro.config
--- resiprocate-1.8.5/debian/conf/repro.config 2012-08-08 15:13:05.0
+0200
+++ resiprocate-1.8.5/debian/conf/repro.config 2013-03-21 20:10:58.0
+0100
@@ -429,6 +429,9 @@
# the holder of a particular certificate to use any of the `mapped'
# `From:' addresses specified in the mappings file
#
+# Default: there is no default value: if this filename is not specified,
+# repro will not look for it
+#
# File format:
# common nameTABmapping,mapping,...
#
@@ -436,7 +439,7 @@
#TAB is exactly one tab
#mapping is `user@domain' or just `domain'
#
-CommonNameMappings = /etc/repro/tlsUserMappings.txt
+#CommonNameMappings = /etc/repro/tlsUserMappings.txt
diff -Nru
resiprocate-1.8.5/debian/patches/0003-log-an-error-if-TLS-mappings-file-missing.patch
resiprocate-1.8.5/debian/patches/0003-log-an-error-if-TLS-mappings-file-missing.patch
---
resiprocate-1.8.5/debian/patches/0003-log-an-error-if-TLS-mappings-file-missing.patch
1970-01-01 01:00:00.0 +0100
+++
resiprocate-1.8.5/debian/patches/0003-log-an-error-if-TLS-mappings-file-missing.patch
2013-03-21 20:11:27.0 +0100
@@ -0,0 +1,20 @@
+From: Daniel Pocock dan...@pocock.com.au
+Date: Thu, 21 Mar 2013 20:09:05 +0100
+Subject: log an error if TLS mappings file missing
+
+---
+ repro/ReproRunner.cxx |1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/repro/ReproRunner.cxx b/repro/ReproRunner.cxx
+index 8aaa7c3..9a77e6e 100644
+--- a/repro/ReproRunner.cxx
b/repro/ReproRunner.cxx
+@@ -1248,6 +1248,7 @@ ReproRunner::loadCommonNameMappings()
+ifstream mappingsFile(mappingsFileName.c_str());
+if(!mappingsFile)
+{
++ ErrLog( failed to open mappings file: mappingsFileName ,
aborting);
+ throw std::runtime_error(Error opening/reading mappings file);
+}
+
diff -Nru resiprocate-1.8.5/debian/patches/series
resiprocate-1.8.5/debian/patches/series
--- resiprocate-1.8.5/debian/patches/series 2013-03-17 12:28:37.0
+0100
+++ resiprocate-1.8.5/debian/patches/series 2013-03-21 20:11:27.0
+0100
@@ -1,2 +1,3 @@
0001-remove-Proxy-Authorization-headers-for-successful-Di.patch
0002-discard-repeated-requests-received-over-reliable-tra.patch
+0003-log-an-error-if-TLS-mappings-file-missing.patch
Bug#703650: unblock: resiprocate - added missing error message, more sane TLS config
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 21/03/13 22:07, Jonathan Wiltshire wrote: Control: tag -1 + moreinfo On Thu, Mar 21, 2013 at 09:39:00PM +0100, Daniel Pocock wrote: Package: release.debian.org Severity: normal A user reported a problem with the default TLS config upstream, it is fixed by this debdiff In accordance with the tightening freeze policy, we are no longer accepting fixes for bugs of severity 'important' without a very good reason. This was found by a user following the popular RTCquickstart.org instructions (which are aimed at Debian users): http://list.resiprocate.org/archive/repro-users/msg00455.html and every other user following that guide is likely to encounter the same bug. Any user who enables TLS will find repro refuses to start and has to turn on debugging to find out why, but even then it doesn't give them an error, just a clue in the last line of log output. The fix itself is very trivial (1 line of code to log a helpful error, and 1 line to make the default config valid) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJRS4bQAAoJEOm1uwJp1aqDHQ4P/18BgVNBSrnbKkp0e5ls3nDS i5AJOeoMcRL7aHq/+W9jSgzSQr21Ryyr5lyC5ofWis0qttVMQzar00Cv89bzitJd Vch3SE+iA57fSoXKcHXLzvRfv18z0vv7PcyfUWxwKOQry0yUhCEEWWZ4Ym/kN0E5 Tq25amHc0A/YpxYhcuBoLSIdgolwbxQLALvFYU5TYg/sTTbKDMvN1h6r4qSqhUna DnJpIzlaHaSF7TaRaCj/0hG1NwLIYeAR/yJe7PJ+Z6M9XBtOhfD7sqlZ7dINfYdO HUK3egdh0qj7MKQ6JEXfAjuDdBEK3RqCP6et3MMbDO/NYVCJ18hKzbaA73IKRXLL H9mKuSiUpcI1lXbnlYEOBUbfS/3c0RAsBjpeUizwqdzAvJ+4UNSUfWwxB73Bzjtg gP1cFmR3aJxlz3zDF/feUl0DC0rQmo3VtSyIXZ19KIJWLFumn01MqI5QJLge1UzA BWhyHPdbIJIdcEYbfhYHxhGj/+owx+wnfiKm4HVPppkUTuiyUrO+y77PHSe48kiq 54L0ejP9eccH6xhuSWsFEsgPYLA579t5Tn4JCtenLTLnq0unYjgH6kfGdyoZOZ4b HlGJHLmZqdUJfX/cPPRhtoxgbCG8+tJr8ybdq8dDUy1YqSoNvWMwGZyqqrMVjCUB e/TtSrmZFpH2wGaXb0GL =rDdc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/514b86d0.4050...@pocock.com.au
Bug#702458: [Pkg-xen-devel] unblock: xcp-xapi - urgent documentation fixes
On 18/03/13 07:02, Thomas Goirand wrote: On 03/07/2013 04:23 AM, Daniel Pocock wrote: Package: release.debian.org Severity: normal The current README.Debian is quite old It gives some advice that will lead to people having a broken system (e.g. no networking). It describes a procedure for configuring networking that is completely opposite to what has been described more recently on the upstream mailing list http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702337 I'm happy to overhaul this document and submit a debdiff for the release team to review - please confirm if this work should go ahead. No other files in the package will be changed. Hi Daniel and the release team, First, thanks Daniel, for taking care of this. I do appreciate such contributions. I agree the README is not perfect, though I don't agree it is such a disaster. The network configuration which I described in it does work, contrary to what Daniel says. Others also reported using this howto successfully. What's annoying though, is that to do it, you have to reboot under a broken networking setup for a while, to be able to do such a configuration, which is very annoying if you don't have a KVM over IP in your server. I have applied all of your git patches. Thanks for them. However, I cannot apply the part that changes paragraph 4.2, as it did work for me, and that I would not recommend removing all trace of the network interface (you would loose network if you reboot without XCP). The email on the list says that you must do exactly what I described, empty the /etc/network/interfaces file This works for me - I have done multiple reboots to test I also tried re-running the pif-reconfigure-ip a couple of times with the empty interfaces file, it definitely expects to work that way. It may be that it works differently for Linux bridge users, I use the Open vSwitch bridge. If I do not follow those exact steps, then the dom0 IP networking works, but XCP fails to add any domU to the xenbr0 bridge and they have to be bridged using manual brctl commands. I by the way believe that your paragraph IMPORTANT BUG is important to add. Mike told me Citrix guys would come back to me with a fix for #695221 (though it's been weeks I didn't hear about him yet). Cheers, Thomas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5146ba9c.3030...@pocock.com.au
Bug#703233: unblock: resiprocate - crash issue fixed
Package: release.debian.org
Severity: normal
There are two fixes, both using patches backported from the upstream
release branch
One of the issues is marked serious because it causes the process to
stop in certain situations.
The other is marked as important because it causes incompatibility with
FreeSWITCH PBXes
diff -Nru resiprocate-1.8.5/debian/changelog resiprocate-1.8.5/debian/changelog
--- resiprocate-1.8.5/debian/changelog 2012-08-08 15:02:29.0 +0200
+++ resiprocate-1.8.5/debian/changelog 2013-03-17 12:33:44.0 +0100
@@ -1,3 +1,10 @@
+resiprocate (1.8.5-2) unstable; urgency=low
+
+ * Remove proxy-auth headers after validating them (Closes: #697341)
+ * Discard repeated requests over reliable transport (Closes: #703232)
+
+ -- Daniel Pocock dan...@pocock.com.au Sun, 17 Mar 2013 12:30:47 +0100
+
resiprocate (1.8.5-1) unstable; urgency=low
* New upstream release
@@ -7,7 +14,6 @@
* Fix support for multiple ENUM carriers
* Fix issue with help text causing crash
* Fix clash between DIGEST and mutual TLS when used concurrently
- * Proposed for wheezy unblock (Closes: #681387)
-- Daniel Pocock dan...@pocock.com.au Wed, 08 Aug 2012 15:02:03 +0200
diff -Nru
resiprocate-1.8.5/debian/patches/0001-remove-Proxy-Authorization-headers-for-successful-Di.patch
resiprocate-1.8.5/debian/patches/0001-remove-Proxy-Authorization-headers-for-successful-Di.patch
---
resiprocate-1.8.5/debian/patches/0001-remove-Proxy-Authorization-headers-for-successful-Di.patch
1970-01-01 01:00:00.0 +0100
+++
resiprocate-1.8.5/debian/patches/0001-remove-Proxy-Authorization-headers-for-successful-Di.patch
2013-03-17 12:28:37.0 +0100
@@ -0,0 +1,61 @@
+From: Daniel Pocock dan...@pocock.com.au
+Date: Sun, 17 Mar 2013 12:09:48 +0100
+Subject: remove Proxy-Authorization headers for successful Digest Challenges
+ before forwarding message (closes: #697341) (upstream: r9886, fixed
+ in v1.8.6)
+
+---
+ repro/monkeys/DigestAuthenticator.cxx | 29 -
+ 1 file changed, 16 insertions(+), 13 deletions(-)
+
+diff --git a/repro/monkeys/DigestAuthenticator.cxx
b/repro/monkeys/DigestAuthenticator.cxx
+index c3a8af3..fbaa5e9 100644
+--- a/repro/monkeys/DigestAuthenticator.cxx
b/repro/monkeys/DigestAuthenticator.cxx
+@@ -116,7 +116,6 @@ DigestAuthenticator::process(repro::RequestContext rc)
+ pairHelper::AuthResult,Data result =
+ Helper::advancedAuthenticateRequest(*sipMessage, realm, a1, 3000);
// was 15
+
+-// Auths authHeaders = sipMessage-header(h_ProxyAuthorizations);
+ switch (result.first)
+ {
+ case Helper::Failed:
+@@ -135,22 +134,26 @@ DigestAuthenticator::process(repro::RequestContext rc)
+
+ // Delete the Proxy-Auth header for this realm.
+ // other Proxy-Auth headers might be needed by a downsteram node
+-/*
+-Auths::iterator i = authHeaders.begin();
+-Auths::iterator j = authHeaders.begin();
+-while( i != authHeaders.end() )
++if (sipMessage-exists(h_ProxyAuthorizations))
+ {
+- if (proxy.isMyDomain(i-param(p_realm)))
+- {
+- j = i++;
+- authHeaders.erase(j);
+- }
+- else
++ Auths authHeaders = sipMessage-header(h_ProxyAuthorizations);
++ Data realm = getRealm(rc);
++
++ // if we find a Proxy-Authorization header for a realm we
handle,
++ // asynchronously fetch the relevant userAuthInfo from the
database
++ for (Auths::iterator i = authHeaders.begin(); i !=
authHeaders.end(); )
+{
+- ++i;
++ if(i-exists(p_realm) isEqualNoCase(i-param(p_realm),
realm))
++ {
++ i = authHeaders.erase(i);
++ }
++ else
++ {
++ ++i;
++ }
+}
+ }
+-*/
++
+ if(!sipMessage-header(h_From).isWellFormed() ||
+sipMessage-header(h_From).isAllContacts())
+ {
diff -Nru
resiprocate-1.8.5/debian/patches/0002-discard-repeated-requests-received-over-reliable-tra.patch
resiprocate-1.8.5/debian/patches/0002-discard-repeated-requests-received-over-reliable-tra.patch
---
resiprocate-1.8.5/debian/patches/0002-discard-repeated-requests-received-over-reliable-tra.patch
1970-01-01 01:00:00.0 +0100
+++
resiprocate-1.8.5/debian/patches/0002-discard-repeated-requests-received-over-reliable-tra.patch
2013-03-17 12:28:37.0 +0100
@@ -0,0 +1,37 @@
+From: Daniel Pocock dan...@pocock.com.au
+Date: Sun, 17 Mar 2013 12:28:31 +0100
+Subject: discard repeated requests received over reliable transports (closes:
+ #703232) (upstream: r9998, fixed in v1.8.7)
+
+---
+ resip/stack
Bug#702458: unblock: xcp-xapi - urgent documentation fixes
On 17/03/13 17:29, Niels Thykier wrote: On 2013-03-06 21:46, Daniel Pocock wrote: On 06/03/13 21:42, Niels Thykier wrote: Control: retitle -1 unblock: xen-api/1.3.2-14 (pre-approval) On 2013-03-06 21:23, Daniel Pocock wrote: Package: release.debian.org Severity: normal The current README.Debian is quite old It gives some advice that will lead to people having a broken system (e.g. no networking). It describes a procedure for configuring networking that is completely opposite to what has been described more recently on the upstream mailing list http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702337 I'm happy to overhaul this document and submit a debdiff for the release team to review - please confirm if this work should go ahead. No other files in the package will be changed. I would be willing to consider this documentation fix if it indeed is as bad as you suggest. Though, I'd appreciate seeing a debdiff before saying yay or nay. Ok, I will collaborate with pkg-xen team to prepare a revised document and submit it to the release team for final approval XCP has been highlighted as a major feature of wheezy: http://www.debian.org/News/2012/20120425 so I think it is a good idea to make fixes like this. Hi, Any news on this? The documentation patch was submitted on the bug report I'm not sure if it has been released yet -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5145efbd.8010...@pocock.com.au
Bug#702458: unblock: xcp-xapi - urgent documentation fixes
Package: release.debian.org Severity: normal The current README.Debian is quite old It gives some advice that will lead to people having a broken system (e.g. no networking). It describes a procedure for configuring networking that is completely opposite to what has been described more recently on the upstream mailing list http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702337 I'm happy to overhaul this document and submit a debdiff for the release team to review - please confirm if this work should go ahead. No other files in the package will be changed. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5137a5a8.8040...@pocock.com.au
Bug#702458: unblock: xcp-xapi - urgent documentation fixes
On 06/03/13 21:42, Niels Thykier wrote: Control: retitle -1 unblock: xen-api/1.3.2-14 (pre-approval) On 2013-03-06 21:23, Daniel Pocock wrote: Package: release.debian.org Severity: normal The current README.Debian is quite old It gives some advice that will lead to people having a broken system (e.g. no networking). It describes a procedure for configuring networking that is completely opposite to what has been described more recently on the upstream mailing list http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702337 I'm happy to overhaul this document and submit a debdiff for the release team to review - please confirm if this work should go ahead. No other files in the package will be changed. I would be willing to consider this documentation fix if it indeed is as bad as you suggest. Though, I'd appreciate seeing a debdiff before saying yay or nay. Ok, I will collaborate with pkg-xen team to prepare a revised document and submit it to the release team for final approval XCP has been highlighted as a major feature of wheezy: http://www.debian.org/News/2012/20120425 so I think it is a good idea to make fixes like this. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5137ab3a.5080...@pocock.com.au
Bug#699857: unblock: dynalogin - fixes RC issue with oath_callback / strcmp semantics
Package: release.debian.org
Severity: normal
This is a brief fix (3 lines)
debdiff attached
It also makes minor fixes to the control file (update maintainer contact
details, correct VCS location)
diff -u dynalogin-0.9.14/debian/changelog dynalogin-0.9.14/debian/changelog
--- dynalogin-0.9.14/debian/changelog
+++ dynalogin-0.9.14/debian/changelog
@@ -1,3 +1,12 @@
+dynalogin (0.9.14-2) unstable; urgency=low
+
+ * Correct behavior of oath_callback (Closes: #699856)
+ * Tweak title and description text
+ * Update control file for migration from collab-maint to pkg-auth
+ * Remove deprecated DM-Upload-Allowed
+
+ -- Daniel Pocock dan...@pocock.com.au Tue, 05 Feb 2013 23:25:37 +0100
+
dynalogin (0.9.14-1) unstable; urgency=low
* Initial packaging. (Closes: #665831).
diff -u dynalogin-0.9.14/debian/control dynalogin-0.9.14/debian/control
--- dynalogin-0.9.14/debian/control
+++ dynalogin-0.9.14/debian/control
@@ -1,20 +1,19 @@
Source: dynalogin
Section: admin
Priority: optional
-Maintainer: Daniel Pocock dan...@pocock.com.au
-Uploaders: Stuart Teasdale s...@debian.org
+Maintainer: Debian Authentication Maintainers
pkg-auth-maintain...@lists.alioth.debian.org
+Uploaders: Daniel Pocock dan...@pocock.com.au
Build-Depends: cdbs, debhelper (= 8.0.0), libapr1-dev, liboath-dev,
unixodbc-dev, autotools-dev, pkg-config
Homepage: http://www.dynalogin.org/
Standards-Version: 3.9.3
-DM-Upload-Allowed: yes
-Vcs-Git: git://git.debian.org/collab-maint/dynalogin.git
-Vcs-Browser: http://git.debian.org/?p=collab-maint/dynalogin.git;a=summary
+Vcs-Git: git://git.debian.org/pkg-auth/dynalogin.git
+Vcs-Browser: http://git.debian.org/?p=pkg-auth/dynalogin.git;a=summary
Package: libdynalogin-1-0
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: dynalogin - two-factor HOTP authentication - implementation libs
+Description: two-factor HOTP authentication - implementation libs
dynalogin is a two-factor authentication framework based on the HOTP
(Open Authentication) algorithm. Dynalogin can store credentials in
any database supported by UNIXODBC, which makes the solution
@@ -32,7 +31,7 @@
Package: dynalogin-server
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: dynalogin - two-factor HOTP authentication - server daemon
+Description: two-factor HOTP authentication - server daemon
dynalogin is a two-factor authentication framework based on the HOTP
(Open Authentication) algorithm. Dynalogin can store credentials in
any database supported by UNIXODBC, which makes the solution
@@ -49,7 +48,7 @@
Section: web
Architecture: all
Depends: ${misc:Depends}
-Description: dynalogin - two-factor HOTP authentication - PHP authentication
+Description: two-factor HOTP authentication - PHP client
dynalogin is a two-factor authentication framework based on the HOTP
(Open Authentication) algorithm. Dynalogin can store credentials in
any database supported by UNIXODBC, which makes the solution
@@ -67,7 +66,7 @@
Section: web
Architecture: all
Depends: ${misc:Depends}, simpleid, dynalogin-client-php
-Description: dynalogin - two-factor HOTP authentication - OpenID provider
+Description: two-factor HOTP authentication - OpenID provider
dynalogin is a two-factor authentication framework based on the HOTP
(Open Authentication) algorithm. Dynalogin can store credentials in
any database supported by UNIXODBC, which makes the solution
only in patch2:
unchanged:
--- dynalogin-0.9.14.orig/libdynalogin/dynalogin.c
+++ dynalogin-0.9.14/libdynalogin/dynalogin.c
@@ -141,7 +141,7 @@
return -1;
}
- return strcmp(pvt-code, test_str);
+ return abs(strcmp(pvt-code, test_str));
}
dynalogin_result_t dynalogin_authenticate
only in patch2:
unchanged:
--- dynalogin-0.9.14.orig/libdynalogin/hotpdigest.c
+++ dynalogin-0.9.14/libdynalogin/hotpdigest.c
@@ -11,6 +11,7 @@
#include hotpdigest.h
#include stdio.h /* For snprintf, getline. */
+#include stdlib.h
#include string.h/* For strverscmp. */
#include gc.h
@@ -104,7 +105,7 @@
}
make_hex_string(_response_raw, _response, GC_MD5_DIGEST_SIZE);
- return strcmp (pvt-response, _response);
+ return abs(strcmp (pvt-response, _response));
}
Bug#698984: unblock: simpleid - fixes RC issue with OpenID 2.0 support
On 26/01/13 08:42, Adam D. Barratt wrote: Control: tags -1 + moreinfo On Sat, 2013-01-26 at 03:07 +0100, Daniel Pocock wrote: diff -Nru simpleid-0.8.1/debian/source/format simpleid-0.8.1/debian/source/format --- simpleid-0.8.1/debian/source/format 2013-01-26 03:04:50.0 +0100 +++ simpleid-0.8.1/debian/source/format 2013-01-26 01:25:30.0 +0100 @@ -1 +1 @@ -1.0 +3.0 (quilt) That change isn't mentioned in the changelog; why was it made? (See http://release.debian.org/wheezy/freeze_policy.html point number 1.) There were no other patches included in the package before I used gbp-pq to do the fix for #698037 and that required the upgrade of the source format If it is essential, I can make a 0.8.1-13 upload with the extra changelog detail against 0.8.1-11 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51039ff8.5060...@pocock.com.au
Bug#698984: unblock: simpleid - fixes RC issue with OpenID 2.0 support
On 26/01/13 14:09, Neil McGovern wrote: I believe the use of the 0.8.3 release is not RC, but it does fix one important bug and it also fixes the original RC bug without having to rely on the patching process (so I could delete debian/patches and revert to debian/source/format 1.0) Can you fix the RC bug, by itself, without changing the source format? Ok, I've done it that way now, by creating a debian-wheezy branch in the VCS This has been uploaded as 0.8.1-13 and a cumulative debdiff from 0.8.1-10 is attached post-wheezy the package will be 3.0 (quilt), and I will keep it that way in the VCS master branch If not, I'll simply remove it, simpleid-ldap and dynalogin from testing, especially as popcon seems to indicate that no one actually uses it, and it wasn't in a previous stable release. The lack of any two-factor authentication token solution in previous stable releases of Linux (Debian, RHEL and others) is probably not something to boast about... let me just check how many times my ssh server was probed today by people aspiring to try brute-force dictionary attacks I'd also speculate that the type of person trying two-factor authentication is not always allowing popcon to report info about their host - but whether it is 8 users or 8 million, I'm simply trying to provide a quality package for them. diff -u simpleid-0.8.1/debian/changelog simpleid-0.8.1/debian/changelog --- simpleid-0.8.1/debian/changelog +++ simpleid-0.8.1/debian/changelog @@ -1,3 +1,23 @@ +simpleid (0.8.1-13) unstable; urgency=low + + * Revert to 1.0 source format + + -- Daniel Pocock dan...@pocock.com.au Sat, 26 Jan 2013 16:36:11 +0100 + +simpleid (0.8.1-12) unstable; urgency=low + + * Add myself as uploader + + -- Daniel Pocock dan...@pocock.com.au Sat, 26 Jan 2013 03:02:02 +0100 + +simpleid (0.8.1-11) unstable; urgency=low + + * Send XRD 1.0 rather than XRDS-Simple (Closes: #698037) + * Migrate from collab-maint to pkg-auth + * Change to 3.0 (quilt) source format + + -- Daniel Pocock dan...@pocock.com.au Sat, 26 Jan 2013 01:24:36 +0100 + simpleid (0.8.1-10) unstable; urgency=low * Initial packaging (Closes: #665830). diff -u simpleid-0.8.1/debian/control simpleid-0.8.1/debian/control --- simpleid-0.8.1/debian/control +++ simpleid-0.8.1/debian/control @@ -1,13 +1,13 @@ Source: simpleid Section: web Priority: extra -Maintainer: Daniel Pocock dan...@pocock.com.au -Uploaders: Stuart Teasdale s...@debian.org +Maintainer: Debian Authentication Maintainers pkg-auth-maintain...@lists.alioth.debian.org +Uploaders: Daniel Pocock dan...@pocock.com.au Build-Depends: debhelper (= 8), cdbs (= 0.4.89) Standards-Version: 3.9.3 Homepage: http://simpleid.sourceforge.net/ -Vcs-Git: git://git.debian.org/collab-maint/simpleid.git -Vcs-Browser: http://git.debian.org/?p=collab-maint/simpleid.git;a=summary +Vcs-Git: git://git.debian.org/pkg-auth/simpleid.git +Vcs-Browser: http://git.debian.org/?p=pkg-auth/simpleid.git;a=summary Package: simpleid Architecture: all only in patch2: unchanged: --- simpleid-0.8.1.orig/simpleid/www/html/template.xtpl +++ simpleid-0.8.1/simpleid/www/html/template.xtpl @@ -295,7 +295,6 @@ !-- BEGIN: xrds --?xml version=1.0 encoding=UTF-8? xrds:XRDS xmlns=xri://$xrd*($v*2.0) xmlns:xrds=xri://$xrds xmlns:simple=http://xrds-simple.net/core/1.0; XRD version=2.0 -Typexri://$xrds*simple/Type !-- BEGIN: user_xrds -- Service priority=10 Typehttp://specs.openid.net/auth/2.0/signon/Type
Bug#698984: unblock: simpleid - fixes RC issue with OpenID 2.0 support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: release.debian.org Severity: normal This is a one-liner fix backported from upstream 0.8.3 to create a 0.8.1-11 package (replacing 0.8.1-10) It also updates debian/control to refer to the new pkg-auth team maintainership and VCS locations http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698037 I attach the debdiff contents There is another important issue that requires a backported fix, maybe not an RC issue, it is fixed upstream, I would prefer to take the latest upstream version, 0.8.3, which has been cut from a stable release branch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698396 I would appreciate feedback from the release team about willingness to accept 0.8.3. Given that OpenID is a distributed/networked protocol, I believe it is important to use and support the most recent version. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJRAyT+AAoJEOm1uwJp1aqDyEcQAIPCzTBFLsQKSMJzF2nJ6a6G JssfaljlzSxnO+AoO1NQEO9CEAL/KGRmZkvisfJLxlwlsA4xxXErR+LVAT78gL9n 9ZwzV99yQXjJOKZ+OO/c//xHLYEw9/K6bzhRjd8KD29391rIlwMDAgX9uJKkbnC2 S16ckcqOejMWam6M55eobcJyRpxHIggL4ysz5ERL8G1MA3HEy2Lxx9Q3ZzEiBBhO iCpGM756QRRCxYBs48xy5eimSdTiKg6EiF9qRXthpEVtysQ14MwvJfHrPyflRHBO hrDRFyGXIzzLN1TCuzlx6SPmqIBnIWrUZTs+8VA0hD3JfMtCSKZQkRWIw7rdbY9S zBXo1i0hHgHemjXnlZzt9Cicjc/+yWxa7KwNREbZa7E3sifTL1XD+HEIc6uRF9iz 2VWVTo+24s++6QFVQNGGrGZ2H6ko2HUhqUuTC0K1qzJz1FS+xbnMaG4Ac7tAg9Tu BXle/GA/z7eVqw8uUYBTxs3iTtK7HKMMwwMqJ04WdcJh91+ttw6dVM0BPOLZuRr+ YoFfuI4SjgHD83uMtVNHADk/iBjJMwLgPRTQ461qWs7aZy/2oxsCsT6N3r6CSZfE QBtVn3JsHSBIj5QJc6yjenbdzLcZJvsvwsyfMW0G41U/1VZqzos0vxpmKGmYlzt4 WuxfnwYyT9KOg61B8Nau =aIXg -END PGP SIGNATURE- diff -Nru simpleid-0.8.1/debian/changelog simpleid-0.8.1/debian/changelog --- simpleid-0.8.1/debian/changelog 2013-01-26 01:29:23.0 +0100 +++ simpleid-0.8.1/debian/changelog 2013-01-26 01:24:42.0 +0100 @@ -1,3 +1,10 @@ +simpleid (0.8.1-11) unstable; urgency=low + + * Send XRD 1.0 rather than XRDS-Simple (Closes: #698037) + * Migrate from collab-maint to pkg-auth + + -- Daniel Pocock dan...@pocock.com.au Sat, 26 Jan 2013 01:24:36 +0100 + simpleid (0.8.1-10) unstable; urgency=low * Initial packaging (Closes: #665830). diff -Nru simpleid-0.8.1/debian/control simpleid-0.8.1/debian/control --- simpleid-0.8.1/debian/control 2013-01-26 01:29:23.0 +0100 +++ simpleid-0.8.1/debian/control 2013-01-17 22:18:01.0 +0100 @@ -1,13 +1,12 @@ Source: simpleid Section: web Priority: extra -Maintainer: Daniel Pocock dan...@pocock.com.au -Uploaders: Stuart Teasdale s...@debian.org +Maintainer: Debian Authentication Maintainers pkg-auth-maintain...@lists.alioth.debian.org Build-Depends: debhelper (= 8), cdbs (= 0.4.89) Standards-Version: 3.9.3 Homepage: http://simpleid.sourceforge.net/ -Vcs-Git: git://git.debian.org/collab-maint/simpleid.git -Vcs-Browser: http://git.debian.org/?p=collab-maint/simpleid.git;a=summary +Vcs-Git: git://git.debian.org/pkg-auth/simpleid.git +Vcs-Browser: http://git.debian.org/?p=pkg-auth/simpleid.git;a=summary Package: simpleid Architecture: all diff -Nru simpleid-0.8.1/debian/patches/0001-return-XRD-1.0-rather-than-XRDS-Simple-content.patch simpleid-0.8.1/debian/patches/0001-return-XRD-1.0-rather-than-XRDS-Simple-content.patch --- simpleid-0.8.1/debian/patches/0001-return-XRD-1.0-rather-than-XRDS-Simple-content.patch 1970-01-01 01:00:00.0 +0100 +++ simpleid-0.8.1/debian/patches/0001-return-XRD-1.0-rather-than-XRDS-Simple-content.patch 2013-01-26 01:20:22.0 +0100 @@ -0,0 +1,20 @@ +From: Daniel Pocock dan...@pocock.com.au +Date: Sat, 26 Jan 2013 01:19:32 +0100 +Subject: return XRD-1.0 rather than XRDS-Simple content + +--- + simpleid/www/html/template.xtpl |1 - + 1 file changed, 1 deletion(-) + +diff --git a/simpleid/www/html/template.xtpl b/simpleid/www/html/template.xtpl +index 1043cc5..ae9de85 100644 +--- a/simpleid/www/html/template.xtpl b/simpleid/www/html/template.xtpl +@@ -295,7 +295,6 @@ + !-- BEGIN: xrds --?xml version=1.0 encoding=UTF-8? + xrds:XRDS xmlns=xri://$xrd*($v*2.0) xmlns:xrds=xri://$xrds xmlns:simple=http://xrds-simple.net/core/1.0; + XRD version=2.0 +-Typexri://$xrds*simple/Type + !-- BEGIN: user_xrds -- + Service priority=10 + Typehttp://specs.openid.net/auth/2.0/signon/Type diff -Nru simpleid-0.8.1/debian/patches/series simpleid-0.8.1/debian/patches/series --- simpleid-0.8.1/debian/patches/series1970-01-01 01:00:00.0 +0100 +++ simpleid-0.8.1/debian/patches/series2013-01-26 01:20:22.0 +0100 @@ -0,0 +1 @@ +0001-return-XRD-1.0-rather-than-XRDS-Simple-content.patch diff -Nru simpleid-0.8.1/debian/source/format simpleid-0.8.1/debian/source/format --- simpleid-0.8.1/debian/source/format 2013-01-26 01:29:23.0 +0100 +++ simpleid-0.8.1/debian/source
