equivs-build doesn't work if & is part of PWD

[Martin Mrazik]

Steps to reproduce:

1. mkdir -p '/tmp/a/a&&b&&c'
2. put some code and debian packaging into this dir
3. run mk-build-deps/equivs-build

Result:
mmrazik@fry:/tmp/a/a&&b&&c/autopilot$ equivs-build debian/control
sh: 1: b: not found
Error on copy of the template files: exit status 127

Expected result:
it works.

Patch attached.

[Martin Mrazik (mrazik)]

Unfortunately this is a real world situation when we are using jenkins and mk-build-deps in the test job. We are using label expressions to select the correct test configuration (e.g. "amd64&&precise" to tell jenkins I want to test on amd64 and precise) . For some resons the label expression used for selecting the jenkins node is used in the path of the working directory. Hence this bug.

[era (era)]

Thank you for your bug report. I have forwarded it upstream and added a tracker for the corresponding Debian bug.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Scott Kostyshak (scott-kostyshak)]

There's a more common use case in #881153 and it was reported earlier. Note that the patches are the same.

[Launchpad Janitor (janitor)]

This bug was fixed in the package equivs - 2.0.10

---------------
equivs (2.0.10) unstable; urgency=medium

  * QA upload.
  * Upload to unstable.

 -- Adrian Bunk <email address hidden> Sun, 18 Jun 2017 16:56:59 +0300