Bug#922584: [Help] Re: FTBFS against opencv 4.0.1 (exp)

2022-12-03 Thread Roelof Berg
I agree, it’s also unmaintained. Let’s take it out. Roelof (Author and original packager) Von meinem Mobiltelefon gesendet. > Am 02.12.2022 um 10:38 schrieb Andreas Tille : > > Am Thu, Dec 01, 2022 at 11:39:47PM +0200 schrieb Adrian Bunk: >> [1] contains a patch from a Debian porter, but consi

Bug#922584: [Help] Re: FTBFS against opencv 4.0.1 (exp)

2022-12-02 Thread Andreas Tille
Am Thu, Dec 01, 2022 at 11:39:47PM +0200 schrieb Adrian Bunk: > [1] contains a patch from a Debian porter, but considering the facts > that limereg already missed the current Debian stable bullseye and the > comment from upstream (who is also the original Debian packager) in [2], > removal from

Bug#922584: [Help] Re: FTBFS against opencv 4.0.1 (exp)

2022-12-01 Thread Adrian Bunk
On Mon, Nov 23, 2020 at 05:49:42PM +0100, Andreas Tille wrote: > Control: tags -1 help > > Hi, > > the configure step checks for the existence of opencv and only if > available builds the executable limereg. I found a (hackish) solution > in Git[1] to convince configure that opencv is available.

Bug#922584: [Help] Re: FTBFS against opencv 4.0.1 (exp)

2020-11-23 Thread Andreas Tille
Control: tags -1 help Hi, the configure step checks for the existence of opencv and only if available builds the executable limereg. I found a (hackish) solution in Git[1] to convince configure that opencv is available. However, the code tries to include cv.h which is not available any more. I