- New upstream release 3.0.3 (bz523320, bz527281)
- Update a couple internal patches - Drop a patch in that was in Neil's tree for 3.0.3 that we had pulled for immediate use to resolve a bug - Drop the endian patch because it no longer applied cleanly and all attempts to reproduce the original problem as reported in bz510605 failed, even up to and including downloading the specific package that was reported as failing in that bug and trying to reproduce with it on both ppc and ppc64 hardware and with both ppc and ppc64 versions on the 64bit hardware. Without a reproducer, it is impossible to determine if a rehashed patch to apply to this code would actually solve the problem, so remove the patch entirely since the original problem, as reported, was an easy to detect DOA issue where installing to a raid array was bound to fail on reboot and so we should be able to quickly and definitively tell if the problem resurfaces. - Update the mdmonitor init script for LSB compliance (bz527957) - Link from mdadm.static man page to mdadm man page (bz529314) - Fix a problem in the raid-check script (bz523000) - Fix the intel superblock handler so we can test on non-scsi block devices
This commit is contained in:
parent
fa5ca2339d
commit
bf7f590ca9
43
mdadm.spec
43
mdadm.spec
@ -1,6 +1,6 @@
|
||||
Summary: The mdadm program controls Linux md devices (software RAID arrays)
|
||||
Name: mdadm
|
||||
Version: 3.0.2
|
||||
Version: 3.0.3
|
||||
Release: 1%{?dist}
|
||||
Source: http://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-%{version}.tar.bz2
|
||||
Source1: mdmonitor.init
|
||||
@ -8,11 +8,10 @@ Source2: raid-check
|
||||
Source3: mdadm.rules
|
||||
Source4: mdadm-raid-check-sysconfig
|
||||
Patch1: mdadm-2.5.2-static.patch
|
||||
Patch2: mdadm-3.0-endian-FAIL.patch
|
||||
Patch3: mdadm-3.0-metadata.patch
|
||||
Patch4: mdadm-3.0-uuid.patch
|
||||
Patch5: mdadm-3.0-mdmon-dev-.mdadm.patch
|
||||
Patch6: mdadm-3.0-rh526761.patch
|
||||
Patch2: mdadm-3.0-metadata.patch
|
||||
Patch3: mdadm-3.0-uuid.patch
|
||||
Patch4: mdadm-3.0-mdmon-dev-.mdadm.patch
|
||||
Patch5: mdadm-3.0.3-intel-serial.patch
|
||||
URL: http://www.kernel.org/pub/linux/utils/raid/mdadm/
|
||||
License: GPLv2+
|
||||
Group: System Environment/Base
|
||||
@ -22,7 +21,7 @@ Requires(post): /sbin/service, /sbin/chkconfig
|
||||
Requires(preun): /sbin/service, /sbin/chkconfig
|
||||
Requires(postun): /sbin/service
|
||||
Requires: udev
|
||||
BuildRequires: glibc-static
|
||||
#BuildRequires: glibc-static
|
||||
|
||||
%description
|
||||
The mdadm program is used to create, manage, and monitor Linux MD (software
|
||||
@ -34,11 +33,10 @@ file can be used to help with some common tasks.
|
||||
%prep
|
||||
%setup -q
|
||||
%patch1 -p1 -b .static
|
||||
%patch2 -p1 -b .endian
|
||||
%patch3 -p1 -b .metadata
|
||||
%patch4 -p1 -b .uuid
|
||||
%patch5 -p1 -b .mdmon
|
||||
%patch6 -p1 -b .rh526761
|
||||
%patch2 -p1 -b .metadata
|
||||
%patch3 -p1 -b .uuid
|
||||
%patch4 -p1 -b .mdmon
|
||||
%patch5 -p1 -b .serial
|
||||
|
||||
%build
|
||||
make %{?_smp_mflags} CXFLAGS="$RPM_OPT_FLAGS -fno-strict-aliasing" SYSCONFDIR="%{_sysconfdir}" mdadm.static mdadm mdmon
|
||||
@ -52,6 +50,7 @@ install -Dp -m 755 %{SOURCE2} %{buildroot}%{_sysconfdir}/cron.weekly/99-raid-che
|
||||
install -Dp -m 644 %{SOURCE3} %{buildroot}/lib/udev/rules.d/65-md-incremental.rules
|
||||
install -Dp -m 644 %{SOURCE4} %{buildroot}%{_sysconfdir}/sysconfig/raid-check
|
||||
mkdir -p -m 700 %{buildroot}/var/run/mdadm
|
||||
ln -s mdadm.8.gz %{buildroot}%{_mandir}/man8/mdadm.static.8.gz
|
||||
|
||||
%clean
|
||||
rm -rf %{buildroot}
|
||||
@ -84,6 +83,26 @@ fi
|
||||
%attr(0700,root,root) %dir /var/run/mdadm
|
||||
|
||||
%changelog
|
||||
* Wed Nov 04 2009 Doug Ledford <dledford@redhat.com> - 3.0.3-1
|
||||
- New upstream release 3.0.3 (bz523320, bz527281)
|
||||
- Update a couple internal patches
|
||||
- Drop a patch in that was in Neil's tree for 3.0.3 that we had pulled for
|
||||
immediate use to resolve a bug
|
||||
- Drop the endian patch because it no longer applied cleanly and all attempts
|
||||
to reproduce the original problem as reported in bz510605 failed, even up
|
||||
to and including downloading the specific package that was reported as
|
||||
failing in that bug and trying to reproduce with it on both ppc and ppc64
|
||||
hardware and with both ppc and ppc64 versions on the 64bit hardware.
|
||||
Without a reproducer, it is impossible to determine if a rehashed patch
|
||||
to apply to this code would actually solve the problem, so remove the patch
|
||||
entirely since the original problem, as reported, was an easy to detect DOA
|
||||
issue where installing to a raid array was bound to fail on reboot and so
|
||||
we should be able to quickly and definitively tell if the problem resurfaces.
|
||||
- Update the mdmonitor init script for LSB compliance (bz527957)
|
||||
- Link from mdadm.static man page to mdadm man page (bz529314)
|
||||
- Fix a problem in the raid-check script (bz523000)
|
||||
- Fix the intel superblock handler so we can test on non-scsi block devices
|
||||
|
||||
* Fri Oct 2 2009 Hans de Goede <hdegoede@redhat.com> - 3.0.2-1
|
||||
- New upstream release 3.0.2
|
||||
- Add a patch fixing mdadm --detail -export segfaults (bz526761, bz523862)
|
||||
|
Loading…
Reference in New Issue
Block a user