Re: Bug#1072720: libglib2.0-0: Following fix #1070745, typing `A keys doesn't type an À anymore

[Simon McVittie]

On Mon, 10 Jun 2024 at 05:48:44 +0200, gru...@laposte.net wrote:
> I did a
> $ sudo dpkg-reconfigure keyboard-configuration

This changes the keyboard layout that is used for the login screen, and
for any session that does not have its own, separate configuration.
It does not change the keyboard layout for sessions that have already
saved their own session-specific configuration.

> $ dconf dump /org/gnome/desktop/input-sources/
> [/]
> show-all-sources=false
> sources=[('xkb', 'fr+azerty')]
> xkb-options=['lv3:ralt_switch']

Your personal GNOME configuration is still using fr+azerty. If you want
a different layout while you are logged in to GNOME, you will need to
reconfigure that in the Settings application (gnome-control-center).

If you want to reset the layout used within GNOME to match the layout
used by the login screen, you can run

dconf reset /org/gnome/desktop/input-sources/sources

and then log out and back in.

> On logscreen then, and still now, I have the french keyboard
> BUT with the ! (exclamation mark) replaced by the ; (semicolon)

That's the AFNOR layout that you selected. Several other punctuation marks
are in different places in the AFNOR layout: see 
for details.

If you don't want the punctuation to move around in this way, then you
should not select the AFNOR variant.

https://norme-azerty.fr/ shows "AZERTY traditionnel" which is something
similar to the layout you were previously using, and
"Nouvel AZERTY" which is the layout that is labelled as AFNOR in Debian.

smcv

Re: Bug#1072720: libglib2.0-0: Following fix #1070745, typing `A keys doesn't type an À anymore

[grunt2]

I've chosen another configuration to regain the exclamation mark with
sudo dpkg-reconfigure keyboard-configuration

Among GNOME settings, I have three choices available:
Français
Français Azerty
Français Azerty (AFNOR)

the two firsts displays with ` under the 7 (and Français as also an 1/8 sign at 
the key upper top), but ` of the -7 isn't a dead key and doesn't 
produce a À.
the last one, Français Azerty (AFNOR), makes the -7 produce a _ sign 
(or something like similar) that is a dead key!

Français
Français Azerty
don't fire dead keys on the first row of keys

but
Français Azerty (AFNOR)
does. Strange...

De : "Simon McVittie" 
A : 
gru...@laposte.net,1072...@bugs.debian.org,xkeyboard-con...@packages.debian.org,debian-l10n-fre...@lists.debian.org,i...@packages.debian.org
Envoyé: lundi 10 Juin 2024 11:27
Objet : Re: Bug#1072720: libglib2.0-0: Following fix #1070745, typing `A keys 
doesn't type an À anymore
 
On Mon, 10 Jun 2024 at 05:48:44 +0200, gru...@laposte.net wrote:
> I did a
> $ sudo dpkg-reconfigure keyboard-configuration

This changes the keyboard layout that is used for the login screen, and
for any session that does not have its own, separate configuration.
It does not change the keyboard layout for sessions that have already
saved their own session-specific configuration.

> $ dconf dump /org/gnome/desktop/input-sources/
> [/]
> show-all-sources=false
> sources=[('xkb', 'fr+azerty')]
> xkb-options=['lv3:ralt_switch']

Your personal GNOME configuration is still using fr+azerty. If you want
a different layout while you are logged in to GNOME, you will need to
reconfigure that in the Settings application (gnome-control-center).

If you want to reset the layout used within GNOME to match the layout
used by the login screen, you can run

dconf reset /org/gnome/desktop/input-sources/sources

and then log out and back in.

> On logscreen then, and still now, I have the french keyboard
> BUT with the ! (exclamation mark) replaced by the ; (semicolon)

That's the AFNOR layout that you selected. Several other punctuation marks
are in different places in the AFNOR layout: see
for details.

If you don't want the punctuation to move around in this way, then you
should not select the AFNOR variant.

https://norme-azerty.fr/ shows "AZERTY traditionnel" which is something
similar to the layout you were previously using, and
"Nouvel AZERTY" which is the layout that is labelled as AFNOR in Debian.

smcv

Re: Bug#1072720: libglib2.0-0: Following fix #1070745, typing `A keys doesn't type an À anymore

[Simon McVittie]

On Mon, 10 Jun 2024 at 12:35:25 +0200, gru...@laposte.net wrote:
> Among GNOME settings, I have three choices available:
> Français
> Français Azerty
> Français Azerty (AFNOR)

There should be a lot more than that. I don't speak French, but in an
English-language GNOME installation on Debian 12, if I click on "Other"
and search for French, choices available to me include:

* French (alt.)
* French (alt., Latin-9 only)
* French (alt., no dead keys)
* French (legacy, alt.)
* French (legacy, alt., no dead keys)
* French (no dead keys)

... and many more. Many of these are AZERTY layouts even though their
names don't specifically say so.

Based on the information in /usr/share/X11/xkb/symbols/fr, it seems that
"French (legacy, alt.)" should be an AZERTY layout where AltGr+[7] is a
"dead_grave" dead key.

If I'm reading the translation files correctly, the French translation
of "French (legacy, alt.)" might be "Français (obsolète, variante)".

I am not a French speaker and I am not familiar with the history
of French keyboard layouts, so I cannot say whether you are right
or wrong to expect that AltGr+[7] should be a dead key. Perhaps
 would be able to clarify
whether there is a bug in xkb-data or not.

Based on the information available in this bug report, I'm confident that
GLib is now doing the right thing, so this is not a GLib bug.

> Français
> Français Azerty
> don't fire dead keys on the first row of keys
> but
> Français Azerty (AFNOR)
> does. Strange...

If you think this is a regression when compared with older versions of
Debian, then the xkb-data maintainers will need to know the answer to
this question:

What was the most recent date when your keyboard had the behaviour
that you expected, and what version of Debian were you running at
that time?

Thanks,
smcv

