[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#888238: marked as done (nmu: caffe_1.0.0-5)

Your message dated Fri, 26 Jan 2018 03:22:47 +0000
with message-id <CAGX5NraVD81KmyXPHNaL5JidTwAXQWWKnij6nrBHCEponJ8aPw@mail.gmail.com>
and subject line Re: Bug#888238: nmu: caffe_1.0.0-5
has caused the Debian Bug report #888238,
regarding nmu: caffe_1.0.0-5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
888238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888238
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: binnmu
Severity: normal

Hello,

The current binary dependency of libcaffe-cpu1 includes
    libboost_python-py35.so.1.62.0
However this shared object is nolonger available in the boost package
since python3.6 turns to default. This problem caused CI failures:
    https://ci.debian.net/data/autopkgtest/unstable/amd64/c/caffe/20180107_013801/log.gz
Please rebuild caffe against libboost_python-py36.so.1.62.0
shipped by libboost-python1.62.0 (>= 1.62.0+dfsg-5)
on any architecture.

nmu caffe_1.0.0-5 . ANY . -m "Rebuild against libboost_python-py36.so.1.62.0"

Thanks

-- 
Best,

--- End Message ---
--- Begin Message --- 
On 25 January 2018 at 17:51, Emilio Pozuelo Monfort <pochu@debian.org> wrote:
> This looks like a bug somewhere if libboost-python1.62.0 changed from python3.5
> to python3.6 on a rebuild when the default python3 version changed, thus
> changing the shared library shipped by it as it embeds the python version,
> without a rebuild forced on its users. The bug is not necessarily in boost, it
> could be in caffe as it got rebuilt with python3.6 and yet it picked up a
> dependency on libboost_python-py35.so.1.62.0. We may need stricter dependencies
> so we detect that rebuilds are needed, plus we may want to fail builds when such
> inconsistencies are found. E.g. see the mixed 3.5 and 3.6 in here:
>
> From
> https://buildd.debian.org/status/fetch.php?pkg=caffe&arch=i386&ver=1.0.0-5&stamp=1513655544&raw=0

Investigated into it. This is basically caused by one of my old patches
which hardcoded python3.5 to the cmake build for a temporary fix.

>> -- Found PythonLibs: /usr/lib/i386-linux-gnu/libpython3.6m.so (found suitable version "3.6.4rc1", minimum required is "3.0")
>>   No header defined for python-py3641; skipping header check
>>   No header defined for python-py361; skipping header check
>>   No header defined for python-py31; skipping header check
>> -- Could NOT find Boost

It is Caffe's cmake problem to not check python-py36 when "1" in "rc1"
is incorrectly parsed into python version.
When these checks all failed, cmake will enter a branch where python2 is used.
I patched that branch long time ago for a temporary fix, by hardcoding
python3.5 in the branch.

>> -- Found the following Boost libraries:
>> --   python-py35
>
> Something looks fishy there.

Yes, until I realized that this weird thing is caused by one of my
patches for a temporary fix.
It is coincidental for this package to build successfully when
python3_3.6.4-rc1 and
libboost-python1.62.0_1.62.0+dfsg-4 exists at the same time...

That patch is fixed in the git repo:
https://salsa.debian.org/science-team/caffe/commit/4a0a139a5eb153db9f23a7255cae4c59e56b7cc4

 I'll prepare the 1.0.0-6 upload, so there is no need for an NMU.
Sorry for the noise. :-)

-- 
Best,

--- End Message ---
Reply to: