brltty_5.3.1-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 15 Mar 2016 01:36:39 +0100 Source: brltty Binary: brltty libbrlapi0.6 libbrlapi-dev libbrlapi-jni libbrlapi-java brltty-flite brltty-speechd brltty-espeak brltty-udeb brltty-x11 xbrlapi cl-brlapi python-brlapi

Processing of brltty_5.3.1-2_amd64.changes

brltty_5.3.1-2_amd64.changes uploaded successfully to localhost along with the files: brltty_5.3.1-2.dsc brltty_5.3.1-2.debian.tar.xz brltty-dbgsym_5.3.1-2_amd64.deb brltty-espeak-dbgsym_5.3.1-2_amd64.deb brltty-espeak_5.3.1-2_amd64.deb brltty-flite-dbgsym_5.3.1-2_amd64.deb

Processing of brltty_5.3.1-2_amd64.changes

brltty_5.3.1-2_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: brltty_5.3.1-2.dsc brltty_5.3.1-2.debian.tar.xz brltty-dbgsym_5.3.1-2_amd64.deb brltty-espeak-dbgsym_5.3.1-2_amd64.deb brltty-espeak_5.3.1-2_amd64.deb brltty-flite-dbgsym_5.3.1-2_amd64.deb

Bug#818241: marked as done (brltty: Unstable brltty)

Your message dated Tue, 15 Mar 2016 00:49:34 + with message-id and subject line Bug#818241: fixed in brltty 5.3.1-2 has caused the Debian Bug report #818241, regarding brltty: Unstable brltty to be marked as done. This means that you claim that the

Bug#818241: brltty: Unstable brltty

Hi, If I install from brltty-nonsystemd, here's what I get (attach). And I experience the bug. If I install from szstemd, everything is good (install process, plus running at boot and so on). Regards, Le 15/03/2016 00:59, Samuel Thibault a écrit : > Samuel Thibault, on Tue 15 Mar 2016

Bug#818241: brltty: Unstable brltty

Jean-Philippe MENGUAL, on Tue 15 Mar 2016 01:34:02 +0100, wrote: > If I install from brltty-nonsystemd, here's what I get (attach). > And I experience the bug. > > If I install from szstemd, everything is good (install process, plus > running at boot and so on). Ok, so the missing systemd

Processed: tagging 818241

Processing commands for cont...@bugs.debian.org: > tags 818241 + pending Bug #818241 [brltty] brltty: Unstable brltty Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 818241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818241 Debian Bug

Re: BRLTTY: errorneous systemd unit

Hello, Sebastian Humenda, on Wed 09 Mar 2016 10:28:07 +0100, wrote: > after the recent BRLTTY upgrade (in testing), the systemd unit for BRLTTY > seems > broken. I guess this is related with Bug#818241 that Jean-Philippe has just submitted. Could you also try the +b2-systemd package from

Bug#818241: brltty: Unstable brltty

Samuel Thibault, on Tue 15 Mar 2016 00:52:07 +0100, wrote: > I'm building two brlttys, with the same package set except > libsystemd-dev, to confirm that this makes the difference. I have uploaded them to http://people.debian.org/~sthibault/tmp/ Please try both the +b2-nosystemd and +b2-systemd

Bug#818241: brltty: Unstable brltty

Jean-Philippe MENGUAL, on Tue 15 Mar 2016 00:48:57 +0100, wrote: > hmmm I note a problem. One PID stays, brltty. But another > appears/disappears blinking: /sbin/brltty --no-daemon Ok. I guess they are competing with each other. So the issue is actually that the brltty run by systemd doesn't

Bug#818241: brltty: Unstable brltty

One thing which is notably different between 5.3.1-1 and 5.3.1-1+b1 is that 5.3.1-1 depends on libsystemd while 5.3.1-1+b1 does not. Mario, had you checked in a pbuilder for the build dependencies? Samuel

Bug#818241: brltty: Unstable brltty

Hello, Jean-Philippe MENGUAL, on Mon 14 Mar 2016 23:59:15 +0100, wrote: > I updated my testing, and now use 5.3.1-1+b1 (instead of 5.3.1-1). You forgot to mention explicitly that you tried to downgrade to 5.3.1-1 again, and then it did work fine, so the culprit is really the 5.3.1-1+b1 version.

Bug#818241: brltty: Unstable brltty

Package: brltty Version: 5.3.1-1+b1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I updated my testing, and now use 5.3.1-1+b1 (instead of 5.3.1-1). * What exactly did you do (or not