Hi Juhani,
Bug #974074 is in fact a bug in MRS. However, the bug report does
contain a useful observation, the usage of the various
override_dh_auto_configure rules in libzeep is incorrect and no shared
library is created.
Now the question is, is a shared library really required? If so I
On Wed, Nov 11, 2020 at 11:09:32AM +0100, Maarten L. Hekkelman wrote:
> Hi Juhani,
>
> Bug #974074 is in fact a bug in MRS. However, the bug report does contain a
> useful observation, the usage of the various override_dh_auto_configure
> rules in libzeep is incorrect and no shared library is
On Tue, 10 Nov 2020 23:03:57 +0100 Sebastian Ramacher
wrote:
> Hi Marten
>
> On 2020-11-10 07:42:45 +0100, Maarten L. Hekkelman wrote:
> ...
> >
> > Sorry, long story. To make it short.
> > - Keep mrc, no problem there
> > - Upgrade libzeep to version 5
> >
>
> Thanks for the detailed
Hi Marten
On 2020-11-10 07:42:45 +0100, Maarten L. Hekkelman wrote:
> Hi Andreas,
>
> To avoid confusion, we're talking about three tools here: libzeep, mrc and
> mrs.
>
> mrc is a simple resource compiler, is now compatible and bug free, builds on
> all architectures and should be kept. I
Hi Andreas,
To avoid confusion, we're talking about three tools here: libzeep, mrc
and mrs.
mrc is a simple resource compiler, is now compatible and bug free,
builds on all architectures and should be kept. I believe it is very
useful, using it I can create downloadable, portable
On Tue, 10 Nov 2020 08:18:27 +0100, Andreas Tille wrote:
> On Tue, Nov 10, 2020 at 07:42:45AM +0100, Maarten L. Hekkelman wrote:
> > Sorry, long story. To make it short.
> > - Keep mrc, no problem there
> > - Upgrade libzeep to version 5
libzeep is already at version 5 in unstable but has some
Hi Maarten,
On Tue, Nov 10, 2020 at 07:42:45AM +0100, Maarten L. Hekkelman wrote:
> ...
Thanks a lot for the explanation.
> Sorry, long story. To make it short.
> - Keep mrc, no problem there
> - Upgrade libzeep to version 5
> - Kick out mrs until it is upgraded to use libzeep 5
I'd recommend
I'm sorry, but mrs as it is currently in Debian is not compatible with
libzeep version 5. It needs a major rewrite. Libzeep is a spin off
project of mrs and has evolved a lot since then.
So either libzeep should be kept at version 3 or mrs should be removed.
If mrs and libzeep are kept, I
Hi Maarten,
On Mon, Nov 09, 2020 at 07:22:30PM +0100, Maarten L. Hekkelman wrote:
> I'm sorry, but mrs as it is currently in Debian is not compatible with
> libzeep version 5. It needs a major rewrite. Libzeep is a spin off project
> of mrs and has evolved a lot since then.
>
> So either libzeep
Control: clone -1 -2
Control: reassign -2 src:libzeep 5.0.0-1
Control: retitle -2 "src:libzeep: override targets never called"
Control: block -1 with -2
On Mon, 09 Nov 2020 15:19:21 +, Niko Tyni wrote:
> Looks to me like libzeep-dev is broken because the build
> doesn't pass --enable-shared
Processing control commands:
> clone -1 -2
Bug #974016 [src:mrs] mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for
libzeep...libzeep is not installed"
Bug 974016 cloned as bug 974074
968912 was blocked by: 972275 968913 961157 972274 961155 974061 964902 961154
960863 961152 974063 974058
On Mon, Nov 09, 2020 at 09:17:25AM +0200, Juhani Numminen wrote:
> Source: mrs
> Version: 6.0.5+dfsg-8
> Severity: serious
> Tags: ftbfs sid
> Justification: fails to build from source (but built successfully in the past)
> | Checking for libzeep...libzeep is not installed, either install the
Source: mrs
Version: 6.0.5+dfsg-8
Severity: serious
Tags: ftbfs sid
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
mrs fails to build from source on multiple architectures, with the message
quoted below. See
13 matches
Mail list logo
