On 6/5/2025 9:59 AM, Chuck Zmudzinski wrote: > On 6/5/2025 4:30 AM, Ramiro Aceves wrote: >> >> >> El 4/6/25 a las 21:23, Chuck Zmudzinski escribió: >>> Hello, >>> >>> I have two packages I built and installed from the pkgsrc source tree, >>> xenkernel418-20250521 and xentools418-20250521. I configured pkgin to read >>> my repository of locally built packages first in the list of repositories >>> /usr/pkg/etc/pkg/repositories.conf. >>> >>> In the remote repository, the version of the packages is about two months >>> older: xenkernel418-20241221 xentools418-20241221 >>> >>> With the newer versions from my local repository already installed, I run >>> (after running pkgin update): >>> >>> ave$ sudo pkgin upgrade >>> Password: >>> calculating dependencies...done. >>> >>> 2 packages to upgrade: >>> xenkernel418-20241221 xentools418-20241221 >>> >>> 0 to remove, 0 to refresh, 2 to upgrade, 0 to install >>> 0B to download, 2387K of disk space will be freed up >>> >>> proceed ? [Y/n] >>> >>> So I say n because I don't want to downgrade the packages. >>> >>> This is very annoying if there are other packages I want to upgrade. I >>> spent a few hours figuring out how to tell pkgin not to upgrade the >>> xenkernel and xentools packages because it always wants to downgrade them, >>> but so far no joy. >>> >>> Please help. >>> >>> Thanks. >> >> Hi, perhaps this thread helps. I asked a similar question. >> >> https://mail-index.netbsd.org/pkgsrc-users/2025/05/18/msg041575.html >> >> Just if it helps. > > Yes that thread might help. So far I discovered the only way to upgrade > the packages back to the version in my local repository that pkgin > downgraded to the version in the official repositories is by using > pkg_add instead of pkgin. > > I see the aforementioned thread mentions a PKGPATH value, I have > not yet investigated trying to tweak that. So maybe I can use pkgin > instead of pkg_add for my local packages by adjusting PKGPATH. I > will post here again with the fix if I succeed in finding a fix. >
I can see that the PKGPATH cannot be easily changed except by making a copy of the package in a different directory which is probably more complexity than what I am looking for. I think the best way to handle this for my use case is just to use pkg_add when I am using a package built locally instead of from the latest pkgsrc-YYYYQn branch. I have my system configured to build packages locally from MAIN so I can get the latest versions by building from source if needed or if I need to test some changes to a package. In all other cases, I just want to use the precompiled packages from the latest pkgsrc-YYYYQn branch. Chuck
