Thanks for the reply, unfortunately I already tried all that, and it did not work. Here is what I get:
$> ./naclsdk list
*: update available
I sdk_tools (stable)
I pepper_26 (post_stable)
I pepper_27 (post_stable)
I pepper_28 (post_stable)
I pepper_29 (post_stable)
I pepper_30 (stable)
I pepper_canary (canary)
All installed bundles are up-to-date.
Bundles installed locally that are not available remotely:
I pepper_16 (post_stable)
I pepper_20 (stable)
I pepper_21 (stable)
$> ./naclsdk update pepper_25
WARNING:Ignoring unknown bundle(s): pepper_25
WARNING:No bundles to update.
I'm aware it is just a problem with 'naclsdk' hiding the old bundles, and that it is possible to give a special 'manifest' URL (see the 'naclsdk help' command), but after one day of searching on Google, I really found no more info about how to do to get 'pepper_25'.... :(
An interesting thing is that on another computer, I have an old 'naclsdk' script, and this one is listing 'pepper_16' and 'pepper_17' only, but cannot get 'pepper_25' from it either... and if I update the script, it will get the latest version, the one that is not showing 'pepper_25' either... I guess I would need an 'intermediate' version of the script, that is asking to another manifest file, or something like that...
Any solution would be welcome...