NetBSD Problem Report #58943

From www@netbsd.org  Sat Dec 28 17:04:02 2024
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits)
	 client-signature RSA-PSS (2048 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id C94A01A923A
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 28 Dec 2024 17:04:02 +0000 (UTC)
Message-Id: <20241228170401.884B21A923B@mollari.NetBSD.org>
Date: Sat, 28 Dec 2024 17:04:01 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: pkgin doesn't warn if installed packages vanished and are broken by shlib major bumps
X-Send-Pr-Version: www-1.0

>Number:         58943
>Category:       pkg
>Synopsis:       pkgin doesn't warn if installed packages vanished and are broken by shlib major bumps
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Dec 28 17:05:00 +0000 2024
>Last-Modified:  Mon Dec 30 19:30:01 +0000 2024
>Originator:     Taylor R Campbell
>Release:        current, 2024Q4
>Organization:
The NotPackaged Installation
>Environment:
>Description:
User had packages including firefox installed from 2024Q3.

User configured pkgin to point at not-yet-fully-baked 2024Q4 repo URL, with (a) icu major bump 75 -> 76, but (b) no firefox.

User ran pkgin update && pkgin upgrade.

pkgin reported various packages to update but didn't warn that the update would break firefox because of icu major bump, with no corresponding firefox update to fix it:

calculating dependencies...done.

66 packages to refresh:
  ...

76 packages to upgrade:
  ... icu-76.1nb1 ...

0 to remove, 66 to refresh, 76 to upgrade, 2 to install
644M to download, 298M of additional disk space will be used

proceed ? [Y/n] y
...
pkg_install warnings: 0, errors: 0
reading local summary...
processing local summary...

Switching to the unfinished 2024Q4 URL may be reasonably described as user error.  But pkgin should alert that this update will break packages.
>How-To-Repeat:
1. install a package foo that depends on bar with shlib libbar.so.1
2. point pkgin at a binary package repository with an update for bar but _no foo package_
3. pkgin upgrade
4. try to use foo
>Fix:
Yes, please!

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/58943: pkgin doesn't warn if installed packages vanished and
 are broken by shlib major bumps
Date: Sat, 28 Dec 2024 19:46:05 +0100

 How should pkgin tell this apart from:

  a) foo has become part of bar (so no foo pkg is needed any more) - like
     it happens from time to time with perl extensions/libraries

  b) foo got renamed or a successor pkg and the new pkg was installed
     (e.g. as part of a meta-pkg that used to require foo but now requires
     the new version)


 Martin

From: Thomas Klausner <wiz@NetBSD.org>
To: NetBSD bugtracking <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: pkg/58943: pkgin doesn't warn if installed packages vanished and
 are broken by shlib major bumps
Date: Sat, 28 Dec 2024 20:54:58 +0100

 On Sat, Dec 28, 2024 at 06:50:01PM +0000, Martin Husemann via gnats wrote:
 >  How should pkgin tell this apart from:
 >  
 >   a) foo has become part of bar (so no foo pkg is needed any more) - like
 >      it happens from time to time with perl extensions/libraries
 >  
 >   b) foo got renamed or a successor pkg and the new pkg was installed
 >      (e.g. as part of a meta-pkg that used to require foo but now requires
 >      the new version)

 pkgin already understand SUPERSEDES.
  Thomas

From: nia <nia@NetBSD.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/58943: pkgin doesn't warn if installed packages vanished and
 are broken by shlib major bumps
Date: Mon, 30 Dec 2024 19:28:37 +0000

 Just throwing this out there: the option to keep previous major .so
 versions around after an upgrade.

 Some people locally compile software.

Home	PR Database Search