Control: tags -1 + patch
On Wed, 23 Apr 2025 at 15:59:00 +0100, Simon McVittie wrote:
I think the "option 2" that I proposed is entirely feasible for trixie,
actually. I'm testing an implementation now.
https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/55 works
successfully on my I
On Tue, 15 Apr 2025 at 16:52:56 +0200, Helmut Grohne wrote:
On Tue, Apr 15, 2025 at 01:47:54PM +0100, Simon McVittie wrote:
I think a regression for amd64/i386 co-installation would have a
considerably larger practical negative impact on Debian users
This reasoning convinces me. As it stands,
On 2025-04-15 11:34, Helmut Grohne wrote:
>
> I can also tell you that running a kfreebsd-amd64 ELF executable on a
> Linux amd64 kernel works "too well". The Linux kernel cannot tell these
> architectures apart from the ELF header and happily runs it. As the
> syscall ABI is completely different,
On Tue, Apr 15, 2025 at 10:41:22AM +0200, Michel Dänzer wrote:
> Given that different variants of libvulkan_*.so are located in separate
> search paths, is there any scenario other than a system misconfiguration
> which would result in an attempt to load the wrong one?
I fear the answer to this
Hi Simon,
On Tue, Apr 15, 2025 at 01:47:54PM +0100, Simon McVittie wrote:
> I think a regression for amd64/i386 co-installation would have a
> considerably larger practical negative impact on Debian users than
> ABI conflicts between less-commonly-used architecture pairs like
> armel/armhf, and a
On Mon, 14 Apr 2025 at 18:44:38 +0200, Helmut Grohne wrote:
> In general, I doubt we fix this for trixie other than dropping M-A:same
> maybe.
Please don't drop M-A: same from mesa-vulkan-drivers. From my point of
view as someone helping to make Steam be runnable on Linux:
mesa-vulkan-drivers:amd6
On 2025-04-14 18:44, Helmut Grohne wrote:
> On Mon, Apr 14, 2025 at 05:23:01PM +0100, Simon McVittie wrote:
>> Loaders are expected to be able to recognise that a particular driver is not
>> for them, and gracefully not load it. In practice this works fine, because
>> all
>> of our architectures c
Hi Simon,
On Mon, Apr 14, 2025 at 05:23:01PM +0100, Simon McVittie wrote:
> Loaders are expected to be able to recognise that a particular driver is not
> for them, and gracefully not load it. In practice this works fine, because all
> of our architectures can be distinguished by their ELF headers
On Mon, 14 Apr 2025 at 18:48:02 +0200, Michel Dänzer wrote:
> On 2025-04-14 18:23, Simon McVittie wrote:
> >
> > I can see two ways to resolve #980148 without needing to change the
> > search path for Vulkan drivers:
> >
> > 1. [rename the files to have a longer architecture disambiguator]
> >
>
On 2025-04-14 18:23, Simon McVittie wrote:
>
> I can see two ways to resolve #980148 without needing to change the
> search path for Vulkan drivers:
>
> 1. As far as I'm aware, the basename of these files never matters: all
> that matters is their content. So Mesa's debian/rules could do some
On Fri, 04 Apr 2025 at 20:42:48 +0200, Helmut Grohne wrote:
> On Fri, Jan 15, 2021 at 12:06:14PM +0100, Michel Dänzer wrote:
> > On 2021-01-15 12:02 p.m., Thorsten Glaser wrote:
> > > Package: mesa-vulkan-drivers
> > > […]
> > > Multi-Arch: same
> > >
> > > The file /usr/share/vulkan/icd.d/intel_i
On 2025-04-04 20:42, Helmut Grohne wrote:
> On Fri, Jan 15, 2021 at 12:06:14PM +0100, Michel Dänzer wrote:
>> On 2021-01-15 12:02 p.m., Thorsten Glaser wrote:
>>> Package: mesa-vulkan-drivers
>>> […]
>>> Multi-Arch: same
>>>
>>> The file /usr/share/vulkan/icd.d/intel_icd.x86_64.json differs.
>>>
>>
On Mon, Apr 07, 2025 at 10:26:58AM +0200, Michel Dänzer wrote:
> Actually, I think I was referring to the name of the JSON file containing
> x86_64 instead of something x32 specific.
Right. And there we have the same problem as with ARM32. The filename
only encodes the CPU, but Debian supports mu
On 2025-04-04 20:42, Helmut Grohne wrote:
> On Fri, Jan 15, 2021 at 12:06:14PM +0100, Michel Dänzer wrote:
>> On 2021-01-15 12:02 p.m., Thorsten Glaser wrote:
>>> Package: mesa-vulkan-drivers
>>> […]
>>> Multi-Arch: same
>>>
>>> The file /usr/share/vulkan/icd.d/intel_icd.x86_64.json differs.
>>>
>>
user debian...@lists.debian.org
usertags 980148 + fileconflict
severity 980148 serious
thanks
Hi,
On Fri, Jan 15, 2021 at 12:06:14PM +0100, Michel Dänzer wrote:
> On 2021-01-15 12:02 p.m., Thorsten Glaser wrote:
> > Package: mesa-vulkan-drivers
> > […]
> > Multi-Arch: same
> >
> > The file /usr/
On 2021-01-15 12:02 p.m., Thorsten Glaser wrote:
Package: mesa-vulkan-drivers
Version: 20.3.2-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
Package: mesa-vulkan-drivers
[…]
Multi-Arch: same
The file /usr/share/vulkan/icd.d/intel_icd.x86_64.json differs.
amd64:
{
"ICD": {
"a
Package: mesa-vulkan-drivers
Version: 20.3.2-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
Package: mesa-vulkan-drivers
[…]
Multi-Arch: same
The file /usr/share/vulkan/icd.d/intel_icd.x86_64.json differs.
amd64:
{
"ICD": {
"api_version": "1.2.145",
"library_path": "/
17 matches
Mail list logo
