From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on starla X-Spam-Level: X-Spam-Status: No, score=0.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_BL_SPAMCOP_NET,SPF_HELO_PASS, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 Received: from nue.mailmanlists.eu (nue.mailmanlists.eu [94.130.110.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id D86CA1F508 for ; Tue, 28 Jan 2025 22:12:52 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=ml.ruby-lang.org header.i=@ml.ruby-lang.org header.a=rsa-sha256 header.s=mail header.b=oK4DhnpV; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=k7olnjpC; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1738102369; bh=ECLFC+LO4kn9BngQGaR70z6/biMCL9k2Epm05pvMHHs=; h=Date:References:To:Reply-To:Subject:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From:Cc:From; b=oK4DhnpVYC0dDLTCaLvtJ8hHVAY7QpZCkTHYgEzwSkNUP+oi/IFXgQf1WbfiNWc9j ff0nuOnypLtuGIk51ujnatW4FNDXbTN2lVQH22ThKcZh0Ed6IFUBWkBvIt8R0fBPFv VONIEtVQWAxqeJ+XcABk2Y2YW/gLbyviIboFqbUQ= Received: from nue.mailmanlists.eu (localhost [IPv6:::1]) by nue.mailmanlists.eu (Postfix) with ESMTP id DC85A468A2 for ; Tue, 28 Jan 2025 22:12:49 +0000 (UTC) Authentication-Results: nue.mailmanlists.eu; dkim=pass (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=k7olnjpC; dkim-atps=neutral Received: from s.wrqvtzvf.outbound-mail.sendgrid.net (s.wrqvtzvf.outbound-mail.sendgrid.net [149.72.126.143]) by nue.mailmanlists.eu (Postfix) with ESMTPS id 1189A4689A for ; Tue, 28 Jan 2025 22:12:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ruby-lang.org; h=from:references:subject:mime-version:content-type: content-transfer-encoding:list-id:to:cc:content-type:from:subject:to; s=s1; bh=f9ZUMiguEanjFht8eZS2uzL75Ca1UwK2NNJHpDzFrWA=; b=k7olnjpCqQz2LV1GUVN/GUv1l6aFouLpnvGdOM6/Yoh9EFn49wxy/DZxAExJ7S0SOa6J 861UmuWtG2jVkoZdNdZb9KmFhsaCMDEeqDZQZelBzHqxcV1dtbsRmh6LApFsyPFu08BipI 0ou1a8L5gIsu6hf5OBOYPh4pvDcYwzyyyNlasb8ZnLTXweeo9zKj8SOjD3P5s+kXMOFcCR /Fckdx2LUzAxEj9ZnVEtl95V0ipW81WXRnwLhXbwYwxEH2EsODld5DC5H4BSkPfVbCznZk S6FCB5lALZ69+aNV22S+rG24zpdxOQKtvflLiLkEKgc9cCf3Zrth2H9OS5QlESrA== Received: by recvd-786d47b7ff-m4pj6 with SMTP id recvd-786d47b7ff-m4pj6-1-6799565C-1 2025-01-28 22:12:44.034996247 +0000 UTC m=+6482929.166799230 Received: from herokuapp.com (unknown) by geopod-ismtpd-28 (SG) with ESMTP id nO7FVvvsRLSXkxnp0lPZag for ; Tue, 28 Jan 2025 22:12:43.930 +0000 (UTC) Date: Tue, 28 Jan 2025 22:12:44 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Bug X-Redmine-Issue-Id: 21095 X-Redmine-Issue-Author: ioquatix X-Redmine-Issue-Priority: Normal X-Redmine-Sender: ioquatix X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-Redmine-MailingListIntegration-Message-Ids: 97532 X-SG-EID: =?us-ascii?Q?u001=2E3QFJPY5gaRwyNXkncYONHM3OeFnb=2FgeOrLDgg3PYIKrq5rvk81iAipQ1q?= =?us-ascii?Q?cdmuT9o5PIWGjXtTDstodNmslT=2F6xfCuIofWR2K?= =?us-ascii?Q?w8msDgVaVLydulBokB7oqUVys9LSriCwnC8Iavc?= =?us-ascii?Q?UpVNeDhqgHwPiNx22FGUC3683wfbv0nt=2F1XLlsF?= =?us-ascii?Q?VBI8S90+IYlWfNj0VMjybKWHPBRNAXtvHgiYdm8?= =?us-ascii?Q?d9Qa6kyzDdziwE7pj8JJBYaO3yHLd4AahzTW5Cb?= =?us-ascii?Q?gW10UWeCsaV8ckZQXJ3pGY6HXA=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: u001.I8uzylDtAfgbeCOeLBYDww== Message-ID-Hash: EWODDE3KF2RLZL247WHVQOIU6NUDZRPA X-Message-ID-Hash: EWODDE3KF2RLZL247WHVQOIU6NUDZRPA X-MailFrom: bounces+313651-b711-ruby-core=ml.ruby-lang.org@em5188.ruby-lang.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9 Precedence: list Reply-To: Ruby developers Subject: [ruby-core:120814] [Ruby master Bug#21095] Prefer `uname -n` over `hostname` in tests. List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: "ioquatix (Samuel Williams) via ruby-core" Cc: "ioquatix (Samuel Williams)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #21095 has been updated by ioquatix (Samuel Williams). Ruby should prefer (POSIX) standardised tools and interfaces where possible. This change costs us nothing and reduces downstream friction. it's win-win for everyone, including other distributions which have to maintain their own package for `hostname` - did you read the background context and linked issues? ---------------------------------------- Bug #21095: Prefer `uname -n` over `hostname` in tests. https://bugs.ruby-lang.org/issues/21095#change-111683 * Author: ioquatix (Samuel Williams) * Status: Closed * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: REQUIRED, 3.4: REQUIRED ---------------------------------------- It turns out that `hostname`, while a defacto standard, is not actually a standard in any official sense. On Linux, it's distributed as part of the `inettools` package, and while generally available on other platforms (BSD, Windows, MacOS), it isn't actually part of any standard. The `uname(1)` system call and `uname(2)` command ARE standardised by POSIX and the Open Group, and are included in most base systems without the need to install extra packages (e.g. `inettools` on Linux). As such, I was requested by the Arch Linux Ruby maintainer, to prefer using `uname -n` as they would like to drop the dependency on `inettools` which has various issues; see for more context and background. I've been asked if this can be back ported to 3.3 and 3.4 and while it's not strictly a bug, it will reduce friction in the distribution channels, so I'd like to propose that we backport to 3.4 and if possible 3.3 too. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/