Problem with reprotest-kernel, my build attempt fails

[Evangelos Ribeiro Tzaras]

Thank you for your answer.

On 5/18/20 6:25 PM, Geert Stappers wrote:
> On Sun, May 17, 2020 at 05:22:49PM +0200, Evangelos Ribeiro Tzaras wrote:
>> On 5/14/20 9:11 PM, Evangelos Ribeiro Tzaras wrote:
>>> On 5/14/20 8:47 PM, Geert Stappers wrote:
>>>> On Thu, May 14, 2020 at 07:27:26PM +0200, Evangelos Ribeiro Tzaras wrote:
>>>>> Hello,
>>>>>
>>>>> I have a problem with reprotest on a python package I am building
>>>>> and was recently made aware of this mailinglist.
>>>>>
>>>>> Can anyone tell me what's going on, how I can further debug my issue or
>>>>> ideally how I should fix the issue of a failing reprotest-kernel build?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>>
>>>>> -------- Forwarded Message --------
>>>>> Subject: Problem with reprotest-kernel
>>>>> Date: Thu, 14 May 2020 15:44:21 +0200
>>>>> From: Evangelos Ribeiro Tzaras <devrtz at fortysixandtwo.eu>
>>>>> To: debian-python at lists.debian.org
>>>>>
>>>>> Hello,
>>>>>
>>>>> I need some help with a failing reprotest-kernel (other reprotest works)
>>>>> build (both on CI and locally). My package python3-pyzbar provides
>>>>> bindings for libzbar0.
>>>>> The failure occurs while running the build-time tests for
>>>>> build-experiment-1.
>>>>>
>>>>> Effectively the ImportError is raised here:
>>>>> ctypes.util.find_library('zbar') returns None in build-experiment-1
>>>>> (testbed still works).
>>>>
>>>> My first impression would be a missing build dependency.
>>>>
>>>
>>> Maybe I am missing something obvious, but why would the build (and the
>>> failing test) succeed in the testbed if a dependency were missing?
>>>
>>
>> After some further investigation, I have figured out a solution.
>> Changing the build dependency to the -dev package (from libzbar0 to
>> libzbar-dev) has fixed the failing reprotest-kernel job. I tried this
>> out after reading that ctypes.util.find_library is usually used to
>> lookup build-time dependencies rather than run-time dependencies.
>>
>> Local builds and other reprotest variations work fine without the -dev
>> package. Can someone share some insight into why reprotest-kernel needs
>> the -dev package?
>>
>> Thanks in advance
>>
> 
>> Can someone share some insight into why reprotest-kernel needs the -dev package?
> } Can someone share some insight into why building reprotest-kernel needs the -dev package?
> 
>  -dev is a naming convention
> 
> Those packages contain the development files.  (stuff that the compiler needs)

Maybe I should have worded it better. My question is:
What could be the reason that reprotest-kernel need the -dev package,
while other variations are fine with non-dev package?

> 
> 
> Regards
> Geert Stappers
> 

Evangelos Ribeiro Tzaras