Processed: redland FTCBFS: multiple issues

2022-11-16 Thread Debian Bug Tracking System
Processing control commands:

> block -1 by 1024241
Bug #1024258 [src:redland] redland FTCBFS: multiple issues
1024258 was not blocked by any bugs.
1024258 was not blocking any bugs.
Added blocking bug(s) of 1024258: 1024241

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



Bug#1024258: redland FTCBFS: multiple issues

2022-11-16 Thread Helmut Grohne
Source: redland
Version: 1.0.17-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: block -1 by 1024241
X-Debbugs-Cc: Andrej Shadura 

redland fails to cross build from source for multiple reasons. The
immediate failure is a missing dependency on pkg-config. As such, it
fails discovering rasqal and fails. Beyond that, it also uses
mysql_config, which is known to not work during cross compilation.
Instead, pkg-config should be used. Unfortunately, the .pc file shipped
by mariadb wrongly reports an ancient version (#1024241). This must be
fixed before using it. Once that has happened, the attached patch makes
redland cross buildable.

Helmut
diff --minimal -Nru redland-1.0.17/debian/changelog 
redland-1.0.17/debian/changelog
--- redland-1.0.17/debian/changelog 2022-11-14 06:03:12.0 +0100
+++ redland-1.0.17/debian/changelog 2022-11-16 09:28:10.0 +0100
@@ -1,3 +1,11 @@
+redland (1.0.17-4) UNRELEASED; urgency=medium
+
+  * Fix FTCBFS: (Closes: #-1)
++ Missing Build-Depends: pkg-config.
++ cross.patch: avoid using mysql_config
+
+ -- Helmut Grohne   Wed, 16 Nov 2022 09:28:10 +0100
+
 redland (1.0.17-3) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru redland-1.0.17/debian/control redland-1.0.17/debian/control
--- redland-1.0.17/debian/control   2022-11-14 05:57:56.0 +0100
+++ redland-1.0.17/debian/control   2022-11-16 09:28:08.0 +0100
@@ -15,6 +15,7 @@
  libsqlite3-dev,
  libtool,
  perl:any,
+ pkg-config,
  unixodbc-dev,
 Rules-Requires-Root: no
 Standards-Version: 4.6.1
diff --minimal -Nru redland-1.0.17/debian/patches/cross.patch 
redland-1.0.17/debian/patches/cross.patch
--- redland-1.0.17/debian/patches/cross.patch   1970-01-01 01:00:00.0 
+0100
+++ redland-1.0.17/debian/patches/cross.patch   2022-11-16 09:28:10.0 
+0100
@@ -0,0 +1,81 @@
+--- redland-1.0.17.orig/configure.ac
 redland-1.0.17/configure.ac
+@@ -659,25 +659,34 @@
+   fi
+   mysql_config=yes
+ fi
+-if test $mysql_config = yes -a "X$MYSQL_CONFIG" = "X" ; then
+-  AC_CHECK_PROGS(MYSQL_CONFIG, mysql_config)
+-fi
+ 
+ libmysql_min_version=3.23.56
+ # Also tested on 4.0.14
+ 
+-mysql_cflags=
+-mysql_libs=
++MYSQL_CPPFLAGS=
++MYSQL_LIBS=
++
++AS_IF([test "$mysql_config" = yes],[
++  PKG_CHECK_MODULES([MYSQL],[mysqlclient >= $libmysql_min_version],[
++mysql_config=no
++MYSQL_CPPFLAGS=$MYSQL_CFLAGS
++storages_available="$storages_available mysql"
++mysql_storage_available=yes
++  ],[])
++])
++
++if test $mysql_config = yes -a "X$MYSQL_CONFIG" = "X" ; then
++  AC_CHECK_PROGS(MYSQL_CONFIG, mysql_config)
++fi
++
+ if test "X$MYSQL_CONFIG" != X; then
+   dnl need to change quotes to allow square brackets
+   changequote(<<, >>)dnl
+-  mysql_libs=`$MYSQL_CONFIG --libs | sed -e "s/'//g"`
++  MYSQL_LIBS=`$MYSQL_CONFIG --libs | sed -e "s/'//g"`
+   # Stop the MySQL config program adding -Os or -O options to CFLAGS
+-  mysql_cflags=`$MYSQL_CONFIG --cflags | sed -e "s/'//g" -e "s/[ 
\t]-O[A-Za-z0-9]*/ /" `
++  MYSQL_CPPFLAGS=`$MYSQL_CONFIG --cflags | sed -e "s/'//g" -e "s/[ 
\t]-O[A-Za-z0-9]*/ /" `
+   changequote([, ])dnl
+ 
+-  LIBS="$LIBRDF_LIBS $mysql_libs"
+-  CPPFLAGS="$LIBRDF_CPPFLAGS $mysql_cflags"
+   AC_MSG_CHECKING(for mysql library)
+   LIBMYSQL_VERSION=`$MYSQL_CONFIG --version`
+   libmysql_version_dec=`echo $LIBMYSQL_VERSION | $AWK -F. '{printf("%d\n", 
1*$1 + 100*$2 + $3)};'`
+@@ -689,7 +698,11 @@
+ storages_available="$storages_available mysql($LIBMYSQL_VERSION)"
+ mysql_storage_available=yes
+   fi
++fi
+ 
++AS_IF([test -n "$MYSQL_LIBS"],[
++  LIBS="$LIBRDF_LIBS $MYSQL_LIBS"
++  CPPFLAGS="$LIBRDF_CPPFLAGS $MYSQL_CPPFLAGS"
+   AC_MSG_CHECKING(whether MYSQL_OPT_RECONNECT is declared)
+   AC_COMPILE_IFELSE([AC_LANG_SOURCE([#include 
+ int x=MYSQL_OPT_RECONNECT;])],
+@@ -699,8 +712,7 @@
+ 
+   LIBS="$LIBRDF_LIBS"
+   CPPFLAGS="$LIBRDF_CPPFLAGS"
+-fi
+-
++])
+ 
+ 
+ AC_ARG_WITH(sqlite, [  --with-sqlite(=yes|no) Enable SQLite store 
(default=auto)], with_sqlite="$withval", with_sqlite="auto")
+@@ -1071,9 +1083,9 @@
+ AM_CONDITIONAL(STORAGE_POSTGRESQL, test $postgresql_storage = yes)
+ AM_CONDITIONAL(STORAGE_VIRTUOSO,  test $virtuoso_storage  = yes)
+ 
+-if test $mysql_storage  = yes; then
+-  MYSQL_CPPFLAGS=`$MYSQL_CONFIG --cflags | sed -e "s/'//g" -e 
"s/-O[A-Za-z0-9]*//" `
+-  MYSQL_LIBS="$LIBRDF_LIBS $mysql_libs"
++if test $mysql_storage != yes; then
++  MYSQL_CPPFLAGS=
++  MYSQL_LIBS=
+ fi
+ if test $tstore_storage  = yes; then
+   TSTORE_CPPFLAGS="`$TSTORE_CONFIG --cflags` `$PKG_CONFIG glib --cflags`"
diff --minimal -Nru redland-1.0.17/debian/patches/series 
redland-1.0.17/debian/patches/series
--- redland-1.0.17/debian/patches/series1970-01-01 01:00:00.0 
+0100
+++ redland-1.0.17/debian/patches/series2022-11-16 09:28:10.0 
+0100
@@ -0,0 +1 @@
+cross.patch


Processing of sysrqd_14-3_sourceonly.changes

2022-11-16 Thread Debian FTP Masters
sysrqd_14-3_sourceonly.changes uploaded successfully to localhost
along with the files:
  sysrqd_14-3.dsc
  sysrqd_14-3.debian.tar.xz
  sysrqd_14-3_sourceonly.buildinfo

Greetings,

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



sysrqd_14-3_sourceonly.changes ACCEPTED into unstable

2022-11-16 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Nov 2022 18:53:26 CET
Source: sysrqd
Binary: 
Architecture: source
Version: 14-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: gregor herrmann 
Description: 
Changes:
 sysrqd (14-3) unstable; urgency=medium
 .
   * QA upload.
   * Fix init script.
 The restart action would fail if the daemon was not running, as the
 start-stop-daemon call there did not have the --oknodo option set
 (contrary to the same call in the stop action).
 Simplify the init script by using /lib/lsb/init-functions.
   * Remove unneeded debian/dirs.
   * debian/control:
 - use debhelper-compat (= 13), and
 - set Pre-Depends: ${misc:Pre-Depends}
   * debian/rules: enable all hardening flags.
Checksums-Sha256: 
 6db99862e9cbf86a1a7be2defd957e919a685a5c18ec60a43a9c3bcd864736d8 1761 
sysrqd_14-3.dsc
 d64f3001805ae5f282c96303693e4f4ce9b68fa207fd073b392ee70e0721ca22 2744 
sysrqd_14-3.debian.tar.xz
 a0f43ea4bacae703cdf4ff0e82fa434c2a5e61bcd17b9b2f2a5193f30795d5e0 6228 
sysrqd_14-3_sourceonly.buildinfo
Checksums-Sha1: 
 2b68c84fe15b0f015f429d45764b1481e4c1d9c9 1761 sysrqd_14-3.dsc
 306ae066536930b6faa2bef95013a8e64d921f7e 2744 sysrqd_14-3.debian.tar.xz
 23abc128ec6de8aaa76095050a49caa379337654 6228 sysrqd_14-3_sourceonly.buildinfo
Files: 
 0b0b972e1fcacbc3c4376eb972ade556 1761 admin optional sysrqd_14-3.dsc
 16d5186856d4179d8a62c50937870a39 2744 admin optional sysrqd_14-3.debian.tar.xz
 514c6e3bec34cd032ab07d86e0185777 6228 - - sysrqd_14-3_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmN1I5pfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbBIA/+MxxjjR9mDsTl0CICDyrnUqwQIp2qK/Qp4IUAYIhtcg2jYA0yrxTVk2jx
KidRGDEnp/qi5vtx3hj7gSSY/di/mvOBnTMBoWQI0fIn3KtpxivPGcOwHNfY5Mbg
SQHhMyn4l4wPd1HrwHkfEAi5t8jA6Ahoz1xRFlyknkvqqINAjeJRCAirME2QLlJJ
FpPWEhpXMqvLflEFsClyZcooxJNZQStk22kEcA18tWTdEeoOkYyio8HlSvHt1dxS
S3T+wvVJUSjYQ2G+4kvRe1sMuz/QV456bRXuHmmnW77XbClrzqHmXhD8V5wyFcpM
8vNtsr9aSszkgmS8gL8yTc+/IXJhGUy76oTzGBk0rag80h3MKjAkX1qk2d1nEUTd
DYrqI70ZBY66w45WL+oeGgm/9h1ijR7Kw+z4WRHwkK7C+CszoLNsETXvWpvZRQ9z
JcdTVxjWc6TvhHAwkEYJ1qBOm1AC3WGh6jyAxSSGchVW6+PKkzZ8P+mfoZCy7Tvh
Bpjl9KnqiQM+KB88ezVpMYsyM1frn5guz7oQUeCoKSIJFWHBof7UvjIHFgTn2AMe
6NKGYF+DX6B8LswuG1YeixpN2gcjZvUlg97o5CKhA/SJMz1IP7U1blsSZAVOpeOp
K9prtspCE8GEnyFxBI1iHG9xZa9hRroe11qVke2P1TExHMYq/Y8=
=aH57
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Processing of openvpn-auth-radius_2.1-8~bpo11+1_amd64.changes

2022-11-16 Thread Debian FTP Masters
openvpn-auth-radius_2.1-8~bpo11+1_amd64.changes uploaded successfully to 
localhost
along with the files:
  openvpn-auth-radius_2.1-8~bpo11+1.dsc
  openvpn-auth-radius_2.1.orig.tar.gz
  openvpn-auth-radius_2.1-8~bpo11+1.debian.tar.xz
  openvpn-auth-radius-dbgsym_2.1-8~bpo11+1_amd64.deb
  openvpn-auth-radius_2.1-8~bpo11+1_amd64.buildinfo
  openvpn-auth-radius_2.1-8~bpo11+1_amd64.deb

Greetings,

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



Processing of flask-babel_2.0.0-3_source.changes

2022-11-16 Thread Debian FTP Masters
flask-babel_2.0.0-3_source.changes uploaded successfully to localhost
along with the files:
  flask-babel_2.0.0-3.dsc
  flask-babel_2.0.0-3.debian.tar.xz
  flask-babel_2.0.0-3_amd64.buildinfo

Greetings,

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



flask-babel_2.0.0-3_source.changes ACCEPTED into unstable

2022-11-16 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Nov 2022 19:36:50 +
Source: flask-babel
Architecture: source
Version: 2.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Jelmer Vernooij 
Changes:
 flask-babel (2.0.0-3) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.6.1, no changes needed.
Checksums-Sha1:
 17d9efd45161988ee252bda86ee2513433e86f04 2207 flask-babel_2.0.0-3.dsc
 703e0b5783187c295c4c116d8f6fb70a80be26ef 3904 flask-babel_2.0.0-3.debian.tar.xz
 351a6974ba1ddcf82620701c5b5f377f1c9a1411 8708 
flask-babel_2.0.0-3_amd64.buildinfo
Checksums-Sha256:
 427f842e05cf42fdc6f387e639a55836a6fc2b7018653cc0cca0f42f4657fa47 2207 
flask-babel_2.0.0-3.dsc
 6e0ce2b4e992e5249d0bc96ac3aaf4088362b866deba39b0a80024f2cda116d8 3904 
flask-babel_2.0.0-3.debian.tar.xz
 b658486230c50be5d70a07a215758793bd6a242d70e7ca44c6422f74aa1f8ca5 8708 
flask-babel_2.0.0-3_amd64.buildinfo
Files:
 2f118add68070446e85dc10ee73d48ae 2207 python optional flask-babel_2.0.0-3.dsc
 ab13e3772677a288eb88fbb806d29f76 3904 python optional 
flask-babel_2.0.0-3.debian.tar.xz
 e075e8b6d2259141f4aba5ddb6de8fcb 8708 python optional 
flask-babel_2.0.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAmN1PB0ACgkQV5wWDUye
I+juEQ//e0TH+GRdVzhQnIzFQIbW6DL2vwD8RF1t/R5w2q9PWxTvFdZmC7mOilIx
D4WNTDGCeAJQw0BtEqismVFv0L36sU+PSwL0iEeMF5HMJI6kVY2PvADKK6BkKWZk
6Y/5YT395QOKtz0lZKMDlEsDvZNcZk2vkR/UOME0aj/MBjToC/2VIJSaNqohJKri
tWyC8cglRmxRFyu6SEqRPkMfKVVnBvmfIpDZCDNpoo6q79fEQatwrlOOC1C7f6fY
h9QmIKgLOnDWQ7zpRb+uXhzSJ5gayY+NhE271NUmtKCAsyymR/crj+wQYsZaCuqP
W0eiEI8XERHJbHSSWxBeIhIyLLpAdkdO67/68embO6PgWpfcRYCa9FkHjSeJ9RQe
WmF+7fB9QpDIhvUjxm02x5CbEJ7469gkqueORGsOpnHjVGhaKT0yVTXt4gc8LPDp
OzEHOFK2/5DD5skPSxNmhBg2mjnnXrRwD06QJWAMQjmR6HtwyMIVWoqLPGC4YVCH
1gPWOQE7rqwsE7mkrrU7+PQ7z6ynUImJTbsmqhoKilsoma9LvWVgcJ3JTbG+kE65
s2o/S388yfks8PufZqSMlV5B1RgnlLk42M7eErdjc3xmb12JNMBi0OtTTGUryMoK
Smi6mV7ApnHbFMWOLkeyGQmDydueFQ9SvzSZBdf5afdFjbQCffs=
=lr4X
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Bug#1024279: tolua++: reproducible-builds: build path embedded in tolua++5.1

2022-11-16 Thread Vagrant Cascadian
Source: tolua++
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build path is embedded in /usr/bin/tolua++5.1:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/tolua++.html

  /build/1st/tolua++-1.0.93/src/bin/tolua.c:84
  vs.
  /build/2/tolua++-1.0.93/2nd/src/bin/tolua.c:84

The attached patch to debian/rules fixes this by adding
-ffile-prefix-map to the CCFLAGS included in debian/custom.py.

According to my local tests, with this patch applied tolua++ should build
reproducibly on tests.reproducible-builds.org!

Thanks for maintaining tolua++!

live well,
  vagrant
From d911d743084b67294d20379c4f9375f75dcac9f1 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 16 Nov 2022 22:52:46 +
Subject: [PATCH] debian/rules: Avoid embedding build paths by adding
 -ffile-prefix-map to CCFLAGS.

---
 debian/rules | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/rules b/debian/rules
index 1f3c3d5..8552863 100755
--- a/debian/rules
+++ b/debian/rules
@@ -10,6 +10,8 @@ override_dh_clean:
 
 override_dh_auto_configure:
 	cp $(CURDIR)/debian/custom.py $(CURDIR)
+	# Add -ffile-prefix-map to CCFLAGS to avoid embedding build paths.
+	sed -i -e "s,CCFLAGS = .,CCFLAGS =['-ffile-prefix-map=$(CURDIR)=.'\,,g" $(CURDIR)/custom.py
 	scons prefix=$(CURDIR)/debian/libtolua++5.1-dev/usr configure
 
 override_dh_auto_build:
-- 
2.38.1



signature.asc
Description: PGP signature


Bug#1024282: twoftpd: reproducible-builds: buildid differences in various binaries

2022-11-16 Thread Vagrant Cascadian
Source: twoftpd
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The buildid differs when built from a different path:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/twoftpd.html

The attached patch to debian/rules fixes this by adding
-ffile-prefix-map to CFLAGS.

Switching to dh and a recent debhelper compat level might also solve
this problem.

According to my local tests, with this patch applied, twoftpd should
build reproducibly on tests.reproducible-builds.org!

Thanks for maintaining twoftpd!

live well,
  vagrant
From cecd1ef2c4696e009cb18ae2ad3661169cc34dea Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 16 Nov 2022 23:15:16 +
Subject: [PATCH] debian/rules: Add -ffile-prefix-map to CFLAGS to avoid
 embedding build paths.

https://reproducible-builds.org/docs/build-path/
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 4342317..4bc21ee 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,7 +5,7 @@ ifneq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
   STRIP =: nostrip
 endif
 
-CFLAGS =-g -O2 -Wall
+CFLAGS =-g -O2 -Wall -ffile-prefix-map=$(CURDIR)=.
 LDFLAGS =
 CC =gcc
 BGLIBS =/usr/lib/bglibs
-- 
2.38.1



signature.asc
Description: PGP signature


Bug#1024283: ipsvd: reproducible-builds: buildid differences in various binaries

2022-11-16 Thread Vagrant Cascadian
Source: ipsvd
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The buildid differs when built from a different path for various
binaries in /usr/bin:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/ipsvd.html

The attached patch to debian/rules fixes this by adding
-ffile-prefix-map to CFLAGS.

Switching to dh and a recent debhelper compat level might also solve
this problem.

According to my local tests, with this patch applied, ipsvd should
build reproducibly on tests.reproducible-builds.org!

Thanks for maintaining ipsvd!

live well,
  vagrant
From 7310c68df7db93c4b837e18e70cebfde1a60f9ae Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 16 Nov 2022 23:30:03 +
Subject: [PATCH] debian/rules: Add -ffile-prefix-map to CFLAGS to avoid
 embedding build paths.

https://reproducible-builds.org/docs/build-path/
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index f3d69a5..97ec522 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,7 +5,7 @@ ifneq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
   STRIP =: nostrip
 endif
 
-CFLAGS =-g -O2 -Wall
+CFLAGS =-g -O2 -Wall -ffile-prefix-map=$(CURDIR)=.
 LDFLAGS =-Os
 CC =gcc
 ifneq (,$(findstring diet,$(DEB_BUILD_OPTIONS)))
-- 
2.38.1



signature.asc
Description: PGP signature


Bug#1024284: gentoo: reproducible-builds: home directory embedded in /usr/bin/gentoo

2022-11-16 Thread Vagrant Cascadian
Source: gentoo
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: environment
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The home directory of the build user is embedded in /usr/bin/gentoo:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/gentoo.html

The attached patch to src/Makefile.am fixes this by adding setting the
configuration option to a fixed value.

According to my local tests, with this patch applied, gentoo should
build reproducibly on tests.reproducible-builds.org!

Thanks for maintaining gentoo!

live well,
  vagrant
From 2445243834ff430f55ed0e6bfa2abb4846a2f9dc Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 16 Nov 2022 23:33:50 +
Subject: [PATCH] src/Makefile.am: Do not embed the build user's home directory

---
 src/Makefile.am | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/Makefile.am b/src/Makefile.am
index eb0194c..07bd08b 100644
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -203,7 +203,7 @@ localedir=@localedir@
 
 AM_CFLAGS=@GENTOO_CFLAGS@ @GTK_CFLAGS@ -I../widgets \
   -DPATH_CFG=\"$(sysconfdir)\" \
-  -DPATH_GRC=\"$$HOME/\" \
+  -DPATH_GRC=\"/nonexistent/\" \
   -DPATH_ICN=\"$(datadir)/gentoo/icons\"\
   -DLOCALEDIR=\"$(localedir)\"
 
-- 
2.38.1



signature.asc
Description: PGP signature


Bug#1024286: lcm: reproducible-builds: Embedded build path and usrmerge paths in Makefile

2022-11-16 Thread Vagrant Cascadian
Source: lcm
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath usrmerge
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build path and binary paths are embedded in
/usr/share/doc/lcm-doc/examples/Makefile:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/lcm.html

  ACLOCAL·=·${SHELL}·'/build/1st/lcm-1.3.1+repack1/missing'·aclocal-1.16
  vs.
  ACLOCAL·=·${SHELL}·'/build/2/lcm-1.3.1+repack1/2nd/missing'·aclocal-1.16

  EGREP·=·/bin/grep·-E
  vs.
  EGREP·=·/usr/bin/grep·-E

The attached patch fixes this by removing the example Makefile, which
would have to be regenerated anyways to match the system to run it on.

If removing the example Makefile is not viable, it might be possible to
sanitize the build paths, and all relevent arguments to configure
(e.g. EGREP='/bin/grep -e') to use the specified paths.

According to my local tests, With this patch applied lcm should build
reproducibly on tests.reproducible-builds.org!

Thanks for maintaining lcm!

live well,
  vagrant
From 65bc199c9a7bdb9f8a7fde7dc3aad441105394cf Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Thu, 17 Nov 2022 00:25:41 +
Subject: [PATCH] debian/rules: Remove example Makefile that embedded build
 paths and binary paths.

---
 debian/rules | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/debian/rules b/debian/rules
index f29f30d..c9efc4e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -13,6 +13,12 @@ override_dh_auto_install:
 # I build the docs after the 'make install' because the python docs require an installed lcm
 	cd docs; ./build-docs.sh
 
+override_dh_installdocs:
+	dh_installdocs
+	# Remove example makefile which contains build paths and
+	# binary paths
+	rm -vf debian/liblcm-doc/usr/share/doc/liblcm-doc/examples/Makefile
+
 override_dh_auto_clean:
 	dh_auto_clean
 	rm -rf docs/html
-- 
2.38.1



signature.asc
Description: PGP signature


Bug#984149: Fwd: Bug#984149: genparse: Fix ftbfs: Use "std=c++14" flag to build

2022-11-16 Thread Paul Wise
Forwarding a response that went to the wrong place.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
--- Begin Message ---
Source: genparse
Version: 0.9.2-1
Followup-For: Bug #984149
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

Dear Maintainer,

This patch will make this package build with C++14 standard, as this package 
doesn`t install any header files in /usr/include, so this patch should be OK.

I tried build on amd64/riscv64 and both succeed with this patch.

Thanks, 
Yifan Xu
--- rules   2016-11-10 20:18:01.0 +0800
+++ genparse-0.9.2/debian/rules 2022-11-15 17:59:38.254170492 +0800
@@ -4,6 +4,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic
+export DEB_CPPFLAGS_MAINT_APPEND = -std=c++14
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
 RM = \
Description: fix ftbfs: use std=c++14 flag to build
 .
 genparse (0.9.2-2) unstable; urgency=medium
 .
   * Add -std=c++14 flag
Author: Yifan Xu 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Bug-Debian: https://bugs.debian.org/984149
Last-Update: 2022-11-15

--- genparse-0.9.2.orig/tests/misc/test-lib.sh
+++ genparse-0.9.2/tests/misc/test-lib.sh
@@ -27,7 +27,7 @@ error_() { echo "$0: $@" 1>&2; exit 1; }
 framework_failure() { error_ 'failure in testing framework'; }
 
 CFLAGS=-I.
-CXXFLAGS=-I.
+CXXFLAGS="-std=c++14 -I."
 GNULIB_CPPFLAGS=-I$srcdir/../../gnulib/lib
 GNULIB_LDFLAGS="-L../../gnulib/lib -lgnu"
 
--- End Message ---


signature.asc
Description: This is a digitally signed message part


Bug#1024209: genparse: Fix ftbfs: Use "std=c++14" flag to build

2022-11-16 Thread Paul Wise
close 1024209
tags 984149 + patch
user debian-ri...@lists.debian.org
usertags 1024209 - riscv64
thanks

On Wed, 2022-11-16 at 11:58 +0800, Yifan Xu wrote:

> To: Debian Bug Tracking System 
> Followup-For: Bug #984149

Please submit followups for existing bug reports to the existing bugs
instead of submitting new bug reports containing the followups.

I have forwarded your mail to bug #984149 just now:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984149#16

> User: debian-ri...@lists.debian.org
> Usertags: riscv64
> X-Debbugs-Cc: debian-ri...@lists.debian.org

This bug isn't riscv64-specific so you should not add the riscv64
usertags and should not CC the debian-riscv mailing list.

> Dear Maintainer,

I note that this package is orphaned so it doesn't have a maintainer.

https://tracker.debian.org/pkg/genparse

I also note that the upstream of this package isn't very active:

https://sourceforge.net/p/genparse/

> This patch will make this package build with C++14 standard, as this package 
> doesn`t install any header files in /usr/include, so this patch should be OK.

When submitting patches to the BTS, it is a good idea to mark the bug
as having a patch using the patch tag. Add this to the pseudo-headers:

Control: tags -1 + patch

https://www.debian.org/Bugs/Reporting#control
https://www.debian.org/Bugs/server-control#tag
https://www.debian.org/Bugs/Developer#tags

The patch to debian/rules seems like it should have been made to the
upstream build system so both patches could be sent upstream instead.

In addition both patches are workarounds not proper fixes, since they
switch the package to an older version of C++ instead of fixing it to
work with the current version of C++.

Since this package is orphaned in Debian, unmaintained upstream,
nothing in Debian seems to depend on it and fails to build with current
versions of its build dependencies, perhaps it should be just removed
from Debian instead of fixing it? If you agree, please file a removal:

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#removing-packages

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Processed: Re: Bug#1024209: genparse: Fix ftbfs: Use "std=c++14" flag to build

2022-11-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1024209
Bug #1024209 [src:genparse] genparse: Fix ftbfs: Use "std=c++14" flag to build
Marked Bug as done
> tags 984149 + patch
Bug #984149 [src:genparse] genparse: ftbfs with GCC-11
Added tag(s) patch.
> user debian-ri...@lists.debian.org
Setting user to debian-ri...@lists.debian.org (was nekorou...@outlook.com).
> usertags 1024209 - riscv64
Usertags were: riscv64.
There are now no usertags set.
> thanks
Stopping processing here.

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



adv-17v35x is marked for autoremoval from testing

2022-11-16 Thread Debian testing autoremoval watch
adv-17v35x 5.0.6.0-3 is marked for autoremoval from testing on 2022-12-07

It is affected by these RC bugs:
1023662: adv-17v35x-dkms: module fails to build for Linux 6.0
 https://bugs.debian.org/1023662



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl