Re: [Pkg-mediawiki-devel] Bug#700595: mediawiki: Upstream bug: Bug 39635 - PostgreSQL LOCK IN SHARE MODE option is a syntax error
On Wed, 27 Feb 2013, Adam D. Barratt wrote: As a side note, the changelog didn't really need: + * Note: these changes were part of this upload, even though +they were not detailed in this changelog entry when uploading: which will look a little odd to those perusing the changelog in future rather than diffing it, I suspect. Ah well. Hm, do you have a better wording for changelog entries that were supposed to accompany the changes of a past upload but had been forgotten? I thought adding them “after the fact” to the older version but marking them specially would be somewhat clearer than adding them to the newer version, since the changes themselves slipped in with the older one. But then, I’m not an English native speaker… bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- 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/alpine.deb.2.02.1302281024570.23...@tglase.lan.tarent.de
Bug#698245: unblock: moodle/2.2.3.dfsg-2.6~wheezy2
Hi Thomasz, Le mercredi, 23 janvier 2013 23.57:39, Jonathan Wiltshire a écrit : Le samedi, 19 janvier 2013 14.37:39, Tomasz Muras a écrit : CVE numbers added, new changelog entry copied below for your convenience. MSA-13-0001 has no CVE assigned. Newest package available at: dget http://dev.agilesparkle.com/moodle_2.2.3.dfsg-2.6~wheezy2.dsc Seems good to me; now waiting on the release team's opinion I would be happy to accept the patches proposed, but they need fixing in unstable first if they have not been already. Did you plan to prepare an update for Moodle 2.2 on unstable ? It would be good to get the latest security fixes in unstable soon and then to wheezy. Cheers, OdyX -- 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/201302281303.26215.o...@debian.org
Re: [Pkg-mediawiki-devel] Bug#700595: mediawiki: Upstream bug: Bug 39635 - PostgreSQL LOCK IN SHARE MODE option is a syntax error
On 28.02.2013 09:26, Thorsten Glaser wrote: On Wed, 27 Feb 2013, Adam D. Barratt wrote: As a side note, the changelog didn't really need: + * Note: these changes were part of this upload, even though +they were not detailed in this changelog entry when uploading: which will look a little odd to those perusing the changelog in future rather than diffing it, I suspect. Ah well. Hm, do you have a better wording for changelog entries that were supposed to accompany the changes of a past upload but had been forgotten? I'd just have included them in the older changelog stanza as is and noted in the current version that I'd added them; there's no particular need to know in future versions that they were added after the fact. ymmv. 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/0a3c3952904086e7d2abb2c9bae10...@mail.adsl.funky-badger.org
Re: [Pkg-mediawiki-devel] Bug#700595: mediawiki: Upstream bug: Bug 39635 - PostgreSQL LOCK IN SHARE MODE option is a syntax error
On Thu, 28 Feb 2013, Adam D. Barratt wrote: I'd just have included them in the older changelog stanza as is and noted in the current version that I'd added them; there's no particular need to know in future versions that they were added after the fact. ymmv. OK, thanks, will do that next time. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- 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/alpine.deb.2.02.1302281412130.23...@tglase.lan.tarent.de
Bug#701882: release.debian.org: unblock: chef/10.12.0-3
Package: release.debian.org
Severity: normal
The security fix in ruby-json 1.7.3-3 broke chef, and this is worked
around in the just-uploaded 10.12.0-3 version of chef. Please unblock
this version.
Debdiff attached.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
diff -Nru chef-10.12.0/debian/changelog chef-10.12.0/debian/changelog
--- chef-10.12.0/debian/changelog 2012-08-05 21:04:52.0 +0200
+++ chef-10.12.0/debian/changelog 2013-02-28 14:07:45.0 +0100
@@ -1,3 +1,10 @@
+chef (10.12.0-3) unstable; urgency=high
+
+ * Backport fixes from 10.22 to work around API breakage in JSON gem.
+Closes: #701629
+
+ -- Tollef Fog Heen tfh...@debian.org Thu, 28 Feb 2013 13:56:32 +0100
+
chef (10.12.0-2) unstable; urgency=low
* Team upload
diff -Nru chef-10.12.0/debian/patches/json_create_CVE-2013-0269_workaround.diff chef-10.12.0/debian/patches/json_create_CVE-2013-0269_workaround.diff
--- chef-10.12.0/debian/patches/json_create_CVE-2013-0269_workaround.diff 1970-01-01 01:00:00.0 +0100
+++ chef-10.12.0/debian/patches/json_create_CVE-2013-0269_workaround.diff 2013-02-28 13:54:47.0 +0100
@@ -0,0 +1,165 @@
+diff --git a/lib/chef/cookbook_version.rb b/lib/chef/cookbook_version.rb
+index 1c2deef..c7c9503 100644
+--- a/lib/chef/cookbook_version.rb
b/lib/chef/cookbook_version.rb
+@@ -807,7 +807,7 @@ class Chef
+ cookbook_version.manifest = o
+
+ # We don't need the following step when we decide to stop supporting deprecated operators in the metadata (e.g. , )
+- cookbook_version.manifest[metadata] = JSON.parse(cookbook_version.metadata.to_json)
++ cookbook_version.manifest[metadata] = Chef::JSONCompat.from_json(cookbook_version.metadata.to_json)
+
+ cookbook_version.freeze_version if o[frozen?]
+ cookbook_version
+diff --git a/lib/chef/json_compat.rb b/lib/chef/json_compat.rb
+index 9f59a41..4e14a11 100644
+--- a/lib/chef/json_compat.rb
b/lib/chef/json_compat.rb
+@@ -24,6 +24,22 @@ class Chef
+ class JSONCompat
+ JSON_MAX_NESTING = 1000
+
++JSON_CLASS = json_class.freeze
++
++CHEF_APICLIENT = Chef::ApiClient.freeze
++CHEF_CHECKSUM = Chef::Checksum.freeze
++CHEF_COOKBOOKVERSION= Chef::CookbookVersion.freeze
++CHEF_DATABAG= Chef::DataBag.freeze
++CHEF_DATABAGITEM= Chef::DataBagItem.freeze
++CHEF_ENVIRONMENT= Chef::Environment.freeze
++CHEF_NODE = Chef::Node.freeze
++CHEF_ROLE = Chef::Role.freeze
++CHEF_SANDBOX= Chef::Sandbox.freeze
++CHEF_RESOURCE = Chef::Resource.freeze
++CHEF_RESOURCECOLLECTION = Chef::ResourceCollection.freeze
++CHEF_WEBUIUSER = Chef::WebUIUser.freeze
++CHEF_OPENIDREGISTRAION = Chef::OpenIDRegistration.freeze
++
+ class self
+ # See CHEF-1292/PL-538. Increase the max nesting for JSON, which defaults
+ # to 19, and isn't enough for some (for example, a Node within a Node)
+@@ -38,7 +54,49 @@ class Chef
+
+ # Just call the JSON gem's parse method with a modified :max_nesting field
+ def from_json(source, opts = {})
+-::JSON.parse(source, opts_add_max_nesting(opts))
++obj = ::Yajl::Parser.parse(source)
++
++unless obj.kind_of?(Hash) || obj.kind_of?(Array)
++ raise JSON::ParserError, Top level JSON object must be a Hash or Array (actual: #{obj.class})
++end
++
++# The old default in the json gem (which we are mimicing because we
++# sadly rely on this misfeature) is to create additions i.e., convert
++# JSON objects into ruby objects. Explicit :create_additions = false
++# is required to turn it off.
++if opts[:create_additions].nil? || opts[:create_additions]
++ map_to_rb_obj(obj)
++else
++ obj
++end
++ rescue Yajl::ParseError = e
++raise JSON::ParserError, e.message
++ end
++
++ # Look at an object that's a basic type (from json parse) and convert it
++ # to an instance of Chef classes if desired.
++ def map_to_rb_obj(json_obj)
++res = case json_obj
++when Hash
++ mapped_hash = map_hash_to_rb_obj(json_obj)
++ if json_obj.has_key?(JSON_CLASS) (class_to_inflate = class_for_json_class(json_obj[JSON_CLASS]))
++class_to_inflate.json_create(mapped_hash)
++ else
++mapped_hash
++ end
++when Array
++ json_obj.map {|e| map_to_rb_obj(e) }
++else
++ json_obj
++end
++res
++ end
++
++ def map_hash_to_rb_obj(json_hash)
++json_hash.each do |key, value|
++ json_hash[key] = map_to_rb_obj(value)
++end
++json_hash
+ end
+
+ def to_json(obj, opts = nil)
+@@ -48,6 +106,44 @@ class Chef
+ def to_json_pretty(obj, opts = nil)
+ ::JSON.pretty_generate(obj,
Bug#701882: marked as done (release.debian.org: unblock: chef/10.12.0-3)
Your message dated Thu, 28 Feb 2013 13:36:19 +
with message-id 13d755de8c53630a6b6701f34bac3...@mail.adsl.funky-badger.org
and subject line Re: Bug#701882: release.debian.org: unblock: chef/10.12.0-3
has caused the Debian Bug report #701882,
regarding release.debian.org: unblock: chef/10.12.0-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.)
--
701882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
Severity: normal
The security fix in ruby-json 1.7.3-3 broke chef, and this is worked
around in the just-uploaded 10.12.0-3 version of chef. Please unblock
this version.
Debdiff attached.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
diff -Nru chef-10.12.0/debian/changelog chef-10.12.0/debian/changelog
--- chef-10.12.0/debian/changelog 2012-08-05 21:04:52.0 +0200
+++ chef-10.12.0/debian/changelog 2013-02-28 14:07:45.0 +0100
@@ -1,3 +1,10 @@
+chef (10.12.0-3) unstable; urgency=high
+
+ * Backport fixes from 10.22 to work around API breakage in JSON gem.
+Closes: #701629
+
+ -- Tollef Fog Heen tfh...@debian.org Thu, 28 Feb 2013 13:56:32 +0100
+
chef (10.12.0-2) unstable; urgency=low
* Team upload
diff -Nru chef-10.12.0/debian/patches/json_create_CVE-2013-0269_workaround.diff chef-10.12.0/debian/patches/json_create_CVE-2013-0269_workaround.diff
--- chef-10.12.0/debian/patches/json_create_CVE-2013-0269_workaround.diff 1970-01-01 01:00:00.0 +0100
+++ chef-10.12.0/debian/patches/json_create_CVE-2013-0269_workaround.diff 2013-02-28 13:54:47.0 +0100
@@ -0,0 +1,165 @@
+diff --git a/lib/chef/cookbook_version.rb b/lib/chef/cookbook_version.rb
+index 1c2deef..c7c9503 100644
+--- a/lib/chef/cookbook_version.rb
b/lib/chef/cookbook_version.rb
+@@ -807,7 +807,7 @@ class Chef
+ cookbook_version.manifest = o
+
+ # We don't need the following step when we decide to stop supporting deprecated operators in the metadata (e.g. , )
+- cookbook_version.manifest[metadata] = JSON.parse(cookbook_version.metadata.to_json)
++ cookbook_version.manifest[metadata] = Chef::JSONCompat.from_json(cookbook_version.metadata.to_json)
+
+ cookbook_version.freeze_version if o[frozen?]
+ cookbook_version
+diff --git a/lib/chef/json_compat.rb b/lib/chef/json_compat.rb
+index 9f59a41..4e14a11 100644
+--- a/lib/chef/json_compat.rb
b/lib/chef/json_compat.rb
+@@ -24,6 +24,22 @@ class Chef
+ class JSONCompat
+ JSON_MAX_NESTING = 1000
+
++JSON_CLASS = json_class.freeze
++
++CHEF_APICLIENT = Chef::ApiClient.freeze
++CHEF_CHECKSUM = Chef::Checksum.freeze
++CHEF_COOKBOOKVERSION= Chef::CookbookVersion.freeze
++CHEF_DATABAG= Chef::DataBag.freeze
++CHEF_DATABAGITEM= Chef::DataBagItem.freeze
++CHEF_ENVIRONMENT= Chef::Environment.freeze
++CHEF_NODE = Chef::Node.freeze
++CHEF_ROLE = Chef::Role.freeze
++CHEF_SANDBOX= Chef::Sandbox.freeze
++CHEF_RESOURCE = Chef::Resource.freeze
++CHEF_RESOURCECOLLECTION = Chef::ResourceCollection.freeze
++CHEF_WEBUIUSER = Chef::WebUIUser.freeze
++CHEF_OPENIDREGISTRAION = Chef::OpenIDRegistration.freeze
++
+ class self
+ # See CHEF-1292/PL-538. Increase the max nesting for JSON, which defaults
+ # to 19, and isn't enough for some (for example, a Node within a Node)
+@@ -38,7 +54,49 @@ class Chef
+
+ # Just call the JSON gem's parse method with a modified :max_nesting field
+ def from_json(source, opts = {})
+-::JSON.parse(source, opts_add_max_nesting(opts))
++obj = ::Yajl::Parser.parse(source)
++
++unless obj.kind_of?(Hash) || obj.kind_of?(Array)
++ raise JSON::ParserError, Top level JSON object must be a Hash or Array (actual: #{obj.class})
++end
++
++# The old default in the json gem (which we are mimicing because we
++# sadly rely on this misfeature) is to create additions i.e., convert
++# JSON objects into ruby objects. Explicit :create_additions = false
++# is required to turn it off.
++if opts[:create_additions].nil? || opts[:create_additions]
++ map_to_rb_obj(obj)
++else
++ obj
++end
++ rescue Yajl::ParseError = e
++raise JSON::ParserError, e.message
++ end
++
++ # Look at an object that's a basic type (from json parse) and convert it
++ # to an instance of
release date for debian wheezy?
Hello. Is there a release date for debian squeeze to stable ? -- 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/201302281606.13084.heiko.er...@aschershain.de
Bug#701833: unblock: pigz/2.2.4-2
On Wed, Feb 27, 2013 at 21:05:45 +0100, Eduard Bloch wrote: Hallo, * Thijs Kinkhorst [Wed, Feb 27 2013, 06:52:05PM]: Package pigz/2.2.4-2 was uploaded to sid fixing CVE-2013-0296 (#700608). The maintainer also added hardening flags. This may be on the border of acceptable/unacceptable for an unblock. Please let me know either way. Thanks for reporting. If the hardening flags are not acceptable I can just build another revision disabling them. Just tell me soon enough. I'd prefer to have the security fix on its own. Thanks, Julien signature.asc Description: Digital signature
Re: release date for debian wheezy?
On Thu, Feb 28, 2013 at 16:06:13 +0100, heiko wrote: Hello. Is there a release date for debian squeeze to stable ? February 6th, 2011. As for $subject, when it's ready, and sooner if you help. Cheers, Julien signature.asc Description: Digital signature
Bug#698245: unblock: moodle/2.2.3.dfsg-2.6~wheezy2
Hi Thomas, and thanks for this package, sorry for my misguided mail earlier, apparently yours just missed my inbox. Le lundi, 28 janvier 2013 18.38:49, Tomasz Muras a écrit : The package for unstable is available at: dget http://dev.agilesparkle.com/moodle_2.2.7.dfsg-1.dsc Please review upload to unstable. It contains all upstream fixes + CURL issue patch. One important thing: this is not Moodle 2.2.7. That's the weekly release of Moodle 2.2, released after 2.2.7. So the version is IMHO wrong and should instead be something like 2.2.7+20130125.dfsg-1 . Even if I usually try to stick to released tarballs, in the specific case of Moodle I'm fine with relasing weekly snapshots, but they must be versionned correctly. Other than that, the package looks good to me, besides the usual- but-not-worse-than-before embedded libraries such as TinyMCE (3.4.9, tiny_mce.js, tiny_mce_popup.js and tiny_mce_src.js), HTMLPurifier.php and YUI (3.4.1). So please just re-issue a correctly-versionned Debian package and I'll upload it to unstable (then we'll take a look at the package for testing-proposed- updates). OdyX -- 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/201302281800.19687.o...@debian.org
Bug#701923: unblock: btrfs-tools/0.19+20120328-7.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, please ack the following patch for a rc bug fix through tpu. Thanks, Julien diff -Nru btrfs-tools-0.19+20120328/debian/changelog btrfs-tools-0.19+20120328/debian/changelog --- btrfs-tools-0.19+20120328/debian/changelog 2012-06-29 17:57:00.0 +0200 +++ btrfs-tools-0.19+20120328/debian/changelog 2013-02-28 19:54:50.0 +0100 @@ -1,3 +1,11 @@ +btrfs-tools (0.19+20120328-7.1) wheezy; urgency=low + + * Non-maintainer upload. + * Move udev rules file from 60-btrfs.rules to 70-btrfs.rules so it runs +after blkid (closes: #701642). Thanks, Bastian Blank! + + -- Julien Cristau jcris...@debian.org Thu, 28 Feb 2013 19:54:48 +0100 + btrfs-tools (0.19+20120328-7) unstable; urgency=low * Using official package-type for udeb packages in control now. diff -Nru btrfs-tools-0.19+20120328/debian/rules btrfs-tools-0.19+20120328/debian/rules --- btrfs-tools-0.19+20120328/debian/rules 2012-06-29 03:40:53.0 +0200 +++ btrfs-tools-0.19+20120328/debian/rules 2013-02-28 19:52:46.0 +0100 @@ -27,7 +27,7 @@ done # Adding udev integration - install -D -m 0644 debian/local/btrfs.udev debian/btrfs-tools/lib/udev/rules.d/60-btrfs.rules + install -D -m 0644 debian/local/btrfs.udev debian/btrfs-tools/lib/udev/rules.d/70-btrfs.rules # Adding initramfs-tools integration install -D -m 0755 debian/local/btrfs.hook debian/btrfs-tools/usr/share/initramfs-tools/hooks/btrfs signature.asc Description: Digital signature
r-cran-dosnow fix for 700498 cannot migrate to testing
Hi Dirk, The fix for #700498 is currently stuck in unstable due to a dependency on a versioned dependency on r-base (or an binary built by r-base). At this point we are not ready to accept the changes to r-base for Wheezy. So, I was hoping that we convince you to upload a fix for #700498 to testing-proposed-updates. ~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/512fb1e1.8050...@thykier.net
Bug#701833: unblock: pigz/2.2.4-2
Hallo,
* Julien Cristau [Thu, Feb 28 2013, 05:14:08PM]:
On Wed, Feb 27, 2013 at 21:05:45 +0100, Eduard Bloch wrote:
Hallo,
* Thijs Kinkhorst [Wed, Feb 27 2013, 06:52:05PM]:
Package pigz/2.2.4-2 was uploaded to sid fixing CVE-2013-0296 (#700608).
The maintainer also added hardening flags. This may be on the border of
acceptable/unacceptable for an unblock. Please let me know either way.
Thanks for reporting. If the hardening flags are not acceptable I can
just build another revision disabling them. Just tell me soon enough.
I'd prefer to have the security fix on its own.
Ok, here we go. pigz 2.2.4-3 is uploaded, debian-diff and debdiff
attached here (note: debdiff gets slightly confused on hardlinks).
Regards,
Eduard.
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in second .deb but not in first
-
-rw-r--r-- root/root /usr/share/man/man1/pigz.1.gz
-rwxr-xr-x root/root /usr/bin/unpigz
hrw-r--r-- root/root /usr/share/man/man1/unpigz.1.gz link to
./usr/share/man/man1/pigz.1.gz
hrwxr-xr-x root/root /usr/bin/pigz link to ./usr/bin/unpigz
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/share/man/man1/unpigz.1.gz
-rwxr-xr-x root/root /usr/bin/pigz
hrw-r--r-- root/root /usr/share/man/man1/pigz.1.gz link to
./usr/share/man/man1/unpigz.1.gz
hrwxr-xr-x root/root /usr/bin/unpigz link to ./usr/bin/pigz
Control files: lines which differ (wdiff format)
Version: [-2.2.4-1-] {+2.2.4-3+}
diff -Nurd pigz_2.2.4-1.debian/debian/changelog pigz_2.2.4-3.debian/debian/changelog
--- pigz_2.2.4-1.debian/debian/changelog 2012-05-08 22:59:23.0 +0200
+++ pigz_2.2.4-3.debian/debian/changelog 2013-02-28 20:17:36.0 +0100
@@ -1,3 +1,17 @@
+pigz (2.2.4-3) unstable; urgency=low
+
+ * removed hardening flags, this build is targeting Wheezy
+
+ -- Eduard Bloch bl...@debian.org Thu, 28 Feb 2013 20:16:03 +0100
+
+pigz (2.2.4-2) unstable; urgency=high
+
+ * Use 600 permissions for unfinished output files (CVE-2013-0296,
+closes: #700608)
+ * started applying Debian hardening flags
+
+ -- Eduard Bloch bl...@debian.org Sat, 23 Feb 2013 13:44:42 +0100
+
pigz (2.2.4-1) unstable; urgency=low
* New upstream release
diff -Nurd pigz_2.2.4-1.debian/debian/patches/series pigz_2.2.4-3.debian/debian/patches/series
--- pigz_2.2.4-1.debian/debian/patches/series 2012-05-01 13:02:06.0 +0200
+++ pigz_2.2.4-3.debian/debian/patches/series 2013-02-28 20:15:20.0 +0100
@@ -0,0 +1 @@
+strict_temp_file_permissions
diff -Nurd pigz_2.2.4-1.debian/debian/patches/strict_temp_file_permissions pigz_2.2.4-3.debian/debian/patches/strict_temp_file_permissions
--- pigz_2.2.4-1.debian/debian/patches/strict_temp_file_permissions 1970-01-01 01:00:00.0 +0100
+++ pigz_2.2.4-3.debian/debian/patches/strict_temp_file_permissions 2013-02-28 20:14:29.0 +0100
@@ -0,0 +1,22 @@
+Index: pigz/pigz.c
+===
+--- pigz-2.2.4/pigz.c (Revision 4038)
pigz-2.2.5/pigz.c (Arbeitskopie)
+@@ -3228,7 +3228,7 @@
+ memcpy(out, to, len);
+ strcpy(out + len, decode ? : sufx);
+ outd = open(out, O_CREAT | O_TRUNC | O_WRONLY |
+- (force ? 0 : O_EXCL), 0666);
++ (force ? 0 : O_EXCL), 0600);
+
+ /* if exists and not -f, give user a chance to overwrite */
+ if (outd 0 errno == EEXIST isatty(0) verbosity) {
+@@ -3244,7 +3244,7 @@
+ } while (ch != EOF ch != '\n' ch != '\r');
+ if (reply == 1)
+ outd = open(out, O_CREAT | O_TRUNC | O_WRONLY,
+-0666);
++0600);
+ }
+
+ /* if exists and no overwrite, report and go on to next */
signature.asc
Description: Digital signature
Bug#701923: unblock: btrfs-tools/0.19+20120328-7.1
Control: tags -1 + confirmed On Thu, 2013-02-28 at 20:17 +0100, Julien Cristau wrote: +btrfs-tools (0.19+20120328-7.1) wheezy; urgency=low + + * Non-maintainer upload. + * Move udev rules file from 60-btrfs.rules to 70-btrfs.rules so it runs +after blkid (closes: #701642). Thanks, Bastian Blank! 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/1362080702.32751.3.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#701923: unblock: btrfs-tools/0.19+20120328-7.1
Processing control commands: tags -1 + confirmed Bug #701923 [release.debian.org] unblock: btrfs-tools/0.19+20120328-7.1 Added tag(s) confirmed. -- 701923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701923 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.b701923.13620807158195.transcr...@bugs.debian.org
Bug#701833: marked as done (unblock: pigz/2.2.4-2)
Your message dated Thu, 28 Feb 2013 20:52:39 +0100 with message-id 20130228195239.gn5...@radis.cristau.org and subject line Re: Bug#701833: unblock: pigz/2.2.4-2 has caused the Debian Bug report #701833, regarding unblock: pigz/2.2.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.) -- 701833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi RT, Package pigz/2.2.4-2 was uploaded to sid fixing CVE-2013-0296 (#700608). The maintainer also added hardening flags. This may be on the border of acceptable/unacceptable for an unblock. Please let me know either way. If unacceptable I propose that I make an upload to wheezy-security as a guinea pig(z) for the setup, as according to my information it should now be operational. unblock pigz/2.2.4-2 Thanks, Thijs ---End Message--- ---BeginMessage--- On Thu, Feb 28, 2013 at 20:39:10 +0100, Eduard Bloch wrote: Hallo, * Julien Cristau [Thu, Feb 28 2013, 05:14:08PM]: On Wed, Feb 27, 2013 at 21:05:45 +0100, Eduard Bloch wrote: Hallo, * Thijs Kinkhorst [Wed, Feb 27 2013, 06:52:05PM]: Package pigz/2.2.4-2 was uploaded to sid fixing CVE-2013-0296 (#700608). The maintainer also added hardening flags. This may be on the border of acceptable/unacceptable for an unblock. Please let me know either way. Thanks for reporting. If the hardening flags are not acceptable I can just build another revision disabling them. Just tell me soon enough. I'd prefer to have the security fix on its own. Ok, here we go. pigz 2.2.4-3 is uploaded, debian-diff and debdiff attached here (note: debdiff gets slightly confused on hardlinks). Much appreciated, thanks. Unblocked. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Re: r-cran-dosnow fix for 700498 cannot migrate to testing
Hi Niels, On 28 February 2013 at 20:37, Niels Thykier wrote: | Hi Dirk, | | The fix for #700498 is currently stuck in unstable due to a dependency | on a versioned dependency on r-base (or an binary built by r-base). At | this point we are not ready to accept the changes to r-base for Wheezy. | So, I was hoping that we convince you to upload a fix for #700498 to | testing-proposed-updates. Sure -- always happy to help the releases. But could you be a tiny bit more explicit and tell me what you want me to fix, where I need to upload, etc or I may get this messed. The changelog doesn't show me what I did wrong: r-cran-dosnow (1.0.6-2) unstable; urgency=low * debian/control: Added r-cran-snow to Depends(Closes: #700498) * debian/control: Set Build-Depends: to current R version * debian/control: Set Standards-Version: to current version -- Dirk Eddelbuettel e...@debian.org Wed, 13 Feb 2013 09:33:14 -0600 Are you asking for a build under a different R version? Couldn't you just make a binary NMU with a different Build-Depends? We have an informal policy to release r-cran-* packages _for unstable_. So I always encode the then-current version via Build-Depends. On Feb 13, that will have been R 2.15.2 aka r-base-core_2.15.2. Upstream for r-cran-dosnow has much weaker requirements. It would probably build on stable... but I frankly do not know where to upload to. The version in unstable has the correct control file. Dirk, generally busy | | ~Niels | -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.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/20783.46784.550132.191...@max.nulle.part
Bug#701178: preapproval unblock: dspam/dspam/3.10.1+dfsg-9
On Fri, Feb 22, 2013 at 14:01:45 +0100, Thomas Preud'homme wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package dspam [Sorry Jonathan for the duplicate] Current dspam is affected by a corruption of message headers when releasing from quarantine. This has for effect that mails are lost when releasing from quarantine. A patch has been commited upstream but there is some concern about buffer overflow. Hence, although the patch was initially backported in sid, it was subsequently removed. See [1] for the previous discussion. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698701#32 Today I've been working on a patch to solve the problem without security concern. The patch is not pretty, I know it, but it should do its job. The patch makes sure recipient points to an area of size at least 256 bytes. It wasn't always the case initially. The list of place where recipient pointer is set is: % egrep -RIn recipient[^s]*= src src/dspam.c:503:ATX-recipient = CTX-username; src/dspam.c:948:ATX-recipient=args; src/dspam.c:1675: ATX-recipient = node_rcpt-ptr; src/dspam.c:1683: ATX-recipient = node_nt-ptr; src/dspam.c:1694: ATX-recipient = mailbox; mailbox and args are of respective size 256 and 1024 bytes. node_rcpt-ptr and node_nt-ptr on the other hand are exactly the size of the string. They are allocated when calling nt_add (which call nt_node_create). Thus, the approach is to copy node_rcpt-ptr and node_nt-ptr into an array of size 256 as well and this size can be used to limit the strlcpy when copying CTX-username to ATX-recipient. I don't like to hardcode the size but didn't find anything better for now. I'll forward upstream and let him find a long term solution. See attached debdiff for details. That debdiff is for 3.10.2 in sid. Do you have one for 3.10.1? Thanks, Julien signature.asc Description: Digital signature
Bug#699882: pre-approval: elmerfem/6.1.0.svn.5396.dfsg2-2
On Wed, Feb 6, 2013 at 11:57:23 +0200, Boris Pek wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, I request permission to upload elmerfem 6.1.0.svn.5396.dfsg2-2 into unstable, targeted at wheezy. Diff is quite big (see attachment), but there is only one way to fix RC bug #698527 now: remove ElmerGUI and all related stuff. Ack, please go ahead. Cheers, Julien signature.asc Description: Digital signature
Processed: tagging 699882
Processing commands for cont...@bugs.debian.org: tags 699882 + confirmed Bug #699882 [release.debian.org] pre-approval: elmerfem/6.1.0.svn.5396.dfsg2-2 Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 699882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699882 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.136208166616110.transcr...@bugs.debian.org
Bug#700699: marked as done (unblock: sundials/2.5.0-3)
Your message dated Thu, 28 Feb 2013 20:07:36 +
with message-id 1362082056.32751.4.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#700699: unblock: sundials/2.5.0-2
has caused the Debian Bug report #700699,
regarding unblock: sundials/2.5.0-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.)
--
700699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700699
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
Hello,
Could you unblock sundials version 2.5.0-2 ? It would fix the RC bug
#700525 (fix by Christophe).
The change is basically adding -lblas -llapack -lm to LDFLAGS
debdiff attached.
Thanks
Sylvestre
diff -u sundials-2.5.0/debian/changelog sundials-2.5.0/debian/changelog
--- sundials-2.5.0/debian/changelog
+++ sundials-2.5.0/debian/changelog
@@ -1,3 +1,10 @@
+sundials (2.5.0-2) unstable; urgency=low
+
+ * debian/rules:
+ - Add -lblas -llapack -lm to LDFLAGS (closes: #700525)
+
+ -- Christophe Trophime christophe.troph...@lncmi.cnrs.fr Fri, 15 Feb 2013 11:40:09 +0100
+
sundials (2.5.0-1) unstable; urgency=low
* New upstream release
reverted:
--- sundials-2.5.0/debian/libsundials-cvodes1.install
+++ sundials-2.5.0.orig/debian/libsundials-cvodes1.install
@@ -1 +0,0 @@
-usr/lib/libsundials_cvodes.so.*
diff -u sundials-2.5.0/debian/rules sundials-2.5.0/debian/rules
--- sundials-2.5.0/debian/rules
+++ sundials-2.5.0/debian/rules
@@ -11,6 +11,7 @@
#LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)
#CFLAGS+=$(HARDENING_CFLAGS)
#LDFLAGS+=$(HARDENING_LDFLAGS)
+LDFLAGS+=-lblas -llapack -lm
debusr := $(DEB_DESTDIR)usr
debexp = debian/libsundials-serial-dev/usr/share/doc/libsundials-serial-dev/examples
@@ -28,7 +29,7 @@
DEB_COMPRESS_EXCLUDE = .c .out .f
USCAN_DESTDIR := $(CURDIR)/../tarballs
-DEB_STRIPPED_UPSTREAM_VERSION = $(shell echo $(DEB_UPSTREAM_VERSION) | sed -n -e 's/\.dfsg.*$$//p')
+
# Get the appropriate paths for the installation of the Octave files
mpath = $(shell octave-config -p LOCALFCNFILEDIR)
reverted:
--- sundials-2.5.0/debian/libsundials-ida1.install
+++ sundials-2.5.0.orig/debian/libsundials-ida1.install
@@ -1 +0,0 @@
-usr/lib/libsundials_ida.so.*
reverted:
--- sundials-2.5.0/debian/libsundials-cvode0.install
+++ sundials-2.5.0.orig/debian/libsundials-cvode0.install
@@ -1 +0,0 @@
-usr/lib/libsundials_cvode.so.*
reverted:
--- sundials-2.5.0/debian/libsundials-kinsol0.install
+++ sundials-2.5.0.orig/debian/libsundials-kinsol0.install
@@ -1 +0,0 @@
-usr/lib/libsundials_kinsol.so.*
diff -u sundials-2.5.0/debian/patches/series sundials-2.5.0/debian/patches/series
--- sundials-2.5.0/debian/patches/series
+++ sundials-2.5.0/debian/patches/series
@@ -1,4 +1,6 @@
+cmake.patch
makefile.patch
#sh4.patch
fix-format-error.patch
octave-sundialstb.patch
+sundials-config.patch
only in patch2:
unchanged:
--- sundials-2.5.0.orig/debian/patches/sundials-config.patch
+++ sundials-2.5.0/debian/patches/sundials-config.patch
@@ -0,0 +1,34 @@
+Index: sundials-2.5.0/bin/sundials-config.in
+===
+--- sundials-2.5.0.orig/bin/sundials-config.in 2012-04-12 02:31:04.0 +0200
sundials-2.5.0/bin/sundials-config.in 2012-07-16 17:18:30.0 +0200
+@@ -1,4 +1,4 @@
+-#! @SHELL@
++#! /bin/bash
+ # ---
+
+ NAME_=sundials-config
+@@ -65,7 +65,7 @@
+ abs_includedir=`cd ${includedir} /dev/null 21 pwd`;
+ abs_libdir=`cd ${libdir} /dev/null 21 pwd`;
+
+-if test $abs_includedir != /usr/include ; then
++if test $abs_includedir != /usr/include ; then
+ includes=-I$abs_includedir
+ fi
+
+Index: sundials-2.5.0/CMakeLists.txt
+===
+--- sundials-2.5.0.orig/CMakeLists.txt 2012-07-16 16:21:00.0 +0200
sundials-2.5.0/CMakeLists.txt 2012-07-16 17:12:04.0 +0200
+@@ -516,6 +516,10 @@
+ ${PROJECT_SOURCE_DIR}/include/sundials/sundials_config.in
+ ${PROJECT_BINARY_DIR}/include/sundials/sundials_config.h
+ )
++CONFIGURE_FILE(
++ ${PROJECT_SOURCE_DIR}/bin/sundials-config.in
++ ${PROJECT_SOURCE_DIR}/bin/sundials-config
++ )
+
+ # Add the include directory in the source tree and the one in
+ # the binary tree (for the header file sundials_config.h)
only in patch2:
unchanged:
--- sundials-2.5.0.orig/debian/patches/cmake.patch
+++ sundials-2.5.0/debian/patches/cmake.patch
@@ -0,0 +1,111 @@
+Index: sundials-2.5.0/CMakeLists.txt
Re: r-cran-dosnow fix for 700498 cannot migrate to testing
On 2013-02-28 20:57, Dirk Eddelbuettel wrote: Hi Niels, On 28 February 2013 at 20:37, Niels Thykier wrote: | Hi Dirk, | | The fix for #700498 is currently stuck in unstable due to a dependency | on a versioned dependency on r-base (or an binary built by r-base). At | this point we are not ready to accept the changes to r-base for Wheezy. | So, I was hoping that we convince you to upload a fix for #700498 to | testing-proposed-updates. Sure -- always happy to help the releases. Thanks for your prompt reply, it is much appreciated. :) But could you be a tiny bit more explicit and tell me what you want me to fix, where I need to upload, etc or I may get this messed. The changelog doesn't show me what I did wrong: Sure, but you have not done anything wrong in your r-cran-dosnow upload. It is just that we would like the missing r-cran-snow dependency bug to be fixed in testing and we cannot take it via unstable[1]. r-cran-dosnow (1.0.6-2) unstable; urgency=low * debian/control: Added r-cran-snow to Depends (Closes: #700498) * debian/control: Set Build-Depends: to current R version * debian/control: Set Standards-Version: to current version -- Dirk Eddelbuettel e...@debian.org Wed, 13 Feb 2013 09:33:14 -0600 Are you asking for a build under a different R version? Basically, yes. A build of r-cran-dosnow in a testing chroot. Couldn't you just make a binary NMU with a different Build-Depends? To my knowledge we (still) cannot do binNMUs of a package in a different suite. But even if we could, we still need a source upload of r-cran-dosnow because it has a versioned Build-Depends on r-cran-dev that can only be satisfied in sid. :) We have an informal policy to release r-cran-* packages _for unstable_. So I always encode the then-current version via Build-Depends. On Feb 13, that will have been R 2.15.2 aka r-base-core_2.15.2. In this case, we need a one-time exception to that policy and the package must be built in a clean chroot using only packages from testing. Upstream for r-cran-dosnow has much weaker requirements. It would probably build on stable... but I frankly do not know where to upload to. The version in unstable has the correct control file. Dirk, generally busy | | ~Niels | Please target testing-proposed-updates (instead of unstable or sid). ~Niels [1] ... or rather, if we were to take it, it would include a new upstream release of r-base and we are not ready to accept that. -- 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/512fbb4d.20...@thykier.net
Bug#701857: marked as done (unblock: mpi4py/1.3+hg20120611-3)
Your message dated Thu, 28 Feb 2013 20:16:15 + with message-id 1362082575.32751.5.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#701857: unblock: mpi4py/1.3+hg20120611-3 has caused the Debian Bug report #701857, regarding unblock: mpi4py/1.3+hg20120611-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.) -- 701857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701857 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 mpi4py. It contains a fix for RC bug #700995 (directory vs. symlink conflict: /usr/include/python3.2), and another bug fix for #691244 (to fix failing unittests with python3.3). Debdiff is as follows: diff -Nru mpi4py-1.3+hg20120611/debian/changelog mpi4py-1.3+hg20120611/debian/changelog --- mpi4py-1.3+hg20120611/debian/changelog 2012-06-11 18:51:02.0 -0700 +++ mpi4py-1.3+hg20120611/debian/changelog 2013-02-20 12:00:26.0 -0800 @@ -1,3 +1,18 @@ +mpi4py (1.3+hg20120611-3) unstable; urgency=medium + + * Create a suffixed (e.g. python3.2mu) python3 directory matching the +one present on the system for the given version of python3 (Closes: +#700995) + + -- Yaroslav Halchenko deb...@onerussian.com Wed, 20 Feb 2013 14:51:54 -0500 + +mpi4py (1.3+hg20120611-2) unstable; urgency=low + + * Cherry-picked patch from upstream for python3.3 compatibility (failing +unittests) (Closes: #691244) + + -- Yaroslav Halchenko deb...@onerussian.com Tue, 23 Oct 2012 10:23:29 -0400 + mpi4py (1.3+hg20120611-1) unstable; urgency=low [ Bradley M. Froehle ] diff -Nru mpi4py-1.3+hg20120611/debian/patches/series mpi4py-1.3+hg20120611/debian/patches/series --- mpi4py-1.3+hg20120611/debian/patches/series 2012-06-11 18:51:02.0 -0700 +++ mpi4py-1.3+hg20120611/debian/patches/series 2013-02-20 12:00:26.0 -0800 @@ -1,2 +1,3 @@ up_no_modlibs cython_version_check.patch +up_test_win_python3.3.patch diff -Nru mpi4py-1.3+hg20120611/debian/patches/up_test_win_python3.3.patch mpi4py-1.3+hg20120611/debian/patches/up_test_win_python3.3.patch --- mpi4py-1.3+hg20120611/debian/patches/up_test_win_python3.3.patch 1969-12-31 16:00:00.0 -0800 +++ mpi4py-1.3+hg20120611/debian/patches/up_test_win_python3.3.patch 2013-02-20 12:00:26.0 -0800 @@ -0,0 +1,43 @@ +Author: Lisandro Dalcin dalc...@gmail.com +Subject: Python 3.3 compatibility patch from upstream + +Origin: upstream +Bug-Debian: http://bugs.debian.org/691244 +Applied-Upstream: https://code.google.com/p/mpi4py/source/detail?r=330fde6ffccbdf68f5e3bdd0378bf4d6cfa82f50 +Last-Update: 2012-10-23 + +diff --git a/test/test_win.py b/test/test_win.py +--- a/test/test_win.py b/test/test_win.py +@@ -25,7 +25,10 @@ + if type(self.memory).__name__ == 'buffer': + self.assertEqual(sys.getrefcount(self.memory), refcnt+1) + else: +-self.assertEqual(sys.getrefcount(self.memory), refcnt) ++if sys.version_info[:3] (3, 3): ++self.assertEqual(sys.getrefcount(self.memory), refcnt) ++else: ++self.assertEqual(sys.getrefcount(self.memory), refcnt+1) + + def tearDown(self): + refcnt = sys.getrefcount(self.memory) +@@ -33,7 +36,10 @@ + if type(self.memory).__name__ == 'buffer': + self.assertEqual(sys.getrefcount(self.memory), refcnt-1) + else: +-self.assertEqual(sys.getrefcount(self.memory), refcnt) ++if sys.version_info[:3] (3, 3): ++self.assertEqual(sys.getrefcount(self.memory), refcnt) ++else: ++self.assertEqual(sys.getrefcount(self.memory), refcnt-1) + if self.mpi_memory: + MPI.Free_mem(self.mpi_memory) + +@@ -46,7 +52,6 @@ + self.assertEqual(dunit, 1) + self.assertEqual(base, pointer) + +- + def testAttributes(self): + cgroup = self.COMM.Get_group() + wgroup = self.WIN.Get_group() diff -Nru mpi4py-1.3+hg20120611/debian/rules mpi4py-1.3+hg20120611/debian/rules --- mpi4py-1.3+hg20120611/debian/rules 2012-06-11 18:51:02.0 -0700 +++ mpi4py-1.3+hg20120611/debian/rules 2013-02-20 12:00:26.0 -0800 @@ -54,10 +54,14 @@ done : # Python 3 + : # Can have python$$v symlink pointing to python3.?m or python3.?mu + : # see #700995 for more details. So first look where it points to + : # and use that directory set -e; for v in $(PY3VERS); do \ [
Bug#699915: tpu: lcdf-typetools/2.92+dfsg1-1.1
On Sun, 2013-02-10 at 14:26 +0100, Michael Stapelberg wrote: Adam D. Barratt a...@adam-barratt.org.uk writes: It looks like this issue still affects the unstable package; is that correct? If so then it should be resolved there first, before we consider a tpu. That is correct. I will NMU 2.92-2 in unstable soon. That appears to have turned in to 2.92+dfsg1-0.1? A quick query on the proposed diff - why is the same symlink being managed both via debian/links and an ln -sf (and later rm) in debian/rules? debian/links is for the symlink which gets shipped in the resulting package, whereas I left the ln -sf/rm in debian/rules for providing the glyphlist.txt at compile time. I’m not sure if anything actually uses that, or might use it in the future, so I am playing it safe here :). Okay. David Prévot taf...@debian.org writes: Is there any reason not to push this version directly in unstable ? (2.92+dfsg1-1.1 is greater than 2.92-2 anyway). 2.92+dfsg1-0.1 might be more conventional for an initial NMU too. Well, the version in unstable has changes (e.g. hardening directives) which I presume will not be accepted in a subsequent unblock request. Adam: Does that match your opinion? Or do you prefer an unblock request instead? I'd prefer the tpu at this point. 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/1362082915.32751.7.ca...@jacala.jungle.funky-badger.org
Bug#696671: tpu: isc-dhcp/4.2.2.dfsg.1-5+deb70u3
Control: tags -1 + confirmed d-i On Wed, 2013-02-20 at 21:11 -0500, Michael Gilbert wrote: On Sun, Feb 17, 2013 at 8:50 AM, Philipp Kern wrote: On Sat, Feb 16, 2013 at 04:20:45PM -0500, Michael Gilbert wrote: On Sat, Feb 16, 2013 at 4:18 PM, Michael Gilbert wrote: I've attached an updated proposed patch, which also fixes #698582 (and consequentially #700363). File attached. Really attached this time ... thanks. Please go ahead. Uploaded. Unblocked, but needs a d-i ack. 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/1362083074.32751.8.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#696671: tpu: isc-dhcp/4.2.2.dfsg.1-5+deb70u3
Processing control commands: tags -1 + confirmed d-i Bug #696671 [release.debian.org] tpu: isc-dhcp/4.2.2.dfsg.1-5+deb70u3 Added tag(s) d-i. -- 696671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696671 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.b696671.136208308325411.transcr...@bugs.debian.org
Bug#699148: unblock: celery/2.5.3-2
On Sat, 2013-02-09 at 10:35 +0100, Julien Cristau wrote: On Sat, Feb 9, 2013 at 08:17:44 +0100, Michael Fladischer wrote: Also, /usr/share/pyshared/celery as home dir for the user seems kind of weird... Would /var/lib/celery be a better choice? I would be emptpy though. I think so. Or /nonexistent, I guess, if it's not used for anything. Any news on an upload? 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/1362083230.32751.9.ca...@jacala.jungle.funky-badger.org
Bug#698341: pu: package spatialite/3.0.0~beta20110817-3+deb7u1
On Fri, 2013-02-15 at 21:13 +0100, David Paleino wrote: On Fri, 15 Feb 2013 18:21:29 +, Adam D. Barratt wrote: On Sun, 2013-01-27 at 20:13 +0100, David Paleino wrote: On Sun, 27 Jan 2013 14:16:08 +, Adam D. Barratt wrote: Please go ahead with the upload to unstable, as we need the issues fixing there in any case, however we proceed; thanks. Done, 3.1.0~rc2-2 just uploaded to sid. That was a little over two weeks ago now. Have there been any reported issues with the package in sid? None up to now. Cool; thanks. Did you have chance to look at whether fixing the testing package just requires the source file split or if there were any other issues? 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/1362083500.32751.11.ca...@jacala.jungle.funky-badger.org
Re: openjdk maintenance for wheezy and squeeze
Niels Thykier ni...@thykier.net schrieb: On 2013-02-17 23:04, Matthias Klose wrote: There is a bug report open for openjdk-6 in wheezy (#675495) and squeeze didn't see any security updates for several months. To summarize, no party involved is capable or willing to provide security updates based on backports of single patches to the released openjdk-6 version in a stable release. So what to do about it? Hi, Thanks for bringing up this topic. Here is my view on it: - Remove openjdk-6 in wheezy. Probably would require falling back to gcj. Not recommended as a runtime environment, but should work fine for building packages, as ecj is used for byte-code compilation. Falling back to an easier-to-main jvm could be an option too, but I didn't check how well that would work. Not having a fall-back would require removing most of java in Debian. I do not believe this is a functional solution. In my experience, gcj is not capable of running a lot of our Java programs reliably. - Updating to openjdk-7 in wheezy would not solve any issues from my point of view, and it would need some porting of packages to 7, and probably removing some packages which are not yet ported. Otoh removing openjdk-7 for wheezy could be an option if only one version should be supported for a stable release. We tried to accomplish this (replacing openjdk-6 with openjdk-7) a couple of months before the freeze; there was too much then and the freeze has not changed that. If we were to do this, we should have done it before the freeze (and continued in the early freeze). - Release openjdk-6 with wheezy, and provide security support by updating to new OpenJDK and IcedTea versions. Usually this does include some backports and other fixes. The potential for regressions could be higher, however even the single security fixes show regressions, as shown by the last security update on Feb 1. These builds could be provided as security updates, updates to the stable releases, or as backports. As a proof of concept, see [1]. I am sad to hear that stable releases are having regressions (especially for security fixes), but I do not see a way to release Wheezy without OpenJDK-6 (as default java). - Release openjdk-7 with wheezy, and do the same as with openjdk-6. The issue here is that 7 sees more changes than 6, and that the current openjdk-7 release doesn't build anymore on mips or mipsel, as communicated to the Debian mips porters, so an update would require removal of the binary mips packages. Fine if somebody wants to fix it, but apparently there is no-one interested in that. So this looks more difficult than the openjdk-6 updates. Removing the openjdk mips binaries would require changes to source packages building arch any packages and build-depending on default-jdk or openjdk. openjdk-7/7u3-2.1.3-1 is currently in testing, so we would release openjdk-7 with Wheezy? Admittedly with the security bugs in Java currently, I suspect the u13 might be better for us. That said, I got the feeling that this option would include us replacing the default-jdk with openjdk-7? As mentioned above, I don't see how that can happen with breaking a lot (unless we only change the default plugin). I've looked into the openjdk/icedtea in disguise situation of the last days. It's great to see that their will be ongoing icedtea6 releases. I wasn't aware of that so far. Backporting security fixes with Java has turned out to be more of less unfeasible. I tried this once with DSA 2507 and I think that amounted to at least two man days of work for that update alone. Also, Ubuntu has shipped backports to all suites in USN-1724 and AFAICS the world hasn't stopped. After all, everyone using Oracle Java will be exposed to the same behaviourial changes. So we should proceed with providing backports for openjdk in the future. If Matthias keeps the Debian/Ubuntu packaging in a state that it's easily buildable on squeeze/wheezy for ojdk6 and for wheezy on ojdk7 I think we should be able to handle Java updates resource-wise. I'm not familiar with the Java internals, but if we're following that approach it would make sense to upgrade Wheezy to the version in experimental (i.e. 7u15 instead of 7u3). Cheers, Moritz I recognise that OpenJDK-7 would most likely have been better default. However, I do not think it is possible for us to change the default-java at this point of the freeze without great distruption. * Even if we were to change the default to OpenJDK-7, we would still have a lot way to go before we could get rid of OpenJDK-6. * Using GCJ as default java will just cause programs to fail/crash. I believe I mentioned this to you at UDS-R; I do not think GCJ should be a provider of Java for programs anymore (for fixing post Wheezy). To my knowledge it is (at best) a
Bug#701930: unblock: squid3/3.1.20-2.2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi Release Team
Please unblock package squid3
The previous fix for CVE-2012-5643 and CVE-2013-0189 uploaded as
3.1.20-2.1 caused a cachemgr.cgi always crashing when supplying auth
credentials. Upstream provided a patch which was uploaded as
3.1.20-2.2.
See: #701123
The full debdiff against the current version in testing is attached.
Would it be possible to get a unblock for squid3?
unblock squid3/3.1.20-2.2
Regards,
Salvatore
Base version: squid3_3.1.20-2.1 from testing
Target version: squid3_3.1.20-2.2 from unstable
No hints in place.
Excuses:
changelog | 10 ++
patches/fix-701123-regression-in-cachemgr.patch | 39
patches/series |1
3 files changed, 50 insertions(+)
gpgv: keyblock resource `/home/carnil/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made Tue 05 Feb 2013 10:18:19 PM UTC using RSA key ID 4AC8EE1D
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpPcyNcv/squid3_3.1.20-2.1.dsc
gpgv: keyblock resource `/home/carnil/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made Sat 23 Feb 2013 02:13:52 PM UTC using RSA key ID 7FD863FE
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpPcyNcv/squid3_3.1.20-2.2.dsc
diff -Nru squid3-3.1.20/debian/changelog squid3-3.1.20/debian/changelog
--- squid3-3.1.20/debian/changelog 2013-02-05 22:16:28.0 +
+++ squid3-3.1.20/debian/changelog 2013-02-23 14:07:26.0 +
@@ -1,3 +1,13 @@
+squid3 (3.1.20-2.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add fix-701123-regression-in-cachemgr.patch patch.
+Fix missing bits in the fix for CVE-2012-5643 and CVE-2013-0189 causing
+cachemgr.cgi crashing when authentication credentials are supplied.
+Thanks to Amos Jeffries a...@treenet.co.nz (Closes: #701123)
+
+ -- Salvatore Bonaccorso car...@debian.org Sat, 23 Feb 2013 13:44:48 +0100
+
squid3 (3.1.20-2.1) unstable; urgency=high
* Non-maintainer upload
diff -Nru squid3-3.1.20/debian/patches/fix-701123-regression-in-cachemgr.patch squid3-3.1.20/debian/patches/fix-701123-regression-in-cachemgr.patch
--- squid3-3.1.20/debian/patches/fix-701123-regression-in-cachemgr.patch 1970-01-01 00:00:00.0 +
+++ squid3-3.1.20/debian/patches/fix-701123-regression-in-cachemgr.patch 2013-02-23 14:07:26.0 +
@@ -0,0 +1,39 @@
+Description: Fix regression in cachemgr.cgi
+ Fix regression introduced by the patches for CVE-2012-5643 and
+ CVE-2013-0189. Apply further patch provided by upstream.
+Origin: upstream, http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10486.patch
+Bug: http://bugs.squid-cache.org/show_bug.cgi?id=3790
+Bug-Debian: http://bugs.debian.org/701123
+Forwarded: not-needed
+Author: Reinhard Sojka reinhard.so...@parlament.gv.at
+Last-Update: 2013-02-23
+Applied-Upstream: yes
+
+--- a/tools/cachemgr.cc
b/tools/cachemgr.cc
+@@ -1162,7 +1162,6 @@
+ {
+ static char buf[1024];
+ size_t stringLength = 0;
+-const char *str64;
+
+ if (!req-passwd)
+ return ;
+@@ -1171,15 +1170,12 @@
+ req-user_name ? req-user_name : ,
+ req-passwd);
+
+-str64 = base64_encode(buf);
+-
+-stringLength += snprintf(buf, sizeof(buf), Authorization: Basic %s\r\n, str64);
++stringLength += snprintf(buf, sizeof(buf), Authorization: Basic %s\r\n, base64_encode(buf));
+
+ assert(stringLength sizeof(buf));
+
+-snprintf(buf[stringLength], sizeof(buf) - stringLength, Proxy-Authorization: Basic %s\r\n, str64);
++snprintf(buf[stringLength], sizeof(buf) - stringLength, Proxy-Authorization: Basic %s\r\n, base64_encode(buf));
+
+-xxfree(str64);
+ return buf;
+ }
+
diff -Nru squid3-3.1.20/debian/patches/series squid3-3.1.20/debian/patches/series
--- squid3-3.1.20/debian/patches/series 2013-02-05 21:53:05.0 +
+++ squid3-3.1.20/debian/patches/series 2013-02-23 14:07:26.0 +
@@ -3,3 +3,4 @@
15-cachemgr-default-config.patch
20-ipv6-fix
30-CVE-2012-5643-CVE-2013-0189.patch
+fix-701123-regression-in-cachemgr.patch
Hints needed:
unblock squid3/3.1.20-2.2
Re: r-cran-dosnow fix for 700498 cannot migrate to testing
On 28 February 2013 at 21:17, Niels Thykier wrote: | On 2013-02-28 20:57, Dirk Eddelbuettel wrote: | | Hi Niels, | | On 28 February 2013 at 20:37, Niels Thykier wrote: | | Hi Dirk, | | | | The fix for #700498 is currently stuck in unstable due to a dependency | | on a versioned dependency on r-base (or an binary built by r-base). At | | this point we are not ready to accept the changes to r-base for Wheezy. | | So, I was hoping that we convince you to upload a fix for #700498 to | | testing-proposed-updates. | | Sure -- always happy to help the releases. | | | Thanks for your prompt reply, it is much appreciated. :) | | But could you be a tiny bit more explicit and tell me what you want me to | fix, where I need to upload, etc or I may get this messed. | | The changelog doesn't show me what I did wrong: | | | Sure, but you have not done anything wrong in your r-cran-dosnow upload. | It is just that we would like the missing r-cran-snow dependency bug to | be fixed in testing and we cannot take it via unstable[1]. | | r-cran-dosnow (1.0.6-2) unstable; urgency=low | |* debian/control: Added r-cran-snow to Depends(Closes: #700498) | |* debian/control: Set Build-Depends: to current R version |* debian/control: Set Standards-Version: to current version | | -- Dirk Eddelbuettel e...@debian.org Wed, 13 Feb 2013 09:33:14 -0600 | | Are you asking for a build under a different R version? | | Basically, yes. A build of r-cran-dosnow in a testing chroot. Don't have one :-/ Only have one for unstable, I fear. I have a non-chroot testing. Shall I build there? | Couldn't you just make a binary NMU with a different Build-Depends? | | | To my knowledge we (still) cannot do binNMUs of a package in a different | suite. But even if we could, we still need a source upload of | r-cran-dosnow because it has a versioned Build-Depends on r-cran-dev | that can only be satisfied in sid. :) | | We have an informal policy to release r-cran-* packages _for unstable_. So I | always encode the then-current version via Build-Depends. On Feb 13, that | will have been R 2.15.2 aka r-base-core_2.15.2. | | | In this case, we need a one-time exception to that policy and the | package must be built in a clean chroot using only packages from testing. The exception is no issue :) Our policy is very informal. There isn't a public chroot somewhere for this, is there? Would be nice if we had build from source upload sigh. | Upstream for r-cran-dosnow has much weaker requirements. It would probably | build on stable... but I frankly do not know where to upload to. The | version in unstable has the correct control file. | | Dirk, generally busy | | | | | ~Niels | | | | | | Please target testing-proposed-updates (instead of unstable or sid). Yep. Vaguely recalled that from times past. | ~Niels | | [1] ... or rather, if we were to take it, it would include a new | upstream release of r-base and we are not ready to accept that. I know that isn't how it works, but in R's case one really could as the upstream releases are very, very stable and well tested. But unstable sucks in other depends etc pp. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.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/20783.49493.387285.462...@max.nulle.part
Bug#701930: marked as done (unblock: squid3/3.1.20-2.2)
Your message dated Thu, 28 Feb 2013 20:49:13 +
with message-id 1362084553.32751.14.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#701930: unblock: squid3/3.1.20-2.2
has caused the Debian Bug report #701930,
regarding unblock: squid3/3.1.20-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.)
--
701930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi Release Team
Please unblock package squid3
The previous fix for CVE-2012-5643 and CVE-2013-0189 uploaded as
3.1.20-2.1 caused a cachemgr.cgi always crashing when supplying auth
credentials. Upstream provided a patch which was uploaded as
3.1.20-2.2.
See: #701123
The full debdiff against the current version in testing is attached.
Would it be possible to get a unblock for squid3?
unblock squid3/3.1.20-2.2
Regards,
Salvatore
Base version: squid3_3.1.20-2.1 from testing
Target version: squid3_3.1.20-2.2 from unstable
No hints in place.
Excuses:
changelog | 10 ++
patches/fix-701123-regression-in-cachemgr.patch | 39
patches/series |1
3 files changed, 50 insertions(+)
gpgv: keyblock resource `/home/carnil/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made Tue 05 Feb 2013 10:18:19 PM UTC using RSA key ID 4AC8EE1D
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpPcyNcv/squid3_3.1.20-2.1.dsc
gpgv: keyblock resource `/home/carnil/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made Sat 23 Feb 2013 02:13:52 PM UTC using RSA key ID 7FD863FE
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpPcyNcv/squid3_3.1.20-2.2.dsc
diff -Nru squid3-3.1.20/debian/changelog squid3-3.1.20/debian/changelog
--- squid3-3.1.20/debian/changelog 2013-02-05 22:16:28.0 +
+++ squid3-3.1.20/debian/changelog 2013-02-23 14:07:26.0 +
@@ -1,3 +1,13 @@
+squid3 (3.1.20-2.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add fix-701123-regression-in-cachemgr.patch patch.
+Fix missing bits in the fix for CVE-2012-5643 and CVE-2013-0189 causing
+cachemgr.cgi crashing when authentication credentials are supplied.
+Thanks to Amos Jeffries a...@treenet.co.nz (Closes: #701123)
+
+ -- Salvatore Bonaccorso car...@debian.org Sat, 23 Feb 2013 13:44:48 +0100
+
squid3 (3.1.20-2.1) unstable; urgency=high
* Non-maintainer upload
diff -Nru squid3-3.1.20/debian/patches/fix-701123-regression-in-cachemgr.patch squid3-3.1.20/debian/patches/fix-701123-regression-in-cachemgr.patch
--- squid3-3.1.20/debian/patches/fix-701123-regression-in-cachemgr.patch 1970-01-01 00:00:00.0 +
+++ squid3-3.1.20/debian/patches/fix-701123-regression-in-cachemgr.patch 2013-02-23 14:07:26.0 +
@@ -0,0 +1,39 @@
+Description: Fix regression in cachemgr.cgi
+ Fix regression introduced by the patches for CVE-2012-5643 and
+ CVE-2013-0189. Apply further patch provided by upstream.
+Origin: upstream, http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10486.patch
+Bug: http://bugs.squid-cache.org/show_bug.cgi?id=3790
+Bug-Debian: http://bugs.debian.org/701123
+Forwarded: not-needed
+Author: Reinhard Sojka reinhard.so...@parlament.gv.at
+Last-Update: 2013-02-23
+Applied-Upstream: yes
+
+--- a/tools/cachemgr.cc
b/tools/cachemgr.cc
+@@ -1162,7 +1162,6 @@
+ {
+ static char buf[1024];
+ size_t stringLength = 0;
+-const char *str64;
+
+ if (!req-passwd)
+ return ;
+@@ -1171,15 +1170,12 @@
+ req-user_name ? req-user_name : ,
+ req-passwd);
+
+-str64 = base64_encode(buf);
+-
+-stringLength += snprintf(buf, sizeof(buf), Authorization: Basic %s\r\n, str64);
++stringLength += snprintf(buf, sizeof(buf), Authorization: Basic %s\r\n, base64_encode(buf));
+
+ assert(stringLength sizeof(buf));
+
+-snprintf(buf[stringLength], sizeof(buf) - stringLength, Proxy-Authorization: Basic %s\r\n, str64);
++snprintf(buf[stringLength], sizeof(buf) - stringLength, Proxy-Authorization: Basic %s\r\n, base64_encode(buf));
+
+-xxfree(str64);
+ return buf;
+ }
+
diff -Nru squid3-3.1.20/debian/patches/series squid3-3.1.20/debian/patches/series
--- squid3-3.1.20/debian/patches/series 2013-02-05 21:53:05.0 +
+++
Bug#701923: unblock: btrfs-tools/0.19+20120328-7.1
Control: tags -1 + d-i On Thu, 2013-02-28 at 19:45 +, Adam D. Barratt wrote: Control: tags -1 + confirmed On Thu, 2013-02-28 at 20:17 +0100, Julien Cristau wrote: +btrfs-tools (0.19+20120328-7.1) wheezy; urgency=low + + * Non-maintainer upload. + * Move udev rules file from 60-btrfs.rules to 70-btrfs.rules so it runs +after blkid (closes: #701642). Thanks, Bastian Blank! Please go ahead; thanks. Silly me failed to spot the udeb. Unblocked, but needs the d-i dance. 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/1362084657.32751.15.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#701923: unblock: btrfs-tools/0.19+20120328-7.1
Processing control commands: tags -1 + d-i Bug #701923 [release.debian.org] unblock: btrfs-tools/0.19+20120328-7.1 Added tag(s) d-i. -- 701923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701923 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.b701923.13620846675863.transcr...@bugs.debian.org
Bug#701860: unblock: pycxx/6.2.4-3
Control: tags -1 + moreinfo On Wed, 2013-02-27 at 22:51 -0800, Vincent Cheng wrote: + * install into real include/python3* folder instead of symlink folder +Thanks to Sebastian Ramacher for the patch. (Closes: #700782) [...] Build-Depends: debhelper (= 7.0.50~), python-all (= 2.6.6-3~), - python3-all (= 3.1.2-10~) + python3-all-dev (= 3.1.2-10~), + python3-all-dbg Why the new -dbg build-dependency? 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/1362085631.32751.17.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#701860: unblock: pycxx/6.2.4-3
Processing control commands: tags -1 + moreinfo Bug #701860 [release.debian.org] unblock: pycxx/6.2.4-3 Added tag(s) moreinfo. -- 701860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701860 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.b701860.136208564214477.transcr...@bugs.debian.org
Bug#701859: pre-approval unblock: python-bsddb3/5.2.0-1+deb7u1
Control: tags -1 + confirmed On Wed, 2013-02-27 at 22:40 -0800, Vincent Cheng wrote: +python-bsddb3 (5.2.0-1+deb7u1) testing-proposed-updates; urgency=low + + * Non-maintainer upload. + * Build-depend on python3.2-dev (= 3.2.3-7) to fix directory vs. symlink +conflict on /usr/include/python3.2. Closes: #700996. 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/1362085750.32751.18.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#701859: pre-approval unblock: python-bsddb3/5.2.0-1+deb7u1
Processing control commands: tags -1 + confirmed Bug #701859 [release.debian.org] pre-approval unblock: python-bsddb3/5.2.0-1+deb7u1 Added tag(s) confirmed. -- 701859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701859 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.b701859.136208575915438.transcr...@bugs.debian.org
Bug#685230: unblock hylafax 3:6.0.6-4
On Sun, Jan 6, 2013 at 00:12:57 +0100, Ivo De Decker wrote: Hi Joachim, On Thu, Jan 03, 2013 at 06:39:27PM +0100, Joachim Wiedorn wrote: a) create the updated version 3:6.0.6-5 which is the same as 3:6.0.6-1 and then create the next version 3:6.0.6-6 which all needed patches for Wheezy, or There is no need to create a 3:6.0.6-5 identical to 3:6.0.6-1 first. You can just create 3:6.0.6-5, based on 3:6.0.6-1, with the changes for wheezy (and without other changes from 3:6.0.6-2, 3:6.0.6-3 and 3:6.0.6-4 that are not appropriate for wheezy). This version 3:6.0.6-5 should be uploaded to unstable. Hi, is there an ETA for that new upload? Cheers, Julien signature.asc Description: Digital signature
Re: r-cran-dosnow fix for 700498 cannot migrate to testing
On Thu, Feb 28, 2013 at 14:43:01 -0600, Dirk Eddelbuettel wrote: Don't have one :-/ Only have one for unstable, I fear. I have a non-chroot testing. Shall I build there? debootstrap --variant=buildd wheezy $path $mirror There, you have a testing chroot. Cheers, Julien signature.asc Description: Digital signature
Bug#701860: unblock: pycxx/6.2.4-3
Control: tags -1 - moreinfo On 2013-02-28 21:07:11, Adam D. Barratt wrote: Control: tags -1 + moreinfo On Wed, 2013-02-27 at 22:51 -0800, Vincent Cheng wrote: + * install into real include/python3* folder instead of symlink folder +Thanks to Sebastian Ramacher for the patch. (Closes: #700782) [...] Build-Depends: debhelper (= 7.0.50~), python-all (= 2.6.6-3~), - python3-all (= 3.1.2-10~) + python3-all-dev (= 3.1.2-10~), + python3-all-dbg Why the new -dbg build-dependency? Because the symlinks that are read in d/rules are shipped in python3.*-dev and python3.*-dbg. If they are not there, the files end up in /usr/include/python3.2/CXX again. Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Processed: Re: Bug#701860: unblock: pycxx/6.2.4-3
Processing control commands: tags -1 - moreinfo Bug #701860 [release.debian.org] unblock: pycxx/6.2.4-3 Removed tag(s) moreinfo. -- 701860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701860 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.b701860.136208644920148.transcr...@bugs.debian.org
Bug#701859: marked as done (pre-approval unblock: python-bsddb3/5.2.0-1+deb7u1)
Your message dated Thu, 28 Feb 2013 21:25:58 + with message-id 1362086758.32751.20.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#701859: pre-approval unblock: python-bsddb3/5.2.0-1+deb7u1 has caused the Debian Bug report #701859, regarding pre-approval unblock: python-bsddb3/5.2.0-1+deb7u1 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.) -- 701859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I've attached a proposed debdiff to fix RC bug #700996 (directory vs. symlink conflict: /usr/include/python3.2). It's pretty straightforward, but this has to go through testing-proposed-updates so I assume that a pre-approval is needed? diff -u python-bsddb3-5.2.0/debian/control python-bsddb3-5.2.0/debian/control --- python-bsddb3-5.2.0/debian/control +++ python-bsddb3-5.2.0/debian/control @@ -2,7 +2,7 @@ Section: python Priority: optional Maintainer: Matthias Klose d...@debian.org -Build-Depends: debhelper (= 6), libdb5.1-dev, python-all-dev (= 2.6.6-1~), python-all-dbg, python3-all-dev (= 3.1.2-10~), python3-all-dbg +Build-Depends: debhelper (= 6), libdb5.1-dev, python-all-dev (= 2.6.6-1~), python-all-dbg, python3-all-dev (= 3.1.2-10~), python3-all-dbg, python3.2-dev (= 3.2.3-7) Build-Depends-Indep: python-sphinx Standards-Version: 3.9.2 XS-Python-Version: = 2.6 diff -u python-bsddb3-5.2.0/debian/changelog python-bsddb3-5.2.0/debian/changelog --- python-bsddb3-5.2.0/debian/changelog +++ python-bsddb3-5.2.0/debian/changelog @@ -1,3 +1,11 @@ +python-bsddb3 (5.2.0-1+deb7u1) testing-proposed-updates; urgency=low + + * Non-maintainer upload. + * Build-depend on python3.2-dev (= 3.2.3-7) to fix directory vs. symlink +conflict on /usr/include/python3.2. Closes: #700996. + + -- Vincent Cheng vincentc1...@gmail.com Wed, 27 Feb 2013 22:36:16 -0800 + python-bsddb3 (5.2.0-1) unstable; urgency=low * New upstream release. Regards, Vincent ---End Message--- ---BeginMessage--- Hi, On Thu, 2013-02-28 at 21:09 +, Adam D. Barratt wrote: Control: tags -1 + confirmed Actually, as was kindly pointed out on IRC, for wheezy we can just binNMU this once the new python3.2 migrates to testing. So let's skip the tpu upload; thanks for the work. Regards, Adam---End Message---
Bug#701860: marked as done (unblock: pycxx/6.2.4-3)
Your message dated Thu, 28 Feb 2013 21:33:34 +
with message-id 1362087214.32751.22.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#701860: unblock: pycxx/6.2.4-3
has caused the Debian Bug report #701860,
regarding unblock: pycxx/6.2.4-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.)
--
701860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701860
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 pycxx.
It contains a fix for RC bug #700782 (directory vs. symlink conflict
relating to /usr/include/python3.2).
Debdiff is as follows:
diff -Nru pycxx-6.2.4/debian/changelog pycxx-6.2.4/debian/changelog
--- pycxx-6.2.4/debian/changelog2012-12-30 11:24:04.0 -0800
+++ pycxx-6.2.4/debian/changelog2013-02-27 10:50:34.0 -0800
@@ -1,3 +1,10 @@
+pycxx (6.2.4-3) unstable; urgency=low
+
+ * install into real include/python3* folder instead of symlink folder
+Thanks to Sebastian Ramacher for the patch. (Closes: #700782)
+
+ -- Julian Taylor jtaylor.deb...@googlemail.com Wed, 27 Feb 2013
19:34:50 +0100
+
pycxx (6.2.4-2) unstable; urgency=low
* Remove symlink /usr/share/doc/python{,3}-cxx-dev before installing
diff -Nru pycxx-6.2.4/debian/control pycxx-6.2.4/debian/control
--- pycxx-6.2.4/debian/control 2012-12-30 11:24:04.0 -0800
+++ pycxx-6.2.4/debian/control 2013-02-27 10:47:27.0 -0800
@@ -5,7 +5,8 @@
Uploaders: Julian Taylor jtaylor.deb...@googlemail.com
Build-Depends: debhelper (= 7.0.50~),
python-all (= 2.6.6-3~),
- python3-all (= 3.1.2-10~)
+ python3-all-dev (= 3.1.2-10~),
+ python3-all-dbg
XS-Python-Version: all
Standards-Version: 3.9.3
Homepage: http://cxx.sourceforge.net
diff -Nru pycxx-6.2.4/debian/rules pycxx-6.2.4/debian/rules
--- pycxx-6.2.4/debian/rules2012-12-30 11:24:04.0 -0800
+++ pycxx-6.2.4/debian/rules2013-02-27 10:47:27.0 -0800
@@ -30,10 +30,12 @@
set -e for i in $(PY3VERS); do \
$${i} setup.py install --force --root=$(CURDIR)/debian/tmp
--no-compile -O0 --install-layout=deb; \
2to3 -w -n $(CURDIR)/debian/tmp/usr/lib; \
- dh_install -ppython3-cxx-dev CXX/*.hxx
/usr/include/$${i}/CXX/; \
- dh_install -ppython3-cxx-dev CXX/*.h
/usr/include/$${i}/CXX/; \
- dh_install -ppython3-cxx-dev CXX/Python3/*
/usr/include/$${i}/CXX/Python3; \
- dh_link -ppython3-cxx-dev /usr/include/$${i}/CXX/
/usr/include/$${i}_d/CXX; \
+ python_inc_dir=$$(readlink -f /usr/include/$$i); \
+ pythond_inc_dir=$$(readlink -f /usr/include/$${i}_d); \
+ dh_install -ppython3-cxx-dev CXX/*.hxx
$${python_inc_dir}/CXX/; \
+ dh_install -ppython3-cxx-dev CXX/*.h
$${python_inc_dir}/CXX/; \
+ dh_install -ppython3-cxx-dev CXX/Python3/*
$${python_inc_dir}/CXX/Python3; \
+ dh_link -ppython3-cxx-dev $${python_inc_dir}/CXX/
$${pythond_inc_dir}/CXX; \
dh_install -ppython3-cxx-dev Src/*.c
/usr/share/$${i}/CXX/; \
dh_install -ppython3-cxx-dev Src/*.cxx
/usr/share/$${i}/CXX/; \
dh_install -ppython3-cxx-dev Src/Python3/*
/usr/share/$${i}/CXX/Python3; \
unblock pycxx/6.2.4-3
Regards,
Vincent
---End Message---
---BeginMessage---
On Thu, 2013-02-28 at 22:20 +0100, Sebastian Ramacher wrote:
On 2013-02-28 21:07:11, Adam D. Barratt wrote:
On Wed, 2013-02-27 at 22:51 -0800, Vincent Cheng wrote:
+ * install into real include/python3* folder instead of symlink folder
+Thanks to Sebastian Ramacher for the patch. (Closes: #700782)
[...]
Build-Depends: debhelper (= 7.0.50~),
python-all (= 2.6.6-3~),
- python3-all (= 3.1.2-10~)
+ python3-all-dev (= 3.1.2-10~),
+ python3-all-dbg
Why the new -dbg build-dependency?
Because the symlinks that are read in d/rules are shipped in
python3.*-dev and python3.*-dbg. If they are not there, the files end up
in /usr/include/python3.2/CXX again.
Hrm, I obviously looked at the wrong link the first time *sigh*.
Unblocked.
Regards,
Adam---End Message---
Bug#699882: pre-approval: elmerfem/6.1.0.svn.5396.dfsg2-2
I request permission to upload elmerfem 6.1.0.svn.5396.dfsg2-2 into unstable, targeted at wheezy. Diff is quite big (see attachment), but there is only one way to fix RC bug #698527 now: remove ElmerGUI and all related stuff. Ack, please go ahead. Thanks. Uploaded. -- 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/254731362087...@web24f.yandex.ru
Processed: retitle
Processing commands for cont...@bugs.debian.org: retitle 699882 unblock: elmerfem/6.1.0.svn.5396.dfsg2-2 Bug #699882 [release.debian.org] pre-approval: elmerfem/6.1.0.svn.5396.dfsg2-2 Changed Bug title to 'unblock: elmerfem/6.1.0.svn.5396.dfsg2-2' from 'pre-approval: elmerfem/6.1.0.svn.5396.dfsg2-2' thanks Stopping processing here. Please contact me if you need assistance. -- 699882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699882 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.136208787730214.transcr...@bugs.debian.org
Processed: Re: Bug#701178: preapproval unblock: dspam/dspam/3.10.1+dfsg-9
Processing control commands: tag -1 confirmed Bug #701178 [release.debian.org] preapproval unblock: dspam/dspam/3.10.1+dfsg-9 Added tag(s) confirmed. -- 701178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701178 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.b701178.1362088308681.transcr...@bugs.debian.org
Bug#701178: preapproval unblock: dspam/dspam/3.10.1+dfsg-9
Control: tag -1 confirmed On Thu, Feb 28, 2013 at 22:49:21 +0100, Thomas Preud'homme wrote: Le jeudi 28 février 2013 20:56:54, Julien Cristau a écrit : That debdiff is for 3.10.2 in sid. Do you have one for 3.10.1? Sure, sorry. Here you are. Thanks. Go ahead. Cheers, Julien signature.asc Description: Digital signature
Bug#701178: preapproval unblock: dspam/dspam/3.10.1+dfsg-9
Le jeudi 28 février 2013 20:56:54, Julien Cristau a écrit :
That debdiff is for 3.10.2 in sid. Do you have one for 3.10.1?
Sure, sorry. Here you are.
Pretty much the same except for the offsets. :)
Thanks,
Julien
Best regards,
Thomas
diff -Nru dspam-3.10.1+dfsg/debian/changelog dspam-3.10.1+dfsg/debian/changelog
--- dspam-3.10.1+dfsg/debian/changelog 2013-01-22 13:38:35.0 +0100
+++ dspam-3.10.1+dfsg/debian/changelog 2013-02-28 21:34:52.0 +0100
@@ -1,3 +1,10 @@
+dspam (3.10.1+dfsg-9) testing-proposed-updates; urgency=low
+
+ * Add a new version of the patch fixing recipient corruption when releasing
+a message from quarantine (Closes: #698136).
+
+ -- Thomas Preud'homme robo...@debian.org Thu, 28 Feb 2013 21:33:50 +0100
+
dspam (3.10.1+dfsg-8) testing-proposed-updates; urgency=low
* Stop shipping ucf template as a conffile: this avoid unnecessary prompt
diff -Nru dspam-3.10.1+dfsg/debian/patches/009_fix_recipient_corruption_when_releasing_message_from_quarantine.diff dspam-3.10.1+dfsg/debian/patches/009_fix_recipient_corruption_when_releasing_message_from_quarantine.diff
--- dspam-3.10.1+dfsg/debian/patches/009_fix_recipient_corruption_when_releasing_message_from_quarantine.diff 1970-01-01 01:00:00.0 +0100
+++ dspam-3.10.1+dfsg/debian/patches/009_fix_recipient_corruption_when_releasing_message_from_quarantine.diff 2013-02-28 21:34:52.0 +0100
@@ -0,0 +1,55 @@
+Description: Fix recipient corruption when releasing a message from quarantine
+
+When releasing mail from quarantine, dspam corrupts the FROM part in the
+SMTP/LMTP handshake.
+
+Author: Allan Ievers aimail-dspam_us...@rearden.com
+Origin: vendor
+Bug-Debian: http://bugs.debian.org/698136
+Forwarded: ste...@bajic.ch
+Last-Update: 2013-02-28
+
+diff --git a/src/dspam.c b/src/dspam.c
+index 26266c9..68e1165 100644
+--- a/src/dspam.c
b/src/dspam.c
+@@ -498,8 +498,9 @@ process_message (
+ ATX-train_pristine = 1;
+ }
+
+-/* Change also the mail recipient */
+-ATX-recipient = CTX-username;
++/* Change also the mail recipient. ATX-recipient either points to
++ * recipient[] or mailbox[] in process_users, hence the size of 256 */
++strlcpy(ATX-recipient, CTX-username, 256);
+
+ }
+ }
+@@ -1621,6 +1622,7 @@ int process_users(AGENT_CTX *ATX, buffer *message) {
+ char filename[MAX_FILENAME_LENGTH];
+ int optin, optout;
+ char *username = NULL;
++char recipient[256];
+
+ /* If ServerParameters specifies a --user, there will only be one
+ * instance on the stack, but possible multiple recipients. So we
+@@ -1659,7 +1661,7 @@ int process_users(AGENT_CTX *ATX, buffer *message) {
+ username = node_nt-ptr;
+
+ if (node_rcpt) {
+- ATX-recipient = node_rcpt-ptr;
++ strlcpy(recipient, node_rcpt-ptr, sizeof(recipient));
+ node_rcpt = c_nt_next (ATX-recipients, c_rcpt);
+ } else {
+
+@@ -1667,8 +1669,9 @@ int process_users(AGENT_CTX *ATX, buffer *message) {
+ if (have_rcpts)
+ break;
+
+- ATX-recipient = node_nt-ptr;
++ strlcpy(recipient, node_nt-ptr, sizeof(recipient));
+ }
++ATX-recipient = recipient;
+
+ /* If support for +detail is enabled, save full mailbox name for
+ delivery and strip detail for processing */
diff -Nru dspam-3.10.1+dfsg/debian/patches/series dspam-3.10.1+dfsg/debian/patches/series
--- dspam-3.10.1+dfsg/debian/patches/series 2013-01-22 13:38:35.0 +0100
+++ dspam-3.10.1+dfsg/debian/patches/series 2013-02-28 21:34:52.0 +0100
@@ -6,3 +6,4 @@
006_default-daemon-port.diff
007_ctime.pl.diff
008_fix_exim_integration_doc.diff
+009_fix_recipient_corruption_when_releasing_message_from_quarantine.diff
signature.asc
Description: This is a digitally signed message part.
Bug#699882: marked as done (unblock: elmerfem/6.1.0.svn.5396.dfsg2-2)
Your message dated Thu, 28 Feb 2013 23:04:36 +0100 with message-id 20130228220436.gx5...@radis.cristau.org and subject line Re: Bug#699882: pre-approval: elmerfem/6.1.0.svn.5396.dfsg2-2 has caused the Debian Bug report #699882, regarding unblock: elmerfem/6.1.0.svn.5396.dfsg2-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.) -- 699882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, I request permission to upload elmerfem 6.1.0.svn.5396.dfsg2-2 into unstable, targeted at wheezy. Diff is quite big (see attachment), but there is only one way to fix RC bug #698527 now: remove ElmerGUI and all related stuff. Best regards, Boris PS: diff file was produced using command: $ debdiff elmerfem_6.1.0.svn.5396.dfsg2-1.dsc elmerfem_6.1.0.svn.5396.dfsg2-2.dsc | \ filterdiff -x '*debian/po/*' -x '*debian/patches/*.patch' elmerfem_6.1.0.svn.5396.dfsg2-1:6.1.0.svn.5396.dfsg2-2.diff elmerfem_6.1.0.svn.5396.dfsg2-1:6.1.0.svn.5396.dfsg2-2.diff Description: Binary data ---End Message--- ---BeginMessage--- On Thu, Feb 28, 2013 at 23:39:34 +0200, Boris Pek wrote: I request permission to upload elmerfem 6.1.0.svn.5396.dfsg2-2 into unstable, targeted at wheezy. Diff is quite big (see attachment), but there is only one way to fix RC bug #698527 now: remove ElmerGUI and all related stuff. Ack, please go ahead. Thanks. Uploaded. Unblocked. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#695265: marked as done (RM: fs2ram/3.0.10 testing)
Your message dated Thu, 28 Feb 2013 22:08:11 + with message-id 1362089291.32751.23.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#695265: fs2ram has caused the Debian Bug report #695265, regarding RM: fs2ram/3.0.10 testing 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.) -- 695265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi, as explained in the bug 691742[1], The current version of fs2ram in testing is RC buggy. The last upload fixing this the RC bug was late according to the debian release objective for wheezy. So, I prefer fs2ram be removed from testing. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691742 fs2ram is a leaf package. There is no dependency problem to remove it. Thanks for the release team efforts ! Cheers, -- Philippe Le Brouster ---End Message--- ---BeginMessage--- On Mon, 2013-02-11 at 23:51 +, Jonathan Wiltshire wrote: On Mon, Feb 11, 2013 at 04:12:10PM +0100, Philippe Le Brouster wrote: - Pull fs2ram 0.3.12 to testing[1] or - Remove fs2ram 0.3.10 from testing (and fs2ram will be backported for wheezy after released) [1] Bug#691742, especially http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691742#20 At a glance the diff from wheezy - sid makes me uncomfortable; certainly some of the changelog entries would normally rule it out for an unblock. I will add a removal hint if you are sure that's the path you want to take, or you can propose isolated fixes through tpu if you like. Apparently Julien did the former; closing. Regards, Adam---End Message---
Bug#699560: marked as done (gpa/0.9.0-4: Setting wheezy-ignore for #634930)
Your message dated Thu, 28 Feb 2013 23:13:30 +0100 with message-id 20130228221330.gy5...@radis.cristau.org and subject line Re: Bug#699560: gpa/0.9.0-4: Setting wheezy-ignore for #634930 has caused the Debian Bug report #699560, regarding gpa/0.9.0-4: Setting wheezy-ignore for #634930 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.) -- 699560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal Weitergeleitete Nachricht Von: Daniel Leidert daniel.leidert.s...@gmx.net An: debian-release@lists.debian.org Betreff: gpa/0.9.0-3: Setting wheezy-ignore for #634930 Datum: Sun, 27 Jan 2013 16:19:42 +0100 Hi, The upload of gpa/0.9.0-2 contained a workaround for #634930 [1] which avoids this crash. The crash itself is not reproducible for me although several people reported it. So the (programmed) cause is still unknown. But the bug appears on a special X.509 certificate [2]. So backporting the --disable-x509 switch is just a workaround. However it looks like the to be the best solution for wheezy atm. I'm therefor asking for setting the wheezy-ignore tag for this RC-bug. (The other RC bug is currently being fixed.) [1] http://bugs.debian.org/634930 [2] http://bugs.debian.org/634930#90 Regards, Daniel ---End Message--- ---BeginMessage--- On Fri, Feb 1, 2013 at 21:16:43 +0100, Daniel Leidert wrote: Package: release.debian.org Severity: normal Weitergeleitete Nachricht Von: Daniel Leidert daniel.leidert.s...@gmx.net An: debian-release@lists.debian.org Betreff: gpa/0.9.0-3: Setting wheezy-ignore for #634930 Datum: Sun, 27 Jan 2013 16:19:42 +0100 Hi, The upload of gpa/0.9.0-2 contained a workaround for #634930 [1] which avoids this crash. The crash itself is not reproducible for me although several people reported it. So the (programmed) cause is still unknown. But the bug appears on a special X.509 certificate [2]. So backporting the --disable-x509 switch is just a workaround. However it looks like the to be the best solution for wheezy atm. I'm therefor asking for setting the wheezy-ignore tag for this RC-bug. (The other RC bug is currently being fixed.) wheezy-ignore tag added. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#700244: marked as done (unblock: openjdk-6/6b27-1.12.3-1)
Your message dated Thu, 28 Feb 2013 23:26:24 +0100 with message-id 20130228222624.gz5...@radis.cristau.org and subject line Re: Bug#700244: unblock: openjdk-6/6b27-1.12.1-2 has caused the Debian Bug report #700244, regarding unblock: openjdk-6/6b27-1.12.3-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.) -- 700244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700244 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 openjdk-6/6b27-1.12.1-2, updating to the most recent Icedtea6 release, including a batch of security fixes. ---End Message--- ---BeginMessage--- On Sun, Feb 10, 2013 at 15:16:46 +0100, Matthias Klose wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock openjdk-6/6b27-1.12.1-2, updating to the most recent Icedtea6 release, including a batch of security fixes. Unblocked. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Re: r-cran-dosnow fix for 700498 cannot migrate to testing
On 28 February 2013 at 22:17, Julien Cristau wrote: | On Thu, Feb 28, 2013 at 14:43:01 -0600, Dirk Eddelbuettel wrote: | | Don't have one :-/ Only have one for unstable, I fear. | | I have a non-chroot testing. Shall I build there? | | debootstrap --variant=buildd wheezy $path $mirror | | There, you have a testing chroot. Understood I just don't know if I'll have time for that in the next few days as I have a few other balls up in the air. r-cran-snow is a pretty marginal package so if it doesn't make it ... nobody gets hurt. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.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/20783.57727.129121.283...@max.nulle.part
Bug#701939: unblock: libio-async-loop-glib-perl/0.20-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package libio-async-loop-glib-perl/0.20-3. The unblock disables a test which fixes #699258. Upstream considers the tests unreliable and has removed them for the next release: https://rt.cpan.org/Public/Bug/Display.html?id=83033 Debdiff attached. unblock libio-async-loop-glib-perl/0.20-3 Thanks in advance, gregor -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRL/cRAAoJELs6aAGGSaoGfTEQAI7bB9gHtT2I1OSo4W4zhGLh 2dAfqv0XYfcY7xJlB1DpmCbLjzDtj5N23hOFZSL3CjI2frt6xp1m+Fcw+60DcFr1 1uYgp6/XV3t50STtQzttlWpKiN5iIsLXuTrCIC7Dt6B1+cebAVG8lGJMxFKRL9pn W+FqvVksh7U/NSnhB1/tzPKY5OMnbJ24huLn6Jy/SfYfGIITmgRITrt0SrR8r306 SUjCal7Du5Wib/nFU6/fGJap3carzEtUvEnGqgfkmfznnXvAorgDJN6ByD5q2FqU H8kwtUJ/D3V6PpseGLH6zpn7HtGc6wLfpkaDOIct/1eE/Xmz2vNtQAHMndkftjy2 fvtjxGN7e+gC4BdgaA24a1/BLkxpFHSSKMqtYb1ffrQwzIMrSnuLovWo0IfSULxy iV7V1r0Jn2Ifmtsi9UUERQsRubFQCLtBQGsYe9Hll46kPWLLaXCGyTbd2cdP7gDx ZWLuKWWTzu6YwO/jBQRKBSPqqSNHTDENbqN8/UwP8e0vEUet6rOwm77zuKWbcwKv pO4FcVdk9H2oGd15fnVk0Of2SWIzmr0srGFKYlVsR2MaJ0Lfpt7/BeU1GfQ+fmFX zWuv0tWba52H3J6t7AUCXcyyPZg7dgq11OccX0FlNwGvWVme8Y979IEFWksEgfF3 avDYJpgfeGqDQp74Hnkr =APYZ -END PGP SIGNATURE- diff -Nru libio-async-loop-glib-perl-0.20/debian/changelog libio-async-loop-glib-perl-0.20/debian/changelog --- libio-async-loop-glib-perl-0.20/debian/changelog 2012-08-15 15:16:32.0 +0200 +++ libio-async-loop-glib-perl-0.20/debian/changelog 2013-03-01 01:18:32.0 +0100 @@ -1,3 +1,11 @@ +libio-async-loop-glib-perl (0.20-3) unstable; urgency=low + + * Disable t/06loop-control.t. These tests are unreliable and have been +removed by upstream for the next release; cf. CPAN RT#83033. +(Closes: #699258) + + -- gregor herrmann gre...@debian.org Fri, 01 Mar 2013 01:16:04 +0100 + libio-async-loop-glib-perl (0.20-2) unstable; urgency=low * Add patch pollhup.patch: remove declaration that IO::Async::Loop::Glib diff -Nru libio-async-loop-glib-perl-0.20/debian/rules libio-async-loop-glib-perl-0.20/debian/rules --- libio-async-loop-glib-perl-0.20/debian/rules 2012-08-15 15:16:32.0 +0200 +++ libio-async-loop-glib-perl-0.20/debian/rules 2013-03-01 01:18:32.0 +0100 @@ -1,4 +1,9 @@ #!/usr/bin/make -f +TEST_FILES=$(filter-out t/06loop-control.t,$(shell echo t/*.t)) + %: dh $@ + +override_dh_auto_test: + dh_auto_test -- TEST_FILES=$(TEST_FILES)
Processed: unblock: debian-edu-doc/1.5~20130228~7.0
Processing control commands: retitle -1 unblock: debian-edu-doc/1.5~20130228~7.0 Bug #700757 [release.debian.org] unblock: debian-edu-doc/1.5~20130215~7.0 Changed Bug title to 'unblock: debian-edu-doc/1.5~20130228~7.0' from 'unblock: debian-edu-doc/1.5~20130215~7.0' -- 700757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700757 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.b700757.136209896312569.transcr...@bugs.debian.org
Bug#700757: unblock: debian-edu-doc/1.5~20130228~7.0
Control: retitle -1 unblock: debian-edu-doc/1.5~20130228~7.0
Le 16/02/2013 20:31, David Prévot a écrit :
Dear release team
Please unblock package debian-edu-doc, the version currently in Wheezy
contains only the Squeeze-related doc, and we believe it's important to
have the Wheezy-related doc in Wheezy…
Furthermore, the version currently in Wheezy FTBFS in Wheezy
Please find attached an updated (filtered) debdiff, since we just
updated the documentation to match the Debian Edu Squeeze point release.
There is also an updated script (to match the move to Git) that is not
used in the build system, so I filtered it too.
unblock debian-edu-doc/1.5~20130228~7.0
Many thanks in advance, regards.
David
diff -Nru --exclude documentation --exclude mail_stats_to_list debian-edu-doc-1.4~20120925~6.0.6+r0/debian/changelog debian-edu-doc-1.5~20130228~7.0/debian/changelog
--- debian-edu-doc-1.4~20120925~6.0.6+r0/debian/changelog 2012-09-25 17:17:01.0 -0400
+++ debian-edu-doc-1.5~20130228~7.0/debian/changelog 2013-02-28 18:56:24.0 -0400
@@ -1,3 +1,55 @@
+debian-edu-doc (1.5~20130228~7.0) unstable; urgency=low
+
+ * Update manuals and images from the wiki.
+
+ [ Squeeze manual translation update ]
+ * French (Cédric Boutillier).
+ * Danish (Joe Hansen).
+ * Italian (Claudio Carboncini).
+
+ -- David Prévot taf...@debian.org Thu, 28 Feb 2013 18:25:09 -0400
+
+debian-edu-doc (1.5~20130225~7.0) unstable; urgency=low
+
+ [ Holger Levsen ]
+ * Adapt debian/mail_stats_to_list to the change to git.
+ * common/Makefile.common: remove *.po~ on clean target.
+
+ [ David Prévot ]
+ * Update manuals and images from the wiki.
+
+ [ Manual translation update ]
+ * German (Wolfgang Schweer).
+
+ -- David Prévot taf...@debian.org Mon, 25 Feb 2013 10:18:07 -0400
+
+debian-edu-doc (1.5~20130215~7.0) unstable; urgency=low
+
+ [ David Prévot ]
+ * Update manuals and images from the wiki.
+ * Update debian/copyright.
+ * README: mention the Danish translation among the complete ones.
+ * Update internal doc to the new Git repository, thanks to Wolfgang Schweer
+for the review and extra comments.
+ * README: document that the latest po4a version must be used.
+ * control: Build-Depends on fonts-arphic-gbsn00lp and fonts-arphic-bsmi00lp
+instead of transitional ttf-arphic-gbsn00lp and ttf-arphic-bsmi00lp.
+ * Add initial Wheezy manual, based on the Squeeze one.
+
+ [ Updated Squeeze manual translations ]
+ * German (Wolfgang Schweer).
+ * French (Cédric Boutillier).
+ * Italian (Claudio Carboncini).
+ * Danish (Joe Hansen).
+
+ [ Updated Wheezy manual translations ]
+ * German (Wolfgang Schweer).
+ * French (David Prévot).
+ * Danish (Joe Hansen).
+ * Italian (Francesca Ciceri).
+
+ -- David Prévot taf...@debian.org Fri, 15 Feb 2013 22:18:55 -0400
+
debian-edu-doc (1.4~20120925~6.0.6+r0) unstable; urgency=low
* debian/debian-edu-doc-{es,fr,it}.preinst: Remove previous images symlinks
diff -Nru --exclude documentation --exclude mail_stats_to_list debian-edu-doc-1.4~20120925~6.0.6+r0/debian/control debian-edu-doc-1.5~20130228~7.0/debian/control
--- debian-edu-doc-1.4~20120925~6.0.6+r0/debian/control 2012-07-05 21:00:20.0 -0400
+++ debian-edu-doc-1.5~20130228~7.0/debian/control 2013-02-28 18:56:24.0 -0400
@@ -4,7 +4,7 @@
Build-Depends: debhelper (= 5)
Build-Depends-Indep: docbook-utils, poxml, ldp-docbook-xsl, dblatex, po4a,
gsfonts, lmodern, texlive-xetex,
- ttf-arphic-gbsn00lp, ttf-arphic-bsmi00lp, ttf-wqy-zenhei,
+ fonts-arphic-gbsn00lp, fonts-arphic-bsmi00lp, ttf-wqy-zenhei,
texlive-lang-cyrillic, texlive-lang-danish, texlive-lang-spanish,
texlive-lang-french, texlive-lang-german, texlive-lang-italian,
texlive-lang-norwegian, imagemagick
@@ -14,14 +14,14 @@
David Prévot taf...@debian.org
Standards-Version: 3.9.3
Homepage: http://wiki.debian.org/DebianEdu/Documentation/Squeeze
-Vcs-Svn: svn://svn.debian.org/svn/debian-edu/trunk/src/debian-edu-doc/
-Vcs-Browser: http://anonscm.debian.org/viewvc/debian-edu/trunk/src/debian-edu-doc/
+Vcs-Git: git://anonscm.debian.org/debian-edu/debian-edu-doc.git
+Vcs-Browser: http://anonscm.debian.org/gitweb/?p=debian-edu/debian-edu-doc.git;a=summary
Package: debian-edu-doc-en
Depends: ${misc:Depends}
Architecture: all
Description: English documentation from the Debian Edu project
- The English version of the manual for the Squeeze based release of
+ The English version of the manual for the Squeeze and Wheezy based release of
the Debian Edu / Skolelinux project is included in this package, as well as
the Rosegarden and Audacity manuals.
.
@@ -33,7 +33,7 @@
Depends: debian-edu-doc-en, ${misc:Depends}
Architecture: all
Description: Danish documentation from the Debian Edu project
- The Danish version of the manual for the Squeeze based release of
+ The Danish version of the manual for the Squeeze and Wheezy based release of
the Debian Edu / Skolelinux project is included
Bug#701939: marked as done (unblock: libio-async-loop-glib-perl/0.20-3)
Your message dated Fri, 01 Mar 2013 06:03:48 + with message-id 1362117828.8518.1.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#701939: unblock: libio-async-loop-glib-perl/0.20-3 has caused the Debian Bug report #701939, regarding unblock: libio-async-loop-glib-perl/0.20-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.) -- 701939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701939 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 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package libio-async-loop-glib-perl/0.20-3. The unblock disables a test which fixes #699258. Upstream considers the tests unreliable and has removed them for the next release: https://rt.cpan.org/Public/Bug/Display.html?id=83033 Debdiff attached. unblock libio-async-loop-glib-perl/0.20-3 Thanks in advance, gregor -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRL/cRAAoJELs6aAGGSaoGfTEQAI7bB9gHtT2I1OSo4W4zhGLh 2dAfqv0XYfcY7xJlB1DpmCbLjzDtj5N23hOFZSL3CjI2frt6xp1m+Fcw+60DcFr1 1uYgp6/XV3t50STtQzttlWpKiN5iIsLXuTrCIC7Dt6B1+cebAVG8lGJMxFKRL9pn W+FqvVksh7U/NSnhB1/tzPKY5OMnbJ24huLn6Jy/SfYfGIITmgRITrt0SrR8r306 SUjCal7Du5Wib/nFU6/fGJap3carzEtUvEnGqgfkmfznnXvAorgDJN6ByD5q2FqU H8kwtUJ/D3V6PpseGLH6zpn7HtGc6wLfpkaDOIct/1eE/Xmz2vNtQAHMndkftjy2 fvtjxGN7e+gC4BdgaA24a1/BLkxpFHSSKMqtYb1ffrQwzIMrSnuLovWo0IfSULxy iV7V1r0Jn2Ifmtsi9UUERQsRubFQCLtBQGsYe9Hll46kPWLLaXCGyTbd2cdP7gDx ZWLuKWWTzu6YwO/jBQRKBSPqqSNHTDENbqN8/UwP8e0vEUet6rOwm77zuKWbcwKv pO4FcVdk9H2oGd15fnVk0Of2SWIzmr0srGFKYlVsR2MaJ0Lfpt7/BeU1GfQ+fmFX zWuv0tWba52H3J6t7AUCXcyyPZg7dgq11OccX0FlNwGvWVme8Y979IEFWksEgfF3 avDYJpgfeGqDQp74Hnkr =APYZ -END PGP SIGNATURE- diff -Nru libio-async-loop-glib-perl-0.20/debian/changelog libio-async-loop-glib-perl-0.20/debian/changelog --- libio-async-loop-glib-perl-0.20/debian/changelog 2012-08-15 15:16:32.0 +0200 +++ libio-async-loop-glib-perl-0.20/debian/changelog 2013-03-01 01:18:32.0 +0100 @@ -1,3 +1,11 @@ +libio-async-loop-glib-perl (0.20-3) unstable; urgency=low + + * Disable t/06loop-control.t. These tests are unreliable and have been +removed by upstream for the next release; cf. CPAN RT#83033. +(Closes: #699258) + + -- gregor herrmann gre...@debian.org Fri, 01 Mar 2013 01:16:04 +0100 + libio-async-loop-glib-perl (0.20-2) unstable; urgency=low * Add patch pollhup.patch: remove declaration that IO::Async::Loop::Glib diff -Nru libio-async-loop-glib-perl-0.20/debian/rules libio-async-loop-glib-perl-0.20/debian/rules --- libio-async-loop-glib-perl-0.20/debian/rules 2012-08-15 15:16:32.0 +0200 +++ libio-async-loop-glib-perl-0.20/debian/rules 2013-03-01 01:18:32.0 +0100 @@ -1,4 +1,9 @@ #!/usr/bin/make -f +TEST_FILES=$(filter-out t/06loop-control.t,$(shell echo t/*.t)) + %: dh $@ + +override_dh_auto_test: + dh_auto_test -- TEST_FILES=$(TEST_FILES) ---End Message--- ---BeginMessage--- On Fri, 2013-03-01 at 01:32 +0100, gregor herrmann wrote: Please unblock package libio-async-loop-glib-perl/0.20-3. The unblock disables a test which fixes #699258. Upstream considers the tests unreliable and has removed them for the next release: https://rt.cpan.org/Public/Bug/Display.html?id=83033 Unblocked; thanks. Regards, Adam---End Message---
Bug#685230: unblock hylafax 3:6.0.6-4
Hello Julien, Julien Cristau wrote on 2013-02-28 22:11: This version 3:6.0.6-5 should be uploaded to unstable. is there an ETA for that new upload? At first we need an updated version of capi4hylafax to solve one half of the problems between hylafax and capi4hylafax. This new version is already on mentors.d.o ready for wheezy: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697733 And I have asked the release team for pre-approval: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699171 The next step is creating hylafax 6.0.6-5 as mentioned by Ivo De Decker. Should I already prepare these updated package of hylafax now? --- Have a nice day. Joachim (Germany) -- 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/20130301080027.2fd6b...@jupiter.home
Bug#699148: unblock: celery/2.5.3-2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-02-28 21:27, Adam D. Barratt wrote: Any news on an upload? 2.5.3-3 is prepared in SVN but paravoid (my sponsor on celery) seems to be busy. Cheers, - -- Michael Fladischer Fladi.at -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlEwTiEACgkQeJ3z1zFMUGZrpgCdH1oB+9oH6E4lpNHf/ktooD1c D5kAoILthBpjr5JovfuqTG+uSYqf90Au =dqbX -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/51304e23.9050...@fladi.at
