Control: severity -1 normal
On Thu, Dec 15, 2016 at 09:42:08PM +0100, Petter Reinholdtsen wrote:
> Control: severity -1 grave
>...
> If I understand the test results from
> https://ci.debian.net/packages/o/ocrad/unstable/amd64/ > correct, the
> library is no longer usable.
>...
That's mostly unr
Processing control commands:
> severity -1 normal
Bug #774164 [libocrad-dev] libocrad-dev: libocrad.a contains non-reallocatable
code
Severity set to 'normal' from 'grave'
--
774164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774164
Debian Bug Tracking System
Contact ow...@bugs.debian.org
On 2016-12-16 10:16, Alexander Alemayhu wrote:
> On Thu, Dec 15, 2016 at 09:42:08PM +0100, Petter Reinholdtsen wrote:
>>
>> Personally I use tesseract these days for my OCR work, and do not need ocrad.
>
> I have unfortunately stopped using ocrad in favour of proprietary
> solutions.
>
> Thanks f
On Thu, Dec 15, 2016 at 09:42:08PM +0100, Petter Reinholdtsen wrote:
>
> Personally I use tesseract these days for my OCR work, and do not need ocrad.
I have unfortunately stopped using ocrad in favour of proprietary
solutions.
Thanks for adding me to the recipient list, but I don't have the
mot
Processing control commands:
> severity -1 grave
Bug #774164 [libocrad-dev] libocrad-dev: libocrad.a contains non-reallocatable
code
Severity set to 'grave' from 'normal'
--
774164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774164
Debian Bug Tracking System
Contact ow...@bugs.debian.org
5 matches
Mail list logo
