Re: #809589

[Mathieu Malaterre <malat@debian.org>]

On Tue, Feb 16, 2016 at 3:39 PM, Jo Shields <directhex@apebox.org> wrote:
>
>
> On 16/02/16 14:32, Mathieu Malaterre wrote:
>> [CC me please]
>>
>> I was trying to reproduce #809589 (no luck so far) to get my package
>> back in shape. However I cannot get all the steps to the package
>> generatation it currently fails with:
>>
>> dh_clideps: Warning! No Build-Depends(-Indep) on cli-common-dev (>= 0.8~)!
>> /usr/bin/monodis: /usr/lib/libmonosgen-2.0.so.1: no version
>> information available (required by /usr/bin/monodis)
>> /usr/bin/monodis: relocation error: /usr/bin/monodis: symbol
>> mono_opcodes, version VER_1 not defined in file libmonosgen-2.0.so.1
>> with link time reference
>> dh_clideps: cli_parser call failed: 'LANG=C MONO_PATH=
>> MONO_GAC_PREFIX=  /usr/bin/monodis --moduleref
>> StucturedStorageExplorer.exe 2>&1 > /tmp/dh_clideps.i8fA' rc: 32512
>> output:
>> debian/rules:4: recipe for target 'binary' failed
>> make: *** [binary] Error 127
>> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
>>
>>
>> This is within a 32bits sid chroot running on 64 bits debian/stretch.
>
> Which version of mono-utils? I'm pretty sure Debian's monodis isn't
> built against libmonosgen

Right I had a messed up environment. Sorry for the noise.