pkg_add weirdness (4.5-current)

[Thomas Pfaff-5]

Trying to add a few packages on my -current system and there's
some weirdness going on that I believe was not present before:

Script started on Fri May 22 12:34:41 2009
$ sudo pkg_add -v samba
$ sudo pkg_info -I samba
samba-3.0.34        SMB and CIFS client and server for UNIX
samba-3.0.34-ads    SMB and CIFS client and server for UNIX
samba-3.0.34-cups   SMB and CIFS client and server for UNIX
samba-3.0.34-cups-ads SMB and CIFS client and server for UNIX
samba-3.0.34-cups-ldap SMB and CIFS client and server for UNIX
samba-3.0.34-ldap   SMB and CIFS client and server for UNIX
$ sudo pkg_add -v samba-3.0.34
parsing samba-3.0.34
^C
$ echo $PKG_PATH
ftp://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/packages/amd64:http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64:ftp://ftp.uninett.no/pub/OpenBSD/snapshots/packages/amd64:ftp://ftp.dkuug.dk/pub/OpenBSD/snapshots/packages/amd64
$ sysctl kern.version
kern.version=OpenBSD 4.5-current (GENERIC.MP) #18: Fri May 22 11:42:25 CEST 2009
    tpfaff@...:/usr/src/sys/arch/amd64/compile/GENERIC.MP
$ exit
Script done on Fri May 22 12:36:00 2009

The first pkg_add should show something like

  Ambiguous: samba could be samba-3.0.33 ...

right?  The above also happens for packages like vim and emacs.

What am I missing here?

[Edho P Arief]

On Fri, May 22, 2009 at 5:53 PM, Thomas Pfaff <tpfaff@...> wrote:

> Trying to add a few packages on my -current system and there's
> some weirdness going on that I believe was not present before:
>
> Script started on Fri May 22 12:34:41 2009
> $ sudo pkg_add -v samba
> $ sudo pkg_info -I samba
> samba-3.0.34 B  B  B  B SMB and CIFS client and server for UNIX
> samba-3.0.34-ads B  B SMB and CIFS client and server for UNIX
> samba-3.0.34-cups B  SMB and CIFS client and server for UNIX
> samba-3.0.34-cups-ads SMB and CIFS client and server for UNIX
> samba-3.0.34-cups-ldap SMB and CIFS client and server for UNIX
> samba-3.0.34-ldap B  SMB and CIFS client and server for UNIX
> $ sudo pkg_add -v samba-3.0.34
> parsing samba-3.0.34
> ^C
> $ echo $PKG_PATH
>

ftp://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/packages/amd64:http://ftp.open
bsd.org/pub/OpenBSD/snapshots/packages/amd64:ftp://ftp.uninett.no/pub/OpenBSD
/snapshots/packages/amd64:ftp://ftp.dkuug.dk/pub/OpenBSD/snapshots/packages/a
md64
> $ sysctl kern.version
> kern.version=OpenBSD 4.5-current (GENERIC.MP) #18: Fri May 22 11:42:25 CEST
2009
> B  B tpfaff@...:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> $ exit
> Script done on Fri May 22 12:36:00 2009
>
> The first pkg_add should show something like
>
> B Ambiguous: samba could be samba-3.0.33 ...
>

perhaps you meant

pkg_add -i pkgname

...?

> right? B The above also happens for packages like vim and emacs.
>
> What am I missing here?
>
>



--
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

[Thomas Pfaff-5]

On Fri, 22 May 2009 22:56:33 +0700
Edho P Arief <edhoprima@...> wrote:

> On Fri, May 22, 2009 at 5:53 PM, Thomas Pfaff <tpfaff@...> wrote:
> > Trying to add a few packages on my -current system and there's
> > some weirdness going on that I believe was not present before:
> >
> > Script started on Fri May 22 12:34:41 2009
> > $ sudo pkg_add -v samba
> > $ sudo pkg_info -I samba
> > samba-3.0.34 B  B  B  B SMB and CIFS client and server for UNIX
> > samba-3.0.34-ads B  B SMB and CIFS client and server for UNIX
> > samba-3.0.34-cups B  SMB and CIFS client and server for UNIX
> > samba-3.0.34-cups-ads SMB and CIFS client and server for UNIX
> > samba-3.0.34-cups-ldap SMB and CIFS client and server for UNIX
> > samba-3.0.34-ldap B  SMB and CIFS client and server for UNIX
> > $ sudo pkg_add -v samba-3.0.34
> > parsing samba-3.0.34
> > ^C
>
> perhaps you meant
>
> pkg_add -i pkgname
>

That enters interactive mode and I'm presented with the correct
choices (as listed above) so, sure, that works.  Without the -i
option, however, pkg_add just terminates.  This is on May 18th
userland.  On another system of mine running February 28th user-
land the pkg_add behaviour is different, and as I would expect:

  Feb28$ sudo pkg_add vim
  Ambiguous: vim could be vim-7.2.77-gtk2 vim-7.2.77-no_x11
  Feb28$

  May18$ sudo pkg_add vim
  May18$

As far as I can tell, both systems are configured the same with
respect to the package manager (Feb28 is i386 and May18 is amd64
though).

[Thomas Pfaff-5]

On Fri, 22 May 2009 19:21:14 +0200
Thomas Pfaff <tpfaff@...> wrote:

> On Fri, 22 May 2009 22:56:33 +0700
> Edho P Arief <edhoprima@...> wrote:
> >
> > perhaps you meant
> >
> > pkg_add -i pkgname
>
> That enters interactive mode and I'm presented with the correct
> choices (as listed above) so, sure, that works.  Without the -i
> option, however, pkg_add just terminates.  This is on May 18th
> userland.  On another system of mine running February 28th user-
> land the pkg_add behaviour is different, and as I would expect:
>
>   Feb28$ sudo pkg_add vim
>   Ambiguous: vim could be vim-7.2.77-gtk2 vim-7.2.77-no_x11
>   Feb28$
>
>   May18$ sudo pkg_add vim
>   May18$
>
> As far as I can tell, both systems are configured the same with
> respect to the package manager (Feb28 is i386 and May18 is amd64
> though).
>

I just upgraded the "Feb28" system to a May 18th snapshot (i386)
and the pkg_add behaviour has changed to what I described above.

Surely this is not an intended change?

[Thomas Pfaff-5]

On Sat, 23 May 2009 11:44:30 +0200
Thomas Pfaff <tpfaff@...> wrote:

> >   Feb28$ sudo pkg_add vim
> >   Ambiguous: vim could be vim-7.2.77-gtk2 vim-7.2.77-no_x11
> >   Feb28$
> >
> >   May18$ sudo pkg_add vim
> >   May18$
> >
>
> I just upgraded the "Feb28" system to a May 18th snapshot (i386)
> and the pkg_add behaviour has changed to what I described above.
>

So, for the record; the old behaviour is back again.  Thanks.