On 26/11/2023 11:36, Chris Boot wrote:
On 26/11/2023 10:56, Chris Boot wrote:
Any way to reduce possible breakage, or to detect and fix it before
the transition starts? Like rebuilding rdeps, or checking rdep
autopkgtests?
I'll go an do some rebuilds now and see how they go. If any breakage
occurs it will be obvious at build time.
The status of the rdeps (list taken from the tracker):
connman: OK
network-manager: OK
pptpd: https://bugs.debian.org/1056898
sstp-client: https://bugs.debian.org/1056900
network-manager-fortisslvpn: https://bugs.debian.org/1056901
network-manager-l2tp: OK
network-manager-pptp: OK
network-manager-sstp: https://bugs.debian.org/1056903
All that's left now is pptpd (with an offer from Christoph to upload
when ready) and network-manager-fortisslvpn (with commits fixing the
issues upstream, but no upstream release).
In the mean time, #1065940 has become a blocker for the time_t
transition. I think I'd rather upload 2.5.0 and break
network-manager-fortisslvpn than just the patch to fix the breakage.
Would the release team be happy to continue with this transition?
Thanks,
Chris
--
Chris Boot
bo...@debian.org
