Bug#1071222: marked as done (mesa: FTBFS due to missing build dependency python3-pycparser)
Your message dated Fri, 31 May 2024 13:05:43 +
with message-id
and subject line Bug#1071222: fixed in mesa 24.1.0-2
has caused the Debian Bug report #1071222,
regarding mesa: FTBFS due to missing build dependency python3-pycparser
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.)
--
1071222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mesa
Version: 24.1.0~rc3-1
Severity: minor
Tags: ftbfs
Dear Maintainer,
On my local machine, mesa FTBFS unless I install python3-pycparser:
Running command: /usr/bin/python3 -c '
try:
from packaging.version import Version
except:
from distutils.version import StrictVersion as Version
import pycparser
assert Version(pycparser.__version__) >= Version("2.20")
'
--- stdout ---
--- stderr ---
Traceback (most recent call last):
File "", line 6, in
ModuleNotFoundError: No module named 'pycparser'
../src/etnaviv/hwdb/meson.build:17:2: ERROR: Problem encountered: Python
(3.x) pycparser module >= 2.20 required to build mesa.
It seems to install the dependency and build fine on Debian buildd, so
marking the bug as minor. Since this package seems to be a direct
dependency for the etnaviv hwdb bits, I think we should add
python3-pycparser as a direct build depends.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.12-amd64 (SMP w/16 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
--- End Message ---
--- Begin Message ---
Source: mesa
Source-Version: 24.1.0-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 1071...@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: Fri, 31 May 2024 15:40:01 +0300
Source: mesa
Built-For-Profiles: noudeb
Architecture: source
Version: 24.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force
Changed-By: Timo Aaltonen
Closes: 1071222
Changes:
mesa (24.1.0-2) unstable; urgency=medium
.
* Upload to unstable.
* control: Add python3-pycparser to build-depends for armhf, arm64.
(Closes: #1071222)
Checksums-Sha1:
4b2631a37ac18b397c5c12d820ea7f3eb00b8654 5926 mesa_24.1.0-2.dsc
7398a8f43330bfee7a6403f3c513b9b86bf17f8d 103372 mesa_24.1.0-2.debian.tar.xz
d8373bfa6d75be852fa22ff784b001c6b68a2037 10590 mesa_24.1.0-2_source.buildinfo
Checksums-Sha256:
a50782453d68476077b5731b7e9d302e36122f66427b20ad0c0a7ea6c3d01733 5926
mesa_24.1.0-2.dsc
ac0ff8b299752dd523e37f53674dfff4bd18af3ee3362a08dce0bab28362154c 103372
mesa_24.1.0-2.debian.tar.xz
b5ec971341f2eca61cd23b8a6267029d55c80464c27b6146577ea0b11ca8f735 10590
mesa_24.1.0-2_source.buildinfo
Files:
75b4bf7586a3585e13042d95df657a9c 5926 graphics optional mesa_24.1.0-2.dsc
4d55827e68df64d5960583367006bb6a 103372 graphics optional
mesa_24.1.0-2.debian.tar.xz
4d026822f5b7e0d71fb9af3d47c82247 10590 graphics optional
mesa_24.1.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmZZxYYACgkQy3AxZaiJ
hNwKmRAAr1b+v6FGzzzp7gTvJWWgG/5tV6zTKuTI7VeaX+wEAiYN2k0eC+j2kpOm
MhOA5tSMmFSgfJY3KygYDBG/VD3UPNKrM6oZtZVsIUFELVABll4LbZPlUKnPLi5V
3wUzP7oUhpquM7cCB533gGEPK5Qs8xiOJTfI5N685TJ24rnHNfizbHWIpBxf1jiL
U9Bbr5n/SUIIqWuP8YAx+a0RZVypArCMvPwnY1lxCVd9b2gig9Htaqg8Tou2X0A9
xL1IjKi6YA3GHFsUi88oSdc0yFA/311C29dir4f9gcT60IQeoX/ir6p/gSlMsLtW
srXsGZYyiLhbmTGC0Nh6ZpkPgsSeMpQ5s9WbzGwwR2b8dU4xc0RdKXwcGrfYovrc
Izs3XO2Hcgwy8myKMWJarYBjLZek7hKMu5RVdchbfNdYurm4oKCUOOSyK1R3avmE
RqsSJC9iWwcozdkEWzitgJ8dmFk7jfMVDNt806xoUFf9WqsBSj6torKhxvnKhBS8
x4qKUK3CksE+FQ9AI0fUwQDeUagLhrYXJK0S9x
Bug#907152: marked as done (vulkan: Porting to non-linux systems)
Your message dated Thu, 30 May 2024 08:35:31 +
with message-id
and subject line Bug#907152: fixed in vulkan-loader 1.3.283.0-1
has caused the Debian Bug report #907152,
regarding vulkan: Porting to non-linux systems
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.)
--
907152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vulkan
Version: 1.1.73+dfsg-1
Severity: important
Tags: ftbfs, patch
User: debian-h...@lists.debian.org, debian-k...@lists.debian.org
Usertags: hurd-i386, kfreebsd-any
Hello,
Currently vulkan is not available on GNU/Hurd and GNU/kFreeBSD due to
lack of porting to these architectures. Attached is a patch,
debian_control.diff, to make the libwayland-dev dependency linux-only
and add hurd, kfreebsd to the Architecture field of the packages.
The remaining patches:
CMakeLists.txt.diff
demos_CMakeLists.txt.diff
demos_smoke_CMakeLists.txt.diff
external_glslang_External_spirv-tools_CMakeLists.txt.diff
icd_CMakeLists.txt.diff
layers_CMakeLists.txt.diff
loader_CMakeLists.txt.diff
loader_loader.c.diff
loader_vk_loader_platform.h.diff
tests_CMakeLists.txt.diff
are mainly patches for various CMakeLists.txt files. The last patch is
not tested yet since the package build does not run tests.
Vulkan has been built successfully with the attached patches on hurd-
i386 and kfreebsd-amd64 boxes.
This package is important to have available due to the build dependency
chain of wine-development:
wine-development -> libvkd3d-dev -> libvulkan-dev
Thanks!--- a/debian/control 2018-08-22 07:52:50.0 +0200
+++ b/debian/control 2018-08-22 08:03:31.0 +0200
@@ -4,7 +4,7 @@
Uploaders: Timo Aaltonen
Build-Depends: debhelper (>= 9),
cmake,
- libwayland-dev,
+ libwayland-dev [linux-any],
libx11-dev,
libxcb1-dev,
libxrandr-dev,
@@ -20,7 +20,7 @@
Vcs-Browser: https://salsa.debian.org/xorg-team/vulkan/vulkan.git
Package: libvulkan1
-Architecture: linux-any
+Architecture: linux-any kfreebsd-any hurd-any
Depends: ${shlibs:Depends}, ${misc:Depends}
Breaks: vulkan-loader,
libvulkan-dev (<< 1.1.70+dfsg1-2),
@@ -37,7 +37,7 @@
Package: libvulkan-dev
Section: libdevel
-Architecture: linux-any
+Architecture: linux-any kfreebsd-any hurd-any
Depends:
libvulkan1 (= ${binary:Version}),
${misc:Depends},
@@ -53,7 +53,7 @@
This package includes files needed for development.
Package: vulkan-utils
-Architecture: linux-any
+Architecture: linux-any kfreebsd-any hurd-any
Section: graphics
Depends: ${shlibs:Depends}, ${misc:Depends},
libvulkan1,
Index: vulkan-1.1.73+dfsg/demos/CMakeLists.txt
===
--- vulkan-1.1.73+dfsg.orig/demos/CMakeLists.txt
+++ vulkan-1.1.73+dfsg/demos/CMakeLists.txt
@@ -73,7 +73,71 @@ elseif(CMAKE_SYSTEM_NAME STREQUAL "Linux
include_directories ("${PROJECT_SOURCE_DIR}/icd/common")
link_libraries(${API_LOWERCASE} m)
elseif(CMAKE_SYSTEM_NAME STREQUAL "Darwin")
-add_definitions(-DVK_USE_PLATFORM_MACOS_MVK)
+add_definitions(-DVK_USE_PLATFORM_XCB_KHR)
+elseif(CMAKE_SYSTEM_NAME STREQUAL "kFreeBSD")
+if (NOT DEMOS_WSI_SELECTION)
+set(DEMOS_WSI_SELECTION "XCB")
+endif()
+
+if (DEMOS_WSI_SELECTION STREQUAL "XCB")
+if (NOT BUILD_WSI_XCB_SUPPORT)
+message( FATAL_ERROR "Selected XCB for demos build but not building Xcb support" )
+endif()
+set(DEMO_INCLUDE_DIRS
+${XCB_INCLUDE_DIRS}
+${DEMO_INCLUDE_DIRS}
+)
+link_libraries(${XCB_LIBRARIES})
+add_definitions(-DVK_USE_PLATFORM_XCB_KHR)
+elseif(DEMOS_WSI_SELECTION STREQUAL "XLIB")
+if (NOT BUILD_WSI_XLIB_SUPPORT)
+message( FATAL_ERROR "Selected XLIB for demos build but not building Xlib support" )
+endif()
+set(DEMO_INCLUDE_DIRS
+${X11_INCLUDE_DIR}
+${DEMO_INCLUDE_DIRS}
+)
+link_libraries(${X11_LIBRARIES})
+add_definitions(-DVK_USE_PLATFORM_XLIB_KHR)
+elseif(DEMOS_WSI_SELECTION STREQUAL "DISPLAY")
+add_definitions(-DVK_USE_PLATFORM_DISPLAY_KHR)
+else()
+message( FATAL_ERROR "Unrecognized value for DEMOS_WSI_SELECTION: ${DEMOS_WSI_SELECTION}" )
+ endif()
+include_directories ("${PROJECT_SOURCE_DIR}/icd/common")
+link_libraries(${API_LOWERCASE} m)
+elseif(CMAKE_SYSTEM_NAME STREQUAL "GN
Processed: xdm: diff for NMU version 1:1.1.11-3.1
Processing control commands: > tags 1063693 + pending Bug #1063693 [src:xdm] xdm: move systemd unit to /usr (DEP17) Added tag(s) pending. -- 1063693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: raise remaining usrmerge normal bugs to important
054191 1055514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055514 1061238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061238 1061245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061245 1061248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061248 1061259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061259 1061332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061332 1061337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061337 1061342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061342 1061352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061352 1061353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061353 1061489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061489 1061491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061491 1061527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061527 1061702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061702 1061849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061849 1061851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061851 1061855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061855 1061865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061865 1063455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063455 1063458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063458 1063552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063552 1063571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063571 1063572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063572 1063620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063620 1063622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063622 1063692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063692 1063693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063693 1063694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063694 1063696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063696 1063699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063699 1063876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063876 1063878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063878 1064045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064045 1064046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064046 1064125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064125 1064126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064126 1064237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064237 1064238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064238 1064299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064299 1064315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064315 1064316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064316 1064396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064396 1064400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064400 1064408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064408 1064430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064430 1064449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064449 1064459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064459 1064887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064887 1064888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064888 1071119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: more usrmerge bugs to important
Processing commands for cont...@bugs.debian.org: > severity 1063693 important Bug #1063693 [src:xdm] xdm: move systemd unit to /usr (DEP17) Severity set to 'important' from 'normal' > severity 1063572 important Bug #1063572 [jfsutils] jfsutils: move files to /usr (DEP17) Severity set to 'important' from 'normal' > severity 1051460 important Bug #1051460 [src:crowdsec-custom-bouncer] crowdsec-custom-bouncer: move systemd units to /usr Severity set to 'important' from 'wishlist' > severity 1054013 important Bug #1054013 [src:dnssec-trigger] dnssec-trigger: defer location of systemd units to systemd.pc Severity set to 'important' from 'normal' > severity 1054084 important Bug #1054084 [src:crowdsec] let dh_installsystemd choose the location of systemd units Severity set to 'important' from 'normal' > severity 1054086 important Bug #1054086 [src:lsm] lsm: let dh_installsystemd choose the location of units Severity set to 'important' from 'normal' > severity 1054088 important Bug #1054088 [src:sanoid] sanoid: let dh_installsystemd choose the location of units Severity set to 'important' from 'normal' > severity 1054089 important Bug #1054089 [src:php-defaults] php-common: let dh_installsystemd choose the location of units Severity set to 'important' from 'normal' > severity 1054090 important Bug #1054090 [src:zram-tools] zram-tools: let dh_installsystemd choose the location of the unit Severity set to 'important' from 'normal' > severity 1054093 important Bug #1054093 [src:monit] monit: let dh_installsystemd choose the location of units Severity set to 'important' from 'normal' > severity 1054191 important Bug #1054191 [src:memlockd] memlockd: installs an empty /lib/systemd/system once dh_installsystemd installs to /usr Severity set to 'important' from 'normal' > severity 1064449 important Bug #1064449 [open-infrastructure-system-build] open-infrastructure-system-build: ineffective diversions due to /usr-move (DEP17) Severity set to 'important' from 'normal' > severity 1063455 important Bug #1063455 [open-infrastructure-compute-tools] open-infrastructure-compute-tools: move files to /usr for DEP17 Severity set to 'important' from 'normal' > severity 1063458 important Bug #1063458 [open-infrastructure-storage-tools] open-infrastructure-storage-tools: move files to /usr for DEP17 Severity set to 'important' from 'normal' > severity 1067817 important Bug #1067817 [libfuse2t64] libfuse2: move library to /usr (DEP17 P1) Ignoring request to change severity of Bug 1067817 to the same value. > severity 1063878 important Bug #1063878 [di-utils] di-utils: chroot-setup.sh creates ineffective diversions (DEP17) Severity set to 'important' from 'normal' > severity 1064408 important Bug #1064408 [live-build] [PATCH] duplicate aliased diversions for DEP17 Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1051460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051460 1054013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054013 1054084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054084 1054086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054086 1054088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054088 1054089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054089 1054090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054090 1054093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054093 1054191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054191 1063455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063455 1063458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063458 1063572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063572 1063693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063693 1063878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063878 1064408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064408 1064449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064449 1067817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036177: marked as done (glslang: please consider upgrading to 3.0 source format)
Your message dated Wed, 29 May 2024 20:10:09 +0200 with message-id <6a3b3639-d649-4728-ba93-a07072065...@gmx.fr> and subject line glslang: please consider upgrading to 3.0 source format -- done has caused the Debian Bug report #1036177, regarding glslang: please consider upgrading to 3.0 source format 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.) -- 1036177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glslang Version: 12.0.0-2 Severity: wishlist Please switch to the 3.0 (quilt) source format. --- End Message --- --- Begin Message --- Control: fixed -1 14.2.0-1 The package has been upgraded to 3.0 source format in version 14.2.0-1 (https://salsa.debian.org/xorg-team/vulkan/glslang/-/commit/0502d46e1dba4028caa0680897a2bce93a28) (I forgot the Closes tag in d/changelog, sorry...) Philippe.--- End Message ---
Processed: closing 1070440
Processing commands for cont...@bugs.debian.org: > close 1070440 Bug #1070440 [mesa-va-drivers] mesa-va-drivers: vaapi cannot find target for triple amdgcn Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1070440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: glslang breaks shaderc autopkgtest: undefined reference: ABI breakage??
Processing control commands: > found -1 glslang/14.2.0-1 Bug #1072110 [src:glslang, src:shaderc] glslang breaks shaderc autopkgtest: undefined reference: ABI breakage?? Marked as found in versions glslang/14.2.0-1. > found -1 shaderc/2023.2-1 Bug #1072110 [src:glslang, src:shaderc] glslang breaks shaderc autopkgtest: undefined reference: ABI breakage?? Marked as found in versions shaderc/2023.2-1. -- 1072110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1062799: marked as done (glslang-dev: Missing libraries listed in glslang.pc)
Your message dated Tue, 28 May 2024 10:04:26 +
with message-id
and subject line Bug#1062799: fixed in glslang 14.2.0-1
has caused the Debian Bug report #1062799,
regarding glslang-dev: Missing libraries listed in glslang.pc
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.)
--
1062799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glslang-dev
Version: 14.0.0-1
Severity: serious
Dear Maintainer,
pkgconf --libs return :
,
| $ pkgconf --libs glslang
| -lglslang -lMachineIndependent -lOSDependent -lHLSL -lOGLCompiler
-lGenericCodeGen -lSPVRemapper -lpthread
`
But -lHLSL and -lOGLCompiler are not available in Debian and packages
fail to build (ffmpeg).
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.2-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages glslang-dev depends on:
ii spirv-tools 2023.6~rc1-1
glslang-dev recommends no packages.
Versions of packages glslang-dev suggests:
pn glslang-tools
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glslang
Source-Version: 14.2.0-1
Done: Timo Aaltonen
We believe that the bug you reported is fixed in the latest version of
glslang, 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 1062...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Timo Aaltonen (supplier of updated glslang 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: Tue, 28 May 2024 12:42:40 +0300
Source: glslang
Built-For-Profiles: noudeb
Architecture: source
Version: 14.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force
Changed-By: Timo Aaltonen
Closes: 1062799
Changes:
glslang (14.2.0-1) unstable; urgency=medium
.
[ Timo Aaltonen ]
* New upstream release.
.
[ Philippe SWARTVAGHER ]
* Convert d/source/format to "3.0 (quilt)"
* Build-Depends on pkgconf instead of pkg-config
* Remove spurious ${shlibs:Depends} from Depends of glslang-dev
* Do not use dpkg-parsechangelog in d/rules, as suggested by Lintian
* Bump Standards-Version to 4.7.0: no change needed
* Build with hardening=+all
* Rename overridden lintian tag binary-without-manpage to no-manual-page
* Add 'Rules-Requires-Root: no' to d/control
* Add a patch to fix few typos
* Add d/upstream/metadata
* Fix linking glslang and spirv. Closes: #1062799
Checksums-Sha1:
f06085930900c509e0d12bb6d0684af2dd0edb48 2127 glslang_14.2.0-1.dsc
2e6a034ce2fc57ab7abd297e433db9e4dae0a72a 3842427 glslang_14.2.0.orig.tar.gz
7fad9d129364fea9a14b475b637e7a1019f967ab 15184 glslang_14.2.0-1.debian.tar.xz
8d30cdd230b2638d7f2b82e926c263950c621d39 8871 glslang_14.2.0-1_source.buildinfo
Checksums-Sha256:
85b816431c8c2b77e0f1a5fb96ae4d8768a62e7bbb3853d681a4f8ba1d5537d8 2127
glslang_14.2.0-1.dsc
14a2edbb509cb3e51a9a53e3f5e435dbf5971604b4b833e63e6076e8c0a997b5 3842427
glslang_14.2.0.orig.tar.gz
73c0d9a89ba243a48ab8126a88c6dc3419e0bc2502001fc349bb8ad8ba0473b8 15184
glslang_14.2.0-1.debian.tar.xz
13546069922a1f4369f43a255682bce2c43fc3b1c1db7733a5264ef5691df499 8871
glslang_14.2.0-1_source.buildinfo
Files:
eed9fad061ffba63756ba07252add233 2127 libdevel optional glslang_14.2.0-1.dsc
876ae2fdff34ef549e23208dfa075f0b 3842427 libdevel optional
glslang_14.2.0.orig.tar.gz
79fe79ad69c37e155596ab49b47ebf8d 15184 libdevel optional
glslang_14.2.0-1.debian.tar.xz
d51cd5693d3dc402b28111c7c41a0e7b 8871 libdevel optional
glslang_14.2.0-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmZVp+oACgkQy3AxZaiJ
hNwNOA//Xg1kuzAP0tLAoY45V8KozaLTdwhyuyaZmRqSJXlOcu25ZTZoqiVIA19y
k4z9w5C+Kdmqa30i52hkIiR4Tj
Bug#981656: marked as done (libxcb: reduce Build-Depends)
Your message dated Tue, 21 May 2024 09:19:49 + with message-id and subject line Bug#981656: fixed in libxcb 1.17.0-2 has caused the Debian Bug report #981656, regarding libxcb: reduce Build-Depends 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.) -- 981656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxcb Version: 1.14-3 Tags: patch User: helm...@debian.org Usertags: rebootstrap libxcb participates in dependency loops relevant to architecture bootstrap. Instead of looking into such a difficult problem, I looked into easily droppable dependencies and found thre. * pthread-stubs are only required on non-linux architectures. I propose annotating it [!linux-any]. * xsltproc is only used for rendering test results. I propose annotating it . * dctrl-tools is entirely unused. I propose dropping it. Please consider applying the attached patch. Helmut diff -u libxcb-1.14/debian/changelog libxcb-1.14/debian/changelog --- libxcb-1.14/debian/changelog +++ libxcb-1.14/debian/changelog @@ -1,3 +1,14 @@ +libxcb (1.14-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Reduce Build-Depends: (Closes: #-1) ++ pthread-stubs are only required on non-linux architectures. Annotate + [!linux-any]. ++ xsltproc is only used for rendering test results. Annotate . ++ dctrl-tools is entirely unused. Drop it. + + -- Helmut Grohne Tue, 02 Feb 2021 15:09:54 +0100 + libxcb (1.14-3) unstable; urgency=high * tests: don't use deprecated fail_unless check API (closes: #980602). diff -u libxcb-1.14/debian/control libxcb-1.14/debian/control --- libxcb-1.14/debian/control +++ libxcb-1.14/debian/control @@ -9,17 +9,16 @@ libxdmcp-dev (>= 1:1.0.3-2), xcb-proto (>= 1.14), xcb-proto (<< 2.0), - libpthread-stubs0-dev (>= 0.1), + libpthread-stubs0-dev (>= 0.1) [!linux-any], debhelper-compat (= 12), pkg-config, xutils-dev, - xsltproc (>= 1.1.19), + xsltproc (>= 1.1.19) , check (>= 0.9.4-2) , python3-xcbgen (>= 1.14), libtool, automake, python3:native, - dctrl-tools Build-Depends-Indep: # libxcb-doc doxygen, --- End Message --- --- Begin Message --- Source: libxcb Source-Version: 1.17.0-2 Done: Emilio Pozuelo Monfort We believe that the bug you reported is fixed in the latest version of libxcb, 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 981...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emilio Pozuelo Monfort (supplier of updated libxcb 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: SHA256 Format: 1.8 Date: Tue, 21 May 2024 10:46:46 +0200 Source: libxcb Architecture: source Version: 1.17.0-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Emilio Pozuelo Monfort Closes: 981656 1024938 1069408 Changes: libxcb (1.17.0-2) unstable; urgency=medium . [ Aurélien COUDERC ] * Add missing dependency from libxcb-present-dev on libxcb-dri3-dev. (Closes: #1069408) . [ Helmut Grohne ] * Reduce Build-Depends: (Closes: #981656) + pthread-stubs are only required on non-linux architectures. Annotate [!linux-any]. + xsltproc is only used for rendering test results. Annotate . + dctrl-tools is entirely unused. Drop it. * Support the noudeb build profile. (Closes: #1024938) . [ Emilio Pozuelo Monfort ] * Also annotate libpthread-stubs0-dev dependency for libxcb1-dev. * Build-depend on pkgconf instead of pkg-config. Checksums-Sha1: a4c891dace6227bdd9663f24161ddf57cb1c4706 5318 libxcb_1.17.0-2.dsc 220ec81181bcd8bf5a8367610858673e8de6e705 661593 libxcb_1.17.0.orig.tar.gz 365b0f86925e0bb58f8ea27a6090a12d0278c516 28069 libxcb_1.17.0-2.diff.gz c144ddd8055db80be465947cc9a16a66af42cfc3 6708 libxcb_1.17.0-2_source.buildinfo Checksums-Sha256: b2728d156f79d2e757e7378cfcefca52bd570739d2efffa87e1aaeaf4f21de3a 5318 libxcb_1.17.0-2.dsc 2c69287424c9e2128cb47ffe92171e10417041ec2963bceafb65cb3fcf8f0b85 661593 libxcb_1.17.0.orig.tar.gz c5b33b67a61d0d1c1b624bf88a8150f4be1ba9b46e855e38f03a8f73858af558
Bug#1069408: marked as done (libxcb-present-dev 1.17 misses dependency on libxcb-dri3-dev)
Your message dated Tue, 21 May 2024 09:19:49 + with message-id and subject line Bug#1069408: fixed in libxcb 1.17.0-2 has caused the Debian Bug report #1069408, regarding libxcb-present-dev 1.17 misses dependency on libxcb-dri3-dev 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.) -- 1069408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kwin Version: 4:5.27.10-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > cd /<>/obj-aarch64-linux-gnu/src && /usr/bin/c++ > -DCMS_NO_REGISTER_KEYWORD=1 -DEGL_NO_PLATFORM_SPECIFIC_TYPES -DEGL_NO_X11 > -DKCOREADDONS_LIB -DMESA_EGL_NO_X11_HEADERS -DQT_CONCURRENT_LIB -DQT_CORE_LIB > -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB -DQT_NETWORK_LIB > -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_KEYWORDS > -DQT_NO_URL_CAST_FROM_STRING -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB > -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB > -DQT_XKBCOMMON_SUPPORT_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE > -Dkwin_EXPORTS -I/<>/obj-aarch64-linux-gnu/src > -I/<>/src > -I/<>/obj-aarch64-linux-gnu/src/kwin_autogen/include > -I/<>/src/colors -I/<>/src/platformsupport > -I/<>/src/tabbox -I/<>/src/effects > -I/<>/src/libkwineffects > -I/<>/obj-aarch64-linux-gnu/src/wayland > -I/<>/obj-aarch64-linux-gnu/src/libkwineffects > -I/<>/src/platformsupport/scenes/qpainter > -I/<>/src/platformsupport/scenes/opengl > -I/<>/src/platformsupport/vsyncconvenience -isystem > /usr/include/KF5/KConfig -isystem /usr/include/KF5/KConfigCore -isystem > /usr/include/KF5 -isystem /usr/include/aarch64-linux-gnu/qt5 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtCore -isystem > /usr/lib/aarch64-linux-gnu/qt5/mkspecs/linux-g++ -isystem > /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KWindowSystem -isystem > /usr/include/aarch64-linux-gnu/qt5/QtGui -isystem > /usr/include/aarch64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/aarch64-linux-gnu/qt5/QtConcurrent -isystem > /usr/include/aarch64-linux-gnu/qt5/QtDBus -isystem > /usr/include/aarch64-linux-gnu/qt5/QtQuick -isystem > /usr/include/aarch64-linux-gnu/qt5/QtQmlModels -isystem > /usr/include/aarch64-linux-gnu/qt5/QtQml -isystem > /usr/include/aarch64-linux-gnu/qt5/QtNetwork -isystem > /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KWidgetsAddons > -isystem /usr/include/KF5/KConfigGui -isystem > /usr/include/aarch64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KCodecs > -isystem /usr/include/KF5/KAuthWidgets -isystem /usr/include/KF5/KAuthCore > -isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KCrash -isystem > /usr/include/KF5/KGlobalAccel -isystem > /usr/include/aarch64-linux-gnu/qt5/QtX11Extras -isystem > /usr/include/KF5/KI18n -isystem /usr/include/KF5/KPackage -isystem > /usr/include/KF5/KService -isystem /usr/include/KDecoration2 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtXkbCommonSupport/5.15.10 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtXkbCommonSupport/5.15.10/QtXkbCommonSupport > -isystem /usr/include/aarch64-linux-gnu/qt5/QtXkbCommonSupport -isystem > /usr/include/aarch64-linux-gnu/qt5/QtGui/5.15.10 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtGui/5.15.10/QtGui -isystem > /usr/include/aarch64-linux-gnu/qt5/QtCore/5.15.10 -isystem > /usr/include/aarch64-linux-gnu/qt5/QtCore/5.15.10/QtCore -isystem > /usr/include/KF5/KNotifications -isystem /usr/include/libdrm -isystem > /usr/include/KF5/KWayland -isystem /usr/include/KF5/KActivities -isystem > /usr/include/KScreenLocker -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -mbranch-protection=standard -Wdate-time > -D_FORTIFY_SOURCE=2 -fno-operator-names -fno-exceptions -Wall -Wextra > -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long > -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual > -Werror=return-type -Werror=init-self -Wvla -Wdate-time -Wsuggest-override > -Wlogical-op -std=gnu++20 -f
Bug#1024938: marked as done (libxcb: support the noudeb build profile)
Your message dated Tue, 21 May 2024 09:19:49 +
with message-id
and subject line Bug#1024938: fixed in libxcb 1.17.0-2
has caused the Debian Bug report #1024938,
regarding libxcb: support the noudeb build profile
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.)
--
1024938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxcb
Version: 1.15-1
Severity: minor
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
libxcb builds a udeb package. It would be nice to be able to opt out of
building it via the noudeb build profile. I'm attaching a patch for your
convenience.
Helmut
diff -u libxcb-1.15/debian/changelog libxcb-1.15/debian/changelog
--- libxcb-1.15/debian/changelog
+++ libxcb-1.15/debian/changelog
@@ -1,3 +1,10 @@
+libxcb (1.15-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Support the noudeb build profile. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 27 Nov 2022 20:37:46 +0100
+
libxcb (1.15-1) unstable; urgency=medium
* New upstream release.
diff -u libxcb-1.15/debian/control libxcb-1.15/debian/control
--- libxcb-1.15/debian/control
+++ libxcb-1.15/debian/control
@@ -54,6 +54,7 @@
Package: libxcb1-udeb
Package-Type: udeb
+Build-Profiles:
Section: debian-installer
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
--- End Message ---
--- Begin Message ---
Source: libxcb
Source-Version: 1.17.0-2
Done: Emilio Pozuelo Monfort
We believe that the bug you reported is fixed in the latest version of
libxcb, 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 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort (supplier of updated libxcb 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: SHA256
Format: 1.8
Date: Tue, 21 May 2024 10:46:46 +0200
Source: libxcb
Architecture: source
Version: 1.17.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force
Changed-By: Emilio Pozuelo Monfort
Closes: 981656 1024938 1069408
Changes:
libxcb (1.17.0-2) unstable; urgency=medium
.
[ Aurélien COUDERC ]
* Add missing dependency from libxcb-present-dev on libxcb-dri3-dev.
(Closes: #1069408)
.
[ Helmut Grohne ]
* Reduce Build-Depends: (Closes: #981656)
+ pthread-stubs are only required on non-linux architectures. Annotate
[!linux-any].
+ xsltproc is only used for rendering test results. Annotate .
+ dctrl-tools is entirely unused. Drop it.
* Support the noudeb build profile. (Closes: #1024938)
.
[ Emilio Pozuelo Monfort ]
* Also annotate libpthread-stubs0-dev dependency for libxcb1-dev.
* Build-depend on pkgconf instead of pkg-config.
Checksums-Sha1:
a4c891dace6227bdd9663f24161ddf57cb1c4706 5318 libxcb_1.17.0-2.dsc
220ec81181bcd8bf5a8367610858673e8de6e705 661593 libxcb_1.17.0.orig.tar.gz
365b0f86925e0bb58f8ea27a6090a12d0278c516 28069 libxcb_1.17.0-2.diff.gz
c144ddd8055db80be465947cc9a16a66af42cfc3 6708 libxcb_1.17.0-2_source.buildinfo
Checksums-Sha256:
b2728d156f79d2e757e7378cfcefca52bd570739d2efffa87e1aaeaf4f21de3a 5318
libxcb_1.17.0-2.dsc
2c69287424c9e2128cb47ffe92171e10417041ec2963bceafb65cb3fcf8f0b85 661593
libxcb_1.17.0.orig.tar.gz
c5b33b67a61d0d1c1b624bf88a8150f4be1ba9b46e855e38f03a8f73858af558 28069
libxcb_1.17.0-2.diff.gz
23926007c32a7c63e42b9038a822be6261a074f6fbe44e55f0b8480820f4e0f8 6708
libxcb_1.17.0-2_source.buildinfo
Files:
cb126bf126298d1bc94833e51c3b9ff5 5318 libdevel optional libxcb_1.17.0-2.dsc
186c67e4fdc867dd7372f04b4dfa7c03 661593 libdevel optional
libxcb_1.17.0.orig.tar.gz
ac9e4b4c051a32f274de9a97ed21e212 28069 libdevel optional
libxcb_1.17.0-2.diff.gz
2cef38933d5cf75f9ac542bb22435293 6708 libdevel optional
libxcb_1.17.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEcJymx+vmJZxd92Q+nUbEiOQ2gwIFAmZMYY0ACgkQnUbEiOQ2
gwJokg//QyqJFkW+uWpogq93bwDJXIIcm38SwHPLeVnOzeujBRh76TmNDNAyTBAW
vATNu3kJrp1xSZxQkewuXWOG6uVCg4lH24mPlzcvkXK7vEJNy15LpsoCd/ct5b51
P/IyO5SxWf4dpoKGrcZtFsN1z7Td8K+BNgv4Lza8pUoe5TrxP2EVYZQAkxDm8v+G
2afAwLsu0Y07uxR/I48K8B0qyDwlpuGXHrG91UBtrNkuNhMTbl
Bug#1069382: marked as done (libxcb: FTBFS on arm64: KeyError: 'xcb_redirect_t')
Your message dated Tue, 21 May 2024 10:07:46 +0200 with message-id <826b7d28-4766-4e0e-9274-1a00d1f18...@debian.org> and subject line Re: Bug#1069382: libxcb: FTBFS on arm64: KeyError: 'xcb_redirect_t' has caused the Debian Bug report #1069382, regarding libxcb: FTBFS on arm64: KeyError: 'xcb_redirect_t' 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.) -- 1069382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxcb Version: 1.15-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build/src' > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/xproto.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/bigreq.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/xc_misc.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/composite.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/damage.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/dpms.xml > Traceback (most recent call last): > File "/<>/build/src/../../src/c_client.py", line 3394, in > > module.generate() > File "/usr/lib/python3/dist-packages/xcbgen/state.py", line 131, in generate > item.out(name) > File "/<>/build/src/../../src/c_client.py", line 3198, in > c_request > _c_request_helper(self, name, void=True, regular=False) > File "/<>/build/src/../../src/c_client.py", line 2273, in > _c_request_helper > if namecount[tname] > 1: >~^^^ > KeyError: 'xcb_redirect_t' > make[2]: *** [Makefile:1408: composite.c] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/04/20/libxcb_1.15-1_unstable-arm64.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- On 19/05/2024 04:45, Shmerl wrote: Is there any way to fix or work around this? It's been blocking new version of obs-studio from entering testing for a while. I don't understand, we've had libxcb 1.17-1 in sid for a while and that built properly on arm64. Your problem with obs-studio is that libxcb is not migrating due to #1069408, not because of this bug. I'm closing this one since libxcb now builds fine on arm64. Cheers, Emilio--- End Message ---
Bug#1036176: marked as done (mesa: please consider upgrading to 3.0 source format)
Your message dated Fri, 10 May 2024 07:34:57 + with message-id and subject line Bug#1036176: fixed in mesa 24.0.7-1 has caused the Debian Bug report #1036176, regarding mesa: please consider upgrading to 3.0 source format 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.) -- 1036176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa Version: 22.3.6-1+deb12u1 Severity: wishlist Please switch xss-lock to the 3.0 (quilt) source format. --- End Message --- --- Begin Message --- Source: mesa Source-Version: 24.0.7-1 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 1036...@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: Fri, 10 May 2024 10:18:58 +0300 Source: mesa Built-For-Profiles: noudeb Architecture: source Version: 24.0.7-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1036176 Changes: mesa (24.0.7-1) unstable; urgency=medium . * New upstream release. * source: Switch to source format 3.0 (quilt), because upstream provides only .xz tarballs. (Closes: #1036176) Checksums-Sha1: 22f478d035467d1eb2d0ec2c12ac6c0db1056d7a 5893 mesa_24.0.7-1.dsc af2a772ce3ee4dd001cd7a44c3d1370d042dbfb1 20144724 mesa_24.0.7.orig.tar.xz af267e53b0eec7089187d6aec3a9d89e37308431 488 mesa_24.0.7.orig.tar.xz.asc d072056f71e786cd51d8fd5cfae3e3c0fc8ce9fc 103288 mesa_24.0.7-1.debian.tar.xz 303f5ecfc5a1c5d90f4ca14ca4a5263033ff7cdd 10588 mesa_24.0.7-1_source.buildinfo Checksums-Sha256: 409be08af1e8cb61a8d64fe3dc15d4f2809c39e5918b532b9706e7311f2be3aa 5893 mesa_24.0.7-1.dsc 7454425f1ed4a6f1b5b107e1672b30c88b22ea0efea000ae2c7d96db93f6c26a 20144724 mesa_24.0.7.orig.tar.xz b381152085813b52872f460ebc9a98b7db60cd3756edd2e2b3b68de55791e1c9 488 mesa_24.0.7.orig.tar.xz.asc e89de7fd999376da01854b0ab997b0c920f96e12188c115ab0405f4931d4fbdf 103288 mesa_24.0.7-1.debian.tar.xz c7727b7e59ec78a8c3b5cc71ad15909a1f1aa22919f966ba9b7e0668f3a0beea 10588 mesa_24.0.7-1_source.buildinfo Files: 8c1d371d05a7cd6b0e3df3ccd8b6443c 5893 graphics optional mesa_24.0.7-1.dsc 20e3808393ab7e726447fafa38cddb71 20144724 graphics optional mesa_24.0.7.orig.tar.xz decaf23e27ba1a29ef751f0b16a05aad 488 graphics optional mesa_24.0.7.orig.tar.xz.asc 217f51bb99a39f8a1bad364a9845a7eb 103288 graphics optional mesa_24.0.7-1.debian.tar.xz 5bf8018029a154d95e4a247be05ac59c 10588 graphics optional mesa_24.0.7-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmY9ynIACgkQy3AxZaiJ hNyaJA//THVpYfpOxuD7ZINWgk/h3pBDr1n82EAB2k1e6SguixEKquJ/4b+2e7Yu dVaq39wzTPpvJIepDQgWXmhWJjg5MaMRq7Rc6oMdJEXMK3CNzDiJ3ASgJel3P+dm U145B32CAGZqJZDs2JlxxHO6u2gdixrMkleNgEP2mJNnzgqvNTS70eEazjcbHS40 2tBO2iDznuolKrxPNEUWEXEqwgkcRlKFIMw6bJDyi/xR/gTGH+cyrI8PosYxPa8h HE0MLDu6kHegNNBNmrrpmaNb/BG5SoJZZUkbhFEMsEphuz9HP13xoFZlxMbB/AHq NBZlToH3QMH09oMzne8Oon452Xqc6m7xPg0lHsY7WsT2D39Koqgibr7DLi0MDyeU ojCpBiMzimUrGjSzBCXBGhr2bOMQ06U4ikeZF0Jw8rO3gBuKJ2M2tfHQlLQ5rSUx VGyWyM9vsLrsRBzD0Rdbf/BAXnhsE8NTVmXO/2BtJqdvxm8yfxQY9en9lit9MRLH XJ6/QPlREfH7Re2ybEpCrP/pPiCb14gi6b393jD3YrvOS63oA/z2SqN0a1VF4yDM NsaGKHnIXp6VF2l3XKzQ/AxDDzmBmHdZ0GrUDKtC1ZfsQ1N6d7aIcXq8WiBDnRy6 vPGC+Z7fPrfMvbA0bNma0Eq72wkqK6+JNNbeZzaWf94l5oZGT+s= =Yq/T -END PGP SIGNATURE- pgpvE2PpyGVmM.pgp Description: PGP signature --- End Message ---
Processed: Re: src:libdmx Bug#1035474: Don't include in Bookworm?
Processing commands for cont...@bugs.debian.org: > clone 1035474 -1 Bug #1035474 [src:libdmx] Don't include in trixie? Bug 1035474 cloned as bug 1070350 > block 1035474 by -1 Bug #1035474 [src:libdmx] Don't include in trixie? 1035474 was not blocked by any bugs. 1035474 was not blocking any bugs. Added blocking bug(s) of 1035474: 1070350 > reassign -1 xorg-dev Bug #1070350 [src:libdmx] Don't include in trixie? Bug reassigned from package 'src:libdmx' to 'xorg-dev'. No longer marked as found in versions libdmx/1:1.1.4-2. Ignoring request to alter fixed versions of bug #1070350 to the same values previously set > retitle -1 xorg-dev: drop dependency on libdmx-dev Bug #1070350 [xorg-dev] Don't include in trixie? Changed Bug title to 'xorg-dev: drop dependency on libdmx-dev' from 'Don't include in trixie?'. > found -1 1:7.7+23 Bug #1070350 [xorg-dev] xorg-dev: drop dependency on libdmx-dev Marked as found in versions xorg/1:7.7+23. > thanks Stopping processing here. Please contact me if you need assistance. -- 1035474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035474 1070350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Blocks
Processing commands for cont...@bugs.debian.org: > block 1069378 by 1069408 Bug #1069378 [src:picom] picom: FTBFS on arm64: cc: error: unrecognized command-line option '-Wunknown-warning-option' 1069378 was not blocked by any bugs. 1069378 was not blocking any bugs. Added blocking bug(s) of 1069378: 1069408 > thanks Stopping processing here. Please contact me if you need assistance. -- 1069378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met
Processing control commands: > retitle -1 x11-apps: FTBFS with libxcb 1.17: Package requirements (x11-xcb > xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met Bug #1069405 [src:x11-apps] x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met Changed Bug title to 'x11-apps: FTBFS with libxcb 1.17: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met' from 'x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met'. > block -1 with 1069408 Bug #1069405 [src:x11-apps] x11-apps: FTBFS with libxcb 1.17: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met 1069405 was not blocked by any bugs. 1069405 was not blocking any bugs. Added blocking bug(s) of 1069405: 1069408 -- 1069405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063088: marked as done (weston: NMU diff for 64-bit time_t transition)
Your message dated Sun, 21 Apr 2024 18:37:58 +0200
with message-id
and subject line Re: Bug#1063088: weston: NMU diff for 64-bit time_t transition
has caused the Debian Bug report #1063088,
regarding weston: NMU diff for 64-bit time_t transition
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.)
--
1063088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: weston
Version: 13.0.0-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
weston as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for weston
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru weston-13.0.0/debian/changelog weston-13.0.0/debian/changelog
--- weston-13.0.0/debian/changelog 2024-01-22 09:00:54.0 +
+++ weston-13.0.0/debian/changelog 2024-02-05 01:50:20.0 +
@@ -1,3 +1,10 @@
+weston (13.0.0-1.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Mon, 05 Feb 2024 01:50:20 +
+
weston (13.0.0-1) unstable; urgency=medium
* Upload to unstable
diff -Nru weston-13.0.0/debian/control weston-13.0.0/debian/control
--- weston-13.0.0/debian/control2024-01-22 09:00:54.0 +
+++ weston-13.0.0/debian/control2024-02-05 01:50:19.0 +
@@ -72,13 +72,14 @@
and fast compositor and is suitable for many embedded and mobile use
cases.
-Package: libweston-13-0
+Package: libweston-13-0t64
+Provides: ${t64:Provides}
Section: libs
Architecture: linux-any
Multi-Arch: same
Depends: ${misc:Depends}, ${shlibs:Depends}
-Replaces: weston (<< 1.12.0-1)
-Breaks: weston (<< 1.12.0-1)
+Replaces: libweston-13-0, weston (<< 1.12.0-1)
+Breaks: libweston-13-0 (<< ${source:Version}), weston (<< 1.12.0-1)
Description: reference implementation of a wayland compositor (shared libs)
Part of the Wayland project is also the Weston reference implementation
of a Wayland compositor. Weston can run as an X client or under Linux
@@ -93,7 +94,7 @@
Architecture: linux-any
Depends: libpixman-1-dev,
libwayland-dev,
- libweston-13-0 (= ${binary:Version}),
+ libweston-13-0t64 (= ${binary:Version}),
libxkbcommon-dev,
${misc:Depends},
${shlibs:Depends}
diff -Nru weston-13.0.0/debian/libweston-13-0.install
weston-13.0.0/debian/libweston-13-0.install
--- weston-13.0.0/debian/libweston-13-0.install 2024-01-22 09:00:54.0
+
+++ weston-13.0.0/debian/libweston-13-0.install 1970-01-01 00:00:00.0
+
@@ -1,13 +0,0 @@
-usr/lib/*/libweston-1
Processed: Re: Bug#1069408: kwin: FTBFS on arm64: present.h:20:10: fatal error: dri3.h: No such file or directory
Processing control commands: > reassign -1 libxcb Bug #1069408 [src:kwin] kwin: FTBFS on arm64: present.h:20:10: fatal error: dri3.h: No such file or directory Bug reassigned from package 'src:kwin' to 'libxcb'. No longer marked as found in versions kwin/4:5.27.10-1. Ignoring request to alter fixed versions of bug #1069408 to the same values previously set > found -1 1.17.0-1 Bug #1069408 [libxcb] kwin: FTBFS on arm64: present.h:20:10: fatal error: dri3.h: No such file or directory There is no source info for the package 'libxcb' at version '1.17.0-1' with architecture '' Unable to make a source version for version '1.17.0-1' Marked as found in versions 1.17.0-1. > retitle -1 libxcb-present-dev 1.17 misses dependency on libxcb-dri3-dev Bug #1069408 [libxcb] kwin: FTBFS on arm64: present.h:20:10: fatal error: dri3.h: No such file or directory Changed Bug title to 'libxcb-present-dev 1.17 misses dependency on libxcb-dri3-dev' from 'kwin: FTBFS on arm64: present.h:20:10: fatal error: dri3.h: No such file or directory'. > affects -1 + kwin Bug #1069408 [libxcb] libxcb-present-dev 1.17 misses dependency on libxcb-dri3-dev Added indication that 1069408 affects kwin -- 1069408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064702: marked as done (libxcb: FTBFS: KeyError: 'xcb_report_level_t')
Your message dated Fri, 19 Apr 2024 09:05:50 + with message-id and subject line Bug#1064702: fixed in libxcb 1.17.0-1 has caused the Debian Bug report #1064702, regarding libxcb: FTBFS: KeyError: 'xcb_report_level_t' 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.) -- 1064702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxcb Version: 1.15-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240224 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build/src' > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/xproto.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/bigreq.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/xc_misc.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/composite.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/damage.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/dpms.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/dri2.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/dri3.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/present.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/glx.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/randr.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/record.xml > python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \ > -s "3" -p //usr/lib/python3.11/site-packages \ >\ > //usr/share/xcb/render.xml > Traceback (most recent call last): > File "/<>/build/src/../../src/c_client.py", line 3394, in > > module.generate() > File "/usr/lib/python3/dist-packages/xcbgen/state.py", line 131, in generate > item.out(name) > File "/<>/build/src/../../src/c_client.py", line 3198, in > c_request > _c_request_helper(self, name, void=True, regular=False) > File "/<>/build/src/../../src/c_client.py", line 2273, in > _c_request_helper > if namecount[tname] > 1: >~^^^ > KeyError: 'xcb_report_level_t' > make[2]: *** [Makefile:1408: damage.c] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/02/24/libxcb_1.15-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions i
Processed: tagging 907152
Processing commands for cont...@bugs.debian.org: > tags 907152 + pending Bug #907152 [src:vulkan-loader] vulkan: Porting to non-linux systems Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 907152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066398: marked as done (xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1I
Your message dated Sat, 13 Apr 2024 15:08:52 + with message-id and subject line Bug#1065184: fixed in xwayland 2:23.2.6-1 has caused the Debian Bug report #1065184, regarding xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1Init' 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.) -- 1065184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xwayland Version: 2:23.2.4-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/ccL8lXZd.o: in function `main': > ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): > undefined reference to `SHA1Init' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/03/13/xwayland_23.2.4-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: xwayland Source-Version: 2:23.2.6-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of xwayland, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated xwayland 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: Sat, 13 Apr 2024 16:58:45 +0300 Source: xwayland Built-For-Profiles: noudeb Architecture: source Version: 2:23.2.6-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1065184 Changes: xwayland (2:23.2.6-1) unstable; urgency=medium . * New upstream release. - CVE-2024-31080 - CVE-2024-31081 - CVE-2024-31083 * control: Add libtirpc-dev to build-depends. (Closes: #1065184) Checksums-Sha1: 6f803a9969d399ec777d9bf016715807b3bdd2da 2530 xwayland_23.2.6-1.dsc 8c45b889051bdea66fba51f267374a38b1fd1f49 1300092 xwayland_23.2.6.orig.tar.xz f9765cfd191e9210e0669e848075589800316c21 195 xwayland_23.2.6.orig.tar.xz.asc eee62a6e27ab952d3e5fd09af1e67f58b192 35864 xwayland_23.2.6-1.debian.tar.xz 5f6515cae9b5a99b8c0ccba25ab39e198eb87c56 10357 xwayland_23.2.6-1_source.buildinfo Checksums-Sha256: 85bec8f2eb913c3b9494102521154ce3b98edfba646a6c1b49e872d3042d9f8b 2530 xwayland_23.2.6-1.dsc 1c9a366b4e7ccadba0f9bd313c59eae12d23bd72543b22a26eaf8b20835cfc6d 1300092 xwayland_23.2.6.orig.tar.xz 65d51108cc57f7cd282c86dbc71fa78e1365b738536e5b38847ef08d5dfb8c96 195 xwayland_23.2.6.orig.tar.xz.asc 537251328f7c7dad8c804fcb911ae9f784ba6d9cde91de236e898e5379e0297e 35864 xwayland_23.2.6-1.debian.tar.xz 3b0c06c46eb764de8233a85d36fa3b539e2a01e078a82773d6e749b3f662692c 10357 xwayland_23.2.6-1_source.buildinfo Files: 24b64125796ac61b40e744de0a66d849 2530 x11 optional xwayland_23.2.6-1.dsc 8f2bb6789e22b5ea1f1f19694267e539 1300092 x11 optional xwayland_23.2.6.orig.tar.xz b5091809677b5c57107c6a92f1d34f05 195 x11 optional xwayland_23.2.6.orig.tar.xz.asc 3e91428c04ebd21c1c61fa53ca7abc8c 35864 x11 optional xwayland_23.2.6-1.debian.tar.xz 905dcafe3c1775c7b0f542f1c3bbbc32 10357 x11 optional xwayland_23.2.6-1_sour
Bug#1065184: marked as done (xwayland: missing build-dep on libtirpc-dev )
Your message dated Sat, 13 Apr 2024 15:08:52 + with message-id and subject line Bug#1065184: fixed in xwayland 2:23.2.6-1 has caused the Debian Bug report #1065184, regarding xwayland: missing build-dep on libtirpc-dev 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.) -- 1065184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xwayland Version: 2:23.2.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-gl...@lists.debian.org Usertags: libtirpc-dev Dear maintainer, Starting with glibc 2.31, support for NIS (libnsl library) has been moved to a separate libnsl2 package. In order to allow a smooth transition, a libnsl-dev, which depends on libtirpc-dev, has been added to the libc6-dev package. The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1 NMU, as part of the 64-bit time_t transition. This causes xwayland to FTBFS in sid with: | Configuring version-config.h using configuration | Configuring xkb-config.h using configuration | Configuring xwayland-config.h using configuration | Run-time dependency glproto found: YES 1.4.17 | Run-time dependency gl found: YES 1.2 | Dependency glproto found: YES 1.4.17 (cached) | Dependency gl found: YES 1.2 (cached) | Run-time dependency libtirpc found: NO (tried pkgconfig and cmake) | Has header "rpc/rpc.h" : NO | | ../os/meson.build:63:8: ERROR: Problem encountered: secure-rpc requested, but neither libtirpc or libc RPC support were found | | A full log can be found at /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt | cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt This could be fixed by adding an explicit Build-Depends on libtirpc-dev. The glibc change will likely be reverted in the short term, but given its a change we want to do for Trixie, this will only lower the severity of the bug. Regards Aurelien --- End Message --- --- Begin Message --- Source: xwayland Source-Version: 2:23.2.6-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of xwayland, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated xwayland 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: Sat, 13 Apr 2024 16:58:45 +0300 Source: xwayland Built-For-Profiles: noudeb Architecture: source Version: 2:23.2.6-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1065184 Changes: xwayland (2:23.2.6-1) unstable; urgency=medium . * New upstream release. - CVE-2024-31080 - CVE-2024-31081 - CVE-2024-31083 * control: Add libtirpc-dev to build-depends. (Closes: #1065184) Checksums-Sha1: 6f803a9969d399ec777d9bf016715807b3bdd2da 2530 xwayland_23.2.6-1.dsc 8c45b889051bdea66fba51f267374a38b1fd1f49 1300092 xwayland_23.2.6.orig.tar.xz f9765cfd191e9210e0669e848075589800316c21 195 xwayland_23.2.6.orig.tar.xz.asc eee62a6e27ab952d3e5fd09af1e67f58b192 35864 xwayland_23.2.6-1.debian.tar.xz 5f6515cae9b5a99b8c0ccba25ab39e198eb87c56 10357 xwayland_23.2.6-1_source.buildinfo Checksums-Sha256: 85bec8f2eb913c3b9494102521154ce3b98edfba646a6c1b49e872d3042d9f8b 2530 xwayland_23.2.6-1.dsc 1c9a366b4e7ccadba0f9bd313c59eae12d23bd72543b22a26eaf8b20835cfc6d 1300092 xwayland_23.2.6.orig.tar.xz 65d51108cc57f7cd282c86dbc71fa78e1365b738536e5b38847ef08d5dfb8c96 195 xwayland_23.2.6.orig.tar.xz.asc 537251328f7c7dad8c804fcb911ae9f784ba6d9cde91de236e898e5379e0297e 35864 xwayland_23.2.6-1.debian.tar.xz 3b0c06c46eb764de8233a85d36fa3b539e2a01e078a82773d6e749b3f662692c 10357 xwayland_23.2.6-1_source.buildinfo Files: 24b64125796ac61b40e744de0a66d849 2530 x11 optional xwayland_23.2.6-1.dsc 8f2bb6789e22b5ea1f1f19694267e539 1300092 x11 optional xwayland_23.2.6.orig.tar.xz b5091809677b5c57107c6a92f1d34f05 195 x11 optional xwayland_23.2.6.orig.tar.xz.asc 3e91428c04ebd21c1c61fa53ca7abc8c 35864 x11 o
Processed: Re: Bug#1066398: xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1In
Processing control commands: > forcemerge -1 1065184 Bug #1066398 [src:xwayland] xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1Init' Bug #1065184 [src:xwayland] xwayland: missing build-dep on libtirpc-dev Added tag(s) trixie and sid. Merged 1065184 1066398 -- 1065184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065184 1066398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067197: marked as done (xserver-xorg-video-nouveau ftbfs)
Your message dated Thu, 11 Apr 2024 21:38:04 +0200 with message-id <87edbb1yhv@turtle.gmx.de> and subject line Re: Bug#1067197: xserver-xorg-video-nouveau ftbfs has caused the Debian Bug report #1067197, regarding xserver-xorg-video-nouveau ftbfs 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.) -- 1067197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xserver-xorg-video-nouveau Version: 1:1.0.17-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: del...@debian.org Failure can be seen on hppa architecture, but I assume it will show up on armel too: https://buildd.debian.org/status/fetch.php?pkg=xserver-xorg-video-nouveau=hppa=1%3A1.0.17-3=1710537593=0 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/xorg -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -I/usr/include/libdrm -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -Wall -I/usr/include/xorg -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c ../../src/nv_shadow.c -fPIC -DPIC -o .libs/nv_shadow.o ../../src/nv_driver.c: In function ‘NVScreenInit’: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declaration] 1451 | ret = wfbScreenInit(pScreen, FBStart, pScrn->virtualX, | ^ | fbScreenInit cc1: some warnings being treated as errors make[3]: *** [Makefile:674: nv_driver.lo] Error 1 --- End Message --- --- Begin Message --- Am 20.03.2024 um 01:02 schrieb Helge Deller: > On 3/19/24 23:46, Helge Deller wrote: >>> The problem is that the hppa and powerpc buildds have an outdated >>> version of dpkg-dev installed, although a newer one has been available >>> for over a week. >> >> Oh... yes. >> Luckily I just updated the chroots a few hours ago. >> Giving-back packet again to try. > > You were right. Using newer dpkg-dev solved this issue. > This bug can be closed. Sorry for the delay. I was waiting for the powerpc build to succeed, by now xserver-xorg-video-nouveau has been built on all architectures :-). Cheers, Sven--- End Message ---
Bug#1068507: marked as done (libxpresent: New upstream version)
Your message dated Thu, 11 Apr 2024 09:04:26 + with message-id and subject line Bug#1068507: fixed in libxpresent 1.0.1-1 has caused the Debian Bug report #1068507, regarding libxpresent: New upstream version 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.) -- 1068507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxpresent Version: 1.0.0-2 Severity: wishlist Please import the latest upstream version, which is 1.0.1 currently. --- End Message --- --- Begin Message --- Source: libxpresent Source-Version: 1.0.1-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of libxpresent, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated libxpresent 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: Thu, 11 Apr 2024 11:41:57 +0300 Source: libxpresent Built-For-Profiles: noudeb Architecture: source Version: 1.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1068507 Changes: libxpresent (1.0.1-1) unstable; urgency=medium . * control: Migrate to x11proto-dev. * New upstream release. (Closes: #1068507) * Update signing-key.asc. * Drop upstreamed patch. * control, rules: Migrate to debhelper-compat 13. * control: Bump policy to 4.7.0. * Update vcs urls. * control: Migrate to pkgconf. Checksums-Sha1: b182707957d6a0e627373c48b1d38e69138385b4 2346 libxpresent_1.0.1-1.dsc 3102c66b57ced19b686afe139f94ea6b4074e29b 386385 libxpresent_1.0.1.orig.tar.gz 9be7534ca78eb49dc264a903c54fb05901dfceeb 801 libxpresent_1.0.1.orig.tar.gz.asc c5030bffae34b9d1e8fe974b8ae16fdf09a9697b 17924 libxpresent_1.0.1-1.diff.gz 356eb8d9bc95ac6cdaff331e05ae22ab70539155 7640 libxpresent_1.0.1-1_source.buildinfo Checksums-Sha256: 258bf15fd4beeda78ee19a276e0cb9b7e5591619a0461a93e580abce180df08d 2346 libxpresent_1.0.1-1.dsc 8ebf8567a8f6afe5a64275a2ecfd4c84e957970c27299d964350f60be9f3541d 386385 libxpresent_1.0.1.orig.tar.gz 70ac5c28474b1d0f76c996abbfd0090ab96614d5e61424d83df60ffcd5213057 801 libxpresent_1.0.1.orig.tar.gz.asc 954198e1b50fd3e160b7b85fad4eb101a716f0416e573a43d1d2042825b7 17924 libxpresent_1.0.1-1.diff.gz f6918ae2524dc9d40e3cd205ad7b2277b2f72b8ec6ad6f6eed49a50a00fc87d6 7640 libxpresent_1.0.1-1_source.buildinfo Files: e162808a317b4f003d6e089453f7a248 2346 x11 optional libxpresent_1.0.1-1.dsc 312f1d9ece56e598e85e2e9a39ca5efc 386385 x11 optional libxpresent_1.0.1.orig.tar.gz ed487dbbf7214cb32ca4f68413675e84 801 x11 optional libxpresent_1.0.1.orig.tar.gz.asc 496581058befaef077d63001cb728084 17924 x11 optional libxpresent_1.0.1-1.diff.gz 4313936c2ddcc5b38c63bb8cc77b2b6d 7640 x11 optional libxpresent_1.0.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmYXopcACgkQy3AxZaiJ hNzXOw//aSUcjAUcQa7zfuGow49CN6vkrrwizy3eCM024vhqJJt/OGy1eJ3oLBGU TZ3AJfOaFoOwqD/sB03CCf4u9GO2k3+hc9a+AYk1UJ9oIQ4UAMHprwkvoZTKKOfz 5PRxYEMHLLz2hYbCSkF3Se2pjmB11wWmEu/JwJNqf5GCPt7PiwmI61NVrz/IywWU qmMz1Zm18gmuKyFx32wxvWi7luIi5qNsk9WVVogFmksbxzOuDZ3GG8dsdqyOV3pn YDJpBWGlB77qtB2/G6ZYoLfsBhJ5OuQ3Y5t5K/Oljmh5DV+kbQP6Oe90124Xg1gU MqXl91fpxu5DQMXmIZr5Nu6vazzx+qcetREbXoPYRMtuYD+noMMyHFeZOLsoe5pJ ZiWsbZnBpaw8M6eCZZIWLJy812yTWSOAMz69AIJLiWbkxobJRae0+3tqVqzHh0ag gjiOsp0dHGkQQyQ3Zb+5Xh6lAupFRxE7lIZGyc0LNA0tBcHDW04GBH4F6STOogYZ 5ikJfSHmtEEiYPSimxqK4jkmzUTBhhhaLzPCTgA9liLFdhe/G0RhHXlLkBbyKXzB Q/udPaHYpNphtQC0JubtwWMBTWMiLo3wV0mernxwSB/imA4qc54K7L0zv2tRyG8A rlJEH+AslMMjGsyohkmlXbvJnY7UmOu5xcoe5PaCYDBgOQ4dwF8= =j1XQ -END PGP SIGNATURE- pgpKkOjZXaL6V.pgp Description: PGP signature --- End Message ---
Bug#1068470: marked as done (xorg-server: double free in fix for CVE-2024-31083)
Your message dated Wed, 10 Apr 2024 09:05:22 + with message-id and subject line Bug#1068470: fixed in xorg-server 2:21.1.12-1 has caused the Debian Bug report #1068470, regarding xorg-server: double free in fix for CVE-2024-31083 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.) -- 1068470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorg-server Version: 2:21.1.11-3 Severity: grave Tags: security upstream patch Justification: user security hole X-Debbugs-Cc: jcris...@debian.org, Debian Security Team The latest security fixes introduced a regression, apparently replacing use-after-free with double-free in some circumstances: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1476 Cheers, Julien --- End Message --- --- Begin Message --- Source: xorg-server Source-Version: 2:21.1.12-1 Done: Julien Cristau We believe that the bug you reported is fixed in the latest version of xorg-server, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated xorg-server 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: Wed, 10 Apr 2024 10:44:55 +0200 Source: xorg-server Architecture: source Version: 2:21.1.12-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Julien Cristau Closes: 1068470 Changes: xorg-server (2:21.1.12-1) unstable; urgency=medium . * New upstream release. * render: Avoid possible double-free in ProcRenderAddGlyphs() (closes: #1068470) Checksums-Sha1: a1d657b8ffbc2bd97b05f131a0988d3e2b71af73 4269 xorg-server_21.1.12-1.dsc 8cccd82e3d0954abb4e26ab8ba0f1fc316d5cab3 9023823 xorg-server_21.1.12.orig.tar.gz 98bdf3227d471ad5bda7efd224147d1dd49b3ab0 488 xorg-server_21.1.12.orig.tar.gz.asc a6eeb39464690f011307bbeedb2be2c8e295c0ab 169446 xorg-server_21.1.12-1.diff.gz Checksums-Sha256: 104d482e7cdccd9d37b3b18a4f2fea4c60ba3f4146e06a5a39bbf535c9161702 4269 xorg-server_21.1.12-1.dsc f76a5878b0e6d16415cf0cd24ffc21090845fef3bc4ada45e57ea86b6c8fb75b 9023823 xorg-server_21.1.12.orig.tar.gz 4dcd14c489665fcc8257f24b3ce88e711945c831fe4a9ca81087b915ddc057a0 488 xorg-server_21.1.12.orig.tar.gz.asc f89c8907569b76cbf5cf352e52228c4fd79e87039e9aea1e312ac264ccd1af06 169446 xorg-server_21.1.12-1.diff.gz Files: 58ed8527d8e3b50ad119950b18cedc21 4269 x11 optional xorg-server_21.1.12-1.dsc ac54ae30ef6b8f57ade1753a601388ef 9023823 x11 optional xorg-server_21.1.12.orig.tar.gz 22eacdf447315529eb5156d20d94dca4 488 x11 optional xorg-server_21.1.12.orig.tar.gz.asc c64d9fdb537568431df5570105b6bbbf 169446 x11 optional xorg-server_21.1.12-1.diff.gz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAmYWUgQUHGpjcmlzdGF1 QGRlYmlhbi5vcmcACgkQnbAjVVb4z62cxRAAopFEuLtrQQBpN4w3/7IkWkr/3lEQ bnPhkLb/yABGLkx5+jWL2Hy1DYybutIJb4opFpJ2/dy4llfKQJXk2wI2HVg0A98A mdzDh1HvaJH5HQLtNiRgZOJ2yFs1PJI8FqGp+VjaOxvi07d7YzropSaTt/3V+xGW NCxV8Ic7g5p8wJIKIehzC5c0djgE31vtidBInfO4Dhm0c5nqARWd0ViirNWyHI6/ 471dFtcRefYy/OIulM3rTCEUtf16IP2AGDTUvOW0iITfMPXcRn/dCM5cBer6XKP2 wAAeyISe33xU/Xbkv9MmHLE+UyYyV/SyWAzBLrwuKKNJeASoa9mzUxbHyF7iu7Gv rK2OrymDLdwYiRC6Pz3lgUcm7H9lUdDwaiINKPAtS4dkGvsuYwLNr6qRpQxodrsz My6T+1bhPKeJJMmNvCg3PiGsiluZcOxuDR+CC/llrLx5hDn2jQ9A9fgBSILi3r1l DPJOKQq5j1rYJaAf5gjU/rmdvgUyWJouw21JuqHHuqGgbl3azakHN/om4kM+Q8A0 4qEr/TrKtgLU8db4yfXu0SOKyeFtv3UxUqeBOMYMaIAC0QLUMcRxhvkQYL8h8T4i GBu8P0MeB7/3/8S0r4B10a5k5wZZGBU1eRYhTLnDoubGJYFrxTEFDrZubJZ5DB2J RYkt1WA6RvpmRH4= =Wgch -END PGP SIGNATURE- pgpYYfItvTd5p.pgp Description: PGP signature --- End Message ---
Bug#550308: marked as done ([xedit] missing deps on xbitmaps)
Your message dated Tue, 9 Apr 2024 21:39:15 +0200 with message-id and subject line Re: Bug#550308: [xedit] missing deps on xbitmaps has caused the Debian Bug report #550308, regarding [xedit] missing deps on xbitmaps 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.) -- 550308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: x11-apps Version: 7.4+2 Severity: normal When i hit Control-S in xedit I get a dialog window which seems to be transparent (it displays the viewed file on top of its background). That makes it very close to unreadable. I tried to capture a xwd dump, not sure if it will be useful, but it's here: http://primate.net/~itz/xedit.xwd (note that you must type the entire URL in the address bar, or better use wget or curl) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.30.9-core2-virgin (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages x11-apps depends on: ii cpp 4:4.3.3-9 The GNU C preprocessor (cpp) ii libc6 2.9-25 GNU C Library: Shared libraries ii libpng12-01.2.39-1 PNG library - runtime ii libsm62:1.1.1-1 X11 Session Management library ii libx11-6 2:1.2.2-1 X11 client-side library ii libxaw7 2:1.0.6-1 X11 Athena Widget library ii libxcursor1 1:1.1.9-1 X cursor management library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft2 2.1.13-3 FreeType-based font drawing librar ii libxkbfile1 1:1.0.5-1 X11 keyboard file manipulation lib ii libxmu6 2:1.0.4-2 X11 miscellaneous utility library ii libxmuu1 2:1.0.4-2 X11 miscellaneous micro-utility li ii libxrender1 1:0.9.4-2 X Rendering Extension client libra ii libxt61:1.0.6-1 X11 toolkit intrinsics library ii x11-common1:7.3+20 X Window System (X.Org) infrastruc x11-apps recommends no packages. Versions of packages x11-apps suggests: ii mesa-utils7.5.1-1Miscellaneous Mesa GL utilities -- no debconf information --- End Message --- --- Begin Message --- Version: 7.7~1 On Sat, 13 Jun 2020 15:50:27 + Ivan Shmakov wrote: > Control: fixed -1 7.7~1 > > >>>>> On 2011-10-06 12:42:01 +0200, Ralf Jung wrote: > > > Actually, x11-apps currently recommends xbitmap, which does not exist > > and is probably a typo of xbitmaps. > > Per Debian changelog, this was fixed in 7.7~1. I don’t seem > to see what else could be done for this issue, and thus suggest > to close this bug.--- End Message ---
Bug#810497: marked as done (xwayland: There is no manpage for Xwayland)
Your message dated Tue, 9 Apr 2024 21:27:41 +0200 with message-id and subject line xwayland: There is no manpage for Xwayland has caused the Debian Bug report #810497, regarding xwayland: There is no manpage for Xwayland 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.) -- 810497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xwayland Version: 2:1.17.3-2 Severity: normal Dear Maintainer, I see that Wayland is now used by default in Debian testing. While trying to figure out why it happens not to work for me (which may lead to another bug report) I found that there is very little (if any) documentation about it. Not even a manpage. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xwayland depends on: ii libaudit1 1:2.4.5-1 ii libc6 2.21-6 ii libdrm2 2.4.65-3 ii libegl1-mesa [libegl1-x11] 11.0.8-1 ii libepoxy0 1.3.1-1 ii libgbm1 11.0.8-1 ii libgcrypt20 1.6.4-4 ii libgl1-mesa-glx [libgl1]11.0.8-1 ii libpixman-1-0 0.33.4-1 ii libselinux1 2.4-3 ii libwayland-client0 1.9.0-1 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1 ii libxfont1 1:1.5.1-1 ii libxshmfence1 1.2-1 ii xserver-common 2:1.17.3-2 xwayland recommends no packages. xwayland suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 2:21.1.3-1 There is a manpage for xwayland since at least 2:21.1.3-1--- End Message ---
Processed: bug 1068470 is forwarded to https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659
Processing commands for cont...@bugs.debian.org: > forwarded 1068470 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659 Bug #1068470 [src:xorg-server] xorg-server: double free in fix for CVE-2024-31083 Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068378
Processing control commands: > tags -1 patch Bug #1068378 [xdm] xdm: pam_keyinit is missing from /etc/pam.d/xdm Added tag(s) patch. -- 1068378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057945: marked as done (xorg-server: use udev.pc to place udev rules)
Your message dated Wed, 03 Apr 2024 20:48:06 + with message-id and subject line Bug#1057945: fixed in xorg-server 2:21.1.11-3 has caused the Debian Bug report #1057945, regarding xorg-server: use udev.pc to place udev rules 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.) -- 1057945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorg-server Version: 21.1.9-1 Severity: normal Tags: patch User: helm...@debian.org Usertags: dep17m2 Dear Maintainer, your package installs files related to udev, into /lib. These files need to be moved to /usr/lib as part of Debian's usr-merge effort [1]. Attached you will find a patch to delegate the exact placement of the udev files to udev.pc (using pkg-config). This works today in unstable and also for bookworm. Once udev.pc in unstable points to /usr/lib your package will benefit automatically after a binNMU or any other upload. If during the trixie cycle your package will undergo structural changes or any other file moves, please see the wiki and upload to experimental first when these changes are done. Later during the trixie cycle I expect this bug class to raise in priority. Thank you for considering, Chris [1] https://wiki.debian.org/UsrMerge diff -u xorg-server-21.1.9/debian/changelog xorg-server-21.1.9/debian/changelog --- xorg-server-21.1.9/debian/changelog +++ xorg-server-21.1.9/debian/changelog @@ -1,3 +1,10 @@ +xorg-server (2:21.1.9-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Use udev.pc to place udev files. (Closes: #-1) + + -- Chris Hofstaedtler Sun, 10 Dec 2023 20:49:20 +0100 + xorg-server (2:21.1.9-1) unstable; urgency=medium * New upstream release. diff -u xorg-server-21.1.9/debian/control xorg-server-21.1.9/debian/control --- xorg-server-21.1.9/debian/control +++ xorg-server-21.1.9/debian/control @@ -73,6 +73,7 @@ libdbus-1-dev (>= 1.0) [linux-any], # systemd-daemon libsystemd-dev [linux-any], + systemd-dev [linux-any], Build-Depends-Indep: xz-utils Standards-Version: 3.9.8 Rules-Requires-Root: binary-targets diff -u xorg-server-21.1.9/debian/rules xorg-server-21.1.9/debian/rules --- xorg-server-21.1.9/debian/rules +++ xorg-server-21.1.9/debian/rules @@ -4,6 +4,10 @@ include /usr/share/dpkg/architecture.mk +ifeq ($(DEB_HOST_ARCH_OS), linux) +deb_udevdir = $(shell pkg-config --variable=udevdir udev) +endif + %: dh $@ --with quilt @@ -129,10 +133,10 @@ install -m 755 -d debian/xserver-xorg-core/usr/share/bug/xserver-xorg-core install -m 755 debian/xserver-xorg-core.bug.script debian/xserver-xorg-core/usr/share/bug/xserver-xorg-core/script ifeq ($(DEB_HOST_ARCH_OS), linux) - install -d debian/xserver-xorg-core/lib/udev/rules.d - install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core/lib/udev/rules.d - install -d debian/xserver-xorg-core-udeb/lib/udev/rules.d - install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core-udeb/lib/udev/rules.d + install -d debian/xserver-xorg-core$(deb_udevdir)/rules.d + install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core$(deb_udevdir)/rules.d + install -d debian/xserver-xorg-core-udeb$(deb_udevdir)/rules.d + install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core-udeb$(deb_udevdir)/rules.d endif override_dh_missing-indep: --- End Message --- --- Begin Message --- Source: xorg-server Source-Version: 2:21.1.11-3 Done: Julien Cristau We believe that the bug you reported is fixed in the latest version of xorg-server, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated xorg-server 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: Wed, 03 Apr 2024 21:09:12 +0200 Source: xorg-server Architecture: source Version: 2:21.1.11-3 Distribution: unstable Urgency: high Maintainer: Debian X Strike Force Changed-By: Julien Cristau Closes: 1057945 Changes: xorg-server (2:21.1.11-3) unstable; urgency=high . [ Chris Hofstaedtler ] * Use udev
Processed: Re: Bug#1067207: mesa: switch statement too large, might need -mlong-jump-table-offsets
Processing commands for cont...@bugs.debian.org: > retitle 1067207 mesa: [m68k] switch statement too large, needs > -mlong-jump-table-offsets Bug #1067207 [src:mesa] mesa: switch statement too large, might need -mlong-jump-table-offsets Changed Bug title to 'mesa: [m68k] switch statement too large, needs -mlong-jump-table-offsets' from 'mesa: switch statement too large, might need -mlong-jump-table-offsets'. > tags 1067207 + patch Bug #1067207 [src:mesa] mesa: [m68k] switch statement too large, needs -mlong-jump-table-offsets Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1067207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1062170: marked as done (glw: NMU diff for 64-bit time_t transition)
Your message dated Mon, 01 Apr 2024 18:00:11 +
with message-id
and subject line Bug#1062170: fixed in glw 8.0.0-3
has caused the Debian Bug report #1062170,
regarding glw: NMU diff for 64-bit time_t transition
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.)
--
1062170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glw
Version: 8.0.0-1.1
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
glw as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for glw
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -u glw-8.0.0/debian/changelog glw-8.0.0/debian/changelog
--- glw-8.0.0/debian/changelog
+++ glw-8.0.0/debian/changelog
@@ -1,3 +1,10 @@
+glw (8.0.0-1.2) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Lukas Märdian Wed, 31 Jan 2024 14:53:50 +
+
glw (8.0.0-1.1) unstable; urgency=low
[ Paul Gevers ]
diff -u glw-8.0.0/debian/control glw-8.0.0/debian/control
--- glw-8.0.0/debian/control
+++ glw-8.0.0/debian/control
@@ -19,11 +19,13 @@
Homepage: http://mesa3d.sourceforge.net/
Package: libglw1-mesa
+Replaces: libglw1-mesa
+Breaks: libglw1-mesa (<< ${source:Version})
Architecture: any
Depends:
${shlibs:Depends},
${misc:Depends},
-Provides: libglw1
+Provides: libglw1, ${t64:Provides}
Pre-Depends: ${misc:Pre-Depends}
Multi-Arch: same
Description: GL widget library for Athena and Motif -- runtime
--- End Message ---
--- Begin Message ---
Source: glw
Source-Version: 8.0.0-3
Done: Julien Cristau
We believe that the bug you reported is fixed in the latest version of
glw, 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 1062...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julien Cristau (supplier of updated glw 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: Sun, 31 Mar 2024 13:00:14 +0200
Source: glw
Binary: libglw1-mesa-dev libglw1t64-mesa libglw1t64-mesa-dbgsym
Architecture: source amd64
Version: 8.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force
Changed-By: Julien Cristau
Description:
libglw1-mesa-dev - GL widget library for Athena and Motif -- development files
libglw1t64-mesa - GL
Bug#1061287: marked as done (libllvmspirvlib-15-dev is needed even with rusticl disabled)
Your message dated Fri, 29 Mar 2024 17:01:40 + with message-id and subject line Bug#1061287: fixed in mesa 24.0.4-1 has caused the Debian Bug report #1061287, regarding libllvmspirvlib-15-dev is needed even with rusticl disabled 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.) -- 1061287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa Version: 24.0.0~rc2-1.1 Severity: normal Hi, I'm trying to build mesa 24 from experimental on bookworm. Since rusticl requires rust-bindgen 0.66 and since building that and the surrounding rust packages on bookworm is infeasible, I decided to disable rusticl by excluding my host architecture from RUSTICL_ARCHS in debian/rules. Unfortunately it seems, that libllvmspirvlib-15-dev which is pulled in only when rusticl is enabled, is also necessary without rusticl: Determining dependency 'LLVMSPIRVLib' with pkg-config executable '/usr/bin/pkg-config' env[PKG_CONFIG_PATH]:█ env[PKG_CONFIG]: /usr/bin/pkg-config --- Called: `/usr/bin/pkg-config --modversion LLVMSPIRVLib` -> 1 stderr: Package LLVMSPIRVLib was not found in the pkg-config search path. Perhaps you should add the directory containing `LLVMSPIRVLib.pc' to the PKG_CONFIG_PATH environment variable Package 'LLVMSPIRVLib', required by 'virtual:world', not found --- CMake binary for host machine is cached as not found Dependency lookup for LLVMSPIRVLib with method 'cmake' failed: CMake binary for machine host machine not found.Giving up. Run-time dependency llvmspirvlib found: NO (tried pkgconfig) ../meson.build:1844:21: ERROR: Dependency "LLVMSPIRVLib" not found, tried pkgconfig Reading meson.build, with_opencl_spirv seems to be set when opencl is not disabled and thus does not only depend on rusticl. Could you change debian/control.in such that the dependency on libllvmspirvlib-15-dev is not only emitted when rusticl is enabled but also otherwise? Let me also quickly send you two missing minimum version restrictions I found: ../meson.build:831:4: ERROR: Problem encountered: rusticl requires meson 1.3.1 or newer and: Message: libdrm 2.4.119 needed because amdgpu has the highest requirement Dependency libdrm_amdgpu found: NO found 2.4.114 but need: '>=2.4.119' Run-time dependency libdrm_amdgpu found: NO█ ../meson.build:1674:6: ERROR: Dependency lookup for libdrm_amdgpu with method 'pkgconfig' failed: Invalid version, need 'libdrm_amdgpu' ['>=2.4.119'] found '2.4.114'. Thanks! cheers, josch --- End Message --- --- Begin Message --- Source: mesa Source-Version: 24.0.4-1 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 1061...@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: Fri, 29 Mar 2024 17:59:50 +0200 Source: mesa Built-For-Profiles: noudeb Architecture: source Version: 24.0.4-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1061287 Changes: mesa (24.0.4-1) unstable; urgency=medium . [ Timo Aaltonen ] * New upstream release. * patches: Dropped upstreamed patches. . [ Fabio Pedretti ] * control: libllvmspirvlib-*-dev is needed even with rusticl disabled (Closes: #1061287) * control: Bump meson build-dep Checksums-Sha1: 5c07969f07328fa899840d9f61e3e7bdf190cd91 5629 mesa_24.0.4-1.dsc 7fdca41e718aa9ed65ef438b828455a48959a072 32922354 mesa_24.0.4.orig.tar.gz 17f72042ad7253f90c084d54489f771b091a41a3 115838 mesa_24.0.4-1.diff.gz 5825927846d8aee772529d30eab9faae39b6852f 10302 mesa_24.0.4-1_source.buildinfo Checksums-Sha256: 686b0646c3b6639ab78d4a6be2745772a75fff60bfcaa19b6fdf244e413e5b73 5629 mesa_24.0.4-1.dsc 7fbc95b2d426488c48ff86763c86f4991ed3c9aa2606d640910b3f4bfbcb7685 32922354 mesa
Processed: Re: Bug#1067778: retroarch ftbfs in unstable
Processing control commands: > forcemerge 1064681 1067778 Bug #1064681 [src:retroarch] retroarch: FTBFS: glslang is disabled and forced to build with SPIRV-Cross support. Bug #1067778 [src:retroarch] retroarch ftbfs in unstable Severity set to 'important' from 'serious' 1067778 was not blocked by any bugs. 1067778 was not blocking any bugs. Added blocking bug(s) of 1067778: 1062799 Bug #1064681 [src:retroarch] retroarch: FTBFS: glslang is disabled and forced to build with SPIRV-Cross support. Added tag(s) trixie. Merged 1064681 1067778 -- 1064681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064681 1067778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065131: marked as done (electron: GPU process crash with AMDGPU, ac: Unknown GPU, using 0 for raster_config)
Your message dated Mon, 25 Mar 2024 20:12:41 +0100 with message-id and subject line Re: Bug#1065131: electron: GPU process crash with AMDGPU, ac: Unknown GPU, using 0 for raster_config has caused the Debian Bug report #1065131, regarding electron: GPU process crash with AMDGPU, ac: Unknown GPU, using 0 for raster_config 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.) -- 1065131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mesa-va-drivers Version: 24.0.1-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading mesa-va-drivers to version 24.0.1-1 cause GPU process craches in electron based applications. This cause very bad performance in electron applications that need the GPU support (like EasyEDA, a PCB design software). Downgrading only mesa-va-drivers to version 23.3.5-1 fix GPU process crashes. The error given is (in EasyEDA Pro, an electron based application): ``` ac: Unknown GPU, using 0 for raster_config [28335:0229/235949.402210:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=11 ``` Then ``` amd: LLVM doesn't support , bailing out... KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission non accordée KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission non accordée ``` With many of the last "KMS" line. EasyEDA Pro detect the issue and shows a messagebox about missing GPU support. With VS Code(an electron based application): ``` ac: Unknown GPU, using 0 for raster_config [28721:0301/54.499841:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=11 [28721:0301/54.499852:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 1 time(s) ac: Unknown GPU, using 0 for raster_config [28721:0301/54.675312:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=11 [28721:0301/54.675323:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 2 time(s) ac: Unknown GPU, using 0 for raster_config [28721:0301/54.823694:ERROR:gpu_process_host.cc(995)] GPU process exited unexpectedly: exit_code=11 [28721:0301/54.823705:WARNING:gpu_process_host.cc(1364)] The GPU process has crashed 3 time(s) amd: LLVM doesn't support , bailing out... KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission non accordée KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission non accordée ``` With many of the last "KMS" line. Downgrading to mesa-va-drivers 23.3.5-1 fixes the issue. Note that I have libgl1-mesa-dri package at version 23.3.3-3, maybe the version difference with mesa-va-drivers is causing troubles. I'm not upgrading libgl1-mesa-dri because of bug #1064123. I have a Radeon RX 580 GPU and I'm using the mesa's AMDGPU driver. *** End of the template - remove these template lines *** -- Package-specific info: glxinfo: name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_get_drawable_type, GLX_EXT_libglvnd, GLX_EXT_no_config_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_no_config_context, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, G
Processed: let these show up on buildd.d.o overview page
Processing commands for cont...@bugs.debian.org:
> tags 883308 + ftbfs
Bug #883308 [libseccomp2] libseccomp2 is missing support for ia64, alpha, sh4,
sparc64, m68k
Added tag(s) ftbfs.
> tags 1067055 + ftbfs
Bug #1067055 [src:openmpi] openmpi: error: implicit declaration of function
'OPAL_THREAD_ADD_FETCH64'
Ignoring request to alter tags of bug #1067055 to the same tags previously set
> tags 1067207 + ftbfs
Bug #1067207 [src:mesa] mesa: switch statement too large, might need
-mlong-jump-table-offsets
Ignoring request to alter tags of bug #1067207 to the same tags previously set
> tags 1067447 + ftbfs
Bug #1067447 [src:jackd2] jackd2: patch to fix ftbfs on m68k; jack{1,2}:
unneeded libffado-dev B-D on some arches
Added tag(s) ftbfs.
> tags 1067577 + ftbfs
Bug #1067577 [src:sysprof] sysprof: B-D on libunwind-dev which is not generally
available
Added tag(s) ftbfs.
> tags 1067582 + ftbfs
Bug #1067582 [src:gnuplot] gnuplot: please provide a profile to break B-D cycle
Added tag(s) ftbfs.
> tags 1067613 + ftbfs
Bug #1067613 [src:openjdk-11] openjdk-11: FTBFS on alpha: d/rules references
deleted patch (trivial fix)
Added tag(s) ftbfs.
> tags 1067643 + ftbfs
Bug #1067643 [src:webkit2gtk] webkit2gtk: please use architecture whitelist for
libseccomp-dev B-D
Added tag(s) ftbfs.
> tags 1067644 + ftbfs
Bug #1067644 [src:gcc-12] gcc-12: BD-Uninstallable on m68k due to gnat-11 vs
gnat-12
Added tag(s) ftbfs.
> tags 1067646 + ftbfs
Bug #1067646 [src:llvm-toolchain-17] llvm-toolchain-17: please enable m68k build
Added tag(s) ftbfs.
> tags 1067647 + ftbfs
Bug #1067647 [src:google-perftools] google-perftools: FTBFS: #error Could not
determine cache line length - unknown architecture
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067055
1067207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067207
1067447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067447
1067577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067577
1067582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067582
1067613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067613
1067643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067643
1067644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067644
1067646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067646
1067647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067647
883308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1067197: xserver-xorg-video-nouveau ftbfs
Processing control commands: > severity -1 normal Bug #1067197 [src:xserver-xorg-video-nouveau] xserver-xorg-video-nouveau ftbfs Severity set to 'normal' from 'serious' -- 1067197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#405859: marked as done (GLUT_ALPHA does not work with DRI)
Your message dated Mon, 18 Mar 2024 12:08:46 +0100 with message-id and subject line GLUT_ALPHA does not work with DRI has caused the Debian Bug report #405859, regarding GLUT_ALPHA does not work with DRI 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.) -- 405859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-mga Version: 1:1.4.4.dfsg.1-2 Severity: normal An OpenGL application fails to start using the following error message: Warning: Cannot convert string "" to type FontStruct freeglut (my_program): ERROR: Internal error in function fgOpenWindow X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 4 (X_DestroyWindow) Resource id in failed request: 0x0 Serial number of failed request: 23 Current serial number in output stream: 26 The problem occurs at the source code line: glutInitDisplayMode(GLUT_DOUBLE | GLUT_ALPHA | GLUT_DEPTH ); but with glutInitDisplayMode(GLUT_DOUBLE | GLUT_RGB | GLUT_DEPTH ); it works. My xorg config file contains: SubSection "Display" Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" #Virtual 1600 1200 EndSubSection If I comment the Virtual line out it works with both GLUT_ALPHA and GLUT_RGB. Jens -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-08-23 23:42 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1597868 2006-12-30 02:39 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 (rev 04) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 3205 2007-01-06 20:32 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/X11R6/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/X11R6/lib/X11/fonts/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/X11R6/lib/X11/fonts/Type1" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/X11R6/lib/X11/fonts/100dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/X11R6/lib/X11/fonts/75dpi" # path to defoma fonts FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load"i2c" Load"bitmap" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option
Bug#646929: marked as done (libgl1-mesa-glx: message "failed to create drawable" when starting Firefox)
Your message dated Mon, 18 Mar 2024 11:50:26 +0100
with message-id
and subject line libgl1-mesa-glx: message "failed to create drawable" when
starting Firefox
has caused the Debian Bug report #646929,
regarding libgl1-mesa-glx: message "failed to create drawable" when starting
Firefox
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.)
--
646929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgl1-mesa-glx
Version: 7.11-6
Severity: normal
Whenever I start Firefox[*], I get the message
failed to create drawable
which appears to come from
/usr/lib/x86_64-linux-gnu/libGL.so.1
One can find it in src/glx/glx_pbuffer.c line 206:
pdraw = psc->driScreen->createDrawable(psc, drawable,
glxdrawable, config);
if (pdraw == NULL) {
fprintf(stderr, "failed to create drawable\n");
return;
}
A library should not output messages to stderr (possibly except
critical errors), as they are annoying. Any error should be
returned to the caller, which should handle it (or ignore it
if it doesn't have ay consequence).
[*] Various users have this problem:
http://support.mozilla.com/questions/863200
-- Package-specific info:
glxinfo:
name of display: :0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_MESA_copy_sub_buffer, GLX_INTEL_swap_event
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_framebuffer_sRGB,
GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent,
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap,
GLX_INTEL_swap_event
GLX version: 1.4
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_MESA_multithread_makecurrent, GLX_OML_swap_method,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_INTEL_swap_event
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.11
OpenGL shading language version string: 1.20
OpenGL extensions:
GL_ARB_multisample, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract,
GL_EXT_copy_texture, GL_EXT_paletted_texture, GL_EXT_polygon_offset,
GL_EXT_subtexture, GL_EXT_texture_object, GL_EXT_vertex_array,
GL_EXT_compiled_vertex_array, GL_EXT_texture, GL_EXT_texture3D,
GL_IBM_rasterpos_clip, GL_ARB_point_parameters,
GL_EXT_draw_range_elements, GL_EXT_packed_pixels, GL_EXT_point_parameters,
GL_EXT_rescale_normal, GL_EXT_separate_specular_color,
GL_EXT_texture_edge_clamp, GL_SGIS_generate_mipmap,
GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp,
GL_SGIS_texture_lod, GL_ARB_multitexture, GL_IBM_multimode_draw_arrays,
GL_IBM_texture_mirrored_repeat, GL_3DFX_texture_compression_FXT1,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_transpose_matrix,
GL_EXT_blend_func_separate, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays,
GL_EXT_secondary_color, GL_EXT_texture_env_add,
GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias,
GL_INGR_blend_func_separate, GL_MESA_resize_buffers, GL_NV_blend_square,
GL_NV_light_max_exponent, GL_NV_texgen_reflection,
GL_NV_texture_env_combine4, GL_SUN_multi_draw_arrays,
GL_ARB_texture_border_clamp, GL_ARB_texture_compression,
GL_EXT_framebuffer_object, GL_EXT_shared_texture_palette,
GL_EXT_texture_env_dot3, GL_MESA_window_pos, GL_NV_packed_depth_stencil,
GL_NV_texture_rectangle, GL_NV_vertex_program, GL_ARB_depth_texture,
GL_ARB_occlusion_query, GL_ARB_shadow, GL_ARB_shadow_ambient,
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
GL_ARB_texture_env_
Processed: mesa: please build
Processing commands for cont...@bugs.debian.org: > retitle 901533 mesa: please build intel_sanitize_gpu tool Bug #901533 [src:mesa] mesa: please build Changed Bug title to 'mesa: please build intel_sanitize_gpu tool' from 'mesa: please build'. > End of message, stopping processing here. Please contact me if you need assistance. -- 901533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018207: marked as done (mesa: missing svga gallium driver for arm64)
Your message dated Sun, 17 Mar 2024 12:45:18 +0100 with message-id and subject line mesa: missing svga gallium driver for arm64 has caused the Debian Bug report #1018207, regarding mesa: missing svga gallium driver 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.) -- 1018207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mesa Version: 22.2.0~rc3-1 Severity: wishlist X-Debbugs-Cc: ro...@me.com Dear Maintainer, please include the "SVGA" gallium driver in ARM64 builds. It is used by VMware Fusion 22H2 Public Tech Preview. Thank you Ronny Kotzschmar --- End Message --- --- Begin Message --- Version: 22.2.0-1 "svga" gallium driver was added in 22.2.0-1.--- End Message ---
Bug#1025213: marked as done (gnome-shell: Flickering and mangled screens on wayland if dri driver not available)
Your message dated Sun, 17 Mar 2024 12:36:41 +0100 with message-id and subject line gnome-shell: Flickering and mangled screens on wayland if dri driver not available has caused the Debian Bug report #1025213, regarding gnome-shell: Flickering and mangled screens on wayland if dri driver not available 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.) -- 1025213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell Version: 43.1-2 Severity: serious Justification: Policy 3.8 Dear Maintainer, Recently a general upgrade was executed with gnome-shell upgrading from version 43.0-2 to 43.1-2. After this upgrade the gnome-shell wayland screen is flickering and mangled at any action. Flickering stops after short time, but screen often is mangled. During flickering different old or background screens are shown. Also the logon-screen is flickering and mangled. Some user-friendly person has decided to stop support for the i915 dri driver. As a "service" the mesa-upgrade at Debian also automatically deletes this driver. If an old i915-dri driver is moved to the original location, the flickering problem is gone. Also if "Gnome on Xorg" is started there is no flickering problem. In that case swrast is used for software rendering. I do not know which method gnome with wayland is using, but it is not swrast. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 6.0.0-4-686-pae (SMP w/2 CPU threads; PREEMPT) 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 gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gir1.2-accountsservice-1.0 22.08.8-1+b1 ii gir1.2-adw-1 1.2.0-1 ii gir1.2-atk-1.0 2.46.0-4 ii gir1.2-atspi-2.0 2.46.0-4 ii gir1.2-freedesktop 1.74.0-2 ii gir1.2-gcr-3 3.41.1-1+b1 ii gir1.2-gdesktopenums-3.0 43.0-1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1 ii gir1.2-gdm-1.0 43.0-1 ii gir1.2-geoclue-2.0 2.6.0-2 ii gir1.2-glib-2.0 1.74.0-2 ii gir1.2-gnomebluetooth-3.0 42.4-1 ii gir1.2-gnomedesktop-3.0 43-2 ii gir1.2-graphene-1.0 1.10.8-1 ii gir1.2-gstreamer-1.0 1.20.4-1 ii gir1.2-gtk-3.0 3.24.35-1 ii gir1.2-gtk-4.0 4.8.2+ds-3 ii gir1.2-gweather-4.0 4.2.0-1 ii gir1.2-ibus-1.0 1.5.27-4 ii gir1.2-mutter-11 43.0-2 ii gir1.2-nm-1.0 1.40.4-1 ii gir1.2-nma-1.0 1.10.4-2 ii gir1.2-pango-1.0 1.50.10+ds-1 ii gir1.2-polkit-1.0 122-1 ii gir1.2-rsvg-2.0 2.54.5+dfsg-1 ii gir1.2-soup-3.0 3.2.1-2 ii gir1.2-upowerglib-1.0 0.99.20-1+b1 ii gir1.2-webkit2-4.1 2.38.2-1+b1 ii gnome-backgrounds 43-1 ii gnome-settings-daemon 43.0-3 ii gnome-shell-common 43.1-2 ii gsettings-desktop-schemas 43.0-1 ii gstreamer1.0-pipewire 0.3.61-1 ii libatk-bridge2.0-0 2.46.0-4 ii libatk1.0-0 2.46.0-4 ii libc6 2.36-5 ii libcairo2 1.16.0-6 ii libecal-2.0-2 3.46.1-1+b2 ii libedataserver-1.2-27 3.46.1-1+b2 ii libgcr-base-3-1 3.41.1-1+b1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 ii libgirepository-1.0-1 1.74.0-2 ii libgjs0g 1.74.1-1 ii libgles2 1.5.0-1 ii libglib2.0-0 2.74.1-2 ii libglib2.0-bin
Processed: iris: Retry DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
Processing commands for cont...@bugs.debian.org: > fixed 1041591 23.1.3-1 Bug #1041591 [libgl1-mesa-dri] iris: Retry DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM Marked as fixed in versions mesa/23.1.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: xserver-xorg-video-nouveau: does not build with -Werror=implicit-function-declaration
Processing control commands: > block -1 by 1066966 Bug #1066968 [src:xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: does not build with -Werror=implicit-function-declaration 1066968 was not blocked by any bugs. 1066968 was not blocking any bugs. Added blocking bug(s) of 1066968: 1066966 -- 1066968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066382: marked as done (xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-f
Your message dated Fri, 15 Mar 2024 20:22:20 + with message-id and subject line Bug#1066382: fixed in xserver-xorg-video-nouveau 1:1.0.17-3 has caused the Debian Bug report #1066382, regarding xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declaration] 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.) -- 1066382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xserver-xorg-video-nouveau Version: 1:1.0.17-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/xorg > -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri > -I/usr/include/libdrm -I/usr/include/libdrm -I/usr/include/libdrm/nouveau > -I/usr/include/libdrm -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -minline-all-stringops -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c -o > nv04_xv_ovl.lo ../../src/nv04_xv_ovl.c > ../../src/nv_driver.c: In function ‘NVScreenInit’: > ../../src/nv_driver.c:1451:23: error: implicit declaration of function > ‘wfbScreenInit’; did you mean ‘fbScreenInit’? > [-Werror=implicit-function-declaration] > 1451 | ret = wfbScreenInit(pScreen, FBStart, pScrn->virtualX, > | ^ > | fbScreenInit > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm > -I/usr/include/libdrm -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -minline-all-stringops -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c > ../../src/nv04_exa.c -fPIC -DPIC -o .libs/nv04_exa.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm > -I/usr/include/libdrm -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -minline-all-stringops -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c > ../../src/nv04_xv_ovl.c -fPIC -DPIC -o .libs/nv04_xv_ovl.o > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/xorg > -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri > -I/usr/include/libdrm -I/usr/include/libdrm -I/usr/include/libdrm/nouveau > -I/usr/include/libdrm -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -minline-all-stringops -I/usr/include/xorg -fvisibility=hidden > -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c -o > nv04_xv_blit.lo ../../src/nv04_xv_blit.c > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/xorg > -fvisibility=hidden -I/usr/i
Bug#1064123: marked as done (libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard)
Your message dated Fri, 15 Mar 2024 11:57:55 + with message-id and subject line Bug#1064123: fixed in mesa 24.0.3-1 has caused the Debian Bug report #1064123, regarding libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard 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.) -- 1064123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgl1-mesa-dri Version: 24.0.1-1 Severity: important Dear Maintainer, after the latest upgrade it's impossible for me to run a display manager or startx any window manager; after at most a few seconds / keypresses / mouse movements the screen freezes, completely unresponsive to anything other than the power button; the log below suggests a null pointer. Running "sleep 30; killall -u lorenzo" as root before startx returns me to a tty. Reverting to the previous version everything works. I'm running this on a debian derivative, devuan; afaik it shouldn't make a difference, as the package is unmodified from debian - I don't know how to verify that other than by installing debian in some partition, can one start some window manager from a debian chroot/whatever? If it's ok in debian or you need any more info please do let me know. -- Package-specific info: glxinfo: DISPLAY is not set. /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520 OEM] [1002:6611] /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 6.6.15-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 13.2.0-13) 13.2.0, GNU ld (GNU Binutils for Debian) 2.42) #1 SMP PREEMPT_DYNAMIC Debian 6.6.15-2 (2024-02-04) Xorg X server log files on system: -- -rw-r--r-- 1 lorenzo lorenzo 48300 Sep 19 15:56 /home/lorenzo/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 rootroot39672 Feb 16 20:09 /var/log/Xorg.0.log -rw-r--r-- 1 lorenzo lorenzo 45226 Feb 17 12:58 /home/lorenzo/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/lorenzo/.local/share/xorg/Xorg.0.log): [ 2392.994] X.Org X Server 1.21.1.10 X Protocol Version 11, Revision 0 [ 2392.996] Current Operating System: Linux dudu 6.6.15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.15-2 (2024-02-04) x86_64 [ 2392.996] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.6.15-amd64 root=/dev/mapper/dev1-root ro quiet [ 2392.997] xorg-server 2:21.1.10-1devuan1 (https://www.devuan.org/os/community) [ 2392.998] Current version of pixman: 0.42.2 [ 2392.999] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 2392.999] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 2393.002] (==) Log file: "/home/lorenzo/.local/share/xorg/Xorg.0.log", Time: Sat Feb 17 12:58:09 2024 [ 2393.003] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 2393.003] (==) No Layout section. Using the first Screen section. [ 2393.003] (==) No screen section available. Using defaults. [ 2393.003] (**) |-->Screen "Default Screen Section" (0) [ 2393.003] (**) | |-->Monitor "" [ 2393.003] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 2393.003] (==) Automatically adding devices [ 2393.003] (==) Automatically enabling devices [ 2393.003] (==) Automatically adding GPU devices [ 2393.003] (==) Automatically binding GPU devices [ 2393.003] (==) Max clients allowed: 256, resource mask: 0x1f [ 2393.003] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 2393.003] Entry deleted from font path. [ 2393.003] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 2393.003] Entry deleted from font path. [ 2393.003] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 2393.003] Entry deleted from font path.
Bug#1065654: marked as done (mesa ftbfs with time_t64)
Your message dated Fri, 15 Mar 2024 11:57:55 + with message-id and subject line Bug#1065654: fixed in mesa 24.0.3-1 has caused the Debian Bug report #1065654, regarding mesa ftbfs with time_t64 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.) -- 1065654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mesa Version: 24.0.2-1 Severity: serious Tags: sid trixie patch mesa ftbfs with time_t64, patch attached. I didn't check if the _TIMET_BITS are used in the affected files. There's also a bug in the profile support. WINE cannot be built without LLVM, and therefore should be disabled.reverted: --- mesa-24.0.2/.pc/.quilt_patches +++ mesa-24.0.2.orig/.pc/.quilt_patches @@ -1 +0,0 @@ -patches reverted: --- mesa-24.0.2/.pc/.quilt_series +++ mesa-24.0.2.orig/.pc/.quilt_series @@ -1 +0,0 @@ -series reverted: --- mesa-24.0.2/.pc/.version +++ mesa-24.0.2.orig/.pc/.version @@ -1 +0,0 @@ -2 reverted: --- mesa-24.0.2/.pc/applied-patches +++ mesa-24.0.2.orig/.pc/applied-patches @@ -1 +0,0 @@ -time64.diff reverted: --- mesa-24.0.2/.pc/time64.diff/src/drm-shim/drm_shim.c +++ mesa-24.0.2.orig/.pc/time64.diff/src/drm-shim/drm_shim.c @@ -1,836 +0,0 @@ -/* - * Copyright © 2018 Broadcom - * - * Permission is hereby granted, free of charge, to any person obtaining a - * copy of this software and associated documentation files (the "Software"), - * to deal in the Software without restriction, including without limitation - * the rights to use, copy, modify, merge, publish, distribute, sublicense, - * and/or sell copies of the Software, and to permit persons to whom the - * Software is furnished to do so, subject to the following conditions: - * - * The above copyright notice and this permission notice (including the next - * paragraph) shall be included in all copies or substantial portions of the - * Software. - * - * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR - * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, - * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL - * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER - * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING - * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER - * DEALINGS IN THE SOFTWARE. - */ - -/** - * @file - * - * Implements wrappers of libc functions to fake having a DRM device that - * isn't actually present in the kernel. - */ - -/* Prevent glibc from defining open64 when we want to alias it. */ -#undef _FILE_OFFSET_BITS -#define _LARGEFILE64_SOURCE - -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include - -#include "util/anon_file.h" -#include "util/set.h" -#include "util/simple_mtx.h" -#include "util/u_debug.h" -#include "drm_shim.h" - -#define REAL_FUNCTION_POINTER(x) __typeof__(x) *real_##x - -static simple_mtx_t shim_lock = SIMPLE_MTX_INITIALIZER; -struct set *opendir_set; -bool drm_shim_debug; - -/* If /dev/dri doesn't exist, we'll need an arbitrary pointer that wouldn't be - * returned by any other opendir() call so we can return just our fake node. - */ -DIR *fake_dev_dri = (void *)_set; - -REAL_FUNCTION_POINTER(close); -REAL_FUNCTION_POINTER(closedir); -REAL_FUNCTION_POINTER(dup); -REAL_FUNCTION_POINTER(fcntl); -REAL_FUNCTION_POINTER(fopen); -REAL_FUNCTION_POINTER(ioctl); -REAL_FUNCTION_POINTER(mmap); -REAL_FUNCTION_POINTER(mmap64); -REAL_FUNCTION_POINTER(open); -REAL_FUNCTION_POINTER(opendir); -REAL_FUNCTION_POINTER(readdir); -REAL_FUNCTION_POINTER(readdir64); -REAL_FUNCTION_POINTER(readlink); -REAL_FUNCTION_POINTER(realpath); - -#define HAS_XSTAT __GLIBC__ == 2 && __GLIBC_MINOR__ < 33 - -#if HAS_XSTAT -REAL_FUNCTION_POINTER(__xstat); -REAL_FUNCTION_POINTER(__xstat64); -REAL_FUNCTION_POINTER(__fxstat); -REAL_FUNCTION_POINTER(__fxstat64); -#else -REAL_FUNCTION_POINTER(stat); -REAL_FUNCTION_POINTER(stat64); -REAL_FUNCTION_POINTER(fstat); -REAL_FUNCTION_POINTER(fstat64); -#endif - -static char render_node_dir[] = "/dev/dri/"; -/* Full path of /dev/dri/renderD* */ -static char *render_node_path; -/* renderD* */ -static char *render_node_dirent_name; -/* /sys/dev/char/major: */ -static int drm_device_path_len; -static char *drm_device_path; -/* /sys/dev/char/major:minor/device */ -static int device_path_len
Bug#1065304: marked as done (mesa: 24.0.2 requires libdrm-dev >=2.4.119)
Your message dated Fri, 15 Mar 2024 11:57:55 + with message-id and subject line Bug#1065304: fixed in mesa 24.0.3-1 has caused the Debian Bug report #1065304, regarding mesa: 24.0.2 requires libdrm-dev >=2.4.119 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.) -- 1065304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa Version: 24.0.2 requires libdrm-dev >=2.4.119 Severity: normal Dear Maintainer, While trying to build 24.0.2-1 on bookworm, mesa reported this issue. Maybe you would like to update d/control to the new required version of libdrm- dev Dependency libdrm_intel found: NO found 2.4.114 but need: '>=2.4.119' Dependency lookup for libdrm_intel with method 'pkgconfig' failed: Invalid version, need 'libdrm_intel' ['>=2.4.119'] found '2.4.114'. CMake binary for host machine is cached as not found Dependency lookup for libdrm_intel with method 'cmake' failed: CMake binary for machine host machine not found. Giving up. Run-time dependency libdrm_intel found: NO ../meson.build:1674:6: ERROR: Dependency lookup for libdrm_intel with method 'pkgconfig' failed: Invalid version, need 'libdrm_intel' ['>=2.4.119'] found '2.4.114'. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (991, 'stable-updates'), (991, 'stable-security'), (991, 'stable'), (990, 'proposed-updates'), (390, 'oldstable-security'), (390, 'oldstable'), (389, 'oldstable-updates'), (380, 'oldoldstable'), (379, 'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, 'unstable'), (93, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: mesa Source-Version: 24.0.3-1 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 1065...@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: Fri, 15 Mar 2024 13:03:15 +0200 Source: mesa Built-For-Profiles: noudeb Architecture: source Version: 24.0.3-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1064123 1065304 1065654 Changes: mesa (24.0.3-1) unstable; urgency=medium . [ Timo Aaltonen ] * New upstream release. (Closes: #1065654) * radeon-fix-gnome-shell-crash.diff: Fix a regression crashing gnome-shell. (Closes: #1064123) * fix-zink-logging.diff: Updated. * control: Bump libdrm build-dep. (Closes: #1065304) . [ Fabio Pedretti ] * patches: Drop patch for obsolete powerpcspe arch Checksums-Sha1: 2ce0ecf2cc1f2088e1c1d32402504e3c6d3f6b9e 5620 mesa_24.0.3-1.dsc 1d9bcd4078a4bdd210dd7d34ee9a28c0394da507 32867503 mesa_24.0.3.orig.tar.gz a4864a1c8b25f8b28415f1a193bd3aac9c548203 117589 mesa_24.0.3-1.diff.gz f64a389171c0435a340949c4d0c93769d65bf89a 10302 mesa_24.0.3-1_source.buildinfo Checksums-Sha256: e1d219fa7324d3bb65c936ee01601fcc06e6bebd3fd064cc394cdf6470e9885d 5620 mesa_24.0.3-1.dsc ebe00cd70bbc613b699d1b47e5b00ee3ce6f0de926b12d0a1912a144294deb9c 32867503 mesa_24.0.3.orig.tar.gz 572ac04d82575bb1b25cee8cbf5771949b9db8bb80dfb0b6ac4457dd4378c7d5 117589 mesa_24.0.3-1.diff.gz 38c05cd6e0597f7ab06e074318a8b5bba7809a8c84df47c2be79c599dc0f55f5 10302 mesa_24.0.3-1_source.buildinfo Files: 4203618cd314f32408d93714570af909 5620 graphics optional mesa_24.0.3-1.dsc 95ad2523e7b480e8f21e5f8b3b37e598 32867503 graphics optional mesa_24.0.3.orig.tar.gz 691e102fd47bcd7978fed81ba3493cb2 117589 graphics optional mesa_24.0.3-1.diff.gz 17f77795db79d2d62524212b2c2ddfaa 10302 graphics optional mesa_24.0.3-1_s
Processed: Re: Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard
Processing control commands: > forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613 Bug #1064123 [libgl1-mesa-dri] libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613'. -- 1064123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1066382: xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-fu
Processing control commands: > forwarded -1 > https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569 Bug #1066382 [src:xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declaration] Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569'. -- 1066382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1020873 [src:xserver-xorg-video-glide] xserver-xorg-video-glide: reproducible-builds: build path embedded in glide_drv.so Severity set to 'wishlist' from 'normal' -- 1020873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed:
Processing control commands: > severity -1 wishlist Bug #1020715 [src:xserver-xorg-input-joystick] xserver-xorg-input-joystick: reproducible-builds: Embedded build path in joystick_drv.so Severity set to 'wishlist' from 'normal' -- 1020715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 1066112 12.0.1-1 Bug #1066112 [src:weston] weston: Enable support to libseat launcher in weston 10 Marked as fixed in versions weston/12.0.1-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 1066112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065551: marked as done (spirv-headers: please update to commit b73e168ca5e123dcf3dea8a34b19a5130f421ae1 or later)
Your message dated Tue, 12 Mar 2024 16:50:25 + with message-id and subject line Bug#1065551: fixed in spirv-headers 1.6.1+1.3.275.0+git20240228-1 has caused the Debian Bug report #1065551, regarding spirv-headers: please update to commit b73e168ca5e123dcf3dea8a34b19a5130f421ae1 or later 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.) -- 1065551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spirv-headers Version: 1.6.1+1.3.275.0-1 Severity: wishlist Hi, spirv-llvm-translator upstream just had in its llvm_release_180 branch a commit (d970c9126c033ebcbb7187bc705eae2e54726b74) pushed that bumps the header dependency to b73e168ca5e123dcf3dea8a34b19a5130f421ae1 for using SPV_INTEL_maximum_registers. This will be part of the 18.0.0 release soon and in order to package that we need some newer spirv-headers packaged, too. AFAICS there is no new spirv-headers tag yet that includes this commit. Thanks Andreas --- End Message --- --- Begin Message --- Source: spirv-headers Source-Version: 1.6.1+1.3.275.0+git20240228-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of spirv-headers, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated spirv-headers 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: Tue, 12 Mar 2024 18:08:31 +0200 Source: spirv-headers Built-For-Profiles: noudeb Architecture: source Version: 1.6.1+1.3.275.0+git20240228-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1065551 Changes: spirv-headers (1.6.1+1.3.275.0+git20240228-1) unstable; urgency=medium . * New upstream snapshot. (Closes: #1065551) Checksums-Sha1: 581a9608b60b2cc67c3cd0601ad691688a0450e2 2088 spirv-headers_1.6.1+1.3.275.0+git20240228-1.dsc af079df929b2e16f33d9d64e6f8120dbfa8efb73 457056 spirv-headers_1.6.1+1.3.275.0+git20240228.orig.tar.gz a1e05437e7c5a6055b7fa69ef13f4a33d7678282 3316 spirv-headers_1.6.1+1.3.275.0+git20240228-1.debian.tar.xz cb955f6e7a5262406f4fe01e9bc76a364d7dc5bc 8178 spirv-headers_1.6.1+1.3.275.0+git20240228-1_source.buildinfo Checksums-Sha256: 357678ef0feeb6dc98efc21c5cbc1052fdd3db1aa42f062d230d431654a4ff73 2088 spirv-headers_1.6.1+1.3.275.0+git20240228-1.dsc ab0bef030fbdda4d67a2d4c00e9bac30ee34e6f060458a2756d88682ef2db005 457056 spirv-headers_1.6.1+1.3.275.0+git20240228.orig.tar.gz b0690c186f8b42cdfc9c0d11e5d7f9b0829f4d991fba08b857b931341a6ed302 3316 spirv-headers_1.6.1+1.3.275.0+git20240228-1.debian.tar.xz 8afcd7ea9b584c3b0f11d0d62c10861ff2112c34e62e95bf76dc65d1412a9869 8178 spirv-headers_1.6.1+1.3.275.0+git20240228-1_source.buildinfo Files: e6bd0429291dce797433ad25244fc48b 2088 libdevel optional spirv-headers_1.6.1+1.3.275.0+git20240228-1.dsc e6138ae8660c0ff4cb260ff4cd8906ad 457056 libdevel optional spirv-headers_1.6.1+1.3.275.0+git20240228.orig.tar.gz 949b955ac3d4509cf334cabbcabfed8a 3316 libdevel optional spirv-headers_1.6.1+1.3.275.0+git20240228-1.debian.tar.xz 37de63cfd4bee8ef4a3f58b183c0c84e 8178 libdevel optional spirv-headers_1.6.1+1.3.275.0+git20240228-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmXwfgwACgkQy3AxZaiJ hNw4ahAAiG2CiirdumVPqao45X4Ntt7skVs9Ry6q77bLC4ilyPKuSeNRct8Ca25a OzcwDVT+oT9Q6/ogzYJzD65aGIGSGM77a4uKKLMrrnZp44HSEjCLv5S/ugJMbzpg GYQ5EO8wG95QgwsAzf1PQT7yrgd+W81z5MOLwfBM+lNGK1RxwI9ViJhrT5RzrC3F Qv0+zeXw44eel/iKOi03UFlt28MZFJbqyHkRJ1jYQvGa8NGzv/42SVwpUn4c3XAE Er98dDqApqtnL6bHsveXCOyI0VNjdExCzLdR6699ligUJAo4o/WpznyCqTClLA4Y aqKdHma5yvyo1/rnStAo02HJCbFHmFz2+8I4cGGnXuW64ECZFxxzfE8FkkaNvcuY faEMD2Keq3OMEFjwKHS2xuvLq54EBSQ0B5zS6fBqvJ72Qx08xAHKq1IHR+fOrIor s+R3iyW5qQLfIODEt80zc5A4QsOCh2pL5hKRNao1sYTCUDbBRCfhLFUhBYUK7U3x tbXQLUXEyiVr2TU3kn55ej/R21ZLB/MipdP1PhfXRWwvUPDiIWJ/yfHcA2dpiyX7 8UmCl6DsCPMEGPiO2uQtS+c5HeQwUmiU+C0jycuT8ahG7t1Idd/+l570SIzLmP2D u8xG/rmI37aJlXPee+Txwbdit4lJi2EO8VMNSSXfVB/vg2jetuc= =LKqR -END PGP SIGNATURE
Processed: Re: Bug#1066095: llvm-18 is available in unstable, please also build spirv-llvm-translator-18 in unstable
Processing control commands: > block -1 with 1065551 Bug #1066095 [src:spirv-llvm-translator-18] llvm-18 is available in unstable, please also build spirv-llvm-translator-18 in unstable 1066095 was not blocked by any bugs. 1066095 was not blocking any bugs. Added blocking bug(s) of 1066095: 1065551 > severity 1065551 important Bug #1065551 [src:spirv-headers] spirv-headers: please update to commit b73e168ca5e123dcf3dea8a34b19a5130f421ae1 or later Severity set to 'important' from 'wishlist' -- 1065551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065551 1066095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1038447
Processing commands for cont...@bugs.debian.org: > tags 1038447 - help Bug #1038447 [libpixman-1-0] librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022 Removed tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022
Processing control commands: > tags -1 + fixed-upstream Bug #1038447 [libpixman-1-0] librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022 Added tag(s) fixed-upstream. > block -1 by 1061616 Bug #1038447 [libpixman-1-0] librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022 1038447 was not blocked by any bugs. 1038447 was not blocking any bugs. Added blocking bug(s) of 1038447: 1061616 > retitle 1061616 pixman: New upstream version 0.43.4 Bug #1061616 [src:pixman] New upstream version 0.43.0 Changed Bug title to 'pixman: New upstream version 0.43.4' from 'New upstream version 0.43.0'. -- 1038447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038447 1061616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065816: marked as done (weston: Dependency neatvnc found: NO found 0.8.0 but need: '< 0.8.0' ; matched: '>= 0.7.0')
Your message dated Mon, 11 Mar 2024 11:46:39 + with message-id and subject line Bug#1065816: fixed in weston 13.0.0-5 has caused the Debian Bug report #1065816, regarding weston: Dependency neatvnc found: NO found 0.8.0 but need: '< 0.8.0' ; matched: '>= 0.7.0' 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.) -- 1065816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: weston Version: 13.0.0-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, weston fails to build in unstable since the upload of neatvnc in version 8.0. From my build log on amd64: | Determining dependency 'neatvnc' with pkg-config executable '/usr/bin/pkg-config' | env[PKG_CONFIG_PATH]: | env[PKG_CONFIG]: /usr/bin/pkg-config | --- | Called: `/usr/bin/pkg-config --modversion neatvnc` -> 0 | stdout: | 0.8.0 | --- | env[PKG_CONFIG_PATH]: | env[PKG_CONFIG]: /usr/bin/pkg-config | --- | Called: `/usr/bin/pkg-config --cflags neatvnc` -> 0 | stdout: | -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/p11-kit-1 -I/usr/include/x86_64-linux-gnu | --- | env[PKG_CONFIG_ALLOW_SYSTEM_LIBS]: 1 | env[PKG_CONFIG_PATH]: | env[PKG_CONFIG]: /usr/bin/pkg-config | --- | Called: `/usr/bin/pkg-config --libs neatvnc` -> 0 | stdout: | -L/usr/lib/x86_64-linux-gnu -lneatvnc | --- | env[PKG_CONFIG_PATH]: | env[PKG_CONFIG]: /usr/bin/pkg-config | --- | Called: `/usr/bin/pkg-config --libs neatvnc` -> 0 | stdout: | -lneatvnc | --- | Dependency neatvnc found: NO found 0.8.0 but need: '< 0.8.0' ; matched: '>= 0.7.0' | CMake binary for host machine is cached as not found | CMake binary for machine host machine not found. Giving up. | Run-time dependency neatvnc found: NO (tried pkgconfig and cmake) | Looking for a fallback subproject for the dependency neatvnc | Automatic wrap-based subproject downloading is disabled | Subproject neatvnc is buildable: NO (disabling) | Dependency neatvnc from subproject neatvnc found: NO (subproject failed to configure) | | ../libweston/backend-vnc/meson.build:8:1: ERROR: Problem encountered: VNC backend requires neatvnc which was not found. Or, you can use '-Dbackend-vnc=false'. | dh_auto_configure: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 -Dbackend-rdp=true -Dbackend-vnc=true -Dscreenshare=true -Dsystemd=true returned exit code 1 | make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:44: binary] Error 2 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 A full build log is also available here: https://buildd.debian.org/status/fetch.php?pkg=weston=riscv64=13.0.0-4%2Bb2=1710049432=0 Regards Aurelien --- End Message --- --- Begin Message --- Source: weston Source-Version: 13.0.0-5 Done: Dylan Aïssi We believe that the bug you reported is fixed in the latest version of weston, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated weston 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, 11 Mar 2024 12:01:23 +0100 Source: weston Architecture: source Version: 13.0.0-5 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Dylan Aïssi Closes: 1065816 Changes: weston (13.0.0-5) unstable; urgency=medium . * Don't install disabled features on ia64 and sparc64 * Do not check the upper limit for neatvnc version (Closes: #1065816) Checksums-Sha1: 2ad657f3a81e0d8ab1b94e8566dd91b9d0c3d5c1 3347 weston_13.0.0-5.dsc c25d9c064d61f1aa7b3d6010aacac57cda16b108 25804 weston_13.0.0-5.debian.tar.xz 27be934d5bf957002e75199f1d52ff4c2a74a878
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > forwarded 1065816 https://gitlab.freedesktop.org/wayland/weston/-/issues/890 Bug #1065816 [src:weston] weston: Dependency neatvnc found: NO found 0.8.0 but need: '< 0.8.0' ; matched: '>= 0.7.0' Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/wayland/weston/-/issues/890'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1065816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1065816: weston: Dependency neatvnc found: NO found 0.8.0 but need: '< 0.8.0' ; matched: '>= 0.7.0'
Processing control commands: > block 1036884 by -1 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was not blocked by any bugs. 1036884 was not blocking any bugs. Added blocking bug(s) of 1036884: 1065816 -- 1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884 1065816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fix ftbfs bug metadata
ign from binary to source > reassign 986494 src:sipxtapi Bug #986494 [sipxtapi] sipxtapi: FTBFS with glibc >= 2.32 Bug reassigned from package 'sipxtapi' to 'src:sipxtapi'. No longer marked as found in versions 3.3.0~test18+dfsg.1-0.1. Ignoring request to alter fixed versions of bug #986494 to the same values previously set > # restore found version after reassign > found 986494 sipxtapi/3.3.0~test18+dfsg.1-0.1 Bug #986494 [src:sipxtapi] sipxtapi: FTBFS with glibc >= 2.32 Marked as found in versions sipxtapi/3.3.0~test18+dfsg.1-0.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000213 1010533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010533 1014512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014512 1020160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020160 1020185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020185 1051985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051985 1064128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064128 1065184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065184 1065214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065214 985813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985813 986494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986494 989391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989391 989392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989392 989395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989395 989399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989399 989533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989533 989804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989804 991213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:glslang: fails to migrate to testing for too long: unresolved RC bug and autopkgtest failure
Processing control commands: > close -1 14.0.0-2 Bug #1065324 [src:glslang] src:glslang: fails to migrate to testing for too long: unresolved RC bug and autopkgtest failure Marked as fixed in versions glslang/14.0.0-2. Bug #1065324 [src:glslang] src:glslang: fails to migrate to testing for too long: unresolved RC bug and autopkgtest failure Marked Bug as done -- 1065324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1062736: marked as done (libxt: NMU diff for 64-bit time_t transition)
Your message dated Fri, 01 Mar 2024 07:38:07 + with message-id and subject line Bug#1062736: fixed in libxt 1:1.2.1-1.2 has caused the Debian Bug report #1062736, regarding libxt: NMU diff for 64-bit time_t transition 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.) -- 1062736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxt Version: 1:1.2.1-1.1 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified libxt as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for libxt which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: libxt Source-Version: 1:1.2.1-1.2 Done: Steve Langasek We believe that the bug you reported is fixed in the latest version of libxt, 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 1062...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated libxt 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: Fri, 01 Mar 2024 07:22:36 + Source: libxt Architecture: source Version: 1:1.2.1-1.2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Steve Langasek Closes: 1062736 Changes: libxt (1:1.2.1-1.2) unstable; urgency=medium . * Non-maintainer upload. * Rename libraries for 64-bit time_t transition. Closes: #1062736 Checksums-Sha1: 7ed5c1c5e005290775b26f76b9d8e64a04260198 2373 libxt_1.2.1-1.2.dsc 5c48620f0353f4ccdd94649959885dafe08254a5 45635 libxt_1.2.1-1.2.diff.gz dc5db8f89f44913c29cdbad477d0a0fa3fce8a4c 8523 libxt_1.2.1-1.2_source.buildinfo Checksums-Sha256: 780be4cf9b0b90757758691dc8196d85322b30a599c36fb8fe368b7060c7b774 2373 libxt_1.2.1-1.2.dsc d4c510871909584398d88552b69cc5e92e124098ce544be93ef1743d0d112d4c 45635 libxt_1.2.1-1.2.diff.gz e9765eec46546f902eaad43ec6b33f1c4d155e8d66e966914f10eba8875f87c7 8523 libxt_1.2.1-1.2_source.buildinfo Files: 1db3581aeda19ce1e91d53b0bdcdd267 2373 x11 optional libxt_1.2.1-1.2.dsc c345c61806138c947c8d19baaf7c8b03 45635 x11 optional libxt_1.2.1-1.2.diff.gz be930db01ef319ad72cfb9c8651edd05 8523 x11 optional libxt_1.2.1
Processed: closing 1063370
Processing commands for cont...@bugs.debian.org: > close 1063370 1.3.275.0+dfsg1-1 Bug #1063370 [src:vulkan-tools] vulkan-tools: Fails to build from source. Marked as fixed in versions vulkan-tools/1.3.275.0+dfsg1-1. Bug #1063370 [src:vulkan-tools] vulkan-tools: Fails to build from source. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1063370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1064547, block 1063143 with 1064547
Processing commands for cont...@bugs.debian.org: > affects 1064547 + src:filament Bug #1064547 [glslang-dev] glslang-dev: no longer shipping intermediate.h (among others) Added indication that 1064547 affects src:filament > block 1063143 with 1064547 Bug #1063143 [src:filament] filament: FTBFS on armel: fatal error: 'localintermediate.h' file not found 1063143 was not blocked by any bugs. 1063143 was not blocking any bugs. Added blocking bug(s) of 1063143: 1064547 > thanks Stopping processing here. Please contact me if you need assistance. -- 1063143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063143 1064547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1061888 is serious, severity of 1061920 is serious, severity of 1062060 is serious ...
Processing commands for cont...@bugs.debian.org: > # time_t transition started > severity 1061888 serious Bug #1061888 [src:anfo] anfo: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1061920 serious Bug #1061920 [src:arrayfire] arrayfire: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062060 serious Bug #1062060 [src:cinnamon-desktop] cinnamon-desktop: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062095 serious Bug #1062095 [src:colord-gtk] colord-gtk: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062125 serious Bug #1062125 [src:gimp] gimp: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062308 serious Bug #1062308 [src:libgda5] libgda5: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062309 serious Bug #1062309 [src:libgdamm5.0] libgdamm5.0: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062318 serious Bug #1062318 [src:libgom] libgom: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062360 serious Bug #1062360 [src:libgweather4] libgweather4: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062363 serious Bug #1062363 [src:libgxps] libgxps: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062502 serious Bug #1062502 [src:kseexpr] kseexpr: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062633 serious Bug #1062633 [src:libsoup2.4] libsoup2.4: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062674 serious Bug #1062674 [src:lua-compat53] lua-compat53: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062723 serious Bug #1062723 [src:qt6-3d] qt6-3d: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062747 serious Bug #1062747 [src:qt6-declarative] qt6-declarative: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062748 serious Bug #1062748 [src:link-grammar] link-grammar: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062749 serious Bug #1062749 [src:qt6-tools] qt6-tools: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062750 serious Bug #1062750 [src:qt6-virtualkeyboard] qt6-virtualkeyboard: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062751 serious Bug #1062751 [src:qt6-wayland] qt6-wayland: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062758 serious Bug #1062758 [src:qt6-webengine] qt6-webengine: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062759 serious Bug #1062759 [src:qt6-websockets] qt6-websockets: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062760 serious Bug #1062760 [src:qtquickcontrols2-opensource-src] qtquickcontrols2-opensource-src: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062762 serious Bug #1062762 [src:qtsystems-opensource-src] qtsystems-opensource-src: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062763 serious Bug #1062763 [src:qttools-opensource-src] qttools-opensource-src: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062764 serious Bug #1062764 [src:qtwayland-opensource-src] qtwayland-opensource-src: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062766 serious Bug #1062766 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062873 serious Bug #1062873 [src:ruby3.1] ruby3.1: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062927 serious Bug #1062927 [src:stellarsolver] stellarsolver: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1062940 serious Bug #1062940 [src:qtbase-opensource-src-gles] qtbase-opensource-src-gles: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1063053 serious Bug #1063053 [src:volume-key] volume-key: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1063055 serious Bug #1063055 [src:vowpal-wabbit] vowpal-wabbit: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > severity 1063077 serious Bug #1063077
Processed: block 1064681 with 1062799
Processing commands for cont...@bugs.debian.org: > block 1064681 with 1062799 Bug #1064681 [src:retroarch] retroarch: FTBFS: glslang is disabled and forced to build with SPIRV-Cross support. 1064681 was not blocked by any bugs. 1064681 was not blocking any bugs. Added blocking bug(s) of 1064681: 1062799 > thanks Stopping processing here. Please contact me if you need assistance. -- 1064681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fix ftbfs/ftcbfs bug metadata
.cgi?bug=1061327 1063370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063370 1063601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063601 1064034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064034 998258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1054709
Processing commands for cont...@bugs.debian.org: > close 1054709 1.3.275.0-1 Bug #1054709 [src:vulkan-validationlayers] vulkan-validationlayers: FTBFS: gpu_validation.cpp:959:55: error: too many arguments to function ‘spvtools::Optimizer::PassToken spvtools::CreateInstBindlessCheckPass(uint32_t, uint32_t)’ Marked as fixed in versions vulkan-validationlayers/1.3.275.0-1. Bug #1054709 [src:vulkan-validationlayers] vulkan-validationlayers: FTBFS: gpu_validation.cpp:959:55: error: too many arguments to function ‘spvtools::Optimizer::PassToken spvtools::CreateInstBindlessCheckPass(uint32_t, uint32_t)’ Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1054709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard
Processing control commands: > severity -1 grave Bug #1064123 [libgl1-mesa-dri] libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard Severity set to 'grave' from 'important' -- 1064123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: vulkan-tools: Fails to build from source.
Processing control commands: > tag -1 upstream fixed-upstream Bug #1063370 [vulkan-tools] vulkan-tools: Fails to build from source. Added tag(s) upstream and fixed-upstream. -- 1063370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063725: marked as done (xkb-data: keymap alias 'dvorak' no longer available)
Your message dated Tue, 13 Feb 2024 08:44:18 +
with message-id
and subject line Bug#1063725: fixed in xkeyboard-config 2.41-2
has caused the Debian Bug report #1063725,
regarding xkb-data: keymap alias 'dvorak' no longer available
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.)
--
1063725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xkb-data
Version: 2.41-1
Dear Maintainer,
I noticed a "setxkbmap dvorak" command, run by my X session scripts,
starting giving an error with the latest xkb-data:
Error loading new keyboard description
It started after upgrading the following 4 packages together:
console-setup:amd64 (1.223, 1.226)
console-setup-linux:amd64 (1.223, 1.226)
xkb-data:amd64 (2.38-2, 2.41-1),
keyboard-configuration:amd64 (1.223, 1.226)
(The xkb-data changes look the most substantial, which is why I've filed
against that package.)
My keyboard layout was still as expected, but downgrading those packages
to the versions from 'testing' eliminated the error.
Here's the output of "setxkbmap -verbose 10 -print dvorak" with 2.38-2:
Setting verbose level to 10
locale is C
Warning! Multiple definitions of keyboard layout
Using command line, ignoring X server
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: pc105
layout: dvorak
options:ctrl:swapcaps,compose:menu
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols:pc+us(dvorak)+inet(evdev)+ctrl(swapcaps)+compose(menu)
geometry: pc(pc105)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ include "complete" };
xkb_symbols { include
"pc+us(dvorak)+inet(evdev)+ctrl(swapcaps)+compose(menu)"};
xkb_geometry { include "pc(pc105)" };
};
And with 2.41-1:
Setting verbose level to 10
locale is C
Warning! Multiple definitions of keyboard layout
Using command line, ignoring X server
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: pc105
layout: dvorak
options:ctrl:swapcaps,compose:menu
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols:pc+dvorak+inet(evdev)+ctrl(swapcaps)+compose(menu)
geometry: pc(pc105)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ include "complete" };
xkb_symbols { include
"pc+dvorak+inet(evdev)+ctrl(swapcaps)+compose(menu)"};
xkb_geometry { include "pc(pc105)" };
};
The contents of /etc/default/keyboard:
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT="dvorak"
XKBOPTIONS="ctrl:swapcaps"
BACKSPACE="guess"
My X session was configured to run this command at startup:
setxkbmap -option 'ctrl:swapcaps' -option 'compose:menu' dvorak
After looking at the above output, I changed "dvorak" to "us(dvorak)" in
the command, and it worked without error.
It's not clear whether support for just "dvorak" was dropped on purpose,
but I don't recall seeing any deprecation warnings about it, and don't
see any relevant Debian changelog or "NEWS" entry.
- Michael
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1,
'experimental')
Architecture: amd64 (x86_64)
Ke
Bug#1063702: marked as done (xkb-data: german keyboard config fails)
Your message dated Tue, 13 Feb 2024 08:44:18 + with message-id and subject line Bug#1063702: fixed in xkeyboard-config 2.41-2 has caused the Debian Bug report #1063702, regarding xkb-data: german keyboard config fails 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.) -- 1063702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xkb-data Version: 2.41-1 Severity: important Dear Maintainer(s), a german-greek keyboard configuration fails after upgrading from version 2.38-2. The config file "/etc/default/keyboard" contains: XKBMODEL="pc105" XKBLAYOUT="de,gr" XKBVARIANT="nodeadkeys,extended" XKBOPTIONS="grp:lwin_toggle,grp_led:scroll" BACKSPACE="guess" (comment lines removed). In "/var/log/Xorg.log" it says: [ 2467.320] (EE) Error loading keymap /tmp/server-0.xkm [ 2467.320] (EE) XKB: Failed to load keymap. Loading default keymap instead. Any idea? Regards, Jörg. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.3 (SMP w/16 CPU threads) Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) -- no debconf information --- End Message --- --- Begin Message --- Source: xkeyboard-config Source-Version: 2.41-2 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of xkeyboard-config, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated xkeyboard-config 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: Tue, 13 Feb 2024 10:04:05 +0200 Source: xkeyboard-config Built-For-Profiles: noudeb Architecture: source Version: 2.41-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1063702 1063725 Changes: xkeyboard-config (2.41-2) unstable; urgency=medium . * Update NEWS. (Closes: #1063725, #1063702) Checksums-Sha1: 21ef77f317691ca57b5944014e288f9c63af18b8 2112 xkeyboard-config_2.41-2.dsc 46a884f3c69d535c99f210a6e78d292be9ff5905 37632 xkeyboard-config_2.41-2.diff.gz b0dbb9861f7f76dfd487d663c3f8ba339b3aceb9 7629 xkeyboard-config_2.41-2_source.buildinfo Checksums-Sha256: 8c99206283e2faa2d8687e13c326f5a2c623b50d85f72ede8719178acb4424ca 2112 xkeyboard-config_2.41-2.dsc 7151114f1cc727e7879f6b9a2acb603847bdb3e3e192b09557ce40e63c15d528 37632 xkeyboard-config_2.41-2.diff.gz df632ce0a829f4acd109cb78be73df93ffeaf102f86a39f4da4b15d566f51bca 7629 xkeyboard-config_2.41-2_source.buildinfo Files: f6b65ed8875c9aed0c45a2f60ab4d636 2112 x11 optional xkeyboard-config_2.41-2.dsc ddcae14e47d96b379bab19c45c456182 37632 x11 optional xkeyboard-config_2.41-2.diff.gz 6e41d2c28bd10af3768fbe9cd2f2ebda 7629 x11 optional xkeyboard-config_2.41-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmXLIr8ACgkQy3AxZaiJ hNy0iw//R52WKn98vsg8X8uOId/dJOEi+uvtd0JhtyIyOkbQHfAAmBFFz7pMIldd 7sdQv5H4+oApXORTMfvt1bdJHyn9nSm7yNInqhENnHeSUyaEDr04BaUB1jW4DhYL vHQ6unhBHE5SH41O4bUkTvsC5WNRQ+P1SSBWA3Y0Xod85GtOl9BoftowrtNuODcR AwwmnQoFRGzIinPzM3f2CgEkRBg+4t7rvp6rX3/MtnRSoIOLdYi2xvBiwSnyQgwZ cwtf453eQ3NuelM7mvoVdj1wRKjJwRpJgpxMpcVAbKUzeRi1KP43TtrGfZ0Ffm2k s0RXGFV38mGwnMFi8ajEBrF0Or8hsOKlT40wv89qm/OEF6LI8HKRD6zxF/e46lqw fe8zcCVrPPMV0qdXgpsEkPR6iOQB2O4lGkG4q3pgL8OUpzdD38Cqzgl5NWyfWa8z OJ2R9a5WqI/ZA4LVQrkp98+IbH9TM6P8nabiIbZt0MeL+1mTjWhNkdcRBBEamWRp iND+jDTALHkqm0AdwLqva5JNX0y9mg/FJmnqC1OfgjVGbc08Y+j2Z+wbguEn0y86 Qli3c+YY86bCxEjC1Gh1SpjTkv07QveEvWDSPAm7jmxgpf442ZZg55Mj14h7PQl2 T2gtZhndYuevsWJ/Ddx7sTutShadN5XL3I860t62Q6/mu9PUUZQ= =uTAQ -END PGP SIGNATURE- pgp_6LB_TYlG7.pgp Description: PGP signature --- End Message ---
Processed: Re: Bug#1063702: xkb-data: german keyboard config fails
Processing commands for cont...@bugs.debian.org: > package xkb-data Limiting to bugs with field 'package' containing at least one of 'xkb-data' Limit currently set to 'package':'xkb-data' > tag 1063702 + upstream Bug #1063702 [xkb-data] xkb-data: german keyboard config fails Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1063702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1061866, tagging 1061872, tagging 1061873, tagging 1061874, tagging 1061875, tagging 1061878 ...
Processing commands for cont...@bugs.debian.org:
> tags 1061866 + sid trixie
Bug #1061866 [src:adns] adns: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061872 + sid trixie
Bug #1061872 [src:adolc] adolc: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061873 + sid trixie
Bug #1061873 [src:afflib] afflib: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061874 + sid trixie
Bug #1061874 [src:colpack] colpack: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061875 + sid trixie
Bug #1061875 [src:afterstep] afterstep: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061878 + sid trixie
Bug #1061878 [src:agg] agg: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061881 + sid trixie
Bug #1061881 [src:akonadi-search] akonadi-search: NMU diff for 64-bit time_t
transition
Added tag(s) trixie and sid.
> tags 1061883 + sid trixie
Bug #1061883 [src:alberta] alberta: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061889 + sid trixie
Bug #1061889 [src:angelscript] angelscript: NMU diff for 64-bit time_t
transition
Added tag(s) sid and trixie.
> tags 1061890 + sid trixie
Bug #1061890 [src:anthy] anthy: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061891 + sid trixie
Bug #1061891 [src:apbs] apbs: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061892 + sid trixie
Bug #1061892 [src:apophenia] apophenia: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061893 + sid trixie
Bug #1061893 [src:apr-util] apr-util: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061894 + sid trixie
Bug #1061894 [src:apr] apr: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061897 + sid trixie
Bug #1061897 [src:aribb24] aribb24: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061900 + sid trixie
Bug #1061900 [src:comedilib] comedilib: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061901 + sid trixie
Bug #1061901 [src:compiz] compiz: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061903 + sid trixie
Bug #1061903 [src:coolkey] coolkey: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061905 + sid trixie
Bug #1061905 [src:cpp-hocon] cpp-hocon: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061908 + sid trixie
Bug #1061908 [src:cppdb] cppdb: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061909 + sid trixie
Bug #1061909 [src:croaring] croaring: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061911 + sid trixie
Bug #1061911 [src:csmith] csmith: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061913 + sid trixie
Bug #1061913 [src:ctpl] ctpl: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061914 + sid trixie
Bug #1061914 [src:cuneiform] cuneiform: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061915 + sid trixie
Bug #1061915 [src:cups-filters] cups-filters: NMU diff for 64-bit time_t
transition
Added tag(s) sid and trixie.
> tags 1061921 + sid trixie
Bug #1061921 [src:asl] asl: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061922 + sid trixie
Bug #1061922 [src:astrometry.net] astrometry.net: NMU diff for 64-bit time_t
transition
Added tag(s) trixie and sid.
> tags 1061928 + sid trixie
Bug #1061928 [src:avro-c] avro-c: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061929 + sid trixie
Bug #1061929 [src:bamf] bamf: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061932 + sid trixie
Bug #1061932 [src:blitz++] blitz++: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061934 + sid trixie
Bug #1061934 [src:boinc] boinc: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061943 + sid trixie
Bug #1061943 [src:forge] forge: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061945 + sid trixie
Bug #1061945 [src:fpgatools] fpgatools: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061953 + sid trixie
Bug #1061953 [src:freewnn] freewnn: NMU diff for 64-bit time_t transition
Added tag(s) sid and trixie.
> tags 1061954 + sid trixie
Bug #1061954 [src:frog] frog: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061955 + sid trixie
Bug #1061955 [src:fsplib] fsplib: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061957 + sid trixie
Bug #1061957 [src:funtools] funtools: NMU diff for 64-bit time_t transition
Added tag(s) trixie and sid.
> tags 1061961 + sid trixie
Bug #1061961 {Done: Bas Couwenberg } [src:fyba] fyba: NMU
diff for 64-bit
Bug#1059782: marked as done (mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter)
Your message dated Thu, 01 Feb 2024 08:52:21 + with message-id and subject line Bug#1059782: fixed in mesa 24.0.0-1 has caused the Debian Bug report #1059782, regarding mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter 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.) -- 1059782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mesa-vdpau-drivers Version: 23.3.1-4 Severity: important Dear Maintainer, Upgrading from 23.2.1-1 to any 23.3.* version breaks video rendering in Python tkinter-based applications. I'm embedding a python-vlc media player in tkinter to play videos. Playback is fine when using 23.2.1-1 or older. However, after upgrading to any 23.3.* version, a black square is displayed where the video output should be. Playback is occurring, as audio can be heard. I tracked the issue to the mesa packages, but I don't know how to debug this further or identify the binary package causing the issue. I'll attach a simple test case. Please install python3-tk and python3-vlc. -- Package-specific info: glxinfo: name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_get_drawable_type, GLX_EXT_libglvnd, GLX_EXT_no_config_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_no_config_context, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_gl_interop, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_NV_float_buffer, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_no_config_context, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_gl_interop, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_video_sync Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x15ad) Device: SVGA3D; build: RELEASE; LLVM; (0x405) Version: 23.3.1 Accelerated: no Video memory: 1MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.1 Max compat profile version: 4.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 OpenGL vendor string: VMware, Inc. OpenGL renderer string: SVGA3D; build: RELEASE; LLVM; OpenGL core profile version string: 4.1 (Core Profile) Mesa 23.3.1-4 OpenGL core profile shading language version string: 4.10 OpenGL core profile context flags: (none
Processed: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
Processing commands for cont...@bugs.debian.org: > package mesa-vdpau-drivers Limiting to bugs with field 'package' containing at least one of 'mesa-vdpau-drivers' Limit currently set to 'package':'mesa-vdpau-drivers' > fixed 1059782 24.0.0~rc1-1 Bug #1059782 [mesa-vdpau-drivers] mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter Marked as fixed in versions mesa/24.0.0~rc1-1. > forwarded 1059782 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10468 Bug #1059782 [mesa-vdpau-drivers] mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/mesa/mesa/-/issues/10468'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061768: marked as done (vulkan-loader: new upstream release 1.3.275.0)
Your message dated Tue, 30 Jan 2024 11:58:58 + with message-id and subject line Bug#1061768: fixed in vulkan-loader 1.3.275.0-1 has caused the Debian Bug report #1061768, regarding vulkan-loader: new upstream release 1.3.275.0 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.) -- 1061768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vulkan-loader Version: 1.3.268.0-1 Severity: wishlist A new upstream release vulkan-sdk-1.3.275.0 is available. smcv --- End Message --- --- Begin Message --- Source: vulkan-loader Source-Version: 1.3.275.0-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of vulkan-loader, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated vulkan-loader 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: Tue, 30 Jan 2024 13:29:31 +0200 Source: vulkan-loader Built-For-Profiles: noudeb Architecture: source Version: 1.3.275.0-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1061768 Changes: vulkan-loader (1.3.275.0-1) unstable; urgency=medium . * New upstream release. (Closes: #1061768) * rules: Create loader/generated if it doesn't exist. Checksums-Sha1: 3a12eee216227995e4bed3033e883c99366dd1ba 2252 vulkan-loader_1.3.275.0-1.dsc 7295569482af305619609300bb2468a21fb39ac3 2642760 vulkan-loader_1.3.275.0.orig.tar.xz 8286013148b3c52824979e8b2fb03d9594c4c237 9012 vulkan-loader_1.3.275.0-1.debian.tar.xz 0f49348fc399275140b33df31365f23a700883f4 8854 vulkan-loader_1.3.275.0-1_source.buildinfo Checksums-Sha256: daf53ed7e6784e9b8e6dca6c18cdf1ba9b67fdc4dd75e39e9a57fa2e9eb7d443 2252 vulkan-loader_1.3.275.0-1.dsc 5f95219fc189b4c09ce537d8ec1ea4b5861b087cd00b6d821f99aecf6e9dddce 2642760 vulkan-loader_1.3.275.0.orig.tar.xz 99fb9e65b015b2e9e9c693b58c1326ad2f419930831bc45d3f6b1ce76fb832c6 9012 vulkan-loader_1.3.275.0-1.debian.tar.xz e8c2b6e80f323d00a99aecb195a09764666192255f2f634ffb547f4b1db1e6bc 8854 vulkan-loader_1.3.275.0-1_source.buildinfo Files: bd600148c0caab775429ae3115d71376 2252 libs optional vulkan-loader_1.3.275.0-1.dsc 6d1907a69c5218d29b917c7700fd7fc2 2642760 libs optional vulkan-loader_1.3.275.0.orig.tar.xz c269222b5832d137951824ac8f97c910 9012 libs optional vulkan-loader_1.3.275.0-1.debian.tar.xz 3dc17beca03cd3255b849de54fd99fa7 8854 libs optional vulkan-loader_1.3.275.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmW43csACgkQy3AxZaiJ hNzhqBAAgbl0JNX9HtNDEimldT7+ieAVdMtJrqdj6At3Zno6olaaGFnQD/b9Jydv E9xeyUdcwSP9Do2GXOhplRWH4hoZkMc/dtsDqOdrQi0oGLOez2NH2Ue1AulvGoQH oFJR6UXZQzmrSd8+q54aJg85ezxw5UaxdJXCT700IKeqAXtZOoaLqIM9zwuo8WBk WqqQQM68JR+gm0OTshwNwLlRUWlHlKYKTf85924Wu7XFmQYvJdx3F+5sCRAbvjIn dCI71lF/zep+LS9pBDX305UqespMVUABkgyCuexde5cuACM6JgocU1xrObZrqKC7 gP2XUbK/XfpA+1pwfADLViNOnga71/VpqljN5iGdf1bkLBW/EMDG2aNb2x9inwb2 VMdJO1DSvWhwbxhrpWj/u4XYDgvBaQhlv9gLzO/1a3OrubyuqIbJbwBRw4gFIaEe 65/BwWFSgGPFZ76+kImuXv2ysap+vOit9/4ny0URRNpnctVaA0qS2KQ9AfaCC388 3HdfvTX0VJkbOPMOLaOeW51ShcGlaGCx9rOSTUfFyBrd8ASucjcIdnm4yJrlgamP qY7DRksYgfcIZyrQkePTNqVtxLBUx/IQYqJiFY/JehAxV5Bg13h/D32ag1HnvvRt ILyJoNCROh2vU7O8h4fpOIRpcAjWXE0dfSc1NpSE0my23N0oFWU= =jepR -END PGP SIGNATURE End Message ---
Bug#1058218: marked as done (libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned e
Your message dated Mon, 29 Jan 2024 17:57:47 -0500 with message-id and subject line re: libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1 has caused the Debian Bug report #1058218, regarding libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1 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.) -- 1058218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libei Version: 1.2.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test -- --timeout-multiplier 2 > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 > MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 > ninja: Entering directory `/<>/obj-x86_64-linux-gnu' > ninja: no work to do. > 1/10 libei / unit-tests-utilsOK 0.04s > 2/10 libei / unit-tests-ei OK 0.03s > 3/10 libei / unit-tests-eis OK 0.03s > 4/10 libei / unit-tests-oeffis OK 0.03s > 5/10 libei:nosigalrm / eierpecken-no-sigalrm OK 0.54s > 6/10 libei:python / python-black OK 0.68s > 7/10 libei:python / scanner-pytest OK 0.75s > 8/10 libei:python / oeffis-pytestOK 2.79s > 9/10 libei:python / protocol-testOK 6.81s > 10/10 libei:sigalrm / eierpecken TIMEOUT60.02s killed > by signal 15 SIGTERM > >>> MALLOC_PERTURB_=137 > >>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 > >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 > >>> > >>> LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/subprojects/munit:/<>/obj-x86_64-linux-gnu/src > >>> /<>/obj-x86_64-linux-gnu/test/eierpecken --log-visible > >>> debug --enable-sigalarm > > > Ok: 9 > Expected Fail: 0 > Fail: 0 > Unexpected Pass:0 > Skipped:0 > Timeout:1 > > Full log written to > /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt > ==> meson-logs/testlog.txt <== > Log of Meson test suite run on 2023-12-11T19:27:35.378286 > > Inherited environment: SCHROOT_GID=1001 DEB_HOST_MULTIARCH=x86_64-linux-gnu > LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu > DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_LDFLAGS_MAINT_APPEND='-Wl,-O1 > -Wl,-z,defs' DEB_TARGET_ARCH_LIBC=gnu FFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -fcf-protection' DEB_BUILD_ARCH_ENDIAN=little > DEB_BUILD_GNU_SYSTEM=linux-gnu CFLAGS_FOR_BUILD='-g -O2' > OBJCXXFLAGS_FOR_BUILD='-g -O2' DEB_BUILD_ARCH_BITS=64 > DEB_BUILD_OPTIONS=parallel=8 DEB_HOST_ARCH=amd64 LDFLAGS_FOR_BUILD='' > DEB_TARGET_ARCH_ENDIAN=little SOURCE_DATE_EPOCH=1701821063 > OBJCFLAGS_FOR_BUILD='-g -O2' OBJCXXFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' > DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS=w SCHROOT_GROUP=user42 > DEB_TARGET_ARCH=amd64 DPKG_GENSYMBOLS_CHECK_LEVEL=4 DH_INTERNAL_OPTIONS='' > DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu MFLAGS=-w > DEB_TARGET_ARCH_BITS=64 CXXFLAGS_FOR_BUILD='-g -O2' ASFLAGS='' > DEB_BUILD_ARCH_CPU=amd64 LC_COLLATE=C.UTF-8 SCHROOT_ALIAS_NAME=unstable > DEB_HOST_ARCH_OS=linux SHELL=/bin/sh FCFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -fcf-protection' DEB_HOST_ARCH_CPU=amd64 > SCHROOT_USER=user42 > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > DEB_BUILD_ARC
Processed: Re: Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022
Processing control commands: > reassign -1 libpixman-1-0 0.42.2-1 Bug #1038447 [src:librsvg] librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022 Bug reassigned from package 'src:librsvg' to 'libpixman-1-0'. No longer marked as found in versions librsvg/2.54.5+dfsg-1. Ignoring request to alter fixed versions of bug #1038447 to the same values previously set Bug #1038447 [libpixman-1-0] librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022 Marked as found in versions pixman/0.42.2-1. > affects -1 + librsvg Bug #1038447 [libpixman-1-0] librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022 Added indication that 1038447 affects librsvg > tags -1 + upstream Bug #1038447 [libpixman-1-0] librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022 Added tag(s) upstream. > forwarded -1 https://gitlab.freedesktop.org/pixman/pixman/-/issues/78 Bug #1038447 [libpixman-1-0] librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022 Changed Bug forwarded-to-address to 'https://gitlab.freedesktop.org/pixman/pixman/-/issues/78' from 'https://gitlab.gnome.org/GNOME/librsvg/-/issues/972'. -- 1038447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061535: marked as done (wayland-protocols: Please update to 1.33)
Your message dated Sun, 28 Jan 2024 10:50:04 + with message-id and subject line Bug#1061535: fixed in wayland-protocols 1.33-1 has caused the Debian Bug report #1061535, regarding wayland-protocols: Please update to 1.33 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.) -- 1061535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wayland-protocols Version: 1.32-1 Severity: wishlist wayland-protocols 1.33 has been released and the next version of mutter will be using it. Please package the new version. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: wayland-protocols Source-Version: 1.33-1 Done: Dylan Aïssi We believe that the bug you reported is fixed in the latest version of wayland-protocols, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated wayland-protocols 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: Sun, 28 Jan 2024 11:29:16 +0100 Source: wayland-protocols Architecture: source Version: 1.33-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Dylan Aïssi Closes: 1061535 Changes: wayland-protocols (1.33-1) unstable; urgency=medium . * Team upload. * New upstream release. (Closes: #1061535, LP: #2050856) * Update standards version to 4.6.2, no changes needed. * Convert debian/copyright to DEP5 format. Checksums-Sha1: 9a7fdb695360f54ff06db0c60a35faceb7a6cb3e 2096 wayland-protocols_1.33-1.dsc 847f110ef87b22d42a30612f3b07298a12988c9f 137725 wayland-protocols_1.33.orig.tar.gz 7deb43ea81e9aa39b55d95c8a1293006e706ae3c 5760 wayland-protocols_1.33-1.debian.tar.xz 91fb6c290316676d061650ee564f0c7219ee27c5 7495 wayland-protocols_1.33-1_amd64.buildinfo Checksums-Sha256: 94650b6a32f8a2ed26bb1afda3dcdf698ab6609b4e1e20eb58697ebfa9a4cc29 2096 wayland-protocols_1.33-1.dsc 71a7d2f062d463aa839497ddfac97e4bd3f00aa306e014f94529aa3a2be193a8 137725 wayland-protocols_1.33.orig.tar.gz 78498dd4e415ad17901356b2679e8dc4b9b46c600af6697bad780a6b1695cc9e 5760 wayland-protocols_1.33-1.debian.tar.xz a663cb2399ab2554c575bbe44d200de882e30146d85ef03bfcc680106d3744bf 7495 wayland-protocols_1.33-1_amd64.buildinfo Files: 58c161470ec5b6b647c02f7a5e40de17 2096 x11 optional wayland-protocols_1.33-1.dsc 4b38876fca59f6771e4aa98d3147ad18 137725 x11 optional wayland-protocols_1.33.orig.tar.gz ccb264c6150c073a27b7455398f929de 5760 x11 optional wayland-protocols_1.33-1.debian.tar.xz 125b32c7e8c880fb545bba80ea213bbb 7495 x11 optional wayland-protocols_1.33-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmW2LiEACgkQYS7xYT4F D1S/eg//ffVNyEM1gl/pAPNgaSK1jD94nCaLTumOxWZAnPx5aEXDfaS9Gl08feej cCia7tUk77bvQ7WFvi3z8yoI1RSfngQE65EJ0LzYd2yD7ihx/WtYwMyFOHHMTB/P nKRJz+IHFgsFdKZVlV4nXNRPocjPTZ4QlEGNG1D1FdrHJLqzyO7Wl3eR0wsNIy+S wSW/LyRT/xv+pKtDkwkhVYPzhistbHoN1vSnn9kYjLCcOZgAzpssLO3kP+4YMIJw RK/v3L4Q0V9lJVxrGsQ2zE2Sh4GW4oqihBcPs+nwDYXe+JKHZotQ9kXlyW8GPf6W pPA0yb439Mw2SSH9vtqKzd1XWmJ2QYZYRNWR9tdDUzuwVbLhgcEeqm2iOxl86Ag8 2NNfR2l9PITyowwmnlP9rmhDEFqH4FGCTE1e9fPfsJKIDivFFpZX5D3Dzk7HCm73 rQFNXFR/i1O6ccdtJ/0qdmF7gSJJYRfbogtdSOegRgw7QpCBdliGaQUd3eZHNBW3 XS0qFdKlXwkqxiUHE7QZZVKJ1PdutLvwYyeSYpArch8Vn/tdWa4EnE7BhK+DRUoZ xYOUfRJi2CB3G5kwb+Og5OnacP0RWlgHJOTf3wwRB8o0MzJjVYyIT3CBRgaaLjNx LmqRMCWaL4ubKO/NrEUTGwBymjST81zmublPwD1o8VvegrntktI= =hKL7 -END PGP SIGNATURE End Message ---
Processed (with 1 error): Re: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
Processing control commands: > retitle -1: Upgrade to 23.3.* breaks video rendering Unknown command or malformed arguments to command. > severity -1 serious Bug #1059782 [mesa-vdpau-drivers] mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter Severity set to 'serious' from 'important' -- 1059782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054076: marked as done (mesa: fix name collision causing Wayland SIGSEGV on i915 machines)
Your message dated Tue, 23 Jan 2024 11:28:50 +0100
with message-id
and subject line mesa: fix name collision causing Wayland SIGSEGV on i915
machines
has caused the Debian Bug report #1054076,
regarding mesa: fix name collision causing Wayland SIGSEGV on i915 machines
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.)
--
1054076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mesa
Version: 23.2.1-1
Severity: important
Tags: patch upstream
X-Debbugs-Cc: hlieber...@debian.org
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889
Control: affects -1 gnome-shell
Hello maintainer,
Due to a name collision in the radeonsi module, gdm under Wayland will segfault
on any machine running an Intel Iris Plus GPU. This was reported in a variety of
distro trackers (https://bugzilla.redhat.com/show_bug.cgi?id=2238711,
https://bugs.archlinux.org/task/79831, etc.).
It can be fixed trivially with the cherry-pick of a patch upstream that is
allocated to be pulled into the 23.2 release stream
(https://gitlab.freedesktop.org/mesa/mesa/-/commit/9590bce3e249a34665b2c42b20bfdbdc7f32147f).
However, due to the impact on users, it would be nice to pull it in before Mesa
makes their next release.
I've attached the patch as well for your reference.
Sincerely,
--
Harlan Lieberman-Berg
~hlieberman
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 9590bce3e249a34665b2c42b20bfdbdc7f32147f Mon Sep 17 00:00:00 2001
From: WinLinux1028
Date: Tue, 11 Jul 2023 18:16:01 +0900
Subject: [PATCH] radeonsi: prefix function with si_ to prevent name collision
Fixed a build error caused by multiple gfx11_init_query symbols when building
with iris and radeonsi specified in gallium-drivers.
Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9238
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24045>
---
src/gallium/drivers/radeonsi/gfx11_query.c | 4 ++--
src/gallium/drivers/radeonsi/si_pipe.c | 4 ++--
src/gallium/drivers/radeonsi/si_pipe.h | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/gfx11_query.c
b/src/gallium/drivers/radeonsi/gfx11_query.c
index bfcd8e2511050..2a331cc3bda25 100644
--- a/src/gallium/drivers/radeonsi/gfx11_query.c
+++ b/src/gallium/drivers/radeonsi/gfx11_query.c
@@ -422,13 +422,13 @@ struct pipe_query *gfx11_sh_query_create(struct si_screen
*screen, enum pipe_que
return (struct pipe_query *)query;
}
-void gfx11_init_query(struct si_context *sctx)
+void si_gfx11_init_query(struct si_context *sctx)
{
list_inithead(>shader_query_buffers);
sctx->atoms.s.shader_query.emit = emit_shader_query;
}
-void gfx11_destroy_query(struct si_context *sctx)
+void si_gfx11_destroy_query(struct si_context *sctx)
{
if (!sctx->shader_query_buffers.next)
return;
diff --git a/src/gallium/drivers/radeonsi/si_pipe.c
b/src/gallium/drivers/radeonsi/si_pipe.c
index fb5c02c473b96..2b4fceb89b198 100644
--- a/src/gallium/drivers/radeonsi/si_pipe.c
+++ b/src/gallium/drivers/radeonsi/si_pipe.c
@@ -192,7 +192,7 @@ static void si_destroy_context(struct pipe_context *context)
si_release_all_descriptors(sctx);
if (sctx->gfx_level >= GFX10 && sctx->has_graphics)
- gfx11_destroy_query(sctx);
+ si_gfx11_destroy_query(sctx);
if (sctx->sqtt) {
struct si_screen *sscreen = sctx->screen;
@@ -637,7 +637,7 @@ static struct pipe_context *si_create_context(struct
pipe_screen *screen, unsign
/* Initialize graphics-only context functions. */
if (sctx->has_graphics) {
if (sctx->gfx_level >= GFX10)
- gfx11_init_query(sctx);
+ si_gfx11_init_query(sctx);
si_init_msaa_functions(sctx);
si_init_shader_functions(sctx);
si_init_state_functions(sctx);
diff --git a/src/gallium/drivers/radeonsi/si_pipe.h
b/src/gallium/drivers/radeonsi/si_pipe.h
index 55f1d1788f1a1..389716854f9a6 100644
--- a/src/gallium/drivers/radeonsi/si_pipe.h
+++ b/src/gallium/drivers/radeonsi/si_pipe.h
@@ -1616,8 +1616,8 @@ void *si_crea
Processed: weston: Fails to start with `environment variable XDG_RUNTIME_DIR is not set.`
Processing control commands: > tag -1 wontfix Bug #988337 [weston] weston: Fails to start with `environment variable XDG_RUNTIME_DIR is not set.` Added tag(s) wontfix. -- 988337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061110: marked as done (xorg-server: Regression from fixes for CVE-2024-21886)
Your message dated Mon, 22 Jan 2024 12:36:05 + with message-id and subject line Bug#1061110: fixed in xorg-server 2:21.1.11-2 has caused the Debian Bug report #1061110, regarding xorg-server: Regression from fixes for CVE-2024-21886 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.) -- 1061110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorg-server Version: 2:21.1.11-1 Severity: important Tags: upstream X-Debbugs-Cc: car...@debian.org, jcris...@debian.org, a...@debian.org, t...@security.debian.org While preparing the update for xorg-server for bookworm an autopkgtest regression in uqm was seen. The same is shown with the 2:21.1.11-1 upload to unstable: https://ci.debian.net/packages/u/uqm/testing/amd64/41866714/ Julien Cristau was able to reproduce the leak independly from uqm: Xvfb :10 & sleep 2; DISPLAY=:10 xdpyinfo >/dev/null resulting in 1 XSELINUXs still allocated at reset SCREEN: 0 objects of 304 bytes = 0 total bytes 0 private allocs DEVICE: 0 objects of 88 bytes = 0 total bytes 0 private allocs CLIENT: 0 objects of 144 bytes = 0 total bytes 0 private allocs WINDOW: 0 objects of 48 bytes = 0 total bytes 0 private allocs PIXMAP: 0 objects of 16 bytes = 0 total bytes 0 private allocs GC: 0 objects of 16 bytes = 0 total bytes 0 private allocs CURSOR: 1 objects of 8 bytes = 8 total bytes 0 private allocs TOTAL: 1 objects, 8 bytes, 0 allocs 1 CURSORs still allocated at reset CURSOR: 1 objects of 8 bytes = 8 total bytes 0 private allocs TOTAL: 1 objects, 8 bytes, 0 allocs 1 CURSOR_BITSs still allocated at reset TOTAL: 0 objects, 0 bytes, 0 allocs As per upstream commit bisection it seems that the first bad commit is https://gitlab.freedesktop.org/xorg/xserver/-/commit/26769aa71fcbe0a8403b7fb13b7c9010cc07c3a8 which is related for the CVE-2024-21886 fix. Regards, Salvatore --- End Message --- --- Begin Message --- Source: xorg-server Source-Version: 2:21.1.11-2 Done: Julien Cristau We believe that the bug you reported is fixed in the latest version of xorg-server, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated xorg-server 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, 22 Jan 2024 13:17:07 +0100 Source: xorg-server Architecture: source Version: 2:21.1.11-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Julien Cristau Closes: 1061110 Changes: xorg-server (2:21.1.11-2) unstable; urgency=medium . [ Salvatore Bonaccorso ] * dix: Fix use after free in input device shutdown (Closes: #1061110) Checksums-Sha1: 2b4d8eb08924a0a64d3cb854eb6805d649238195 4244 xorg-server_21.1.11-2.dsc 4431b563acdc7b60e97c6eb39040b0a3ab2882ce 169271 xorg-server_21.1.11-2.diff.gz Checksums-Sha256: 400d2358ec3c2ce491f80f806a4adea428adc327503b4958c3cf33ae1477e90f 4244 xorg-server_21.1.11-2.dsc 6c46b83042ebdd1262eeabb6fb96945cb5b92045556ab6dd1fde68d3c57180fc 169271 xorg-server_21.1.11-2.diff.gz Files: 55600cec8dfa6d30b38db580439590c8 4244 x11 optional xorg-server_21.1.11-2.dsc 1a06be6653dcdba98e728a071b4271e6 169271 x11 optional xorg-server_21.1.11-2.diff.gz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAmWuXP8UHGpjcmlzdGF1 QGRlYmlhbi5vcmcACgkQnbAjVVb4z60+iQ/+P2vF95E8pBffSl9HfftFvDrvLgL6 WsJyxMqMRF/jpJ7n1u0idqzWgZ6HpY4TVdRah9GiGVpT0VDEF3UvBHCUgo+v9Dvk QvPcqsZqjZGYVa7mrK5C6tCSYzd0aS8O1JNiK+5cNrBq3BAKVMnwZE0ER5so6j6/ 3zWiTiGHcuabMY3t/cnZFH9ytJJ/3mOO7p/7GjYUqjnUPpTscuBPIMxev3+LvFfy XLwJAOPjHv6YBpR9vONwq33PRaIF08jpsXuX+8kDBdXwZT1Ei8Mc6smDV1mmsvIV bdQJl0uyaGYODnqjaWqujpEVMDW2NxigAvWZKxBTVsfxzRFBE7almTQicXpFZkkb 15xjN5O/Ja/UdBVIkki5+1DVJ5eWlX+0+jvE+IFMbbuEhkxeiVSP8oi2bI93SSZT wz+PykuKhdFf80la+EGYrj9IVOEpyv6T6Gd9WA92n2oQj/TjVDowCPSopl8olkHA VaOT0/cKBTVrdRBecFOcOSwGZVAF8FhrW6vrv4pfZki0ibFkvjbzBfoJBhxsV2ya sUhnmWuqoIQQyFFnb+2Jj/JZRMO2/CpKEmLnXQRd3IgRXMRdFpiniNRpVG9xC2Si 90oea8DblVL8AMjIvS3pSFl8DhVcszC62atfbApyL3qd6qo0l0a05IfxFytOFnh1 U83ZFQcFTmOMwJ4= =SNxW -
Bug#980995: marked as done (weston-info recommends wayland-info that does not exist in Debian)
Your message dated Fri, 19 Jan 2024 09:19:01 + with message-id and subject line Bug#980995: fixed in weston 13.0.0-1~exp2 has caused the Debian Bug report #980995, regarding weston-info recommends wayland-info that does not exist in Debian 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.) -- 980995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: weston Version: 9.0.0-2 Severity: minor Dear Maintainer, When weston-info is started, it says: $ weston-info *** Please use wayland-info instead *** weston-info is deprecated and will be removed in a future version But "weston-info" does not exist in the Debian packages. Best regards, Ryutaroh Matsumoto -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 5.10.10raspi4usb (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages weston depends on: ii adduser 3.118 ii libc62.31-9 ii libcairo21.16.0-5 ii libcolord2 1.4.5-3 ii libdrm2 2.4.103-2 ii libegl1 1.3.2-1 ii libegl1-mesa 20.3.3-1 ii libevdev21.10.1+dfsg-1 ii libgbm1 20.3.3-1 ii libgles2 1.3.2-1 ii libglib2.0-0 2.66.4-1 ii libinput10 1.16.4-3 ii libjpeg62-turbo 1:2.0.5-2 ii liblcms2-2 2.12~rc1-2 ii libpam0g 1.4.0-2 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpixman-1-00.40.0-1 ii libpng16-16 1.6.37-3 ii libsystemd0 247.2-5 ii libwayland-client0 1.18.0-2~exp1.1 ii libwayland-cursor0 1.18.0-2~exp1.1 ii libwayland-egl1 1.18.0-2~exp1.1 ii libwayland-server0 1.18.0-2~exp1.1 ii libwebp6 0.6.1-2+b1 ii libweston-9-09.0.0-2 ii libxkbcommon01.0.3-2 Versions of packages weston recommends: ii libgl1-mesa-dri 20.3.3-1 weston suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: weston Source-Version: 13.0.0-1~exp2 Done: Dylan Aïssi We believe that the bug you reported is fixed in the latest version of weston, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated weston 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: Fri, 19 Jan 2024 09:47:00 +0100 Source: weston Architecture: source Version: 13.0.0-1~exp2 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Dylan Aïssi Closes: 980995 Changes: weston (13.0.0-1~exp2) experimental; urgency=medium . * Drop outdated references to quilt * Fix short description of libweston-13-dev * Standards-Version: 4.6.2 (no changes required) * Update debian/copyright * Remove trailing whitespace in debian/changelog * Update minimum version of Build-Deps - libdrm-dev >= 2.4.108 - libinput-dev >= 1.2.0 - libwayland-dev >= 1.22.0 - meson >= 0.63.0 - wayland-protocols >= 1.31 - libneatvnc-dev >= 0.7.0 * Add debian/gbp.conf * Use secure URI for homepage * Switch to debhelper-compat 13 * Install some binaries in usr/libexec/ instead of usr/lib/*/ * Drop useless debian/tmp/ prefix * weston suggests wayland-utils (Closes: #980995) * Mark libweston-13-0 as 'Multi-Arch: same' * Remove all references to weston-launch which was dropped upstream with weston 11 * Drop dependency on adduser, no longer required since weston.postinst was dropped * Restrict Build-Deps on libneatvnc-dev for supported architectures Checksums-Sha1: 21fe5961f6c1a40b2686158e03108b36730feb2f 3
Bug#1043140: marked as done (libweston-12-0: Weston fails to start with "Assertion `csi->width == width' failed")
Your message dated Thu, 18 Jan 2024 21:14:23 +0100 with message-id and subject line libweston-12-0: Weston fails to start with "Assertion `csi->width == width' failed" has caused the Debian Bug report #1043140, regarding libweston-12-0: Weston fails to start with "Assertion `csi->width == width' failed" 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.) -- 1043140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libweston-12-0 Version: 12.0.1-1 Severity: important Tags: upstream After upgrading my system sddm fails to start a wayland session with the following error in .local/share/sddm/wayland-session.log: weston: ../libweston/output-capture.c:398 weston_output_pull_capture_task: Assertion `csi->width == width' failed. Failed to process Wayland connection: Broken pipe failed to create display: Broken pipe Failed to process Wayland connection: Broken pipe failed to create display: Broken pipe This seems to match upstream bug https://gitlab.freedesktop.org/wayland/weston/-/issues/757 which is also against weston 12.0 and has a fix. Hopefully this can be applied to the Debian package. Best regards, Thomas -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libweston-12-0 depends on: ii libaml0 0.3.0-1 ii libc6 2.37-7 ii libcairo2 1.16.0-7 ii libdrm2 2.4.115-1 ii libegl1 1.6.0-1 ii libfontconfig1 2.14.1-4 ii libfreerdp-server2-22.10.0+dfsg1-1 ii libfreerdp2-2 2.10.0+dfsg1-1 ii libgbm1 23.1.4-1 ii libgles21.6.0-1 ii libglib2.0-02.77.1-2 ii libgstreamer-plugins-base1.0-0 1.22.4-1 ii libgstreamer1.0-0 1.22.4-1 ii libinput10 1.23.0-2 ii libjpeg62-turbo 1:2.1.5-2 ii liblcms2-2 2.14-2 ii libneatvnc0 0.6.0+dfsg-4+b1 ii libpam0g1.5.2-6 ii libpango-1.0-0 1.50.14+ds-1 ii libpangocairo-1.0-0 1.50.14+ds-1 ii libpipewire-0.3-0 0.3.77-1 ii libpixman-1-0 0.42.2-1 ii libpng16-16 1.6.40-1 ii libseat10.8.0-1 ii libudev1254-1 ii libva-drm2 2.19.0-1 ii libva2 2.19.0-1 ii libwayland-client0 1.22.0-2 ii libwayland-cursor0 1.22.0-2 ii libwayland-egl1 1.22.0-2 ii libwayland-server0 1.22.0-2 ii libwebp71.2.4-0.2 ii libwinpr2-2 2.10.0+dfsg1-1 ii libx11-62:1.8.6-1 ii libx11-xcb1 2:1.8.6-1 ii libxcb-composite0 1.15-1 ii libxcb-render0 1.15-1 ii libxcb-shm0 1.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb-xkb1 1.15-1 ii libxcb1 1.15-1 ii libxcursor1 1:1.2.1-1 ii libxkbcommon0 1.5.0-1 libweston-12-0 recommends no packages. libweston-12-0 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 13.0.0-1~exp1--- End Message ---
Processed: bug 1061110 is forwarded to https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623
Processing commands for cont...@bugs.debian.org: > forwarded 1061110 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623 Bug #1061110 [src:xorg-server] xorg-server: Regression from fixes for CVE-2024-21886 Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054695: marked as done (weston: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpkmn7e13q/./obj-x86_64-linux-gnu/meson-private/tmpkmn7e13q/testfile.c:17:(.text+0x9): undefined reference to `unreach
Your message dated Thu, 18 Jan 2024 18:00:16 + with message-id and subject line Bug#1054695: fixed in weston 13.0.0-1~exp1 has caused the Debian Bug report #1054695, regarding weston: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpkmn7e13q/./obj-x86_64-linux-gnu/meson-private/tmpkmn7e13q/testfile.c:17:(.text+0x9): undefined reference to `unreachable' 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.) -- 1054695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: weston Version: 12.0.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /tmp/ccvk05IG.o: in function `main': > ./obj-x86_64-linux-gnu/meson-private/tmpkmn7e13q/./obj-x86_64-linux-gnu/meson-private/tmpkmn7e13q/testfile.c:17:(.text+0x9): > undefined reference to `unreachable' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2023/10/27/weston_12.0.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: weston Source-Version: 13.0.0-1~exp1 Done: Dylan Aïssi We believe that the bug you reported is fixed in the latest version of weston, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated weston 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: Wed, 17 Jan 2024 20:56:05 +0100 Source: weston Binary: libweston-13-0 libweston-13-0-dbgsym libweston-13-dev weston weston-dbgsym Architecture: source amd64 Version: 13.0.0-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Dylan Aïssi Description: libweston-13-0 - reference implementation of a wayland compositor (shared libs) libweston-13-dev - reference implementation of a wayland compositor (shared libs) weston - reference implementation of a wayland compositor Closes: 1054695 Changes: weston (13.0.0-1~exp1) experimental; urgency=medium . [ Dylan Aïssi ] * New upstream release. (Closes: #1054695) * Bump SONAME to libweston-13-0 * Update symbols file * Use format: 3.0 (quilt) * Import Marius Vlad's key * Add myself in Uploaders . [ Timo Aaltonen ] * rules: Drop the workaround to drop includedir from libweston-NN-protocols.pc. (LP: #1887301) Checksums-Sha1: 63fc5c767e2712559bce7365327b9ef4d74de6d5 3269 weston_13.0.0-1~exp1.dsc 2c06ff8dddc6b5531a06e30776f5006ca0c2f560 1986520 weston_13.0.0.orig.tar.xz c0c8c91102dea58b86014ee729bf8253ea4e9d06 833 weston_13.0.0.orig.tar.xz.asc 3a17b1697c8d88251e8c3fc1bb9f70e6ce4c9896 25660 weston_13.0.0-1~exp1.debian.tar.xz 95ae20b59a5b7515279f3536aa9c27ddb3d76deb 2089512 libweston-13-0-dbgsym_13.0.0-1~exp1_amd64.deb ee63c0fec82fb7f5590b29f527c2b1075dff29de 385404 libweston-13-0_13.0.0-1~exp1_amd64.deb 0c7ff2d359b1bf1171b5a425a18388bcb0e2b141 43116 libweston-13-dev_13.0.0-1~exp1_amd64.deb eba7f239f673869b58027bd11b2928cc7d9dfbd7 5168900 weston-dbgsym_13.0.0-1~exp1_amd64.deb c923117250ccaed00560f84d5ab37551f75b72b3 19934 weston_13.0.0-1~exp1_amd64.buildinfo c8b7edbf3ab3c4675842c75ac525395b2a74dc6b 892100 weston_13.0.0-1~exp1_amd64.deb Chec
Bug#912827: marked as done (weston: add support for stable xdg-shell)
Your message dated Thu, 18 Jan 2024 14:37:14 +0100 with message-id and subject line weston: add support for stable xdg-shell has caused the Debian Bug report #912827, regarding weston: add support for stable xdg-shell 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.) -- 912827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mpv Version: 0.28.2-3 Severity: important Dear Maintainer, * What led up to the situation? Updated MPV to 0.29.1 from 0.28.2 * What exactly did you do (or not do) that was effective (or ineffective)? Tried to play a video file I have played many times before * What was the outcome of this action? MPV failed to play the file with the following error message: krc@ken:~/NFS/public/video/documentaries/David_Attenborough$ mpv 2017_Blue_Planet_2/Blue_Planet_2_03_Coral_Reefs.mkv Playing: 2017_Blue_Planet_2/Blue_Planet_2_03_Coral_Reefs.mkv Unable to revert mtime: /usr/local/share/fonts (+) Video --vid=1 (*) (h264 1920x1080 25.000fps) (+) Audio --aid=1 --alang=eng (*) (dts 6ch 48000Hz) Subs --sid=1 --slang=eng (*) (hdmv_pgs_subtitle) [vo/gpu/wayland] Compositor doesn't support the required xdg_wm_base protocol! [vo/gpu] Failed initializing any suitable GPU context! Error opening/initializing the selected video_out (--vo) device. Video: no video Exiting... (Errors when loading file) krc@ken:~/NFS/public/video/documentaries/David_Attenborough$ * What outcome did you expect instead? The video should have played I went and got mpv 0.28.3 (and libsndio6.1) from the Debian snapshots and installed it, video now plays fine again. Considering that Weston is the reference implementation of a Wayland compositor, and 5.0 is the latest release, this seems like a problem. I did not attempt to use other -vo methods, they should not be needed. relevant bit of my mpv.conf: vo=gpu profile=opengl-hq gpu-context=wayland hwdec=vaapi ao=pulse,alsa krc@ken:~/$ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.3 (libva 2.2.0) vainfo: Driver version: Intel i965 driver for Intel(R) Ivybridge Desktop - 2.2.0 -- System Information: Debian Release: buster/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mpv depends on: ii libarchive13 3.2.2-5 ii libasound21.1.7-1 ii libass9 1:0.14.0-2 ii libavcodec58 7:4.0.3-1 ii libavdevice58 7:4.0.3-1 ii libavfilter7 7:4.0.3-1 ii libavformat58 7:4.0.3-1 ii libavutil56 7:4.0.3-1 ii libbluray21:1.0.2-3 ii libc6 2.27-8 ii libcaca0 0.99.beta19-2+b3 ii libcdio-cdda2 10.2+0.94+2-4 ii libcdio-paranoia2 10.2+0.94+2-4 ii libcdio18 2.0.0-2 ii libdrm2 2.4.95-1 ii libdvdnav46.0.0-1 ii libdvdread4 6.0.0-1 ii libegl1 1.1.0-1 ii libgbm1 18.1.9-1 ii libgl11.1.0-1 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-22.9-3 ii liblua5.2-0 5.2.4-1.1+b2 ii libpulse0 12.2-2 ii librubberband21.8.1-7 ii libsdl2-2.0-0 2.0.8+dfsg1-6 ii libsmbclient 2:4.9.1+dfsg-2 ii libsndio6.1 1.1.0-3 ii libswresample37:4.0.3-1 ii libswscale5 7:4.0.3-1 ii libuchardet0 0.0.6-3 ii libva-drm22.3.0-2 ii libva-wayland22.3.0-2 ii libva-x11-2 2.3.0-2 ii libva22.3.0-2 ii libvdpau1 1.1.1-8 ii libvulkan11.1.73+dfsg-1 ii
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > forwarded 988337 https://bugs.freedesktop.org/show_bug.cgi?id=62092 Bug #988337 [weston] weston: Fails to start with `environment variable XDG_RUNTIME_DIR is not set.` Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=62092'. > End of message, stopping processing here. Please contact me if you need assistance. -- 988337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015704: marked as done (weston: ftbfs with LTO (link time optimization) enabled)
Your message dated Thu, 18 Jan 2024 12:44:26 +0100 with message-id and subject line weston: ftbfs with LTO (link time optimization) enabled has caused the Debian Bug report #1015704, regarding weston: ftbfs with LTO (link time optimization) enabled 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.) -- 1015704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:weston Version: 10.0.0-1 Severity: minor Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-lto This package currently fails to build (at least on the amd64 architecture) with link time optimizations enabled. For a background for LTO please see https://wiki.debian.org/ToolChain/LTO The goal is to enable this optimization by default in an upcoming Debian release in dpkg-buildflags for 64bit architectures. The goal is to get this package to build with link time optimizations, or to explicitly disable link time optimizations for this package build. To reproduce the build failure, enable the lto optimization in testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS in the debian/rules file, or if this macro is unset, just set it: export DEB_BUILD_MAINT_OPTIONS = optimize=+lto Please try to fix the build with lto enabled, fixing the packaging or forwarding the issue upstream. If the issue cannot be fixed, explicitly disallow building the package with lto by adding to your rules file: export DEB_BUILD_MAINT_OPTIONS = optimize=-lto or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/dpkglto/weston_10.0.0-1_unstable_dpkglto.log The last lines of the build log are at the end of this report. [...] 385 | asprintf(, "--modules=%s%s%s", TESTSUITE_PLUGIN_PATH, | ^ 386 | setup->extra_module ? "," : "", | ~~~ 387 | setup->extra_module ? setup->extra_module : ""); | ~~~ ../tests/weston-test-fixture-compositor.c:392:17: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 392 | asprintf(, "--width=%d", setup->width); | ^~ ../tests/weston-test-fixture-compositor.c:395:17: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 395 | asprintf(, "--height=%d", setup->height); | ^~~~ ../tests/weston-test-fixture-compositor.c:400:17: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 400 | asprintf(, "--scale=%d", setup->scale); | ^~ ../tests/weston-test-fixture-compositor.c:405:17: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 405 | asprintf(, "--transform=%s", | ^~~~ 406 | transform_to_str(setup->transform)); | ~~~ ../tests/weston-test-fixture-compositor.c:411:17: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 411 | asprintf(, "--config=%s", setup->config_file); | ^ ../tests/weston-test-fixture-compositor.c:422:9: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 422 | asprintf(, "--shell=%s", shell_to_str(setup->shell)); | ^~~~ ../tests/weston-test-fixture-compositor.c:426:17: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 426 | asprintf(, "--logger-scopes=%s", setup->logging_scopes); | ^~~ [375/490] cc -o cli
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > forwarded 1015704 https://gitlab.freedesktop.org/wayland/weston/-/issues/517 Bug #1015704 [src:weston] weston: ftbfs with LTO (link time optimization) enabled Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/wayland/weston/-/issues/517'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1015704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > forwarded 1043140 https://gitlab.freedesktop.org/wayland/weston/-/issues/757 Bug #1043140 [libweston-12-0] libweston-12-0: Weston fails to start with "Assertion `csi->width == width' failed" Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/wayland/weston/-/issues/757'. > tag 1043140 pending Bug #1043140 [libweston-12-0] libweston-12-0: Weston fails to start with "Assertion `csi->width == width' failed" Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1043140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 1054695 pending Bug #1054695 [src:weston] weston: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpkmn7e13q/./obj-x86_64-linux-gnu/meson-private/tmpkmn7e13q/testfile.c:17:(.text+0x9): undefined reference to `unreachable' Added tag(s) pending. > tag 980995 pending Bug #980995 [weston] weston-info recommends wayland-info that does not exist in Debian Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054695 980995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#847656: marked as done (weston: Weston > 1.9 all have reproducable crash with browser in xwayland with Ivy Bridge class gpu)
Your message dated Thu, 18 Jan 2024 12:29:18 +0100 with message-id and subject line weston: Weston > 1.9 all have reproducable crash with browser in xwayland with Ivy Bridge class gpu has caused the Debian Bug report #847656, regarding weston: Weston > 1.9 all have reproducable crash with browser in xwayland with Ivy Bridge class gpu 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.) -- 847656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: weston Version: 1.12.0-1 Severity: important Dear Maintainer, In Weston 1.10 and 1.11 (several minor revisions), and the new 1.12 package, I have a reproducable crash. In Firefox/Iceweasel (several versions in the low 30s) and in SeaMonkey (several version, up to latest beta), if I click and drag on an image, upon release, Weston crashes. Current Cromium (55) and Chrome beta (56) do not have this issue with Weston 1.12. I believe they did have it with earlier Weston versions, which makes me think it may be xwayland specific... with Weston 1.12 and recent Chrome, it is Wayland native, but it did not work with 1.11 and 1.10 (console messages about falling back to xwayland) Weston 1.9 has no issues at all with image dragging in any browser. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages weston depends on: ii adduser 3.115 ii libc6 2.24-8 ii libcairo2 1.14.6-1.1 ii libcolord2 1.3.3-2 ii libdrm2 2.4.74-1 ii libegl1-mesa [libegl1-x11] 13.0.2-1 ii libgles2-mesa [libgles2]13.0.2-1 ii libglib2.0-02.50.2-2 ii libinput10 1.5.3-1 ii libjpeg62-turbo 1:1.5.1-2 ii liblcms2-2 2.8-2 ii libpam0g1.1.8-3.3 ii libpango-1.0-0 1.40.3-3 ii libpangocairo-1.0-0 1.40.3-3 ii libpixman-1-0 0.34.0-1 ii libpng16-16 1.6.26-6 ii libsystemd0 232-7 ii libwayland-client0 1.12.0-1 ii libwayland-cursor0 1.12.0-1 ii libwayland-egl1-mesa [libwayland-egl1] 13.0.2-1 ii libwayland-server0 1.12.0-1 ii libweston-1-0 1.12.0-1 ii libxkbcommon0 0.7.0-1 Versions of packages weston recommends: ii libgl1-mesa-dri 13.0.2-1 weston suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 3.0.0-1 As per the bug history, it's fixed since a long time.--- End Message ---
Bug#850658: marked as done (Build weston RDP compositor in Sid)
Your message dated Thu, 18 Jan 2024 12:25:45 +0100
with message-id
and subject line weston: Please enable RDP and screen-share support
has caused the Debian Bug report #850658,
regarding Build weston RDP compositor in Sid
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.)
--
850658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: weston
This debdiff enables building of the Weston rdp compositor in Sid. It
produces a separate package, as that has dependencies on freerdp2.
Originally produced on Ubuntu Zesty, re launchpad:
https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1654864diff -u weston-1.12.0/debian/changelog weston-1.12.0/debian/changelog
--- weston-1.12.0/debian/changelog
+++ weston-1.12.0/debian/changelog
@@ -1,3 +1,12 @@
+weston (1.12.0-2) unstable; urgency=medium
+
+ * d/control:
++ Create weston-rdp-backend package
++ Add freerdp2-dev to build depends
+ * Build rdp compositor
+
+ -- John Moser Sun, 08 Jan 2017 09:02:17 -0500
+
weston (1.12.0-1) unstable; urgency=medium
* New upstream release. Closes: #841735.
diff -u weston-1.12.0/debian/control weston-1.12.0/debian/control
--- weston-1.12.0/debian/control
+++ weston-1.12.0/debian/control
@@ -39,6 +39,7 @@
libsystemd-dev,
libinput-dev (>= 0.8.0),
wayland-protocols (>= 1.7),
+ freerdp2-dev,
Standards-Version: 3.9.8
Homepage: http://wayland.freedesktop.org/
Vcs-Git: git://anonscm.debian.org/pkg-xorg/wayland/weston
@@ -102,0 +104,16 @@
+
+Package: weston-rdp-compositor
+Architecture: linux-any
+Depends:
+ weston,
+ ${shlibs:Depends},
+ ${misc:Depends},
+Recommends:
+Description: reference implementation of a wayland compositor
+ Part of the Wayland project is also the Weston reference implementation
+ of a Wayland compositor. Weston can run as an X client or under Linux
+ KMS and ships with a few demo clients. The Weston compositor is a minimal
+ and fast compositor and is suitable for many embedded and mobile use
+ cases.
+ .
+ This package contains the RDP compositor for Wayland.
diff -u weston-1.12.0/debian/rules weston-1.12.0/debian/rules
--- weston-1.12.0/debian/rules
+++ weston-1.12.0/debian/rules
@@ -2,7 +2,8 @@
override_dh_auto_configure:
dh_auto_configure -- --disable-libunwind --libexec=/usr/lib/weston \
- --with-cairo=image --enable-libinput-backend
+ --with-cairo=image --enable-libinput-backend \
+ --enable-rdp-compositor
override_dh_auto_test:
# the test suite does not 100% pass in headless mode
only in patch2:
unchanged:
--- weston-1.12.0.orig/debian/weston-rdp-compositor.install
+++ weston-1.12.0/debian/weston-rdp-compositor.install
@@ -0,0 +1 @@
+usr/lib/*/libweston-1/rdp-backend.so
only in patch2:
unchanged:
--- weston-1.12.0.orig/libweston/compositor-rdp.c
+++ weston-1.12.0/libweston/compositor-rdp.c
@@ -618,13 +618,13 @@
context->rfx_context->mode = RLGR3;
context->rfx_context->width = client->settings->DesktopWidth;
context->rfx_context->height = client->settings->DesktopHeight;
- rfx_context_set_pixel_format(context->rfx_context, RDP_PIXEL_FORMAT_B8G8R8A8);
+ rfx_context_set_pixel_format(context->rfx_context, PIXEL_FORMAT_BGRA32);
context->nsc_context = nsc_context_new();
if (!context->nsc_context)
goto out_error_nsc;
- nsc_context_set_pixel_format(context->nsc_context, RDP_PIXEL_FORMAT_B8G8R8A8);
+ nsc_context_set_pixel_format(context->nsc_context, PIXEL_FORMAT_BGRA32);
context->encode_stream = Stream_New(NULL, 65536);
if (!context->encode_stream)
--- End Message ---
--- Begin Message ---
Version: 6.0.1-1
RDP and screensharing are enabled in weston since 6.0.1-1.--- End Message ---
Bug#775855: marked as done (weston: Please enable RDP and screen-share support)
Your message dated Thu, 18 Jan 2024 12:25:45 +0100 with message-id and subject line weston: Please enable RDP and screen-share support has caused the Debian Bug report #775855, regarding weston: Please enable RDP and screen-share support 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.) -- 775855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: weston Version: 1.6.0-2+b1 Severity: wishlist It appears that rdp-backend and the screen-share module are disabled in the Debain package. It would be nice if these were enabled. Thanks -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages weston depends on: ii adduser 3.113+nmu3 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libcolord2 1.2.1-1+b2 ii libdbus-1-3 1.8.12-3 ii libdrm2 2.4.58-2 ii libegl1-mesa [libegl1-x11] 10.3.2-1 ii libgbm1 10.3.2-1 ii libgles2-mesa [libgles2]10.3.2-1 ii libglib2.0-02.42.1-1 ii libinput5 0.6.0+dfsg-2 ii libjpeg62-turbo 1:1.3.1-11 ii liblcms2-2 2.6-3+b3 ii libmtdev1 1.1.5-1 ii libpam0g1.1.8-3.1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpixman-1-0 0.32.6-3 ii libpng12-0 1.2.50-2+b2 ii libsystemd0 215-8 ii libudev1215-8 ii libwayland-client0 1.6.0-2 ii libwayland-cursor0 1.6.0-2 ii libwayland-egl1-mesa [libwayland-egl1] 10.3.2-1 ii libwayland-server0 1.6.0-2 ii libx11-62:1.6.2-3 ii libx11-xcb1 2:1.6.2-3 ii libxcb-composite0 1.10-3+b1 ii libxcb-render0 1.10-3+b1 ii libxcb-shape0 1.10-3+b1 ii libxcb-shm0 1.10-3+b1 ii libxcb-xfixes0 1.10-3+b1 ii libxcb-xkb1 1.10-3+b1 ii libxcb1 1.10-3+b1 ii libxcursor1 1:1.1.14-1+b1 ii libxkbcommon0 0.4.3-2 Versions of packages weston recommends: ii libgl1-mesa-dri 10.3.2-1 weston suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 6.0.1-1 RDP and screensharing are enabled in weston since 6.0.1-1.--- End Message ---
