Hi I do not know the details of i2pd package. For stretch we generally update only due to security reasons. There are exceptions, but it needs to be a really good one. Like "if we do not update the package is useless or severely crippled". What you describe does not strike me as something that warrant an update. But maybe there is more to it than I understood. As I said I'm not someone who knows i2pd. Another thing is that you also need to convince stable release managers first, because we do not want to update oldstable if not stable is updated.
Cheers // Ola On Sun, 23 May 2021 at 17:22, R4SAS <r4...@i2pd.xyz> wrote: > Hello. > > I'm one of i2pd [1] developers/internal maintainer. > > In next release (2.39.0) we will disable LeaseSet1 publishing and > planning to switch to LeaseSet2. > > Initial support of LS2 was added in 2.23.0, which currently in stretch, > but after 2 years too much changes were done, race conditions fixed, and > encryption types added. Also old transport NTCP is deprecated few > releases ago (totally removed from sources). > > That's why we want to know, is it possible make SRU (stable release > update, as descripted on Ubuntu) for package in stretch? > > [1] https://github.com/PurpleI2P/i2pd > -- --- Inguza Technology AB --- MSc in Information Technology ---- | o...@inguza.com o...@debian.org | | http://inguza.com/ Mobile: +46 (0)70-332 1551 | ---------------------------------------------------------------
