On Sat, Oct 27, 2018 at 08:34:49AM +0530, Pirate Praveen wrote:
>
>
> On 2018, ഒക്ടോബർ 27 2:38:23 AM IST, Adrian Bunk <[email protected]> wrote:
> >No, it is not.
> >
> >I would expect everything that fails during build time to fail the same
> >
> >way at runtime.
> >
>
> Can you reproduce the bug? Once it is built against the correct version, it
> will use that version only.
After downgrading libarcus3 to 3.3.0-1:
$ CuraEngine
[libprotobuf FATAL google/protobuf/stubs/common.cc:79] This program was
compiled against version 3.0.0 of the Protocol Buffer runtime library, which is
not compatible with the installed version (3.6.1). Contact the program author
for an update. If you compiled the program yourself, make sure that your
headers are from the same version of Protocol Buffers as your link-time
library. (Version verification failed in "google/protobuf/any.pb.cc".)
terminate called after throwing an instance of
'google::protobuf::FatalException'
what(): This program was compiled against version 3.0.0 of the Protocol
Buffer runtime library, which is not compatible with the installed version
(3.6.1). Contact the program author for an update. If you compiled the program
yourself, make sure that your headers are from the same version of Protocol
Buffers as your link-time library. (Version verification failed in
"google/protobuf/any.pb.cc".)
Aborted
$
Properly handling this in package like libarcus3 becomes difficult once
you consider that such packages might be backported to stretch-backports
and would use libprotobuf10 there.
We might even end up with upgrade failures if a user could end up with
a nonworking combination of packages installed during an upgrade, and
a maintainer script calls such a nonworking program.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
