ncftp bug (was Re: debian updates tree structure)

1997-01-07 Thread Richard Jones
Ryan Shaw <[EMAIL PROTECTED]> typed:
> 

[snip]

> 
> i then went back to caldera to grab the 1.2.1 release thinking that it
> would be mostly links back to the 1.2 release (other than the updated
> packages).
> 
> however, all i got was a bunch of links.
> 
> here's how i have my tree setup:
> 

[pretty tree output snipped]

>   
> i downloaded everything under `rex-fixed' aka Debian-1.2.1 and ended up
> with a bunch of symlinks.
> 
> i am using ncftp to grab these.
> 
> what am i doing wrong?  (besides not ordering a cd)
> 

Its not really what you are doing wrong it is what (IMO) ncftp is doing wrong.
I've noticed that ncftp will *not* follow symlinks in at least the case
of get -CR directory_name.  I feel that whilst this may be useful behaviour in 
some circumstances, that the ommission of an option to turn this "feature" off 
is probably a bug.  It certainly makes ncftp useless for situations such as 
the sensible symlink setup of the 1.2.1 tree.  I've meant to send a mail to 
the upstream maintainer about this.  On this same topic, ncftp with get -CR 
will happily merge two files into one if you are doing simultaenous recursive 
regets on the same directory. For example get -CR dir1 executed in two 
seperate ncftp sessions on the same dir1 will for say the file dir1/filename 
create a dir1/filename on your host which is a blend of the two identical 
filenames.  methinks this is also an avoidable problem (i.e. bug).


> 
> 
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
> 



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Re: debian updates tree structure

1997-01-07 Thread Guy Maor
Ryan Shaw <[EMAIL PROTECTED]> writes:

> i then went back to caldera to grab the 1.2.1 release thinking that it
> would be mostly links back to the 1.2 release (other than the updated
> packages).
> 
> however, all i got was a bunch of links.

All the updates are in Debian-1.2-updates.  Debian-1.2.1 is just
links, some into updates and some into the Debian-1.2 tree.

The README files in these directories explain this.


Guy


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


debian updates tree structure

1997-01-07 Thread Ryan Shaw

i was looking through the debian mirror on caldera and noticed the 1.2.1
tree.  i have already downloaded an exact copy of the 1.2 tree (both the
binary-all and binary-i386 parts) but have held off changing over to
debian from redhat because of some of the posts to this list. 

i want to wait until things become more stable.

armed with the latest `problems list' that someone posted and the release
of some updates i think i am ready to take the plunge.

i then went back to caldera to grab the 1.2.1 release thinking that it
would be mostly links back to the 1.2 release (other than the updated
packages).

however, all i got was a bunch of links.

here's how i have my tree setup:

.
|-- Debian-1.2 -> rex
|-- bo
|-- contrib
|-- disks
|-- doc
|-- kernel
|-- lost+found
|-- misc
|-- non-free
|-- rex
|   |-- binary-all
|   |   |-- admin
|   |   |-- comm
|   |   |-- devel
|   |   |-- doc
|   |   |-- editors
|   |   |-- games
|   |   |-- graphics
|   |   |-- mail
|   |   |-- misc
|   |   |-- net
|   |   |-- news
|   |   |-- shells
|   |   |-- text
|   |   `-- x11
|   `-- binary-i386
|   |-- admin
|   |-- comm
|   |-- devel
|   |-- doc
|   |-- editors
|   |-- games
|   |-- graphics
|   |-- mail
|   |-- misc
|   |-- net
|   |-- news
|   |-- shells
|   |-- text
|   `-- x11
|-- tex
|   `-- tetex
|   `-- rpms
`-- unstable -> bo/

47 directories

i downloaded everything under `rex-fixed' aka Debian-1.2.1 and ended up
with a bunch of symlinks.

i am using ncftp to grab these.

what am i doing wrong?  (besides not ordering a cd)



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]