Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

Package: libasound2 Version: 1.2.3.2-1+b1 Followup-For: Bug #870396 X-Debbugs-Cc: t...@mirbsd.de This is still pertinent. -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100,

Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

Package: libasound2 Version: 1.1.8-2 Followup-For: Bug #870396 Still exists… updated debdiff anbei. Verified 1.1.8-2+x32.1 to work. -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100,

Bug#870396: [Pkg-alsa-devel] Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

(For alsa-de...@alsa-project.org I’ve attached the diffs this eMail thread has been about, with hope you will apply them in the next upstream release.) Elimar Riesebieter dixit: >it seems that you are an exclusive user of the x32 port ;-) Please If you actually read that thread you’d know I’m

Bug#870396: [Pkg-alsa-devel] Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

Hi Thorsten, * Thorsten Glaser [2017-08-01 18:18 +0200]: > Source: alsa-lib > Version: 1.1.3-5 > Severity: important > Tags: patch > > I was a bit annoyed I could not play any sound on my x32 desktop > any more and today investigated it. It boils down to that amd64 > assembly code was run,

Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

* Thorsten Glaser [2018-12-12 11:28 +0100]: > On Wed, 12 Dec 2018, Elimar Riesebieter wrote: > > > Why don't you try to push your patches upstream? I won't because you > > Because I don’t even *know* upstream, let alone have a > working relationship with them. alsa-de...@alsa-project.org >

Bug#870396: [Pkg-alsa-devel] Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

On Wed, 12 Dec 2018, Elimar Riesebieter wrote: > Why don't you try to push your patches upstream? I won't because you Because I don’t even *know* upstream, let alone have a working relationship with them. > are the author and you know what you did. ☹ bye, //mirabilos -- tarent solutions GmbH

Bug#870396: [Pkg-alsa-devel] Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

* Thorsten Glaser [2018-12-10 18:18 +0100]: > found 870396 1.1.7-1 > thanks > > Here is an updated debdiff, as usual. It still fixes the segfaults. Why don't you try to push your patches upstream? I won't because you are the author and you know what you did. Elimar -- On the keyboard of

Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

found 870396 1.1.7-1 thanks Here is an updated debdiff, as usual. It still fixes the segfaults. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941

Bug#870396: [Pkg-alsa-devel] Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

Hi, >As I can't evaluate the impact to our officially supported arch's I The impact of 0011-distinguish-x32-from-amd64.patch on any other architecture is absolutely zero, and that’s what fixes x32, so… >and wait till they be pushed. … I’d prefer it very much if you can merge at least that

Bug#870396: [Pkg-alsa-devel] Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

Hi Thorsten, * Thorsten Glaser [2017-08-01 18:18 +0200]: > Source: alsa-lib > Version: 1.1.3-5 > Severity: important > Tags: patch > > I was a bit annoyed I could not play any sound on my x32 desktop > any more and today investigated it. It boils down to that amd64 > assembly

Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

Source: alsa-lib Version: 1.1.3-5 Severity: important Tags: patch I was a bit annoyed I could not play any sound on my x32 desktop any more and today investigated it. It boils down to that amd64 assembly code was run, which, of course, cannot work. While the fix for that