Bug#994729: brltty doesn't start on GUI login screen if sysvinit-core is used

2021-10-07 Thread Paul Gevers
Hi all,

With the risk of sounding nit-picking...

On 07-10-2021 01:26, Samuel Thibault wrote:
> Gregory Nowak, le mer. 06 oct. 2021 16:20:13 -0700, a ecrit:
>> It seems that the updated brltty package hasn't yet made it into
>> bullseye-proposed-updates.
> 
> Yes, I was too busy and didn't manage to upload before now.
> 
>> Is there any news on when that would happen?
> 
> That'll be postponed until the next dot release, whose date
> debian-release will decide on in perhaps a month or so.

Gregory is asking explicitly about bullseye-proposed-updates, which can
have once one of the Stable Release Managers has time to review and
acknowledge the pu upload (as the upload already happened). We'll be
releasing 11.1 this weekend, so energy is spend on that now (and new pu
requests aren't processed now [1]), but after the 11.1 release, it
*could* happen quickly (not saying it does as SRM typically processes in
batches), so it could be available well before 11.2.

Paul

[1] https://lists.debian.org/debian-live/2021/09/msg00027.html



OpenPGP_signature
Description: OpenPGP digital signature


Bug#994729: brltty doesn't start on GUI login screen if sysvinit-core is used

2021-10-06 Thread Samuel Thibault
Hello,

Gregory Nowak, le mer. 06 oct. 2021 16:20:13 -0700, a ecrit:
> It seems that the updated brltty package hasn't yet made it into
> bullseye-proposed-updates.

Yes, I was too busy and didn't manage to upload before now.

> Is there any news on when that would happen?

That'll be postponed until the next dot release, whose date
debian-release will decide on in perhaps a month or so.

Samuel



Bug#994729: brltty doesn't start on GUI login screen if sysvinit-core is used

2021-10-06 Thread Gregory Nowak
Hello Samuel.

It seems that the updated brltty package hasn't yet made it into
bullseye-proposed-updates. Is there any news on when that would
happen? Thanks.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org



Bug#994729: brltty doesn't start on GUI login screen if sysvinit-core is used

2021-09-21 Thread Samuel Thibault
Samuel Thibault, le mar. 21 sept. 2021 08:20:44 +0200, a ecrit:
> Unfortunately that's entangled with the glibc migration to
> testing. Hopefully that'll happen soon since some fixes have been done
> there and the migration delay was explicitly set to 2 days.

I've seen on #debian-release:

 aurel32: rspamd succeeeded, so I added a force-skiptest hint. 
glibc should migrate tonight.

Samuel



Bug#994729: brltty doesn't start on GUI login screen if sysvinit-core is used

2021-09-21 Thread Samuel Thibault
Gregory Nowak, le lun. 20 sept. 2021 21:13:44 -0700, a ecrit:
> On Mon, Sep 20, 2021 at 11:47:56PM +0200, Samuel Thibault wrote:
> > Could you test it before I request a stable-proposed-update?
> 
> I just have, and it works as expected here, thanks. Any idea how long
> it will take to move from stable-proposed-update to stable?

I'll first have to wait for brltty to enter testing (at least 5
days). Unfortunately that's entangled with the glibc migration to
testing. Hopefully that'll happen soon since some fixes have been done
there and the migration delay was explicitly set to 2 days.

Then it'll have to pass through the release team, which can be days.
Hopefully that'll make it for the 11.1 release on october 9-10.

Samuel



Bug#994729: brltty doesn't start on GUI login screen if sysvinit-core is used

2021-09-20 Thread Gregory Nowak
On Mon, Sep 20, 2021 at 11:47:56PM +0200, Samuel Thibault wrote:
> Could you test it before I request a stable-proposed-update?

I just have, and it works as expected here, thanks. Any idea how long
it will take to move from stable-proposed-update to stable?

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org



Bug#994729: brltty doesn't start on GUI login screen if sysvinit-core is used

2021-09-20 Thread Samuel Thibault
Hello,

Gregory Nowak, le dim. 19 sept. 2021 19:59:27 -0700, a ecrit:
> The fix is to add "$local_fs" to the "Required-Start" line of 
> /etc/init.d/brltty.

Thanks for the investigation!

I have uploaded a fixed package in my bullseye-tmp repository:

To use this repository, you need to add this to your sources.list:

  deb https://people.debian.org/~sthibault/tmp/bullseye-tmp ./

and run

  sudo apt-key adv --recv-keys --keyserver keyring.debian.org 
900CB024B67931D40F82304BD0178C767D069EE6

and then you can install packages like this:

  sudo apt install brltty/bullseye-tmp-sthibault


Could you test it before I request a stable-proposed-update?

Samuel



Bug#994729: brltty doesn't start on GUI login screen if sysvinit-core is used

2021-09-19 Thread Gregory Nowak
Package: brltty
Version: 6.3+dfsg-1
Severity: normal
Tags: a11y

Dear Maintainer,

When using sysvinit as the init system, brltty
shows "screen not in text mode" at the lightdm and gdm3 login screen.
This is because the /var/lib/BrlAPI/0 socket is missing at boot.

The fix is to add "$local_fs" to the "Required-Start" line of 
/etc/init.d/brltty.
So, the lsb header of /etc/init.d/brltty should read as follows:

### BEGIN INIT INFO
# Provides:  brltty
# Required-Start:mountkernfs $local_fs
# Required-Stop:
# Should-Start:  udev
# Should-Stop:
# Default-Start: S
# Default-Stop:
# Short-Description: Braille terminal driver
# Description: Used to provide access to refreshable braille terminals.
### END INIT INFO

Implementing this fix to brltty in debian would be much appreciated.
Thank you.


-- System Information:
Debian Release: 11.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages brltty depends on:
ii  init-system-helpers1.60
ii  libasound2 1.2.4-1.1
ii  libbluetooth3  5.55-3.1
ii  libbrlapi0.8   6.3+dfsg-1
ii  libc6  2.31-13
ii  libcap21:2.44-1
ii  libdbus-1-31.12.20-2
ii  libelogind0 [libsystemd0]  246.9.1-1+debian1
ii  libexpat1  2.2.10-2
ii  libglib2.0-0   2.66.8-1
ii  libgpm21.20.7-8
ii  libicu67   67.1-7
ii  liblouis20 3.16.0-1
ii  libncursesw6   6.2+20201114-2
ii  libpcre2-32-0  10.36-2
ii  libpolkit-gobject-1-0  0.105-31
ii  libtinfo6  6.2+20201114-2
ii  lsb-base   11.1.0
ii  policykit-10.105-31

Versions of packages brltty recommends:
ii  python3  3.9.2-3

Versions of packages brltty suggests:
pn  brltty-speechd   
ii  brltty-x11   6.3+dfsg-1
pn  console-braille  

-- no debconf information