bootlogd logging to multiple console devices: patch in Debian 7 (Wheezy)
Dear release team, On the 24th of August, I uploaded to unstable a fix for #181756 to unstable. So far, nobody complained about it. I would like to also fix the Wheezy version of bootlogd, through the proposed-updates. The proposed patch is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=51;filename=allow-multiple-console-output.patch;att=1;bug=181756 This patch is important for anyone that uses a server and wants to activate the serial console, while keeping tty0 working. This is also important when using a Debian image on the cloud: for example, using OpenStack, by default, it expects that logging to both tty0 and ttyS0, otherwise either the nova log or the interactive physical console through the web interface is broken (depending which console option you put in the kernel command line). Note that using console=/dev/console didn't work for me, only console=/dev/tty0 console=ttyS0,115200 with the above bootlogd patch worked. What is the opinion of the release team? Does it seem reasonable to include this patch in the next point release of Wheezy? 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/544f35ee.80...@debian.org
Bug#757539: Debian: apertium language pairs broken in jessie due to pcre3 update
On Tue, Oct 28, 2014 at 10:13:16 +0800, Paul Wise wrote: On Wed, 2014-08-13 at 09:29 +0800, Paul Wise wrote: I don't think a proper fix is going to happen before the freeze so can we have the binNMUs so that apertium works in jessie? So it is now too late to easily fix this issue for jessie. In addition some language pairs got removed due to RC bugs being filed and the automatic removal process removing them. There are three ways forward: Have Kartik/Francis/Tino upload the latest upstream code and language pairs to unstable and unblock them for jessie. This seems unlikely. binNMU all of the relevant language pairs as initially requested, close the relevant RC bugs and unblock the binNMUed and removed packages. Remove apertium related packages from jessie entirely. It is fairly pointless to have apertium in Debian without working language pairs. Any thoughts from the Debian release team? I'm scheduling the binNMUs now, but I'd rather keep an RC bug open against apertium (and possibly tag it jessie-ignore). Cheers, Julien signature.asc Description: Digital signature
Bug#767061: unblock: lyx/2.1.2-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package lyx The changes are mainly cleanups and lintian issues. lyx (2.1.2-3) unstable; urgency=low * Bumped up Standards version to 3.9.6 (no changes needed) * Add support for upstream GPG signature tarball check * Update copyright file and convert to machine-readable format * Specify NEWS as the upstream changelog to be included in the binary packages * Mark fonts-lyx binary package as Multi-Arch: foreign * Add a lintian override for lyx-common's link to external mythes directory * Add a patch that populates .desktop file with a Keywords field * Fix permissions for some scripts -- Nick Andrik nick.and...@gmail.com Sun, 12 Oct 2014 01:13:52 +0200 I'm very sorry that I missed the deadline for automatic migrations due to my vacation, but a helpful contributor to the LyX package provided some valuable cleanups I'd like to see in jessie while I was absent. unblock lyx/2.1.2-3 -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-0.bpo.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 -- 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/20141028082320.6241.82361.reportbug@shoexter.internal
Re: bootlogd logging to multiple console devices: patch in Debian 7 (Wheezy)
Hi Thomas, Thomas Goirand z...@debian.org (2014-10-28): What is the opinion of the release team? Does it seem reasonable to include this patch in the next point release of Wheezy? This should be tracked as a pu bug report, instead of being possibly lost in the debian-release@ traffic. Mraw, KiBi. signature.asc Description: Digital signature
Bug#767063: unblock: claws-mail/3.11.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package claws-mail This is a bugfix release to complete removal of SSLv3 usage in all protocols and broken appdata added in 3.11.0 mainly. There's no Debian bugs reported yet (3.11.0 happened last week). Further details: http://git.claws-mail.org/?p=claws.git;f=RELEASE_NOTES;hb=refs/tags/3.11.1 Thanks in advance, unblock claws-mail/3.11.1-1 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-7-g56678ec (PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.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/20141028083630.8026.87000.reportbug@trasgu
Bug#757539: Debian: apertium language pairs broken in jessie due to pcre3 update
On 28 October 2014 03:13, Paul Wise p...@debian.org wrote: On Wed, 2014-08-13 at 09:29 +0800, Paul Wise wrote: I don't think a proper fix is going to happen before the freeze so can we have the binNMUs so that apertium works in jessie? Have Kartik/Francis/Tino upload the latest upstream code and language pairs to unstable and unblock them for jessie. This seems unlikely. And here I was sure that the whole PCRE thing was taken care of, but then I double-checked, and I had only taken care of it for the nightly builds. The Debian-Science git repos for apertium and lttoolbox are now updated with the patches that work around the PCRE issues: http://anonscm.debian.org/cgit/debian-science/packages/apertium.git http://anonscm.debian.org/cgit/debian-science/packages/lttoolbox.git -- Tino Didriksen
Bug#767069: apertium: breaks after incompatible pcre3 updates
Package: apertium Severity: serious Version: 3.1.0-2 X-Debbugs-CC: debian-release@lists.debian.org, kar...@debian.org, fty...@prompsit.com, apertium-st...@lists.sourceforge.net, debian-scie...@lists.debian.org This is an RC bug requested by the release team in #757539. The recent pcre3 update has caused apertium to start segfaulting because the language data packages need to be rebuilt after pcre3 updates as they store only pcre3 regex bytecode and not original regexes. The segfaults occur when old bytecode is used with newer pcre3. This bug is fixed in the Debian science git repos and soon in experimental. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#757539: Debian: apertium language pairs broken in jessie due to pcre3 update
On Tue, 2014-10-28 at 08:59 +0100, Julien Cristau wrote: I'm scheduling the binNMUs now, but I'd rather keep an RC bug open against apertium (and possibly tag it jessie-ignore). Great, thanks. Filed #767069, please tag it jessie-ignore as it is unlikely pcre3 will change incompatibly during the freeze :) Please also unblock apertium-en-es and close #761087 after the binNMU. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#757539: Debian: apertium language pairs broken in jessie due to pcre3 update
On Tue, 2014-10-28 at 09:39 +0100, Tino Didriksen wrote: The Debian-Science git repos for apertium and lttoolbox are now updated with the patches that work around the PCRE issues: Thanks, please close #767069 in the changelog too. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#767074: unblock: taurus/3.3.1+dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package taurus Hello, me and the upstream of taurus worked last week to prepare a release of taurus specifically for debian8. this is mostly a bug fix. (the usual relase cycle of taurus and sardana is two per years, january and july). due to a lake of time and even with their week-end we missed the window for one day. They take all the week to prepare and test the new taurus. so I am confidant thaht it is better to have this version in Debian 8 instead of the current one. Would you be kind to unblock the package. I do not put the debdiff because this is a new release instead of a bug fix from the maintainer. If you have other questions do not hesitate to contact me. thanks Frederic unblock taurus/3.3.1+dfsg-1 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16-2-486 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (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/20141028093655.4196.92282.reportbug@mordor
Bug#767077: unblock: sardana/1.4.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package sardana Hello, first this unblock depends of this other unblock bug #767074. with the same reasons than taurus. but sardana depends of the latests taurus package. so it would be nice if you could unblock also this package. this mostly a bug fix from the upstream for Debian Jessie. no debdiff, this is a new upstream bug fix. to be fair the upstream source package contain a dirty directory containing some documentation pre=built (sphinx) which is removed in dh_clean. The upstream is aware of this and will fix the problem for the next upload (Debian 9). thanks for your willingness unblock sardana/1.4.2-1 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16-2-486 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (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/20141028094813.4326.4100.reportbug@mordor
Bug#757539: marked as done (nmu: apertium language packages due to pcre3 update)
Your message dated Tue, 28 Oct 2014 10:59:52 +0100 with message-id 20141028095952.gd3...@betterave.cristau.org and subject line Re: Bug#757539: Debian: apertium language pairs broken in jessie due to pcre3 update has caused the Debian Bug report #757539, regarding nmu: apertium language packages due to pcre3 update to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 757539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757539 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: binnmu X-Debbugs-Cc: Kartik Mistry kar...@debian.org The recent pcre3 update has caused apertium to start segfaulting because the language data packages need to be rebuilt after pcre3 updates. apertium-es-ca was already rebuilt manually with an NMU. Please binNMU the rest, wanna-build commands below (hope I didn't get them wrong). https://bugs.debian.org/726590 https://packages.qa.debian.org/a/apertium-es-ca/news/20140712T171843Z.html nmu apertium-en-ca_0.8.9-1+b1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-en-es_0.6.0-1.1+b1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-eo-ca_0.9.0-1.1+b1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-eo-es_0.9.0-1.1+b1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-es-gl_1.0.7-1. ALL . -m Rebuilding against new libpcre3 nmu apertium-es-pt_1.0.3-2.1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-es-ro_0.7.1-2.1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-eu-es_0.3.1-1+b1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-fr-ca_1.0.2-1. ALL . -m Rebuilding against new libpcre3 nmu apertium-fr-es_0.9.0-1+b1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-oc-ca_1.0.5-1.1+b1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-oc-es_1.0.5-1.1+b1 . ALL . -m Rebuilding against new libpcre3 nmu apertium-pt-ca_0.8.1-1. ALL . -m Rebuilding against new libpcre3 nmu apertium-pt-gl_0.9.1-1. ALL . -m Rebuilding against new libpcre3 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- On Tue, Oct 28, 2014 at 17:22:46 +0800, Paul Wise wrote: On Tue, 2014-10-28 at 08:59 +0100, Julien Cristau wrote: I'm scheduling the binNMUs now, but I'd rather keep an RC bug open against apertium (and possibly tag it jessie-ignore). Great, thanks. Filed #767069, please tag it jessie-ignore as it is unlikely pcre3 will change incompatibly during the freeze :) Please also unblock apertium-en-es and close #761087 after the binNMU. Okay. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#767085: unblock: pcl/1.7.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please reduce the 10-day age period to 9 (or less) of this package. Let me explain the situation: We have worked hard with a big package: pcl. The package goes to new queue on June (2014-06-10). It was about 4 months. - It was rejected because problems in the copyright file. (2014-10-03) - Upstream in the middle releases a new version. (2014-09-10) - We worked with the new version and I asked my sponsor to upload it on Wednesday. (2014-10-15) - My sponsor upload it on Wednesday (2014-10-22) and ftp-masters upload it to unstable on Friday. (2014-10-24) - The same day, a few hours after to be in unstable, someone filled a Important bug of one binary package #766685: libpcl-dev - A few hours after I prepare a new version of the package solving the bug and I uploaded to mentors the new package, commented the bug and asked to my sponsor to upload the package (2014-10-25). However, I made a mistake and I put UNRELEASED so my sponsor rejects to upload it. - On Sunday morning (2014-10-26 Morning (UTC)) I asked to my sponsor to upload the new version, thinking that the period to have a package in testing before November 5th ended Sunday 26th 23:55 (UTC) (November 5th - 10 days). My sponsor upload it this morning 5:57, day 27th. I don't know if someone will fill any bug against the package before November 5th. I hope that no. But, we are not in time to be in testing before freeze because 6 hours... so it won't be in Jessie. Please, could you reduced the 10-day delay? Thanks in advance. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (600, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (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/20141028111049.11036.55765.report...@soho.upc.es
Bug#767082: unblock: exifprobe/2.0.1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package exifprobe. The package was orphan and I did a QA upload on 2014-08-24. Yesterday I adopted (under the Forensics Team) and uploaded the package to Sid. I Solved all bugs (4 bugs) and Lintian warnings (15 messages). The changelog is here[1]. The package is useful in forensics activities, is clean and working fine. I believe that is a good idea have this package in Jessie and I need a reduction of the migration time to 8 days. This will be my last request of reduction. I no need this for other packages. Thanks in advance. Regards, Eriberto unblock exifprobe/2.0.1-3 [1] http://metadata.ftp-master.debian.org/changelogs/main/e/exifprobe/unstable_changelog -- 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/20141028110045.26150.85733.report...@libra.gabcmt.eb.mil.br
Bug#767074: unblock: taurus/3.3.1+dfsg-1
Control: tags -1 + moreinfo Hi, Picca Frédéric-Emmanuel wrote (28 Oct 2014 09:36:55 GMT) : Hello, me and the upstream of taurus worked last week to prepare a release of taurus specifically for debian8. this is mostly a bug fix. My understanding is that you would like the release team to unblock this package without looking at the actual (debdiff) data. I doubt it'll work, but I'm pretty sure that it won't work unless they're given at least basic information about the proposed changes. Sadly, the last Debian upload doesn't close any bug, the 3.3.1 release isn't announced on the upstream website, and I could not find any upstream changelog in the Debian source tree. So, please point to the relevant bug reports closed by 3.3.1, that might help convincing the release team that accepting this last-minute upstream release is worth it. Thanks! 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/85tx2o8lx8@boum.org
Processed: Re: Bug#767074: unblock: taurus/3.3.1+dfsg-1
Processing control commands: tags -1 + moreinfo Bug #767074 [release.debian.org] unblock: taurus/3.3.1+dfsg-1 Added tag(s) moreinfo. -- 767074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767074 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.b767074.141449627413095.transcr...@bugs.debian.org
Processed: block 767077 with 767074
Processing commands for cont...@bugs.debian.org: block 767077 with 767074 Bug #767077 [release.debian.org] unblock: sardana/1.4.2-1 767077 was not blocked by any bugs. 767077 was not blocking any bugs. Added blocking bug(s) of 767077: 767074 thanks Stopping processing here. Please contact me if you need assistance. -- 767077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767077 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.141449642514909.transcr...@bugs.debian.org
A small thanks to the kFreeBSD porters
I would like to share a good experience I had with the kFreeBSD porter team. On Sunday afternoon I foolishly uploaded a package which, if I had thought about it, I ought to have known would FTBFS on FreeBSD. Less than 4 hours later I had a bug report (#766913) from Steven Chamberlain, who had triaged the bug and correctly diagnosed it. While fixing the bug on a porterbox I got very helpful IRC support from Christoph Egger, who gave advice about BSD the relevant userland and kernel APIs and #defines and also helped me by checking that apparently-to-me-working acctdump program actually produced plausible output when fed a real BSD process accounting file. Thanks, Ian. -- 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/21583.36298.379484.540...@chiark.greenend.org.uk
Bug#767074: unblock: taurus/3.3.1+dfsg-1
thanks for the review So, please point to the relevant bug reports closed by 3.3.1, that might help convincing the release team that accepting this last-minute upstream release is worth it. Thanks! here the information from the mailing list http://sourceforge.net/p/sardana/mailman/message/32974642/ Release of sardana 1.4.1 and taurus 3.3.1 (Debian 8 Jessie). The main improvements in Sardana since 1.4.0 (aka Jul14) are: * add features: 231, 250 * fix bugs: 251 * dscanc return to start position The main improvements in Taurus since 3.3.0 (aka Jul14) are: * fix bugs: 234, 135, 208, 211, 210, 221, 222, 217, 224 * Add support for color video encoded images in Taurus Image Other minor changes We have also evaluated other pending patches but due their complexity or lower priority we have postponed their integration. These were, among others: feat-131, feat-233, bug-242, feat-155, bug-207, spock logging macros, add new view options. you can find the tickets here http://sourceforge.net/p/sardana/tickets/ cheers Frederic -- 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/a2a20ec3b8560d408356cac2fc148e53b1fbb...@sun-dag3.synchrotron-soleil.fr
Bug#767116: unblock: vagrant/1.6.5+dfsg1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package vagrant, or age it in a way that it reaches
jessie in time for the freeze provided there are no other issues with
it.
This version fixes an RC bug which makes it impossible to download OS
images over HTTP (which mainly breaks central use cases of the tool).
Attached:
- vagrant.diff: full debdiff against the version currently in jessie
- 0008-Use-a-private-temporary-dir.patch: the larger patch included with
this version so you don't have to read a diff-inside-diff.
unblock vagrant/1.6.5+dfsg1-2
-- System Information:
Debian Release: jessie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Antonio Terceiro terce...@debian.org
diff -Nru vagrant-1.6.5+dfsg1/debian/changelog vagrant-1.6.5+dfsg1/debian/changelog
--- vagrant-1.6.5+dfsg1/debian/changelog 2014-10-12 16:48:53.0 -0300
+++ vagrant-1.6.5+dfsg1/debian/changelog 2014-10-28 12:16:13.0 -0200
@@ -1,3 +1,13 @@
+vagrant (1.6.5+dfsg1-2) unstable; urgency=medium
+
+ * debian/patches/0008-Use-a-private-temporary-dir.patch: create temporary
+files inside a private temporary directory instead of cluttering $TMPDIR.
+ * debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch:
+updated, remove trailing newline from version number (Closes: #765074)
+- Thanks Etienne Millon m...@emillon.org
+
+ -- Antonio Terceiro terce...@debian.org Tue, 28 Oct 2014 12:12:27 -0200
+
vagrant (1.6.5+dfsg1-1) unstable; urgency=medium
[ Antonio Terceiro ]
diff -Nru vagrant-1.6.5+dfsg1/debian/patches/0001-Constrain-dependency-resolution.patch vagrant-1.6.5+dfsg1/debian/patches/0001-Constrain-dependency-resolution.patch
--- vagrant-1.6.5+dfsg1/debian/patches/0001-Constrain-dependency-resolution.patch 2014-10-12 16:48:53.0 -0300
+++ vagrant-1.6.5+dfsg1/debian/patches/0001-Constrain-dependency-resolution.patch 2014-10-28 12:16:13.0 -0200
@@ -1,7 +1,6 @@
-From f8bcc4e98d2476a44425bc9b2d0f9c077444bfda Mon Sep 17 00:00:00 2001
From: Antonio Terceiro terce...@debian.org
Date: Sat, 11 Oct 2014 16:46:32 -0300
-Subject: [PATCH 1/7] Constrain dependency resolution
+Subject: Constrain dependency resolution
---
Gemfile | 6 --
@@ -63,6 +62,3 @@
# The following block of code determines the files that should be included
# in the gem. It does this by reading all the files in the directory where
---
-2.1.1
-
diff -Nru vagrant-1.6.5+dfsg1/debian/patches/0002-Disable-Checkpoint.patch vagrant-1.6.5+dfsg1/debian/patches/0002-Disable-Checkpoint.patch
--- vagrant-1.6.5+dfsg1/debian/patches/0002-Disable-Checkpoint.patch 2014-10-12 16:48:53.0 -0300
+++ vagrant-1.6.5+dfsg1/debian/patches/0002-Disable-Checkpoint.patch 2014-10-28 12:16:13.0 -0200
@@ -1,7 +1,6 @@
-From b8279f909656ad977dc54aec9c312b7578d7bec9 Mon Sep 17 00:00:00 2001
From: Antonio Terceiro terce...@debian.org
Date: Sat, 11 Oct 2014 16:48:07 -0300
-Subject: [PATCH 2/7] Disable Checkpoint
+Subject: Disable Checkpoint
We don't want vagrant phoning home all the time
---
@@ -72,6 +71,3 @@
end
# Makes a call to the CLI with the given arguments as if they
---
-2.1.1
-
diff -Nru vagrant-1.6.5+dfsg1/debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch vagrant-1.6.5+dfsg1/debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch
--- vagrant-1.6.5+dfsg1/debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch 2014-10-12 16:48:53.0 -0300
+++ vagrant-1.6.5+dfsg1/debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch 2014-10-28 12:16:13.0 -0200
@@ -1,14 +1,13 @@
-From 20131cc976e97b5d64dd1304a5f334a4098b066c Mon Sep 17 00:00:00 2001
From: Antonio Terceiro terce...@debian.org
Date: Sat, 11 Oct 2014 16:54:26 -0300
-Subject: [PATCH 3/7] VERSION: fallback to /usr/share/vagrant/version.txt
+Subject: VERSION: fallback to /usr/share/vagrant/version.txt
---
lib/vagrant/version.rb | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/lib/vagrant/version.rb b/lib/vagrant/version.rb
-index 0640365..22f6188 100644
+index 0640365..e8d35c3 100644
--- a/lib/vagrant/version.rb
+++ b/lib/vagrant/version.rb
@@ -2,6 +2,10 @@ module Vagrant
@@ -21,9 +20,6 @@
+VERSION = File.read(
+ File.expand_path(../../../version.txt, __FILE__)).chomp
+ rescue Errno::ENOENT
-+VERSION = File.read('/usr/share/vagrant/version.txt')
++VERSION = File.read('/usr/share/vagrant/version.txt').chomp
+ end
end
---
-2.1.1
-
diff -Nru vagrant-1.6.5+dfsg1/debian/patches/0004-bin-vagrant-silence-warning-about-installer.patch
Bug#767118: unblock: sympow/1.023-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock The sympow package, which had not been updated since 2008-08-14, contains numerical fixes from the upstream maintainer himself and some major improvements regarding its linux integration part recently brought by myself. Because some intricate arch-indep data must be precomputed, the binary-indep deb ball could not build properly on some architectures (as sparc) due to a too long computing time: the issue was finally resolved by implementing a arch/indep scheme and now it can build for all architectures. Neverthless this last resolving process brought a sequence of FTBFS bugs. After all this efforts, the buildable version of the package was finally uploaded only a few hours after the the freeze time minus the 10-day age period. Hence the request to reduce its current transition period to 5 days in such a way the interesting audience can enjoy the updated version of sympow within Jessie. Please could the transition period for sympow/1.023-5 be reduced to 5 days. Thanks, Jerome unblock sympow/1.023-5 -- System Information: Debian Release: Wheezy* APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.10-amd64-mbp62 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (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/20141028145647.7070.71159.report...@nen.dnsalias.org
Bug#767122: unblock: ruby-sass-rails/4.0.3-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ruby-sass-rails, or better, age it in a way that it can get into jessie before the freeze. A recent upload of ruby-sass (not maintained by the Ruby team, so not really under our control) revealed that the dependency specification in ruby-sass-rails was too strict. This caused the rails test suite to fail on CI, what brought the issue to my attention: http://ci.debian.net/data/packages/unstable/amd64/r/rails/20141028_031245.autopkgtest.log Attached you will find a debdiff agains the package in jessie, which is quite simple and fixes the default Rails stack. unblock ruby-sass-rails/4.0.3-2 -- System Information: Debian Release: jessie/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Antonio Terceiro terce...@debian.org diff -Nru ruby-sass-rails-4.0.3/debian/changelog ruby-sass-rails-4.0.3/debian/changelog --- ruby-sass-rails-4.0.3/debian/changelog 2014-08-03 00:06:42.0 -0300 +++ ruby-sass-rails-4.0.3/debian/changelog 2014-10-28 13:10:04.0 -0200 @@ -1,3 +1,11 @@ +ruby-sass-rails (4.0.3-2) unstable; urgency=medium + + * Team upload + * debian/patches/sprockets-2.x.patch: amend change to metadata.yml to relax +dependency on sass-rails. + + -- Antonio Terceiro terce...@debian.org Tue, 28 Oct 2014 13:09:58 -0200 + ruby-sass-rails (4.0.3-1) unstable; urgency=medium * Team upload diff -Nru ruby-sass-rails-4.0.3/debian/patches/sprockets-2.x.patch ruby-sass-rails-4.0.3/debian/patches/sprockets-2.x.patch --- ruby-sass-rails-4.0.3/debian/patches/sprockets-2.x.patch 2014-07-27 16:17:23.0 -0300 +++ ruby-sass-rails-4.0.3/debian/patches/sprockets-2.x.patch 2014-10-28 13:10:04.0 -0200 @@ -307,6 +307,23 @@ end --- a/metadata.yml +++ b/metadata.yml +@@ -17,14 +17,14 @@ dependencies: + requirements: + - - ~ + - !ruby/object:Gem::Version +-version: 3.2.0 ++version: '3.2' + type: :runtime + prerelease: false + version_requirements: !ruby/object:Gem::Requirement + requirements: + - - ~ + - !ruby/object:Gem::Version +-version: 3.2.0 ++version: '3.2' + - !ruby/object:Gem::Dependency + name: railties + requirement: !ruby/object:Gem::Requirement @@ -65,20 +65,14 @@ dependencies: requirements: - - ~ signature.asc Description: Digital signature
Processed: tagging 767074
Processing commands for cont...@bugs.debian.org: tags 767074 - moreinfo Bug #767074 [release.debian.org] unblock: taurus/3.3.1+dfsg-1 Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 767074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767074 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.14145117892888.transcr...@bugs.debian.org
Bug#767074: unblock: taurus/3.3.1+dfsg-1
On 2014-10-28 12:37, PICCA Frederic-Emmanuel wrote: So, please point to the relevant bug reports closed by 3.3.1, that might help convincing the release team that accepting this last-minute upstream release is worth it. Thanks! here the information from the mailing list http://sourceforge.net/p/sardana/mailman/message/32974642/ Release of sardana 1.4.1 and taurus 3.3.1 (Debian 8 Jessie). The main improvements in Sardana since 1.4.0 (aka Jul14) are: * add features: 231, 250 * fix bugs: 251 * dscanc return to start position The main improvements in Taurus since 3.3.0 (aka Jul14) are: * fix bugs: 234, 135, 208, 211, 210, 221, 222, 217, 224 * Add support for color video encoded images in Taurus Image Other minor changes [...] http://sourceforge.net/p/sardana/tickets/ Thanks for that. You may find other team members are prepared to go through the upstream tickets, but personally I'd appreciate more information than add features: 231, 250 in this request. 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/c862be7c7634a36ca36b1152d...@mail.adsl.funky-badger.org
Bug#767122: marked as done (unblock: ruby-sass-rails/4.0.3-2)
Your message dated Tue, 28 Oct 2014 17:02:54 + with message-id 2f194bf00e1de1f1242493e488831...@mail.adsl.funky-badger.org and subject line Re: Bug#767122: unblock: ruby-sass-rails/4.0.3-2 has caused the Debian Bug report #767122, regarding unblock: ruby-sass-rails/4.0.3-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.) -- 767122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767122 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 ruby-sass-rails, or better, age it in a way that it can get into jessie before the freeze. A recent upload of ruby-sass (not maintained by the Ruby team, so not really under our control) revealed that the dependency specification in ruby-sass-rails was too strict. This caused the rails test suite to fail on CI, what brought the issue to my attention: http://ci.debian.net/data/packages/unstable/amd64/r/rails/20141028_031245.autopkgtest.log Attached you will find a debdiff agains the package in jessie, which is quite simple and fixes the default Rails stack. unblock ruby-sass-rails/4.0.3-2 -- System Information: Debian Release: jessie/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Antonio Terceiro terce...@debian.org diff -Nru ruby-sass-rails-4.0.3/debian/changelog ruby-sass-rails-4.0.3/debian/changelog --- ruby-sass-rails-4.0.3/debian/changelog 2014-08-03 00:06:42.0 -0300 +++ ruby-sass-rails-4.0.3/debian/changelog 2014-10-28 13:10:04.0 -0200 @@ -1,3 +1,11 @@ +ruby-sass-rails (4.0.3-2) unstable; urgency=medium + + * Team upload + * debian/patches/sprockets-2.x.patch: amend change to metadata.yml to relax +dependency on sass-rails. + + -- Antonio Terceiro terce...@debian.org Tue, 28 Oct 2014 13:09:58 -0200 + ruby-sass-rails (4.0.3-1) unstable; urgency=medium * Team upload diff -Nru ruby-sass-rails-4.0.3/debian/patches/sprockets-2.x.patch ruby-sass-rails-4.0.3/debian/patches/sprockets-2.x.patch --- ruby-sass-rails-4.0.3/debian/patches/sprockets-2.x.patch 2014-07-27 16:17:23.0 -0300 +++ ruby-sass-rails-4.0.3/debian/patches/sprockets-2.x.patch 2014-10-28 13:10:04.0 -0200 @@ -307,6 +307,23 @@ end --- a/metadata.yml +++ b/metadata.yml +@@ -17,14 +17,14 @@ dependencies: + requirements: + - - ~ + - !ruby/object:Gem::Version +-version: 3.2.0 ++version: '3.2' + type: :runtime + prerelease: false + version_requirements: !ruby/object:Gem::Requirement + requirements: + - - ~ + - !ruby/object:Gem::Version +-version: 3.2.0 ++version: '3.2' + - !ruby/object:Gem::Dependency + name: railties + requirement: !ruby/object:Gem::Requirement @@ -65,20 +65,14 @@ dependencies: requirements: - - ~ signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On 2014-10-28 15:18, Antonio Terceiro wrote: Please unblock package ruby-sass-rails, or better, age it in a way that it can get into jessie before the freeze. Aged to 5 days. Regards, Adam---End Message---
Bug#767139: unblock: security imagemagick/8:6.8.9.9-1
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: important Please unblock package imagemagick. This package release 4 security problems: - TEMP-0764872-F3D8A2 - TEMP-000-77B6EF - TEMP-000-3CE5AC - TEMP-000-1800A5 Three are remotly exploitable Moreover it fix #753770 that could be considered as a serious bug. I have programmed to made a last release of imagemagick for october the 23th or 24th just after my honeymoon but this release was delayed due to waiting upstream to fix the security problem. So please unblock imagemagick/8:6.8.9.9-1 Bastien -- 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/CAE2SPAaBw79=wydg6d-kk947eq+hmaywq0j6nq8vaichpud...@mail.gmail.com
Bug#767116: marked as done (unblock: vagrant/1.6.5+dfsg1-2)
Your message dated Tue, 28 Oct 2014 17:25:11 + with message-id 6f2b524c738ebc84d47abe56ceac1...@mail.adsl.funky-badger.org and subject line Re: Bug#767116: unblock: vagrant/1.6.5+dfsg1-2 has caused the Debian Bug report #767116, regarding unblock: vagrant/1.6.5+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.) -- 767116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767116 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 vagrant, or age it in a way that it reaches jessie in time for the freeze provided there are no other issues with it. This version fixes an RC bug which makes it impossible to download OS images over HTTP (which mainly breaks central use cases of the tool). Attached: - vagrant.diff: full debdiff against the version currently in jessie - 0008-Use-a-private-temporary-dir.patch: the larger patch included with this version so you don't have to read a diff-inside-diff. unblock vagrant/1.6.5+dfsg1-2 -- System Information: Debian Release: jessie/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Antonio Terceiro terce...@debian.org diff -Nru vagrant-1.6.5+dfsg1/debian/changelog vagrant-1.6.5+dfsg1/debian/changelog --- vagrant-1.6.5+dfsg1/debian/changelog 2014-10-12 16:48:53.0 -0300 +++ vagrant-1.6.5+dfsg1/debian/changelog 2014-10-28 12:16:13.0 -0200 @@ -1,3 +1,13 @@ +vagrant (1.6.5+dfsg1-2) unstable; urgency=medium + + * debian/patches/0008-Use-a-private-temporary-dir.patch: create temporary +files inside a private temporary directory instead of cluttering $TMPDIR. + * debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch: +updated, remove trailing newline from version number (Closes: #765074) +- Thanks Etienne Millon m...@emillon.org + + -- Antonio Terceiro terce...@debian.org Tue, 28 Oct 2014 12:12:27 -0200 + vagrant (1.6.5+dfsg1-1) unstable; urgency=medium [ Antonio Terceiro ] diff -Nru vagrant-1.6.5+dfsg1/debian/patches/0001-Constrain-dependency-resolution.patch vagrant-1.6.5+dfsg1/debian/patches/0001-Constrain-dependency-resolution.patch --- vagrant-1.6.5+dfsg1/debian/patches/0001-Constrain-dependency-resolution.patch 2014-10-12 16:48:53.0 -0300 +++ vagrant-1.6.5+dfsg1/debian/patches/0001-Constrain-dependency-resolution.patch 2014-10-28 12:16:13.0 -0200 @@ -1,7 +1,6 @@ -From f8bcc4e98d2476a44425bc9b2d0f9c077444bfda Mon Sep 17 00:00:00 2001 From: Antonio Terceiro terce...@debian.org Date: Sat, 11 Oct 2014 16:46:32 -0300 -Subject: [PATCH 1/7] Constrain dependency resolution +Subject: Constrain dependency resolution --- Gemfile | 6 -- @@ -63,6 +62,3 @@ # The following block of code determines the files that should be included # in the gem. It does this by reading all the files in the directory where --- -2.1.1 - diff -Nru vagrant-1.6.5+dfsg1/debian/patches/0002-Disable-Checkpoint.patch vagrant-1.6.5+dfsg1/debian/patches/0002-Disable-Checkpoint.patch --- vagrant-1.6.5+dfsg1/debian/patches/0002-Disable-Checkpoint.patch 2014-10-12 16:48:53.0 -0300 +++ vagrant-1.6.5+dfsg1/debian/patches/0002-Disable-Checkpoint.patch 2014-10-28 12:16:13.0 -0200 @@ -1,7 +1,6 @@ -From b8279f909656ad977dc54aec9c312b7578d7bec9 Mon Sep 17 00:00:00 2001 From: Antonio Terceiro terce...@debian.org Date: Sat, 11 Oct 2014 16:48:07 -0300 -Subject: [PATCH 2/7] Disable Checkpoint +Subject: Disable Checkpoint We don't want vagrant phoning home all the time --- @@ -72,6 +71,3 @@ end # Makes a call to the CLI with the given arguments as if they --- -2.1.1 - diff -Nru vagrant-1.6.5+dfsg1/debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch vagrant-1.6.5+dfsg1/debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch --- vagrant-1.6.5+dfsg1/debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch 2014-10-12 16:48:53.0 -0300 +++ vagrant-1.6.5+dfsg1/debian/patches/0003-VERSION-fallback-to-usr-share-vagrant-version.txt.patch 2014-10-28 12:16:13.0 -0200 @@ -1,14 +1,13 @@ -From 20131cc976e97b5d64dd1304a5f334a4098b066c Mon Sep 17 00:00:00 2001 From: Antonio Terceiro terce...@debian.org Date: Sat, 11
Bug#767082: unblock: exifprobe/2.0.1-3
Control: tags -1 + moreinfo On 2014-10-28 11:00, Joao Eriberto Mota Filho wrote: Please unblock package exifprobe. The package was orphan and I did a QA upload on 2014-08-24. Yesterday I adopted (under the Forensics Team) and uploaded the package to Sid. I Solved all bugs (4 bugs) and Lintian warnings (15 messages). The changelog is here[1]. The package is useful in forensics activities, is clean and working fine. I believe that is a good idea have this package in Jessie and I need a reduction of the migration time to 8 days. Looking at the diff, the changes all appear to be tidy-up or packaging changes (e.g. source format 3.0, copyright 1.0). What actual problems with the package currently in jessie does this update solve? 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/a40f8683e54117593e1b62babd5e6...@mail.adsl.funky-badger.org
Processed: Re: Bug#767082: unblock: exifprobe/2.0.1-3
Processing control commands: tags -1 + moreinfo Bug #767082 [release.debian.org] unblock: exifprobe/2.0.1-3 Added tag(s) moreinfo. -- 767082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767082 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.b767082.141451871522232.transcr...@bugs.debian.org
Bug#767082: unblock: exifprobe/2.0.1-3
Hi, Thanks for your reply. Yes, I updated the whole package. However, this solves 4 bugs and several warnings. I put all changes in d/copyright[1] (you will can see the changes and bugs). The patch provided by bug #597123 is essential to a proper functioning of the exifgrep command, provided by exifprobe. Thanks! Regards, Eriberto [1] http://metadata.ftp-master.debian.org/changelogs/main/e/exifprobe/unstable_changelog 2014-10-28 15:51 GMT-02:00 Adam D. Barratt a...@adam-barratt.org.uk: Control: tags -1 + moreinfo On 2014-10-28 11:00, Joao Eriberto Mota Filho wrote: Please unblock package exifprobe. The package was orphan and I did a QA upload on 2014-08-24. Yesterday I adopted (under the Forensics Team) and uploaded the package to Sid. I Solved all bugs (4 bugs) and Lintian warnings (15 messages). The changelog is here[1]. The package is useful in forensics activities, is clean and working fine. I believe that is a good idea have this package in Jessie and I need a reduction of the migration time to 8 days. Looking at the diff, the changes all appear to be tidy-up or packaging changes (e.g. source format 3.0, copyright 1.0). What actual problems with the package currently in jessie does this update solve? 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/CAP+dXJd-bFn1uGQpQj_cKmWKprPPZCM=zjcu3c4ghijfksr...@mail.gmail.com
Bug#767085: unblock: pcl/1.7.2-2
Let me support the Leopold request and explain why: from the robotics community (I work for the Open Source Robotics Foundation) the point cloud manipulation is one of the core tasks related to robotics perception. In our way of making Debian a good platform for free and open robots, pcl is definitely one of the main software we needed. Leo and the other debian-science folks were working hard to get this beast under debian and it would be really a pity to lost the opportunity to get it into the Jessie distribution for just a few days. Thanks. On 28/10/14 04:10, Leopold Palomo-Avellaneda wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please reduce the 10-day age period to 9 (or less) of this package. Let me explain the situation: We have worked hard with a big package: pcl. The package goes to new queue on June (2014-06-10). It was about 4 months. - It was rejected because problems in the copyright file. (2014-10-03) - Upstream in the middle releases a new version. (2014-09-10) - We worked with the new version and I asked my sponsor to upload it on Wednesday. (2014-10-15) - My sponsor upload it on Wednesday (2014-10-22) and ftp-masters upload it to unstable on Friday. (2014-10-24) - The same day, a few hours after to be in unstable, someone filled a Important bug of one binary package #766685: libpcl-dev - A few hours after I prepare a new version of the package solving the bug and I uploaded to mentors the new package, commented the bug and asked to my sponsor to upload the package (2014-10-25). However, I made a mistake and I put UNRELEASED so my sponsor rejects to upload it. - On Sunday morning (2014-10-26 Morning (UTC)) I asked to my sponsor to upload the new version, thinking that the period to have a package in testing before November 5th ended Sunday 26th 23:55 (UTC) (November 5th - 10 days). My sponsor upload it this morning 5:57, day 27th. I don't know if someone will fill any bug against the package before November 5th. I hope that no. But, we are not in time to be in testing before freeze because 6 hours... so it won't be in Jessie. Please, could you reduced the 10-day delay? Thanks in advance. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (600, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Jose Luis Rivero jriv...@osrfoundation.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/544fe2d3.8000...@osrfoundation.org
Bug#767139: unblock: security imagemagick/8:6.8.9.9-1
Control: tag -1 moreinfo Bastien ROUCARIES roucaries.bast...@gmail.com (2014-10-28): Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: important Please unblock package imagemagick. This package release 4 security problems: - TEMP-0764872-F3D8A2 - TEMP-000-77B6EF - TEMP-000-3CE5AC - TEMP-000-1800A5 Three are remotly exploitable Moreover it fix #753770 that could be considered as a serious bug. I have programmed to made a last release of imagemagick for october the 23th or 24th just after my honeymoon but this release was delayed due to waiting upstream to fix the security problem. So please unblock imagemagick/8:6.8.9.9-1 Given: https://buildd.debian.org/status/package.php?p=imagemagicksuite=unstable https://bugs.debian.org/767156 I'm not sure it's going to happen. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#767139: unblock: security imagemagick/8:6.8.9.9-1
Processing control commands: tag -1 moreinfo Bug #767139 [release.debian.org] unblock: security imagemagick/8:6.8.9.9-1 Added tag(s) moreinfo. -- 767139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767139 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.b767139.141452454531039.transcr...@bugs.debian.org
Bug#767085: marked as done (unblock: pcl/1.7.2-2)
Your message dated Tue, 28 Oct 2014 21:05:54 +0100 with message-id 544ff722.7060...@thykier.net and subject line Re: Bug#767085: unblock: pcl/1.7.2-2 has caused the Debian Bug report #767085, regarding unblock: pcl/1.7.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.) -- 767085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767085 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 reduce the 10-day age period to 9 (or less) of this package. Let me explain the situation: We have worked hard with a big package: pcl. The package goes to new queue on June (2014-06-10). It was about 4 months. - It was rejected because problems in the copyright file. (2014-10-03) - Upstream in the middle releases a new version. (2014-09-10) - We worked with the new version and I asked my sponsor to upload it on Wednesday. (2014-10-15) - My sponsor upload it on Wednesday (2014-10-22) and ftp-masters upload it to unstable on Friday. (2014-10-24) - The same day, a few hours after to be in unstable, someone filled a Important bug of one binary package #766685: libpcl-dev - A few hours after I prepare a new version of the package solving the bug and I uploaded to mentors the new package, commented the bug and asked to my sponsor to upload the package (2014-10-25). However, I made a mistake and I put UNRELEASED so my sponsor rejects to upload it. - On Sunday morning (2014-10-26 Morning (UTC)) I asked to my sponsor to upload the new version, thinking that the period to have a package in testing before November 5th ended Sunday 26th 23:55 (UTC) (November 5th - 10 days). My sponsor upload it this morning 5:57, day 27th. I don't know if someone will fill any bug against the package before November 5th. I hope that no. But, we are not in time to be in testing before freeze because 6 hours... so it won't be in Jessie. Please, could you reduced the 10-day delay? Thanks in advance. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (600, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Control: tags -1 wontfix On 2014-10-28 12:10, Leopold Palomo-Avellaneda wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please reduce the 10-day age period to 9 (or less) of this package. Let me explain the situation: [...] Please, could you reduced the 10-day delay? Thanks in advance. [...] I suspect you have made a mistake in the calculation of the deadline. AFAICT, pcl will have age 10/10 on the 5th in the second Britney run giving it *one shot* at migrating to testing (providing nothing blocks it)[2]. Mind you, if it misses that chance, you will truly have missed the deadline and then pcl will /not/ be included in Jessie. ~Niels [1] I do not say this to be mean, but we have to set the cut-off at some point. [2] If I am not mistaken, it will get age 2/10 tonight (in ~3-4 hours from now).---End Message---
Bug#767118: marked as done (unblock: sympow/1.023-5)
Your message dated Tue, 28 Oct 2014 21:12:13 +0100 with message-id 544ff89d.3070...@thykier.net and subject line Re: Bug#767118: unblock: sympow/1.023-5 has caused the Debian Bug report #767118, regarding unblock: sympow/1.023-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.) -- 767118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767118 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 The sympow package, which had not been updated since 2008-08-14, contains numerical fixes from the upstream maintainer himself and some major improvements regarding its linux integration part recently brought by myself. Because some intricate arch-indep data must be precomputed, the binary-indep deb ball could not build properly on some architectures (as sparc) due to a too long computing time: the issue was finally resolved by implementing a arch/indep scheme and now it can build for all architectures. Neverthless this last resolving process brought a sequence of FTBFS bugs. After all this efforts, the buildable version of the package was finally uploaded only a few hours after the the freeze time minus the 10-day age period. Hence the request to reduce its current transition period to 5 days in such a way the interesting audience can enjoy the updated version of sympow within Jessie. Please could the transition period for sympow/1.023-5 be reduced to 5 days. Thanks, Jerome unblock sympow/1.023-5 -- System Information: Debian Release: Wheezy* APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.10-amd64-mbp62 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Control: tags -1 wontfix On 2014-10-28 15:56, Jerome Benoit wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock [...] Please could the transition period for sympow/1.023-5 be reduced to 5 days. Thanks, Jerome [...] Hi Jerome, Sorry, but I will have to decline your request. While I am certain you did it with the best of intentions, we set a deadline for including arbitrary changes and your upload of sympow/1.023-5 seems to have missed said deadline. Sadly, the changes between the current version of sympow in testing and sympow/1.023-5 are /not/ compatible with our freeze guidelines. Accordingly, I will also have to decline giving an unblock for sympow. Yours truly, ~Niels---End Message---
Bug#767063: unblock: claws-mail/3.11.1-1
Control: tags -1 moreinfo On 2014-10-28 09:36, Ricardo Mones wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package claws-mail This is a bugfix release to complete removal of SSLv3 usage in all protocols and broken appdata added in 3.11.0 mainly. There's no Debian bugs reported yet (3.11.0 happened last week). Further details: http://git.claws-mail.org/?p=claws.git;f=RELEASE_NOTES;hb=refs/tags/3.11.1 Thanks in advance, unblock claws-mail/3.11.1-1 [...] Hi Ricardo, The changes seems to contain quite a bit of noise. Would you be able to provide a filtered debdiff between the version in unstable and testing? This might give us a better idea of what we will be accepting. ~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/544ffcc6.60...@thykier.net
Bug#767074: unblock: taurus/3.3.1+dfsg-1
ok, so here all the link * sardana ** features + http://sourceforge.net/p/sardana/tickets/231/ + http://sourceforge.net/p/sardana/tickets/250/ ** bugs +http://sourceforge.net/p/sardana/tickets/251/ (fix a crash) the dscan things has no bug report but is something important for the final users. * taurus * features + http://sourceforge.net/p/sardana/tickets/234/ + http://sourceforge.net/p/sardana/tickets/135/ + http://sourceforge.net/p/sardana/tickets/208/ (#208 TaurusValueEdit: exception when editing) + http://sourceforge.net/p/sardana/tickets/211/ + http://sourceforge.net/p/sardana/tickets/210/ + http://sourceforge.net/p/sardana/tickets/221/ (regression: Default Custom Widgets in TaurusValues stopped working) + http://sourceforge.net/p/sardana/tickets/222/ (compact mode fails with old PyQt versions) + http://sourceforge.net/p/sardana/tickets/217/ (Taurus configuration panel error when clicking ok/cancel) + http://sourceforge.net/p/sardana/tickets/224/ I would say that 251 and 221 deserve an upgrade of both package. Do you need more informations ? thanks Frederic -- 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/a2a20ec3b8560d408356cac2fc148e53b1fbb...@sun-dag3.synchrotron-soleil.fr
Bug#767061: marked as done (unblock: lyx/2.1.2-3)
Your message dated Tue, 28 Oct 2014 21:25:00 +0100 with message-id 544ffb9c.9040...@thykier.net and subject line Re: Bug#767061: unblock: lyx/2.1.2-3 has caused the Debian Bug report #767061, regarding unblock: lyx/2.1.2-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.) -- 767061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767061 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 lyx The changes are mainly cleanups and lintian issues. lyx (2.1.2-3) unstable; urgency=low * Bumped up Standards version to 3.9.6 (no changes needed) * Add support for upstream GPG signature tarball check * Update copyright file and convert to machine-readable format * Specify NEWS as the upstream changelog to be included in the binary packages * Mark fonts-lyx binary package as Multi-Arch: foreign * Add a lintian override for lyx-common's link to external mythes directory * Add a patch that populates .desktop file with a Keywords field * Fix permissions for some scripts -- Nick Andrik nick.and...@gmail.com Sun, 12 Oct 2014 01:13:52 +0200 I'm very sorry that I missed the deadline for automatic migrations due to my vacation, but a helpful contributor to the LyX package provided some valuable cleanups I'd like to see in jessie while I was absent. unblock lyx/2.1.2-3 -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-0.bpo.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 ---End Message--- ---BeginMessage--- Control: tags -1 wontfix On 2014-10-28 09:23, sven wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package lyx The changes are mainly cleanups and lintian issues. [...] I'm very sorry that I missed the deadline for automatic migrations due to my vacation, but a helpful contributor to the LyX package provided some valuable cleanups I'd like to see in jessie while I was absent. [...] Hi Sven, Sorry, but I will have to decline your request. While I am certain you did it with the best of intentions, we set a deadline for including arbitrary changes and your upload of lyx/2.1.2-3 seems to have missed said deadline. Sadly, the changes between the current version of lyx in testing and lyx/2.1.2-3 are /not/ compatible with our freeze guidelines. Accordingly, I will also have to decline giving an unblock for lyx. Yours truly, ~Niels---End Message---
Processed: Re: Bug#767063: unblock: claws-mail/3.11.1-1
Processing control commands: tags -1 moreinfo Bug #767063 [release.debian.org] unblock: claws-mail/3.11.1-1 Added tag(s) moreinfo. -- 767063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767063 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.b.141452820824137.transcr...@bugs.debian.org
Processed: Re: Bug#767063: unblock: claws-mail/3.11.1-1
Processing control commands: tags -1 moreinfo Bug #767063 [release.debian.org] unblock: claws-mail/3.11.1-1 Ignoring request to alter tags of bug #767063 to the same tags previously set -- 767063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767063 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.b767063.141452820824139.transcr...@bugs.debian.org
Processed: block 767077 with 767074
Processing commands for cont...@bugs.debian.org: block 767077 with 767074 Bug #767077 [release.debian.org] unblock: sardana/1.4.2-1 767077 was blocked by: 767074 767077 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #767077 to the same blocks previously set thanks Stopping processing here. Please contact me if you need assistance. -- 767077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767077 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.141452828024607.transcr...@bugs.debian.org
Bug#767082: marked as done (unblock: exifprobe/2.0.1-3)
Your message dated Tue, 28 Oct 2014 20:30:47 + with message-id 1414528247.12825.12.ca...@adam-barratt.org.uk and subject line Re: Bug#767082: unblock: exifprobe/2.0.1-3 has caused the Debian Bug report #767082, regarding unblock: exifprobe/2.0.1-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.) -- 767082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767082 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 exifprobe. The package was orphan and I did a QA upload on 2014-08-24. Yesterday I adopted (under the Forensics Team) and uploaded the package to Sid. I Solved all bugs (4 bugs) and Lintian warnings (15 messages). The changelog is here[1]. The package is useful in forensics activities, is clean and working fine. I believe that is a good idea have this package in Jessie and I need a reduction of the migration time to 8 days. This will be my last request of reduction. I no need this for other packages. Thanks in advance. Regards, Eriberto unblock exifprobe/2.0.1-3 [1] http://metadata.ftp-master.debian.org/changelogs/main/e/exifprobe/unstable_changelog ---End Message--- ---BeginMessage--- On Tue, 2014-10-28 at 16:31 -0200, Eriberto wrote: Thanks for your reply. Yes, I updated the whole package. However, this solves 4 bugs and several warnings. I put all changes in d/copyright[1] (you will can see the changes and bugs). I think you mean d/changelog. ;-) The patch provided by bug #597123 is essential to a proper functioning of the exifgrep command, provided by exifprobe. Having looked at that, okay. However, a further upload before -3 migrates is unlikely to get the same treatment. Regards, Adam---End Message---
Bug#766995: marked as done (unblock: pnp4nagios/0.6.24+dfsg1-2)
Your message dated Tue, 28 Oct 2014 21:59:32 +0100 with message-id 545003b4.2020...@thykier.net and subject line Re: Bug#766995: unblock: pnp4nagios/0.6.24+dfsg1-2 has caused the Debian Bug report #766995, regarding unblock: pnp4nagios/0.6.24+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.) -- 766995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766995 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 release team, would you be willing to allow pnp4nagios to migrate to testing before 5th Nov? (Lower the migration time to 5 days) I finally had the time to finalize and *proper* test the package yesterday. A lot of work was required to make the package fit and up2date. The package was not in testing since 2014-04-30, but is in wheezy at the moment I'll be happy if we can ship with jessie pnp4nagios if possible. Note: I just uploaded -2 for a description fix. Thanks Markus Frosch unblock pnp4nagios/0.6.24+dfsg1-2 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Control: tags -1 moreinfo On 2014-10-27 14:36, Markus Frosch wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi release team, would you be willing to allow pnp4nagios to migrate to testing before 5th Nov? (Lower the migration time to 5 days) I finally had the time to finalize and *proper* test the package yesterday. A lot of work was required to make the package fit and up2date. The package was not in testing since 2014-04-30, but is in wheezy at the moment I'll be happy if we can ship with jessie pnp4nagios if possible. Note: I just uploaded -2 for a description fix. Thanks Markus Frosch [...] Hi Markus, Sorry, but I will have to decline your request. While I am certain you put a lot of effort into this uplaod, we set a deadline for including arbitrary changes and your upload of pnp4nagios/0.6.24+dfsg1-2 seems to have missed said deadline. Sadly, since pnp4nagios is not in testing, we will have to regard it as a completely new package and these are /not/ compatible with our freeze guidelines. Yours truly, ~Niels---End Message---
Bug#767190: unblock: oxygen-gtk3/1.4.1-1
Package: release.debian.org Severity: minor User: release.debian@packages.debian.org Usertags: unblock oxygen-gtk3/1.4.1-1 Please unblock the above package (or reduce unstable-to-testing migration delay to allow package propagation to testing before freeze). Upstream just released a minor update to oxygen-gtk3/1.4 without even bothering to describe the changes. However by comparing previous 1.4.0 to the current 1.4.1 release I see that updates are mostly focused on improving (much needed) compatibility with GTK. Since there is still some time before freeze I'd like to ask you to consider inclusion of oxygen-gtk3/1.4.1 to Jessie. Brief run-time testing revealed no (obvious) problems and I think that probability of regression is low. I shall be happy to provide debdiff if needed. Thank you. -- All the best, Dmitry Smirnov. --- The great enemy of the truth is very often not the lie -- deliberate, contrived and dishonest, but the myth, persistent, persuasive, and unrealistic. Belief in myths allows the comfort of opinion without the discomfort of thought. -- John F Kennedy signature.asc Description: This is a digitally signed message part.
Bug#767191: unblock: zabbix/1:2.2.7+dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock zabbix/1:2.2.7+dfsg-1 Please unblock the above package (or reduce unstable-to-testing migration delay to allow package propagation to testing before freeze). As per upstream Life Cycle Release Policy [1] Zabbix 2.2 is a long term support (LTS) release which just received its 7th update fixing over 30 issues. Point release LTS updates are conservative bugfix-only updates (see list of changes in [2]). As bugfix-only update I believe Zabbix_2.2.7 is eligible for Jessie and including latest point release 2.2.7 will provide strategic advantages for future updates. I estimate low risk of regression and recommend 2.2.7 for inclusion to Jessie. Thank you. [1]: http://www.zabbix.com/life_cycle_and_release_policy.php [2]: http://www.zabbix.com/rn2.2.7.php -- Best wishes, Dmitry Smirnov GPG key : 4096R/53968D1B --- Reality is that which, when you stop believing in it, doesn't go away. -- Philip K. Dick signature.asc Description: This is a digitally signed message part.
Bug#767192: unblock: xpra/0.14.10+dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock xpra/0.14.10+dfsg-1 Please unblock the above package (or reduce unstable-to-testing migration delay to allow package propagation to testing before freeze). Xpra-0.14.10 is a bug-fix update for long-term supported branch. Here is how upstream described the latest changes in the announce: This minor update fixes some important bugs, some of which can cause crashes or deadlocks. Upgrading is strongly recommended: * fix crash with JPEG encoding and OpenGL * fix deadlocks with sound on connection shutdown * fix server errors with clients supporting very limited encodings * fix compatibility with Fedora 21+ Xorg suid script * fix compatibility with some login shells (ie: tcsh) * fix warnings with NVENC and newer Nvidia driver versions * fix warning with newer versions of Python Pillow As conservative update fixing serious problems such as crash and deadlock I believe xpra/0.14.10+dfsg-1 is eligible for Jessie hence I recommend to include Xpra 0.14.10 to Jessie. IMHO it should be safe due to low probability of regression. Thank you. -- Best wishes, Dmitry Smirnov GPG key : 4096R/53968D1B --- The persistence of erroneous beliefs exacerbates the widespread anachronistic failure to recognize the urgent problems that face humanity on this planet. -- Murray Gell-Mann, Quark and the Jaguar signature.asc Description: This is a digitally signed message part.
