Re: armel 2.0.10-5 Dep-Wait: libmono-dev (>= 2.4+dfsg-5)
On Tue, Jun 23, 2009 at 2:45 PM, Jo Shields<directhex@apebox.org> wrote:
> On Tue, 2009-06-23 at 14:30 +0200, Mathieu Malaterre wrote:
>> On Tue, Jun 23, 2009 at 2:26 PM, Jo Shields<directhex@apebox.org> wrote:
>> > On Tue, 2009-06-23 at 12:03 +0200, Mathieu Malaterre wrote:
>> >> Hi there,
>> >>
>> >> I am still struggling to get my gdcm: debian/control file right. As
>> >> you can see on the buildd page, I am still getting:
>> >>
>> >> https://buildd.debian.org/pkg.cgi?pkg=gdcm
>> >>
>> >> armel 2.0.10-5 Dep-Wait: libmono-dev (>= 2.4+dfsg-5)
>> >> and
>> >> mipsel 2.0.10-5 Dep-Wait: mono-runtime
>> >>
>> >> While my debian/control looks like:
>> >>
>> >> Build-Depends-Indep: cli-common-dev (>= 0.5.7),
>> >> mono-devel (>= 2.0) | mono-mcs (>= 1.0) | mono-gmcs (>= 1.1.8)
>> >>
>> >> mono-devel /mono-mcs / mono-gmcs should be available on 'all'
>> >> architecture right ? (I know I need to remove dep on mono-gmcs,
>> >> mono-mcs in the near future).
>> >
>> > armel we had a FTBFS on 2.4+dfsg-5. It should be fixed soonish. mipsel
>> > we don't ship support for (although this may be functional in Mono 2.6)
>>
>> Does this means I should explicitely Builds-Depends-Indep [!armel
>> !mipsel] for now ? I'd like to see if the other binary package are
>> building fine on those arch but for now I haven't had much luck, it
>> always stop way too early (at mono dependency problem).
>
> armel it's just a FTBFS, so dep-wait is to be expected. mipsel, yes, you
> should !mipsel the build-depend.
Just out of curiosity why is everything working fine with gmime2.4:
https://buildd.debian.org/pkg.cgi?pkg=gmime2.4
I copied the debian/control file from it.
Thanks,
--
Mathieu
Reply to: