From nobody Wed Mar 23 14:05:18 2022 X-Original-To: freebsd-ports@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 579461A33A27 for ; Wed, 23 Mar 2022 14:05:31 +0000 (UTC) (envelope-from shamaz.mazum@gmail.com) Received: from mail-ua1-x934.google.com (mail-ua1-x934.google.com [IPv6:2607:f8b0:4864:20::934]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KNqrB4tM0z4crg; Wed, 23 Mar 2022 14:05:30 +0000 (UTC) (envelope-from shamaz.mazum@gmail.com) Received: by mail-ua1-x934.google.com with SMTP id i26so732845uap.6; Wed, 23 Mar 2022 07:05:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bBwvm2v5F9C3wEiRzurFE703dxEbkIxCcrDP4cBbeag=; b=hVRZiZzqW8ksQyWoL2CrLYi2s5GbMg7LCO3afZfy6z5AetkgoN3XEfy/BmvuOcOlRN iN+4qpsf+D99/zXj7ZIKpX/jcJd4ZACrcKqINxXUmaFWF0dDH2/GttNfcyUEKVxtTuW0 yJ3LJskJMRcNTFFt5Wxq28RDL9f8BZLOu9de+6xO1Insu48adFdzoPzaQPHBneShzOAL NRQALd/7zp5QRDDDCBpqPaOCkiDF6GB07kCav3Pp3HY4mUG3RYjm3M5sKNAhn1++nzFm hjgdLB7vBddQuSquogaqbwaaZHixayGWi7GZq7lRrlD+1A6/qXDxy/1/QLm+wy27jePt 40LQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bBwvm2v5F9C3wEiRzurFE703dxEbkIxCcrDP4cBbeag=; b=hu5DkQYuzFCU9yM7e/PjXLvrWBwsB1wEksB7WX9fxkkQNCTzric9pU20jNcYAG5OH4 AB2bl91pd58VDKY6LPCLEGDo2ZFf0WLlVIydBljYi0NQOnFyP98g+PPIHbS4Z6mqNE58 yf0oUUxw2At9Ha6bWG0a3tSCoTXnBCoMTgthoToRVOt/ykcNFH08H2k/BTyB3r1XqjS1 Xz27jh7TJqJG1OtBARgXmwgd9pZr1nA9Qix5ULsqA/gIFYwK7FQkDcBBOyr1PillHuCh V4EbrJzlROb+dbW6m+e69kwZw8UPavkAHo/xOlZGq0xNsWtiA+XZFM4jWLDrc43JccS2 NZYA== X-Gm-Message-State: AOAM531EORAphcYYvDYajXcinnGEQzn8UkU0zGqjMPLuxvcOj38DAlun kRW4lwEiqkWMrUXLSrIaWlr9Q1qSXPDJvjsp9J1s0xfdGQhGcRYS X-Google-Smtp-Source: ABdhPJw17muKhZXnAqLkW+mA3U06Ez/QpDwj2Nm4ag59EDq94iL3t8RtKHr5hCxSxj3UcZ5XKBmuTnQFUUes4Z4BXlM= X-Received: by 2002:a05:6130:301:b0:359:7ac8:6f81 with SMTP id ay1-20020a056130030100b003597ac86f81mr2364163uab.32.1648044329938; Wed, 23 Mar 2022 07:05:29 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: <90949B3A-DB76-485B-BA14-425849635B49@freebsd.org> <20220323135659.s4ameibeobk7tft7@aniel.nours.eu> In-Reply-To: <20220323135659.s4ameibeobk7tft7@aniel.nours.eu> From: Vasily Postnicov Date: Wed, 23 Mar 2022 17:05:18 +0300 Message-ID: Subject: Re: What to do if e-mail from pkg-fallout@freebsd.org arrives? To: Baptiste Daroussin Cc: Muhammad Moinur Rahman , freebsd-ports@freebsd.org Content-Type: multipart/alternative; boundary="000000000000dc362005dae33844" X-Rspamd-Queue-Id: 4KNqrB4tM0z4crg X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=hVRZiZzq; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of shamazmazum@gmail.com designates 2607:f8b0:4864:20::934 as permitted sender) smtp.mailfrom=shamazmazum@gmail.com X-Spamd-Result: default: False [-2.45 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.45)[-0.454]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::934:from]; MLMMJ_DEST(0.00)[freebsd-ports]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --000000000000dc362005dae33844 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Lol, I've just checked the source code. And voil=C3=A0, va_list is gone in master :) I was really confused why I cannot reproduce that bug on my machine, didn't see the log was for arm. Thank you all! =D1=81=D1=80, 23 =D0=BC=D0=B0=D1=80. 2022 =D0=B3. =D0=B2 16:57, Baptiste Da= roussin : > On Wed, Mar 23, 2022 at 04:44:29PM +0300, Vasily Postnicov wrote: > > Oh my! I didn't see that. I tried on x86-64 :) I don't even have arm64 > > machine. Any ideas what to do? > > > > Communicate with upstream to see if they are aware of such a build issue > (providing them the build error) in their cases they will probably say > "yes sure > that rings a bell we got rid of this issue a year and a half ago) > > > https://github.com/Interrupt/systemshock/commit/81804761044593a22aeba6b6a= 3a7af56465f5153 > > (Side note: I am not claiming you should have guessed this could be a > potential > fix, but upstream should be able to point you at this patch). > > Since they haven't issue a release since they commit that you can try > backporting that patch into your port, praying that the patches applies, > if it > does, test that your port still works on plateform you can actually test > on, and > open a PR with the said patch applied). > > if it fixes the issue pkg-fallout should not bother you anymore, if not, > then > the investigation needs to be pursued. > > > Hope it helps, > > Best regards, > Bapt > > --000000000000dc362005dae33844 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Lol, I've just checked the source code. And voil=C3=A0= , va_list is gone in master :)

I was really confused why= I cannot reproduce that bug on my machine, didn't see the log was for = arm.

Thank you all!

=D1=81=D1=80, 23 =D0=BC= =D0=B0=D1=80. 2022 =D0=B3. =D0=B2 16:57, Baptiste Daroussin <bapt@nours.eu>:
On W= ed, Mar 23, 2022 at 04:44:29PM +0300, Vasily Postnicov wrote:
> Oh my! I didn't see that. I tried on x86-64 :) I don't even ha= ve arm64
> machine. Any ideas what to do?
>

Communicate with upstream to see if they are aware of such a build issue (providing them the build error) in their cases they will probably say &quo= t;yes sure
that rings a bell we got rid of this issue a year and a half ago)

https://gith= ub.com/Interrupt/systemshock/commit/81804761044593a22aeba6b6a3a7af56465f515= 3

(Side note: I am not claiming you should have guessed this could be a poten= tial
fix, but upstream should be able to point you at this patch).

Since they haven't issue a release since they commit that you can try backporting that patch into your port, praying that the patches applies, if= it
does, test that your port still works on plateform you can actually test on= , and
open a PR with the said patch applied).

if it fixes the issue pkg-fallout should not bother you anymore, if not, th= en
the investigation needs to be pursued.


Hope it helps,

Best regards,
Bapt

--000000000000dc362005dae33844--