Re: Bug#592539: (isc-dhcp-server: supply additional initscript for IPv6 daemon): Yet another idea how to solve this issue
Hi, On Fri, Oct 26, 2012 at 01:11:41PM +0200, Jan Wagner wrote: Could you please state, if you would accept such fix via t-p-u, if this was also fixed in unstable. iff this fix has spent a while in unstable and was confirmed not to have some unpleasant side effects that affect IPv4 usage. There's no way this will be accepted just into t-p-u without unstable being fixed. This fix will enhance the IPv6-readyness in wheezy a lot, as in the next years the IPv6 rollout in corporate networks requires DHCPv6 in most cases (beside maybe parallel DHCPv4). Meh, DHCPv6 is mostly used with Windows clients anyway. Many people relate the necessity of running DHCPv4 when using IPv4 with DHCPv6 and IPv6. That's simply not true. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#691664: unblock: libinfinity/0.5.2-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libinfinity
Fix a crash that could occur when it is noticed at send time that a
connection is down. Fix a broken recommends.
0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch adds
some state tracking to see if the data processing handler is currently
in XML or TLS processing and frees resources accordingly.
0001-Rework-Gtk3-support.patch had to be refreshed to be able to apply
correctly. Sorry for not reordering the series so that this wouldn't
have been necessary.
unblock libinfinity/0.5.2-5
Thanks
Philipp Kern
Base version: libinfinity_0.5.2-3 from testing
Target version: libinfinity_0.5.2-5 from unstable
No hints in place.
changelog | 18
control |2
patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch | 393 ++
patches/0001-Rework-Gtk3-support.patch | 47 -
patches/series |1
5 files changed, 435 insertions(+), 26 deletions(-)
gpgv: keyblock resource `/home/pkern/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made Sat 02 Jun 2012 10:19:37 PM UTC using DSA key ID B2CFCDD8
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpRo6cmB/libinfinity_0.5.2-3.dsc
gpgv: keyblock resource `/home/pkern/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made Tue 23 Oct 2012 10:18:42 PM UTC using RSA key ID 35D056EC
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpRo6cmB/libinfinity_0.5.2-5.dsc
diff -Nru libinfinity-0.5.2/debian/changelog libinfinity-0.5.2/debian/changelog
--- libinfinity-0.5.2/debian/changelog 2012-06-02 21:59:24.0 +
+++ libinfinity-0.5.2/debian/changelog 2012-10-23 22:08:40.0 +
@@ -1,3 +1,21 @@
+libinfinity (0.5.2-5) unstable; urgency=low
+
+ * Fix a crash when a connection goes down while attempting to
+send data.
+ * Revert Mark infinoted multi-arch:foreign. It would not be useful
+in wheezy.
+ * Refresh patch Rework Gtk3 support.
+
+ -- Philipp Kern pk...@debian.org Wed, 24 Oct 2012 00:04:51 +0200
+
+libinfinity (0.5.2-4) unstable; urgency=low
+
+ * Recommend the correct infgtk3 library package in libinfinity-0.5-dbg.
+(Closes: #680444)
+ * Mark infinoted multi-arch:foreign.
+
+ -- Philipp Kern pk...@debian.org Tue, 10 Jul 2012 12:34:18 -0600
+
libinfinity (0.5.2-3) unstable; urgency=low
* Make infinoted the real daemon package, providing the non-versioned
diff -Nru libinfinity-0.5.2/debian/control libinfinity-0.5.2/debian/control
--- libinfinity-0.5.2/debian/control 2012-06-02 21:36:41.0 +
+++ libinfinity-0.5.2/debian/control 2012-10-23 22:06:54.0 +
@@ -42,7 +42,7 @@
Architecture: any
Pre-Depends: dpkg (= 1.15.6)
Depends: ${misc:Depends}, libinfinity-0.5-0 (= ${binary:Version})
-Recommends: libinfgtk-0.5-0 (= ${binary:Version}), infinoted-0.5 (= ${binary:Version})
+Recommends: libinfgtk3-0.5-0 (= ${binary:Version}), infinoted-0.5 (= ${binary:Version})
Description: infinote-based collaborative editing - debugging symbols
libinfinity is library to build collaborative text editors. Changes
to the text buffers are synced to all other clients over a central server.
diff -Nru libinfinity-0.5.2/debian/patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch libinfinity-0.5.2/debian/patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch
--- libinfinity-0.5.2/debian/patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch 1970-01-01 00:00:00.0 +
+++ libinfinity-0.5.2/debian/patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch 2012-10-23 22:03:30.0 +
@@ -0,0 +1,393 @@
+From 9469bdf6116857c9d4c3df154dadb942285c9d98 Mon Sep 17 00:00:00 2001
+From: Armin Burgmeier ar...@arbur.net
+Date: Sun, 21 Oct 2012 17:14:35 +0200
+Subject: [PATCH] Fix a crash when a connection goes down while attempting to
+ send data
+
+2012-10-21 Armin Burgmeier ar...@arbur.net
+
+ * libinfinity/common/inf-xmpp-connection.c: Fix a crash that could
+ occur when it is noticed at send time that a connection is down.
+
+diff --git a/libinfinity/common/inf-xmpp-connection.c b/libinfinity/common/inf-xmpp-connection.c
+index b6f7fe3..6bf2edb 100644
+--- a/libinfinity/common/inf-xmpp-connection.c
b/libinfinity/common/inf-xmpp-connection.c
+@@ -117,7 +117,7 @@ struct _InfXmppConnectionPrivate {
+ InfXmppConnectionMessage* last_message;
+
+ /* XML parsing */
+- gboolean parsing; /* Whether we are currently in an XML parser callback */
++ guint parsing; /* Whether we are currently in an XML parser or GnuTLS callback */
+
Bug#691664: marked as done (unblock: libinfinity/0.5.2-5)
Your message dated Sun, 28 Oct 2012 10:56:20 +
with message-id 1351421780.5616.60.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#691664: unblock: libinfinity/0.5.2-5
has caused the Debian Bug report #691664,
regarding unblock: libinfinity/0.5.2-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
691664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691664
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 libinfinity
Fix a crash that could occur when it is noticed at send time that a
connection is down. Fix a broken recommends.
0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch adds
some state tracking to see if the data processing handler is currently
in XML or TLS processing and frees resources accordingly.
0001-Rework-Gtk3-support.patch had to be refreshed to be able to apply
correctly. Sorry for not reordering the series so that this wouldn't
have been necessary.
unblock libinfinity/0.5.2-5
Thanks
Philipp Kern
Base version: libinfinity_0.5.2-3 from testing
Target version: libinfinity_0.5.2-5 from unstable
No hints in place.
changelog | 18
control |2
patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch | 393 ++
patches/0001-Rework-Gtk3-support.patch | 47 -
patches/series |1
5 files changed, 435 insertions(+), 26 deletions(-)
gpgv: keyblock resource `/home/pkern/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made Sat 02 Jun 2012 10:19:37 PM UTC using DSA key ID B2CFCDD8
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpRo6cmB/libinfinity_0.5.2-3.dsc
gpgv: keyblock resource `/home/pkern/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made Tue 23 Oct 2012 10:18:42 PM UTC using RSA key ID 35D056EC
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpRo6cmB/libinfinity_0.5.2-5.dsc
diff -Nru libinfinity-0.5.2/debian/changelog libinfinity-0.5.2/debian/changelog
--- libinfinity-0.5.2/debian/changelog 2012-06-02 21:59:24.0 +
+++ libinfinity-0.5.2/debian/changelog 2012-10-23 22:08:40.0 +
@@ -1,3 +1,21 @@
+libinfinity (0.5.2-5) unstable; urgency=low
+
+ * Fix a crash when a connection goes down while attempting to
+send data.
+ * Revert Mark infinoted multi-arch:foreign. It would not be useful
+in wheezy.
+ * Refresh patch Rework Gtk3 support.
+
+ -- Philipp Kern pk...@debian.org Wed, 24 Oct 2012 00:04:51 +0200
+
+libinfinity (0.5.2-4) unstable; urgency=low
+
+ * Recommend the correct infgtk3 library package in libinfinity-0.5-dbg.
+(Closes: #680444)
+ * Mark infinoted multi-arch:foreign.
+
+ -- Philipp Kern pk...@debian.org Tue, 10 Jul 2012 12:34:18 -0600
+
libinfinity (0.5.2-3) unstable; urgency=low
* Make infinoted the real daemon package, providing the non-versioned
diff -Nru libinfinity-0.5.2/debian/control libinfinity-0.5.2/debian/control
--- libinfinity-0.5.2/debian/control 2012-06-02 21:36:41.0 +
+++ libinfinity-0.5.2/debian/control 2012-10-23 22:06:54.0 +
@@ -42,7 +42,7 @@
Architecture: any
Pre-Depends: dpkg (= 1.15.6)
Depends: ${misc:Depends}, libinfinity-0.5-0 (= ${binary:Version})
-Recommends: libinfgtk-0.5-0 (= ${binary:Version}), infinoted-0.5 (= ${binary:Version})
+Recommends: libinfgtk3-0.5-0 (= ${binary:Version}), infinoted-0.5 (= ${binary:Version})
Description: infinote-based collaborative editing - debugging symbols
libinfinity is library to build collaborative text editors. Changes
to the text buffers are synced to all other clients over a central server.
diff -Nru libinfinity-0.5.2/debian/patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch libinfinity-0.5.2/debian/patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch
--- libinfinity-0.5.2/debian/patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch 1970-01-01 00:00:00.0 +
+++ libinfinity-0.5.2/debian/patches/0001-Fix-a-crash-when-a-connection-goes-down-while-attemp.patch 2012-10-23 22:03:30.0 +
@@ -0,0 +1,393 @@
+From 9469bdf6116857c9d4c3df154dadb942285c9d98 Mon Sep 17 00:00:00 2001
+From: Armin Burgmeier
NEW changes in stable-new
Processing changes file: request-tracker3.8_3.8.8-7+squeeze6_i386.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tsqd3-0007yo...@franck.debian.org
Bug#687487: pre-approve unblock: manpages-de/1.2-1
retitle 687487 unblock: manpages-de/1.2-1 thanks Am 11.10.2012 22:56, schrieb Julien Cristau: On Thu, Sep 13, 2012 at 10:23:08 +0200, Tobias Quathamer wrote: Dear release managers, I'd like to upload a new upstream version of the German translation of various manpages. I've added a check in the configure script to ensure that the required program po4a is installed on the system. Would you accept such a change for a freeze exception as well? If not, I'd revert that patch upstream and release a version with translation updates only. That's fine, go ahead with the upload. Just uploaded to unstable, thanks for the feedback. unblock manpages-de/1.2-1 Regards, Tobias signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#687487: pre-approve unblock: manpages-de/1.2-1
Processing commands for cont...@bugs.debian.org: retitle 687487 unblock: manpages-de/1.2-1 Bug #687487 [release.debian.org] pre-approve unblock: manpages-de/1.2-1 Changed Bug title to 'unblock: manpages-de/1.2-1' from 'pre-approve unblock: manpages-de/1.2-1' thanks Stopping processing here. Please contact me if you need assistance. -- 687487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687487 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.13514229848.transcr...@bugs.debian.org
Bug#691647: unblock: schroot/1.6.4-1
On Sun, Oct 28, 2012 at 12:39:28AM +0100, Roger Leigh wrote: Please unblock package schroot I have uploaded schroot 1.6.4-1 to unstable. This contains some documentation for wheezy upgrade issues, plus some fixes for serious and important bugs in wheezy: I had to make an additional 3 line change to fix building on hurd and kfreebsd (attached) Thanks, Roger unblock schroot/1.6.4-2 -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 diff -Nru schroot-1.6.4/debian/changelog schroot-1.6.4/debian/changelog --- schroot-1.6.4/debian/changelog 2012-10-27 23:39:05.0 +0100 +++ schroot-1.6.4/debian/changelog 2012-10-28 11:53:31.0 + @@ -1,3 +1,12 @@ +schroot (1.6.4-2) unstable; urgency=low + + * sbuild::chroot_facet_session_clonable: Include +sbuild-chroot-block-device-base.h, which was missing on +kFreeBSD and Hurd builds (it's included indirectly on Linux +via the LVM snapshot header). + + -- Roger Leigh rle...@debian.org Sun, 28 Oct 2012 11:49:57 + + schroot (1.6.4-1) unstable; urgency=low * New upstream stable release. diff -Nru schroot-1.6.4/debian/patches/1.6.4-2 schroot-1.6.4/debian/patches/1.6.4-2 --- schroot-1.6.4/debian/patches/1.6.4-21970-01-01 01:00:00.0 +0100 +++ schroot-1.6.4/debian/patches/1.6.4-22012-10-28 11:54:35.0 + @@ -0,0 +1,23 @@ +Description: 1.6.4-2 + schroot (1.6.4-2) unstable; urgency=low + . + * sbuild::chroot_facet_session_clonable: Include + sbuild-chroot-block-device-base.h, which was missing on + kFreeBSD and Hurd builds (it's included indirectly on Linux + via the LVM snapshot header). +Author: Roger Leigh rle...@debian.org + +--- + +--- schroot-1.6.4.orig/sbuild/sbuild-chroot-facet-session-clonable.cc schroot-1.6.4/sbuild/sbuild-chroot-facet-session-clonable.cc +@@ -24,6 +24,9 @@ + #include sbuild-chroot-facet-session-clonable.h + #include sbuild-chroot-facet-source-clonable.h + #include sbuild-chroot-plain.h ++#ifdef SBUILD_FEATURE_BLOCKDEV ++#include sbuild-chroot-block-device-base.h ++#endif + #ifdef SBUILD_FEATURE_LVMSNAP + #include sbuild-chroot-lvm-snapshot.h + #endif // SBUILD_FEATURE_LVMSNAP diff -Nru schroot-1.6.4/debian/patches/series schroot-1.6.4/debian/patches/series --- schroot-1.6.4/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ schroot-1.6.4/debian/patches/series 2012-10-28 11:53:59.0 + @@ -0,0 +1 @@ +1.6.4-2
Bug#691675: unblock: libskk/1.0.0-1 ibus-skk/1.4.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libskk/1.0.0-1 and ibus-skk/1.4.1-2
I am requesting unblock on behalf of the maintainer. (We discussed)
These packages are maintained by Daiki who is DM and the upstream. In
retrospect, this upload of libskk/1.0.0-1 should have been made in the
form of 0.0.12-4. (0.0.12-3 was uploaded by me before the freeze).
The libskk transition from 0.0.12-3 to 1.0.0-1 seems big but there is no
API change and fix several critical porting issues and minor bugs. He
included his patch used in my libskk 0.0.12-3 Debian upload to the
upstream source tree fixing ARM/MIPS bug #674471. He fixed another RC
level bug causing segmentation fault in BSD systems. This may fix our
kFreeBSD port too. (No bug reported on Debian yet.)
https://github.com/ueno/libskk/issues/18
https://github.com/ueno/libskk/commit/a95245abe22eda52255daf3925d587907ca6f925
The upstream patches between 0.0.12 and 1.0.0 is attached here. (Some are
testing code changes.)
ibus-skk transition from 1.4.1-2 to 1.4.1-2 fixes #686472 which just
add missed documentation in Debian packaging. (This is not RC bug but
very safe fix. Since this ensures rebuild against new libskk/1.0.0-1
to make us feel safer although no API has changed.)
Here is some back ground. Daiki (DM) is one of the leading upstream
coder of the GNOME ibus input method code. He is the primary upstream
coder of skk related modules for ibus too. But He is new to Debian and
I handed these packages to him as DM very recently.
Daiki assured me with API stability of these changes when contacted
on these. (I was worried about these may block my ibus package
transition to testing. Now I know it is OK without the unblock of thee.
But fixing segfaults is nice thing to have.)
(include/attach the debdiff against the package in testing)
* The upstream patch set between 0.0.12 and 1.0.0 is attached here for
libskk/1.0.0-1.
* Debdiff: ibus-skk_1.4.1-2.debdiff attached.
unblock libskk/1.0.0-1
unblock ibus-skk/1.4.1-2
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (10, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
From bdbf9319ec8720fb128cb0c5c97aaa65268473d2 Mon Sep 17 00:00:00 2001
From: Daiki Ueno u...@unixuser.org
Date: Mon, 16 Apr 2012 16:07:37 +0900
Subject: [PATCH 01/13] Make some map files optional.
---
libskk/map-file.vala | 32
libskk/rom-kana.vala |2 +-
libskk/rule.vala | 41 +
3 files changed, 50 insertions(+), 25 deletions(-)
diff --git a/libskk/map-file.vala b/libskk/map-file.vala
index 4482671..b1272c9 100644
--- a/libskk/map-file.vala
+++ b/libskk/map-file.vala
@@ -34,19 +34,13 @@ namespace Skk {
}
}
-void load (string rule,
+void load (RuleMetadata metadata,
string type,
string name,
Setstring included) throws RuleParseError
{
-var metadata = Rule.find_rule (rule);
-if (metadata == null) {
-throw new RuleParseError.FAILED (can't find rule %s, rule);
-}
-var filename = Path.build_filename (metadata.base_dir,
-type,
-name + .json);
-if (!FileUtils.test (filename, FileTest.EXISTS)) {
+var filename = metadata.locate_map_file (type, name);
+if (filename == null) {
throw new RuleParseError.FAILED (no such file %s, filename);
}
@@ -80,15 +74,21 @@ namespace Skk {
throw new RuleParseError.FAILED (
found circular include of %s, parent);
}
+string parent_rule, parent_name;
var index = parent.index_of (/);
if (index 0) {
-load (rule, type, parent, included);
+parent_rule = metadata.name;
+parent_name = parent;
} else {
-load (parent[0:index],
- type,
- parent[index + 1:parent.length],
- included);
+parent_rule = parent[0:index];
+parent_name = parent[index + 1:parent.length];
+}
+var parent_metadata = Rule.find_rule (parent_rule);
+if (parent_metadata == null) {
+throw new RuleParseError.FAILED (can't find rule %s,
+
Bug#691676: unblock: ensymble/0.28-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-CC: eddy.petri...@gmail.com On Sun, Oct 21, 2012 at 12:46:43PM +0100, Dominic Hargreaves wrote: On Wed, Oct 10, 2012 at 11:02:10PM +0300, Eddy Petrișor wrote: I realized the previous 0.28-2.1 proposal had UNRELEASED as suite. I corrected this and attached the patch based on ensymble 0.28-2 to obtain 0.28-2.1. I would really prefer 0.29-1, but if not, Is this 0.28-2.1 version acceptable for a new upload? Dear debian-release, Eddy Petrișor has provided updates to my (RFA) package ensymble, fixing an important bug (#629125) relating to python compatibility). There are two options here: - 0.28-3 this is a minimal patch fixing #629125 (As Eddy points out this is actually #616799) - 0.29-1 this is a new upstream release which also fixes #629125 (severity: normal) based on some work I did a while ago but never managed to upload I have reviewed both sets of changes proposed by Eddy and merged them into my git repository. http://anonscm.debian.org/gitweb/?p=users/dom/ensymble.git;a=shortlog;h=refs/heads/0.28 http://anonscm.debian.org/gitweb/?p=users/dom/ensymble.git;a=shortlog;h=refs/heads/master I attach diffs for both. Note that the one including 0.29 is long because upstream has reorganised the directory layout, but the actual changes are minimal - see http://code.google.com/p/ensymble/source/list. I think both are suitable for wheezy. Please let me know which one you prefer, and I'll upload it. In the interests in expedience and taking some workload off the release team, I have uploaded 0.28-3 (which qualifies for an unblock as is it is a minimal fix for an important bug in an optional package). Please unblock: unblock ensymble/0.28-3 Thanks, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- 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/20121028134049.gn4...@urchin.earth.li
Processed: retitle 683323 to unblock: python-apt/0.8.8
Processing commands for cont...@bugs.debian.org: retitle 683323 unblock: python-apt/0.8.8 Bug #683323 [release.debian.org] unblock: python-apt/0.8.7 Bug #684450 [release.debian.org] unblock: python-apt/0.8.7 Changed Bug title to 'unblock: python-apt/0.8.8' from 'unblock: python-apt/0.8.7' Changed Bug title to 'unblock: python-apt/0.8.8' from 'unblock: python-apt/0.8.7' thanks Stopping processing here. Please contact me if you need assistance. -- 683323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683323 684450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684450 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.135143575415682.transcr...@bugs.debian.org
Bug#691185: pre-approval: perl/5.14.2-15
On Sat, Oct 27, 2012 at 07:52:17PM +0100, Adam D. Barratt wrote: Control: tags -1 + confirmed On Mon, 2012-10-22 at 21:45 +0300, Niko Tyni wrote: Upstream recently released 5.14.3, which is a bugfix only stable update. We're assuming that importing this into wheezy is out of question at this point, but please let us know if you'd be willing to entertain that option. The upstream rules for stable updates are quite strict; see the 'MAINTENANCE BRANCHES' section in perlpolicy(1) of the perl-doc package for details. In principle it doesn't sound entirely unreasonable, but I'd like a little more information as to the specific fixes included. Hi Adam, Niko posted a summary of 5.14.3 changes at http://lists.alioth.debian.org/pipermail/perl-maintainers/2012-October/003321.html taking some snippets from that, the changes not in Niko's 5.14.2-15 proposal which would be added by importing 5.14.3 are: - Module::CoreList has been updated to version 2.49_04 to add data for this release. - In Configure, the test for procselfexe was refactored into a loop. - Linux: libutil is no longer used when compiling on Linux platforms, which avoids warnings being emitted. (already fixed in a different way in Debian) - Linux: The system gcc (rather than any other gcc which might be in the compiling user's path) is now used when searching for libraries such as -lm. - The sitecustomize support was made relocatableinc aware, so that -Dusesitecustomize and -Duserelocatableinc may be used together. and some platform specific fixes for non-Debian platforms: - FreeBSD: The FreeBSD hints file was corrected to be compatible with FreeBSD 10.0. - Solaris and NetBSD: Configure was updated for procselfexe support on Solaris and NetBSD. - HP-UX: README.hpux was updated to note the existence of a broken header in HP-UX 11.00. - Mac OS X: The locale tests were updated to reflect the behaviour of locales in Mountain Lion. - NetBSD: The NetBSD hints file was corrected to be compatible with NetBSD 6.* Moving to 5.14.3 would have the advantage that it will reduce Debian's patch count and therefore make later analysis and patch management/triage a bit easier; it will need to be accompanied by a new libmodule-corelist-perl package for consistency. I'm not aware at this stage of any other external changes needed. The upstream full changelog is at https://metacpan.org/module/DOM/perl-5.14.3/pod/perldelta.pod Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- 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/20121028150717.gq4...@urchin.earth.li
Re: Bug#683323: unblock: python-apt/0.8.7
Hi,
A quick note first, as I noticed the subject was updated to reference
0.8.8... That version isn't a valid candidate right now in any case, as
it FTBFS on approximately half the architectures - see
https://buildd.debian.org/status/package.php?p=python-apt
On Mon, 2012-10-15 at 09:14 +0200, Michael Vogt wrote:
On Sun, Oct 14, 2012 at 01:48:52PM +0300, Martin-Éric Racine wrote:
2012/9/3 Michael Vogt m...@debian.org:
I created a branch at
http://anonscm.debian.org/bzr/bzr/apt/python-apt/debian-wheezy/ that
is based on the debian-sid branch but disables auth.py. I am happy to
upload this to wheezy if that approach is approved by the release
team.
[...]
A separate branch was created for Wheezy and a debdiff submitted. Is
there anything else missing to move this issue forward and achieve a
concensus about what will be allowed into Testing?
Unfortunately, that debdiff never made it to debian-release@ due to the
size of the diff.
Extracting it from the BTS and excluding *.po{,t}, tests/* and the
disabled module brings it down to
20 files changed, 523 insertions(+), 92 deletions(-)
which is a little more manageable.
A good chunk of that diff appears to be data file / documentation
updates, the changelog and some Python 3 string-handling fixes. The rest
of the fixes look sane enough.
It would be great to know the direction, I uploaded a version of
python-apt 0.8.8 to sid in the meantime with some more fixes. I am
happy to cherry pick the fixes to the wheezy branch - but of course I
need to know if thats the way forward or if 0.8.8 (with the auth.py
module) is allowed to get in. I'm happy either way. I would slightly
prefer 0.8.8 as the auth.py module is IMO a good idea compared to
having multiple apps duplicating this code in various places.
Whilst I agree that reducing code duplication is generally a good thing,
for wheezy the practical difference is presumably none given that
nothing outside of python-apt itself would be using the code?
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/1351442201.5616.69.ca...@jacala.jungle.funky-badger.org
Bug#689765: unblock: libio-socket-ssl-perl/1.76-2
Control: retitle -1 unblock: libio-socket-ssl-perl/1.76-2
Hi
I asked on IRC on #debian-release if it is okay to upload this to
unstable to give it testing. Neil McGovern answered me to upload it
now to unstable and ping here again when accepted.
Would it possible to unblock it? Only change is the patch applied by
upstream. Debdiff for the package is attached.
There is no Debian Bug in the BTS, but upstream's RT is at [1].
[1]: https://rt.cpan.org/Public/Bug/Display.html?id=79916
Regards,
Salvatore
Base version: libio-socket-ssl-perl_1.76-1 from testing
Target version: libio-socket-ssl-perl_1.76-2 from unstable
No hints in place.
changelog |7 +
patches/0001-Fix-update_peer-subroutine-to-work-with-IPv6.patch | 48
++
patches/series |1
3 files changed, 56 insertions(+)
diff -Nru libio-socket-ssl-perl-1.76/debian/changelog
libio-socket-ssl-perl-1.76/debian/changelog
--- libio-socket-ssl-perl-1.76/debian/changelog 2012-06-22 13:40:40.0
+
+++ libio-socket-ssl-perl-1.76/debian/changelog 2012-10-27 16:32:23.0
+
@@ -1,3 +1,10 @@
+libio-socket-ssl-perl (1.76-2) unstable; urgency=low
+
+ * Add 0001-Fix-update_peer-subroutine-to-work-with-IPv6.patch patch.
+Fix _update_peer subroutine to work with IPv6.
+
+ -- Salvatore Bonaccorso car...@debian.org Fri, 05 Oct 2012 17:41:19 +0200
+
libio-socket-ssl-perl (1.76-1) unstable; urgency=low
* Imported Upstream version 1.75 and 1.76
diff -Nru
libio-socket-ssl-perl-1.76/debian/patches/0001-Fix-update_peer-subroutine-to-work-with-IPv6.patch
libio-socket-ssl-perl-1.76/debian/patches/0001-Fix-update_peer-subroutine-to-work-with-IPv6.patch
---
libio-socket-ssl-perl-1.76/debian/patches/0001-Fix-update_peer-subroutine-to-work-with-IPv6.patch
1970-01-01 00:00:00.0 +
+++
libio-socket-ssl-perl-1.76/debian/patches/0001-Fix-update_peer-subroutine-to-work-with-IPv6.patch
2012-10-27 16:32:23.0 +
@@ -0,0 +1,48 @@
+Description: Fix _update_peer subroutine to work with IPv6
+Origin: vendor
+Bug: https://rt.cpan.org/Public/Bug/Display.html?id=79916
+Forwarded: not-needed
+Author: Salvatore Bonaccorso car...@debian.org
+Last-Update: 2012-10-05
+
+---
+ SSL.pm | 18 +-
+ 1 file changed, 13 insertions(+), 5 deletions(-)
+
+--- a/SSL.pm
b/SSL.pm
+@@ -69,11 +69,11 @@
+ my $ip6 = eval {
+ require Socket;
+ Socket-VERSION(1.95);
+- Socket-import( 'inet_pton' );
++ Socket-import( qw/inet_pton inet_ntop/ );
+ 1;
+ } || eval {
+ require Socket6;
+- Socket6-import( 'inet_pton' );
++ Socket6-import( qw/inet_pton inet_ntop/ );
+ 1;
+ };
+
+@@ -525,9 +525,17 @@
+ my $self = shift;
+ my $arg_hash = ${*$self}{'_SSL_arguments'};
+ eval {
+- my ($port,$addr) = sockaddr_in( getpeername( $self ));
+- $arg_hash-{PeerAddr} = inet_ntoa( $addr );
+- $arg_hash-{PeerPort} = $port;
++my $sockaddr = getpeername( $self );
++my $af = sockaddr_family($sockaddr);
++if( $af == AF_INET6 ) {
++my ($port, $addr, $scope, $flow ) = unpack_sockaddr_in6(
$sockaddr );
++$arg_hash-{PeerAddr} = inet_ntop( $af, $addr );
++$arg_hash-{PeerPort} = $port;
++} else {
++my ($port,$addr) = sockaddr_in( $sockaddr);
++$arg_hash-{PeerAddr} = inet_ntoa( $addr );
++$arg_hash-{PeerPort} = $port;
++}
+ }
+ }
+
diff -Nru libio-socket-ssl-perl-1.76/debian/patches/series
libio-socket-ssl-perl-1.76/debian/patches/series
--- libio-socket-ssl-perl-1.76/debian/patches/series1970-01-01
00:00:00.0 +
+++ libio-socket-ssl-perl-1.76/debian/patches/series2012-10-27
16:32:23.0 +
@@ -0,0 +1 @@
+0001-Fix-update_peer-subroutine-to-work-with-IPv6.patch
signature.asc
Description: Digital signature
Processed: Re: Bug#689765: unblock: libio-socket-ssl-perl/1.76-2
Processing control commands: retitle -1 unblock: libio-socket-ssl-perl/1.76-2 Bug #689765 [release.debian.org] [pre-approval request] unblock: libio-socket-ssl-perl/1.76-2 Changed Bug title to 'unblock: libio-socket-ssl-perl/1.76-2' from '[pre-approval request] unblock: libio-socket-ssl-perl/1.76-2' -- 689765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689765 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.b689765.13514434231276.transcr...@bugs.debian.org
Bug#689765: marked as done (unblock: libio-socket-ssl-perl/1.76-2)
Your message dated Sun, 28 Oct 2012 17:48:57 +
with message-id 1351446537.5616.70.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#689765: unblock: libio-socket-ssl-perl/1.76-2
has caused the Debian Bug report #689765,
regarding unblock: libio-socket-ssl-perl/1.76-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.)
--
689765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
Dear Release-Team
I have prepared an update for libio-socket-ssl-perl 1.76-1 which is
found in wheezy and unstable but not yet uploaded. 1.77 was released
upstream to fix[1].
[1]: https://rt.cpan.org/Public/Bug/Display.html?id=79916
Upstream RT#79916 is marked 'Serverity Critical'. As comment in SSL.pm
we can read, before the _update_peer subroutine:
# called if PeerAddr is not set in ${*$self}{'_SSL_arguments'}
# this can be the case if start_SSL is called with a normal IO::Socket::INET
# so that PeerAddr|PeerPort are not set from args
The following script demostrates the problem, but is not exactly what
the comment suggest. I was not able to reproduce a better example.
Daniel Kahn Gillmor gave me some quidance on #debian-perl.
cut-cut-cut-cut-cut-cut-
#!/usr/bin/perl
use strict;
use warnings;
use IO::Socket::SSL;
use IO::Socket::INET6;
my $sock = IO::Socket::INET6-new(
PeerAddr = '127.0.0.1',
PeerPort = 5556,
Type = SOCK_STREAM,
) or die Cannot construct socket - $@;
use Data::Show;
show $sock;
my $upgraded_sock = IO::Socket::SSL-start_SSL($sock);
use Data::Show;
show $upgraded_sock;
cut-cut-cut-cut-cut-cut-
With PeerAddr set to 127.0.0.1 you get for upgraded_sock:
cut-cut-cut-cut-cut-cut-
==( $upgraded_sock )==[ 'test.pl', line 19 ]==
do {
require Symbol;
my $a = bless(Symbol::gensym(), IO::Socket::SSL);
*{$a} = {
_SSL_arguments= {
PeerAddr = 127.0.0.1,
PeerPort = 5556,
Proto = tcp,
SSL_cert_file =
certs/client-cert.pem,
SSL_check_crl = 0,
SSL_honor_cipher_order = 0,
SSL_key_file =
certs/client-key.pem,
SSL_server = 0,
SSL_use_cert = 0,
SSL_verify_mode= 0,
SSL_version= SSLv23:!SSLv2,
},
_SSL_ctx = bless({ context = 27267440 },
IO::Socket::SSL::SSL_Context),
_SSL_fileno = 3,
_SSL_ioclass_upgraded = IO::Socket::INET6,
_SSL_object = 27913664,
_SSL_opened = 1,
io_socket_domain = 2,
io_socket_proto = 6,
io_socket_timeout = undef,
io_socket_type= 1,
};
$a;
}
cut-cut-cut-cut-cut-cut-
but for '::1' you see that PeerAddr is missing from _SSL_arguments:
cut-cut-cut-cut-cut-cut-
==( $upgraded_sock )==[ 'test.pl', line 19 ]==
do {
require Symbol;
my $a = bless(Symbol::gensym(), IO::Socket::SSL);
*{$a} = {
_SSL_arguments= {
Proto = tcp,
SSL_cert_file =
certs/client-cert.pem,
SSL_check_crl = 0,
SSL_honor_cipher_order = 0,
SSL_key_file =
certs/client-key.pem,
SSL_server = 0,
SSL_use_cert = 0,
SSL_verify_mode= 0,
SSL_version= SSLv23:!SSLv2,
},
_SSL_ctx = bless({ context = 14291248 },
IO::Socket::SSL::SSL_Context),
Bug#691698: unblock: dkimpy/0.5.2-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package dkimpy
This upload fixes two grave upstream issues (one of which has
securtyy implicaitions).
unblock dkimpy/0.5.2-1
diff -Nru dkimpy-0.5.2/ChangeLog dkimpy-0.5.3/ChangeLog
--- dkimpy-0.5.2/ChangeLog 2012-06-13 06:27:37.0 +0200
+++ dkimpy-0.5.3/ChangeLog 2012-07-21 07:41:31.0 +0200
@@ -1,4 +1,8 @@
-2012-06-13 Verion 0.5.2
+UNRELEASED Version 0.5.3
+- Make key parsing error messages more specific to help troubleshooting
+ (Based on user feedback)
+
+2012-06-13 Version 0.5.2
- Change canonicalization defaults to work around issues with different
verification implementations https://launchpad.net/bugs/939128
- Fully fold DKIM-Signature on sign, and ignore FWS in b= value on verify
diff -Nru dkimpy-0.5.2/debian/changelog dkimpy-0.5.3/debian/changelog
--- dkimpy-0.5.2/debian/changelog 2012-10-28 10:48:11.0 +0100
+++ dkimpy-0.5.3/debian/changelog 2012-10-28 10:48:12.0 +0100
@@ -1,3 +1,15 @@
+dkimpy (0.5.3-1) unstable; urgency=medium
+
+ * Urgency medium for multiple RC bug fixes
+ * New upstream release:
+ * Fix header unfolding and body hash calculation errors that cause
+correct DKIM signatures to fail to verify in many cases
+(Closes: #691663)
+ * Add minimum key length requirement to prevent validation of signatures
+generated with insecure keys (Closes: #691662)
+
+ -- Scott Kitterman sc...@kitterman.com Sun, 28 Oct 2012 10:32:13 +0100
+
dkimpy (0.5.2-1) unstable; urgency=low
* New upstream release
Binary files /tmp/vhfFWHbNtB/dkimpy-0.5.2/dkim/.asn1.py.swp and /tmp/4HMA0c1mG7/dkimpy-0.5.3/dkim/.asn1.py.swp differ
diff -Nru dkimpy-0.5.2/dkim/crypto.py dkimpy-0.5.3/dkim/crypto.py
--- dkimpy-0.5.2/dkim/crypto.py 2012-06-13 06:21:56.0 +0200
+++ dkimpy-0.5.3/dkim/crypto.py 2012-07-21 07:39:51.0 +0200
@@ -112,7 +112,7 @@
x = asn1_parse(ASN1_Object, data)
pkd = asn1_parse(ASN1_RSAPublicKey, x[0][1][1:])
except ASN1FormatError as e:
-raise UnparsableKeyError(str(e))
+raise UnparsableKeyError('Unparsable public key: ' + str(e))
pk = {
'modulus': pkd[0][0],
'publicExponent': pkd[0][1],
@@ -129,7 +129,7 @@
try:
pka = asn1_parse(ASN1_RSAPrivateKey, data)
except ASN1FormatError as e:
-raise UnparsableKeyError(str(e))
+raise UnparsableKeyError('Unparsable private key: ' + str(e))
pk = {
'version': pka[0][0],
'modulus': pka[0][1],
diff -Nru dkimpy-0.5.2/dkim/__init__.py dkimpy-0.5.3/dkim/__init__.py
--- dkimpy-0.5.2/dkim/__init__.py 2012-06-13 06:21:56.0 +0200
+++ dkimpy-0.5.3/dkim/__init__.py 2012-10-27 18:17:59.0 +0200
@@ -65,6 +65,10 @@
Relaxed = b'relaxed'# for clients passing dkim.Relaxed
Simple = b'simple' # for clients passing dkim.Simple
+def bitsize(x):
+Return size of long in bits.
+return len(bin(x)) - 2
+
class DKIMException(Exception):
Base class for DKIM errors.
pass
@@ -114,8 +118,8 @@
lastindex[h] = i
return sign_headers
-FWS = r'(?:\r\n\s+)?'
-RE_BTAG = re.compile(r'([; ]b'+FWS+r'=)(?:'+FWS+r'[a-zA-Z0-9+/=])*(?:\r\n\Z)?')
+FWS = r'(?:\r?\n\s+)?'
+RE_BTAG = re.compile(r'([;\s]b'+FWS+r'=)(?:'+FWS+r'[a-zA-Z0-9+/=])*(?:\r?\n\Z)?')
def hash_headers(hasher, canonicalize_headers, headers, include_headers,
sigheader, sig):
@@ -284,7 +288,8 @@
#: (with either \\n or \\r\\n line endings)
#: @param logger: a logger to which debug info will be written (default None)
#: @param signature_algorithm: the signing algorithm to use when signing
- def __init__(self,message=None,logger=None,signature_algorithm=b'rsa-sha256'):
+ def __init__(self,message=None,logger=None,signature_algorithm=b'rsa-sha256',
+minkey=1024):
self.set_message(message)
if logger is None:
logger = get_default_logger()
@@ -302,6 +307,9 @@
self.should_not_sign = set(DKIM.SHOULD_NOT)
#: Header fields to sign an extra time to prevent additions.
self.frozen_sign = set(DKIM.FROZEN)
+#: Minimum public key size. Shorter keys raise KeyFormatError. The
+#: default is 1024
+self.minkey = minkey
def add_frozen(self,s):
Add headers not in should_not_sign to frozen_sign.
@@ -337,6 +345,8 @@
#: is a name,value tuple. FIXME: The headers are canonicalized.
#: This could be more useful as original headers.
self.signed_headers = []
+#: The public key size last verified.
+self.keysize = 0
def default_sign_headers(self):
Return the default list of headers to sign: those in should_sign or
@@ -493,6 +503,8 @@
logger.debug(sig: %r % sig)
validate_signature_fields(sig)
+self.domain = sig[b'd']
+self.selector = sig[b's']
try:
canon_policy = CanonicalizationPolicy.from_c_value(sig.get(b'c'))
@@ -506,8
Bug#691702: unblock: ibus/1.4.1-8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock ibus/1.4.1-8 which fixes RC bug #691071 as well as a bit more maintenance updates. ibus (1.4.1-8) unstable; urgency=low * dh to call dh_girepository. Closes: #691071 * Removed unused-override unknown-section introspection for lintian. * Add symbols file for libibus-1.0-0. Closes: #691070 * Bump policy to 3.9.3. -- Osamu Aoki os...@debian.org Sun, 21 Oct 2012 22:29:37 +0900 debdiff has been attached. -- Regards, Aron Xu ibus_1.4.1-8.debdiff Description: Binary data
Bug#691698: unblock: dkimpy/0.5.2-1
On Sun, Oct 28, 2012 at 3:01 PM, Scott Kitterman wrote: Please unblock package dkimpy This upload fixes two grave upstream issues (one of which has securtyy implicaitions). unblock dkimpy/0.5.2-1 I think you mean 0.5.3-1? Best wishes, Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANTw=MMyDqf+z6V=Y=ekgefs29sqc9qxxzgutt7xlwzwya3...@mail.gmail.com
Bug#691710: unblock: mdadm/3.2.5-4 (pre-upload)
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock This is a pre-upload unblock request for mdadm/3.2.5-4. Recently, upstream released a new version of mdadm, v3.2.6, which contains only bugfixes or documentation improvements. I'm cherry-picking only the most important changes from this version. These changes fixes a number of important bugs, each of which is not of RC severity, but important enough to be included into wheezy in my point of view. Each of the bug has relatively low impact or probability, or can be seen in only very specific configurations, but once you hit it, it might be difficult to recover the data which was on the raid array in question. This is why I consider these to be good candidates for wheezy. This unblock request consists of two parts. First, the main part, which talks about several bugfixes: Here are the list of changelog entries of this nature: * Fix 'enough' function for RAID10, to prevent starting of a RAID10 array which does not have required minimum of component devices. (Closes: #691668). * fix segfaults in Detail() - mdadm --detail may segfault if a drive has been removed from the array (Closes: #691670) * super0: do not override uuid with homehost. The bug prevented re-creating an array with v0.90 superblock with the specified uuid when homehost is also specified. (Closes: #686703) Each of the above 3 patches fixes specific bugs relevant to data stability, so to say. * several fixes for mdmon argument processing (Closes: #691671): - allow --takeover when original was started with --offroot - fix arg parsing. - fix arg processing for -a The last series - mdmon argument processing fixes - is not directly relevant for version of the package currently in wheezy, since mdmon utility there is not used right now. For this reason, the fixes above are of zero risk for configurations which are directly supported by mdadm debian package infrastructure. However, mdmon is required to support raid arrays with external metadata, which are all the fakeraid arrays (ahci and other in-chipset implementations), found in almost all modern motherboards or PCs. These tiny bugfixes allows usage of such arrays in saner way. More about mdmon is below. While at it, I'm also fixing 2 minor issues with packaging which were slipped in - one debian/changelog typo and an inverse logic in `/etc/init.d/mdadm status' handling (#686100). Debdiff between current version in wheezy (3.2.5-3) and the proposed release attached in file named mdadm_3.2.5-4.debdiff. Whole packaging is done in git, and each change is visible in the git repository on git.debian.org, maybe this one is easier to review: http://anonscm.debian.org/gitweb/?p=pkg-mdadm/mdadm.git;a=shortlog;h=master And second, there's a second part, which talks especially about mdmon and usage of arrays with external metadata. There's one bugreport of RC severity, filed by Miquel van Smoorenburg, who requested a new feature: adding support for raid arrays with external metadata. It is #684708. First, a little explanation. mdadm utility is used to manage raid arrays. For native linux arrays, only 2 components are necessary: mdadm utility to start/stop/etc, and the kernel to handle all the rest. However, for arrays with non-native formats/metadata, metadata updates are handled by external program, kernel sends events affecting metadata to userspace and expects an external program to udpate the metadata using whatever format it is in. This external program is mdmon. Kernel refuses to make the device read-write unless such external prgram is running for the array in question. When mdadm is asked to assemble such a non-native array, it tries to execute mdmon automatically. Once running, it will handle metadata updates from kernel, and the array becomes fully operational. No additional actions are necessary, mdadm does it all internally. If such non-native arrays are assembled from initramfs, mdmon should be in the initramfs too, because else, say, ext4 journal replay (which is done even on a read-only mount) can not be completed, so an uncleanly umounted ext4 can't be mounted. And we need to just provide mdmon binary in initramfs for the whole thing to start working. But we also need 3 extra steps _after_ such an array is started: first, we need to restart mdmon from real root once the system is booted, in order to release initramfs. Second, we need to ensure that these mdmon processes will not be killed by sendsigs during shutdown, because mdmon might still be needed after sendsigs is done - when umounting filesystems etc. And third, we need to wait for such arrays to settle down (to sync metadata etc) at the very end of the shutdown process (mdmon need to finish its task there), or else at next boot the array will not be clean. Miquel provided a patch implementing all this, and I reworked it a bit. In the second
Towards d-i wheezy beta 4
Hi folks, sorry, I hadn't found time yet to let you know about the prospective plans for beta 4. I also haven't found time to read most of the last ~ 200 mails on -boot@ but baring regressions in beta 3 (privext handling for netcfg/NM comes to mind, which got worked around already), I'm tempted to release a beta 4 as soon as src:linux hits testing. If you want to see packages migrate from sid to testing before that, please speak up. I'm tempted to keep everything l10n-ish for release candidates (beta 4 might be the last beta). Release team: please ping me before unblocking packages. Mraw, KiBi. signature.asc Description: Digital signature
