Re: dput problem: Ancient sha256sum? [and 1 more messages]

[dettus <dettus@dettus.net>]

Hello.

Thanks to you guys, it worked.
It actually did all of what you suggested. ;)

I removed my package, and reuploaded it as dmagnetic_0.17-1. This time,
it worked. Now, I have to find a sponsor. Any volunteers?



Hi.

Your upload of the package 'dmagnetic' to mentors.debian.net was
successful. Others can now see it. The URL of your package is:
https://mentors.debian.net/package/dmagnetic

The respective dsc file can be found at:
https://mentors.debian.net/debian/pool/main/d/dmagnetic/dmagnetic_0.17-1.dsc

If you do not yet have a sponsor for your package you may want to go to
https://mentors.debian.net/sponsors/rfs-howto/dmagnetic
and set the "Seeking a sponsor" option to highlight your package on the
welcome page.

You can also send an RFS (request for sponsorship) to the debian-mentors
mailing list. Your package page will give your suggestions on how to
send that mail.

Good luck in finding a sponsor!

Thanks,

-- mentors.debian.net

On 8/29/19 5:07 PM, Ian Jackson wrote:
> 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.