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

Bug#832429: Failure when trying to build



On Mon, Sep 12, 2016 at 12:26:01PM +0100, Ghislain Vaillant wrote:
> >CMakeFiles/Makefile2:88: recipe for target 'library/CMakeFiles/clSPARSE.dir/all' failed
> >make[2]: *** [library/CMakeFiles/clSPARSE.dir/all] Error 2
> >...
> 
> Indeed, I forgot our current OpenCL C++ setup is broken in sid:
> 
> https://packages.debian.org/sid/opencl-headers
> 
> dep: opencl-clhpp-headers (>= 2.0.10)
>     Package not available
> 
> So we'll have to wait for #837112 to be fixed first I guess. I should
> have remembered.

I've pinged ftpmaster about this the day before yesterday ...
 
> >BTW, is there any good reason to replace the master branch by
> >debian/master.  Gbp clone always makes noise about it and I need to
> >check what branches you are using.
> 
> That's my fault I forgot to update the symbolic link to HEAD (fixed
> now). Otherwise, the repository layout is clearly defined in gbp.conf,
> so gbp buildpackage should behave appropriately.

Gbp behaves correctly - except that after cloning I get an empty dir and
need to guess what branch to use.
 
> >I'd prefer the defaults specified in our team policy.
> 
> I adopted DEP-14 [1] which is supposed to be the most flexible scheme.
> 
> The nice thing with debian/master is that it is both applicable for
> upstream git (since they use a master branch already) and import-orig
> based packaging.
> 
> [1] https://lists.debian.org/debian-devel/2014/11/msg00444.html

I'd consider this a valid reason - but if I want to switch all my
repositories because of this - hmmmm ...
 
Kind regards

       Andreas.

-- 
http://fam-tille.de


Reply to: