Re: reuploading a source package (same version)
Too late. I did request for ROM and it was executed quite quickly. I
just re-uploaded paraview:
$ dupload paraview_3.8.1-2_amd64.changes
dupload note: no announcement will be sent.
Checking signatures before upload......signatures are ok
Uploading (ftp) to ftp.upload.debian.org:/pub/UploadQueue/
[ job paraview_3.8.1-2_amd64 from paraview_3.8.1-2_amd64.changes
paraview_3.8.1-2_amd64.deb, size ok, md5sum ok, sha1sum ok, sha256sum ok
paraview_3.8.1-2.diff.gz, size ok, md5sum ok, sha1sum ok, sha256sum ok
paraview_3.8.1-2.dsc, size ok, md5sum ok, sha1sum ok, sha256sum ok
paraview_3.8.1-2_amd64.changes ok ]
Uploading (ftp) to anonymous-ftp-master (ftp.upload.debian.org)
[ Uploading job paraview_3.8.1-2_amd64
paraview_3.8.1-2_amd64.deb 39316.4 kB, ok (371 s, 105.97 kB/s)
paraview_3.8.1-2.diff.gz 24.6 kB, ok (1 s, 24.58 kB/s)
paraview_3.8.1-2.dsc 1.8 kB, ok (1 s, 1.77 kB/s)
paraview_3.8.1-2_amd64.changes 1.5 kB, ok (1 s, 1.53 kB/s) ]
On Tue, Feb 22, 2011 at 3:13 PM, Yaroslav Halchenko <firstname.lastname@example.org> wrote:
> why not to augment upstream version? e.g. 3.8.1+1 ? additionally you
> could add a note to debian/README.Debian-source or just debian/README
> describing the WTF, or just mention in the changelog entry... I see no
> objective reason to mess with ftp removals or waiting for a new release
> On Tue, 22 Feb 2011, Sylvestre Ledru wrote:
>> Le mardi 22 février 2011 à 09:58 +0100, Mathieu Malaterre a écrit :
>> > Hi,
>> > I am reading the following bug:
>> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611840
>> > I clearly did the first upload:
>> > http://packages.qa.debian.org/p/paraview/news/20100819T093347Z.html
>> > However I do not understand what could have happen that I did not
>> > upload paraview 3.8.1 tarball (maybe I used a release candidate...).
>> > Anyway to solve this issue I need to re-upload the same package
>> > (same version!), but I fear ftp will drop it since md5sum will not
>> > match.
>> > does anyone knows what to do in this case ?
>> I guess you would have to ask for a removal and then reupload it
>> (however, it might have to go through NEW again).
>> Otherwise, the lazy way would be to wait for a new upstream release.
> Keep in touch www.onerussian.com
> Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic