Copntrol: severity -1 serious Cyril Brulebois <kibi@debian.org> (2020-05-03): > I can confirm this in the Debian Installer as well (spotted early April > but only debugged right now). > > Getting a little back in time and comparing what unstable used to be at > 20200401T154401Z and at 20200405T084040Z, I'm seeing these changes in > the list of udebs used to build the netboot-gtk image: > > -libcrypt1-udeb_1%3a4.4.15-1_amd64.udeb > +libcrypt1-udeb_1%3a4.4.16-1_amd64.udeb > -libdrm2-udeb_2.4.100-4_amd64.udeb > +libdrm2-udeb_2.4.101-1_amd64.udeb > -libpango1.0-udeb_1.42.4-8_amd64.udeb > +libpango1.0-udeb_1.44.7-3_amd64.udeb > -libudev1-udeb_245.2-1_amd64.udeb > +libudev1-udeb_245.4-2_amd64.udeb > -udev-udeb_245.2-1_amd64.udeb > +udev-udeb_245.4-2_amd64.udeb > > Compare attached 1/2 screenshots to see the regression. > > To make sure the pango update was responsible, I deb-reversion'ed its > udeb (taking the old udeb, faking a higher version so that it would be > preferred to the new udeb), and rebuilt the installer with unstable > from 20200405T084040Z, and I can confirm the regression disappears > (see 2+revert screenshot). I thought severity was higher than that. Reasoning for serious is that rendering looks ***bad*** plus this breaking d-i's automated testing. I'm told desktop users also suffer from that (cc-ing Corsac for a possible confirmation). Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature