Bug#942085: RFS: hijra/0.4.1-2 [RC] -- Hijri Islamic Calendar converting functions for Python

[Jeremy Bicha <jbicha@debian.org>]

‪On Sat, Nov 2, 2019 at 3:40 AM ‫أحمد المحمودي (Ahmed El-Mahmoudy)‬‎
<aelmahmoudy@users.sourceforge.net> wrote:‬
> On Tue, Oct 29, 2019 at 06:24:23AM -0400, Jeremy Bicha wrote:
> > 2. Do a binary upload of the package.
>
> Can't do binary upload since it adds a new package, and I am not a DD

Yes, I will sponsor this for you.

> > 3. Ask for auto-builds to be enabled
> > 4. After all that is done, the next upload can be source-only.
> >
> > If that sounds good with you, could you make the change and then bump
> > the Debian version number? (There is no need to try to re-use the
> > tagged version number; there are lots of higher version numbers we can
> > use!).
> ---end quoted text---
>
> I didn't bump the debian version number. Why should I do so ?

If you pushed a git release tag, it is better to just bump the
version. git does not allow updating tags easily for anyone who has
already pulled the old tag. Since there are so many available version
numbers, I highly recommend just using a higher version number when a
git tag has been pushed.

In this case, I see the new tag has already been pushed so I wouldn't
worry about it here.

Thanks,
Jeremy Bicha