Re: Gnome settings hangs orca
On Sat, Feb 9, 2019 at 12:37 PM Jason White wrote: > If the user has to rely on "flat review" to navigate to an object, then > that indicates a serious accessibility bug I think we all agree on that. gnome-control-center is a complex app and I expect it will take someone a good deal of time to fix the bug. I don't have a strong background in GTK's keyboard navigation and accessibility models (and the extra time) to be able to do it myself right now. Thanks, Jeremy Bicha
Re: default desktop
On Sat, Feb 9, 2019 at 8:36 AM Samuel Thibault wrote: > > Ok, then you need to discuss this with the rest of the Debian GNOME > > team. I suggest the debian-gtk-gnome list. (And I think it would have > > been more polite to talk to them before talking to the tasksel team.) > > > > It's a bit late to be talking about reverting Wayland by default for > > everyone since this has been enabled for Testing since soon after the > > Stretch release. > > Well, actually, personally I realized that gnome switched to wayland in > Debian only recently. I believe most of debian-accessibility@ is in the > same situation, so this is mostly untested, and for instance > https://lists.debian.org/debian-accessibility/2019/01/msg00014.html > needs to be fixed to have gtk2 applications accessible. > > As you say, it's now too late for doing much changes in gnome anyway. I said only "a bit late", but there is still time to make this change if necessary. If there are significant problems with GNOME on Wayland that the Debian GNOME team may have been unaware of, please let them know promptly. Thanks, Jeremy Bicha
Re: default desktop
On Fri, Feb 8, 2019 at 7:37 PM Samuel Thibault wrote: > As mentioned earlier in the thread, the default desktop for > accessibility is already MATE. I'm here talking about the choice of > default desktop for Debian indeed. IIRC one of the reasons for the > choice of gnome was its general accessibility, and I'm just saying I > believe that part has changed. Ok, then you need to discuss this with the rest of the Debian GNOME team. I suggest the debian-gtk-gnome list. (And I think it would have been more polite to talk to them before talking to the tasksel team.) It's a bit late to be talking about reverting Wayland by default for everyone since this has been enabled for Testing since soon after the Stretch release. Thanks, Jeremy Bicha
Re: default desktop
On Fri, Feb 8, 2019 at 12:07 PM Samuel Thibault wrote: > Re-opening the question of the default desktop just a bit to provide > updated information: the current gnome-with-wayland default is a concern > for accessibility. Accessibility on Wayland has a lot of glitches in > all kinds of places, and nobody is working on fixing them yet. Also, > MATE+Compiz now provides very nice zoom support. Sorry: I have lots of questions. Could you rephrase this email and provide more context? Are you proposing to change Debian's default desktop or just the default desktop for accessibility? If it's just for accessibility, could you explain more about how users opt in to that and what its effects are? Sorry I don't install Debian very often and I've not tried doing it with accessibility enabled. Could you point to issues with accessibility using GNOME on Wayland? You can force disable GNOME on Wayland completely by setting WaylandEnable=false in /etc/gdm3/daemon.conf I assume MATE isn't defaulting to using Compiz now? If so, it seems simpler to just disable Wayland for accessible users than installing MATE and switching to Compiz? Thanks, Jeremy Bicha
Re: Gnome settings hangs orca
On Fri, Feb 8, 2019 at 3:51 PM Sam Hartman wrote: > 2) Since stretch, the UI of the settings panel has been significantly > redone. It looks like there is a list of possible task areas along the > side. There doesn't seem to be good keyboard navigation to get into > that list; it doesn't appear to be in the tab order and neither > alt-backtick nor f6 will get you there. Yes, keyboard accessibility for gnome-control-center is in really bad shape. I recently fixed several smaller issues and backported those to Buster but these issues remain: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/327 (Note the first sentence of Matthias' comment on 327 gives another workaround) https://gitlab.gnome.org/GNOME/gnome-control-center/issues/330 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/369 Of those, 369 is probably the easiest to solve. There is also a Debian RC bug: https://bugs.debian.org/913978 but sadly I think we'll end up demoting that or ignoring it for the Buster release. Sorry. Thanks, Jeremy Bicha
Re: Do not upgrade espeakup to 1:0.80-5+deb9u2!!
On Sun, Nov 11, 2018 at 12:05 PM Samuel Thibault wrote: > Now, how did we end up in such a situation. Apparently I didn't test > this update well enough. The issue is that I do not actually use > accessibility software, so I'm using VMs etc. which is far from ideal, > and lets me make more harm than good. I appreciate the work you do. I firmly believe you do far more good than harm. > I guess in the future I'll have to just refrain from making updates of > such essential accessibility packages unless people do test packages > that I'll make available in the staging area mentioned above. I didn't read closely and initially thought you were talking about delaying uploads to Unstable. Your proposal sounds like a useful precaution for stable-backports (at least until we get some kind of PPA system where we can have stability tiers.) Finding testers for stable bugfixes can be difficult. I hope people that can safely test those updates will continue to help you out there. I appreciate their work too! Thanks, Jeremy Bicha
Re: multiple ITPs - mbrola voices
On Sat, Apr 21, 2018 at 4:02 AM, Chris Lamb wrote: > Secondly, am sorry for not seeing this until these hit NEW. For 100% > clarity, I've put them "on hold" there for the time being. Chris, are you aware that there are already about 45 mbrola voices packages in Debian, even before these new ITPs? [1] It might be a bit late to try to change the source packaging for all of that… [1] https://qa.debian.org/developer.php?email=sthibault%40debian.org Thanks, Jeremy Bicha
sound-icons integration with speech-dispatcher?
Hi, How integrated is sound-icons with speech-dispatcher? I'm asking because we are late in Ubuntu 18.04's release cycle and Ubuntu is considering lowering speech-dispatcher's Recommends: sound-icons to Suggests. If Ubuntu did that, what would Ubuntu miss out on? Thanks, Jeremy Bicha
Re: Alioth to Salsa migration of a11y and tts packages
On Sun, Jan 21, 2018 at 2:00 PM, Paul Gevers wrote: > On 20-01-18 22:10, Jeremy Bicha wrote: >> The VCS fields should be updated when someone has time. > > Ack, but I think there should be a solution that doesn't contain the > salsa name, e.g. > https://anonscm.debian.org/ > I should have been more clear in my previous message. salsa.debian.org is intended to be the permanent name for the service. Thanks, Jeremy Bicha
Re: Alioth to Salsa migration of a11y and tts packages
On Sat, Jan 20, 2018 at 3:36 PM, Paul Gevers wrote: > An a11y team was already been created² (not by me by the way), I just > created the tts team³. Who wants to be co-owner with me? I can help some with the migration, but I'll need to have at least Master access for that. The 5 existing repos in the Ally Team are in the GNOME Team namespace but shared with the a11y team since they are co-maintained. [1] > I propose we don't start yet with updating the VCS-* and maintainer > fields yet, as I don't believe there is consensus if the old values have > to go away (there is an effort ongoing to keep supporting the Alioth > mail lists). In case of emergency, we can always temporarily use the > debian-accessibility@l.d.o list again). The VCS fields should be updated when someone has time. [1] https://lists.debian.org/debian-gtk-gnome/2018/01/msg1.html Thanks, Jeremy Bicha
Adopting sound-icons?
Paul, were you still planning on moving sound-icons to be maintained by the Accessibility Team? https://bugs.debian.org/730987 Thanks, Jeremy Bicha
Removing gnome-speech from Debian
I intend to file a removal bug for gnome-speech soon. The last thing to use it was dasher but I think that wasn't needed any more after the 5.0 beta. gnome-speech hadn't been maintained upstream since 2009 and it uses the libbonobo library which we are trying to remove from Debian before the Buster release. Thanks, Jeremy Bicha
pkg-gnome packages have been converted from svn to git
Hi, There are a few packages [1] that are co-maintained between the Debian GNOME (pkg-gnome) and Debian Accessibility (pkg-a11y) teams. I am pleased to announce that all of the accessibility packages have now been converted from svn to git. The pkg-gnome packages use a somewhat different repo layout and workflow than the packages in the pkg-a11y. For more information, see [2]. If you have any questions or concerns, please feel free to reply here or ask in #debian-gnome on IRC. [1] https://anonscm.debian.org/git/pkg-gnome/?q=a11y [2] https://wiki.debian.org/Gnome/Git Thanks, Jeremy Bicha
Re: gnome-orca version policy?
On Mon, Sep 18, 2017 at 1:46 PM, Paul Gevers wrote: > Can't we find an easy way to have these delta's within the package? I > believe there is some trick to apply patches only in Ubuntu (not sure > how stable that is, but I'd like the discussion). Yes, this can be done by adding debian/patches/ubuntu.series that lists all of the patches that need to apply on Ubuntu. The tricky part to remember is that if you add a patch to debian/patches/series, you will probably want to add it to debian/patches/ubuntu.series or Ubuntu won't have that patch applied there. I can do this if there is consensus that we want this. The Debian GNOME team is a bit hesitant about this strategy but it may not be a big deal if this package is mostly maintained by the Accessibility Team. Thanks, Jeremy Bicha
Re: gnome-orca version policy?
On Sun, Sep 3, 2017 at 1:56 AM, Paul Gevers wrote: > On 02-09-17 21:05, Jeremy Bicha wrote: >> I am now a DD so I can help with uploads if desired. > > That would be great. I hope that means way less Debian <-> Ubuntu > delta's (which always annoy me). I uploaded the GNOME 3.26 a11y packages to unstable now (except for pyatspi). Ubuntu's orca has 2 extra patches: one for better Unity support and one to use gsettings for new installs. Otherwise, the a11y packages are in sync now between Debian and Ubuntu, at least in the Debian VCS. Thanks, Jeremy Bicha
Re: gnome-orca version policy?
On Sat, Sep 2, 2017 at 1:42 PM, Paul Gevers wrote: > The watch file in the gnome-orca package suggests that only the even > versions of minor releases should be packaged, but you packages 3.25.4 > for Ubuntu. Should we update our watch file or is 3.25.4 special? Since Ubuntu 17.10 is targeting GNOME 3.26 and Ubuntu Feature Freeze was last week, I needed to upload the GNOME 3.26 Beta to Ubuntu then. The GNOME 3.26 Release Candidate is supposed to be released around Monday. If there aren't any objections, I think it would be good to release the a11y packages to Debian unstable then. Substantial parts of GNOME 3.26 are in unstable already. I am now a DD so I can help with uploads if desired. References https://wiki.gnome.org/ThreePointTwentyfive https://wiki.ubuntu.com/ArtfulAardvark/ReleaseSchedule https://www.0d.be/debian/debian-gnome-3.26-status.html Thanks, Jeremy Bicha
Re: GNOME 3.24 a11y updates
On Tue, Jul 11, 2017 at 3:35 PM, Paul Gevers wrote: > On 06/25/17 16:07, Jeremy Bicha wrote: >> at-spi2-core >> at-spi2-atk >> atk1.0 (in pkg-gnome svn) > > All uploaded now. Thanks Paul! Jeremy Bicha
Re: GNOME 3.24 a11y updates
Oops, I wasn't subscribed to this list. > I quickly reviewed and uploaded at-spi2-core to debomatic, but it > contains an extremely big amount of lintian warnings on the > debian/copyright file. Could you please have a look? I'm not interested right now in working on updating the copyright file, but feel free to work on it if you like. > Isn't bindnow and fortify possible now? I think I fixed that issue in the git branch now. Sometimes that lintian check reports apparently false positives though. Thanks, Jeremy Bicha
GNOME 3.24 a11y updates
With Samuel's permission, I updated the packaging for the a11y components of GNOME 3.24 last month. I am not a DD yet so I will need sponsorship for these updates. Now that Stretch is released, maybe now would be a good time to upload these to Debian? at-spi2-core at-spi2-atk atk1.0 (in pkg-gnome svn) Thanks, Jeremy Bicha
Bug#852047: dasher: Fails to build from source without networking
From 9de31b549cda1d94d312419badca7867124a3c19 Mon Sep 17 00:00:00 2001 From: Jeremy Bicha Date: Sat, 21 Jan 2017 03:54:19 + Subject: [PATCH] Build-Depend on rarian-compat Closes: #852047 --- debian/control | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/debian/control b/debian/control index 377002e..fd80f13 100644 --- a/debian/control +++ b/debian/control @@ -6,8 +6,9 @@ Uploaders: Thibaut Paumard Vcs-Git: https://anonscm.debian.org/git/pkg-a11y/dasher.git Vcs-Browser: https://anonscm.debian.org/gitweb/?p=pkg-a11y/dasher.git Build-Depends: debhelper (>= 9.0.0), - gnome-common, + gnome-common, gnome-pkg-tools (>= 0.6), + rarian-compat, dpkg-dev (>= 1.13.19), intltool (>= 0.40.1), libglib2.0-dev (>= 2.16.0), -- 2.10.2
Bug#852047: dasher: Fails to build from source without networking
Package: dasher Version: 5.0.0~beta~repack-1 Severity: serious Tags: patch dasher fails to build from source in a builder without external network access such as the Launchpad builders. https://launchpad.net/ubuntu/+source/dasher/5.0.0~beta~repack-1/+build/11896314 xmllint --noout --xinclude --dtdvalid 'http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd' dasher-C.omf error : No such file or directory warning: failed to load external entity "http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd"; Could not parse DTD http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd This is a violation of Debian policy 4.9 https://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules "For packages in the main archive, no required targets may attempt network access." Adding rarian-compat to Build-Depends fixes this. It would be nice if dasher wouldn't try to use scrollkeeper either but I think a quick fix is preferred at this stage of Debian's release cycle. Trivial git patch attached (in next email) Thanks, Jeremy Bicha
Bug#851484: espeak-ng: Update Homepage and Vcs-* fields
On 15 January 2017 at 09:22, Samuel Thibault wrote: >> Patch attached. > > Patch was forgotten :) I wanted to wait for bugs.debian.org to assign a bug number first to add that to the patch too but you were too fast! Jeremy
Bug#851484: espeak-ng: Update Homepage and Vcs-* fields
From 1140ba0f2a9edb23e907366179deb5791ed40e16 Mon Sep 17 00:00:00 2001 From: Jeremy Bicha Date: Sun, 15 Jan 2017 09:10:57 -0500 Subject: [PATCH] Update Homepage and Vcs fields Closes: #851484 --- debian/control | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/debian/control b/debian/control index 12bfc00..29e87eb 100644 --- a/debian/control +++ b/debian/control @@ -3,9 +3,9 @@ Section: sound Priority: optional Maintainer: Debian Accessibility Team Uploaders: Samuel Thibault -Vcs-Browser: http://git.debian.org/?p=pkg-a11y/espeak.git;a=summary -Vcs-Git: git://git.debian.org/git/pkg-a11y/espeak.git -Homepage: http://espeak.sourceforge.net/ +Vcs-Browser: https://anonscm.debian.org/git/pkg-a11y/espeak-ng.git/ +Vcs-Git: https://anonscm.debian.org/git/pkg-a11y/espeak-ng.git/ +Homepage: https://github.com/espeak-ng/espeak-ng Build-Depends: debhelper (>= 9.20150628), dh-autoreconf, dh-exec, libpcaudio-dev, libsonic-dev, ruby-ronn, ruby-kramdown -- 2.10.2
Bug#851484: espeak-ng: Update Homepage and Vcs-* fields
Package: espeak-ng Version: 1.49.0+dfsg-6 Tags: patch The Homepage and Vcs fields still point to espeak instead of espeak-ng. Patch attached. Thanks, Jeremy
Bug#719139: liblouis: Use Arch: all for python packages
Source: liblouis Version: 2.5.3-1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy I believe python-liblouis and python3-liblouis should be "Architecture: all" not any. Originally reported at https://launchpad.net/bugs/1070251 Thanks, Jeremy - -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy'), (100, 'saucy-backports') -- To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAAajCMY15O3wFHvuLhVwzKDKV7ZBfSZRu_TeHDAjYB6+-=x...@mail.gmail.com
Bug#708985: java-atk-wrapper: Please merge Ubuntu changes
merge-with-ubuntu.patch Description: Binary data
Bug#708985: java-atk-wrapper: Please merge Ubuntu changes
Package: java-atk-wrapper Version: 0.30.4-3 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy Tags: patch I'm attaching a patch with the remaining diff from Ubuntu. Thanks, Jeremy - -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'raring'), (100, 'saucy-backports') -- To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caaajcmanesxvh3fwuz70cpazax4vppbbkqvof+rfzwthjx2...@mail.gmail.com
