⚠️ ryanofsky opened an issue: "CI failure "buster-backports InRelease: The following signatures couldn't be verified because the public key is not available""
(https://github.com/bitcoin/bitcoin/issues/27531)
### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

Not sure if this CI failure would be fixed by a rebase but the failure happens reliably in the merge_base phase of the "[no wallet, libbitcoinkernel] [focal]" the task in #26485 when the task is rerun:

https://cirrus-ci.com/task/6566074339033088

```
Reading package lists...
W: GPG error: http://deb.debian.org/debian buster-backports InRelease: The following signatures couldn't be v
...

💬 aureleoules commented on pull request "wallet: Refactor and document CoinControl":
(https://github.com/bitcoin/bitcoin/pull/26066#issuecomment-1523198262)
Rebased

💬 fanquake commented on issue "CI failure "buster-backports InRelease: The following signatures couldn't be verified because the public key is not available"":
(https://github.com/bitcoin/bitcoin/issues/27531#issuecomment-1523199075)
Think this might be part of #27492?

⚠️ karask opened an issue: "Cannot disable RBF with walletrbf configuration option"
(https://github.com/bitcoin/bitcoin/issues/27532)
### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

I am creating a tx using:

$ bitcoin-cli createrawtransaction '''
[{"txid":"7b6412a0eed56338731e83c606f13ebb7a3756b3e4e1dbbe43a7db8d09106e56","vout": 1}]
''' '''{"mtVHHCqCECGwiMbMoZe8ayhJHuTdDbYWdJ": 0.00004}'''
0200000001566e10098ddba743bedbe1e4b356377abb3ef106c6831e733863d5eea012647b0100000000`fdffffff`01a00f0000000000001976a9148e48a6c5108efa
...

💬 furszy commented on issue "Cannot disable RBF with walletrbf configuration option":
(https://github.com/bitcoin/bitcoin/issues/27532#issuecomment-1523257213)
`createrawtransaction` does not interact with the wallet. Use the `replaceable` arg to enable/disable RBF.
```
createrawtransaction <inputs> <outputs> <locktime> <replaceable>
```

💬 MarcoFalke commented on issue "CI failure "buster-backports InRelease: The following signatures couldn't be verified because the public key is not available"":
(https://github.com/bitcoin/bitcoin/issues/27531#issuecomment-1523283058)
Yeah, sorry this is a duplicate. My recommendation for now would be to rebase, if there has been no or only stale review, and ignore the failure for now? My long term hope is that Cirrus fixes the issue. An alternative might be to revert this part of the CI change.

✅ MarcoFalke closed an issue: "CI failure "buster-backports InRelease: The following signatures couldn't be verified because the public key is not available""
(https://github.com/bitcoin/bitcoin/issues/27531)

💬 MarcoFalke commented on pull request "test: clean up logs when there aren't perf subprocesses":
(https://github.com/bitcoin/bitcoin/pull/23928#issuecomment-1523287514)
I still think if the user passes `--perf` and perf is not available, the program should fail and tell the user that perf isn't found. Not sure what the point is to silently ignore what the user asked for and add code for a special case that shouldn't exist.

💬 mzumsande commented on pull request "p2p, rpc: Manual block-relay-only connections with addnode":
(https://github.com/bitcoin/bitcoin/pull/24170#issuecomment-1523288640)
b36db71 to c13c986: rebased (will address the oustanding review comments soon!)

💬 karask commented on issue "Cannot disable RBF with walletrbf configuration option":
(https://github.com/bitcoin/bitcoin/issues/27532#issuecomment-1523304198)
Ah, missed that. Thanks!

✅ karask closed an issue: "Cannot disable RBF with walletrbf configuration option"
(https://github.com/bitcoin/bitcoin/issues/27532)

💬 ryanofsky commented on issue "CI failure "buster-backports InRelease: The following signatures couldn't be verified because the public key is not available"":
(https://github.com/bitcoin/bitcoin/issues/27531#issuecomment-1523323865)
Thanks. The thing I don't understand is why rebasing fixes the problem when rerunning the task doesn't fix the problem.

This failure doesn't seem to have anything to do with the contents of the PR, so I wouldn't expect pushing a rebased version of the PR to change anything. How is rebasing actually different than rerunning? Does a github push clear some cirrus cache that would otherwise not be cleared? I think I've been confused about this behavior in other contexts so would appreciate any po
...

👋 glozow's pull request is ready for review: "mempool: keep CPFP'd transactions when loading from mempool.dat"
(https://github.com/bitcoin/bitcoin/pull/27476)

✅ achow101 closed an issue: "gettransaction does not contain the field "abandoned" for abandoned receiving tx"
(https://github.com/bitcoin/bitcoin/issues/25130)

🚀 achow101 merged a pull request: "rpc, wallet: add abandoned field for all categories of transaction in ListTransaction"
(https://github.com/bitcoin/bitcoin/pull/25158)

💬 achow101 commented on pull request "rpc: Return block hash & height in getbalances, gettransaction and getwalletinfo":
(https://github.com/bitcoin/bitcoin/pull/26094#issuecomment-1523381226)
There's a test failure in `wallet_orphanedreward.py`.

```
256/263 - wallet_orphanedreward.py failed, Duration: 17 s

stdout:
2023-04-26T12:57:28.311000Z TestFramework (INFO): PRNG seed is: 5570008732445289618
2023-04-26T12:57:28.313000Z TestFramework (INFO): Initializing test directory /tmp/test_runner_₿_🏃_20230426_085557/wallet_orphanedreward_19
2023-04-26T12:57:40.283000Z TestFramework (ERROR): Assertion failed
Traceback (most recent call last):
File "/home/andy/bitcoin/bitcoin/m
...

💬 pinheadmz commented on pull request "system: use %LOCALAPPDATA% as default datadir on windows":
(https://github.com/bitcoin/bitcoin/pull/27064#issuecomment-1523392935)
Push to 60cd07b781bfe46262a5d66c97e257e0dd378f5c:
- rebase on master
- add PR release note
- change how we detect "old" directory use from looking for `blocks/` to looking for `chainstate/`

💬 MarcoFalke commented on issue "CI failure "buster-backports InRelease: The following signatures couldn't be verified because the public key is not available"":
(https://github.com/bitcoin/bitcoin/issues/27531#issuecomment-1523395787)
Yeah, in Cirrus there is a setting to merge the cirrus.yaml of the pull request with the one in the target branch. It is enabled, however it doesn't merge the git contents. Thus, there is a workaround step to achieve that: https://github.com/bitcoin/bitcoin/blob/91ccb62faab21b2b52b089cc04f3a5c1bf6989cc/.cirrus.yml#L27

However, the workaround does not work for Cirrus Docker Env files. Ideally this is fixed by Cirrus CI. I don't see another workaround than either rebasing or removing the Env fe
...

💬 willcl-ark commented on issue "Relative paths named in the -conf parameter reset when parsing datadir in named config":
(https://github.com/bitcoin/bitcoin/issues/19990#issuecomment-1523439189)
Will this issue be closed by https://github.com/bitcoin/bitcoin/pull/27302 ?

💬 MarcoFalke commented on pull request "Remove now-unnecessary poll, fcntl includes from net(base).cpp":
(https://github.com/bitcoin/bitcoin/pull/27530#issuecomment-1523481640)
Can you add this to iwyu CI to double check and aid reviewers?