[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Broken uploads to mentors.debian.net

On Sun, 15 Jul 2007 22:41:57 +0200
Christoph Haas <haas@debian.org> wrote:

> On Sun, Jul 15, 2007 at 12:31:29AM +0200, I wrote:
> > On Sat, Jul 14, 2007 at 10:42:52PM +0100, Neil Williams wrote:
> > > 
> > > However, the .dsc file uploaded to m.d.n references a
> > > different .orig.tar.gz: 
> > > 8287bfd7e9ef9a507024bf34761791d8 9562064 xracer_0.96.9.orig.tar.gz
> >
> > I'll look into this later today and probably fix it.
> Now I checked the import script at mentors.debian.net and also did a
> few test uploads. If a 'dsc' file mentions an orig tarball then the
> old tarball is replaced in every case. So if the package maintainer
> would upload a package built with "-sa" (including the orig tarball
> even with non-1 revisions) then everything should work well.
> I have no good explanation for the situation Neil mentioned though.

It turned out to be due to a broken upload - an FTP connection timeout.
(I've been busy finalising the actual upload.)

The maintainer used nemesis to keep the next connection alive.

> The package maintainer must have uploaded a package with an orig
> tarball. But then the orig tarball was changed and an upload without
> an orig tarball was done that mentioned the orig tarball though.
> How come the .dsc file mentions an orig file that is not uploaded? All
> files mentioned in the .dsc file must be uploaded. I'm confused.

Is there some way of detecting a failed FTP upload and removing the
corrupted files?


Neil Williams

Attachment: pgpSwR2LOCMOk.pgp
Description: PGP signature

Reply to: