From nobody Tue Nov 21 21:31:34 2023 X-Original-To: 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 4SZcyL04wBz52L6p for ; Tue, 21 Nov 2023 21:31:38 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SZcyK6ljcz3c7l; Tue, 21 Nov 2023 21:31:37 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1700602297; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YEynva4yecbgu1O3u8KCafuLs3qkkhA1xT7Ia3WyodY=; b=OkMZs9pkDo6yEHweh6tWIp/0hA667u8+FMmU3lz7VA5kWdlftpOXFrueSF/VhOwUUqZpxH BPy3Qn2EHjrTQ9cn8kNjDiKaN/6qW/Vrq+Rv/ArTHeMnnDxxx6RrsGTMwIFLa148+zgbhO Ba59fRXO5Hxgwp70/AS1/fPHtQ4eHc6rhvvG7r4N1KlGlQN3o8ReqAiCK1zdqyBDbTOmL4 HW0EechuAQXuYR7kIv6+0X2iMDAaeZOaxa8MfQlrtxQjqJzlSDErzp8UdAD3F+uv48EPgr 1G6enmHmR7Mi7wv7LLoRRe6SmARuTECqlshF4uAbpO32T+bIA+vH5zpNtEQ5Rw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1700602297; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YEynva4yecbgu1O3u8KCafuLs3qkkhA1xT7Ia3WyodY=; b=dnpCw8IsiitNfn4KPcRg66YAdO/QtSl4lBLM1gsPWjkui8CQs6CPhbUPjIA0AxmlMSHRLT UEZDVQ0HtMPF8rojYn9Et9ekGjf40YZ7pxCvrrjxg1s9iuFk83WKg56wp18YFy+1KNhVBq v5wJCku3qWJT265/z2JMyoPqIhwzD4lXMffIdllnXNgFdb8c6h2ASS3P+zFobOpJz20jFT ZiThniF13HdBPbG30NFFFcihtkNZqMI0S82YOgO7iLLReQZ0h/NW2XfLjNiEonHLH8K6JH MLkKbCGS721O5zPuwewsuPw8+T7bItkaSo762h/xlcUAyt2/lna9Y+o0FyAWqw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1700602297; a=rsa-sha256; cv=none; b=XaqrHm2V9/K1TJGqbm/ahpA7aGoJheW1QDFFPa9ZpRTSVvzib1koep54k1H3pua8WkPyJA 2zJonkMJYPDIOqnaOuYf9Pj4Yi/tm8ksQkWX7RkefFKoMVHbudUvmglWHPdKgIFn2o0jZl Bamkjoe9tP2Me4qCakEw1zj0SwWNvv7exDk2bQHPnMcM90BMduYBMKnwWkKaoRHu5JiOzS ZH5MO4HiJWkRgOtxhRv1066ShId1gjyFX7+rpP57xRMUN6439kjyLb5OfQDsoULC/W5O+9 K3PCpaAOB5tM6Hi38NVa4muiR6HrNxpq1MOldJfSFAL6/0tFjYYWSkbDlE26vw== Received: from [IPV6:2a01:e11:2002:4280:4aee:cff:fe73:9857] (unknown [IPv6:2a01:e11:2002:4280:4aee:cff:fe73:9857]) (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 did not present a certificate) (Authenticated sender: madpilot/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SZcyK3XQ1z1Sn4; Tue, 21 Nov 2023 21:31:37 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Message-ID: Date: Tue, 21 Nov 2023 22:31:34 +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 Subject: Re: Why do packages disappear? To: "Edward Sanford Sutton, III" , ports@freebsd.org References: <7a0cfebd-9137-435e-910a-3e9641650976@redwoodhodling.com> <36734d00-d0cb-4007-b631-9255cb7880e9@FreeBSD.org> Content-Language: en-US From: Guido Falsi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 21/11/23 22:00, Edward Sanford Sutton, III wrote: > On 11/21/23 09:21, Guido Falsi wrote: >> On 21/11/23 16:39, Richard Childers wrote: >>> >>> I was using ungoogled-chromium and I had 60+ tabs that I can now not >>> get back because ungoogled-chromium has been withdrawn from circulation. >>> >>> >>> why are these packages appearing and disappearing? If it's a package, >>> it's supposed to be good enough to public use. The experimental stuff >>> is supposed to stay in the ports section, not be promoted to packages. >>> >> >> Can you explain what you mean by "disappear"? >> >> If the problem is that from time to time the package is not present in >> the set of official packages, that is most probably due to the package >> failing to build in the last run, which could be due to many many >> reasons (*). If you track quarterly it should happen less frequently. >> >> If by disappear you mean that pkg unexpectedly removed it from your >> system, pkg should have stated that it wanted to do that and why, and >> maybe some investigation is required. > > It should always be listed that it will be removed but in my experience > it does not state 'why'. Usually it is the result of dependency updates > need a new version of the package and the new version isn't in the > repository; to complete the update of what is installed and in the > repository, the package will be removed instead of left installed+broken. > Well it not always states why, you are right, but stopping pkg before it performs the update and analyzing things usually sheds some light. Anyway pkg has not been removing packages only because they are not present in the repo for a long time (I do remember this used to happen in the early days when it was still named pkgng) > I do wish it said why and I also wish there was a way to say to perform > upgrades but not upgrade things if they relate to a specified port; > locking the port that would be removed would leave it, but also would > still permit its dependencies to upgrade even if the locked port broke > last I tested it. This is something that requires operator intervention, locking locks only that package, that is the semantics, if you want to lock all dependencies you should do it by hand (can also be automated with a pkg query pipe I guess). But I don't see an easy solution to what you report. I am not able to suggest patches to pkg in this direction. -- Guido Falsi