Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Jun 2020 14:59:28 -0400
From:      George Mitchell <george+freebsd@m5p.com>
To:        freebsd-ports@freebsd.org
Subject:   Re: Jumbled dependencies
Message-ID:  <54dce842-d65c-157f-395e-5fe52bddd7b7@m5p.com>
In-Reply-To: <4ae12d16-0cf6-e4d6-bdf7-2216f0a6683a@m5p.com>
References:  <4ae12d16-0cf6-e4d6-bdf7-2216f0a6683a@m5p.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--udM6QLNjGoSonOS7k8c2XOJuvQ1PyL5Qh
Content-Type: multipart/mixed; boundary="H6kQqZWnMeQLHznEZ4G0yn5xAFtyhKu9O";
 protected-headers="v1"
From: George Mitchell <george+freebsd@m5p.com>
To: freebsd-ports@freebsd.org
Message-ID: <54dce842-d65c-157f-395e-5fe52bddd7b7@m5p.com>
Subject: Re: Jumbled dependencies
References: <4ae12d16-0cf6-e4d6-bdf7-2216f0a6683a@m5p.com>
In-Reply-To: <4ae12d16-0cf6-e4d6-bdf7-2216f0a6683a@m5p.com>

--H6kQqZWnMeQLHznEZ4G0yn5xAFtyhKu9O
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 2020-06-14 09:10, George Mitchell wrote:
> I do package builds on one machine on my (small) network, using
> portmaster, and then distributes the built packages to my other
> machines.  Last week, I decided to make python38, rather than
> python37, my default version on Python 3.  Specifically,
>=20
> portmaster -o lang/python38 python37
>=20
> I think I missed a step here to upgrade all my py37-* packages to
> py38-* packages.  However, I did recompile a whole list of packages
> (specific example: vim) so that on my build machine it lists
> python38-3.8.3 as a dependency.  I build a new repo on the build
> machine and then did a "pkg upgrade" on the other machines.  This
> did install the new version of vim on the client machines, but
> "pkg info -d vim" on a client still says it depends on
> python37-3.7.7.  (And there are a pile of other packages that are
> spuriously listed as still depending on python37.)
>=20
> Any suggestions as to why "pkg upgrade" did not copy correct
> dependency information from the build machine to the clients?  And
> how do I bandage up the foot I shot myself in?        -- George

So I elected to fix it with a sledge hammer.  On my client machines,
I did a "pkg delete python37" while making a note of the packages
that were to be deleted.  Then I reinstalled those (changing the
"py37-" to "py38-" where needed).  Everything is fine now, except
that I have a pile of "duplicate dependency listing" messages,
which seem to be harmless.                            -- George



--H6kQqZWnMeQLHznEZ4G0yn5xAFtyhKu9O--

--udM6QLNjGoSonOS7k8c2XOJuvQ1PyL5Qh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAl7nxRYACgkQwRES3m+p
4flxiA//aWgAEUhpcvgyro/W4N5I2G9p6+D3Y1tNw8TefHcMFRE6mfZe9MLgwJjQ
zpDEMLCyMLWzn5YbxJogn+oM2zFdkk9tQgW5DUHBbdTzfs1wvnfo92qDVcKnVmDO
jhs/NwBFU+Cg132BUBAKF0mIrOeZWSOj3UtC1Ezm3TMURu1noP0qMaoji1ndsKSJ
MCX4MjX093OkllGa84N/JxuSvp710ZwkHSVTSozYlOQJqfUjdxQVyRkhi1G3PVgZ
NV6Y54XYJ6nHZ7LcdlA/grhjsUHmTgEPXG4kkDEwPdrffKsed8GHw2JjTM4nu+vI
xaL2JxBjWl1nJv9Yz9g3uBrkCIVjsgYqw5yPqESMwsx6WGe8cML5K2aQ2e0L3blE
CpsJHKrGjyh0DiPxpZIGiBVucbvCNgvGGV4k8yGrcl3WeeiIXA1hEYGViv6sTorf
i+N6IJQRTKo+sAhaUlXvdAlyqXUZPr7oyBoU45kxnYs4ZmQba+SCrgIndBwEOV8t
CgLW4DkWaRGDZJK2cv6sWqpARGrIcasMVF/sPSgqIyxz9cwLU9qp0cNy2cRAA/tt
08vnSPo/YSYPioCGTab17XQPjL/fGsV322aANi5CxWrp6HHTMT/De/1kLpZQLpEl
od45KQMKx5pHkVEs6MmCRTVZ7Bpvk3xHXqBt43ndHRV5A3oG81c=
=iS51
-----END PGP SIGNATURE-----

--udM6QLNjGoSonOS7k8c2XOJuvQ1PyL5Qh--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54dce842-d65c-157f-395e-5fe52bddd7b7>