ci: previous_release.py fails for C++17 Travis job on forked repo #19812

1. 
   hebasto commented at 8:58 am on August 26, 2020: member

   https://travis-ci.org/github/hebasto/bitcoin/jobs/721269536
2. hebasto added the label Bug on Aug 26, 2020
3. 
   MarcoFalke commented at 9:07 am on August 26, 2020: member

   This is a know issue/oversight. See #19013 (comment)
4. MarcoFalke added the label Tests on Aug 26, 2020
5. 
   hebasto commented at 9:11 am on August 26, 2020: member

   In #19013 I found a workaround, but not the root of the issue :)
6. 
   MarcoFalke commented at 9:13 am on August 26, 2020: member

   The issue is that gpg isn’t installed. Even if it was installed, it would reject the signatures as untrusted because the keys haven’t been marked trusted nor has gpg been told to use a different trust model.
7. 
   hebasto commented at 9:14 am on August 26, 2020: member

   The issue is that gpg isn’t installed. Even if it was installed, it would reject the signatures as untrusted because the keys haven’t been marked trusted nor has gpg been told to use a different trust model.

   So why it works for the GUI repo which is also forked?

8. 
   MarcoFalke commented at 9:20 am on August 26, 2020: member

   The script isn’t run when the release folder already exists in the cache
9. 
   hebasto commented at 9:23 am on August 26, 2020: member

   The script isn’t run when the release folder already exists in the cache

   So if Travis cache were cleaned the builds would be broken even in this repo?

10. MarcoFalke added this to the milestone 0.21.0 on Aug 26, 2020
11. MarcoFalke referenced this in commit c1e0c2ad3b on Aug 31, 2020
12. MarcoFalke closed this on Aug 31, 2020

    ---

13. sidhujag referenced this in commit dd6081216a on Aug 31, 2020
14. DrahtBot locked this on Feb 15, 2022

Contributors
hebasto MarcoFalke

Labels
Bug Tests

Milestone
0.21.0