From nobody Tue Jan 2 03:04:00 2024 X-Original-To: freebsd-testing@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 4T3yP42hspz561wr for ; Tue, 2 Jan 2024 03:04:08 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 4T3yP35LWgz4Pvd; Tue, 2 Jan 2024 03:04:07 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x72d.google.com with SMTP id af79cd13be357-78106c385a1so898535185a.0; Mon, 01 Jan 2024 19:04:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704164644; x=1704769444; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=pw8VKqBykOxkdZAWZElVgLFDpreFLGFPNrHeH+4/Zg4=; b=MR7a01X4zt/De9AnnY2bnozumMRc8vcqwkvQXPKN0ACIRg5S0EwSeQk1WxK31evvvk tLPQ87Lfl/Icx2A7OhGDZss+Xutzq0iSx2txGtnlFewtocqJF+rU3vHmTmJZiLWYqMPK zKOSiMRzYDskb6TDtunxU5L3h8w2JqfMELkraq76lGclaycdoJ349Ym7B301rn382LKb /JOWzXN3Bhy1wdRhIt8SiHCTycGMHug4KYbxDmnNCCWdhCU3wiyVy7UaWqxAdEF1xq+n zWancFQ8G0gnkEDGyAkPUwkEojBTkDfHC6ZBd44kh5hjVty+xbmKQTrQuuKADB1Hq3Z/ FSKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704164644; x=1704769444; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=pw8VKqBykOxkdZAWZElVgLFDpreFLGFPNrHeH+4/Zg4=; b=OlXJ7lJYs217tACYkbfiETrWWerA1jlHkB01Ouis/ZYib2SeULdoqpI5Zq5e9CccLV In/eCfhRTATXzqt2DaUeebT775ZS3r2MQIAcIz7+ifdOznJNWgD7dD+vVfHzt4D/nrf5 MFG1AgRlSZw+PKWPmZbmioqNjvne8fiAR3955Fm8xm+/b0rmoKYQFwYRUWR7VggqFKfs rscxNVXZDQR3yM7lgSIckV9spqNVNLqcOEFfl7mfhLsrWVXPHXWRuKdLZRRIjvErnJBF f21By/zxxS4MfT8bm/2CueU+ElVaXI5IQb5zqtRODjwIQfEO2uXybm02UAHkKi/YciSL 9xaA== X-Gm-Message-State: AOJu0YwoPSw1SFx5LnuEHV6sp1UxlQtXjRx0OmKKFUaN7Met0BRLJjax jvQEoDg1Hi9JE6KHLMlP1XMTXrZqQFzXJA== X-Google-Smtp-Source: AGHT+IFxIl5v/OBNWWwrgzvFTLHFsGcHGClYPf2owlWIfRKxifgVdNpHZJpwMfHTnaySyeSWlIg1cg== X-Received: by 2002:a05:620a:8408:b0:781:be0d:59f4 with SMTP id pc8-20020a05620a840800b00781be0d59f4mr3424406qkn.107.1704164643576; Mon, 01 Jan 2024 19:04:03 -0800 (PST) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id c6-20020ae9e206000000b0077f289b92c6sm9146697qkc.123.2024.01.01.19.04.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 01 Jan 2024 19:04:03 -0800 (PST) Date: Mon, 1 Jan 2024 22:04:00 -0500 From: Mark Johnston To: Moin Rahman Cc: freebsd-testing@freebsd.org Subject: Re: new kyua import Message-ID: References: <6F793310-839A-426A-9B90-AAAEB57929CF@freebsd.org> <73A08DFD-F4FA-41A4-9F9D-772962F27397@freebsd.org> <4059A36A-278C-475A-B2FA-BC058704BC6C@freebsd.org> List-Id: Testing List-Archive: https://lists.freebsd.org/archives/freebsd-testing List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-testing@freebsd.org X-BeenThere: freebsd-testing@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4059A36A-278C-475A-B2FA-BC058704BC6C@freebsd.org> 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:15169, ipnet:2607:f8b0::/32, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T3yP35LWgz4Pvd On Tue, Jan 02, 2024 at 03:26:49AM +0100, Moin Rahman wrote: > > > > On Jan 2, 2024, at 2:41 AM, Mark Johnston wrote: > > > > On Tue, Jan 02, 2024 at 02:37:01AM +0100, Moin Rahman wrote: > >> > >> > >>> On Jan 2, 2024, at 2:35 AM, Mark Johnston wrote: > >>> > >>> On Tue, Jan 02, 2024 at 02:29:38AM +0100, Moin Rahman wrote: > >>>> > >>>> > >>>>> On Jan 2, 2024, at 2:23 AM, Mark Johnston wrote: > >>>>> > >>>>> Hi, > >>>>> > >>>>> It looks like the kyua repo here has received a number of bug fixes > >>>>> since kyua was last re-imported back into the base system. It looks > >>>>> like neither the base system copy nor devel/kyua in the ports tree is > >>>>> being kept up to date with https://github.com/freebsd/kyua. > >>>>> > >>>>> In particular, we're missing a fix for > >>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273481 which is > >>>>> available in github. That bug is causing occasional failed CI runs. > >>>>> > >>>>> Would anyone volunteer to import the latest version of kyua into the > >>>>> base system? > >>>>> > >>>> > >>>> I am not a src committer but if you want I can create a separate port > >>>> for that. jmmv@ has been mia for a while and our fork is ahead of the > >>>> original one. > >>> > >>> Thank you, but is there really a need to add a new port? Can we just > >>> switch to https://github.com/freebsd/kyua as the upstream? jmmv/kyua > >>> has not gotten any new development or bug fixes in a long time, and I > >>> cannot see any other places where kyua development is ongoing. > >>> > >>>> Kind regards, > >>>> Moin > >> > >> We can wait for 2 weeks for the timeout then. :) > > > > Sounds good to me, thank you. I don't use kyua from the ports tree (and > > I don't think our jenkins does either) but other folks may be interested > > in the update. > > > > We still need someone to do the import into the src tree. I can try but > > I'm not experienced with vendor imports, and I don't particularly want > > to change that. :) > > > Do you know how to submit a review for a vendor tree import? It's easy > importing but I need someone to review it. As it is totally a seperate > tree it is difficult to submit the review itself. Although the commit > for the merge might be submitted for the review. You can upload arbitrary diffs to phabricator, so you could diff the tree before and after the merge and upload the resulting patch. And maybe push the merge somewhere to let others take a look and verify that it appears to be done correctly. I'm also happy to test the import (probably not until late this week though).