Bug#1069943: bullseye-pu: package emacs/27.1+1-3.1+deb11u3
Control: tag -1 confirmed Control: retitle -1 bullseye-pu: package emacs/27.1+1-3.1+deb11u4 On Sun, May 19, 2024 at 11:30:26AM +0100, Sean Whitton wrote: > How should we proceed? Please go ahead. Since the test package Adam built installs correctly, which was the original symptom, I'm satisfied that users will be able to install it as well or we will get better reports to inform a regression update. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1069943: bullseye-pu: package emacs/27.1+1-3.1+deb11u3
control: tag -1 - moreinfo Hello Jonathan, On Sun 12 May 2024 at 09:00pm +01, Jonathan Wiltshire wrote: > The security release hasn't been accepted into bullseye yet because > there were reports of it being broken on mips64el. There was a bug but > I'm afraid I don't have a reference to it. I believe this was #1031888. > Do you know if your version solves the issue? Upstream addressed the memory leak that Adrian thought might be causing #1031888. I prepared a deb11u4 in git which includes that fix. Unfortunately, however, #1031888 is no longer reproducible. Adam took a look at my deb11u4 (thank you), but the buildds which were previously showing the problem are no longer running bullseye. I just tried preparing a mips64el qemu image and booting that, but the problem is not reproducible there: deb11u2 installs fine. How should we proceed? -- Sean Whitton signature.asc Description: PGP signature
Bug#1069943: bullseye-pu: package emacs/27.1+1-3.1+deb11u3
Control: tag -1 moreinfo Hi, On Sat, Apr 27, 2024 at 12:34:45PM +0100, Sean Whitton wrote: > This update also has the effect of rolling in changes already in > oldstable-security earlier than the usual point release copy, as > oldstable-security has deb11u2, while oldstable still has deb11u1. The security release hasn't been accepted into bullseye yet because there were reports of it being broken on mips64el. There was a bug but I'm afraid I don't have a reference to it. Do you know if your version solves the issue? If it does I can accept the security first for you to rebase against if that helps with the diffs. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
