> > 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). Thanks.
