From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [PATCH v2 1/2] build: changing SUSE release file
Date: Wed, 28 May 2025 10:03:37 +0200 [thread overview]
Message-ID: <aDbDWc6dB05icJgO@arm64> (raw)
In-Reply-To: <20250515024817.25717-2-heming.zhao@suse.com>
On Thu, May 15, 2025 at 10:48:14AM +0800, Heming Zhao wrote:
> This commit changes /etc/SuSe-release to /etc/os-release.
> The SuSe-release file disappeared a long time ago.
>
> Signed-off-by: Heming Zhao <heming.zhao@suse.com>
> ---
> configure.ac | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 282fdf1584e3..883fe3e5cdb3 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -402,7 +402,7 @@ else
> if test -z $DISTRO; then
> AC_CHECK_FILE(/etc/redhat-release, [DISTRO="redhat"])
> AC_CHECK_FILE(/etc/debian_version, [DISTRO="debian"])
> - AC_CHECK_FILE(/etc/SuSE-release, [DISTRO="suse"])
> + AC_CHECK_FILE(/etc/os-release, [DISTRO="suse"])
Hi,
everything that has a /etc/os-release (which by now is basically every
distribution on this planet) is suse? No.
This (not only this) part of the automagic in drbd-utils is a mess and
I'm currently in the process of cleaning that up a bit. I will not take
this patch as is, IMO it is just wrong, please just wait, this should
improve in a week or two.
Regards, rck
next prev parent reply other threads:[~2025-05-28 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 2:48 [PATCH v2 0/2] fix drbd-utils minor issues Heming Zhao
2025-05-15 2:48 ` [PATCH v2 1/2] build: changing SUSE release file Heming Zhao
2025-05-28 8:03 ` Roland Kammerer [this message]
2025-05-28 10:08 ` Heming Zhao
2025-05-15 2:48 ` [PATCH v2 2/2] remove lock file after using it Heming Zhao
2025-05-28 8:11 ` Roland Kammerer
2025-05-29 6:59 ` Heming Zhao
2025-05-29 7:55 ` Heming Zhao
2025-05-29 7:57 ` Heming Zhao
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=aDbDWc6dB05icJgO@arm64 \
--to=roland.kammerer@linbit.com \
--cc=drbd-dev@lists.linbit.com \
/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