Jumbled Dependencies (George Mitchell)

[Gladiola]

To troubleshoot this, we might try the following.<div><br /></div>1. Record your current state. Before adjusting machines, use pkg version >> someFile.txt to record what package is installed. Look carefully at that list.<div><br /></div>2.  Check if the clients are calling the repo you expect.  pkg.conf will hold a bracket of files. Are you hitting the file or http URL that holds the right stuff?  Maybe a simple update there could pull down what you need.<div><br /></div>3.  The dependencies seem to be missing. Did we try the man page's command for that? Maybe pkg didn't realize it was missing what was needed.  pkg check -d -a<div><br /></div>4.  Before doing anything destructive, like wrecking out or ripping out progams, can you back up those repo items? <div><br /></div>REF:  <br><a href="https://www.freebsd.org/cgi/man.cgi?query=pkg&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html">https://www.freebsd.org/cgi/man.cgi?query=pkg&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html</a><div><br /></div>v/r,<br>gladiola<div><br /></div><br>-------- Original Message --------<br>On Jun 14, 2020, 8:00 AM, < freebsd-hackers-request at freebsd.org> wrote:<blockquote class="protonmail_quote"><br><p dir="ltr">Send freebsd-hackers mailing list submissions to<br>
	freebsd-hackers at freebsd.org</p>
<p dir="ltr">To subscribe or unsubscribe via the World Wide Web, visit<br>
	<a href="https://lists.freebsd.org/mailman/listinfo/freebsd-hackers">https://lists.freebsd.org/mailman/listinfo/freebsd-hackers</a><br>
or, via email, send a message with subject or body 'help' to<br>
	freebsd-hackers-request at freebsd.org</p>
<p dir="ltr">You can reach the person managing the list at<br>
	freebsd-hackers-owner at freebsd.org</p>
<p dir="ltr">When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of freebsd-hackers digest..."<br></p>
<p dir="ltr">Today's Topics:</p>
<p dir="ltr">1. Jumbled Dependencies (George Mitchell)<br></p>
<p dir="ltr">----------------------------------------------------------------------</p>
<p dir="ltr">Message: 1<br>
Date: Sat, 13 Jun 2020 16:09:43 -0400<br>
From: George Mitchell <george+freebsd at m5p.com><br>
To: FreeBSD Hackers <freebsd-hackers at FreeBSD.org><br>
Subject: Jumbled Dependencies<br>
Message-ID: <f3593bf6-c998-88dc-949c-634aa9b063e1 at m5p.com><br>
Content-Type: text/plain; charset="utf-8"</p>
<p dir="ltr">I do package builds on one machine on my (small) network, using<br>
portmaster, and then distributes the built packages to my other<br>
machines. This week, I decided to make python38, rather than<br>
python37, my default version on Python 3. Specifically,</p>
<p dir="ltr">portmaster -o lang/python38 python37</p>
<p dir="ltr">I think I missed a step here to upgrade all my py37-* packages to<br>
py38-* packages. However, I did recompile a whole list of packages<br>
(specific example: vim) so that on my build machine it lists<br>
python38-3.8.3 as a dependency. I build a new repo on the build<br>
machine and then did a "pkg upgrade" on the other machines. This<br>
did install the new version of vim on the client machines, but<br>
"pkg info -d vim" on a client still says it depends on<br>
python37-3.7.7. (And there are a pile of other packages that are<br>
spuriously listed as still depending on python37.)</p>
<p dir="ltr">Any suggestions as to why "pkg upgrade" did not copy correct<br>
dependency information from the build machine to the clients? And<br>
how do I bandage up the foot I shot myself in? -- George</p>
<p dir="ltr">-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: <a href="http://signature.asc">signature.asc</a><br>
Type: application/pgp-signature<br>
Size: 833 bytes<br>
Desc: OpenPGP digital signature<br>
URL: <<a href="http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20200613/bbb0cc0e/attachment-0001.sig">http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20200613/bbb0cc0e/attachment-0001.sig</a>></p>
<p dir="ltr">------------------------------</p>
<p dir="ltr">Subject: Digest Footer</p>
<p dir="ltr">_______________________________________________<br>
freebsd-hackers at freebsd.org mailing list<br>
<a href="https://lists.freebsd.org/mailman/listinfo/freebsd-hackers">https://lists.freebsd.org/mailman/listinfo/freebsd-hackers</a><br>
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"<br></p>
<p dir="ltr">------------------------------</p>
<p dir="ltr">End of freebsd-hackers Digest, Vol 894, Issue 7<br>
***********************************************<br>
</p>
</div>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 489 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20200614/28b2a3df/attachment.sig>