[arch-commits] Commit in mdadm/repos (5 files)

Mon Jan 10 16:13:33 UTC 2022

Date: Monday, January 10, 2022 @ 16:13:33
  Author: tpowa
Revision: 434144

archrelease: copy trunk to testing-x86_64

Added:
  mdadm/repos/testing-x86_64/
  mdadm/repos/testing-x86_64/PKGBUILD
    (from rev 434143, mdadm/trunk/PKGBUILD)
  mdadm/repos/testing-x86_64/disable-werror.patch
    (from rev 434143, mdadm/trunk/disable-werror.patch)
  mdadm/repos/testing-x86_64/mdadm.conf
    (from rev 434143, mdadm/trunk/mdadm.conf)
  mdadm/repos/testing-x86_64/mdadm_udev_install
    (from rev 434143, mdadm/trunk/mdadm_udev_install)

----------------------+
 PKGBUILD             |   43 +++++++++++++++++++++++++++++++
 disable-werror.patch |   11 ++++++++
 mdadm.conf           |   67 +++++++++++++++++++++++++++++++++++++++++++++++++
 mdadm_udev_install   |   25 ++++++++++++++++++
 4 files changed, 146 insertions(+)

Copied: mdadm/repos/testing-x86_64/PKGBUILD (from rev 434143, mdadm/trunk/PKGBUILD)
===================================================================

--- testing-x86_64/PKGBUILD	                        (rev 0)
+++ testing-x86_64/PKGBUILD	2022-01-10 16:13:33 UTC (rev 434144)
@@ -0,0 +1,43 @@
+# Maintainer: Tobias Powalowski <tpowa at archlinux.org>
+# Contributor: Judd Vinet <jvinet at zeroflux.org>
+
+pkgname=mdadm
+pkgver=4.2
+pkgrel=1
+pkgdesc='A tool for managing/monitoring Linux md device arrays, also known as Software RAID'
+arch=('x86_64')
+license=('GPL')
+url='https://git.kernel.org/pub/scm/utils/mdadm'
+makedepends=('git')
+depends=('glibc' 'systemd')
+replaces=('raidtools')
+backup=('etc/mdadm.conf')
+validpgpkeys=('6A86B80E1D22F21D0B26BA75397D82E0531A9C91') # Jes Sorensen
+source=("git+https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git#tag=${pkgname}-${pkgver}?signed"
+        'disable-werror.patch'
+	'mdadm.conf'
+        'mdadm_udev_install')
+sha256sums=('SKIP'
+            '85c98b8fe880bdd365fc0e400af10c2e5d0c439d338e055f66c16162f9282846'
+            '4ce1e90690282f98e4828e11576fbd61be65e97a2cdae6c7eac7035ea5ee53e5'
+            'b6782029bdae2d7f87ea0e332bb90f72a7792e933580e37602e81e2f1bb82a9c')
+prepare() {
+  cd mdadm
+  patch -Np0 -i ${srcdir}/disable-werror.patch
+}
+
+build() {
+  cd mdadm
+
+  make CXFLAGS="$CFLAGS" BINDIR=/usr/bin UDEVDIR=/usr/lib/udev 
+}
+
+package() {
+  cd mdadm
+
+  make INSTALL=/usr/bin/install BINDIR=/usr/bin DESTDIR="$pkgdir" UDEVDIR=/usr/lib/udev install
+  make SYSTEMD_DIR="$pkgdir"/usr/lib/systemd/system install-systemd
+  install -D -m644 ../mdadm.conf "$pkgdir"/etc/mdadm.conf
+  install -D -m644 ../mdadm_udev_install "$pkgdir"/usr/lib/initcpio/install/mdadm_udev
+  ln -s mdadm_udev "$pkgdir"/usr/lib/initcpio/install/mdadm
+}

Copied: mdadm/repos/testing-x86_64/disable-werror.patch (from rev 434143, mdadm/trunk/disable-werror.patch)
===================================================================
--- testing-x86_64/disable-werror.patch	                        (rev 0)
+++ testing-x86_64/disable-werror.patch	2022-01-10 16:13:33 UTC (rev 434144)
@@ -0,0 +1,11 @@
+--- Makefile.old	2022-01-10 17:07:50.475985407 +0100
++++ Makefile	2022-01-10 17:08:11.599433663 +0100
+@@ -50,7 +50,7 @@
+ CC := $(CROSS_COMPILE)gcc
+ endif
+ CXFLAGS ?= -ggdb
+-CWFLAGS = -Wall -Werror -Wstrict-prototypes -Wextra -Wno-unused-parameter
++CWFLAGS = -Wall -Wstrict-prototypes -Wextra -Wno-unused-parameter
+ ifdef WARN_UNUSED
+ CWFLAGS += -Wp,-D_FORTIFY_SOURCE=2 -O3
+ endif

