This bug was fixed in the package update-notifier - 0.154
---
update-notifier (0.154) trusty; urgency=medium
* Do not say that a partition will be checked when the check is disabled in
fstab. Thanks to Nils Kassube for the patch. (LP: #1282760)
* Use print function instead o
** Changed in: update-notifier (Ubuntu)
Status: Incomplete => In Progress
** Changed in: update-notifier (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Branch linked: lp:update-notifier
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282760
Title:
update-motd-fsck-at-reboot claims that partitions will be checked even
if check is disabled in fst
Ah, I see what I missed now. Thanks for the clarification, I'll get
your change added shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282760
Title:
update-motd-fsck-at-reboot claims that pa
Thanks for the review. With the cut command I want to select the mount
point and not the device. The device is known inside the loop from
"$part" but there are several ways to name the device in /etc/fstab
(device, UUID, label). It is unknown which version is used for the
partition in question. On
Thanks for you work on this patch but, I think the cut command is
incorrect "cut -s -f 2,6", I believe you want "cut -s -f 1,6". I say
this as ext_partitions is the following on my system:
$ mount | awk '$5 ~ /^ext(2|3|4)$/ { print $1 }'
/dev/mapper/ubuntu--vg-root
/dev/mapper/virtual--vg-sec--m
** Changed in: update-notifier (Ubuntu)
Importance: Undecided => Medium
** Changed in: update-notifier (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282760
The attachment "This patch disables the faulty message" seems to be a
patch. If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad use
And here is an alternative patch
** Attachment added: "This patch changes the message"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1282760/+attachment/3988730/+files/patch2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
