Joerg Jaspert | 20 Sep 18:29
Favicon

DELAYED queue and upload hostname

Hi,

for the impatient people: :)

 - the DELAYED queue is back on ftp-master
 - there is ftp.upload.debian.org, please use that in future instead of
   ftp-master.debian.org

DELAYED queue
-------------
Thanks to work from Thomas Viehmann the DELAYED queue is back on the
ftp-master host, integrated with the normal processing tools. The
current service provided by Tollef[1] is probably going away sometime
soon.

To upload your files with a waiting delay before they enter Debian,
upload them into a subdirectory of the new DELAYED/ you can find at the
normal ftp upload place. Packages uploaded into the X-day (X between 0
and 15) subdirectories of that DELAYED/ will be moved into the DEFERRED
queue and won't be placed into the archive before the waiting time is
over.

To avoid confusion, the terms used are:
DELAYED  - the public ftp upload directories, reachable via DELAYED/X-day

DEFERRED - this is the place where the uploads are placed by the queue
           daemon after processing and where packages wait before they
           are moved into the incoming queue.

You can modify the queues (besides uploading packages) with *.commands
(Continue reading)

Mike Hommey | 20 Sep 18:38

Re: DELAYED queue and upload hostname

On Sat, Sep 20, 2008 at 06:30:55PM +0200, Joerg Jaspert wrote:
> ftp.upload.debian.org
> ---------------------
> To untie the upload queue from the archive DSA setup an alias to be used
> for future uploads. Please change your configuration of dput, dupload or
> whatever you use to no longer use ftp-master.debian.org but
> ftp.upload.debian.org instead.

Are default configurations for dput, etc. planned to be changed before
Lenny? (this also applies to DELAYED queue, actually)

Mike

Joerg Jaspert | 20 Sep 20:40
Favicon

Re: DELAYED queue and upload hostname

On 11514 March 1977, Mike Hommey wrote:

>> To untie the upload queue from the archive DSA setup an alias to be used
>> for future uploads. Please change your configuration of dput, dupload or
>> whatever you use to no longer use ftp-master.debian.org but
>> ftp.upload.debian.org instead.
> Are default configurations for dput, etc. planned to be changed before
> Lenny? (this also applies to DELAYED queue, actually)

I know that at least dput will get this uploaded soon, guess dupload
too.
Getting it into lenny is a decision the release team has to do. I guess
if the changes are otherwise small they will be in favor for it, but
thats up to them.

--

-- 
bye, Joerg
[...] when an Idea and a developer get laid, code awakes to the world, then
a Debian package is made and pulled in the unstable distribution[...]

Julien Cristau | 20 Sep 18:49
Favicon

Re: DELAYED queue and upload hostname

On Sat, Sep 20, 2008 at 18:30:55 +0200, Joerg Jaspert wrote:

>  - the DELAYED queue is back on ftp-master
> 
Some questions:
1) I use Tollef's DELAYED queue mostly for 0-day because it's accessible
over ssh, so I can rsync files over which is more reliable than ftp on a
bad link.  It sounds like you're removing the possibility to use that (I
know I can rsync files to some debian host and ftp from there, but
that's more manual work).
2) Will files in DELAYED be readable?  It's occasionally useful to
inspect uploads there before they reach the archive, like if somebody
forgot to send his nmu diff to the bts.

Cheers,
Julien

Joerg Jaspert | 20 Sep 20:44
Favicon

Re: DELAYED queue and upload hostname

On 11514 March 1977, Julien Cristau wrote:

> 1) I use Tollef's DELAYED queue mostly for 0-day because it's accessible
> over ssh, so I can rsync files over which is more reliable than ftp on a
> bad link.  It sounds like you're removing the possibility to use that (I
> know I can rsync files to some debian host and ftp from there, but
> that's more manual work).

Yes, the way via .d.o hosts it is.

> 2) Will files in DELAYED be readable?  It's occasionally useful to
> inspect uploads there before they reach the archive, like if somebody
> forgot to send his nmu diff to the bts.

