Bug#1016687: Clarification Needed

To: 1016687@bugs.debian.org
Subject: Bug#1016687: Clarification Needed
From: Dan Letzeisen <dtl131@gmail.com>
Date: Sun, 14 Aug 2022 17:10:43 -0400
Message-id: <[🔎] b74f7a34-b2b1-4ae1-26f8-73ad2e9f0c8e@gmail.com>
Reply-to: Dan Letzeisen <dtl131@gmail.com>, 1016687@bugs.debian.org
References: <[🔎] 165969260076.17864.15277364320337951040.reportbug@snorlax.broadband>

I realize this is a tricky situation with dfsg, but is there any intentto fix this bug at Debian distro level or should we look at building ourown mesa?

Also, the bug should be retitled. It doesn't just affect VA-APIencoding. It affects VA-API/VDPAU/Vulkan decoding and encoding of thecodecs in question.


Thank you

Reply to:

Follow-Ups:
- Bug#1016687: Clarification Needed
  - From: Timo Aaltonen <tjaalton@debian.org>

References:
- Bug#1016687: mesa-va-drivers: 22.2.0~rc1-1 breaks VAAPI hardware encoding
  - From: A Ozbay <ago_debianbug@protonmail.com>

Prev by Date: [Git][xorg-team/lib/mesa][upstream-experimental] 55 commits: .pick_status.json: Update to 8e6bdb2ed31f27c28d258859ec48e8e67f51ff41
Next by Date: Processing of libdrm_2.4.112-3ubuntu1_source.changes
Previous by thread: Bug#1016687: 22.2.0~rc1-1 breaks VAAPI hardware encoding
Next by thread: Bug#1016687: Clarification Needed
Index(es):
- Date
- Thread