I signed it manually as explained on another post of the forum ...!
As explained earlier in the post I got really mad about this

and through away my PC through the window ...
No in fact The application was not rolled out on an important number of users (and especially I know many of them), so I "unpublished" the previous one and published a new one with a brand new private key ... easy but loosing the already (small!) installed based!
If it might help someone else: What I tried to do before giving up:
1) I signed my apk manually as described in another post of the forum. I tried different variation on key signing algorithm (cf. batch file attached some variation as comment with
), but no way!
It nevers worked despite some versions could be uploaded to the market sucessfully passing google post upload treatment ...!?
2) When checking the signed apk with
, I had the following kind of issues: "
[certificate is valid from 11/28/13 10:38 AM to 4/15/41 11:38 AM] [CertPath not validated: Path does not chain with any of the trust anchors]sm
"
3) I googled the web for "
CertPath not validated: Path does not chain with any of the trust anchors
", the articles I found (all aged about one year ago) explained issues with latest jdk, and advise an older version of jdk ...
I tried to uninstall jdk to install older ones with 3 different versions but keep on facing same issue ...
Anyway, tired from testing stupid things with no clear vision of what was going wrong, I give up and I handled it differently ...!
Thanks anyway ...