[Debichem-devel] Bug#1097201: libint2: diff for NMU version 2.7.2-1.2

[Michael Banck]

Hi,

(dropping the bug report)

On Wed, Oct 08, 2025 at 10:24:36PM +0200, Santiago Vila wrote:
> > > Thanks for your work, but this NMU is disruptive, because salsa
> > > currently contains a new upstream version
> > 
> > The time_t NMU from February 2024 is already missing in salsa.
> > 
> > > which presumably also fixes the gcc-15 problem:
> > >...
> > > Date:   Sun Sep 22 10:59:11 2024 +0200
> > 
> > This was a year ago.
> 
> Big oops! The "new" release (according to debian/changelog)
> is actually from "Sun, 30 Oct 2022"!
> 
> Ok, I'm open for ideas from other team members regarding how we should
> handle the history in salsa in cases like this. I am a big fan of
> linear history when it is possible to do so, but I understand that such
> thing is not always possible.
> 
> (If this was not a team-maintained package, I would force-push
> as needed to match the archive).

Assuming the NMU is good (which I guess, cause it's from Adrian, but I
don't have time to test it right now), we can just acknowledge that as
well, and push it between the last NMU and the current changelog entry.

If you prefer a force-push, I can live with that as well.

There's a new 2.11 release anyway, and I think this (or 2.10) is finally
going to allow to build both CP2K and PSI4 against it, so it was on my
list of things to look at once I got time.


Michael