Bug#697667: unblock: opendkim/2.6.8-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package opendkim
I haven't uploaded this to unstable yet, this is a pre-approval request as
the bug is not RC, but it's a trivial fix backported from upstream with
negligible risk of regression that will help admins diagnose and troubleshoot
DKIM signing/verification issues. Since currently the logs get the message
selector wrong (it logs the signing domain instead), it makes it very
difficult to troubleshoot selector related isseus (which are not rare).
Please let me know if this is OK and if so, I'm prepared to upload right
away.
unblock opendkim/2.6.8-4
diff -u opendkim-2.6.8/debian/changelog opendkim-2.6.8/debian/changelog
--- opendkim-2.6.8/debian/changelog
+++ opendkim-2.6.8/debian/changelog
@@ -1,3 +1,10 @@
+opendkim (2.6.8-4) unstable; urgency=low
+
+ * Backport fix from upstream to log the correct message selector
+(Closes: #695145) (fix was included as part of the just released 2.7.4)
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 08 Jan 2013 02:44:28 -0500
+
opendkim (2.6.8-3) unstable; urgency=medium
* Urgency medium for low risk RC bug fix
only in patch2:
unchanged:
--- opendkim-2.6.8.orig/opendkim/opendkim.c
+++ opendkim-2.6.8/opendkim/opendkim.c
@@ -13365,7 +13365,7 @@
for (c = 0; c nsigs; c++)
{
domain = dkim_sig_getdomain(sigs[c]);
- selector = dkim_sig_getdomain(sigs[c]);
+ selector = dkim_sig_getselector(sigs[c]);
err = dkim_sig_geterror(sigs[c]);
errstr = dkim_sig_geterrorstr(err);
Bug#687526: Bug#696983: slbackup: cronjob warn about obsolete getopts.pl dependency
On 2013-01-08 01:14, Mike Gabriel wrote: Hi Niels, thanks for taking your time to look at this issue more deeply. Your extra info is very valuable to me and the D-E team. You are welcome. :) On Mo 07 Jan 2013 14:34:17 CET Niels Thykier wrote: On 2013-01-07 12:12, Holger Levsen wrote: Hi Mike, [...] Mind you, I am a bit out of my conform zone on what this postinst script is doing, so I am not sure I'd ACK it on my own (even with the parts above fixed). Particularly, Julien already suggested that he found the changes to invasive[3]. I am happy to follow any of your suggestions, esp. because I would call my self a still-learning-Perl-person. The big question is, if a change like you propose might make a difference for the transition of an adapted-like-you-suggest package to wheezy. If there is a yes to that question, I will put fixing the package on prio-A. Personally, I would flat out reject the changes as long as they ignore errors[1]. So that sense, I suppose it will make a difference. Mind you, even with the proper error handling I am not sure I would unblock the package. Partly because I am not confident with particular things the script is doing and partly because of Julien's comment on the changes being invasive. But if nothing else, I believe you would be fixing a latent RC bug in experimental. Thanks+Greets, Mike ~Niels [1] I see it as a violation of Policy §6.1: It is important that they [maintainer scripts] exit with a non-zero status if there is an error, so that the package management system can stop its processing. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50ebdbd0.2040...@thykier.net
Bug#696722: Processed: Re: Bug#696722: unblock: maint-guide/1.2.31
tag 696722 - moreinfo thanks Hi, On Thu, Dec 27, 2012 at 09:33:06PM +, Debian Bug Tracking System wrote: Processing control commands: tag -1 + moreinfo Bug #696722 [release.debian.org] unblock: maint-guide/1.2.31 Added tag(s) moreinfo. Oh I see this is why it is not moving to testing. Well the only thing missing was debdiff if I understand this right. (It would be nice if this also send message to the -submitter address too. So I could have acted quicker.) Here is the debdiff excluding all the XML(*.dbk, *.ent) and their PO translation (*.po, *.pot) files. (I see no point including extremely long XML/PO diff since this source is build for package and web site without problem.) Just as I wrote, no change in build script: $ debdiff --exclude '*.po' --exclude '*.pot' --exclude '*.ent' --exclude '*.dbk' maint-guide_1.2.30.dsc maint-guide_1.2.31.dsc diff -Nru --exclude '*.po' --exclude '*.pot' --exclude '*.ent' --exclude '*.dbk' maint-guide-1.2.30/debian/changelog maint-guide-1.2.31/debian/changelog --- maint-guide-1.2.30/debian/changelog 2012-09-21 00:04:13.0 +0900 +++ maint-guide-1.2.31/debian/changelog 2012-12-24 23:32:41.0 +0900 @@ -1,3 +1,13 @@ +maint-guide (1.2.31) unstable; urgency=low + + * Correct ML reference to debian-devel-changes. Closes: #671703 + * Correct URL links. Closes: #678041, #692210 + * Document dh_link(1) and debian/links debian/symbols, --with gir. +and shared libraries. Closes: #668935, #691094 + * Updated translations: ja fr it es ca ru Closes: #688243, #696255 + + -- Osamu Aoki os...@debian.org Mon, 24 Dec 2012 23:32:31 +0900 + maint-guide (1.2.30) unstable; urgency=low [ David Prévot ] Osamu -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130108124613.GA5739@goofy.localdomain
Processed: Re: Processed: Re: Bug#696722: unblock: maint-guide/1.2.31
Processing commands for cont...@bugs.debian.org: tag 696722 - moreinfo Bug #696722 [release.debian.org] unblock: maint-guide/1.2.31 Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 696722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696722 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: http://lists.debian.org/handler.s.c.135764921128215.transcr...@bugs.debian.org
Bug#696722: Processed: Re: Bug#696722: unblock: maint-guide/1.2.31
[there's no need to CC -release on mail to release.d.o bugs...] On 08.01.2013 12:46, Osamu Aoki wrote: On Thu, Dec 27, 2012 at 09:33:06PM +, Debian Bug Tracking System wrote: Processing control commands: tag -1 + moreinfo [...] (It would be nice if this also send message to the -submitter address too. So I could have acted quicker.) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696722#10 (where the tag was added) says To: Osamu Aoki os...@debian.org... Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/b377299585eba929bcc86957c1b6a...@mail.adsl.funky-badger.org
Bug#697688: unblock: proftpd-dfsg/1.3.4a-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package proftpd-dfsg [SECURITY] New patch 3841 fixes CVE-2012-6095: a possible race condition in the handling of the MKD/XMKD FTP commands, when the UserOwner directive is involved, and the attacker is on the same physical machine as a running proftpd. Diff consists in a single patch file '3841' in quilt format. The same patch has been backported to stable (for version 1.3.3). unblock proftpd-dfsg/1.3.4a-3 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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: http://lists.debian.org/20130108141459.9490.62558.report...@blegrez.ba.issia.cnr.it
Bug#697691: preapproval unblock: dspam/3.10.1+dfsg-7
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package dspam
[this is a preapproval unblock request]
Bug #695275 harmful actions in multiple postrm scripts of M-A:same
packages was not fixed completely by previous upload to t-p-u. Indeed,
many more resources are shared between several architecture of a same
package, for instance configuration file.
As such, the least intrusive change now is to just disable multiarch.
It's not even much a big loss since the libraries shipped by src:dspam
are private libraries (plugins).
Since multi-arch is disabled, I decided to restore the old postinst
script of libdspam7 which was in testing before last upload.
See attached debdiff.
unblock dspam/3.10.1+dfsg-7
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru dspam-3.10.1+dfsg/debian/changelog dspam-3.10.1+dfsg/debian/changelog
--- dspam-3.10.1+dfsg/debian/changelog 2012-12-20 06:33:53.0 +0100
+++ dspam-3.10.1+dfsg/debian/changelog 2013-01-08 11:40:36.0 +0100
@@ -1,3 +1,11 @@
+dspam (3.10.1+dfsg-7) testing-proposed-updates; urgency=low
+
+ * Disable multi-arch since it create many problems with regards to the
+handling of shared resources when a package is installed for several
+architectures (Closes: #695275).
+
+ -- Thomas Preud'homme robo...@debian.org Tue, 08 Jan 2013 11:37:35 +0100
+
dspam (3.10.1+dfsg-6) testing-proposed-updates; urgency=low
* Do not lock dspam user account on purge since the package could be still
diff -Nru dspam-3.10.1+dfsg/debian/control dspam-3.10.1+dfsg/debian/control
--- dspam-3.10.1+dfsg/debian/control 2012-12-20 06:33:53.0 +0100
+++ dspam-3.10.1+dfsg/debian/control 2013-01-08 11:40:36.0 +0100
@@ -54,7 +54,6 @@
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}, adduser
Suggests: libdspam7-drv (= ${binary:Version})
-Multi-Arch: ${misc:Multi-Arch}
Description: Core message processing and classification functionality for DSPAM
DSPAM is a dedicated statistical filter with minimal resources. It includes
many new algorithms to fight against spam including:
@@ -87,7 +86,6 @@
Replaces: dspam (= 3.9.1~rc1+git20110514.347379b+dfsg-1)
Breaks: dspam (= 3.9.1~rc1+git20110514.347379b+dfsg-1)
Provides: libdspam7-drv
-Multi-Arch: ${misc:Multi-Arch}
Description: Hash backend for DSPAM anti-spam filter
DSPAM is a dedicated statistical filter with minimal resources. It includes
many new algorithms to fight against spam including:
@@ -104,7 +102,6 @@
Depends: ${misc:Depends}, ${shlibs:Depends}, libdspam7 (= ${binary:Version}), dbconfig-common, ucf (= 0.28), postgresql-client
Recommends: postgresql
Provides: libdspam7-drv
-Multi-Arch: ${misc:Multi-Arch}
Description: PostgreSQL backend for DSPAM anti-spam filter
DSPAM is a dedicated statistical filter with minimal resources. It includes
many new algorithms to fight against spam including:
@@ -121,7 +118,6 @@
Depends: ${misc:Depends}, ${shlibs:Depends}, libdspam7 (= ${binary:Version}), dbconfig-common, ucf (= 0.28), mysql-client
Recommends: mysql-server
Provides: libdspam7-drv
-Multi-Arch: ${misc:Multi-Arch}
Description: MySQL backend for DSPAM anti-spam filter
DSPAM is a dedicated statistical filter with minimal resources. It includes
many new algorithms to fight against spam including:
@@ -137,7 +133,6 @@
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}, sqlite3, libdspam7 (= ${binary:Version})
Provides: libdspam7-drv
-Multi-Arch: ${misc:Multi-Arch}
Description: sqlite3 backend for DSPAM anti-spam filter
DSPAM is a dedicated statistical filter with minimal resources. It includes
many new algorithms to fight against spam including:
@@ -184,7 +179,6 @@
Recommends: libdspam7-drv-hash (= ${binary:Version}), libdspam7-drv-mysql (= ${binary:Version}), libdspam7-drv-pgsql (= ${binary:Version}), libdspam7-drv-sqlite3 (= ${binary:Version})
Suggests: libc-dbg
Priority: extra
-Multi-Arch: ${misc:Multi-Arch}
Description: debugging symbols for DSPAM related libraries
DSPAM is a dedicated statistical filter with minimal resources. It includes
many new algorithms to fight against spam including:
diff -Nru dspam-3.10.1+dfsg/debian/libdspam7.postrm dspam-3.10.1+dfsg/debian/libdspam7.postrm
--- dspam-3.10.1+dfsg/debian/libdspam7.postrm 2012-12-20 06:33:53.0 +0100
+++ dspam-3.10.1+dfsg/debian/libdspam7.postrm 2013-01-08 11:40:36.0 +0100
@@ -1,6 +1,11 @@
#!/bin/sh
set -e
+# Locks dspam system account on purge
+if [ $1 = purge ] ; then
+usermod -L -e 1 dspam /dev/null || true
+fi
+
Bug#697140: unblock: zangband/1:2.7.5pre1-7
On 06.01.2013 16:11, Niels Thykier wrote: I am not convinced that version 1:2.7.5pre1-7 does not fix all license issues in zangband (see the remark about Files: debian/* below). Dear release team, i have prepared an updated copyright file. Before uploading a new revision i would like to ask you for your opinion about it and if it comes into question for an unblock. I have changed the GPL-3+ license for the debian directory to the GNU All-Permissive license. My intention is to make the files in the debian directory freely available for everyone without making the package non-distributable. I have also reviewed the Angband-License again. The only occurrence of the license is in src/angband.h. Zangband and Angband license both apply to this file. Therefore i have created two stand-alone license paragraphs for the Angband and Zangband license so that the newly created Files paragraph for src/angband.h conforms to copyright format 1.0. A new debdiff is attached to this bug report. Regards, Markus zangband.debdiff.gz Description: GNU Zip compressed data signature.asc Description: OpenPGP digital signature
Bug#696722: Processed: Re: Bug#696722: unblock: maint-guide/1.2.31
Excuse me. On Tue, Jan 08, 2013 at 01:11:11PM +, Adam D. Barratt wrote: (It would be nice if this also send message to the -submitter address too. So I could have acted quicker.) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696722#10 (where the tag was added) says To: Osamu Aoki os...@debian.org... PEBKAC (I have it in my inbox too. Too much new year celebration.) Osamu -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130108152819.GA13446@goofy.localdomain
Bug#661078: britney: ignore additional packages in Sources index
Hi,
I finally got around to implement this in dak. The patch is available in
the f/extra-sources branch of my Git repository[1].
Sources only referenced by Built-Using will have a field
Extra-Source-Only: yes
On franck.d.o you can look at the changes this would introduce to
testing's Sources with
cd /home/ansgar/public_html/root/srv/ftp-master.debian.org/ftp/dists
zdiff -d -u testing{-old,}/main/source/Sources.gz
The files are also accessible from [2].
Niels, could you update the patch to britney you prepared earlier?
Ansgar
[1] https://ftp-master.debian.org/users/ansgar/dak.git
[2] http://ftp-master.debian.org/users/ansgar/root/
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50ec3fc9.1030...@debian.org
Bug#695642: pu: package magpierss/0.72-8+squeeze2
Hi Niels, On Sun, 2013-01-06 at 23:15 +0100, Niels Thykier wrote: Looks good; please let us know when you have uploaded it. Uploaded! Cheers, -- Marcelo Jorge Vieira xmpp:me...@jabber-br.org http://metaldot.alucinados.com signature.asc Description: This is a digitally signed message part
Bug#687779: release.debian.org: New NMU fixing #679966
retitle 687779 unblock: ksh/93u+-1.2 thanks On Mon, Jan 07, 2013 at 01:24:29PM +, Adam D. Barratt wrote: So, what do you suggest? New upstream version or patching the current version in unstable? Either would work for me. otoh, maybe I'm being too fussy - it just feels a little wrong to me to have fixes bypassing unstable when it's affected; thoughts from readers welcome. :-( Oliver has now prepared the new upstream version 2012-08-01 which I have reviewed and uploaded into unstable, the issue has now been fixed in unstable as well. We are now ready to unblock the version in t-p-u I guess such that the bug can finally be closed in testing. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130108183753.ga12...@physik.fu-berlin.de
Processed: Re: Bug#687779: release.debian.org: New NMU fixing #679966
Processing commands for cont...@bugs.debian.org: retitle 687779 unblock: ksh/93u+-1.2 Bug #687779 [release.debian.org] unblock: ksh/93u+20120628-1 Changed Bug title to 'unblock: ksh/93u+-1.2' from 'unblock: ksh/93u+20120628-1' thanks Stopping processing here. Please contact me if you need assistance. -- 687779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687779 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: http://lists.debian.org/handler.s.c.135767028118284.transcr...@bugs.debian.org
Bug#697667: unblock: opendkim/2.6.8-4
Control: tag -1 confirmed On Tue, Jan 8, 2013 at 02:55:00 -0500, Scott Kitterman wrote: Please let me know if this is OK and if so, I'm prepared to upload right away. Go ahead. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#697667: unblock: opendkim/2.6.8-4
Processing control commands: tag -1 confirmed Bug #697667 [release.debian.org] unblock: opendkim/2.6.8-4 Added tag(s) confirmed. -- 697667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697667 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: http://lists.debian.org/handler.s.b697667.135767115023936.transcr...@bugs.debian.org
Bug#697706: RM: elementary/0.7.0.55225-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm The version of elementary currently in testing is a development snapshot which will receive no upstream support in the future; newer, supported versions of elementary are too recent to go into testing. Please remove the package from testing so that it's not released with wheezy. Thanks, -- Albin -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-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/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130108185342.12072.85262.reportbug@x220
Bug#697707: RM: e17/0.16.999.70492-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Dear release team, The version of e17 currently in testing is a development snapshot which will receive no upstream support in the future; newer, supported versions of e17 are too recent to go into testing. Please remove the package from testing so that it's not released with wheezy. Thanks, -- Albin -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-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/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130108185643.12159.92627.reportbug@x220
Bug#697708: RM: e17/0.16.999.70492-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Dear release team, The version of e17 currently in testing is a development snapshot which will receive no upstream support in the future; newer, supported versions of e17 are too recent to go into testing. Please remove the package from testing so that it's not released with wheezy. Thanks, -- Albin -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-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/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130108185138.11917.91022.reportbug@x220
Bug#697706: RM: elementary/0.7.0.55225-1
Control: tags -1 + moreinfo On Tue, 2013-01-08 at 19:53 +0100, Albin Tonnerre wrote: The version of elementary currently in testing is a development snapshot which will receive no upstream support in the future; newer, supported versions of elementary are too recent to go into testing. Please remove the package from testing so that it's not released with wheezy. It also has several reverse-dependencies, so can't be removed right now: Checking reverse dependencies... # Broken Depends: enna: enna [amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc] intone: intone libphone-ui-shr: libphone-ui-shr [amd64 armel armhf i386 ia64 mips mipsel powerpc s390 s390x sparc] # Broken Build-Depends: enna: libelementary-dev (= 0.7.0.49898) intone: libelementary-dev libphone-ui-shr: libelementary-dev (= 0.7.0) Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1357672029.4189.2.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#697706: RM: elementary/0.7.0.55225-1
Processing control commands: tags -1 + moreinfo Bug #697706 [release.debian.org] RM: elementary/0.7.0.55225-1 Added tag(s) moreinfo. -- 697706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697706 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: http://lists.debian.org/handler.s.b697706.135767204130413.transcr...@bugs.debian.org
Bug#697708: RM: e17/0.16.999.70492-2
On Tue, 2013-01-08 at 19:51 +0100, Albin Tonnerre wrote: The version of e17 currently in testing is a development snapshot which will receive no upstream support in the future; newer, supported versions of e17 are too recent to go into testing. Please remove the package from testing so that it's not released with wheezy. This appears to be a duplicate of #697707? Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1357672195.4189.4.ca...@jacala.jungle.funky-badger.org
Bug#697707: marked as done (RM: e17/0.16.999.70492-2)
Your message dated Tue, 08 Jan 2013 19:09:06 + with message-id 1357672146.4189.3.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#697707: RM: e17/0.16.999.70492-2 has caused the Debian Bug report #697707, regarding RM: e17/0.16.999.70492-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.) -- 697707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697707 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 Dear release team, The version of e17 currently in testing is a development snapshot which will receive no upstream support in the future; newer, supported versions of e17 are too recent to go into testing. Please remove the package from testing so that it's not released with wheezy. Thanks, -- Albin -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-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/dash ---End Message--- ---BeginMessage--- On Tue, 2013-01-08 at 19:56 +0100, Albin Tonnerre wrote: The version of e17 currently in testing is a development snapshot which will receive no upstream support in the future; newer, supported versions of e17 are too recent to go into testing. Please remove the package from testing so that it's not released with wheezy. Removal hint added. Regards, Adam---End Message---
Bug#687779: marked as done (unblock: ksh/93u+-1.2)
Your message dated Tue, 08 Jan 2013 19:13:20 + with message-id 1357672400.4189.7.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#687779: release.debian.org: New NMU fixing #679966 has caused the Debian Bug report #687779, regarding unblock: ksh/93u+-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.) -- 687779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687779 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: freeze-exception Hi, Please unblock package ksh/93u+20120628-1 which fixes #679966 (severity grave). Frankly it would be better to exclude ksh from the next Debian release than include it with this bug because it breaks very basic functionality in the shell. The fix was done upstream so I don't really know the details. Thanks Oliver ---End Message--- ---BeginMessage--- On Tue, 2013-01-08 at 19:37 +0100, John Paul Adrian Glaubitz wrote: On Mon, Jan 07, 2013 at 01:24:29PM +, Adam D. Barratt wrote: So, what do you suggest? New upstream version or patching the current version in unstable? Either would work for me. otoh, maybe I'm being too fussy - it just feels a little wrong to me to have fixes bypassing unstable when it's affected; thoughts from readers welcome. :-( Oliver has now prepared the new upstream version 2012-08-01 which I have reviewed and uploaded into unstable, the issue has now been fixed in unstable as well. Approved, thanks. fwiw, the description appears to be missing some words +Description: fix-cd-builtin + This patch integrates the changes from the upstream commit + ee4582a which fixes the built-in cd command which caused + 'cd ..' when the parent directory was the root directory. ^ here? Regards, Adam---End Message---
Bug#697708: RM: e17/0.16.999.70492-2
merge 697707 697708 thanks On Tue, Jan 8, 2013 at 8:09 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: On Tue, 2013-01-08 at 19:51 +0100, Albin Tonnerre wrote: The version of e17 currently in testing is a development snapshot which will receive no upstream support in the future; newer, supported versions of e17 are too recent to go into testing. Please remove the package from testing so that it's not released with wheezy. This appears to be a duplicate of #697707? Yes, sorry. I somehow managed to send the mail twice. Regards, -- Albin -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANa7bJvxnt1DaCts=9HAtCiN2AOxP=+5v2dvpz0z+zyxkva...@mail.gmail.com
Processed (with 1 errors): Re: Bug#697708: RM: e17/0.16.999.70492-2
Processing commands for cont...@bugs.debian.org:
merge 697707 697708
Bug #697707 {Done: Adam D. Barratt a...@adam-barratt.org.uk}
[release.debian.org] RM: e17/0.16.999.70492-2
Unable to merge bugs because:
done of #697708 is '' not 'Adam D. Barratt a...@adam-barratt.org.uk'
Failed to merge 697707: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2920780)',
'requester', 'Albin Tonnerre lu...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'CANa7bJvxnt1DaCts=9HAtCiN2AOxP=+5v2dvpz0z+zyxkva...@mail.gma...',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', undef, 'clonebugs',
'HASH(0x2897160)', 'limit', 'HASH(0x2896b48)', 'common_control_options',
'ARRAY(0x2896b90)', 'errors', ...) called at /usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
697707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697707
697708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697708
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:
http://lists.debian.org/handler.s.c.13576724791972.transcr...@bugs.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org:
forcemerge 697707 697708
Bug #697707 {Done: Adam D. Barratt a...@adam-barratt.org.uk}
[release.debian.org] RM: e17/0.16.999.70492-2
Bug #697708 [release.debian.org] RM: e17/0.16.999.70492-2
Marked Bug as done
Merged 697707 697708
thanks
Stopping processing here.
Please contact me if you need assistance.
--
697707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697707
697708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697708
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:
http://lists.debian.org/handler.s.c.13576729465489.transcr...@bugs.debian.org
Bug#697710: unblock: geoip-database/20130108-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package geoip-database Just another monthly database update, thanks :) unblock geoip-database/20130108-1 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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: http://lists.debian.org/20130108192823.13402.68294.report...@srv1.linux-dev.org
Bug#697711: unblock: apt-dater/0.9.0-3+wheezy1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package apt-dater
It fixes bug #697330 which should be included into Wheezy, so that..
a) Wheezy kernels are not displayed as selfbuilt ones
b) so on also the restart detection works (if the kernel needs a restart after
an security update)
diff -Naur '--exclude=.svn' 0.9.0-3/debian/changelog
0.9.0-3+wheezy1/debian/changelog
--- 0.9.0-3/debian/changelog2012-07-18 20:15:49.0 +0200
+++ 0.9.0-3+wheezy1/debian/changelog2013-01-08 19:57:50.712596633 +0100
@@ -1,3 +1,11 @@
+apt-dater (0.9.0-3+wheezy1) unstable; urgency=low
+
+ * Add patch 03-wheezy-kernel, which fixes an missdetection of the Wheezy 3.2
+Linux Kernel as selfbuilt variant.
+Closes: #697330
+
+ -- Patrick Matthäi pmatth...@debian.org Tue, 08 Jan 2013 19:39:23 +0100
+
apt-dater (0.9.0-3) unstable; urgency=low
* Add upstream patch 02-refresh-ssh-flags which adds OptionalCmdFlags on
diff -Naur '--exclude=.svn' 0.9.0-3/debian/patches/03-wheezy-kernel.diff
0.9.0-3+wheezy1/debian/patches/03-wheezy-kernel.diff
--- 0.9.0-3/debian/patches/03-wheezy-kernel.diff1970-01-01
01:00:00.0 +0100
+++ 0.9.0-3+wheezy1/debian/patches/03-wheezy-kernel.diff2013-01-08
19:57:50.716596648 +0100
@@ -0,0 +1,18 @@
+# Upstream patch to fix detection of the Wheezy 3.2 Linux Kernel. It was
+# missdetected as selfbuilt variant.
+# Closes: #697330
+
+diff -Naur apt-dater-0.9.0.orig/clients/debian/apt-dater-host
apt-dater-0.9.0/clients/debian/apt-dater-host
+--- apt-dater-0.9.0.orig/clients/debian/apt-dater-host 2012-05-29
14:18:43.0 +0200
apt-dater-0.9.0/clients/debian/apt-dater-host 2013-01-08
19:32:09.520617548 +0100
+@@ -337,7 +337,9 @@
+ return;
+ }
+
+-unless(`cat /proc/version` =~ /^\S+ \S+ \S+ \(Debian ([^\)]+)\)/) {
++ my $vstr = `cat $verfile`;
++ unless($vstr =~ /^\S+ \S+ \S+ \(Debian ([^\)]+)\)/ ||
++ $vstr =~ /^\S+ \S+ \S+ \(debian-kernel\@lists\.debian\.org\) .+ Debian
(\S+)$/) {
+ print $infostr 2 $version\n;
+ return;
+ }
diff -Naur '--exclude=.svn' 0.9.0-3/debian/patches/series
0.9.0-3+wheezy1/debian/patches/series
--- 0.9.0-3/debian/patches/series 2012-07-18 20:15:49.0 +0200
+++ 0.9.0-3+wheezy1/debian/patches/series 2013-01-08 19:57:50.716596648
+0100
@@ -1,2 +1,3 @@
01-ld-flags-non-linux.diff
02-refresh-ssh-flags.diff
+03-wheezy-kernel.diff
unblock apt-dater/0.9.0-3+wheezy1
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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:
http://lists.debian.org/20130108193218.13454.61984.report...@srv1.linux-dev.org
Processed: forcibly merging 697707 697708
Processing commands for cont...@bugs.debian.org:
forcemerge 697707 697708
Bug #697707 {Done: Adam D. Barratt a...@adam-barratt.org.uk}
[release.debian.org] RM: e17/0.16.999.70492-2
Bug #697708 {Done: Adam D. Barratt a...@adam-barratt.org.uk}
[release.debian.org] RM: e17/0.16.999.70492-2
Bug #697708 {Done: Adam D. Barratt a...@adam-barratt.org.uk}
[release.debian.org] RM: e17/0.16.999.70492-2
Merged 697707 697708
thanks
Stopping processing here.
Please contact me if you need assistance.
--
697707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697707
697708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697708
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:
http://lists.debian.org/handler.s.c.135767366811184.transcr...@bugs.debian.org
Bug#687779: release.debian.org: New NMU fixing #679966
On Tue, 2013-01-08 at 20:14 +0100, John Paul Adrian Glaubitz wrote: On 01/08/2013 08:13 PM, Adam D. Barratt wrote: Approved, thanks. fwiw, the description appears to be missing some words +Description: fix-cd-builtin + This patch integrates the changes from the upstream commit + ee4582a which fixes the built-in cd command which caused + 'cd ..' when the parent directory was the root directory. ^ here? to fail :). Should I make another upload? It's not really worth it just to fix that; if the package is in a VCS it would be worth adding there so it's included in any future uploads though. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1357673778.4189.9.ca...@jacala.jungle.funky-badger.org
Bug#697711: marked as done (unblock: apt-dater/0.9.0-3+wheezy1)
Your message dated Tue, 08 Jan 2013 19:39:07 +
with message-id 1357673947.4189.10.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#697711: unblock: apt-dater/0.9.0-3+wheezy1
has caused the Debian Bug report #697711,
regarding unblock: apt-dater/0.9.0-3+wheezy1
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.)
--
697711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697711
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 apt-dater
It fixes bug #697330 which should be included into Wheezy, so that..
a) Wheezy kernels are not displayed as selfbuilt ones
b) so on also the restart detection works (if the kernel needs a restart after
an security update)
diff -Naur '--exclude=.svn' 0.9.0-3/debian/changelog
0.9.0-3+wheezy1/debian/changelog
--- 0.9.0-3/debian/changelog2012-07-18 20:15:49.0 +0200
+++ 0.9.0-3+wheezy1/debian/changelog2013-01-08 19:57:50.712596633 +0100
@@ -1,3 +1,11 @@
+apt-dater (0.9.0-3+wheezy1) unstable; urgency=low
+
+ * Add patch 03-wheezy-kernel, which fixes an missdetection of the Wheezy 3.2
+Linux Kernel as selfbuilt variant.
+Closes: #697330
+
+ -- Patrick Matthäi pmatth...@debian.org Tue, 08 Jan 2013 19:39:23 +0100
+
apt-dater (0.9.0-3) unstable; urgency=low
* Add upstream patch 02-refresh-ssh-flags which adds OptionalCmdFlags on
diff -Naur '--exclude=.svn' 0.9.0-3/debian/patches/03-wheezy-kernel.diff
0.9.0-3+wheezy1/debian/patches/03-wheezy-kernel.diff
--- 0.9.0-3/debian/patches/03-wheezy-kernel.diff1970-01-01
01:00:00.0 +0100
+++ 0.9.0-3+wheezy1/debian/patches/03-wheezy-kernel.diff2013-01-08
19:57:50.716596648 +0100
@@ -0,0 +1,18 @@
+# Upstream patch to fix detection of the Wheezy 3.2 Linux Kernel. It was
+# missdetected as selfbuilt variant.
+# Closes: #697330
+
+diff -Naur apt-dater-0.9.0.orig/clients/debian/apt-dater-host
apt-dater-0.9.0/clients/debian/apt-dater-host
+--- apt-dater-0.9.0.orig/clients/debian/apt-dater-host 2012-05-29
14:18:43.0 +0200
apt-dater-0.9.0/clients/debian/apt-dater-host 2013-01-08
19:32:09.520617548 +0100
+@@ -337,7 +337,9 @@
+ return;
+ }
+
+-unless(`cat /proc/version` =~ /^\S+ \S+ \S+ \(Debian ([^\)]+)\)/) {
++ my $vstr = `cat $verfile`;
++ unless($vstr =~ /^\S+ \S+ \S+ \(Debian ([^\)]+)\)/ ||
++ $vstr =~ /^\S+ \S+ \S+ \(debian-kernel\@lists\.debian\.org\) .+ Debian
(\S+)$/) {
+ print $infostr 2 $version\n;
+ return;
+ }
diff -Naur '--exclude=.svn' 0.9.0-3/debian/patches/series
0.9.0-3+wheezy1/debian/patches/series
--- 0.9.0-3/debian/patches/series 2012-07-18 20:15:49.0 +0200
+++ 0.9.0-3+wheezy1/debian/patches/series 2013-01-08 19:57:50.716596648
+0100
@@ -1,2 +1,3 @@
01-ld-flags-non-linux.diff
02-refresh-ssh-flags.diff
+03-wheezy-kernel.diff
unblock apt-dater/0.9.0-3+wheezy1
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
On Tue, 2013-01-08 at 20:32 +0100, Patrick Matthäi wrote:
Please unblock package apt-dater
It fixes bug #697330 which should be included into Wheezy, so that..
a) Wheezy kernels are not displayed as selfbuilt ones
b) so on also the restart detection works (if the kernel needs a restart after
an security update)
Unblocked; thanks.
Regards,
Adam---End Message---
Bug#697101: tpu: freerdp/1.0.1-1.1+deb7u1 (pre-approval)
2013/1/7 Julien Cristau jcris...@debian.org: So yes I think I'd prefer an upload reverting the .symbols change. Unfortunately, simply reverting the .symbols change is not enough, as dpkg-gensymbols is passed -c4 option which makes freerdp FTBFS due to newly added symbols. What do you suggest? Lowering -c4 to -c3 to ignore the symbols change? Adjusting the patch to flag the recently added functions as static? -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADk7b0Mco-KqBdGS=i6urtp8yftprth4-7qrr9anevjorjp...@mail.gmail.com
Bug#697649: pre-approve for freeze exception: snacc 1.3.1-2
On Tue, 2013-01-08 at 01:20 +0100, Bálint Réczey wrote: I would like to update the snacc package enabling multiarch for the shipped libraries. I'm afraid it's too late for such changes to make it to wheezy imo. I'm also not sure what the rationale would be for wheezy - the only user in the archive appears to be wireshark, which doesn't seem like the sort of application one would install multiple architectures of simultaneously. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1357674219.4189.14.ca...@jacala.jungle.funky-badger.org
Bug#697710: marked as done (unblock: geoip-database/20130108-1)
Your message dated Tue, 08 Jan 2013 20:42:03 +0100 with message-id 50ec768b.5070...@thykier.net and subject line Re: Bug#697710: unblock: geoip-database/20130108-1 has caused the Debian Bug report #697710, regarding unblock: geoip-database/20130108-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.) -- 697710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697710 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 geoip-database Just another monthly database update, thanks :) unblock geoip-database/20130108-1 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On 2013-01-08 20:28, Patrick Matthäi wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package geoip-database Just another monthly database update, thanks :) unblock geoip-database/20130108-1 [...] Unblocked, thanks. ~Niels---End Message---
Bug#697101: tpu: freerdp/1.0.1-1.1+deb7u1 (pre-approval)
On Tue, Jan 8, 2013 at 5:43 PM, Luca Falavigna dktrkr...@debian.org wrote: 2013/1/7 Julien Cristau jcris...@debian.org: So yes I think I'd prefer an upload reverting the .symbols change. Unfortunately, simply reverting the .symbols change is not enough, as dpkg-gensymbols is passed -c4 option which makes freerdp FTBFS due to newly added symbols. What do you suggest? Lowering -c4 to -c3 to ignore the symbols change? Adjusting the patch to flag the recently added functions as static? I think changing the patch is the way to go. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAP9ODKrtccMnZD2XoTCeB18bRLGv=ezrxpov3wvmj5s+r1z...@mail.gmail.com
Re: [Openstack-devel] Bug#685251: Fixing Debian bug #685251 for the ryu plugin in Openstack
Happy new year Thomas! Skipping release team for this mail as I want to check one thing with you. You write that we will not maintain the -6 version in sid. Do that mean that all the work I did for this package (to move out the plugin files to respective package will be in vain? Or is folsom release based on -6 version? Just checking. Based on your answer I will simply upload a -7 version that will be more or less identical to the version I was thinking of uploading to testing-proposed-updates. // Ola On Mon, Dec 31, 2012 at 03:32:34AM +0800, Thomas Goirand wrote: On 12/29/2012 09:22 PM, Ola Lundqvist wrote: * I don't think there's the need to use testing-proposed-updates. Uploading to SID will be just fine, as anyway, we haven't uploaded anything newer in SID which would pose a problem, and that we use Experimental for Folsom. (in other words: nothing prevents uploading to SID, and when we upload there it's in the hope it migrates to testing) No that won't work because the changes in -6 should remain. We will *not* maintain -6 in SID. It will go away and will be replaced by the Folsom packaging as soon as Wheezy is released. So why would you keep it in SID? And no I do not want to first upload a -7 version and than a new -8 with the changes in -6 because then I have to have a very complicated replaces rules in the control file which we really should avoid. Ah, that makes sense!!! :) But I don't think this cuts it. The changes will be necessary in Folsom anyway, because we should provide an upgrade path in SID. So we're doomed to the replaces+breaks it here. Note that we already have a Replaces: in the alioth for the Folsom release Quantum which I plan to upload soon. Should I add a Breaks: too? (I think so) Same answer as above. I have followed the instructions in http://www.debian.org/doc/manuals/developers-reference/pkgs.html chapter 5.13.3. Version numbers are usually selected by adding the codename of the testing distribution and a running number, like 1.2squeeze1 for the first upload through testing-proposed-updates of package version 1.2. This is just as valid for testing uploads as for stable uploads. Yeah, I wasn't debating this, I was questioning the relevance of using t-p-u instead of SID. * Our Git already contains entries for -6 and -7. Please use that, modifying the candidate version -7, and do not get out of sync with our Git please, otherwise it's going to be a nightmare! The -7 version is what I have used to backport from. I have taken your changes and re-done them for testing only. Then you should create a debian/wheezy branch in the Git! I was planning on doing that just right after the release of wheezy for all of our packages, but it will be needed now for Quantum if you want the package to have a Wheezy and a SID branch now. As much as I can see, Alioth doesn't have a debian/wheezy branch, does it? Also, this issue has been pending for 6 months! I do appreciate that you finally decide to work on it, even that late. But I continue to refuse to take the responsibility for it. The main mistake, IMO, was to leave the issue as-is, doing nothing to fix it. So you and Loic should really take the responsibility for the upload, and make sure it's in a correct shape *in time* for the release. I surely would feel bad if Quantum had to be removed from Wheezy. Please don't leave this pending again. I do not want to start a flamewar It wasn't my intention. I just wanted to highlight that this needs to be fixed soon. I do hope you don't take it personally. First of all it is 3.5 months (not 6) My count started on the 2012-07-06, when Quantum -6 was uploaded by Loic in SID. After such an upload, action should have been taken to have the package unblock (or that upload should have been made in experimental). secondly I have asked about your opintion on this matter without response and that explains more than 2 months. Well, the problem is that I might agree with the changes, *BUT*, I'm not a member of the release team, and therefore, I don't have any decision power. Also, I didn't really understand what was done at the time, and I probably still don't get why everything all of the code isn't stored in the python-* package. The only reason why I've been asking you, was to provide information to the release team for an unblock. But now I see that discussing it with me didn't help. :( I'm sorry that it seems you've been waiting on me. (As a rule, if I don't answer within 5 days, consider that either I don't know what to answer, or that your mail is stuck on my huge mail queue and that I had no time to answer. In which case, either send me another mail, or try to deal without my answer.) Again, I'm not trying to put the blame on you, just trying to push you to solve the current problem. Thanks again for working on it. Thomas -- --- Inguza
Bug#687779: release.debian.org: New NMU fixing #679966
On 01/08/2013 08:36 PM, Adam D. Barratt wrote: It's not really worth it just to fix that; if the package is in a VCS it would be worth adding there so it's included in any future uploads though. Ok, so version 93u+-1.2 is unblocked for migration from t-p-u to testing now? Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50ec7c0a.8080...@physik.fu-berlin.de
Bug#687779: release.debian.org: New NMU fixing #679966
On Tue, 2013-01-08 at 21:05 +0100, John Paul Adrian Glaubitz wrote: On 01/08/2013 08:36 PM, Adam D. Barratt wrote: It's not really worth it just to fix that; if the package is in a VCS it would be worth adding there so it's included in any future uploads though. Ok, so version 93u+-1.2 is unblocked for migration from t-p-u to testing now? Yes, as per MID:1357672400.4189.7.ca...@jacala.jungle.funky-badger.org Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1357675741.4189.18.ca...@jacala.jungle.funky-badger.org
Bug#697649: pre-approve for freeze exception: snacc 1.3.1-2
2013/1/8 Adam D. Barratt a...@adam-barratt.org.uk: On Tue, 2013-01-08 at 01:20 +0100, Bálint Réczey wrote: I would like to update the snacc package enabling multiarch for the shipped libraries. I'm afraid it's too late for such changes to make it to wheezy imo. I'm also not sure what the rationale would be for wheezy - the only user in the archive appears to be wireshark, which doesn't seem like the sort of application one would install multiple architectures of simultaneously. OK. I agree that it is not really important to update snacc. I'll upload the new package after the release. Cheers, Balint -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAK0Odpzm=0u0f-c1mh2l27wgfrbtjnywhpk2kcngu4cqr44...@mail.gmail.com
Bug#697649: marked as done (pre-approve for freeze exception: snacc 1.3.1-2)
Your message dated Tue, 8 Jan 2013 21:21:05 +0100 with message-id CAK0Odpzm=0u0f-c1mh2l27wgfrbtjnywhpk2kcngu4cqr44...@mail.gmail.com and subject line Re: Bug#697649: pre-approve for freeze exception: snacc 1.3.1-2 has caused the Debian Bug report #697649, regarding pre-approve for freeze exception: snacc 1.3.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.) -- 697649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697649 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: freeze-exception Dear Release Team, I would like to update the snacc package enabling multiarch for the shipped libraries. The debdiff also adds a watch file which I can remove if its presence blocks getting the freeze exception. Changes: snacc (1.3.1-2) unstable; urgency=low . [ Bart Martens ] * add watch file . [ Balint Reczey ] * multiarch support Cheers, Balint snacc-1.3.1-1-1.3.1-2.debdiff Description: Binary data ---End Message--- ---BeginMessage--- 2013/1/8 Adam D. Barratt a...@adam-barratt.org.uk: On Tue, 2013-01-08 at 01:20 +0100, Bálint Réczey wrote: I would like to update the snacc package enabling multiarch for the shipped libraries. I'm afraid it's too late for such changes to make it to wheezy imo. I'm also not sure what the rationale would be for wheezy - the only user in the archive appears to be wireshark, which doesn't seem like the sort of application one would install multiple architectures of simultaneously. OK. I agree that it is not really important to update snacc. I'll upload the new package after the release. Cheers, Balint---End Message---
Bug#695642: pu: package magpierss/0.72-8+squeeze2
Control: tags 694052 pending On 2013-01-08 17:09, Marcelo Jorge Vieira wrote: Hi Niels, On Sun, 2013-01-06 at 23:15 +0100, Niels Thykier wrote: Looks good; please let us know when you have uploaded it. Uploaded! Cheers, Flagged for acceptance, thanks. ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50ec9477.8030...@thykier.net
Processed: tagging 695642
Processing commands for cont...@bugs.debian.org: tags 695642 + pending Bug #695642 [release.debian.org] pu: package magpierss/0.72-8+squeeze2 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 695642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695642 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: http://lists.debian.org/handler.s.c.13576819647990.transcr...@bugs.debian.org
Bug#683053: marked as done (unblock: python2.7/2.7.3-2)
Your message dated Tue, 8 Jan 2013 23:06:22 +0100 with message-id 20130108220622.gb5...@radis.cristau.org and subject line Re: Bug#683053: unblock: python2.7/2.7.3-2 has caused the Debian Bug report #683053, regarding unblock: python2.7/2.7.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.) -- 683053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683053 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 python2.7 On balance, I think it's better to accept the newer python2.7 than not. I'm finally motivated to file this bug (instead of randomly hoping jcristau will feel motivated to do it) because of an RC issue that came up in Ubuntu today and affects Wheezy, but not Unstable in Debian (683050). As far as I know, the only issue that's come up with the 2.7.3-2 is the urlparse module where they simplified it and dropped some options which gave some packages a bit of trouble. It appears jwilk did a systematic sweep for packages that were affected by this (I say it seems because I haven't caught him online recently to ask, but everywhere I found the issue, he'd already filed a bug). All of these except three, because they weren't on their own RC (in some cases the change really broke packages, in others the impact was less so). Still open are #682148, #682150, and #679454. The first two are not RC and I didn't NMU gwibber (the last one) because it seems pretty broken in its current state and the maintainers said they're preparing a new upstream that already has this fixed. On a related note, #682603 is an unblock for one of these fixes that's waiting for approval. In addition to thinking releasing with the newer python2.7 udpate is a good idea, that would also unblock python-defaults (unblock pending as #682906). As I mentioned there, I think we definitely want those changes in. My recommendation is that you unblock python2.7, but increase the age requirement to 30 days (it's at 14 righ now) and that you also unblock linkchecker (#682603) and I'll NMU pegasus-wm, createrepo, and gwibber, file fore unblocks, etc. In each case the diff is very compact (similar to #682603 in scope). With python2.7 having two weeks to go, this was all the fixed packages can migrate with or before python2.7 so it can be a smooth switch (the fixed packages work fine with either the python2.7 in wheezy or unstable there's no need to tightly coordinate things. unblock python2.7/2.7.3-2 ---End Message--- ---BeginMessage--- On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python2.7 Unblocked 2.7.3-6. Cheers, Julien signature.asc Description: Digital signature ---End Message---
NEW changes in stable-new
Processing changes file: magpierss_0.72-8+squeeze2_i386.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tshfe-0007rd...@franck.debian.org
Bug#697726: unblock: vinagre/3.4.2-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package vinagre. Version 3.4.2-2 fixes important bug #696701.
The debdiff is attached.
unblock vinagre/3.4.2-2
Cheers,
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://www.dynare.org/sebastien
`- GPG Key: 4096R/381A7594
diff -Nru vinagre-3.4.2/debian/changelog vinagre-3.4.2/debian/changelog
--- vinagre-3.4.2/debian/changelog 2012-05-15 19:01:06.0 +0200
+++ vinagre-3.4.2/debian/changelog 2013-01-08 21:25:05.0 +0100
@@ -1,3 +1,11 @@
+vinagre (3.4.2-2) unstable; urgency=low
+
+ * Team upload.
+ * debian/patches/fix-vnc-through-ssh.patch: new patch, fixes VNC
+tunneling through SSH. Closes: #696701
+
+ -- Sébastien Villemot sebast...@debian.org Tue, 08 Jan 2013 21:24:48 +0100
+
vinagre (3.4.2-1) unstable; urgency=low
* New upstream translation release.
diff -Nru vinagre-3.4.2/debian/patches/fix-vnc-through-ssh.patch vinagre-3.4.2/debian/patches/fix-vnc-through-ssh.patch
--- vinagre-3.4.2/debian/patches/fix-vnc-through-ssh.patch 1970-01-01 01:00:00.0 +0100
+++ vinagre-3.4.2/debian/patches/fix-vnc-through-ssh.patch 2013-01-08 20:52:08.0 +0100
@@ -0,0 +1,137 @@
+Description: Fix VNC tunneling through SSH
+ Use GPollableInputStream when checking for SSH errors. Otherwise the read on
+ stderr blocks, causing the SSH connection to timeout.
+ .
+ The original code sets O_NONBLOCK on stderr, but this does not work: the flag
+ is not propagated to the corresponding GDataInputStream (at least with glib =
+ 2.32; it may have worked with older versions).
+ .
+ As a side effect, the patch fixes a minor memory leak in
+ vinagre-ssh.c:look_for_stderr_errors() where the line variable was not
+ correctly freed in all cases.
+Author: Sébastien Villemot sebast...@debian.org
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=690449
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696701
+Applied-Upstream: 3.6.3, http://git.gnome.org/browse/vinagre/commit/?h=gnome-3-6id=5f0688183974e3d5d055b8d136c1ac7ee6e3041c
+Last-Update: 2013-01-08
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/vinagre/vinagre-ssh.c
b/vinagre/vinagre-ssh.c
+@@ -667,17 +667,30 @@
+ }
+
+ static gboolean
+-look_for_stderr_errors (GDataInputStream *error_stream, GError **error)
++look_for_stderr_errors (GInputStream *is, GError **error)
+ {
+- char *line;
++ GDataInputStream *error_stream;
++ char *line = NULL;
++ gboolean ret;
++
++ error_stream = g_data_input_stream_new (is);
+
+ while (1)
+ {
++#ifndef G_OS_WIN32
++ if (!g_pollable_input_stream_is_readable (G_POLLABLE_INPUT_STREAM (is)))
++{
++ ret = TRUE;
++ break;
++}
++#endif
++
+ line = g_data_input_stream_read_line (error_stream, NULL, NULL, NULL);
+
+ if (line == NULL)
+ {
+- return TRUE;
++ ret = TRUE;
++ break;
+ }
+
+ if (strstr (line, Permission denied) != NULL)
+@@ -685,41 +698,49 @@
+ g_set_error_literal (error,
+ VINAGRE_SSH_ERROR, VINAGRE_SSH_ERROR_PERMISSION_DENIED,
+ _(Permission denied));
+- return FALSE;
++ ret = FALSE;
++ break;
+ }
+ else if (strstr (line, Name or service not known) != NULL)
+ {
+ g_set_error_literal (error,
+ VINAGRE_SSH_ERROR, VINAGRE_SSH_ERROR_HOST_NOT_FOUND,
+ _(Hostname not known));
+- return FALSE;
++ ret = FALSE;
++ break;
+ }
+ else if (strstr (line, No route to host) != NULL)
+ {
+ g_set_error_literal (error,
+ VINAGRE_SSH_ERROR, VINAGRE_SSH_ERROR_HOST_NOT_FOUND,
+ _(No route to host));
+- return FALSE;
++ ret = FALSE;
++ break;
+ }
+ else if (strstr (line, Connection refused) != NULL)
+ {
+ g_set_error_literal (error,
+ VINAGRE_SSH_ERROR, VINAGRE_SSH_ERROR_PERMISSION_DENIED,
+ _(Connection refused by server));
+- return FALSE;
++ ret = FALSE;
++ break;
+ }
+ else if (strstr (line, Host key verification failed) != NULL)
+ {
+ g_set_error_literal (error,
+ VINAGRE_SSH_ERROR, VINAGRE_SSH_ERROR_FAILED,
+ _(Host key verification failed));
+- return FALSE;
++ ret = FALSE;
++ break;
+ }
+
+- g_free (line);
+ }
+
+- return TRUE;
++ if (line)
++g_free (line);
++
++ g_object_unref (error_stream);
++ return ret;
+ }
+
+ gboolean
+@@ -737,7 +758,6 @@
+ gchar *user, *host, **args;
+ gboolean res;
+ GInputStream *is;
+- GDataInputStream *error_stream;
+
+ if
Bug#693924: unblock: ltsp/5.4.2-4
On Sun, Jan 06, 2013 at 11:40:29PM +0100, Julien Cristau wrote: On Wed, Nov 21, 2012 at 12:02:39 -0800, Vagrant Cascadian wrote: +- Fix initramfs udhcp hook to use /run instead of /tmp, which allows the + booting from a network using PXE ProxyDHCP (Closes: #693746). This requires initramfs-tools 0.99 AFAICT, there's no /run before that. Thanks for the review. The patch makes an attempt at implementing backwards compatibility, but looking into it, it may fail if /run is not present. Bumping the versioned dependency on initramfs-tools would be simple enough, if that was needed, alternately it wouldn't be hard to update the patch to ensure /run is present (a simple mkdir -p /run should do it). Any preference on that? live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130108222852.GA6011@talon.fglan
Bug#693924: unblock: ltsp/5.4.2-4
On Tue, Jan 8, 2013 at 14:28:52 -0800, Vagrant Cascadian wrote: On Sun, Jan 06, 2013 at 11:40:29PM +0100, Julien Cristau wrote: On Wed, Nov 21, 2012 at 12:02:39 -0800, Vagrant Cascadian wrote: +- Fix initramfs udhcp hook to use /run instead of /tmp, which allows the + booting from a network using PXE ProxyDHCP (Closes: #693746). This requires initramfs-tools 0.99 AFAICT, there's no /run before that. Thanks for the review. The patch makes an attempt at implementing backwards compatibility, but looking into it, it may fail if /run is not present. Bumping the versioned dependency on initramfs-tools would be simple enough, if that was needed, alternately it wouldn't be hard to update the patch to ensure /run is present (a simple mkdir -p /run should do it). Any preference on that? I'd prefer the versioned dep, if you don't mind. Thanks, Julien signature.asc Description: Digital signature
Processed: Re: Bug#697434: pu: package gzip/1.3.12-9+deb6u0
Processing control commands: tags -1 + pending Bug #697434 [release.debian.org] pu: package gzip/1.3.12-9+deb6u0 Added tag(s) pending. -- 697434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697434 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: http://lists.debian.org/handler.s.b697434.13576860254476.transcr...@bugs.debian.org
Bug#697434: pu: package gzip/1.3.12-9+deb6u0
Control: tags -1 + pending On Mon, 2013-01-07 at 00:11 +0100, Niels Thykier wrote: On 2013-01-06 23:32, Adam D. Barratt wrote: On Sat, 2013-01-05 at 11:47 +0100, Niels Thykier wrote: +gzip (1.3.12-9+deb6u0) UNRELEASED; urgency=low + + * Non-maintainer upload to stable. + * Backport upstream patch to avoid using memcpy on overlapping +memory regions. (Closes: #627121) [...] Uploaded as gzip_1.3.12-9+squeeze1, been tested in a run of the Lintian 2.4.3+squeeze1 test suite in Squeeze 6.0.6. :) Flagged for acceptance; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1357686014.4189.20.ca...@jacala.jungle.funky-badger.org
Bug#692734: unblock: ettercap/0.7.5-4
That is a matter of release policy. I believe I've made clear my own recommended action, listed the alternative possibilities I consider realistic, and given supporting reasoning. After that, this becomes a matter for the release team to decide. They can take my recommendation, or do something else, as they wish. It is ridiculous process-over-sense to say that the release team should ask me, via your sending me your interpretation of their policy document, to ask them to do something which you think they've already decided to do. (Especially when I don't think what you seem to think they've already decided to do is the best option.) After all, if they have decided to do something, they can just do it. We're trying to produce a good operating system here, not an improv parody of paralyzing procedure-heavy bureaucratic inertia. It's a bit frustrating to see that the release gets delayed because of situations like these. Ettercap is a minor leaf package. This issue is not a release delayer. --Barak. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/871udvs2e8@cs.nuim.ie
NEW changes in stable-new
Processing changes file: gzip_1.3.12-9+squeeze1_i386.changes ACCEPT Processing changes file: zendframework_1.10.6-1squeeze2_amd64.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tsibj-0006ek...@franck.debian.org
Bug#682906: unblock: python-defaults/2.7.3-2
On Monday, December 31, 2012 04:49:08 PM Jonathan Nieder wrote: ... If someone is interested in getting some appropriate subset of these changes well tested for wheezy, I suspect the next step is to prepare an upload for tpu that does not bump the python2.7 requirement. python2.7 is unblocked now, so I think this is OBE. Is there anything else that needs to be done to get this unblocked? Scott K -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3575671.SXCbgu6huv@scott-latitude-e6320
Bug#697667: unblock: opendkim/2.6.8-4
On Tuesday, January 08, 2013 07:52:26 PM Julien Cristau wrote: Control: tag -1 confirmed On Tue, Jan 8, 2013 at 02:55:00 -0500, Scott Kitterman wrote: Please let me know if this is OK and if so, I'm prepared to upload right away. Go ahead. Thanks, uploaded. Scott K signature.asc Description: This is a digitally signed message part.
NEW changes in stable-new
Processing changes file: gzip_1.3.12-9+squeeze1_amd64.changes ACCEPT Processing changes file: gzip_1.3.12-9+squeeze1_kfreebsd-i386.changes ACCEPT Processing changes file: gzip_1.3.12-9+squeeze1_mipsel.changes ACCEPT Processing changes file: gzip_1.3.12-9+squeeze1_powerpc.changes ACCEPT Processing changes file: gzip_1.3.12-9+squeeze1_s390.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tsma5-0001xi...@franck.debian.org
NEW changes in stable-new
Processing changes file: gzip_1.3.12-9+squeeze1_mips.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tsmoa-0004wp...@franck.debian.org
NEW changes in stable-new
Processing changes file: gzip_1.3.12-9+squeeze1_kfreebsd-amd64.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tsn69-0008sl...@franck.debian.org
NEW changes in stable-new
Processing changes file: gzip_1.3.12-9+squeeze1_armel.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tsnza-0005vd...@franck.debian.org
NEW changes in stable-new
Processing changes file: gzip_1.3.12-9+squeeze1_sparc.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tsojl-0003kq...@franck.debian.org
Processed: Re: Bug#693924: unblock: ltsp/5.4.2-5
Processing control commands: retitle -1 unblock: ltsp/5.4.2-5 Bug #693924 [release.debian.org] unblock: ltsp/5.4.2-4 Changed Bug title to 'unblock: ltsp/5.4.2-5' from 'unblock: ltsp/5.4.2-4' -- 693924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693924 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: http://lists.debian.org/handler.s.b693924.13577153178152.transcr...@bugs.debian.org
Bug#693924: unblock: ltsp/5.4.2-5
Control: retitle -1 unblock: ltsp/5.4.2-5 On Tue, Jan 08, 2013 at 11:35:45PM +0100, Julien Cristau wrote: On Tue, Jan 8, 2013 at 14:28:52 -0800, Vagrant Cascadian wrote: On Sun, Jan 06, 2013 at 11:40:29PM +0100, Julien Cristau wrote: On Wed, Nov 21, 2012 at 12:02:39 -0800, Vagrant Cascadian wrote: +- Fix initramfs udhcp hook to use /run instead of /tmp, which allows the + booting from a network using PXE ProxyDHCP (Closes: #693746). This requires initramfs-tools 0.99 AFAICT, there's no /run before that. Thanks for the review. The patch makes an attempt at implementing backwards compatibility, but looking into it, it may fail if /run is not present. Bumping the versioned dependency on initramfs-tools would be simple enough, if that was needed, alternately it wouldn't be hard to update the patch to ensure /run is present (a simple mkdir -p /run should do it). Any preference on that? I'd prefer the versioned dep, if you don't mind. Uploaded: ltsp (5.4.2-5) unstable; urgency=low * ltsp-client-core: Depend on initramfs-tools 0.99, to ensure /run is available in the initramfs. -- Vagrant Cascadian vagr...@debian.org Tue, 08 Jan 2013 22:00:39 -0800 Please unblock it. Thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130109070830.GC6011@talon.fglan
