https://ci.appveyor.com/api/projects/status/l0i1kvh7o5qfk3ws?svg=true

• metanorma/packed-mn#87

Previous release v1.7.6 was done with the same [email protected] version so probably it fails due to runner image changed

Failed runner details:

2023-08-18T08:28:09.2075228Z Current runner version: '2.308.0'
2023-08-18T08:28:09.2109951Z ##[group]Operating System
2023-08-18T08:28:09.2110688Z Microsoft Windows Server 2022
2023-08-18T08:28:09.2111054Z 10.0.20348
2023-08-18T08:28:09.2111383Z Datacenter
2023-08-18T08:28:09.2111748Z ##[endgroup]
2023-08-18T08:28:09.2112107Z ##[group]Runner Image
2023-08-18T08:28:09.2112447Z Image: windows-2022
2023-08-18T08:28:09.2112809Z Version: 20230804.1.0
2023-08-18T08:28:09.2113399Z Included Software: https://github.com/actions/runner-images/blob/win22/20230804.1/images/win/Windows2022-Readme.md
2023-08-18T08:28:09.2114153Z Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20230804.1
2023-08-18T08:28:09.2114612Z ##[endgroup]
2023-08-18T08:28:09.2114994Z ##[group]Runner Image Provisioner
2023-08-18T08:28:09.2115374Z 2.0.266.1
2023-08-18T08:28:09.2115714Z ##[endgroup]

Success runner details:

2023-07-25T03:39:49.1758319Z Current runner version: '2.306.0'
2023-07-25T03:39:51.0974746Z ##[group]Operating System
2023-07-25T03:39:51.0975398Z Microsoft Windows Server 2022
2023-07-25T03:39:51.0975934Z 10.0.20348
2023-07-25T03:39:51.0976244Z Datacenter
2023-07-25T03:39:51.0976514Z ##[endgroup]
2023-07-25T03:39:51.0977071Z ##[group]Runner Image
2023-07-25T03:39:51.0977361Z Image: windows-2022
2023-07-25T03:39:51.0977899Z Version: 20230716.1.0
2023-07-25T03:39:51.0978656Z Included Software: https://github.com/actions/runner-images/blob/win22/20230716.1/images/win/Windows2022-Readme.md
2023-07-25T03:39:51.0979504Z Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20230716.1
2023-07-25T03:39:51.0979860Z ##[endgroup]
2023-07-25T03:39:51.0980195Z ##[group]Runner Image Provisioner
2023-07-25T03:39:51.0980525Z 2.0.238.1
2023-07-25T03:39:51.0980799Z ##[endgroup]

To be investigated

A user has reported that after installing the latest Chocolatey package, he had to:

1. Manually install metanorma gems (https://www.metanorma.com/software/metanorma-cli/docs/installation/#installing-the-gems)

2. Manually install gem tzinfo-data to get rid of the https://github.com/tzinfo/tzinfo/wiki/Resolving-TZInfo::DataSourceNotFound-Errors

3. Was shown the following error:

        12: from C:/tools/ruby25/bin/metanorma:23:in `<main>'
        11: from C:/tools/ruby25/bin/metanorma:23:in `load'
        10: from C:/tools/ruby25/lib/ruby/gems/2.5.0/gems/metanorma-cli-1.1.8/exe/metanorma:11:in `<top (required)>'
         9: from C:/tools/ruby25/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in `require'
         8: from C:/tools/ruby25/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in `require'
         7: from C:/tools/ruby25/lib/ruby/gems/2.5.0/gems/bundler-2.0.1/lib/bundler/setup.rb:10:in `<top (required)>'
         6: from C:/tools/ruby25/lib/ruby/gems/2.5.0/gems/bundler-2.0.1/lib/bundler.rb:107:in `setup'
         5: from C:/tools/ruby25/lib/ruby/gems/2.5.0/gems/bundler-2.0.1/lib/bundler/runtime.rb:26:in `setup'
         4: from C:/tools/ruby25/lib/ruby/gems/2.5.0/gems/bundler-2.0.1/lib/bundler/runtime.rb:26:in `map'
         3: from C:/tools/ruby25/lib/ruby/gems/2.5.0/gems/bundler-2.0.1/lib/bundler/spec_set.rb:148:in `each'
         2: from C:/tools/ruby25/lib/ruby/gems/2.5.0/gems/bundler-2.0.1/lib/bundler/spec_set.rb:148:in `each'
         1: from C:/tools/ruby25/lib/ruby/gems/2.5.0/gems/bundler-2.0.1/lib/bundler/runtime.rb:31:in `block in setup'
C:/tools/ruby25/lib/ruby/gems/2.5.0/gems/bundler-2.0.1/lib/bundler/runtime.rb:319:in `check_for_activated_spec!': You have already activated isodoc 0.9.23, but your Gemfile requires isodoc 0.9.22. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

Finally the user had to run bundle exec metanorma ... and it worked.

@CAMOBAP795 can you attempt to reproduce these issues and provide the necessary PRs to ensure this doesn't happen?

The user should only need to install Chocolatey Metanorma, and can run metanorma ... directly.

Thanks!

For @CAMOBAP795

https://github.com/metanorma/chocolatey-metanorma/actions/runs/3862089946/jobs/6583471255

C:/Users/CONTAI~1/AppData/Local/Temp/ocrB2D0.tmp/lib/ruby/gems/2.7.0/gems/rouge-4.0.1/lib/rouge/lexer.rb:532:in `load': cannot load such file -- C:/Users/CONTAI~1/AppData/Local/Temp/ocrB2D0.tmp/lib/ruby/gems/2.7.0/gems/rouge-4.0.1/lib/rouge/lexers/../../../../../../../../../../../../../../ContainerAdministrator/AppData/Local/Temp/ocrB2D0.tmp/lib/ruby/gems/2.7.0/gems/rouge-4.0.1/lib/rouge/lexers/abap.rb (LoadError)
[8](https://github.com/metanorma/chocolatey-metanorma/actions/runs/3862089946/jobs/6583471255#step:5:9)

The problem is that this is published to chocolatey as 1.6.11 -- it looks like it doesn't work?

https://community.chocolatey.org/packages/metanorma/1.4.17.20211007#virus

Because our score is either 7 or 8 (tried a couple runs on virustotal.com), it is automatically held up preventing release:
https://www.virustotal.com/gui/file/d006fd078d8c73d0b13a77196944180f6c5cee2b7aeb74240bb5223251210a87?nocache=1

While these are all unknown virus scanners we might still want to remove/update the files that have been falsely flagged as malicious.

The problematic files are:

• cve-2017-6419-lzx-negative-spaninfo.chm
• stub.exe
• stubw.exe
• edicon.exe
• lzma.exe

Is it possible for us to remove or modify these files?

The actual scores are:

https://community.chocolatey.org/packages/metanorma/1.5.4/

The voodoo in this package for using @geraldcombs's xsltproc to set up libxml2/libxslt to build against is awesome.

I think it would be very useful for it to become a separate package , or be included into the xsltproc package . A quick-ish hack would be for the new package to include no files but merely post-process xsltproc, set envvars pointing to the correct include/lib location, and set/update PKG_CONFIG_PATH, etc.

It might even be possible to fix the .pc files in xsltproc/dist/lib/pkgconfig/ and get those to be usable with a pkgconfig.

The new package could then be a stable dependency for any packages needing a native libxml2/libxslt-dev

Is @metanorma interested in hosting such a new package , since you did the initial work?

A user has reported that Chocolatey installation on Windows failed with the message "Error: specified file setup doesn't exists".

https://github.com/metanorma/mn-samples-iso/actions/runs/3915699018/jobs/6694115248

From "gep13" a reviewer on Chocolatey:

gep13 (reviewer) on 20 Dec 2018 08:17:49 +00:00:

I know nothing about this software application, so I can't speak to how it is expected to work, but I don't think hard coding to c:/tools/ruby is a good idea.

First, the end user can change this location through an environment variable which defaults to c:/tools. Have a look at the ruby chocolateyInstall.ps1 file to see how it uses Get-ToolsLocation.

@CAMOBAP795 can you please help fix this? Thanks!

Path: https://chocolatey.org/packages/metanorma/1.0.10

Current status = Waiting for Maintainer to take corrective action

chocolatey-ops left the following comment(s):

metanorma has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/5b4128876df6e776deabd92ed6ec2046 for details.
The package status will be changed and will be waiting on your next actions.

NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
Please log in and leave a review comment if you have questions and/or comments.
If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Attention - DO NOT REPLY TO THIS MESSAGE!

No human moderators see packages until automated checks are passed or the maintainer uses the review comments box to respond. This is very important to understand, if a package has failed any automated checks, you must take action to fix or respond.
ATTENTION: If your package is failing any automated checks, the ONLY way to get in front of a human moderator is to follow the instructions in the next step.
If you need to update or respond to package review information, please login and visit your package page (listed below). Use the Add to Review Comments box ONLY, Disqus/Gist comments will not reach a human reviewer.
This may include review comments prior to the automated checks, check the status on the package - it must be in 'Ready' or 'Responded' to be in front of a human moderator.
You can also self-reject packages in certain scenarios - see self-reject for more information.
Package Url: https://chocolatey.org/packages/metanorma/1.1.4
Maintainer(s): ribose

Maintainer Notes

If we've asked you to make changes, repush your updated package with the exact same version (unless the change we requested was based on an incorrect version).

yq.exe file is not automatically installed during Metanorma installation via Chocolatey package on Windows. Thus, make command fails with the following output:

PS D:\Upwork\mn-samples-itu-master> make -f Makefile.win SHELL=cmd
A subdirectory or file C:\Users\Nermina.cache\xml2rfc already exists.
'yq' is not recognized as an internal or external command,
operable program or batch file.

After metanorma/packed-mn#118 it looks like GitHub Actions test environment can hide some issues. Mostly because a lot of preinstalled software

Possible solutions:

• check environment where chocolatey's pre-publish tests executes https://community.chocolatey.org/courses/creating-chocolatey-packages/building-testing-and-pushing, and review possibilities to run custom tests
• free third-party services which can be used to test metanorma on windows
• go back to appveyour just for test porpouse

cc @ronaldtse

VirusTotal changed their interface and I can't see what exactly those engines are complaining about.

I do know that the CHM files are still being copied and they must trigger some issue:
https://www.virustotal.com/gui/file/3894e66aa4aef6e71ea83865021aff61450c1ab8a9f137baf1e671ecf58a94c0/behavior/VirusTotal%20Observer

@CAMOBAP can you file an issue and make a PR to https://github.com/davispuh/ruby-libmspack to have the gemspec file exclude these test files?

This has been reported here: davispuh/ruby-libmspack#2

Originally posted by @ronaldtse in #66 (comment)

Integrate instructions from https://github.com/metanorma/mn-native-pdf/blob/master/README.adoc, as we are now integrating the functionality of that repository into metanorma

According to last run https://github.com/metanorma/chocolatey-metanorma/runs/751671464?check_suite_focus=true it looks like secrets.METANORMA_CI_PAT_TOKEN missing

@ronaldtse could you please have a look

Let's wait for https://pypi.org/project/id2xml/ the release

Currently problem is #31 (comment)

• port bash bellow

export IDNITS_URL=https://tools.ietf.org/tools/idnits/
export IDNITS_VER=$(curl -Ls $IDNITS_URL | grep -e 'tgz' | sed -e 's/.(idnits-.).tgz.*/\1/') ; echo ${IDNITS_VER}
curl -SL ${IDNITS_URL}${IDNITS_VER} | tar xzv
export PATH=$(pwd)/${IDNITS_VER}:${PATH}

• metanorma/ci#1

https://github.com/metanorma/mn-samples-un/pull/35/checks?check_run_id=611650211

The CHOCO_API_KEY is encrypted as this:

environment:
  my_variable:
    secure: hsyCpvNm18kiTWHdcPSN7PLra8FGfypgnSuviKQMBdY1LGnpjE4//JD1uQ+vnzU5

https://github.com/metanorma/hk-ogcio-infosec-docs/pull/27/checks?check_run_id=679680842

Checking metanorma-cli
The term 'metanorma' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Setup metanorma
ERROR: The term 'metanorma' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Environment Vars (like PATH) have changed. Close/reopen your shell to
 see the changes (or in powershell/cmd.exe just type `refreshenv`).
The install of metanorma was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\metanorma\tools\chocolateyinstall.ps1'.
 See log for details.

Chocolatey installed 15/16 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

In appveyor.yml we specify the following packages to be installed.

- choco install -y git make gnuwin32-coreutils.portable sed

Metanorma MUST DEPEND on these chocolatey packages. git in particular is used for Metanorma to download templates, it is a "hard" dependency now.

https://github.com/metanorma/chocolatey-metanorma/runs/2685255782?check_suite_focus=true

This already happened for 1.8.3

Looks like Chocolatey has updated their automated validation. @CAMOBAP can you help address this? Thanks!

'metanorma' is Submitted.
Current status = Waiting for Maintainer to take corrective action

chocolatey-ops left the following comment(s):

metanorma has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

The IconUrl element in the nuspec file should be a valid Url. Please correct this More...
Attention - DO NOT REPLY TO THIS MESSAGE!

No human moderators see packages until automated checks are passed or the maintainer uses the review comments box to respond. This is very important to understand, if a package has failed any automated checks, you must take action to fix or respond.
ATTENTION: If your package is failing any automated checks, the ONLY way to get in front of a human moderator is to follow the instructions in the next step.
If you need to update or respond to package review information, please login and visit your package page (listed below). Use the Add to Review Comments box ONLY, Disqus/Gist comments will not reach a human reviewer.
This may include review comments prior to the automated checks, check the status on the package - it must be in 'Ready' or 'Responded' to be in front of a human moderator.
You can also self-reject packages in certain scenarios - see self-reject for more information.
Package Url: https://community.chocolatey.org/packages/metanorma/1.5.1
Maintainer(s): ribose, CAMOBAP

Maintainer Notes

If we've asked you to make changes, repush your updated package with the exact same version (unless the change we requested was based on an incorrect version).

• https://github.com/actions-mn/build-and-publish/actions/runs/3486977973/jobs/5834615721
• https://github.com/metanorma/chocolatey-metanorma/actions/runs/3434755533/jobs/5835098692

Always use "cinst metanorma -y" ("-y" is important!)

https://chocolatey.org/packages/metanorma/1.1.3

• The <owners> field is for your name / Chocolatey username.
• The <copyright> field is where you would put the software copyright and is intended to be in the format <year> <software author>.
• Can you point the <bugtrackerUrl> to the GitHub issues page instead of the project root?
• The <docsUrl> appears to be invalid (I'm getting a 504 error from Clouldflare when trying to connect). Can you advise / correct this?

FYI @ronaldtse

PS C:\Windows\system32> cinst metanorma -y
Chocolatey v0.10.11
Installing the following packages:
metanorma
By installing you accept licenses for the packages.
Progress: Downloading metanorma 1.0.10... 100%

metanorma v1.0.10 [Approved]
metanorma package files install completed. Performing other installation steps.
Installing gems...
C:\tools
ERROR: The term 'C:\tools\ruby25\bin\gem.cmd' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
The install of metanorma was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\metanorma\tools\chocolateyinstall.ps1'.
 See log for details.

Chocolatey installed 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - metanorma (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\metanorma\tools\chocolateyinstall.ps1'.
 See log for details.
PS C:\Windows\system32>

So the "gem.cmd" is not found?

All samples repos failing for windows:

• imagemagick.tool (exited 404) - Error while running 'C:\ProgramData\chocolatey\lib\imagemagick.tool\tools\chocolateyInstall.ps1'.

Full log https://github.com/metanorma/ogc-tcpnp/runs/1302596947?check_suite_focus=true

Intro

During actions-mn/setup#5 was observed that our -pre packages are broken because they looks for:
https://github.com/metanorma/packed-mn/releases/download/v1.5.4-pre/metanorma-windows-x64.exe instead https://github.com/metanorma/packed-mn/releases/download/v1.5.4pre/metanorma-windows-x64.exe

The repository github.com/metanorma has been set up to host all Metanorma related work. This is one such piece of work. While the migration will be slow (there is a lot to do, and a lot of interdependencies), we need to schedule migration for all related repositories.

Migration to Metanorma:

• Repost the repository to http://github.com/metanorma/X
  • This should be as simple as changing the following field in .git/config: [remote "origin"] url = https://github.com/riboseinc/metanorma-iso.git. Refer https://help.github.com/en/articles/transferring-a-repository
• If this is a Ruby gem, change the address of the repository in the *.gemspec
• Delete all files but the Readme in the riboseinc repository
• Replace the Readme in the riboseinc repository with the message "Repository migrated to http://github.com/metanorma/X
• Update the links to the repository in any documentation you maintain
• Link the README in the new location to updated links for appveyor, CodeClimate, travis, etc. New links to travis should be to travis-ci.com, not travis-ci.org.
• Notify @opoudjis and @strogonoff when you have migrated the repository. They will then update the links to the repository in any documentation they maintain.

subj

Use the latest single executable file for manageability and speed of installation.

Fix warning https://docs.chocolatey.org/en-us/community-repository/moderation/package-validator/rules/cpmr0055

https://github.com/microsoft/winget-pkgs

cc @ronaldtse