public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve McIntyre <steve@einval.com>
To: Nathan Scott <nathans@debian.org>
Cc: 804255@bugs.debian.org
Subject: Bug#804255: Please update initramfs in postinst
Date: Tue, 10 Nov 2015 16:41:15 +0000	[thread overview]
Message-ID: <20151110164115.GG13015@einval.com> (raw)
In-Reply-To: <1822095565.6959319.1447027220334.JavaMail.zimbra@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

Control: tag -1 +patch

On Sun, Nov 08, 2015 at 07:00:20PM -0500, Nathan Scott wrote:
>Hi Steve,
>
>----- Original Message -----
>> Package: xfsprogs
>> Version: 3.2.1
>> Severity: important
>> Tags: d-i
>> 
>> To make this work well, all filesystem tools packages for filesystems
>> that are likely to be used for / and/or /usr should call
>> "update-initramfs -u" in their postinst. This will
>
>OK.
>
>> I've checked your package and I don't see any update-initramfs
>> calls.
>
>(yep, xfsprogs has no postinst at all IIRC)
>
>> Please add one. If you'd like help doing that postinst work, I
>> can supply a patch - just ask!
>
>That would be great, if you don't mind Steve?  Many thanks!

Here's a debdiff of what I've just built. Ignore the NMU version in
the changelog...

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
The two hard things in computing:
 * naming things
 * cache invalidation
 * off-by-one errors                  -- Stig Sandbeck Mathisen

[-- Attachment #2: xfsprogs_4.2.0.1.debdiff --]
[-- Type: text/plain, Size: 1114 bytes --]

diff -Nru xfsprogs-4.2.0/debian/changelog xfsprogs-4.2.0.1/debian/changelog
--- xfsprogs-4.2.0/debian/changelog	2015-09-11 01:51:36.000000000 +0000
+++ xfsprogs-4.2.0.1/debian/changelog	2015-11-10 16:35:45.000000000 +0000
@@ -1,3 +1,11 @@
+xfsprogs (4.2.0.1) unstable; urgency=low
+
+  * NMU
+  * * Add a postinst to update the initramfs on install/upgrade.
+    (Closes: #804255)
+
+ -- Steve McIntyre <93sam@debian.org>  Tue, 10 Nov 2015 16:33:59 +0000
+
 xfsprogs (4.2.0) unstable; urgency=low
 
   * New upstream release
diff -Nru xfsprogs-4.2.0/debian/postinst xfsprogs-4.2.0.1/debian/postinst
--- xfsprogs-4.2.0/debian/postinst	1970-01-01 00:00:00.000000000 +0000
+++ xfsprogs-4.2.0.1/debian/postinst	2015-11-10 16:35:20.000000000 +0000
@@ -0,0 +1,25 @@
+#!/bin/sh
+
+set -e
+
+case "${1}" in
+	configure)
+		if [ -x /usr/sbin/update-initramfs ] && [ -e /etc/initramfs-tools/initramfs.conf ]
+		then
+			update-initramfs -u
+		fi
+		;;
+
+	abort-upgrade|abort-remove|abort-deconfigure)
+
+		;;
+
+	*)
+		echo "postinst called with unknown argument \`${1}'" >&2
+		exit 1
+		;;
+esac
+
+#DEBHELPER#
+
+exit 0

[-- Attachment #3: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-11-10 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 16:19 Bug#804255: Please update initramfs in postinst Steve McIntyre
2015-11-09  0:00 ` Nathan Scott
2015-11-10 16:41   ` Steve McIntyre [this message]
2015-11-10 21:50     ` Nathan Scott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151110164115.GG13015@einval.com \
    --to=steve@einval.com \
    --cc=804255@bugs.debian.org \
    --cc=nathans@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox