Another pkg showstopper-- more information

[Steven Hartland]

Unless I'm missing something you don't actually provide any information 
about the issue your actually seeing?

I personally have already updated 10 or so boxes with a wide range of 
packages to pkg 1.4 and apart from a change with the handling of pkg 
upgrade -f <pkg>, which was an intended fix, I didn't have any problems.

So not sure what your "show stopper" is or what you think could be 
tested more thoroughly (don't forget the call for testing did go out the 
other week, so looks like there was quite a bit of opportunity to get 
involved.

     Regards
     Steve

On 12/12/2014 18:20, Jeffrey Bouquet via freebsd-ports wrote:
> Reverted to pkg, by build, and FORCE PKG REGISTER.
>
> pkgs still cannot be installed.
>
> Still stuck with ports ( however portupgrade -- non-packages -- seems to be
> working with this pkg << pkg-devel downgrade )
>
> (/ portmaster?  == no, cannot get
> handle, lock on database)  only.
>
> ..............###########...............##################...........
>
> Should pkg and/or pkg-devel be more thoroughly tested before
> release into the tree?   No other pkg usually hints at similar pkg
> system(s) breakage without a proven recovery/rollback procedure
> already documented...  similar to what portupgrade does with its
> saving of shared libraries prior to upgrade of a port.
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"