Bug#1066430: namazu2: FTBFS: ld: ../nmz/.libs/libnmz.so: undefined reference to `_nmz_memcmp'

2024-03-13 Thread Takatsugu Nokubi
On Wed, 13 Mar 2024 13:03:57 +0100 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 > > -Werror=implicit-function-declaration

Bug#1017038: icinga2-bin: Uninstallable, missing denepdency package libboost-iostreams1.67.0

2022-08-11 Thread Takatsugu Nokubi
Package: icinga2-bin Version: 2.31-13+deb11u3 Severity: grave Depends: icinga2-common (= 2.13.5-1.buster), libboost-atomic1.67.0, libboost-chrono1.67.0, libboost-context1.67.0, libboost-coroutine1.67.0, libboost-date-time1.67.0, libboost-filesystem1.67.0, libboost-iostreams1.67.0,

Bug#973459: uim: FAIL: test-composer.scm

2020-12-17 Thread Takatsugu Nokubi
https://salsa.debian.org/debian/uim/-/merge_requests/9 This is the fix request. Could you review the patch? 2020年12月14日(月) 18:24 : > On Sun, Dec 13, 2020 at 02:35:58PM +0900, Takatsugu Nokubi wrote: > > I made a simple patch to skip test-composer: > > > https://salsa.deb

Bug#973459: uim: FAIL: test-composer.scm

2020-12-12 Thread Takatsugu Nokubi
I made a simple patch to skip test-composer: https://salsa.debian.org/debian/uim/-/commit/3cd351b6f2b15fb3161e1d00ed4c8ba26925429b (Oh, I forgot to fix description of the patch) 2020年12月13日(日) 10:36 : > Control: forwarded -1 https://github.com/uim/uim/issues/167 > > On Sat, Dec 12, 2020 at

Bug#973459: uim: FAIL: test-composer.scm

2020-11-18 Thread Takatsugu Nokubi
020 at 09:11:54AM +0900, Takatsugu Nokubi wrote: > > I need the test2/test-suite.log file, so I had tried to reproduce it > > on abel twice, but > > I couldn't get the error, just succeeded. > > > > Can I get the test2/test-suite.log file from anywhere? > >

Bug#973459: uim: FAIL: test-composer.scm

2020-11-16 Thread Takatsugu Nokubi
On Sat, 31 Oct 2020 21:52:30 +0300 Dmitry Shachnev wrote: > Control: unblock 972278 by -1 > > It built for me on abel, which is exactly the same hardware as the > > buildds where it failed. > > > > This makes it feel more like a generic race condition that only happened > > to hit here than an

Bug#880341: uim: FTBFS: configure: error: no qmake for Qt5 found

2017-11-02 Thread Takatsugu Nokubi
On Mon, 30 Oct 2017 21:14:18 +0100 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): > > checking where the gettext function comes from... libc > > checking for GTK2... yes > > checking for

Bug#873860: ibus-anthy FTBFS: UnicodeDecodeError: 'euc_jp' codec can't decode byte 0xe5 in position 46: illegal multibyte sequence

2017-10-27 Thread Takatsugu Nokubi
On Fri, 22 Sep 2017 23:20:39 +0900 Osamu Aoki wrote: > On Fri, Sep 22, 2017 at 09:14:22AM +0200, John Paul Adrian Glaubitz wrote: > > This FTBFS can be easily fixed with: > > > > --- ibus-anthy-1.5.9.orig/data/zipcode-textdic.py > > +++

Bug#814626: chasen: causes installation failure in naist-jdic

2016-03-02 Thread Takatsugu Nokubi
On Sat, 13 Feb 2016 15:37:43 +0100 Andreas Beckmann wrote: > You shouldn't use dpkg-architecture from maintainer scripts > but resolve the architecture specific bits at package build time. This problem was fixed in 2.4.5-24.