Re: PkgCheck.pm can't locate "new"
On Mon, Feb 10, 2014 at 05:22:15PM -0800, Rob Fabry wrote: >so these problems are not about using URLs or FTP sites to find >packages over >the net, but packages that are present locally on the machine. I never said "Url over the net". Local files also have urls. >Is is something I could do simply, by downloading it on another machine >and running some command? Just set your PKG_PATH, it can point to local dirs.
Re: PkgCheck.pm can't locate "new"
On Sun, Feb 09, 2014 at 07:21:18PM -0800, Rob Fabry wrote: > I'm trying to install OpenBSD on a new machine so I can learn how > to setup a > router, but running into a strange problem. > > A Supermicro 5015A-H with Intel > Atom 330 at 1.6 GHz > > When I tried to install the unbound package, it can't > find it > (even though it's in the directory, and the shell autocompletes > the > name) > > # pkg_add unbound_1.4.20.tgz > Can't find package unbound_1.4.20.tgz > (adding multiple -v doesn't elaborate on the problem) > > since the pkg_add > didn't work, I thought I'd try some > # pkg_check > Packing-list sanity: ok > Direct > dependencies: ok > Reverse dependencies: ok > Files from packages: ok > Can't locate > object method "new" via package "OpenBSD::PkgSpec" at > ?/usr/libdata/perl5/OpenBSD/PkgCheck.pm line 713 > Yes, it looks like an issue in pkg_check on OpenBSD 5.4 :) Go install the pkglocatedb package manually, from the location of the error, it's almost certainly that. (when pkg_check finds some files that don't belong to any package, it should go recheck thru pkglocatedb where those are supposed to live---this is most often due to fsck issues where files are there but not registered and pkg_check will use pkglocatedb to locate the packages it should repair)
Re: PkgCheck.pm can't locate "new"
On Mon, Feb 10, 2014 at 02:28:49PM +0100, Marcus MERIGHI wrote: > Hello Rob, > > from pkg_add(1) > PKG_PATH If a given package name cannot be found, the directories > named by PKG_PATH are searched. It should contain a series > of entries separated by colons. Each entry consists of a > directory name. URL schemes such as FTP, HTTP, HTTPS, or > SCP are also appropriate. The current directory may be > indicated implicitly by an empty directory name, or > explicitly by a single period (`./'). > > from pkg.conf(5) > installpath URL to package repository updated during installation. > Used for accessing packages if the environment variable > PKG_PATH is not defined and no further options are defined. > > Bye, Marcus The url usage in pkg_add has a few issues those WON'T be fixed before 5.5. Eventually, it should work much better.
Re: PkgCheck.pm can't locate "new"
On 10 February 2014 15:26, Josh Grosse wrote: > On 2014-02-09 22:21, Rob Fabry wrote: >> >> I'm trying to install OpenBSD on a new machine so I can learn how >> to setup a >> router, but running into a strange problem. >> >> A Supermicro 5015A-H with Intel >> Atom 330 at 1.6 GHz >> >> When I tried to install the unbound package, it can't >> find it >> (even though it's in the directory, and the shell autocompletes >> the >> name) >> >> # pkg_add unbound_1.4.20.tgz >> Can't find package unbound_1.4.20.tgz >> (adding multiple -v doesn't elaborate on the problem) > > > Hi. pkg_add(1) uss $PKG_PATH, unless you use a directory path. Try adding > the directory: > > # pkg_add ./unbound_1.4.20.tgz Bummer, you are right. That works too. Regards, Ville
Re: PkgCheck.pm can't locate "new"
Hello Rob, from pkg_add(1) PKG_PATH If a given package name cannot be found, the directories named by PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. The current directory may be indicated implicitly by an empty directory name, or explicitly by a single period (`./'). from pkg.conf(5) installpath URL to package repository updated during installation. Used for accessing packages if the environment variable PKG_PATH is not defined and no further options are defined. Bye, Marcus robfabr...@yahoo.com (Rob Fabry), 2014.02.10 (Mon) 04:21 (CET): > I'm trying to install OpenBSD on a new machine so I can learn how > to setup a > router, but running into a strange problem. > > A Supermicro 5015A-H with Intel > Atom 330 at 1.6 GHz > > When I tried to install the unbound package, it can't > find it > (even though it's in the directory, and the shell autocompletes > the > name) > > # pkg_add unbound_1.4.20.tgz > Can't find package unbound_1.4.20.tgz > (adding multiple -v doesn't elaborate on the problem) > > since the pkg_add > didn't work, I thought I'd try some > other pkg commands > > # pkg_info > unbound_1.4.20.tgz > (works fine) > > # pkg_check > Packing-list sanity: ok > Direct > dependencies: ok > Reverse dependencies: ok > Files from packages: ok > Can't locate > object method "new" via package "OpenBSD::PkgSpec" at > ?/usr/libdata/perl5/OpenBSD/PkgCheck.pm line 713 > > I get the same error when I > try: > A. OpenBSD 5.4 amd64 install54.iso > B. OpenBSD 5.4 amd64 separate > 54.tgz > C. OpenBSD 5.3 amd64 install54.iso > D. OpenBSD 5.4 i386 > install54.iso > > Any thoughts on what is this problem with finding method "new" > ? > > > !DSPAM:52f8d14f181365490293996!
Re: PkgCheck.pm can't locate "new"
On 10 February 2014 05:21, Rob Fabry wrote: > I'm trying to install OpenBSD on a new machine so I can learn how > to setup a > router, but running into a strange problem. > > A Supermicro 5015A-H with Intel > Atom 330 at 1.6 GHz > > When I tried to install the unbound package, it can't > find it > (even though it's in the directory, and the shell autocompletes > the > name) > > # pkg_add unbound_1.4.20.tgz > Can't find package unbound_1.4.20.tgz > (adding multiple -v doesn't elaborate on the problem) > Any thoughts on what is this problem with finding method "new" > ? Hello Rob, please read http://www.openbsd.org/faq/faq15.html. In addition what does this command print? $ env |grep PKG_PATH *Hint it's covered in here* http://www.openbsd.org/faq/faq15.html#Easy. Yet another hint: http://www.openbsd.org/faq/faq15.html#PkgInstall. And finally the answer, you must use the absolute path when installing packages without the PKG_PATH set. Regards, Ville
Re: PkgCheck.pm can't locate "new"
On 2014-02-09 22:21, Rob Fabry wrote: I'm trying to install OpenBSD on a new machine so I can learn how to setup a router, but running into a strange problem. A Supermicro 5015A-H with Intel Atom 330 at 1.6 GHz When I tried to install the unbound package, it can't find it (even though it's in the directory, and the shell autocompletes the name) # pkg_add unbound_1.4.20.tgz Can't find package unbound_1.4.20.tgz (adding multiple -v doesn't elaborate on the problem) Hi. pkg_add(1) uss $PKG_PATH, unless you use a directory path. Try adding the directory: # pkg_add ./unbound_1.4.20.tgz
PkgCheck.pm can't locate "new"
I'm trying to install OpenBSD on a new machine so I can learn how to setup a router, but running into a strange problem. A Supermicro 5015A-H with Intel Atom 330 at 1.6 GHz When I tried to install the unbound package, it can't find it (even though it's in the directory, and the shell autocompletes the name) # pkg_add unbound_1.4.20.tgz Can't find package unbound_1.4.20.tgz (adding multiple -v doesn't elaborate on the problem) since the pkg_add didn't work, I thought I'd try some other pkg commands # pkg_info unbound_1.4.20.tgz (works fine) # pkg_check Packing-list sanity: ok Direct dependencies: ok Reverse dependencies: ok Files from packages: ok Can't locate object method "new" via package "OpenBSD::PkgSpec" at /usr/libdata/perl5/OpenBSD/PkgCheck.pm line 713 I get the same error when I try: A. OpenBSD 5.4 amd64 install54.iso B. OpenBSD 5.4 amd64 separate 54.tgz C. OpenBSD 5.3 amd64 install54.iso D. OpenBSD 5.4 i386 install54.iso Any thoughts on what is this problem with finding method "new" ?
