From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13846] New: BR2_PACKAGE_LVM2_STANDARD_INSTALL should be default to y as before
Date: Tue, 15 Jun 2021 06:32:21 +0000 [thread overview]
Message-ID: <bug-13846-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13846
Bug ID: 13846
Summary: BR2_PACKAGE_LVM2_STANDARD_INSTALL should be default to
y as before
Product: buildroot
Version: 2021.02.3
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: dominique.tronche at atos.net
CC: buildroot at uclibc.org
Target Milestone: ---
With commit 3cdbe916, the default value of package
BR2_PACKAGE_LVM2_STANDARD_INSTALL has been changed.
I'm not sure this was the wanted behavior.
Indeed in the commit the package was introduced (ff0f55e3), it was written "the
new option defaults to y *UNLESS* the legacy BR2_PACKAGE_LVM2_DMSETUP_ONLY was
selected"
Now that the legacy package is obsolete, the default shall be y in all cases.
I think most people requires the standard installation of lvm2, otherwise it
would not really be standard.
I have set the severity to major as this change has broken our installation
since the lvm2 binaries were not compiled anymore and all scripts that required
lvm manipulation failed
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-06-15 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 6:32 bugzilla at busybox.net [this message]
2021-06-16 19:09 ` [Buildroot] [Bug 13846] BR2_PACKAGE_LVM2_STANDARD_INSTALL should be default to y as before bugzilla at busybox.net
2021-06-17 5:20 ` bugzilla at busybox.net
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=bug-13846-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.