mesa_24.1.1-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Jun 2024 14:39:17 +0300
Source: mesa
Built-For-Profiles: noudeb
Architecture: source
Version: 24.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1072901
Changes:
 mesa (24.1.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * control: Bump build-depends on meson for rusticl.
   * rules, control: Bump llvm to 18. (Closes: #1072901)
Checksums-Sha1:
 0e2682c236907261c3bd44ba5f9d5fbf6ee99f7a 5926 mesa_24.1.1-1.dsc
 c8effed23c5a413fcf2ccd98a1118473bff22213 29019256 mesa_24.1.1.orig.tar.xz
 c62b2f7849d8b279ec058d20160964a4e0dbedc8 488 mesa_24.1.1.orig.tar.xz.asc
 51a123cc8e85dd818069affb64c4de1dc2d9792e 103440 mesa_24.1.1-1.debian.tar.xz
 2a53828d01b53dd44745fa3966b05786cbed12d1 10590 mesa_24.1.1-1_source.buildinfo
Checksums-Sha256:
 8fecba0aec417661f9a8a776b636bdab9a2c0e584b11a6cde931dbd42011ecc6 5926 
mesa_24.1.1-1.dsc
 0038826c6f7e88d90b4ce6f719192fa58ca7dedf4edcaa1174cf7bd920ef89ea 29019256 
mesa_24.1.1.orig.tar.xz
 786730e5541f7f7e23112d3d96bf7cbd5fc0ee14f223ccfe0f1960006598805f 488 
mesa_24.1.1.orig.tar.xz.asc
 9f70f36cde1585b6359b9aa0c2b97280fd645b5ae0d4dce1ae41d8c7fc835bb8 103440 
mesa_24.1.1-1.debian.tar.xz
 2b251c8914e0eda227b93f04a9b3560422ab4036ea402ff4d3879b9f66a1543e 10590 
mesa_24.1.1-1_source.buildinfo
Files:
 fbacf1dfba736f376c8aa628701ab12c 5926 graphics optional mesa_24.1.1-1.dsc
 8415005045bfa3a423da5ef1a2303a42 29019256 graphics optional 
mesa_24.1.1.orig.tar.xz
 2785774b090c2c32c0b38a81e8867ec0 488 graphics optional 
mesa_24.1.1.orig.tar.xz.asc
 3972121f09403509ce98572ab4b10176 103440 graphics optional 
mesa_24.1.1-1.debian.tar.xz
 1829e1b7c355e019f364c6655d179684 10590 graphics optional 
mesa_24.1.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmZm5gMACgkQy3AxZaiJ
hNwcUxAAoLIKkL/ZHfd0oHPrbjuBpgHg51QKX3B0sMfQlX1SEyj0xzrit8smFzBt
Pv9O4U9+WcL1AKB3jdCUYTA8Bl7Dhcr8S7SoPN7TSs7Xz4lJUaRhDiWwj5G7qNoO
xxKciGl+YoRY+qbrgLmxpJUgSBxg1MiUWQJffTRrIvfgZwciwwK06mldqmJJWx/n
hHTJiW4YMlavPnWg2obauVrxkT+QotqLJDT3QSMfkkPIhstdf11R1e2wkgQURBQA
oc1ZcDy2eLT2VL2Kcii21PvUGgF5GqBhK1l8Q5PxCHErBIZ8lywJDtRgFDmIZlZS
EfQNzo35FmOa82lVsH4gL/oRnE8jbz0i1KKI8Nq+rNmpcQnERgInKvUHHAeT4fOk
xw1+kHMFwqSXvWzfa9cEFjWHoIe47nWGe8z9He6QzCb5QefZZ+4ax21n7qtzdUrc
20hv2n/NgEHX8PRVP6uQr2ND9LzhMv/v64ClvQBN09q+Cg1Nz5/L9qlwKLdk76BB
A+oen+g1xg9y29hD1XXUamxH/0CLLvWiWz+7lugC0suBUPf3UhtknJoU7EEjA8T0
Q83YwKiBE7sJDJGsKJjhfAQOtNcM29YsxWDK9DMX0F/Exd0GVxsVrOpamgGOBe79
q5+wE1eqPMnC6V+GAgVhMaQU8lp1dGWl4/lVz5FxhwHnwAv/jTA=
=RrK1
-END PGP SIGNATURE-



pgpnqlMuBLlGz.pgp
Description: PGP signature

Processing of mesa_24.1.1-1_source.changes

[Debian FTP Masters]

mesa_24.1.1-1_source.changes uploaded successfully to localhost
along with the files:
  mesa_24.1.1-1.dsc
  mesa_24.1.1.orig.tar.xz
  mesa_24.1.1.orig.tar.xz.asc
  mesa_24.1.1-1.debian.tar.xz
  mesa_24.1.1-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1072901: marked as done (mesa-opencl-icd: Please upgrade to libclc-18/19 supporting newer GPUs)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 12:05:45 +
with message-id 
and subject line Bug#1072901: fixed in mesa 24.1.1-1
has caused the Debian Bug report #1072901,
regarding mesa-opencl-icd: Please upgrade to libclc-18/19 supporting newer GPUs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1072901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mesa-opencl-icd
Version: 24.1.0-2
Severity: normal

Dear Maintainer,

I have a new GPU which is not supported by the current mesa-opencl-icd because 
libclc-17 is too old:

$ clinfo
[..]
Number of devices 2
  Device Name AMD Radeon RX 7800 XT 
(radeonsi, navi32, LLVM 17.0.6, DRM 3.57, 6.7.12-amd64)
[..]
=== CL_PROGRAM_BUILD_LOG ===
fatal error: cannot open file '/usr/lib/clc/gfx1036-amdgcn-mesa-mesa3d.bc': No 
such file or directory
  Preferred work group size multiple (kernel) 
[..]

$ apt-file search /usr/lib/clc/gfx1036-amdgcn-mesa-mesa3d.bc
libclc-18: /usr/lib/clc/gfx1036-amdgcn-mesa-mesa3d.bc
libclc-19: /usr/lib/clc/gfx1036-amdgcn-mesa-mesa3d.bc

Please upgrade.

Thanks in advance,
Ximin


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (300, 'unstable'), (100, 
'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mesa-opencl-icd depends on:
ii  libc62.38-12
ii  libclang-cpp17t641:17.0.6-12
ii  libclc-171:17.0.6-12
ii  libdrm-amdgpu1   2.4.120-2
ii  libdrm-radeon1   2.4.120-2
ii  libdrm2  2.4.120-2
ii  libelf1t64   0.191-1+b1
ii  libexpat12.6.2-1
ii  libgcc-s114-20240330-1
ii  libllvm17t64 1:17.0.6-12
ii  libllvmspirvlib1717.0.0-5
ii  libstdc++6   14-20240330-1
ii  libzstd1 1.5.5+dfsg2-2
ii  ocl-icd-libopencl1 [libopencl1]  2.3.2-1+b1
ii  zlib1g   1:1.3.dfsg+really1.3.1-1

mesa-opencl-icd recommends no packages.

mesa-opencl-icd suggests no packages.

Versions of packages xserver-xorg depends on:
ii  x11-xkb-utils 7.7+8+b1
ii  xkb-data  2.41-2
ii  xserver-xorg-core 2:21.1.12-1
ii  xserver-xorg-input-all1:7.7+23
ii  xserver-xorg-input-evdev [xorg-driver-input]  1:2.10.6-2+b3
ii  xserver-xorg-input-libinput [xorg-driver-input]   1.4.0-1
ii  xserver-xorg-input-synaptics [xorg-driver-input]  1.9.2-1+b1
ii  xserver-xorg-input-wacom [xorg-driver-input]  1.2.2-1
ii  xserver-xorg-video-all1:7.7+23
ii  xserver-xorg-video-amdgpu [xorg-driver-video] 23.0.0-1
ii  xserver-xorg-video-ati [xorg-driver-video]1:22.0.0-1
ii  xserver-xorg-video-cirrus [xorg-driver-video] 1:1.5.3-1+b5
ii  xserver-xorg-video-fbdev [xorg-driver-video]  1:0.5.0-2
ii  xserver-xorg-video-intel [xorg-driver-video]  2:2.99.917+git20210115-1
ii  xserver-xorg-video-mga [xorg-driver-video]1:2.0.0-1+b1
ii  xserver-xorg-video-nouveau [xorg-driver-video]1:1.0.17-3
ii  xserver-xorg-video-qxl [xorg-driver-video]0.1.6-1
ii  xserver-xorg-video-radeon [xorg-driver-video] 1:22.0.0-1
ii  xserver-xorg-video-vesa [xorg-driver-video]   1:2.6.0-1
ii  xserver-xorg-video-vmware [xorg-driver-video] 1:13.4.0-1

Versions of packages xserver-xorg recommends:
ii  libgl1-mesa-dri  24.1.0-2
pn  xserver-xorg-legacy  

Versions of packages xserver-xorg-core depends on:
ii  keyboard-configuration  1.227
ii  libaudit1   1:3.1.2-2
ii  libc6   2.38-12
ii  libdbus-1-3 1.14.10-4+b1
ii  libdrm2 2.4.120-2
ii  libegl1 1.7.0-1+b1
ii  libepoxy0   1.5.10-1+b2
ii  libgbm1 24.1.0-2
ii  libgcrypt20 1.10.3-3
ii  libgl1  1.7.0-1+b1
ii  libpciaccess0   0.17-3+b1
ii  libpixman-1-0   0.42.2-1+b1

[Git][xorg-team/lib/mesa] Pushed new tag mesa-24.1.1-1

[Timo Aaltonen (@tjaalton)]

Timo Aaltonen pushed new tag mesa-24.1.1-1 at X Strike Force / lib / mesa

-- 
This project does not include diff previews in email notifications.
View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/-/tree/mesa-24.1.1-1
You're receiving this email because of your account on salsa.debian.org.

[Git][xorg-team/lib/mesa][debian-unstable] 71 commits: docs: add sha256sum for 24.1.0

[Timo Aaltonen (@tjaalton)]

Timo Aaltonen pushed to branch debian-unstable at X Strike Force / lib / mesa


Commits:
e844211d by Eric Engestrom at 2024-05-22T20:30:50+02:00
docs: add sha256sum for 24.1.0

- - - - -
f361b348 by Friedrich Vock at 2024-05-22T21:23:13+02:00
radv: Use max_se instead of num_se where appropriate

Scratch allocation needs to happen using max_se, otherwise there can be
hangs.

Cc: mesa-stable
Reviewed-by: Marek Olšák 
Part-of: ;
(cherry picked from commit db564a40b3bd936053e5e14d1f0df6b96e305a08)

- - - - -
fd3f9a15 by Friedrich Vock at 2024-05-22T21:23:13+02:00
radeonsi: Use max_se instead of num_se where appropriate

Scratch allocation needs to happen using max_se, otherwise there can be
hangs.

Cc: mesa-stable
Reviewed-by: Marek Olšák 
Part-of: ;
(cherry picked from commit 18c736bcfc55b8fa309ede02332b9c7a2ca22e78)

- - - - -
83fc0888 by Timur Kristóf at 2024-05-22T21:23:13+02:00
radv: Fix TCS -> TES I/O linking typo of VARYING_SLOT vs. BIT.

In these bitwise expressions, VARYING_BIT_* should be used,
but the code mistakenly used VARYING_SLOT_* which is wrong.

Fixes: 0e481a4adcd8006256c27d100a0a0f0c01a94171
Signed-off-by: Timur Kristóf 
Reviewed-by: Mike Blumenkrantz 
Reviewed-by: Samuel Pitoiset 
Part-of: ;
(cherry picked from commit 3963e4b53aa73ef032709769585bdb1e3b6a8099)

- - - - -
6206f4cf by Lionel Landwerlin at 2024-05-31T08:33:32+02:00
.pick_status.json: Update to ce43d7eb7f97bdde61b184a99940c4b03c2f0929

- - - - -
9d34ce91 by Renato Pereyra at 2024-05-31T08:33:45+02:00
anv: Attempt to compile all pipelines even after errors

Per the Vulkan Spec section 10.1, the implementation is supposed to
attempt to create all pipelines even if creation of any one pipeline
in a create call fails. If more than one error occur, any one error
is valid as a return value.

Signed-off-by: Renato Pereyra 
Cc: mesa-stable
Reviewed-by: Ivan Briano 
Reviewed-by: Lionel Landwerlin 
Part-of: ;
(cherry picked from commit 51d6162c80bb27281f014b72b52b12e7ef11db98)

- - - - -
76874a44 by Jose Maria Casanova Crespo at 2024-05-31T08:33:46+02:00
v3d: fix CLE MMU errors avoiding using last bytes of CL BOs.

The last V3D_CLE_READAHEAD bytes of the CLE buffer are unusable because
using them would prefetch the next readahead bytes of the CL that would
be outside the allocated BO. To guarantee that we can chain a BO to the
current CL we always reserve space for the BRANCH packet.

Not taking this into account has been generating kernel dmesg errors like
"MMU error from client CLE".

As V3D_CLE_READAHEAD is different from RPi4 (256 bytes) to RPi5 (1024 bytes).
So we needed to rename v3d_cl.c to v3dX_cl.c to have different objects per
V3D_VERSION.

Extra assertions have been included to validate that we don't write
packets over the usable size of the CL silently.

v2: - Remove spurious blank line (Iago Toral)
- Do not declare unusable the space needed for the BRANCH packet,
  and take it into account for all reservations.
v3: - Handle BRANCH packet reserve only when CLE BO allocation is done.
v4: - Assert on BO size updates that we are within the BO size.
  (Iago Toral)

Reviewed-by: Iago Toral Quiroga 
cc: mesa-stable

Part-of: ;
(cherry picked from commit 11dce2ac8154237b74ee3c4bd2aaec685739f0cc)

- - - - -
4f056182 by Jose Maria Casanova Crespo at 2024-05-31T08:33:48+02:00
v3dv: fix CLE MMU errors avoiding using last bytes of CL BOs.

The last V3D_CLE_READAHEAD bytes of the CLE buffer are unusable because
using them would prefetch the next readahead bytes of the CL that would
be outside the allocated BO. To guarantee that we can chain a BO to the
current CL we always reserve space for the BRANCH or
RETURN_FROM_SUB_LIST packets.

Not taking this into account has been generating kernel dmesg errors like
"MMU error from client CLE".

As V3D_CLE_READAHEAD is different from RPi4 (256 bytes) to RPi5 (1024 bytes).
So we needed to rename v3dv_cl.c to v3dvX_cl.c to have different objects per
V3D_VERSION.

Extra assertions have been included to validate that we don't write
packets over the usable size of the CL silently.

v2: - Do not declare unusable the space needed for the BRANCH packet,
  but take it into account for all space reservations.
v3: - Squash here ("v3dv: Secondary CL needs also to handle CLE 
readahead")
- Remove spureous parenthesis (Iago Toral)
- Refactor to avoid checking for needs_return_from_sub_list inside
  cl_alloc_bo adding unusable_space as new p

[Git][xorg-team/lib/mesa][upstream-unstable] 66 commits: docs: add sha256sum for 24.1.0

[Timo Aaltonen (@tjaalton)]

Timo Aaltonen pushed to branch upstream-unstable at X Strike Force / lib / mesa


Commits:
e844211d by Eric Engestrom at 2024-05-22T20:30:50+02:00
docs: add sha256sum for 24.1.0

- - - - -
f361b348 by Friedrich Vock at 2024-05-22T21:23:13+02:00
radv: Use max_se instead of num_se where appropriate

Scratch allocation needs to happen using max_se, otherwise there can be
hangs.

Cc: mesa-stable
Reviewed-by: Marek Olšák 
Part-of: ;
(cherry picked from commit db564a40b3bd936053e5e14d1f0df6b96e305a08)

- - - - -
fd3f9a15 by Friedrich Vock at 2024-05-22T21:23:13+02:00
radeonsi: Use max_se instead of num_se where appropriate

Scratch allocation needs to happen using max_se, otherwise there can be
hangs.

Cc: mesa-stable
Reviewed-by: Marek Olšák 
Part-of: ;
(cherry picked from commit 18c736bcfc55b8fa309ede02332b9c7a2ca22e78)

- - - - -
83fc0888 by Timur Kristóf at 2024-05-22T21:23:13+02:00
radv: Fix TCS -> TES I/O linking typo of VARYING_SLOT vs. BIT.

In these bitwise expressions, VARYING_BIT_* should be used,
but the code mistakenly used VARYING_SLOT_* which is wrong.

Fixes: 0e481a4adcd8006256c27d100a0a0f0c01a94171
Signed-off-by: Timur Kristóf 
Reviewed-by: Mike Blumenkrantz 
Reviewed-by: Samuel Pitoiset 
Part-of: ;
(cherry picked from commit 3963e4b53aa73ef032709769585bdb1e3b6a8099)

- - - - -
6206f4cf by Lionel Landwerlin at 2024-05-31T08:33:32+02:00
.pick_status.json: Update to ce43d7eb7f97bdde61b184a99940c4b03c2f0929

- - - - -
9d34ce91 by Renato Pereyra at 2024-05-31T08:33:45+02:00
anv: Attempt to compile all pipelines even after errors

Per the Vulkan Spec section 10.1, the implementation is supposed to
attempt to create all pipelines even if creation of any one pipeline
in a create call fails. If more than one error occur, any one error
is valid as a return value.

Signed-off-by: Renato Pereyra 
Cc: mesa-stable
Reviewed-by: Ivan Briano 
Reviewed-by: Lionel Landwerlin 
Part-of: ;
(cherry picked from commit 51d6162c80bb27281f014b72b52b12e7ef11db98)

- - - - -
76874a44 by Jose Maria Casanova Crespo at 2024-05-31T08:33:46+02:00
v3d: fix CLE MMU errors avoiding using last bytes of CL BOs.

The last V3D_CLE_READAHEAD bytes of the CLE buffer are unusable because
using them would prefetch the next readahead bytes of the CL that would
be outside the allocated BO. To guarantee that we can chain a BO to the
current CL we always reserve space for the BRANCH packet.

Not taking this into account has been generating kernel dmesg errors like
"MMU error from client CLE".

As V3D_CLE_READAHEAD is different from RPi4 (256 bytes) to RPi5 (1024 bytes).
So we needed to rename v3d_cl.c to v3dX_cl.c to have different objects per
V3D_VERSION.

Extra assertions have been included to validate that we don't write
packets over the usable size of the CL silently.

v2: - Remove spurious blank line (Iago Toral)
- Do not declare unusable the space needed for the BRANCH packet,
  and take it into account for all reservations.
v3: - Handle BRANCH packet reserve only when CLE BO allocation is done.
v4: - Assert on BO size updates that we are within the BO size.
  (Iago Toral)

Reviewed-by: Iago Toral Quiroga 
cc: mesa-stable

Part-of: ;
(cherry picked from commit 11dce2ac8154237b74ee3c4bd2aaec685739f0cc)

- - - - -
4f056182 by Jose Maria Casanova Crespo at 2024-05-31T08:33:48+02:00
v3dv: fix CLE MMU errors avoiding using last bytes of CL BOs.

The last V3D_CLE_READAHEAD bytes of the CLE buffer are unusable because
using them would prefetch the next readahead bytes of the CL that would
be outside the allocated BO. To guarantee that we can chain a BO to the
current CL we always reserve space for the BRANCH or
RETURN_FROM_SUB_LIST packets.

Not taking this into account has been generating kernel dmesg errors like
"MMU error from client CLE".

As V3D_CLE_READAHEAD is different from RPi4 (256 bytes) to RPi5 (1024 bytes).
So we needed to rename v3dv_cl.c to v3dvX_cl.c to have different objects per
V3D_VERSION.

Extra assertions have been included to validate that we don't write
packets over the usable size of the CL silently.

v2: - Do not declare unusable the space needed for the BRANCH packet,
  but take it into account for all space reservations.
v3: - Squash here ("v3dv: Secondary CL needs also to handle CLE 
readahead")
- Remove spureous parenthesis (Iago Toral)
- Refactor to avoid checking for needs_return_from_sub_list inside
  cl_alloc_bo adding unusable_space as new

Re: Bug#1072720: libglib2.0-0: Following fix #1070745, typing `A keys doesn't type an À anymore

[grunt2]

It ‌was difficult to find in the Gnome Settings, but yes, you're right : 
there's a French(legacy,variant) that can be reached and should be taken to 
have the dead keys back.

So it isn't a bug, eventually, that I've encountered. Except that I don't 
understand how my keyboard might have changed its layout once.
Thanks for all the help you provided !

It's fine now. À È Ù Ì Ỳ...

Regards,

Marc Le Bihan

De : "Simon McVittie" 
A : 
gru...@laposte.net,1072...@bugs.debian.org,xkeyboard-con...@packages.debian.org,debian-l10n-fre...@lists.debian.org,i...@packages.debian.org
Envoyé: lundi 10 Juin 2024 13:37
Objet : Re: Bug#1072720: libglib2.0-0: Following fix #1070745, typing `A keys 
doesn't type an À anymore
 
On Mon, 10 Jun 2024 at 12:35:25 +0200, gru...@laposte.net wrote:
> Among GNOME settings, I have three choices available:
> Français
> Français Azerty
> Français Azerty (AFNOR)

There should be a lot more than that. I don't speak French, but in an
English-language GNOME installation on Debian 12, if I click on "Other"
and search for French, choices available to me include:

* French (alt.)
* French (alt., Latin-9 only)
* French (alt., no dead keys)
* French (legacy, alt.)
* French (legacy, alt., no dead keys)
* French (no dead keys)

... and many more. Many of these are AZERTY layouts even though their
names don't specifically say so.

Based on the information in /usr/share/X11/xkb/symbols/fr, it seems that
"French (legacy, alt.)" should be an AZERTY layout where AltGr+[7] is a
"dead_grave" dead key.

If I'm reading the translation files correctly, the French translation
of "French (legacy, alt.)" might be "Français (obsolète, variante)".

I am not a French speaker and I am not familiar with the history
of French keyboard layouts, so I cannot say whether you are right
or wrong to expect that AltGr+[7] should be a dead key. Perhaps
would be able to clarify
whether there is a bug in xkb-data or not.

Based on the information available in this bug report, I'm confident that
GLib is now doing the right thing, so this is not a GLib bug.

> Français
> Français Azerty
> don't fire dead keys on the first row of keys
> but
> Français Azerty (AFNOR)
> does. Strange...

If you think this is a regression when compared with older versions of
Debian, then the xkb-data maintainers will need to know the answer to
this question:

What was the most recent date when your keyboard had the behaviour
that you expected, and what version of Debian were you running at
that time?

Thanks,
smcv

Processing of xcb-util-errors_1.0.1-2~bpo12+1_amd64.changes

[Debian FTP Masters]

xcb-util-errors_1.0.1-2~bpo12+1_amd64.changes uploaded successfully to localhost
along with the files:
  xcb-util-errors_1.0.1-2~bpo12+1.dsc
  xcb-util-errors_1.0.1.orig.tar.xz
  xcb-util-errors_1.0.1.orig.tar.xz.asc
  xcb-util-errors_1.0.1-2~bpo12+1.debian.tar.xz
  libxcb-errors-dev_1.0.1-2~bpo12+1_amd64.deb
  libxcb-errors0-dbgsym_1.0.1-2~bpo12+1_amd64.deb
  libxcb-errors0_1.0.1-2~bpo12+1_amd64.deb
  xcb-util-errors_1.0.1-2~bpo12+1_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1072941: libgl1-mesa-dri: not multi-arch coinstallable

[Sven Joachim]

Package: libgl1-mesa-dri
Version: 24.1.1-1
Severity: serious
Control: block -1 by 1067699

I just had to downgrade a bunch of packages from src:mesa to version
24.1.0-2, because the installation of libllvm18:i386 failed due to a
file conflict that has been present for a few months, see #1067699.

Probably quite a few other people are going to experience the same
issue, therefore I am filing this as RC to prevent testing migration and
alert unstable users.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Processed: libgl1-mesa-dri: not multi-arch coinstallable

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1067699
Bug #1072941 [libgl1-mesa-dri] libgl1-mesa-dri: not multi-arch coinstallable
1072941 was not blocked by any bugs.
1072941 was not blocking any bugs.
Added blocking bug(s) of 1072941: 1067699

-- 
1072941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

[Git][xorg-team/lib/libdrm] Pushed new tag libdrm-2.4.121-1

[Timo Aaltonen (@tjaalton)]

Timo Aaltonen pushed new tag libdrm-2.4.121-1 at X Strike Force / lib / libdrm

-- 
This project does not include diff previews in email notifications.
View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/libdrm/-/tree/libdrm-2.4.121-1
You're receiving this email because of your account on salsa.debian.org.

libdrm_2.4.121-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Jun 2024 19:31:37 +0300
Source: libdrm
Built-For-Profiles: noudeb
Architecture: source
Version: 2.4.121-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1070815
Changes:
 libdrm (2.4.121-1) unstable; urgency=medium
 .
   * New upstream release.
   * control: Add arm64 to libdrm-intel1 archs. (Closes: #1070815)
   * symbols: Updated.
Checksums-Sha1:
 9f2584ab15024e3eab6755cb8f4daca1e4ee4bf3 3168 libdrm_2.4.121-1.dsc
 dc61485b577eb7a69ad68d76cfac3ff033af87a0 480840 libdrm_2.4.121.orig.tar.xz
 9d6cb1b27c7761b3a558e3cbe902600892fef980 659 libdrm_2.4.121.orig.tar.xz.asc
 8534fd551fc1a087507c864ca727f4673c295faa 62308 libdrm_2.4.121-1.debian.tar.xz
 f822660207d887f46099799ad56cd0e90be025bf 8627 libdrm_2.4.121-1_source.buildinfo
Checksums-Sha256:
 477f05a16e73fb69067ba89884efa44306d11241bd99f2f77fd37339191a5bc2 3168 
libdrm_2.4.121-1.dsc
 909084a505d7638887f590b70791b3bbd9069c710c948f5d1f1ce6d080cdfcab 480840 
libdrm_2.4.121.orig.tar.xz
 d337303de9639513ed029da6b009ee1dfd0e11ba79af9dd93dfa5256b3f56207 659 
libdrm_2.4.121.orig.tar.xz.asc
 cae39a57d3a2b758df6a0a27f79c9d6768b19582e6afdf4388376e0b546d0b65 62308 
libdrm_2.4.121-1.debian.tar.xz
 2e8b5e15c755a5840a3f7b00dcc1d43f25b0bfed1f5305a756b93bc41dcc96c0 8627 
libdrm_2.4.121-1_source.buildinfo
Files:
 0d8d8459b07497afd31bf99f15547f57 3168 libs optional libdrm_2.4.121-1.dsc
 9eaa82b7b7a79972c6b11dd25a4356b1 480840 libs optional 
libdrm_2.4.121.orig.tar.xz
 6421330589744e3c3a73fa19fa8c1045 659 libs optional 
libdrm_2.4.121.orig.tar.xz.asc
 48adb0944e99bfde7ade3e2e9edf3930 62308 libs optional 
libdrm_2.4.121-1.debian.tar.xz
 a84ce2cdf319b6a90526b875199bb904 8627 libs optional 
libdrm_2.4.121-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmZnKngACgkQy3AxZaiJ
hNxPHw/8ChKfbtLLCKKrcj90pAtyLKYaqZhlZCp24nM9vVF0Ix4ftO+JJxHZ+GWz
MXPaKQGHfHWzAdpsfu/R61RiVoGuC9jjdAKcnnzADsD07hFReWm6lebiNV8dpgbz
gDN1gCXFtio8AAvZLRBr+ji5AbnZ3Id5xZfjTxaJG9Q5+ck+5wcKgKq2NZK1Bj2f
7ZtQ/bitlu7zDgd3iXDptGeK8YRlTiW/45C6FbxzJ2bg9XibQTGjlCsAmG3Mg0vi
pVp259cJP3Sqm0cBI7x8E+nkRiAneM4KAmAN5wVuDdiyyfWrcTokqfWYocjKxbyU
TKOSq77qF62AT15/1wWeZABn3HlI8Ai4T8CH8e/FlpjLKHB9rSJjCNyrTxnBWCiZ
0Gl3NDY+o67QhSWg7sCJTQiawmaijwKlPa8Npkhm6mIsFs5ZpKO/VTULVEZbfpdt
zRBsNpjYDkutpjVz2JDOtMNV/ibET+grCtkU3OTmxFCX53UpWpaDyBGBfGcfGaw5
BzQaMjIKgFEjtXfKwK6bedYyMdeGCjIWCCelPHJkPT37GQqIsRUMbUnzQkoGOE0a
bq5Ljru+hGeWiEcTwDrQWqQu5aLnTR+Nq4LdIYQeTsMBapCcGpNn2cGnCEvW1Dc9
TwkTESl4NEs520SwZDtO/lMvxzRZgNRvnbNgxtf+fj4SRk+g4l4=
=aLxJ
-END PGP SIGNATURE-



pgpk53sBV6ZAD.pgp
Description: PGP signature

Bug#1070815: marked as done (libdrm-intel1 should be compiled for arm64)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 16:50:03 +
with message-id 
and subject line Bug#1070815: fixed in libdrm 2.4.121-1
has caused the Debian Bug report #1070815,
regarding libdrm-intel1 should be compiled for arm64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1070815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdrm-intel1
Version: 2.4.120-2
Severity: wishlist
Tags: patch
X-Debbugs-Cc: civil.o...@gmail.com

Dear Maintainer,

   * What led up to the situation?

 I recently got an Ampere Altra board and I've decided to try getting
 Intel Arc 750 working on it. While that requires vendor-specific kernel
 patches (Workaround for Altra's PCIe Errata) and recent kernel
 (6.9.0-rc6 with drm-next/xe), I managed to get it working.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 One of the obstacles I had, was that libdrm-intel1 is not compiled on
 arm64 systems in debian (testing or unstable or experimental). Upstream
 actually have nothing that prevents you from compiling it and only
 requires to add arm64 in control for libdrm-intel1.

   * What was the outcome of this action?

 I've actually managed to build libdrm-intel1 on aarch64.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 6.9.0-rc6+ (SMP w/64 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libdrm-intel1 depends on:
ii  libc6  2.38-7
ii  libdrm22.4.120-3
ii  libpciaccess0  0.17-3+b1

libdrm-intel1 recommends no packages.

libdrm-intel1 suggests no packages.

-- no debconf information

-- patch that I've applied to make it build:
--- libdrm-2.4.120.old/debian/control   2024-02-08 08:49:20.0 +0100
+++ libdrm-2.4.120/debian/control   2024-05-09 10:30:48.688180370 +0200
@@ -24,7 +24,7 @@
 Architecture: linux-any hurd-any
 Depends:
  libdrm2 (= ${binary:Version}),
- libdrm-intel1 (= ${binary:Version}) [amd64 i386 hurd-i386 x32],
+ libdrm-intel1 (= ${binary:Version}) [arm64 amd64 i386 hurd-i386 x32],
  libdrm-radeon1 (= ${binary:Version}),
  libdrm-nouveau2 (= ${binary:Version}) [linux-any],
  libdrm-amdgpu1 (= ${binary:Version}),
@@ -104,7 +104,7 @@
  This is a udeb, or a microdeb, for the debian-installer.

 Package: libdrm-intel1
-Architecture: amd64 i386 hurd-i386 x32
+Architecture: arm64 amd64 i386 hurd-i386 x32
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
--- End Message ---
--- Begin Message ---
Source: libdrm
Source-Version: 2.4.121-1
Done: Timo Aaltonen 

We believe that the bug you reported is fixed in the latest version of
libdrm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated libdrm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Jun 2024 19:31:37 +0300
Source: libdrm
Built-For-Profiles: noudeb
Architecture: source
Version: 2.4.121-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1070815
Changes:
 libdrm (2.4.121-1) unstable; urgency=medium
 .
   * New upstream release.
   * control: Add arm64 to libdrm-intel1 archs. (Closes: #1070815)
   * symbols: Updated.
Checksums-Sha1:
 9f2584ab15024e3eab6755cb8f4daca1e4ee4bf3 3168 libdrm_2.4.121-1.dsc
 dc61485b577eb7a69ad68d76cfac3ff033af87a0 480840 libdrm_2.4.121.orig.tar.xz
 9d6cb1b27c7761b3a558e3cbe902600892fef980 659 libdrm_2.4.121.orig.tar.xz.asc
 8534fd551fc1a087507c864ca727f4673c295faa 62308 libdrm_2.4.121-1.debian.tar.xz
 f822660207d887f46099799ad56cd0e90be025bf 8627 libdrm_2.4.121-1_source.buildinfo
Checksums-Sha256:
 477f05a16e73fb69067ba89884efa44306d11241bd99f2f77fd37339191a5bc2 3168 
libdrm_2.4.121-1.dsc
 909084a505d7638887f590b70791b3bbd9

Processing of libdrm_2.4.121-1_source.changes

[Debian FTP Masters]

libdrm_2.4.121-1_source.changes uploaded successfully to localhost
along with the files:
  libdrm_2.4.121-1.dsc
  libdrm_2.4.121.orig.tar.xz
  libdrm_2.4.121.orig.tar.xz.asc
  libdrm_2.4.121-1.debian.tar.xz
  libdrm_2.4.121-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

[Git][xorg-team/lib/mesa] Pushed new tag mesa-24.1.1-2

[Timo Aaltonen (@tjaalton)]

Timo Aaltonen pushed new tag mesa-24.1.1-2 at X Strike Force / lib / mesa

-- 
This project does not include diff previews in email notifications.
View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/-/tree/mesa-24.1.1-2
You're receiving this email because of your account on salsa.debian.org.

[Git][xorg-team/lib/mesa][debian-unstable] 2 commits: rules, control: Revert back to llvm 17. (Closes: #1072941)

[Timo Aaltonen (@tjaalton)]

Timo Aaltonen pushed to branch debian-unstable at X Strike Force / lib / mesa


Commits:
8af1aea9 by Timo Aaltonen at 2024-06-10T19:59:29+03:00
rules, control: Revert back to llvm 17. (Closes: #1072941)

- - - - -
caddef23 by Timo Aaltonen at 2024-06-10T19:59:47+03:00
release to sid

- - - - -


3 changed files:

- debian/changelog
- debian/control
- debian/rules


Changes:

=
debian/changelog
=
@@ -1,3 +1,9 @@
+mesa (24.1.1-2) unstable; urgency=medium
+
+  * rules, control: Revert back to llvm 17. (Closes: #1072941)
+
+ -- Timo Aaltonen   Mon, 10 Jun 2024 19:59:35 +0300
+
 mesa (24.1.1-1) unstable; urgency=medium
 
   * New upstream release.


=
debian/control
=
@@ -45,19 +45,19 @@ Build-Depends:
  libelf-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x sparc64 x32],
  libwayland-dev (>= 1.15.0) [linux-any],
  libwayland-egl-backend-dev (>= 1.15.0) [linux-any],
- llvm-18-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x sparc64 x32],
- libclang-18-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x sparc64 x32],
- libclang-cpp18-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 
ppc64el riscv64 s390x sparc64 x32],
- libclc-18-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x sparc64 x32],
+ llvm-17-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x sparc64 x32],
+ libclang-17-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x sparc64 x32],
+ libclang-cpp17-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 
ppc64el riscv64 s390x sparc64 x32],
+ libclc-17-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x sparc64 x32],
  wayland-protocols (>= 1.24),
  zlib1g-dev,
  libglvnd-core-dev (>= 1.3.2),
  valgrind [amd64 arm64 armhf i386 mips64el powerpc ppc64 ppc64el s390x],
  rustc [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el riscv64 
s390x x32],
  bindgen (>= 0.66.1~) [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 
ppc64el riscv64 s390x x32],
- llvm-spirv-18 [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x x32],
- libclc-18 [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el riscv64 
s390x x32],
- libllvmspirvlib-18-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 
ppc64el riscv64 s390x sparc64 x32],
+ llvm-spirv-17 [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x x32],
+ libclc-17 [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el riscv64 
s390x x32],
+ libllvmspirvlib-17-dev [amd64 arm64 armel armhf i386 loong64 powerpc ppc64 
ppc64el riscv64 s390x sparc64 x32],
 Rules-Requires-Root: no
 Vcs-Git: https://salsa.debian.org/xorg-team/lib/mesa.git
 Vcs-Browser: https://salsa.debian.org/xorg-team/lib/mesa
@@ -382,7 +382,7 @@ Section: libs
 Architecture: amd64 arm64 armel armhf i386 loong64 powerpc ppc64 ppc64el 
riscv64 s390x sparc64 x32
 Pre-Depends: ${misc:Pre-Depends}
 Depends:
- libclc-18,
+ libclc-17,
  ocl-icd-libopencl1 | libopencl1,
  ${shlibs:Depends},
  ${misc:Depends},


=
debian/rules
=
@@ -13,7 +13,7 @@ DEB_HOST_ARCH_OS   ?= $(shell dpkg-architecture 
-qDEB_HOST_ARCH_OS)
 DEB_HOST_ARCH_CPU  ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
 
 # for finding the correct llvm-config when meson doesn't know about it yet
-LLVM_VERSION = 18
+LLVM_VERSION = 17
 export PATH:=/usr/lib/llvm-$(LLVM_VERSION)/bin/:$(PATH)
 
 export DEB_BUILD_MAINT_OPTIONS=optimize=-lto



View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/-/compare/70a170c57d903733edc84689a84e9bb6f9a0a1d8...caddef234411083531177f4a0f0109c0f380a313

-- 
This project does not include diff previews in email notifications.
View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/-/compare/70a170c57d903733edc84689a84e9bb6f9a0a1d8...caddef234411083531177f4a0f0109c0f380a313
You're receiving this email because of your account on salsa.debian.org.

mesa_24.1.1-2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Jun 2024 19:59:35 +0300
Source: mesa
Built-For-Profiles: noudeb
Architecture: source
Version: 24.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1072941
Changes:
 mesa (24.1.1-2) unstable; urgency=medium
 .
   * rules, control: Revert back to llvm 17. (Closes: #1072941)
Checksums-Sha1:
 e072d0673dd87fc21fe97e8f0c64f3870e157bf2 5926 mesa_24.1.1-2.dsc
 e937c0c72de1c68f4bf5e417e5ae6c0efcd3 103472 mesa_24.1.1-2.debian.tar.xz
 493f4f256b05851fa26bf8ed28d3064d390aae84 10590 mesa_24.1.1-2_source.buildinfo
Checksums-Sha256:
 3eea87f9ecf99fdf0e6f4a16b5bc40d0246f97df2d48ee88b9bc1247acaa6d37 5926 
mesa_24.1.1-2.dsc
 19e0461feda34c2883a5f2fd88f592f1568b22c001bdf37f8b634cb2c8cd39d2 103472 
mesa_24.1.1-2.debian.tar.xz
 f4844024ff404b4d73ca4846e3be27e2f3c029da26b419ef1b81b394b97fcdd0 10590 
mesa_24.1.1-2_source.buildinfo
Files:
 f9fe9f0aa79ea580d40f50913d6e8743 5926 graphics optional mesa_24.1.1-2.dsc
 6661fed4baf1baf61e6e4dd245dc9da2 103472 graphics optional 
mesa_24.1.1-2.debian.tar.xz
 9b21ca7ca0faf443852c3075d10822d1 10590 graphics optional 
mesa_24.1.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmZnMQkACgkQy3AxZaiJ
hNzMiw/8DwO+13l9Fpls7wAf7sG9lwnfrmDfJjv/aEssd1ITxV2LiZWwWh2STP5L
/9OC7J8e2GyMZ49tkwmCr8nwHyoG9PxEMcnM9Mt7WdmHSQ8681y083+ySoxBb97m
uUpepWybzoTECl+Y5u46gp1BFlYlxuriebouSBWwzbrsaTLgEw/10SEaRjrXEOLL
CXJNFeraXMF/X0NHPHadhghv4A78iBJyg0bBfb02wQsKrVvtzUvWzoF+K4iVn5is
4GPzn6BDyZBE/LIkJ0/9ddS7e27qCf7y+uzuKK7Gg3AKKw2sVlGmU1rWIilK+1Ju
XUVJyDabTdg3b4hjlEnH9arlnL4nZqcNSyNyyUgQxBRrFvq1Krbxr7UilZfkXFC/
COPkfTKtBeoItWIMy9Q4ZjDgSU5EZbXxG0ee6xi/B0JLxX5A9n8DH4smFdTk1zE5
w3HZqGVRZx4Ui/f2kCqv+KICjL1Rb7g9GZhfKJrOPuHaslz/OIyyGc5XIBVnjwIw
3pJTXHobC5xa8A/uunPsa9NN8EUxVDFA4Ze4e9se6gG1shRtI887iFboyHPTpJp9
Cqo6s4c8zLMaA049ftF0CV4Z9zxMdsNXWrNjfOl34Dt4xdiGJ9cOcKICnIYUw8yj
u+PTor3MkybSB/QZCegIyYTfIT1nrV9q/8bt8bulSJqATwOGxrA=
=XFYq
-END PGP SIGNATURE-



pgpCo5nkaXuPV.pgp
Description: PGP signature

Processing of mesa_24.1.1-2_source.changes

[Debian FTP Masters]

mesa_24.1.1-2_source.changes uploaded successfully to localhost
along with the files:
  mesa_24.1.1-2.dsc
  mesa_24.1.1-2.debian.tar.xz
  mesa_24.1.1-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1072941: marked as done (libgl1-mesa-dri: not multi-arch coinstallable)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 17:22:28 +
with message-id 
and subject line Bug#1072941: fixed in mesa 24.1.1-2
has caused the Debian Bug report #1072941,
regarding libgl1-mesa-dri: not multi-arch coinstallable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1072941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgl1-mesa-dri
Version: 24.1.1-1
Severity: serious
Control: block -1 by 1067699

I just had to downgrade a bunch of packages from src:mesa to version
24.1.0-2, because the installation of libllvm18:i386 failed due to a
file conflict that has been present for a few months, see #1067699.

Probably quite a few other people are going to experience the same
issue, therefore I am filing this as RC to prevent testing migration and
alert unstable users.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
--- End Message ---
--- Begin Message ---
Source: mesa
Source-Version: 24.1.1-2
Done: Timo Aaltonen 

We believe that the bug you reported is fixed in the latest version of
mesa, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1072...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated mesa package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Jun 2024 19:59:35 +0300
Source: mesa
Built-For-Profiles: noudeb
Architecture: source
Version: 24.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1072941
Changes:
 mesa (24.1.1-2) unstable; urgency=medium
 .
   * rules, control: Revert back to llvm 17. (Closes: #1072941)
Checksums-Sha1:
 e072d0673dd87fc21fe97e8f0c64f3870e157bf2 5926 mesa_24.1.1-2.dsc
 e937c0c72de1c68f4bf5e417e5ae6c0efcd3 103472 mesa_24.1.1-2.debian.tar.xz
 493f4f256b05851fa26bf8ed28d3064d390aae84 10590 mesa_24.1.1-2_source.buildinfo
Checksums-Sha256:
 3eea87f9ecf99fdf0e6f4a16b5bc40d0246f97df2d48ee88b9bc1247acaa6d37 5926 
mesa_24.1.1-2.dsc
 19e0461feda34c2883a5f2fd88f592f1568b22c001bdf37f8b634cb2c8cd39d2 103472 
mesa_24.1.1-2.debian.tar.xz
 f4844024ff404b4d73ca4846e3be27e2f3c029da26b419ef1b81b394b97fcdd0 10590 
mesa_24.1.1-2_source.buildinfo
Files:
 f9fe9f0aa79ea580d40f50913d6e8743 5926 graphics optional mesa_24.1.1-2.dsc
 6661fed4baf1baf61e6e4dd245dc9da2 103472 graphics optional 
mesa_24.1.1-2.debian.tar.xz
 9b21ca7ca0faf443852c3075d10822d1 10590 graphics optional 
mesa_24.1.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmZnMQkACgkQy3AxZaiJ
hNzMiw/8DwO+13l9Fpls7wAf7sG9lwnfrmDfJjv/aEssd1ITxV2LiZWwWh2STP5L
/9OC7J8e2GyMZ49tkwmCr8nwHyoG9PxEMcnM9Mt7WdmHSQ8681y083+ySoxBb97m
uUpepWybzoTECl+Y5u46gp1BFlYlxuriebouSBWwzbrsaTLgEw/10SEaRjrXEOLL
CXJNFeraXMF/X0NHPHadhghv4A78iBJyg0bBfb02wQsKrVvtzUvWzoF+K4iVn5is
4GPzn6BDyZBE/LIkJ0/9ddS7e27qCf7y+uzuKK7Gg3AKKw2sVlGmU1rWIilK+1Ju
XUVJyDabTdg3b4hjlEnH9arlnL4nZqcNSyNyyUgQxBRrFvq1Krbxr7UilZfkXFC/
COPkfTKtBeoItWIMy9Q4ZjDgSU5EZbXxG0ee6xi/B0JLxX5A9n8DH4smFdTk1zE5
w3HZqGVRZx4Ui/f2kCqv+KICjL1Rb7g9GZhfKJrOPuHaslz/OIyyGc5XIBVnjwIw
3pJTXHobC5xa8A/uunPsa9NN8EUxVDFA4Ze4e9se6gG1shRtI887iFboyHPTpJp9
Cqo6s4c8zLMaA049ftF0CV4Z9zxMdsNXWrNjfOl34Dt4xdiGJ9cOcKICnIYUw8yj
u+PTor3MkybSB/QZCegIyYTfIT1nrV9q/8bt8bulSJqATwOGxrA=
=XFYq
-END PGP SIGNATURE-



pgpUD0GmYMoHL.pgp
Description: PGP signature
--- End Message ---

Processed: found 1072901 in 24.1.1-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1072901 24.1.1-2
Bug #1072901 {Done: Timo Aaltonen } [mesa-opencl-icd] 
mesa-opencl-icd: Please upgrade to libclc-18/19 supporting newer GPUs
There is no source info for the package 'mesa-opencl-icd' at version '24.1.1-2' 
with architecture ''
Unable to make a source version for version '24.1.1-2'
Marked as found in versions 24.1.1-2 and reopened.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1072901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems