building shiny server on debian 11 fails

[litschkot]

using the instructions on the respective wiki page I experience the following error with cmake command. How can I circumvent this? Or is there a need to update hash values? Thanx for any help to a newbie.

`/shiny-server/tmp$ cmake -DCMAKE_INSTALL_PREFIX=/usr/local ../ -- The C compiler identification is GNU 10.2.1 -- The CXX compiler identification is GNU 10.2.1 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Downloading pandoc CMake Error at external/pandoc/CMakeLists.txt:48 (file): file DOWNLOAD HASH mismatch

for file: [/home/litschkot/shiny-server/tmp/external/pandoc/pandoc.gz]
  expected hash: [159438262cd1c0d5a6d5d50db53251d209aa5018]
    actual hash: [da39a3ee5e6b4b0d3255bfef95601890afd80709]
         status: [28;"Timeout was reached"]

-- gunzip /home/litschkot/shiny-server/tmp/external/pandoc/pandoc.gz

gzip: /home/litschkot/shiny-server/tmp/external/pandoc/pandoc.gz: unexpected end of file CMake Error at external/pandoc/CMakeLists.txt:65 (message): Failed to gunzip /home/litschkot/shiny-server/tmp/external/pandoc/pandoc.gz

-- Configuring incomplete, errors occurred!`

[roman-tremmel]

Have you solved the problem?

Here almost the same error.

-- Downloading pandoc
CMake Error at external/pandoc/CMakeLists.txt:48 (file):
  file DOWNLOAD HASH mismatch

    for file: [/home/usr/shiny-server/tmp/external/pandoc/pandoc.gz]
      expected hash: [159438262cd1c0d5a6d5d50db53251d209aa5018]
        actual hash: [da39a3ee5e6b4b0d3255bfef95601890afd80709]
             status: [22;"HTTP response code said error"]

Since I'm sitting behind a proxy (which is defined in the environment variable), I assume that the error is related to a connection problem.

[litschkot]

Hi Roman, I think, the error message is misleading and indeed, it was a connection issue in my case. Giving NPM it's own forward proxy definition in '.npmrc' solved the problem. As with apt and R. npm also doesn't use the sessions environment variable.