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

Re: Strange FTBFS on s390



Matt Zimmerman <mdz@debian.org> writes:

> On Wed, Feb 11, 2004 at 01:43:54PM +0100, Johannes Rohr wrote:
>
>> Hello everybody,
>> 
>> sorry for bothering the general newsgroup. I already asked my question on
>> the s390 and gtk-gnome lists but got no response.
>> 
>> nautilus-media, part of the GNOME core desktop, is currently blocked from
>> testing because of this FTBFS on s390:
>> 
>> http://buildd.debian.org/fetch.php?&pkg=nautilus-media&ver=0.3.3.1-4&arch=s390&stamp=1076051222&file=log&as=raw
>> 
>> What happened is that apt failed to properly unpack and configure the
>> build-depends: It tried to configure libeel2-2 before having configured
>> libeel2-data. dpkg complained about this loudly and returend an error.
>> 
>> This happened on s390 _only_. On all other arches the package built just
>> fine.
>> 
>> Can someone explain this? Is apt or dpkg probably misconfigured on s390?
>> What can I do about this? > 
>> Thanks a lot for any hint!
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=172339
>
> Probably the buildd admins patched/upgraded apt to work around this on other
> architectures.

If I understand your last comment to that bug correctly, the issue
should no longer be there, except in very rare exception.

So what can I do in order to get my package into sarge? Should I ask
the s390 buildd admins to increase the config value for the dpkg
command line even more?

Thanks,

Johannes

P.S.: What is the correct address to contact in order to ask for a
rebuild attempt on a specific arch?
-- 
~/.signature under construction



Reply to: