Bug#1016687: Clarification Needed

To: Timo Aaltonen <tjaalton@debian.org>
Cc: Dan Letzeisen <dtl131@gmail.com>, 1016687@bugs.debian.org
Subject: Bug#1016687: Clarification Needed
From: A Ozbay <ago_debianbug@protonmail.com>
Date: Wed, 17 Aug 2022 22:23:56 +0000
Message-id: <[🔎] iwF1zl9VpODcDDYfb15AbQhbJCY9xCzH8MdfdpeIdMoXAI2SD4U3P3z1XS0rmP2X-oFOqgTd1ouTvxhBis0DT8unYqOyajkNqsvGKbTr4Bs=@protonmail.com>
Reply-to: A Ozbay <ago_debianbug@protonmail.com>, 1016687@bugs.debian.org
In-reply-to: <[🔎] 0b95c0e6-e5c9-83b6-16a7-a7dd969113cd@debian.org>
References: <[🔎] 165969260076.17864.15277364320337951040.reportbug@snorlax.broadband> <[🔎] b74f7a34-b2b1-4ae1-26f8-73ad2e9f0c8e@gmail.com> <[🔎] 0b95c0e6-e5c9-83b6-16a7-a7dd969113cd@debian.org> <[🔎] 165969260076.17864.15277364320337951040.reportbug@snorlax.broadband>

> I don't think this can be enabled, since Debian does not allow
> distributing software encumbered by patents:
> 
> https://www.debian.org/legal/patent

But Debian already has been enabling these codecs for many years. You have been able to use the H.264 and H.265 VAAPI codecs on Debian stable for a very long time. The only change was that now you need to explicitly opt in to enable building these codecs, while they were automatically built before. Changing a build flag to enable a feature that was _already_ there in a previous version should not compromise Debian's stance.

Reply to:

References:
- Bug#1016687: mesa-va-drivers: 22.2.0~rc1-1 breaks VAAPI hardware encoding
  - From: A Ozbay <ago_debianbug@protonmail.com>
- Bug#1016687: Clarification Needed
  - From: Dan Letzeisen <dtl131@gmail.com>
- Bug#1016687: Clarification Needed
  - From: Timo Aaltonen <tjaalton@debian.org>

Prev by Date: Bug#1016687: Clarification Needed
Next by Date: Bug#1017499: Related upstream issue
Previous by thread: Bug#1016687: Clarification Needed
Next by thread: Bug#1016687: marked as done (mesa-va-drivers: 22.2.0~rc1-1 breaks VAAPI hardware encoding)
Index(es):
- Date
- Thread