From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1A5DD158089 for ; Fri, 22 Sep 2023 11:23:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0B5582BC05C; Fri, 22 Sep 2023 11:23:35 +0000 (UTC) Received: from uriel.iewc.co.za (uriel.iewc.co.za [IPv6:2c0f:f720:0:3::9a49:2248]) (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) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CDDE82BC014 for ; Fri, 22 Sep 2023 11:23:34 +0000 (UTC) Received: from [154.73.32.4] (helo=tauri.local.uls.co.za) by uriel.iewc.co.za with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1qjeFu-00005X-2U for gentoo-dev@lists.gentoo.org; Fri, 22 Sep 2023 13:23:30 +0200 Received: from [192.168.1.145] by tauri.local.uls.co.za with esmtp (Exim 4.96) (envelope-from ) id 1qjeFt-0001iS-0A for gentoo-dev@lists.gentoo.org; Fri, 22 Sep 2023 13:23:29 +0200 Message-ID: <693d2ee8-ff3b-848d-35cc-1c6d288c282c@uls.co.za> Date: Fri, 22 Sep 2023 13:23:28 +0200 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: [gentoo-dev] Re: Standard parsable format for profiles/package.mask file Content-Language: en-GB To: gentoo-dev@lists.gentoo.org References: <645f542c-38b3-ddf1-7c0d-1a4fe32d12e3@gentoo.org> From: Jaco Kroon Organization: Ultimate Linux Solutions (Pty) Ltd In-Reply-To: <645f542c-38b3-ddf1-7c0d-1a4fe32d12e3@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-report: Relay access (uriel.iewc.co.za). X-Archives-Salt: 05b84ad3-ede1-4634-a266-17f95636927a X-Archives-Hash: 0e38c284e842a68c0dc2f2113b4f87e7 Hi, On 2023/09/22 13:16, Florian Schmaus wrote: > On 21/09/2023 21.40, Arthur Zamarin wrote: >> If this is a last-rite message, the last line must list the last-rite >> last date (removal date) and the last-rite bug number. You can also list > > FWIW, I would assume the last-rite date to be the date where the > package's last rites where initiated, i.e., where it was p.masked. The > removal date would be the date on which the packages was cleaned from > the tree. > >> other bugs relevant to the last-rite. So I think a format of: "Removal >> on ${REMOVAL_DATE}. > > I now we, myself included, often wrote "Removal on…", however, I > wonder if we should reflect reality and write "Removal after…" instead. +1 "on or after" would probably be most accurate though but gets very wordy. Kind regards, Jaco