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

Bug#779912: unblock: cdbs/0.4.128



On 2015-03-06 14:17, Jonas Smedegaard wrote:
> Quoting Niels Thykier (2015-03-06 12:10:47)
>> On 2015-03-06 11:58, Jonas Smedegaard wrote:
>>> Additionally, the fix for #770767 is believed to also fix applying 
>>> all default security-strengthening compiler flags for arch-any 
>>> packages that uses a CDBS perl snippet.  Since that is a release 
>>> goal, and since missing default flags may also lead to other breakage 
>>> on i386 due to how that platform links perl code (see bug#770767), 
>>> unblocking of cdbs should probably be followed by BinNMUs + unblock 
>>> of e.g. all arch-any packages matching regext 
>>> '^include\s+.*perl.*\.mk' for its rules file.
>>
>> We might not want that actually.
> 
> Why?
> 
> Please note that your search below include far too many packages: most 
> perl libraries are arch-all which need not - and cannot - be BinNMUed.
> 

Indeed it did.

> 
>>> I don't know (and am not skilled so now is probably the wrong time to 
>>> start if others can help) how to reliably locate such package list, 
>>> but can do it among the packages I maintain myself which might be 
>>> adequate (I am not alone in using CDBS but might be for perl libs 
>>> specifically).
> 
>> Probably
>> http://codesearch.debian.net/results/include%5Cs+.*perl.*%5C.mk%20path:debian/rules/page_0
> 
> I knew of that search, but it locates _all_ packages using perl snippet 
> - not only arch-any packages.  I can only think of needing to both grep 
> rules file for snippet inclusion and control file to exclude arch-all - 
> but I don't think such cross-file combo is possible with codesearch.d.n.
> 

Indeed, my bad.

> 
>> And then the "To see all packages which contain results:" cmd.
> 
> Where is that command?
> 
> 
>  - Jonas
> 

When I tried the search, codesearch showed me a command for figuring out
the affecting packages.  Something like:

  curl -s http://codesearch.debian.net/results/.../packages.json | \
    jq -r '.Packages[]'

Didn't work for me as I did not have jq though.

~Niels


Reply to: