Date: Sat, 7 Mar 2020 13:37:50 -0600 From: Paul Schmehl <pschmehl_lists@tx.rr.com> To: freebsd-questions@freebsd.org Subject: Re: Strange outcome: different outcomes from portmaster and pkg upgrade Message-ID: <104a6a24-b411-35f9-0674-d3fc68fd3da1@tx.rr.com> In-Reply-To: <20200306140700.32a85c58@gumby.homeunix.com> References: <4418f3c1-e025-e691-5c98-9ab9dd32ccc9@tx.rr.com> <20200305122407.4198b191@gumby.homeunix.com> <a2003dd6-612c-ccd9-5e5a-a14bd6af0305@tx.rr.com> <20200306140700.32a85c58@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/6/20 8:07 AM, RW via freebsd-questions wrote: > On Thu, 5 Mar 2020 15:25:31 -0600 > Paul Schmehl wrote: > >> On 3/5/20 6:24 AM, RW via freebsd-questions wrote: >> >>> Presumably your packages are up to date with the repository, but not >>> the ports tree. >> The ports tree is updated daily through a script in >> /etc/periodic/daily. >> >> >> [root@colo11 /usr/home/schmehl]# cat /etc/periodic/daily/190.portsnap >> #!/bin/sh >> /usr/sbin/portsnap cron >> /usr/sbin/portsnap update >> ... >> I just ran it manually, but it didn't update any of the affected >> ports. > Packages are built from the ports tree, so can lag behind it. You have > to wait for the packages to catch up. Just an FYI for anyone following this thread. I resolved the issue with gnutls by disabling the TPM option, which allowed the port to build as well as the two others that depended upon it. -- Paul Schmehl, Retired My opinions are my own. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?104a6a24-b411-35f9-0674-d3fc68fd3da1>