Pkg 1.3.x Bug...

[extremelydangerous]

pkg -R does not work as expected.. here is an example, FreeBSD 10 stable, amd64, pkg version 1.3.3

pkg info -qr db6 results.... redland-1.0.17_3 serf-1.3.6_1 subversion-1.8.9_7 apr-1.5.1.1.5.3_3 squidGuard-1.4_9 cyrus-sasl-saslauthd-2.1.26_1 evolution-data-server-2.32.1_11

bogofilter-1.2.4_2

Now the command....

pkg install -fR db6

Updating repository catalogue DIST64 repository is up-to-date All repositories are up-to-date Checking integrity... done (0 conflicting) The following 1 packages will be affected (of 1037 checked):

Installed packages to be REINSTALLED:

db6-6.1.19 (forced reinstall)

look that it will reinstall db6 (which is correct) but not will reinstall the other packages as the manual says so...

Another missing thing is that pkg upgrade will not reinstall the packages that changed options or that changed direct dependencies (as pkg 1.2.X did)...

[vstakhov]

-Rf is a hack that should never ever be used in any sane package management system. We are currently discussing a better approach for this.

[extremelydangerous]

freebsd ports/UPDATING,shows that I need, pkg install -fR ====================/usr/ports/UPDATING================ AFFECTS: users of security/libgcrypt AUTHOR: pi@FreeBSD.org

libgcrypt has been updated to 1.6.1 and all shared libraries versions have been bumped. So you need to rebuild all applications that depend on libgcrypt.

portmaster -r libgcrypt

or

portupgrade -fr security/libgcrypt

or

pkg install -fR security/libgcrypt

================END============================= I build the package on the server, so I go in the client (where I will install the package...) and if I type only pkg update -y, it only updates ligcrypt So, as FreeBSD says, I need to use -fR then older version 1.2.x, would then compare the checksum of the repo with the checksum in the /var/cache/pkg/libgcrypt.... and fetch those that do not match and installs it.

New version 1.3 I have to issue the command: pkg install -fy $(pkg info -qr libgcrypt) than the pkg would update the system as needed.

[vstakhov]

Again, it is ports committers' duty to provide bump of revisions of all affected ports, not pkg's one. Nevertheless, I'm working on an update to fix this issue as well.

[bdrewery]

We do still need to support it for 1.3 though.

[extremelydangerous]

I am now using git repository for building pkg, it is in version 1.4. it got better result now, but the issue of pkg -fR still continues.. No hush people, continue the GOOD Job..