Copied: mdadm/repos/testing-x86_64/mdadm.conf (from rev 434143, mdadm/trunk/mdadm.conf)
===================================================================
--- testing-x86_64/mdadm.conf	                        (rev 0)
+++ testing-x86_64/mdadm.conf	2022-01-10 16:13:33 UTC (rev 434144)
@@ -0,0 +1,67 @@
+# mdadm configuration file
+#
+# mdadm will function properly without the use of a configuration file,
+# but this file is useful for keeping track of arrays and member disks.
+# In general, a mdadm.conf file is created, and updated, after arrays
+# are created. This is the opposite behavior of /etc/raidtab which is
+# created prior to array construction.
+#
+#
+# the config file takes two types of lines:
+#
+#	DEVICE lines specify a list of devices of where to look for
+#	  potential member disks
+#
+#	ARRAY lines specify information about how to identify arrays so
+#	  so that they can be activated
+#
+
+
+# You can have more than one device line and use wild cards. The first 
+# example includes SCSI the first partition of SCSI disks /dev/sdb,
+# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second 
+# line looks for array slices on IDE disks.
+#
+#DEVICE /dev/sd[bcdjkl]1
+#DEVICE /dev/hda1 /dev/hdb1
+#
+# The designation "partitions" will scan all partitions found in
+# /proc/partitions
+DEVICE partitions
+
+
+# ARRAY lines specify an array to assemble and a method of identification.
+# Arrays can currently be identified by using a UUID, superblock minor number,
+# or a listing of devices.
+#
+#	super-minor is usually the minor number of the metadevice
+#	UUID is the Universally Unique Identifier for the array
+# Each can be obtained using
+#
+# 	mdadm -D <md>
+#
+# To capture the UUIDs for all your RAID arrays to this file, run these:
+#    to get a list of running arrays:
+#    # mdadm -D --scan >>/etc/mdadm.conf
+#    to get a list from superblocks:
+#    # mdadm -E --scan >>/etc/mdadm.conf
+#
+#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
+#ARRAY /dev/md1 super-minor=1
+#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
+#
+# ARRAY lines can also specify a "spare-group" for each array.  mdadm --monitor
+# will then move a spare between arrays in a spare-group if one array has a
+# failed drive but no spare
+#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
+#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
+#
+
+
+# When used in --follow (aka --monitor) mode, mdadm needs a
+# mail address and/or a program.  To start mdadm's monitor mode, enable
+# mdadm.service in systemd.
+#
+# If the lines are not found, mdadm will exit quietly
+#MAILADDR root at mydomain.tld
+#PROGRAM /usr/sbin/handle-mdadm-events

Copied: mdadm/repos/testing-x86_64/mdadm_udev_install (from rev 434143, mdadm/trunk/mdadm_udev_install)
===================================================================
--- testing-x86_64/mdadm_udev_install	                        (rev 0)
+++ testing-x86_64/mdadm_udev_install	2022-01-10 16:13:33 UTC (rev 434144)
@@ -0,0 +1,25 @@
+#!/bin/bash
+
+build() {
+    add_checked_modules -f 'dm-' 'drivers/md/*'
+
+    # check if a custom mdadm.conf exists
+    if grep -qw ^ARRAY "$BASEDIR/etc/mdadm.conf"; then
+        echo "Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays."
+        add_file "/etc/mdadm.conf"
+    fi
+
+    map add_udev_rule \
+        '63-md-raid-arrays.rules' \
+        '64-md-raid-assembly.rules'
+}
+
+help() {
+  cat <<HELPEOF
+This hook loads the necessary modules for a RAID array and uses incremental
+assembly via udev at runtime to create the devices. This hook will NOT work
+without the udev hook included on the image.
+HELPEOF
+}
+
+# vim: set ft=sh ts=4 sw=4 et:

