Bug#1008518: nmu: libxxf86vm_1:1.1.4-1+b2

To: Jordan Justen <jljusten@debian.org>, 1008518@bugs.debian.org
Subject: Bug#1008518: nmu: libxxf86vm_1:1.1.4-1+b2
From: Paul Gevers <elbrus@debian.org>
Date: Mon, 28 Mar 2022 20:57:14 +0200
Message-id: <[🔎] c6344a5c-aeb4-4370-60b9-8005a0657c76@debian.org>
Reply-to: Paul Gevers <elbrus@debian.org>, 1008518@bugs.debian.org
In-reply-to: <[🔎] 164845560144.171003.6193456899753048070.reportbug@localhost>
References: <[🔎] 164845560144.171003.6193456899753048070.reportbug@localhost> <[🔎] 164845560144.171003.6193456899753048070.reportbug@localhost>

Hi Jordan,

On 28-03-2022 10:20, Jordan Justen wrote:

nmu libxxf86vm_1:1.1.4-1+b2 . ANY . unstable . -m "riscv64 arch is at 1:1.1.4-1
while others are at 1:1.1.4-1+b2"

It may be obvious to you, but, so what? Why is that a problem and howdoes rebuilding on all architectures solve that?


Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply to:

Follow-Ups:
- Bug#1008518: nmu: libxxf86vm_1:1.1.4-1+b2
  - From: Jordan Justen <jljusten@debian.org>

References:
- Bug#1008518: nmu: libxxf86vm_1:1.1.4-1+b2
  - From: Jordan Justen <jljusten@debian.org>

Prev by Date: Bug#1006836: transition: python3.10 as default
Next by Date: Désabonnement
Previous by thread: Bug#1008518: nmu: libxxf86vm_1:1.1.4-1+b2
Next by thread: Bug#1008518: nmu: libxxf86vm_1:1.1.4-1+b2
Index(es):
- Date
- Thread