Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Cryptology ePrint entries #18

Open
wichtfx opened this issue Mar 26, 2023 · 0 comments · May be fixed by #19
Open

Issue with Cryptology ePrint entries #18

wichtfx opened this issue Mar 26, 2023 · 0 comments · May be fixed by #19

Comments

@wichtfx
Copy link

wichtfx commented Mar 26, 2023

First of all, let me thank you for this amazing tool.

It seems, however, that working with entries from the Cryptology ePrint archive raises issues. Here is the transcript of running dblpbibtex with the key cryptoeprint:2022/1767:

DBLPBibTeX - version 2.4 - Copyright Marc Stevens 2010-2019
Projectpage: https://github.com/cr-marcstevens/dblpbibtex/
Loading configuration from: dblpbibtex.cfg
Parsing auxfile: 'main.aux'.
Configuration:
	bibtex: 'bibtex'
	mainbibfile: 'dblpbibtex.bib'
	DBLP format: compact
Bib files: 'references.bib' 'dblpbibtex.bib'
Bib search directories: '.'
Loaded content of main bibfile: 'dblpbibtex.bib'!
New citation: 'cryptoeprint:2022/1767'
Running bibtex: 'bibtex "main"'.
Caught exception: basic_string::_M_create
This is BibTeX, Version 0.99d (TeX Live 2020/Debian)
The top-level auxiliary file: main.aux
The style file: ieeesort.bst
Database file #1: references.bib
Database file #2: dblpbibtex.bib
Warning--I didn't find a database entry for "cryptoeprint:2022/1767"
(There was 1 warning)

The same issue arises on Arch Linux running kernel 6.2.6 and on Debian Bullseye inside a Docker container (see. #17 ).

@anatosun anatosun linked a pull request Mar 29, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant