Re: Bug#1006187: bullseye-pu: package espeakup/0.80-20+deb11u1

2022-03-14 Thread Adam D. Barratt
Control: tags -1 + confirmed d-i

On Sun, 2022-02-20 at 21:35 +0100, Samuel Thibault wrote:
> Users have reported that when they are building large packages in
> parallel, or generally loading the system a bit, the espeakup screen
> reader becomes very laggy. This is because espeakup gets scheduled
> only along other the parallel processes. Worse, if the system goes
> OOM, espeakup might get killed by the OOM killer.
> 
> This is not a regression with respect to previous releases.
> 
> In the case of the brltty screen reader, we fixed this by making
> brltty niced to -10 and its OOM score set to -900.
> 

Does this have any impact on the udeb?

Regards,

Adam



Re: Bug#1006192: bullseye-pu: package espeak-ng/1.50+dfsg-7+deb11u1

2022-03-14 Thread Adam D. Barratt
Control: tags -1 + confirmed d-i

On Mon, 2022-02-21 at 00:07 +0100, Samuel Thibault wrote:
> People have reported that when they work on the linux console with
> the
> espeakup screen reader, if they e.g. cat a long file, and the reader
> starts speaking it, and the user presses some key to interrupt the
> read,
> the screen reader remains silent for several seconds before it speaks
> anything again. That is because the speaking events for all the file
> reading have still been queued and the speak cancellation just makes
> them processed very quickly to flush the queue. Unfortunately there
> is a
> little usleep(50ms) that is performed on each event processing. This
> is
> a very old trick that was probably browntape-fixing some erroneous
> condition. We tried to remove that sleep and it didn't seem to have
> any
> nasty side effect. Upstream did commit the change and users are
> really
> happy with the change that completely fixes the delay.
> 

Does this have any impact on the udeb?

Regards,

Adam



Re: Bug#1006165: bullseye-pu: package tasksel/3.68+deb11u1

2022-03-14 Thread Adam D. Barratt
Control: tags -1 + confirmed d-i

On Sun, 2022-02-20 at 11:01 +0100, Holger Wansing wrote:
> I would like to do a little update to tasksel, to make tasksel
> install
> CUPS for all desktop tasks.
> In the past (buster and before), it was like this as well, via a
> different
> approach: there was a "task-print-service" task for this, which has
> been
> removed for bullseye.

That seems reasonable enough, but for completeness I'd appreciate a
KiBi-ack ("don't be silly, Holger knows what they're doing" counts ;-)
)

Regards,

Adam



Re: 11.3 and 10.12 planning

2022-03-14 Thread Mark Hymers
On Sun, 06, Mar, 2022 at 09:51:57PM +, Adam D. Barratt spoke thus..
> - March 19th (means freezing next weekend, so not ideal)
> - March 26th
> - April 2nd
> - April 9th
> 

I can currently do any of those but it currently looks like March 26th
has the biggest availability overlap (unless I missed an email).

Mark

-- 
Mark Hymers 



Upcoming stable point release (11.3)

2022-03-14 Thread Adam D. Barratt
Hi,

The next point release for "bullseye" (11.3) is scheduled for Saturday,
March 26th. Processing of new uploads into bullseye-proposed-updates 
will be frozen during the preceding weekend.

Regards,

Adam



Upcoming oldstable point release (10.12)

2022-03-14 Thread Adam D. Barratt
Hi,

The next point release for "buster" (10.12) is scheduled for Saturday,
March 26th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.

Regards,

Adam



Re: Bug#1006187: bullseye-pu: package espeakup/0.80-20+deb11u1

2022-03-14 Thread Samuel Thibault
Adam D. Barratt, le lun. 14 mars 2022 20:19:02 +, a ecrit:
> Control: tags -1 + confirmed d-i
> 
> On Sun, 2022-02-20 at 21:35 +0100, Samuel Thibault wrote:
> > Users have reported that when they are building large packages in
> > parallel, or generally loading the system a bit, the espeakup screen
> > reader becomes very laggy. This is because espeakup gets scheduled
> > only along other the parallel processes. Worse, if the system goes
> > OOM, espeakup might get killed by the OOM killer.
> > 
> > This is not a regression with respect to previous releases.
> > 
> > In the case of the brltty screen reader, we fixed this by making
> > brltty niced to -10 and its OOM score set to -900.
> 
> Does this have any impact on the udeb?

No because in d-i espeakup is started by hand, the systemd service file
is not installed in the .udeb.

d-i doesn't usually start large amounts of process in parallel so it's
not a problem there.

Samuel



Re: Bug#1006192: bullseye-pu: package espeak-ng/1.50+dfsg-7+deb11u1

2022-03-14 Thread Samuel Thibault
Adam D. Barratt, le lun. 14 mars 2022 20:20:26 +, a ecrit:
> On Mon, 2022-02-21 at 00:07 +0100, Samuel Thibault wrote:
> > We tried to remove that sleep and it didn't seem to have any nasty
> > side effect. Upstream did commit the change and users are really
> > happy with the change that completely fixes the delay.
> 
> Does this have any impact on the udeb?

The same fix will be used there.

d-i doesn't usually spit out large amounts of text so the problem was
not really showing up there, the effect won't really be noticed.

Samuel



Bug#1007265: override: gcc-12-base:libs/optional

2022-03-14 Thread Daniel Lewart
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-boot@lists.debian.org, gcc...@packages.debian.org

Debian FTP Team,

Please change gcc-12-base from:
libs/required
to:
libs/optional

Reason:
  #997826 - gcc-11: Current/future gcc-N-base packages
should not declare Priority: required:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997826

And gcc-10-base should be taken care of at the same time:
  #992477 - override: gcc-10-base:libs/optional:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992477

Thank you!
Daniel Lewart
Urbana, Illinois