Control: package mailman3-web Control: severity -1 important Hi again,
Jonas Meurer: > Christian Ehrhardt: >> while analyzing the dependencies of the mailman3 stack I found this >> change [1] changing it from sassc to ruby-sass. >> >> As you already know I'm discussing with upstream on the option to >> eliminate the compressors all together, but if we fail at least for >> sass we seem to have a maintenance issue. >> According to upstream [2] ruby-sass is deprecated and unmaintained in 11 >> days. >> >> The changelog does not hold why the switch was made - so I'm a bit lost. > > To be honest, I don't remember anymore, either. I vaguely remember some > problem with sassc not being available ins stretch (for backports) or > something like that, but looking at it now, all looks good. > >> But could we switch back to sassc for longer upstream support? >> If so a change should be as easy as [3] > > Thanks a lot for the merge request and bugreport. It looks sane to me > and we will merge it shortly. > > Since you asked: my personal preference is exactly what you did: provide > a merge request on Salsa and file an accompanying bugreport that links > to the merge request :) > >> While for the serviceability of e.g. security issues it would be nice >> to have it in buster I know it is too late :-/ > > Let's see. Since it should be a non-invasive change and one with > security implications, we might get an unblock exception for that one by > the Release Team. I'll wait for them to accept my current unblock > request for mailman-suite/0+20180916-7 and try to get this change in > afterwards. I finally found time to look into it and I definitely would like to get this into Buster due to the security implications. I'll raise the severity of the bugreport and ask for an unblock request shortly. Cheers jonas
signature.asc
Description: OpenPGP digital signature
