Re: Documented way to update python?

To: Taylor R Campbell <campbell+netbsd-tech-pkg%mumble.net@localhost>
Subject: Re: Documented way to update python?
From: Jonathan Perkin <jperkin%mnx.io@localhost>
Date: Sat, 28 Oct 2023 08:20:15 +0100

* On 2023-10-27 at 22:57 BST, Taylor R Campbell wrote:

But, whatever the mechanism is, I think we should treat it as a high
priority for `pkgin update && pkgin upgrade' to do the right thing for
anyone following a binary package repository.  Any requirement for
manual intervention should be treated as a severe bug in whatever it
is we're doing.

It should do. There was an issue with SUPERSEDES metadata not beinggenerated correctly but myself and wiz fixed that.

If a package has correct metadata and pkgin is not upgrading it properlythen yes, please raise a bug for pkgin and I will look into it.


--
Jonathan Perkin   -   mnx.io   -   pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com

Follow-Ups:
- Re: Documented way to update python?
  - From: Benny Siegert

References:
- Re: Documented way to update python?
  - From: Greg Troxel
- Re: Documented way to update python?
  - From: Taylor R Campbell

Prev by Date: daily pkgsrc CVS update output
Next by Date: Re: Documented way to update python?
Previous by Thread: Re: Documented way to update python?
Next by Thread: Re: Documented way to update python?
Indexes:

Home | Main Index | Thread Index | Old Index