As said. The files are mentioned in All Reference Guides - ROOT , but are missing.
Hi @mlo,
Thanks for pointing that out.
It seems like html636
files are indeed missing, but most other links do work, we will fix the broken links. Let me add @couet in the loop.
Cheers,
Dev
Yes only that one is missing . I’ll see if there is a reason for that.
All looks fine in the github action. I must admit I do not understand fro the time being. 636 does the same as 634…
I am not sur but the name of the ta file may have changed. Can you try: https://root.cern/download/htmlv6-36-00-patches.tar.gz
Indeed the tar files of older versions (ie 6.34) are following the old naming scheme and point to old version of the tar files. I will fix the web site in order to point to the new versions.
This PR fixes the problem fix the links by couet · Pull Request #1127 · root-project/web · GitHub
Thanks to have seen it.
I downloaded htmlv6-36-00-patches.tar.gz ; v6-36-00-patches has a subdirectory “html” with a content similar to the one of v634. There is an index.html that, when opened, shows the complete manual for v636. Why a new subdirectory? Why the “patch” string in the name? At a first sight, I interpreted the name as identifying something intended for the unix utility patch(1). But, more important, the “all reference guides” page of the root program (https://root.cern.ch/reference) shows clearly a link with the names html636.tar.gz - html636.tar.xz that, if followed, go to error 404. And - the xz version?
The of the tar ball changed since we go to github action to build the doc. We do not generate the xz anymore.
Just to be clear – I need to:
- download and unpack https://root.cern/download/htmlv6-36-00-patches.tar.gz (I still don’t understand the “-patches” but this is your business) ;
- replace my soft link to /MyChoice/v634/index.html with /MyChoice/v6-36-00-patches/html/index.html ;
- Nothing will change in the near future;
- When root_v6.36.00 will be released, there will be a file htmlv6-36-01-patches.tar.gz .
TIA - mlo
Sorry for that changes. We recently moved from jenkins CI to a github-action CI. There was a lot of changes in that process and we are still investigating/experimenting. We concentrated primarily on master the older version 632 → 636 came after.