Control: severity 837565 serious

On Sat, Oct 22, 2016 at 11:18:44AM +0200, Rene Engelhard wrote:
> severity 837565 important
> thanks
> 
> Hi,

Hi Rene,

> On Fri, Oct 21, 2016 at 09:57:07PM +0000, Debian Bug Tracking System wrote:
> > Bug #837565 [liblpsolve55-dev] liblpsolve55-dev: Please build 
> > liblpsolve55.a with -fPIC
> > Severity set to 'serious' from 'important'
> 
> If this bug was assigned to mccs and was a FTBFS, you were right. This isn't,
> though.
> 
> And it's not RC in lpsolve55-dev. There's a extra _pic variant there one
> could have been (and should since ever a PIC library needed to include a .a)
> to be used.
> 
> That this PIE thingy now broke mccs' build is not liblpsolve55-devs fault.
> 
> But yes, the fix probably is to ditch the _pic variant (so much work for
> people not using it, sigh) and give in building liblpsolve55.a with -fPIC.
> 
> That doesn't make it RC _in liblpsolve55-dev_, though.

mccs in unstable does FTBFS, and this has to be an RC bug somewhere.

If the bug is that mccs does not use the _pic variant and the fix should 
be to make it use that, then reassign this bug to src:mccs.

If you plan to give in building liblpsolve55.a with -fPIC, that's
a wishlist bug against liblpsolve55-dev. But it inherits RC severity 
through fixing a FTBFS in mccs. Version tracking does not really
support that an lp-solve upload fixes an RC bug in mccs.

I have no opinion which of the packages should be changed,
and it is fine for me if you reassign this bug to mccs.

> Regards,
> 
> Rene

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Reply via email to