#1034016 unblock (pre-approval): debos/1.1.1-2.1

#1034016#5
Date:
2023-04-06 13:51:38 UTC
From:
To:
Hello release-team,

I'm looking for a pre-approval for an unblock of my NMU of debos,
which contains 3 commits cherry-picked from upstream.

The main bug to fix is https://bugs.debian.org/1027787
The current version of debos in bookworm is not compatible with
bookworm. The maintainer promised me to deal with this if I
submitted an upstream PR where he merged my patch for it,
but apparently never found the time to update the debian
package.

While at it I also cherry-picked 2 documentation fixes.

I'm attaching a debdiff, but if you'd like to avoid reading
patch-in-patch these are the commits:
https://github.com/go-debos/debos/commit/18998ffaf78321e111d9823b3180eca3fa4593f6
https://github.com/go-debos/debos/commit/f4ff78305513a90eca089e33f7bba35bffa96bd1
https://github.com/go-debos/debos/commit/c8c5075853aab9e1ac6ae07a3a7c2b070aa38a62


unblock debos/1.1.1-2.1

#1034016#12
Date:
2023-04-06 14:22:19 UTC
From:
To:
Please go ahead

Cheers

#1034016#17
Date:
2023-04-06 15:37:30 UTC
From:
To:
Hi Andreas,

As the upstream maintainer, I can just tag a new version upstream as 1.1.2 & pick that in Debian.
Then I hope it can flow into bookworm?

The past few months have been... quite crazy in my personal life so I haven't gotten around to doing this as yet. Huge apologies for that, it is on my radar this week.

Hope that is acceptable to you?

Thanks,

Chris

#1034016#22
Date:
2023-04-06 16:45:54 UTC
From:
To:
Hello Chris,

I wonder if the release team will accept a new upstream release at this
point in the freeze.... We're pretty deep into the hard freeze at this
point (but I don't have enough insight into how the release team works
these days, it seems much more relaxed than in the old times where I was
more involved and basically any extra character would get you a NACK,
specially an "unneccessary" upstream version number change).

Do you have time to do all the work and still accept a potential NO from
the release team? Please be honest to yourself.

IMHO it feels much safer to just go with a targeted upload (which is now
also already approved), but if you feel strongly about it and also think
you have time to pursue a new release then just send me a NACK on the
NMU (ASAP! I'm ready to upload *now*) and I will not pursue it.

No need to apologize. We're all busy sometimes and that's why we have
NMUs so we can help each other out. (I've also been quite busy or the
NMU would have happened much sooner in the release cycle.)
Thanks for all the work you have had time to do!

Regards,
Andreas Henriksson

PS. Feel free to ignore my NMU and just upload the new upstream release
once we're past the freeze/release and the development opens up again.

#1034016#27
Date:
2023-04-06 16:52:32 UTC
From:
To:
Hi Andreas,
will upload the new version into unstable once development opens.

How does that sound?

PS: Can you push your source to salsa?


Thanks!
Chris

#1034016#32
Date:
2023-04-06 18:10:39 UTC
From:
To:
Hello,
[...]

Pushed to salsa (incl. tag)!

dput new version, so should hopefully he accepted for unstable soon!

Thanks for the quick followup!

Regards,
Andreas Henriksson

#1034016#37
Date:
2023-04-08 20:10:12 UTC
From:
To:
Hi,

done.

Paul