Thomas plans to provide a similar overview as we have for NEW
packages. We could enable that to have links to the files itself.

Only problem is - if someone goes and uploads a NEW package there it
would get us in trouble, as we would distribute it before it got its
inspection if we really can do that. So if that ever happens it needs
some extra code to look if its valid to give links or not.

--

-- 
bye, Joerg
<liw> I'm kinky and perverse, but my illness is laziness

Faidon Liambotis | 20 Sep 21:44
Favicon

Re: DELAYED queue and upload hostname

Joerg Jaspert wrote:
> Only problem is - if someone goes and uploads a NEW package there it
> would get us in trouble, as we would distribute it before it got its
> inspection if we really can do that. So if that ever happens it needs
> some extra code to look if its valid to give links or not.
Well, and anyone can upload anything to his ~/public_html and have
Debian servers distribute it.

As long as it's not distributed as part of the official archive, I think
we should be mostly OK.

Not that I would disagree with having those extra checks, I'm just
saying that we shouldn't overreact with this, IMHO.

Regards,
Faidon

Joerg Jaspert | 20 Sep 22:38
Favicon

Re: DELAYED queue and upload hostname

On 11514 March 1977, Faidon Liambotis wrote:
> Joerg Jaspert wrote:
>> Only problem is - if someone goes and uploads a NEW package there it
>> would get us in trouble, as we would distribute it before it got its
>> inspection if we really can do that. So if that ever happens it needs
>> some extra code to look if its valid to give links or not.
> Well, and anyone can upload anything to his ~/public_html and have
> Debian servers distribute it.

> As long as it's not distributed as part of the official archive, I think
> we should be mostly OK.

*NO* we aren't.

> Not that I would disagree with having those extra checks, I'm just
> saying that we shouldn't overreact with this, IMHO.

If you go and export unregistered crypto foo from debian.org systems it
will get you into trouble, at least with Debian.

--

-- 
bye, Joerg
Contrary to common belief, Arch:i386 is *not* the same as Arch: any.

Daniel Baumann | 21 Sep 09:43
Favicon

Re: DELAYED queue and upload hostname

Joerg Jaspert wrote:
> If you go and export unregistered crypto foo from debian.org systems it
> will get you into trouble, at least with Debian.

simply a check for a delayed upload to be NEW or not doesn't help then
either, imagine someone uploads an already existing package to delayed
with enabled crypto (or new upstream with crypto).

you probably want to consider to not link to actual files at all.

--

-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          daniel.baumann <at> panthera-systems.net
Internet:       http://people.panthera-systems.net/~daniel-baumann/

Christian Perrier | 21 Sep 07:54
Favicon
Gravatar

Re: DELAYED queue and upload hostname

Quoting Julien Cristau (jcristau <at> debian.org):

> Some questions:
> 1) I use Tollef's DELAYED queue mostly for 0-day because it's accessible
> over ssh, so I can rsync files over which is more reliable than ftp on a
> bad link.  It sounds like you're removing the possibility to use that (I
> know I can rsync files to some debian host and ftp from there, but
> that's more manual work).

I have the same concern.

Tollef's DELAYED queue for 0-day is my "regular" upload method for
years now because I can upload with SSH, which is convenient for me in
several situations where I can't use anything but SSH (often from my
company's internal network).

Will a possibility to "upload" with SSH be added at some moment?

I recently saw mentions of /org/delayed.debian.org/ on ravel and
thought that this was the new delayed queue, but it appears that files
sent there are not processed.

So, as of now, my only method to upload when I only have SSH/scp
possible is using Tollef's old delayed queue.

Cyril Brulebois | 21 Sep 08:16
Favicon

Re: DELAYED queue and upload hostname

Christian Perrier <bubulle <at> debian.org> (21/09/2008):
> Will a possibility to "upload" with SSH be added at some moment?

Maybe it'd be feasible to teach dput/dupload how to use an @d.o machine
as “proxy”, where the files are scp'd to, and from which they're moved
to the appropriate place afterwards?

Mraw,
KiBi.

Gmane