tags 412970 + pending thanks On Fr, 2007-03-02 at 15:21 +0100, Rene Engelhard wrote: > [ resend to the bug and the ml, sorry... ] > > Hi, > > Sebastian Dröge wrote: > > could you please describe a bit more verbose what exactly you are doing? > > Sure. > > > Where can one get the source in question and how can one reproduce it? > > http://people.debian.org/~rene/openoffice.org/2.2. > Already in NEW with the workaround being build-depending against > mono-utils >= 1.2.3 explicitly) > > How to reproduce it? Just build it with mono-mcs, mono-gmcs, mono-gac, > libmono-dev (and its deps) from experimental *but* with mono-utils > 1.2.2.1-2. > > dh_makeclilibs and dh_clideps will fail. > > > Also what's the output of dh_makeclilibs and dh_clideps? > > with all mono packages on 1.2.3.1-1: > > dh_makeclilibs -V > dh_makeclilibs: > debian/openoffice.org-dev/usr/share/java/openoffice/win/unowinreg.dll > has no valid signature, ignoring > dh_clideps > dh_clideps: Warning: Could not resolve moduleref: uno_cppu for: > cli_uno_bridge.dll! > dh_clideps: Warning: Could not resolve moduleref: cli_uno for: > cli_uno_bridge.dll! > dh_clideps: Warning: Could not resolve moduleref: sal for: > cli_uno_bridge.dll! > dh_clideps: Warning: Could not resolve moduleref: cli_uno_glue for: > cli_cppuhelper.dll! > Error while trying to process unowinreg.dll > Error while trying to process unowinreg.dll > > (unowinreg.dll is expected, because that's no mono dll but a "real" windows > JNI dll - and before you even think of filing a bug, yes it's rebuilt - > using mingw32)
Just out of curiosity... why would you want to ship a real windows dll with the openoffice packages? How is this used? > With all mono packages on 1.2.3.1-1 *except* mono-utils (which is > at 1.2.2.1-2). Ok, thanks... With the next upload of mono mono-utils will depend on libmono-corlib1.0-cil with a stricter version requirement. This should solve all your issues then... Bye
signature.asc
Description: This is a digitally signed message part
