On 03.04.19 09:05, Marc Dequènes (duck) wrote: > I already asked for an unblock, explaining the situation (like why it > was blocked out of testing, why the recent fixes…), but it was rejected > without any comment on my rational: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923885
Strange, #923885 doesn't appear on https://lists.debian.org/debian-release/2019/03/threads.html (or page 2 or 3). I checked before, and now triple checked again. > I'm not convinced backporting a bunch of patches on top of 0.8-1 > (important and security fixes), which would end-up creating an untested > version would be a safe solution. 0.9.1-1 and now 0.10.1-1 have been > around for some time without problem. After reading duck's insiders rational I'm even more convinced that this is the right way to go. libmspack/0.8-1 really is problematic. The now broken "cabextract -F" is used quite often in Winetricks. Users are frequently reporting issues upstream.[1] So if we can't get 0.10.1-1 accepted, I guess I'd try to submit a patched, freeze-policy compliant version targeted only at the problem that affects winetricks. I'd be more then surprised if that results in a nearly as good and tested version as 0.10.1-1 is. 0.8-1 was superseded after only 8 days by 0.9.1-1 in unstable last November. At least winetricks users will have manually updated long time ago. > So I hope the release team will change their mind, or suggest a solution. Yes, please make an exception. Sorry for the work now, but please help us to solve this issue in a good way. Greets jre [1] https://github.com/kyz/libmspack/issues/22 https://github.com/Winetricks/winetricks/issues/1120 https://github.com/Winetricks/winetricks/issues/1154 https://github.com/Winetricks/winetricks/issues/1172 https://github.com/Winetricks/winetricks/issues/1178 https://github.com/Winetricks/winetricks/issues/1193