BUG: pkg_add

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

BUG: pkg_add

J.C. Roberts-3
On 4.7-Release i386, attempting to pkg_add an already installed package
results in a spurious error message:

        $ sudo pkg_add terminus-font
        No packages available in the PKG_PATH
        $

On 4.7-Current i386 (Apr 28 snap), no error is given at all:

        $ sudo pkg_add terminus-font
        $

I'm sorry I can't test on a more recent -current for you right now since
my other test box was reverted to Apr 18 while chasing intel bugs.

--
The OpenBSD Journal - http://www.undeadly.org

Reply | Threaded
Open this post in threaded view
|

Re: BUG: pkg_add

Marc Espie-2
On Mon, May 24, 2010 at 10:46:05PM -0700, J.C. Roberts wrote:
> On 4.7-Release i386, attempting to pkg_add an already installed package
> results in a spurious error message:
>
> $ sudo pkg_add terminus-font
> No packages available in the PKG_PATH
> $

The spurious message is known. I'm supposed to look at it at some point.
It's mostly a question of reordering local paths associated to package.

> On 4.7-Current i386 (Apr 28 snap), no error is given at all:
>
> $ sudo pkg_add terminus-font
> $

There are reasons for giving or not giving an error. A printed diagnostic
ought to be useful, but after all, installing something that's already there
means you want to have it.

What's going on is that I'm trying to get rid of -u/-r in obvious cases,
such as this. What's new in -current is that  when the package is already
there, instead of erroring out, pkg_add will see if it can update it.

(you see other symptoms of that when pkg_add automatically removes
partial-* packages while adding the correct one).