Actually, instead of passing the prefix to the test suite, we could just use
`%_rpmmacrodir`, but nah, I've already decided to go with a backport instead
:smile:
--
Reply to this email directly or view it on GitHub:
Closed #2401.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2401#event-8617644470
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing list
OK, so this is because the non-tilde macro paths depend on the install prefix,
and we don't currently pass it to the test suite. While it would be quite easy
to add, at that point, I'm thinking it would be more appropriate to only
include this patch on the respective stable branches, after all.
@dmnks pushed 1 commit.
07388f7709866a997c12a1d642f9c14e2754d66b Fix a test relying on glibc version
of glob(3)
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2401/files/2c154b31bc5d7582115fe908a527d6f2ff970c97..07388f7709866a997c12a1d642f9c14e2754d66b
You are
Ugh, this breaks the actual test, what? :confused: Investigating...
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2401#issuecomment-1446550510
You are receiving this because you are subscribed to this thread.
Message ID:
When fakechroot is called with FAKECHROOT_BASE and HOME both pointed at the
same directory (as is the case with our test suite, see the file
tests/atlocal.in), the pattern ~ gets expanded by glob() to the
empty string. However, this wasnt the case back when we bundled our own
glob()
