On Fri, Apr 25, 2025 at 11:15:03PM +0200, Martin Hostettler wrote:
Bump to avoid auto removal due to unsolved RC bug in key package bouncycastle.
pgpainless is currently blocked by bouncycastle, which has got RC bug #1100227, and is waiting for the maintainer to respond to the patch.
Thank you for bumping this Martin, and thank you to Julien for the
patch. I have uploaded bouncycastle 1.80-3 with Julien's patch for
#1100227.
Hi,
On Sat, Apr 26, 2025 at 06:08:20PM +0000, tony mancill wrote:
On Fri, Apr 25, 2025 at 11:15:03PM +0200, Martin Hostettler wrote:
Bump to avoid auto removal due to unsolved RC bug in key package bouncycastle.
pgpainless is currently blocked by bouncycastle, which has got RC bug #1100227, and is waiting for the maintainer to respond to the patch.
Thank you for bumping this Martin, and thank you to Julien for the
patch. I have uploaded bouncycastle 1.80-3 with Julien's patch for #1100227.
I think bouncycastle should also add
Breaks: libpgpainless-core-java (<< 1.6.9-1~), pgpainless-cli (<< 1.6.9-1~).
(Maybe this list is not complete.)
At the very least so bouncycastle can migrate to testing, as the debci/autopkgtests try to test the new bouncycastle with the old
pgpainless from testing. Obviously this still fails, as only the
combination of new bouncycastle and new pgpainless works.
CC-ing release for awareness.
On Sun, Apr 27, 2025 at 06:27:51PM +0200, Chris Hofstaedtler wrote:
On Sat, Apr 26, 2025 at 06:08:20PM +0000, tony mancill wrote:
On Fri, Apr 25, 2025 at 11:15:03PM +0200, Martin Hostettler wrote:
Bump to avoid auto removal due to unsolved RC bug in key package bouncycastle.
pgpainless is currently blocked by bouncycastle, which has got RC bug #1100227, and is waiting for the maintainer to respond to the patch.
Thank you for bumping this Martin, and thank you to Julien for the
patch. I have uploaded bouncycastle 1.80-3 with Julien's patch for #1100227.
I think bouncycastle should also add
Breaks: libpgpainless-core-java (<< 1.6.9-1~), pgpainless-cli (<< 1.6.9-1~).
(Maybe this list is not complete.)
At the very least so bouncycastle can migrate to testing, as the debci/autopkgtests try to test the new bouncycastle with the old
pgpainless from testing. Obviously this still fails, as only the combination of new bouncycastle and new pgpainless works.
CC-ing release for awareness.
Apologies if I'm missing something here, but I thought the issue was build-time. Wouldn't adding Breaks: imply a runtime issue?
Should we upload pgpainless with a build-dep on (>= 1.80-3)?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 481 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 12:22:09 |
| Calls: | 9,540 |
| Calls today: | 8 |
| Files: | 13,653 |
| Messages: | 6,139,413 |
| Posted today: | 1 |