Package Details: zotero 6.0.20-1

Git Clone URL: (read-only, click to copy)
Package Base: zotero
Description: A free, easy-to-use tool to help you collect, organize, cite, and share your research sources.
Upstream URL:
Licenses: AGPL3
Submitter: agkphysics
Maintainer: agkphysics
Last Packager: agkphysics
Votes: 8
Popularity: 0.73
First Submitted: 2022-08-13 10:04 (UTC)
Last Updated: 2023-01-29 01:38 (UTC)

Latest Comments

1 2 Next › Last »

rcrath commented on 2022-11-30 04:04 (UTC) (edited on 2022-11-30 04:05 (UTC) by rcrath)

I got the node: --openssl-legacy-provider is not allowed in NODE_OPTIONS error too. replacing the line

NODE_OPTIONS=--openssl-legacy-provider npm run build


NODE_OPTIONS= npm run build

made it work for me with none of the other changes recommended below. we'll see if that breaks something in the program when I'm using it, but it looks good so far.

avemilia commented on 2022-11-13 09:29 (UTC) (edited on 2022-11-13 09:35 (UTC) by avemilia)

That gives

node: --openssl-legacy-provider is not allowed in NODE_OPTIONS

UPD: removing NODE_OPTIONS fixed the build.

the_z0id commented on 2022-11-11 21:33 (UTC) (edited on 2022-11-11 21:40 (UTC) by the_z0id)

Following peippos workaround I still get an error message aborting the install:

curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)
==> ERROR: A failure occurred in prepare().
error: failed to build 'zotero-6.0.18-1': 
error: packages failed to build: zotero-6.0.18-1

Any ideas for a fix?

peippo commented on 2022-11-09 14:22 (UTC)

To work around the build failures reported by @petronny and @MangoMan, add a line

export NODE_OPTIONS=--openssl-legacy-provider

to the beginning of build().

(The pdf.js seems to pin versions of node modules that do not support openssl>=3)

petronny commented on 2022-11-06 11:52 (UTC) (edited on 2022-11-06 11:53 (UTC) by petronny)

[02:38:05] Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:140:10)
    at BulkUpdateDecorator.hashFactory (/build/zotero/src/zotero-client/pdf-reader/pdf.js/node_modules/webpack/lib/util/createHash.js:144:18)
    at BulkUpdateDecorator.update (/build/zotero/src/zotero-client/pdf-reader/pdf.js/node_modules/webpack/lib/util/createHash.js:46:50)
    at RawSource.updateHash (/build/zotero/src/zotero-client/pdf-reader/pdf.js/node_modules/webpack-sources/lib/RawSource.js:64:8)
    at NormalModule._initBuildHash (/build/zotero/src/zotero-client/pdf-reader/pdf.js/node_modules/webpack/lib/NormalModule.js:753:17)
    at handleParseResult (/build/zotero/src/zotero-client/pdf-reader/pdf.js/node_modules/webpack/lib/NormalModule.js:817:10)
    at /build/zotero/src/zotero-client/pdf-reader/pdf.js/node_modules/webpack/lib/NormalModule.js:908:4
    at processResult (/build/zotero/src/zotero-client/pdf-reader/pdf.js/node_modules/webpack/lib/NormalModule.js:640:11)
    at /build/zotero/src/zotero-client/pdf-reader/pdf.js/node_modules/webpack/lib/NormalModule.js:692:5
[02:38:05] 'generic-legacy' errored after 2.72 s

Full build log:

MangoMan commented on 2022-11-06 08:51 (UTC) (edited on 2022-11-06 08:57 (UTC) by MangoMan)

Unable to update and build with yay. something is wrong with pdf-reader

full error message

Node.js v19.0.1
ERROR: "build:pdf.js" exited with 1.

    at ChildProcess.exithandler (node:child_process:412:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1098:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5) {
  code: 1,
  killed: false,
  signal: null,
  cmd: 'npm run build',
  stdout: '\n' +
    '> pdf-reader@1.0.0 build\n' +
    '> run-s build:pdf.js build:reader\n' +
    '\n' +
    '\n' +
    '> pdf-reader@1.0.0 build:pdf.js\n' +
    '> sh scripts/build-pdfjs\n' +
    '\n' +
    '\n' +
    'added 1527 packages, and audited 1962 packages in 20s\n' +
    '\n' +
    '102 packages are looking for funding\n' +
    '  run `npm fund` for details\n' +

Rikayon commented on 2022-10-30 19:12 (UTC)

I just want to express my gratitude, by folowing @Pippip19 's comment to @Feakster regarding the file policy, I was finally able to upgrade zotero to zotero 6.0.15-1, previously it was failing. Thanks

nomaly commented on 2022-10-23 21:18 (UTC)

@agkphysics awesome. it's there and I was able to install the package file. thanking you kindly for the help

agkphysics commented on 2022-10-23 11:06 (UTC)

@nomaly That means it built. It can't find it because I think it's looking for official packages not custom packages. Check wherever your built packages are for the created package file zotero-6.0.15-1-x86_64.pkg.tar.zst.

nomaly commented on 2022-10-23 10:36 (UTC)

@agkphysics Apologies, I didn't with the previous message! Tried just now with extra-x86_64-build and it's still failed. Not sure if I've messed up somewhere this is the first time I've ever done something like this. My exact steps:

  1. git clone
  2. installed yay -S devtools-git
  3. tried with extra-x86_64-build -c it errored the first time failing to find lzo so had to yay -S lzo (which wasn't up to date, but updated successfully) and tried again.
  4. ran extra-x86_64-build -c again and everything seemed to complete until the very end where it gave the following:
Success: [browserify] 4 files processed [3090ms]
Success: [copy] 67 files processed | 67 checked [3191ms]
Success: [js] 317 files processed | 329 checked [3414ms]
Success: [sass] 3 files processed | 55 checked [913ms]
Success: [sass] 0 files processed [124ms]
Success: [symlink] 1412 files processed | 1412 checked [3427ms]
Success: [symlink] 4 files processed | 4 checked [297ms]
Success: [cleanup] 0 files processed [0ms]
Success: [pdf-reader] 1 files processed | 1 checked [5402ms]
Success: [pdf-worker] 1 files processed | 1 checked [126922ms]
Success: [note-editor] 1 files processed | 1 checked [32682ms]
Total build time 126951ms


Checking zotero-6.0.15-1-x86_64.pkg.tar.zst


==> Running checkpkg
error: target not found: zotero
==> WARNING: Skipped checkpkg due to missing repo packages

Have I missed some essential step?

Terminal's stdout is muuuch longer but I'm not sure if it is appropriate to post it all here.