[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#271650: marked as done (FTBFS: illuminator/arm -- shlibs error)

Your message dated Sun, 27 Aug 2006 16:35:36 +0200
with message-id <20060827143533.GA30929@bode.aurel32.net>
and subject line FTBFS: illuminator/arm -- shlibs error
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: illuminator
Version: 0.8.9-2
Severity: serious

http://buildd.debian.org/fetch.php?&pkg=illuminator&ver=0.8.9-2&arch=arm&stamp=1094119654&file=log&as=raw

Automatic build of illuminator_0.8.9-2 on elara by sbuild/arm 1.170.5
[...]
Toolchain package versions: libc6-dev_2.3.2.ds1-16
linux-kernel-headers_2.5.999-test7-bk-17 gcc-3.3_1:3.3.4-7 g++-3.3_1:3.3.4-7
binutils_2.15-1 libstdc++5_1:3.3.4-7 libstdc++5-3.3-dev_1:3.3.4-7
[...]
dpkg-shlibdeps: failure: ldd on
`debian/libluminate5/usr/lib/libluminate.so.5.0.0' gave error exit status 1
dh_shlibdeps: command returned error code 256
make: *** [binary-arch] Error 1


Note that this FTBFS is holding new versions of your package out of Sarge.
Although this might be caused by some other package, it would be wrong to
reassign this bug, since it is your package that FTBFS's. Clone this bug
and reassign it in case you identify the cause in some other package.

Note that also it would be wrong to manually-build this package on arm, since
the build failure might still occur on the autobuilder, and either it should
be identified as a autobuilder bug (and fixed), or your package should be
fixed. This is especially important w.r.t. security support.

If you have questions about this build error, please ask them on
debian-devel or debian-<arch>, chances that someone with the required
knowledge can help you there is higher than mailing me personally.

--Jeroen

Disclaimer: I'm not a buildd admin, and are by far not as experienced in
classifying build logs.

-- 
Jeroen van Wolffelaar
jeroen@wolffelaar.nl
http://jeroen.A-Eskwadraat.nl

--- End Message ---
--- Begin Message --- 
Version: 2.3.6.ds1-4

On Tue, Sep 14, 2004 at 12:42:41PM +0200, Jeroen van Wolffelaar wrote:
> Package: illuminator
> Version: 0.8.9-2
> Severity: serious
> 
> http://buildd.debian.org/fetch.php?&pkg=illuminator&ver=0.8.9-2&arch=arm&stamp=1094119654&file=log&as=raw
> 
> Automatic build of illuminator_0.8.9-2 on elara by sbuild/arm 1.170.5
> [...]
> Toolchain package versions: libc6-dev_2.3.2.ds1-16
> linux-kernel-headers_2.5.999-test7-bk-17 gcc-3.3_1:3.3.4-7 g++-3.3_1:3.3.4-7
> binutils_2.15-1 libstdc++5_1:3.3.4-7 libstdc++5-3.3-dev_1:3.3.4-7
> [...]
> dpkg-shlibdeps: failure: ldd on
> `debian/libluminate5/usr/lib/libluminate.so.5.0.0' gave error exit status 1
> dh_shlibdeps: command returned error code 256
> make: *** [binary-arch] Error 1
> 
> 

Illuminator has been built correctly for the last 1,5+ years, so I
believe the bug is fixed. I marked it fix for the current version of the
glibc because I don't know exactly in which version it has been fixed.

Please feel free to reopen the bug if you don't agree.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

--- End Message ---
Reply to: