This bug was fixed in the package mdadm - 3.2.5-1ubuntu1
---------------
mdadm (3.2.5-1ubuntu1) quantal; urgency=low
* Merge from Debian testing. (LP: #920324) Remaining changes:
- Call checks in local-premount to avoid race condition with udev
and opening a degraded array.
- d/initramfs/mdadm-functions: Record in /run when boot-degraded
question has been asked so that it is only asked once
- pass --test to mdadm to enable result codes for degraded arrays.
- debian/control: we need udev and util-linux in the right version. We
also remove the build dependency from quilt and docbook-to-man as both
are not used in Ubuntus mdadm.
- debian/initramfs/hook: kept the Ubuntus version for handling the absence
of active raid arrays in <initramfs>/etc/mdadm/mdadm.conf
- debian/initramfs/script.local-top.DEBIAN, debian/mdadm-startall,
debian/mdadm.raid.DEBIAN: removed. udev does its job now instead.
- debian/mdadm-startall.sgml, debian/mdadm-startall.8: documentation of
unused startall script
- debian/mdadm.config, debian/mdadm.postinst - let udev do the handling
instead. Resolved merge conflict by keeping Ubuntu's version.
- debian/mdadm.postinst, debian/mdadm.config, initramfs/init-premount:
boot-degraded enablement; maintain udev starting of RAID devices;
init-premount hook script for the initramfs, to provide information at
boot
- debian/mkconf.in is the older mkconf. Kept the Ubuntu version.
- debian/rules: Kept Ubuntus version for installing apport hooks, not
installing un-used startall script.
- debian/install-rc, check.d/_numbers, check.d/root_on_raid: Ubuntu partman
installer changes
- debian/presubj: Dropped this unused bug reporting file. Instead use
source_mdadm.py act as an apport hook for bug handling.
- d/p/debian-changes-3.1.4-1+8efb9d1ubuntu4: mdadm udev rule
incrementally adds mdadm member when detected. Starting such an
array in degraded mode is possible by mdadm -IRs. Using mdadm
-ARs without stopping the array first does nothing when no
mdarray-unassociated device is available. Using mdadm -IRs to
start a previously partially assembled array through incremental
mode. Keeping the mdadm -ARs for assembling arrays which were for
some reason not assembled through incremental mode (i.e through
mdadm's udev rule).
* Additional Ubuntu changes:
- debian/initramfs/local-premount: add call wait_for_udev to wait a
little longer for RAID devices to appear (LP: #942106)
* Dropped Ubuntu changes:
- Build udeb with -O2 on ppc64, working around a link error. Builds
fine without it on debian.
- rename debian/mdadm.vol_id.udev to debian/mdadm.mdadm-blkid.udev so
that the rules file ends up with a more reasonable name. debian/rules
changes for adding ubuntu's udev rule corresponding to mdadm. As we
are now using 'upstream' udev rules see 3.2.3-2ubuntu2.
* Changes to Ubuntu changes:
- debian/source_mdadm.py: make apport hook python 2 and 3 compatible
(LP: #1013171).
* New upstream release closes this bugs:
- mdadm --detail --scan segfaults during update-initramfs (LP: #969384)
-- Dmitrijs Ledkovs <dmitrij.led...@ubuntu.com> Fri, 15 Jun 2012 15:31:59
+0100
** Changed in: mdadm (Ubuntu Quantal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1013171
Title:
Many package hooks not ported to python3
Status in “apport” package in Ubuntu:
Fix Released
Status in “apport-symptoms” package in Ubuntu:
Fix Released
Status in “bluez” package in Ubuntu:
Fix Released
Status in “dkms” package in Ubuntu:
Fix Released
Status in “firefox” package in Ubuntu:
Fix Committed
Status in “gnome-screensaver” package in Ubuntu:
Fix Released
Status in “libatasmart” package in Ubuntu:
Fix Released
Status in “mdadm” package in Ubuntu:
Fix Released
Status in “network-manager” package in Ubuntu:
Fix Committed
Status in “notify-osd” package in Ubuntu:
Fix Released
Status in “shadow” package in Ubuntu:
Fix Released
Status in “thunderbird” package in Ubuntu:
Fix Committed
Status in “udisks2” package in Ubuntu:
Fix Released
Status in “xdiagnose” package in Ubuntu:
Fix Released
Status in “apport” source package in Quantal:
Fix Released
Status in “apport-symptoms” source package in Quantal:
Fix Released
Status in “bluez” source package in Quantal:
Fix Released
Status in “dkms” source package in Quantal:
Fix Released
Status in “firefox” source package in Quantal:
Fix Committed
Status in “gnome-screensaver” source package in Quantal:
Fix Released
Status in “libatasmart” source package in Quantal:
Fix Released
Status in “mdadm” source package in Quantal:
Fix Released
Status in “network-manager” source package in Quantal:
Fix Committed
Status in “notify-osd” source package in Quantal:
Fix Released
Status in “shadow” source package in Quantal:
Fix Released
Status in “thunderbird” source package in Quantal:
Fix Committed
Status in “udisks2” source package in Quantal:
Fix Released
Status in “xdiagnose” source package in Quantal:
Fix Released
Bug description:
While trying to upgrade from 12.04 to Quantal I received an error of:
Could not install python3:
subprocess installed post-installation script returned error exit
status 4
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: python3 3.2.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.2.2-0ubuntu2
Architecture: amd64
Date: Thu Jun 14 09:13:21 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: python3-defaults
UpgradeStatus: Upgraded to quantal on 2012-06-14 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1013171/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
