Processed: ssvnc should not use xmkmf
Processing control commands: > block 873764 by -1 Bug #873764 [xutils-dev] Please remove xmkmf and imake from xutils-dev 873764 was blocked by: 873807 876248 873764 was not blocking any bugs. Added blocking bug(s) of 873764: 888009 -- 873764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873764 888009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libxft-dev: Please mark the package Multi-Arch: same
Processing control commands: > severity -1 important Bug #884176 [libxft-dev] libxft-dev: Please mark the package Multi-Arch: same Severity set to 'important' from 'wishlist' -- 884176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#887482 in dh-autoreconf marked as pending
Processing control commands: > tag 887482 pending Bug #887482 [src:xorg-server] xorg-server: FTBFS: dh_autoreconf can only be run once Added tag(s) pending. -- 887482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#887482: marked as done (xorg-server: FTBFS: dh_autoreconf can only be run once)
Your message dated Wed, 24 Jan 2018 21:50:43 + with message-id and subject line Bug#887482: fixed in dh-autoreconf 16 has caused the Debian Bug report #887482, regarding xorg-server: FTBFS: dh_autoreconf can only be run once 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.) -- 887482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorg-server Version: 2:1.19.5-1 Severity: serious >From my pbuilder build log: ... make[6]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb/test/xi2' make[5]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb/test' make[4]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb/test' make[4]: Entering directory '/build/xorg-server-1.19.5/debian/build/udeb' make[4]: Nothing to be done for 'all-am'. make[4]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb' make[3]: Leaving directory '/build/xorg-server-1.19.5/debian/build/udeb' make[2]: Leaving directory '/build/xorg-server-1.19.5' debian/rules override_dh_auto_test make[2]: Entering directory '/build/xorg-server-1.19.5' dh_auto_test -- -j1 VERBOSE=1 make[2]: Leaving directory '/build/xorg-server-1.19.5' make[1]: Leaving directory '/build/xorg-server-1.19.5' dh_quilt_patch -O--parallel -Nxserver-common -Nxorg-server-source File series fully applied, ends at patch 06_use-intel-only-on-pre-gen4.diff dh_update_autotools_config -O--parallel -Nxserver-common -Nxorg-server-source dh_autoreconf -O--parallel -Nxserver-common -Nxorg-server-source dh_autoreconf: Can only be run once, see dh-autoreconf(7) debian/rules:8: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 On further testing, it seems that on a freshly unpacked source, either "dpkg-buildpackage -B" or "dpkg-buildpackage -A" separately will work; but "dpkg-buildpackage -b" will fail with the above error. -- Daniel Schepler --- End Message --- --- Begin Message --- Source: dh-autoreconf Source-Version: 16 We believe that the bug you reported is fixed in the latest version of dh-autoreconf, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Andres Klode (supplier of updated dh-autoreconf 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, 24 Jan 2018 22:26:43 +0100 Source: dh-autoreconf Binary: dh-autoreconf Architecture: source Version: 16 Distribution: unstable Urgency: medium Maintainer: Julian Andres Klode Changed-By: Julian Andres Klode Description: dh-autoreconf - debhelper add-on to call autoreconf and clean up after the build Closes: 882479 887482 Changes: dh-autoreconf (16) unstable; urgency=medium . * Do not fail, only warn, if run multiple times (Closes: #887482) * Also clean up symlinks (Closes: #882479) * Run dh_autoreconf after dh_update_autotools_config, not before dh_auto_configure Checksums-Sha1: c9bf7a920013021dad5fbd898dfd5a79c7a150f9 1578 dh-autoreconf_16.dsc 58459600164398ad6807ddd877a6f814c799c62c 7372 dh-autoreconf_16.tar.xz ac9708e6f60aef4f9a6305004b41e128b87fcc80 4983 dh-autoreconf_16_source.buildinfo Checksums-Sha256: 1c1b2ab5f1ae5496bd50dbb3c30e9b7d181a06c8d02ee8d7e9c35ed6f2a69b5f 1578 dh-autoreconf_16.dsc 5c6a6a362907327bec77a867ff3fd0eceba8015d1b881b48275aff7e4ce0f629 7372 dh-autoreconf_16.tar.xz cb95435376f713675c83edf4da20abe848578218c77b2e397032cfee309a4833 4983 dh-autoreconf_16_source.buildinfo Files: 6576a28fe1918ce10bd31543ba545901 1578 devel optional dh-autoreconf_16.dsc 302c8bf43db02412e3f2197fd0f2ee0f 7372 devel optional dh-autoreconf_16.tar.xz 0d23df9377d98dc0d9b7437817fd9ab5 4983 devel optional dh-autoreconf_16_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEzeVhi4gF/W4gLOnC1zw55WWAs4YFAlpo+pEPHGpha0BkZWJp YW4ub3JnAAoJENc8OeVlgLOG4dgP/joeOfhyTgn9qBMbV
Processed: reassign 888315 to libgl1-mesa-dri
Processing commands for cont...@bugs.debian.org: > reassign 888315 libgl1-mesa-dri Bug #888315 [blender] blender: segfault on start Bug reassigned from package 'blender' to 'libgl1-mesa-dri'. No longer marked as found in versions blender/2.79+dfsg0-3. Ignoring request to alter fixed versions of bug #888315 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 888315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#888315: blender: segfault on start
Processing control commands: > reassign -1 libgl1-mesa-dri Bug #888315 [libgl1-mesa-dri] blender: segfault on start Ignoring request to reassign bug #888315 to the same package -- 888315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#884176: libxft-dev: Please mark the package Multi-Arch: same
Processing control commands: > severity -1 wishlist Bug #884176 [libxft-dev] libxft-dev: Please mark the package Multi-Arch: same Severity set to 'wishlist' from 'important' -- 884176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#888047: marked as done (mesa: FTBFS on hurd-i386)
Your message dated Thu, 25 Jan 2018 19:40:21 +
with message-id
and subject line Bug#888047: fixed in mesa 18.0.0~rc2-1
has caused the Debian Bug report #888047,
regarding mesa: FTBFS on hurd-i386
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.)
--
888047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mesa
Version: 17.3.3-1
Severity: important
Tags: patch
Hello,
mesa currently FTBFS on hurd-i386 for a few upstream and downstream
reasons. The attached patches pthread_setname_np and GetDriverConfig are
cherry-picks from upstream. The attached patch "patch" is for the Debian
changes: the libva dependency is avoided on hurd-any, but --with libva
was still pased, thus failing. Also, surfaceless requires libdrm, which
is not available.
Samuel
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unreleased'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (1,
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: hurd-i386 (i686-AT386)
Kernel: GNU-Mach 1.8+git20171101-486-dbg/Hurd-0.9
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
commit 9131e6d3c2dcc30260e23f2232b44c8cffc6f315
Author: Samuel Thibault
Date: Sat Jan 13 12:33:15 2018 +0100
u_thread: Use pthread_setname_np on linux only.
pthread_setname_np was added in glibc 2.12 for the Linux port only, other
ports do not necessarily have it.
Signed-off-by: Jose Fonseca
diff --git a/src/util/u_thread.h b/src/util/u_thread.h
index 26cc0b0934..8c6e0bdc59 100644
--- a/src/util/u_thread.h
+++ b/src/util/u_thread.h
@@ -62,7 +62,8 @@ static inline void u_thread_setname( const char *name )
{
#if defined(HAVE_PTHREAD)
# if defined(__GNU_LIBRARY__) && defined(__GLIBC__) &&
defined(__GLIBC_MINOR__) && \
- (__GLIBC__ >= 3 || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 12))
+ (__GLIBC__ >= 3 || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 12)) && \
+ defined(__linux__)
pthread_setname_np(pthread_self(), name);
# endif
#endif
commit 47ac11bcf8bd9e4525e0fb4308d0bca87a8900c6
Author: Samuel Thibault
Date: Mon Jan 15 15:38:25 2018 +0100
glx: fix non-dri build
glXGetDriverConfig parameters do not provide a context to dynamically
check for the presence of the function, so the dispatcher directly calls
glXGetDriverConfig, but in non-dri builds dri_glx.c didn't provide
glXGetDriverConfig.
This change make it just return NULL in that case.
Fixes: 84f764a7591 "glxglvnddispatch: Add missing dispatch for
GetDriverConfig
Reviewed-by: Nicolai Hähnle
Reviewed-by: Hans de Goede
Reviewed-by: Emil Velikov
diff --git a/src/glx/g_glxglvnddispatchfuncs.c
b/src/glx/g_glxglvnddispatchfuncs.c
index 56d894eda7..5b65afc860 100644
--- a/src/glx/g_glxglvnddispatchfuncs.c
+++ b/src/glx/g_glxglvnddispatchfuncs.c
@@ -338,11 +338,15 @@ static Display *dispatch_GetCurrentDisplayEXT(void)
static const char *dispatch_GetDriverConfig(const char *driverName)
{
+#if defined(GLX_DIRECT_RENDERING) && !defined(GLX_USE_APPLEGL)
/*
* The options are constant for a given driverName, so we do not need
* a context (and apps expect to be able to call this without one).
*/
return glXGetDriverConfig(driverName);
+#else
+return NULL;
+#endif
}
diff -ur mesa-17.3.1.orig/debian/rules mesa-17.3.1/debian/rules
--- mesa-17.3.1.orig/debian/rules 2018-01-13 09:10:32.0 +
+++ mesa-17.3.1/debian/rules2018-01-13 09:52:21.0 +
@@ -26,16 +26,20 @@
DRI_DRIVERS =
GALLIUM_DRIVERS =
VULKAN_DRIVERS =
-EGL_PLATFORMS = x11,surfaceless
confflags_DRI3 = --disable-dri3
# hurd doesn't do direct rendering
ifeq ($(DEB_HOST_ARCH_OS), hurd)
+ EGL_PLATFORMS = x11
+
confflags_DIRECT_RENDERING = --disable-driglx-direct
confflags_GBM = --disable-gbm
DRI_DRIVERS = swrast
+ with_libva =
else
+ EGL_PLATFORMS = x11,surfaceless
+
ifeq ($(DEB_HOST_ARCH_OS), linux)
confflags_DRI3 = --enable-dri3
# Gallium drivers which require kernel support, not yet ported to
non-Linux
@@ -108,6 +112,7 @@
confflags_G
Bug#887444: marked as done (mesa: Please build with optimization level -O1 on sh3 and sh4)
Your message dated Thu, 25 Jan 2018 19:40:21 + with message-id and subject line Bug#887444: fixed in mesa 18.0.0~rc2-1 has caused the Debian Bug report #887444, regarding mesa: Please build with optimization level -O1 on sh3 and sh4 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.) -- 887444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa Version: 17.3.2-1 Severity: normal Tags: patch User: debian-sup...@lists.debian.org Usertags: sh3 sh4 Hello! mesa currently FTBFS on sh4 (and consequently sh3) due to a bug in upstream gcc which hasn't been resolved yet [1]. To work around this bug, it's enough to add "-O1" to the extra C/C++ build flags on sh3/sh4 which sets "-freorder-blocks-algorithm=simple" Just passing "-freorder-blocks-algorithm=simple" doesn't unfor- tunately work as gcc would just crash the qemu buildd. This might be a bug in qemu. For the time being, we will be happy with just passing "-O1" to fix the FTBFS. Patch attached. Thanks, Adrian > [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83143 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 diff -Nru old/mesa-17.3.2/debian/rules new/mesa-17.3.2/debian/rules --- old/mesa-17.3.2/debian/rules2018-01-16 16:00:16.0 +0100 +++ new/mesa-17.3.2/debian/rules2018-01-16 16:50:14.789910395 +0100 @@ -10,13 +10,19 @@ DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU) -ifeq (,$(filter $(DEB_HOST_ARCH), armhf)) +ifeq (,$(filter $(DEB_HOST_ARCH), armhf sh3 sh4)) buildflags = \ $(shell DEB_CFLAGS_MAINT_APPEND=-Wall DEB_CXXFLAGS_MAINT_APPEND=-Wall dpkg-buildflags --export=configure) else -# Workaround for a variant of LP: #725126 -buildflags = \ + ifneq (,$(filter $(DEB_HOST_ARCH), armhf)) + # Workaround for a variant of LP: #725126 + buildflags = \ $(shell DEB_CFLAGS_MAINT_APPEND="-Wall -fno-optimize-sibling-calls" DEB_CXXFLAGS_MAINT_APPEND="-Wall -fno-optimize-sibling-calls" dpkg-buildflags --export=configure) + else + # Workaround for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83143 + buildflags = \ + $(shell DEB_CFLAGS_MAINT_APPEND="-Wall -O1" DEB_CXXFLAGS_MAINT_APPEND="-Wall -O1" dpkg-buildflags --export=configure) + endif endif # keep a list of files we don't install (yet), but since it's a bit --- End Message --- --- Begin Message --- Source: mesa Source-Version: 18.0.0~rc2-1 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 887...@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: SHA256 Format: 1.8 Date: Thu, 25 Jan 2018 13:42:14 +0200 Source: mesa Binary: libxatracker2 libxatracker-dev libgbm1 libgbm-dev libegl-mesa0 libegl1-mesa libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa libgles2-mesa-dev libglapi-mesa libglx-mesa0 libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-dev mesa-common-dev libosmesa6 libosmesa6-dev mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers mesa-opencl-icd Architecture: source Version: 18.0.0~rc2-1 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library libegl1-mesa - transitional dummy package libegl1-mesa-dev - free implementation of the EGL API -- development files libgbm-dev - generic buffer management API -- development files libgbm1- generic buffer management API -- runtime libgl1-mesa-dev - free implementation of the OpenGL API -- GLX development files libgl1-mesa-dri - free implementation of the Open
Processed: bug 884717 is forwarded to https://github.com/NVIDIA/libglvnd/issues/147
Processing commands for cont...@bugs.debian.org: > forwarded 884717 https://github.com/NVIDIA/libglvnd/issues/147 Bug #884717 [libgl1] libgl1: consider using a version that is higher than 1.2.0 for the libGL.so.1.0.0 filename Set Bug forwarded-to-address to 'https://github.com/NVIDIA/libglvnd/issues/147'. > thanks Stopping processing here. Please contact me if you need assistance. -- 884717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836453: marked as done (xserver-xorg-dev: please move xorg-server.pc to a multiarch path)
Your message dated Fri, 26 Jan 2018 15:33:00 +
with message-id
and subject line Bug#836453: fixed in xorg-server 2:1.19.6-1
has caused the Debian Bug report #836453,
regarding xserver-xorg-dev: please move xorg-server.pc to a multiarch path
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.)
--
836453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-dev
Version: 2:1.18.4-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:xf86-input-wacom src:xserver-xorg-input-evdev
src:xserver-xorg-input-libinput src:xserver-xorg-input-mouse
src:xserver-xorg-input-synaptics src:xserver-xorg-video-amdgpu
src:xserver-xorg-video-ati src:xserver-xorg-video-cirrus
src:xserver-xorg-video-fbdev src:xserver-xorg-video-mach64
src:xserver-xorg-video-mga src:xserver-xorg-video-neomagic
src:xserver-xorg-video-nouveau src:xserver-xorg-video-r128
src:xserver-xorg-video-savage src:xserver-xorg-video-siliconmotion
src:xserver-xorg-video-sisusb src:xserver-xorg-video-tdfx
src:xserver-xorg-video-trident
Hi,
xserver-xorg-dev makes the aforementioned affected packages fail to
cross build from source, because pkg-config does not consider[1]
/usr/lib/pkgconfig/ during cross compilation. In contrast, it always
considers /usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig, so moving
xorg-server.pc there will make both native and cross builds happy.
The requested change is implemented in the attached patch for your
convenience.
Helmut
[1] This choice was discusses with pkg-config maintainer Tollef Fog Heen
and the conclusion was that packages should move their .pc files.
diff -u xorg-server-1.18.4/debian/changelog xorg-server-1.18.4/debian/changelog
--- xorg-server-1.18.4/debian/changelog
+++ xorg-server-1.18.4/debian/changelog
@@ -1,3 +1,10 @@
+xorg-server (2:1.18.4-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Install xserver-xorg.pc into a multiarch path. (Closes: #-1)
+
+ -- Helmut Grohne Sat, 03 Sep 2016 09:02:57 +0200
+
xorg-server (2:1.18.4-1) unstable; urgency=medium
* New upstream stable release.
diff -u xorg-server-1.18.4/debian/rules xorg-server-1.18.4/debian/rules
--- xorg-server-1.18.4/debian/rules
+++ xorg-server-1.18.4/debian/rules
@@ -21,10 +21,7 @@
MAKEFLAGS += -j$(NUMJOBS)
endif
-DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
-DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
+include /usr/share/dpkg/architecture.mk
ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE))
confflags += --build=$(DEB_HOST_GNU_TYPE)
else
@@ -396,6 +393,8 @@
install -m 644 debian/local/64-xorg-xkb.rules
debian/xserver-xorg-core-udeb/lib/udev/rules.d
endif
endif
+ $(INSTALL) -m 755 -d
debian/xserver-xorg-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig
+ $(INSTALL) -m 644 debian/tmp/main/usr/lib/pkgconfig/xorg-server.pc
debian/xserver-xorg-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/
dh_installdebconf -s
dh_installman -s
dh_link -s
diff -u xorg-server-1.18.4/debian/xserver-xorg-dev.install
xorg-server-1.18.4/debian/xserver-xorg-dev.install
--- xorg-server-1.18.4/debian/xserver-xorg-dev.install
+++ xorg-server-1.18.4/debian/xserver-xorg-dev.install
@@ -1,5 +1,4 @@
main/usr/include/xorg usr/include
-main/usr/lib/pkgconfig/xorg-server.pc usr/lib/pkgconfig
main/usr/share/aclocal usr/share
../../debian/local/dh_xsf_substvars usr/bin
--- End Message ---
--- Begin Message ---
Source: xorg-server
Source-Version: 2:1.19.6-1
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 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Timo Aaltonen (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: SHA256
Format: 1.8
Date: Thu, 18 Jan 2018 14:11:18 +0200
Source: xorg-server
Processed: Re: Bug#888460: libxss: bad git URL in package description
Processing control commands: > notfound -1 1:1.2.2-2 Bug #888460 [src:libxss] libxss: bad git URL in package description The source 'libxss' and version '1:1.2.2-2' do not appear to match any binary packages No longer marked as found in versions libxss/1:1.2.2-2. > found -1 1:1.2.2-1 Bug #888460 [src:libxss] libxss: bad git URL in package description Marked as found in versions libxss/1:1.2.2-1. > tags -1 + pending Bug #888460 [src:libxss] libxss: bad git URL in package description Added tag(s) pending. -- 888460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#888454: xorg-docs: broken watch file
Processing control commands: > notfound -1 1:1.7.1-2 Bug #888454 [src:xorg-docs] xorg-docs: broken watch file The source 'xorg-docs' and version '1:1.7.1-2' do not appear to match any binary packages No longer marked as found in versions xorg-docs/1:1.7.1-2. > found -1 1:1.7.1-1 Bug #888454 [src:xorg-docs] xorg-docs: broken watch file Marked as found in versions xorg-docs/1:1.7.1-1. -- 888454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885919: marked as done (amdgpu: Can't start X with amdgpu kernel module)
Your message dated Sat, 27 Jan 2018 11:52:11 + with message-id and subject line Re: Bug#885919: amdgpu: Can't start X with amdgpu kernel module has caused the Debian Bug report #885919, regarding amdgpu: Can't start X with amdgpu kernel module 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.) -- 885919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-amdgpu Version: 1.4.0-1 Severity: important File: amdgpu Dear Maintainer, After a recent upgrade, I'm not able to start X with the amdgpu kernel module. I had to blacklist amdgpu module to be able to start X using the Intel's IGP. I attach some information I think it could be useful. I hope you have all the information you need. Best regards. --- * Laptop model: Lenovo ThinkPad E460, model 20ETCTO1WW ThinkPad BIOS R00ET57W (1.32 ), EC unknown LENOVO 20ETCTO1WW/20ETCTO1WW, BIOS R00ET57W (1.32 ) 10/31/2017 * System info: Debian Buster (updated) Linux version 4.14.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 7.2.0 (Debian 7.2.0-18)) #1 SMP Debian 4.14.7-1 (2017-12-22) CPU0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (family: 0x6, model: 0x4e, stepping: 0x3) * lspci -knn output: 03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [1002:6900] (rev 81) Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [17aa:5049] Kernel modules: amdgpu * dmesg info and trace: [9.648665] [drm] initializing kernel modesetting (TOPAZ 0x1002:0x6900 0x17AA:0x5049 0x81). [9.648696] [drm] register mmio base: 0xF200 [9.648699] [drm] register mmio size: 262144 [9.648744] [drm] probing gen 2 caps for device 8086:9d18 = 9724043/e [9.648748] [drm] probing mlw for device 8086:9d18 = 9724043 [9.648778] vga_switcheroo: enabled [9.707549] ACPI Error: Field [TBF3] at bit offset/length 262144/32768 exceeds size of target Buffer (262144 bits) (20170728/dsopcode-235) [9.707594] ACPI Error: Method parse/execution failed \_SB.PCI0.GFX0.GETB, AE_AML_BUFFER_LIMIT (20170728/psparse-550) [9.707633] ACPI Error: Method parse/execution failed \_SB.PCI0.GFX0.ATRM, AE_AML_BUFFER_LIMIT (20170728/psparse-550) [9.707668] failed to evaluate ATRM got AE_AML_BUFFER_LIMIT [9.707671] ATOM BIOS: BR46504.001 [9.707681] [drm] GPU posting now... [9.711157] [drm] Changing default dispclk from 0Mhz to 600Mhz [9.711231] [drm] vm size is 64 GB, block size is 13-bit, fragment size is 4-bit [9.796448] [drm] RC6 on [9.843351] amdgpu :03:00.0: firmware: direct-loading firmware amdgpu/topaz_mc.bin [9.843403] amdgpu :03:00.0: VRAM: 2048M 0x00F4 - 0x00F47FFF (2048M used) [9.843406] amdgpu :03:00.0: GTT: 256M 0x - 0x0FFF [9.843429] [drm] Detected VRAM RAM=2048M, BAR=256M [9.843431] [drm] RAM width 64bits DDR3 [9.843555] [TTM] Zone kernel: Available graphics memory: 4029196 kiB [9.843557] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [9.843558] [TTM] Initializing pool allocator [9.843566] [TTM] Initializing DMA pool allocator [9.843627] [drm] amdgpu: 2048M of VRAM memory ready [9.843629] [drm] amdgpu: 3072M of GTT memory ready. [9.843663] [drm] GART: num cpu pages 65536, num gpu pages 65536 [9.845744] [drm] PCIE GART of 256M enabled (table at 0x00F40004). [9.845899] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [9.845900] [drm] Driver supports precise vblank timestamp query. [9.846089] amdgpu :03:00.0: amdgpu: using MSI. [9.846150] [drm] amdgpu: irq initialized. [ 10.118311] amdgpu: [powerplay] amdgpu: powerplay sw initialized [ 10.158075] amdgpu :03:00.0: firmware: direct-loading firmware amdgpu/topaz_pfp.bin [ 10.158800] amdgpu :03:00.0: firmware: direct-loading firmware amdgpu/topaz_me.bin [ 10.356607] amdgpu :03:00.0: firmware: direct-loading firmware amdgpu/topaz_ce.bin [ 10.389277] amdgpu :03:00.0: firmware: direct-loading firmware amdgpu/topaz_rlc.bin [ 10.414746] amdgpu :03:00.0: firmware: direct-loading firmware amdgpu/topaz_mec.bin [ 10.415019] amdgpu :03:00.0: fence driver on ring 0 use gpu addr 0x00400080, cpu addr 0xb45b8183a080 [ 10.415147] amdgpu :03:00.0: fence driver on ring 1 use gpu addr 0x00400100, cpu addr 0xb45b8183a100 [ 10.41
Processed: Re: xserver-xorg-video-mach64 FTCBFS: abuses AC_CHECK_FILE for build system files
Processing control commands: > clone -1 -2 Bug #888662 [src:xserver-xorg-video-mach64] xserver-xorg-video-mach64 FTCBFS: abuses AC_CHECK_FILE for build system files Bug 888662 cloned as bug 888692 > reassign -2 src:xserver-xorg-video-r128 Bug #888692 [src:xserver-xorg-video-mach64] xserver-xorg-video-mach64 FTCBFS: abuses AC_CHECK_FILE for build system files Bug reassigned from package 'src:xserver-xorg-video-mach64' to 'src:xserver-xorg-video-r128'. No longer marked as found in versions xserver-xorg-video-mach64/6.9.5-1. Ignoring request to alter fixed versions of bug #888692 to the same values previously set > found -2 6.10.2-1 Bug #888692 [src:xserver-xorg-video-r128] xserver-xorg-video-mach64 FTCBFS: abuses AC_CHECK_FILE for build system files Marked as found in versions xserver-xorg-video-r128/6.10.2-1. -- 888662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888662 888692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: xserver-xorg-video-mga FTCBFS: abuses AC_CHECK_FILE for build system files
Processing control commands: > clone -1 -2 Bug #888694 [src:xserver-xorg-video-mga] xserver-xorg-video-mga FTCBFS: abuses AC_CHECK_FILE for build system files Bug 888694 cloned as bug 888696 > reassign -2 src:xserver-xorg-video-savage Bug #888696 [src:xserver-xorg-video-mga] xserver-xorg-video-mga FTCBFS: abuses AC_CHECK_FILE for build system files Bug reassigned from package 'src:xserver-xorg-video-mga' to 'src:xserver-xorg-video-savage'. No longer marked as found in versions xserver-xorg-video-mga/1:1.6.5-1. Ignoring request to alter fixed versions of bug #888696 to the same values previously set > found -2 1:2.3.9-1 Bug #888696 [src:xserver-xorg-video-savage] xserver-xorg-video-mga FTCBFS: abuses AC_CHECK_FILE for build system files Marked as found in versions xserver-xorg-video-savage/1:2.3.9-1. -- 888694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888694 888696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: xserver-xorg-video-mga FTCBFS: abuses AC_CHECK_FILE for build system files
Processing control commands: > clone -1 -2 Bug #888694 [src:xserver-xorg-video-mga] xserver-xorg-video-mga FTCBFS: abuses AC_CHECK_FILE for build system files Bug 888694 cloned as bug 888713 > reassign -2 src:xserver-xorg-video-tdfx Bug #888713 [src:xserver-xorg-video-mga] xserver-xorg-video-mga FTCBFS: abuses AC_CHECK_FILE for build system files Bug reassigned from package 'src:xserver-xorg-video-mga' to 'src:xserver-xorg-video-tdfx'. No longer marked as found in versions xserver-xorg-video-mga/1:1.6.5-1. Ignoring request to alter fixed versions of bug #888713 to the same values previously set > found -2 1:1.4.7-1 Bug #888713 [src:xserver-xorg-video-tdfx] xserver-xorg-video-mga FTCBFS: abuses AC_CHECK_FILE for build system files Marked as found in versions xserver-xorg-video-tdfx/1:1.4.7-1. -- 888694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888694 888713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 884356 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=104836
Processing commands for cont...@bugs.debian.org: > forwarded 884356 https://bugs.freedesktop.org/show_bug.cgi?id=104836 Bug #884356 [src:mesa] mesa FTBFS on ia64 Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=104836'. > thanks Stopping processing here. Please contact me if you need assistance. -- 884356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Move to the package where it was fixed
Processing commands for cont...@bugs.debian.org:
> reassign 887482 dh-autoreconf
Bug #887482 {Done: Julian Andres Klode } [src:xorg-server]
xorg-server: FTBFS: dh_autoreconf can only be run once
Bug reassigned from package 'src:xorg-server' to 'dh-autoreconf'.
No longer marked as found in versions xorg-server/2:1.19.5-1.
No longer marked as fixed in versions dh-autoreconf/16.
> fixed 887482 16
Bug #887482 {Done: Julian Andres Klode } [dh-autoreconf]
xorg-server: FTBFS: dh_autoreconf can only be run once
Marked as fixed in versions dh-autoreconf/16.
> tags 887482 buster sid
Bug #887482 {Done: Julian Andres Klode } [dh-autoreconf]
xorg-server: FTBFS: dh_autoreconf can only be run once
Added tag(s) buster and sid.
> affects 887482 src:xorg-server
Bug #887482 {Done: Julian Andres Klode } [dh-autoreconf]
xorg-server: FTBFS: dh_autoreconf can only be run once
Added indication that 887482 affects src:xorg-server
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
887482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#884822: marked as done (Please upgrade to 2.22)
Your message dated Thu, 01 Feb 2018 15:51:10 + with message-id and subject line Bug#884822: fixed in xkeyboard-config 2.23.1-1 has caused the Debian Bug report #884822, regarding Please upgrade to 2.22 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.) -- 884822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:xkeyboard-config version: 2.19-1.1 severity: wishlist xkeyboard-config 2.22 is available upstream. It would be great if the package could be upgraded to 2.22, since we are about to release an Ubuntu LTS (Long Term Support) in April, and would like to include an as updated version as possible. Thanks! -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj --- End Message --- --- Begin Message --- Source: xkeyboard-config Source-Version: 2.23.1-1 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 884...@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: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 17:30:40 +0200 Source: xkeyboard-config Binary: xkb-data xkb-data-udeb Architecture: source Version: 2.23.1-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: xkb-data - X Keyboard Extension (XKB) configuration data xkb-data-udeb - X Keyboard Extension (XKB) configuration data (udeb) Closes: 884822 Changes: xkeyboard-config (2.23.1-1) unstable; urgency=medium . * New upstream release. (Closes: #884822) * revert-indic-blacklist.diff: Dropped, upstream. * fix-typo.diff: Fix a typo in pl layout. Checksums-Sha1: 17aadbb146a70b78da9348d146220bb11ff8be57 2109 xkeyboard-config_2.23.1-1.dsc 6f0ff8ac2361eb8baf4d1550f49c0e9dac99d68f 1599103 xkeyboard-config_2.23.1.orig.tar.gz 601da1375e380ce643ed817c9beaf75ef1e87e02 44602 xkeyboard-config_2.23.1-1.diff.gz Checksums-Sha256: e862c150967356dc7ebf0af82bf8f5ba1152d3e7755d877930eb720eb790b052 2109 xkeyboard-config_2.23.1-1.dsc 6567ccf5d134aae19ef110f5c847d5326aed01fc671167a6b8f8c47aeada0b85 1599103 xkeyboard-config_2.23.1.orig.tar.gz 0f19b9f652330a32fc352cd4fe7c53ecbeb17ce7a78f50235bf1a59fdb112bc1 44602 xkeyboard-config_2.23.1-1.diff.gz Files: 594e736431447572e7c581a519c01ca7 2109 x11 extra xkeyboard-config_2.23.1-1.dsc baad22820d19668a3bbcdc46ba729d04 1599103 x11 extra xkeyboard-config_2.23.1.orig.tar.gz c30976bf6f4e71f3281e93fb626f61bf 44602 x11 extra xkeyboard-config_2.23.1-1.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJaczK1AAoJEMtwMWWoiYTcW1UP/3CnHonVqqr/RVwzETKmY83S izmdsEFtNVSC6OP0jV7gS1HRDAtH7fK6hvTx4F8naxd9pDzcKXKHYi6lx7IVkdqV kba1iTKtdn9DsFDrHknhgH0YasH3p8bX8QxMUFhTf4RJxCmNV3P7LxYpCSiJ2NLr iDWNTQd9gKhKkV8INoD16Bjv1ori6qkEMY5biOwNilG0m6kZxjICKB2N6y7GU34f 6Emq4gKvfXaKSpwhLMnc/pd7RZAh7VAsv3i/vgY4BYPM6AUZhhRe9/dG4dhLgBwL nuq8Rgt+DPQO2Ty+6WiONsvzI/lXTdpNtYednvnkPvO/TY7hEvjkK9fnn6utBIl6 qV6KU2FVyuCTNyH5R+PEDRmWQS53ju0I5EIfh3YVkQOABjddKGHG8NPGm02ZtAac CIQVAqwKDuCQ8g3xzK+yTIcF3lG29D4IvKNjHfCkqGON0bfin1i0nH855DRFZkgd kWGqo98aJVzIaxfqngghsM4W+567VfGYSqmle/TcsTS9VdWVCvSUb/P3FAHuAaeh fzx0Q15AnfhVEA8VgvJzysOaidVJ9Qukw9iFIW+hlM8atDQfLafF5bws1IRG677L zy54SgtVyVLTRktGBLfBoJXQ1KW+lfKPhtFO4ChS8CE8Z65QG0hl3CrkqHfLOGog dgnMUV6Mese7D8m2xhpX =5/DY -END PGP SIGNATURE End Message ---
Processed: Re: Bug#884717: libgl1: consider using a version that is higher than 1.2.0 for the libGL.so.1.0.0 filename
Processing control commands: > tag -1 fixed-upstream Bug #884717 [libgl1] libgl1: consider using a version that is higher than 1.2.0 for the libGL.so.1.0.0 filename Added tag(s) fixed-upstream. -- 884717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#889301: Updating the xft Uploaders list
Processing control commands: > tag -1 patch pending Bug #889301 [src:xft] Updating the xft Uploaders list Added tag(s) pending and patch. -- 889301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#889483: marked as done (libegl1 package disables amdgpu direct rendering)
Your message dated Sun, 4 Feb 2018 15:31:55 +0200 with message-id <845a1caa-a251-e832-eb2a-c72fd2a6a...@debian.org> and subject line Re: Bug#889483: libegl1 package disables amdgpu direct rendering has caused the Debian Bug report #889483, regarding libegl1 package disables amdgpu direct rendering 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.) -- 889483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libegl1 Version: 1.0.0-2 The presence of this package disables 2d and 3d hardware acceleration of the Mesa amdgpu driver: [ 6.245] (EE) AMDGPU(0): eglGetDisplay() failed [ 6.245] (EE) AMDGPU(0): glamor detected, failed to initialize EGL. [ 6.452] (II) AMDGPU(0): Front buffer pitch: 7680 bytes [ 6.452] (==) AMDGPU(0): DRI3 disabled [ 6.452] (==) AMDGPU(0): Backing store enabled [ 6.452] (WW) AMDGPU(0): Direct rendering disabled [ 6.452] (II) AMDGPU(0): 2D and 3D acceleration disabled [ 6.452] (==) AMDGPU(0): DPMS enabled [ 6.452] (==) AMDGPU(0): Silken mouse enabled [ 6.453] (II) AMDGPU(0): RandR 1.2 enabled, ignore the following RandR disabled message. [ 6.489] (--) RandR disabled [ 6.491] (II) SELinux: Disabled on system [ 6.491] (II) AIGLX: Screen 0 is not DRI2 capable [ 6.491] (EE) AIGLX: reverting to software rendering [ 6.499] (II) IGLX: enabled GLX_MESA_copy_sub_buffer [ 6.500] (II) IGLX: Loaded and initialized swrast [ 6.500] (II) GLX: Initialized DRISWRAST GL provider for screen 0 Many Debian buster mesa packages can not install with Oibaf ppa Mesa packages any more, because depends versions use = instead of >=. This happened about 26.1.2018. xfce@ryzen5pc:~$ inxi -bM System:Host: ryzen5pc Kernel: 4.15.0-rc8+ x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x serial: N/A UEFI [Legacy]: American Megatrends v: 3401 date: 12/04/2017 CPU: 6 core AMD Ryzen 5 1600 Six-Core (-MT-MCP-) speed/max: 2727/3375 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Polaris11] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,ati,radeon,amdgpu (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: llvmpipe (LLVM 5.0, 128 bits) version: 3.3 Mesa 17.3.3 Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 Drives:HDD Total Size: 256.1GB (66.9% used) Info: Processes: 242 Uptime: 7 min Memory: 737.0/7976.9MB --- End Message --- --- Begin Message --- On 03.02.2018 21:20, fin4478 fin4478 wrote: > Package: libegl1 > Version: 1.0.0-2 > > The presence of this package disables 2d and 3d hardware acceleration > of the Mesa amdgpu driver: > > [ 6.245] (EE) AMDGPU(0): eglGetDisplay() failed > [ 6.245] (EE) AMDGPU(0): glamor detected, failed to initialize EGL. > > [ 6.452] (II) AMDGPU(0): Front buffer pitch: 7680 bytes > [ 6.452] (==) AMDGPU(0): DRI3 disabled > [ 6.452] (==) AMDGPU(0): Backing store enabled > [ 6.452] (WW) AMDGPU(0): Direct rendering disabled > [ 6.452] (II) AMDGPU(0): 2D and 3D acceleration disabled > [ 6.452] (==) AMDGPU(0): DPMS enabled > [ 6.452] (==) AMDGPU(0): Silken mouse enabled > [ 6.453] (II) AMDGPU(0): RandR 1.2 enabled, ignore the following RandR > disabled message. [ 6.489] (--) RandR disabled > [ 6.491] (II) SELinux: Disabled on system > [ 6.491] (II) AIGLX: Screen 0 is not DRI2 capable > [ 6.491] (EE) AIGLX: reverting to software rendering > [ 6.499] (II) IGLX: enabled GLX_MESA_copy_sub_buffer > [ 6.500] (II) IGLX: Loaded and initialized swrast > [ 6.500] (II) GLX: Initialized DRISWRAST GL provider for screen 0 > > Many Debian buster mesa packages can not install with Oibaf ppa Mesa > packages any more, because depends versions use = instead of >=. This > happened about 26.1.2018. You can't mix non-glvnd mesa from a random ppa with Debian.--- End Message ---
Bug#843837: marked as done (libxft-dev: Xft/Xft.h header incorrectly includes ft2build.h)
Your message dated Mon, 5 Feb 2018 15:38:05 +0100 with message-id <56babf10-9d75-e0f9-135b-47dff5afe...@debian.org> and subject line Re: Bug#843837: libxft-dev: Xft/Xft.h header incorrectly includes ft2build.h has caused the Debian Bug report #843837, regarding libxft-dev: Xft/Xft.h header incorrectly includes ft2build.h 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.) -- 843837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxft-dev Version: 2.3.2-1 Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? Tried to build Motif from sources. * What exactly did you do (or not do) that was effective (or ineffective)? Take Motif sources and run configure && make * What was the outcome of this action? Compilation error: make[3]: Entering directory '/home/alex/heap/motif.sf.git/lib/Xm' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../include -I.. -I./.. -DXMBINDDIR_FALLBACK=\"/usr/lib/X11/bindings\" -DINCDIR=\"/usr/include/X11\" -DLIBDIR=\"/usr/lib/X11\" -O0 -g3 -Wall -g -fno-strict-aliasing -Wno-unused -Wno-comment -fno-tree-ter -MT Label.lo -MD -MP -MF .deps/Label.Tpo -c -o Label.lo Label.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../include -I.. -I./.. -DXMBINDDIR_FALLBACK=\"/usr/lib/X11/bindings\" -DINCDIR=\"/usr/include/X11\" -DLIBDIR=\"/usr/lib/X11\" -O0 -g3 -Wall -g -fno-strict-aliasing -Wno-unused -Wno-comment -fno-tree-ter -MT Label.lo -MD -MP -MF .deps/Label.Tpo -c Label.c -fPIC -DPIC -o .libs/Label.o In file included from XmRenderTI.h:33:0, from Label.c:77: /usr/include/X11/Xft/Xft.h:39:22: fatal error: ft2build.h: No such file or directory #include ^ compilation terminated. Makefile:1048: recipe for target 'Label.lo' failed make[3]: *** [Label.lo] Error 1 make[3]: Leaving directory '/home/alex/heap/motif.sf.git/lib/Xm' * What outcome did you expect instead? Motif should compile without errors. /usr/include/X11/Xft/Xft.h from the package libxft-dev. This header has include string: #include on line 39. This is incorrect. Since ft2build.h is installed in /usr/include/freetype2 dir, the include macro must be the following: #include -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libxft-dev depends on: ii libc6-dev [libc-dev] 2.19-18+deb8u6 ii libfontconfig1-dev 2.11.0-6.3+deb8u1 ii libfreetype6-dev 2.5.2-3+deb8u1 ii libx11-dev 2:1.6.2-3 ii libxft22.3.2-1 ii libxrender-dev 1:0.9.8-1+b1 ii zlib1g-dev [libz-dev] 1:1.2.8.dfsg-2+b1 libxft-dev recommends no packages. libxft-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On 02/04/2018 01:05 PM, Hugh McMaster wrote: > Hi Graham, > > Sorry for the delayed reply. > > On Wednesday, 31 January 2018 5:23 PM, Graham Inggs wrote: >> I saw this message in bug #887595 [1] and thought it would be relevant here: >> >> On Tue, Jan 23, 2018 at 11:56:38AM +, Hugh McMaster wrote: >>> Also note that the Freetype2 developers no longer recommend using >>> #include >>> in source files (which was the intent of my patch). The following should be >>> used instead: >>> #include >>> #include FT_FREETYPE_H >>> >>> Developers would then use either freetype-config or pkg-config to >>> obtain the cflags etc. >> >> Hugh, do you have a reference for the above? > > The freetype-2.8 API reference shows this #include usage. Look at the > documentation > provided with libfreetype6-dev in > /usr/share/doc/libfreetype6/documentation.html, > particulary Tutorial #1 and Example #1. > > Freetype-2.9 (the most recent upstream version) also has this information. > See [1] for information on freetype2's header inclusion scheme and [2] for > the tutorial. > > [1] > https://www.freetype.org/freetype2/docs/reference/ft2-header_inclusion.html > [2] https://www.freetype.org/freetype2/docs/tutorial/step1.html > [3] > https://anonscm.debian.org/cgit/collab-maint/motif.git/tree/debian/patches/fix_ac_find_xft.patch > Closing this bug as invalid. Cheers, Julien--- End Message ---
Processed: xserver-xorg-video-ast: diff for NMU version 1.1.5-1.1
Processing control commands: > tags 887076 + patch Bug #887076 [src:xserver-xorg-video-ast] xserver-xorg-video-ast: unused build-dependency on libxatracker-dev Added tag(s) patch. > tags 887076 + pending Bug #887076 [src:xserver-xorg-video-ast] xserver-xorg-video-ast: unused build-dependency on libxatracker-dev Added tag(s) pending. -- 887076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package xorg-server
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package xorg-server > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #861956 (http://bugs.debian.org/861956) > # Bug title: X server hangs at shutdown if it's in background > # * https://bugs.freedesktop.org/show_bug.cgi?id=103782 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 861956 + fixed-upstream Bug #861956 [xserver-xorg-core] X server hangs at shutdown if it's in background Added tag(s) fixed-upstream. > usertags 861956 - status-NEW Usertags were: status-NEW. Usertags are now: . > usertags 861956 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. -- 861956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:wayland
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:wayland > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #889681 (http://bugs.debian.org/889681) > # Bug title: wayland: CVE-2017-16612 > # * https://bugs.freedesktop.org/show_bug.cgi?id=103961 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 889681 + fixed-upstream Bug #889681 [src:wayland] wayland: CVE-2017-16612 Added tag(s) fixed-upstream. > usertags 889681 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. -- 889681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 888633 in 17.3.3-1.1, found 888633 in 17.3.3-1 ..., tagging 888633
Processing commands for cont...@bugs.debian.org: > notfound 888633 17.3.3-1.1 Bug #888633 [libgl1-mesa-dri] libgl1-mesa-dri: Problem with Firefox and other XWayland applications on AMD GPU There is no source info for the package 'libgl1-mesa-dri' at version '17.3.3-1.1' with architecture '' Unable to make a source version for version '17.3.3-1.1' No longer marked as found in versions 17.3.3-1.1. > found 888633 17.3.3-1 Bug #888633 [libgl1-mesa-dri] libgl1-mesa-dri: Problem with Firefox and other XWayland applications on AMD GPU Marked as found in versions mesa/17.3.3-1. > forwarded 888633 https://bugs.freedesktop.org/show_bug.cgi?id=104306 Bug #888633 [libgl1-mesa-dri] libgl1-mesa-dri: Problem with Firefox and other XWayland applications on AMD GPU Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=104306'. > tags 888633 + fixed-upstream pending Bug #888633 [libgl1-mesa-dri] libgl1-mesa-dri: Problem with Firefox and other XWayland applications on AMD GPU Added tag(s) pending and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 888633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 890337 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=105129
Processing commands for cont...@bugs.debian.org: > forwarded 890337 https://bugs.freedesktop.org/show_bug.cgi?id=105129 Bug #890337 [xserver-xorg-core] Disabling Trackpoint Scrolling via xorg.conf freezes screen/input Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=105129'. > thanks Stopping processing here. Please contact me if you need assistance. -- 890337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: splitting off distinct issues
Processing commands for cont...@bugs.debian.org: > retitle 801401 with systemd, cannot start X from the console command line > using xinit, only startx Bug #801401 [xserver-xorg] cannot start X from the console command line Changed Bug title to 'with systemd, cannot start X from the console command line using xinit, only startx' from 'cannot start X from the console command line'. > clone 801401 -1 Bug #801401 [xserver-xorg] with systemd, cannot start X from the console command line using xinit, only startx Bug 801401 cloned as bug 890749 > severity 801401 normal Bug #801401 [xserver-xorg] with systemd, cannot start X from the console command line using xinit, only startx Severity set to 'normal' from 'important' > retitle -1 using startx requires either libpam-systemd or xserver-xorg-legacy Bug #890749 [xserver-xorg] with systemd, cannot start X from the console command line using xinit, only startx Changed Bug title to 'using startx requires either libpam-systemd or xserver-xorg-legacy' from 'with systemd, cannot start X from the console command line using xinit, only startx'. > submitter -1 James Richardson Bug #890749 [xserver-xorg] using startx requires either libpam-systemd or xserver-xorg-legacy Changed Bug submitter to 'James Richardson ' from 'Giuseppe Bilotta '. > thanks Stopping processing here. Please contact me if you need assistance. -- 801401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801401 890749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#697932: marked as done (init script for single application appliances)
Your message dated Mon, 19 Feb 2018 15:37:43 +0100 with message-id and subject line Re: init script for single application appliances has caused the Debian Bug report #697932, regarding init script for single application appliances 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.) -- 697932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg Version: 1:7.7+1 Severity: wishlist Hi, Using the X server to draw applications running fullscreen on dedicated appliances is not so uncommon. There are numerous tutorials describing how to do that, and various techniques. There is the /etc/inittab way. But I prefer the init script way as the X server can be started and stopped. The only caveat is that the init script launching the X server needs users not logged in the start the X server (dpkg-reconfigure x11-common). I've written such a script[1] for my package. It runs the X server as a dedicated user and provides access to a Xauthority file using permissions to the video group. Some more details in the 'default' file[2]. It as been working reliabily for me and some friends for a few years. But I now found out that this can be beneficial to other packages as well (xbmc for instance). I think my script requires very few adaptations to be more general-purpose. That's why I could propose either a patch to one of the X packages or a new source package (containing only one script?) making easy to deploy such configuration (initscript, dedicated user creation). Any comments, fixes, guidelines will be very welcome. Thanks, Alex [1] http://sousmonlit.incube.tk/~niol/repositories/deejayd/file/d52a42471c0a/debian/deejayd.deejayd-xserver.init [2] http://sousmonlit.incube.tk/~niol/repositories/deejayd/file/d52a42471c0a/debian/deejayd.default --- End Message --- --- Begin Message --- lightdm-autologin-greeter provides the functionality, thus closing.--- End Message ---
Processed: Re: Bug#890866: mesa: regression vs mesa 17.3.3-1: crash on i915 triggered by running emacs
Processing control commands: > severity -1 serious Bug #890866 [src:mesa] mesa: regression vs mesa 17.3.3-1: crash on i915 triggered by running emacs Severity set to 'serious' from 'important' > tags -1 upstream Bug #890866 [src:mesa] mesa: regression vs mesa 17.3.3-1: crash on i915 triggered by running emacs Added tag(s) upstream. > forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=105169 Bug #890866 [src:mesa] mesa: regression vs mesa 17.3.3-1: crash on i915 triggered by running emacs Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=105169'. -- 890866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 889979 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=105133
Processing commands for cont...@bugs.debian.org: > forwarded 889979 https://bugs.freedesktop.org/show_bug.cgi?id=105133 Bug #889979 [xserver-xephyr] Composite extension broken Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=105133'. > thanks Stopping processing here. Please contact me if you need assistance. -- 889979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#874715: marked as done (mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2)
Your message dated Tue, 20 Feb 2018 16:21:33 +0100 with message-id <20180220152133.dqisjsjrvo6svw44@localhost.localdomain> and subject line Re: Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2 has caused the Debian Bug report #874715, regarding mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2 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.) -- 874715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa Version: 17.0.2-2 Severity: grave Justification: renders package unusable Hi, after upgrading mesa from 17.1.5 to 17.2.0-2 none of my games are able to start. At least Counter-Strike Global Offensive reports this failure back to me: Failed to create GL context: Could not make GL context current: GLXBadContextTag Regards Dominik -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- On Mon, Feb 19, 2018 at 06:56:15AM +0100, Dominik Kupschke wrote: > Am Donnerstag, 14. Dezember 2017, 20:14:46 CET schrieb Andreas Boll: > > Control: tag -1 moreinfo > > > > On Fri, Oct 13, 2017 at 10:24:19AM +0200, Andreas Boll wrote: > > > Control: severity -1 important > > > > > > On Mon, Oct 02, 2017 at 09:00:59PM +0200, Dominik Kupschke wrote: > > > > Hi, > > > > > > > > I was able to start some steam games without steam-runtime. > > > > Also non Steam Games work properly. > > > > > > > > Regards > > > > Dominik > > > > > > Hi, > > > > > > so it looks like an issue with the steam-runtime. Please report this > > > issue to Valve on github and let us know the bug number/url for > > > tracking. > > > > > > I'm lowering the severity to important to let Mesa migrate to testing > > > since it blocks lots of packages. > > > > > > Thanks, > > > Andreas > > > > Is this still an issue with mesa 17.3.0? Did you report this issue to > > Valve on github? > > > > Thanks, > > Andreas > > > > Hi, > > this is fixed in the latest steam package released by debian: > https://tracker.debian.org/news/933866 > > Regards > Dominik Nice to hear that your issue is resolved. Closing this bug. Thanks, Andreas--- End Message ---
Bug#887076: marked as done (xserver-xorg-video-ast: unused build-dependency on libxatracker-dev)
Your message dated Wed, 21 Feb 2018 13:34:57 + with message-id and subject line Bug#887076: fixed in xserver-xorg-video-ast 1.1.5-1.1 has caused the Debian Bug report #887076, regarding xserver-xorg-video-ast: unused build-dependency on libxatracker-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.) -- 887076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xserver-xorg-video-ast Version: 1.1.5-1 Severity: serious xserver-xorg-video-ast build-depends on libxatracker-dev [linux-any], but: 1) it doesn't use it anywhere 2) libxatracker-dev is x86 only nowadays Please get rid of that build-dependency. Cheers, Julien --- End Message --- --- Begin Message --- Source: xserver-xorg-video-ast Source-Version: 1.1.5-1.1 We believe that the bug you reported is fixed in the latest version of xserver-xorg-video-ast, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated xserver-xorg-video-ast 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, 11 Feb 2018 14:37:01 +0200 Source: xserver-xorg-video-ast Binary: xserver-xorg-video-ast Architecture: source Version: 1.1.5-1.1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force Changed-By: Adrian Bunk Description: xserver-xorg-video-ast - X.Org X server -- ASpeed Technologies display driver Closes: 887076 Changes: xserver-xorg-video-ast (1.1.5-1.1) unstable; urgency=low . * Non-maintainer upload. * Remove the unused build dependency on libxatracker-dev. (Closes: #887076) Checksums-Sha1: e69ac65363fa03f46ff6da89c44354ee58df2b17 2112 xserver-xorg-video-ast_1.1.5-1.1.dsc 7c2c2516018d8ed4fbbf7d223098389127579bab 2376 xserver-xorg-video-ast_1.1.5-1.1.debian.tar.xz Checksums-Sha256: 3b0724271fd4de96161102ac6f948fa6a8cb3d822654b46fdfbc7173b12d7e37 2112 xserver-xorg-video-ast_1.1.5-1.1.dsc 8c07e9d8f859e67f0a726d34f594702f36f0ab36544efca297d507e37339a141 2376 xserver-xorg-video-ast_1.1.5-1.1.debian.tar.xz Files: fa5e7c34c3bf6732ba170edb118b243d 2112 x11 optional xserver-xorg-video-ast_1.1.5-1.1.dsc 461405b408b46fc1aa62943f73f0da80 2376 x11 optional xserver-xorg-video-ast_1.1.5-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqAOcYACgkQiNJCh6LY mLGewxAAwNs0USYQ5zF+Gcq6vTi053oPl8JY9dMEBV2y+et5VxwFS8+fjkiztCqE N7deSr/asZXsSLBd1Bpm5RatTZYn6509v4TcEwNFfvUUeTro0EJEygzgT+qerXLj /w2I5obHigj3pUxRbM4p/UbqaqB9nIWypbhDo3hE6dHDi46w0mNhbtPNcRKBdQIp p1FOLUuZQsbo8/68VdygJoR5UKa4iZJlzfv+w/43sawdi8tnfP+UHbd8SKgl1EIX VyK4Y4HROJG5n3R4iWuRQ7ee6HAxob5qXG+/zRhWSSVB5t1Y3PDjB+u9732SZAde rV7WnJ6s/GBYBgHU/93tOvhdq8n0qAX8gtnIx181dLQGv4iFchvdhq1hua6vkVuB YokK04rHzyNnVvynJzoXXuchcUGwBckJOn6wHoxY50wQF148gU7EgoMp9WU+NJoJ TFFGsVD1nQXWTefhJ9kFUYNHW93idr7IuJgiRplKaleIgJpeM7g2wb3S1V7n9eBg NYPJYpTFd+cPIivUJWyCXrFxQ5CjOQ40MVc6u0RidwJ8uv5hX9yA0UbWb32+gGi5 l/yy44iGLwMUiRtV4ceoL+TTkpT0YHSDjq/lRSl5sdM8P+V0r2uJdB2advez1tqo 75ltt8tziqDaN7Qg9Q2fK3EOu9taCJGIwVaDJDi08H3mu9d9i0c= =VpJn -END PGP SIGNATURE End Message ---
Processed: Xwayland: random crash (SIGABRT) while running under gdm
Processing control commands: > reassign -1 mutter 3.26.2-1 Bug #887402 [xwayland] Xwayland: random crash (SIGABRT) while running under gdm Bug reassigned from package 'xwayland' to 'mutter'. No longer marked as found in versions xorg-server/2:1.19.5-1. Ignoring request to alter fixed versions of bug #887402 to the same values previously set Bug #887402 [mutter] Xwayland: random crash (SIGABRT) while running under gdm Marked as found in versions mutter/3.26.2-1. > affects -1 gnome-shell xwayland Bug #887402 [mutter] Xwayland: random crash (SIGABRT) while running under gdm Added indication that 887402 affects gnome-shell and xwayland > retitle -1 Xwayland error "invalid global wl_output" and gnome-shell killed > by SIGTRAP Bug #887402 [mutter] Xwayland: random crash (SIGABRT) while running under gdm Changed Bug title to 'Xwayland error "invalid global wl_output" and gnome-shell killed by SIGTRAP' from 'Xwayland: random crash (SIGABRT) while running under gdm'. > forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=789070 Bug #887402 [mutter] Xwayland error "invalid global wl_output" and gnome-shell killed by SIGTRAP Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=789070'. > severity -1 important Bug #887402 [mutter] Xwayland error "invalid global wl_output" and gnome-shell killed by SIGTRAP Severity set to 'important' from 'normal' > tags -1 + upstream fixed-upstream patch Bug #887402 [mutter] Xwayland error "invalid global wl_output" and gnome-shell killed by SIGTRAP Added tag(s) patch, upstream, and fixed-upstream. -- 887402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 798097 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=104759
Processing commands for cont...@bugs.debian.org: > forwarded 798097 https://bugs.freedesktop.org/show_bug.cgi?id=104759 Bug #798097 [xserver-xorg-core] Restarting logind kills Xserver Changed Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=104759' from 'https://github.com/systemd/systemd/issues/1163'. > thanks Stopping processing here. Please contact me if you need assistance. -- 798097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: close 855105
Processing commands for cont...@bugs.debian.org: > close 855105 Bug #855105 [xserver-xorg-core] xserver-xorg-core: numerous deleted DRM mmaped objects in Xorg server memory mappings Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 855105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Add patch and fixed-upstream tag
Processing commands for cont...@bugs.debian.org: > tags 889038 + patch fixed-upstream Bug #889038 [xserver-xorg-core] xserver-xorg-core: Running xserver results in blank screen, no keyboard input Added tag(s) patch and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 889038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: add patch and fixed-upstream tag
Processing commands for cont...@bugs.debian.org: > tags 890337 + patch fixed-upstream Bug #890337 [xserver-xorg-core] Disabling Trackpoint Scrolling via xorg.conf freezes screen/input Added tag(s) fixed-upstream and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 890337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug
Processing commands for cont...@bugs.debian.org: > reassign 891554 xserver-xorg-video-nouveau Bug #891554 [okular] okular: Desktop freezes when resizing the okular window Bug reassigned from package 'okular' to 'xserver-xorg-video-nouveau'. No longer marked as found in versions okular/4:16.08.2-1. Ignoring request to alter fixed versions of bug #891554 to the same values previously set > severity 891554 normal Bug #891554 [xserver-xorg-video-nouveau] okular: Desktop freezes when resizing the okular window Severity set to 'normal' from 'important' > merge 891554 889966 Bug #891554 [xserver-xorg-video-nouveau] okular: Desktop freezes when resizing the okular window Bug #891554 [xserver-xorg-video-nouveau] okular: Desktop freezes when resizing the okular window Marked as found in versions xserver-xorg-video-nouveau/1:1.0.15-2. Bug #889966 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: X lockup (cursor still ok), often triggered by video/window resize Merged 889966 891554 > thanks Stopping processing here. Please contact me if you need assistance. -- 889966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889966 891554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#890866: marked as done (mesa: regression vs mesa 17.3.3-1: crash on i915 triggered by running emacs)
Your message dated Tue, 27 Feb 2018 09:20:07 + with message-id and subject line Bug#890866: fixed in mesa 17.3.6-1 has caused the Debian Bug report #890866, regarding mesa: regression vs mesa 17.3.3-1: crash on i915 triggered by running emacs 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.) -- 890866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa Version: 17.3.4-1 Severity: important Dear Maintainer, After upgrading to Mesa 17.3.4-1, starting emacs (in X11) would reliably cause the X server to crash. Reverting to mesa 17.3.3-1 with the following packages: libegl1-mesa_17.3.3-1_amd64.deb libegl-mesa0_17.3.3-1_amd64.deb libgbm1_17.3.3-1_amd64.deb libgl1-mesa-dri_17.3.3-1_amd64.deb libgl1-mesa-glx_17.3.3-1_amd64.deb libglapi-mesa_17.3.3-1_amd64.deb libglx-mesa0_17.3.3-1_amd64.deb libwayland-egl1-mesa_17.3.3-1_amd64.deb mesa-va-drivers_17.3.3-1_amd64.deb mesa-vdpau-drivers_17.3.3-1_amd64.deb Causes the problem to go away. This was running on a 2018 Dell XPS 13 (model number 9370) with a 4k display. Found in dmesg was the following: Feb 19 14:07:00 cwcc kernel: [ 1740.829003] [drm] GPU HANG: ecode 9:0:0x85df3cff, in Xorg [1098], reason: Hang on rcs0, action: reset Feb 19 14:07:00 cwcc kernel: [ 1740.829111] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Feb 19 14:07:00 cwcc kernel: [ 1740.829112] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Feb 19 14:07:00 cwcc kernel: [ 1740.829113] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Feb 19 14:07:00 cwcc kernel: [ 1740.829114] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Feb 19 14:07:00 cwcc kernel: [ 1740.829115] [drm] GPU crash dump saved to /sys/class/drm/card0/error Feb 19 14:07:00 cwcc kernel: [ 1740.829123] i915 :00:02.0: Resetting rcs0 after gpu hang Feb 19 14:07:08 cwcc kernel: [ 1748.819899] i915 :00:02.0: Resetting rcs0 after gpu hang And attached please find the contents of /sys/class/drm/card0/error -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled GPU HANG: ecode 9:0:0x85df, in Xorg [1555], reason: Hang on rcs0, action: reset Kernel: 4.14.0-3-amd64 Time: 1519086048 s 628402 us Boottime: 128 s 796155 us Uptime: 119 s 301934 us Active process (on ring render): Xorg [1555], score 0 Reset count: 0 Suspend count: 0 Platform: KABYLAKE PCI ID: 0x5917 PCI Revision: 0x07 PCI Subsystem: 1028:07e6 IOMMU enabled?: 0 DMC loaded: yes DMC fw version: 1.1 GT awake: yes RPM wakelock: yes PM suspended: no EIR: 0x IER: 0x0800 GTIER[0]: 0x01010101 GTIER[1]: 0x01010101 GTIER[2]: 0x0070 GTIER[3]: 0x0101 PGTBL_ER: 0x FORCEWAKE: 0x00010001 DERRMR: 0x2077efef CCID: 0x Missed interrupts: 0x fence[0] = 300030003 fence[1] = 300403b0261 fence[2] = fence[3] = fence[4] = fence[5] = 20b900402088003 fence[6] = fence[7] = fence[8] = 330032003 fence[9] = 318a00903005003 fence[10] = 1e001e003 fence[11] = fence[12] = 20872060003 fence[13] = fence[14] = fence[15] = 340034003 fence[16] = 360035003 fence[17] = fence[18] = fence[19] = 202100202010003 fence[20] = fence[21] = 370037003 fence[22] = 2d002d003 fence[23] = fence[24] = 1f001f003 fence[25] = fence[26] = 222b004021fa003 fence[27] = 25dc00802499003 fence[28] = 200e200e003 fence[29] = 200f200f003 fence[30] = 21f9004021f5003 fence[31] = ERROR: 0x FAULT_TLB_DATA: 0x0011 0xe4bf2b9a DONE_REG: 0x render command stream: START: 0x00011000 HEAD: 0x02a03100 [0x30a8] TAIL: 0x3420 [0x3100, 0x3128] CTL: 0x3001 MODE: 0x HWS: 0xfffe8000 ACTHD: 0x 02a03100 IPEIR: 0x IPEHR: 0x7a04 INSTDONE: 0xffdb SC
Processed: reassign 891056 to src:mesa, found 891056 in mesa/17.3.5-1, fixed 891056 in mesa/17.3.6-1
Processing commands for cont...@bugs.debian.org: > reassign 891056 src:mesa Bug #891056 [src:linux] Reproducible Intel GPU hang on rcs0 with ecode 9:0:0x86dd Bug reassigned from package 'src:linux' to 'src:mesa'. No longer marked as found in versions linux/4.14.17-1, linux/4.14.13-1, linux/4.15.4-1, and linux/4.14.7-1. Ignoring request to alter fixed versions of bug #891056 to the same values previously set > found 891056 mesa/17.3.5-1 Bug #891056 [src:mesa] Reproducible Intel GPU hang on rcs0 with ecode 9:0:0x86dd Marked as found in versions mesa/17.3.5-1. > fixed 891056 mesa/17.3.6-1 Bug #891056 [src:mesa] Reproducible Intel GPU hang on rcs0 with ecode 9:0:0x86dd Marked as fixed in versions mesa/17.3.6-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 891056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Move bug to proper package
Processing commands for cont...@bugs.debian.org: > reassign 891674 libpciaccess 0.13.4-1+b2 Bug #891674 [xserver-xorg-core] xserver-xorg-core: crashes if started as root Bug reassigned from package 'xserver-xorg-core' to 'libpciaccess'. No longer marked as found in versions xorg-server/2:1.19.6-1. Ignoring request to alter fixed versions of bug #891674 to the same values previously set Bug #891674 [libpciaccess] xserver-xorg-core: crashes if started as root There is no source info for the package 'libpciaccess' at version '0.13.4-1+b2' with architecture '' Unable to make a source version for version '0.13.4-1+b2' Marked as found in versions 0.13.4-1+b2. > quit Stopping processing here. Please contact me if you need assistance. -- 891674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891579: marked as done (libinput10: Crashes Xorg with assertion failed)
Your message dated Wed, 28 Feb 2018 16:35:04 + with message-id and subject line Bug#891579: fixed in libinput 1.10.1-1 has caused the Debian Bug report #891579, regarding libinput10: Crashes Xorg with assertion 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.) -- 891579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libinput10 Version: 1.10.0-1 Severity: important Tags: fixed-upstream patch Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=105160 See Forwarded. This happens to me once every few hours while using my touchpad. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: libinput Source-Version: 1.10.1-1 We believe that the bug you reported is fixed in the latest version of libinput, 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 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated libinput 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, 28 Feb 2018 18:20:21 +0200 Source: libinput Binary: libinput10 libinput-bin libinput10-udeb libinput-dev libinput-tools Architecture: source Version: 1.10.1-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libinput-bin - input device management and event handling library - udev quirks libinput-dev - input device management and event handling library - development libinput-tools - input device management and event handling library - command line libinput10 - input device management and event handling library - shared libra libinput10-udeb - input device management and event handling library - shared libra (udeb) Closes: 891579 Launchpad-Bugs-Fixed: 1750664 Changes: libinput (1.10.1-1) unstable; urgency=medium . * New upstream release. - fix crashers (Closes: #891579) (LP: #1750664) Checksums-Sha1: bfd2e511b924023d7c058d95989458853d8588a0 2589 libinput_1.10.1-1.dsc 1b2a8970960998c5798b0ecba07dcaab2b340084 495644 libinput_1.10.1.orig.tar.xz 48a7d500a487ea222c75767ffb548eef887570f8 241 libinput_1.10.1.orig.tar.xz.asc a1b40d210bd3c43b90b189cecb5af781b78e8fd3 8004 libinput_1.10.1-1.debian.tar.xz 96f68cbfab560c0d705b4ef7d5d2e43150318be3 6133 libinput_1.10.1-1_source.buildinfo Checksums-Sha256: 4787c914e40762c26d93546588f038ea3e1e5e8bd9877495a1823e5272597b21 2589 libinput_1.10.1-1.dsc 877522d76575e1945c7b3a9eb92cab90d5ad0379c4ef0dbe13054e489d4c6665 495644 libinput_1.10.1.orig.tar.xz 1d4116e56944c395eefa559bdd5e30771c838f9a04f75b59bec4beca33356efb 241 libinput_1.10.1.orig.tar.xz.asc 36af35cb77651a101523ab976a29a88ed82bb311629fcc7de0d0bcf70c0d012a 8004 libinput_1.10.1-1.debian.tar.xz 42c629de0b0e20c78828100efb0b63fd718b0d3af76bffed773a7ee1cfab3fb6 6133 libinput_1.10.1-1_source.buildinfo Files: 4bdf434dcab5a257012b155aec06903e 2589 libs optional libinput_1.10.1-1.dsc b3d009f36691cb9c340a18109df837ef 495644 libs optional libinput_1.10.1.orig.tar.xz 8279b775716f8dccd198634e223541fe 241 libs optional libinput_1.10.1.orig.tar.xz.asc a7f002a11f53acf886bf9817af224f99 8004 libs optional libinput_1.10.1-1.debian.tar.xz 423e0fe72ca1799eeaa31ce04f005c45 6133 libs optional libinput_1.10.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlqW1ucACgkQy3AxZaiJ hNy8kA//XvaUQNxcAbVSRoisb/qgDANq+X5h7w/H0335U4g+A2gJ9SoWSF9khRLe WTx/utQp9r2F2FyldW9Bh+OYhRFOASKMhik6v6AnGdu+THfu3+khvMjhhI39XObc sn7ZwLmqalxQkbn2qXdqTuxvGJOJbglswuhudjba6whkKANOIB4ZOJK41JbR/zrj 9+akS2hShg3lEKzu1gpWWMVqlYLl5SOFyzPQi+HztV2Te2uBSn7uYdUcMciicU5b WuE/N8BFDvAo7FSCqaVXW6r+NOYaUol5H89ZjcKOWvKC5yZf8+b8Kgw59aPJ9
Bug#890795: marked as done (New upstream versions 1.12 and 1.13)
Your message dated Thu, 1 Mar 2018 04:23:07 -0500 with message-id and subject line Re: New upstream versions 1.12 and 1.13 has caused the Debian Bug report #890795, regarding New upstream versions 1.12 and 1.13 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.) -- 890795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wayland-protocols Version: 1.11-1 Severity: wishlist Hi, version 1.12 was tagged in december https://cgit.freedesktop.org/wayland/wayland-protocols/tag/?h=1.12 and 1.13 just recently. Let me know if I can help e.g. by a NMU to experimental. Cheers, -- Guido -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- wayland-protocols (1.13-1) unstable; urgency=medium . * New upstream release. * Switch priority from extra to optional. * Switch Vcs to salsa.--- End Message ---
Bug#889681: marked as done (wayland: CVE-2017-16612)
Your message dated Sun, 04 Mar 2018 11:22:06 + with message-id and subject line Bug#889681: fixed in wayland 1.14.0-2 has caused the Debian Bug report #889681, regarding wayland: CVE-2017-16612 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.) -- 889681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wayland Version: 1.6.0-1 Severity: important Tags: patch security upstream Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=103961 Hi, the following vulnerability was published for wayland. CVE-2017-16612[0]: | libXcursor before 1.1.15 has various integer overflows that could lead | to heap buffer overflows when processing malicious cursors, e.g., with | programs like GIMP. It is also possible that an attack vector exists | against the related code in cursor/xcursor.c in Wayland through | 1.14.0. Note, I asked MITRE for advice if the CVE should apply as well to wayland leading to the above updated description. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-16612 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16612 [1] https://bugs.freedesktop.org/show_bug.cgi?id=103961 [2] https://cgit.freedesktop.org/wayland/wayland/commit/?id=5d201df72f3d4f4cb8b8f75f980169b03507da38 [3] https://lists.freedesktop.org/archives/wayland-devel/2017-November/035979.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: wayland Source-Version: 1.14.0-2 We believe that the bug you reported is fixed in the latest version of wayland, 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 889...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated wayland 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, 04 Mar 2018 11:56:31 +0100 Source: wayland Binary: libwayland-client0 libwayland-server0 libwayland-cursor0 libwayland-dev libwayland-doc libwayland-bin Architecture: source Version: 1.14.0-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Héctor Orón Martínez Description: libwayland-bin - wayland compositor infrastructure - binary utilities libwayland-client0 - wayland compositor infrastructure - client library libwayland-cursor0 - wayland compositor infrastructure - cursor library libwayland-dev - wayland compositor infrastructure - development files libwayland-doc - wayland compositor infrastructure - documentation files libwayland-server0 - wayland compositor infrastructure - server library Closes: 889681 Changes: wayland (1.14.0-2) unstable; urgency=medium . * debian/patches/CVE-2017-16612.patch: (Closes: #889681) - libXcursor before 1.1.15 has various integer overflows that could lead to heap buffer overflows when processing malicious cursors, e.g., with programs like GIMP. It is also possible that an attack vector exists against the related code in cursor/xcursor.c in Wayland through 1.14.0. * switch back to use upstream tarball * debian/control: bump standards version, drop priority stanzas Checksums-Sha1: 6f88a222b16d48ba31319b683d2c6051c62f16df 2404 wayland_1.14.0-2.dsc 07fb66726fa530902982c494867ebffb2be23f73 673438 wayland_1.14.0.orig.tar.gz bf08b8a4c3a1f542ed8aa264242eda1aeb687291 10855 wayland_1.14.0-2.diff.gz 53765ac72a781ae713afed17f3d0c5033b733d75 5599 wayland_1.14.0-2_source.buildinfo Checksums-Sha256: bd10ee4e17a0cc97590890d74fc3094ca06f6f1eca1d022260b85717717d6fa1 2404 wayland_1.14.0-2.dsc 6042516a27d56ad78dab123fbde7ba697ae6af1080ab9f9ca9f9783a888ce8db 673438 wayland_1.14.0.orig.tar.gz 06db73e127907b3033a1caf1fd36a6701b427795763d369f914d836d5d8a7c05 10855 wayland_1.14.0-2.diff.gz ae059f2b221d32bbfb8317031945212f4f2299f4899565aadcaebfe79c8bbdb4 5599 wayland_1.14.0-2_source.buildinfo Files: 6adaa0fdfa79ed38064c7ea1f687
Processed: tagging 854627
Processing commands for cont...@bugs.debian.org: > tags 854627 + wontfix Bug #854627 [src:wayland] root applications will not run under wayland Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 854627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: glibc 2.27 is now in unstable
ty set to 'serious' from 'important'
> severity 891337 serious
Bug #891337 [src:mia] mia: FTBFS with glibc 2.27: error: 'HUGE' was not
declared in this scope
Severity set to 'serious' from 'important'
> severity 891338 serious
Bug #891338 [src:micropolis-activity] micropolis-activity: FTBFS with glibc
2.27: error: 'DOMAIN' undeclared (first use in this function)
Severity set to 'serious' from 'important'
> tags 891338 buster sid
Bug #891338 [src:micropolis-activity] micropolis-activity: FTBFS with glibc
2.27: error: 'DOMAIN' undeclared (first use in this function)
Added tag(s) buster and sid.
> severity 891372 serious
Bug #891372 [kbuild] kbuild: FTBFS with glibc 2.27: undefined reference to
`__alloca'
Severity set to 'serious' from 'important'
> severity 891373 serious
Bug #891373 [src:gridengine] gridengine: FTBFS with glibc 2.27: undefined
reference to `__alloca'
Severity set to 'serious' from 'important'
> severity 891335 serious
Bug #891335 [clonalframe] clonalframe: FTBFS with glibc 2.27: error:
'UNDERFLOW' was not declared in this scope
Severity set to 'serious' from 'important'
> severity 891336 serious
Bug #891336 [lynkeos.app] lynkeos.app: FTBFS with glibc 2.27: error: 'HUGE'
undeclared (first use in this function)
Severity set to 'serious' from 'important'
> tags 891336 buster sid
Bug #891336 [lynkeos.app] lynkeos.app: FTBFS with glibc 2.27: error: 'HUGE'
undeclared (first use in this function)
Added tag(s) sid and buster.
> severity 891368 serious
Bug #891368 {Done: Dima Kogan } [remake] remake: FTBFS with
glibc 2.27: undefined reference to `__alloca'
Severity set to 'serious' from 'important'
> found 891368 4.1+dbg1.1+dfsg-1
Bug #891368 {Done: Dima Kogan } [remake] remake: FTBFS with
glibc 2.27: undefined reference to `__alloca'
Marked as found in versions remake/4.1+dbg1.1+dfsg-1.
> tags 891368 buster sid
Bug #891368 {Done: Dima Kogan } [remake] remake: FTBFS with
glibc 2.27: undefined reference to `__alloca'
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
890271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890271
890631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890631
890633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890633
890634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890634
890669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890669
890671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890671
890672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890672
890679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890679
890716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890716
891272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891272
891275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891275
891292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891292
891293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891293
891299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891299
891335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891335
891336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891336
891337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891337
891338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891338
891365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891365
891368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891368
891372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891372
891373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891373
891375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891375
891679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#788861: marked as done (unsatisfiable cross Build-Depends)
Your message dated Wed, 07 Mar 2018 09:20:02 + with message-id and subject line Bug#788861: fixed in libxcb 1.13-1 has caused the Debian Bug report #788861, regarding unsatisfiable cross 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.) -- 788861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxcb Version: 1.10-3 Tags: patch User: helm...@debian.org Usertags: rebootstrap Currently, trying to satisfy cross Build-Depends for libxcb fails, because the python dependency selects the host arch python and the python-xcbgen dependency requires the build arch python. The solution to this problem is to add ":native" (or ":any") to the python dependency. In addition, it would be nice if building check could be avoided. This requires marking the check dependency with the nocheck build profile. Please consider applying the attached patch. Helmut diff -u libxcb-1.10/debian/changelog libxcb-1.10/debian/changelog --- libxcb-1.10/debian/changelog +++ libxcb-1.10/debian/changelog @@ -1,3 +1,12 @@ +libxcb (1.10-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Make dependencies cross-sastifiable (closes: #-1). ++ Mark python dependency with :native to pick an executable python. ++ Do not build-depend on check when the nocheck profile is passed. + + -- Helmut Grohne Mon, 15 Jun 2015 15:24:14 +0200 + libxcb (1.10-3) unstable; urgency=medium * Add missing dependencies to libxcb-present-dev. Thanks, Michel Dänzer! diff -u libxcb-1.10/debian/control libxcb-1.10/debian/control --- libxcb-1.10/debian/control +++ libxcb-1.10/debian/control @@ -12,11 +12,11 @@ debhelper (>= 8.9.4~), pkg-config, xsltproc (>= 1.1.19), - check (>= 0.9.4-2), + check (>= 0.9.4-2) , python-xcbgen (>= 1.10), libtool, automake, - python, + python:native, dctrl-tools Build-Depends-Indep: # libxcb-doc --- End Message --- --- Begin Message --- Source: libxcb Source-Version: 1.13-1 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 788...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (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: SHA512 Format: 1.8 Date: Wed, 07 Mar 2018 10:57:47 +0200 Source: libxcb Binary: libxcb1 libxcb1-udeb libxcb1-dev libxcb-doc libxcb-composite0 libxcb-composite0-dev libxcb-damage0 libxcb-damage0-dev libxcb-dpms0 libxcb-dpms0-dev libxcb-glx0 libxcb-glx0-dev libxcb-randr0 libxcb-randr0-dev libxcb-record0 libxcb-record0-dev libxcb-render0 libxcb-render0-dev libxcb-res0 libxcb-res0-dev libxcb-screensaver0 libxcb-screensaver0-dev libxcb-shape0 libxcb-shape0-dev libxcb-shm0 libxcb-shm0-dev libxcb-sync1 libxcb-sync-dev libxcb-xf86dri0 libxcb-xf86dri0-dev libxcb-xfixes0 libxcb-xfixes0-dev libxcb-xinerama0 libxcb-xinerama0-dev libxcb-xtest0 libxcb-xtest0-dev libxcb-xv0 libxcb-xv0-dev libxcb-xvmc0 libxcb-xvmc0-dev libxcb-dri2-0 libxcb-dri2-0-dev libxcb-present0 libxcb-present-dev libxcb-dri3-0 libxcb-dri3-dev libxcb-xkb1 libxcb-xkb-dev Architecture: source Version: 1.13-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libxcb-composite0 - X C Binding, composite extension libxcb-composite0-dev - X C Binding, composite extension, development files libxcb-damage0 - X C Binding, damage extension libxcb-damage0-dev - X C Binding, damage extension, development files libxcb-doc - X C Binding, development documentation libxcb-dpms0 - X C Binding, dpms extension libxcb-dpms0-dev - X C Binding, dpms extension, development files libxcb-dri2-0 - X C Binding, dri2 extension libxcb-dri2-0-dev - X C Binding, dri2 extension, development files libxcb-dri3-0 - X C Binding, dri3 extension libxcb-dri3-dev - X C Binding, dri3 extension, development files libxcb-glx0 - X C Binding, glx extension libxcb-glx0-dev - X C Binding, glx extension, development files libxcb-present-dev - X C Binding, p
Bug#892215: marked as done (libxcb FTBFS: KeyError: 'eventstruct')
Your message dated Wed, 07 Mar 2018 09:20:02 + with message-id and subject line Bug#892215: fixed in libxcb 1.13-1 has caused the Debian Bug report #892215, regarding libxcb FTBFS: KeyError: 'eventstruct' 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.) -- 892215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxcb Version: 1.12-1 Severity: serious Justification: FTBFS User: helm...@debian.org Usertags: rebootstrap Since a few days(?), libxcb FTBFS. The build ends with: | make[1]: Entering directory '/<>/build' | Making all in src | make[2]: Entering directory '/<>/build/src' | /usr/bin/python ../../src/c_client.py -c "libxcb 1.12" -l "X Version 11" \ | -s "3" -p /usr/lib/python2.7/dist-packages \ | \ | /usr/share/xcb/xproto.xml | Traceback (most recent call last): | File "../../src/c_client.py", line 3294, in | from xcbgen.state import Module | File "/usr/lib/python2.7/dist-packages/xcbgen/state.py", line 7, in | from xcbgen import matcher | File "/usr/lib/python2.7/dist-packages/xcbgen/matcher.py", line 12, in | from xcbgen.xtypes import * | File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1221, in | class EventStruct(Union): | File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1239, in EventStruct | out = __main__.output['eventstruct'] | KeyError: 'eventstruct' | make[2]: *** [Makefile:1290: xproto.c] Error 1 | make[2]: Leaving directory '/<>/build/src' | make[1]: *** [Makefile:787: all-recursive] Error 1 | make[1]: Leaving directory '/<>/build' | dh_auto_build: cd build && make -j1 returned exit code 2 | make: *** [debian/rules:17: build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 libxcb wasn't uploaded in a while. Very likely, the cause lies elsewhere. The earliest failure I have seen was Tue, 6 Mar 2018 06:31:35 (UTC), so it should be close to the dinstall prior to that. Could it be the xcb-proto/1.13-1 upload? Helmut --- End Message --- --- Begin Message --- Source: libxcb Source-Version: 1.13-1 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 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (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: SHA512 Format: 1.8 Date: Wed, 07 Mar 2018 10:57:47 +0200 Source: libxcb Binary: libxcb1 libxcb1-udeb libxcb1-dev libxcb-doc libxcb-composite0 libxcb-composite0-dev libxcb-damage0 libxcb-damage0-dev libxcb-dpms0 libxcb-dpms0-dev libxcb-glx0 libxcb-glx0-dev libxcb-randr0 libxcb-randr0-dev libxcb-record0 libxcb-record0-dev libxcb-render0 libxcb-render0-dev libxcb-res0 libxcb-res0-dev libxcb-screensaver0 libxcb-screensaver0-dev libxcb-shape0 libxcb-shape0-dev libxcb-shm0 libxcb-shm0-dev libxcb-sync1 libxcb-sync-dev libxcb-xf86dri0 libxcb-xf86dri0-dev libxcb-xfixes0 libxcb-xfixes0-dev libxcb-xinerama0 libxcb-xinerama0-dev libxcb-xtest0 libxcb-xtest0-dev libxcb-xv0 libxcb-xv0-dev libxcb-xvmc0 libxcb-xvmc0-dev libxcb-dri2-0 libxcb-dri2-0-dev libxcb-present0 libxcb-present-dev libxcb-dri3-0 libxcb-dri3-dev libxcb-xkb1 libxcb-xkb-dev Architecture: source Version: 1.13-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libxcb-composite0 - X C Binding, composite extension libxcb-composite0-dev - X C Binding, composite extension, development files libxcb-damage0 - X C Binding, damage extension libxcb-damage0-dev - X C Binding, damage extension, development files libxcb-doc - X C Binding, development documentation libxcb-dpms0 - X C Binding, dpms extension libxcb-dpms0-dev - X C Binding, dpms extension, development files libxcb-dri2-0 - X C Binding, dri2 extension libxcb-dr
Bug#881014: marked as done (vulkan-utils: upstream adapted Apache-2.0 but debian/copyright wrongly says it's MIT)
Your message dated Thu, 08 Mar 2018 07:19:41 + with message-id and subject line Bug#881014: fixed in vulkan 1.0.68+dfsg1-1 has caused the Debian Bug report #881014, regarding vulkan-utils: upstream adapted Apache-2.0 but debian/copyright wrongly says it's MIT 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.) -- 881014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vulkan-utils Version: 1.0.61.1+dfsg1-1 Severity: serious Justification: 1 Compare https://anonscm.debian.org/cgit/pkg-xorg/lib/vulkan.git/tree/debian/copyright with https://anonscm.debian.org/cgit/pkg-xorg/lib/vulkan.git/tree/COPYRIGHT.txt (and https://anonscm.debian.org/cgit/pkg-xorg/lib/vulkan.git/tree/LICENSE.txt ) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vulkan-utils depends on: ii libc6 2.24-17 ii libgcc1 1:7.2.0-12 ii libstdc++6 7.2.0-12 ii libvulkan1 1.0.61.1+dfsg1-1 ii libxcb1 1.12-1 vulkan-utils recommends no packages. vulkan-utils suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: vulkan Source-Version: 1.0.68+dfsg1-1 We believe that the bug you reported is fixed in the latest version of vulkan, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated vulkan 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, 08 Mar 2018 08:55:08 +0200 Source: vulkan Binary: libvulkan1 libvulkan-dev vulkan-utils Architecture: source Version: 1.0.68+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libvulkan-dev - Vulkan loader library -- development files libvulkan1 - Vulkan loader library vulkan-utils - Miscellaneous Vulkan utilities Closes: 881014 Changes: vulkan (1.0.68+dfsg1-1) unstable; urgency=medium . [ Timo Aaltonen ] * New upstream release. * copyright: Updated. (Closes: #881014) * patches: Refreshed. * get-external.sh: Use upstream script to update glslang and spirv- tools/headers. * get-external.sh, use-known-sha.diff: Don't require git, grep the spirv sha from known-good.json and use that. * rules: Update glslang build. * rules: Tell cmake where glslangValidator is. * rules: Update clean target. * control: Update VCS urls. * control: Bump policy to 4.1.3, no changes. . [ Andreas Boll ] * debian/get-external.sh: Append external Git revision of glslang to the commit message. * Add man pages for vulkaninfo and vulkan-smoketest. Checksums-Sha1: dc0939f43398ce0476114b7bbaf1d17a5b61b809 2218 vulkan_1.0.68+dfsg1-1.dsc 38099949e76d711238f10314805b8b0742a2d18b 4181996 vulkan_1.0.68+dfsg1.orig.tar.xz 7a27ee3c4c523f7bbda1cbe23bef342acd96f3ff 7916 vulkan_1.0.68+dfsg1-1.debian.tar.xz a81ad91d82784e17d4702d1a57f8fbb75d09ff75 7256 vulkan_1.0.68+dfsg1-1_source.buildinfo Checksums-Sha256: 1ebc084d0f8480a6718085181f578d1b5d5a12e4a175deb6e2fb2e90ebe189ee 2218 vulkan_1.0.68+dfsg1-1.dsc 6c6b24760f76b34666d175dde7417214db35ae0e5cafd3423c69a715799a4e35 4181996 vulkan_1.0.68+dfsg1.orig.tar.xz 56db463de380a274c6813a0a170220707cf82307675bfeab1d2ca0a581cbe67a 7916 vulkan_1.0.68+dfsg1-1.debian.tar.xz 95740e2fa7deba10e51058418a53dfbd4122270321861e5c3830b853107d243e 7256 vulkan_1.0.68+dfsg1-1_source.buildinfo Files: b54ba782c7b7ddb8497a83b5bf2f349c 2218 libs optional vulkan_1.0.68+dfsg1-1.dsc 2c0c49dec09cfe2bcedc6504a1d6bedd 4181996 libs optional vulkan_1.0.68+dfsg1.orig.tar.xz 0c455f117262b73a208536c7d3a22bed 7916 libs optional vulkan_1.0.68+dfsg1-1.debian.tar.xz 0efe2b4ec5391534ffcda5d77ae99e4
Processed: [bts-link] source package mesa
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package mesa > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #423606 (http://bugs.debian.org/423606) > # Bug title: segmentation fault of k3dsurf on start up > # * https://bugs.freedesktop.org/show_bug.cgi?id=13705 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> INVALID > # * closed upstream > tags 423606 + fixed-upstream Bug #423606 [libgl1-mesa-dri] segmentation fault of k3dsurf on start up Added tag(s) fixed-upstream. > usertags 423606 - status-NEW Usertags were: status-NEW. Usertags are now: . > usertags 423606 + status-RESOLVED resolution-INVALID There were no usertags set. Usertags are now: resolution-INVALID status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. -- 423606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#876100: marked as done (libglvnd-dev: libglvnd-dev not coinstallable with nvidia packages)
Your message dated Sat, 10 Mar 2018 17:00:28 +
with message-id
and subject line Bug#876100: fixed in nvidia-graphics-drivers 384.111-4~deb9u1
has caused the Debian Bug report #876100,
regarding libglvnd-dev: libglvnd-dev not coinstallable with nvidia packages
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.)
--
876100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglvnd-dev
Severity: normal
Dear Maintainer,
libglvnd depends on many OpenGL related packages like libgl1, specified
by concrete version. This means those dependencies can't be satisfied
with virtual packages, ie. nvidia packages providing libgl1. However,
those nvidia packages conflict with any other packages providing those
names, particularly libgl1 et al. provided by libglvnd.
In effect, this makes development packages like
- libegl1-mesa-dev
- libsdl2-dev
- qtbase5-dev
uninstallable on systems with nvidia packages installed. This
restriction didn't exist with mesa packages older than 17.2.0.
Please check if that conflict can be rectified, either on the
libglvnd-dev side, or the nvidia packages (CC-d).
Regards
Jiri Palecek
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 4.13.0-trunk-686-pae (SMP w/2 CPU cores)
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ
(charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 384.111-4~deb9u1
We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated nvidia-graphics-drivers
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: Mon, 26 Feb 2018 01:45:42 +0100
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs
nvidia-driver-libs-i386 nvidia-driver-libs-nonglvnd
nvidia-driver-libs-nonglvnd-i386 xserver-xorg-video-nvidia nvidia-legacy-check
libglvnd0-nvidia libopengl0-glvnd-nvidia libglx0-glvnd-nvidia libglx-nvidia0
libgl1-glvnd-nvidia-glx libgl1-nvidia-glvnd-glx libgl1-nvidia-glx
libnvidia-glcore libegl1-glvnd-nvidia libegl1-nvidia libegl-nvidia0
libgles1-glvnd-nvidia libgles1-nvidia libgles-nvidia1 libgles2-glvnd-nvidia
libgles2-nvidia libgles-nvidia2 libnvidia-eglcore nvidia-egl-common
nvidia-egl-icd libnvidia-egl-wayland1 nvidia-egl-wayland-common
nvidia-egl-wayland-icd nvidia-vulkan-common nvidia-vulkan-icd
nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-icd libnvidia-cfg1
nvidia-alternative nvidia-kernel-support nvidia-kernel-dkms
nvidia-kernel-source nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1
libcuda1-i386 libnvidia-compiler libnvidia-fatbinaryloader
libnvidia-ptxjitcompiler1 libnvcuvid1
libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1
nvidia-detect
Architecture: source i386
Version: 384.111-4~deb9u1
Distribution: stretch
Urgency: high
Maintainer: Debian NVIDIA Maintainers
Changed-By: Andreas Beckmann
Description:
libcuda1 - NVIDIA CUDA Driver Library${nvidia:LegacyDesc}
libcuda1-i386 - NVIDIA CUDA 32-bit runtime library${nvidia:LegacyDesc}
libegl-nvidia0 - NVIDIA binary EGL library${nvidia:LegacyDesc}
libegl1-glvnd-nvidia - Vendor neutral GL dispatch library -- libEGL
libegl1-nvidia - NVIDIA binary EGL library (non-GLVND
variant)${nvidia:LegacyDesc}
libgl1-glvnd-nvidia-glx - Vendor neutral GL dispatch library -- libGL
libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND
variant)${nvidia:LegacyDe
libgl1-nvidia-glx - NVIDIA binary
Processed: tagging 859841, tagging 892415, tagging 892529, tagging 865585, tagging 865606, tagging 891307 ...
Processing commands for cont...@bugs.debian.org:
> tags 859841 + experimental
Bug #859841 {Done: Jan Niehusmann } [zurl] zurl: Please
migrate to openssl1.1 in Buster
Added tag(s) experimental.
> tags 892415 + experimental
Bug #892415 [nvidia-cuda-toolkit] nvcc wants GCC 6 which we want to remove
Added tag(s) experimental.
> tags 892529 + experimental
Bug #892529 [src:java-common] java-common: Depends on GCJ which is going away
Added tag(s) experimental.
> tags 865585 + sid buster
Bug #865585 [src:apex] apex FTBFS: No rule to make target
'debian-nslu2-armel_config'. Stop.
Added tag(s) sid and buster.
> tags 865606 + sid buster
Bug #865606 {Done: Sebastien Jodogne } [src:orthanc]
orthanc FTBFS with libdcmtk-dev 3.6.1~20170228-2
Added tag(s) sid and buster.
> tags 891307 + sid buster
Bug #891307 [src:activity-log-manager] activity-log-manager: Depends on NBS
python-zeitgeist
Added tag(s) buster and sid.
> tags 890716 + sid buster
Bug #890716 [src:xfsprogs] xfsprogs: FTBFS with glibc 2.27: error: conflicting
types for 'copy_file_range'
Added tag(s) sid and buster.
> fixed 890716 4.15.1-1
Bug #890716 [src:xfsprogs] xfsprogs: FTBFS with glibc 2.27: error: conflicting
types for 'copy_file_range'
Marked as fixed in versions xfsprogs/4.15.1-1.
> tags 867945 + sid buster experimental
Bug #867945 [src:moonshot-ui] moonshot-ui: Build-Depends on deprecated
libgnome-keyring-dev
Added tag(s) sid, buster, and experimental.
> tags 892215 + sid buster
Bug #892215 {Done: Timo Aaltonen } [src:libxcb] libxcb
FTBFS: KeyError: 'eventstruct'
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
859841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859841
865585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865585
865606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865606
867945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867945
890716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890716
891307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891307
892215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892215
892415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892415
892529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#891582: Dependency missing in vulkan-utils
Processing commands for cont...@bugs.debian.org: > severity 891582 normal Bug #891582 [vulkan] Dependency missing in vulkan-utils Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 891582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#892714: marked as done (libinput10: Crashes Gnome session)
Your message dated Wed, 14 Mar 2018 09:34:51 + with message-id and subject line Bug#892714: fixed in libinput 1.10.3-1 has caused the Debian Bug report #892714, regarding libinput10: Crashes Gnome session 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.) -- 892714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libinput10 Version: 1.10.2-1 Severity: important Dear Maintainer, Upgrading to 1.10.2-1 causes serious stability issues on Gnome-Shell. Trying to scroll on an XWayland window (Firefox in my case) crashes the Wayland session, sending the user to the login screen. All unsaved work is obviously lost. Downgrading to 1.10.1-1 fixes the problem. One of the errors I get on my syslog is the same as addressed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891579. I was experiencing that bug too, which had been fixed in 1.10.1-1. The error is more explicitly: gnome-shell: ../src/evdev-mt-touchpad-tap.c:1028: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed. Regards, -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libinput10 depends on: ii libc6 2.27-1 ii libevdev2 1.5.8+dfsg-1 ii libinput-bin 1.10.2-1 ii libmtdev1 1.1.5-1+b1 ii libudev1 237-4 ii libwacom2 0.26-1 libinput10 recommends no packages. libinput10 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libinput Source-Version: 1.10.3-1 We believe that the bug you reported is fixed in the latest version of libinput, 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 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated libinput 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, 14 Mar 2018 11:04:22 +0200 Source: libinput Binary: libinput10 libinput-bin libinput10-udeb libinput-dev libinput-tools Architecture: source Version: 1.10.3-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libinput-bin - input device management and event handling library - udev quirks libinput-dev - input device management and event handling library - development libinput-tools - input device management and event handling library - command line libinput10 - input device management and event handling library - shared libra libinput10-udeb - input device management and event handling library - shared libra (udeb) Closes: 892714 Changes: libinput (1.10.3-1) unstable; urgency=medium . * New upstream release. (Closes: #892714) Checksums-Sha1: b7ff051e77a6219a3cb56740a15bb4f7106304f1 2589 libinput_1.10.3-1.dsc 164c2463a34d0e39f55741fbf607d6dcdce873a7 493216 libinput_1.10.3.orig.tar.xz 1c03c161f08e3ffee93238e85a1de5d1d38c27a4 482 libinput_1.10.3.orig.tar.xz.asc 95749ae4a0ebafa25f27773f849b3037bec28f11 8048 libinput_1.10.3-1.debian.tar.xz b10f32c1d0445efe7d38de5edb10fc76fd6d42e7 6163 libinput_1.10.3-1_source.buildinfo Checksums-Sha256: 4987b28878f771c5e38dfa68a2cc3f763169c24d034132f62150b6538dc96cc6 2589 libinput_1.10.3-1.dsc 0d52909584027ff6fcaba865c4454b77e91a2dba3c6cf520cdf87eccd2ec0200 493216 libinput_1.10.3.orig.tar.xz 79eae3c760609f9a03ce2babf3253d4f07914894d569ffe9a8ec5f8cfa44284e 482 libinput_1.10.3.orig.tar.xz.asc 5b98aedfddf5873d393bbce9a611c1020e3ddd17222a72e13c6f9b45c825185d 8048 libinput_1.10.3-1.debian.tar.xz dfc37b968be7559cf3f9d701e4da7c4573989499558f5eef02fc17185c735cc2 6163 libinput_1.10.3-1_source.buildinfo Files: 736fa3131d9b2893216a9b0576711291 2589 libs optional libinput_1.10.3-1.dsc ffcf71ec913988c1c1a79a2169d71651 493216 libs optional libinput_1.10.3.orig.tar.xz 4
Processed: Re: Bug#892916: libinput: Invalid tap event TAP_EVENT_RELEASE in state TAP_STATE_{TAPPED,MULTITAP}
Processing control commands:
> found -1 1.10.3-1
Bug #892916 [libinput] libinput: Invalid tap event TAP_EVENT_RELEASE in state
TAP_STATE_{TAPPED,MULTITAP}
There is no source info for the package 'libinput' at version '1.10.3-1' with
architecture ''
Unable to make a source version for version '1.10.3-1'
Marked as found in versions 1.10.3-1.
--
892916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: libinput-dev: Requires.private without package dependencies breaks pkg-config users
Processing control commands: > affects -1 src:efl src:gnome-twitch src:muffin src:mutter src:gnome-shell Bug #892956 [libinput-dev] libinput-dev: Requires.private without package dependencies breaks pkg-config users Added indication that 892956 affects src:efl, src:gnome-twitch, src:muffin, src:mutter, and src:gnome-shell -- 892956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#892960: libdrm FTBFS on arm*: symbol differences
Processing control commands: > tags -1 + pending Bug #892960 [src:libdrm] libdrm FTBFS on arm*: symbol differences Added tag(s) pending. -- 892960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#892916: libinput: Invalid tap event TAP_EVENT_RELEASE in state TAP_STATE_{TAPPED,MULTITAP}
Processing control commands:
> forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=105512
Bug #892916 [libinput] libinput: Invalid tap event TAP_EVENT_RELEASE in state
TAP_STATE_{TAPPED,MULTITAP}
Set Bug forwarded-to-address to
'https://bugs.freedesktop.org/show_bug.cgi?id=105512'.
--
892916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: affects 892956
Processing commands for cont...@bugs.debian.org: > affects 892956 src:gnome-control-center src:budgie-desktop src:cinnamon > src:totem Bug #892956 [libinput-dev] libinput-dev: Requires.private without package dependencies breaks pkg-config users Added indication that 892956 affects src:gnome-control-center, src:budgie-desktop, src:cinnamon, and src:totem > thanks Stopping processing here. Please contact me if you need assistance. -- 892956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#892982: bugs.debian.org: system freeze after lock screen/switched off moniturs/spontaneously
Processing control commands: > reassign -1 xserver-xorg-video-amdgpu Bug #892982 [bugs.debian.org] bugs.debian.org: system freeze after lock screen/switched off moniturs/spontaneously Bug reassigned from package 'bugs.debian.org' to 'xserver-xorg-video-amdgpu'. Ignoring request to alter found versions of bug #892982 to the same values previously set Ignoring request to alter fixed versions of bug #892982 to the same values previously set -- 892982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users
Processing control commands: > reassign -1 meson 0.45.0-1 Bug #892956 [libinput-dev] libinput-dev: Requires.private without package dependencies breaks pkg-config users Bug reassigned from package 'libinput-dev' to 'meson'. No longer marked as found in versions libinput/1.10.3-1. Ignoring request to alter fixed versions of bug #892956 to the same values previously set Bug #892956 [meson] libinput-dev: Requires.private without package dependencies breaks pkg-config users Marked as found in versions meson/0.45.0-1. > retitle -1 meson creates bogus pkgconfig files Bug #892956 [meson] libinput-dev: Requires.private without package dependencies breaks pkg-config users Changed Bug title to 'meson creates bogus pkgconfig files' from 'libinput-dev: Requires.private without package dependencies breaks pkg-config users'. > affects -1 libinput-dev Bug #892956 [meson] meson creates bogus pkgconfig files Added indication that 892956 affects libinput-dev -- 892956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836687: marked as done (wayland FTCBFS: cross builds require --with-host-scanner)
Your message dated Fri, 16 Mar 2018 09:00:39 + with message-id and subject line Bug#836687: fixed in wayland 1.14.91-1 has caused the Debian Bug report #836687, regarding wayland FTCBFS: cross builds require --with-host-scanner 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.) -- 836687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wayland Version: 1.11.0-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap wayland fails to cross build from source, because cross building requires the configure option --with-host-scanner (and making a wayland-scanner executable available to the build). Adding that flag turned out not to be trivial due to the semantics of override_*-arch. In my attached patch, I thus opt to avoid that technique and add --disable-documentation depending on the dh_listpackages output instead. I hope that works for you. Either way, the gist is that we need --with-host-scanner for cross builds. Helmut diff -u wayland-1.11.0/debian/changelog wayland-1.11.0/debian/changelog --- wayland-1.11.0/debian/changelog +++ wayland-1.11.0/debian/changelog @@ -1,3 +1,11 @@ +wayland (1.11.0-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: (Closes: #-1) ++ Use wayland-scanner from libwayland-bin. + + -- Helmut Grohne Sun, 04 Sep 2016 14:27:28 +0200 + wayland (1.11.0-2) unstable; urgency=medium * d/control: libwayland-dev depends on libwayland-bin diff -u wayland-1.11.0/debian/control wayland-1.11.0/debian/control --- wayland-1.11.0/debian/control +++ wayland-1.11.0/debian/control @@ -12,6 +12,7 @@ libexpat1-dev, libffi-dev, libxml2-dev, + libwayland-bin , Build-Depends-Indep: doxygen, graphviz, diff -u wayland-1.11.0/debian/rules wayland-1.11.0/debian/rules --- wayland-1.11.0/debian/rules +++ wayland-1.11.0/debian/rules @@ -4,9 +4,16 @@ BUILD_DOC= +ifneq (,$(filter cross,$(DEB_BUILD_PROFILES))) +configure_flags += --with-host-scanner +endif # Don't build the documentation when not building arch:all packages -override_dh_auto_configure-arch: - dh_auto_configure -- --disable-documentation +ifeq (,$(filter libwayland-doc,$(shell dh_listpackages))) +configure_flags += --disable-documentation +endif + +override_dh_auto_configure: + dh_auto_configure -- $(configure_flags) # Kill *.la files, and forget no-one: override_dh_install: --- End Message --- --- Begin Message --- Source: wayland Source-Version: 1.14.91-1 We believe that the bug you reported is fixed in the latest version of wayland, 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 836...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated wayland 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 Mar 2018 16:01:40 +0100 Source: wayland Binary: libwayland-client0 libwayland-egl1 libwayland-server0 libwayland-cursor0 libwayland-dev libwayland-doc libwayland-bin Architecture: source amd64 all Version: 1.14.91-1 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Héctor Orón Martínez Description: libwayland-bin - wayland compositor infrastructure - binary utilities libwayland-client0 - wayland compositor infrastructure - client library libwayland-cursor0 - wayland compositor infrastructure - cursor library libwayland-dev - wayland compositor infrastructure - development files libwayland-doc - wayland compositor infrastructure - documentation files libwayland-egl1 - wayland compositor infrastructure - EGL library libwayland-server0 - wayland compositor infrastructure - server library Closes: 836687 857139 Changes: wayland (1.14.91-1) experimental; urgency=medium . [ Helmut Grohne ] * Use wayland-scanner from libwayland-bin (Closes: #836687) - Fixes cross builds . [ Héctor Orón Martínez ] * New upstream pre-release * debian/control: libwayland-dev suggests libwayland-doc (Closes: #857139) * debian/libwayland-server0.symbols: update * debian/control: update priority from ext
Bug#857139: marked as done (Should Suggest: libwayland-doc)
Your message dated Fri, 16 Mar 2018 09:00:39 + with message-id and subject line Bug#857139: fixed in wayland 1.14.91-1 has caused the Debian Bug report #857139, regarding Should Suggest: libwayland-doc 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.) -- 857139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwayland-dev Version: 1.12.0-1 Severity: wishlist It would be nice if libwayland-dev suggested it's reference documentation. Thanks! -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.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 libwayland-dev:amd64 depends on: ii libwayland-bin 1.12.0-1 ii libwayland-client0 1.12.0-1 ii libwayland-cursor0 1.12.0-1 ii libwayland-server0 1.12.0-1 libwayland-dev:amd64 recommends no packages. libwayland-dev:amd64 suggests no packages. --- End Message --- --- Begin Message --- Source: wayland Source-Version: 1.14.91-1 We believe that the bug you reported is fixed in the latest version of wayland, 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 857...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated wayland 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 Mar 2018 16:01:40 +0100 Source: wayland Binary: libwayland-client0 libwayland-egl1 libwayland-server0 libwayland-cursor0 libwayland-dev libwayland-doc libwayland-bin Architecture: source amd64 all Version: 1.14.91-1 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Héctor Orón Martínez Description: libwayland-bin - wayland compositor infrastructure - binary utilities libwayland-client0 - wayland compositor infrastructure - client library libwayland-cursor0 - wayland compositor infrastructure - cursor library libwayland-dev - wayland compositor infrastructure - development files libwayland-doc - wayland compositor infrastructure - documentation files libwayland-egl1 - wayland compositor infrastructure - EGL library libwayland-server0 - wayland compositor infrastructure - server library Closes: 836687 857139 Changes: wayland (1.14.91-1) experimental; urgency=medium . [ Helmut Grohne ] * Use wayland-scanner from libwayland-bin (Closes: #836687) - Fixes cross builds . [ Héctor Orón Martínez ] * New upstream pre-release * debian/control: libwayland-dev suggests libwayland-doc (Closes: #857139) * debian/libwayland-server0.symbols: update * debian/control: update priority from extra to optional * libwayland-egl1: add new package * debian/control: bump standards version Checksums-Sha1: f7cbaaa564c16249f2e8871f2e940436531a618c 2496 wayland_1.14.91-1.dsc bbf0a83759c0085a9db60850da7cfa89e8f87cb6 698135 wayland_1.14.91.orig.tar.gz 216cf50d2c95d41058bc1fbc0de9691fd36f7a79 14660 wayland_1.14.91-1.diff.gz e7c1749d544ad31d4e3b18d08c792d72991cb988 41484 libwayland-bin-dbgsym_1.14.91-1_amd64.deb db5c2e471ef1f1b23929c063486e6364b75a1af7 21772 libwayland-bin_1.14.91-1_amd64.deb be57b105d2b18b58b6f0873731c0a536907f4e1f 47416 libwayland-client0-dbgsym_1.14.91-1_amd64.deb 5176956b9561ff8b1f67f1779b141f9a4d2ebc9d 25760 libwayland-client0_1.14.91-1_amd64.deb d6f600c2d99fd9ec6d5e050cbb66a133d2d41d4f 20452 libwayland-cursor0-dbgsym_1.14.91-1_amd64.deb 4072f02dc146129cd548c5c46561e6e5177b6e37 13380 libwayland-cursor0_1.14.91-1_amd64.deb 272db0446af75a322084af882920e0fe3d2b6128 104832 libwayland-dev_1.14.91-1_amd64.deb 26bae49137ae9b8c335aa28e187d63f4fc191af1 188292 libwayland-doc_1.14.91-1_all.deb c7df91090447940239d4cfd0f39636375a07dccc 4092 libwayland-egl1-dbgsym_1.14.91-1_amd64.deb 03c1b23aa60122926b7b162b08904041dd283deb 7416 libwayland-egl1_1.14.91-1_amd64.deb 377a1064cfd0ca77248d3fc503ed162102d8986d
Bug#892960: marked as done (libdrm FTBFS on arm*: symbol differences)
Your message dated Fri, 16 Mar 2018 12:05:12 + with message-id and subject line Bug#892960: fixed in libdrm 2.4.91-2 has caused the Debian Bug report #892960, regarding libdrm FTBFS on arm*: symbol differences 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.) -- 892960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdrm Version: 2.4.91-1 Severity: serious https://buildd.debian.org/status/package.php?p=libdrm&suite=sid ... debian/rules override_dh_makeshlibs make[1]: Entering directory '/<>' dh_makeshlibs -plibdrm2 -V'libdrm2 (>= 2.4.89)' --add-udeb=libdrm2-udeb -- -c4 dh_makeshlibs -plibdrm-nouveau2 -V'libdrm-nouveau2 (>= 2.4.66)' -- -c4 dh_makeshlibs -plibdrm-radeon1 -V'libdrm-radeon1 (>= 2.4.39)' -- -c4 dh_makeshlibs -plibdrm-amdgpu1 -V'libdrm-amdgpu1 (>= 2.4.90)' -- -c4 dh_makeshlibs -plibdrm-tegra0 -V'libdrm-tegra0' -- -c4 dh_makeshlibs -plibdrm-freedreno1 -V'libdrm-freedreno1 (>= 2.4.89)' -- -c4 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libdrm-freedreno1/DEBIAN/symbols doesn't match completely debian/libdrm-freedreno1.symbols --- debian/libdrm-freedreno1.symbols (libdrm-freedreno1_2.4.91-1_arm64) +++ dpkg-gensymbolsaJO5I2 2018-03-14 07:53:26.403570801 + @@ -7,10 +7,12 @@ fd_bo_from_fbdev@Base 0 fd_bo_from_handle@Base 0 fd_bo_from_name@Base 0 + fd_bo_get_iova@Base 2.4.91-1 fd_bo_get_name@Base 0 fd_bo_handle@Base 0 fd_bo_map@Base 0 fd_bo_new@Base 0 + fd_bo_put_iova@Base 2.4.91-1 fd_bo_ref@Base 0 fd_bo_size@Base 0 fd_device_del@Base 0 dh_makeshlibs: failing due to earlier errors debian/rules:103: recipe for target 'override_dh_makeshlibs' failed make[1]: *** [override_dh_makeshlibs] Error 2 --- End Message --- --- Begin Message --- Source: libdrm Source-Version: 2.4.91-2 We believe that the bug you reported is fixed in the latest version of libdrm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sven Joachim (supplier of updated libdrm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 14 Mar 2018 22:23:03 +0100 Source: libdrm Binary: libdrm-dev libdrm2 libdrm-common libdrm2-udeb libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm-omap1 libdrm-freedreno1 libdrm-exynos1 libdrm-tegra0 libdrm-amdgpu1 libdrm-etnaviv1 Architecture: source Version: 2.4.91-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Sven Joachim Description: libdrm-amdgpu1 - Userspace interface to amdgpu-specific kernel DRM services -- run libdrm-common - Userspace interface to kernel DRM services -- common files libdrm-dev - Userspace interface to kernel DRM services -- development files libdrm-etnaviv1 - Userspace interface to etnaviv-specific kernel DRM services -- ru libdrm-exynos1 - Userspace interface to exynos-specific kernel DRM services -- run libdrm-freedreno1 - Userspace interface to msm/kgsl kernel DRM services -- runtime libdrm-intel1 - Userspace interface to intel-specific kernel DRM services -- runt libdrm-nouveau2 - Userspace interface to nouveau-specific kernel DRM services -- ru libdrm-omap1 - Userspace interface to omap-specific kernel DRM services -- runti libdrm-radeon1 - Userspace interface to radeon-specific kernel DRM services -- run libdrm-tegra0 - Userspace interface to tegra-specific kernel DRM services -- runt libdrm2- Userspace interface to kernel DRM services -- runtime libdrm2-udeb - Userspace interface to kernel DRM services -- runtime (udeb) Closes: 892960 Changes: libdrm (2.4.91-2) unstable; urgency=medium . * Update libdrm-freedreno1.symbols and shlibs (Closes: #892960). Checksums-Sha1: 339048a76a9113f150203bf6af1e0cf8041a0dca 3040 libdrm_2.4.91-2.dsc 1f6dfc63d813ead05db783414a3772bb3fdcf99f 50222 libdrm_2.4.91-2.diff.gz
Processed: Re: libinput-dev: pkg-config file does not work without libwacom-dev installed
Processing control commands: > severity -1 serious Bug #893067 [libinput-dev] libinput-dev: pkg-config file does not work without libwacom-dev installed Severity set to 'serious' from 'important' -- 893067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#893067: libinput-dev: pkg-config file does not work without libwacom-dev installed
Processing control commands: > tags -1 + pending Bug #893067 [libinput-dev] libinput-dev: pkg-config file does not work without libwacom-dev installed Added tag(s) pending. -- 893067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893067: marked as done (libinput-dev: pkg-config file does not work without libwacom-dev installed)
Your message dated Sun, 18 Mar 2018 15:12:16 + with message-id and subject line Bug#893067: fixed in libinput 1.10.3-2 has caused the Debian Bug report #893067, regarding libinput-dev: pkg-config file does not work without libwacom-dev installed 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.) -- 893067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libinput-dev Version: 1.10.3-1 Severity: important Justification: causing numerous new FTBFS bugs In a clean pbuilder chroot: # apt install libinput-dev pkg-config # pkg-config --cflags libinput Package libwacom was not found in the pkg-config search path. Perhaps you should add the directory containing 'libwacom.pc' to the PKG_CONFIG_PATH environment variable Package 'libwacom', required by 'libinput', not found # pkg-config --exists libinput # echo $? 1 I've been seeing several new FTBFS issues in other packages due to this, either due to configure scripts erroring out when they find libinput "does not exist", or in the case of qtbase-opensource-src, the configuration leaves out the libinput plugin which then causes an error at dh_install time. -- Daniel --- End Message --- --- Begin Message --- Source: libinput Source-Version: 1.10.3-2 We believe that the bug you reported is fixed in the latest version of libinput, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated libinput 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, 18 Mar 2018 15:39:44 +0200 Source: libinput Binary: libinput10 libinput-bin libinput10-udeb libinput-dev libinput-tools Architecture: source Version: 1.10.3-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libinput-bin - input device management and event handling library - udev quirks libinput-dev - input device management and event handling library - development libinput-tools - input device management and event handling library - command line libinput10 - input device management and event handling library - shared libra libinput10-udeb - input device management and event handling library - shared libra (udeb) Closes: 893067 Changes: libinput (1.10.3-2) unstable; urgency=medium . [ Jeremy Bicha ] * control: Update VCS urls. * control: Add more packages to libinput-dev Depends as a workaround for buggy meson/pkg-config. (Closes: #893067) Checksums-Sha1: 41d277bc955a9ee213ecd2673e723ff0bbf87364 2574 libinput_1.10.3-2.dsc 620ad3361bb6ed37dfc7efb6dc42a08f661e2e57 8136 libinput_1.10.3-2.debian.tar.xz 68b4631e9286da8da57b4ffb208766d136ea4246 6163 libinput_1.10.3-2_source.buildinfo Checksums-Sha256: ee28dccaaa8d693dc29011de845995a25c99cd77cd3a5711bbdc0a8011391b3d 2574 libinput_1.10.3-2.dsc 3341c4575c00ca835029668a1acba7399594c87cb8f6af7f9d6f5943580874a1 8136 libinput_1.10.3-2.debian.tar.xz daf1c3f5320c7a498f11c1441973a604f09a57a847d003deba31b5295dd29e68 6163 libinput_1.10.3-2_source.buildinfo Files: 74d8db4455a3dbdaccf1f30072c9d676 2574 libs optional libinput_1.10.3-2.dsc ed4151fc0b9e07b316732d488951e08c 8136 libs optional libinput_1.10.3-2.debian.tar.xz 469f9b52e0387a5947f2bb96841472b3 6163 libs optional libinput_1.10.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlqubOEACgkQy3AxZaiJ hNwtqA/+JEKWopt2F5a+T/8UcBfpIdQJ4eNZpbSqWwyYvM2NS+1u3oJIB16RHDFa VTuZfHfeN023ENsGlJKQ0NiF5YTbLwyvZeUP5a175+bGrsxRk70SNdutVfDVqizV OHjzs7sNhO0fJHxjP9A6TtEMbux74rxQqHCdacRhn7J2kjMHWBxTTNCDC6xbey+c 6lC8JAW9RrkSEVtUkvQ6I7UpDr78RBub3DXCGZ6D4ASYVGZhrva3DPHchyNpLFkL Ui8fl5hua+whiqZL7bfZjgmkCeo8g6/nC+7A1HadEn6KyXVqA6ZDG+E8um0L54Gk YI8/7kxWggdqCgGOZZf1ID2vL4J96OULqQFrVHZ7X19kfhcSQEK1pd8I72OebnkD hPcj2+ceaeDvk4qm+ICmeSlNnA73LOwlj2t4Mn9JJ8SCrVPEccvBuLJrO3EDVp3Q BkDY+Uy1Fr0C7Nv6bvWtLzUe8l3bOzbybRMiAu3ILM/KsVWYSAGRpZfrI9EAZAQe sLinQ1qiRFubCYuOg8q
Processed: closing 883929
Processing commands for cont...@bugs.debian.org: > close 883929 1:2.0.3-1 Bug #883929 [src:libxfont] libxfont: CVE-2017-16611: User can trigger reads on special files as root allowing for DoS Marked as fixed in versions libxfont/1:2.0.3-1. Bug #883929 [src:libxfont] libxfont: CVE-2017-16611: User can trigger reads on special files as root allowing for DoS Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 883929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893433: marked as done (libegl1-mesa-dev: File conflicts with libwayland-dev:amd64 1.14.91-1)
Your message dated Sun, 18 Mar 2018 22:43:11 +0100 with message-id <20180318214311.euphco43iyml2...@betterave.cristau.org> and subject line Re: Bug#893433: libegl1-mesa-dev: File conflicts with libwayland-dev:amd64 1.14.91-1 has caused the Debian Bug report #893433, regarding libegl1-mesa-dev: File conflicts with libwayland-dev:amd64 1.14.91-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.) -- 893433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libegl1-mesa-dev Version: 18.0.0~rc4-1 Severity: serious Justification: File conflicts Hi! While trying to build qtwayland I ran across: dpkg: error processing archive /tmp/apt-dpkg-install-VBKAMl/062-libegl1-mesa-dev_18.0.0~rc4-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libwayland-dev:amd64 1.14.91-1 Admitedly I'm using a build against experimental using aspcud as dep resolver, as I need to build Qt in experimental, so maybe this is related. Thanks, Lisandro. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libegl1-mesa-dev depends on: ii libdrm-dev2.4.91-1 ii libglvnd-dev 1.0.0-2 pn libwayland-dev ii libwayland-egl1-mesa 17.3.6-1 ii libx11-dev2:1.6.4-3 ii libx11-xcb-dev2:1.6.4-3 ii libxcb-dri2-0-dev 1.13-1 ii libxcb-dri3-dev 1.13-1 ii libxcb-glx0-dev 1.13-1 ii libxcb-present-dev1.13-1 ii libxcb-sync-dev 1.13-1 ii libxdamage-dev1:1.1.4-3 ii libxext-dev 2:1.3.3-1+b2 ii libxfixes-dev 1:5.0.3-1 ii libxshmfence-dev 1.2-1+b2 ii libxxf86vm-dev1:1.1.4-1+b2 ii x11proto-dri2-dev 2.8-2 ii x11proto-gl-dev 1.4.17-1 libegl1-mesa-dev recommends no packages. libegl1-mesa-dev suggests no packages. --- End Message --- --- Begin Message --- On Sun, Mar 18, 2018 at 16:51:48 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Package: libegl1-mesa-dev > Version: 18.0.0~rc4-1 > Severity: serious > Justification: File conflicts > > Hi! While trying to build qtwayland I ran across: > > dpkg: error processing archive > /tmp/apt-dpkg-install-VBKAMl/062-libegl1-mesa-dev_18.0.0~rc4-1_amd64.deb > (--unpack): > trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', > which is also in package libwayland-dev:amd64 1.14.91-1 > > Admitedly I'm using a build against experimental using aspcud as dep > resolver, as I need to build Qt in experimental, so maybe this is related. > This is a dupe of #893366. Cheers, Julien--- End Message ---
Processed: tagging 893366
Processing commands for cont...@bugs.debian.org: > tags 893366 + pending Bug #893366 [libwayland-dev] libwayland-dev: Uninstallable due to conflicting wayland-egl.pc Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 893366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885004: marked as done (xdriinfo: fails to detect direct rendering capability)
Your message dated Tue, 20 Mar 2018 17:37:00 + with message-id and subject line Re: Bug#885004: Acknowledgement (xdriinfo: fails to detect direct rendering capability) has caused the Debian Bug report #885004, regarding xdriinfo: fails to detect direct rendering capability 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.) -- 885004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: x11-utils Version: 7.7+3+b1 Severity: important Control: tags -1 + fixed-upstream Dear Maintainer, I believe this [0] is the bug I'm experiencing; fixed upstream [1], though apparently still unreleased. 0: https://bugs.freedesktop.org/show_bug.cgi?id=101214 1: https://cgit.freedesktop.org/xorg/app/xdriinfo/commit/?id=6273d9dacbf165331c21bcda5a8945c8931d87b8 Please consider cherry-picking the patch (or asking upstream to cut a release and shipping that). Cheers. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages x11-utils depends on: ii libc62.25-5 ii libfontconfig1 2.12.6-0.1 ii libfontenc1 1:1.1.3-1+b2 ii libfreetype6 2.8.1-0.1 ii libgl1 1.0.0-1 ii libgl1-mesa-glx 17.3.0-1 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxaw7 2:1.0.13-1+b2 ii libxcb-shape01.12-1 ii libxcb1 1.12-1 ii libxcomposite1 1:0.4.4-2 ii libxext6 2:1.3.3-1+b2 ii libxft2 2.3.2-1+b2 ii libxi6 2:1.7.9-1 ii libxinerama1 2:1.1.3-1+b3 ii libxmu6 2:1.1.2-2 ii libxmuu1 2:1.1.2-2 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxt6 1:1.1.5-1 ii libxtst6 2:1.2.3-1 ii libxv1 2:1.0.11-1 ii libxxf86dga1 2:1.1.4-1+b3 ii libxxf86vm1 1:1.1.4-1+b2 x11-utils recommends no packages. Versions of packages x11-utils suggests: ii mesa-utils 8.3.0-5 -- no debconf information _ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de --- End Message --- --- Begin Message --- Version: 7.7+4 The latest package upload fixes this. Thanks. Cheers.--- End Message ---
Bug#752695: marked as done (libxfont1: xorg fails to start up. Segfaults at libxfont)
Your message dated Wed, 21 Mar 2018 17:41:51 + with message-id and subject line Bug#893445: Removed package(s) from unstable has caused the Debian Bug report #752695, regarding libxfont1: xorg fails to start up. Segfaults at libxfont 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.) -- 752695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxfont1 Version: 1:1.4.7-2 Severity: important Dear Maintainer, * What led up to the situation? After the latest update of the nvidia legacy driver 173xx, xorg fails to start up, but from another package * What exactly did you do (or not do) that was effective (or ineffective)? Couldn't do anything to resolve this * What was the outcome of this action? Can't use Xorg * What outcome did you expect instead? Xorg to work -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libxfont1 depends on: ii libbz2-1.0 1.0.6-5 ii libc6 2.19-3 ii libfontenc11:1.1.2-1 ii libfreetype6 2.5.2-1 ii multiarch-support 2.19-3 ii zlib1g 1:1.2.8.dfsg-1 libxfont1 recommends no packages. libxfont1 suggests no packages. -- no debconf information [2478424.240] X.Org X Server 1.15.1 Release Date: 2014-04-13 [2478424.241] X Protocol Version 11, Revision 0 [2478424.241] Build Operating System: Linux 3.13-1-amd64 x86_64 Debian [2478424.241] Current Operating System: Linux warpcore 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 [2478424.241] Kernel command line: auto BOOT_IMAGE=Linux ro root=UUID=1155a15b-3d39-462d-9641-db37fdf21281 [2478424.241] Build Date: 15 April 2014 06:58:36PM [2478424.241] xorg-server 2:1.15.1-1 (http://www.debian.org/support) [2478424.241] Current version of pixman: 0.32.4 [2478424.242] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [2478424.242] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [2478424.243] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 25 14:04:40 2014 [2478424.243] (==) Using config file: "/etc/X11/xorg.conf" [2478424.243] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [2478424.243] (==) ServerLayout "Layout0" [2478424.243] (**) |-->Screen "Screen0" (0) [2478424.243] (**) | |-->Monitor "Monitor0" [2478424.244] (**) | |-->Device "Device0" [2478424.244] (**) |-->Input Device "Keyboard0" [2478424.244] (**) |-->Input Device "Mouse0" [2478424.244] (==) Automatically adding devices [2478424.244] (==) Automatically enabling devices [2478424.244] (==) Automatically adding GPU devices [2478424.244] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [2478424.244] Entry deleted from font path. [2478424.244] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [2478424.244] (==) ModulePath set to "/usr/lib/xorg/modules" [2478424.244] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [2478424.244] (WW) Disabling Keyboard0 [2478424.244] (WW) Disabling Mouse0 [2478424.244] (II) Loader magic: 0x7f1e625f7d40 [2478424.244] (II) Module ABI versions: [2478424.244] X.Org ANSI C Emulation: 0.4 [2478424.244] X.Org Video Driver: 15.0 [2478424.244] X.Org XInput driver : 20.0 [2478424.244] X.Org Server Extension : 8.0 [2478424.245] (--) PCI:*(0:1:0:0) 10de:0322:1462:9171 rev 161, Mem @ 0xfb00/16777216, 0xf000/134217728, BIOS @ 0x/131072 [2478424.245] Initializing built-in extension Generic Event Extension [2478424.245] Initializing built-in extension SHAPE [2478424.245] Initializing built-in extension MIT-SHM [2478424.245] Initializing built-in extension XInputExtension [2478424.246] Initiali
Bug#893366: marked as done (libwayland-dev: Uninstallable due to conflicting wayland-egl.pc)
Your message dated Wed, 21 Mar 2018 21:28:13 + with message-id and subject line Bug#893366: fixed in wayland 1.14.92-1 has caused the Debian Bug report #893366, regarding libwayland-dev: Uninstallable due to conflicting wayland-egl.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.) -- 893366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwayland-dev Version: 1.14.91-1 Severity: serious Hi! This package ships the file /usr/lib//pkgconfig/wayland-egl.pc which conflicts with the one installed by libegl1-mesa-dev, w/o any Replaces field or similar. The problem also is that the file providing the shared library is also not pulled in by libwayland-dev, so packages that would find the pkg-config file would then fail to build, and they should really not be depending on the shared library directly. Thanks, Guillem --- End Message --- --- Begin Message --- Source: wayland Source-Version: 1.14.92-1 We believe that the bug you reported is fixed in the latest version of wayland, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated wayland 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, 21 Mar 2018 21:42:58 +0200 Source: wayland Binary: libwayland-client0 libwayland-egl1 libwayland-server0 libwayland-cursor0 libwayland-dev libwayland-doc libwayland-bin Architecture: source Version: 1.14.92-1 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libwayland-bin - wayland compositor infrastructure - binary utilities libwayland-client0 - wayland compositor infrastructure - client library libwayland-cursor0 - wayland compositor infrastructure - cursor library libwayland-dev - wayland compositor infrastructure - development files libwayland-doc - wayland compositor infrastructure - documentation files libwayland-egl1 - wayland compositor infrastructure - EGL library libwayland-server0 - wayland compositor infrastructure - server library Closes: 893366 Changes: wayland (1.14.92-1) experimental; urgency=medium . [ Timo Aaltonen ] * New upstream pre-release. * signing-keys.asc: Updated. * libwayland-dev.install: Drop static libs, they're not provided anymore. * libwayland-egl1.symbols: Updated. * control: Adjust Breaks/Provides for libwayland-egl migration. . [ Héctor Orón Martínez ] * control: Fix uninstallability issues. (Closes: #893366) Checksums-Sha1: 80b397f7c82717859ee0a50544039c4223c8ba26 2249 wayland_1.14.92-1.dsc d86a35744617790e4a7e056168d95a7e09a79f45 320179 wayland_1.14.92-1.tar.gz 5b45b42693c71b0ed28c8ec4165177a57df804fa 6253 wayland_1.14.92-1_source.buildinfo Checksums-Sha256: c1e6d8f0e33a1497676c3b5f094d0b9516cf1345ad77218049b5f63a828377ff 2249 wayland_1.14.92-1.dsc 4489f1d29172710db56fa55fc01deb53ebd5f02e499e7084c69898d7215a1c98 320179 wayland_1.14.92-1.tar.gz 620dd296bea4e21c4d7f32c4b2adf82799e1e7b7c6a0611706678bdc76f06107 6253 wayland_1.14.92-1_source.buildinfo Files: d0139a8ac039b678ffb01d8cec308985 2249 x11 optional wayland_1.14.92-1.dsc 10d538f42092ebba6a99bf3ef33e30a4 320179 x11 optional wayland_1.14.92-1.tar.gz b2f4f400ab96a2a5fa5e4f10aa822182 6253 x11 optional wayland_1.14.92-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlqythYACgkQy3AxZaiJ hNz4NBAAjnXMDzmYTBZPfcsSdCiLyMYcT4jaTc7/7thux7kvGPVQT1wwzldF/yH1 5B8XS6ba0Un1gA1zg8wckk4RhdTiVXxfcluXDRaxj8NVV0L2f392964t+WTbpnXG lDM0pvyWTlwhX/J1kQmniR2lbK5njS/tXZb/HVOAABbv6BmHKEXsLkFqjorbXwO/ S+VWirfYPc1DqwFLlix5jcZ21VQ3zKhl1G0bKBx+rrTnDGq+Hc5Voa6DBrXu0Oxn yE3KQuKeNkI7fhs+gyHYWCcJQlKJHJyQxJsb2mOyQue9D3ta0e9Gu0+7LJ5qKB6B llCKLT6aUxpcDxaC6k3KET0bHLtBPoCLhNqKH3FxcCpKeztqFySqXWEwdREUhqgS nOXtFSnmRY4kaIa3/Jr1y4LKNjGOAU7af9sMX/Pzi/WNCsXA7heP/XJt03pLHRzP zV+fVi0qwXtpTpNv0kPJvFrvpQIVedrQa9a6GGScybA+D77RHOfuxiGBm0caGZDT Q/Fsr001fHBAcG4ZYE17MOCyFSHFX5BTYxSBwQ3vOyeDXSr4yJwGgFILLe6hTOmB enJi8AOdYd8Fnu1BqF/hi68WExOaD0Hly+H
Bug#876084: marked as done ([libglvnd-dev] Can't upgrade libglvnd-dev anymore)
Your message dated Fri, 23 Mar 2018 10:24:23 +0200 with message-id <8337fbe5-6920-78f7-66db-44e3d429d...@debian.org> and subject line Re: Bug#876084: [libglvnd-dev] Can't upgrade libglvnd-dev anymore has caused the Debian Bug report #876084, regarding [libglvnd-dev] Can't upgrade libglvnd-dev anymore 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.) -- 876084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libglvnd-dev Severity: normal --- Please enter the report below this line. --- When I'm trying to upgrade that package (which is needed by libgl1-mesa-dev) apt says that it depends on "libopengl0 (= 0.2.999+git20170802-4)" which it's not available. --- System information. --- Architecture: Kernel: Linux 4.12.0-1-amd64 Debian Release: buster/sid 500 unstable-debug deb.debian.org 500 unstableftp.debian.org 500 stable repo.skype.com 500 stable dl.google.com --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. --- End Message --- --- Begin Message --- On 25.11.2017 18:17, Andreas Beckmann wrote: > Followup-For: Bug #876084 > > This bug could be related to several similar ones against > nvidia-graphics-drivers recently, finally fixed with 375.82-8 ... > > I suggest to add a bug-control file to automatically record this fact in > case of bug reports. libgl1-nvidia-glx-any is a virtual package that is > provided by src:nvidia-graphics-drivers for several years already. > > And there is another little patch switching to dh_missing ... > > The --builddirectory=build/ is a bit unfortunate, since it clashes with > 'dh build' in case someone manually runs it twice - which I obviously did :-) those changes got added earlier, closing the bug -- t--- End Message ---
Bug#884717: marked as done (libgl1: consider using a version that is higher than 1.2.0 for the libGL.so.1.0.0 filename)
Your message dated Fri, 23 Mar 2018 08:52:05 + with message-id and subject line Bug#884717: fixed in libglvnd 1.0.0+git20180308-1 has caused the Debian Bug report #884717, regarding libgl1: consider using a version that is higher than 1.2.0 for the libGL.so.1.0.0 filename 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.) -- 884717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgl1 Version: 1.0.0-1 Severity: normal Hi, if the system got messed up by some proprietary installer, it may be well possible that some cruft libGL.so.1.X.Y outside the control of dpkg is left on the system and takes precedence over libGL.so.1.0.0 Like in #879041: libglvnd0: Nvidia-Installer 384.90: "An incomplete installation of libglvnd was found." where an old copy of the MESA libGL.so.1.2.0 was left and was still ebing used. ldconfig will give precedence to the file with the highest filename version as the target of the SONAME link libGL.so.1. So unfortunately libGL.so.1.0.0 will always be the loser. Renaming libGL.so.1.0.0 (or just adding a symlink with a higher version to it) would circumvent these bugs by giving precedence to the libglvnd libGL.so.1. The following filenames have been in use in the past and present: libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1.0.0 libgl1-fglrx-glx: /usr/lib/x86_64-linux-gnu/fglrx/fglrx-libGL.so.1.2 libgl1-fglrx-legacy-glx: /usr/lib/x86_64-linux-gnu/fglrx/fglrx-libGL.so.1.2 libgl1-glvnd-nvidia-glx: /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1.0.0 libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/libGL.so.1.2 libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 libgl1-mesa-swx11: /usr/lib/x86_64-linux-gnu/libGL.so.1.5.08005 libgl1-mesa-swx11: /usr/lib/x86_64-linux-gnu/libGL.so.1.6.0 I would suggest to add a symlink libGL.so.1.7.0 -> libGL.so.1.0.0 That also means to adjust the SONAME link to libGL.so.1 -> libGL.so.1.7.0 to ship the link like it would be created by ldconfig, otherwise it may trigger errors in some library symlink validation test in piuparts. Also give me a notice before uploading such a change s.t. I can adjust glx-diversions accordingly and you can bump the Breaks against the glx-diversions versions not knowing about the new filename. It may be worthwile suggesting such a rename to upstream, too. Andreas --- End Message --- --- Begin Message --- Source: libglvnd Source-Version: 1.0.0+git20180308-1 We believe that the bug you reported is fixed in the latest version of libglvnd, 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 884...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated libglvnd 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: Fri, 23 Mar 2018 10:15:50 +0200 Source: libglvnd Binary: libglvnd-dev libglvnd-core-dev libglvnd0 libegl1 libgles2 libgl1 libglx0 libopengl0 Architecture: source Version: 1.0.0+git20180308-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libegl1- Vendor neutral GL dispatch library -- EGL support libgl1 - Vendor neutral GL dispatch library -- legacy GL support libgles2 - Vendor neutral GL dispatch library -- GLES support libglvnd-core-dev - Vendor neutral GL dispatch library -- core development files libglvnd-dev - Vendor neutral GL dispatch library -- development files libglvnd0 - Vendor neutral GL dispatch library libglx0- Vendor neutral GL dispatch library -- GLX support libopengl0 - Vendor neutral GL dispatch library -- OpenGL support Closes: 884717 Changes: libglvnd (1.0.0+git20180308-1) unstable; urgency=medium . * New upstream snapshot. - bump library minor versions to avoid issues with leftover libs taking precedence (Closes: #884717) * control, rules: Enable tests, build-depend on xauth, xvfb. * kfreebsd-hurd.patch: Dropped, upstream. * control: Update VCS urls. Checksums-Sha1: 8c625f50a6c5f5a09dfffce787090b71be7fd61a 2425 libglvnd_1.0.0+g
Bug#890973: marked as done (ITP: xorgproto -- X11 extension protocols and auxiliary headers)
Your message dated Fri, 23 Mar 2018 12:00:12 + with message-id and subject line Bug#890973: fixed in xorgproto 2018.4-2 has caused the Debian Bug report #890973, regarding ITP: xorgproto -- X11 extension protocols and auxiliary headers 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.) -- 890973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Timo Aaltonen * Package name: xorgproto Version : 2018.3 Upstream Author : X.Org * URL : http://www.x.org/ * License : MIT/X Programming Lang: C Description : X11 extension protocols and auxiliary headers This package provides development headers describing the wire protocol for the X11 core and extension protocols, and also provides a number of utility headers, used to abstract OS-specific functions. --- End Message --- --- Begin Message --- Source: xorgproto Source-Version: 2018.4-2 We believe that the bug you reported is fixed in the latest version of xorgproto, 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 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated xorgproto 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, 02 Mar 2018 11:46:05 +0200 Source: xorgproto Binary: x11proto-dev x11proto-bigreqs-dev x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-dmx-dev x11proto-dri2-dev x11proto-dri3-dev x11proto-fixes-dev x11proto-fonts-dev x11proto-gl-dev x11proto-input-dev x11proto-kb-dev x11proto-present-dev x11proto-print-dev x11proto-randr-dev x11proto-record-dev x11proto-render-dev x11proto-resource-dev x11proto-scrnsaver-dev x11proto-video-dev x11proto-xcmisc-dev x11proto-xext-dev x11proto-xf86bigfont-dev x11proto-xf86dga-dev x11proto-xf86dri-dev x11proto-xf86vidmode-dev x11proto-xinerama-dev Architecture: source all Version: 2018.4-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: x11proto-bigreqs-dev - transitional dummy package x11proto-composite-dev - transitional dummy package x11proto-core-dev - transitional dummy package x11proto-damage-dev - transitional dummy package x11proto-dev - X11 extension protocols and auxiliary headers x11proto-dmx-dev - transitional dummy package x11proto-dri2-dev - transitional dummy package x11proto-dri3-dev - transitional dummy package x11proto-fixes-dev - transitional dummy package x11proto-fonts-dev - transitional dummy package x11proto-gl-dev - transitional dummy package x11proto-input-dev - transitional dummy package x11proto-kb-dev - transitional dummy package x11proto-present-dev - transitional dummy package x11proto-print-dev - transitional dummy package x11proto-randr-dev - transitional dummy package x11proto-record-dev - transitional dummy package x11proto-render-dev - transitional dummy package x11proto-resource-dev - transitional dummy package x11proto-scrnsaver-dev - transitional dummy package x11proto-video-dev - transitional dummy package x11proto-xcmisc-dev - transitional dummy package x11proto-xext-dev - transitional dummy package x11proto-xf86bigfont-dev - transitional dummy package x11proto-xf86dga-dev - transitional dummy package x11proto-xf86dri-dev - transitional dummy package x11proto-xf86vidmode-dev - transitional dummy package x11proto-xinerama-dev - transitional dummy package Closes: 890973 Changes: xorgproto (2018.4-2) unstable; urgency=medium . * Initial release. (Closes: #890973) - upstream merged all protocol headers into a single repository, this replaces all now-obsolete x11proto-* packages Checksums-Sha1: 9beec5be70d299740c77fe27bbca2a165f6e4865 4136 xorgproto_2018.4-2.dsc a0e2d39316a99266fdbbf8020fe425b6da91409c 493597 xorgproto_2018.4.orig.tar.gz 30d0cd6d0f7b6d6a207867518cce6353b2b2fd95 241 xorgproto_2018.4.orig.tar.gz.asc 88dfbb8c94290e1b1755b1c0180b25bcea57e5ec 20458 xorgproto_2018.4-2.diff.gz a10dd5c69c2a6300e7bc061d59056c167fbb99df 2844 x11proto
Processed: Re: Bug#859461: xterm: seperate package for resize would be nice
Processing control commands: > tag 859461 + patch Bug #859461 [xterm] xterm: seperate package for resize would be nice Added tag(s) patch. -- 859461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893943: marked as done (xorgproto: mark all dummy packages Multi-Arch: foreign)
Your message dated Sat, 24 Mar 2018 09:30:46 +
with message-id
and subject line Bug#893943: fixed in xorgproto 2018.4-3
has caused the Debian Bug report #893943,
regarding xorgproto: mark all dummy packages Multi-Arch: foreign
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.)
--
893943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xorgproto
Version: 2018.4-2
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Very many packages cannot be cross built anymore, because they have one
of those transitional dummy packages in their dependency closure. In
general, Architecture: all packages can never satisfy cross
Build-Depends unless marked Multi-Arch: foreign. Such a marking is
correct, because these packages don't have any maintainer scripts and
their only dependency is marked Multi-Arch: foreign already. I am
setting the severity to important, because this is a regression with big
impact to cross building and bootstrapping architectures. Please fix
this quickly as the current state breaks the QA testing and thus hides
later failures. I am attaching a patch for your convenience.
Helmut
diff -u xorgproto-2018.4/debian/changelog xorgproto-2018.4/debian/changelog
--- xorgproto-2018.4/debian/changelog
+++ xorgproto-2018.4/debian/changelog
@@ -1,3 +1,11 @@
+xorgproto (2018.4-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Mark all those transitional dummy packages that forward to
+x11proto-dev Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne Sat, 24 Mar 2018 07:25:05 +0100
+
xorgproto (2018.4-2) unstable; urgency=medium
* Initial release. (Closes: #890973)
diff -u xorgproto-2018.4/debian/control xorgproto-2018.4/debian/control
--- xorgproto-2018.4/debian/control
+++ xorgproto-2018.4/debian/control
@@ -120,6 +120,7 @@
Package: x11proto-bigreqs-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -127,6 +128,7 @@
Package: x11proto-composite-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -134,6 +136,7 @@
Package: x11proto-core-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -141,6 +144,7 @@
Package: x11proto-damage-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -148,6 +152,7 @@
Package: x11proto-dmx-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -155,6 +160,7 @@
Package: x11proto-dri2-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -162,6 +168,7 @@
Package: x11proto-dri3-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -169,6 +176,7 @@
Package: x11proto-fixes-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -176,6 +184,7 @@
Package: x11proto-fonts-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -183,6 +192,7 @@
Package: x11proto-gl-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transitional dummy package
This is a transitional dummy package, it can be safely removed.
@@ -190,6 +200,7 @@
Package: x11proto-input-dev
Section: oldlibs
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, x11proto-dev
Description: transit
Processed: Re: Bug#893178: gdm3 crashes: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed.
Processing control commands: > reassign -1 libinput 1.10.2-1 Bug #893178 [gdm3] gdm3 crashes: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed. Bug reassigned from package 'gdm3' to 'libinput'. No longer marked as found in versions gdm3/3.26.2.1-3. Ignoring request to alter fixed versions of bug #893178 to the same values previously set Bug #893178 [libinput] gdm3 crashes: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed. There is no source info for the package 'libinput' at version '1.10.2-1' with architecture '' Unable to make a source version for version '1.10.2-1' Marked as found in versions 1.10.2-1. -- 893178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893178: marked as done (gdm3 crashes: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed.)
Your message dated Mon, 26 Mar 2018 09:17:54 +0100 with message-id <20180326081754.gb2...@espresso.pseudorandom.co.uk> and subject line Re: Bug#893178: gdm3 crashes: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed. has caused the Debian Bug report #893178, regarding gdm3 crashes: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' 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.) -- 893178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdm3 Version: 3.26.2.1-3 Severity: important Dear Maintainer, This occurs seemingly randomly at intervals of anywhere between 2 and 30 minutes. The desktop isn't running anything fancy. An open terminal window and the ReportBug application are enough to make it crash. I get the impression that me using the trackpad is related, as I'm certain that was the case for the last few crashes. Every single time I got the same stracktrace in /usr/lib/gdm3/gdm-x-session (~/.local/share/xorg/Xorg.0.log.old) so I'm certain this is related. After the crash other processes are terminated and the desktop is reloaded. The stacktrace as seen in journalctl: mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: Xorg: ../src/evdev-mt- touchpad-tap.c:1028: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed. mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) Backtrace: mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x55c67d570e3d] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 1: /usr/lib/xorg/Xorg (0x55c67d3b9000+0x1bbbd9) [0x55c67d574bd9] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff9164a5000+0x11f50) [0x7ff9164b6f50] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x10b) [0x7ff91611fe7b] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x151) [0x7ff916121231] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7ff9160eb000+0x2d9da) [0x7ff9161189da] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7ff9160eb000+0x2da52) [0x7ff916118a52] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 7: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7ff912ed8000+0x1e693) [0x7ff912ef6693] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 8: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7ff912ed8000+0x19857) [0x7ff912ef1857] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 9: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7ff912ed8000+0x1ba20) [0x7ff912ef3a20] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 10: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7ff912ed8000+0xfe51) [0x7ff912ee7e51] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 11: /usr/lib/x86_64-linux-gnu/libinput.so.10 (libinput_dispatch+0x5f) [0x7ff912ee3e7f] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 12: /usr/lib/xorg/modules/input/libinput_drv.so (0x7ff913112000+0x8988) [0x7ff91311a988] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 13: /usr/lib/xorg/Xorg (0x55c67d3b9000+0x1b9fb3) [0x55c67d572fb3] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 14: /usr/lib/xorg/Xorg (0x55c67d3b9000+0x1bc6b1) [0x55c67d5756b1] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 15: /usr/lib/xorg/Xorg (0x55c67d3b9000+0x1b9dfe) [0x55c67d572dfe] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 16: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff9164a5000+0x75aa) [0x7ff9164ac5aa] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (clone+0x3f) [0x7ff9161e1cbf] mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: Fatal server error: mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) Caught signal 6 (Aborted). Server aborting mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: Please consult the The X.Org Foundation support mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: at http://wiki.x.org mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-
Processed: found 894086 in 2:1.19.99.901-1
Processing commands for cont...@bugs.debian.org: > found 894086 2:1.19.99.901-1 Bug #894086 [xserver-xorg-core] Cannot upgrade Marked as found in versions xorg-server/2:1.19.99.901-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 894086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#894086: marked as done (Cannot upgrade)
Your message dated Mon, 26 Mar 2018 15:04:08 +0300 with message-id <32c980f6-5f6a-983e-b1ac-37cf2e5c0...@debian.org> and subject line Re: Bug#894086: Cannot upgrade has caused the Debian Bug report #894086, regarding Cannot upgrade 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.) -- 894086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-core The following packages have unmet dependencies: xserver-xorg-video-vesa : Depends: xorg-video-abi-23 which is a virtual package, provided by: - xserver-xorg-core (2:1.19.6-1), but 2:1.19.99.901-1 is to be installed xserver-xorg-video-fbdev : Depends: xorg-video-abi-23 which is a virtual package, provided by: - xserver-xorg-core (2:1.19.6-1), but 2:1.19.99.901-1 is to be installed xserver-xorg-video-intel : Depends: xorg-video-abi-23 which is a virtual package, provided by: - xserver-xorg-core (2:1.19.6-1), but 2:1.19.99.901-1 is to be installed --- End Message --- --- Begin Message --- On 26.03.2018 14:13, 積丹尼 Dan Jacobson wrote: > Package: xserver-xorg-core > > The following packages have unmet dependencies: > xserver-xorg-video-vesa : Depends: xorg-video-abi-23 which is a virtual > package, provided by: > - xserver-xorg-core (2:1.19.6-1), but > 2:1.19.99.901-1 is to be installed > > xserver-xorg-video-fbdev : Depends: xorg-video-abi-23 which is a virtual > package, provided by: > - xserver-xorg-core (2:1.19.6-1), but > 2:1.19.99.901-1 is to be installed > > xserver-xorg-video-intel : Depends: xorg-video-abi-23 which is a virtual > package, provided by: > - xserver-xorg-core (2:1.19.6-1), but > 2:1.19.99.901-1 is to be installed > don't enable experimental unless you know what you're doing -- t--- End Message ---
Processed: Update bug reports to my debian address
bug=745124 745125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745125 748402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748402 748504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748504 748505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748505 748712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748712 748835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748835 749624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749624 760025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760025 765485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765485 765940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765940 772674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772674 775312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775312 778872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778872 780306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780306 781176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781176 782255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782255 784989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784989 784992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784992 785005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785005 793778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793778 794121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794121 794692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794692 799157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799157 802539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802539 802568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802568 802686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802686 803161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803161 807557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807557 809600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809600 812506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812506 813736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813736 815904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815904 818307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818307 819865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819865 830867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830867 832289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832289 832788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832788 833731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833731 833920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833920 839159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839159 840043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840043 840398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840398 841726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841726 842149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842149 850297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850297 850442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850442 850751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850751 852162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852162 852555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852555 852628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852628 853189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853189 853248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853248 853258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853258 856003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856003 856385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856385 856893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856893 857091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857091 857129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857129 857786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857786 858367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858367 861093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861093 861322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861322 861670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861670 862191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862191 863631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863631 863701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863701 867150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867150 867584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867584 870066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870066 870112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870112 870767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870767 873271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873271 878873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878873 878875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878875 878876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878876 878877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878877 878879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878879 878881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878881 878882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878882 878884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878884 878885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878885 878886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878886 878887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878887 880084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880084 884453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884453 884483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884483 884561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884561 890494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890494 890544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890544 890622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890622 891829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891829 893108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893108 893109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893109 893111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893111 893113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893113 893120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893120 893394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893394 893724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#890679: marked as done (libxshmfence: FTBFS with glibc 2.27: error: implicit declaration of function 'memfd_create')
Your message dated Mon, 26 Mar 2018 17:59:52 +0300
with message-id <20180326145952.GH9516@localhost>
and subject line Fixed in 1.3-1
has caused the Debian Bug report #890679,
regarding libxshmfence: FTBFS with glibc 2.27: error: implicit declaration of
function 'memfd_create'
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.)
--
890679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxshmfence
Version: 1.2-1
Severity: important
Tags: upstream patch
User: debian-gl...@lists.debian.org
Usertags: 2.27
libxshmfence 1.2-1 fails to build with glibc 2.27 (2.27-0experimental0 from
experimental):
| libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time
-D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast
-Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized
-Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls
-Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main
-Werror=missing-braces -Werror=sequence-point -Werror=return-type
-Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address
-Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fvisibility=hidden -c ../../src/xshmfence_alloc.c
-fPIC -DPIC -o .libs/xshmfence_alloc.o
| ../../src/xshmfence_alloc.c: In function 'xshmfence_alloc_shm':
| ../../src/xshmfence_alloc.c:73:7: error: implicit declaration of function
'memfd_create'; did you mean 'SYS_memfd_create'?
[-Werror=implicit-function-declaration]
| fd = memfd_create("xshmfence", MFD_CLOEXEC|MFD_ALLOW_SEALING);
|^~~~
|SYS_memfd_create
| ../../src/xshmfence_alloc.c:73:7: warning: nested extern declaration of
'memfd_create' [-Wnested-externs]
| cc1: some warnings being treated as errors
| Makefile:474: recipe for target 'xshmfence_alloc.lo' faile
A full build logs is available there:
http://aws-logs.debian.net/2018/02/07/glibc-exp/libxshmfence_1.2-1_unstable_glibc-exp.log
glibc 2.27 added support for memfd_create. libxshmfence correctly
detects in its configure script the availability of this function and
consequently disables its own syscall wrapper. Unfortunately this is
not enough as memfd_create as a GNU extension and thus needs to be built
with _GNU_SOURCE.
The problem has been fixed in upstream commit 0b550a4e. I have also
attached it as a patch to this mail.
--- libxshmfence-1.2.orig/debian/patches/memfd_create.patch
+++ libxshmfence-1.2/debian/patches/memfd_create.patch
@@ -0,0 +1,29 @@
+From 0b550a4e7acf02d3478602848f6afbfcbfb0d4b2 Mon Sep 17 00:00:00 2001
+From: Ross Burton
+Date: Mon, 29 Jan 2018 16:24:36 +
+Subject: configure.ac: call AC_USE_SYSTEM_EXTENSIONS
+
+With glibc 2.27 memfd_create() is inside a _GNU_SOURCE guard, so call
+AC_USE_SYSTEM_EXTENSIONS to get this defined.
+
+Signed-off-by: Ross Burton
+---
+ configure.ac | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/configure.ac b/configure.ac
+index 55772d0..ed77e6d 100644
+--- a/configure.ac
b/configure.ac
+@@ -28,6 +28,8 @@ AC_INIT([libxshmfence], [1.2],
+ AC_CONFIG_SRCDIR([Makefile.am])
+ AC_CONFIG_HEADERS([config.h])
+
++AC_USE_SYSTEM_EXTENSIONS
++
+ # Initialize Automake
+ AM_INIT_AUTOMAKE([foreign dist-bzip2])
+
+--
+cgit v1.1
+
--- libxshmfence-1.2.orig/debian/patches/series
+++ libxshmfence-1.2/debian/patches/series
@@ -0,0 +1 @@
+memfd_create.patch
--- End Message ---
--- Begin Message ---
Version: 1.3-1
This was fixed upstream in 1.3
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed--- End Message ---
Processed: Re: Bug#894076: Can't include GL and GLES headers simultaneously on non-64 bit architectures
Processing control commands: > severity -1 normal Bug #894076 [mesa] Can't include GL and GLES headers simultaneously on non-64 bit architectures Severity set to 'normal' from 'serious' > tag -1 upstream Bug #894076 [mesa] Can't include GL and GLES headers simultaneously on non-64 bit architectures Added tag(s) upstream. -- 894076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#893975: x11proto-dev: trying to overwrite '/usr/include/X11/extensions/xf86misc.h'
Processing control commands: > severity -1 serious Bug #893975 [x11proto-dev] x11proto-dev: trying to overwrite '/usr/include/X11/extensions/xf86misc.h' Severity set to 'serious' from 'normal' -- 893975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#859461: xterm: seperate package for resize would be nice
Processing control commands: > tag -1 - patch Bug #859461 [xterm] xterm: seperate package for resize would be nice Removed tag(s) patch. -- 859461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893975: marked as done (x11proto-dev: trying to overwrite '/usr/include/X11/extensions/xf86misc.h')
Your message dated Tue, 03 Apr 2018 09:15:07 + with message-id and subject line Bug#893975: fixed in xorgproto 2018.4-4 has caused the Debian Bug report #893975, regarding x11proto-dev: trying to overwrite '/usr/include/X11/extensions/xf86misc.h' 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.) -- 893975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: x11proto-dev Version: 2018.4-3 Severity: normal Dear Maintainer, Error while trying to install as part of a dist-upgrade: Selecting previously unselected package x11proto-dev. Preparing to unpack .../158-x11proto-dev_2018.4-3_all.deb ... Unpacking x11proto-dev (2018.4-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-8XuetG/158-x11proto-dev_2018.4-3_all.deb (--unpack): trying to overwrite '/usr/include/X11/extensions/xf86misc.h', which is also in package x11proto-xf86misc-dev 0.9.3-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-8XuetG/158-x11proto-dev_2018.4-3_all.deb Looks like this package needs some conflicts/replaces. Greetings Haegar -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages x11proto-dev depends on: ii xorg-sgml-doctools 1:1.11-1 x11proto-dev recommends no packages. x11proto-dev suggests no packages. --- End Message --- --- Begin Message --- Source: xorgproto Source-Version: 2018.4-4 We believe that the bug you reported is fixed in the latest version of xorgproto, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated xorgproto 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, 03 Apr 2018 10:19:04 +0200 Source: xorgproto Binary: x11proto-dev x11proto-bigreqs-dev x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-dmx-dev x11proto-dri2-dev x11proto-dri3-dev x11proto-fixes-dev x11proto-fonts-dev x11proto-gl-dev x11proto-input-dev x11proto-kb-dev x11proto-present-dev x11proto-randr-dev x11proto-record-dev x11proto-render-dev x11proto-resource-dev x11proto-scrnsaver-dev x11proto-video-dev x11proto-xcmisc-dev x11proto-xext-dev x11proto-xf86bigfont-dev x11proto-xf86dga-dev x11proto-xf86dri-dev x11proto-xf86vidmode-dev x11proto-xinerama-dev Architecture: source Version: 2018.4-4 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Julien Cristau Description: x11proto-bigreqs-dev - transitional dummy package x11proto-composite-dev - transitional dummy package x11proto-core-dev - transitional dummy package x11proto-damage-dev - transitional dummy package x11proto-dev - X11 extension protocols and auxiliary headers x11proto-dmx-dev - transitional dummy package x11proto-dri2-dev - transitional dummy package x11proto-dri3-dev - transitional dummy package x11proto-fixes-dev - transitional dummy package x11proto-fonts-dev - transitional dummy package x11proto-gl-dev - transitional dummy package x11proto-input-dev - transitional dummy package x11proto-kb-dev - transitional dummy package x11proto-present-dev - transitional dummy package x11proto-randr-dev - transitional dummy package x11proto-record-dev - transitional dummy package x11proto-render-dev - transitional dummy package x11proto-resource-dev - transitional dummy package x11proto-scrnsaver-dev - transitional dummy package x11proto-video-dev - transitional dummy package x11proto-xcmisc-dev - transitional dummy package x11proto-xext-dev - transitional dummy package x11proto-xf86bigfont-dev - transitional
Processed: [xserver-xorg-legacy]
Processing control commands: > close -1 Bug #803621 [xserver-xorg-legacy] [xserver-xorg-legacy] (EE) systemd-logind: failed to get session: PID xxx does not belong to any known session Marked Bug as done -- 803621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package xserver-xorg-video-intel
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package xserver-xorg-video-intel > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #675734 (http://bugs.debian.org/675734) > # Bug title: xserver-xorg-video-intel: Font corruption after Suspend > # * https://bugs.freedesktop.org/show_bug.cgi?id=36326 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > usertags 675734 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #617419 (http://bugs.debian.org/617419) > # Bug title: xserver-xorg-video-intel: xrandr doesn't offer all possible > resolutions (regression) > # * https://bugs.freedesktop.org/show_bug.cgi?id=35843 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> WONTFIX > usertags 617419 + status-RESOLVED resolution-WONTFIX There were no usertags set. Usertags are now: resolution-WONTFIX status-RESOLVED. > # remote status report for #651741 (http://bugs.debian.org/651741) > # Bug title: gnome-power-manager: display backlight brightness has no effect > on Sony Vaio VPCYA1V9E > # * https://bugs.freedesktop.org/show_bug.cgi?id=44809 > # * remote status changed: (?) -> CLOSED > # * remote resolution changed: (?) -> NOTOURBUG > # * closed upstream > tags 651741 + fixed-upstream Bug #651741 [xserver-xorg-video-intel] gnome-power-manager: display backlight brightness has no effect on Sony Vaio VPCYA1V9E Added tag(s) fixed-upstream. > usertags 651741 + status-CLOSED resolution-NOTOURBUG There were no usertags set. Usertags are now: resolution-NOTOURBUG status-CLOSED. > # remote status report for #655017 (http://bugs.debian.org/655017) > # Bug title: xserver-xorg-video-intel: [Sandybridge] missing graphics > refresh, black areas since SNA is enabled > # * https://bugs.freedesktop.org/show_bug.cgi?id=44787 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > usertags 655017 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #675734 (http://bugs.debian.org/675734) > # Bug title: xserver-xorg-video-intel: Font corruption after Suspend > # * https://bugs.freedesktop.org/show_bug.cgi?id=36326 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > usertags 675734 + status-RESOLVED resolution-FIXED Usertags were: status-RESOLVED resolution-FIXED. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #755673 (http://bugs.debian.org/755673) > # Bug title: xserver-xorg-video-intel: Screen flickering with Xorg 1.16 > # * https://bugs.freedesktop.org/show_bug.cgi?id=81551 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> WONTFIX > usertags 755673 + status-RESOLVED resolution-WONTFIX There were no usertags set. Usertags are now: status-RESOLVED resolution-WONTFIX. > # remote status report for #787241 (http://bugs.debian.org/787241) > # Bug title: xserver-xorg-video-intel: VT never returns from powersave on > Haswell > # * https://bugs.freedesktop.org/show_bug.cgi?id=90804 > # * remote status changed: (?) -> CLOSED > # * remote resolution changed: (?) -> WONTFIX > usertags 787241 + status-CLOSED resolution-WONTFIX There were no usertags set. Usertags are now: resolution-WONTFIX status-CLOSED. > # remote status report for #813625 (http://bugs.debian.org/813625) > # Bug title: xserver-xorg-video-intel: rendering corruption when not on > battery power > # * https://bugs.freedesktop.org/show_bug.cgi?id=94011 > # * remote status changed: (?) -> CLOSED > # * remote resolution changed: (?) -> FIXED > usertags 813625 + status-CLOSED resolution-FIXED There were no usertags set. Usertags are now: resolution-FIXED status-CLOSED. > # remote status report for #846882 (http://bugs.debian.org/846882) > # Bug title: xserver-xorg-video-intel: wrong scale for backlight with Xfce > # * https://bugs.freedesktop.org/show_bug.cgi?id=99126 > # * remote status changed: (?) -> NEEDINFO > usertags 846882 + status-NEEDINFO There were no usertags set. Usertags are now: status-NEEDINFO. > thanks Stopping processing here. Please contact me if you need assistance. -- 651741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651741 846882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package x11-apps
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package x11-apps > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #93665 (http://bugs.debian.org/93665) > # Bug title: xbase-clients: [xcalc] uses wrong order of operations in infix > mode > # * https://bugs.freedesktop.org/show_bug.cgi?id=10578 > # * remote status changed: (?) -> ASSIGNED > usertags 93665 + status-ASSIGNED There were no usertags set. Usertags are now: status-ASSIGNED. > # remote status report for #101937 (http://bugs.debian.org/101937) > # Bug title: xbase-clients: [xwd] 'xwd -name windowtitle -frame' doesn't > capture frame > # * https://bugs.freedesktop.org/show_bug.cgi?id=10583 > # * remote status changed: (?) -> NEW > usertags 101937 + status-NEW There were no usertags set. Usertags are now: status-NEW. > # remote status report for #753596 (http://bugs.debian.org/753596) > # Bug title: x11-apps: xclock -render doesn't retain clock aspect ratio > # * https://bugs.freedesktop.org/show_bug.cgi?id=3110 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> NOTABUG > # * closed upstream > tags 753596 + fixed-upstream Bug #753596 [x11-apps] x11-apps: xclock -render doesn't retain clock aspect ratio Added tag(s) fixed-upstream. > usertags 753596 + status-RESOLVED resolution-NOTABUG There were no usertags set. Usertags are now: status-RESOLVED resolution-NOTABUG. > thanks Stopping processing here. Please contact me if you need assistance. -- 753596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package xserver-xorg-video-ati
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package xserver-xorg-video-ati > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #406373 (http://bugs.debian.org/406373) > # Bug title: [radeon] [ia64] No direct rendering [FireGL X1 R300, 4e47] > # * https://bugs.freedesktop.org/show_bug.cgi?id=7770 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> WORKSFORME > # * closed upstream > tags 406373 + fixed-upstream Bug #406373 [xserver-xorg-video-ati] [radeon] [ia64] No direct rendering [FireGL X1 R300, 4e47] Added tag(s) fixed-upstream. > usertags 406373 + status-RESOLVED resolution-WORKSFORME There were no usertags set. Usertags are now: resolution-WORKSFORME status-RESOLVED. > # remote status report for #459431 (http://bugs.debian.org/459431) > # Bug title: [radeon] with Depth 16, blank display with playing video file > [Mobility M6 LY, 4c59] > # * https://bugs.freedesktop.org/show_bug.cgi?id=13924 > # * remote status changed: (?) -> REOPENED > usertags 459431 + status-REOPENED There were no usertags set. Usertags are now: status-REOPENED. > # remote status report for #459837 (http://bugs.debian.org/459837) > # Bug title: [radeon] manual edit of xorg.conf is required. xrandr and > xdpyinfo do not correspond to correct ddcprobe edid info [9100 IGP, 5834] > # * https://bugs.freedesktop.org/show_bug.cgi?id=13964 > # * remote status changed: (?) -> NEW > usertags 459837 + status-NEW There were no usertags set. Usertags are now: status-NEW. > # remote status report for #463076 (http://bugs.debian.org/463076) > # Bug title: [radeon] machine freezes when X is stopped or second X started > [9200 RV280, 5962] > # * https://bugs.freedesktop.org/show_bug.cgi?id=15056 > # * remote status changed: (?) -> NEW > usertags 463076 + status-NEW There were no usertags set. Usertags are now: status-NEW. > # remote status report for #497209 (http://bugs.debian.org/497209) > # Bug title: xserver-xorg-video-radeon: Strange behaviour using dvi-port only > with Radeon 9200 pro > # * https://bugs.freedesktop.org/show_bug.cgi?id=17455 > # * remote status changed: (?) -> NEW > usertags 497209 + status-NEW There were no usertags set. Usertags are now: status-NEW. > # remote status report for #529178 (http://bugs.debian.org/529178) > # Bug title: xserver-xorg-video-radeon: Monitor turns black for 2 seconds > regularly when using dvi port > # * https://bugs.freedesktop.org/show_bug.cgi?id=89110 > # * remote status changed: (?) -> CLOSED > # * remote resolution changed: (?) -> NOTOURBUG > usertags 529178 + status-CLOSED resolution-NOTOURBUG There were no usertags set. Usertags are now: resolution-NOTOURBUG status-CLOSED. > # remote status report for #597692 (http://bugs.debian.org/597692) > # Bug title: kde-full: Strange mouse cursor behaviour. > # * https://bugs.freedesktop.org/show_bug.cgi?id=28426 > # * remote status changed: (?) -> REOPENED > usertags 597692 + status-REOPENED There were no usertags set. Usertags are now: status-REOPENED. > # remote status report for #683796 (http://bugs.debian.org/683796) > # Bug title: black screen happens about 10 seconds after boot starts > # * https://bugs.freedesktop.org/show_bug.cgi?id=90220 > # * remote status changed: (?) -> NEW > usertags 683796 + status-NEW There were no usertags set. Usertags are now: status-NEW. > # remote status report for #848575 (http://bugs.debian.org/848575) > # Bug title: xserver-xorg-video-radeon: unable to restart Xorg without > rebooting (radeon) > # * https://bugs.freedesktop.org/show_bug.cgi?id=99138 > # * remote status changed: (?) -> NEW > usertags 848575 + status-NEW There were no usertags set. Usertags are now: status-NEW. > # remote status report for #762047 (http://bugs.debian.org/762047) > # Bug title: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC > # * https://bugs.launchpad.net/bugs/1438231 > # * remote status changed: (?) -> New > usertags 762047 + status-New There were no usertags set. Usertags are now: status-New. > thanks Stopping processing here. Please contact me if you need assistance. -- 406373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406373 762047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895905: marked as done (mesa-va-drivers attempts to overwrite nouveau_drv_video.so from vdpau-va-driver)
Your message dated Tue, 17 Apr 2018 15:29:56 +0200 with message-id <2b4bf3e7-f036-af08-0233-e7d5c0599...@debian.org> and subject line Re: Bug#895905: mesa-va-drivers attempts to overwrite nouveau_drv_video.so from vdpau-va-driver has caused the Debian Bug report #895905, regarding mesa-va-drivers attempts to overwrite nouveau_drv_video.so from vdpau-va-driver 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.) -- 895905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa Version: 17.3.8-1 Severity: important I run `apt full-upgrade` and it ended up with an error. Now the `apt-get install -f` reports the following: Preparing to unpack .../mesa-va-drivers_17.3.8-1_amd64.deb ... Unpacking mesa-va-drivers:amd64 (17.3.8-1) ... dpkg: error processing archive /var/cache/apt/archives/mesa-va-drivers_17.3.8-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so', which is also in package vdpau-va-driver:amd64 0.7.4-dmo5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/mesa-va-drivers_17.3.8-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Maybe those packages should be marked as conflicting or the file should be handled as by update-alternatives? -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.11 (SMP w/4 CPU cores) Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8), LANGUAGE=pl_PL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- On 04/17/2018 03:22 PM, Sebastian Ramacher wrote: On 2018-04-17 15:07:10, Piotr Szydelko wrote: Source: mesa Version: 17.3.8-1 Severity: important I run `apt full-upgrade` and it ended up with an error. Now the `apt-get install -f` reports the following: Preparing to unpack .../mesa-va-drivers_17.3.8-1_amd64.deb ... Unpacking mesa-va-drivers:amd64 (17.3.8-1) ... dpkg: error processing archive /var/cache/apt/archives/mesa-va-drivers_17.3.8-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so', which is also in package vdpau-va-driver:amd64 0.7.4-dmo5 You are using vdpau-va-driver from dmo which is not supported. Please use the version provided by Debian. Closing per the above. Cheers, Julien--- End Message ---
Bug#884176: marked as done (libxft-dev: Please mark the package Multi-Arch: same)
Your message dated Tue, 17 Apr 2018 17:15:43 + with message-id and subject line Bug#884176: fixed in xft 2.3.2-2 has caused the Debian Bug report #884176, regarding libxft-dev: Please mark the package Multi-Arch: same 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.) -- 884176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxft-dev Version: 2.3.2-1+b2 Severity: wishlist Dear Maintainer, The package libxft-dev is not currently multi-arch installable. A comparison of the i386 and amd64 variants reveals no file conflicts. Multi-arch support is needed for packages such as libfontforge-dev and libpango1.0-dev. Please mark the package Multi-Arch: same. If it helps, I can prepare an NMU for this issue. Thank you -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libxft-dev depends on: ii libc6-dev [libc-dev] 2.25-3 ii libfontconfig1-dev 2.12.6-0.1 ii libfreetype6-dev 2.8.1-0.2 ii libx11-dev 2:1.6.4-3 ii libxft22.3.2-1+b2 ii libxrender-dev 1:0.9.10-1 ii zlib1g-dev [libz-dev] 1:1.2.8.dfsg-5 libxft-dev recommends no packages. libxft-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: xft Source-Version: 2.3.2-2 We believe that the bug you reported is fixed in the latest version of xft, 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 884...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emilio Pozuelo Monfort (supplier of updated xft 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, 17 Apr 2018 18:41:29 +0200 Source: xft Binary: libxft2 libxft2-udeb libxft-dev Architecture: source Version: 2.3.2-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Emilio Pozuelo Monfort Description: libxft-dev - FreeType-based font drawing library for X (development files) libxft2- FreeType-based font drawing library for X libxft2-udeb - FreeType-based font drawing library for X (udeb) Closes: 884176 889301 Changes: xft (2.3.2-2) unstable; urgency=medium . [ Julien Cristau ] * Use https URL in debian/watch. * Update packaging VCS URL for move to salsa. . [ Cyril Brulebois ] * Remove myself from Uploaders (Closes: #889301). . [ Emilio Pozuelo Monfort ] * Mark libxft-dev Multi-Arch: same. Thanks Hugh McMaster for the patch. (Closes: #884176). * Specify source format. * Switch to automatic -dbgsym packages. * debian/README.source: dropped, we no longer use xsfbs. * Bump the debhelper compat to 11. - parallel builds and autoreconf enabled by default. - --disable-silent-rules automatically passed by debhelper. * Switch to dh_missing and enable fail-missing. Checksums-Sha1: 062abe04d388b9c58c55381ea383b4552aab351a 2000 xft_2.3.2-2.dsc 0568a360a9f3ca97bdcdaf61535bf9d0bdae80db 402454 xft_2.3.2.orig.tar.gz 222974578037489a8de29f3ab4c58eb29597f8ae 10327 xft_2.3.2-2.diff.gz 62f32fa24037c2ff8db057bb34ea0f7dfc974ad3 5923 xft_2.3.2-2_source.buildinfo Checksums-Sha256: 56c1f34591cdc307e83abaabb28e22e190cabcf528241e18dfcd5dca9e530f89 2000 xft_2.3.2-2.dsc 26cdddcc70b187833cbe9dc54df1864ba4c03a7175b2ca9276de9f05dce74507 402454 xft_2.3.2.orig.tar.gz e94bd505f05507b5691dca9380c2bd4595ba1fd267c09831ab6e3be4bfd87062 10327 xft_2.3.2-2.diff.gz 973d4319cb1f57c4287210914a2311c11b1ad73aa2233b10622d50327e911de0 5923 xft_2.3.2-2_source.buildinfo Files: 4bdc91942a6e4eb19d8296e6d204170b 2000 devel optional xft_2.3.2-2.dsc 3a2c1ce2641817dace55cd2bfe10b0f0 402454 devel optional xft_2.3.2.orig.tar.gz 86664eba72602b630aa92d8377319a7c 10327 devel optional xft_2.3.2
Bug#889301: marked as done (Updating the xft Uploaders list)
Your message dated Tue, 17 Apr 2018 17:15:43 + with message-id and subject line Bug#889301: fixed in xft 2.3.2-2 has caused the Debian Bug report #889301, regarding Updating the xft Uploaders list 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.) -- 889301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xft Version: 2.3.2-1 Severity: minor The MIA team has received notice that Cyril Brulebois wishes no longer to be uploader of xft, but the corresponding was not filed, The MIA team and would like to ask you to remove him from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- tobi (for the MIA team) signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: xft Source-Version: 2.3.2-2 We believe that the bug you reported is fixed in the latest version of xft, 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 889...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emilio Pozuelo Monfort (supplier of updated xft 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, 17 Apr 2018 18:41:29 +0200 Source: xft Binary: libxft2 libxft2-udeb libxft-dev Architecture: source Version: 2.3.2-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Emilio Pozuelo Monfort Description: libxft-dev - FreeType-based font drawing library for X (development files) libxft2- FreeType-based font drawing library for X libxft2-udeb - FreeType-based font drawing library for X (udeb) Closes: 884176 889301 Changes: xft (2.3.2-2) unstable; urgency=medium . [ Julien Cristau ] * Use https URL in debian/watch. * Update packaging VCS URL for move to salsa. . [ Cyril Brulebois ] * Remove myself from Uploaders (Closes: #889301). . [ Emilio Pozuelo Monfort ] * Mark libxft-dev Multi-Arch: same. Thanks Hugh McMaster for the patch. (Closes: #884176). * Specify source format. * Switch to automatic -dbgsym packages. * debian/README.source: dropped, we no longer use xsfbs. * Bump the debhelper compat to 11. - parallel builds and autoreconf enabled by default. - --disable-silent-rules automatically passed by debhelper. * Switch to dh_missing and enable fail-missing. Checksums-Sha1: 062abe04d388b9c58c55381ea383b4552aab351a 2000 xft_2.3.2-2.dsc 0568a360a9f3ca97bdcdaf61535bf9d0bdae80db 402454 xft_2.3.2.orig.tar.gz 222974578037489a8de29f3ab4c58eb29597f8ae 10327 xft_2.3.2-2.diff.gz 62f32fa24037c2ff8db057bb34ea0f7dfc974ad3 5923 xft_2.3.2-2_source.buildinfo Checksums-Sha256: 56c1f34591cdc307e83abaabb28e22e190cabcf528241e18dfcd5dca9e530f89 2000 xft_2.3.2-2.dsc 26cdddcc70b187833cbe9dc54df1864ba4c03a7175b2ca9276de9f05dce74507 402454 xft_2.3.2.orig.tar.gz e94bd505f05507b5691dca9380c2bd4595ba1fd267c09831ab6e3be4bfd87062 10327 xft_2.3.2-2.diff.gz 973d4319cb1f57c4287210914a2311c11b1ad73aa2233b10622d50327e911de0 5923 xft_2.3.2-2_source.buildinfo Files: 4bdc91942a6e4eb19d8296e6d204170b 2000 devel optional xft_2.3.2-2.dsc 3a2c1ce2641817dace55cd2bfe10b0f0 402454 devel optional xft_2.3.2.orig.tar.gz 86664eba72602b630aa92d8377319a7c 10327 devel optional xft_2.3.2-2.diff.gz ea729ee3ae408c4db01521dfdab9ff78 5923 devel optional xft_2.3.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEcJymx+vmJZxd92Q+nUbEiOQ2gwIFAlrWI/YACgkQnUbEiOQ2 gwLx9w//S4ta4NvRJqaWSxfNLkwYs8o3dgxguhY/nhf8LU12Avs/XvENNNzlVD+U F77kaErTrNYV1Xi/bkNsi7yDd6eYYG23/+J+Uxks+ZJGBOp5xOKwpgZ6k3KPSh3+ 0boPzuOZVE+pTIkAQRbjGnMT/UuZoTYqGnunZoiqkgmIONhqkQ8fruxtLtJvSw6R KEFRf1JFqYQ8TMNglIjbIOTelxyAcQn62fREQyfMCoOg8zUAhmZCxaOGNeb/jw3o oCDclF8rTe/BzuDawAogEDA3TYhFySE6U+Z2ms69AgxSdsxylLdvxi7LIrFhipHI z2gGljGfjZKBIV6DgUXqbEA0SC6JY0ocnK7xTjEOvkX1US7v6IABhsaybRbAcD3j 2kaVo0A4JH8N6o9C9JgjMJkWZsOf7Lzmws0Qv+A99K1yLoebHmfzHXSZn2ZyWNE4 tl/3rzPg1qtMGcqpnpypwktfRsNozhBlOOlkrNPma6gA/EvBrRoL8gj5rm00NX5v 1hxgJnJARjXqkFB+9ja0CHeSnhV2qxNhzcs4ykmV
Bug#896146: marked as done (mesa: Update control file to point at salsa)
Your message dated Fri, 20 Apr 2018 11:52:21 + with message-id and subject line Bug#896146: fixed in mesa 18.0.1-1 has caused the Debian Bug report #896146, regarding mesa: Update control file to point at salsa 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.) -- 896146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa Severity: minor Tags: patch Dear Maintainer, Attached is a patch that updates the Vcs-Git and Vcs-Browser fields in debian/control to point at salsa rather than anonscm. This fixes current lintian warnings on these entries. Note: Patch should apply as is directly to both 17.3.9 (unstable) and 18.0.1 (experimental) branches. --- debian/control.orig 2018-04-20 17:59:50.724171710 +1000 +++ debian/control 2018-04-20 18:00:33.935088336 +1000 @@ -48,8 +48,8 @@ wayland-protocols (>= 1.9), zlib1g-dev, libglvnd-core-dev, -Vcs-Git: https://anonscm.debian.org/git/pkg-xorg/lib/mesa.git -Vcs-Browser: https://anonscm.debian.org/cgit/pkg-xorg/lib/mesa.git +Vcs-Git: https://salsa.debian.org/xorg-team/lib/mesa.git +Vcs-Browser: https://salsa.debian.org/xorg-team/lib/mesa Homepage: https://mesa3d.org/ Package: libxatracker2 --- End Message --- --- Begin Message --- Source: mesa Source-Version: 18.0.1-1 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 896...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Boll (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, 20 Apr 2018 13:29:30 +0200 Source: mesa Binary: libxatracker2 libxatracker-dev libgbm1 libgbm-dev libegl-mesa0 libegl1-mesa libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa libgles2-mesa-dev libglapi-mesa libglx-mesa0 libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-dev mesa-common-dev libosmesa6 libosmesa6-dev mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers mesa-opencl-icd Architecture: source Version: 18.0.1-1 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Andreas Boll Description: libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library libegl1-mesa - transitional dummy package libegl1-mesa-dev - free implementation of the EGL API -- development files libgbm-dev - generic buffer management API -- development files libgbm1- generic buffer management API -- runtime libgl1-mesa-dev - free implementation of the OpenGL API -- GLX development files libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules libgl1-mesa-glx - transitional dummy package libglapi-mesa - free implementation of the GL API -- shared library libgles2-mesa - transitional dummy package libgles2-mesa-dev - free implementation of the OpenGL|ES 2.x API -- development files libglx-mesa0 - free implementation of the OpenGL API -- GLX vendor library libosmesa6 - Mesa Off-screen rendering extension libosmesa6-dev - Mesa Off-screen rendering extension -- development files libwayland-egl1-mesa - transitional dummy package libxatracker-dev - X acceleration library -- development files libxatracker2 - X acceleration library -- runtime mesa-common-dev - Developer documentation for Mesa mesa-opencl-icd - free implementation of the OpenCL API -- ICD runtime mesa-va-drivers - Mesa VA-API video acceleration drivers mesa-vdpau-drivers - Mesa VDPAU video acceleration drivers mesa-vulkan-drivers - Mesa Vulkan graphics drivers Closes: 896146 Changes: mesa (18.0.1-1) experimental; urgency=medium . [ Timo Aaltonen ] * New upstream release. . [ Andreas Boll ] * Update Vcs-* URLs to point at salsa.debian.org (Closes: #896146). Thanks, Stuart Young! * Bump debhelper compat to 11. * Bump standards version to 4.1.4. Checksums-Sha1: 390c887303e305a3e19b68585f481fc25208f2a1 4887 mesa_18.0.1-1.dsc 8b366988729f86f1a5d89b8ad2b44ec4becefd44 19109328 mesa_18.0.1.orig.tar.gz e90abf67cdc24aaeb70d79df95241353be668cc3 118873 mesa_18.0.1-1.diff.gz Checksums-Sha
Bug#896602: marked as done (libglvnd: FTBFS on many architectures)
Your message dated Mon, 23 Apr 2018 08:53:19 + with message-id and subject line Bug#896602: fixed in libglvnd 1.0.0+git20180308-2 has caused the Debian Bug report #896602, regarding libglvnd: FTBFS on many architectures 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.) -- 896602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libglvnd Version: 1.0.0+git20180308-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, the snapshot uploaded to sid FTBFS on many architectures where it previously built. https://buildd.debian.org/status/package.php?p=libglvnd&suite=unstable Andreas --- End Message --- --- Begin Message --- Source: libglvnd Source-Version: 1.0.0+git20180308-2 We believe that the bug you reported is fixed in the latest version of libglvnd, 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 896...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated libglvnd 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: Mon, 23 Apr 2018 10:56:11 +0300 Source: libglvnd Binary: libglvnd-dev libglvnd-core-dev libglvnd0 libegl1 libgles2 libgl1 libglx0 libopengl0 Architecture: source Version: 1.0.0+git20180308-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libegl1- Vendor neutral GL dispatch library -- EGL support libgl1 - Vendor neutral GL dispatch library -- legacy GL support libgles2 - Vendor neutral GL dispatch library -- GLES support libglvnd-core-dev - Vendor neutral GL dispatch library -- core development files libglvnd-dev - Vendor neutral GL dispatch library -- development files libglvnd0 - Vendor neutral GL dispatch library libglx0- Vendor neutral GL dispatch library -- GLX support libopengl0 - Vendor neutral GL dispatch library -- OpenGL support Closes: 896602 Changes: libglvnd (1.0.0+git20180308-2) unstable; urgency=medium . * rules: Disable tests, they fail the build on many archs. (Closes: #896602) Checksums-Sha1: 9763cec22b5058e6222d3bd087e2fb2c1a85f98a 2439 libglvnd_1.0.0+git20180308-2.dsc 5ee1a189dc469c0afb61a51f4b66d6c6002fe968 19448 libglvnd_1.0.0+git20180308-2.debian.tar.xz 33c4f3babfc37678322cd18dcc6a96676eb52454 7509 libglvnd_1.0.0+git20180308-2_source.buildinfo Checksums-Sha256: c52a2a71b7cf59a9fbb26c9d117a9e821a124d796d0dcdb2183c21b6d888aec6 2439 libglvnd_1.0.0+git20180308-2.dsc 6ceef08fb0a7bb28f2e1486374feed65d1ae3386294244e2630b04f76f59211d 19448 libglvnd_1.0.0+git20180308-2.debian.tar.xz 20b047156c9c1463dc4b5883854b5c1413c3f3f1cce8130f9e573c23ec0a01b0 7509 libglvnd_1.0.0+git20180308-2_source.buildinfo Files: b5e7384728e3246f76f85c165c77c355 2439 libs optional libglvnd_1.0.0+git20180308-2.dsc 181dd83b73a639ac48953bf9ce662580 19448 libs optional libglvnd_1.0.0+git20180308-2.debian.tar.xz 2c1bda14c87d9ba5aba4e936fb370378 7509 libs optional libglvnd_1.0.0+git20180308-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlrdkbYACgkQy3AxZaiJ hNzLIg/9EYd1Y9KI9ypR/YPHsigYti0AuGIg13DNcIpnWyy74tM3s3kgcAjYHmOd jJGyaAiwKFUVWeu3tq8wYyotXR1/23rHsMTWHnZ4djeWDaaG8xyikkyMZ8Ah9YzI Q8Ya1ZaTTAVejacCAliHrXBGw3Q7VkjjCD9/f9Uz/U91hHH662pVMmuczYwOjDm/ p0Z+3G5oQLDjtNTT8Y1khP4iMDEiOQsR+WtrNHgiupSJkWGtpKzLGJ0lpMmeSXxM MKGEgoVAKyrdgqYACSET9GGC+imlKwDLGi5mDtF6wwdhpiZpGhTNnoTLUCVpqet8 xvB7UWTSmF6s+5SlCC11Bx9AbStMXZo9bzr7OmeVbwGw+3Am+RUQQa6tdnkCCvWn FgTI4FJXYYcigWg/KbyXiOmhFtf0yOH3Ae9mro2vGy/9yfC+TEyEFKIicqXK3H46 CxGdc3JD9SO0yHQ6icinhrzvHSfcMLSgbl6RN0KhEem6N3DQH02Y3nf8iASvhUib qwuNHeinVdz0RpHtyyTbQAHNxpI+w0qo5AIOX8Nc8OkRBZY+VgStPu98u2AApPwm YwCL4ec2hQ0L77XrNrP3+YW3MxhWhWRtIk/+qWW1IEOHMTbTZYPdXIbJJlLXpcRv n1rqvtPA6Ae0/rdbqYrO24jk1SBBPaVeqkzsssxlL0Nnqm99bN0= =XNM4 -END PGP SIGNATURE End Message ---
