New pkg_* woes

	Free Downloads, Community Forum, FAQs and Developer Resources

Make /Tools Your Home | Link to us

Today's posts | Posts since last visit | Most Active Topics

All Forums	Register	Login	Search	Subscriptions	My Profile	Inbox
Tool Warehouse	FAQs	Resources	Help	Member List	Address Book	Logout

New pkg_* woes

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [SFU / Interix / SUA Technology] >> SFU / Interix - Getting Started >> New pkg_* woes

Page: [1]

Message

<< Older Topic Newer Topic >>

New pkg_* woes - Sep. 29, '06, 7:13:58 PM

dotequals

Posts: 4
Joined: May 10, '06,
Status: offline

***UPDATE*** The problem appears to have cleared itself up; perhaps my connection was bad, or the ftp server was down temporarily. Thanks anyway!

I've set up Interix UNIX Tools on several machines in the past, but haven't done so in several months and as such I'm a bit rusty.

Since the last time I did this the sanctioned method for installing packages has changed from pkg_add to pkg_update. I think I've gotten over the confusion of this, but I'm still having some trouble:

I'm trying to install openssh and both "pkg_update -L openssh" and "pkg_add -v ftp://ftp.interopsystems.com/pkgs/3.5/openssh-current-bin.tgz" fail.

Relevant errors:
From pkg_update

bash-3.00$ pkg_update -L openssh
Starting checks for updates
Percent complete/package:
100% |**************************************************|          opensshftp: f
tp.interopsystems.com: temporary failure
ftp: Can't connect or login to host `ftp.interopsystems.com'
grep: Cannot open file '/var/db/pkg/openssh-*-bin/+CONTENTS': No such file or di
rectory

Done.

From pkg_add

bash-3.00$ pkg_add -v ftp://ftp.interopsystems.com/pkgs/3.5/openssh-current-bin
.tgz
Trying to fetch ftp://ftp.interopsystems.com/pkgs/3.5/openssh-current-bin.tgz.
Extracting from FTP connection into /tmp/instmp.uLlikbB475

gzip: stdin: unexpected end of file
tar: End of archive volume 1 reached
tar: Sorry, unable to determine archive format.
tar command returns 1 status
pkg_add(openssh-current-bin): URL `ftp://ftp.interopsystems.com/pkgs/3.5/openssh
-current-bin.tgz' has unknown hostname part!
pkg_add(openssh-current-bin): unable to fetch `ftp://ftp.interopsystems.com/pkgs
/3.5/openssh-current-bin.tgz' by URL
pkg_add(openssh-current-bin): 1 package addition(s) failed

I've checked my .netrc and it seems right, so I figure I must be doing something wrong, but what?

Thanks for the help.

Max

< Message edited by dotequals -- Sep. 30, '06, 12:43:19 AM >

Post #: 1

RE: New pkg_* woes - Sep. 30, '06, 5:27:12 AM

Rodney

Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline

I know that things have resolved for you as I write this, but I just wanted to
give an FYI about pkg_add versus pkg_update.

If you want to you can still use pkg_add. There's no problem doing this.
You'll have to type more characters, but that's up to you

The aim of getting people to use pkg_update is to ease the problems that
people have now with multiple versions (3.5, 5.2 and 6.0) plus multiple platforms
(x86, authenicatedamd, EM64T and soon IA64). There's a lot of overlap for the
packages, but there are some that are different (and likely more in the future).
There are also extra features so that downloads are minimized by comparing version
numbers, dates, etc. We save terabytes of download per day because of this and
it's faster for (you) the human installer -- particularly if you have mulitple machines.

(in reply to dotequals)