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

Re: Broken uploads to mentors.debian.net



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:
> > Just had a problem with a package for sponsoring that, AFAICT, could
> > not happen with other repositories that I use, so I'm a tad concerned
> > about how it happened on m.d.n.
> > 
> > http://mentors.debian.net/debian/pool/main/x/xracer/
> > 
> > A package has been uploaded to m.d.n several times during sponsoring
> > (not uncommon) at the same version (also no uncommon) so
> > the .orig.tar.gz is unchanged (which is correct):
> > xracer_0.96.9.orig.tar.gz 26-Jun-2007 17:26  9.1M
> > 
> > Other files have been updated, as expected:
> > xracer_0.96.9-1.diff.gz   14-Jul-2007 17:28   28K  
> > xracer_0.96.9-1.dsc       14-Jul-2007 17:28  1.4K  
> > 
> > That .orig.tar.gz on m.d.n is the same as my last build:
> >  41bdf64eca9960ae8932e27e7ba2bea1 9562055 xracer_0.96.9.orig.tar.gz
> > 
> > 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. 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.

 Christoph
-- 
Peer review means that you can feel better because someone else
missed the problem, too.



Reply to: