View Issue Details

IDProjectCategoryView StatusLast Update
0007140Talermerchant backoffice SPApublic2022-03-01 17:37
Reporterms-mantis Assigned Tosebasjm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Summary0007140: 'make i18n' fails
Description$ make i18n
./build-translations.sh
./build-translations.sh: line 2: cd: packages/frontend: No such file or directory
./build-translations.sh: line 10: src/i18n/taler-merchant-backoffice.pot: No such file or directory
find: ‘src’: No such file or directory
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module '/home/job/merchant-backoffice/node_modules/@gnu-taler/pogen/bin/pogen.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
merging src/i18n/*.po
msgmerge: error while opening "src/i18n/*.po" for reading: No such file or directory
./build-translations.sh: line 20: src/i18n/strings.ts: No such file or directory
appending src/i18n/*.po
./build-translations.sh: line 23: src/i18n/strings.ts: No such file or directory
make: *** [Makefile:92: i18n] Error 1
Additional InformationThe DESIGN.md document advertises the use of the Makefile's "make i18n" command to extract and build new translations.
TagsNo tags attached.

Activities

ms-mantis

2022-01-03 09:27

reporter   ~0018621

fixed here: d786453c6b4e6ce67f41ff3b25d4e51059333491

ms-mantis

2022-01-03 10:30

reporter   ~0018622

Actually, there are still a bunch of those being printed by the command:

(node:8997) [DEP0128] DeprecationWarning: Invalid 'main' field in '/home/job/merchant-backoffice/packages/bank/node_modules/po2json/package.json' of './lib/po2json'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)

sebasjm

2022-03-01 17:37

developer   ~0018758

fixed 36d3f508..454c3b51

Issue History

Date Modified Username Field Change
2022-01-03 08:27 ms-mantis New Issue
2022-01-03 08:27 ms-mantis Status new => assigned
2022-01-03 08:27 ms-mantis Assigned To => sebasjm
2022-01-03 09:27 ms-mantis Note Added: 0018621
2022-01-03 10:30 ms-mantis Note Added: 0018622
2022-03-01 17:37 sebasjm Status assigned => resolved
2022-03-01 17:37 sebasjm Resolution open => fixed
2022-03-01 17:37 sebasjm Note Added: 0018758