Le Sun, Oct 12, 2025 at 01:28:59AM +0500, Syed Shahrukh Hussain a écrit : > > To keep in mind for next time: please don’t force push to any of the > > three main branches (master, upstream, pristine-tar) of the salsa > > repository. It’s OK to fix review feedback in dedicated commits, even if > > the changelog entry was already set. > Noted. > I apologize for the inconvenience. No problem, sponsored uploads are the best time to make mistakes and learn from them. > It was one of a kind, i made mistake in the comment message which was > "upload to unstable". A convention i observed when package is changed from > UNRELEASED to unstable in changelog. > It wouldn't make any sense if i am fixing issues > afterwards. It’s OK if the commit with "upload to unstable" is not the one tied to the actual upload, only the debian/xxx tag shoud be in sync with what is sent to the archive (actually even that tag is only a convention, but it’s one I strongly suggest following). If you look at this example, I too did a mistake and made the "0.49.0-1 release targeting Debian unstable" commit a bit too early, not noticing an error I then fix in the following commit: https://salsa.debian.org/games-team/openmw/-/commits/debian/0.49.0-1 Don’t try too hard to get a perfect looking git history, what matters most is what ends up in the debian/changelog file. This is the only kind of history the users of that package are going to see.
Attachment:
signature.asc
Description: PGP signature