Bug#683052: unblock: pgbouncer/1.5.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pgbouncer. pgbouncer (1.5.2-2) unstable; urgency=low * Init script: Use --oknodo. Closes: #681978. Create /var/run/postgresql when missing. Closes: #681372. -- Christoph Berg m...@debian.org Thu, 26 Jul 2012 13:12:23 +0200 681978 is serious, 681372 is important. Thanks. unblock pgbouncer/1.5.2-2 Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#683053: unblock: python2.7/2.7.3-2
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 -- 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/20120728073951.357.96134.reportbug@Scott-Latitude-E6320
Bug#681196: unblock: tryton-proteus/2.2.2-4
tag 681196 - moreinfo thanks On Wed, Jul 11, 2012 at 12:11:14 +0200, Mathias Behrle wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package tryton-proteus. The -3 upload fixes the #680817 FTBFS, revealed by a Lucas-powered rebuild. 680817 is still open. Cheers, Julien Removing tag moreinfo, which seems to keep this issue out of the scope of the release team. Cheers, Mathias signature.asc Description: PGP signature
Bug#675762: marked as done (RM: python-cdb -- RoM; licensing issues)
Your message dated Sat, 28 Jul 2012 08:41:17 + with message-id 20120728084117.gc6...@master.debian.org and subject line RM: python-cdb -- RoM; licensing issues has caused the Debian Bug report #675762, regarding RM: python-cdb -- RoM; licensing issues 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.) -- 675762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ftp.debian.org Severity: normal Please remove python-cdb from unstable, testing and stable. The software cdb at http://cr.yp.to/cdb.html has this information for distributors: | You may distribute unmodified copies of the cdb package. Packages that need to | read cdb files should incorporate the necessary portions of the cdb library | rather than relying on an external cdb library. The software python-cdb contains a modified copy of part of the software cdb. The files cdb-0.75/cdb.c and python-cdb-0.34/src/cdb.c are different. The file python-cdb-0.34/src/cdb.c contains these lines: | /* Public domain. */ | /* Adapted from DJB's original cdb-0.75 package */ So the software python-cdb must not be distributed, so must not be in Debian. Regards, Bart Martens ---End Message--- ---BeginMessage--- On Fri, Jul 27, 2012 at 04:17:21PM -0700, Russ Allbery wrote: I similarly don't agree with Rune's analysis, but djb later changed the license in a separate statement on his web site (he did it for nearly all of his projects), which clearly does state that all the files are now public domain. So there's no need to parse that statement; it's thankfully been superseded. I find the following on the website and in the tarball : http://cr.yp.to/distributors.html | 2009.07.21: I hereby place the cdb package (in particular, cdb-0.75.tar.gz, | with MD5 checksum 81fed54d0bde51b147dd6c20cdb92d51) into the public domain. The | package is no longer copyrighted. http://cr.yp.to/cdb.html | Information for distributors | You may distribute unmodified copies of the cdb package. cdb-0.75/README: | cdb 0.75, beta. | 2219 | Copyright 2000 | D. J. Bernstein | | cdb home page: http://cr.yp.to/cdb.html | Installation instructions: http://cr.yp.to/cdb/install.html grep -riI public cdb-0.75 | cdb-0.75/cdb.h:/* Public domain. */ | cdb-0.75/cdb.c:/* Public domain. */ | cdb-0.75/cdb_make.h:/* Public domain. */ | cdb-0.75/cdb_hash.c:/* Public domain. */ | cdb-0.75/cdb_make.c:/* Public domain. */ md5sum cdb-0.75.tar.gz 81fed54d0bde51b147dd6c20cdb92d51 cdb-0.75.tar.gz At this point I think that it is reasonable to assume that the software has been copyrighted in the past (2219) and that D. J. Bernstein has had the intention on 2009.07.21 to make it unconditionally public domain. I'm closing this bug now. Regards, Bart Martens---End Message---
Bug#683052: marked as done (unblock: pgbouncer/1.5.2-2)
Your message dated Sat, 28 Jul 2012 11:01:42 +0200 with message-id 5013aa76.1050...@thykier.net and subject line Re: Bug#683052: unblock: pgbouncer/1.5.2-2 has caused the Debian Bug report #683052, regarding unblock: pgbouncer/1.5.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.) -- 683052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683052 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 pgbouncer. pgbouncer (1.5.2-2) unstable; urgency=low * Init script: Use --oknodo. Closes: #681978. Create /var/run/postgresql when missing. Closes: #681372. -- Christoph Berg m...@debian.org Thu, 26 Jul 2012 13:12:23 +0200 681978 is serious, 681372 is important. Thanks. unblock pgbouncer/1.5.2-2 Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On 2012-07-28 09:27, Christoph Berg wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pgbouncer. pgbouncer (1.5.2-2) unstable; urgency=low * Init script: Use --oknodo. Closes: #681978. Create /var/run/postgresql when missing. Closes: #681372. -- Christoph Berg m...@debian.org Thu, 26 Jul 2012 13:12:23 +0200 681978 is serious, 681372 is important. Thanks. unblock pgbouncer/1.5.2-2 Christoph Unblocked, thanks. ~Niels---End Message---
Re: w3af (Re: pysvn: RC fix #678559 as new upstream release)
Adding the w3af maintainer to recipients. On Sat, Jul 28, 2012 at 09:55:50 +0900, Hideki Yamane wrote: Hi, Have you tested the reverse dependencies with the new version (seems to be svn-workbench, svn-load, , ibid, There's no reply from w3af maintainer so I've investigated it and there is not a problem with updating pysvn. w3af uses pysvn for update only, and its feature shouldn't work in Debian. w3af needs pysvn to use auto-update feature, and it is not suitable for Debian package binary. Debian w3af packages are installed into system wide, not user's directory. So, if unprivilledged user would execute update, w3af files would not be overwritten. However, I've found this package needs to be patched, and also it's not up-to-date upstream stable version (1.1) in testing/unstable (=1.0-rc3svn3489-1) (even experimental=1.0.0-1). Outdated program is not good for users (and also maintainer/security team), but there are 250 w3af users (by popcon), just removing package is not good for them. --- choices for w3af) --- 1. Not touch w3af - easiest way - needs simple patch to work with python2.6, at least (Debian doesn't have python2.5 anymore, and its source says it supports 2.6, not 2.7) - outdated version (2 years ago), maybe not useful for users 2. Just remove w3af from testing - easy - no reverse dependency - users cannot use w3af since Wheezy 3. update w3af - violate basic freeze rule (however, upstream 1.1 was released before freeze, 2011-11-10) - need some work to update (I'll try) - need some check if it works Any comments? -- Hideki Yamane henr...@debian.or.jp -- 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/20120728095550.ab97ba1d8b906dd8912c8...@debian.or.jp signature.asc Description: Digital signature
Bug#683044: marked as done (unblock: rhythmbox/2.97-2.1)
Your message dated Sat, 28 Jul 2012 10:09:51 +0100 with message-id 1343466591.18013.45.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#683044: unblock: rhythmbox/2.97-2.1 has caused the Debian Bug report #683044, regarding unblock: rhythmbox/2.97-2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 683044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683044 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 rhythmbox Fixes RC/security bug #616673. unblock rhythmbox/2.97-2.1 diff -Nru rhythmbox-2.97/debian/changelog rhythmbox-2.97/debian/changelog --- rhythmbox-2.97/debian/changelog 2012-06-20 01:38:10.0 -0400 +++ rhythmbox-2.97/debian/changelog 2012-07-27 21:42:01.0 -0400 @@ -1,3 +1,18 @@ +rhythmbox (2.97-2.1) unstable; urgency=high + + * Non-maintainer upload. + * Urgency high for security fix + * fix insecure directory for python module import in context plugin +(Closes: #616673) +- debian/patches/CVE-2012-3355.patch: update context plugin to use + tempfile.mkdtemp() instead of /tmp/context. Patch thanks to Andreas + Henriksson (used theUbuntu security fix instead of the upstream commit + because the upstream commit was a mix of functional changes and a + security fix)) +- CVE-2012-3355 + + -- Scott Kitterman sc...@kitterman.com Fri, 27 Jul 2012 16:41:52 -0400 + rhythmbox (2.97-2) unstable; urgency=low [ Jon Dowland ] diff -Nru rhythmbox-2.97/debian/patches/CVE-2012-3355.patch rhythmbox-2.97/debian/patches/CVE-2012-3355.patch --- rhythmbox-2.97/debian/patches/CVE-2012-3355.patch 1969-12-31 19:00:00.0 -0500 +++ rhythmbox-2.97/debian/patches/CVE-2012-3355.patch 2012-07-27 16:40:00.0 -0400 @@ -0,0 +1,100 @@ +Origin: http://bugzilla-attachments.gnome.org/attachment.cgi?id=218103 +Author: Andreas Henriksson andr...@fatal.se +Description: use mkdtemp to securely create temp dir +Bug: https://bugzilla.gnome.org/process_bug.cgi +Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616673 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=835076 + +Index: rhythmbox-2.96/plugins/context/AlbumTab.py +=== +--- rhythmbox-2.96.orig/plugins/context/AlbumTab.py 2012-03-10 04:22:26.0 -0600 rhythmbox-2.96/plugins/context/AlbumTab.py 2012-07-09 10:53:07.0 -0500 +@@ -126,9 +126,9 @@ + self.path = rb.find_plugin_file (self.plugin, 'tmpl/album-tmpl.html') + self.loading_path = rb.find_plugin_file (self.plugin, 'tmpl/loading.html') + self.album_template = Template (filename = self.path, +-module_directory = '/tmp/context') ++module_directory = self.plugin.tempdir) + self.loading_template = Template (filename = self.loading_path, +- module_directory = '/tmp/context') ++ module_directory = self.plugin.tempdir) + self.styles = self.basepath + '/tmpl/main.css' + + def album_list_ready (self, ds): +Index: rhythmbox-2.96/plugins/context/ArtistTab.py +=== +--- rhythmbox-2.96.orig/plugins/context/ArtistTab.py 2012-03-10 04:22:26.0 -0600 rhythmbox-2.96/plugins/context/ArtistTab.py 2012-07-09 10:53:07.0 -0500 +@@ -123,8 +123,8 @@ + def load_tmpl (self): + self.path = rb.find_plugin_file(self.plugin, 'tmpl/artist-tmpl.html') + self.loading_path = rb.find_plugin_file (self.plugin, 'tmpl/loading.html') +-self.template = Template (filename = self.path, module_directory = '/tmp/context/') +-self.loading_template = Template (filename = self.loading_path, module_directory = '/tmp/context') ++self.template = Template (filename = self.path, module_directory = self.plugin.tempdir) ++self.loading_template = Template (filename = self.loading_path, module_directory = self.plugin.tempdir) + self.styles = self.basepath + '/tmpl/main.css' + + def connect_signals (self): +Index: rhythmbox-2.96/plugins/context/context.py +=== +--- rhythmbox-2.96.orig/plugins/context/context.py 2012-02-12 00:13:11.0 -0600 rhythmbox-2.96/plugins/context/context.py 2012-07-09 10:53:07.0 -0500 +@@ -26,6
Bug#681196: marked as done (unblock: tryton-proteus/2.2.2-4)
Your message dated Sat, 28 Jul 2012 11:15:41 +0200 with message-id 20120728091541.gg10...@radis.cristau.org and subject line Re: Bug#681196: unblock: tryton-proteus/2.2.2-3 has caused the Debian Bug report #681196, regarding unblock: tryton-proteus/2.2.2-4 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.) -- 681196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681196 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 tryton-proteus. The -3 upload fixes the #680817 FTBFS, revealed by a Lucas-powered rebuild. unblock tryton-proteus/2.2.2-3 debdiff attached tryton-proteus_2.2.2-3.debdiff Description: Binary data signature.asc Description: PGP signature ---End Message--- ---BeginMessage--- On Wed, Jul 11, 2012 at 12:11:14 +0200, Mathias Behrle wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package tryton-proteus. The -3 upload fixes the #680817 FTBFS, revealed by a Lucas-powered rebuild. Does #680817 affect the version in testing? The BTS doesn't think so, and looking at the changes in proteus/pyson.py and setup.py I guess not. Now on to the changes themselves: --- tryton-proteus-2.2.1/debian/compat 2011-12-26 12:35:55.0 + +++ tryton-proteus-2.2.2/debian/compat 2012-07-11 09:31:06.0 + @@ -1 +1 @@ -8 +9 This is not ok during freeze. --- tryton-proteus-2.2.1/debian/rules 2011-12-26 12:35:55.0 + +++ tryton-proteus-2.2.2/debian/rules 2012-07-11 09:31:06.0 + @@ -7,3 +7,6 @@ dh_auto_clean rm -rf *.egg-info + +override_dh_builddeb: + dh_builddeb -- -Zxz -z9 neither is this, really. So with no RC or important bug fix that I know of in this version, I'm afraid I'm going to have to say no, sorry. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#681196: unblock: tryton-proteus/2.2.2-3
On Wed, 2012-07-11 at 12:11 +0200, Mathias Behrle wrote: Please unblock package tryton-proteus. The -3 upload fixes the #680817 FTBFS, revealed by a Lucas-powered rebuild. So far as I can see, that bug doesn't apply to the version of tryton-proteus in wheezy: $ egrep -ir dateutil tryton-proteus-2.2.1-1/ $ Is that correct, or am I missing something? 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/1343467068.18013.48.ca...@jacala.jungle.funky-badger.org
Re: Freeze exception for lightspeed/1.2a-9
On Fri, Jul 6, 2012 at 21:29:08 +0300, Boris Pek wrote: Dear release team, I ask for a freeze exception for lightspeed version 1.2a-9. I have prepared few QA uploads. But unfortunately not all of them were sponsored before freeze [1]. This update of the package does not fix any RC bug, but it fixes important, normal and minor bugs. Also the quality of package was improved in common. File in attachment was produced using command: $ debdiff lightspeed_1.2a-8.dsc lightspeed_1.2a-9.dsc | \ filterdiff -x '*config.guess' -x '*config.sub' lightspeed_1.2a-8:1.2a-9.diff It would be nice to see this updated package in Wheezy. I'm afraid a completely rewritten packaging is very much not appropriate during the freeze. Cheers, Julien signature.asc Description: Digital signature
Re: Freeze exception for qpxtool/0.7.1.002-6
On Fri, Jul 6, 2012 at 21:42:40 +0300, Boris Pek wrote: Dear release team, I ask for a freeze exception for qpxtool version 0.7.1.002-6. I have prepared few QA uploads. But unfortunately not all of them were sponsored before freeze [1]. This update of the package does not fix any RC bug, but it fixes important and wishlist bugs. Also the quality of package was improved in common. File in attachment was produced using command: $ debdiff qpxtool_0.7.1.002-5.dsc qpxtool_0.7.1.002-6.dsc qpxtool_0.7.1.002-5:0.7.1.002-6.diff It would be nice to see this updated package in Wheezy. Best regards, Boris [1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?include=subject%3A[QA];package=sponsorship-requests diff -Nru qpxtool-0.7.1.002/debian/changelog qpxtool-0.7.1.002/debian/changelog --- qpxtool-0.7.1.002/debian/changelog2011-06-21 14:04:14.0 +0300 +++ qpxtool-0.7.1.002/debian/changelog2012-06-26 03:13:59.0 +0300 @@ -1,3 +1,24 @@ +qpxtool (0.7.1.002-6) unstable; urgency=low + + * QA upload. + * Bumped Standards-Version to 3.9.3 (was 3.9.2). + * Bumped debhelper version to 9 (was 7.0.50~); updated debian/compat. This is not ok. + * Added file debian/patches/05-add-hardening-flags-in-compiler-options.patch. + * Updated debian/rules: added hardening flags in compiler options. + * Changed build dependency from libpng12-dev to libpng-dev. +Added file debian/patches/04-fix-build-with-libpng15.patch. +Added small hack in debian/rules (see LIBPNG_VER variable). +Build with libpng version 1.5.10 was tested successfully. +(Closes: #662481, #648127) The hack is unneeded, -lpng should work fine AFAIK. + * Used [kfreebsd-any] instead of hardcoded list of kFreeBSD architectures +[kfreebsd-i386 kfreebsd-amd64] in build dependency. (Closes: #634714) + * File debian/copyright was updated in according to Copyright format 1.0. + * Fixed such lintian warnings and notes: +- out-of-date-copyright-format-uri +- hardening-no-relro and hardening-no-fortify-functions + + -- Boris Pek tehnic...@mail.ru Tue, 26 Jun 2012 03:11:10 +0300 + So I don't think I would accept this, sorry. Cheers, Julien signature.asc Description: Digital signature
Re: Freeze exception for awffull/3.10.2-2
Hi Boris,
I'm just looking at the changelog here, in case you're still interested
in doing this.
On Fri, Jul 6, 2012 at 22:11:13 +0300, Boris Pek wrote:
diff -Nru awffull-3.10.2/debian/changelog awffull-3.10.2/debian/changelog
--- awffull-3.10.2/debian/changelog 2012-01-01 11:16:10.0 +0200
+++ awffull-3.10.2/debian/changelog 2012-06-29 23:45:51.0 +0300
@@ -1,3 +1,47 @@
+awffull (3.10.2-2) unstable; urgency=low
+
+ * QA upload.
+ * Bumped Standards-Version to 3.9.3 (was 3.7.3).
+ * Bumped debhelper version to 9 (was 8); updated debian/compat.
Not ok.
+ * Added file debian/patches/fix-GeoIP-default-path.patch:
+fixed default path to GeoIP database. (Closes: #458647)
+ * Added file debian/patches/fix-quietly-run-of-cron-job.patch:
+disables useless output messages when job is run without any verbose
+options. (Closes: #665680)
These two would probably be ok on their own.
+ * Added file debian/patches/fix-font-in-use.patch:
+- now recommended font ttf-dejavu is used instead of bitstream-vera
+ font which is going to be removed from the repository
+- fixed path to used font (Closes: #458647)
Wrong bug number? This one is about the geoip db above.
+ * Updated debian/templates: switched from apache to apache2.
+(Closes: #467641)
Probably ok.
+ * Updated debian/awffull.cron.daily:
+- deleted useless output message when cron job runs without errors
+ (Closes: #482168)
+- updated notifications for more correct messages
+ (Closes: #565813)
Probably ok.
+ * Updated debian/control:
+- awffull now suggests ttf-dejavu
+- changed build dependency from libpng12-dev to libpng-dev
+ (Closes: #662274)
First one probably ok depending on the related change above, second one
not needed for wheezy but probably harmless.
+ * Rewritten debian/rules:
+- now dh is used instead of direct dh_* commands
+- added --as-needed option to LDFLAGS
+- added section get-orig-source (uscan is used)
+- fixed FTBFS because of outdated config.{sub,guess}:
+ used symlinks to files from autotools-dev package
+ (Closes: #536835)
+- fixed lintian warnings:
+ + hardening-no-relro
+ + hardening-no-fortify-functions
NAK.
+ * Added file debian/awffull.lintian-overrides:
+possible-bashism-in-maintainer-script warning is false positive.
+ * Added file debian/patches/fix-hyphen-used-as-minus-sign.patch.
+ * File debian/copyright was rewritten in according to Copyright format 1.0.
+Added missed licenses and copyright holders. Fixed lintian note:
+copyright-refers-to-symlink-license usr/share/common-licenses/GPL.
Weak NAK to the copyright rewrite.
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#682960: unblock (pre-approval): gnome-shell/3.4.2-1
Le Fri, 27 Jul 2012 19:47:41 -0400,
Mike Miller mtmil...@ieee.org a écrit :
On Sat, Jul 28, 2012 at 12:44:13AM +0200, Michael Biebl wrote:
Am 28.07.2012 00:31, schrieb Mike Miller:
Just happened to spot this, sorry if I'm intruding, but how about
fixing RC bug #681737 in this release? It's an easy cherry-pick
patch, fuzz-free, I've been running with this patch applied for
over a week with no problems.
While we should definitely fix this issue for wheezy, the upstream
patch only works, if we update *all* NM vpn plugins to supply an
absolute path in their corresponding .name file. (I assume you
manually patched the .name file on your local system?)
Yes.
It might be easier to just change gnome-shell to look for the
vpn-auth-dialogs in /usr/lib/NetworkManager instead of
Config.LIBEXECDIR (which expands to /usr/lib/gnome-shell).
True enough. That was how I was looking at it until I ran across the
upstream bug report. Solving it that way is slightly more coordination
now, but it's future-proof and less coordination later.
If you all decide hardcoding gnome-shell to /usr/lib/NetworkManager is
the best for wheezy, that's fine too.
I think both should be done as some VPN modules (like nm-strongswan)
are already using a full path.
I've added the following patch to the package. I'm waiting RT ack
before pushing everything to the svn.
=8==
Description: Use Debian specific NM VPN helpers paths
Author: Laurent Bigonville bi...@debian.org
Forwarded: not-needed
--- a/js/ui/networkAgent.js
+++ b/js/ui/networkAgent.js
@@ -685,7 +685,7 @@ const NetworkAgent = new Lang.Class({
} catch(e) { } // ignore errors if key does not exist
let path = binary;
if (!GLib.path_is_absolute(path)) {
-path = GLib.build_filenamev([Config.LIBEXECDIR, path]);
+path =
GLib.build_filenamev(['/usr/lib/NetworkManager/VPN', path]);
}
if (GLib.file_test(path, GLib.FileTest.IS_EXECUTABLE))
8===
Cheers
Laurent Bigonville
--
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/20120728115106.4f5eb...@eldamar.bigon.be
Bug#683063: unblock: sparkleshare/0.9.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package sparkleshare Release 0.9.0 (and the -1 package) has a bug in its status icon code that causes it to disappear and reappear instead of showing an animation (which also causes the rest of the icons to move around). The sparkleshare bug is #682070. unblock sparkleshare/0.9.0-2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-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 -- 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/20120728094853.12970.65940.report...@centaur.cmartin.tk
Re: Next upload 2012-06-26 (dpkg 1.16.5)
On Mon, Jul 23, 2012 at 07:18:29PM +0200, Guillem Jover wrote: On Mon, 2012-07-23 at 17:51:56 +0100, Neil McGovern wrote: Nope, 1.16.5. I'd like to see that to get a view as to why 1.16.5 was broken. Once we've managed to have a look at that, it may give a clue as to if it's worth reviewing the giant-diff-from-doom. Thanks, attached the filtered diff (with additional junk left by filterdiff, but left the changelog) from git: Right, the delta diff was small enough that I actually put in the time to look at the full diff. This took a number of hours, but anyway: Some questions: dpkg-1.16.8/dpkg-deb/main.c - -h|--helpShow this help message.\n - --versionShow the version.\n + -?, --help Show this help message.\n + --versionShow the version.\n Why are you removing -h? dpkg-1.16.8/lib/dpkg/ar.c + if (strlen(name) 15) + ohshit(_(ar member name '%s' length too long), name); + if (size 99L) + ohshit(_(ar member size %jd too large), size); + Why 99? dpkg-1.16.8/scripts/Dpkg/Deps.pm -(any) # architecture name +([a-zA-Z0-9][a-zA-Z0-9-]*) # architecture name Why the additional restriction? *.gmo - are you sure you're meant to be shipping these in the tarball? Thanks, Neil -- signature.asc Description: Digital signature
Bug#683063: marked as done (unblock: sparkleshare/0.9.0-2)
Your message dated Sat, 28 Jul 2012 11:59:15 +0200 with message-id 5013b7f3.3010...@thykier.net and subject line Re: Bug#683063: unblock: sparkleshare/0.9.0-2 has caused the Debian Bug report #683063, regarding unblock: sparkleshare/0.9.0-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.) -- 683063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683063 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 sparkleshare Release 0.9.0 (and the -1 package) has a bug in its status icon code that causes it to disappear and reappear instead of showing an animation (which also causes the rest of the icons to move around). The sparkleshare bug is #682070. unblock sparkleshare/0.9.0-2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-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--- On 2012-07-28 11:48, Carlos Martín Nieto wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package sparkleshare Release 0.9.0 (and the -1 package) has a bug in its status icon code that causes it to disappear and reappear instead of showing an animation (which also causes the rest of the icons to move around). The sparkleshare bug is #682070. unblock sparkleshare/0.9.0-2 [...] Unblocked, thanks. ~Niels---End Message---
Bug#683063: unblock: sparkleshare/0.9.0-2
On 2012-07-28 11:48, Carlos Martín Nieto wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package sparkleshare Release 0.9.0 (and the -1 package) has a bug in its status icon code that causes it to disappear and reappear instead of showing an animation (which also causes the rest of the icons to move around). The sparkleshare bug is #682070. unblock sparkleshare/0.9.0-2 PS: #682070 hasn't been closed, please do that with the proper version. ~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/5013b95b.1080...@thykier.net
Bug#681016: [release.debian.org] unblock: dotlrn/2.5.0+dfsg-8
On Tue, Jul 10, 2012 at 00:40:43 +0200, Hector Romojaro wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception --- Please enter the report below this line. --- Hi Relase Team! Please unblock package dotlrn. It fixes an important bug (#677060) and a minor patch issue. Unfortunately, and I apologize for that, the previous version (2.5.0+dfsg-7) also included the migration of the package format to the new 3.0 one (#661038), but didn't reach testing on time before the freeze, so the version now in unstable (2.5.0+dfsg-8) also differs from the testing one (2.5.0+dfsg-6) in the package format issue. Please find in attachment the debdiff between testing and unstable versions. I'm afraid all the unrelated packaging changes make this unsuitable. If you want to fix #677060 please prepare a targetted fix based on -6 for upload to testing-proposed-updates. Thanks, Julien signature.asc Description: Digital signature
Re: would it be possible to reinstantiate openmeeg and ants in wheezy?
On 2012-07-05 18:09, Yaroslav Halchenko wrote: Hi Release Team, Hi, [...] ants [...] FTBFS atm on mips, mipsel, s390 imho due to insufficient resources and might be tricky to make them build reliably What is keeping this package out is the fact there it FTBFS on mips, mipsel and s390. If your package is unsupported (or unsupportable) on these architectures, have the FTP masters remove the binaries on these architectures in unstable. Assuming it is done really soon(tm) ants can re-enter testing with its current freeze exception (which will be retired the 30th as it is). openmeeg [...] FTBFS atm on mips only, and could be resolved simply through disabling build time unittesting Pretty much the same story as ants, though #679315 is still open despite looking fixed. Please close that bug as well. I wondered, than even if I manage to overcome FTBFS on those -- would they be allowed to come back to wheezy? Thanks in advance ~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/5013bd79.9010...@thykier.net
Re: Next upload 2012-06-26 (dpkg 1.16.5)
On Sat, Jul 28, 2012 at 11:59:07AM +0200, Neil McGovern wrote: On Mon, Jul 23, 2012 at 07:18:29PM +0200, Guillem Jover wrote: On Mon, 2012-07-23 at 17:51:56 +0100, Neil McGovern wrote: Nope, 1.16.5. I'd like to see that to get a view as to why 1.16.5 was broken. Once we've managed to have a look at that, it may give a clue as to if it's worth reviewing the giant-diff-from-doom. Thanks, attached the filtered diff (with additional junk left by filterdiff, but left the changelog) from git: Right, the delta diff was small enough that I actually put in the time to look at the full diff. This took a number of hours, but anyway: Oh, and also, I want to see a specific ack/nack from the SRMs for: --- dpkg-1.16.4.3/debian/source/options 2012-06-09 14:32:05.0 + +++ dpkg-1.16.8/debian/source/options 2012-07-19 12:27:34.0 + @@ -1,2 +1,2 @@ -# Use bzip2 compression by default, we save 2.5Mb -compression = bzip2 +# Use xz compression by default, we save 4.6 MiB +compression = xz Neil -- signature.asc Description: Digital signature
Re: Next upload 2012-06-26 (dpkg 1.16.5)
On Sat, 2012-07-28 at 12:40 +0200, Neil McGovern wrote: Oh, and also, I want to see a specific ack/nack from the SRMs for: --- dpkg-1.16.4.3/debian/source/options 2012-06-09 14:32:05.0 + +++ dpkg-1.16.8/debian/source/options 2012-07-19 12:27:34.0 + @@ -1,2 +1,2 @@ -# Use bzip2 compression by default, we save 2.5Mb -compression = bzip2 +# Use xz compression by default, we save 4.6 MiB +compression = xz afaics, this is just the upstream dpkg tarball changing compression method. Does anything actually care about that? 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/1343472337.18013.49.ca...@jacala.jungle.funky-badger.org
Bug#682268: marked as done (unblock: foremost/1.5.7-4)
Your message dated Sat, 28 Jul 2012 13:26:38 +0200 with message-id 20120728112638.gp10...@radis.cristau.org and subject line Re: Bug#682268: unblock: foremost/1.5.7-4 has caused the Debian Bug report #682268, regarding unblock: foremost/1.5.7-4 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.) -- 682268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock the package foremost. The updated version fixed the build on kfreebsd-* (1.5.7-3) and hurd (1.5.7-4). It would be great to have one more software ported to those platform by making simple build system changes. -- Regards, Aron Xu ---End Message--- ---BeginMessage--- On Sat, Jul 21, 2012 at 04:28:53 +0800, Aron Xu wrote: Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock the package foremost. The updated version fixed the build on kfreebsd-* (1.5.7-3) and hurd (1.5.7-4). It would be great to have one more software ported to those platform by making simple build system changes. Unblocked. The dpkg-buildflags stuff shouldn't really be in a patch though, I'd just set the variables in debian/rules when calling make and remove the .c.o rule which overrides the builtin one. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#682279: unblock: libweb-id-perl/1.921-3
On Sat, Jul 21, 2012 at 20:55:27 +0200, Jonas Smedegaard wrote: Is the noise of the non-crucial changes so problematic (a.k.a. unpleasing) that the release team considers the current package unsuitable for getting an exception from the freeze? I honestly did not consider that noise as significant changes not related to the bug to be fixed, as it is phrased at the fine http://release.debian.org/wheezy/freeze_policy.html. Do the release team consider the package unsuitable for freeze exception due to the lack of bug reference in the changelog (the bug was unfortunately unavailable to reference at the time the package was produced and I honestly was unaware that such reference was problematic for the release team to get passed in the freeze exception bugreport)? Do the release team consider the package unsuitable for freeze exception due to the user-only oriented changelog entry - i.e. lack of verbose enough details in changelog for release managers to follow _how_ the issue was fixed? Would it be more helpful of me to upload another package release that rephrased the changelog to be more helpful for release managers to understand how non-newest-debhelper-style packaging was performed internally? Should I do that in addition to the user-oriented changelog entry or instead of it? Would it be more helpful if I had not asked these questions but instead just uploaded a new package fixing these three issues raised by Cyril? So I think I'll answer these all at once because I think they boil down to the same thing. For a request like this, if it takes more than 5 minutes to process it's a waste of our time. Having a clear changelog helps avoid that, as does not arguing or getting on your high horse when asked clarification questions. And by helping that, it helps get your request approved, which I guess is what you want? Cheers, Julien signature.asc Description: Digital signature
Bug#682300: unblock: hunspell-en-us/20070829-6 and openoffice.org-dictionaries/1:3.3.0~rc10-4
On Sat, Jul 21, 2012 at 10:49:55 +0200, Rene Engelhard wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock packages hunspell-en-us and openoffice.org-dictionaries. Trivial fix for (admittedly minor) bug #680485 unblock hunspell-en-us/20070829-6 unblock openoffice.org-dictionaries/1:3.3.0~rc10-4 I must admit between the myspell vs hunspell confusion in debian/control vs debian/changelog I don't understand what the intent is here. Cheers, Julien signature.asc Description: Digital signature
please unblock open-vm-tools (rc bugfix)
Hi, open-vm-tools/2:8.8.0+2012.05.21-724730-3 was uploaded to fix an RC bug in the package (#679886). It has now aged for 11 days without problems discovered. It must be noted that wheezy now contains -1. -2 was uploaded before the freeze and got an automatic unblock already. Its changes have been in unstable for a month and I'm using -3 on a wheezy machine for weeks to full satisfaction. Please consider to unblock. thanks, Thijs signature.asc Description: This is a digitally signed message part.
Bug#682392: marked as done (unblock: tap-plugins/0.7.2-1)
Your message dated Sat, 28 Jul 2012 13:53:34 +0200 with message-id 20120728115334.gb17...@radis.cristau.org and subject line Re: Bug#682392: unblock: tap-plugins/0.7.2-1 has caused the Debian Bug report #682392, regarding unblock: tap-plugins/0.7.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 682392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682392 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 tap-plugins 0.7.2-1. I've uploaded the most recent upstream release to unstable in order to fix an annoying issue encountered when using one of the plugins provided by the suite: - Fix sharp peaks / level jumps in the output when using the Scaling Limiter plugin. The debdiff between versions in testing and unstable is attached. Thanks for considering. unblock tap-plugins/0.7.2-1 -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise'), (100, 'precise-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-26-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru tap-plugins-0.7.1/CREDITS tap-plugins-0.7.2/CREDITS --- tap-plugins-0.7.1/CREDITS 2009-08-17 13:10:57.0 +0200 +++ tap-plugins-0.7.2/CREDITS 2012-07-08 16:16:01.0 +0200 @@ -58,6 +58,9 @@ caused problems on 64-bit machines, found uninitialised variables via Valgrind, and also pinned down long lurking denormal issues. Thanks! +Taku Yamamoto t...@tackymt.homeip.net investigated a buffer boundary +related bug in Scaling Limiter and provided a patch solving the problem. + And, of course, special thanks to the Ardour [http://ardour.org] and JACK [http://jackit.sf.net] development teams for their tireless diff -Nru tap-plugins-0.7.1/debian/changelog tap-plugins-0.7.2/debian/changelog --- tap-plugins-0.7.1/debian/changelog 2011-07-01 12:19:13.0 +0200 +++ tap-plugins-0.7.2/debian/changelog 2012-07-18 16:58:26.0 +0200 @@ -1,3 +1,14 @@ +tap-plugins (0.7.2-1) unstable; urgency=low + + * Team upload. + * New bugfix release: +- Fix sharp peaks / level jumps in the output when using the Scaling + Limiter plugin. + * Update debian/copyright. + * Bump Standards. + + -- Alessio Treglia ales...@debian.org Wed, 18 Jul 2012 16:56:59 +0200 + tap-plugins (0.7.1-2) unstable; urgency=low * Team upload. diff -Nru tap-plugins-0.7.1/debian/control tap-plugins-0.7.2/debian/control --- tap-plugins-0.7.1/debian/control 2011-07-01 12:15:04.0 +0200 +++ tap-plugins-0.7.2/debian/control 2012-07-18 16:56:40.0 +0200 @@ -5,7 +5,7 @@ Uploaders: Jaromír Mikeš mira.mi...@seznam.cz Build-Depends: debhelper (= 7.0.50~), sharutils -Standards-Version: 3.9.2 +Standards-Version: 3.9.3 DM-Upload-Allowed: yes Vcs-Git: git://git.debian.org/git/pkg-multimedia/tap-plugins.git Vcs-Browser: http://git.debian.org/?p=pkg-multimedia/tap-plugins.git diff -Nru tap-plugins-0.7.1/debian/copyright tap-plugins-0.7.2/debian/copyright --- tap-plugins-0.7.1/debian/copyright 2011-07-01 12:13:54.0 +0200 +++ tap-plugins-0.7.2/debian/copyright 2012-07-18 16:56:05.0 +0200 @@ -1,4 +1,4 @@ -Format: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=filerev=174 +Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: TAP-plugins Upstream-Contact: Tom Szilagyi tszila...@users.sourceforge.net Source: http://sourceforge.net/projects/tap-plugins/files/ @@ -14,7 +14,7 @@ Files: debian/* Copyright: - 2010 Alessio Treglia quadris...@ubuntu.com + 2010-2012 Alessio Treglia quadris...@ubuntu.com 2010 Jaromír Mikeš mira.mi...@seznam.cz 2004 Anand Kumria wildf...@progsoc.org License: GPL-2+ @@ -29,9 +29,9 @@ but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. -Comment: You should have received a copy of the GNU General Public License - along with this package; if not, write to the Free Software - Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA +Comment: + You should have received a copy of the GNU General Public License + along with this program. If not, see http://www.gnu.org/licenses/. . On Debian systems, the complete text of the GNU General Public License can be found in
Bug#682402: marked as done (unblock: libxml2/2.8.0+dfsg1-5)
Your message dated Sat, 28 Jul 2012 13:59:36 +0200 with message-id 20120728115936.ga17...@radis.cristau.org and subject line Re: Bug#682402: unblock: libxml2/2.8.0+dfsg1-5 has caused the Debian Bug report #682402, regarding unblock: libxml2/2.8.0+dfsg1-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.) -- 682402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682402 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 libxml2/2.8.0+dfsg1-5 which fixes CVE-2012-2807, Bug #679280. Fix for squeeze has been agreed by security team and uploaded to security-master just now. -- Regards, Aron Xu ---End Message--- ---BeginMessage--- On Sun, Jul 22, 2012 at 21:12:43 +0800, Aron Xu wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock libxml2/2.8.0+dfsg1-5 which fixes CVE-2012-2807, Bug #679280. Fix for squeeze has been agreed by security team and uploaded to security-master just now. Unblocked by Adam. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Processed (with 1 errors): your mail
Processing commands for cont...@bugs.debian.org:
reopen 681196
Bug #681196 {Done: Julien Cristau jcris...@debian.org} [release.debian.org]
unblock: tryton-proteus/2.2.2-4
Bug reopened
Ignoring request to alter fixed versions of bug #681196 to the same values
previously set
thx
End of message, stopping processing here.
Please contact me if you need assistance.
--
681196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681196
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.134347746414157.transcr...@bugs.debian.org
Bug#681196: unblock: tryton-proteus/2.2.2-4
* Betr.: Re: Bug#681196: unblock: tryton-proteus/2.2.2-3 (Sat, 28 Jul 2012 11:15:41 +0200): On Wed, Jul 11, 2012 at 12:11:14 +0200, Mathias Behrle wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package tryton-proteus. The -3 upload fixes the #680817 FTBFS, revealed by a Lucas-powered rebuild. Does #680817 affect the version in testing? The BTS doesn't think so, and looking at the changes in proteus/pyson.py and setup.py I guess not. Now on to the changes themselves: --- tryton-proteus-2.2.1/debian/compat 2011-12-26 12:35:55.0 + +++ tryton-proteus-2.2.2/debian/compat 2012-07-11 09:31:06.0 + @@ -1 +1 @@ -8 +9 This is not ok during freeze. --- tryton-proteus-2.2.1/debian/rules 2011-12-26 12:35:55.0 + +++ tryton-proteus-2.2.2/debian/rules 2012-07-11 09:31:06.0 + @@ -7,3 +7,6 @@ dh_auto_clean rm -rf *.egg-info + +override_dh_builddeb: + dh_builddeb -- -Zxz -z9 neither is this, really. So with no RC or important bug fix that I know of in this version, I'm afraid I'm going to have to say no, sorry. Cheers, Julien I now can see, what has happened. tryton-proteus_2.2.2-2 was uploaded and accepted into unstable on 2012-06-30, but didn't make it into testing so far because of a version mismatch [1]. This should be due to a missing upload of 2.2.1-1 on Wed May 9, that I wasn't aware of. Could you please mark 2.2.2-2 for acceptance in testing, because it is a legitimate version uploaded before the freeze? The fix for #680817 is a really simple non-invasive fix and there should be no problem to accept it with 2.2.2-4, once 2.2.2-2 is in testing. [1] http://packages.qa.debian.org/t/tryton-proteus/news/20120630T165055Z.html Thanks, Mathias signature.asc Description: PGP signature
Bug#683053: unblock: python2.7/2.7.3-2
On Sat, Jul 28, 2012 at 03:39:51AM -0400, Scott Kitterman wrote: 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. Couldn't python2.7 get Breaks on the broken packages or something? I shortly talked with doko about that when I thought that only one package is affected and hence that was discarded. It is a private undocumented API but given that it really does affect other packages, it makes sense to me at least. Kind regards Philipp Kern signature.asc Description: Digital signature
Re: Please allow postgresql-9.1 9.1.4-3 into testing: RC bug fix
On Thu, Jul 26, 2012 at 04:11:37PM +0200, Martin Pitt wrote: For the record: the package has built everywhere, will be ready for testing tomorrow, and I just successfully ran the postgresql-common integration tests against this version in sid. Can this be considered, please? Unblocked, thanks. Kind regards Philipp Kern signature.asc Description: Digital signature
Processed: closing 680676
Processing commands for cont...@bugs.debian.org: close 680676 Bug #680676 [release.debian.org] unblock: busybox/1:1.20.0-5 Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 680676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680676 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.134347834318432.transcr...@bugs.debian.org
Bug#683053: unblock: python2.7/2.7.3-2
On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote: 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). There was also the part where it broke vim. Cheers, Julien signature.asc Description: Digital signature
Bug#683053: unblock: python2.7/2.7.3-2
On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote: 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). FWIW I think this is a major failure on the part of python upstream, and would rather see this change reverted. Cheers, Julien signature.asc Description: Digital signature
Re: please unblock open-vm-tools (rc bugfix)
On Sat, Jul 28, 2012 at 13:51:31 +0200, Thijs Kinkhorst wrote: Hi, open-vm-tools/2:8.8.0+2012.05.21-724730-3 was uploaded to fix an RC bug in the package (#679886). It has now aged for 11 days without problems discovered. It must be noted that wheezy now contains -1. -2 was uploaded before the freeze and got an automatic unblock already. Its changes have been in unstable for a month and I'm using -3 on a wheezy machine for weeks to full satisfaction. The changes in -2 are out of scope for the freeze IMO. Cheers, Julien signature.asc Description: Digital signature
Bug#681196: marked as done (unblock: tryton-proteus/2.2.2-4)
Your message dated Sat, 28 Jul 2012 14:34:26 +0200 with message-id 20120728123426.gf17...@radis.cristau.org and subject line Re: Bug#681196: unblock: tryton-proteus/2.2.2-4 has caused the Debian Bug report #681196, regarding unblock: tryton-proteus/2.2.2-4 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.) -- 681196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681196 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 tryton-proteus. The -3 upload fixes the #680817 FTBFS, revealed by a Lucas-powered rebuild. unblock tryton-proteus/2.2.2-3 debdiff attached tryton-proteus_2.2.2-3.debdiff Description: Binary data signature.asc Description: PGP signature ---End Message--- ---BeginMessage--- On Sat, Jul 28, 2012 at 14:16:14 +0200, Mathias Behrle wrote: I now can see, what has happened. tryton-proteus_2.2.2-2 was uploaded and accepted into unstable on 2012-06-30, but didn't make it into testing so far because of a version mismatch [1]. No, it didn't make it into testing because it had a serious regression (namely #680817). This should be due to a missing upload of 2.2.1-1 on Wed May 9, that I wasn't aware of. Could you please mark 2.2.2-2 for acceptance in testing, because it is a legitimate version uploaded before the freeze? I'm not sure what you mean by legitimate. 2.2.2-2 was RC-buggy. Plus, marking that version for acceptance wouldn't make sense now, since it's been superseded in unstable. So, I'm sorry, but no. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Re: Request unblock sdl-stretch/0.3.1-3
On Sun, Jul 08, 2012 at 11:58:28AM +0100, Manuel A. Fernandez Montecelo wrote: I would like to ask an unblock to sdl-stretch/0.3.1-3. There's an unblock already for sdl-stretch/0.3.1-2 because it was in unstable before the freeze, but -2 failed to build in kfreebsd-i386 and thus it never migrated to testing: Yep, hence the unblock for -2 does not matter. There are changes in debian/rules that are not mentioned in the changelog (like the DEB_CFLAGS_MAINT_APPEND and DEB_LDFLAGS_MAINT_APPEND bits). Please revert those. You also introduced a whitespace issue in debian/rules. I can live with the other changes even if they are really not conformant to the freeze rules. Kind regards Philipp Kern signature.asc Description: Digital signature
Re: please unblock open-vm-tools (rc bugfix)
On 07/28/2012 02:35 PM, Julien Cristau wrote: On Sat, Jul 28, 2012 at 13:51:31 +0200, Thijs Kinkhorst wrote: Hi, open-vm-tools/2:8.8.0+2012.05.21-724730-3 was uploaded to fix an RC bug in the package (#679886). It has now aged for 11 days without problems discovered. It must be noted that wheezy now contains -1. -2 was uploaded before the freeze and got an automatic unblock already. Its changes have been in unstable for a month and I'm using -3 on a wheezy machine for weeks to full satisfaction. The changes in -2 are out of scope for the freeze IMO. Can you be more specific please? Cheers Luk -- 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/5013de46.7040...@debian.org
Bug#683073: unblock: gnunet/0.9.3-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Dear release team,
(this bug submission is following my message [1] on debian-release@, to
make sure my mail will not get inadvertently overlooked in the
surrounding sea of unblock requests)
I prepared a new revision of GNUnet fixing a few bugs with the following
changes (the diff is attached):
* debian/control: update Vcs-* to the new repository in collab-maint.
* Install only the generated binaries on Hurd, thanks to Cyril
Roelandt (Closes: #670794).
* Use chmod and chown instead of dpkg-statoverride to set special
permissions and upgrade properly depending on the previous version
(Closes: #673301).
* Rewrite gnunet-server.init based on /etc/init.d/skeleton and make
gnunet-server depend on lsb-base to use LSB logging.
Would you consider to give gnunet 0.9.3-3 a freeze exception ?
This version is not yet uploaded to unstable, my sponsor is waiting for
your approval.
Cheers,
Bertrand
unblock gnunet/0.9.3-3
[1] http://lists.debian.org/debian-release/2012/07/msg01149.html
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 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 gnunet-0.9.3/debian/changelog gnunet-0.9.3/debian/changelog
--- gnunet-0.9.3/debian/changelog 2012-06-20 23:55:23.0 +0200
+++ gnunet-0.9.3/debian/changelog 2012-07-13 22:14:28.0 +0200
@@ -1,3 +1,15 @@
+gnunet (0.9.3-3) unstable; urgency=low
+
+ * debian/control: update Vcs-* to the new repository in collab-maint.
+ * Install only the generated binaries on Hurd, thanks to Cyril Roelandt
+(Closes: #670794).
+ * Use chmod and chown instead of dpkg-statoverride to set special permissions
+and upgrade properly depending on the previous version (Closes: #673301).
+ * Rewrite gnunet-server.init based on /etc/init.d/skeleton and make
+gnunet-server depend on lsb-base to use LSB logging.
+
+ -- Bertrand Marc beberk...@gmail.com Fri, 13 Jul 2012 22:13:55 +0200
+
gnunet (0.9.3-2) unstable; urgency=low
* Clean properly dpkg-statoverride in gnunet-server.postrm
diff -Nru gnunet-0.9.3/debian/control gnunet-0.9.3/debian/control
--- gnunet-0.9.3/debian/control 2012-06-10 10:29:08.0 +0200
+++ gnunet-0.9.3/debian/control 2012-07-13 20:04:35.0 +0200
@@ -10,8 +10,8 @@
libsqlite3-dev (=3.0), libpq-dev (=8.3), guile-1.8-dev, libglpk-dev (=4.32)
Build-Conflicts: autoconf2.13, automake1.4
Standards-Version: 3.9.3
-Vcs-Git: git://git.debian.org/git/users/bbk-guest/gnunet.git
-Vcs-browser: http://git.debian.org/?p=users/bbk-guest/gnunet.git
+Vcs-Git: git://git.debian.org/git/collab-maint/gnunet.git
+Vcs-browser: http://git.debian.org/?p=collab-maint/gnunet.git
Homepage: http://www.gnunet.org/
Package: gnunet
@@ -75,7 +75,7 @@
Pre-Depends: ${misc:Pre-Depends}
Depends:
${misc:Depends}, ${shlibs:Depends}, gnunet-common (= ${binary:Version}),
- adduser, gettext, netbase
+ adduser, gettext, netbase, lsb-base
Suggests: miniupnpc
Breaks: gnunet-fuse (0.9), gnunet-client (0.9)
Replaces: gnunet-fuse (0.9), gnunet-client (0.9)
diff -Nru gnunet-0.9.3/debian/gnunet-server.init gnunet-0.9.3/debian/gnunet-server.init
--- gnunet-0.9.3/debian/gnunet-server.init 2012-05-02 21:43:40.0 +0200
+++ gnunet-0.9.3/debian/gnunet-server.init 2012-07-13 20:02:50.0 +0200
@@ -1,64 +1,109 @@
-#!/bin/sh
-
+#! /bin/sh
### BEGIN INIT INFO
-# Provides: gnunet-server
-# Required-Start: $syslog $network $local_fs $remote_fs
-# Required-Stop: $syslog $network $local_fs $remote_fs
-# Should-Start:
-# Should-Stop:
-# Default-Start: 2 3 4 5
-# Default-Stop: 0 1 6
-# Short-Description: Starts the GNUnet server at boot time.
-# Description: GNUnet is a secure, trust-based peer-to-peer framework.
+# Provides: gnunet-server
+# Required-Start:$remote_fs $syslog $network
+# Required-Stop: $remote_fs $syslog $network
+# Default-Start: 2 3 4 5
+# Default-Stop: 0 1 6
+# Short-Description: Starts the GNUnet server at boot time.
+# Description: GNUnet is a secure, trust-based peer-to-peer framework.
### END INIT INFO
-PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
+PATH=/sbin:/usr/sbin:/bin:/usr/bin
+DESC=GNUnet
+NAME=gnunet-server
DAEMON=/usr/bin/gnunet-service-arm
-NAME=gnunet-service-arm
-DESC=GNUnet
LOGFILE=/var/log/gnunetd/gnunetd.log
+DAEMON_ARGS=-c /etc/gnunet.conf -d -l $LOGFILE
+SCRIPTNAME=/etc/init.d/$NAME
-test -x ${DAEMON} || exit 0
-
-set -e
-
-# Get configuration
-if [ -f /etc/default/gnunet-server ]
-then
- . /etc/default/gnunet-server
-fi
-
-if [ ${GNUNET_AUTOSTART} != true ]
-then
- exit 0
-fi
-
-case ${1} in
- start)
- echo -n Starting ${DESC}:
- start-stop-daemon --start --chuid
Re: please unblock typo3-src for wheezy
On Thu, Jul 12, 2012 at 11:26:36 +0200, Christian Welzel wrote: Hello there, please unblock typo3-src 4.5.17+dfsg1-1 from freeze. It is a upstream bugfix only release and contains a fix that prevents the backend of the CMS to work properly if the build-in js/css compressor is acitivated. There are no packages that depend on typo3-src so nothing will break. I'm not sure how to interpret the last sentence. If there's breakage in the package then it could affect users, surely? What's typo3/contrib/extjs/resources/resources.jsb, and what's the rewrite of that file about? Same with typo3/sysext/em/res/js/ux/filter/* Cheers, Julien signature.asc Description: Digital signature
Re: please unblock open-vm-tools (rc bugfix)
On Sat, Jul 28, 2012 at 14:42:46 +0200, Luk Claes wrote: On 07/28/2012 02:35 PM, Julien Cristau wrote: The changes in -2 are out of scope for the freeze IMO. Can you be more specific please? Specifically I mean the open-vm-tools 2:8.8.0+2012.05.21-724730-2 upload, with this changelog entry: open-vm-tools (2:8.8.0+2012.05.21-724730-2) unstable; urgency=low * Switching to xz compression. * Loading modules through kmod instead of initscript. * Adding sleep during restart in initscript. * Removing old dpkg trigger for update-initramfs. * Updating GPL boilerplate in copyright file. * Calling dh_dkms with version argument (Closes: #677503). -- Daniel Baumann daniel.baum...@progress-technologies.net Sat, 30 Jun 2012 04:55:23 +0200 None of these items seem to be fixing RC or important bugs (at least if as I understood it the last one didn't actually fix the dkms package, so it needed a followup fix from Thijs. Specific enough? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#680898: build-depends on gcc-4.5/g++-4.6; build-conflicts against obsolete gcc version on x86
On Thu, Jul 26, 2012 at 09:29:09PM +0900, Samuel Thibault wrote: Ah, gcc-4.4 will stay? That's an option which should work, yes. Yep, it will. See for instance [1]. Kind regards Philipp Kern [1] https://lists.debian.org/debian-superh/2012/04/msg1.html signature.asc Description: Digital signature
Re: please unblock open-vm-tools (rc bugfix)
On 07/28/2012 02:57 PM, Julien Cristau wrote: On Sat, Jul 28, 2012 at 14:42:46 +0200, Luk Claes wrote: On 07/28/2012 02:35 PM, Julien Cristau wrote: The changes in -2 are out of scope for the freeze IMO. Can you be more specific please? Specifically I mean the open-vm-tools 2:8.8.0+2012.05.21-724730-2 upload, with this changelog entry: open-vm-tools (2:8.8.0+2012.05.21-724730-2) unstable; urgency=low * Switching to xz compression. * Loading modules through kmod instead of initscript. * Adding sleep during restart in initscript. * Removing old dpkg trigger for update-initramfs. * Updating GPL boilerplate in copyright file. * Calling dh_dkms with version argument (Closes: #677503). -- Daniel Baumann daniel.baum...@progress-technologies.net Sat, 30 Jun 2012 04:55:23 +0200 None of these items seem to be fixing RC or important bugs (at least if as I understood it the last one didn't actually fix the dkms package, so it needed a followup fix from Thijs. Specific enough? The first one became a release goal AFAICS. The second and the last were not enough, but are needed to fix the RC bug AFAICS. The sleep is a workaround as otherwise people need to refrain from using restart. Which is an unfiled RC bug AFAICT. The GPL one is not just the boilerplate, but also fixing the copyright of some files. Which certainly can be seen as RC AFAICT. So the only one I could see you argue about, is the one about the initramfs or am I missing something? Cheers Luk -- 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/5013e2d4.2060...@debian.org
Re: Request unblock sdl-stretch/0.3.1-3
2012/7/28, Philipp Kern pk...@debian.org:
On Sun, Jul 08, 2012 at 11:58:28AM +0100, Manuel A. Fernandez Montecelo
wrote:
I would like to ask an unblock to sdl-stretch/0.3.1-3.
There's an unblock already for sdl-stretch/0.3.1-2 because it was in
unstable before the freeze, but -2 failed to build in kfreebsd-i386
and thus it never migrated to testing:
Yep, hence the unblock for -2 does not matter. There are changes in
debian/rules
that are not mentioned in the changelog (like the DEB_CFLAGS_MAINT_APPEND
and
DEB_LDFLAGS_MAINT_APPEND bits). Please revert those. You also introduced a
whitespace issue in debian/rules.
These changes that you mention, were introduced the 26th of April for
0.3.1-2, well before the release, without any bug report being
submitted since then. This is what it's already authorised to migrate
in the unblock.
The only changes introduced are the ones about architecture, 2 lines,
and the changelog. In the case that I didn't attach the diff
recently, I do it now, as generated by:
debdiff ../*/sdl-stretch_0.3.1-[23]*.dsc /tmp/sdl-stretch_-2_to_-3.diff
If you don't feel comfortable about authorising -2 either, that's
another question. It's been working apparently fine for 3+ months
now, without any bug report (then again it's not much used, so if
people find bugs maybe they're just ignoring it).
I've been working and spending time with this package with the hope
that the best possible version goes into unstable. It was only built
in i386 arches, which are mostly obsolete in mainstream hardware,
since nobody had bothered to update this package in the past few
Debian releases since 2005 when amd64 was not even an accepted
architecture.
I think that reversing these changes is not a good idea, for reasons
explained in the changelog and these bugs reports, I won't repeat
myself. So if you prefer to just remove the unblock, or the package
altogether for the next stable, I think that I prefer that solution to
producing a package that will get a FTBFS shortly after stable is
released.
Cheers.
--
Manuel A. Fernandez Montecelo manuel.montez...@gmail.com
diff -Nru sdl-stretch-0.3.1/debian/changelog sdl-stretch-0.3.1/debian/changelog
--- sdl-stretch-0.3.1/debian/changelog 2012-04-26 15:51:26.0 +0100
+++ sdl-stretch-0.3.1/debian/changelog 2012-07-04 20:25:34.0 +0100
@@ -1,3 +1,22 @@
+sdl-stretch (0.3.1-3) unstable; urgency=low
+
+ * Change Architecture: any-amd64 any-i386 for both binary packages.
+
+This package is a bit special because it contains optimised routines in
+assembler for some architectures, so even if it can be built successfully in
+others, it doesn't really make sense to provide the package. According to
+upstream, current models of both i386 and amd64 are supported, and while
+it's desired to have support in other platforms (e.g. ARM), it's not there
+yet.
+
+Before 0.3.1-1, debian/control was set only to build on i386; and in 0.3.1-1
+it was set to any, but the file
+https://buildd.debian.org/quinn-diff/sid/Packages-arch-specific restricted
+the architectures effectively to i386 kfreebsd-i386 hurd-i386 (see
+#680275).
+
+ -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com Wed, 04 Jul 2012 20:12:03 +0100
+
sdl-stretch (0.3.1-2) unstable; urgency=low
* Bump Standards-Version to 3.9.3 (no changes needed)
diff -Nru sdl-stretch-0.3.1/debian/control sdl-stretch-0.3.1/debian/control
--- sdl-stretch-0.3.1/debian/control 2012-04-26 15:51:35.0 +0100
+++ sdl-stretch-0.3.1/debian/control 2012-07-04 20:07:19.0 +0100
@@ -17,7 +17,7 @@
Homepage: http://sdl-stretch.sourceforge.net
Package: libsdl-stretch-0-3
-Architecture: any
+Architecture: any-amd64 any-i386
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends},
@@ -33,7 +33,7 @@
Package: libsdl-stretch-dev
Section: libdevel
-Architecture: any
+Architecture: any-amd64 any-i386
Depends: ${misc:Depends},
libsdl-stretch-0-3 (= ${binary:Version}),
libsdl1.2-dev(= 1.2.14~)
Re: Next upload 2012-06-26 (dpkg 1.16.5)
Hi, Neil McGovern wrote: dpkg-1.16.8/dpkg-deb/main.c - -h|--helpShow this help message.\n - --versionShow the version.\n + -?, --help Show this help message.\n + --versionShow the version.\n Why are you removing -h? I'll leave this one for Guillem. dpkg-1.16.8/lib/dpkg/ar.c + if (strlen(name) 15) + ohshit(_(ar member name '%s' length too long), name); + if (size 99L) + ohshit(_(ar member size %jd too large), size); + Why 99? In the common ar format, the member size is stored as a 10-byte character array as a decimal integer (padded on the right with spaces). The maximum value that can be represented is 10^10 - 1 = 9 999 999 999. Now a person might worry for a moment: since log2(10) is a little more than 3.3, isn't 10^10 around 2^33, which is larger than can be represented in a long on 32-bit architectures? Luckily dpkg uses C99, where this is automatically treated as a long long literal when appropriate. dpkg-1.16.8/scripts/Dpkg/Deps.pm -(any) # architecture name +([a-zA-Z0-9][a-zA-Z0-9-]*) # architecture name Why the additional restriction? It's a loosening. Previously the only permitted architecture-qualified dependency was :any. *.gmo - are you sure you're meant to be shipping these in the tarball? I also dislike that convention, but it's what gettextized projects do by default. See http://lists.gnu.org/archive/html/autoconf/2007-08/msg00024.html Thanks, Jonathan -- 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/20120728132123.GA9715@burratino
Bug#682960: unblock (pre-approval): gnome-shell/3.4.2-1
On Sat, Jul 28, 2012 at 11:51:06AM +0200, Laurent Bigonville wrote:
Le Fri, 27 Jul 2012 19:47:41 -0400,
Mike Miller mtmil...@ieee.org a écrit :
On Sat, Jul 28, 2012 at 12:44:13AM +0200, Michael Biebl wrote:
Am 28.07.2012 00:31, schrieb Mike Miller:
Just happened to spot this, sorry if I'm intruding, but how about
fixing RC bug #681737 in this release? It's an easy cherry-pick
patch, fuzz-free, I've been running with this patch applied for
over a week with no problems.
While we should definitely fix this issue for wheezy, the upstream
patch only works, if we update *all* NM vpn plugins to supply an
absolute path in their corresponding .name file. (I assume you
manually patched the .name file on your local system?)
Yes.
It might be easier to just change gnome-shell to look for the
vpn-auth-dialogs in /usr/lib/NetworkManager instead of
Config.LIBEXECDIR (which expands to /usr/lib/gnome-shell).
True enough. That was how I was looking at it until I ran across the
upstream bug report. Solving it that way is slightly more coordination
now, but it's future-proof and less coordination later.
If you all decide hardcoding gnome-shell to /usr/lib/NetworkManager is
the best for wheezy, that's fine too.
I think both should be done as some VPN modules (like nm-strongswan)
are already using a full path.
I've added the following patch to the package. I'm waiting RT ack
before pushing everything to the svn.
=8==
Description: Use Debian specific NM VPN helpers paths
Author: Laurent Bigonville bi...@debian.org
Forwarded: not-needed
--- a/js/ui/networkAgent.js
+++ b/js/ui/networkAgent.js
@@ -685,7 +685,7 @@ const NetworkAgent = new Lang.Class({
} catch(e) { } // ignore errors if key does not exist
let path = binary;
if (!GLib.path_is_absolute(path)) {
-path = GLib.build_filenamev([Config.LIBEXECDIR,
path]);
+path =
GLib.build_filenamev(['/usr/lib/NetworkManager/VPN', path]);
Except the Debian path is /usr/lib/NetworkManager without the VPN part.
Fix that, and this looks good to me. Thanks!
--
mike
--
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/20120728132328.ga7...@ohm.home.local
Re: please unblock open-vm-tools (rc bugfix)
On Sat, Jul 28, 2012 at 15:02:12 +0200, Luk Claes wrote: The first one became a release goal AFAICS. Reference? The second and the last were not enough, but are needed to fix the RC bug AFAICS. Can you be more specific please? Cheers, Julien signature.asc Description: Digital signature
Bug#682467: unblock: blist/1.3.4-2
On Mon, Jul 23, 2012 at 00:55:52 -0400, Scott Kitterman wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package blist Fixed RC bug #681583 Would it be better to remove it instead? Before the fix, it has had one upload ever, that shipped broken on everything but amd64, so I guess it's not getting much use/attention. Cheers, Julien signature.asc Description: Digital signature
Bug#683053: unblock: python2.7/2.7.3-2
On Saturday, July 28, 2012 02:14:04 PM Philipp Kern wrote: On Sat, Jul 28, 2012 at 03:39:51AM -0400, Scott Kitterman wrote: 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. Couldn't python2.7 get Breaks on the broken packages or something? I shortly talked with doko about that when I thought that only one package is affected and hence that was discarded. It is a private undocumented API but given that it really does affect other packages, it makes sense to me at least. It could, I suppose. I don't think that, once this is sorted out in Wheezy/Unstable there is an upgrade issue for Squeeze. If one of the relevant applications is running during the upgrade it will keep using the old version of the module. In my estimation, for Squeeze upgrades it's not worth making the package upgrade sequencing more complicated for the apt resolver. 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/55982943.NZb4h4FIRU@scott-latitude-e6320
Bug#682468: marked as done (unblock: python-colorama/0.2.4-1.1)
Your message dated Sat, 28 Jul 2012 15:43:31 +0200
with message-id 20120728134331.gm17...@radis.cristau.org
and subject line Re: Bug#682468: unblock: python-colorama/0.2.4-1.1
has caused the Debian Bug report #682468,
regarding unblock: python-colorama/0.2.4-1.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
682468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-colorama
Fixes RC bug #681584
unblock python-colorama/0.2.4-1.1
diff -Nru python-colorama-0.2.4/debian/changelog python-colorama-0.2.4/debian/changelog
--- python-colorama-0.2.4/debian/changelog 2012-03-06 13:17:39.0 -0500
+++ python-colorama-0.2.4/debian/changelog 2012-07-23 01:02:44.0 -0400
@@ -1,3 +1,13 @@
+python-colorama (0.2.4-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Use dh_python2.
+Build-Depend on python (= 2.6.6-3~) for that.
+Add python:Depends to Depends.
+Closes: #681584
+
+ -- Evgeni Golov evg...@debian.org Tue, 17 Jul 2012 08:52:08 +0200
+
python-colorama (0.2.4-1) unstable; urgency=low
* Initial release (Closes: #662761)
diff -Nru python-colorama-0.2.4/debian/control python-colorama-0.2.4/debian/control
--- python-colorama-0.2.4/debian/control 2012-03-06 13:17:39.0 -0500
+++ python-colorama-0.2.4/debian/control 2012-07-23 01:01:55.0 -0400
@@ -2,7 +2,7 @@
Section: python
Priority: optional
Maintainer: Khalid El Fathi kha...@elfathi.fr
-Build-Depends: debhelper (= 9.0.0), python
+Build-Depends: debhelper (= 9.0.0), python (= 2.6.6-3~)
Standards-Version: 3.9.3
Homepage: http://pypi.python.org/pypi/colorama/
Vcs-Git: git://git.debian.org/collab-maint/python-colorama.git
@@ -11,7 +11,7 @@
Package: python-colorama
Architecture: all
-Depends: ${misc:Depends}
+Depends: ${python:Depends}, ${misc:Depends}
Description: Cross-platform colored terminal text in Python
Python-colorama provides a simple cross-platform API to print colored terminal
text from Python applications.
diff -Nru python-colorama-0.2.4/debian/rules python-colorama-0.2.4/debian/rules
--- python-colorama-0.2.4/debian/rules 2012-03-06 13:17:39.0 -0500
+++ python-colorama-0.2.4/debian/rules 2012-07-23 01:01:55.0 -0400
@@ -2,7 +2,7 @@
#export DH_VERBOSE=1
%:
- dh $@
+ dh $@ --with=python2
override_dh_installexamples:
cp -r $(CURDIR)/demos/* $(CURDIR)/debian/python-colorama/usr/share/doc/python-colorama/examples/
---End Message---
---BeginMessage---
On Mon, Jul 23, 2012 at 01:11:06 -0400, Scott Kitterman wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-colorama
Fixes RC bug #681584
Same question as blist, I guess. Hrm, except this one has one reverse
dependency (httpcode). Oh well, unblocked.
Cheers,
Julien
signature.asc
Description: Digital signature
---End Message---
Bug#683053: unblock: python2.7/2.7.3-2
On Saturday, July 28, 2012 02:30:36 PM Julien Cristau wrote: On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote: 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). There was also the part where it broke vim. You're right. I forgot about that one. From that bug (#681599), I understand the pland to be: Plan B == In any order: - Fix vim build not to link config.c into the binary. (I attached a proposed patch.) - Fix python2.7 symbols. Add Breaks for each provider of vim-python. The vim part of that is done, but the python2.7 part is not. I guess that needs doing as well, although I don't know if it should be done as a separate upload after the current one transitions or to replace the current one in Unstable. I didn't look at what needs to be done to fix the symbols, so I don't know how hard that'll be. 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/2316865.tj79B075Ts@scott-latitude-e6320
Bug#682827: marked as done (nmu: libgeier0_0.13-1)
Your message dated Sat, 28 Jul 2012 15:44:36 +0200 with message-id 20120728134436.ga19...@spike.0x539.de and subject line Re: Bug#682827: nmu: libgeier0_0.13-1 has caused the Debian Bug report #682827, regarding nmu: libgeier0_0.13-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.) -- 682827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682827 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 nmu libgeier0_0.13-1 . ALL . -m rebuild to work around xmlsec issue (bug #675513) ---End Message--- ---BeginMessage--- On Thu, Jul 26, 2012 at 10:17:18PM -0400, John Belmonte wrote: On Thu, Jul 26, 2012 at 3:58 AM, Philipp Kern pk...@debian.org wrote: On Wed, Jul 25, 2012 at 08:41:57PM -0400, John V. Belmonte wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu libgeier0_0.13-1 . ALL . -m rebuild to work around xmlsec issue (bug #675513) Where's the proposed patch to xmlsec? I've just uploaded xmlsec1_1.2.18-2 which has the fix. If we can't get that xmlsec1 update into wheezy, for now I think it's sufficient to rebuild libgeier against the existing version 1.2.18-1. The issue would only come up again if wheezy somehow got a newer upstream version of xmlsec1. Can we get rid of that check altogether? (Even upstream?) It does not make sense at all in a Debian context and I wonder what the first check (minor XMLSEC_VERSION_MINOR) should tell me. As far as I can see it will now prevent *at runtime* that you use an older xmlsec than the one $package was compiled with. At least you are already using `dh_makeshlibs -V' (which I hate but I guess here it then makes some sense). I've unblocked xmlsec1 and scheduled the binnmus of libgeier. Kind regards Philipp Kern signature.asc Description: Digital signature ---End Message---
Please grant freeze exception for RoarAudio related packages
flum, Small background: I left the Debian project because of the CELT/Opus/mumble/RoarAudio case. Because of Ron's bad timing all of this falls into the freeze interval. I'm very sorry about this. Some time ago I asked if I should file O or RM bugs for my packages. You told me that you have no preference. In meantime some people got interested and took over my packages. I'm thankful to those people. All non RoarAudio packages as well as src:roarplaylistd have successfully moved to the new maintainsers already. The following packages still contain my name in Mainatiner or Uploader field in current unstable/testing version. I opend tickets about the removal of my name as I was told. * aroarfw (#682876) * ckport (#682886) * muroar (#682885, see below) * muroard (#682877) * roaraudio (#682878, see below) * vclt-tools (#682879) I kindly ask you to allow uploads with my name removed so this is done before the release. This is very important to me as I consider my good name damaged with the current situation in Debian (this is why I leave the project). Patrick Matthäi is willing to do uploads as soon as you allow it. Also as of my knowlage he will do his own requests for some security(?) updates soon for muroar and roaraudio so they are just listed here for completness. Will you be so kind and allow uploads for aroarfw, ckport, muroard and vclt-tools? Thank you for your work and time. PS: please keep Patrick Matthäi in CC as he is not on the list. -- Philipp. (Rah of PH2) signature.asc Description: This is a digitally signed message part
Bug#683053: unblock: python2.7/2.7.3-2
On Saturday, July 28, 2012 02:31:50 PM Julien Cristau wrote: On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote: 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). FWIW I think this is a major failure on the part of python upstream, and would rather see this change reverted. We're going to need another upload of python2.7 to fix the symbols, so this would not be that hard to revert in the same upload. Since I'm not the maintainer, I guess I need to leave answering this question to doko (along with the symbols question from #681599. 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/1707269.h0UzCmZCgI@scott-latitude-e6320
Bug#682467: unblock: blist/1.3.4-2
On Saturday, July 28, 2012 03:37:16 PM Julien Cristau wrote: On Mon, Jul 23, 2012 at 00:55:52 -0400, Scott Kitterman wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package blist Fixed RC bug #681583 Would it be better to remove it instead? Before the fix, it has had one upload ever, that shipped broken on everything but amd64, so I guess it's not getting much use/attention. Clearly the impact of removal is low. Personally, since a fix is available, I'd be inclined to keep it, but either approach is reasonable. 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/32772399.d9lsKKDtT6@scott-latitude-e6320
Re: Please grant freeze exception for RoarAudio related packages
On Sat, Jul 28, 2012 at 15:51:15 +0200, Philipp Schafft wrote: Will you be so kind and allow uploads for aroarfw, ckport, muroard and vclt-tools? You don't need our permission for uploading, so go ahead. Cheers, Julien signature.asc Description: Digital signature
Bug#683079: unblock: awesome/3.4.13-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package awesome This is a new release upstream with only a short list of bug fix. The main important one is to fix an important usability regression (see #681364). unblock awesome/3.4.13-1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash pgpCT3XDsFrut.pgp Description: PGP signature
Bug#682467: marked as done (unblock: blist/1.3.4-2)
Your message dated Sat, 28 Jul 2012 15:59:55 +0200
with message-id 20120728135955.go17...@radis.cristau.org
and subject line Re: Bug#682467: unblock: blist/1.3.4-2
has caused the Debian Bug report #682467,
regarding unblock: blist/1.3.4-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.)
--
682467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682467
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 blist
Fixed RC bug #681583
unblock blist/1.3.4-2
diff -ruN export/debian/changelog blist-1.3.4/debian/changelog
--- export/debian/changelog 2012-07-23 00:29:25.089477000 -0400
+++ blist-1.3.4/debian/changelog 2012-07-23 00:45:37.229289894 -0400
@@ -1,3 +1,20 @@
+blist (1.3.4-2) unstable; urgency=low
+
+ * Team upload
+
+ [ Evgeni Golov ]
+ * Non-maintainer upload.
+ * Use dh_python2.
+ * Add python-all-dev to Build-Depends.
+ * Add python:Depends to Depends.
+ * This all closes: #681583
+
+ [ Scott Kitterman ]
+ * Add python-setuptools to Build-Depends
+ * Add missing Vcs-* to Control
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 23 Jul 2012 00:40:43 -0400
+
blist (1.3.4-1) unstable; urgency=low
* Initial release.
diff -ruN export/debian/control blist-1.3.4/debian/control
--- export/debian/control 2012-07-23 00:29:25.089477000 -0400
+++ blist-1.3.4/debian/control 2012-07-23 00:45:10.533290680 -0400
@@ -5,15 +5,18 @@
Uploaders:
Michael Gilbert mgilb...@debian.org
Build-Depends:
- debhelper (= 9)
+ debhelper (= 9), python-all-dev (= 2.6.6-3~), python-setuptools
Standards-Version: 3.9.3
Homepage: http://pypi.python.org/pypi/blist
+Vcs-Svn: svn://svn.debian.org/python-modules/packages/blist/trunk
+Vcs-Browser: http://svn.debian.org/viewsvn/python-modules/packages/blist/trunk/
Package: python-blist
Architecture: any
Depends:
${shlibs:Depends},
${misc:Depends},
+ ${python:Depends}
Description: List-like type for python with better asymptotic performance
This package is a drop-in replacement for the Python list the provides better
performance when modifying large lists. The blist package also provides
diff -ruN export/debian/rules blist-1.3.4/debian/rules
--- export/debian/rules 2012-07-23 00:29:25.089477000 -0400
+++ blist-1.3.4/debian/rules 2012-07-23 00:42:46.077294949 -0400
@@ -9,4 +9,4 @@
dh_clean
%:
- dh $@
+ dh $@ --with=python2
---End Message---
---BeginMessage---
On Sat, Jul 28, 2012 at 09:56:17 -0400, Scott Kitterman wrote:
On Saturday, July 28, 2012 03:37:16 PM Julien Cristau wrote:
On Mon, Jul 23, 2012 at 00:55:52 -0400, Scott Kitterman wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package blist
Fixed RC bug #681583
Would it be better to remove it instead? Before the fix, it has had one
upload ever, that shipped broken on everything but amd64, so I guess
it's not getting much use/attention.
Clearly the impact of removal is low. Personally, since a fix is available,
I'd be inclined to keep it, but either approach is reasonable.
Unblocked.
Cheers,
Julien
signature.asc
Description: Digital signature
---End Message---
Bug#683028: unblock: libsbsms/2.0.1-1
On Sat, 2012-07-28 at 00:39 +0200, Benjamin Drung wrote: Please unblock package libsbsms The new upstream release 2.0.1 contains just one bug fix (found by the Audacity developers). This bug fix touches src/buffer.cpp and src/buffer.h [1]. All other changes are just visual clutter and have no effect on the package. What happened to test/*? The entire tree seems to have vanished. 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/1343483999.18013.54.ca...@jacala.jungle.funky-badger.org
Re: Please grant freeze exception for RoarAudio related packages
reflum, On Sat, 2012-07-28 at 15:58 +0200, Julien Cristau wrote: On Sat, Jul 28, 2012 at 15:51:15 +0200, Philipp Schafft wrote: Will you be so kind and allow uploads for aroarfw, ckport, muroard and vclt-tools? You don't need our permission for uploading, so go ahead. Oh. I'm sorry, it was maybe my bad wording: I kindly asks if you will allow them to go into testing/wheezy. -- Philipp. (Rah of PH2) signature.asc Description: This is a digitally signed message part
Bug#683082: unblock: postgresql-common/134
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
unblock postgresql-common/134
Hello release team,
I have uploaded version 133 and 134 of postgresql-common which fixes
two really important bugs which should go into Wheezy, as well as some
rather harmless cleanup which I consider appropriate for Wheezy as
well. Can this please considered to get an unblock request?
I ran this against postgresql-9.1 and -9.2 in sid (automatic and
manual tests).
Debdiff attached, some notes about the individual changes:
| postgresql-common (133) unstable; urgency=low
|
| [ Christoph Berg ]
| * Add .bzrignore file.
No runtime impact at all, just VCS cleanup.
| * PgCommon.pm: Check IPv4 and IPv6 in next_free_port(). (Closes: #678858)
This is one of the two fixes. It prevented proper working for the case
that you only have IPv6 on your system. It does not change behaviour
on an IPv4 system, but of course this is still a relatively intrusive
change.
| [ Peter Eisentraut ]
| * debian/control: Add myself to Uploaders.
| * debian/postgresql-common.lintian-overrides: Remove unused
| binary-without-manpage overrides (files were moved to
| postgresql-client-common package).
Trivial.
| * debian/rules: Catch errors in for loops.
This causes an FTBFS on any error, which improves robustness and error
detection. Package still builds fine in pbuilder as well as the Ubuntu
buildds.
| * pg_wrapper: Avoid Perl warnings if psql is linked against libreadline
| instead of libedit, even though that is not standard anymore.
This is a corner case when people build their own postgresql-9.1
package from the source with libreadline enabled, and avoids a nasty
error message in that case. It does not change behaviour when using
the Debian postgresql-9.1 packages.
| * testsuite: Reset core limit for pg_ctl tests.
| * testsuite: Allow running individual tests by passing them on the
| command line.
No runtime impact at all, just test suite improvements.
| [ Martin Pitt ]
| * pg_ctlcluster: Do not remove the PID file after SIGKILLing the
| postmaster in the last-ditch effort to shut down in --force mode. This
| is a potentially dangerous thing to do when trying to start a second
| postmaster in parallel while the first one is still being shut down.
| (see http://archives.postgresql.org/pgsql-general/2012-07/msg00475.php)
This is a rather serious potential data loss bugs (happens very
seldomly, but if it does it thoroughly messes up your data), the
second bug which really ought to go into Wheezy. The fix is trivial
(one-line patch which just drops the unlink()).
| -- Martin Pitt mp...@debian.org Thu, 26 Jul 2012 13:20:10 +0200
| postgresql-common (134) unstable; urgency=low
|
| * debian/backport-ppa: Fix syntax error.
No build/runtime impact at all, I just use this to generate uploads to
https://launchpad.net/~pitti/+archive/postgresql .
| * PgCommon.pm: Drop unconditional import of Socket::IN6ADDR_ANY and only do
| the IPv6 check if it is available. This keeps this version backwards
| compatible with Debian/Ubuntu releases with older Perl versions.
This makes the fix for #678858 compatible with Perl 5.12, so that the
package stays backportable to Squeeze.
Thank you for considering, and let me know if you have any question or
doubts.
Martin
-- System Information:
Debian Release: wheezy/sid
APT prefers quantal
APT policy: (500, 'quantal')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5.0-6-generic (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
diff -Nru postgresql-common-132/debian/backport-ppa postgresql-common-134/debian/backport-ppa
--- postgresql-common-132/debian/backport-ppa 2012-06-06 19:55:54.0 +0200
+++ postgresql-common-134/debian/backport-ppa 2012-07-26 13:42:12.0 +0200
@@ -26,7 +26,7 @@
for release in $RELEASES; do
dch -D$release -v$CUR_VERSION~${release} -b 'Backport'
-if [ $release = lucid -o -o $release = natty -o $release = oneiric ]; then
+if [ $release = lucid -o $release = natty -o $release = oneiric ]; then
sed -i 's/dpkg-dev.*| hardening-wrapper/hardening-wrapper/' debian/control
fi
bzr bd -S -- -sd -v$SINCE_VERSION
diff -Nru postgresql-common-132/debian/changelog postgresql-common-134/debian/changelog
--- postgresql-common-132/debian/changelog 2012-06-30 21:31:56.0 +0200
+++ postgresql-common-134/debian/changelog 2012-07-26 21:29:48.0 +0200
@@ -1,3 +1,39 @@
+postgresql-common (134) unstable; urgency=low
+
+ * debian/backport-ppa: Fix syntax error.
+ * PgCommon.pm: Drop unconditional import of Socket::IN6ADDR_ANY and only do
+the IPv6 check if it is available. This keeps this
Bug#682736: unblock: vmware-manager/0.2.0-2
On Wed, 2012-07-25 at 18:27 +1000, Alexander Zangerl wrote: Please unblock package vmware-manager the version in unstable fixes rc bug #680481, which is a file name conflict between the packages vmm and vmware-manager: both provide a program named vmm, and the man page is causing the clash. the fix consists of vmware-manager switching to use /usr/bin/vwm (note: w). Are vwm and vmm supposed to be identical, other than the name change? The version of vmm shipped in -2 appears to include new changes which are then not carried over in to vmw: +* Install all the required CPAN modules + + cpan Config::IniFiles Getopt::Long Number::Bytes::Human Term::ReadKey Text::Glob - This requires the packages libclass-methodmaker-perl libcrypt-ssleay-perl - libsoap-lite-perl libuuid-perl libxml-libxml-perl. +* Setup the config file. See either the CONFIG section above or use the sample file from /usr/share/doc/vmm -* Setup the config file. See either the CONFIG section above or use the sample file from /usr/share/doc/vmware-manager. [...] +use Number::Bytes::Human qw/format_bytes/; -use Number::Format qw/format_bytes/; use Term::ReadKey; use Text::Glob qw/match_glob glob_to_regex/; +use VMware::VIRuntime; - -my $mod=VMware::VIRuntime; -die Couldn't load the VMware SDK: maybe you haven't installed it yet?\nPlease check the README file in /usr/share/doc/vmware-manager/ for details.\n -if (!eval require $mod); -$mod-import(); [...] my $cfg = Config::IniFiles-new( -file = ($cfgfile ? $cfgfile : \*DATA), # Read defaults from __DATA__ section if we cant find a default file. -default = 'global', + -fallback = 'global', -nocase = 1, -allowempty = 1, + -handle_trailing_comment = 1, What's going on with those? 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/1343484949.18013.59.ca...@jacala.jungle.funky-badger.org
Bug#682460: unblock: boost1.50/1.50.0-1
Hi Steve, On Mon, Jul 23, 2012 at 20:26:36 -0500, Steve M. Robbins wrote: Yes, it's a judgement call, I'd agree. My thinking is that (a) it's already building on all architectures (low risk) and (b) has somewhat better support for GCC 4.7 and (c) it's Boost :-) Could providing updated boost packages in wheezy-backports be a possible alternative? Cheers, Julien signature.asc Description: Digital signature
Bug#683082: marked as done (unblock: postgresql-common/134)
Your message dated Sat, 28 Jul 2012 15:31:10 +0100 with message-id 1343485870.18013.61.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#683082: unblock: postgresql-common/134 has caused the Debian Bug report #683082, regarding unblock: postgresql-common/134 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.) -- 683082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683082 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 unblock postgresql-common/134 Hello release team, I have uploaded version 133 and 134 of postgresql-common which fixes two really important bugs which should go into Wheezy, as well as some rather harmless cleanup which I consider appropriate for Wheezy as well. Can this please considered to get an unblock request? I ran this against postgresql-9.1 and -9.2 in sid (automatic and manual tests). Debdiff attached, some notes about the individual changes: | postgresql-common (133) unstable; urgency=low | | [ Christoph Berg ] | * Add .bzrignore file. No runtime impact at all, just VCS cleanup. | * PgCommon.pm: Check IPv4 and IPv6 in next_free_port(). (Closes: #678858) This is one of the two fixes. It prevented proper working for the case that you only have IPv6 on your system. It does not change behaviour on an IPv4 system, but of course this is still a relatively intrusive change. | [ Peter Eisentraut ] | * debian/control: Add myself to Uploaders. | * debian/postgresql-common.lintian-overrides: Remove unused | binary-without-manpage overrides (files were moved to | postgresql-client-common package). Trivial. | * debian/rules: Catch errors in for loops. This causes an FTBFS on any error, which improves robustness and error detection. Package still builds fine in pbuilder as well as the Ubuntu buildds. | * pg_wrapper: Avoid Perl warnings if psql is linked against libreadline | instead of libedit, even though that is not standard anymore. This is a corner case when people build their own postgresql-9.1 package from the source with libreadline enabled, and avoids a nasty error message in that case. It does not change behaviour when using the Debian postgresql-9.1 packages. | * testsuite: Reset core limit for pg_ctl tests. | * testsuite: Allow running individual tests by passing them on the | command line. No runtime impact at all, just test suite improvements. | [ Martin Pitt ] | * pg_ctlcluster: Do not remove the PID file after SIGKILLing the | postmaster in the last-ditch effort to shut down in --force mode. This | is a potentially dangerous thing to do when trying to start a second | postmaster in parallel while the first one is still being shut down. | (see http://archives.postgresql.org/pgsql-general/2012-07/msg00475.php) This is a rather serious potential data loss bugs (happens very seldomly, but if it does it thoroughly messes up your data), the second bug which really ought to go into Wheezy. The fix is trivial (one-line patch which just drops the unlink()). | -- Martin Pitt mp...@debian.org Thu, 26 Jul 2012 13:20:10 +0200 | postgresql-common (134) unstable; urgency=low | | * debian/backport-ppa: Fix syntax error. No build/runtime impact at all, I just use this to generate uploads to https://launchpad.net/~pitti/+archive/postgresql . | * PgCommon.pm: Drop unconditional import of Socket::IN6ADDR_ANY and only do | the IPv6 check if it is available. This keeps this version backwards | compatible with Debian/Ubuntu releases with older Perl versions. This makes the fix for #678858 compatible with Perl 5.12, so that the package stays backportable to Squeeze. Thank you for considering, and let me know if you have any question or doubts. Martin -- System Information: Debian Release: wheezy/sid APT prefers quantal APT policy: (500, 'quantal') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-6-generic (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru postgresql-common-132/debian/backport-ppa postgresql-common-134/debian/backport-ppa --- postgresql-common-132/debian/backport-ppa 2012-06-06 19:55:54.0 +0200 +++ postgresql-common-134/debian/backport-ppa 2012-07-26 13:42:12.0 +0200 @@ -26,7 +26,7 @@ for release in
Re: would it be possible to reinstantiate openmeeg and ants in wheezy?
Thank you Niels -- I am reporting that I have filed those bug reports and closed #679315 (succeeded upon re-build) On Sat, 28 Jul 2012, Niels Thykier wrote: ants [...] FTBFS atm on mips, mipsel, s390 imho due to insufficient resources and might be tricky to make them build reliably What is keeping this package out is the fact there it FTBFS on mips, mipsel and s390. If your package is unsupported (or unsupportable) on these architectures, have the FTP masters remove the binaries on these architectures in unstable. #683086 Pretty much the same story as ants, though #679315 is still open despite looking fixed. Please close that bug as well. closed and opened #683085 for ftp.debian.org -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120728145041.gg16...@onerussian.com
Re: Request unblock sdl-stretch/0.3.1-3
2012/7/28 Philipp Kern pk...@debian.org: On Sat, Jul 28, 2012 at 02:02:47PM +0100, Manuel A. Fernandez Montecelo wrote: These changes that you mention, were introduced the 26th of April for 0.3.1-2, well before the release, without any bug report being submitted since then. This is what it's already authorised to migrate in the unblock. As said we don't care. The package was unable to migrate by itself so that exception is void. The package didn't migrate to testing not because of any problem of the package itself, nor the changes in -2, or while building it or bug reports, but because of a row in Package-arch-specific set in 2005 that allowed it only to be built for i386. In 2009 and 2011 the package was updated (incl. 2011, when the arch-restriction in debian/control was removed), but the restriction in that P-a-s file remained intact. So the package wasn't ever built *by buildd daemons* in amd64 arches (or any other non-386). But since it happens that we uploaders have amd64 machines, the package was actually provided in binary form for amd64 in the Debian repositories. It was never part of mips, armel or any other architecture, not even kfreebsd-amd64 where it's now built: === sdl-stretch: (you co-maintain it) = Missing build(s) on amd64 armel ia64 kfreebsd-i386 mips This might need manual action from your side. See https://buildd.debian.org/status/package.php?p=sdl-stretch = No migration to testing for 64 days. See http://release.debian.org/migration/testing.pl?package=sdl-stretch I updated -2 in April also without realising that, and about the freeze as per the notice above, I realized that this package was not being migrated to testing (-2 hadn't make it in 3 months) because of that ancient restriction in Package-arch-specific, etc. Why did -1 migrate but -2 didn't? I really don't know, but it was not due to a bug report or inherent problem. While trying to fix that and requesting removal from Package-arch-specific, I *was asked* to create -3 because a developer called Philipp Kern set it as a pre-requisite for him to remove the restriction on packages-arch-architecture [1]. And that's where we are now, otherwise the package would have already been migrated with -2, and this unblock would be a non-issue. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680275 I don't see how those ramblings relate to the two lines I objected to. They don't explain them, they just say that there was no bug report (yet). *Why* does one need to set -pipe -Wall, *why* --as-needed (whose prior absence might cause rdepends to rely on linkage to be present), *why* --no-undefined. But then I see now that it hasn't got any rdepends at all. The changes in -2 were mostly harmless, whitespace + debhelper/policy depends updates + descriptions, and only these extra BUILD options which didn't cause any problem in buildds, nor any bug reports, same in Ubuntu (they already have -3 since a few weeks, also no bugs). The same options are used in other SDL packages (so they are there for consistency). --no-undefined is present already in the current version of sdl-mixer1.2 (~17k popcon, 15% of Debian systems) before the renewed SDL-team took over; and in the testing/unstable version sdl-ttf2.0, sdl-sound1.2, sdl-net1.2 since 8 months ago. --as-needed in most SDL modules. -pipe -Wall are pet peeves of mine, present in almost all of the packages that I maintain in Debian. I am not saying that they *have* to be there, but that now that they are there, most of them I deem them innocuous and want them to be there in the future, some of the more dangerous LDFLAGS don't seem to cause problem (and they are supposed to bring hardening benefits, which incidentally it's a release goal, even if --no-undefined is not included), and so I don't want to spend time removing them from sdl-stretch. So I'm not keen on the idea of spending more time changing back things that are IMO mostly inoccuous and will be introduced again ASAP, with no evidence so far that cause problems here or in Ubuntu, when if these do indeed cause an option they are already identified and can be promptly corrected in a new upload *if they really cause harm*. Apart from that, I've been waiting most of this month for this issue to be solved, now I am embarked in other tasks. So I respect your decision as release manager/helper and agree if you don't want to approve -3 or want to remove sdl-stretch altogether, but I'm really not planning in going ahead with the changes that you request. We've all been spending more time on this that this package really deserves. Maybe some other people in SDL team will, although I know that at least some of them are on holidays and offline for a few days/weeks. Also I do not see how reverting those changes make that package FTBFS shortly after stable is released. Having -1 without changes in -3, and now that the restriction in P-a-s files is removed, will make that a binary rebuild of the
Re: Request unblock sdl-stretch/0.3.1-3
Just to be clear... 2012/7/28 Manuel A. Fernandez Montecelo manuel.montez...@gmail.com: We've all been spending more time on this that this package really deserves. I'm also including you (Philipp) in this group, for the P-a-s file and these e-mails; as well as other debian-release folks who looked at it. So please, just decide if -3 will go as it is, or not at all. Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- 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/CAPQ4b8k37n3tEFFor8=0e_3jfeackggbpk9siugule-jwyu...@mail.gmail.com
Re: Please grant freeze exception for RoarAudio related packages
(resent due to rejection due to 8-bit data in headers) Philipp Schafft writes (Re: Please grant freeze exception for RoarAudio related packages): On Sat, 2012-07-28 at 15:58 +0200, Julien Cristau wrote: On Sat, Jul 28, 2012 at 15:51:15 +0200, Philipp Schafft wrote: Will you be so kind and allow uploads for aroarfw, ckport, muroard and vclt-tools? You don't need our permission for uploading, so go ahead. Oh. I'm sorry, it was maybe my bad wording: I kindly asks if you will allow them to go into testing/wheezy. To clarify: my understanding of Philipp's position is that he objects to the presence of his name in the Maintainer field in the packages which will be released in wheezy. To change that would require updates in wheezy, of course. I don't know what the release team's view about that is. The source change would be small of course (assuming the update contains only that one change) but it obviously involves a rebuild. Ian. -- 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/20500.1218.968496.340...@chiark.greenend.org.uk
Bug#683091: unblock: freevo/1.9.2b2-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package freevo
I just found out I overlooked a RC bug in freevo; I uploaded corrected
version 1.9.2b2-4 ; see attachments; please provide exception.
unblock freevo/1.9.2b2-4
ps: I had written to d-release@d.o on 22 July
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Andrea Mennucc
E' un mondo difficile. Che vita intensa! (Tonino Carotone)
File lists identical (after any substitutions)
Control files of package freevo: lines which differ (wdiff format)
--
Depends: debconf (= 0.5) | debconf-2.0, python (= 2.6.6-7~), python-freevo (= [-1.9.2b2-3),-] {+1.9.2b2-4),+} freevo-data (= [-1.9.2b2-3),-] {+1.9.2b2-4),+} mplayer, lsdvd, console-tools | kbd, debconf, adduser, xinit
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}
Control files of package freevo-data: lines which differ (wdiff format)
---
Recommends: freevo (= [-1.9.2b2-3)-] {+1.9.2b2-4)+}
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}
Control files of package freevo-doc: lines which differ (wdiff format)
--
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}
Control files of package freevo-lirc: lines which differ (wdiff format)
---
Depends: freevo (= [-1.9.2b2-3),-] {+1.9.2b2-4),+} python-pylirc, lirc
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}
Control files of package python-freevo: lines which differ (wdiff format)
-
Recommends: freevo (= [-1.9.2b2-3)-] {+1.9.2b2-4)+}
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}
diff -Nru freevo-1.9.2b2/debian/changelog freevo-1.9.2b2/debian/changelog
--- freevo-1.9.2b2/debian/changelog 2012-03-23 10:47:46.0 +0100
+++ freevo-1.9.2b2/debian/changelog 2012-07-22 09:53:49.0 +0200
@@ -1,3 +1,10 @@
+freevo (1.9.2b2-4) unstable; urgency=low
+
+ * Bug fix: fails to install due to insserv rejecting the script
+header, thanks to Andreas Beckmann (Closes: #665741).
+
+ -- A Mennucc1 mennu...@debian.org Sun, 22 Jul 2012 09:53:46 +0200
+
freevo (1.9.2b2-3) unstable; urgency=low
* make sure the recordserver starts after dvbstreamer
diff -Nru freevo-1.9.2b2/debian/freevo.freevo_recordserver.init freevo-1.9.2b2/debian/freevo.freevo_recordserver.init
--- freevo-1.9.2b2/debian/freevo.freevo_recordserver.init 2012-03-17 09:39:54.0 +0100
+++ freevo-1.9.2b2/debian/freevo.freevo_recordserver.init 2012-07-22 09:54:03.0 +0200
@@ -1,10 +1,10 @@
#! /bin/sh
### BEGIN INIT INFO
# Provides:freevo-recordserver
-# Required-Start: $remote_fs $time dvbstreamer
-# Required-Stop:$remote_fs $time dvbstreamer
-# Should-Start:
-# Should-Stop:
+# Required-Start: $remote_fs $time
+# Required-Stop:$remote_fs $time
+# Should-Start: dvbstreamer
+# Should-Stop: dvbstreamer
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Starts the Freevo Home Theatre PC Platform Recordserver
signature.asc
Description: Digital signature
Bug#683030: unblock: vlc/2.0.3-1
On Sat, 2012-07-28 at 15:54 +0100, Adam D. Barratt wrote: Depends: vlc libav (not considered) The new libav does not have an unblock request ttbomk and from a quick look at the diff I'm not prepared to unblock it without at least some discussion (there are changes which don't appear to be mentioned in the changelog and some of the changes listed in the changelog don't actually appear tohave been made). Looking again and reading through the associated bug reports, it looks a bit better than I thought; I really shouldn't have to read through longish bug report logs to find out why a change has been made to the packaging, however. libav maintainers (Cced): - the changelog for -5 mentions making transitional packages arch:all, but not a number of removals of Multi-Arch: foreign that seem to have been applied to some packages. - the changelog also doesn't mention the dropping of the ffmpeg Provides. - this change looks slightly odd: * Do not run doxygen if it is not installed. doxygen is in B-D-Indep and only appears to be used when building the arch:all -doc package. On that basis, why would it not always be installed when required? 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/1343490475.18013.87.ca...@jacala.jungle.funky-badger.org
Bug#682279: unblock: libweb-id-perl/1.921-3
Hi Julien, and others, On 12-07-28 at 01:33pm, Julien Cristau wrote: For a request like this, if it takes more than 5 minutes to process it's a waste of our time. Having a clear changelog helps avoid that, as does not arguing or getting on your high horse when asked clarification questions. And by helping that, it helps get your request approved, which I guess is what you want? Yes, that is what I want. My apologies for not following rules and getting on my high horse. How to proceeed from here? Should I now... * Wait for you to ask clarification questions or make a verdict? * Make a new package fixing the bad things pointed out by Cyril - i.e. a) mention in changelog relevant bugs that was filed after last package release, and b) more descriptive changelog regarding how changes was made, and c) random noise reverted? * Something else? Regards, - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#683091: unblock: freevo/1.9.2b2-4
On Sat, 2012-07-28 at 17:29 +0200, A Mennucc wrote: Please unblock package freevo I just found out I overlooked a RC bug in freevo; I uploaded corrected version 1.9.2b2-4 ; see attachments; please provide exception. The RC bug appears to have been introduced in -3, which has consequently never migrated to testing; as such, the bug doesn't actually affect testing - is that correct? 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/1343492202.18013.90.ca...@jacala.jungle.funky-badger.org
Re: please unblock typo3-src for wheezy
On 28.07.2012 14:53, Julien Cristau wrote: please unblock typo3-src 4.5.17+dfsg1-1 from freeze. It is a upstream bugfix only release and contains a fix that prevents the backend of the CMS to work properly if the build-in js/css compressor is acitivated. There are no packages that depend on typo3-src so nothing will break. I'm not sure how to interpret the last sentence. If there's breakage in the package then it could affect users, surely? Sure. But that was not my intention. I wanted to express, that typo3 is leaf package and there are no checks neccessary, if other packages are affected by the changes made. I assumed that this would simplify the review process. I do not think, there would be any breakage in the package. What's typo3/contrib/extjs/resources/resources.jsb, and what's the rewrite of that file about? Same with typo3/sysext/em/res/js/ux/filter/* These are changes from upstream, as 4.5.17 is a bugfix only release of 4.5.x branch of typo3. 4.5 is a long time support version of typo3 that gets bugfixes until April 2014. -- MfG, Christian Welzel GPG-Key: pub 4096R/5117E119 2011-09-19 Fingerprint: 3688 337C 0D3E 3725 94EC E401 8D52 CDE9 5117 E119 -- 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/501411a9.4030...@camlann.de
Re: please unblock typo3-src for wheezy
On Sat, Jul 28, 2012 at 18:22:01 +0200, Christian Welzel wrote: On 28.07.2012 14:53, Julien Cristau wrote: What's typo3/contrib/extjs/resources/resources.jsb, and what's the rewrite of that file about? Same with typo3/sysext/em/res/js/ux/filter/* These are changes from upstream, as 4.5.17 is a bugfix only release of 4.5.x branch of typo3. 4.5 is a long time support version of typo3 that gets bugfixes until April 2014. I can see that they're changes from upstream. I can't see what the changes actually are because the diff is basically remove the entire file and add it back. Cheers, Julien signature.asc Description: Digital signature
Bug#683094: unblock: tuareg-mode/1:2.0.6-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package tuareg-mode
This upload fixes serious bug #681823 that made upgrading tuareg-mode from
squeeze to wheezy fail when emacs24 is installed.
Diff with the previous version in sid/wheezy:
% git diff debian/1%2.0.6-2
diff --git a/debian/changelog b/debian/changelog
index 3bb6bbe..e01ccbf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+tuareg-mode (1:2.0.6-3) unstable; urgency=low
+
+ * Updated the emacsen-install file from the current template shipped
+with dh-make to fix an upgrade failure from squeeze (closes: #681823).
+Thanks to Hilko Bengen for the patch!
+
+ -- Ralf Treinen trei...@debian.org Sat, 28 Jul 2012 14:16:52 +0200
+
tuareg-mode (1:2.0.6-2) unstable; urgency=low
* debian/emacsen-install: fix tuareg-use-smie (f - nil). Thanks to
diff --git a/debian/emacsen-install b/debian/emacsen-install
index 152e711..a268320 100644
--- a/debian/emacsen-install
+++ b/debian/emacsen-install
@@ -27,8 +27,8 @@ fi
install -m 755 -d ${ELCDIR}
cd ${ELDIR}
FILES=`echo *.el`
-cp ${FILES} ${ELCDIR}
cd ${ELCDIR}
+ln -sf ${RELELDIR}/*.el .
cat EOF path.el
(setq load-path (cons . load-path) byte-compile-warnings nil)
@@ -42,7 +42,7 @@ case ${FLAVOR} in
;;
esac
-rm -f *.el path.el path.elc
+rm -f path.el
cd ${ELCDIR}
for f in ${FILES} ; do
unblock tuareg-mode/1:2.0.6-3
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20120728170855.22114.15819.report...@seneca.free.fr
Re: please unblock typo3-src for wheezy
On 28.07.2012 18:25, Julien Cristau wrote:
I can see that they're changes from upstream. I can't see what the
changes actually are because the diff is basically remove the entire
file and add it back.
Ah, ok.
It seems someone changed all line endings from unix to windows.
I attached the diff from 4.5.16 to 4.5.17 orig tar gz without
files were only whitespaces are changed (diff -Naurw).
--
MfG, Christian Welzel
GPG-Key: pub 4096R/5117E119 2011-09-19
Fingerprint: 3688 337C 0D3E 3725 94EC E401 8D52 CDE9 5117 E119
diff -Naurw blankpackage-4.5.16/ChangeLog blankpackage-4.5.17/ChangeLog
--- blankpackage-4.5.16/ChangeLog 2012-05-22 12:03:06.0 +0200
+++ blankpackage-4.5.17/ChangeLog 2012-07-04 11:19:24.0 +0200
@@ -1,3 +1,31 @@
+2012-07-04 acf7796 [RELEASE] Release of TYPO3 4.5.17 (TYPO3 Release Team)
+2012-07-04 4356de4 #38578 [SECURITY] XSS in swfupload (Oliver Hader)
+2012-07-04 d5cb5fb #35154 [BUGFIX] Exclude E_STRICT from exceptionalErrors (Mario Rimann)
+2012-07-04 4cca68b #37615 [BUGFIX] IRRE records can't be expanded without an hidden field (Oliver Hader)
+2012-07-04 5fd49b5 #29254 [BUGFIX] TSFE-additionalFooterData for USER_INT (Oliver Hader)
+2012-07-03 15847d2 #38574 [BUGFIX] In IE9, RTE does not work correctly in compat modes IE8/IE7 (Stanislas Rolland)
+2012-07-03 9a1c36c #34786 [BUGFIX] Custom HTML tags no longer malformed in IE (Bart Dubelaar)
+2012-07-01 8ea1408 #38511 [BUGFIX] Remove a rather dubious unit test for Redis cache backend (Christian Kuhn)
+2012-06-30 353ab74 #38501 [BUGFIX] Fix unit test failure if gif compress is disabled (Susanne Moog)
+2012-06-30 74701ef #35915 [BUGFIX] VariableFrontend initializeObject not called (Daniel Pötzinger)
+2012-06-30 2cc2efb #37618 [BUGFIX] Remove class of td if No CSS styles for this table is set (Juergen Furrer)
+2012-06-30 364926e #36290 [BUGFIX] Markers (%s) are not replaced in TCEmain error messages (Bart Dubelaar)
+2012-06-29 880f256 #38357 [TASK] Add travis configuration file (Helmut Hummel)
+2012-06-29 027a9b3 #36093 [BUGFIX] Reports: Wrong indication for saltedpasswords (Markus Klein)
+2012-06-28 885d256 #37541 [BUGFIX] Declaration of tx_rtehtmlarea_base::drawRTE() not compatible (Stanislas Rolland)
+2012-06-28 50b5136 #34303 [BUGFIX] IRRE hide/unhide broken (dkd-egerer Sascha Egerer)
+2012-06-28 6918eda #34685 [TASK] PHP 5.4 adjustments (Markus Klein)
+2012-06-28 1f7ebfd #36194 [BUGFIX] Ensure $output is used as string (Peter Niederlag)
+2012-06-27 7366511 #32773 [BUGFIX] fe_adminLib.inc uses undefined function (Sven Burkert)
+2012-06-27 b82dfa5 [TASK] Raise submodule pointer (TYPO3 Release Team)
+2012-06-21 3f3c200 #36300 [BUGFIX] Properly load existing usergroups in task (Bart Dubelaar)
+2012-06-13 1e97470 #35944 [BUGFIX] Hide the field Selected Pages for menu type Sitemap (Marco Huber)
+2012-05-30 bbc55bf #21943 [BUGFIX] redirect to referrer when changing password (Jigal van Hemert)
+2012-05-28 1c43954 #37553 BUGFIX] Illegal string offset (Jigal van Hemert)
+2012-05-22 1d59cbf [TASK] Set TYPO3 version to 4.5.17-dev (TYPO3 v4 Release Team)
+2012-05-22 75b2564 [RELEASE] Release of TYPO3 4.5.16 (TYPO3 v4 Release Team)
+
+
2012-05-22 841e939 [RELEASE] Release of TYPO3 4.5.16 (TYPO3 v4 Release Team)
2012-05-22 b81c747 [TASK] Raise submodule pointer (TYPO3 v4 Release Team)
2012-05-21 d4da799 #26993 [BUGFIX] Pagetree: Copying large branches duplicates branch (Steffen Gebert)
diff -Naurw blankpackage-4.5.16/index.php blankpackage-4.5.17/index.php
--- blankpackage-4.5.16/index.php 2012-05-22 12:03:12.0 +0200
+++ blankpackage-4.5.17/index.php 2012-07-04 11:19:29.0 +0200
@@ -39,12 +39,7 @@
// Set error reporting
// ***
-if (defined('E_DEPRECATED')) {
- error_reporting(E_ALL ^ E_NOTICE ^ E_DEPRECATED);
-} else {
- error_reporting(E_ALL ^ E_NOTICE);
-}
-
+error_reporting(E_ALL ~(E_STRICT | E_NOTICE | E_DEPRECATED));
// **
// Constants defined
diff -Naurw blankpackage-4.5.16/t3lib/cache/frontend/class.t3lib_cache_frontend_variablefrontend.php blankpackage-4.5.17/t3lib/cache/frontend/class.t3lib_cache_frontend_variablefrontend.php
--- blankpackage-4.5.16/t3lib/cache/frontend/class.t3lib_cache_frontend_variablefrontend.php 2012-05-22 12:03:12.0 +0200
+++ blankpackage-4.5.17/t3lib/cache/frontend/class.t3lib_cache_frontend_variablefrontend.php 2012-07-04 11:19:29.0 +0200
@@ -62,7 +62,7 @@
* @return void
* @author Robert Lemke rob...@typo3.org
*/
- protected function initializeObject() {
+ public function initializeObject() {
$this-useIgBinary =
Re: Next upload 2012-06-26 (dpkg 1.16.5)
On Sat, 2012-07-28 at 11:45:37 +0100, Adam D. Barratt wrote: On Sat, 2012-07-28 at 12:40 +0200, Neil McGovern wrote: Oh, and also, I want to see a specific ack/nack from the SRMs for: --- dpkg-1.16.4.3/debian/source/options 2012-06-09 14:32:05.0 + +++ dpkg-1.16.8/debian/source/options 2012-07-19 12:27:34.0 + @@ -1,2 +1,2 @@ -# Use bzip2 compression by default, we save 2.5Mb -compression = bzip2 +# Use xz compression by default, we save 4.6 MiB +compression = xz afaics, this is just the upstream dpkg tarball changing compression method. Does anything actually care about that? Exactly, in Debian this should not affect anything AFAIK, the only ones who might be “affected” are dpkg downstreams, and the ones I'm tracking do not seem to have complained; but then they always have the option to repack the tarball. thanks, guillem -- 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/20120728173149.ga14...@gaara.hadrons.org
Re: Next upload 2012-06-26 (dpkg 1.16.5)
On Sat, 2012-07-28 at 11:59:07 +0200, Neil McGovern wrote: On Mon, Jul 23, 2012 at 07:18:29PM +0200, Guillem Jover wrote: On Mon, 2012-07-23 at 17:51:56 +0100, Neil McGovern wrote: Nope, 1.16.5. I'd like to see that to get a view as to why 1.16.5 was broken. Once we've managed to have a look at that, it may give a clue as to if it's worth reviewing the giant-diff-from-doom. Thanks, attached the filtered diff (with additional junk left by filterdiff, but left the changelog) from git: Right, the delta diff was small enough that I actually put in the time to look at the full diff. This took a number of hours, but anyway: Well then, thanks for taking the time. Some questions: dpkg-1.16.8/dpkg-deb/main.c - -h|--helpShow this help message.\n - --versionShow the version.\n + -?, --help Show this help message.\n + --versionShow the version.\n Why are you removing -h? Using -h (or -H) on a program that you don't know its command-line options could produce surprising effects, as such the only safe option that can be used blindly is really --help, which is unambiguous (or -? now). Keeping -h does not seem useful after those, so I removed them. It also allows for the _possibility_ of considering reusing -h for other uses in a pretty distant future, once there's no known dpkg versions with the old semantics in the wild (JFTR there's still at least dpkg 1.10.21 used on Fink, released in 2004-04). Jonathan has already replied to the other inquiries. thanks, guillem -- 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/20120728175218.gb14...@gaara.hadrons.org
Re: Please unblock: lua5.1/5.1.5-4
On Thu, Jul 26, 2012 at 4:24 PM, Julien Cristau jcris...@debian.org wrote: On Thu, Jul 26, 2012 at 16:21:10 +0800, Aron Xu wrote: On Thu, Jul 26, 2012 at 4:15 PM, Julien Cristau jcris...@debian.org wrote: On Thu, Jul 26, 2012 at 16:03:46 +0800, Aron Xu wrote: I'd like to see lua5.1/5.1.5-4 can be unblocked so I can upload fcitx to unstable, which depends on lua5.1 and has already been pre-granted an unblock. I don't see the connection. I have not tested whether building against Multiarched version of lua5.1 will affect the usability of fcitx (theoretically won't), but I think to be safe I will wait for it if an unblock can be granted to lua5.1. Sounds like something that should be tested in any case? And if it *does* impact fcitx then that would be a reason to *not* unblock lua5.1. I have tested it and the package works, I'll upload fcitx very soon. -- Regards, Aron Xu -- 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/CAMr=8w4wn54Vu1=k2ifzq+f1ek41qxsafnnpmwxb+d+fiun...@mail.gmail.com
Bug#682960: unblock (pre-approval): gnome-shell/3.4.2-1
Am 28.07.2012 15:23, schrieb Mike Miller: On Sat, Jul 28, 2012 at 11:51:06AM +0200, Laurent Bigonville wrote: Le Fri, 27 Jul 2012 19:47:41 -0400, I think both should be done as some VPN modules (like nm-strongswan) are already using a full path. Yep, I think doing both is sensible and for jessie we will certainly update affected packages to use absolute paths. As for wheezy using /usr/lib/NetworkManager is the easiest way to address this issue with the least amount of churn. +path = GLib.build_filenamev(['/usr/lib/NetworkManager/VPN', path]); Except the Debian path is /usr/lib/NetworkManager without the VPN part. Fix that, and this looks good to me. Thanks! Yeah, please fix that to use /usr/lib/NetworkManager Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#683101: unblock: pyspf/2.0.7-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pyspf Fixes RC bug 683098. unblock pyspf/2.0.7-3 diff -u pyspf-2.0.7/debian/changelog pyspf-2.0.7/debian/changelog --- pyspf-2.0.7/debian/changelog +++ pyspf-2.0.7/debian/changelog @@ -1,3 +1,10 @@ +pyspf (2.0.7-3) unstable; urgency=low + + * override dh_python3 to not act on spf-tools-python so that its shebangs +don't get rewritten to /usr/bin/python3 (Closes: #683098) + + -- Scott Kitterman sc...@kitterman.com Sat, 28 Jul 2012 14:53:59 -0400 + pyspf (2.0.7-2) unstable; urgency=low * Add debian/patches/catch_unicode_spf to correctly raise errors when SPF diff -u pyspf-2.0.7/debian/rules pyspf-2.0.7/debian/rules --- pyspf-2.0.7/debian/rules +++ pyspf-2.0.7/debian/rules @@ -49,0 +50,3 @@ + +override_dh_python3: + dh_python3 -N spf-tools-python
Bug#683101: marked as done (unblock: pyspf/2.0.7-3)
Your message dated Sat, 28 Jul 2012 20:30:03 +0100 with message-id 1343503803.18013.96.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#683101: unblock: pyspf/2.0.7-3 has caused the Debian Bug report #683101, regarding unblock: pyspf/2.0.7-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.) -- 683101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683101 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 pyspf Fixes RC bug 683098. unblock pyspf/2.0.7-3 diff -u pyspf-2.0.7/debian/changelog pyspf-2.0.7/debian/changelog --- pyspf-2.0.7/debian/changelog +++ pyspf-2.0.7/debian/changelog @@ -1,3 +1,10 @@ +pyspf (2.0.7-3) unstable; urgency=low + + * override dh_python3 to not act on spf-tools-python so that its shebangs +don't get rewritten to /usr/bin/python3 (Closes: #683098) + + -- Scott Kitterman sc...@kitterman.com Sat, 28 Jul 2012 14:53:59 -0400 + pyspf (2.0.7-2) unstable; urgency=low * Add debian/patches/catch_unicode_spf to correctly raise errors when SPF diff -u pyspf-2.0.7/debian/rules pyspf-2.0.7/debian/rules --- pyspf-2.0.7/debian/rules +++ pyspf-2.0.7/debian/rules @@ -49,0 +50,3 @@ + +override_dh_python3: + dh_python3 -N spf-tools-python ---End Message--- ---BeginMessage--- On Sat, 2012-07-28 at 15:21 -0400, Scott Kitterman wrote: Please unblock package pyspf Fixes RC bug 683098. Unblocked; thanks. Regards, Adam---End Message---
Fixing mess involving emacs23, emacs24, and the emacs metapackage
I made a bit of a mess with respect to the emacs metapackage in unstable and wheezy that I'd like to fix. The problem is that both emacs23 and emacs24 provide the emacs metapackage, and of course, at DebConf, Adam pointed out that as soon as we need updates to emacs23, we'll have a problem. One plausible solution would be to just move the emacs metapackage to its own emacs-defaults source package (a la gcc-defaults), and so a bit of discussion on IRC produced a plan that I'd like to vet here: - Upload a new emacs23 to for wheezy that doesn't provide the emacs binary. - Upload a new emacs-defaults for wheezy that provides the emacs binary. - Upload a new emacs24 to unstable that doesn't provide the emacs binary. This would require two freeze exceptions, one for the updated emacs23 package, and one for the new (trivial) emacs-defaults package. Please let me know if that sounds reasonable, or if you have some other way you'd rather handle the problem. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- 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/87ipd7vfrk@trouble.defaultvalue.org
Bug#682808: pu: package spip/2.1.1-3squeeze4
Control: tags 682808 + squeeze confirmed On Wed, 2012-07-25 at 16:16 -0400, David Prévot wrote: The spip package currently in stable is vulnerable to some security issues (#677290, #672961, #680118), the last one being pretty nasty… Having no answer from the security team, I hereby propose this update via the upcoming point release. As in #680381, the attached debdiff is pretty thin: most of the changes, in the security screen file, are due to rewritten comments. +spip (2.1.1-3squeeze4) stable-security; urgency=low + + * Non-maintainer upload by the Security Team. Please s/-security// and drop the NMU comment. + * Updated security screen to 1.1.3. Prevent cross site scripting on referer +(addresses missing bits of [CVE-2012-2151]), cross site scripting and PHP +injections in internal functions. + Closes: #680118 The alignment of the Closes: item here looks slightly odd, imho (as do the others). Please go ahead; 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/1343504430.18013.101.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#682808: pu: package spip/2.1.1-3squeeze4
Processing control commands: tags 682808 + squeeze confirmed Bug #682808 [release.debian.org] pu: package spip/2.1.1-3squeeze4 Added tag(s) squeeze and confirmed. -- 682808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682808 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.b682808.134350451724350.transcr...@bugs.debian.org
Re: haskell-cryptocipher (+yesod) entangled with pandoc
On Sat, 2012-07-28 at 16:08 +0100, Adam D. Barratt wrote: On Wed, 2012-07-25 at 19:47 +0100, Adam D. Barratt wrote: On Mon, 2012-07-23 at 23:14 +0200, Joachim Breitner wrote: A fixed pandoc has been uploaded (1.9.4.2-2) [...] Ignoring tests and the Slideous stuff makes it a little happier to look at, although it's still larger than I'd like. Unblocked in any case, let's hope it doesn't need any more help to get things unbunged. Following on from a discussion on IRC this morning, the stack including pandoc is not currently in a position to migrate, and some of the packages that have been blocked behind pandoc will lose their auto-exceptions soon. Niels's auto-hinter came up with a better solution. We've added that, together with urgenting pandoc, for tonight's britney run. 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/1343506276.18013.105.ca...@jacala.jungle.funky-badger.org
Bug#681969: unblock: xorg-server/2:1.12.3-1
On Wed, 2012-07-18 at 11:06 +0200, Julien Cristau wrote: Please unblock package xorg-server. 1.12.3 is a bugfix release made from upstream's stable branch. The debdiff contains a lot of irrelevant changes to autotools/yacc/lex-generated files, which we delete and regenerate on build anyway, so you'll find something hopefully more usable below. Unblocked, but it'll need a udeb ack before it'll migrate. 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/1343507022.18013.107.ca...@jacala.jungle.funky-badger.org
Bug#683030: unblock: vlc/2.0.3-1
On 12-07-28 at 04:47pm, Adam D. Barratt wrote: - this change looks slightly odd: * Do not run doxygen if it is not installed. doxygen is in B-D-Indep and only appears to be used when building the arch:all -doc package. On that basis, why would it not always be installed when required? I did not apply this change but recognize it from Emdebian sprint: Reason is, I believe, to ease bootstrapping new architectures by suppressing build of arch-all packages. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#683113: unblock: insighttoolkit/3.20.1+git20120521-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package insighttoolkit. Once again, please unblock insighttoolkit. This last upload fixes an issue with signalling NaN behavior on gcc 4.7 on i386 platform. This allowed running successfully the test suite of the plastimatch package (and thus fixes symptoms of #645101). For more details see #682805 Thanks unblock insighttoolkit/3.20.1+git20120521-3 -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-bpo.2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120728204532.11354.54080.report...@maester.malat.net
Bug#683113: marked as done (unblock: insighttoolkit/3.20.1+git20120521-3)
Your message dated Sat, 28 Jul 2012 21:48:09 +0100 with message-id 1343508489.18013.108.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#683113: unblock: insighttoolkit/3.20.1+git20120521-3 has caused the Debian Bug report #683113, regarding unblock: insighttoolkit/3.20.1+git20120521-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.) -- 683113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683113 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 insighttoolkit. Once again, please unblock insighttoolkit. This last upload fixes an issue with signalling NaN behavior on gcc 4.7 on i386 platform. This allowed running successfully the test suite of the plastimatch package (and thus fixes symptoms of #645101). For more details see #682805 Thanks unblock insighttoolkit/3.20.1+git20120521-3 -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-bpo.2-amd64 (SMP w/8 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--- On Sat, 2012-07-28 at 22:45 +0200, Mathieu Malaterre wrote: Please unblock package insighttoolkit. Once again, please unblock insighttoolkit. This last upload fixes an issue with signalling NaN behavior on gcc 4.7 on i386 platform. This allowed running successfully the test suite of the plastimatch package (and thus fixes symptoms of #645101). For more details see #682805 Already unblocked. Regards, Adam---End Message---
Bug#683028: unblock: libsbsms/2.0.1-1
Am Samstag, den 28.07.2012, 14:59 +0100 schrieb Adam D. Barratt: On Sat, 2012-07-28 at 00:39 +0200, Benjamin Drung wrote: Please unblock package libsbsms The new upstream release 2.0.1 contains just one bug fix (found by the Audacity developers). This bug fix touches src/buffer.cpp and src/buffer.h [1]. All other changes are just visual clutter and have no effect on the package. What happened to test/*? The entire tree seems to have vanished. Yes. It's not shipped in the source any more, but we didn't use the tests. -- Benjamin Drung Debian Ubuntu Developer signature.asc Description: This is a digitally signed message part
Bug#682808: pu: package spip/2.1.1-3squeeze4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 28/07/2012 15:40, Adam D. Barratt a écrit : Control: tags 682808 + squeeze confirmed On Wed, 2012-07-25 at 16:16 -0400, David Prévot wrote: The spip package currently in stable is vulnerable to some security issues (#677290, #672961, #680118), the last one being pretty nasty… […] Please s/-security// and drop the NMU comment. […] The alignment of the Closes: item here looks slightly odd, imho (as do the others). Changelog fixed according to your feedback, thanks. Please go ahead; thanks. Uploaded. Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQFFFfAAoJELgqIXr9/gny+MgQAIhFrw6ry5xsfnBHch24sr+d 5NpL49y3JAFiIgstU58PR6XU26XwByVRxKcBCQz79OwN63TKN5VDXNCf320T38mM f7zybN2X8Nj1KMSjBfY7Id39QsIYqRElJo3xbOafqQmIzVEBQ/dodvIPawWgkDJy rgXZzhPts9ogdhWSEkRiCoN4tjOaZN1i/mC2RAOGpr0ngnRJ+AOYcMFWd0tMCp/P aTkF9nrgM/dzLK28mUCW1DrfPqq9Dl8KNdeC9+GvYutw+dsNxnon8ZDFcg/tA4E5 /vM36PBjnL1jt8MAu4acD5WajsoMgCzTm4nMu0IhKRBKH4x24fdVGB8yOvUhuHrB nS/sgTw8hDvTbmFxLdsjU8RhgCexnTUD94y7J4msLPyxD9EhsQK5gSA4yMaZrO71 4CLe53HkZMgfBMfM3GB0KCiS3uRa+Iyjzxh2h95uZl6xUSSRIvM7ll6BnyMIuAqO RCGxmqFRGu0Ff5F/bDqbEqs+wwPGt0ieKWN8ZG6Gttmm8HzLg3bVP71f2dd3Z7mP gjSRyF3YcNdULwp42QTLJFvK6/rK3fOpqESj8e2AQVAUNM6O/HOB67Pvs/FwNjSh faPi5EiuomK651vYImgpWN36sSL5qwrQw4cAQ2wO/Up1l/BQbl+KJT0NJyr1bpXF S7BhaAj/LUPc0AOW0ovO =bKMF -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5014515f.1090...@debian.org
Bug#683119: unblock: mlt/0.8.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mlt I had to disable the --luma-compress option on mips, so that building the package does not time out anymore. With enabled luma-compressing, the luma files are also processed by /usr/bin/convert, which seems to not work and just consuming CPU cycles in this case on mips. Compressing is not necessary. unblock mlt/0.8.0-3 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-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/20120728214232.28293.80959.report...@srv1.linux-dev.org
Bug#683053: unblock: python2.7/2.7.3-2
On Saturday, July 28, 2012 02:31:50 PM Julien Cristau wrote: On Sat, Jul 28, 2012 at 03:39:51 -0400, Scott Kitterman wrote: 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). FWIW I think this is a major failure on the part of python upstream, and would rather see this change reverted. One additional data point on this issue. I finally caught up with jwilk and he did do a comprehensive search on this issue: jwilk ScottK: I believe I hunted down everything that had such a bug in unstable on Jun 17. I agree it's an upstream failing, but I still think it's better to just fix the remaining three packages. 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/4322381.YXEj4pmfeS@scott-latitude-e6320
Bug#683125: unblock: frontaccounting/2.2.10-3.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package frontaccounting
Fixes RC bugs #618771 and # 682249.
unblock frontaccounting/2.2.10-3.1
diff -Nru frontaccounting-2.2.10/debian/changelog frontaccounting-2.2.10/debian/changelog
--- frontaccounting-2.2.10/debian/changelog 2010-10-29 11:44:31.0 -0400
+++ frontaccounting-2.2.10/debian/changelog 2012-07-28 19:11:53.0 -0400
@@ -1,3 +1,19 @@
+frontaccounting (2.2.10-3.1) unstable; urgency=medium
+
+ [ Scott Kitterman ]
+ * Non-maintainer upload
+ * Urgency medium for grave data loss bug fix
+
+ [ Evgeni Golov ]
+ * Use ENGINE=x instead of TYPE=x which was deprecated since MySQL 4.1
+and removed in 5.4.4.
+Closes: #682249
+
+ [ Jamie McClelland ]
+ * Fix postinst variable quoting Closes: #618771
+
+ -- Scott Kitterman sc...@kitterman.com Sat, 28 Jul 2012 19:08:31 -0400
+
frontaccounting (2.2.10-3) unstable; urgency=low
* Fix pending l10n issues. Debconf translations:
diff -Nru frontaccounting-2.2.10/debian/patches/series frontaccounting-2.2.10/debian/patches/series
--- frontaccounting-2.2.10/debian/patches/series 2010-02-21 01:09:02.0 -0500
+++ frontaccounting-2.2.10/debian/patches/series 2012-07-28 19:08:22.0 -0400
@@ -1,3 +1,4 @@
config.default.php.patch
remove-files.patch
debian-changes-2.2.6-1
+use_engine_instead_of_type.patch
diff -Nru frontaccounting-2.2.10/debian/patches/use_engine_instead_of_type.patch frontaccounting-2.2.10/debian/patches/use_engine_instead_of_type.patch
--- frontaccounting-2.2.10/debian/patches/use_engine_instead_of_type.patch 1969-12-31 19:00:00.0 -0500
+++ frontaccounting-2.2.10/debian/patches/use_engine_instead_of_type.patch 2012-07-28 19:08:22.0 -0400
@@ -0,0 +1,1521 @@
+Description: Use ENGINE=x instead of TYPE=x
+ It was deprecated since MySQL 4.1 and removed in 5.4.4.
+Author: Evgeni Golov evg...@debian.org
+Bug-Debian: http://bugs.debian.org/682249
+Last-Update: 2012-07-21
+
+--- frontaccounting-2.2.10.orig/sql/alter2.2.sql
frontaccounting-2.2.10/sql/alter2.2.sql
+@@ -70,7 +70,7 @@ CREATE TABLE `0_audit_trail` (
+ `gl_seq` int(11) unsigned default NULL,
+PRIMARY KEY (`id`),
+ KEY (`fiscal_year`, `gl_seq`)
+-) TYPE=InnoDB ;
++) ENGINE=InnoDB ;
+
+ ALTER TABLE `0_stock_master` ADD COLUMN `no_sale` tinyint(1) NOT NULL default '0';
+ ALTER TABLE `0_currencies` ADD COLUMN `auto_update` tinyint(1) NOT NULL default '1';
+@@ -93,7 +93,7 @@ CREATE TABLE `0_security_roles` (
+ `inactive` tinyint(1) NOT NULL default '0',
+ PRIMARY KEY (`id`),
+ UNIQUE KEY `role` (`role`)
+-) TYPE=MyISAM AUTO_INCREMENT=1;
++) ENGINE=MyISAM AUTO_INCREMENT=1;
+
+ ALTER TABLE `0_company` ADD COLUMN `login_tout` SMALLINT(6) NOT NULL DEFAULT '600';
+ ALTER TABLE `0_users` CHANGE COLUMN `full_access` `role_id` int(11) NOT NULL default '1';
+@@ -119,7 +119,7 @@ CREATE TABLE `0_tags` (
+ `inactive` tinyint(1) NOT NULL default '0',
+ PRIMARY KEY (`id`),
+ UNIQUE KEY(`type`,`name`)
+-) TYPE=MyISAM AUTO_INCREMENT=1;
++) ENGINE=MyISAM AUTO_INCREMENT=1;
+
+ DROP TABLE IF EXISTS `0_tag_associations`;
+
+@@ -127,7 +127,7 @@ CREATE TABLE `0_tag_associations` (
+ `record_id` varchar(11) NOT NULL,
+ `tag_id` int(11) NOT NULL,
+ UNIQUE KEY(`record_id`,`tag_id`)
+-) TYPE=MyISAM;
++) ENGINE=MyISAM;
+
+ DROP TABLE IF EXISTS `0_useronline` ;
+
+@@ -138,7 +138,7 @@ CREATE TABLE `0_useronline` (
+ `file` varchar(100) NOT NULL default '',
+ PRIMARY KEY `id` (`id`) ,
+ KEY (`timestamp`)
+-) TYPE=MYISAM AUTO_INCREMENT=1;
++) ENGINE=MYISAM AUTO_INCREMENT=1;
+
+ ALTER TABLE `0_suppliers` ADD COLUMN `phone2` varchar(30) NOT NULL default '' AFTER `phone`;
+ ALTER TABLE `0_cust_branch` ADD COLUMN `phone2` varchar(30) NOT NULL default '' AFTER `phone`;
+--- frontaccounting-2.2.10.orig/sql/alter2.2rc.sql
frontaccounting-2.2.10/sql/alter2.2rc.sql
+@@ -12,4 +12,4 @@ CREATE TABLE `0_useronline` (
+ `file` varchar(100) NOT NULL default '',
+ PRIMARY KEY `id` (`id`) ,
+ KEY (`timestamp`)
+-) TYPE=MYISAM AUTO_INCREMENT=1;
++) ENGINE=MYISAM AUTO_INCREMENT=1;
+--- frontaccounting-2.2.10.orig/sql/alter2.1.sql
frontaccounting-2.2.10/sql/alter2.1.sql
+@@ -25,7 +25,7 @@ CREATE TABLE `0_attachments` (
+ `filetype` varchar(60) NOT NULL default '',
+ PRIMARY KEY (`id`),
+ KEY `type_no` (`type_no`,`trans_no`)
+-) TYPE=MyISAM AUTO_INCREMENT=1 ;
++) ENGINE=MyISAM AUTO_INCREMENT=1 ;
+
+ DROP TABLE IF EXISTS `0_groups`;
+
+@@ -35,7 +35,7 @@ CREATE TABLE `0_groups` (
+ `inactive` tinyint(1) NOT NULL default 0,
+ PRIMARY KEY (`id`),
+ UNIQUE KEY `description` (`description`)
+-) TYPE=MyISAM AUTO_INCREMENT=1 ;
++) ENGINE=MyISAM AUTO_INCREMENT=1 ;
+
+ INSERT INTO `0_groups` VALUES ('1', 'Small', '0');
+ INSERT INTO `0_groups` VALUES ('2', 'Medium', '0');
+@@ -56,7 +56,7 @@ CREATE TABLE `0_recurrent_invoices` (
+ `last_sent` date NOT NULL default '-00-00',
+ PRIMARY KEY (`id`),
Re: Orca shortcuts
Hello, (writting with my release assistant hat on, and cc-ing the release team accordingly.) Jason White ja...@jasonjgw.net (29/07/2012): It's unrealistic to expect the accessibility to work smoothly in 3.4, which will be released with Wheezy. For example, the log-out dialogue is not accessible and, so far as I know, the patches to fix that won't arrive until 3.6. Debian is already stabilizing its release, which limits the patches that can go in. While I understand it's hard to be talking about backporting patches to 3.4 that haven't been written/merged for 3.6 yet, I can assure you that the release team will be happy to see such patches being proposed for wheezy. As for the needed work, I'm pretty sure the almighty Gnome team will be able to craft something up. On the other hand, where there is a well tested patch that is known to work, the recent Mozilla bugs show that Debian can accept it into Wheezy with permission of the release team. So, I would say, definitely pursue it if you have a patch which is known to work and not to break anything, but your prospects are constrained otherwise. Definitely. Mraw, KiBi. signature.asc Description: Digital signature
Bug#683142: unblock: bdii/5.2.12-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception unblock bdii/5.2.12-1 Hi! The bdii package was removed from testing due to an RC bug, together with the packages that depends on it. The 5.2.12-1 update fixes the RC bug (bug #663444). I would like to request a freeze exception for this update to allow the bdii package and the packages depending on it to be part of the release. Mattias smime.p7s Description: S/MIME cryptographic signature
