Html636.tar.gz/xz missing: error 404

Site Feedback
1

As said. The files are mentioned in All Reference Guides - ROOT , but are missing.

2

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

3

Yes only that one is missing . I’ll see if there is a reason for that.

4

All looks fine in the github action. I must admit I do not understand fro the time being. 636 does the same as 634…

5

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

6

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.

7

This PR fixes the problem fix the links by couet · Pull Request #1127 · root-project/web · GitHub
Thanks to have seen it.

8

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?

9

The of the tar ball changed since we go to github action to build the doc. We do not generate the xz anymore.

10

Just to be clear – I need to:

  1. 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) ;
  2. replace my soft link to /MyChoice/v634/index.html with /MyChoice/v6-36-00-patches/html/index.html ;
  3. Nothing will change in the near future;
  4. When root_v6.36.00 will be released, there will be a file htmlv6-36-01-patches.tar.gz .

TIA - mlo

11

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.

12

My interpretation:

“-patches” means it corresponds this branch of GitHub: GitHub - root-project/root at v6-36-00-patches
which is also called the “tip” of the 6.36 branch,

The old naming of just writing “6.36” in the file name is ambiguous, since one does not know if it refers to 6.36.00 or 6.36.02 patch release or …
By specifying ‘patches’, it’s clear that it’s the latest commit or patch release of that 6.36 version.

There is also htmlmaster, which refers to the master branch of the git repository.

Both tar files are being continuously updated on the web when commits are pushed to the master branch or the tip of the 6.36 branch.

That was probably unintended when creating the TAR file in the new script, but @couet can confirm.

13

As I said we changed from Jenkins to Github Actions. We concentrate 1st on master. Right now the 6.3x have problem… I am on it.

14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.