From debbugs-submit-bounces@debbugs.gnu.org Thu May 06 13:15:37 2021 Received: (at 48214) by debbugs.gnu.org; 6 May 2021 17:15:37 +0000 Received: from localhost ([127.0.0.1]:38644 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lehb7-0005b7-4d for submit@debbugs.gnu.org; Thu, 06 May 2021 13:15:37 -0400 Received: from knopi.disroot.org ([178.21.23.139]:33274) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lehb4-0005b1-Kz for 48214@debbugs.gnu.org; Thu, 06 May 2021 13:15:35 -0400 Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 86AEB53032; Thu, 6 May 2021 19:15:33 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from knopi.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6sxNlGkLhjho; Thu, 6 May 2021 19:15:32 +0200 (CEST) References: <87a6pbjlao.fsf@disroot.org> <871ramoogd.fsf@nckx> <87eeekiq76.fsf@disroot.org> <87zgx7hpy0.fsf@disroot.org> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1620321331; bh=MmDrULs4mQ9s1cdkaliyK4KGpRAA2QP+EU/An9/61No=; h=References:From:To:Cc:Subject:In-reply-to:Date; b=a31WmnRyc0ZfRko7m0FB1QSuwb2MHidjYoRupJHpAh70bFEwChHlp7+mI3Jwv1VOo ivG2tqoC+EgaBwLPSdxm40q8yIuvcIhBsXhoEOZ/IyYKaBd8QIdBACRSyALHE5y5qI lnUZjLDkbi9/blU1JQevnf4eiuh79Ze18VtZcLFz/s78YL7J8oCx5gfoq3yiXeuL5l mYDSt8EPazBCBRB0Izre746UUkbf0o+eMi4t835WBRAf9z6SjnsbAhHM4pie26ffPF 7F16ibF7qIGN50Krdv6+sYBu1pm1VpDBRITtKmoCyOh3ys2rbJqjUX2egtztMNS9Vo kyqA29Qmtli8Q== From: Bone Baboon To: Bone Baboon Subject: Re: bug#48214: inetutils-1.9.4 build fails In-reply-to: <87zgx7hpy0.fsf@disroot.org> Date: Thu, 06 May 2021 13:14:13 -0400 Message-ID: <87tunfhjiy.fsf@disroot.org> Mime-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 48214 Cc: 48214@debbugs.gnu.org, Tobias Geerinckx-Rice , bug-guix@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) > Bone Baboon via Bug reports for GNU Guix writes: >> I have reported this to the inetutils bug mailing list and asked if the >> inetutils test suite could be modified so that syslogd.sh does not fail >> if IPv6 is disabled. > > I received this response on the inetutils mailing list: > >> Hi. Thanks for the report. Could you investigate if the >> tests/runtime-ipv6.c program return appropriately? It is supposed to >> check wether the runtime system supports IPv6 or not, and should detect >> this properly on your system (or there is a bug in the self-test code >> elsewhere). >> >> Looking at the code, I don't think a getaddrinfo-lookup is sufficient, >> the code probably need to attempt to listen to a socket too, in order to >> fully test wether IPv6 is disabled globally or not. > > I looked for tests/runtime-ipv6.c in the inetutils's build tree. I > could not find it. I looked up the current version of inetutils which > is 2.0. Guix has 1.9.4 of inetutils packaged. > > Based on the response I received on the inetutils mailing list it sounds > like updating the inetutils package to 2.0 may resolve this failing > test. On the inetutils mailing list it was suggested that I try inetutils 2.0 on the core-updates branch. I can successfully build inetutils 2.0 from the core-updates branch even with IPv6 disabled. What is the purpose of the core-updates branch? If inetutils follows semantic version numbering then that would suggest a breaking change to the inetutils API moving from 1.9.4 to 2.0. Can the Guix master branch provide inetutils 2.0 instead of 1.9.4? How can I use a package definition from core-updates with guix build or in a system configuration if it is not available on Guix's master branch? What are the reasons I might not want to use a package from the core-updates branch?