Bug#713090: kiwix: FTBFS: xpidl.IDLError: error: type 'PRUint32' not found, ../../../src/components/zimAccessor/IZimAccessor.idl line 13:30
Lucas Nussbaum
lucas at lucas-nussbaum.net
Sat Jun 22 11:08:14 UTC 2013
Source: kiwix
Version: 0.9~beta6.8-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[4]: Entering directory `/«PKGBUILDDIR»/src/components/zimAccessor'
> /usr/bin/python /usr/lib/xulrunner-devel-17.0/sdk/bin/typelib.py --cachedir=/tmp -o zimAccessor.xpt -I /usr/lib/xulrunner-devel-17.0/idl ../../../src/components/zimAccessor/IZimAccessor.idl
> Traceback (most recent call last):
> File "/usr/lib/xulrunner-devel-17.0/sdk/bin/typelib.py", line 290, in <module>
> idl.resolve(options.incdirs, p)
> File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 287, in resolve
> p.resolve(self)
> File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 526, in resolve
> member.resolve(self)
> File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 897, in resolve
> p.resolve(self)
> File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 1035, in resolve
> self.realtype = method.iface.idl.getName(self.type, self.location)
> File "/usr/lib/xulrunner-devel-17.0/sdk/bin/xpidl.py", line 271, in getName
> raise IDLError("type '%s' not found" % id, location)
> xpidl.IDLError: error: type 'PRUint32' not found, ../../../src/components/zimAccessor/IZimAccessor.idl line 13:30
> boolean getArticleCount(out PRUint32 count);
> ^
> make[4]: *** [zimAccessor.xpt] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/kiwix_0.9~beta6.8-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
More information about the Debian-edu-pkg-team
mailing list