Am 21.10.18 um 23:19 schrieb Kevin P. Neal: > On Sun, Oct 21, 2018 at 08:45:55PM +0000, Lorenzo Salvadore via freebsd-ports > wrote: >>> So I just saw another post on this list that mentioned the "pkg version >>> -vL=" >>> command. Now, I've got a /usr/ports tree used by poudriere and run on the >>> same machine. I svn updated my /usr/ports and kicked off poudriere. When it >>> was done I ran "pkg upgrade". But the "pkg version -vL=" still shows this: >>> >>> py27-ndg_httpsclient-0.4.2 < needs updating (port has 0.5.1) >>> py27-pbr-1.8.1_1 < needs updating (port has 3.1.1) >>> py27-pip-9.0.1 < needs updating (port has 9.0.3) >>> py27-psutil-5.2.2 < needs updating (port has 5.4.7) >>> py27-pyasn1-0.2.2 < needs updating (port has 0.4.2) >>> py27-python2-pythondialog-3.4.0 < needs updating (port has 3.4.0_1) >>> py27-werkzeug-0.12.2 < needs updating (port has 0.14.1) >>> transmission-web-2.93_1 < needs updating (port has 2.94) >>> >>> The question is: why are these packages not getting upgraded when I run >>> pkg upgrade? >>> >>> And, yes, pkg version is getting its info from my poudriere server. I'm >>> looking at the web server logs in real time. >>> >>> Any ideas? >> pkg upgrade is for upgrading packages and not ports, but pkg version is >> comparing >> your version against the versions of the port tree, not of the package >> repository. > It is comparing against the version of the ports tree _shared_ with > _Poudriere_. I'm running my own package server. The packages installed, > the packages built by Poudriere, and the ports tree should all be sync > because they are all on the same machine. But they aren't it seems. That's > odd. > >> To compare against the package repository, use the -R flag: >> >> pkg version -RvL= > Huh. When I try that I get: > > idnkit-1.0_7 ? orphaned: dns/idnkit > py27-funcsigs-1.0.2 ? orphaned: devel/py-funcsigs > py27-mock-2.0.0 ? orphaned: devel/py-mock > py27-ndg_httpsclient-0.4.2 ? orphaned: net/py-ndg_httpsclient > py27-pbr-1.8.1_1 ? orphaned: devel/py-pbr > py27-pip-9.0.1 ? orphaned: devel/py-pip > py27-psutil-5.2.2 ? orphaned: sysutils/py-psutil > py27-pyasn1-0.2.2 ? orphaned: devel/py-pyasn1 > py27-python2-pythondialog-3.4.0 ? orphaned: devel/py-python2-pythondialog > py27-werkzeug-0.12.2 ? orphaned: www/py-werkzeug > python2-2_3 ? orphaned: lang/python2 > transmission-web-2.93_1 ? orphaned: www/transmission-web > > ... and there's no hit on the web server for the packages database. > > I do notice that none of these packages are listed in the file that tells > Poudriere what to build. It is telling me that these packages were > dependencies of something but aren't any longer? But they're still getting > built I guess because why else would Poudriere say they are in the meta.txz > or packagesite.txz files (I don't know which one)? > Just a few "have you plugged the appliance in"-style questions:
* Have you build your poudriere ports against an up-to-date ports tree, or an older version? I guess you've checked this already when reading your text above. * Have you made sure to add the @py27 to all the origins, so that poudriere doesn't build packages for a different FLAVOR, for instance, py36? (This does not explain transmission-web or python2-2_3 though) * Have you checked poudriere logs that there aren't any skips or failures? * Have you made sure that the repository has been rebuilt at the end of the poudriere run? _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
