Re: Bug#648775: Mono 2.10 Transition has started (was Re: Bug#648775: transition: mono 2.10)
On Mon, Jan 30, 2012 at 5:05 PM, Jo Shields <directhex@apebox.org> wrote:
> On Mon, 2012-01-30 at 16:29 +0100, Mathieu Malaterre wrote:
>> On Mon, Jan 30, 2012 at 4:18 PM, Mirco Bauer <meebey@debian.org> wrote:
>> > On 01/30/2012 03:04 PM, Mathieu Malaterre wrote:
>> >> Quick question, gdcm is setup the following way:
>> >>
>> >> $ cat control
>> >> ...
>> >> Package: libgdcm-cil
>> >> Section: cli-mono
>> >> Architecture: i386 lpia kfreebsd-i386 powerpc amd64 kfreebsd-amd64
>> >> ia64 arm armeb armel sparc s390
>> >> ...
>> >>
>> >> Isn't there something easier such as ${mono:Architecture} ? Or do I
>> >> need a source upload each time there is a change in mono source ?
>> >
>> > Since mono 2.10.1-2 there is /usr/share/mono/mono-archs.make which
>> > includes 2 variables:
>> > DEB_MONO_ARCHS and DEB_MONO_SGEN_ARCHS which can be used to get a list
>> > of all mono arches.
>>
>> Hum, before I do something silly, you understand that s390x is listed
>> in DEB_MONO_ARCHS ?
>
> The upstream Mono s390 maintainer instituted a "32 bit and above"
> policy. So 64-bit 390x kept getting maintenance, 31-bit s390 did not.
>
> Packages for Mono for s390x are awaiting only an upload - but we want to
> get the transition done as-is first
Thanks for the clarification, according to my RC bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657779
I had to :
...
Please consider making the build-dependency architecture-specific and
not building the -cil binary packages on s390*.
...
I'll remove s390 and add s390x & armhf
Thanks
--
Mathieu
Reply to: