Closed #1290 via #1291.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1290#event-3485664720___
Rpm-maint mailing list
Here's an simple reproducer that doesn't need messing with mock:
> [pmatilai︎lumikko rpm]$ cp tests/data/RPMS/hello-2.0-1.x86_64.rpm /tmp/
[pmatilai︎lumikko rpm]$ ./rpmsign --addsign /tmp/hello-2.0-1.x86_64.rpm <
/dev/null
/tmp/hello-2.0-1.x86_64.rpm:
warning: Could not set GPG_TTY to stdin:
No worries, it's not the first (or last) time mock trips up something because
it's a rather special environment.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Oh my. Thanks for sharing, I'll check that.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1290#issuecomment-648804803___
Seems that something in mock environment trips up the new GPG_TTY related
warning, causing (a bogus) test-suite failure due to the extra output:
https://download.copr.fedorainfracloud.org/results/pmatilai/rpm-snapshot/fedora-rawhide-x86_64/01499743-rpm/build.log.gz
```
--- /dev/null 2020-06-24
