From nobody Sun Jan 5 10:43:15 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YQv6b677pz5hycr for ; Sun, 05 Jan 2025 10:43:19 +0000 (UTC) (envelope-from SRS0=ywL3=T5=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YQv6Z6d9Sz4Y42 for ; Sun, 5 Jan 2025 10:43:18 +0000 (UTC) (envelope-from SRS0=ywL3=T5=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Sun, 5 Jan 2025 11:43:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1736073796; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Fsg2U1GQFjFxn/CaiHxxuC7zghLZUbssGLRyMq1Vyz0=; b=rebl9jY4b/OC/s6qOsmU6rqEBYWOyeEpFVAT3KfbBzYi1xK8bJjPlz83bjB1zZQnkQc0Ny NFE4eYaYa/Dc+RBOhCEI1PrF4S/89dzf0YzEd6HljkVjZD8Y9blGCrJg5983A/Ds+rSiK+ zNa4MmMP/9quzLp0joqUUSG1PEFvPd5P0LbVwMS93lbIRaho7jqfqfHv61JuCtyHZDGv7c 3ihKuXJcLbv7YBQ0llneZCsvjZtQLGsi5TFy9HJmVvPD0Rf/6heMmF1HMbO0TYUjcfXMyu 4OrqH7Ih0xzRH5hwBSz3lB2/+QBxO5zxnQg1HL36QNKOmGhYfAqwdGLAFtAIwQ== From: Ronald Klop To: Dennis Clarke Cc: Current FreeBSD Message-ID: <1645708192.12009.1736073795989@localhost> In-Reply-To: <36c212cc-0da9-43b7-b760-d29d71bc35e5@blastwave.org> References: <36c212cc-0da9-43b7-b760-d29d71bc35e5@blastwave.org> Subject: Re: Is there any way to nudge security/libfido2? It blocks chunks of KDE List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_12008_193046442.1736073795943" X-Mailer: Realworks (732.110) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4YQv6Z6d9Sz4Y42 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] ------=_Part_12008_193046442.1736073795943 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Dennis Clarke Datum: zondag, 5 januari 2025 06:45 Aan: Current FreeBSD Onderwerp: Is there any way to nudge security/libfido2? It blocks chunks of KDE > > It seems to have been a while since I was able to run a poudriere bulk build and get KDE available. At least on 15-CURRENT. There is a > little brick in the path called security/libfido2 : > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283697 > > commit 74ecdf86d8d2a94a4bfcf094a2e21b4747e4907f resulted in the > appropriate declarations for the correct versions of _POSIX_C_SOURCE > via __POSIX_VISIBLE and then we get > > error: call to undeclared function 'ppoll'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration] > > > Sort of annoying as even 14.2-RELEASE on amd64 and ports 2024Q4 fails : > > [142amd64-2024Q4] [2025-01-04_10h11m35s] [committing] Queued: 5 Built: 4 Failed: 1 Skipped: 0 Ignored: 0 Fetched: 0 Tobuild: 0 Time: 00:04:44 > > The 15.0-CURRENT is much much worse : > > [150amd64-latest] [2025-01-04_08h12m11s] [committing] Queued: 365 Built: 323 Failed: 2 Skipped: 40 Ignored: 0 Fetched: 0 Tobuild: 0 Time: 01:52:01 > > > In any case ... is there a way to nudge that ? > > -- > -- > Dennis Clarke > RISC-V/SPARC/PPC/ARM/CISC > UNIX and Linux spoken > > > > Hi, The issue is assigned and the port has an active maintainer so that looks good. I see you replied on the issue with a patch for a solution, but the patch is hidden in quite a large comment (I needed to read it twice before I spotted it). It can help to put the patch in an attachment of the issue as type 'patch'. You can send an email to ports@freebsd.org to get the attention of the ports managers. It can also help to open an upstream issue on the github repo of libfido. If the patch is accepted there it is a good argument to get the patch into FreeBSD. NB: I understand your feeling of urgency in this. In the meantime this is also a period of holidays/weekend, etc. Hope this helps. Regards, Ronald. ------=_Part_12008_193046442.1736073795943 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Van: Dennis Clarke <dclarke@blastwave.org>
Datum: zondag, 5 januari 2025 06:45
Aan: Current FreeBSD <freebsd-current@freebsd.org>
Onderwerp: Is there any way to nudge security/libfido2? It blocks chunks of KDE


     It seems to have been a while since I was able to run a poudriere bulk build and get KDE available. At least on 15-CURRENT. There is a
little brick in the path called security/libfido2 :

     https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283697

commit 74ecdf86d8d2a94a4bfcf094a2e21b4747e4907f resulted in the
appropriate declarations for the correct versions of _POSIX_C_SOURCE
via __POSIX_VISIBLE and then we get

error: call to undeclared function 'ppoll'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration]


Sort of annoying as even 14.2-RELEASE on amd64 and ports 2024Q4 fails :

[142amd64-2024Q4] [2025-01-04_10h11m35s] [committing] Queued: 5  Built: 4  Failed: 1  Skipped: 0  Ignored: 0  Fetched: 0  Tobuild: 0   Time: 00:04:44

The 15.0-CURRENT is much much worse :

[150amd64-latest] [2025-01-04_08h12m11s] [committing] Queued: 365 Built: 323 Failed: 2   Skipped: 40  Ignored: 0   Fetched: 0   Tobuild: 0 Time: 01:52:01


In any case ... is there a way to nudge that ?

-- 
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
 


Hi,

The issue is assigned and the port has an active maintainer so that looks good.
I see you replied on the issue with a patch for a solution, but the patch is hidden in quite a large comment (I needed to read it twice before I spotted it). It can help to put the patch in an attachment of the issue as type 'patch'.
You can send an email to ports@freebsd.org to get the attention of the ports managers.
It can also help to open an upstream issue on the github repo of libfido. If the patch is accepted there it is a good argument to get the patch into FreeBSD.

NB: I understand your feeling of urgency in this. In the meantime this is also a period of holidays/weekend, etc.

Hope this helps.

Regards,
Ronald.
  ------=_Part_12008_193046442.1736073795943--