Hi,
I also ran into this bug. I updated my Debian Sid machine last Monday
(7th of dec 2020). I think it updated my zsh-antigen package at that
time. After that, everything still ran OK.
Today, while wondering if I needed to update OMZ plugins, I discovered
the "omz update" command. I ran it, and after that I had the same error
as in this bug. I deleted my antigen cache folder, thinking it maybe
needs to reinstall everything cleanly, but this didn't fix it. I guess
my omz update forced antigen to go through it's setup again and surfaced
the issue.
So I also tried the command in the above mail, downloading the source
package and building it:
$ apt source zsh-antigen
$ cd zsh-antigen-2.2.3/
$ debuild -us -uc
Building and installing the package didn't solve the problem, it was
still missing the function. Now, I have no idea about building packages,
but I can read makefiles a bit,so I had a look at it.
It looks like the make command from antigen builds the antigen script by
copying files from it's source directory into bin/antigen.zsh.
When it does that, it uses a GLOB variable, that accumulatees the files
to copy. This in turn is filled by the COMMANDS, HELPERS and LIB
variables (Makefile.in lines 48-50). Those in turn depend on the PWD
variable. I think (but am not sure), that this variable is passed by the
environment to the make command.
To check my suspicion, replacing the ${PWD} code that expands to the PWD
variable by ${shell pwd} that runs the pwd command inside a shell and
returns it's value made a workable package. But this is probably a
workaround rather than a fix.
I suspect that the debian packaging environment erases the PWD variable
(I guess for reproducible build, this one can be tricky). There is
probably a canonical way to handle this, but I don't know enough about
packaging in debian for this.
Hope this helps,
Urs
