From nobody Sun Mar 03 01:48:09 2024 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 4TnPqH4sGkz5DMgJ for ; Sun, 3 Mar 2024 01:48:11 +0000 (UTC) (envelope-from hubert.tournier@gmail.com) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 4TnPqG5cjLz52vQ for ; Sun, 3 Mar 2024 01:48:10 +0000 (UTC) (envelope-from hubert.tournier@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=VIYwg0y1; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of hubert.tournier@gmail.com designates 2a00:1450:4864:20::433 as permitted sender) smtp.mailfrom=hubert.tournier@gmail.com Received: by mail-wr1-x433.google.com with SMTP id ffacd0b85a97d-33d36736d4eso2061034f8f.1 for ; Sat, 02 Mar 2024 17:48:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709430489; x=1710035289; darn=freebsd.org; h=subject:from:cc:to:content-language:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=NamfPG35UWwfTtstqzvLgZQAXLpQ4MOaUI6oeOvsWzo=; b=VIYwg0y1JsypE7TnYDdsSsRk8nZdpZc37gevDw8Cq7ZGLbPwxBWxteR7zhap/EnoHE Y+pUzYxzHz2a5KPMVrbBi3WXu2kTgvHZo/D3UWUhJ9LQA5sJ+5aMBXsONJaBkhQDmOGe xSBbv9SerpM2sEMMGKT/nO7bvxwwvv31qq4FgWAU8Y189YKKLMb6SRC+J5UYlK+kGTXL K889SUAX3oGRR0x192QBviuT2pIKMgjLAKS7Lm4k3HWngRMQVgsbfTXGWxnmsyDvXHDF xzDB3eBOzgNpxk5YP7BUMAzdK7aZ9A5CX47iPUgYM6PmPtHlCdOjVyJjcnStWURP4fka ftEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709430489; x=1710035289; h=subject:from:cc:to:content-language:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=NamfPG35UWwfTtstqzvLgZQAXLpQ4MOaUI6oeOvsWzo=; b=UEVH5ZeJT8TndnCIU2fbglu4BsIuyeIlYhdGhNy8m3EjgvxL9O1dEgZLGsoftM6BXi LrFpnF5MdwPCQ6cMHI4ZxtsFz3x+39faSXrtex+Woev3bkzPa0NLM7a99ufhNmXBzLhf imNVHBy4RCkmW3E5e20X+OIV/noRG8SWPvQ6NzhBk9x65dVhO7ynt+zRyaPOMs/+eCxk Kdg1GXl/lGKCjlXGexuU8N1yRH9nMWndxgPiNjSBm9HQz2tC4W6YvwkQZ4Evjew0kXQi Fc7E+LiAczMqhLgxxUoOlG19KHxiGmzzs0J2HneaUk/Mhl94LKBQAevkXhfXyri39MRA 6VYw== X-Gm-Message-State: AOJu0YwMMgWIcSo/cot6AEm36CE6sXrXRtkQSqIzg2KSJS1ZHcqwheMp dLivt+SQd6K2M2lO+GVQzXv5vEw60AOgf/j4W1l8CDSnRkl35rTYx0vSfsyw/q4= X-Google-Smtp-Source: AGHT+IHNUg9o/KW6vcXj41HG0BKlQgJuWQBW9Il8HqxGDeKlwQW27iXZWJBnFvM0XXPRf/KP0OgMCA== X-Received: by 2002:adf:e9d1:0:b0:33d:c6dd:b4b2 with SMTP id l17-20020adfe9d1000000b0033dc6ddb4b2mr3870085wrn.54.1709430488837; Sat, 02 Mar 2024 17:48:08 -0800 (PST) Received: from ?IPV6:2a01:e0a:80d:9d80:12d:1878:26dd:4881? ([2a01:e0a:80d:9d80:12d:1878:26dd:4881]) by smtp.gmail.com with ESMTPSA id l9-20020a056000022900b0033cf2063052sm8413947wrz.111.2024.03.02.17.48.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 02 Mar 2024 17:48:08 -0800 (PST) Content-Type: multipart/alternative; boundary="------------6SepmZHSLXbozTyNjxsHDyqj" Message-ID: Date: Sun, 3 Mar 2024 02:48:09 +0100 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 User-Agent: Mozilla Thunderbird Content-Language: fr To: Xin LI Cc: freebsd-ports@FreeBSD.org From: Hubert Tournier Subject: Re: Proposed ports deprecation and removal policy X-Spamd-Bar: / X-Spamd-Result: default: False [-0.50 / 15.00]; THREAD_HIJACKING_FROM_INJECTOR(2.00)[]; FAKE_REPLY(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.51)[-0.507]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; XM_UA_NO_VERSION(0.01)[]; FREEMAIL_TO(0.00)[gmail.com]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::433:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; TAGGED_FROM(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4TnPqG5cjLz52vQ This is a multi-part message in MIME format. --------------6SepmZHSLXbozTyNjxsHDyqj Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On Thu, 29 Feb 2024 19:26:23 UTC, Xin LI wrote: > For example, one of my port gets marked as DEPRECATED because a dependency > was deprecated and scheduled for removal after 1 month, without any email > telling me so (the port doesn't have a lot of releases and there isn't any > release during that "parole" month), and it gets removed after that. So in > order to know there is an ongoing deprecation of the port, I as a port > maintainer would have to either watch the directory for any changes, or > read all ports-git commit messages or at least a filtered version of it, > and that's burdensome and inefficient use of developer time at best. > What I would love to see happen is that, when a port gets marked as > DEPRECATED, there is an automated system that sends me notification with > something like: > ACTION REQUESTED: X new ports you maintain is marked as DEPRECATED [...] > and that email gets sent every 7 days until the port is removed or the > issue is fixed. Or a bug is created and assigned to the maintainer, etc. Alternately, you could just create a periodic batch on your own machine to do that check on the ports you maintain. The tool I mentioned in the neighboring "Port tree linter" thread can do that for you with the following command: $ portstreelint -hu -mdelphij@freebsd.org 2> /dev/null It would check BROKEN, FORBIDDEN, IGNORE (poorly) and DEPRECATED marks, as well as vulnerabilities reported in VuXML (in the version I will upload tomorrow) and many other things, automatically on your 31 ports. Best regards, Hubert --------------6SepmZHSLXbozTyNjxsHDyqj Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit 
On Thu, 29 Feb 2024 19:26:23 UTC, Xin LI wrote:

> For example, one of my port gets marked as DEPRECATED because a dependency
> was deprecated and scheduled for removal after 1 month, without any email
> telling me so (the port doesn't have a lot of releases and there isn't any
> release during that "parole" month), and it gets removed after that.  So in
> order to know there is an ongoing deprecation of the port, I as a port
> maintainer would have to either watch the directory for any changes, or
> read all ports-git commit messages or at least a filtered version of it,
> and that's burdensome and inefficient use of developer time at best.

> What I would love to see happen is that, when a port gets marked as
> DEPRECATED, there is an automated system that sends me notification with
> something like:

> ACTION REQUESTED: X new ports you maintain is marked as DEPRECATED

[...]

> and that email gets sent every 7 days until the port is removed or the
> issue is fixed.  Or a bug is created and assigned to the maintainer, etc.

Alternately, you could just create a periodic batch on your own machine
to do that check on the ports you maintain.

The tool I mentioned in the neighboring "Port tree linter" thread can do
that for you with the following command:

$ portstreelint -hu -m delphij@freebsd.org 2> /dev/null

It would check BROKEN, FORBIDDEN, IGNORE (poorly) and DEPRECATED marks,
as well as vulnerabilities reported in VuXML (in the version I will
upload tomorrow) and many other things, automatically on your 31 ports.

Best regards,

Hubert

--------------6SepmZHSLXbozTyNjxsHDyqj--