Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Geert Stappers Newsgroups: linux.debian.maint.python Subject: Re: Fwd: Problem with reprotest-kernel Date: Thu, 14 May 2020 21:30:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu May 14 19:25:30 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20170113 (1.7.2) X-Mailing-List: archive/latest/18280 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20200514192514.ord67bnmu5fxwvt6@gpm.stappers.nl Approved: robomod@news.nic.it Lines: 70 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 14 May 2020 21:25:14 +0200 X-Original-Message-ID: <20200514192514.ord67bnmu5fxwvt6@gpm.stappers.nl> X-Original-References: <9c231f3b-7179-5ea2-0471-b4ae17696ced@fortysixandtwo.eu> <20200514184730.52epzo42pfvaqhf5@gpm.stappers.nl> Xref: csiph.com linux.debian.maint.python:12584 On Thu, May 14, 2020 at 09:11:51PM +0200, 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 > >> > >> > >> Subject: Problem with reprotest-kernel > >> Date: Thu, 14 May 2020 15:44:21 +0200 > >> From: Evangelos Ribeiro Tzaras > >> To: debian-python@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 [1]. > >> > >> Effectively the ImportError is raised here [2]: > >> 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? Good question. Sadly I can't tell what the differences are between the testbed and the non-testbed. Hopefully is the answer to the original problem in making the non-testbed more like the testbed. > >> So far I found out that uname -a prints 4.9.0-12-amd64 for testbed and > >> 2.6.69-12-amd64 for build-experiment-1. On a local build I have seen > >> some "FATAL: kernel too old" messages[3], but they don't show up in the > >> logs[4], so I am wondering if it also happens on the CI but also does > >> not show in the logs. > >> > >> A quick ddg search yielded [5] . Can anyone give me any insights? > >> Because I feel disabling the kernel variation (without fully > >> understanding the issue) is not the winning move here :) > >> > >> Thanks in advance > >> > >> [1] https://salsa.debian.org/devrtz/pyzbar/-/jobs/738921#L1116 > >> [2] https://salsa.debian.org/devrtz/pyzbar/-/blob/master/pyzbar/zbar_library.py#L63 > >> [3] https://fortysixandtwo.eu/img/reprotest_kernel_too_old.png > >> [4] https://fortysixandtwo.eu/img/reprotest_too_old_not_in_log.png > >> [5] http://debian.2.n7.nabble.com/Bug-928921-reprotest-kernel-too-old-SIGSEGV-td4512112.html > >> Regards Geert Stappers P.S. I'm on both mailinglists, no need to CC me. -- Silence is hard to parse