Hi,
On Samstag, 18. Juli 2015, Chris Lamb wrote:
Fixed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792491
shouldn't we upload dpkg with that fix to our repo then?
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
shouldn't we upload dpkg with that fix to our repo then?
If the impact was more widespread, then definitely.. but am tempted to
wait until some response from dpkg maintainers, especially as I'm not
100% confident in the patch.
--
,''`.
: :' : Chris Lamb
`. `'`
btw: https://reproducible.debian.net/rb-pkg/unstable/amd64/pyopencl.html
After fixing the other issues, I now have a reproducability rate of 50% ...
IIRC you are repeating a failed test once to ignore some spurious
failures? So you would end up at an error rate of 25% - or less if you
On 2015-07-09 18:38, Holger Levsen wrote:
PPS: Similarly complex symbols files are used by ocl-icd-libopencl1
and nvidia-libopencl1, too.
are these both only in non-free too?
ocl-icd is in main
and reproducible when tested in our setup:
https://reproducible.debian.net/ocl-icd
no, you
On Thu, Jul 09, 2015 at 08:23:12PM +0200, Holger Levsen wrote:
The issue is nondeterministic - a first rebuild after partly fixing
another reproducibility issue has not shown this again.
btw: https://reproducible.debian.net/rb-pkg/unstable/amd64/pyopencl.html
I recall some other cases,
Hi,
On Donnerstag, 9. Juli 2015, Andreas Beckmann wrote:
no, you need to test something that uses both OpenCL 1.1 and OpenCL 1.2
functions, e.g. amd-clinfo, erlang-cl, python{,3}-pyopencl{,-dbg}. That
list is complete - all rdepends of the libopencl-1.2-1 virtual package.
any of these in
