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=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS autolearn=ham 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) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id ABDC31F508 for ; Fri, 31 Jan 2025 09:55:00 +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=GazOpR8c; 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=WTcR5sKl; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1738317268; bh=XzwvrjSH0eu7cffdnat/6iUFH4ylDe2tp1d1wQ6WGFA=; 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=GazOpR8cZcWxXbwKnf3Z7T9W3VyRLh8+MmfZk2wIku5P0SQkRKqo7Uo6OX1VDUien KKBxzPADVtD/PXxoDXM1rV+OJ9RM//ZwQ5wNei2csYKmGXtzkiIuqCjogcyftx6p71 zl/Dmrfpu95PSZhb2pL4DGrXrG+XMYg3hHbeDxiA= Received: from nue.mailmanlists.eu (localhost [IPv6:::1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 2ADE7469E0 for ; Fri, 31 Jan 2025 09:54:28 +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=WTcR5sKl; dkim-atps=neutral Received: from s.wfbtzhsv.outbound-mail.sendgrid.net (s.wfbtzhsv.outbound-mail.sendgrid.net [159.183.224.104]) by nue.mailmanlists.eu (Postfix) with ESMTPS id 5173F468B4 for ; Fri, 31 Jan 2025 09:54:23 +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=JLUtXtDpXpxSpQdWam4cKY1hA9/+yjs/mnsf7nTh4nc=; b=WTcR5sKl69/MM235354t0xnaWrmTapx0VQrSvIHYCSVFYcUn/lrqi9SCle6gIXYbBkpd +NJPylb285Fw9iFM3FyO+Vw4KRBUjOJv+oljQTwvd3ELR9xOWYeD6iUdf7HXMCQPyYhDKA CMlIR/vU9PXMy7y4UH38EUnt0+53DPvvge494z43FIMIbWYlebbBBwAnxTpWkB5SjjQ6lS LTG7GPFPNBG7DwZaxUkQ4g+2pGRE/NSaqorloJCVvK0jQwanfCJfq/RfPd+L99M40MEjU4 C95MqDiVcGhn4b+HFsQDg4yuua8d7JNYczU50jWg55CF0tb1jEMTobBfRaMuKXLw== Received: by recvd-5c8ccdbd88-mbfdl with SMTP id recvd-5c8ccdbd88-mbfdl-1-679C9DCE-12 2025-01-31 09:54:22.50277622 +0000 UTC m=+6697903.570181852 Received: from herokuapp.com (unknown) by geopod-ismtpd-3 (SG) with ESMTP id kTDDGBh4SDK9HTSFZsdhHw for ; Fri, 31 Jan 2025 09:54:22.452 +0000 (UTC) Date: Fri, 31 Jan 2025 09:54:22 +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: Eregon 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: 97565 X-SG-EID: =?us-ascii?Q?u001=2EByjZWvxTCjdoV8K03xEuhE7KqN4thWULFLM7+oH78KY30oYB3qFthsDpL?= =?us-ascii?Q?4w4cbYa3ttBh8bAHPOnE=2FkzPba67JNu7Lnrked2?= =?us-ascii?Q?O7K9VQ=2FJax2Aba6qdVmhrZqr3be8reR01js6Cdg?= =?us-ascii?Q?q1IZBoRE9UHwk+RgjTDygjd0iKprAKSiHr2ggdi?= =?us-ascii?Q?HkUR7WS7b7Xy09OSrAuWTyY7Dl79jptkcyoweeF?= =?us-ascii?Q?qqJUpvS5O8O3OlqwooVy9F1FD6y8tIjCpiJTlFg?= =?us-ascii?Q?8nwBSFNNI9CYWE8G=2FpEoPHHMBQ=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: u001.I8uzylDtAfgbeCOeLBYDww== Message-ID-Hash: RUZPESXJ5ZPGMNKVKXODYF3IUK3LKJ5H X-Message-ID-Hash: RUZPESXJ5ZPGMNKVKXODYF3IUK3LKJ5H 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:120849] [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: "Eregon (Benoit Daloze) via ruby-core" Cc: "Eregon (Benoit Daloze)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #21095 has been updated by Eregon (Benoit Daloze). @ioquatix There are several problems with what happened here, so I'll list them in the hope this does not repeat in the future: * The rationale for this change is not well explained (e.g. why is it a problem for Arch to have `inettools`/"another hostname impl" as a test dependency of the Ruby package?). It's not OK to ask people to read various issues on some other bug tracker (takes a lot of time), the rationale should be expressed directly in the PR or issue description, clearly. * You merged 2 PRs without waiting for review, and there were issues with both PRs. Reviewing after it's merged is a lot more time-demanding and frustrating (for both sides). * Instead, you wrote on the CRuby Slack #general channel for this (IMO too small matter to spam general for this), but the PR was already merged when I could see it. Having the split discussion in 3 places is also wasting more time. Instead, ask one or a few reviewers to review the PR, and wait for one review. * The PR should ideally be to https://github.com/ruby/spec directly, then it would be clear you need a ruby/spec maintainer review. * It would be best if the Arch maintainer would make the PR or issue themselves, they know the rationale best and then if there is any question they can easily be asked. You are playing messenger here and that's slowing things down and losing information. * I know you are well intentioned and are trying to help Arch maintainers here, but the net result is frustration at least on my side, lots of time wasted, a brittle/broken spec and still no clear reason for this extra complexity. Hopefully those concerns will be solved on https://github.com/ruby/ruby/pull/12655 and the next PR, if not I will revert both PRs and then it can be done the proper way from the start, which should be better for everyone involved. ---------------------------------------- Bug #21095: Prefer `uname -n` over `hostname` in tests. https://bugs.ruby-lang.org/issues/21095#change-111725 * 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/