Mattia Rizzolo writes ("Re: dput problem: Ancient sha256sum?"):
> That said, the fact that your .orig.tar.gz changed is an indicator
> that you are doing something fishy and you should double check your
> workflow. You should not be able to accidentally end up with a
> different .orig.tar.gz.
I agree with this. That is, Thomas, I would advise you to try to
understand what you did differently to generate the two different orig
tarballs.
When you know why they are different you will know which one you want.
If it's the old one, download it from mentors and arrange for your
re-upload to use it. If it's the new one, delete your upload as Peter
Pentchev suggests and then you can upload your new .orig.
I do have to disagree with something Peter writes:
Peter Pentchev writes ("Re: dput problem: Ancient sha256sum?"):
> [...] Since dmagnetic is a package that is not in
> Debian yet, the first version to be uploaded must have a -1 revision;
> rebuild your package as 0.17-1 and try to upload it again. Then
> mentors.d.n will recognize that you are trying to upload a new version
> of the same package and (unlike the actual Debian archive) will allow
> you to replace the original upstream tarball.
As far as I'm aware there is no requirement for the first version of a
package uploaded to Debian to have a -1 revision. There is certainly
no general requirement that first upload of any particular upstream
version has to have a -1 revision, or even that it must have a -1 or
-0.1 revision.
I think the practice of reusing version numbers for different packages
is confusing. It leads to mistakes, and should be deprecated.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
