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 531D6158020 for ; Mon, 14 Nov 2022 21:53:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 178CBE0920; Mon, 14 Nov 2022 21:53:50 +0000 (UTC) Received: from foo.stuge.se (foo.stuge.se [212.116.89.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 92656E091B for ; Mon, 14 Nov 2022 21:53:49 +0000 (UTC) Received: (qmail 15329 invoked by uid 1000); 14 Nov 2022 21:53:43 -0000 Message-ID: <20221114215343.15328.qmail@stuge.se> Date: Mon, 14 Nov 2022 21:53:43 +0000 From: Peter Stuge To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Last rites: net-mail/vchkuser References: <291178b1-075f-6d89-8ff3-2a464ea9556f@gentoo.org> <20221114164352.11396.qmail@stuge.se> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Archives-Salt: 96178f32-a310-41ad-91e5-57075ba72791 X-Archives-Hash: cd8a59b49dac2de0b80ece581e122285 John Helmert III wrote: > > Jonas Stein wrote: > > > # Dead upstream > > > # Removal after 2023-01-01. Bug #881249. > > > net-mail/vchkuser > > > > Was there an actual issue with the package that prompted you to do > > this - something that a package maintainer should have resolved? > > > > I think it's a bad idea to remove a package if "Upstream Homepage and > > SRC_URI is gone" and "Gentoo is the last distro with this package" > > are the only reasons... > > Do you use it? Is it still functional? I don't use it, I use something else for the same task. Looking up the GitHub user that person seems present, just that particular repo is no longer there. Searching for the repo name on GitHub finds this however: https://github.com/bdrewery/vchkuser ..which seems to be a 2010 version of the code. I did a test, it works fine. Maybe just change the SRC_URI. //Peter