Env expansion not working for global replaces, conflicts

[mayocream]

What happened?

Env expansion introduced in #548 only works for deb.Overrides, but not working for global replaces, conflicts.

How can we reproduce this?

Example config file:

name: "mayo"
arch: ${ARCH}
platform: "linux"
version: 1.0.0
section: "default"
priority: "extra"
maintainer: "Mayo"
vendor: "Mayo Inc."
license: "ASL 2.0"
replaces:
  - foobar
  - ${REPLACE_BLA}
conflicts:
  - mercurial
  - ${CONFLICTS_BLA}
contents:
- src: /tmp/mayo
  dst: /usr/local/bin

Result:

$ REPLACE_BLA=mayo nfpm pkg -f tests/nfpm.yaml -p deb
new Debian package, version 2.0.
size 740 bytes: control archive=386 bytes.
     1 bytes,     0 lines      conffiles            
   223 bytes,    10 lines      control              
    50 bytes,     1 lines      md5sums              
Package: mayo
Version: 1.0.0
Section: default
Priority: extra
Architecture: amd64
Maintainer: Mayo
Installed-Size: 0
Replaces: foobar, ${REPLACE_BLA}
Conflicts: mercurial, ${CONFLICTS_BLA}
Description: no description given

nfpm version

nfpm version nfpm version 2.22.2
commit: 66760061ee255a163cbc77c7193826c15837fc0a
built at: 2022-11-30T12:46:25Z
built by: goreleaser
module version: v2.22.2, checksum: h1:K/how1xpNJC4xHpgMKQwE46iJp8+h0iTxWhhMYizhAA=

Search

• I did search for other open and closed issues before opening this.

Code of Conduct

• I agree to follow this project's Code of Conduct

Additional context

nfpm/www/docs/configuration.md

Lines 107 to 112 in c80d81b

	# Packages it replaces. (overridable)
	# This will expand any env var you set in the field, e.g. ${REPLACE_BLA}
	# the env var approach can be used to account for differences in platforms
	replaces:
	- foobar
	- ${REPLACE_BLA}

[djgilcrease]

Will get to this tomorrow

[mayocream]

Will get to this tomorrow

Just wonder is it feasible to make env expansion also work on name config field? Thanks!