Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64

To: Jing Luo <jing@jing.rocks>, 1103250@bugs.debian.org
Subject: Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64
From: Peter Green <plugwash@debian.org>
Date: Tue, 15 Apr 2025 21:50:12 +0100
Message-id: <[🔎] 8500e77b-9f15-443b-8325-a4edc6a2c9aa@debian.org>
Reply-to: Peter Green <plugwash@debian.org>, 1103250@bugs.debian.org
In-reply-to: <[🔎] 174472964262.1536461.2688023939880684256.reportbug@cfarm421.jing.rocks>
References: <[🔎] 174472964262.1536461.2688023939880684256.reportbug@cfarm421.jing.rocks> <[🔎] 174472964262.1536461.2688023939880684256.reportbug@cfarm421.jing.rocks>

On 15/04/2025 16:07, Jing Luo wrote:

X-Debbugs-Cc: debian-amd64@lists.debian.org, debian-arm@lists.debian.org, debian-powerpc@lists.debian.org, debian-riscv@lists.debian.org


I understand CC'ing the porters when you have an issue that is specific to the port, but
if it's failing on every damn architecture, that isn't really a porter problem.

Reply to:

Follow-Ups:
- Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64
  - From: Jing Luo <jing@jing.rocks>

References:
- Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64
  - From: Jing Luo <jing@jing.rocks>

Prev by Date: Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64
Next by Date: Bug#1103284: Patch: Fix assertion error in pycares
Previous by thread: Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64
Next by thread: Bug#1103250: yasm: FTBFS on amd64, arm64, armel, armhf, i386, ppc64el, ppc64, powerpc, riscv64
Index(es):
- Date
- Thread