[Debichem-devel] The drawbacks of dummy changelog entries

[Santiago Vila]

Hello.

I've just made a team upload of dbcsr, as it fails in Salsa CI:

https://salsa.debian.org/debichem-team/dbcsr/-/pipelines/829636

and also in some of my autobuilders:

     -------------------------------------------------------------------
     There are not enough slots available in the system to satisfy the 2
     slots that were requested by the application:
     
       ./dbcsr_tensor_test
     
       Either request fewer procs for your application, or make more slots
       available for use.
     -------------------------------------------------------------------

While doing so I noticed that there was a dummy changelog entry
for 2.8.0-2:

dbcsr (2.8.0-2) UNRELEASED; urgency=medium

Such dummy changelog entries make tracker.debian.org to signal
that there is something wrong with the repo:

https://tracker.debian.org/pkg/dbcsr

version in VCS is newer than in repository, is it time to upload?

So, I'm not sure where this tradition comes from, maybe from the time
we did not have this tracker thing which takes care of repo health,
but I don't see that there is a clear benefit in doing those dummy
changelog entries. (So I hope you forgive me if I don't make them).

Thanks.