Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.os2.programmer.misc > #1401 > unrolled thread

Uploads of more than one release to Hobbes

Back to article view | Back to comp.os.os2.programmer.misc

Contents

  Uploads of more than one release to Hobbes "A.D. Fundum" <what.ever@neverm.ind> - 2014-06-19 10:21 +0200
    Re: Uploads of more than one release to Hobbes Lars Erdmann <lars.erdmann@arcor.de> - 2014-06-19 10:33 +0200
      Re: Uploads of more than one release to Hobbes "A.D. Fundum" <what.ever@neverm.ind> - 2014-06-19 11:35 +0200
        Re: Uploads of more than one release to Hobbes "A.D. Fundum" <what.ever@neverm.ind> - 2014-06-28 12:12 +0200
    Re: Uploads of more than one release to Hobbes "A.D. Fundum" <what.ever@neverm.ind> - 2015-02-06 03:25 +0100

#1401 — Uploads of more than one release to Hobbes

Do not upload more than one release to Hobbes. None of the uploads 
will be moved to the proposed directory. You'll have to wait until the
first released is processed.

Recently FM/2 didn't make it initially (IIRC one TXT file, two 
archives). I also cannot find DATASEEK112.ZIP nor DATASEEK113.ZIP 
(more than one), apparently two proper releases. Mirrors of Hobbes may
offer these files in their /pub/incoming directory.

Using FTP and the /pub/incoming directory instead of the website won't
work. There's a psycho's polution there, and processing files by 
Hobbes may result in lost files.

I haven't contacted the manager of the server myself, for one because 
I tend to check my own processed uploads (right processing, damaged 
archive file). 
 

--

[toc] | [next] | [standalone]

#1402

A.D. Fundum schrieb:
> Do not upload more than one release to Hobbes. None of the uploads
> will be moved to the proposed directory. You'll have to wait until the
> first released is processed.
>
> Recently FM/2 didn't make it initially (IIRC one TXT file, two
> archives). I also cannot find DATASEEK112.ZIP nor DATASEEK113.ZIP
> (more than one), apparently two proper releases. Mirrors of Hobbes may
> offer these files in their /pub/incoming directory.
>
> Using FTP and the /pub/incoming directory instead of the website won't
> work. There's a psycho's polution there, and processing files by
> Hobbes may result in lost files.

For me ftp uploads worked just fine (as long as you make sure you upload 
in binary mode). At least in the past.
But you are right: you should always wait for an upload to be processed 
before you go ahead and try to replace it.

Lars

[toc] | [prev] | [next] | [standalone]

#1403

 > For me ftp uploads worked just fine (as long as you make sure you
 > upload  in binary mode). At least in the past.

Uploading isn't the problem. Hobbes' processing is. I think it is 
related to deleting a previous version, and I think they except not 
more than one FILE NAME.* per *.TXT file.

Users/reviewers/mirrors have reported a broken file once or twice. 
Uploading it again (FTP-PM template, binary upload) solved that issue.
Perhaps their processing damaged it, albeit I also cannot download all
OS/2 LZH files (according to my ISP the file format is the problem, 
which is also a reason to not use "7ZIP" e.a.)

If http://hobbes.nmsu.edu/h-browse.php?dir=/pub/new&sort=date lists my
file, then  I download and test-unzip or compare it, even if the 
users/reviewers/mirrors are using the /pub/incoming directory.  So far
a damaged file was always reported by UNZIP.EXE; I never had to verify
the files within an archive.

 > But you are right: you should always wait for an upload to be
 > processed  before you go ahead and try to replace it.

Apparently the latest FM/2 was uploaded again, albeit the new version 
isn't the same size. Examples like DATASEEK112.ZIP and DATASEEK113.ZIP
can be found at mirror sites. Other files may be lost.

Anyway: check if Hobbes processed your file correctly, especially in 
case you uploaded more than one release (more than one TXT file and 
one matching ZIP file) in the /pub/incoming directory. That's the most
important step. Verifying your own uploaded file is an optional 
service.


--

[toc] | [prev] | [next] | [standalone]

#1404

 > Anyway: check if Hobbes processed your file correctly

BTW and FWIW, this also avoids the problem of a wrong processing 
order. If you replace /pub/what/ever/foo*.zip,  then Hobbes may also 
delete your new foo*.zip file.


--

[toc] | [prev] | [next] | [standalone]

#1466

This won't work (pseudo textfile):

Archive: bloodsweatandtears.zip
Directory: /pub/investeddays
Replaces: bloodsweatandtears.zip

One may be able to find a file called hex-a-hop* in the /pub/incoming 
directory of a Hobbes' mirror, but there's no more file called 
hex-a-hop* at Hobbes. It looks like the textfile is processed top 
first (or insert-update-delete), adding and finally deleting the same 
file. People may understand that this is an update, but a script 
won't.


--

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.os2.programmer.misc

csiph-web