Processed: Re: Bug#768920: RM: gobby-infinote/0.4.13-2
Processing commands for cont...@bugs.debian.org: # Thanks reportbug. retitle 768920 RM: gobby/0.4.13-2 Bug #768920 [release.debian.org] RM: gobby-infinote/0.4.13-2 Changed Bug title to 'RM: gobby/0.4.13-2' from 'RM: gobby-infinote/0.4.13-2' End of message, stopping processing here. Please contact me if you need assistance. -- 768920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141560623215774.transcr...@bugs.debian.org
Processed: tagging 768826
Processing commands for cont...@bugs.debian.org: tags 768826 - moreinfo Bug #768826 [release.debian.org] unblock: auctex/11.87-3 Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 768826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141560711522208.transcr...@bugs.debian.org
Bug#768923: unblock: rsskit/0.3-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please approve rsskit/0.3-3 to fix FTBFS bug #768749 via t-p-u. The bug is fixed in the version in unstable (0.4-1) but as this is a new upstream release with a SONAME bump it is not applicable for jessie. (My initial plan was to upload this new release way before the transition freeze but I was waiting for upstream comments for the relevant gnustep-make RC bug and was MIA for a few months so it didn't work out as intended). Proposed debdiff attached. unblock rsskit/0.3-3 diff --git a/debian/changelog b/debian/changelog index 2cd85b2..721024a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +rsskit (0.3-3) testing-proposed-updates; urgency=medium + + * debian/librsskit-dev.install: + * debian/librsskit0.install: Update for gnustep-make/2.6.6-3 (Closes: +#768749). + + -- Yavor Doganov ya...@gnu.org Mon, 10 Nov 2014 09:44:38 +0200 + rsskit (0.3-2) unstable; urgency=low * debian/rules (binary-arch): Invoke dh_makeshlibs. diff --git a/debian/librsskit-dev.install b/debian/librsskit-dev.install index 86500d5..6ebcde6 100644 --- a/debian/librsskit-dev.install +++ b/debian/librsskit-dev.install @@ -3,6 +3,7 @@ usr/lib/lib*.so usr/lib/GNUstep/Frameworks/RSSKit.framework/Versions/0/*.so usr/lib/GNUstep/Frameworks/RSSKit.framework/Versions/0/Headers usr/lib/GNUstep/Frameworks/RSSKit.framework/Versions/0/RSSKit +usr/lib/GNUstep/Frameworks/RSSKit.framework/Versions/Current usr/lib/GNUstep/Frameworks/RSSKit.framework/RSSKit usr/lib/GNUstep/Frameworks/RSSKit.framework/*.so usr/lib/GNUstep/Frameworks/RSSKit.framework/Headers diff --git a/debian/librsskit0.install b/debian/librsskit0.install index 9b9f871..96b2c80 100644 --- a/debian/librsskit0.install +++ b/debian/librsskit0.install @@ -1,5 +1,3 @@ usr/lib/libRSSKit.so.* usr/lib/GNUstep/Frameworks/RSSKit.framework/Versions/0/*.so.* usr/lib/GNUstep/Frameworks/RSSKit.framework/Versions/0/Resources -usr/lib/GNUstep/Frameworks/RSSKit.framework/Versions/Current -usr/lib/GNUstep/Frameworks/RSSKit.framework/Resources
Bug#768924: unblock: thunar/1.6.3-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package thunar Hi, Thunar in Jessie is affected by a regression due to Glib 2.42. This was tracked as bug #763726 (opened as severity normal) and the problem was that default application selection was broken (so double clicking on a file in Thunar doesn't open the user-chosen application). A patch went in the 1.6.3-2 package version, along with some documentation/descriptions fixes. The changelog entries are as follow and the debdiff is attached thunar (1.6.3-2) unstable; urgency=medium [ Evgeni Golov ] * Correct Vcs-* URLs to point to anonscm.debian.org [ Jackson Doak ] * Bump standards-version to 3.9.6 [ Yves-Alexis Perez ] * debian/control: - update long descriptions. - fix typo in thunar-dbg long description * debian/patches: - 02_fix-default-application-selection added, fix selection of default application for opening files, broken since glib 2.42.closes: #763726 -- Yves-Alexis Perez cor...@debian.org Thu, 30 Oct 2014 11:00:02 +0100 Thanks in advance, unblock thunar/1.6.3-2 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru thunar-1.6.3/debian/changelog thunar-1.6.3/debian/changelog --- thunar-1.6.3/debian/changelog 2013-05-21 23:55:11.0 +0200 +++ thunar-1.6.3/debian/changelog 2014-10-30 11:00:04.0 +0100 @@ -1,3 +1,21 @@ +thunar (1.6.3-2) unstable; urgency=medium + + [ Evgeni Golov ] + * Correct Vcs-* URLs to point to anonscm.debian.org + + [ Jackson Doak ] + * Bump standards-version to 3.9.6 + + [ Yves-Alexis Perez ] + * debian/control: +- update long descriptions. +- fix typo in thunar-dbg long description + * debian/patches: +- 02_fix-default-application-selection added, fix selection of default + application for opening files, broken since glib 2.42.closes: #763726 + + -- Yves-Alexis Perez cor...@debian.org Thu, 30 Oct 2014 11:00:02 +0100 + thunar (1.6.3-1) unstable; urgency=low * New upstream release. diff -Nru thunar-1.6.3/debian/control thunar-1.6.3/debian/control --- thunar-1.6.3/debian/control 2013-05-21 23:54:01.0 +0200 +++ thunar-1.6.3/debian/control 2014-10-30 10:59:53.0 +0100 @@ -9,10 +9,10 @@ libpcre3-dev, libjpeg-dev, libstartup-notification0-dev (= 0.4), intltool, libxfce4util-dev (= 4.10.0), libxfce4ui-1-dev (= 4.10.0), libnotify-dev, libgudev-1.0-dev [linux-any], xfce4-panel-dev (= 4.10.0) -Standards-Version: 3.9.3 +Standards-Version: 3.9.6 Homepage: http://thunar.xfce.org -Vcs-Svn: svn://svn.debian.org/pkg-xfce/desktop/trunk/thunar/ -Vcs-Browser: http://svn.debian.org/wsvn/pkg-xfce/desktop/trunk/thunar/ +Vcs-Svn: svn://anonscm.debian.org/pkg-xfce/desktop/trunk/thunar/ +Vcs-Browser: http://anonscm.debian.org/viewvc/pkg-xfce/desktop/trunk/thunar/ Package: libthunarx-2-dev Section: libdevel @@ -42,24 +42,24 @@ Breaks: thunar-data ( 1.2.3-3) Replaces: thunar-data ( 1.2.3-3) Description: File Manager for Xfce - Thunar is the file manager designed to be the default file manager of Xfce 4.6 - It has been designed to be fast and easy to use. + Thunar is the file manager designed to be the default file manager for the + Xfce desktop environment. It has been designed to be fast and easy to use. . - An Xfce plugin can manages the trash, if xfce4-panel is installed as well. - Please read README.Debian for volume management stuff. + Also included is an Xfce panel plugin which can manage the desktop trash. Package: thunar-data Section: xfce Architecture: all Depends: ${misc:Depends} Description: Provides thunar documentation, icons and translations - This package contains architecture-independent files for thunar. + This package contains architecture-independent files for thunar, the file + manager and file management libraries for Xfce desktop environment. Package: thunar-dbg Section: debug Architecture: any Priority: extra Depends: ${shlibs:Depends}, thunar (= ${binary:Version}), ${misc:Depends} -Description: debugging informations for thunar +Description: debugging information for thunar This package contains debugging symbols for thunar and libthunarx, the file - manager and file management libraries for Xfce Desktop Environment. + manager and file management libraries for Xfce desktop environment. diff -Nru thunar-1.6.3/debian/patches/02_fix-default-application-selection.patch thunar-1.6.3/debian/patches/02_fix-default-application-selection.patch --- thunar-1.6.3/debian/patches/02_fix-default-application-selection.patch 1970-01-01 01:00:00.0 +0100 +++
Bug#768886: unblock: beignet/0.9.3~dfsg-1
Control: merge 767961 -1 Hi Simon, Simon Richter wrote (09 Nov 2014 21:57:06 GMT) : unblock beignet/0.9.3~dfsg-1 This was asked on #767961 already = merging those bugs. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/857fz3lbat@boum.org
Processed: Re: Bug#768886: unblock: beignet/0.9.3~dfsg-1
Processing control commands: merge 767961 -1 Bug #767961 [release.debian.org] unblock: beignet/0.9.3~dfsg-1 Bug #768886 [release.debian.org] unblock: beignet/0.9.3~dfsg-1 Merged 767961 768886 -- 767961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767961 768886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b768886.141560745024830.transcr...@bugs.debian.org
Bug#768925: unblock: php-net-ldap/1:1.1.5-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, Please unblock package php-net-ldap/1:1.1.5-3. It fixes RC bug #768246 (unhandled symlink to directory conversion). The complete changelog is: php-net-ldap (1:1.1.5-3) unstable; urgency=medium [ Thijs Kinkhorst ] * Remove self from uploaders. [ Prach Pongpanich ] * Bump Standards-Version to 3.9.6. * Rebuild with pkg-php-tools 1.26, that don't ship test files in binary package (Closes: #768246). -- Prach Pongpanich prach...@gmail.com Mon, 10 Nov 2014 11:08:57 +0700 The debdiff is attached. Regards, Prach php-net-ldap_1.1.5-3.debdiff Description: Binary data
Bug#768402: unblock: simplesamlphp/1.13.1-1
On Sat, November 8, 2014 22:25, intrigeri wrote: I doubt it would add much value, but Jonathan's point was about getting enough information to assess severity, so perhaps you could tell the release team what severity you _would_ set for each of these bugs in the Debian BTS, if they were reported there? These are the issues fixed in this release. https://github.com/simplesamlphp/simplesamlphp/issues/97 - normal https://github.com/simplesamlphp/simplesamlphp/issues/99 - important https://github.com/simplesamlphp/simplesamlphp/issues/104 - important https://github.com/simplesamlphp/simplesamlphp/issues/109 - minor https://github.com/simplesamlphp/simplesamlphp/issues/114 - normal https://github.com/simplesamlphp/simplesamlphp/issues/117 - minor Thanks, Thijs -- 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/46ac6ca8b9a10d7ec2cd17efe3cdc73d.squir...@aphrodite.kinkhorst.nl
Processed: Re: Bug#768920: RM: gobby-infinote/0.4.13-2
Processing control commands: tags -1 + moreinfo jessie Bug #768920 [release.debian.org] RM: gobby/0.4.13-2 Added tag(s) jessie and moreinfo. -- 768920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b768920.14156097308294.transcr...@bugs.debian.org
Bug#768920: RM: gobby-infinote/0.4.13-2
Control: tags -1 + moreinfo jessie On 2014-11-10 7:27, Philipp Kern wrote: Please remove the following *source* packages from jessie: gobby 0.4.13-2 net6 1:1.3.14-2 obby 0.4.8-1 gobby-infinote has taken over the gobby package just in time for the jessie freeze. I do not want gobby-0.4 to stay around for jessie, it won't receive any more updates upstream. net6 and obby are support packages only around for gobby-0.4 and can (and should) hence go as well. What about sobby? That has both build- and runtime dependencies on both libobby and libnet6. Regards, Adam -- 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/f78676032897ab90d7cf16afb1ff5...@mail.adsl.funky-badger.org
Bug#768886: unblock: beignet/0.9.3~dfsg-1
Please unblock package beignet That's already been requested and declined in #767961: we are already too late for 0.9.3 in jessie, we need to decide whether 0.8 in jessie + 1.0 (expected soon) in jessie-backports is better or worse than just 1.0 in jessie-backports. Backporting the relevant changes is unfeasible, While that's probably true if you mean 'make 0.8 work with llvm 3.5', llvm 3.4 isn't being removed from jessie, it just isn't the default any more. I strongly suspect that #768691 is the same bug as #767387, which can be fixed by explicitly requesting 3.4: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767387#34 (Please don't upload that, it doesn't fix #768090 yet.) -- 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/54607daf.7080...@zoho.com
Bug#768139: unblock: mumble/1.2.8-1
On Thu, Nov 06, 2014 at 02:24:20PM +, Adam D. Barratt wrote: On 2014-11-06 2:52, Chris Knadle wrote: On 05.11.14, Adam D. Barratt wrote: Control: tags -1 + moreinfo On Wed, 2014-11-05 at 05:43 -0500, Chris Knadle wrote: mumble_1.2.8-1 contains a bugfix of priority important for allowing installation with pre-allocated user/group and the package has been in Unstable for 6 days without new bugs reported. Additionally 1.2.8-1 is marked as a stable upstream version, where the current 1.2.8~7~g76f6870-2 in Jessie is a snapshot. The differences in code between the versions are small -- I believe it's literrally only two patches incorporated. There's also debian/mumble-server.init | 143 +++ which doesn't appear to be mentioned afaics. *sigh* Thanks for catching this: it wasn't mentioned because I didn't make this change (AFAIK) and was unaware of it concerning this upload; [...] At one time I had accidentily included a debian/mumble-server.init (in a prior version) because it's something upstream includes in their PPA package for Ubuntu so I was testing using the file but had not committed it to git. [...] Other than that, do you have a suggestion as to how I should proceed from here? If it can happen really soon, I'd be happy with an upload that matches what you intended. Okay, a new mumble 1.2.8-2 has been uploaded into Unstable, and I believe it matches what we would all want. I was asked to revert the Standards-Version back to 3.9.5 so this upload is just slightly different from the last debdiff I sent; as such I've attaching a new debdiff and an interdiff against the first debdiff (mumble_1.2.8~7_to_1.2.8-1.diff) that I had started the bug with. The interdiff is just slightly larger than expected because the time zone changed back an hour (-0400 to -0500) since the last upload. Thanks much. -- Chris -- Chris Knadle chris.kna...@coredump.us diffstat for mumble-1.2.8~7~g76f6870 mumble-1.2.8 CHANGES | 42 debian/changelog | 29 debian/control |1 debian/mumble-server.postinst|4 - debian/patches/23-fix-pulseaudio-segfault-pt1.diff | 66 --- debian/patches/24-fix-pulseaudio-segfault-pt2.diff | 48 - debian/patches/25-make-logfiles-readable-by-adm.diff | 15 debian/patches/series|3 src/Version.h|2 src/mumble/PulseAudio.cpp| 26 ++- 10 files changed, 112 insertions(+), 124 deletions(-) diff -Nru mumble-1.2.8~7~g76f6870/CHANGES mumble-1.2.8/CHANGES --- mumble-1.2.8~7~g76f6870/CHANGES 2014-07-04 06:15:44.0 -0400 +++ mumble-1.2.8/CHANGES 2014-08-08 11:51:59.0 -0400 @@ -1,3 +1,36 @@ +2014-08-08 + Mikkel Krautz mik...@krautz.dk +82c483e scripts: modify git2cl.pl to work on the currently checked-out + branch rather than origin/master. + +2014-07-23 + Mikkel Krautz mik...@krautz.dk +0bf4aa3 PulseAudio: don't call pa_stream_drop() for empty + pa_stream_peek(). + +2014-07-20 + Mikkel Krautz mik...@krautz.dk +633f905 PulseAudio: stricter pa_stream_peek() validation. + +2014-07-02 + Mikkel Krautz mik...@krautz.dk +76f6870 PulseAudio: fix access to protected enums in AudioInput and + AudioOutput. +9529651 installer: add the ability to use a custom bzip2 directory in + the Win32 installer. +8609912 installer: fix ability to use a custom OpenSslDir when + building the Win32 installer. + +2014-06-29 + Mikkel Krautz mik...@krautz.dk +196a6f7 Allow building 1.2.x on Windows with + mumble-releng/buildenv/1.2.x/win32 + +2014-06-14 + Mikkel Krautz mik...@krautz.dk +414494d Bump version to 1.2.8 +173ec2b Update changelog + 2014-06-13 Mikkel Krautz mik...@krautz.dk aef3509 Add CA certificate filter to MumbleSSL::addSystemCA() to work @@ -31,6 +64,15 @@ 8323bd4 mumble: allow Log_macx.mm to build against the OS X 10.4 SDK (for universal builds). +2013-08-02 + Mikkel Krautz mik...@krautz.dk +228f844 mumble: fix VoiceRecorderDialog build on Apple clang-500.1.70. + +2013-06-08 + Mikkel Krautz mik...@krautz.dk +9c06ecf bonjour: use Qt::AutoConnection for BonjourServiceResolver's + QSocketNotifier slot. + 2013-06-01 Stefan Hacker d...@users.sourceforge.net 5ff038e Update changelog diff -Nru mumble-1.2.8~7~g76f6870/debian/changelog mumble-1.2.8/debian/changelog --- mumble-1.2.8~7~g76f6870/debian/changelog 2014-07-23 22:32:00.0 -0400 +++ mumble-1.2.8/debian/changelog 2014-11-09 11:10:08.0 -0500 @@ -1,3 +1,32 @@ +mumble (1.2.8-2) unstable; urgency=medium + + * debian/mumble-server.init + - Remove file as it was included accidentily + + -- Christopher Knadle
Processed: tagging 768865
Processing commands for cont...@bugs.debian.org: tags 768865 + jessie Bug #768865 {Done: Ivo De Decker ivo.dedec...@ugent.be} [release.debian.org] RM: a bunch of packages Added tag(s) jessie. thanks Stopping processing here. Please contact me if you need assistance. -- 768865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141561071414725.transcr...@bugs.debian.org
Bug#768315: unblock: util-linux/2.25.2-3
Russ Allbery [2014-11-06 22:13 -0800]: The concern with the service unit is that it's only a service unit with no corresponding init script. If the behavior is a good idea, we should do it regardless of the init system, I would think I agree. In Ubuntu we've carried this for a while now: | $ cat /etc/cron.weekly/fstrim | #!/bin/sh | # trim all mounted file systems which support it | /sbin/fstrim --all || true This is init system agnostic, and with anacron it also works nicely on desktops. Of course, if in your view as a maintainer this functionality isn't ready for jessie or you don't want to support it, just backing out of the change also works. It also took us quite some time in Ubuntu to enable it by default, and we did extensive measurements to see which approach is best. But not trimming SSDs is really quite bad these days, so from my POV it would be quite prudent to include either the timer or the cron job in jessie. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
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#768786: unblock: wxglade/0.6.8-2.2
On Sun, Nov 9, 2014 at 8:10 AM, Georges Khaznadar georges.khazna...@free.fr wrote: Please Vincent, go ahead! and many thanks in advance. If the unblock query for wxglade-0.7.0 is accepted, wxglade will be part of Jessie, but this is not sure. So please upload wxglade_0.6.8-2.2 now :) Thanks (both to you and to Jonathan for approving the upload); uploaded wxglade/0.6.8-2.2 to t-p-u just now. Regards, Vincent -- 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/CACZd_tDgacb33RAWc+6iYKZDBZiMszG3Az=6a8vpt6nsun1...@mail.gmail.com
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.'), ); +
Processed: tagging 768402
Processing commands for cont...@bugs.debian.org: tags 768402 - moreinfo Bug #768402 [release.debian.org] unblock: simplesamlphp/1.13.1-1 Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 768402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141561508218111.transcr...@bugs.debian.org
Bug#768139: marked as done (unblock: mumble/1.2.8-1)
Your message dated Mon, 10 Nov 2014 10:49:42 + with message-id 2ce02c8f08f7f77bba697715c56d1...@mail.adsl.funky-badger.org and subject line Re: Bug#768139: unblock: mumble/1.2.8-1 has caused the Debian Bug report #768139, regarding unblock: mumble/1.2.8-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mumble mumble_1.2.8-1 contains a bugfix of priority important for allowing installation with pre-allocated user/group and the package has been in Unstable for 6 days without new bugs reported. Additionally 1.2.8-1 is marked as a stable upstream version, where the current 1.2.8~7~g76f6870-2 in Jessie is a snapshot. The differences in code between the versions are small -- I believe it's literrally only two patches incorporated. debdiff attached. I would have uploaded 1.2.8-1 earlier but my laptop had a hardware failure and didn't have other hardware to read the disk. [The Lenovo T61p uses an Nvidia G84 GPU which was misdesigned such that it eventually fails, requiring motherboard replacement.] I and my package sponsor were unaware that the sid-jessie transition time had been extended from 5 to 10 days for October. Thanks much. -- Chris -- Chris Knadle chris.kna...@coredump.us diffstat for mumble-1.2.8~7~g76f6870 mumble-1.2.8 CHANGES | 42 debian/changelog | 22 ++ debian/control |1 debian/mumble-server.postinst|4 - debian/patches/23-fix-pulseaudio-segfault-pt1.diff | 66 --- debian/patches/24-fix-pulseaudio-segfault-pt2.diff | 48 - debian/patches/25-make-logfiles-readable-by-adm.diff | 15 debian/patches/series|3 src/Version.h|2 src/mumble/PulseAudio.cpp| 26 ++- 10 files changed, 105 insertions(+), 124 deletions(-) diff -Nru mumble-1.2.8~7~g76f6870/CHANGES mumble-1.2.8/CHANGES --- mumble-1.2.8~7~g76f6870/CHANGES 2014-07-04 06:15:44.0 -0400 +++ mumble-1.2.8/CHANGES 2014-08-08 11:51:59.0 -0400 @@ -1,3 +1,36 @@ +2014-08-08 + Mikkel Krautz mik...@krautz.dk +82c483e scripts: modify git2cl.pl to work on the currently checked-out + branch rather than origin/master. + +2014-07-23 + Mikkel Krautz mik...@krautz.dk +0bf4aa3 PulseAudio: don't call pa_stream_drop() for empty + pa_stream_peek(). + +2014-07-20 + Mikkel Krautz mik...@krautz.dk +633f905 PulseAudio: stricter pa_stream_peek() validation. + +2014-07-02 + Mikkel Krautz mik...@krautz.dk +76f6870 PulseAudio: fix access to protected enums in AudioInput and + AudioOutput. +9529651 installer: add the ability to use a custom bzip2 directory in + the Win32 installer. +8609912 installer: fix ability to use a custom OpenSslDir when + building the Win32 installer. + +2014-06-29 + Mikkel Krautz mik...@krautz.dk +196a6f7 Allow building 1.2.x on Windows with + mumble-releng/buildenv/1.2.x/win32 + +2014-06-14 + Mikkel Krautz mik...@krautz.dk +414494d Bump version to 1.2.8 +173ec2b Update changelog + 2014-06-13 Mikkel Krautz mik...@krautz.dk aef3509 Add CA certificate filter to MumbleSSL::addSystemCA() to work @@ -31,6 +64,15 @@ 8323bd4 mumble: allow Log_macx.mm to build against the OS X 10.4 SDK (for universal builds). +2013-08-02 + Mikkel Krautz mik...@krautz.dk +228f844 mumble: fix VoiceRecorderDialog build on Apple clang-500.1.70. + +2013-06-08 + Mikkel Krautz mik...@krautz.dk +9c06ecf bonjour: use Qt::AutoConnection for BonjourServiceResolver's + QSocketNotifier slot. + 2013-06-01 Stefan Hacker d...@users.sourceforge.net 5ff038e Update changelog diff -Nru mumble-1.2.8~7~g76f6870/debian/changelog mumble-1.2.8/debian/changelog --- mumble-1.2.8~7~g76f6870/debian/changelog 2014-07-23 22:32:00.0 -0400 +++ mumble-1.2.8/debian/changelog 2014-10-28 15:54:13.0 -0400 @@ -1,3 +1,25 @@ +mumble (1.2.8-1) unstable; urgency=medium + + * New upstream stable release from 2014-08-09 + * debian/control: + - Remove uploader Thorvald Natvig thorv...@debian.org due to +inactivity; thanks very much for your prior
Bug#768967: unblock: python-requests-kerberos/0.5-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, My last upload of python-requests-kerberos fixed CVE-2014-8650: failure to handle mutual authentication (Closes: #768408) reported by the security team (debdiff including upstream patch is attached). Please unblock python-requests-kerberos/0.5-2 Cheers, Thomas Goirand (zigo) diff -Nru python-requests-kerberos-0.5/debian/changelog python-requests-kerberos-0.5/debian/changelog --- python-requests-kerberos-0.5/debian/changelog 2014-06-27 06:37:32.0 + +++ python-requests-kerberos-0.5/debian/changelog 2014-11-10 13:25:13.0 + @@ -1,3 +1,11 @@ +python-requests-kerberos (0.5-2) unstable; urgency=high + + * CVE-2014-8650: failure to handle mutual authentication. Applied upstream +patch: CVE-2014-8650_Handle_mutual_authentication.patch (Closes: #768408). +Thanks to Salvatore Bonaccorso car...@debian.org for reporting it. + + -- Thomas Goirand z...@debian.org Mon, 10 Nov 2014 21:22:51 +0800 + python-requests-kerberos (0.5-1) unstable; urgency=medium * Initial release. (Closes: #752858) diff -Nru python-requests-kerberos-0.5/debian/patches/CVE-2014-8650_Handle_mutual_authentication.patch python-requests-kerberos-0.5/debian/patches/CVE-2014-8650_Handle_mutual_authentication.patch --- python-requests-kerberos-0.5/debian/patches/CVE-2014-8650_Handle_mutual_authentication.patch 1970-01-01 00:00:00.0 + +++ python-requests-kerberos-0.5/debian/patches/CVE-2014-8650_Handle_mutual_authentication.patch 2014-11-10 13:25:13.0 + @@ -0,0 +1,39 @@ +Description: CVE-2014-8650: Handle mutual authentication + Make certain that responses always pass through handle_other() to provide + mutual authentication before returning them to the user. +Origin: upstream, https://github.com/mkomitee/requests-kerberos/commit/9c1e08cc17bb6950455a85d33d391ecd2bce6eb6.patch +Author: Michael Komitee komi...@deshaw.com +Date: Fri, 8 Aug 2014 17:47:42 -0400 +Bug-Debian: https://bugs.debian.org/768408 +Index: python-requests-kerberos/requests_kerberos/kerberos_.py +=== +--- python-requests-kerberos.orig/requests_kerberos/kerberos_.py 2014-06-12 09:10:24.0 +0800 python-requests-kerberos/requests_kerberos/kerberos_.py 2014-11-10 21:24:56.0 +0800 +@@ -251,7 +251,7 @@ + if response.status_code == 401: + _r = self.handle_401(response, **kwargs) + log.debug(handle_response(): returning {0}.format(_r)) +-return _r ++return self.handle_response(_r, **kwargs) + else: + _r = self.handle_other(response) + log.debug(handle_response(): returning {0}.format(_r)) +Index: python-requests-kerberos/test_requests_kerberos.py +=== +--- python-requests-kerberos.orig/test_requests_kerberos.py 2014-11-10 21:24:56.0 +0800 python-requests-kerberos/test_requests_kerberos.py 2014-11-10 21:24:56.0 +0800 +@@ -403,10 +403,14 @@ + response.connection = connection + response._content = + response.raw = raw ++ + auth = requests_kerberos.HTTPKerberosAuth() ++auth.handle_other = Mock(return_value=response_ok) ++ + r = auth.handle_response(response) + + self.assertTrue(response in r.history) ++auth.handle_other.assert_called_with(response_ok) + self.assertEqual(r, response_ok) + self.assertEqual(request.headers['Authorization'], 'Negotiate GSSRESPONSE') + connection.send.assert_called_with(request) diff -Nru python-requests-kerberos-0.5/debian/patches/series python-requests-kerberos-0.5/debian/patches/series --- python-requests-kerberos-0.5/debian/patches/series 2014-06-27 06:37:32.0 + +++ python-requests-kerberos-0.5/debian/patches/series 2014-11-10 13:25:13.0 + @@ -1,2 +1,3 @@ disable-broken-test-in-python3.patch fix-setup.py-to-work-with-python3.patch +CVE-2014-8650_Handle_mutual_authentication.patch
Bug#768970: unblock: openstack-pkg-tools/17
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, The version 16 of openstack-pkg-tools attempted to support systemd, but it wasn't creating /var/run/PROJECT-NAME, and therefore, it isn't possible to start daemons properly if using systemd in Jessie. Version 17 corrects the problem, together with adding the possibility to *not* use --config-file, as this is needed to fix another bug. Please unblock openstack-pkg-tools/17. Once this upload is approved, I'll have to proceed with uploading updates for all OpenStack core packages, which is needed anyway to add new Debconf translations which were sent to the BTS. Cheers, Thomas Goirand (zigo) diff --git a/debian/changelog b/debian/changelog index 84a6a18..dd170aa 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +openstack-pkg-tools (17) unstable; urgency=medium + + * Make it possible to have no --config-file= argument for the daemon. + * Adds a RuntimeDirectory=/var/run/${PROJECT_NAME} in the systemd template, +so that /var/run/${PROJECT_NAME} can be created on boot (Closes: #767711). + + -- Thomas Goirand z...@debian.org Wed, 29 Oct 2014 00:31:49 +0800 + openstack-pkg-tools (16) unstable; urgency=medium * Fix some upstart job generation handling for murano-agent. diff --git a/init-template/init-script-template b/init-template/init-script-template index 810fc34..0326b5d 100644 --- a/init-template/init-script-template +++ b/init-template/init-script-template @@ -29,7 +29,9 @@ if [ -z ${CONFIG_FILE} ] ; then CONFIG_FILE=/etc/${PROJECT_NAME}/${PROJECT_NAME}.conf fi LOGFILE=/var/log/${PROJECT_NAME}/${NAME}.log -DAEMON_ARGS=${DAEMON_ARGS} --config-file=${CONFIG_FILE} +if [ -z ${NO_OPENSTACK_CONFIG_FILE_DAEMON_ARG} ] ; then + DAEMON_ARGS=${DAEMON_ARGS} --config-file=${CONFIG_FILE} +fi # Exit if the package is not installed [ -x $DAEMON ] || exit 0 diff --git a/init-template/pkgos-gen-systemd-unit b/init-template/pkgos-gen-systemd-unit index 0ce0858..8168319 100755 --- a/init-template/pkgos-gen-systemd-unit +++ b/init-template/pkgos-gen-systemd-unit @@ -35,6 +35,7 @@ User=${SYSTEM_USER} Group=${SYSTEM_GROUP} ExecStart=${SCRIPTNAME} systemd-start ExecStop=${SCRIPTNAME} systemd-stop +RuntimeDirectory=/var/run/${PROJECT_NAME} PIDFile=/var/run/${PROJECT_NAME}/${NAME}.pid Restart=on-failure Type=forking
Bug#768971: unblock: intel-vaapi-driver/1.4.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package intel-vaapi-driver. It fixes a segmentation fault on unsupported platforms (Intel graphics chip without VA-API support) as reported on the upstream mailing list [1]. unblock intel-vaapi-driver/1.4.1-2 Cheers [1] http://lists.freedesktop.org/archives/libva/2014-October/002799.html -- Sebastian Ramacher diff -Nru intel-vaapi-driver-1.4.1/debian/changelog intel-vaapi-driver-1.4.1/debian/changelog --- intel-vaapi-driver-1.4.1/debian/changelog 2014-10-24 13:49:05.0 +0200 +++ intel-vaapi-driver-1.4.1/debian/changelog 2014-11-10 13:59:50.0 +0100 @@ -1,3 +1,10 @@ +intel-vaapi-driver (1.4.1-2) unstable; urgency=medium + + * debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch: Apply +upstream patch to avoid segmentation faults on unsupported platforms. + + -- Sebastian Ramacher sramac...@debian.org Mon, 10 Nov 2014 13:59:29 +0100 + intel-vaapi-driver (1.4.1-1) unstable; urgency=medium * New upstream release. diff -Nru intel-vaapi-driver-1.4.1/debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch intel-vaapi-driver-1.4.1/debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch --- intel-vaapi-driver-1.4.1/debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch 1970-01-01 01:00:00.0 +0100 +++ intel-vaapi-driver-1.4.1/debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch 2014-11-10 13:47:53.0 +0100 @@ -0,0 +1,31 @@ +Description: Avoid segfailt on unsupported platforms + Call preinit_hw_codec callback after successful initialization to avoid segment + fault issue on unsupported platforms. +Origin: upstream, + http://cgit.freedesktop.org/vaapi/intel-driver/commit/?h=v1.4-branchid=eb097b1a39b69af76b5575835255cb4653195c1c +Last-Update: 2014-11-10 + +diff --git a/src/i965_drv_video.c b/src/i965_drv_video.c +index ba7c7be..e768537 100644 +--- a/src/i965_drv_video.c b/src/i965_drv_video.c +@@ -5669,9 +5669,6 @@ i965_Init(VADriverContextP ctx) + break; + } + +-if (i965-codec_info-preinit_hw_codec) +-i965-codec_info-preinit_hw_codec(ctx, i965-codec_info); +- + if (i == ARRAY_ELEMS(i965_sub_ops)) { + switch (i965-intel.device_id) { + #undef CHIPSET +@@ -5697,6 +5694,9 @@ i965_Init(VADriverContextP ctx) + + i965-current_context_id = VA_INVALID_ID; + ++if (i965-codec_info i965-codec_info-preinit_hw_codec) ++i965-codec_info-preinit_hw_codec(ctx, i965-codec_info); ++ + return VA_STATUS_SUCCESS; + } else { + i--; diff -Nru intel-vaapi-driver-1.4.1/debian/patches/series intel-vaapi-driver-1.4.1/debian/patches/series --- intel-vaapi-driver-1.4.1/debian/patches/series 2014-06-16 10:28:59.0 +0200 +++ intel-vaapi-driver-1.4.1/debian/patches/series 2014-11-10 13:48:20.0 +0100 @@ -1 +1,2 @@ 0001-Fix_FTBFS_on_kFreeBSD.patch +0002-avoid_segfault_on_unsupported_platforms.patch signature.asc Description: Digital signature
Bug#768975: RM: ironic/2014.1-9, tuskar/0.4.2-3, tuskar-ui/0.1.0-2, tripleo-heat-templates/0.6.1-1, tripleo-image-elements/0.7.1-1, python-os-apply-config/0.1.14-1, python-os-cloud-config/0.0.2-1, pyt
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi, A number of OpenStack packages are IMO not ready for being release in a Stable version of Debian. Therefore, I would like to have them removed from Jessie. Here's the list. It consists of packages which are part of the TripleO release (eg: OpenStack on OpenStack): tuskar/0.4.2-3 tuskar-ui/0.1.0-2 tripleo-heat-templates/0.6.1-1 tripleo-image-elements/0.7.1-1 python-os-apply-config/0.1.14-1 python-os-cloud-config/0.0.2-1 python-os-collect-config/0.1.15-1 python-os-refresh-config/0.1.2-1 Please remove them all from Jessie. As for Ironic, there's no nova driver in Icehouse (the version of OpenStack which is in Jessie), so please also remove: ironic/2014.1-9 Cheers, Thomas Goirand (zigo) -- 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/20141110141153.26151.44045.report...@buzig.gplhost.com
Bug#768976: unblock: fail2ban/0.9.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package fail2ban We have 0.8.13 in jessie ATM and I have released 0.9.1 and uploaded 0.9.1-1 just few days too short of a freeze - 10days (why didn't I change urgency? ;)) [2014-10-28] Accepted fail2ban 0.9.1-1 (source all) into unstable (Yaroslav Halchenko) 0.9.1 is the 2nd release in the 0.9.0 line and I had 0.9.0 in experimental for a while. So far it shows great promise to be very stable and much more versatile than 0.8.x -- we introduced multiline matching, eliminated divergance between Debian's and upstream jail.conf definitions, extended testing a lot (92% code coverage). After the release I haven't seen major bug reports (there is one minor typo to be fixed) and I have high confidence that this release would be a much better fit to maintain in Debian jessie (instead of now very stable but aging fast 0.8.). debdiff would be infeasible (we also made it a proper fail2ban python module instead of a bunch of internal submodules), but let me know if I need to provide more lines of argumentation to feature unblock unblock fail2ban/0.9.1-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141110141221.21835.35354.report...@hopa.kiewit.dartmouth.edu
Bug#768981: unblock: nipy/0.3.0+git262-gbb838d7-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nipy It was removed from jessie a year ago due to a test failing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729594 which was resolved also long ago, but I forgot to close this bug report :-/ nipy built fine across all architectures https://buildd.debian.org/status/package.php?p=nipysuite=unstable almost a month ago and I have closed that bugreport now Sorry for forgetting about this one for a while unblock nipy/0.3.0+git262-gbb838d7-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141110144810.24379.89752.report...@hopa.kiewit.dartmouth.edu
Bug#768786: marked as done (unblock: wxglade/0.6.8-2.2)
Your message dated Mon, 10 Nov 2014 16:28:26 +0100 with message-id 20141110152826.gn2...@betterave.cristau.org and subject line Re: Bug#768786: unblock: wxglade/0.6.8-2.2 has caused the Debian Bug report #768786, regarding unblock: wxglade/0.6.8-2.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal X-Debbugs-CC: georg...@debian.org Hi, I'd like to upload wxglade/0.6.8-2.2 as a NMU to testing-proposed-updates to fix RC bug #766743. I'm suggesting an upload to t-p-u because the version of wxglade in sid contains changes that don't look suitable for jessie at this point (among other things, a new upstream release); I just cherrypicked the relevant changes from the package in sid (where this bug is marked as fixed). AFAIK it's not possible to upload a package to the delayed queue for t-p-u, so George, I've cc-ed you in this unblock request; please shout if you don't want me to upload this for some reason. unblock wxglade/0.6.8-2.2 diff -Nru wxglade-0.6.8/debian/changelog wxglade-0.6.8/debian/changelog --- wxglade-0.6.8/debian/changelog 2014-10-12 19:55:16.0 -0700 +++ wxglade-0.6.8/debian/changelog 2014-11-09 01:33:17.0 -0800 @@ -1,3 +1,11 @@ +wxglade (0.6.8-2.2) testing-proposed-updates; urgency=medium + + * Non-maintainer upload. + * modified common.py assigned icons_path to '/usr/share/wxglade/icons' +Closes: #766743 + + -- Vincent Cheng vch...@debian.org Sun, 09 Nov 2014 01:32:57 -0800 + wxglade (0.6.8-2.1) unstable; urgency=low * Non-maintainer upload. diff -Nru wxglade-0.6.8/debian/patches/70-common.py.patch wxglade-0.6.8/debian/patches/70-common.py.patch --- wxglade-0.6.8/debian/patches/70-common.py.patch 1969-12-31 16:00:00.0 -0800 +++ wxglade-0.6.8/debian/patches/70-common.py.patch 2014-10-25 09:05:58.0 -0700 @@ -0,0 +1,22 @@ +Index: wxglade-0.6.8/common.py +=== +--- wxglade-0.6.8.orig/common.py wxglade-0.6.8/common.py +@@ -112,7 +112,7 @@ Path to wxGlade documentation (e.g. html + @note: This path will be set during initialisation + + +-icons_path = 'icons' ++icons_path = '/usr/share/wxglade/icons' + \ + Path to wxGlade icons + +@@ -374,7 +374,7 @@ def make_object_button(widget, icon_path + from tree import WidgetTree + id = wx.NewId() + if not os.path.isabs(icon_path): +-icon_path = os.path.join(wxglade_path, icon_path) ++icon_path = os.path.join(/usr/share/wxglade, icon_path) + if wx.Platform == '__WXGTK__': + style = wx.NO_BORDER + else: diff -Nru wxglade-0.6.8/debian/patches/series wxglade-0.6.8/debian/patches/series --- wxglade-0.6.8/debian/patches/series 2014-10-12 18:44:24.0 -0700 +++ wxglade-0.6.8/debian/patches/series 2014-11-09 01:33:46.0 -0800 @@ -5,3 +5,4 @@ 50-setup.py transition-towards-wx30.patch 60-wxpython3.0.patch +70-common.py.patch ---End Message--- ---BeginMessage--- On Mon, Nov 10, 2014 at 01:54:29 -0800, Vincent Cheng wrote: On Sun, Nov 9, 2014 at 8:10 AM, Georges Khaznadar georges.khazna...@free.fr wrote: Please Vincent, go ahead! and many thanks in advance. If the unblock query for wxglade-0.7.0 is accepted, wxglade will be part of Jessie, but this is not sure. So please upload wxglade_0.6.8-2.2 now :) Thanks (both to you and to Jonathan for approving the upload); uploaded wxglade/0.6.8-2.2 to t-p-u just now. Approved. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#768975: marked as done (RM: ironic/2014.1-9, tuskar/0.4.2-3, tuskar-ui/0.1.0-2, tripleo-heat-templates/0.6.1-1, tripleo-image-elements/0.7.1-1, python-os-apply-config/0.1.14-1, python-os-cloud-con
Your message dated Mon, 10 Nov 2014 16:54:12 +0100 with message-id 20141110155412.go2...@betterave.cristau.org and subject line Re: Bug#768975: RM: ironic/2014.1-9, tuskar/0.4.2-3, tuskar-ui/0.1.0-2, tripleo-heat-templates/0.6.1-1, tripleo-image-elements/0.7.1-1, python-os-apply-config/0.1.14-1, python-os-cloud-config/0.0.2-1, python-os-collect-config/0.1.15-1, python-os-refresh-config/0.1.2-1 has caused the Debian Bug report #768975, regarding RM: ironic/2014.1-9, tuskar/0.4.2-3, tuskar-ui/0.1.0-2, tripleo-heat-templates/0.6.1-1, tripleo-image-elements/0.7.1-1, python-os-apply-config/0.1.14-1, python-os-cloud-config/0.0.2-1, python-os-collect-config/0.1.15-1, python-os-refresh-config/0.1.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi, A number of OpenStack packages are IMO not ready for being release in a Stable version of Debian. Therefore, I would like to have them removed from Jessie. Here's the list. It consists of packages which are part of the TripleO release (eg: OpenStack on OpenStack): tuskar/0.4.2-3 tuskar-ui/0.1.0-2 tripleo-heat-templates/0.6.1-1 tripleo-image-elements/0.7.1-1 python-os-apply-config/0.1.14-1 python-os-cloud-config/0.0.2-1 python-os-collect-config/0.1.15-1 python-os-refresh-config/0.1.2-1 Please remove them all from Jessie. As for Ironic, there's no nova driver in Icehouse (the version of OpenStack which is in Jessie), so please also remove: ironic/2014.1-9 Cheers, Thomas Goirand (zigo) ---End Message--- ---BeginMessage--- On Mon, Nov 10, 2014 at 22:11:53 +0800, Thomas Goirand wrote: tuskar/0.4.2-3 tuskar-ui/0.1.0-2 tripleo-heat-templates/0.6.1-1 tripleo-image-elements/0.7.1-1 python-os-apply-config/0.1.14-1 python-os-cloud-config/0.0.2-1 python-os-collect-config/0.1.15-1 python-os-refresh-config/0.1.2-1 ironic/2014.1-9 Removal hints added. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#768981: marked as done (unblock: nipy/0.3.0+git262-gbb838d7-1)
Your message dated Mon, 10 Nov 2014 17:09:40 +0100 with message-id 5460e344.9080...@thykier.net and subject line Re: Bug#768981: unblock: nipy/0.3.0+git262-gbb838d7-1 has caused the Debian Bug report #768981, regarding unblock: nipy/0.3.0+git262-gbb838d7-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nipy It was removed from jessie a year ago due to a test failing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729594 which was resolved also long ago, but I forgot to close this bug report :-/ nipy built fine across all architectures https://buildd.debian.org/status/package.php?p=nipysuite=unstable almost a month ago and I have closed that bugreport now Sorry for forgetting about this one for a while unblock nipy/0.3.0+git262-gbb838d7-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On 2014-11-10 15:48, Yaroslav Halchenko wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nipy It was removed from jessie a year ago due to a test failing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729594 which was resolved also long ago, but I forgot to close this bug report :-/ nipy built fine across all architectures https://buildd.debian.org/status/package.php?p=nipysuite=unstable almost a month ago and I have closed that bugreport now Sorry for forgetting about this one for a while unblock nipy/0.3.0+git262-gbb838d7-1 [...] Hi, Sorry, but I am afraid I will have to decline your as your package was not in testing at the time of the freeze. While it may seem harsh, we have already rejected similar cases - if I was to give you special treatment here, I would risk having to give that to all existing cases that we have rejected. Yours truly, ~Niels---End Message---
Bug#768981: unblock: nipy/0.3.0+git262-gbb838d7-1
On Mon, 10 Nov 2014, Niels Thykier wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nipy It was removed from jessie a year ago due to a test failing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729594 which was resolved also long ago, but I forgot to close this bug report :-/ nipy built fine across all architectures https://buildd.debian.org/status/package.php?p=nipysuite=unstable almost a month ago and I have closed that bugreport now Sorry for forgetting about this one for a while unblock nipy/0.3.0+git262-gbb838d7-1 [...] Sorry, but I am afraid I will have to decline your as your package was not in testing at the time of the freeze. While it may seem harsh, we have already rejected similar cases - if I was to give you special treatment here, I would risk having to give that to all existing cases that we have rejected. oh well. I guess stock wheezy would be quite leaner and crippled enough for quite a few neuroscientists (this request was a pre-condition for the next one -- nipype)... good that at least we will have neuro.debian.net to cover up for insufficiencies of the stock Debian. But in case you guys decide to warrant such requests at some point -- keep me posted please ;-) Cheers, -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20141110162046.gz32...@onerussian.com
Bug#768971: marked as done (unblock: intel-vaapi-driver/1.4.1-2)
Your message dated Mon, 10 Nov 2014 17:24:50 +0100 with message-id 5460e6d2.80...@thykier.net and subject line Re: Bug#768971: unblock: intel-vaapi-driver/1.4.1-2 has caused the Debian Bug report #768971, regarding unblock: intel-vaapi-driver/1.4.1-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package intel-vaapi-driver. It fixes a segmentation fault on unsupported platforms (Intel graphics chip without VA-API support) as reported on the upstream mailing list [1]. unblock intel-vaapi-driver/1.4.1-2 Cheers [1] http://lists.freedesktop.org/archives/libva/2014-October/002799.html -- Sebastian Ramacher diff -Nru intel-vaapi-driver-1.4.1/debian/changelog intel-vaapi-driver-1.4.1/debian/changelog --- intel-vaapi-driver-1.4.1/debian/changelog 2014-10-24 13:49:05.0 +0200 +++ intel-vaapi-driver-1.4.1/debian/changelog 2014-11-10 13:59:50.0 +0100 @@ -1,3 +1,10 @@ +intel-vaapi-driver (1.4.1-2) unstable; urgency=medium + + * debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch: Apply +upstream patch to avoid segmentation faults on unsupported platforms. + + -- Sebastian Ramacher sramac...@debian.org Mon, 10 Nov 2014 13:59:29 +0100 + intel-vaapi-driver (1.4.1-1) unstable; urgency=medium * New upstream release. diff -Nru intel-vaapi-driver-1.4.1/debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch intel-vaapi-driver-1.4.1/debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch --- intel-vaapi-driver-1.4.1/debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch 1970-01-01 01:00:00.0 +0100 +++ intel-vaapi-driver-1.4.1/debian/patches/0002-avoid_segfault_on_unsupported_platforms.patch 2014-11-10 13:47:53.0 +0100 @@ -0,0 +1,31 @@ +Description: Avoid segfailt on unsupported platforms + Call preinit_hw_codec callback after successful initialization to avoid segment + fault issue on unsupported platforms. +Origin: upstream, + http://cgit.freedesktop.org/vaapi/intel-driver/commit/?h=v1.4-branchid=eb097b1a39b69af76b5575835255cb4653195c1c +Last-Update: 2014-11-10 + +diff --git a/src/i965_drv_video.c b/src/i965_drv_video.c +index ba7c7be..e768537 100644 +--- a/src/i965_drv_video.c b/src/i965_drv_video.c +@@ -5669,9 +5669,6 @@ i965_Init(VADriverContextP ctx) + break; + } + +-if (i965-codec_info-preinit_hw_codec) +-i965-codec_info-preinit_hw_codec(ctx, i965-codec_info); +- + if (i == ARRAY_ELEMS(i965_sub_ops)) { + switch (i965-intel.device_id) { + #undef CHIPSET +@@ -5697,6 +5694,9 @@ i965_Init(VADriverContextP ctx) + + i965-current_context_id = VA_INVALID_ID; + ++if (i965-codec_info i965-codec_info-preinit_hw_codec) ++i965-codec_info-preinit_hw_codec(ctx, i965-codec_info); ++ + return VA_STATUS_SUCCESS; + } else { + i--; diff -Nru intel-vaapi-driver-1.4.1/debian/patches/series intel-vaapi-driver-1.4.1/debian/patches/series --- intel-vaapi-driver-1.4.1/debian/patches/series 2014-06-16 10:28:59.0 +0200 +++ intel-vaapi-driver-1.4.1/debian/patches/series 2014-11-10 13:48:20.0 +0100 @@ -1 +1,2 @@ 0001-Fix_FTBFS_on_kFreeBSD.patch +0002-avoid_segfault_on_unsupported_platforms.patch signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On 2014-11-10 14:45, Sebastian Ramacher wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package intel-vaapi-driver. It fixes a segmentation fault on unsupported platforms (Intel graphics chip without VA-API support) as reported on the upstream mailing list [1]. unblock intel-vaapi-driver/1.4.1-2 Cheers [1] http://lists.freedesktop.org/archives/libva/2014-October/002799.html Unblocked, thanks. ~Niels---End Message---
Processed: Re: Bug#768970: unblock: openstack-pkg-tools/17
Processing control commands: tags -1 confirmed Bug #768970 [release.debian.org] unblock: openstack-pkg-tools/17 Added tag(s) confirmed. -- 768970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b768970.14156368981221.transcr...@bugs.debian.org
Bug#768992: unblock: dbus/1.8.10-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package dbus to pick up the denial of service fix that I just released (CVE-2014-7824): unblock dbus/1.8.10-1 The new upstream release does not introduce any changes other than the security fix and the new version metadata, so I imported it as-is rather than doing a trivial backport. I attach a filtered source debdiff with autotools noise excluded (we re-generate the autotools files with autoreconf during the build anyway), and a full source debdiff. Thanks, S diffstat for dbus-1.8.8 dbus-1.8.10 NEWS | 12 +++ aclocal.m4|7 -- bus/activation.c | 28 +++- bus/bus.c | 50 +++--- bus/bus.h |1 configure | 30 configure.ac |4 - dbus/dbus-sysdeps-util-unix.c | 147 +- dbus/dbus-sysdeps-util-win.c | 35 +- dbus/dbus-sysdeps.h | 11 ++- debian/changelog | 12 +++ debian/dbus.init |2 doc/Makefile.in |2 13 files changed, 274 insertions(+), 67 deletions(-) diff -Nru dbus-1.8.8/aclocal.m4 dbus-1.8.10/aclocal.m4 --- dbus-1.8.8/aclocal.m4 2014-09-15 12:43:13.0 +0100 +++ dbus-1.8.10/aclocal.m4 2014-11-06 15:40:17.0 + @@ -103,10 +103,9 @@ # configured tree to be moved without reconfiguration. AC_DEFUN([AM_AUX_DIR_EXPAND], -[dnl Rely on autoconf to set up CDPATH properly. -AC_PREREQ([2.50])dnl -# expand $ac_aux_dir to an absolute path -am_aux_dir=`cd $ac_aux_dir pwd` +[AC_REQUIRE([AC_CONFIG_AUX_DIR_DEFAULT])dnl +# Expand $ac_aux_dir to an absolute path. +am_aux_dir=`cd $ac_aux_dir pwd` ]) # AM_CONDITIONAL-*- Autoconf -*- diff -Nru dbus-1.8.8/bus/activation.c dbus-1.8.10/bus/activation.c --- dbus-1.8.8/bus/activation.c 2014-09-12 12:52:11.0 +0100 +++ dbus-1.8.10/bus/activation.c 2014-11-06 15:30:51.0 + @@ -1688,6 +1688,31 @@ return retval; } +static void +child_setup (void *user_data) +{ +#ifdef DBUS_UNIX + BusActivation *activation = user_data; + DBusRLimit *initial_fd_limit; + DBusError error; + + dbus_error_init (error); + initial_fd_limit = bus_context_get_initial_fd_limit (activation-context); + + if (initial_fd_limit != NULL + !_dbus_rlimit_restore_fd_limit (initial_fd_limit, error)) +{ + /* unfortunately we don't actually know the service name here */ + bus_context_log (activation-context, + DBUS_SYSTEM_LOG_INFO, + Failed to reset fd limit before activating + service: %s: %s, + error.name, error.message); +} +#endif +} + + dbus_bool_t bus_activation_activate_service (BusActivation *activation, DBusConnection *connection, @@ -2121,7 +2146,8 @@ service_name, argv, envp, - NULL, activation, + child_setup, + activation, tmp_error)) { _dbus_verbose (Failed to spawn child\n); diff -Nru dbus-1.8.8/bus/bus.c dbus-1.8.10/bus/bus.c --- dbus-1.8.8/bus/bus.c 2014-09-15 12:29:28.0 +0100 +++ dbus-1.8.10/bus/bus.c 2014-11-06 15:30:51.0 + @@ -64,6 +64,7 @@ BusPolicy *policy; BusMatchmaker *matchmaker; BusLimits limits; + DBusRLimit *initial_fd_limit; unsigned int fork : 1; unsigned int syslog : 1; unsigned int keep_umask : 1; @@ -659,19 +660,38 @@ static void raise_file_descriptor_limit (BusContext *context) { +#ifdef DBUS_UNIX + DBusError error = DBUS_ERROR_INIT; - /* I just picked this out of thin air; we need some extra - * descriptors for things like any internal pipes we create, - * inotify, connections to SELinux, etc. - */ - unsigned int arbitrary_extra_fds = 32; - unsigned int limit; + /* we only do this once */ + if (context-initial_fd_limit != NULL) +return; - limit = context-limits.max_completed_connections + -context-limits.max_incomplete_connections -+ arbitrary_extra_fds; + context-initial_fd_limit = _dbus_rlimit_save_fd_limit (error); - _dbus_request_file_descriptor_limit (limit); + if (context-initial_fd_limit == NULL) +{ + bus_context_log (context, DBUS_SYSTEM_LOG_INFO, + %s: %s, error.name, error.message); + dbus_error_free (error); + return; +} + + /* We used to compute a suitable rlimit based on the configured number + * of connections, but that breaks down as soon as we allow fd-passing, + * because each
Bug#768967: marked as done (unblock: python-requests-kerberos/0.5-2)
Your message dated Mon, 10 Nov 2014 17:29:54 +0100 with message-id 5460e802.9060...@thykier.net and subject line Re: Bug#768967: unblock: python-requests-kerberos/0.5-2 has caused the Debian Bug report #768967, regarding unblock: python-requests-kerberos/0.5-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, My last upload of python-requests-kerberos fixed CVE-2014-8650: failure to handle mutual authentication (Closes: #768408) reported by the security team (debdiff including upstream patch is attached). Please unblock python-requests-kerberos/0.5-2 Cheers, Thomas Goirand (zigo) diff -Nru python-requests-kerberos-0.5/debian/changelog python-requests-kerberos-0.5/debian/changelog --- python-requests-kerberos-0.5/debian/changelog 2014-06-27 06:37:32.0 + +++ python-requests-kerberos-0.5/debian/changelog 2014-11-10 13:25:13.0 + @@ -1,3 +1,11 @@ +python-requests-kerberos (0.5-2) unstable; urgency=high + + * CVE-2014-8650: failure to handle mutual authentication. Applied upstream +patch: CVE-2014-8650_Handle_mutual_authentication.patch (Closes: #768408). +Thanks to Salvatore Bonaccorso car...@debian.org for reporting it. + + -- Thomas Goirand z...@debian.org Mon, 10 Nov 2014 21:22:51 +0800 + python-requests-kerberos (0.5-1) unstable; urgency=medium * Initial release. (Closes: #752858) diff -Nru python-requests-kerberos-0.5/debian/patches/CVE-2014-8650_Handle_mutual_authentication.patch python-requests-kerberos-0.5/debian/patches/CVE-2014-8650_Handle_mutual_authentication.patch --- python-requests-kerberos-0.5/debian/patches/CVE-2014-8650_Handle_mutual_authentication.patch 1970-01-01 00:00:00.0 + +++ python-requests-kerberos-0.5/debian/patches/CVE-2014-8650_Handle_mutual_authentication.patch 2014-11-10 13:25:13.0 + @@ -0,0 +1,39 @@ +Description: CVE-2014-8650: Handle mutual authentication + Make certain that responses always pass through handle_other() to provide + mutual authentication before returning them to the user. +Origin: upstream, https://github.com/mkomitee/requests-kerberos/commit/9c1e08cc17bb6950455a85d33d391ecd2bce6eb6.patch +Author: Michael Komitee komi...@deshaw.com +Date: Fri, 8 Aug 2014 17:47:42 -0400 +Bug-Debian: https://bugs.debian.org/768408 +Index: python-requests-kerberos/requests_kerberos/kerberos_.py +=== +--- python-requests-kerberos.orig/requests_kerberos/kerberos_.py 2014-06-12 09:10:24.0 +0800 python-requests-kerberos/requests_kerberos/kerberos_.py 2014-11-10 21:24:56.0 +0800 +@@ -251,7 +251,7 @@ + if response.status_code == 401: + _r = self.handle_401(response, **kwargs) + log.debug(handle_response(): returning {0}.format(_r)) +-return _r ++return self.handle_response(_r, **kwargs) + else: + _r = self.handle_other(response) + log.debug(handle_response(): returning {0}.format(_r)) +Index: python-requests-kerberos/test_requests_kerberos.py +=== +--- python-requests-kerberos.orig/test_requests_kerberos.py 2014-11-10 21:24:56.0 +0800 python-requests-kerberos/test_requests_kerberos.py 2014-11-10 21:24:56.0 +0800 +@@ -403,10 +403,14 @@ + response.connection = connection + response._content = + response.raw = raw ++ + auth = requests_kerberos.HTTPKerberosAuth() ++auth.handle_other = Mock(return_value=response_ok) ++ + r = auth.handle_response(response) + + self.assertTrue(response in r.history) ++auth.handle_other.assert_called_with(response_ok) + self.assertEqual(r, response_ok) + self.assertEqual(request.headers['Authorization'], 'Negotiate GSSRESPONSE') + connection.send.assert_called_with(request) diff -Nru python-requests-kerberos-0.5/debian/patches/series python-requests-kerberos-0.5/debian/patches/series --- python-requests-kerberos-0.5/debian/patches/series 2014-06-27 06:37:32.0 + +++ python-requests-kerberos-0.5/debian/patches/series 2014-11-10 13:25:13.0 + @@ -1,2 +1,3 @@ disable-broken-test-in-python3.patch fix-setup.py-to-work-with-python3.patch
Bug#768970: unblock: openstack-pkg-tools/17
Control: tags -1 confirmed On 2014-11-10 14:45, Thomas Goirand wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, The version 16 of openstack-pkg-tools attempted to support systemd, but it wasn't creating /var/run/PROJECT-NAME, and therefore, it isn't possible to start daemons properly if using systemd in Jessie. Version 17 corrects the problem, together with adding the possibility to *not* use --config-file, as this is needed to fix another bug. Please unblock openstack-pkg-tools/17. Once this upload is approved, I'll have to proceed with uploading updates for all OpenStack core packages, which is needed anyway to add new Debconf translations which were sent to the BTS. Cheers, Thomas Goirand (zigo) Hi Thomas, The changes to openstack-pkg-tools looks reasonable, feel free to upload that to unstable and let us know when it has been accepted. ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5460e797.6000...@thykier.net
Bug#768976: marked as done (unblock: fail2ban/0.9.1-1)
Your message dated Mon, 10 Nov 2014 17:23:35 +0100 with message-id 5460e687.3010...@thykier.net and subject line Re: Bug#768976: unblock: fail2ban/0.9.1-1 has caused the Debian Bug report #768976, regarding unblock: fail2ban/0.9.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package fail2ban We have 0.8.13 in jessie ATM and I have released 0.9.1 and uploaded 0.9.1-1 just few days too short of a freeze - 10days (why didn't I change urgency? ;)) [2014-10-28] Accepted fail2ban 0.9.1-1 (source all) into unstable (Yaroslav Halchenko) 0.9.1 is the 2nd release in the 0.9.0 line and I had 0.9.0 in experimental for a while. So far it shows great promise to be very stable and much more versatile than 0.8.x -- we introduced multiline matching, eliminated divergance between Debian's and upstream jail.conf definitions, extended testing a lot (92% code coverage). After the release I haven't seen major bug reports (there is one minor typo to be fixed) and I have high confidence that this release would be a much better fit to maintain in Debian jessie (instead of now very stable but aging fast 0.8.). debdiff would be infeasible (we also made it a proper fail2ban python module instead of a bunch of internal submodules), but let me know if I need to provide more lines of argumentation to feature unblock unblock fail2ban/0.9.1-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On 2014-11-10 15:12, Yaroslav Halchenko wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package fail2ban Hi, We have 0.8.13 in jessie ATM and I have released 0.9.1 and uploaded 0.9.1-1 just few days too short of a freeze - 10days (why didn't I change urgency? ;)) FTR, that would not have helped. Prior to the freeze, there was a forced 10-day migration[1]. [2014-10-28] Accepted fail2ban 0.9.1-1 (source all) into unstable (Yaroslav Halchenko) 0.9.1 is the 2nd release in the 0.9.0 line and I had 0.9.0 in experimental for a while. So far it shows great promise to be very stable and much more versatile than 0.8.x -- we introduced multiline matching, eliminated divergance between Debian's and upstream jail.conf definitions, extended testing a lot (92% code coverage). After the release I haven't seen major bug reports (there is one minor typo to be fixed) and I have high confidence that this release would be a much better fit to maintain in Debian jessie (instead of now very stable but aging fast 0.8.). debdiff would be infeasible (we also made it a proper fail2ban python module instead of a bunch of internal submodules), but let me know if I need to provide more lines of argumentation to feature unblock unblock fail2ban/0.9.1-1 [...] While the changes do sound interesting and promising, a freeze is not the time to apply such a change. Sadly, I will be declining your request, sorry. Yours truly, ~Niels [1] https://lists.debian.org/debian-devel-announce/2014/10/msg1.html---End Message---
Bug#768994: unblock: python-stem/1.2.2-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-stem Fix for RC bug #767555 unblock python-stem/1.2.2-1.1 diff -Nru python-stem-1.2.2/debian/changelog python-stem-1.2.2/debian/changelog --- python-stem-1.2.2/debian/changelog 2014-07-02 13:33:10.0 -0400 +++ python-stem-1.2.2/debian/changelog 2014-11-10 10:45:06.0 -0500 @@ -1,3 +1,15 @@ +python-stem (1.2.2-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: Remove /usr/bin/tor-prompt from python3-stem due to file +conflict with python-stem (Closes: #767555) +- Since tor-prompt uses /usr/bin/env python, it will always execute with + python, not python3, so shipping it with python3-stem didn't work in any + case + * debian/control: Add versioned breaks for python3-stem 1.2.2-1.1~ + + -- Scott Kitterman sc...@kitterman.com Mon, 10 Nov 2014 10:27:48 -0500 + python-stem (1.2.2-1) unstable; urgency=medium * New upstream release. diff -Nru python-stem-1.2.2/debian/control python-stem-1.2.2/debian/control --- python-stem-1.2.2/debian/control 2014-07-02 13:32:21.0 -0400 +++ python-stem-1.2.2/debian/control 2014-11-10 10:45:24.0 -0500 @@ -12,6 +12,7 @@ Package: python-stem Architecture: all Depends: ${python:Depends}, ${misc:Depends} +Breaks: python3-stem ( 1.2.2-1.1~) Description: Tor control library for Python Stem is a TorCtl successor, a Python Tor controller with extensions to support path building and various constraints on node and path selection, as well as diff -Nru python-stem-1.2.2/debian/rules python-stem-1.2.2/debian/rules --- python-stem-1.2.2/debian/rules 2014-07-02 12:37:18.0 -0400 +++ python-stem-1.2.2/debian/rules 2014-11-10 10:38:07.0 -0500 @@ -23,6 +23,7 @@ for py in $(PY3VERS); do \ $$py setup.py install --root debian/python3-stem \ --install-layout=deb; \ + rm -rf $(CURDIR)/debian/python3-stem/usr/bin; \ done; \ override_dh_auto_clean:
Bug#768993: wheezy-pu: package dbus/1.6.8-1+deb7u5
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu I would like to fix denial-of-service vulnerability CVE-2014-7824 in wheezy. The security team have indicated that they will not be issuing a DSA for this. It's the same vulnerability for which I just requested a 1.8.10 unblock, and basically the same patch (after fixing minor conflicts in a comment). Source debdiff attached. Thanks, S diffstat for dbus-1.6.8 dbus-1.6.8 changelog | 11 dbus.init |2 patches/0001-CVE-2014-7824-set-fd-rlimit-to-64k-for-the-system-db.patch | 426 ++ patches/series |2 4 files changed, 440 insertions(+), 1 deletion(-) diff -Nru dbus-1.6.8/debian/changelog dbus-1.6.8/debian/changelog --- dbus-1.6.8/debian/changelog 2014-09-15 19:49:38.0 +0100 +++ dbus-1.6.8/debian/changelog 2014-11-06 16:36:28.0 + @@ -1,3 +1,14 @@ +dbus (1.6.8-1+deb7u5) wheezy; urgency=medium + + * Fix CVE-2014-7824: +- Start 'dbus-daemon --system' as root under sysvinit (it already + starts as root under systemd), so it can increase its file + descriptor limit +- Add patch from upstream to increase dbus-daemon's file descriptor + limit to 65536, completing the incomplete fix for CVE-2014-3636 + + -- Simon McVittie s...@debian.org Thu, 06 Nov 2014 16:31:34 + + dbus (1.6.8-1+deb7u4) wheezy-security; urgency=high * Fix several security issues diff -Nru dbus-1.6.8/debian/dbus.init dbus-1.6.8/debian/dbus.init --- dbus-1.6.8/debian/dbus.init 2014-09-15 19:49:38.0 +0100 +++ dbus-1.6.8/debian/dbus.init 2014-11-06 16:36:28.0 + @@ -69,7 +69,7 @@ log_daemon_msg Starting $DESC $NAME start-stop-daemon --start --quiet --pidfile $PIDFILE \ ---user $DAEMONUSER --exec $DAEMON -- --system $PARAMS +--exec $DAEMON -- --system $PARAMS log_end_msg $? } diff -Nru dbus-1.6.8/debian/patches/0001-CVE-2014-7824-set-fd-rlimit-to-64k-for-the-system-db.patch dbus-1.6.8/debian/patches/0001-CVE-2014-7824-set-fd-rlimit-to-64k-for-the-system-db.patch --- dbus-1.6.8/debian/patches/0001-CVE-2014-7824-set-fd-rlimit-to-64k-for-the-system-db.patch 1970-01-01 01:00:00.0 +0100 +++ dbus-1.6.8/debian/patches/0001-CVE-2014-7824-set-fd-rlimit-to-64k-for-the-system-db.patch 2014-11-06 16:36:28.0 + @@ -0,0 +1,426 @@ +From 68cb9ead957314b30e604018f2dd5b0fc3b2127c Mon Sep 17 00:00:00 2001 +From: Simon McVittie simon.mcvit...@collabora.co.uk +Date: Tue, 4 Nov 2014 14:41:54 + +Subject: [PATCH] CVE-2014-7824: set fd rlimit to 64k for the system + dbus-daemon + +This ensures that our rlimit is actually high enough to avoid the +denial of service described in CVE-2014-3636 part A. +CVE-2014-7824 has been allocated for this incomplete fix. + +Restore the original rlimit for activated services, to avoid +them getting undesired higher limits. + +(Thanks to Alban Crequy for various adjustments which have been +included in this commit.) + +Bug: https://bugs.freedesktop.org/show_bug.cgi?id=85105 +Reviewed-by: Alban Crequy alban.cre...@collabora.co.uk +Conflicts: + dbus/dbus-sysdeps-util-unix.c +--- + bus/activation.c | 28 +++- + bus/bus.c | 50 --- + bus/bus.h | 1 + + dbus/dbus-sysdeps-util-unix.c | 145 +- + dbus/dbus-sysdeps-util-win.c | 35 +- + dbus/dbus-sysdeps.h | 11 +++- + 6 files changed, 227 insertions(+), 43 deletions(-) + +diff --git a/bus/activation.c b/bus/activation.c +index 280cc01..b636868 100644 +--- a/bus/activation.c b/bus/activation.c +@@ -1683,6 +1683,31 @@ out: + return retval; + } + ++static void ++child_setup (void *user_data) ++{ ++#ifdef DBUS_UNIX ++ BusActivation *activation = user_data; ++ DBusRLimit *initial_fd_limit; ++ DBusError error; ++ ++ dbus_error_init (error); ++ initial_fd_limit = bus_context_get_initial_fd_limit (activation-context); ++ ++ if (initial_fd_limit != NULL ++ !_dbus_rlimit_restore_fd_limit (initial_fd_limit, error)) ++{ ++ /* unfortunately we don't actually know the service name here */ ++ bus_context_log (activation-context, ++ DBUS_SYSTEM_LOG_INFO, ++ Failed to reset fd limit before activating ++ service: %s: %s, ++ error.name, error.message); ++} ++#endif ++} ++ ++ + dbus_bool_t + bus_activation_activate_service (BusActivation *activation, + DBusConnection *connection, +@@ -2114,7 +2139,8 @@ bus_activation_activate_service (BusActivation *activation, + + if (!_dbus_spawn_async_with_babysitter (pending_activation-babysitter, argv, + envp, +-
Bug#768925: marked as done (unblock: php-net-ldap/1:1.1.5-3)
Your message dated Mon, 10 Nov 2014 17:32:45 +0100 with message-id 5460e8ad.9090...@thykier.net and subject line Re: Bug#768925: unblock: php-net-ldap/1:1.1.5-3 has caused the Debian Bug report #768925, regarding unblock: php-net-ldap/1:1.1.5-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, Please unblock package php-net-ldap/1:1.1.5-3. It fixes RC bug #768246 (unhandled symlink to directory conversion). The complete changelog is: php-net-ldap (1:1.1.5-3) unstable; urgency=medium [ Thijs Kinkhorst ] * Remove self from uploaders. [ Prach Pongpanich ] * Bump Standards-Version to 3.9.6. * Rebuild with pkg-php-tools 1.26, that don't ship test files in binary package (Closes: #768246). -- Prach Pongpanich prach...@gmail.com Mon, 10 Nov 2014 11:08:57 +0700 The debdiff is attached. Regards, Prach php-net-ldap_1.1.5-3.debdiff Description: Binary data ---End Message--- ---BeginMessage--- On 2014-11-10 09:24, Prach Pongpanich wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, Please unblock package php-net-ldap/1:1.1.5-3. It fixes RC bug #768246 (unhandled symlink to directory conversion). The complete changelog is: [...] The debdiff is attached. Regards, Prach Unblocked and aged, thanks. ~Niels---End Message---
Bug#768899: marked as done (unblock: mod-mono/3.8-2)
Your message dated Mon, 10 Nov 2014 17:37:34 +0100 with message-id 5460e9ce.5000...@thykier.net and subject line Re: Bug#768899: unblock: mod-mono/3.8-2 has caused the Debian Bug report #768899, regarding unblock: mod-mono/3.8-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mod-mono The -2 upload fixes bug 767878. changelog |7 +++ rules |3 +-- 2 files changed, 8 insertions(+), 2 deletions(-) unblock mod-mono/3.8-2 -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (500, 'precise'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0-39-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru mod-mono-3.8/debian/changelog mod-mono-3.8/debian/changelog --- mod-mono-3.8/debian/changelog 2014-09-25 10:39:33.0 +0100 +++ mod-mono-3.8/debian/changelog 2014-11-09 23:12:59.0 + @@ -1,3 +1,10 @@ +mod-mono (3.8-2) unstable; urgency=medium + + * [943846f] Revert Work around misalignment of version numbers between +xsp and mod-mono (Closes: #716896) (Closes: #767878) + + -- Jo Shields direct...@apebox.org Sun, 09 Nov 2014 23:12:21 + + mod-mono (3.8-1) unstable; urgency=medium * [1068c40] Imported Upstream version 3.8 diff -Nru mod-mono-3.8/debian/rules mod-mono-3.8/debian/rules --- mod-mono-3.8/debian/rules 2014-09-25 10:39:33.0 +0100 +++ mod-mono-3.8/debian/rules 2014-11-09 23:12:05.0 + @@ -31,8 +31,7 @@ override_dh_gencontrol: dh_gencontrol -- \ - -Vcurrent-version=3.0.11 -Vnext-version=3.0.11.1 -# -Vcurrent-version=$(PKG_VERSION) -Vnext-version=$(NEXT_PKG_VERSION) + -Vcurrent-version=$(PKG_VERSION) -Vnext-version=$(NEXT_PKG_VERSION) get-orig-source: uscan \ ---End Message--- ---BeginMessage--- On 2014-11-10 00:30, Jo Shields wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mod-mono The -2 upload fixes bug 767878. changelog |7 +++ rules |3 +-- 2 files changed, 8 insertions(+), 2 deletions(-) unblock mod-mono/3.8-2 [...] Hi, Sorry, but I am afraid I will have to decline your as your package was not in testing at the time of the freeze. While it may seem harsh, we have already rejected similar cases - if I was to give you special treatment here, I would risk having to give that to all existing cases that we have rejected. Yours truly, ~Niels---End Message---
Bug#768933: unblock: jscommunicator
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. 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? ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5460eae5.7020...@thykier.net
Processed: Re: Bug#768933: unblock: jscommunicator
Processing control commands: tags -1 moreinfo wontfix Bug #768933 [release.debian.org] unblock: jscommunicator Added tag(s) moreinfo and wontfix. -- 768933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b768933.14156377458903.transcr...@bugs.debian.org
Bug#768992: unblock: dbus/1.8.10-1
Control: tag -1 d-i On Mon, Nov 10, 2014 at 16:28:28 +, Simon McVittie wrote: Please unblock package dbus to pick up the denial of service fix that I just released (CVE-2014-7824): unblock dbus/1.8.10-1 The new upstream release does not introduce any changes other than the security fix and the new version metadata, so I imported it as-is rather than doing a trivial backport. I attach a filtered source debdiff with autotools noise excluded (we re-generate the autotools files with autoreconf during the build anyway), and a full source debdiff. cc-ing d-i release manager to ack the udeb unblock. Approved from the -release side. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#768992: unblock: dbus/1.8.10-1
Processing control commands: tag -1 d-i Bug #768992 [release.debian.org] unblock: dbus/1.8.10-1 Added tag(s) d-i. -- 768992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b768992.141563800410691.transcr...@bugs.debian.org
Bug#768992: unblock: dbus/1.8.10-1
On 10/11/14 16:46, Julien Cristau wrote: On Mon, Nov 10, 2014 at 16:28:28 +, Simon McVittie wrote: The new upstream release does not introduce any changes other than the security fix and the new version metadata, so I imported it as-is rather than doing a trivial backport. If you're OK with that as a general approach to upstream releases whose changes are otherwise OK for stable/frozen testing, I'd like to continue to track the 1.8.x branch for as long as I can (at least until the jessie release, and hopefully afterwards too). I do basically all the releases upstream, so I can be as conservative with their contents as you need me to be. If it would help, I can make sure to generate future 1.8.x tarballs using jessie's autotools instead of sid's. S -- 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/5460efb7.6080...@debian.org
Bug#768976: unblock: fail2ban/0.9.1-1
On Mon, 10 Nov 2014, Niels Thykier wrote: We have 0.8.13 in jessie ATM and I have released 0.9.1 and uploaded 0.9.1-1 just few days too short of a freeze - 10days (why didn't I change urgency? ;)) FTR, that would not have helped. Prior to the freeze, there was a forced 10-day migration[1]. [2014-10-28] Accepted fail2ban 0.9.1-1 (source all) into unstable (Yaroslav Halchenko) 0.9.1 is the 2nd release in the 0.9.0 line and I had 0.9.0 in experimental for a while. So far it shows great promise to be very stable and much more versatile than 0.8.x -- we introduced multiline matching, eliminated divergance between Debian's and upstream jail.conf definitions, extended testing a lot (92% code coverage). After the release I haven't seen major bug reports (there is one minor typo to be fixed) and I have high confidence that this release would be a much better fit to maintain in Debian jessie (instead of now very stable but aging fast 0.8.). debdiff would be infeasible (we also made it a proper fail2ban python module instead of a bunch of internal submodules), but let me know if I need to provide more lines of argumentation to feature unblock unblock fail2ban/0.9.1-1 [...] While the changes do sound interesting and promising, a freeze is not the time to apply such a change. Sadly, I will be declining your request, sorry. that is a pity that few busy days delay is so critical that makes jessie worse. but oh well -- your call Thanks for your work and looking at this one -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20141110171659.ga32...@onerussian.com
Bug#768970: unblock: openstack-pkg-tools/19 (was: unblock: openstack-pkg-tools/17)
Hi, It's looking like I should use, in a systemd unit file: RuntimeDirectory=${PROJECT_NAME} which is what version 19 does. That's the only change with version 17, so I didn't do a .debdiff. Let me know if you need one. Cheers, Thomas Goirand (zigo) -- 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/5460f66b.6020...@debian.org
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#768920: RM: gobby-infinote/0.4.13-2
On Mon, Nov 10, 2014 at 08:55:20AM +, Adam D. Barratt wrote: What about sobby? That has both build- and runtime dependencies on both libobby and libnet6. sobby too, please. (How could I forget this... But then dak rm was very confused due to gobby(bin) being provided by !gobby(src).) Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Processed: owner 768992
Processing commands for cont...@bugs.debian.org: owner 768992 ! Bug #768992 [release.debian.org] unblock: dbus/1.8.10-1 Owner recorded as Julien Cristau jcris...@debian.org. thanks Stopping processing here. Please contact me if you need assistance. -- 768992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.14156410103082.transcr...@bugs.debian.org
Processed: Re: Bug#768933: unblock: jscommunicator
Processing control commands: tags -1 -wontfix Bug #768933 [release.debian.org] unblock: jscommunicator Removed tag(s) wontfix. -- 768933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b768933.14156410383254.transcr...@bugs.debian.org
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#768469: closed by Jonathan Wiltshire j...@debian.org (Re: Bug#768469: unblock: gcl/2.6.12-1)
Greetings! Again, please let me thank you for your work on Debian, and state that I do understand why in a project of this size adhering to policies and schedules is important. Apparently, I've made a mistake, and I humbly apologize. If it would help, I'd be happy to forward said apology to whomever you'd deem important. I could have sworn I saw five days on the Debian pages to which I referred, but obviously I haven't saved these, so the most plausible explanation is that I'm mistaken. And it is also true that I should have not exclusively relied on this, but kept up with the mailing list you quoted. But I think these facts are also very relevant: 1) gcl-2.6.12-1 is identical to gcl-2.6.11-6 but for the name change. The latter was uploaded on 10-23, well in advance of the 10 days needed before 11-5. I erroneously thought there was time for a name change only upload to migrate and synchronize with the upstream release. My bad, but the code has in fact had the time requested in unstable. 2) Concomitant with the above, three gcl dependencies, maxima, axiom, and hol88, were built with a build-dependency against gcl = 2.6.11-6, and successfully migrated into testing. They now have rc bugs filed, because I misjudged the time needed for a name-change only upload. Unblocking gcl is the minimal targeted change to clear these bugs, thus falling under point i. of your unblocking policy. If you would prefer, I could re-upload 2.6.11-6, but it is exactly the same as what is in unstable now but for the name. In fact, 2.6.12-1 has had more air time to expose possible issues. So what do you propose? People are human, and mistakes are made and we all have a limited amount of time to spend on this volunteer project. What's best for Debian? May I humbly suggest, unblocking gcl, and having me do 20 push-ups, is clearly the best way forward :-). Take care, Jonathan Wiltshire j...@debian.org writes: On Fri, Nov 07, 2014 at 11:32:26AM -0500, Camm Maguire wrote: Greetings! I humbly ask you to reconsider, especially in light of the fact that the package tracking webpages and quality assurance webpages did not post this migration time change, and still reported the 5 days (and in fact still do). This situation is legitimately confusing, and letting packages in within a five day window of 11-5 when uploaded with this understanding will strengthen the release and project. Excuses output, which is what feeds the PTS, reflected the 10 days required during that period. It no longer does so, because those values have been reset now that migration is fully manual. I have considered carefully overnight, but I have not changed my mind. I'm sorry to disappoint you. -- Camm Maguirec...@maguirefamily.org == The earth is but one country, and mankind its citizens. -- Baha'u'llah -- 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/87r3xbkksc@maguirefamily.org
Bug#769014: unblock: libecap/0.2.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libecap Version 0.2.0-3 fixes an RC bug caused by upstream autoconf which prevented libecap to build on several new architectures. diff -Nru libecap-0.2.0/debian/changelog libecap-0.2.0/debian/changelog --- libecap-0.2.0/debian/changelog 2012-12-05 20:11:58.0 +0100 +++ libecap-0.2.0/debian/changelog 2014-11-10 19:24:58.0 +0100 @@ -1,3 +1,22 @@ +libecap (0.2.0-3) unstable; urgency=low + + * Enable 'foreign' automake option, thanks to Andrey Rahmatullin +(Closes: #766492) + + -- Luigi Gangitano lu...@debian.org Mon, 10 Nov 2014 19:21:04 +0100 + +libecap (0.2.0-2) unstable; urgency=low + + * Fix FTBFS on new ports, thanks to Breno Leitao (Closes: #748292) + + * debian/copyright +- Fixed short name for BSD license + + * debian/control +- Bumped Standard-Version to 3.9.6 (no change needed) + + -- Luigi Gangitano lu...@debian.org Mon, 20 Oct 2014 19:21:04 +0200 + libecap (0.2.0-1) unstable; urgency=low * Initial release (Closes: #634204) diff -Nru libecap-0.2.0/debian/control libecap-0.2.0/debian/control --- libecap-0.2.0/debian/control2012-12-05 20:03:23.0 +0100 +++ libecap-0.2.0/debian/control2014-11-10 19:24:58.0 +0100 @@ -1,8 +1,8 @@ Source: libecap Priority: extra Maintainer: Luigi Gangitano lu...@debian.org -Build-Depends: debhelper (= 8.0.0), autotools-dev, cdbs -Standards-Version: 3.9.2 +Build-Depends: debhelper (= 8.0.0), autotools-dev, cdbs, dh-autoreconf +Standards-Version: 3.9.6 Section: libs Homepage: http://www.e-cap.org/Downloads diff -Nru libecap-0.2.0/debian/copyright libecap-0.2.0/debian/copyright --- libecap-0.2.0/debian/copyright 2011-07-17 20:20:51.0 +0200 +++ libecap-0.2.0/debian/copyright 2014-11-10 19:24:58.0 +0100 @@ -4,7 +4,7 @@ Files: * Copyright: 2008 Alex Rousskov and The Measurement Factory -License: Simplified BSD +License: BSD-2-Clause Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: . diff -Nru libecap-0.2.0/debian/patches/automake-foreign.patch libecap-0.2.0/debian/patches/automake-foreign.patch --- libecap-0.2.0/debian/patches/automake-foreign.patch 1970-01-01 01:00:00.0 +0100 +++ libecap-0.2.0/debian/patches/automake-foreign.patch 2014-11-10 19:24:58.0 +0100 @@ -0,0 +1,16 @@ +Description: Set the foreign option for automake +Author: Andrey Rahmatullin w...@debian.org +Bug-Debian: https://bugs.debian.org/766492 +Last-Update: 2014-11-08 + +--- libecap-0.2.0.orig/configure.in libecap-0.2.0/configure.in +@@ -14,7 +14,7 @@ AC_CONFIG_SRCDIR([src/libecap/adapter/se + AC_CONFIG_HEADERS(src/libecap/common/ac-autoconf.h) + AX_PREFIX_CONFIG_H(src/libecap/common/autoconf.h) + +-AM_INIT_AUTOMAKE([nostdinc]) ++AM_INIT_AUTOMAKE([nostdinc foreign]) + AM_MAINTAINER_MODE + + LT_INIT diff -Nru libecap-0.2.0/debian/patches/series libecap-0.2.0/debian/patches/series --- libecap-0.2.0/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ libecap-0.2.0/debian/patches/series 2014-11-10 19:24:58.0 +0100 @@ -0,0 +1 @@ +automake-foreign.patch diff -Nru libecap-0.2.0/debian/rules libecap-0.2.0/debian/rules --- libecap-0.2.0/debian/rules 2012-12-05 20:10:06.0 +0100 +++ libecap-0.2.0/debian/rules 2014-11-10 19:24:58.0 +0100 @@ -2,6 +2,7 @@ include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/autotools.mk +include /usr/share/cdbs/1/rules/autoreconf.mk override_dh_installchangelogs: dh_installchangelogs change.log upstream unblock libecap/0.2.0-3 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141110183830.26903.4386.report...@debian.openconsulting.it
Bug#768920: marked as done (RM: gobby/0.4.13-2)
Your message dated Mon, 10 Nov 2014 18:35:38 + with message-id b63220a8aec0320b2626a8fbef579...@mail.adsl.funky-badger.org and subject line Re: Bug#768920: RM: gobby-infinote/0.4.13-2 has caused the Debian Bug report #768920, regarding RM: gobby/0.4.13-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove the following *source* packages from jessie: gobby 0.4.13-2 net6 1:1.3.14-2 obby 0.4.8-1 gobby-infinote has taken over the gobby package just in time for the jessie freeze. I do not want gobby-0.4 to stay around for jessie, it won't receive any more updates upstream. net6 and obby are support packages only around for gobby-0.4 and can (and should) hence go as well. Kind regards and thanks Philipp Kern ---End Message--- ---BeginMessage--- On 2014-11-10 17:22, Philipp Kern wrote: On Mon, Nov 10, 2014 at 08:55:20AM +, Adam D. Barratt wrote: What about sobby? That has both build- and runtime dependencies on both libobby and libnet6. sobby too, please. (How could I forget this... But then dak rm was very confused due to gobby(bin) being provided by !gobby(src).) Thanks; hint added. Regards, Adam---End Message---
Bug#768970: unblock: openstack-pkg-tools/19 (was: unblock: openstack-pkg-tools/17)
On 2014-11-10 18:31, Thomas Goirand wrote: Hi, It's looking like I should use, in a systemd unit file: RuntimeDirectory=${PROJECT_NAME} which is what version 19 does. That's the only change with version 17, so I didn't do a .debdiff. Let me know if you need one. Cheers, Thomas Goirand (zigo) Ok, unblocked version 19. ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54610ab6.8020...@thykier.net
Bug#768970: marked as done (unblock: openstack-pkg-tools/17)
Your message dated Mon, 10 Nov 2014 20:05:57 +0100 with message-id 54610c95.5090...@thykier.net and subject line Re: Bug#768970: unblock: openstack-pkg-tools/17 has caused the Debian Bug report #768970, regarding unblock: openstack-pkg-tools/17 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, The version 16 of openstack-pkg-tools attempted to support systemd, but it wasn't creating /var/run/PROJECT-NAME, and therefore, it isn't possible to start daemons properly if using systemd in Jessie. Version 17 corrects the problem, together with adding the possibility to *not* use --config-file, as this is needed to fix another bug. Please unblock openstack-pkg-tools/17. Once this upload is approved, I'll have to proceed with uploading updates for all OpenStack core packages, which is needed anyway to add new Debconf translations which were sent to the BTS. Cheers, Thomas Goirand (zigo) diff --git a/debian/changelog b/debian/changelog index 84a6a18..dd170aa 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +openstack-pkg-tools (17) unstable; urgency=medium + + * Make it possible to have no --config-file= argument for the daemon. + * Adds a RuntimeDirectory=/var/run/${PROJECT_NAME} in the systemd template, +so that /var/run/${PROJECT_NAME} can be created on boot (Closes: #767711). + + -- Thomas Goirand z...@debian.org Wed, 29 Oct 2014 00:31:49 +0800 + openstack-pkg-tools (16) unstable; urgency=medium * Fix some upstart job generation handling for murano-agent. diff --git a/init-template/init-script-template b/init-template/init-script-template index 810fc34..0326b5d 100644 --- a/init-template/init-script-template +++ b/init-template/init-script-template @@ -29,7 +29,9 @@ if [ -z ${CONFIG_FILE} ] ; then CONFIG_FILE=/etc/${PROJECT_NAME}/${PROJECT_NAME}.conf fi LOGFILE=/var/log/${PROJECT_NAME}/${NAME}.log -DAEMON_ARGS=${DAEMON_ARGS} --config-file=${CONFIG_FILE} +if [ -z ${NO_OPENSTACK_CONFIG_FILE_DAEMON_ARG} ] ; then + DAEMON_ARGS=${DAEMON_ARGS} --config-file=${CONFIG_FILE} +fi # Exit if the package is not installed [ -x $DAEMON ] || exit 0 diff --git a/init-template/pkgos-gen-systemd-unit b/init-template/pkgos-gen-systemd-unit index 0ce0858..8168319 100755 --- a/init-template/pkgos-gen-systemd-unit +++ b/init-template/pkgos-gen-systemd-unit @@ -35,6 +35,7 @@ User=${SYSTEM_USER} Group=${SYSTEM_GROUP} ExecStart=${SCRIPTNAME} systemd-start ExecStop=${SCRIPTNAME} systemd-stop +RuntimeDirectory=/var/run/${PROJECT_NAME} PIDFile=/var/run/${PROJECT_NAME}/${NAME}.pid Restart=on-failure Type=forking ---End Message--- ---BeginMessage--- On 2014-11-10 14:45, Thomas Goirand wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, The version 16 of openstack-pkg-tools attempted to support systemd, but it wasn't creating /var/run/PROJECT-NAME, and therefore, it isn't possible to start daemons properly if using systemd in Jessie. Version 17 corrects the problem, together with adding the possibility to *not* use --config-file, as this is needed to fix another bug. Please unblock openstack-pkg-tools/17. Once this upload is approved, I'll have to proceed with uploading updates for all OpenStack core packages, which is needed anyway to add new Debconf translations which were sent to the BTS. Cheers, Thomas Goirand (zigo) Unblocked version 19 and this time closing the bug too. ~Niels---End Message---
Bug#768932: marked as done (unblock: drupal7-mod-fontawesome)
Your message dated Mon, 10 Nov 2014 20:09:00 +0100 with message-id 54610d4c.9050...@thykier.net and subject line Re: Bug#768932: unblock: drupal7-mod-fontawesome has caused the Debian Bug report #768932, regarding unblock: drupal7-mod-fontawesome to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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 + + ---End Message--- ---BeginMessage--- On 2014-11-10 10:47, Daniel Pocock wrote: 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 [...] Unblocked, thanks. ~Niels---End Message---
Bug#768931: marked as done (unblock: drupal7-mod-jqueryi18nproperties)
Your message dated Mon, 10 Nov 2014 20:18:43 +0100 with message-id 54610f93.30...@thykier.net and subject line Re: Bug#768931: unblock: drupal7-mod-jqueryi18nproperties has caused the Debian Bug report #768931, regarding unblock: drupal7-mod-jqueryi18nproperties to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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', ---End Message--- ---BeginMessage--- On 2014-11-10 10:38, Daniel Pocock wrote: Package: release.debian.org The upload to unstable fixes a small but essential bug: bugs.debian.org/768502 [...] Unblocked, thanks. ~Niels---End Message---
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#768935: unblock: drupal7-mod-drucall
Control: owner -1 ! On 2014-11-10 11:11, Daniel Pocock wrote: Package: release.debian.org drupal7-mod-drucall is closely related to the jscommunicator package [...] Since it is related to jscommunicator, I might as well take this one as well. ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/546115b8.5050...@thykier.net
Processed: Re: Bug#768935: unblock: drupal7-mod-drucall
Processing control commands: owner -1 ! Bug #768935 [release.debian.org] unblock: drupal7-mod-drucall Owner recorded as Niels Thykier ni...@thykier.net. -- 768935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b768935.1415648709521.transcr...@bugs.debian.org
Processed: Re: unblock: pynag and syslog-nagios-bridge
Processing control commands: tags -1 moreinfo Bug #768930 [release.debian.org] unblock: pynag and syslog-nagios-bridge Added tag(s) moreinfo. -- 768930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b768930.14156493845661.transcr...@bugs.debian.org
Bug#769026: unblock: cgminer/4.7.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package cgminer Fix for important bug #767719 cgminer was configured with the most configuration options possible. However, some options are only compatible with specific hardware and would cause crashes on many systems. This fix reduces the number of configuration options to what upstream recommends for universal compatibility and stable operation. This fix just reduces the number of configuration options that are enabled and updates the manpage accordingly. (manpage was built separately for each arch, now is included with the source package since it is the same on all archs) unblock cgminer/4.7.0-2 -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: i386 (i686) Kernel: Linux 3.13.0-39-generic (SMP w/4 CPU cores) diff -Nru cgminer-4.7.0/debian/cgminer.1 cgminer-4.7.0/debian/cgminer.1 --- cgminer-4.7.0/debian/cgminer.1 1969-12-31 19:00:00.0 -0500 +++ cgminer-4.7.0/debian/cgminer.1 2014-11-08 12:43:06.0 -0500 @@ -0,0 +1,326 @@ +.\ DO NOT MODIFY THIS FILE! It was generated by help2man 1.44.1. +.TH CGMINER 1 November 2014 cgminer 4.7.0 User Commands +.SH NAME +cgminer \- multi-threaded multi-pool GPU, FPGA and CPU bitcoin miner. +.SH SYNOPSIS +.B cgminer +[\fI-DElmpPQqUSsTouOchnV\fR] +.SH DESCRIPTION +multi-threaded multi-pool GPU, FPGA and CPU bitcoin miner. +Built with avalon avalon2 bflsc bitfury cointerra drillbit hashfast icarus klondike mining support. +.PP +.SH OPTIONS + + +.SS +Options for both config file and command line: +.TP +\fB\-\-anu\-freq\fR arg +Set AntminerU1 frequency in MHz, range 125\-500 (default: 200.0) +.TP +\fB\-\-api\-allow\fR arg +Allow API access only to the given list of [G:]IP[/Prefix] addresses[/subnets] +.TP +\fB\-\-api\-description\fR arg +Description placed in the API status header, default: cgminer version +.TP +\fB\-\-api\-groups\fR arg +API one letter groups G:cmd:cmd[,P:cmd:*...] defining the cmds a groups can use +.TP +\fB\-\-api\-listen\fR +Enable API, default: disabled +.TP +\fB\-\-api\-mcast\fR +Enable API Multicast listener, default: disabled +.TP +\fB\-\-api\-mcast\-addr\fR arg +API Multicast listen address +.TP +\fB\-\-api\-mcast\-code\fR arg +Code expected in the API Multicast message, don't use '\-' +.TP +\fB\-\-api\-mcast\-des\fR arg +Description appended to the API Multicast reply, default: '' +.TP +\fB\-\-api\-mcast\-port\fR arg +API Multicast listen port (default: 4028) +.TP +\fB\-\-api\-network\fR +Allow API (if enabled) to listen on/for any address, default: only 127.0.0.1 +.TP +\fB\-\-api\-port\fR arg +Port number of miner API (default: 4028) +.TP +\fB\-\-api\-host\fR arg +Specify API listen address, default: 0.0.0.0 +.TP +\fB\-\-avalon\-auto\fR +Adjust avalon overclock frequency dynamically for best hashrate +.TP +\fB\-\-avalon\-cutoff\fR arg +Set avalon overheat cut off temperature (default: 60) +.TP +\fB\-\-avalon\-fan\fR +Set fanspeed percentage for avalon, single value or range (default: 20\-100) +.TP +\fB\-\-avalon\-freq\fR +Set frequency range for avalon\-auto, single value or range +.TP +\fB\-\-avalon\-options\fR arg +Set avalon options baud:miners:asic:timeout:freq:tech +.TP +\fB\-\-avalon\-temp\fR arg +Set avalon target temperature (default: 50) +.TP +\fB\-\-avalon2\-freq\fR +Set frequency range for Avalon2, single value or range, step: 25 +.TP +\fB\-\-avalon2\-voltage\fR +Set Avalon2 core voltage, in millivolts, step: 125 +.TP +\fB\-\-avalon2\-fan\fR +Set Avalon2 target fan speed +.TP +\fB\-\-avalon2\-cutoff\fR arg +Set Avalon2 overheat cut off temperature (default: 98) +.TP +\fB\-\-avalon2\-fixed\-speed\fR +Set Avalon2 fan to fixed speed +.TP +\fB\-\-avalon2\-polling\-delay\fR arg +Set Avalon2 polling delay value (ms) (default: 20) +.TP +\fB\-\-balance\fR +Change multipool strategy from failover to even share balance +.TP +\fB\-\-benchfile\fR arg +Run cgminer in benchmark mode using a work file \- produces no shares +.TP +\fB\-\-benchfile\-display\fR +Display each benchfile nonce found +.TP +\fB\-\-benchmark\fR +Run cgminer in benchmark mode \- produces no shares +.TP +\fB\-\-bflsc\-overheat\fR arg +Set overheat temperature where BFLSC devices throttle, 0 to disable (default: 85) +.TP +\fB\-\-bitburner\-voltage\fR arg +Set BitBurner (Avalon) core voltage, in millivolts +.TP +\fB\-\-bitburner\-fury\-voltage\fR arg +Set BitBurner Fury core voltage, in millivolts +.TP +\fB\-\-bitburner\-fury\-options\fR arg +Override avalon\-options for BitBurner Fury boards baud:miners:asic:timeout:freq +.TP +\fB\-\-bxf\-bits\fR arg +Set max BXF/HXF bits for overclocking (default: 54) +.TP +\fB\-\-bxf\-debug\fR arg +BXF: Debug all USB I/O, is to the
Bug#768930: unblock: pynag and syslog-nagios-bridge
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? ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5461185e.7000...@thykier.net
Bug#769027: (pre-approval for) unblock: dhcpy6d/0.4-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I intend to upload the debdiff below to unstable to fix the following two RC bugs: #768989 [G|P| ] [dhcpy6d] dhcpy6d: Overwrites lease databases upon package upgrade if SQLite backend is used #767817 [S|P| ] [dhcpy6d] dhcpy6d: modifies conffiles (policy 10.7.3): /etc/default/dhcpy6d Since the minimal fix for #767817 introduced a new lintian warning (executable-not-elf-or-script usr/share/dhcpy6d/default/dhcpy6d) and because the fix #768989 already modifies the one line in debian/dhcpy6d.postinst which needs to be changed to fix the remaining part of ... #769006 [m| | ] [dhcpy6d] dhcpy6d: Multiple files with unnecessary executable bit I included a fix for this issue/lintian warning, too, but I have neither yet pushed that part nor uploaded 0.4-2 yet. So if the fix for #769006 included below is not ok, and the lintian warning executable-not-elf-or-script is ok to be introduced by the RC fix, I'll upload 0.4-2 without the #769006 fix (and send a new debdiff afterwards). Please note that the removal of dhcpy6d-0.4/debian/dhcpy6d.default below is actually just deletion of a symbolic link. Upstream's dhcpy6d-0.4/etc/default/dhcpy6d (to which the symlink pointed) still exists. Following the debdiff between the two source packages and then the debdiff between the two resulting binary packages. $ debdiff ../dhcpy6d_0.4-{1,2}.dsc diff -Nru dhcpy6d-0.4/debian/changelog dhcpy6d-0.4/debian/changelog --- dhcpy6d-0.4/debian/changelog2014-10-22 21:03:57.0 +0200 +++ dhcpy6d-0.4/debian/changelog2014-11-10 19:56:59.0 +0100 @@ -1,3 +1,18 @@ +dhcpy6d (0.4-2) unstable; urgency=medium + + * Handle /etc/default/dhcpy6d with ucf. (Closes: #767817) ++ Install file to /usr/share/dhcpy6d/default/dhcpy6d instead, remove + symlink debian/dhcpy6d.default, add debian/dhcpy6d.install. ++ Depend on ucf. + * Install volatile.sqlite into /usr/share/dhcpy6d/ and copy it to +/var/lib/dhcpy6d/volatile.sqlite during postinst only if it doesn't +yet exist. Remove it upon purge. (Closes: #768989) + * Both fixes above together also remove unnecessary executable bits. +(Else the fix for #767817 newly introduces the lintian warning +executable-not-elf-or-script; closes: #769006) + + -- Axel Beckert a...@debian.org Mon, 10 Nov 2014 19:56:57 +0100 + dhcpy6d (0.4-1) unstable; urgency=low [ Henri Wahl ] diff -Nru dhcpy6d-0.4/debian/control dhcpy6d-0.4/debian/control --- dhcpy6d-0.4/debian/control 2014-10-22 15:41:40.0 +0200 +++ dhcpy6d-0.4/debian/control 2014-11-10 12:40:18.0 +0100 @@ -15,6 +15,7 @@ Package: dhcpy6d Architecture: all Depends: adduser, + ucf, ${misc:Depends}, ${python:Depends} Pre-Depends: dpkg (= 1.16.5) diff -Nru dhcpy6d-0.4/debian/dhcpy6d.default dhcpy6d-0.4/debian/dhcpy6d.default --- dhcpy6d-0.4/debian/dhcpy6d.default 2014-10-22 21:36:32.0 +0200 +++ dhcpy6d-0.4/debian/dhcpy6d.default 1970-01-01 01:00:00.0 +0100 @@ -1,2 +0,0 @@ -# dhcpy6d is disabled by default -#RUN=yes diff -Nru dhcpy6d-0.4/debian/dhcpy6d.dirs dhcpy6d-0.4/debian/dhcpy6d.dirs --- dhcpy6d-0.4/debian/dhcpy6d.dirs 1970-01-01 01:00:00.0 +0100 +++ dhcpy6d-0.4/debian/dhcpy6d.dirs 2014-11-10 16:13:28.0 +0100 @@ -0,0 +1 @@ +usr/share/dhcpy6d/ diff -Nru dhcpy6d-0.4/debian/dhcpy6d.install dhcpy6d-0.4/debian/dhcpy6d.install --- dhcpy6d-0.4/debian/dhcpy6d.install 1970-01-01 01:00:00.0 +0100 +++ dhcpy6d-0.4/debian/dhcpy6d.install 2014-11-07 19:45:02.0 +0100 @@ -0,0 +1 @@ +etc/default/dhcpy6d usr/share/dhcpy6d/default/ diff -Nru dhcpy6d-0.4/debian/dhcpy6d.postinst dhcpy6d-0.4/debian/dhcpy6d.postinst --- dhcpy6d-0.4/debian/dhcpy6d.postinst 2014-09-18 19:53:36.0 +0200 +++ dhcpy6d-0.4/debian/dhcpy6d.postinst 2014-11-10 19:14:41.0 +0100 @@ -50,14 +50,23 @@ if [ ! -e /var/log/dhcpy6d.log ]; then touch /var/log/dhcpy6d.log fi -chown $SERVER_USER:$SERVER_GROUP /var/log/dhcpy6d.log -chmod 0770 /var/log/dhcpy6d.log +if [ ! -e /var/lib/dhcpy6d/volatile.sqlite ]; then +cp /usr/share/dhcpy6d/volatile.sqlite /var/lib/dhcpy6d/volatile.sqlite +fi +chown $SERVER_USER:$SERVER_GROUP /var/log/dhcpy6d.log /var/lib/dhcpy6d/volatile.sqlite +chmod 0660 /var/log/dhcpy6d.log /var/lib/dhcpy6d/volatile.sqlite # 6. add DUID entry to /etc/default/dhcpy6d if not yet existing -if [ ! $(grep DUID= /etc/default/dhcpy6d) ]; then -echo /etc/default/dhcpy6d -echo # LLT DUID generated by Debian /etc/default/dhcpy6d -echo DUID=$(dhcpy6d --generate-duid) /etc/default/dhcpy6d +TMPFILE=`mktemp` +cat /usr/share/dhcpy6d/default/dhcpy6d ${TMPFILE} +echo${TMPFILE} +echo # LLT DUID generated by Debian ${TMPFILE} +if [ ! -e /etc/default/dhcpy6d ] || ! grep -q
Re: About requests.packages.urllib3 in Debian
Hello Matthias, sorry for the late reply, we had a problematic weekend due to weather in Sicily. On Wednesday 05 November 2014 07:52:55 Matthias Urlichs wrote: I'd add a stub _file_ which just contains from urllib3 import *. Well, urllib3 is composed of multiple subpackage, for a single module this would be the best soluction, but unfortunately it will not works well for a package with multiple submodules. For example, urllib3.contrib.pyopenssl is not imported by from urllib3 import *. IMHO using from-import would be weak: think about new names introduced during an update, missing one will break all code that use the missing name. Cheers, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
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#769033: pre-unblock: php-horde-editor/2.0.4+upstream0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear busy team, (Excuse my poor english). I just filled #769031 in php-horde-editor. Some context: - Since some month, HTML composing in IMP, the Horde webmail, is broken (plain text works) - This is due to some big changes to ckeditor 4.x - Horde upstream include ckeditor 3.6.6 in their source - I tried to fix this without luck. Other persons tried also. - According to Horde devs: Using Ckeditor 4.x will only be possible when all of IMP's javascript code interfacing with Ckeditor is rewritten. I see 3 possible solutions: - release Horde in Debian without HTML composing - This would be odd - port IMP JS to CKeditor 4.x. I don't have the knowledge, help welcomed - use the included CKeditor 3.6.x . This requires copyright review and possible repacking - drop Horde from testing altogether. N ! As jessie is frozen, I need some advice. My choice is #3, which will provide good user experience matching upstream's. But this will take some time to do the copyright review (probably using unminified versions, slower). Regards Mathieu Parent, main pkg-horde-hacker -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- 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/20141110210534.9895.55239.report...@ultrathieu.sathieu.net
Bug#768994: marked as done (unblock: python-stem/1.2.2-1.1)
Your message dated Mon, 10 Nov 2014 21:07:42 + with message-id 1415653662.3087.7.ca...@adam-barratt.org.uk and subject line Re: Bug#768994: unblock: python-stem/1.2.2-1.1 has caused the Debian Bug report #768994, regarding unblock: python-stem/1.2.2-1.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-stem Fix for RC bug #767555 unblock python-stem/1.2.2-1.1 diff -Nru python-stem-1.2.2/debian/changelog python-stem-1.2.2/debian/changelog --- python-stem-1.2.2/debian/changelog 2014-07-02 13:33:10.0 -0400 +++ python-stem-1.2.2/debian/changelog 2014-11-10 10:45:06.0 -0500 @@ -1,3 +1,15 @@ +python-stem (1.2.2-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: Remove /usr/bin/tor-prompt from python3-stem due to file +conflict with python-stem (Closes: #767555) +- Since tor-prompt uses /usr/bin/env python, it will always execute with + python, not python3, so shipping it with python3-stem didn't work in any + case + * debian/control: Add versioned breaks for python3-stem 1.2.2-1.1~ + + -- Scott Kitterman sc...@kitterman.com Mon, 10 Nov 2014 10:27:48 -0500 + python-stem (1.2.2-1) unstable; urgency=medium * New upstream release. diff -Nru python-stem-1.2.2/debian/control python-stem-1.2.2/debian/control --- python-stem-1.2.2/debian/control 2014-07-02 13:32:21.0 -0400 +++ python-stem-1.2.2/debian/control 2014-11-10 10:45:24.0 -0500 @@ -12,6 +12,7 @@ Package: python-stem Architecture: all Depends: ${python:Depends}, ${misc:Depends} +Breaks: python3-stem ( 1.2.2-1.1~) Description: Tor control library for Python Stem is a TorCtl successor, a Python Tor controller with extensions to support path building and various constraints on node and path selection, as well as diff -Nru python-stem-1.2.2/debian/rules python-stem-1.2.2/debian/rules --- python-stem-1.2.2/debian/rules 2014-07-02 12:37:18.0 -0400 +++ python-stem-1.2.2/debian/rules 2014-11-10 10:38:07.0 -0500 @@ -23,6 +23,7 @@ for py in $(PY3VERS); do \ $$py setup.py install --root debian/python3-stem \ --install-layout=deb; \ + rm -rf $(CURDIR)/debian/python3-stem/usr/bin; \ done; \ override_dh_auto_clean: ---End Message--- ---BeginMessage--- On Mon, 2014-11-10 at 11:31 -0500, Scott Kitterman wrote: Please unblock package python-stem Fix for RC bug #767555 unblock python-stem/1.2.2-1.1 Unblocked. Regards, Adam---End Message---
Re: Release Team Sprint Results
Hi Jonathan, On Sun, Nov 09, 2014 at 11:52:31AM +, Jonathan Wiltshire wrote: Release notes = We seek patches and editors for the release notes. We identified the following topics as being particularly important: - init system changes - How to choose (before upgrading) - Pros / cons of upgrading - i486 support dropped I'm rather certain that i486 hasn't been supported in Debian for at least the past 4 years (and probably much longer, my memory is fuzzy; but as a data point, https://lists.debian.org/debian-devel/2011/11/msg00687.html). Why is this on the release team's radar as something that needs to be documented in the release notes for jessie? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: About requests.packages.urllib3 in Debian
Hello Jakub, On Wednesday 05 November 2014 12:15:29 Jakub Wilk wrote: Maybe it'd be overkill, but it's possible to teach Python that urllib3 and requests.packages.urllib3 are the same thing. Adding something like this to the top of requests/__init__.py should do the trick: [CUT patch] Many thanks for the patch! On IRC Paul Tagliamonte suggested also something like this and, after looking at half of requests dependant packages (I will continue to look at them) I'm starting to think that this is the best solution because it's entirely transparent both for our package and for users who install packages on Debian using pip install --user. #753578 was, at first, reported upstream: https://github.com/mk-fg/python-onedrive/issues/13 by someone who installed a something not packaged yet for Debian. So, before my analysis on requests' dependant is completed, I'm going to open an RC bug on requests, fix it using Jakub's patch and than open an unblock bug. If there are any objections please let me know. Kind regards, -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Release Team Sprint Results
On Mon, 2014-11-10 at 13:08 -0800, Steve Langasek wrote: Hi Jonathan, On Sun, Nov 09, 2014 at 11:52:31AM +, Jonathan Wiltshire wrote: [...] - i486 support dropped I'm rather certain that i486 hasn't been supported in Debian for at least the past 4 years (and probably much longer, my memory is fuzzy; but as a data point, https://lists.debian.org/debian-devel/2011/11/msg00687.html). Why is this on the release team's radar as something that needs to be documented in the release notes for jessie? I believe this was intended as a reference to this change in the latest Linux kernel upload: * [i386] Rename 486 flavour to 586, as it has not worked on 486 processors since we enabled CC_STACKPROTECTOR (Closes: #766105) Regards, Adam -- 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/1415654400.3087.9.ca...@adam-barratt.org.uk
Re: Release Team Sprint Results
[re-adding -devel@] On Mon, 2014-11-10 at 21:20 +, Adam D. Barratt wrote: On Mon, 2014-11-10 at 13:08 -0800, Steve Langasek wrote: Hi Jonathan, On Sun, Nov 09, 2014 at 11:52:31AM +, Jonathan Wiltshire wrote: [...] - i486 support dropped I'm rather certain that i486 hasn't been supported in Debian for at least the past 4 years (and probably much longer, my memory is fuzzy; but as a data point, https://lists.debian.org/debian-devel/2011/11/msg00687.html). Why is this on the release team's radar as something that needs to be documented in the release notes for jessie? I believe this was intended as a reference to this change in the latest Linux kernel upload: * [i386] Rename 486 flavour to 586, as it has not worked on 486 processors since we enabled CC_STACKPROTECTOR (Closes: #766105) Regards, Adam -- 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/1415655187.3087.10.ca...@adam-barratt.org.uk
Re: Release Team Sprint Results
On Mon, Nov 10, 2014 at 09:33:07PM +, Adam D. Barratt wrote: [re-adding -devel@] On Mon, 2014-11-10 at 21:20 +, Adam D. Barratt wrote: On Mon, 2014-11-10 at 13:08 -0800, Steve Langasek wrote: Hi Jonathan, On Sun, Nov 09, 2014 at 11:52:31AM +, Jonathan Wiltshire wrote: [...] - i486 support dropped I'm rather certain that i486 hasn't been supported in Debian for at least the past 4 years (and probably much longer, my memory is fuzzy; but as a data point, https://lists.debian.org/debian-devel/2011/11/msg00687.html). Why is this on the release team's radar as something that needs to be documented in the release notes for jessie? I believe this was intended as a reference to this change in the latest Linux kernel upload: * [i386] Rename 486 flavour to 586, as it has not worked on 486 processors since we enabled CC_STACKPROTECTOR (Closes: #766105) Ok, well, given that Debian didn't work on 486 for years before that, I think this is a non-event that doesn't need to be release-noted. However, given that this fatal bug has not (so far as I know) been reported in the 5 years since it was introduced in unstable, I suspect you're one of a very few people still using Debian on a 486, and you may find many other things broken. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766105#28 -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: Plan B for kfreebsd
Petr Salinger wrote: Jonathan Wiltshire wrote: [...] though we do hope that the porters will be able to make a simultaneous unofficial release. It is unclear, what we have to duplicate. Do we stay in testing ? I'd like to know this as soon as possible as it affects our planning. Thanks. If we don't stay in testing, we'd at least want to archive off the last-built kfreebsd packages before they are deleted... Will be there a repository copy in time of official stable release ? A snapshot would be the basis of any unofficial stable release. To support it as best we can, we might like to update it (either in-situ, or in a separate repository) with stable and security updates applied. Maybe just for the core kfreebsd packages we maintain, but ideally the whole archive depending on resources. The same snapshot could also be cloned as the basis of an unofficial testing release; if we could update it with packages from the official Debian sid (trying to mirror what Britney is doing) what we'd have is a kind of rolling release. We could also hold packages back at older versions if they'd introduce portability issues. In the old days, we used to have unreleased suite on debian-ports, it augmented sid whenever we needed a different version of a package. I'd like to avoid that in sid - so that it still works properly using only official packages. But certainly for unofficial releases, a supplemental repository would be great for us. We can bypass usual freeze policy to fix bugs we think are important, which may not have got an unblock. We can apply kfreebsd patches to some packages, such as in the Xorg Intel graphics driver to make it work better out-of-the-box for users. We can even overrule maintainers' decisions; perhaps make openjdk-7 our default JRE, change APT config to not install recommends, override default shell or MTA ;) So - while I disagree with the release team's decision - being an unofficial release doesn't have to be a bad thing for us. It actually gives us freedom to make improvements as we see fit. And it could be a lot of fun. Regards, -- Steven Chamberlain ste...@pyro.eu.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/20141110220944.ga12...@squeeze.pyro.eu.org
Re: Release Team Sprint Results
* Steve Langasek (vor...@debian.org) [141110 23:06]: On Mon, Nov 10, 2014 at 09:33:07PM +, Adam D. Barratt wrote: [re-adding -devel@] On Mon, 2014-11-10 at 21:20 +, Adam D. Barratt wrote: On Mon, 2014-11-10 at 13:08 -0800, Steve Langasek wrote: Hi Jonathan, On Sun, Nov 09, 2014 at 11:52:31AM +, Jonathan Wiltshire wrote: [...] - i486 support dropped I'm rather certain that i486 hasn't been supported in Debian for at least the past 4 years (and probably much longer, my memory is fuzzy; but as a data point, https://lists.debian.org/debian-devel/2011/11/msg00687.html). Why is this on the release team's radar as something that needs to be documented in the release notes for jessie? I believe this was intended as a reference to this change in the latest Linux kernel upload: * [i386] Rename 486 flavour to 586, as it has not worked on 486 processors since we enabled CC_STACKPROTECTOR (Closes: #766105) Ok, well, given that Debian didn't work on 486 for years before that, I think this is a non-event that doesn't need to be release-noted. Well, I think the reference was mostly what we might need to document. If nobody noticed that, then well, you are right, and perhaps we don't need to document that. (Technically it was still input to the release notes, which however was then ignored.) Andi -- 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/20141110221935.gd...@mails.so.argh.org
Re: Release Team Sprint Results
On 2014-11-10 22:01, Steve Langasek wrote: On Mon, Nov 10, 2014 at 09:33:07PM +, Adam D. Barratt wrote: [re-adding -devel@] On Mon, 2014-11-10 at 21:20 +, Adam D. Barratt wrote: On Mon, 2014-11-10 at 13:08 -0800, Steve Langasek wrote: Hi Jonathan, On Sun, Nov 09, 2014 at 11:52:31AM +, Jonathan Wiltshire wrote: [...] - i486 support dropped I'm rather certain that i486 hasn't been supported in Debian for at least the past 4 years (and probably much longer, my memory is fuzzy; but as a data point, https://lists.debian.org/debian-devel/2011/11/msg00687.html). Why is this on the release team's radar as something that needs to be documented in the release notes for jessie? I believe this was intended as a reference to this change in the latest Linux kernel upload: * [i386] Rename 486 flavour to 586, as it has not worked on 486 processors since we enabled CC_STACKPROTECTOR (Closes: #766105) Yes, that matches my recollection. (Our notes on this are pretty rough, and what's in that mail is nearly verbatim from the notes, so...) Ok, well, given that Debian didn't work on 486 for years before that, I think this is a non-event that doesn't need to be release-noted. That sounds reasonable. Thanks! -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- 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/09115201e23228ccfb8fd356a90dd...@hogwarts.powdarrmonkey.net
Re: Plan B for kfreebsd
* Steven Chamberlain (ste...@pyro.eu.org) [141110 23:10]: Petr Salinger wrote: Jonathan Wiltshire wrote: [...] though we do hope that the porters will be able to make a simultaneous unofficial release. It is unclear, what we have to duplicate. Do we stay in testing ? I'd like to know this as soon as possible as it affects our planning. Thanks. If we don't stay in testing, we'd at least want to archive off the last-built kfreebsd packages before they are deleted... That sounds sensible. As you want to do an unofficial release, I think we should coordinate so that this doesn't create unnecessary additional efforts. I don't know how the others feel about, when should kbsd be removed from testing? That would give some impression how fast this should be done. But certainly for unofficial releases, a supplemental repository would be great for us. We can bypass usual freeze policy to fix bugs we think are important, which may not have got an unblock. I'd replace that with that allows to have an freeze policy centered around kbsd. Andi -- 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/20141110222309.ge...@mails.so.argh.org
Re: Plan B for kfreebsd
Hi, Andreas Barth wrote: * Steven Chamberlain (ste...@pyro.eu.org) [141110 23:10]: Petr Salinger wrote: It is unclear, what we have to duplicate. Do we stay in testing ? I'd like to know this as soon as possible as it affects our planning. Thanks. If we don't stay in testing, we'd at least want to archive off the last-built kfreebsd packages before they are deleted... That sounds sensible. As you want to do an unofficial release, I think we should coordinate so that this doesn't create unnecessary additional efforts. Thank you, and others who have offered to help as they can; but I'm sad we're having to do this instead of being part of the official release, and thus duplicate a lot of process/infrastructure that was already in place since wheezy. I don't know how the others feel about, when should kbsd be removed from testing? That would give some impression how fast this should be done. Is that a 'no' in answer to Petr's question: kfreebsd actually must be removed from testing? I think removing it anytime in the next 1-3 months would be okay from our point of view. Would you normally delete the packages outright, or archive them off in any place similar to archive.d.o? I guess snapshots.d.o would still have copies of the last packages that were _in_ testing? But won't have the indices _for_ testing. But certainly for unofficial releases, a supplemental repository would be great for us. We can bypass usual freeze policy to fix bugs we think are important, which may not have got an unblock. I'd replace that with that allows to have an freeze policy centered around kbsd. I don't think it's limited to that; in making an unofficial release, we become our own release managers, and can try to apply our own... personal taste here. I'll discuss that on -bsd@ rather than here. Regards, -- Steven Chamberlain ste...@pyro.eu.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/20141110230127.ga13...@squeeze.pyro.eu.org
Bug#769043: unblock: xserver-xorg-video-geode/2.11.16-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package xserver-xorg-video-geode 2.11.16-4 mistakenly dropped a (Provides: xorg-driver-video). Without it, on hosts without any other X.Org video driver installed, this results in an APT decision to remove the whole X.Org stack and most desktop applications. debdiff (minus changelog.dch, which somehow shipped with 2.11.16-4 unnoticed): diff -Nru xserver-xorg-video-geode-2.11.16/debian/changelog xserver-xorg-video-geode-2.11.16/debian/changelog --- xserver-xorg-video-geode-2.11.16/debian/changelog 2014-09-14 13:41:27.0 +0300 +++ xserver-xorg-video-geode-2.11.16/debian/changelog 2014-11-11 01:12:48.0 +0200 @@ -1,3 +1,12 @@ +xserver-xorg-video-geode (2.11.16-5) unstable; urgency=medium + + * debian/control: ++ Provides: xorg-driver-video + This reverses part of the previous changes. Without this, APT uninstalls + the whole X.Org if no other video driver is installed (Closes: #769042). + + -- Martin-Éric Racine martin-eric.rac...@iki.fi Tue, 11 Nov 2014 01:07:59 +0200 + xserver-xorg-video-geode (2.11.16-4) unstable; urgency=medium * debian/control,debian/rules; Gotten one step closer to XSF: diff -Nru xserver-xorg-video-geode-2.11.16/debian/control xserver-xorg-video-geode-2.11.16/debian/control --- xserver-xorg-video-geode-2.11.16/debian/control 2014-09-14 14:00:15.0 +0300 +++ xserver-xorg-video-geode-2.11.16/debian/control 2014-11-11 00:33:21.0 +0200 @@ -23,7 +23,8 @@ Depends: ${misc:Depends}, ${shlibs:Depends}, ${xviddriver:Depends} -Provides: xserver-xorg-video-amd, +Provides: xorg-driver-video, + xserver-xorg-video-amd, ${xviddriver:Provides} Breaks: xserver-xorg-video-amd ( ${binary:Version}) Description: X.Org X server -- Geode GX2/LX display driver unblock xserver-xorg-video-geode/2.11.16-5 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (1001, 'testing'), (1001, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/debian-release
Bug#769044: unblock (pre-approval): xfce4-notes-plugin
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I'm seeking approval for fixing the arm64 build failure in xfce4-notes-plugin. The package FTBFS due to outdated config.sub/guess. The maintainer doesn't have a problem with the changes but wants approval from the release team before going ahead. The attatched debdiff uses --with autotools_dev to update config.sub and config.guess unconditionally . If you would preffer a different approach to updating them please tell me. -- System Information: Debian Release: 6.0.3 APT prefers oldstable-proposed-updates APT policy: (500, 'oldstable-proposed-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141110231846.9664.1233.reportbug@localhost
Re: Plan B for kfreebsd
Hi all! First, I do not really know enough about release workflow I guess to know what -release@ does not want to do for kfreebsd apart from stamping it as an official release so some of my whishes may be totally reasonable or way of -- please tell me! Steven Chamberlain ste...@pyro.eu.org writes: Andreas Barth wrote: If we don't stay in testing, we'd at least want to archive off the last-built kfreebsd packages before they are deleted... That sounds sensible. As you want to do an unofficial release, I think we should coordinate so that this doesn't create unnecessary additional efforts. My hope here would be to keep a kfreebsd-* in testing -- without the RC severity of bugs and without blocking transition due to out-of-dateness -- I think release tools have the support for that. It would also just automatically continue to improve the non-freebsd-specific packages untill a release happens. But certainly for unofficial releases, a supplemental repository would be great for us. We can bypass usual freeze policy to fix bugs we think are important, which may not have got an unblock. I guess we need that in some way -- we need to do some uploads that do not concern the normal release process like a last kernel upload. I don't think it's limited to that; in making an unofficial release, we become our own release managers, and can try to apply our own... personal taste here. I'll discuss that on -bsd@ rather than here. Which also needs we need to do that. For almost all of debian, the normal release procedures should really work fine for us as well and the more we can get automatically the better IMHO. Plus everywhere we diverge from the normal release process we need to stay atop of these deltas for the whole time. There's also stable updates and security we need to think of. I guess stable updates can be handled without problem manually as it's punctual and not so time critical. security is actually what worries me most. Guess ideally we can still source from security on wanna-build so builds just happen whenever there's a update. Guess we need someone to handle build failures and problems there ourselves but that's way more managable. Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer signature.asc Description: PGP signature
Bug#769049: unblock: ruby-elasticsearch/1.0.5-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ruby-elasticsearch. This package has a RC bug (#768613) filed against it due to a dependency that is not currently in testing. The dependency is for an optional transport-layer plugin that doesn't affect any functionality in the package. One unit test (out of 127) has also been disabled. I would love to see this package stay in testing and not be removed due to a broken, optional dependency. No source changes were made, and the binary packages are unchanged ruby-elasticsearch (1.0.5-2) unstable; urgency=medium * Remove build/test dependency on ruby-patron. The ruby-patron package is not currently in testing and is only one of a handful of transport-layer adapters and so does not affect any functionality. (Closes: #768613) -- Tim Potter t...@hp.com Tue, 11 Nov 2014 10:21:11 +1100 Attached are debdiffs for the source and binary packages. unblock ruby-elasticsearch/1.0.5-1 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.15.3-tinycore64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash diff -Nru ruby-elasticsearch-1.0.5/debian/changelog ruby-elasticsearch-1.0.5/debian/changelog --- ruby-elasticsearch-1.0.5/debian/changelog 2014-11-11 10:48:47.0 +1100 +++ ruby-elasticsearch-1.0.5/debian/changelog 2014-11-11 10:51:21.0 +1100 @@ -1,3 +1,12 @@ +ruby-elasticsearch (1.0.5-2) unstable; urgency=medium + + * Remove build/test dependency on ruby-patron. The ruby-patron +package is not currently in testing and is only one of a handful +of transport-layer adapters and so does not affect any functionality. +(Closes: #768613) + + -- Tim Potter t...@hp.com Tue, 11 Nov 2014 10:21:11 +1100 + ruby-elasticsearch (1.0.5-1) unstable; urgency=low * Initial release (Closes: #760806) diff -Nru ruby-elasticsearch-1.0.5/debian/control ruby-elasticsearch-1.0.5/debian/control --- ruby-elasticsearch-1.0.5/debian/control 2014-11-11 10:48:47.0 +1100 +++ ruby-elasticsearch-1.0.5/debian/control 2014-11-11 10:51:21.0 +1100 @@ -14,7 +14,6 @@ ruby-jsonify, ruby-mocha, ruby-multi-json, - ruby-patron, ruby-shoulda-context, ruby-test-unit Standards-Version: 3.9.6 diff -Nru ruby-elasticsearch-1.0.5/debian/patches/disable-patron-test.patch ruby-elasticsearch-1.0.5/debian/patches/disable-patron-test.patch --- ruby-elasticsearch-1.0.5/debian/patches/disable-patron-test.patch 1970-01-01 10:00:00.0 +1000 +++ ruby-elasticsearch-1.0.5/debian/patches/disable-patron-test.patch 2014-11-11 10:51:21.0 +1100 @@ -0,0 +1,28 @@ +Description: Remove semi-bogus build/test dependency on ruby-patron + The ruby-patron package is currently not in testing, and looks like + it is no longer maintained. This patch disables the build and test + dependency on ruby-patron as it's an optional transport-layer plugin. +Author: Tim Potter t...@hp.com +Last-Update: 2014-11-11 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +Index: ruby-elasticsearch/elasticsearch-transport/test/unit/client_test.rb +=== +--- ruby-elasticsearch.orig/elasticsearch-transport/test/unit/client_test.rb ruby-elasticsearch/elasticsearch-transport/test/unit/client_test.rb +@@ -193,15 +193,6 @@ class Elasticsearch::Transport::ClientTe + + assert_includes handlers, Faraday::Adapter::Typhoeus + end +- +- should detect the adapter do +-require 'patron'; load 'patron.rb' +- +-c = Elasticsearch::Transport::Client.new +-handlers = c.transport.connections.all.first.connection.builder.handlers +- +-assert_includes handlers, Faraday::Adapter::Patron +- end + end + + end diff -Nru ruby-elasticsearch-1.0.5/debian/patches/series ruby-elasticsearch-1.0.5/debian/patches/series --- ruby-elasticsearch-1.0.5/debian/patches/series 2014-11-11 10:48:47.0 +1100 +++ ruby-elasticsearch-1.0.5/debian/patches/series 2014-11-11 10:51:21.0 +1100 @@ -1 +1,2 @@ really-disable-ruby-prof.patch +disable-patron-test.patch File lists identical (after any substitutions) Control files: lines which differ (wdiff format) Depends: ruby | ruby-interpreter, ruby-elasticsearch-api (= [-1.0.5-1),-] {+1.0.5-2),+} ruby-elasticsearch-transport (= [-1.0.5-1)-] {+1.0.5-2)+} Version: [-1.0.5-1-] {+1.0.5-2+} File lists identical (after any substitutions) Control files: lines which differ (wdiff format) Version: [-1.0.5-1-] {+1.0.5-2+} File lists identical (after any substitutions) Control files: lines which differ
Bug#769049: unblock: ruby-elasticsearch/1.0.5-1
Nuts - I think I've filed this against the wrong package version and slightly too early. There should shortly be an upload of version 1.0.5-2 to unstable which (after ageing out) should then be blocked entering testing. Sorry, the whole process makes more sense now. (-: Tim. -- 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/d087a20e.1c340%timothy.pot...@hp.com
Bug#769056: unblock: rkhunter/1.4.2-0.3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package rkhunter This release fixes a single important bug (#767731) introduced in the latest upstream release, with a very simple fix: - if [ `${IPCS_CMD} -u 2/dev/null | awk -F' ' '/segments allocated/ {print $3}'` -ne 0 ]; then + if [ `LANG=C ${IPCS_CMD} -u 2/dev/null | awk -F' ' '/segments allocated/ {print $3}'` -ne 0 ]; then (the addition of LANG=C before grepping in the command's output) Attached is a full debdiff. unblock rkhunter/1.4.2-0.3 diff -Nru rkhunter-1.4.2/debian/changelog rkhunter-1.4.2/debian/changelog --- rkhunter-1.4.2/debian/changelog 2014-10-19 20:14:41.0 +1300 +++ rkhunter-1.4.2/debian/changelog 2014-11-07 14:35:51.0 +1300 @@ -1,3 +1,10 @@ +rkhunter (1.4.2-0.3) unstable; urgency=medium + + * Non-maintainer upload. + * Fix IPCS command on non-English locales (closes: #767731) + + -- Francois Marier franc...@debian.org Fri, 07 Nov 2014 14:34:19 +1300 + rkhunter (1.4.2-0.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru rkhunter-1.4.2/debian/patches/20_fix-ipcs-language.diff rkhunter-1.4.2/debian/patches/20_fix-ipcs-language.diff --- rkhunter-1.4.2/debian/patches/20_fix-ipcs-language.diff 1970-01-01 12:00:00.0 +1200 +++ rkhunter-1.4.2/debian/patches/20_fix-ipcs-language.diff 2014-11-07 14:35:51.0 +1300 @@ -0,0 +1,18 @@ +Description: Force english locale for ipcs call +Author: Francois Marier franc...@debian.org +Forwarded: https://sourceforge.net/p/rkhunter/patches/42/ +Last-Update: 2014-11-07 +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767731 +Bug: https://sourceforge.net/p/rkhunter/bugs/130/ + +--- a/files/rkhunter b/files/rkhunter +@@ -13964,7 +13964,7 @@ ${FOUND_PROCS} + touch ${IPCS_TMPFILE} + FOUND=0; echo $FOUND ${IPCS_TMPFILE} + +-if [ `${IPCS_CMD} -u 2/dev/null | awk -F' ' '/segments allocated/ {print $3}'` -ne 0 ]; then ++if [ `LANG=C ${IPCS_CMD} -u 2/dev/null | awk -F' ' '/segments allocated/ {print $3}'` -ne 0 ]; then + ${IPCS_CMD} -m | grep ^0x | while read RKH_SHM_KEY RKH_SHM_SHMID RKH_SHM_OWNER RKH_SHM_PERMS RKH_SHM_BYTES RKH_SHM_NATTACH RKH_SHM_STATUS; do + if [ $RKH_SHM_PERMS -eq 666 -a $RKH_SHM_BYTES -ge 100 ]; then + FOUND=1; echo $FOUND ${IPCS_TMPFILE} diff -Nru rkhunter-1.4.2/debian/patches/series rkhunter-1.4.2/debian/patches/series --- rkhunter-1.4.2/debian/patches/series 2014-10-19 20:14:41.0 +1300 +++ rkhunter-1.4.2/debian/patches/series 2014-11-07 14:35:51.0 +1300 @@ -1,3 +1,4 @@ 05_custom_conffile.diff 10_fix-man.diff 15_remove-empty-dir.diff +20_fix-ipcs-language.diff
Re: Plan B for kfreebsd
Christoph Egger wrote: Steven Chamberlain ste...@pyro.eu.org writes: But certainly for unofficial releases, a supplemental repository would be great for us. We can bypass usual freeze policy to fix bugs we think are important, which may not have got an unblock. I guess we need that in some way -- we need to do some uploads that do not concern the normal release process like a last kernel upload. Also, between now and release there is a risk of kfreebsd regressions introduced into testing that we want to hold back / revert. I've had opinions for a while that Debian freeze policy has some flaws, concerning not just kfreebsd but the rest of the distro. An unfortunate consequence of having a fixed freeze date, is that many big changes are rushed in at the last moment. (c.f. http://www.openbsd.org/papers/asiabsdcon2009-release_engineering/mgp5.html) Then during freeze, when most testing happens, we discover the trivial, annoying bugs that accumulate to make user experience less than ideal - but by then we can't fix them, because in the Debian BTS they only qualify as 'important' or lower severity, and likely not eligible for unblocks. You and I probably have made dozens of tiny changes on our own kfreebsd systems to make them work smoothly. For other, especially new users, those could be a total roadblock and I want to avoid that if we can at all. I've seen examples of users get frustrated by already-known issues like that and give up on using kfreebsd, and it's sad to see. I don't think it's limited to that; in making an unofficial release, we become our own release managers, and can try to apply our own... personal taste here. I'll discuss that on -bsd@ rather than here. Which also needs we need to do that. For almost all of debian, the normal release procedures should really work fine for us as well and the more we can get automatically the better IMHO. There may at least be some short-cuts we can take, things we can do to make the unofficial release easier for just a few of us to support. We could declare some packages unsupported perhaps. This is another rant coming, sorry, but I think it's relevant when we're talking about doing an unofficial release: I do feel many Debian procedures take way too much time and involve many people to fix trivial issues. A major usability problem might be fixable with just a one-line config file edit, but often there'd be a bug report, perhaps patch submitted by someone else or picked from upstream where it was fixed already; maintainer commits it to a packaging repo, uploads, it's built and waits for dinstall, and then testing migration. So for users running testing it could be 7-14 days for fixes to reach their machines. Arguably some of that time is meant for QA, but some of it is really just waiting around for some next step to happen. (And there are other good ways to supplement QA besides this). For stable, there might need to be a separate upload prepared, debdiff sent to -release@ and reviewed, approved then uploaded, built, queued for many weeks until next point release. In that case there may have been at least 4 people each do some amount of work for that obvious change, probably one of hundreds in the stable release lifetime. Or it may not meet the criteria and have to wait *2 years* or so for the next release. Imagine this was a problem faced in a corporate IT deployment. It wouldn't be acceptable to have such a workflow; work time is scarce, and the issues could be affecting others' work until fixed. Surely the same constraints or goals apply to a volunteer software distribution? Plus everywhere we diverge from the normal release process we need to stay atop of these deltas for the whole time. That's a good point I will try to bear in mind when I get carried away! In sid, by the way, I'd prefer things to stay totally in keeping with Debian practices so that maintainers can still, if they wish, build and maintain their packages for kfreebsd as they do already. Changes we make should ideally go into sid and not just stay in an unofficial repo. There's also stable updates and security we need to think of. I guess stable updates can be handled without problem manually as it's punctual and not so time critical. Yes, the stable-pu queue has debdiffs, we can somehow build updated packages based on those and update an unofficial stable repo, in sync with point releases. security is actually what worries me most. Guess ideally we can still source from security on wanna-build so builds just happen whenever there's a update. For the kfreebsd core packages (kernel and such) it's actually easier that we don't have to involve the security team and can update those directly in an unofficial repo. For the rest of the archive, we can try and do similar to the above; we might have to wait for updated source packages to become public, due to the embargo around security issues and the private security
Re: Re: Plan B for kfreebsd
Sorry, actually meant to take -release@ out of Cc: for that mail. Please follow up to -bsd@ if you have comments on it. Thanks. Regards, -- Steven Chamberlain ste...@pyro.eu.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/546171eb.3070...@pyro.eu.org
Bug#769060: unblock: m-tx/0.60d.ctan20131224-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package m-tx the m-tx lua script had a one-line bug that was fixed shortly after last years release, which I didn't realise. It is about a missing then in a long elseif Full debdiff attached, nothing spectacular, only code change in all of it is this (for m-tx.lua script): @@ -104,7 +104,7 @@ dvi = ; ps2pdf = elseif this_arg == -d then dvi = dvipdfm; ps2pdf = - elseif this_arg == -c + elseif this_arg == -c then pmx = pmxchords elseif this_arg == -F then narg = narg+1 Thanks Norbert unblock m-tx/0.60d.ctan20131224-1 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-rc4+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru m-tx-0.60d.ctan20131214/debian/changelog m-tx-0.60d.ctan20131224/debian/changelog --- m-tx-0.60d.ctan20131214/debian/changelog 2014-10-21 09:25:54.0 +0900 +++ m-tx-0.60d.ctan20131224/debian/changelog 2014-10-31 10:23:10.0 +0900 @@ -1,3 +1,10 @@ +m-tx (0.60d.ctan20131224-1) unstable; urgency=medium + + * Imported Upstream version 0.60d.ctan20131224 +- fixed m-tx.lua script (Closes: #767434) + + -- Norbert Preining prein...@debian.org Fri, 31 Oct 2014 10:22:26 +0900 + m-tx (0.60d.ctan20131214-2) unstable; urgency=medium * fix mismatch of prototypes of predelete (Closes: #749782) diff -Nru m-tx-0.60d.ctan20131214/doc/generic/m-tx/README m-tx-0.60d.ctan20131224/doc/generic/m-tx/README --- m-tx-0.60d.ctan20131214/doc/generic/m-tx/README 2013-12-12 09:52:36.0 +0900 +++ m-tx-0.60d.ctan20131224/doc/generic/m-tx/README 2013-12-24 14:19:30.0 +0900 @@ -1,4 +1,4 @@ -This is M-Tx (Music-from-TeXt), version 0.60d (2013-12-12). +This is M-Tx (Music-from-TeXt), version 0.60d (2013-12-24). M-Tx is a preprocessor for PMX that facilitates inputting lyrics. It builds the PMX input file based on a language very similar to PMX. M-Tx diff -Nru m-tx-0.60d.ctan20131214/README m-tx-0.60d.ctan20131224/README --- m-tx-0.60d.ctan20131214/README 2013-12-12 14:52:36.0 +0900 +++ m-tx-0.60d.ctan20131224/README 2013-12-24 20:19:30.0 +0900 @@ -1,4 +1,4 @@ -This is M-Tx (Music-from-TeXt), version 0.60d (2013-12-12). +This is M-Tx (Music-from-TeXt), version 0.60d (2013-12-24). M-Tx is a preprocessor for PMX that facilitates inputting lyrics. It builds the PMX input file based on a language very similar to PMX. M-Tx diff -Nru m-tx-0.60d.ctan20131214/scripts/m-tx/m-tx.lua m-tx-0.60d.ctan20131224/scripts/m-tx/m-tx.lua --- m-tx-0.60d.ctan20131214/scripts/m-tx/m-tx.lua 2013-12-11 17:09:50.0 +0900 +++ m-tx-0.60d.ctan20131224/scripts/m-tx/m-tx.lua 2013-12-24 14:19:02.0 +0900 @@ -104,7 +104,7 @@ dvi = ; ps2pdf = elseif this_arg == -d then dvi = dvipdfm; ps2pdf = - elseif this_arg == -c + elseif this_arg == -c then pmx = pmxchords elseif this_arg == -F then narg = narg+1
Bug#768930: unblock: pynag and syslog-nagios-bridge
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. signature.asc Description: PGP signature
Bug#769064: unblock: g-wrap/1.9.14-2.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package g-wrap * Build against guile-2.0 (Closes: #761210, also refer to guile-1.8-rm transition) * Automatically use aclocal/autoconf/automake version (Closes: #713203) * Add delete_aclocal_flags.patch to avoid define loop in Makefile.am Please find the debdiff attached. unblock g-wrap/1.9.14-2.1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 diff -Nru g-wrap-1.9.14/debian/changelog g-wrap-1.9.14/debian/changelog --- g-wrap-1.9.14/debian/changelog 2012-12-06 14:28:47.0 +0200 +++ g-wrap-1.9.14/debian/changelog 2014-10-29 13:54:56.0 +0200 @@ -1,3 +1,25 @@ +g-wrap (1.9.14-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Upload to unstable (Closes: #761210). + * merge changes with 1.9.14-1.1 and 1.9.14-2. + * debian/rules +- automatically use aclocal/autoconf/automake version (Closes: #713203) +- include autoreconf.mk + * debian/control +- add Build-Depends: dh-autoreconf to use above autoreconf.mk + * debian/patches +- add delete_aclocal_flags.patch to avoid define loop in Makefile.am + + -- Hideki Yamane henr...@debian.org Thu, 06 Mar 2014 21:16:50 +0900 + +g-wrap (1.9.14-2) experimental; urgency=low + + * Build against guile-2.0: +- Build-Depends, Depends and 'configure' invocation adapted. + + -- Andreas Rottmann ro...@debian.org Tue, 05 Jun 2012 22:44:57 +0200 + g-wrap (1.9.14-1.1) unstable; urgency=low * Non-maintainer upload. diff -Nru g-wrap-1.9.14/debian/control g-wrap-1.9.14/debian/control --- g-wrap-1.9.14/debian/control2012-12-06 14:28:47.0 +0200 +++ g-wrap-1.9.14/debian/control2014-10-29 13:54:56.0 +0200 @@ -6,12 +6,12 @@ Vcs-Git: git://git.debian.org/git/collab-maint/g-wrap.git Vcs-Browser: http://git.debian.org/?p=collab-maint/g-wrap.git Standards-Version: 3.9.3 -Build-Depends: debhelper ( 8), cdbs, texinfo, automake, autoconf, - guile-1.8-dev (= 1.8.3+1), guile-library (= 0.1.1), libglib2.0-dev, libffi-dev +Build-Depends: debhelper ( 8), cdbs, texinfo, automake, autoconf, dh-autoreconf, + guile-2.0-dev (= 2.0.5), guile-library (= 0.1.1), libglib2.0-dev, libffi-dev Package: g-wrap Architecture: all -Depends: guile-1.8, guile-library (= 0.1.1), ${misc:Depends}, +Depends: guile-2.0, guile-library (= 0.1.1), ${misc:Depends}, dpkg (= 1.15.4) | install-info Recommends: indent, libgwrap-runtime-dev (= ${source:Version}) Conflicts: libgwrapguile-dev, guile-g-wrap ( 1.9.9-1) @@ -26,7 +26,7 @@ Package: libgwrap-runtime-dev Section: libdevel Architecture: any -Depends: libgwrap-runtime2 (= ${binary:Version}), guile-1.8-dev, libffi-dev, libc6-dev, ${misc:Depends} +Depends: libgwrap-runtime2 (= ${binary:Version}), guile-2.0-dev, libffi-dev, libc6-dev, ${misc:Depends} Conflicts: libgwrapguile-dev, libgwrap-runtime0-dev Replaces: libgwrapguile1 ( 1.3.4-13) Description: scripting interface generator for C - development files diff -Nru g-wrap-1.9.14/debian/gbp.conf g-wrap-1.9.14/debian/gbp.conf --- g-wrap-1.9.14/debian/gbp.conf 2012-12-06 14:28:47.0 +0200 +++ g-wrap-1.9.14/debian/gbp.conf 2014-10-29 13:54:56.0 +0200 @@ -3,4 +3,3 @@ [git-buildpackage] sign-tags = True - diff -Nru g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch --- g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch 1970-01-01 02:00:00.0 +0200 +++ g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch 2014-10-29 13:54:56.0 +0200 @@ -0,0 +1,14 @@ +Description: short summary of the patch +Author: Hideki Yamane henr...@debian.org +Forwarded: no +Last-Update: 2013-10-22 + +--- g-wrap-1.9.14.orig/Makefile.am g-wrap-1.9.14/Makefile.am +@@ -16,5 +16,5 @@ EXTRA_DIST = g-wrap.scm \ +$(wildcard $(srcdir)/m4/*.m4) \ +$(wildcard $(srcdir)/m4/*.m4-in) + +-ACLOCAL_AMFLAGS = -I m4 @ACLOCAL_FLAGS@ ++ACLOCAL_AMFLAGS = -I m4 + diff -Nru g-wrap-1.9.14/debian/patches/series g-wrap-1.9.14/debian/patches/series --- g-wrap-1.9.14/debian/patches/series 2012-12-06 14:28:47.0 +0200 +++ g-wrap-1.9.14/debian/patches/series 2014-10-29 13:54:56.0 +0200 @@ -1 +1,2 @@ 0001-Use-GUILE-instead-of-hardcoding-guile-binary-name.patch +delete_aclocal_flags.patch diff -Nru g-wrap-1.9.14/debian/README.source g-wrap-1.9.14/debian/README.source ---
Bug#769064: marked as done (unblock: g-wrap/1.9.14-2.1)
Your message dated Tue, 11 Nov 2014 07:55:13 +0100 with message-id 5461b2d1.3040...@thykier.net and subject line Re: Bug#769064: unblock: g-wrap/1.9.14-2.1 has caused the Debian Bug report #769064, regarding unblock: g-wrap/1.9.14-2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package g-wrap * Build against guile-2.0 (Closes: #761210, also refer to guile-1.8-rm transition) * Automatically use aclocal/autoconf/automake version (Closes: #713203) * Add delete_aclocal_flags.patch to avoid define loop in Makefile.am Please find the debdiff attached. unblock g-wrap/1.9.14-2.1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 diff -Nru g-wrap-1.9.14/debian/changelog g-wrap-1.9.14/debian/changelog --- g-wrap-1.9.14/debian/changelog 2012-12-06 14:28:47.0 +0200 +++ g-wrap-1.9.14/debian/changelog 2014-10-29 13:54:56.0 +0200 @@ -1,3 +1,25 @@ +g-wrap (1.9.14-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Upload to unstable (Closes: #761210). + * merge changes with 1.9.14-1.1 and 1.9.14-2. + * debian/rules +- automatically use aclocal/autoconf/automake version (Closes: #713203) +- include autoreconf.mk + * debian/control +- add Build-Depends: dh-autoreconf to use above autoreconf.mk + * debian/patches +- add delete_aclocal_flags.patch to avoid define loop in Makefile.am + + -- Hideki Yamane henr...@debian.org Thu, 06 Mar 2014 21:16:50 +0900 + +g-wrap (1.9.14-2) experimental; urgency=low + + * Build against guile-2.0: +- Build-Depends, Depends and 'configure' invocation adapted. + + -- Andreas Rottmann ro...@debian.org Tue, 05 Jun 2012 22:44:57 +0200 + g-wrap (1.9.14-1.1) unstable; urgency=low * Non-maintainer upload. diff -Nru g-wrap-1.9.14/debian/control g-wrap-1.9.14/debian/control --- g-wrap-1.9.14/debian/control2012-12-06 14:28:47.0 +0200 +++ g-wrap-1.9.14/debian/control2014-10-29 13:54:56.0 +0200 @@ -6,12 +6,12 @@ Vcs-Git: git://git.debian.org/git/collab-maint/g-wrap.git Vcs-Browser: http://git.debian.org/?p=collab-maint/g-wrap.git Standards-Version: 3.9.3 -Build-Depends: debhelper ( 8), cdbs, texinfo, automake, autoconf, - guile-1.8-dev (= 1.8.3+1), guile-library (= 0.1.1), libglib2.0-dev, libffi-dev +Build-Depends: debhelper ( 8), cdbs, texinfo, automake, autoconf, dh-autoreconf, + guile-2.0-dev (= 2.0.5), guile-library (= 0.1.1), libglib2.0-dev, libffi-dev Package: g-wrap Architecture: all -Depends: guile-1.8, guile-library (= 0.1.1), ${misc:Depends}, +Depends: guile-2.0, guile-library (= 0.1.1), ${misc:Depends}, dpkg (= 1.15.4) | install-info Recommends: indent, libgwrap-runtime-dev (= ${source:Version}) Conflicts: libgwrapguile-dev, guile-g-wrap ( 1.9.9-1) @@ -26,7 +26,7 @@ Package: libgwrap-runtime-dev Section: libdevel Architecture: any -Depends: libgwrap-runtime2 (= ${binary:Version}), guile-1.8-dev, libffi-dev, libc6-dev, ${misc:Depends} +Depends: libgwrap-runtime2 (= ${binary:Version}), guile-2.0-dev, libffi-dev, libc6-dev, ${misc:Depends} Conflicts: libgwrapguile-dev, libgwrap-runtime0-dev Replaces: libgwrapguile1 ( 1.3.4-13) Description: scripting interface generator for C - development files diff -Nru g-wrap-1.9.14/debian/gbp.conf g-wrap-1.9.14/debian/gbp.conf --- g-wrap-1.9.14/debian/gbp.conf 2012-12-06 14:28:47.0 +0200 +++ g-wrap-1.9.14/debian/gbp.conf 2014-10-29 13:54:56.0 +0200 @@ -3,4 +3,3 @@ [git-buildpackage] sign-tags = True - diff -Nru g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch --- g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch 1970-01-01 02:00:00.0 +0200 +++ g-wrap-1.9.14/debian/patches/delete_aclocal_flags.patch 2014-10-29 13:54:56.0 +0200 @@ -0,0 +1,14 @@ +Description: short summary of the
Bug#769065: unblock: fatrace/0.9-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I recently noticed (through the autopkgtest regression [1]) that fatrace's power-usage-report got broken with the latest powertop 2.6. So I made a new upstream release 0.9 which adjusts the powertop output format parsing accordingly. It's just a two line diff (complete debdiff attached, there no build system noise etc.). Both the automatic and a manual test are happy again now [2]. Thanks for considering, Martin unblock fatrace/0.9-1 [1] https://jenkins.qa.ubuntu.com/job/vivid-adt-fatrace/2/ARCH=i386,label=adt/console [2] https://jenkins.qa.ubuntu.com/job/vivid-adt-fatrace/3/ARCH=i386,label=adt/console -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru fatrace-0.8/debian/changelog fatrace-0.9/debian/changelog --- fatrace-0.8/debian/changelog2014-09-23 16:07:44.0 +0200 +++ fatrace-0.9/debian/changelog2014-11-07 09:19:03.0 +0100 @@ -1,3 +1,10 @@ +fatrace (0.9-1) unstable; urgency=medium + + * New upstream release: +- power-usage-report: Adjust parsing to also work for powertop 2.6. + + -- Martin Pitt mp...@debian.org Fri, 07 Nov 2014 09:18:56 +0100 + fatrace (0.8-1) unstable; urgency=medium * New upstream bug fix release: Fix the Value too large for defined data diff -Nru fatrace-0.8/NEWS fatrace-0.9/NEWS --- fatrace-0.8/NEWS2014-09-23 15:56:19.0 +0200 +++ fatrace-0.9/NEWS2014-11-07 09:17:24.0 +0100 @@ -1,3 +1,7 @@ +0.9 (2014-11-07) + + - power-usage-report: Adjust parsing to also work for powertop 2.6. + 0.8 (2014-09-23) - The previous O_LARGEFILE change to fix Value too large for defined data diff -Nru fatrace-0.8/power-usage-report fatrace-0.9/power-usage-report --- fatrace-0.8/power-usage-report 2014-09-23 15:56:19.0 +0200 +++ fatrace-0.9/power-usage-report 2014-11-07 09:17:24.0 +0100 @@ -166,7 +166,7 @@ for (search_header, print_header) in blocks: # skip until search_header -while i len(lines) and not lines[i].lower().startswith('**' + search_header): +while i len(lines) and not search_header in lines[i].lower(): i += 1 i += 1 # skip header # skip empty lines @@ -174,7 +174,7 @@ i += 1 print('== %s ==' % print_header) -while i len(lines) and lines[i]: +while i len(lines) and lines[i] and not lines[i].startswith('_'): print(lines[i]) i += 1 print('') signature.asc Description: Digital signature
Bug#768071: marked as done (unblock: docker.io/1.3.1~dfsg1-2)
Your message dated Tue, 11 Nov 2014 08:07:13 +0100 with message-id 5461b5a1.4040...@thykier.net and subject line Re: Bug#768071: unblock: docker.io/1.3.1~dfsg1-1 has caused the Debian Bug report #768071, regarding unblock: docker.io/1.3.1~dfsg1-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package docker.io. This is a new upstream backport release with security (including CVE-2014-5277[1]) and minor functionality fixes on top of 1.3.0, especially in the Dockerfile parser relating to environment variable substitution[2]. Attached is the output of: | debdiff docker.io_1.3.0~dfsg1-1.dsc docker.io_1.3.1~dfsg1-1.dsc docker.io_1.3.1.debdiff (from the version in Jessie to the version now in Sid) unblock docker.io/1.3.1~dfsg1-1 ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 [1]: https://groups.google.com/d/topic/docker-user/oYm0i3xShJU/discussion [2]: https://github.com/docker/docker/blob/v1.3.1/CHANGELOG.md#131-2014-10-28 diff -Nru docker.io-1.3.0~dfsg1/CHANGELOG.md docker.io-1.3.1~dfsg1/CHANGELOG.md --- docker.io-1.3.0~dfsg1/CHANGELOG.md 2014-10-15 19:15:24.0 + +++ docker.io-1.3.1~dfsg1/CHANGELOG.md 2014-10-30 13:44:46.0 + @@ -1,5 +1,23 @@ # Changelog +## 1.3.1 (2014-10-28) + + Security +* Prevent fallback to SSL protocols TLS 1.0 for client, daemon and registry ++ Secure HTTPS connection to registries with certificate verification and without HTTP fallback unless `--insecure-registry` is specified + + Runtime +- Fix issue where volumes would not be shared + + Client +- Fix issue with `--iptables=false` not automatically setting `--ip-masq=false` +- Fix docker run output to non-TTY stdout + + Builder +- Fix escaping `$` for environment variables +- Fix issue with lowercase `onbuild` Dockerfile instruction +- Restrict envrionment variable expansion to `ENV`, `ADD`, `COPY`, `WORKDIR`, `EXPOSE`, `VOLUME` and `USER` + ## 1.3.0 (2014-10-14) Notable features since 1.2.0 diff -Nru docker.io-1.3.0~dfsg1/VERSION docker.io-1.3.1~dfsg1/VERSION --- docker.io-1.3.0~dfsg1/VERSION 2014-10-15 19:15:24.0 + +++ docker.io-1.3.1~dfsg1/VERSION 2014-10-30 13:44:46.0 + @@ -1 +1 @@ -1.3.0 +1.3.1 diff -Nru docker.io-1.3.0~dfsg1/api/client/commands.go docker.io-1.3.1~dfsg1/api/client/commands.go --- docker.io-1.3.0~dfsg1/api/client/commands.go2014-10-15 19:15:24.0 + +++ docker.io-1.3.1~dfsg1/api/client/commands.go2014-10-30 13:44:46.0 + @@ -1986,6 +1986,10 @@ } func (cli *DockerCli) pullImage(image string) error { + return cli.pullImageCustomOut(image, cli.out) +} + +func (cli *DockerCli) pullImageCustomOut(image string, out io.Writer) error { v := url.Values{} repos, tag := parsers.ParseRepositoryTag(image) // pull only the image tagged 'latest' if no tag was specified @@ -2014,7 +2018,7 @@ registryAuthHeader := []string{ base64.URLEncoding.EncodeToString(buf), } - if err = cli.stream(POST, /images/create?+v.Encode(), nil, cli.out, map[string][]string{X-Registry-Auth: registryAuthHeader}); err != nil { + if err = cli.stream(POST, /images/create?+v.Encode(), nil, out, map[string][]string{X-Registry-Auth: registryAuthHeader}); err != nil { return err } return nil @@ -2081,7 +2085,8 @@ if statusCode == 404 { fmt.Fprintf(cli.err, Unable to find image '%s' locally\n, config.Image) - if err = cli.pullImage(config.Image); err != nil { + // we don't want to write to stdout anything apart from container.ID + if err = cli.pullImageCustomOut(config.Image, cli.err); err != nil { return nil, err } // Retry diff -Nru docker.io-1.3.0~dfsg1/api/server/server.go docker.io-1.3.1~dfsg1/api/server/server.go --- docker.io-1.3.0~dfsg1/api/server/server.go 2014-10-15 19:15:24.0 + +++ docker.io-1.3.1~dfsg1/api/server/server.go 2014-10-30 13:44:46.0 + @@ -1439,6 +1439,8 @@ tlsConfig := tls.Config{ NextProtos: []string{http/1.1}, Certificates: []tls.Certificate{cert}, + // Avoid fallback on
Bug#769065: marked as done (unblock: fatrace/0.9-1)
Your message dated Tue, 11 Nov 2014 08:09:14 +0100 with message-id 5461b61a.20...@thykier.net and subject line Re: Bug#769065: unblock: fatrace/0.9-1 has caused the Debian Bug report #769065, regarding unblock: fatrace/0.9-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I recently noticed (through the autopkgtest regression [1]) that fatrace's power-usage-report got broken with the latest powertop 2.6. So I made a new upstream release 0.9 which adjusts the powertop output format parsing accordingly. It's just a two line diff (complete debdiff attached, there no build system noise etc.). Both the automatic and a manual test are happy again now [2]. Thanks for considering, Martin unblock fatrace/0.9-1 [1] https://jenkins.qa.ubuntu.com/job/vivid-adt-fatrace/2/ARCH=i386,label=adt/console [2] https://jenkins.qa.ubuntu.com/job/vivid-adt-fatrace/3/ARCH=i386,label=adt/console -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru fatrace-0.8/debian/changelog fatrace-0.9/debian/changelog --- fatrace-0.8/debian/changelog2014-09-23 16:07:44.0 +0200 +++ fatrace-0.9/debian/changelog2014-11-07 09:19:03.0 +0100 @@ -1,3 +1,10 @@ +fatrace (0.9-1) unstable; urgency=medium + + * New upstream release: +- power-usage-report: Adjust parsing to also work for powertop 2.6. + + -- Martin Pitt mp...@debian.org Fri, 07 Nov 2014 09:18:56 +0100 + fatrace (0.8-1) unstable; urgency=medium * New upstream bug fix release: Fix the Value too large for defined data diff -Nru fatrace-0.8/NEWS fatrace-0.9/NEWS --- fatrace-0.8/NEWS2014-09-23 15:56:19.0 +0200 +++ fatrace-0.9/NEWS2014-11-07 09:17:24.0 +0100 @@ -1,3 +1,7 @@ +0.9 (2014-11-07) + + - power-usage-report: Adjust parsing to also work for powertop 2.6. + 0.8 (2014-09-23) - The previous O_LARGEFILE change to fix Value too large for defined data diff -Nru fatrace-0.8/power-usage-report fatrace-0.9/power-usage-report --- fatrace-0.8/power-usage-report 2014-09-23 15:56:19.0 +0200 +++ fatrace-0.9/power-usage-report 2014-11-07 09:17:24.0 +0100 @@ -166,7 +166,7 @@ for (search_header, print_header) in blocks: # skip until search_header -while i len(lines) and not lines[i].lower().startswith('**' + search_header): +while i len(lines) and not search_header in lines[i].lower(): i += 1 i += 1 # skip header # skip empty lines @@ -174,7 +174,7 @@ i += 1 print('== %s ==' % print_header) -while i len(lines) and lines[i]: +while i len(lines) and lines[i] and not lines[i].startswith('_'): print(lines[i]) i += 1 print('') signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On 2014-11-11 08:04, Martin Pitt wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I recently noticed (through the autopkgtest regression [1]) that fatrace's power-usage-report got broken with the latest powertop 2.6. So I made a new upstream release 0.9 which adjusts the powertop output format parsing accordingly. It's just a two line diff (complete debdiff attached, there no build system noise etc.). Both the automatic and a manual test are happy again now [2]. Thanks for considering, Martin unblock fatrace/0.9-1 [...] Unblocked, thanks. And thanks for keeping the diff minimal. :) ~Niels---End Message---
Bug#769043: marked as done (unblock: xserver-xorg-video-geode/2.11.16-5)
Your message dated Tue, 11 Nov 2014 08:12:00 +0100 with message-id 5461b6c0.2040...@thykier.net and subject line Re: Bug#769043: unblock: xserver-xorg-video-geode/2.11.16-5 has caused the Debian Bug report #769043, regarding unblock: xserver-xorg-video-geode/2.11.16-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package xserver-xorg-video-geode 2.11.16-4 mistakenly dropped a (Provides: xorg-driver-video). Without it, on hosts without any other X.Org video driver installed, this results in an APT decision to remove the whole X.Org stack and most desktop applications. debdiff (minus changelog.dch, which somehow shipped with 2.11.16-4 unnoticed): diff -Nru xserver-xorg-video-geode-2.11.16/debian/changelog xserver-xorg-video-geode-2.11.16/debian/changelog --- xserver-xorg-video-geode-2.11.16/debian/changelog 2014-09-14 13:41:27.0 +0300 +++ xserver-xorg-video-geode-2.11.16/debian/changelog 2014-11-11 01:12:48.0 +0200 @@ -1,3 +1,12 @@ +xserver-xorg-video-geode (2.11.16-5) unstable; urgency=medium + + * debian/control: ++ Provides: xorg-driver-video + This reverses part of the previous changes. Without this, APT uninstalls + the whole X.Org if no other video driver is installed (Closes: #769042). + + -- Martin-Éric Racine martin-eric.rac...@iki.fi Tue, 11 Nov 2014 01:07:59 +0200 + xserver-xorg-video-geode (2.11.16-4) unstable; urgency=medium * debian/control,debian/rules; Gotten one step closer to XSF: diff -Nru xserver-xorg-video-geode-2.11.16/debian/control xserver-xorg-video-geode-2.11.16/debian/control --- xserver-xorg-video-geode-2.11.16/debian/control 2014-09-14 14:00:15.0 +0300 +++ xserver-xorg-video-geode-2.11.16/debian/control 2014-11-11 00:33:21.0 +0200 @@ -23,7 +23,8 @@ Depends: ${misc:Depends}, ${shlibs:Depends}, ${xviddriver:Depends} -Provides: xserver-xorg-video-amd, +Provides: xorg-driver-video, + xserver-xorg-video-amd, ${xviddriver:Provides} Breaks: xserver-xorg-video-amd ( ${binary:Version}) Description: X.Org X server -- Geode GX2/LX display driver unblock xserver-xorg-video-geode/2.11.16-5 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (1001, 'testing'), (1001, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On 2014-11-11 00:17, Martin-Éric Racine wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package xserver-xorg-video-geode 2.11.16-4 mistakenly dropped a (Provides: xorg-driver-video). Without it, on hosts without any other X.Org video driver installed, this results in an APT decision to remove the whole X.Org stack and most desktop applications. debdiff (minus changelog.dch, which somehow shipped with 2.11.16-4 unnoticed): [...[ Unblocked, thanks. ~Niels---End Message---
Bug#768872: marked as done (unblock: ruby-patron/0.4.18-2)
Your message dated Tue, 11 Nov 2014 08:16:49 +0100 with message-id 2014071649.GA30041@sx.local and subject line unblock: ruby-patron/0.4.18-2 has caused the Debian Bug report #768872, regarding unblock: ruby-patron/0.4.18-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, I realise you'll likely laugh and send me away, but still... ruby-patron has not been in jessie for a very long time, and to be completely honest, I don't care about this package at all. Unfortunately ruby-elasticsearch recently made it into testing and depends on ruby-patron. Apparently the cloud guys are quite happy about the elasticsearch thing being in testing, and it'd suck for them if ruby-elasticsearch would have to be removed again (or something). ruby-patron's issue are random build failures (SEGV in ruby) that are hard to diagnose/reproduce -- I've never been able to reproduce the build failures, [1] claims other people tried too and failed. Debdiff 0.4.18-1 (the version that was in testing some time ago) and 0.4.18-2 (in sid) attached. (-2 fixed #744034) So ... please unblock ruby-patron., unblock ruby-patron/0.4.18-2 Thank you, Christian [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744813#15 ---End Message--- ---BeginMessage--- Withdrawing this, as there's now an unblock request for ruby-elasticsearch removing the B-D on ruby-patron. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpzejhGk9V3R.pgp Description: PGP signature ---End Message---