As I saw the new version: First thing to do was update the package. Due to my trouble compiling the binary architecture dependent I have uploaded to debian “experimental” first. It makes no sense to upload to debian “unstable”, because of the deep freeze phase of debian.
Here is a quote from the stockfish team:
“So almost 700 lines of code removed for this release.Actually we didn’t plan to release now, but it happens that our test framework will be down for a couple of weeks due to new year holidays and so, instead of just waiting two weeks, we thought it could be more useful to release.
The release number 2.0 is to be intended as the new year release not as a much improved version from 1.9.1: we expect some ELO gain but nothing earth shattering.”
The debian packages do build in 12 architectures and I will have to push the buildd maintainer to enable building on all 14. AMD64 and i386 builds are with profiling and optimization.
There is a series file in the patches directory. You have to add the patch there too…
Ive been looking into the new maintainer howto to try and understand how I should properly patch an existing Debian package in case a Sarge package rsync..Im being confronted with a rather anoying bug in rsync which totally brakes rsnapshot for me. Read all about that in ..Although I quite understand what Debian stable is all about I fail to understand how a non-security bug that nevertheless severely breaks a package is not solved in Debian stable. .The problem is the bug remains I suspect the patch didnt get applied..Basically what I did was update the changelog and saving the patch in debian patches.