Source: mesa
Followup-For: Bug #1100537
X-Debbugs-Cc: s...@debian.org
Hi,
updated patch, enabling Iris/Xe drivers on both arm64 and ppc64el.
Simon
-- System Information:
Debian Release: 13.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testin
Control: tags -1 - moreinfo
On Thu, 10 Jul 2025 at 10:26:27 +0100, Simon McVittie wrote:
[ Reason ]
Avoid regressions on platforms where Vulkan works but VA-API doesn't,
notably Raspberry Pi (<https://bugs.launchpad.net/bugs/2115956>)
[ Impact ]
If Mesa is updated as requested
3 15:01:58.0 +0100
+++ gnome-remote-desktop-48.1/debian/changelog 2025-07-10 10:04:35.0 +0100
@@ -1,3 +1,17 @@
+gnome-remote-desktop (48.1-4) unstable; urgency=medium
+
+ * Team upload
+ * Upload to unstable
+
+ -- Simon McVittie Thu, 10 Jul 2025 10:04:35 +0100
+
+gnome-remote-des
On Thu, 12 Jun 2025 at 12:18:38 +0100, Simon McVittie wrote:
I haven't verified that 25.0.7 fixes this
Now confirmed: both my examples of affected games start
successfully with 25.0.7.
Thanks,
smcv
On Thu, 15 May 2025 at 01:50:47 -0400, Joseph Hayden wrote:
on my system I have been unable to play marvel rivals
I would suggest getting a Proton log for this by setting environment
variable PROTON_LOG=1 and looking for the log in ~/steam-2767030.log (see
https://github.com/ValveSoftware/Pro
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/13122
Control: tags -1 + patch fixed-upstream
On Tue, 10 Jun 2025 at 23:52:02 +0100, Simon McVittie wrote:
I think this might be caused by the gfxstream driver closing a file
descriptor that does not belong to it (as fixed
Package: mesa-vulkan-drivers
Version: 25.0.5-1
Severity: important
To reproduce:
- Reproducible in Tchia (https://steamdb.info/app/1496590/) and Apollo
Justice: Ace Attorney Trilogy (https://steamdb.info/app/2187220/),
likely also other Windows games, running under multiple versions of
Prot
Hi,
I see that there is a new version of mesa in unstable compared with
what's in trixie, fixing #1104029. This is not going to migrate to
trixie without help, because mesa is a key package.
Is this intended to get into trixie before the 13.0 release? If yes,
please open an unblock request so
Control: retitle -1 steam-libs: Cyberpunk 2077 hang when starting up
Control: severity -1 normal
On Fri, 23 May 2025 at 19:30:29 +0200, Are Mehus wrote:
After a regular update on debian testing, it was not possible to launch
Cyberpunk on Steam anymore.
Debian does not have control over the pro
On Sun, 02 Feb 2025 at 20:05:41 +0100, Ole Streicher wrote:
the build of the "giza" package currently fails in some environments
due to an issue with xvfb-run [1], which is used from debian/rules.
The problem is that the xvfb-run script only checks that Xvfb is
running (by signalling with sign
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
suc
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
chitectures that are not yet in Debian at
all (amd64/musl-linux-amd64).
> 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 fi
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
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 Thu, 20 Mar 2025 at 15:50:44 +0100, John Paul Adrian Glaubitz wrote:
On Mon, 2024-09-16 at 11:43 +0100, Simon McVittie wrote:
Expected result: either of these:
- llvmpipe exists, is used, and works
- llvmpipe doesn't exist and softpipe is automatically used instead
...
I would su
s using an Ampere
Altra, so aarch64 is also a candidate.
In principle, all 64-bit little endian machines are candidates, in
practice I'd expect it to be more limited, for example I'm doubtful if
we'll ever see one of these cards in a RISC-V machine.
Simon
OpenPGP_0xEBF67A8
patch is the minimum I need to get rendering on B580 to work on
TalosII, so that is the "works for me" configuration. Presumably we can
enable more architectures here. Not sure if i915 can maybe also be useful
as well, it refuses to configure so I've left it x86 only for now.
S
Source: mesa
Version: 25.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: armhf
User: debian...@lists.debian.org
Usertags: i386
The recent Mesa up
Package: glslang-dev
Version: 15.1.0-1
Severity: wishlist
Tags: upstream
glslang.pc provides Debian-specific pkg-config metadata so that multiple
build systems (Autotools, Meson, CMake, plain Makefiles, others?) can link
to the glslang library without needing to hard-code a complete list of the
st
On Fri, 14 Feb 2025 at 08:32:47 +0200, Timo Aaltonen wrote:
> Philippe SWARTVAGHER kirjoitti 14.2.2025 klo 0.27:
> > So I guess we could stop shipping libspirv.a
According to
https://codesearch.debian.net/search?q=-lSPIRV%5Cb&literal=0
libSPIRV.a is explicitly linked by at least retroarch and some
Control: retitle -1 xvfb-run: makes tests flaky if multiple clients connect
without -noreset
On Wed, 27 Jan 2021 at 19:50:58 +0100, Sebastien Bacher wrote:
> Le 27/01/2021 à 18:46, Marcin Owsiany a écrit :
> > My concern here is that we're effectively papering over some issue in
> > xvfb, in mult
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-x@lists.debian.org,
debian-devel-ga...@lists.debian.org
* Package name: directxshadercompiler
Version : 2024-07-31
Upstream Contact: Microsoft
* URL : https://github.com/microsoft/Dire
On Thu, 23 Jan 2025 at 13:22:20 +0200, Timo Aaltonen wrote:
> Simon McVittie kirjoitti 23.1.2025 klo 13.11:
> > Is there something blocking upload of that version?
>
> vulkan-volk needs an update
I opened a bug asking for the new version to be packaged, and it has now
been closed
Package: glslang-dev
Version: 15.0.0-1
Severity: serious
Justification: https://release.debian.org/testing/rc_policy.txt §6a
X-Debbugs-Cc: spirv-to...@packages.debian.org
Control: found -1 15.1.0-1
Control: block 1088554 by -1
It looks as though new versions of glslang and/or spirv-tools have caus
RC bug #1093365.
Timo Aaltonen writes:
> Simon McVittie kirjoitti 23.1.2025 klo 13.11:
> > Is there something blocking upload of that version?
>
> vulkan-volk needs an update, but it doesn't follow the workflow of other
> xorg-team packages, so I don't touch it.
Plea
Control: tags -1 + fixed-upstream pending
On Fri, 17 Jan 2025 at 18:54:30 +, Santiago Vila wrote:
> /<>/vulkaninfo/generated/vulkaninfo.hpp: In function
> ‘std::string VkDriverIdString(VkDriverId)’:
> /<>/vulkaninfo/generated/vulkaninfo.hpp:103:15: error:
> ‘VK_DRIVER_ID_RESERVED_27’
On Wed, 20 Nov 2024 at 08:38:40 -0500, Jeremy Bícha wrote:
> The Salsa CI build job for libadwaita-1 is failing after the recent
> upload of libadwaita-1. That upload was in part a workaround for
> https://bugs.debian.org/1085704 which is now fixed in Unstable.
…
> /usr/bin/xvfb-run: 159: cannot cr
On Thu, 07 Feb 2019 at 17:59:42 +, Thorsten Glaser wrote:
> + xvfb-run -a -e /dev/stderr -s '-screen 0 1024x768x24 -fbdir /var/tmp' --
> ctest -O ctest.log -j8 --output-on-failure
> /usr/bin/xvfb-run: 159: /usr/bin/xvfb-run: cannot create /dev/stderr:
> Permission denied
> /usr/bin/xvfb-run:
On Wed, 13 Nov 2024 at 11:13:22 +, Jessica Clarke wrote:
> Uh, I meant to refer to schroot’s new */dev/pts* behaviour. Have you
> tried the trixie/sid version? I expect you’ll see similar issues.
xorg-server_2:21.1.14-2 builds successfully for me in a trixie/sbuild
version of schroot invoked n
On Wed, 13 Nov 2024 at 10:55:59 +, Jessica Clarke wrote:
> [pbuilder? has] mounted /proc for quite a few years now similarly to how
> schroot
> recently started to, but /proc/*/fd/N has always been a little broken.
> Isn’t that also true of schroot though? I seem to recall observing the
> same
On Wed, 13 Nov 2024 at 09:55:43 +, Mark Hindley wrote:
> In version 21.1.14-2 of src:xorg-server, the new compile time Xvfb check fails
> in a pbuilder/cowbuilder chroot:
>
> sudo cowbuilder --build --basepath /var/cache/pbuilder/base-sid.cow/
> xorg-server_21.1.14-2.dsc
...
> # Check basic f
Control: tags -1 + patch
On Sun, 06 Oct 2024 at 23:15:55 +0100, Simon McVittie wrote:
> Until libunwind can be investigated and fixed (presumably by a porter?),
> I think it would be better to disable this optional feature on armhf,
> so that X11-related packages can rely on being ab
Package: xvfb
Version: 2:21.1.13-2
Severity: important
In current unstable, when xvfb-run runs Xvfb, it repeatably crashes in
libunwind on some armhf machines and with some command-line options:
see #1082659. This appears to be a regression with the recent libunwind
1.7.x upload, and is reproducib
On Sat, 05 Oct 2024 at 14:19:50 +0100, Simon McVittie wrote:
> The error message suggests that there might be a problem with the
> chroot/container, or possibly with the host /tmp being shared with it:
>
> > Bail out! libmutter-FATAL-ERROR: Failed to start X Wayland: Directory
Source: mesa
Version: 24.2.3-1
Severity: normal
Tags: upstream patch
Forwarded: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11870
Since Mesa moved from LLVM 18 to 19, running programs with the lavapipe
or llvmpipe driver logs these messages, sometimes repeatedly:
> '-avx512er' is not a reco
Control: reopen 1081192
Control: found 1081192 1:19.1.0-3
Control: affects -1 + src:mesa
On Mon, 09 Sep 2024 at 09:57:01 +, Debian Bug Tracking System wrote:
> #1081192: libllvm19: declares itself as MA: same but is not co-installable
> [...] has been closed
This bug is still present in unsta
Control: retitle -1 mesa-vulkan-drivers: Intel driver logs "FINISHME" warnings
on load
Control: reassign -1 mesa-vulkan-drivers 24.2.2-1
On Mon, 16 Sep 2024 at 18:31:05 +, brian m. carlson wrote:
> % gnome-text-editor foo.rs
> MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FI
Control: tags -1 + moreinfo
On Fri, 16 Aug 2024 at 09:08:35 +0800, wuruilong wrote:
> The loongarch architecture of llvm does not support mcjit, so don't use
> llvmpipe in loongarch at this time.
Now that Mesa supports ORCJIT, llvmpipe seems to work acceptably on loong64.
In particular, it works
Control: tags -1 + patch
On Thu, 12 Sep 2024 at 22:41:10 +0200, Aurelien Jarno wrote:
> Weston 14 is crashing with SIGSEGV a following a few tests like flowbox
> or textiter, despite the test being successful. The following tests
> fails with no display.
The attached patch (proposed upstream by J
Control: retitle -1 weston: 14.x regression: crashes during gtk4 test suite
Control: reassign -1 weston 14.0.0-1
Control: affects -1 + src:gtk4
On Thu, 12 Sep 2024 at 22:41:10 +0200, Aurelien Jarno wrote:
> On 2024-09-12 20:59, Simon McVittie wrote:
> > On Thu, 12 Sep 2024 at 11:48
Control: retitle -1 gtk4: FTBFS with weston 14: many tests fail with
--setup=wayland: Failed to open display
Control: severity -1 serious
(Please remove -ports from cc in replies, this is no longer believed to
be -ports specific)
On Thu, 12 Sep 2024 at 11:48:21 +0100, Simon McVittie wrote
On Tue, 10 Sep 2024 at 10:13:30 +0100, Simon McVittie wrote:
> I'm going to mark the 16-bit half-float
> tests to be skipped on mips64el and downgrade the severity of this bug to
> important. Anyone else is very welcome to investigate further.
Done in 4.16.0+ds-2. It's still
Source: gtk4
Version: 4.15.6+ds-1
Severity: serious
Tags: experimental ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: m...@packages.debian.org, debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el
Control: block 10795
Source: gtk4
Version: 4.14.4+ds-8
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: m...@packages.debian.org, debian-m...@lists.debian.org,
debian-powe...@lists.debian.org, debian-sp...@lists.debian.org
User: debian-m...@list
Source: mesa
Severity: important
Justification: causes FTBFS in at least src:gtk4
Tags: ftbfs
X-Debbugs-Cc: g...@packages.debian.org, debian-ri...@packages.debian.org,
debian-loonga...@packages.debian.org, debian-m...@packages.debian.org
User: debian-m...@packages.debian.org
Usertags: mips64el
Use
Source: mesa
Version: 24.2.1-3
Severity: important
Justification: FTBFS in previously working package
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org, g...@packages.debian.org,
llvm-toolchain...@packages.debian.org
Control: affects -1 + src:gtk4
g
On Tue, 23 Jul 2024 at 20:06:46 +0100, Simon McVittie wrote:
> I needed this version for a work project, so I did some draft packaging
> where libgallium.so is a new binary package mesa-libgallium,
> which libglx-mesa0, libegl-mesa0 and libgbm1 all depend on.
https://salsa.debian.org/
On Wed, 24 Jul 2024 at 18:35:54 +0800, Bo YU wrote:
> The good news is that llvmpipe support riscv64 with orcjit has been
> merged[0]!
>
> [0]: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26018
That's great news. I hope that this can be extended to other problematic
architectures li
Source: mesa
Version: 24.1.3-2
Severity: wishlist
Tags: trixie sid patch
A new upstream release candidate is available, 24.2.0~rc1.
This adds a new private library libgallium.so which is a new dependency
for libGLX_mesa.so.0, libEGL_mesa.so.0 and libgbm.so.1, and therefore
is likely to need a new
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
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 la
Control: reassign -1 xkb-data 2.35.1-1
On Sun, 09 Jun 2024 at 23:13:32 +0200, gru...@laposte.net wrote:
> XKBMODEL="pc105"
> XKBLAYOUT="fr"
> XKBVARIANT="azerty"
(and)
> $ dconf dump /org/gnome/desktop/input-sources/
> [/]
> show-all-sources=false
> sources=[('xkb', 'fr+azerty')]
> xkb-options=['l
On Sun, 09 Jun 2024 at 18:16:01 +0100, Simon McVittie wrote:
> However, the French layout in /usr/share/X11/xkb/symbols/fr says that
> pressing the 7 key (with AltGr held) sends "grave" like my UK English
> layout, and not "dead_grave" like the German layout. So if t
ibus and xkeyboard-config maintainers and debian-l10n-french cc'd in
the hope that someone understands what is happening here, because I dont
think this is actually a libglib2.0-0 bug.
On Sun, 09 Jun 2024 at 17:23:27 +0200, gru...@laposte.net wrote:
> When you did the fix that repaired most of the
Control: tags -1 + fixed-upstream
Control: block -1 by 1061616
Control: retitle 1061616 pixman: New upstream version 0.43.4
On Mon, 29 Jan 2024 at 10:23:45 +, Simon McVittie wrote:
> On Mon, 29 Jan 2024 at 05:13:59 +, Gayathri Berli wrote:
> > we found out that while
>
Control: block 1036884 by -1
On Sun, 10 Mar 2024 at 10:37:51 +0100, Aurelien Jarno wrote:
> weston fails to build in unstable since the upload of neatvnc in version
> 8.0. From my build log on amd64:
...
> | Dependency neatvnc found: NO found 0.8.0 but need: '< 0.8.0' ; matched: '>=
> 0.7.0'
Thi
Package: libneatvnc0
Version: 0.8.0+dfsg-1
Severity: important
Justification: Policy 8.6.2
Tags: upstream
X-Debbugs-Cc: wes...@packages.debian.org, way...@packages.debian.org
libneatvnc 0.8.0 removes a public function from its API/ABI:
│ -const char* nvnc_client_get_hostname(const struct nvnc_cli
Control: tags -1 + confirmed
Context for Mesa maintainers: gtk4 passed its build-time tests on
2024-01-29, but is now failing in a test rebuild. I can reproduce this,
and I think it's a regression triggered by Mesa changes (see also
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10293 upstream)
Source: vulkan-loader
Version: 1.3.268.0-1
Severity: wishlist
A new upstream release vulkan-sdk-1.3.275.0 is available.
smcv
Control: reassign -1 libpixman-1-0 0.42.2-1
Control: affects -1 + librsvg
Control: tags -1 + upstream
Control: forwarded -1 https://gitlab.freedesktop.org/pixman/pixman/-/issues/78
On Mon, 29 Jan 2024 at 05:13:59 +, Gayathri Berli wrote:
> After a lot of debugging, by upgrading librsvg and its
On Sun, 14 Jan 2024 at 08:39:52 +0100, Paul Gevers wrote:
> The Release Team considers packages that are out-of-sync between testing and
> unstable for more than 30 days as having a Release Critical bug in testing
> [1]. Your package src:mesa has been trying to migrate for 31 days [2].
> Hence, I a
Source: mesa
Version: 23.3.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: armel
Control: block 1060779 by -1
The armel baseline does not have lock
(cc -= release team, += Mesa)
On Fri, 15 Dec 2023 at 18:52:58 +0100, Aurelien Jarno wrote:
> On 2023-12-15 11:11, Simon McVittie wrote:
> > On Thu, 14 Dec 2023 at 21:59:19 +0800, Bo YU wrote:
> > > 10/12 gnome-shell:shell / perf-basic FAIL
> > &
e 6.5.10-1 kernel
in case there's something subtly different.
Thanks,
Simon
[ 7.490078] ucsi_acpi USBC000:00: ucsi_handle_connector_change:
GET_CONNECTOR_STATUS failed (-5)
[ 7.605873] ucsi_acpi USBC000:00: possible UCSI driver bug 1
[ 7.605903] ucsi_
meout timeout!
[ 1169.147619] [drm:amdgpu_dm_process_dmub_aux_transfer_sync [amdgpu]] *ERROR*
wait_for_completion_timeout timeout!
[ 1179.387933] [drm:amdgpu_dm_process_dmub_aux_transfer_sync [amdgpu]] *ERROR*
wait_for_completion_timeout timeout!
Thank you, hopefully this info is useful to someone!
request: 0x0
Serial number of failed request: 271
Current serial number in output stream: 271
The resulting file is empty. This also happens when -icmap is specified.
Simon
-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates
On Mon, 11 Sep 2023 at 19:46:07 +0300, Timo Aaltonen wrote:
> Simon McVittie kirjoitti 11.9.2023 klo 12.36:
> > I've opened a Mesa bug at wishlist severity suggesting a move to version
> > 16, and set it to block the bug for llvm-toolchain-15 removal (#1050070).
>
> The
On Sat, 19 Aug 2023 at 10:39:44 +0200, Sylvestre Ledru wrote:
> llvm-defaults has been pointing to 16 in experimental for quite sometime.
> Opening this transition to make sure it is on your radar! :)
>
> I opened bug #1050070 & #1050069 for future removals.
Mesa is a significant user of LLVM, an
Source: mesa
Version: 23.1.6-1
Severity: wishlist
X-Debbugs-Cc: llvm-toolchain...@packages.debian.org
Control: block 1050070 by -1
According to #1050071, #1050070 and #1050069, the LLVM maintainers want
to switch the default LLVM major version from 14 to 16, and remove versions
14 and 15.
Mesa cu
Package: twm
Version: 1:1.0.10-1
Severity: normal
User: xdg-desktop-por...@packages.debian.org
Usertags: portals.conf
As well as being available as a window manager to integrate into some
larger environment, TWM behaves like a very small desktop environment
in its own right, by providing a /usr/sh
Package: weston
Version: 12.0.1-1
Severity: normal
User: xdg-desktop-por...@packages.debian.org
Usertags: portals.conf
In addition to being available as a compositor that is part of
a more comprehensive desktop environment, weston behaves like
a small desktop environment in its own right, by provi
Source: mesa
Version: 23.1.4-1
Severity: normal
X-Debbugs-Cc: debian-m...@lists.debian.org, wzss...@gmail.com
User: debian-m...@lists.debian.org
Usertags: mips64el mipsel
gnome-shell (>= 44) fails its build-time tests on the mips64el porterbox
'eller', using llvmpipe for 3D graphics. I don't know
Control: tags -1 + patch
On Mon, 12 Jun 2023 at 11:59:17 +0100, Simon McVittie wrote:
> If this package only requires functionality from gdk-pixbuf-2.0.pc
> and , please update the build-dependency to
> libgdk-pixbuf-2.0-dev.
Please consider the attached patch, also available
Control: reassign -1 src:mesa 23.1.2-1
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199
On Wed, 05 Jul 2023 at 14:47:11 +0300, Timo Aaltonen wrote:
> I filed this upstream a while ago and bisected the regressing commit
> now:
>
> https://gitlab.freedesktop.org/mesa/mes
I think the problem here is more likely to be this bit:
On Thu, 29 Jun 2023 at 16:21:36 +0200, Paul Gevers wrote:
> 228s libEGL warning: failed to get driver name for fd 0
> 228s 228s libEGL warning: MESA-LOADER: failed to retrieve device information
> 228s 228s libEGL warning: failed to get drive
Source: weston
Version: 10.0.1-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf
Control: found -1 11.0.0-2
This package Build-Depends on libgdk-pixbuf2.0-dev.
In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:
- li
On Wed, 15 Mar 2023 at 14:40:27 +, Simon McVittie wrote:
> [x] attach debdiff against the package in testing
Sorry, here's the debdiff, filtered to exclude .pick_status.json (which is
used upstream to track which changes should/should not be backported).
smcv
mesa_
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: m...@packages.debian.org
Control: affects -1 + src:mesa
Control: block -1 by 1032887
Please consider unblocking package mesa.
[ Reason ]
New upstream bugfix release, fixing #1
Package: spirv-tools
Version: 2023.1-1
Severity: serious
Justification: https://release.debian.org/testing/rc_policy.txt 6a
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-Cc: debian...@lists.debian.org
Control: affects -1 + src:glslang
The test-case debian/tests/glslang-dev that I
incorporating changes from the maintainers'
+packaging repository
+
+ [ Julien Cristau ]
+ * Switch Vcs-* control fields to https.
+ * Switch xorg.freedesktop.org URLs in packaging to https.
+
+ [ Simon McVittie ]
+ * d/control: Update Vcs-* for migration to salsa.debian.org
+ * Use re
g repository
+
+ [ Julien Cristau ]
+ * Remove Cyril and David from Uploaders.
+ * Add Vcs-* control fields.
+ * Use https URL in debian/watch.
+
+ [ Simon McVittie ]
+ * d/control: Update Vcs-* for migration to salsa.debian.org
+ * Use recommended debhelper compat level 13 (Closes: #965894)
00
@@ -1,3 +1,22 @@
+xfonts-base (1:1.0.5+nmu1) unstable; urgency=medium
+
+ * Non-maintainer upload, incorporating changes from the maintainers'
+packaging repository
+
+ [ Simon McVittie ]
+ * d/rules: Add missing build-arch, build-indep targets (Policy §4.9)
+(Closes: #999177)
+ * d/
Control: severity -1 important
On Tue, 20 Dec 2022 at 11:47:10 +, Simon McVittie wrote:
> Recent uploads of mutter have had a FTBFS on armhf and sometimes armel,
> with this test failure in "mutter:core+mutter/wayland / xwayland"
In 43.2-4 I've downgraded failures i
Source: mutter
Version: 43.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: lib...@packages.debian.org, debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: armel armhf
Recent uploads of mutter have ha
Control: reassign -1 src:mesa 22.2.4-1
Control: severity -1 normal
>From what you've said about the various different drivers in use in
different modes, this looks like a Mesa issue more than a gnome-shell
issue, so I'm reassigning this. It also seems to be hardware-specific
and has a straightforw
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/7819
On Fri, 02 Dec 2022 at 12:24:00 +, Simon McVittie wrote:
> - Install a VM/chroot/container with Debian testing
> - Install the dependencies of gtk+3.0's autopkgtests
> (adwaita-icon-theme-full at-
Package: libgl1-mesa-dri
Version: 22.3.0-1
Severity: serious
Justification: FTBFS and autopkgtest regression in affected packages
To reproduce:
- Install a minimal amd64 VM with Debian testing and mesa_22.2.4-1
- apt --no-install-recommends build-dep gtk+3.0
- Build source package gtk+3.0_3.24.35
On Thu, 01 Dec 2022 at 01:11:15 +0100, Gert van de Kraats wrote:
> Recently a general upgrade was executed with gnome-shell
> upgrading from version 43.0-2 to 43.1-2.
Are you sure that the root cause was this gnome-shell upgrade, and not
an upgrade of the mesa packages that may have happened at th
Source: llvm-toolchain-15
Version: 1:15.0.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source, making mesa unbuildable
User: debian-m...@lists.debian.org
Usertags: mipsel mips64el
X-Debbugs-Cc: debian-m...@lists.debian.org, m...@packages.debian.org
Control: affects -1 + src:
Source: vulkan-loader
Version: 1.3.224.0-1
Severity: wishlist
vulkan-loader is currently at upstream version 1.3.224.0, but upstream's
sdk-1.3.224 stable branch now has a 1.3.224.1 point release with these
release notes:
> Enable layer interception of unknown functions
>
> Re-add previously rever
On Sun, 02 Oct 2022 at 17:38:12 -0700, Alex Relis wrote:
> I think it would be a good idea to bring a newer version of mesa to Debian
> Bullseye by bringing it to bullseye-backports. Here are some reasons why:
>
> 1. It reduces friction when running Debian Stable on newer hardware:
> bullseye-back
Control: reassign -1 src:mesa
Control: affects -1 + src:gtk4
On Fri, 03 Sep 2021 at 00:19:29 +0100, Simon McVittie wrote:
> GTK 4 has a new scene-graph-based rendering model, "GSK", with an OpenGL
> preferred implementation and a Cairo fallback. Its regression tests draw
> vari
Control: reassign -1 src:mesa
Control: affects -1 + src:gtk4
On Sat, 08 Jan 2022 at 18:35:20 +, Simon McVittie wrote:
> Similar to #993550, GTK 4 has a new test failure on mips*el.
> Please see https://gitlab.gnome.org/GNOME/gtk/-/issues/4618 for details.
This seems likely to be
Control: tags -1 + patch
On Tue, 19 Jul 2022 at 11:56:43 +0100, Simon McVittie wrote:
> A straightforward revert of 6bbbe15a applies cleanly to 22.1.x and
> appears to solve this.
Alternatively, upstream merge request
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17702 is waiti
On Thu, 21 Jul 2022 at 13:30:19 +0100, Simon McVittie wrote:
> I've prepared merge requests for all the xfonts-* packages (except
> xfonts-utils which contains utilities rather than fonts)
Diffs for -encodings attached. There was no bug report for the missing
build-* targets, but the
On Thu, 21 Jul 2022 at 13:30:19 +0100, Simon McVittie wrote:
> I've prepared merge requests for all the xfonts-* packages (except
> xfonts-utils which contains utilities rather than fonts)
Diffs for -scalable attached. As with -encodings, the missing build-arch
and build-indep ta
On Thu, 21 Jul 2022 at 13:30:19 +0100, Simon McVittie wrote:
> I've prepared merge requests for all the xfonts-* packages (except
> xfonts-utils which contains utilities rather than fonts)
-100dpi diffs attached.
smcv
>From bf4eb2eac34232a1ccf3ee994b48760a8f2c49ed Mon Sep 17
On Thu, 21 Jul 2022 at 13:30:19 +0100, Simon McVittie wrote:
> I've prepared merge requests for all the xfonts-* packages (except
> xfonts-utils which contains utilities rather than fonts)
Diffs for -75dpi attached.
smcv
>From 1f5a1270c484a8e7b6a1ac4be8c09379de97613b Mon Sep 17
On Thu, 21 Jul 2022 at 13:30:19 +0100, Simon McVittie wrote:
> I've prepared merge requests for all the xfonts-* packages (except
> xfonts-utils which contains utilities rather than fonts) fixing the
> missing targets required by Policy §4.9
Here are diffs for xfonts-cyrilli
1 - 100 of 371 matches
Mail list logo