Bug#951559: pinot FTCBFS: uses the build architecture pkg-config
On Tue, 28 Sep 2021 12:57:41 +1300 Olly Betts wrote: > There's a 1.2.0 release planned for the near future, so packaging that > once it is out should address all the issues you reported. > Please note that 1.20 was released in October 2021 and 1.21 on February 2022. Best regards, Fabrice
Bug#953912: pinot: Switch from deprecated to
On Tue, 28 Sep 2021 12:59:21 +1300 Olly Betts wrote: > There's a 1.2.0 release planned for the near future, so packaging that > once it is out should address this. > Please note that 1.20 was released in October 2021 and 1.21 on February 2022. Best regards, Fabrice
Bug#607390: pinot: package fails to install
Hi all, I am Pinot's developer. I have had several user queries about this. Any way it can be fixed ? I don't fully understand what the root of the problem is. If it helps at all, Pinot will work with OOo's UTF8 support patch; indeed, Fedora merged it in its libtextcat package a long time ago without any issue whatsoever. Pinot actually uses UTF8 internally. Best regards, Fabrice Colin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607390: pinot: package fails to install
Hi René, Thanks for the quick reply. On Mon, Mar 21, 2011 at 5:50 PM, Rene Engelhard r...@debian.org wrote: Does it also work with the *unpatched* libraray but the converted data files? That's the situation currenztly in Debian - we don't ship the patched library yet in a public package/location, just ship the patched data files. Pinot would work with the unpatched library fine, but I believe the unpatched library wouldn't work correctly with the converted data files, i.e. it would fail to identify languages correctly. But if you say it works with the fully patched lib, too that can be the solution. Then both pinot and LibreOffice can use that library.. Yes, that would be ideal. Best regards, Fabrice Colin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530572: pinot_0.93-1(mips/unstable): FTBFS on mips - undefined reference
On Sat, Jun 13, 2009 at 11:57 PM, Jonas Smedegaardd...@jones.dk wrote: Unfortunately my first attempt didn't work out as intended. Haven't found time to verify yet, but seems to be that I should set CPPFLAGS instead of CFLAGS (they are handled separately in CDBS packaging tool). Perhaps your upstream autotools setting should be similarly adjusted? Try CXXFLAGS, it will be picked up by configure and used at build time. I have had reports the fix in SVN r1635 fixed the issue, but if you have a log for me to look into, let me know. Fabrice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530572: pinot_0.93-1(mips/unstable): FTBFS on mips - undefined reference
On Mon, Jun 8, 2009 at 5:05 AM, Jonas Smedegaardd...@jones.dk wrote: [update: package released, using CFLAGS directly to avoid patching] Thanks ! It is excellent that you care to nurse your software downstream at our distribution. If you should happen to be interested in engaging more directly in the packaging of your software for Debian, I would be more than happy to team up with you - help you get write access to our Git repository and introduce you to the packaging tools in use. You do *not* need to be an official Debian developer in order to work directly with Debian, it only requires one person from each packaging team to take that responsibility (me, in this case). Ok, drop me an email privately with the above information. I don't run Debian, but getting Pinot to work fine on it is high priority to me. Fabrice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530572: pinot_0.93-1(mips/unstable): FTBFS on mips - undefined reference
Hi Jonas, I am the developer of Pinot. This problem was reported to me by a Debian user a while back, and -I believe- is fixed by SVN revision 1635 : http://svn.berlios.de/wsvn/pinot/?op=compcompare[]=...@1634compare[]=...@1635 Could you give it a try ? Thanks. Fabrice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
