`acro` broken with latest release of `l3kernel`

[dbitouze]

After last l3kernel update, the following MCE:

\documentclass{article}
\usepackage{acro}
\begin{document}
Foo.
\end{document}

fails to compile:

! Undefined control sequence.

\l__acro_tmpa_prop

Other packages are affected as well and the reason is explained here. Hence, adding:

\prop_new:N \l__acro_tmpa_prop

in acro.sty is enough to fix this issue.

[bdtc]

Similar for chemmacros, chemformula, chemnum.

[josephwright]

@bdtc I could see the issue in chemnum and have logged a PR (https://github.com/cgnieder/chemnum/pull/23), and with chemformula can see an unrelated issue with loading l3keys2e (https://github.com/cgnieder/chemformula/pull/21). But I don't see the prop issue with either chemformula or chemmacros: do you have examples available? I'll sort PRs if I know what needs fixing.

[josephwright]

I've put in a PR for this issue and mailed @cgnieder to check on status.

[bdtc]

For chemmacros reactant:

\documentclass{article}
\usepackage{chemmacros}
\begin{document}
\DeclareChemReactant{dichloropentane}{name={\iupac{2,4-di|chloro|pentane}}}
\reactant{dichloropentane}
\end{document}

For chemformula:

\documentclass{article}
\usepackage{chemformula}
\begin{document}
test
\end{document}

gives:

! Undefined control sequence.
l.481 \ProcessKeysPackageOptions

which is almost certainly what you also found.

Sorry I was not more specific, it was late and I was processing tests in bulk.

[josephwright]

For chemmacros reactant:

\documentclass{article}
\usepackage{chemmacros}
\begin{document}
\DeclareChemReactant{dichloropentane}{name={\iupac{2,4-di|chloro|pentane}}}
\reactant{dichloropentane}
\end{document}

The's the issue in chemnum.

For chemformula:

\documentclass{article}
\usepackage{chemformula}
\begin{document}
test
\end{document}

gives:

! Undefined control sequence.
l.481 \ProcessKeysPackageOptions

which is almost certainly what you also found.

Yes, it's an unrelated issue I've also reported.

Sorry I was not more specific, it was late and I was processing tests in bulk.

No problem!