[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1025308: gsequencer: FTBFS with fftw3 (3.3.10-1)



On 12/2/22 16:39, Sebastiaan Couwenberg wrote:
The test target still fails because it uses xvfb which is broken by the recent update of mesa (#1025312).

A work around for the xvfb failure is to set LIBGL_ALWAYS_SOFTWARE=1 in the environment.

The updated debdiff that also implemented this is attached.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
diff -Nru gsequencer-4.4.1/debian/changelog gsequencer-4.4.1/debian/changelog
--- gsequencer-4.4.1/debian/changelog	2022-09-16 05:57:45.000000000 +0200
+++ gsequencer-4.4.1/debian/changelog	2022-12-02 12:21:38.000000000 +0100
@@ -1,3 +1,11 @@
+gsequencer (4.4.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Build depend on libfftw3-dev, fftw3-dev no longer provided.
+  * Set LIBGL_ALWAYS_SOFTWARE=1 for xvfb-run to work around #1025312.
+
+ -- Bas Couwenberg <sebastic@debian.org>  Fri, 02 Dec 2022 12:21:38 +0100
+
 gsequencer (4.4.1-1) unstable; urgency=medium
 
   * New upstream version 4.4.1
diff -Nru gsequencer-4.4.1/debian/control gsequencer-4.4.1/debian/control
--- gsequencer-4.4.1/debian/control	2022-09-16 05:57:45.000000000 +0200
+++ gsequencer-4.4.1/debian/control	2022-12-02 12:21:38.000000000 +0100
@@ -10,7 +10,7 @@
  docbook-xml,
  docbook-xsl,
  dssi-dev,
- fftw3-dev,
+ libfftw3-dev,
  fop,
  gettext,
  gstreamer1.0-plugins-bad,
diff -Nru gsequencer-4.4.1/debian/rules gsequencer-4.4.1/debian/rules
--- gsequencer-4.4.1/debian/rules	2022-09-16 05:57:45.000000000 +0200
+++ gsequencer-4.4.1/debian/rules	2022-12-02 12:21:38.000000000 +0100
@@ -43,7 +43,7 @@
 	$(MAKE) DESTDIR=$$(pwd)/debian/tmp pdf
 
 override_dh_auto_test:
-	xvfb-run --server-args="-screen 0 1920x1080x24" -a dh_auto_test
+	LIBGL_ALWAYS_SOFTWARE=1 xvfb-run --server-args="-screen 0 1920x1080x24" -a dh_auto_test
 
 override_dh_auto_install:
 	dh_auto_install --no-parallel

Reply to: