Package: zeroc-ice-csharp
Version: 3.2.1-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080619 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on
i386.

Relevant part:
> ** Using build dependencies supplied by package:
> Build-Depends: cdbs (>= 0.4.27-1), debhelper (>= 4.2.0)
> Build-Depends-Indep: cli-common-dev (>= 0.4.4), ice32-services (>= 3.2.1), 
> ice32-translators (>= 3.2.1), mono-gmcs (>= 1.1.8) | c-sharp-2.0-compiler, 
> pkg-config
> Checking for already installed source dependencies...
> W: Unable to locate package ice32-services
> cdbs: missing
> Using default version 0.4.52
> debhelper: missing
> Using default version 7.0.11
> cli-common-dev: missing
> Using default version 0.5.7
> ice32-services: missing
> Default version of ice32-services not sufficient, no suitable version found. 
> Skipping for now, maybe there are alternatives.
> ice32-translators: missing
> Default version of ice32-translators not sufficient, no suitable version 
> found. Skipping for now, maybe there are alternatives.
> mono-gmcs: missing
> Using default version 1.9.1+dfsg-2
> c-sharp-2.0-compiler: missing
> pkg-config: missing
> Checking for source dependency conflicts...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> E: Couldn't find package ice32-services

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/06/19

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to