Bug#1034931: libfl-dev: missing Breaks+Replaces for flex-old when upgrading from bullseye
On 2023-04-27 Helmut Grohne wrote: > Package: libfl-dev > Version: 2.6.4-8.1 > Severity: serious > Justification: dpkg unpack error > Attempting to unpack libfl-dev/2.6.4-8.1 from Debian bookworm > on a minimal Debian bullseye with flex-old/2.5.4a-10.1 > installed, causes an unpack error from dpkg due to > /usr/include/FlexLexer.h being contained in both packages. [...] > Please ensure that libfl-dev has sufficient Breaks and Replaces declarations. Hello, we currently have: Package: libfl-dev Replaces: flex (<< 2.5.39), flex-old (<= 2.5.4a-10) Breaks: flex (<< 2.5.39), flex-old (<= 2.5.4a-10) However afaict there are no plans for splitting flex-old into flex-old and libfl-old-dev so this file conflict is permanent, i.e. libfl-dev should use unversioned Conflicts instead of versioned Breaks. On sidenote I think flex should Conflict with flex-old like flex-old does. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1004961: libwmf: please fix cross-test on i386
On 2023-05-17 Gianfranco Costamagna wrote: > control: tags -1 patch pending > Hello, this debdiff will be uploaded in unstable once the current one > migrates. Hello Gianfranco, looks like you accidentally closed this bug instead of tagging it. cu Andreas
Bug#969907: Bug#969537: epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8
On 2023-05-07 Andreas Metzler wrote:
[...]
> The only proper fix would be to use versioned symbols for libpoppler
> (and libpoppler-glib while we are at it). This should not be rocket
> science, just tie it to the soname.
> But that needs to happen upstream.
Something like attached patch.
cu Andreas
Description: Use symbol versioning for libpoppler
.
This needs to be applied upstream when the soname is bumped.
Author: Andreas Metzler
Origin: vendor
Bug-Debian: https://bugs.debian.org/969907
Forwarded: no
Last-Update: 2023-05-14
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -572,16 +572,31 @@ ADD_GPERF_FILE(TimesBoldWidths)
ADD_GPERF_FILE(TimesBoldItalicWidths)
ADD_GPERF_FILE(TimesItalicWidths)
ADD_GPERF_FILE(TimesRomanWidths)
ADD_GPERF_FILE(ZapfDingbatsWidths)
+set(POPPLER_SOVERSION_NUMBER "126")
+
+set(LINKER_SCRIPT "${CMAKE_BINARY_DIR}/libpoppler.map")
+configure_file(
+"${CMAKE_SOURCE_DIR}/poppler/libpoppler.map.in"
+${LINKER_SCRIPT})
+
if(MSVC)
add_definitions(-D_CRT_SECURE_NO_WARNINGS)
endif()
-add_library(poppler ${poppler_SRCS})
+add_library(poppler ${poppler_SRCS} ${LINKER_SCRIPT})
generate_export_header(poppler BASE_NAME poppler-private EXPORT_FILE_NAME "${CMAKE_CURRENT_BINARY_DIR}/poppler_private_export.h")
-set_target_properties(poppler PROPERTIES VERSION 126.0.0 SOVERSION 126)
+set_target_properties(poppler PROPERTIES
+ VERSION ${POPPLER_SOVERSION_NUMBER}.0.0
+ SOVERSION ${POPPLER_SOVERSION_NUMBER})
+
+if(UNIX AND (NOT APPLE))
+ set_target_properties(poppler PROPERTIES
+ LINK_OPTIONS LINKER:--version-script=${LINKER_SCRIPT})
+endif()
+
if(MINGW AND BUILD_SHARED_LIBS)
get_target_property(POPPLER_SOVERSION poppler SOVERSION)
set_target_properties(poppler PROPERTIES SUFFIX "-${POPPLER_SOVERSION}${CMAKE_SHARED_LIBRARY_SUFFIX}")
endif()
target_link_libraries(poppler LINK_PRIVATE ${poppler_LIBS})
--- /dev/null
+++ b/poppler/libpoppler.map.in
@@ -0,0 +1,4 @@
+POPPLER_@POPPLER_SOVERSION_NUMBER@ {
+ global:
+*;
+};
Bug#1036025: unblock: exim4/4.96-15
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: ex...@packages.debian.org
Control: affects -1 + src:exim4
Please unblock package exim4
This fixes an initialzation error which caused a crash in the smtp
transport. See https://bugs.exim.org/show_bug.cgi?id=2996
It is a one-line change, I have also removed garbage (unapplied patch)
from debian/patches.
cu Andreas
unblock exim4/4.96-15
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru exim4-4.96/debian/changelog exim4-4.96/debian/changelog
--- exim4-4.96/debian/changelog 2023-02-04 13:33:50.0 +0100
+++ exim4-4.96/debian/changelog 2023-05-10 18:30:35.0 +0200
@@ -1,3 +1,12 @@
+exim4 (4.96-15) unstable; urgency=medium
+
+ * Pull from upstream GIT master:
++ 75_70-Fix-variable-initialisation-in-smtp-transport.-Bug-2.patch
+ Fix a crash in the smtp transport.
+ https://bugs.exim.org/show_bug.cgi?id=2996
+
+ -- Andreas Metzler Wed, 10 May 2023 18:30:35 +0200
+
exim4 (4.96-14) unstable; urgency=medium
* Pull from upstream GIT master:
diff -Nru exim4-4.96/debian/patches/75_42-Fix-run-arg-parsing.patch exim4-4.96/debian/patches/75_42-Fix-run-arg-parsing.patch
--- exim4-4.96/debian/patches/75_42-Fix-run-arg-parsing.patch 2022-12-04 08:02:50.0 +0100
+++ exim4-4.96/debian/patches/75_42-Fix-run-arg-parsing.patch 1970-01-01 01:00:00.0 +0100
@@ -1,99 +0,0 @@
-From 44b6e099b76f403a55e77650821f8a69e9d2682e Mon Sep 17 00:00:00 2001
-From: Jeremy Harris
-Date: Sat, 3 Dec 2022 23:13:53 +
-Subject: [PATCH] Fix ${run } arg parsing
-
-Broken-by: cfe6acff2ddc
- doc/ChangeLog| 4
- src/expand.c | 13 ++---
- src/transport.c | 4 +++-
- test/scripts/-Basic/0002 | 2 ++
- test/stdout/0002 | 2 ++
- 5 files changed, 21 insertions(+), 4 deletions(-)
-
a/doc/ChangeLog
-+++ b/doc/ChangeLog
-@@ -28,10 +28,14 @@
- JH/14 Bug 2933: Fix regex substring match variables for null matches. Since 4.96
- a capture group which obtained no text (eg. "(abc)*" matching zero
- occurrences) could cause a segfault if the corresponding $ was
- expanded.
-
-+JH/15 Fix argument parsing for ${run } expansion. Previously, when an argument
-+ included a close-brace character (eg. it itself used an expansion) an
-+ error occurred.
-+
-
-
- Exim version 4.96
- -
-
a/src/expand.c
-+++ b/src/expand.c
-@@ -5529,11 +5529,11 @@
- {
- FILE * f;
- const uschar * arg, ** argv;
- BOOL late_expand = TRUE;
-
-- if ((expand_forbid & RDO_RUN) != 0)
-+ if (expand_forbid & RDO_RUN)
- {
- expand_string_message = US"running a command is not permitted";
- goto EXPAND_FAILED;
- }
-
-@@ -5561,16 +5561,23 @@
- }
- s++;
-
- if (late_expand) /* this is the default case */
- {
-- int n = Ustrcspn(s, "}");
-+ int n;
-+ const uschar * t;
-+ /* Locate the end of the args */
-+ (void) expand_string_internal(s,
-+ ESI_BRACE_ENDS | ESI_HONOR_DOLLAR | ESI_SKIPPING, , NULL, NULL);
-+ n = t - s;
- arg = skipping ? NULL : string_copyn(s, n);
- s += n;
- }
- else
- {
-+ DEBUG(D_expand)
-+ debug_printf_indent("args string for ${run} expand before split\n");
- if (!(arg = expand_string_internal(s, TRUE, , skipping, TRUE, )))
- goto EXPAND_FAILED;
- Uskip_whitespace();
- }
- /*{*/
a/src/transport.c
-+++ b/src/transport.c
-@@ -2187,10 +2187,12 @@
- BOOL allow_dollar_recipients = addr && addr->parent
- && Ustrcmp(addr->parent->address, "system-filter") == 0;
-
- for (int i = 0; argv[i]; i++)
- {
-+DEBUG(D_expand) debug_printf_indent("arg %d\n", i);
-+
- /* Handle special fudge for passing an address list */
-
- if (addr &&
- (Ustrcmp(argv[i], "$pipe_addresses") == 0 ||
- Ustrcmp(argv[i], "${pipe_addresses}") == 0))
-@@ -2361,11 +2363,11 @@
- }
- else *errptr = msg;
- return FALSE;
- }
-
-- if ( f.running_in_test_harness && is_tainted(expanded_arg)
-+ if ( f.running_in_test_harness && is_tainted(expanded_arg)
- && Ustrcmp(etext, "queryprogram router") == 0)
- { /* hack, would be good to not need it */
- DEBUG(D_transport)
- debug_printf("SPECIFIC TESTSUITE EXEMPTION: tainted arg '%s'\n",
- expanded_arg);
diff -Nru exim4-4.96/debian/patches/75_70-Fix-variable-initialisation-in-smtp-transport.-Bug-2.patch exim4-4.96/debian/patches/75_70-Fix-variable-initialisation-in-smtp-transport.-Bug-2.patch
--- exim4-4.96/debian/patches/75_70-Fix-variable-initialisation-in-smtp-transport.-Bug-2.patch 1970-01-01 01:00:00.
Bug#1036005: unblock: pcp/6.0.3-1.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: p...@packages.debian.org, ametz...@bebt.de
Control: affects -1 + src:pcp
Hello,
Please unblock package pcp, this just adds missing Replaces: for
upgrades from stable to testing.
The NMU was originally uploaded to the delayed queue but I later got
the go ahead from the package maintainer(s) to move to 0-day.
unblock pcp/6.0.3-1.1
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru pcp-6.0.3/debian/changelog pcp-6.0.3/debian/changelog
--- pcp-6.0.3/debian/changelog 2023-02-23 00:52:31.0 +0100
+++ pcp-6.0.3/debian/changelog 2023-05-07 11:36:37.0 +0200
@@ -1,3 +1,18 @@
+pcp (6.0.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add missing replaces on pcp (<< 5.3.0):
++ pcp-export-pcp2elasticsearch Closes: #1034998
++ pcp-export-pcp2json Closes: #1034983
++ pcp-export-pcp2spark Closes: #1034932
++ pcp-export-pcp2xml Closes: #1034922
++ pcp-export-pcp2zabbix Closes: #1034973
++ pcp-doc Closes: #1034966
++ pcp-zeroconf Closes: #1034895
++ pcp-export-pcp2xlsx (unfiled)
+
+ -- Andreas Metzler Sun, 07 May 2023 11:36:37 +0200
+
pcp (6.0.3-1) unstable; urgency=low
* New release (full details in CHANGELOG).
diff -Nru pcp-6.0.3/debian/control pcp-6.0.3/debian/control
--- pcp-6.0.3/debian/control 2023-02-23 00:52:31.0 +0100
+++ pcp-6.0.3/debian/control 2023-05-07 07:37:15.0 +0200
@@ -385,6 +385,7 @@
Package: pcp-export-pcp2elasticsearch
Depends: python3-pcp, python3-requests, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to Elasticsearch
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -409,6 +410,7 @@
Package: pcp-export-pcp2json
Depends: python3-pcp, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to JSON
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -417,6 +419,7 @@
Package: pcp-export-pcp2spark
Depends: python3-pcp, python3-requests, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to Apache Spark
Performance Co-Pilot (PCP) front-end tools for exporting metric values
@@ -425,6 +428,7 @@
Package: pcp-export-pcp2xml
Depends: python3-pcp, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to XML
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -433,6 +437,7 @@
Package: pcp-export-pcp2zabbix
Depends: python3-pcp, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to Zabbix
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -449,7 +454,7 @@
Section: doc
Depends: ${misc:Depends}
Breaks: pcp (<< 5.3.0), pcp-gui (<< 1.5.13)
-Replaces: pcp-gui (<< 1.5.13)
+Replaces: pcp (<< 5.3.0), pcp-gui (<< 1.5.13)
Suggests: pcp, pcp-gui
Architecture: all
Description: Documentation and tutorial for the Performance Co-Pilot
@@ -462,6 +467,7 @@
Package: pcp-zeroconf
Depends: ${misc:Depends}, ${shlibs:Depends}, pcp (= ${binary:Version})
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Performance Co-Pilot (PCP) Zeroconf Package
Contains configuration tweaks and files that increase metrics gathering
@@ -511,6 +517,7 @@
Package: pcp-export-pcp2xlsx
Depends: ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to Excel spreadsheets
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
signature.asc
Description: PGP signature
Bug#969907: Bug#969537: epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8
On 2021-02-18 Simon McVittie wrote: [...] > So elpa-pdf-tools-server is linked to libpoppler-glib, and because the > (parts of the) libpoppler-glib API that it uses has not changed for a > while, it is happy with an old version; but then during a partial > upgrade, it can get this > elpa-pdf-tools-server > \- old libpoppler-glib > | \- libpoppler95 > \- libpoppler102 > and the two copies of libpoppler fight? > That seems entirely plausible, and I don't immediately see a way to > fix it without adding Breaks (which would force a lockstep upgrade, > somewhat defeating the purpose of SONAMEs). [...] Hello, The only proper fix would be to use versioned symbols for libpoppler (and libpoppler-glib while we are at it). This should not be rocket science, just tie it to the soname. But that needs to happen upstream. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1034895: pcp: diff for NMU version 6.0.3-1.1
Control: tags -1 pending
Dear maintainer,
I've prepared an NMU for pcp (versioned as 6.0.3-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
kind regards
Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru pcp-6.0.3/debian/changelog pcp-6.0.3/debian/changelog
--- pcp-6.0.3/debian/changelog 2023-02-23 00:52:31.0 +0100
+++ pcp-6.0.3/debian/changelog 2023-05-07 11:36:37.0 +0200
@@ -1,3 +1,18 @@
+pcp (6.0.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add missing replaces on pcp (<< 5.3.0):
++ pcp-export-pcp2elasticsearch Closes: #1034998
++ pcp-export-pcp2json Closes: #1034983
++ pcp-export-pcp2spark Closes: #1034932
++ pcp-export-pcp2xml Closes: #1034922
++ pcp-export-pcp2zabbix Closes: #1034973
++ pcp-doc Closes: #1034966
++ pcp-zeroconf Closes: #1034895
++ pcp-export-pcp2xlsx (unfiled)
+
+ -- Andreas Metzler Sun, 07 May 2023 11:36:37 +0200
+
pcp (6.0.3-1) unstable; urgency=low
* New release (full details in CHANGELOG).
diff -Nru pcp-6.0.3/debian/control pcp-6.0.3/debian/control
--- pcp-6.0.3/debian/control 2023-02-23 00:52:31.0 +0100
+++ pcp-6.0.3/debian/control 2023-05-07 07:37:15.0 +0200
@@ -385,6 +385,7 @@
Package: pcp-export-pcp2elasticsearch
Depends: python3-pcp, python3-requests, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to Elasticsearch
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -409,6 +410,7 @@
Package: pcp-export-pcp2json
Depends: python3-pcp, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to JSON
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -417,6 +419,7 @@
Package: pcp-export-pcp2spark
Depends: python3-pcp, python3-requests, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to Apache Spark
Performance Co-Pilot (PCP) front-end tools for exporting metric values
@@ -425,6 +428,7 @@
Package: pcp-export-pcp2xml
Depends: python3-pcp, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to XML
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -433,6 +437,7 @@
Package: pcp-export-pcp2zabbix
Depends: python3-pcp, ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to Zabbix
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
@@ -449,7 +454,7 @@
Section: doc
Depends: ${misc:Depends}
Breaks: pcp (<< 5.3.0), pcp-gui (<< 1.5.13)
-Replaces: pcp-gui (<< 1.5.13)
+Replaces: pcp (<< 5.3.0), pcp-gui (<< 1.5.13)
Suggests: pcp, pcp-gui
Architecture: all
Description: Documentation and tutorial for the Performance Co-Pilot
@@ -462,6 +467,7 @@
Package: pcp-zeroconf
Depends: ${misc:Depends}, ${shlibs:Depends}, pcp (= ${binary:Version})
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Performance Co-Pilot (PCP) Zeroconf Package
Contains configuration tweaks and files that increase metrics gathering
@@ -511,6 +517,7 @@
Package: pcp-export-pcp2xlsx
Depends: ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}
Breaks: pcp (<< 5.3.0)
+Replaces: pcp (<< 5.3.0)
Architecture: any
Description: Tool for exporting data from PCP to Excel spreadsheets
Performance Co-Pilot (PCP) front-end tool for exporting data from PCP
signature.asc
Description: PGP signature
Bug#1034959: libwmf: diff for NMU version 0.2.12-5.1
Control: tags 1034959 + patch
Control: tags 1034959 + pending
Dear maintainer,
I've prepared an NMU for libwmf (versioned as 0.2.12-5.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Kind regards
Andreas
diff -Nru libwmf-0.2.12/debian/changelog libwmf-0.2.12/debian/changelog
--- libwmf-0.2.12/debian/changelog 2022-01-25 09:16:35.0 +0100
+++ libwmf-0.2.12/debian/changelog 2023-05-06 18:19:26.0 +0200
@@ -1,3 +1,11 @@
+libwmf (0.2.12-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add missing Breaks/Replaces on libwmf0.2-7-gtk to libwmf-0.2-7-gtk.
+Closes: #1034959
+
+ -- Andreas Metzler Sat, 06 May 2023 18:19:26 +0200
+
libwmf (0.2.12-5) unstable; urgency=medium
* Upload to unstable
diff -Nru libwmf-0.2.12/debian/control libwmf-0.2.12/debian/control
--- libwmf-0.2.12/debian/control 2022-01-25 09:16:35.0 +0100
+++ libwmf-0.2.12/debian/control 2023-05-06 18:17:54.0 +0200
@@ -53,8 +53,8 @@
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}, libwmf-0.2-7 (= ${binary:Version})
-Breaks: libwmf0.2-7 (<< 0.2.8.4-12)
-Replaces: libwmf0.2-7 (<< 0.2.8.4-12)
+Breaks: libwmf0.2-7 (<< 0.2.8.4-12), libwmf0.2-7-gtk (<< 0.2.12-1)
+Replaces: libwmf0.2-7 (<< 0.2.8.4-12), libwmf0.2-7-gtk (<< 0.2.12-1)
Description: Windows metafile conversion GTK pixbuf plugin
Windows metafile (WMF) is a picture format used by many Windows
programs, e.g. Microsoft Word. libwmf is a library for interpreting
signature.asc
Description: PGP signature
Bug#1034986: xmorph: missing Breaks+Replaces for libmorph when upgrading from bullseye
On 2023-04-29 Andreas Metzler wrote: [...] > Trivial patch: [...] I will fix this. cu Andreas
Bug#1022702: gnupg: Migrating packaging from 2.2.x to "stable" 2.3.x
On 2023-04-27 Simon Josefsson wrote: > > I have spent a little bit of effort on packaging 2.4.0. I have pushed > > this to salsa (sans tags) into 3 temporary branches that could be [...] > Hi, > What do you think about uploading these to experimental, to allow > testing? > I have built your branch and there appears to be community interest in > having binary packages hosted somewhere, and I'm exploring options. My > fairly limited testing suggests they work, and resolve many fixed issues > that I've had with the 2.2.x series so I will use these myself going > forward. > https://lists.gnupg.org/pipermail/gnupg-users/2023-April/066490.html > https://lists.gnupg.org/pipermail/gnupg-users/2023-April/066500.html Hello Simon, I do not indend to hijack/adopt gnupg2, so I am very reluctant to upload without some kind of go from Daniel or Eric. (Even to experimental.) However I have updated the GIT branches to 2.4.1 today. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1034986: xmorph: missing Breaks+Replaces for libmorph when upgrading from bullseye
On 2023-04-27 Helmut Grohne wrote:
> Package: xmorph
> Version: 1:20150712-1
> Severity: serious
> Justification: dpkg unpack error
> Attempting to unpack xmorph/1:20150712-1 from Debian bookworm
> on a minimal Debian bullseye with libmorph/1:20140707+nmu2.1
> installed, causes an unpack error from dpkg due to
> /usr/share/man/man1/morph.1.gz being contained in both packages.
> | Selecting previously unselected package xmorph.
> | (Reading database ... 4692 files and directories currently installed.)
> | Preparing to unpack .../xmorph_1%3a20150712-1_amd64.deb ...
> | Unpacking xmorph (1:20150712-1) ...
> | dpkg: error processing archive ./xmorph_1%3a20150712-1_amd64.deb (--unpack):
> | trying to overwrite '/usr/share/man/man1/morph.1.gz', which is also in
> package libmorph 1:20140707+nmu2.1
> | Errors were encountered while processing:
> | ./xmorph_1%3a20150712-1_amd64.deb
[...]
Trivial patch:
--- a/debian/control
+++ b/debian/control
@@ -38,6 +38,8 @@ Architecture: any
Depends: ${misc:Depends},
${shlibs:Depends}
Suggests: imagemagick | netpbm | xmorph-example
+Breaks: libmorph (<< 1:20150712-1~)
+Replaces: libmorph (<< 1:20150712-1~)
Description: digital image warp and morph (x11)
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
On 2023-04-20 Paul Gevers wrote: > Hi Andreas, > On Fri, 31 Mar 2023 15:06:14 +0200 Andreas Metzler wrote: > > I think 2.5.7-2 was the last sourceful < 3 upload, so (<< 2.5.7-3) > > should work. > And to be backports and other local packages, I think that could/should be > (<< 2.5.7-3~). > Can a/this fix be uploaded soon please? We're trying to pick a bookworm > release date and a fix should be in. Hello Paul, I will not have time for a NMU before next week, I can probably fit it in then. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1034350: gnutls28: autopkgtest regression everywhere except amd64: src/nonexist-builddir/gnutls_ktls: not found
On 2023-04-13 Paul Gevers wrote: > Source: gnutls28 > Version: 3.7.9-1 > Severity: serious > Control: tags -1 bookworm-ignore > User: debian...@lists.debian.org > Usertags: regression > Dear maintainer(s), > Your package has an autopkgtest, great. However, it fails everywhere but on > amd64. If I understand correctly, the 32 bits architecture failures are due > to datefudge/faketime (bug 1031553) and started in September 2022. The 64 > bits architectures started to fail more recently in March 2023. Because some > hosts on ci.debian.net have been upgraded to bookworm recently, I was > fearing/suspecting it might be kernel related, but running the test on an > amd64/bookworm kernel passes. Can you please investigate the situation and > fix it? [...] Thank you. Looks like this did not fail on amd64 since thes machines do not have the tls module loaded while arm64 has. The test should be properly blacklisted instead since a) gnutls is built without ktls support and b) because it is not a pure shell test using gnutls-bin. Should be trivial to fix, will do. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1034156: libgpg-error: New upstream version 1.47
Source: libgpg-error Version: 1.46-1 Severity: wishlist Hello, libgpg-error 1.47 has been released, please find branches on salssa that could be fast-forwarded: debian/experimental-tmp-1.47 --> debian/experimental pristine-tar-tmp-1.47 --> pristine-tar upstream-tmp-1.47 --> upstream cu Andreas
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
Control: tags -1 moreinfo Control: severity -1 normal On 2023-04-06 Wensheng Xie wrote: > Package: exim4 > Severity: important > X-Debbugs-Cc: none, Wensheng Xie [...] >* What exactly did you do (or not do) that was effective (or > ineffective)? > Sending/receiving emails to local users is ok; > LAN users receiving emails from server PC is ok, but cannot send > emails. >* What was the outcome of this action? > exim paniclog /var/log/exim4/paniclog on lenovo has non-zero size, mail > system might be broken. Up to 10 lines are quoted below. > 2023-03-17 23:26:36 daemon_notifier_socket bind: Address already in use ^ [...] Actually that does seem to be relevant at all, the message is from March 17. What do the configuration files look like (especially /etc/exim4/update-exim4.conf.conf)? What doi the log files show for which mail? cu Andreas
Bug#1034080: sdop: fails to clean after successful build: No rule to make target 'distclean'.
Control: tags -1 - ftbfs On 2023-04-08 Andreas Beckmann wrote: > Source: sdop > Version: 1.00-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source twice in a row > Hi, > sdop/experimental fails to build twice in a row. (I haven't checked > whether the package in sid has the same problem.) > The first build succeeds, but the subsequent clean fails: Hello Andreas, thanks, I will fix it. FWIW I think "does not build twice" is something completely different than FTBFS and does not match the tag description. cu Andreas
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
On 2023-04-06 Wensheng Xie wrote: > Package: exim4 > Severity: important > X-Debbugs-Cc: none, Wensheng Xie [...] >* What exactly did you do (or not do) that was effective (or > ineffective)? > Sending/receiving emails to local users is ok; > LAN users receiving emails from server PC is ok, but cannot send > emails. >* What was the outcome of this action? > exim paniclog /var/log/exim4/paniclog on lenovo has non-zero size, mail > system might be broken. Up to 10 lines are quoted below. > 2023-03-17 23:26:36 daemon_notifier_socket bind: Address already in use > 2023-03-17 23:31:06 socket bind() to port 25 for address 127.0.0.1 failed: > Address already in use: daemon abandoned > 2023-03-17 23:31:34 socket bind() to port 25 for address 127.0.0.1 failed: > Address already in use: daemon abandoned >* What outcome did you expect instead? > There is no error, and emails for LAN users via port 25 should work. Looks like there is another program liestening on port 25. cu Andreas
Bug#1031553: gnutls28: please depend on faketime instead of datefudge
On 2023-02-18 Nicolas Boulenguez wrote: > Source: gnutls28 > Version: 3.7.9-1 > Hello. > Datefudge is broken on 32-bit architectures (release-critical bug > #1028587). The author recommends to use alternative tools in message > 24 of the bug log. Only two consumers are remaining, gnutls28 and > oath-toolkit. > The attached diff replaces datefudge with faketime in gnutls28. > The change only affects tests. > A test fails after a local build, but the timestamps seem correct. > The severity is 'wishlist' for gnutls28, but the attached patch (and a > similar one for oath-toolkit) would allow to remove the datefudge > package and 1 RC bug from bookworm. [...] Hello, after a couple of iterations and reworks gnutls upstream /master/ branch now supports both faketime and datefudge. However I am a bit reluctant to patch gnutls 3.7 for bookworm: * Net win (and only if oath-toolkit also switches in time for bookworm) is that datefudge could be removed. The real brokenness remains, since faketime also suffers from the bug (#1032177) and I /think/ it is unlikely to be fixed in time for bookworm. * Downsides: + Rather huge patch that is unlikely to end up in gnutls 3.7.x series + GnuTLS master branch (3.8.x) will probaby move away from datefudge/faketime and use a (newly added) -attime option. So we will patch in dead code. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
Control: tags -1 confirmed patch
On 2023-03-28 Felix Stupp wrote:
> Package: libopenexr-dev
> Version: 3.1.5-4
> Severity: serious
> Justification: Policy 7.4
> X-Debbugs-Cc: me+debian-b...@banananet.work
> Dear Maintainer,
> I cannot upgrade this package from version 2.5.7-1 to version 3.1.5-4
> due to a file conflict with the package libilmbase-dev on version
[...]
Thank you Felix! dist-upgrading from libopenexr{25,-dev} 2.5.7-1 and
libilmbase{25,-dev} 2.5.7-2+b1 fails with
Preparing to unpack .../libopenexr-dev_3.1.5-4_amd64.deb ...
Unpacking libopenexr-dev (3.1.5-4) over (2.5.7-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libopenexr-dev_3.1.5-4_amd64.deb (--unpack):
trying to overwrite '/usr/include/OpenEXR/Iex.h', which is also in package
libilmbase-dev:amd64 2.5.7-2+b1
due to the versioning of the Breaks:/Replaces which was not binNMU-safe:
ametzler@argenau:/tmp$ dpkg --info
/var/cache/apt/archives/libopenexr-dev_3.1.5-4_amd64.deb | grep 'Breaks\|Repl'
Breaks: libilmbase-dev (<= 2.5.7-2)
Replaces: libilmbase-dev (<= 2.5.7-2)
I think 2.5.7-2 was the last sourceful < 3 upload, so (<< 2.5.7-3)
should work.
---
diff --git a/debian/changelog b/debian/changelog
index 9c5fae4..fa9c263 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+openexr (3.1.5-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Make versioning of libilmbase-dev Breaks/Replaces binNMU-safe.
+Closes: #1033617
+
+ -- Andreas Metzler Fri, 31 Mar 2023 15:02:17 +0200
+
openexr (3.1.5-4) unstable; urgency=medium
* d/control: Add missing zlib1g-dev dependency. Closes: #1017516
diff --git a/debian/control b/debian/control
index 5fecc23..3d783c2 100644
--- a/debian/control
+++ b/debian/control
@@ -49,8 +49,8 @@ Package: libopenexr-dev
Section: libdevel
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
-Replaces: libilmbase-dev (<= 2.5.7-2)
-Breaks: libilmbase-dev (<= 2.5.7-2)
+Replaces: libilmbase-dev (<< 2.5.7-3)
+Breaks: libilmbase-dev (<< 2.5.7-3)
Depends: libimath-dev (>= 3.1.2),
libopenexr-3-1-30 (= ${binary:Version}),
zlib1g-dev,
--
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
On 2023-03-28 Felix Stupp wrote: > Package: libopenexr-dev > Version: 3.1.5-4 > Severity: serious > Justification: Policy 7.4 > X-Debbugs-Cc: me+debian-b...@banananet.work > Dear Maintainer, > I cannot upgrade this package from version 2.5.7-1 to version 3.1.5-4 > due to a file conflict with the package libilmbase-dev on version > 2.5.4-1. I tried with apt & aptitude as well. Both want to replace > libilmbase-dev with libopenexr-dev in a single execution of them, but > fail to do that in a way that dpkg allows that (tries first to install > the new package and then uninstall the old one). > Currently I see no other solution than removing the old one first aside > with all packages depending it on it, and then installing the new one > with all packages which were removed before. [...] Hello, I cannot reporoduce this from your description because the original setup you started with libopenexr-dev + libopenexr25 2.5.7-1 libilmbase-dev + libilmbase25 2.5.4-1 is not installable, libopenexr25 2.5.7-1 depends on libilmbase25 (>= 2.5.7). cu Andreas
Bug#1033155: gnupg2: diff for NMU version 2.2.40-1.1
Control: tags 1033155 + pending
Dear maintainer,
I've prepared an NMU for gnupg2 (versioned as 2.2.40-1.1) and
uploaded it non-delayed.
Kind regards
Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru gnupg2-2.2.40/debian/changelog gnupg2-2.2.40/debian/changelog
--- gnupg2-2.2.40/debian/changelog 2022-10-19 17:09:42.0 +0200
+++ gnupg2-2.2.40/debian/changelog 2023-03-26 15:03:05.0 +0200
@@ -1,3 +1,11 @@
+gnupg2 (2.2.40-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * In migration CI test skip debian-archive-bookworm-stable.gpg (and
+aggregated keyring), gpg1 cannot read the ed25519 key. Closes: #1033155
+
+ -- Andreas Metzler Sun, 26 Mar 2023 15:03:05 +0200
+
gnupg2 (2.2.40-1) unstable; urgency=medium
* new upstream version
diff -Nru gnupg2-2.2.40/debian/tests/migration gnupg2-2.2.40/debian/tests/migration
--- gnupg2-2.2.40/debian/tests/migration 2022-09-02 00:08:12.0 +0200
+++ gnupg2-2.2.40/debian/tests/migration 2023-03-26 15:03:05.0 +0200
@@ -11,7 +11,9 @@
mkdir "$GPG_HOME"
chmod 700 "$GPG_HOME"
-cat /usr/share/keyrings/debian-archive-*.gpg | "${gpg1[@]}" --import
+cat $(ls /usr/share/keyrings/debian-archive-*.gpg \
+ | grep -vE 'debian-archive-bookworm-stable.gpg|debian-archive-keyring.gpg') \
+ | "${gpg1[@]}" --import
"${gpg1[@]}" --list-keys
"${gpg[@]}" --list-keys > "$DIR/key.list.before"
migrate-pubring-from-classic-gpg "$GPG_HOME"
signature.asc
Description: PGP signature
Bug#1033155: migration test fails when EC key present in test keyrings
On 2023-03-26 Andreas Metzler wrote: > On 2023-03-18 Jonathan Wiltshire wrote: [...] > > The stable release key for bookworm is EC, and this causes gpg1 to bail > > out when it is imported as part of the migration test. Attached patch > > limits the keyrings used to the archive's automatic keys, which are > > still RSA. > [...] > afaict currently all keys are RSA except for > debian-archive-bookworm-stable.gpg. Wouldn't it be better to just skip > this single key? Hello, I am going to fix this by NMU. (non-delayed, Daniel is on the LowThresholdNmu list.) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' signature.asc Description: PGP signature
Bug#1033155: migration test fails when EC key present in test keyrings
On 2023-03-18 Jonathan Wiltshire wrote: > Source: gnupg2 > Version: 2.2.40-1 > Severity: important > Tags: patch > X-Debbugs-Cc: j...@debian.org > Hi, > The stable release key for bookworm is EC, and this causes gpg1 to bail > out when it is imported as part of the migration test. Attached patch > limits the keyrings used to the archive's automatic keys, which are > still RSA. [...] Hello Jonathan, afaict currently all keys are RSA except for debian-archive-bookworm-stable.gpg. Wouldn't it be better to just skip this single key? cu Andreas
Bug#992172: exim4: CVE-2021-38371
On 2023-03-15 Moritz Mühlenhoff wrote: > Am Sun, Aug 15, 2021 at 07:21:40AM +0200 schrieb Andreas Metzler: > > On 2021-08-14 Salvatore Bonaccorso wrote: [...] > > > CVE-2021-38371[0]: > > > | The STARTTLS feature in Exim through 4.94.2 allows response injection > > > | (buffering) during MTA SMTP sending. > > [...] > > > > IIRC that is mitigated in experimental (4.95 rc) by ALPN and unkown > > command related changes, I will not be able to check in detail for a > > week or so, though. > Do you know if this is fixed in 4.96/bookworm? Yes it is. 4.95 and later are fine. https://lists.exim.org/lurker/message/20230315.200011.3128be8e.en.html cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1031553: gnutls28: please depend on faketime instead of datefudge
On 2023-02-18 Nicolas Boulenguez wrote:
[...]
> The attached diff replaces datefudge with faketime in gnutls28.
> The change only affects tests.
> A test fails after a local build, but the timestamps seem correct.
[...]
Hello Nicolas,
That is caused by changing the date specs to include a space ...
-EXP_OCSP_DATE="2016-03-27"
+EXP_OCSP_DATE="2016-03-27 00:00:00"
... combined with unquoted args to faketime:
-datefudge -s ${EXP_OCSP_DATE} \
+faketime -f ${EXP_OCSP_DATE} \
I will try to get this applied upstream before changing Debian (unless
somebody else beats me to it), but it might take some time.
cu Andreas
Bug#1031020: sqop: Fails to verify sig on gnutls28_3.7.8.orig.tar.xz
Package: sqop Version: 0.27.2-1 Severity: normal X-Debbugs-Cc: ametz...@bebt.de I thought this should work, but it does not: sqop verify gnutls28_3.7.8.orig.tar.xz.asc gnutls-3.7.8/debian/upstream/signing-key.asc < gnutls28_3.7.8.orig.tar.xz.asc No acceptable signatures found One of the signing keys (462225C3B46F34879FC8496CD605848ED7E69871) is in gnutls-3.7.8/debian/upstream/signing-key.asc: ametzler@argenau:/tmp/GNUTLS$ gpg gnutls28_3.7.8.orig.tar.xz.asc gpg: WARNING: no command supplied. Trying to guess what you mean ... gpg: assuming signed data in 'gnutls28_3.7.8.orig.tar.xz' gpg: Signature made Di 27 Sep 2022 16:07:05 CEST gpg:using RSA key A6AB53A01D237A94F9EEC4D0412748A40AFCC2FB gpg: Good signature from "Alexander Sosedkin " [unknown] gpg: aka "[jpeg image of size 984]" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E987 AB7F 7E89 6677 76D0 5B3B B0E9 DD20 B29F 1432 Subkey fingerprint: A6AB 53A0 1D23 7A94 F9EE C4D0 4127 48A4 0AFC C2FB gpg: Signature made Di 27 Sep 2022 17:14:15 CEST gpg:using RSA key 462225C3B46F34879FC8496CD605848ED7E69871 gpg: Good signature from "Daiki Ueno " [undefined] gpg: aka "Daiki Ueno " [undefined] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 4622 25C3 B46F 3487 9FC8 496C D605 848E D7E6 9871 gpg: Signature made Di 27 Sep 2022 17:36:07 CEST gpg:using EDDSA key 5D46CB0F763405A7053556F47A75A648B3F9220C gpg: Good signature from "Zoltan Fridrich " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 5D46 CB0F 7634 05A7 0535 56F4 7A75 A648 B3F9 220C ametzler@argenau:/tmp/GNUTLS$ gpg gnutls-3.7.8/debian/upstream/signing-key.asc gpg: WARNING: no command supplied. Trying to guess what you mean ... pub rsa3104 2008-05-04 [SC] [expires: 2028-04-29] 1F42418905D8206AA754CCDC29EE58B996865171 uid Nikos Mavrogiannopoulos uid Nikos Mavrogiannopoulos uid Nikos Mavrogiannopoulos sub rsa2048 2018-02-06 [S] [expires: 2028-02-04] sub rsa2048 2018-02-06 [E] [expires: 2028-02-04] pub rsa4096 2009-07-23 [SC] [expires: 2023-09-25] 462225C3B46F34879FC8496CD605848ED7E69871 uid Daiki Ueno uid Daiki Ueno sub rsa4096 2010-02-04 [E] (Same behavior on sid 0.27.3-1) cu Andreas
Bug#1031019: sqop verify underdocumented, seems to expect to be verified file on stdin
Package: sqop Version: 0.27.2-1 Severity: normal X-Debbugs-Cc: ametz...@bebt.de According to both manpage and "sqop help verify" sqop verify accepts exactly to args (sig and cert) plus two options (--not-after/--not-before). However this command simply hangs: sqop verify gnutls28_3.7.8.orig.tar.xz.asc gnutls-3.7.8/debian/upstream/signing-key.asc Reading #969590 I found that the to-be verified tarball needs to be passed as third arg on stdin. (Reporting on testing, but also applies to sqop 0.27.3-1.) Andreas
Bug#1029238: imv not found in $PATH
On 2023-01-20 tester732732 via Pkg-phototools-devel wrote: > Package: imv > Version: 4.3.0-1.1+b3 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: devnull771...@proton.me > Dear Maintainer, >* What led up to the situation? > After installing imv on debian Bookwork, the binary is not saved in > /usr/bin but can instead only be found in /usr/libexec/imv/imv > This makes using imv on the command line impossible, most noteable when > using terminal file manager like ranger [...] Quote /usr/share/doc/imv/README.Debian: | Starting from upstream version 4.0.0 imv ships two binaries that | handle Wayland and X11 natively: imv-wayland and imv-x11. To allow | seamless usage to users upstream provides a /usr/bin/imv wrapper that | checks whether a Wayland compositor is available before running the | appropriate binary. | The Debian package does not ship the wrapper script to avoid a file | name clash with the renameutils package. Invoking either imv-wayland or imv-x11 should work perfectly fine on the commandline. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1029117: libtasn1-6: Convert d/copyright to machine-readable format
Control: tags -1 -patch On 2023-01-17 Bastian Germann wrote: > Source: libtasn1-6 > Version: 4.19.0-2 > Tags: patch > Please consider converting the debian/copyright file to the machine-readable > format. > I have attached a converted file that also adds the missing X11 and FSFAP > license and some copyright lines. Good morning, DEP-5 per file copyright is quite unmanageable (i.e. enormously time-consuming if done properly) for non-tiny pieces of software if done manually by editing debian/copyright. I will happily apply patches that do the right thing with "cme update dpkg-copyright", i.e. with debian/fill.copyright.blanks.yml debian/copyright-scan-patterns.yml and debian/fix.scanned.copyright but just doing a one-time conversion with huge maintenance costs afterwards is not productive use of time. cme seems to be only piece of softwar in Debian thatv tries to tackle this, but the degree of handholding required via debian/*copyright* is still huge. cu Andreas
Bug#1018029: idesk: FTBFS with imlib2 1.9.1
On 2022-08-24 Markus Koschany wrote: > Package: idesk > Version: 0.7.5-6 > Severity: important > Tags: ftbfs sid bookwork > User: a...@debian.org > Usertags: imlib2-1.9.1 > X-Debbugs-Cc: a...@debian.org > Dear maintainer, > your package fails to build from source with imlib2 1.9.1 in > experimental. imlib2-config has been dropped by upstream in favor of > pkg-config. Please adjust your build system accordingly. I intend to > upload imlib2 1.9.1 to unstable in one or two months. Feel free to > reply to this bug report if you have any questions. I will take look. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1027137: kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas"
Control: tags -1 patch On 2022-12-28 Sebastian Ramacher wrote: > Source: kicad > Version: 6.0.10+dfsg-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > https://buildd.debian.org/status/fetch.php?pkg=kicad=amd64=6.0.10%2Bdfsg-1%2Bb2=1672197224=0 [...] > /<>/include/gal/opengl/kiglew.h:47:14: error: #error > "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL > canvas" >47 | #error "KICAD_USE_EGL can only be used when wxWidgets is > compiled with the EGL canvas" > | ^ Hello, wxWidgets has recently switched back to non-EGL (See https://bugs.debian.org/1024147 and https://bugs.debian.org/1020640), for kicad the build error is trivially fixable by changing -DKICAD_USE_EGL=ON \ back to -DKICAD_USE_EGL=OFF \ (Ideally the cmake setup should check wxWidgets's EGL-status and set KICAD_USE_EGL accordingly instead of failing at build-time.) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1026487: libvigraimpex: FTBFS: IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices
On 2022-12-20 Lucas Nussbaum wrote: > Source: libvigraimpex > Version: 1.11.1+dfsg-10 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221220 ftbfs-bookworm > Hi, > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] > > executing test file > > /<>/obj.x86_64-linux-gnu/vigranumpy/test/test_arraytypes.py > > .EEE.EE. [...] > > ERROR: test_arraytypes.testImage1 > > -- > > Traceback (most recent call last): > > File > > "/<>/obj.x86_64-linux-gnu/vigranumpy/vigra/arraytypes.py", > > line 1271, in __getitem__ > > res = numpy.ndarray.__getitem__(self, index) > > IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis > > (`None`) and integer or boolean arrays are valid indices > > > > During handling of the above exception, another exception occurred: [...] This is caused/triggered by the recent numpy upgrade from 1:1.21.5-2 to 1:1.23.5-2. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1022702: gnupg: Migrating packaging from 2.2.x to "stable" 2.3.x
Control: retitle -1 gnupg: Migrating packaging from 2.2.x to "stable" 2.4.x On 2022-10-24 Hideki Yamane wrote: > Package: gnupg > Severity: wishlist > Dear Maintainer, > I've noticed that now upstream says 2.3 branch is "stable" series, > not development ones since 2.3.5. [...] Hello, I have spent a little bit of effort on packaging 2.4.0. I have pushed this to salsa (sans tags) into 3 temporary branches that could be fast-forwarded: tmp-ametzler-pristine-tar --ff-> pristine-tar tmp-ametzler-upstream --ff-> upstream tmp-ametzler-v2.4 --ff-> debian/experimental (Merge request does not really seem to make sense for something that requires updating 3 branches at the same time.) However there are some open questions: * The Debian package features some non-trivial patches that need to be doublechecked. The gpg-agent-idling patches were already disabled by Christoph in the 2.3.1-1 upload. * Policy. There seems to be dissens between gnupg and the IETF openpgp workgroup. (See https://lists.gnupg.org/pipermail/gnupg-devel/2022-December/035183.html ff) I do not understand the whole thing well enough to judge the benefits of gnupg's approach, however dissens is evident from reading the thread. I amn not sure whether I could make sense for Debian to wait for thing to play out. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1024475: basket: Loses gpgme integration when rebuilt against gpgme 1.18.0-2
Control: tags -1 pending
On 2022-11-20 Andreas Metzler wrote:
> Package: basket
> Version: 2.49-1
> Severity: important
> User: pkg-gnupg-ma...@lists.alioth.debian.org
> Usertags: gpgme-config-transition
> Hello,
> basket relies on gpgme-config to detect gpgme. gpgme-config has been
> dropped and replaced by pkg-config pc files.
Straightforward patch attached.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru basket-2.49/debian/changelog basket-2.49/debian/changelog
--- basket-2.49/debian/changelog 2019-08-20 21:55:23.0 +0200
+++ basket-2.49/debian/changelog 2022-12-10 14:13:50.0 +0100
@@ -1,3 +1,10 @@
+basket (2.49-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use pkg-config to locate gpgme. Closes: #1024475
+
+ -- Andreas Metzler Sat, 10 Dec 2022 14:13:50 +0100
+
basket (2.49-1) unstable; urgency=medium
* New release (2.49):
diff -Nru basket-2.49/debian/patches/05_gpgme-pkg_search_module.diff basket-2.49/debian/patches/05_gpgme-pkg_search_module.diff
--- basket-2.49/debian/patches/05_gpgme-pkg_search_module.diff 1970-01-01 01:00:00.0 +0100
+++ basket-2.49/debian/patches/05_gpgme-pkg_search_module.diff 2022-12-10 14:13:50.0 +0100
@@ -0,0 +1,61 @@
+Description: Use pkg-config to locate gpgme
+Author: Andreas Metzler
+Bug-Debian: https://bugs.debian.org/1024475
+Origin: vendor
+Forwarded: no
+Last-Update: 2022-12-10
+
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -10,11 +10,12 @@
+ find_package(ECM REQUIRED NO_MODULE)
+ set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} ${ECM_MODULE_PATH})
+
+ set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} "${CMAKE_SOURCE_DIR}/cmake/Modules/")
+ IF(NOT BASKET_DISABLE_GPG)
+- find_package(Gpgme)
++ FIND_PACKAGE(PkgConfig)
++ pkg_search_module(GPGME gpgme)
+ ENDIF(NOT BASKET_DISABLE_GPG)
+
+ # libgit2
+ find_package(Libgit2)
+ IF(LIBGIT2_FOUND)
+--- a/src/CMakeLists.txt
b/src/CMakeLists.txt
+@@ -1,6 +1,6 @@
+-include_directories(${GPGME_INCLUDES})
++include_directories(${GPGME_INCLUDE_DIRS})
+
+ ### next target ###
+
+ set(basketcommon_LIB_SRCS
+ aboutdata.cpp
+@@ -67,11 +67,11 @@
+
+ add_library(basketcommon SHARED ${basketcommon_LIB_SRCS} ${basket_FORM_HDRS} ${basket_RESOURCES})
+
+ target_link_libraries(basketcommon
+ ${PHONON_LIBRARY}
+- ${GPGME_VANILLA_LIBRARIES}
++ ${GPGME_LIBRARIES}
+ KF5::Archive
+ KF5::ConfigWidgets
+ KF5::CoreAddons
+ KF5::Crash
+ KF5::DBusAddons
+--- a/src/tests/CMakeLists.txt
b/src/tests/CMakeLists.txt
+@@ -36,11 +36,11 @@
+
+ add_executable(${_testname} ${_testname}.cpp ${baskettest_SRCS})
+ ecm_mark_as_test(${_testname})
+ add_dependencies(tests ${_testname})
+
+-target_link_libraries(${_testname} basketcommon ${GPGME_VANILLA_LIBRARIES} Qt5::Test)
++target_link_libraries(${_testname} basketcommon ${GPGME_LIBRARIES} Qt5::Test)
+ endmacro(basket_full_unit_test)
+
+
+ basket_standalone_unit_test(notetest)
+ basket_standalone_unit_test(basketviewtest)
diff -Nru basket-2.49/debian/patches/series basket-2.49/debian/patches/series
--- basket-2.49/debian/patches/series 2019-08-20 21:49:15.0 +0200
+++ basket-2.49/debian/patches/series 2022-12-10 14:11:08.0 +0100
@@ -1 +1,2 @@
01-fix-mimetype-installation.patch
+05_gpgme-pkg_search_module.diff
Bug#1024500: libdnf: Loses gpgme integration when rebuilt against gpgme 1.18.0-2
Control: tags -1 patch
On 2022-11-20 Andreas Metzler wrote:
> Source: libdnf
> Version: 0.55.2-6
> Severity: important
> User: pkg-gnupg-ma...@lists.alioth.debian.org
> Usertags: gpgme-config-transition
> The package relies on gpgme-config to detect gpgme. gpgme-config has been
> dropped and replaced by pkg-config pc files.
Straightforward patch attached.
cu Andreas
diff -Nru libdnf-0.55.2/debian/changelog libdnf-0.55.2/debian/changelog
--- libdnf-0.55.2/debian/changelog 2021-04-14 21:26:57.0 +0200
+++ libdnf-0.55.2/debian/changelog 2022-12-10 13:48:46.0 +0100
@@ -1,3 +1,10 @@
+libdnf (0.55.2-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use pkg-config to locate gpgme. Closes: #1024500
+
+ -- Andreas Metzler Sat, 10 Dec 2022 13:48:46 +0100
+
libdnf (0.55.2-6) unstable; urgency=high
* Add patch for signature check with rpmcliVerifySignatures. Closes: #986802.
diff -Nru libdnf-0.55.2/debian/patches/0020_gpmgme-pkg-config.diff libdnf-0.55.2/debian/patches/0020_gpmgme-pkg-config.diff
--- libdnf-0.55.2/debian/patches/0020_gpmgme-pkg-config.diff 1970-01-01 01:00:00.0 +0100
+++ libdnf-0.55.2/debian/patches/0020_gpmgme-pkg-config.diff 2022-12-10 13:48:46.0 +0100
@@ -0,0 +1,34 @@
+Description: Use pkg-config to locate gpgme
+Author: Andreas Metzler
+Bug-Debian: https://bugs.debian.org/1024500
+Origin: vendor
+Forwarded: no
+Last-Update: 2022-12-10
+
+--- libdnf-0.55.2.orig/CMakeLists.txt
libdnf-0.55.2/CMakeLists.txt
+@@ -48,9 +48,11 @@ if(APPLE)
+ endif()
+ LIST (APPEND CMAKE_MODULE_PATH "${CMAKE_INSTALL_PREFIX}/share/cmake/libsolv/")
+
+-
+ # build dependencies
+-find_package(Gpgme REQUIRED)
++pkg_search_module(GPGME REQUIRED gpgme)
++if (${GPGME_FOUND})
++message (STATUS "found gpgme ${GPGME_VERSION}")
++endif (${GPGME_FOUND})
+ find_package(LibSolv 0.6.30 REQUIRED COMPONENTS ext)
+ find_package(OpenSSL REQUIRED)
+
+--- libdnf-0.55.2.orig/libdnf/CMakeLists.txt
libdnf-0.55.2/libdnf/CMakeLists.txt
+@@ -71,7 +71,7 @@ target_link_libraries(libdnf
+ ${JSONC_LIBRARIES}
+ ${LIBMODULEMD_LIBRARIES}
+ ${SMARTCOLS_LIBRARIES}
+-${GPGME_VANILLA_LIBRARIES}
++${GPGME_LIBRARIES}
+ )
+
+ if(ENABLE_RHSM_SUPPORT)
diff -Nru libdnf-0.55.2/debian/patches/series libdnf-0.55.2/debian/patches/series
--- libdnf-0.55.2/debian/patches/series 2021-04-14 21:26:57.0 +0200
+++ libdnf-0.55.2/debian/patches/series 2022-12-10 13:48:46.0 +0100
@@ -12,3 +12,4 @@
0012-data-workaround-for-hardcoded-absolute-path-data-in-.patch
0013-python-tests-fix-locale-issues.patch
0014-Hardening-add-signature-check-with-rpmcliVerifySigna.patch
+0020_gpmgme-pkg-config.diff
Bug#1025739: Is an autogenerated configure shell script non-editable source (Was: Bug#1025739: hmmer2: missing source for configure)
On 2022-12-09 Andreas Tille wrote: [...] > Thanks to Alexander Sulfrian who pointed out the Git repository > featuring old tags that were obviously taken over from SVN I was proven > wrong with the statement that there is no configure.ac any more. > Unfortunately this is no simple drop-in with modern autoconf tools > and my weak attempt in Git to use this failed.[1] [...] Hello, I have given this a a little bit of time. This seems to work: 1. Copy configure.ac from upstream's 2.3.2h2 branch. 2. Add 'export AUTOHEADER = true' to debian/rules. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1024489: gvm-libs: Loses gpgme integration when rebuilt against gpgme 1.18.0-2
Control: tags -1 patch
On 2022-11-20 Andreas Metzler wrote:
[...]
> the package relies on gpgme-config to detect gpgme. gpgme-config has been
> dropped and replaced by pkg-config pc files. Fix looks straightforward,
> just move over to cmake pkg_check_modules() in util/CMakeLists.txt.
Straightforward patch attached.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Description: Use pkg-config to locate gpgme
Author: Andreas Metzler
Origin: vendor
Bug-Debian: https://bugs.debian.org/1024489
Forwarded: no
Last-Update: 2022-12-08
--- gvm-libs-21.4.4.orig/util/CMakeLists.txt
+++ gvm-libs-21.4.4/util/CMakeLists.txt
@@ -53,28 +53,12 @@ pkg_check_modules (LIBXML2 REQUIRED libx
#for gpgmeutils we need libgpgme
set (GPGME_MIN_VERSION "1.7.0")
message (STATUS "Looking for gpgme...")
-find_library (GPGME gpgme)
-if (NOT GPGME)
- message (SEND_ERROR "The gpgme library is required.")
-else (NOT GPGME)
- execute_process (COMMAND gpgme-config --version
-OUTPUT_VARIABLE GPGME_VERSION
-OUTPUT_STRIP_TRAILING_WHITESPACE)
- message (STATUS "Found gpgme: ${GPGME}, version ${GPGME_VERSION}")
- if (GPGME_VERSION VERSION_LESS GPGME_MIN_VERSION)
-message (SEND_ERROR "The gpgme library >= ${GPGME_MIN_VERSION} is required.")
- else (GPGME_VERSION VERSION_LESS GPGME_MIN_VERSION)
-execute_process (COMMAND gpgme-config --libs
- OUTPUT_VARIABLE GPGME_LDFLAGS
- OUTPUT_STRIP_TRAILING_WHITESPACE)
-execute_process (COMMAND gpgme-config --cflags
- OUTPUT_VARIABLE GPGME_CFLAGS
- OUTPUT_STRIP_TRAILING_WHITESPACE)
-set (CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -D_FILE_OFFSET_BITS=64 -DLARGEFILE_SOURCE=1")
-string(REPLACE "-I" "" GPGME_INCLUDE_DIRS "${GPGME_CFLAGS}")
- endif (GPGME_VERSION VERSION_LESS GPGME_MIN_VERSION)
-endif (NOT GPGME)
+pkg_search_module(GPGME REQUIRED gpgme>=${GPGME_MIN_VERSION})
+if (${GPGME_FOUND})
+message (STATUS "found gpgme ${GPGME_VERSION}")
+set (CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -D_FILE_OFFSET_BITS=64 -DLARGEFILE_SOURCE=1")
+endif (${GPGME_FOUND})
message (STATUS "Looking for libcrypt...")
find_library (CRYPT crypt)
@@ -179,7 +163,7 @@ if (BUILD_SHARED)
set_target_properties (gvm_util_shared PROPERTIES PUBLIC_HEADER "${HEADERS}")
target_link_libraries (gvm_util_shared LINK_PRIVATE ${GLIB_LDFLAGS}
- ${GIO_LDFLAGS} ${GPGME_LDFLAGS} ${ZLIB_LDFLAGS}
+ ${GIO_LDFLAGS} ${GPGME_LIBRARIES} ${ZLIB_LDFLAGS}
${RADIUS_LDFLAGS} ${LIBSSH_LDFLAGS} ${GNUTLS_LDFLAGS}
${GCRYPT_LDFLAGS} ${LDAP_LDFLAGS} ${REDIS_LDFLAGS}
${LIBXML2_LDFLAGS} ${UUID_LDFLAGS}
Bug#1024577: libzypp: diff for NMU version 17.25.7-2.3
Control: tags 1024577 + patch
[Replace XX with correct value]
Hello Mike,
I've prepared an NMU for libzypp (versioned as 17.25.7-2.3) and
uploaded it, non-delayed as LowThresholdNmu.
Kind regards
Andreas
diff -Nru libzypp-17.25.7/debian/changelog libzypp-17.25.7/debian/changelog
--- libzypp-17.25.7/debian/changelog 2022-10-06 22:17:51.0 +0200
+++ libzypp-17.25.7/debian/changelog 2022-12-08 12:07:05.0 +0100
@@ -1,3 +1,11 @@
+libzypp (17.25.7-2.3) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * 1010_gpgme-pkg_search_module.diff: Fix FTBFS against libgpgme-dev >=
+1.18.0-2 by using pkg_search_module(). Closes: #1024577
+
+ -- Andreas Metzler Thu, 08 Dec 2022 12:07:05 +0100
+
libzypp (17.25.7-2.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru libzypp-17.25.7/debian/patches/1010_gpgme-pkg_search_module.diff libzypp-17.25.7/debian/patches/1010_gpgme-pkg_search_module.diff
--- libzypp-17.25.7/debian/patches/1010_gpgme-pkg_search_module.diff 1970-01-01 01:00:00.0 +0100
+++ libzypp-17.25.7/debian/patches/1010_gpgme-pkg_search_module.diff 2022-12-08 12:07:05.0 +0100
@@ -0,0 +1,45 @@
+Description: Use pkg-config to lacte gpgme
+Author: Andreas Metzler
+Bug-Debian: https://bugs.debian.org/1024577
+Origin: vendor
+Last-Update: 2022-12-08
+
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -218,17 +218,14 @@
+ # static case: Assert libsolv.a ist the last one linked
+ SET(LibSolv_LIBRARIES ${LibSolv_LIBRARIES} ${LIBSOLV_LIBRARY})
+ ENDIF()
+ ENDIF( LIBSOLV_SRCDIR AND LIBSOLV_BUILDDIR )
+
+-FIND_PACKAGE(Gpgme REQUIRED)
+-IF ( NOT GPGME_PTHREAD_FOUND )
+- MESSAGE( FATAL_ERROR " gpgme not found" )
+-ELSE()
+- INCLUDE_DIRECTORIES( ${GPGME_INCLUDES} )
+- LINK_DIRECTORIES(${GPGME_LIBRARY_DIR})
+-ENDIF()
++pkg_search_module(GPGME REQUIRED gpgme>=1.8.0)
++MESSAGE(STATUS "found gpgme ${GPGME_VERSION}" )
++INCLUDE_DIRECTORIES( ${GPGME_INCLUDE_DIRS} )
++LINK_DIRECTORIES(${GPGME_LIBRARY_DIRS})
+
+ FIND_PACKAGE(OpenSSL REQUIRED)
+
+ FIND_PACKAGE(Udev)
+ IF ( NOT UDEV_FOUND )
+--- a/zypp/CMakeLists.txt
b/zypp/CMakeLists.txt
+@@ -926,11 +926,11 @@
+ TARGET_LINK_LIBRARIES(${LIBNAME} ${LibSolv_LIBRARIES} )
+ TARGET_LINK_LIBRARIES(${LIBNAME} ${OPENSSL_LIBRARIES} )
+ TARGET_LINK_LIBRARIES(${LIBNAME} ${CRYPTO_LIBRARIES} )
+ TARGET_LINK_LIBRARIES(${LIBNAME} ${SIGNALS_LIBRARY})
+ TARGET_LINK_LIBRARIES(${LIBNAME} ${Boost_THREAD_LIBRARY})
+- TARGET_LINK_LIBRARIES(${LIBNAME} ${GPGME_PTHREAD_LIBRARIES})
++ TARGET_LINK_LIBRARIES(${LIBNAME} ${GPGME_LIBRARIES})
+ target_link_libraries(${LIBNAME} ${SIGCPP_LIBRARIES})
+ target_link_libraries(${LIBNAME} ${LIBGLIB_LIBRARIES})
+ target_link_libraries(${LIBNAME} ${YAML_CPP_LIBRARIES})
+
+ IF (ENABLE_ZSTD_COMPRESSION)
diff -Nru libzypp-17.25.7/debian/patches/series libzypp-17.25.7/debian/patches/series
--- libzypp-17.25.7/debian/patches/series 2022-10-06 22:17:48.0 +0200
+++ libzypp-17.25.7/debian/patches/series 2022-12-08 12:01:08.0 +0100
@@ -3,3 +3,4 @@
1004_fix-fastcgi-includes.patch
0001-Add-missing-includes-for-GCC-11-bsc-1181874.patch
0001-Fix-building-with-GCC-12.x-release.patch
+1010_gpgme-pkg_search_module.diff
signature.asc
Description: PGP signature
Bug#1025420: exim4: ${run} expansion fail
On 2022-12-04 Slavko wrote:
> Package: exim4
> Version: 4.96-9
> Hi,
> yesterday (3.12.2022) discussion on exim's ML shows bug in ${run}
> expansion, which fails if there is another expansion, eg (not very
> useful, but shows problem):
> exim -be '${run{/usr/bin/echo ${quote:aaa}}}'
> Failed: Expansion of "${quote:aaa" from command "/usr/bin/echo
> ${quote:aaa" in ${run} expansion failed: missing } at end of string
> (note missing "}" after quote...)
> It is already fixed, perhaps worth to include it, just in case that new
> version will not be released until next stable, see:
> https://github.com/Exim/exim/commit/44b6e099b76f403a55e77650821f8a69e9d2682e
Thanks for the heads-up. Sadly the fix from master does not apply
directly to 4.96 due to some rework ("Args count reduction in expansions
coding").
cu Andreas
Bug#1024920: libgpg-error: support the noudeb build profile
Control: tags -1 pending On 2022-11-27 Helmut Grohne wrote: > Source: libgpg-error [...] > libgpg-error builds a udeb package. It would be nice to be able to opt > out of building it via the noudeb build profile. I'm attaching a patch > for your convenience. Commited to GIT. (Trivial change in salsa "debian" namespace.) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' signature.asc Description: PGP signature
Bug#1023954: WX assertion failure within the raw importer
On 2022-11-13 Michael Deegan wrote: > Package: hugin > Version: 2021.0.0+dfsg-3 > Severity: normal > The raw file importer triggers an assertion after selecting the raw importer > (dcraw, in my case) to use: > ASSERT INFO: > ./src/common/sizer.cpp(2267): assert "CheckSizerFlags(!((flags) & > (wxALIGN_RIGHT)))" failed in DoInsert(): wxALIGN_RIGHT will be ignored in > this sizer: only vertical alignment flags can be used in horizontal sizers [...] Hello Michael, do you still see this with 2022.0~beta1+dfsg-1? TIA, cu Andreas
Bug#1024943: libgcrypt20: support the noudeb build profile
Control: tags -1 pending On 2022-11-27 Helmut Grohne wrote: > Source: libgcrypt20 > Version: 1.10.1-3 > Severity: minor > Tags: patch > User: helm...@debian.org > Usertags: rebootstrap > libgcrypt20 builds a udeb package. It would be nice to be able to opt > out of building it via the noudeb build profile. I'm attaching a patch > for your convenience. Thank you, applied in GIT. cu Andreas signature.asc Description: PGP signature
Bug#1024699: volume-key: Testsuite error on local rebuild
Control: tags: -1 - moreinfo - unreproducible On 2022-11-24 Michael Biebl wrote: > Control: tags -1 + moreinfo unreproducible > Control: severity -1 normal > Am 23.11.22 um 13:18 schrieb Andreas Metzler: >> Source: volume-key >> Version: 0.3.12-5 >> Severity: serious >> Tags: ftbfs >> Justification: fails to build from source (but built successfully in the >> past) >> Hello, >> volume-key FTBFS on current sid: >> FAIL: packet_roundtrips.sh > Please provide instructions how this issue can be reproduced Good morning Michael, I see this in a straightforward rebuild on up-to-date sid chroot. (sid)ametzler@argenau:/tmp$ rm -rf /tmp/VOL ; mkdir /tmp/VOL ; cd /tmp/VOL ; apt source volume-key ; cd volume-key-0.3.12 [...] (sid)ametzler@argenau:/tmp/VOL/volume-key-0.3.12$ dpkg-buildpackage -uc -us -B [...] make[5]: Entering directory '/tmp/volume-key-0.3.12/tests' FAIL: packet_roundtrips.sh [...] Looking at the buildlog we find: GPGME 20221123T121533 13EBF _gpgme_io_read: enter: fd=8 buffer=0x7fff89fd5cf0 count=4096 GPGME 20221123T121533 13EBF _gpgme_io_read: check: gpg: error running '/usr/bin/gpg-agent': probabl GPGME 20221123T121533 13EBF _gpgme_io_read: check: y not installed GPGME 20221123T121533 13EBF _gpgme_io_read: check: gpg: failed to start agent '/usr/bin/gpg-agent': And indeed manually installing gpg-agent lets the testsuite succeed. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1024417: kgpg FTBFS: Did not find GPGME
On 2022-11-25 Aurélien COUDERC wrote: [...] > I tried applying the patch on top of upstream 22.08.3 and the build still > fails. [0] > Ideas welcome, I won't have the time to analyse the issue any further. Good morning, adding pkg-config to Build-Depends works for me. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1024417: kgpg FTBFS: Did not find GPGME
On 2022-11-23 Daniel Kahn Gillmor wrote: > On Wed 2022-11-23 16:27:43 +0100, Andreas Metzler wrote: >> Unless kgpg maintainers/upstream has a strong opinion against using >> pkg-config the obvious choice would be to drop cmake/FindGpgme.cmake >> and simply use FindPkgConfig. - Attached patch seems to work for me, >> i.e. build including dh_auto_test works. > Thanks for this, Andreas. > I've proposed this change upstream as well at > https://invent.kde.org/utilities/kgpg/-/merge_requests/18 Great, with a little bit of luck we should be able to work out a fix that is acceptable for all/most cmake-cases. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1024576: librepo: FTBFS against libgpgme-dev >= 1.18.0-2
Control: tags -1 patch
On 2022-11-21 Andreas Metzler wrote:
> Source: librepo
> Version: 1.12.1-4
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> User: pkg-gnupg-ma...@lists.alioth.debian.org
> Usertags: gpgme-config-transition^
> The package relies on gpgme-config to detect gpgme. gpgme-config has been
> dropped and replaced by pkg-config pc files.
Straightforward patch attached.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- librepo-1.12.1.orig/CMakeLists.txt
+++ librepo-1.12.1/CMakeLists.txt
@@ -30,8 +30,8 @@ FIND_PACKAGE(PkgConfig)
PKG_CHECK_MODULES(GLIB2 glib-2.0 REQUIRED)
PKG_SEARCH_MODULE(LIBCRYPTO REQUIRED libcrypto openssl)
PKG_CHECK_MODULES(LIBXML2 libxml-2.0 REQUIRED)
+PKG_SEARCH_MODULE(GPGME REQUIRED gpgme)
FIND_PACKAGE(CURL REQUIRED)
-FIND_PACKAGE(Gpgme REQUIRED)
IF (WITH_ZCHUNK)
--- librepo-1.12.1.orig/librepo/CMakeLists.txt
+++ librepo-1.12.1/librepo/CMakeLists.txt
@@ -50,7 +50,7 @@ TARGET_LINK_LIBRARIES(librepo
${LIBXML2_LIBRARIES}
${CURL_LIBRARY}
${LIBCRYPTO_LIBRARIES}
-${GPGME_VANILLA_LIBRARIES}
+${GPGME_LIBRARIES}
${GLIB2_LIBRARIES}
)
IF (WITH_ZCHUNK)
Bug#1024417: kgpg FTBFS: Did not find GPGME
On 2022-11-19 Helmut Grohne wrote:
[...]
> kgpg fails to build from source in unstable. The relevant portion is:
> | -- No usable gpgme flavors found.
[...]
> I think this is due to gpgme having dropped its gpgme-config tool in
> favour of providing a .pc file. I think the change is good in principle,
> but the transition is executed in a bad way. gpgme-config was always
> difficult for cross compilation while .pc just works.
> In any case, this puts kgpg into a difficult spot. I hope you can deal
> with it somehow. I've put the gpgme maintainers in the loop for
> assistance.
Hello,
Unless kgpg maintainers/upstream has a strong opinion against using
pkg-config the obvious choice would be to drop cmake/FindGpgme.cmake
and simply use FindPkgConfig. - Attached patch seems to work for me,
i.e. build including dh_auto_test works.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -21,10 +21,11 @@
include(ECMInstallIcons)
include(FeatureSummary)
include(ECMSetupVersion)
include(CMakeFindDependencyMacro)
include(ECMQtDeclareLoggingCategory)
+include(FindPkgConfig)
find_package(Qt5 ${QT_MIN_VERSION} CONFIG REQUIRED COMPONENTS
Core
DBus
Gui
@@ -56,11 +57,11 @@
AkonadiContact
Contacts
)
# only headers are used
-find_package(Gpgme REQUIRED)
+pkg_search_module(GPGME REQUIRED gpgme)
add_definitions(
#-DQT_DISABLE_DEPRECATED_BEFORE=0x050f00
-DQT_DEPRECATED_WARNINGS_SINCE=0x06
-DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x055200
Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On 2022-11-20 Andreas Metzler wrote: [...] > See > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gpgme-config-transition;users=pkg-gnupg-ma...@lists.alioth.debian.org > for progressing buglist. Hello, I have now run through all packages with b-d on gpgme and filed bugs. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1024699: volume-key: Testsuite error on local rebuild
Source: volume-key Version: 0.3.12-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, volume-key FTBFS on current sid: FAIL: packet_roundtrips.sh cu Andreas buildlog.volume-key_0.3.12-5_amd64.gz Description: application/gzip
Bug#1024698: wget2: Loses gpgme integration when rebuilt against gpgme 1.18.0-2
Source: wget2
Version: 1.99.1-2.2
Severity: important
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition
Hello,
when rebuilt gpgme itegration is lost:
--
checking for gpgme-config... no
checking for GPGME - version >= 0.4.2... no
configure: WARNING: *** GPGME not found.
--
gpgme-config has been dropped and replaced by pkg-config pc files. The
issue should be automatically fixed on autoreconf which pulls in a new
version of AM_PATH_GPGME, however wget2 does not use dh_autoreconf and
autoreconf --verbose -f -i
fails with
-
autoreconf: running: aclocal --force -I m4 ${ACLOCAL_FLAGS}
configure.ac:86: error: AC_CONFIG_MACRO_DIR can only be used once
[...]
-
cu Andreas
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Bug#1017621: seahorse-nautilus: Fails to build with Nautilus 43
On 2022-08-18 Jeremy Bicha wrote: > Source: seahorse-nautilus [...] > The newest release of Nautilus, version 43, has switched to GTK4 and > includes major changes in the extensions API. > seahorse-nautilus will need to be converted to GTK4 and make other changes > for the new version. > Nautilus 43 is available in Debian Experimental. When we upload > nautilus 43 to Debian Unstable, we will need to remove > seahorse-nautilus from Testing unless this bug is fixed, because the > package will no longer build from source. Hello, as of today seahorse-nautilus actually FTBFS. It fails to locate gpgme (gpgme-config was dropped, superseded by pkg-config). Find attached a patch to fix this. Even with this change it later fails with checking for libnautilus-extension >= 2.12.0 glib-2.0 >= 2.10.0... no (There is now a libnautilus-extension-4.pc). cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' --- seahorse-nautilus-3.11.92.orig/configure.ac +++ seahorse-nautilus-3.11.92/configure.ac @@ -87,41 +87,7 @@ if test "$DO_CHECK" = "yes"; then fi fi -ok="no" -min_gpgme_version=1.0.0 -AC_PATH_PROG(GPGME_CONFIG, gpgme-config, "failed") -if test $GPGME_CONFIG != "failed" ; then - AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version) - req_major=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'` - req_minor=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'` - req_micro=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'` - gpgme_config_version=`$GPGME_CONFIG --version` - major=`echo $gpgme_config_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'` - minor=`echo $gpgme_config_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'` - micro=`echo $gpgme_config_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'` - - if test "$major" -eq "$req_major"; then - if test "$minor" -ge "$req_minor"; then - if test "$micro" -ge "$req_micro"; then -ok="yes" - fi - fi - fi -fi - -if test $ok = "yes"; then - GPGME_CFLAGS=`$GPGME_CONFIG --cflags` - GPGME_LIBS=`$GPGME_CONFIG --libs` - AC_MSG_RESULT(yes) -else - AC_MSG_ERROR(GPGME $min_gpgme_version or later needed) -fi +PKG_CHECK_MODULES(GPGME, [gpgme >= 1.0.0]) SEAHORSE_CFLAGS="$SEAHORSE_CFLAGS $GPGME_CFLAGS" SEAHORSE_LIBS="$SEAHORSE_LIBS $GPGME_LIBS" @@ -298,6 +264,6 @@ nautilus-ext/Makefile echo " GnuPG Version: $gnupg_version -GPGME Version: $gpgme_config_version +GPGME Version: $GPGME_VERSION Notification Support:$enable_libnotify "
Bug#1024651: ruby-gpgme: FTBFS against libgpgme-dev >= 1.18.0-2
Source: ruby-gpgme Version: 2.0.20-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition^ The package relies on gpgme-config to detect gpgme. gpgme-config has been dropped and replaced by pkg-config pc files. cu Andreas -- checking for gpgme-config... no gpgme-config not found *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options.
Bug#1024579: mcabber: Loses gpgme integration when rebuilt against gpgme 1.18.0-2
Source: mcabber Version: 1.1.2-2 Severity: important Tags: patch User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition The packages ships an outdated version of gpgme.m4 in macros/gpgme.m4 which cannot handle the transition from gpgme-config to gpgrt-config. Deleting the outdated copy fixes the issue. cu Andreas
Bug#1024578: mandos: FTBFS against libgpgme-dev >= 1.18.0-2
Source: mandos Version: 1.8.15-1.1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition The package relies on gpgme-config to detect gpgme. gpgme-config has been dropped and replaced by pkg-config pc files. cu Andreas --- mandos-1.8.15.orig/Makefile +++ mandos-1.8.15/Makefile @@ -96,8 +96,8 @@ GNUTLS_CFLAGS:=$(shell $(PKG_CONFIG) --c GNUTLS_LIBS:=$(shell $(PKG_CONFIG) --libs gnutls) AVAHI_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I avahi-core) AVAHI_LIBS:=$(shell $(PKG_CONFIG) --libs avahi-core) -GPGME_CFLAGS:=$(shell gpgme-config --cflags; getconf LFS_CFLAGS) -GPGME_LIBS:=$(shell gpgme-config --libs; getconf LFS_LIBS; \ +GPGME_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I gpgme; getconf LFS_CFLAGS) +GPGME_LIBS:=$(shell $(PKG_CONFIG) --libs gpgme; getconf LFS_LIBS; \ getconf LFS_LDFLAGS) LIBNL3_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I libnl-route-3.0) LIBNL3_LIBS:=$(shell $(PKG_CONFIG) --libs libnl-route-3.0)
Bug#1024577: libzypp: FTBFS against libgpgme-dev >= 1.18.0-2
Source: libzypp Version: 17.25.7-2.2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition The package relies on gpgme-config to detect gpgme. gpgme-config has been dropped and replaced by pkg-config pc files. I would suggest following #1024417 where the same cmake module seems to be used. cu Andreas
Bug#1024576: librepo: FTBFS against libgpgme-dev >= 1.18.0-2
Source: librepo Version: 1.12.1-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition^ The package relies on gpgme-config to detect gpgme. gpgme-config has been dropped and replaced by pkg-config pc files. Please also see #1024417 or #1024500 which also use FindGpgme.cmake. cu Andreas
Bug#1022287: poldi: diff for NMU version 0.4.2+git20161115.553060d-1.1
On 2022-11-19 Adrian Bunk wrote: > Control: tags 1022287 + patch > Control: tags 1022287 + pending > Dear maintainer, > I've prepared an NMU for poldi (versioned as 0.4.2+git20161115.553060d-1.1) > and uploaded it to DELAYED/14. Please feel free to tell me if I should > cancel it. [...] > +poldi (0.4.2+git20161115.553060d-1.1) unstable; urgency=low > + > + * Non-maintainer upload. > + * Delete m4/gpg-error.m4 to get the latest version from > +libgpg-error-dev instead. (Closes: #1022287) [...] Please also remove the outdated ksba.m4 to prevent: checking for ksba-config... no checking for KSBA - version >= 1.0.2... no [...] configure: *** *** libksba not found, building without X.509 authentication support. TIA, cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1024500: libdnf: Loses gpgme integration when rebuilt against gpgme 1.18.0-2
Source: libdnf Version: 0.55.2-6 Severity: important User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition The package relies on gpgme-config to detect gpgme. gpgme-config has been dropped and replaced by pkg-config pc files. -- No usable gpgme flavours found. I would suggest following #1024417 where the same cmake module seems to be used. cu Andreas
Bug#1024497: libcryptui: FTBFS against libgpgme-dev >= 1.18.0-2
Source: libcryptui
Version: 3.12.2-6
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition
The package relies on gpgme-config to detect gpgme. gpgme-config has been
dropped and replaced by pkg-config pc files.
cu Andreas
--- libcryptui-3.12.2.orig/configure.ac
+++ libcryptui-3.12.2/configure.ac
@@ -128,51 +128,12 @@ if test "$DO_CHECK" = "yes"; then
fi
fi
-ok="no"
-min_gpgme_version=1.0.0
-AC_PATH_PROG(GPGME_CONFIG, gpgme-config, "failed")
-if test $GPGME_CONFIG != "failed" ; then
- AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version)
- req_major=`echo $min_gpgme_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'`
- req_minor=`echo $min_gpgme_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'`
- req_micro=`echo $min_gpgme_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'`
- gpgme_config_version=`$GPGME_CONFIG --version`
- major=`echo $gpgme_config_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'`
- minor=`echo $gpgme_config_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'`
- micro=`echo $gpgme_config_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'`
-
- if test "$major" -eq "$req_major"; then
- if test "$minor" -ge "$req_minor"; then
- if test "$micro" -ge "$req_micro"; then
-ok="yes"
- fi
- fi
- fi
-fi
-
-if test $ok = "yes"; then
- GPGME_CFLAGS=`$GPGME_CONFIG --cflags`
- GPGME_LIBS=`$GPGME_CONFIG --libs`
- AC_MSG_RESULT(yes)
- have_gpgme="$gpgme_config_version"
-else
- AC_MSG_RESULT(no)
-fi
+PKG_CHECK_MODULES([GPGME], [gpgme >= 1.0.0])
if test -z "$have_gpg"; then
AC_MSG_ERROR([Appropriate version of GnuPG not found. Please install one of versions: $accepted_versions])
fi
-if test -z "$have_gpgme"; then
- AC_MSG_ERROR(GPGME $min_gpgme_version or later needed)
-fi
-
SEAHORSE_CFLAGS="$SEAHORSE_CFLAGS $GPGME_CFLAGS"
SEAHORSE_LIBS="$SEAHORSE_LIBS $GPGME_LIBS"
@@ -359,7 +320,7 @@ dnl
echo "
GnuPG Version: $have_gpg
-GPGME Version: $have_gpgme
+GPGME Version: $GPGME_VERSION
Notification Support: $enable_libnotify
Build introspection data: ${enable_introspection}
"
Bug#1024489: gvm-libs: Loses gpgme integration when rebuilt against gpgme 1.18.0-2
Source: gvm-libs Version: 21.4.4-1 Severity: important User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition the package relies on gpgme-config to detect gpgme. gpgme-config has been dropped and replaced by pkg-config pc files. Fix looks straightforward, just move over to cmake pkg_check_modules() in util/CMakeLists.txt. cu Andreas
Bug#1024488: kaddressbook: Unused build-dependency on libgpgmepp-dev?
Source: kaddressbook Version: 4:22.08.3-1 Severity: minor Hello, afaict kaddressbook's b-d on libgpgmepp-dev is unused: ametzler@argenau:/tmp/BUGS$ grep -ril gpgme kaddressbook-22.08.3/ buildlog.kaddressbook_22.08.3-1_amd64 kaddressbook-22.08.3/debian/control Could you please doublecheck? - TIA! cu Andreas
Bug#1024484: gpa: FTBFS against libgpgme-dev >= 1.18.0-2
Source: gpa Version: 0.10.0-4 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition gpa ships an outdated version of gpgme.m4 which cannot handle the transition from gpgme-config to gpgrt-config. Deleting the outdated copy lets the build succeed. cu Andreas --- gpa-0.10.0.orig/m4/gpgme.m4 +++ /dev/null @@ -1,307 +0,0 @@ -# gpgme.m4 - autoconf macro to detect GPGME. -# Copyright (C) 2002, 2003, 2004 g10 Code GmbH -# -# This file is free software; as a special exception the author gives -# unlimited permission to copy and/or distribute it, with or without -# modifications, as long as this notice is preserved. -# -# This file is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the -# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. - - -AC_DEFUN([_AM_PATH_GPGME_CONFIG], -[ AC_ARG_WITH(gpgme-prefix, -AC_HELP_STRING([--with-gpgme-prefix=PFX], - [prefix where GPGME is installed (optional)]), - gpgme_config_prefix="$withval", gpgme_config_prefix="") - if test "x$gpgme_config_prefix" != x ; then - GPGME_CONFIG="$gpgme_config_prefix/bin/gpgme-config" - fi - AC_PATH_PROG(GPGME_CONFIG, gpgme-config, no) - - if test "$GPGME_CONFIG" != "no" ; then -gpgme_version=`$GPGME_CONFIG --version` - fi - gpgme_version_major=`echo $gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'` - gpgme_version_minor=`echo $gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'` - gpgme_version_micro=`echo $gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'` -]) - -dnl AM_PATH_GPGME([MINIMUM-VERSION, -dnl [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]]) -dnl Test for libgpgme and define GPGME_CFLAGS and GPGME_LIBS. -dnl -AC_DEFUN([AM_PATH_GPGME], -[ AC_REQUIRE([_AM_PATH_GPGME_CONFIG])dnl - tmp=ifelse([$1], ,1:0.4.2,$1) - if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then - req_gpgme_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'` - min_gpgme_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'` - else - req_gpgme_api=0 - min_gpgme_version="$tmp" - fi - - AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version) - ok=no - if test "$GPGME_CONFIG" != "no" ; then -req_major=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'` -req_minor=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'` -req_micro=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'` -if test "$gpgme_version_major" -gt "$req_major"; then -ok=yes -else -if test "$gpgme_version_major" -eq "$req_major"; then -if test "$gpgme_version_minor" -gt "$req_minor"; then - ok=yes -else - if test "$gpgme_version_minor" -eq "$req_minor"; then - if test "$gpgme_version_micro" -ge "$req_micro"; then - ok=yes - fi - fi -fi -fi -fi - fi - if test $ok = yes; then - # If we have a recent GPGME, we should also check that the - # API is compatible. - if test "$req_gpgme_api" -gt 0 ; then -tmp=`$GPGME_CONFIG --api-version 2>/dev/null || echo 0` -if test "$tmp" -gt 0 ; then - if test "$req_gpgme_api" -ne "$tmp" ; then - ok=no - fi -fi - fi - fi - if test $ok = yes; then -GPGME_CFLAGS=`$GPGME_CONFIG --cflags` -GPGME_LIBS=`$GPGME_CONFIG --libs` -AC_MSG_RESULT(yes) -ifelse([$2], , :, [$2]) - else -GPGME_CFLAGS="" -GPGME_LIBS="" -AC_MSG_RESULT(no) -ifelse([$3], , :, [$3]) - fi - AC_SUBST(GPGME_CFLAGS) - AC_SUBST(GPGME_LIBS) -]) - -dnl AM_PATH_GPGME_PTH([MINIMUM-VERSION, -dnl [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]]) -dnl Test for libgpgme and define GPGME_PTH_CFLAGS and GPGME_PTH_LIBS. -dnl -AC_DEFUN([AM_PATH_GPGME_PTH], -[ AC_REQUIRE([_AM_PATH_GPGME_CONFIG])dnl - tmp=ifelse([$1], ,1:0.4.2,$1) - if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then - req_gpgme_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'` - min_gpgme_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'` - else - req_gpgme_api=0 - min_gpgme_version="$tmp" - fi - - AC_MSG_CHECKING(for GPGME Pth - version >= $min_gpgme_version) - ok=no - if test "$GPGME_CONFIG" != "no" ; then -if `$GPGME_CONFIG --thread=pth 2> /dev/null` ; then - req_major=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'` - req_minor=`echo $min_gpgme_version | \ - sed
Bug#1024483: geany-plugins: FTBFS against libgpgme-dev >= 1.18.0-2
Source: geany-plugins
Version: 1.38+dfsg-1.1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition
geany-plugins ships an outdated version of gpgme.m4 which cannot handle
the transition from gpgme-config to gpgrt-config. Deleting the outdated
copy lets the build succeed.
cu Andreas
--- geany-plugins-1.38+dfsg.orig/Makefile.am
+++ geany-plugins-1.38+dfsg/Makefile.am
@@ -1,4 +1,4 @@
-ACLOCAL_AMFLAGS = -I build/cache -I build -I build/bundled -I geanypy/m4 --install
+ACLOCAL_AMFLAGS = -I build/cache -I build -I geanypy/m4 --install
AM_DISTCHECK_CONFIGURE_FLAGS = --with-geany-libdir='$${libdir}'
SUBDIRS = po
--- geany-plugins-1.38+dfsg.orig/build/bundled/gpgme.m4
+++ /dev/null
@@ -1,307 +0,0 @@
-# gpgme.m4 - autoconf macro to detect GPGME.
-# Copyright (C) 2002, 2003, 2004 g10 Code GmbH
-#
-# This file is free software; as a special exception the author gives
-# unlimited permission to copy and/or distribute it, with or without
-# modifications, as long as this notice is preserved.
-#
-# This file is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
-# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-
-
-AC_DEFUN([_AM_PATH_GPGME_CONFIG],
-[ AC_ARG_WITH(gpgme-prefix,
-AC_HELP_STRING([--with-gpgme-prefix=PFX],
- [prefix where GPGME is installed (optional)]),
- gpgme_config_prefix="$withval", gpgme_config_prefix="")
- if test "x$gpgme_config_prefix" != x ; then
- GPGME_CONFIG="$gpgme_config_prefix/bin/gpgme-config"
- fi
- AC_PATH_PROG(GPGME_CONFIG, gpgme-config, no)
-
- if test "$GPGME_CONFIG" != "no" ; then
-gpgme_version=`$GPGME_CONFIG --version`
- fi
- gpgme_version_major=`echo $gpgme_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'`
- gpgme_version_minor=`echo $gpgme_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'`
- gpgme_version_micro=`echo $gpgme_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'`
-])
-
-dnl AM_PATH_GPGME([MINIMUM-VERSION,
-dnl [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]])
-dnl Test for libgpgme and define GPGME_CFLAGS and GPGME_LIBS.
-dnl
-AC_DEFUN([AM_PATH_GPGME],
-[ AC_REQUIRE([_AM_PATH_GPGME_CONFIG])dnl
- tmp=ifelse([$1], ,1:0.4.2,$1)
- if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then
- req_gpgme_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'`
- min_gpgme_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'`
- else
- req_gpgme_api=0
- min_gpgme_version="$tmp"
- fi
-
- AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version)
- ok=no
- if test "$GPGME_CONFIG" != "no" ; then
-req_major=`echo $min_gpgme_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'`
-req_minor=`echo $min_gpgme_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'`
-req_micro=`echo $min_gpgme_version | \
- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'`
-if test "$gpgme_version_major" -gt "$req_major"; then
-ok=yes
-else
-if test "$gpgme_version_major" -eq "$req_major"; then
-if test "$gpgme_version_minor" -gt "$req_minor"; then
- ok=yes
-else
- if test "$gpgme_version_minor" -eq "$req_minor"; then
- if test "$gpgme_version_micro" -ge "$req_micro"; then
- ok=yes
- fi
- fi
-fi
-fi
-fi
- fi
- if test $ok = yes; then
- # If we have a recent GPGME, we should also check that the
- # API is compatible.
- if test "$req_gpgme_api" -gt 0 ; then
-tmp=`$GPGME_CONFIG --api-version 2>/dev/null || echo 0`
-if test "$tmp" -gt 0 ; then
- if test "$req_gpgme_api" -ne "$tmp" ; then
- ok=no
- fi
-fi
- fi
- fi
- if test $ok = yes; then
-GPGME_CFLAGS=`$GPGME_CONFIG --cflags`
-GPGME_LIBS=`$GPGME_CONFIG --libs`
-AC_MSG_RESULT(yes)
-ifelse([$2], , :, [$2])
- else
-GPGME_CFLAGS=""
-GPGME_LIBS=""
-AC_MSG_RESULT(no)
-ifelse([$3], , :, [$3])
- fi
- AC_SUBST(GPGME_CFLAGS)
- AC_SUBST(GPGME_LIBS)
-])
-
-dnl AM_PATH_GPGME_PTH([MINIMUM-VERSION,
-dnl [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]])
-dnl Test for libgpgme and define GPGME_PTH_CFLAGS and GPGME_PTH_LIBS.
-dnl
-AC_DEFUN([AM_PATH_GPGME_PTH],
-[ AC_REQUIRE([_AM_PATH_GPGME_CONFIG])dnl
- tmp=ifelse([$1], ,1:0.4.2,$1)
- if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then
- req_gpgme_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'`
- min_gpgme_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'`
- else
- req_gpgme_api=0
- min_gpgme_version="$tmp"
- fi
Bug#1024481: fwknop: FTBFS against libgpgme-dev >= 1.18.0-2 [--with-gpgme was given, but test for gpgme failed]
Source: fwknop Version: 2.6.10-13 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition fwknop ships an outdated version of gpgme.m4 in m4/ which cannot handle the transition from gpgme-config to gpgrt-config. Deleteing the outdated copy lets the build succeed. cu Andreas --- fwknop-2.6.10.orig/m4/gpgme.m4 +++ /dev/null @@ -1,307 +0,0 @@ -# gpgme.m4 - autoconf macro to detect GPGME. -# Copyright (C) 2002, 2003, 2004 g10 Code GmbH -# -# This file is free software; as a special exception the author gives -# unlimited permission to copy and/or distribute it, with or without -# modifications, as long as this notice is preserved. -# -# This file is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the -# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. - - -AC_DEFUN([_AM_PATH_GPGME_CONFIG], -[ AC_ARG_WITH(gpgme-prefix, -AC_HELP_STRING([--with-gpgme-prefix=PFX], - [prefix where GPGME is installed (optional)]), - gpgme_config_prefix="$withval", gpgme_config_prefix="") - if test "x$gpgme_config_prefix" != x ; then - GPGME_CONFIG="$gpgme_config_prefix/bin/gpgme-config" - fi - AC_PATH_PROG(GPGME_CONFIG, gpgme-config, no) - - if test "$GPGME_CONFIG" != "no" ; then -gpgme_version=`$GPGME_CONFIG --version` - fi - gpgme_version_major=`echo $gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'` - gpgme_version_minor=`echo $gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'` - gpgme_version_micro=`echo $gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'` -]) - -dnl AM_PATH_GPGME([MINIMUM-VERSION, -dnl [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]]) -dnl Test for libgpgme and define GPGME_CFLAGS and GPGME_LIBS. -dnl -AC_DEFUN([AM_PATH_GPGME], -[ AC_REQUIRE([_AM_PATH_GPGME_CONFIG])dnl - tmp=ifelse([$1], ,1:0.4.2,$1) - if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then - req_gpgme_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'` - min_gpgme_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'` - else - req_gpgme_api=0 - min_gpgme_version="$tmp" - fi - - AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version) - ok=no - if test "$GPGME_CONFIG" != "no" ; then -req_major=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'` -req_minor=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'` -req_micro=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'` -if test "$gpgme_version_major" -gt "$req_major"; then -ok=yes -else -if test "$gpgme_version_major" -eq "$req_major"; then -if test "$gpgme_version_minor" -gt "$req_minor"; then - ok=yes -else - if test "$gpgme_version_minor" -eq "$req_minor"; then - if test "$gpgme_version_micro" -ge "$req_micro"; then - ok=yes - fi - fi -fi -fi -fi - fi - if test $ok = yes; then - # If we have a recent GPGME, we should also check that the - # API is compatible. - if test "$req_gpgme_api" -gt 0 ; then -tmp=`$GPGME_CONFIG --api-version 2>/dev/null || echo 0` -if test "$tmp" -gt 0 ; then - if test "$req_gpgme_api" -ne "$tmp" ; then - ok=no - fi -fi - fi - fi - if test $ok = yes; then -GPGME_CFLAGS=`$GPGME_CONFIG --cflags` -GPGME_LIBS=`$GPGME_CONFIG --libs` -AC_MSG_RESULT(yes) -ifelse([$2], , :, [$2]) - else -GPGME_CFLAGS="" -GPGME_LIBS="" -AC_MSG_RESULT(no) -ifelse([$3], , :, [$3]) - fi - AC_SUBST(GPGME_CFLAGS) - AC_SUBST(GPGME_LIBS) -]) - -dnl AM_PATH_GPGME_PTH([MINIMUM-VERSION, -dnl [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]]) -dnl Test for libgpgme and define GPGME_PTH_CFLAGS and GPGME_PTH_LIBS. -dnl -AC_DEFUN([AM_PATH_GPGME_PTH], -[ AC_REQUIRE([_AM_PATH_GPGME_CONFIG])dnl - tmp=ifelse([$1], ,1:0.4.2,$1) - if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then - req_gpgme_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'` - min_gpgme_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'` - else - req_gpgme_api=0 - min_gpgme_version="$tmp" - fi - - AC_MSG_CHECKING(for GPGME Pth - version >= $min_gpgme_version) - ok=no - if test "$GPGME_CONFIG" != "no" ; then -if `$GPGME_CONFIG --thread=pth 2> /dev/null` ; then - req_major=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'` - req_minor=`echo $min_gpgme_version | \ - sed
Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On 2022-11-18 Andreas Metzler wrote: [...] > Quick test: updating gpgme.m4 from gpgme GIT lets mutt 2.2.7-1 build > successfully if mutt's local copy m4/gpgme.m4 is removed. Afaiu aclocal > documentation there is nothing we can do more, the included outdated > gpgme.m4 is preferred. gpgme.m4 is now up to date in sid. See https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gpgme-config-transition;users=pkg-gnupg-ma...@lists.alioth.debian.org for progressing buglist. cu Andreas
Bug#1024478: ecryptfs-utils: FTBFS against libgpgme-dev >= 1.18.0-2 [Cannot locate gpgme]
Package: ecryptfs-utils
Version: 111-5
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition
ecryptfs-utils relies on gpgme-config to detect gpgme. gpgme-config has
been dropped and replaced by pkg-config pc files.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- ecryptfs-utils-111.orig/configure.ac
+++ ecryptfs-utils-111/configure.ac
@@ -135,13 +135,6 @@ AC_ARG_ENABLE(
)
AC_ARG_WITH(
- [gpgme-prefix],
- [AS_HELP_STRING([--with-gpgme-prefix=PATH],[Specify the directory where gpgme install, default /usr])],
- ,
- [with_gpgme_prefix="/usr"]
-)
-
-AC_ARG_WITH(
[pamdir],
[AS_HELP_STRING([--with-pamdir=PATH],[Specify the directory where PAM modules are stored])],
[pamdir="${withval}"],
@@ -315,14 +308,7 @@ if test "${enable_tspi}" = "yes" ; then
fi
if test "${enable_gpg}" = "yes" ; then
- AC_MSG_CHECKING([for gpgme])
- if ! test -x "${with_gpgme_prefix}/bin/gpgme-config"; then
- AC_MSG_ERROR([Cannot locate gpgme])
- else
- AC_MSG_RESULT([found])
- GPGME_CFLAGS="`\"${with_gpgme_prefix}/bin/gpgme-config\" --cflags`"
- GPGME_LIBS="`\"${with_gpgme_prefix}/bin/gpgme-config\" --libs`"
- fi
+ PKG_CHECK_MODULES([GPGME], [gpgme >= 1.0.0])
fi
if test "${enable_pam}" = "yes" ; then
@@ -385,8 +371,6 @@ AC_SUBST([pamlibdir])
AC_SUBST([pkgconfigdir])
AC_SUBST([rootsbindir])
AC_SUBST([ecryptfskeymoddir])
-AC_SUBST([GPGME_CFLAGS])
-AC_SUBST([GPGME_LIBS])
AC_SUBST([CRYPTO_CFLAGS])
AC_SUBST([CRYPTO_LIBS])
AM_CONDITIONAL([BUILD_OPENSSL], [test "${enable_openssl}" = "yes"])
Bug#1023917: cpm: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for gpgme-config... no]
Better patch atttached.
cu Andreas
--- cpm-0.32.orig/configure.in
+++ cpm-0.32/configure.in
@@ -353,29 +353,12 @@ PKG_CHECK_MODULES([LIBXML], [libxml-2.0]
LIBXML_XMLLINT="$exec_prefix/bin/xmllint"
AC_SUBST(LIBXML_XMLLINT)
-AC_PATH_PROG([GPGME_CONFIG], [gpgme-config])
-if test -z "$ac_cv_path_GPGME_CONFIG"; then
- AC_MSG_ERROR([Could not find gpgme anywhere.])
-fi
-
-LIBGPGME_VERSION="`$GPGME_CONFIG --version | cut -d '.' -f 1,2 | sed -e 's/\\.//g'`"
-if test $LIBGPGME_VERSION -lt 10; then
- AC_MSG_ERROR([GPGME must be version 1.0 or higher.])
-fi
-if test $LIBGPGME_VERSION -lt 11; then
- AC_MSG_NOTICE([GpgME version lower than 1.1 found, recipients can't be detected automatically.])
- WRAPPER_NECESSARY=1
-else
- AC_MSG_NOTICE([GpgME version 1.1+ found. Enabling automatic recipient detection.])
+PKG_CHECK_MODULES([LIBGPGME], [gpgme >= 1.1.0],
CFLAGS="${CFLAGS} -DGPGME_HAS_RECIPIENT"
WRAPPER_NECESSARY=0
-fi
+)
AC_SUBST(WRAPPER_NECESSARY)
-LIBGPGME_LIBS="`$GPGME_CONFIG --libs`"
-LIBGPGME_CFLAGS="-D_FILE_OFFSET_BITS=64 `$GPGME_CONFIG --cflags`"
-AC_SUBST(LIBGPGME_LIBS)
-AC_SUBST(LIBGPGME_CFLAGS)
# --
Bug#1024475: basket: Loses gpgme integration when rebuilt against gpgme 1.18.0-2
Package: basket Version: 2.49-1 Severity: important User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition Hello, basket relies on gpgme-config to detect gpgme. gpgme-config has been dropped and replaced by pkg-config pc files. cu Andreas
Bug#1024468: gpgme1.0: diff for NMU version 1.18.0-2.1
Package: gpgme1.0
Version: 1.18.0-2
Severity: normal
Tags: patch
Dear maintainer,
I've prepared an NMU for gpgme1.0 (versioned as 1.18.0-2.1) and
uploaded it to unstable. Please also see
https://salsa.debian.org/debian/gpgme/-/merge_requests/9
kind regards
Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru gpgme1.0-1.18.0/debian/changelog gpgme1.0-1.18.0/debian/changelog
--- gpgme1.0-1.18.0/debian/changelog 2022-11-02 15:54:12.0 +0100
+++ gpgme1.0-1.18.0/debian/changelog 2022-11-20 07:16:46.0 +0100
@@ -1,3 +1,16 @@
+gpgme1.0 (1.18.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Cherrypicked from upstream GIT:
++ 0015-build-Prefer-gpgrt-config-when-available.patch,
+ 0016-gpgme.m4-Include-_AM_PATH_GPGRT_CONFIG-implementatio.patch: Update
+ gpgme.m4 to prefer gpgrt-config even if gpgme-config was available and
+ to find gpgrt-config when AM_PATH_GPG_ERROR was not used.
++ 0017-doc-Update-documentation-for-gpgme.pc-and-pkg-config.patch:
+ Document pkg-config instead of gpgme-config in manual.
+
+ -- Andreas Metzler Sun, 20 Nov 2022 07:16:46 +0100
+
gpgme1.0 (1.18.0-2) unstable; urgency=medium
[ Andreas Metzler ]
diff -Nru gpgme1.0-1.18.0/debian/patches/0015-build-Prefer-gpgrt-config-when-available.patch gpgme1.0-1.18.0/debian/patches/0015-build-Prefer-gpgrt-config-when-available.patch
--- gpgme1.0-1.18.0/debian/patches/0015-build-Prefer-gpgrt-config-when-available.patch 1970-01-01 01:00:00.0 +0100
+++ gpgme1.0-1.18.0/debian/patches/0015-build-Prefer-gpgrt-config-when-available.patch 2022-11-20 06:53:26.0 +0100
@@ -0,0 +1,59 @@
+From 9f55dceca0cf2926d14cb4a70bd0cdc454d89f03 Mon Sep 17 00:00:00 2001
+From: NIIBE Yutaka
+Date: Wed, 2 Nov 2022 10:08:52 +0900
+Subject: [PATCH] build: Prefer gpgrt-config when available.
+
+* src/gpgme.m4: Overriding the decision by --with-gpgme-prefix,
+use gpgrt-config gpgme when gpgrt-config is available.
+
+--
+
+This may offer better migration.
+
+GnuPG-bug-id: 5034
+Signed-off-by: NIIBE Yutaka
+---
+ src/gpgme.m4 | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/gpgme.m4 b/src/gpgme.m4
+index c749a5dd..09a282d0 100644
+--- a/src/gpgme.m4
b/src/gpgme.m4
+@@ -5,15 +5,15 @@
+ # unlimited permission to copy and/or distribute it, with or without
+ # modifications, as long as this notice is preserved.
+ #
+ # This file is distributed in the hope that it will be useful, but
+ # WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
+ # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+ #
+-# Last-changed: 2020-11-20
++# Last-changed: 2022-11-02
+
+
+ AC_DEFUN([_AM_PATH_GPGME_CONFIG],
+ [ AC_ARG_WITH(gpgme-prefix,
+ AS_HELP_STRING([--with-gpgme-prefix=PFX],
+[prefix where GPGME is installed (optional)]),
+ gpgme_config_prefix="$withval", gpgme_config_prefix="")
+@@ -33,15 +33,15 @@ AC_DEFUN([_AM_PATH_GPGME_CONFIG],
+AC_MSG_WARN([Ignoring \$SYSROOT as it is not an absolute path.])
+;;
+esac
+ fi
+ fi
+
+ use_gpgrt_config=""
+- if test x"${GPGME_CONFIG}" = x -a x"$GPGRT_CONFIG" != x -a "$GPGRT_CONFIG" != "no"; then
++ if test x"$GPGRT_CONFIG" != x -a "$GPGRT_CONFIG" != "no"; then
+ if $GPGRT_CONFIG gpgme --exists; then
+ GPGME_CONFIG="$GPGRT_CONFIG gpgme"
+ AC_MSG_NOTICE([Use gpgrt-config as gpgme-config])
+ use_gpgrt_config=yes
+ fi
+ fi
+ if test -z "$use_gpgrt_config"; then
+--
+2.35.1
+
diff -Nru gpgme1.0-1.18.0/debian/patches/0016-gpgme.m4-Include-_AM_PATH_GPGRT_CONFIG-implementatio.patch gpgme1.0-1.18.0/debian/patches/0016-gpgme.m4-Include-_AM_PATH_GPGRT_CONFIG-implementatio.patch
--- gpgme1.0-1.18.0/debian/patches/0016-gpgme.m4-Include-_AM_PATH_GPGRT_CONFIG-implementatio.patch 1970-01-01 01:00:00.0 +0100
+++ gpgme1.0-1.18.0/debian/patches/0016-gpgme.m4-Include-_AM_PATH_GPGRT_CONFIG-implementatio.patch 2022-11-20 06:53:26.0 +0100
@@ -0,0 +1,144 @@
+From abd51848bdc8a5ea5929f9cfb819a408dc53d463 Mon Sep 17 00:00:00 2001
+From: NIIBE Yutaka
+Date: Tue, 15 Nov 2022 13:40:57 +0900
+Subject: [PATCH 1/2] gpgme.m4: Include _AM_PATH_GPGRT_CONFIG implementation.
+
+* src/gpgme.m4 (_AM_PATH_GPGRT_CONFIG): New.
+(_AM_PATH_GPGME_CONFIG): Require _AM_PATH_GPGRT_CONFIG.
+
+--
+
+GnuPG-bug-id: 6273
+Signed-off-by: NIIBE Yutaka
+---
+ src/gpgme.m4 | 101 ---
+ 1 file changed, 95 insertions(+), 6 deletions(-)
+
+diff --git a/src/gpgme.m4 b/src/gpgme.m4
+index 09a282d0..363a84f3 100644
+--- a/src/gpgme.m4
b/src/gpgme.m4
+@@ -1,25 +1,114 @@
+ # gpgme.m4 - autoconf macro to detect GPGME.
+-# Copyright (C) 2002, 2003, 200
Bug#1024368: Problems updating libopenexr25 from version 2.5.4-2 to 2.5.7-1
On 2022-11-18 Сергей Фёдоров wrote: > Package: libopenexr25 > Version: 2.5.4-2 > Severity: normal > X-Debbugs-Cc: serfyod...@yandex.ru > Dear Maintainer, > When trying to update the package "libopenexr25" from version 2.5.4-2 to > 2.5.7-1, > the message is displayed: Depends on: libilmbase25 (>=2.5.7), but 2.5.4-1 > will be installed [...] > $ apt-cache -a show libilmbase25 > Package: libilmbase25 [...] > Version: 2.5.4-1 [...] libilmbase25 2.5.7-2+b1 is available in the Debian archive, https://qa.debian.org/madison.php?package=libilmbase25 please update your system (apt update). cu Andreas ametzler@argenau:~$ apt-cache policy libilmbase25 libilmbase25: Installed: (none) Candidate: 2.5.7-2+b1 Version table: 2.5.7-2+b1 500 500 http://ftp.at.debian.org/debian bookworm/main amd64 Packages
Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On 2022-11-16 Andreas Metzler wrote: [...] > Assuming the changes work as advertised (no tests on my side, I will not > have time till weekend) I think both m4 files should be updated in > Debian without waiting for an upstream release. gpgme.m4 is the > important one, the change for gpg-error.m4 is a performance improvement, > avoiding testing for gpgrt twice when both AM_PATH_GPGME (new version) and > AM_PATH_GPG_ERROR (unpatched) are used. Hello, Quick test: updating gpgme.m4 from gpgme GIT lets mutt 2.2.7-1 build successfully if mutt's local copy m4/gpgme.m4 is removed. Afaiu aclocal documentation there is nothing we can do more, the included outdated gpgme.m4 is preferred. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On 2022-11-16 Daniel Kahn Gillmor wrote: > On Tue 2022-11-15 18:24:11 +0100, Andreas Metzler wrote: [...] > > The main reason was AM_PATH_GPGME's pre-dependency on > > AM_PATH_GPG_ERROR. (This also caused the mutt breakage > > afaict). However Niibe Yutaka has pushed updates for gpg-error.m4 and > > gpgme.m4 yesterday in upstream git which should fix this. > Hm, so in terms of upstream git, gpgme has two updates for src/gpgme.m4, > and libgpg-error has one update to src/gpg-error.m4 that i can see. > Do you think we should pull those changes into both source packages in > debian? or should we wait for (or explicitly encourage) an upstream > release? Hello, Assuming the changes work as advertised (no tests on my side, I will not have time till weekend) I think both m4 files should be updated in Debian without waiting for an upstream release. gpgme.m4 is the important one, the change for gpg-error.m4 is a performance improvement, avoiding testing for gpgrt twice when both AM_PATH_GPGME (new version) and AM_PATH_GPG_ERROR (unpatched) are used. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1023601: Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On 2022-11-15 Daniel Kahn Gillmor wrote: [...] > fwiw, upstream has indicated that gpgrt-config is an "internal" > interface, so this is not something that should be used explicitly by > external dependencies. Hello, that was my impression also when I looked at it since gpgrt-config does not work out of the box but needs to be explicitely told where the pc files can be found. [...] > I've reclassified this bug to severity: important because i think that > we should try to go with the upstream default preferences. In the event > that a significant amount of unrelated debian-internal software is > broken by these change, i'm willing to consider a reversion to the > changes in libgpg-error, but at the moment the only remaining packages > i've seen are: > rust-libgpg-error-sys > rust-libgpgme-sys > mutt [...] I had started trying to rebuild all packages build-depending on gpgme last weekend and out of the first 5 at least every other package failed or lost its gpgme linkage. The main reason was AM_PATH_GPGME's pre-dependency on AM_PATH_GPG_ERROR. (This also caused the mutt breakage afaict). However Niibe Yutaka has pushed updates for gpg-error.m4 and gpgme.m4 yesterday in upstream git which should fix this. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On 2022-11-12 Andreas Metzler wrote: > On 2022-11-11 Vincent Lefevre wrote: > [...] >> file and other configuration options. The options that need to be added >> to the compiler invocation at compile time are output by the ‘--cflags’ >> option to ‘gpgme-config’. The following example shows how it can be >> used at the command line: >> gcc -c foo.c `gpgme-config --cflags` >>Adding the output of ‘gpgme-config --cflags’ to the compiler command > [...] > That is clearly suboptimal. I am also do not fond of the fact that > documentation for AM_PATH_GPGME requiring an earlier invocation of > AM_PATH_GPG_ERROR seems to be missing. I have filed https://dev.gnupg.org/T6273 (AM_PATH_GPG_ERROR predependency) and https://dev.gnupg.org/T6274 (outdated docs). cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On 2022-11-11 Vincent Lefevre wrote: [...] > file and other configuration options. The options that need to be added > to the compiler invocation at compile time are output by the ‘--cflags’ > option to ‘gpgme-config’. The following example shows how it can be > used at the command line: > gcc -c foo.c `gpgme-config --cflags` >Adding the output of ‘gpgme-config --cflags’ to the compiler command [...] That is clearly suboptimal. I am also do not fond of the fact that documentation for AM_PATH_GPGME requiring an earlier invocation of AM_PATH_GPG_ERROR seems to be missing. Since upstream BTS is offline for the weekend I cannot check whether this is a known issue. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1023917: cpm: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for gpgme-config... no]
Package: cpm Version: 0.32-1.4 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) cpm FTBFS against libgpgme-dev without gpgme-config. Find attached a minimal patch using gnupg standard autoconf macros. You could also simply use pkgconf. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' Description: Use standard macro to detect gpgme Author: Andreas Metzler Origin: vendor Forwarded: no Last-Update: 2022-11-12 --- a/configure.in +++ b/configure.in @@ -351,10 +351,16 @@ PKG_CHECK_MODULES([LIBXML], [libxml-2.0]) LIBXML_XMLLINT="$exec_prefix/bin/xmllint" AC_SUBST(LIBXML_XMLLINT) +dnl AM_PATH_GPGME requires AM_PATH_GPG_ERROR for fallback to gpgrt-config +AM_PATH_GPG_ERROR() +AM_PATH_GPGME([1.0.0], + AC_MSG_RESULT([found GPGME]), + AC_MSG_ERROR([GPGME must be version 1.0 or higher.])) + AC_PATH_PROG([GPGME_CONFIG], [gpgme-config]) if test -z "$ac_cv_path_GPGME_CONFIG"; then AC_MSG_ERROR([Could not find gpgme anywhere.]) fi
Bug#1023868: caja-seahorse: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for gpgme-config... failed]
Package: caja-seahorse Version: 1.18.5-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Hello, caja-seahorse FTBFS due to removal of gpgme-config. Since caja-seahorse already requires pkgconfig you can simply use this for gpgme, too. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' diff -Nru caja-seahorse-1.18.5/debian/changelog caja-seahorse-1.18.5/debian/changelog --- caja-seahorse-1.18.5/debian/changelog 2020-08-24 10:00:41.0 +0200 +++ caja-seahorse-1.18.5/debian/changelog 2022-11-11 18:45:09.0 +0100 @@ -1,3 +1,11 @@ +caja-seahorse (1.18.5-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * 1010_gpgme_pkgconfig.diff: Use pkgconfig to locate gpgme instead of +gpgme-config fixing FTBFS with libgpgme-dev >= 1.18.0-2. + + -- Andreas Metzler Fri, 11 Nov 2022 18:45:09 +0100 + caja-seahorse (1.18.5-1) unstable; urgency=medium [ Simon Quigley ] diff -Nru caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff --- caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff 1970-01-01 01:00:00.0 +0100 +++ caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff 2022-11-11 18:45:09.0 +0100 @@ -0,0 +1,54 @@ +Description: Use pkgconfig to locate gpgme instead of gpgme-config. +Author: Andreas Metzler +Origin: vendor +Last-Update: 2022-11-11 + +--- a/configure.ac b/configure.ac +@@ -85,45 +85,11 @@ + else + AC_MSG_ERROR([Appropriate version of GnuPG not found. Please install one of versions: $accepted_versions]) + fi + fi + +-ok="no" +-min_gpgme_version=1.0.0 +-AC_PATH_PROG(GPGME_CONFIG, gpgme-config, "failed") +-if test $GPGME_CONFIG != "failed" ; then +- AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version) +- req_major=`echo $min_gpgme_version | \ +- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'` +- req_minor=`echo $min_gpgme_version | \ +- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'` +- req_micro=`echo $min_gpgme_version | \ +- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'` +- gpgme_config_version=`$GPGME_CONFIG --version` +- major=`echo $gpgme_config_version | \ +- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'` +- minor=`echo $gpgme_config_version | \ +- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'` +- micro=`echo $gpgme_config_version | \ +- sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'` +- +- if test "$major" -eq "$req_major"; then +- if test "$minor" -ge "$req_minor"; then +- if test "$micro" -ge "$req_micro"; then +-ok="yes" +- fi +- fi +- fi +-fi +- +-if test $ok = "yes"; then +- GPGME_CFLAGS=`$GPGME_CONFIG --cflags` +- GPGME_LIBS=`$GPGME_CONFIG --libs` +- AC_MSG_RESULT(yes) +-else +- AC_MSG_ERROR(GPGME $min_gpgme_version or later needed) +-fi ++PKG_CHECK_MODULES([GPGME], [gpgme >= 1.0.0]) + + SEAHORSE_CFLAGS="$SEAHORSE_CFLAGS $GPGME_CFLAGS" + SEAHORSE_LIBS="$SEAHORSE_LIBS $GPGME_LIBS" + + # - diff -Nru caja-seahorse-1.18.5/debian/patches/series caja-seahorse-1.18.5/debian/patches/series --- caja-seahorse-1.18.5/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ caja-seahorse-1.18.5/debian/patches/series 2022-11-11 18:43:29.0 +0100 @@ -0,0 +1 @@ +1010_gpgme_pkgconfig.diff
Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On 2022-11-08 Vincent Lefevre wrote: > On 2022-11-07 13:36:30 +0100, Vincent Lefevre wrote: > > The removal of gpgme-config due to > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348 > > > > breaks the build of software relying on it, such as Mutt: [...] > Actually gpgrt-config can be used instead of gpgme-config. But > this requires changes in existing code, possibly non trivial, > as now done for Mutt: > https://gitlab.com/muttmua/mutt/-/issues/430 > (not yet in Debian). > So before gpgme-config gets removed (which is a *recent* upstream > change), you should make sure that existing code based on it has > been updated. Hello Vincent, Disclaimer: I am not in uploaders of gpg packaging but follow the list. We were aware that some breakage was to be expected (a little bit late, though), and will provide help/assistance (quoting Daniel 1023601: "this might cause knock-on effects for projects that themselves think they should be dependent on gpgme-config, but i'll try to sort those through as well.") I do not think the bug severity is correct. It does not break any binary packages, i.e. it fits "a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone." One might argue that the combination of this gpgme version with unbuildable packages is not releaseable and up with serious. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1020640: libglew2.2: Glew built without, wxwidgets with EGL support
Control: block 1023279 by 1020640 On 2022-10-10 Andreas Metzler wrote: > On 2022-10-03 Alastair McKinstry wrote: > > As maintainer would be open to changing Glew to EGL support, but need to > > understand better the consequences. [...] Mandriva also enables glew egl but pulls a patchset from glew GIT head https://github.com/OpenMandrivaAssociation/glew/tree/master and indeed if I build glew GIT head (egl build, i.e. SYSTEM=linux-egl) and run hugin against it it just works and does not crash. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1023279: Segfault on startup; stack overflow involving libwx
On 2022-11-01 Michael Deegan wrote: > Package: hugin > Version: 2021.0.0+dfsg-3 > Severity: important > Console output: [...] > ERROR: 22:42:22.231532 (./src/hugin1/hugin/GLViewer.cpp:133) > SetUpContext(): Error initialising GLEW: Unknown error. > Segmentation fault > I'm wondering if it's the result of a recent libc upgrade, but I'm not about > to attempt a downgrade to verify. :P I did try running Hugin in a libvirt > VM, but I think there it's being fussy about the virtual environment > (despite having working direct-rendering opengl). [...] It is WX related, problably missing EGL support in glew. It worked my in own tests. I realize now that was because I have this setting in ~/.config/hugin.conf: [GLPreviewFrame] [...] isShown=0 (i.e. The OpenGL Preview window does not autoopen). I then need two klicks to actually open it (the first try fails) but apart from that hugin works. Does this workaround also work at your system? cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1023369: ITP: s2n-tls -- C99 implementation of the TLS/SSL protocols
On 2022-11-02 Noah Meyerhans wrote: > * Package name: s2n-tls [...] > s2n-tls implements SSLv3, TLS1.0, TLS1.1, and TLS1.2. For encryption, [...] Hello, I was wondering whether we should still add new TLS implementations to Debian that did not support TLS1.3. However README.md since 1.3.2 says "s2n-tls implements SSLv3, TLS1.0, TLS1.1, TLS1.2, and TLS1.3." cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1022289: libassuan: FTBFS: configure: error: libgpg-error was not found
On 2022-10-23 Andreas Metzler wrote: [...] > Caused by new gpg-error dropping gpg-error-config, this works for me: > --- libassuan-2.5.5/debian/rules2022-04-30 17:47:12.0 +0200 > +++ patched/libassuan-2.5.5.patched/debian/rules2022-10-23 > 18:23:40.505849321 +0200 > @@ -27,7 +27,6 @@ > for cpu in i686 x86_64; do \ > mkdir -p build-$$cpu-w64-mingw32 && \ > cd build-$$cpu-w64-mingw32 && $(WIN_FLAGS) ../configure \ > - --with-libgpg-error-prefix=/usr/$$cpu-w64-mingw32 \ Hello, Commited to GIT, please give me a heads up if you want me to make either a NMU or add myself to Uploaders and make a regular upload. (Although this is a serious bugreport I do not think it is yet so urgent to require a upload without maintainer feedback. - Might change, e.g if libassuan blocked a transition.) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' signature.asc Description: PGP signature
Bug#1023261: bullseye-pu: package libtasn1-6/4.16.0-2+deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: libtasn...@packages.debian.org, t...@security.debian.org Hello, I would like to fix CVE-2021-46848 in bullseye. This was fixed in sid/testing by new upstream 4.19.0. I already had some correspondence with debian-security, no DSA is planned. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' diff -Nru libtasn1-6-4.16.0/debian/changelog libtasn1-6-4.16.0/debian/changelog --- libtasn1-6-4.16.0/debian/changelog 2020-02-15 17:38:59.0 +0100 +++ libtasn1-6-4.16.0/debian/changelog 2022-11-01 11:57:42.0 +0100 @@ -1,3 +1,10 @@ +libtasn1-6 (4.16.0-2+deb11u1) bullseye; urgency=medium + + * Fix ETYPE_OK out of bounds read. CVE-2021-46848 +10_Fix-ETYPE_OK-off-by-one-array-size-check.-Closes-32.patch + + -- Andreas Metzler Tue, 01 Nov 2022 11:57:42 +0100 + libtasn1-6 (4.16.0-2) unstable; urgency=low * Upload to unstable. diff -Nru libtasn1-6-4.16.0/debian/patches/10_Fix-ETYPE_OK-off-by-one-array-size-check.-Closes-32.patch libtasn1-6-4.16.0/debian/patches/10_Fix-ETYPE_OK-off-by-one-array-size-check.-Closes-32.patch --- libtasn1-6-4.16.0/debian/patches/10_Fix-ETYPE_OK-off-by-one-array-size-check.-Closes-32.patch 1970-01-01 01:00:00.0 +0100 +++ libtasn1-6-4.16.0/debian/patches/10_Fix-ETYPE_OK-off-by-one-array-size-check.-Closes-32.patch 2022-10-30 13:02:08.0 +0100 @@ -0,0 +1,29 @@ +From 44a700d2051a666235748970c2df047ff207aeb5 Mon Sep 17 00:00:00 2001 +From: Simon Josefsson +Date: Wed, 17 Aug 2022 12:25:06 +0200 +Subject: [PATCH] Fix ETYPE_OK off by one array size check. Closes: #32. + +Reported by David Trabish in +<https://gitlab.com/gnutls/libtasn1/-/issues/32>. + +Signed-off-by: Simon Josefsson +--- + NEWS | 1 + + lib/int.h | 2 +- + 2 files changed, 2 insertions(+), 1 deletion(-) + +--- a/lib/int.h b/lib/int.h +@@ -95,11 +95,11 @@ + case ASN1_ETYPE_SET_OF + + #define ETYPE_TAG(etype) (_asn1_tags[etype].tag) + #define ETYPE_CLASS(etype) (_asn1_tags[etype].class) + #define ETYPE_OK(etype) (((etype) != ASN1_ETYPE_INVALID && \ +- (etype) <= _asn1_tags_size && \ ++ (etype) < _asn1_tags_size && \ + _asn1_tags[(etype)].desc != NULL)?1:0) + + #define ETYPE_IS_STRING(etype) ((etype == ASN1_ETYPE_GENERALSTRING || \ + etype == ASN1_ETYPE_NUMERIC_STRING || etype == ASN1_ETYPE_IA5_STRING || \ + etype == ASN1_ETYPE_TELETEX_STRING || etype == ASN1_ETYPE_PRINTABLE_STRING || \ diff -Nru libtasn1-6-4.16.0/debian/patches/series libtasn1-6-4.16.0/debian/patches/series --- libtasn1-6-4.16.0/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ libtasn1-6-4.16.0/debian/patches/series 2022-11-01 11:57:42.0 +0100 @@ -0,0 +1 @@ +10_Fix-ETYPE_OK-off-by-one-array-size-check.-Closes-32.patch signature.asc Description: PGP signature
Bug#1022348: gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.
On 2022-10-26 Andreas Metzler wrote: [...] > Which has been promptly fixed. Find attached debdiffs for a proposed > upload. - I can also massage this into a mergew-request or push > directly to https://salsa.debian.org/debian/gpgme Just give me a > heads-up. [...] https://salsa.debian.org/debian/gpgme/-/merge_requests/7 (Sending now since I will not have time tomorrow and on Friday.) cu Andreas
Bug#1022348: gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.
Control: tags -1 patch Control: tags -1 fixed-upstream On 2022-10-25 Andreas Metzler wrote: > Control: forwarded -1 https://dev.gnupg.org/T6204 > On 2022-10-23 Lucas Nussbaum wrote: > > Source: gpgme1.0 > > Version: 1.18.0-1 > [...] > > > Could not find gpg-error-config. Please install the libgpg-error > > > development package. > > > make[4]: *** [Makefile:760: all-local] Error 1 > [...] > There is a patch in upstream GIT ae9258fbf3b9d434495ef11fc184a91fe7c4ca57 but > it breaks when @GPG_ERROR_CFLAGS@ expands to nothing which happens on > Debian. Which has been promptly fixed. Find attached debdiffs for a proposed upload. - I can also massage this into a mergew-request or push directly to https://salsa.debian.org/debian/gpgme Just give me a heads-up. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' diff -Nru gpgme1.0-1.18.0/debian/changelog gpgme1.0-1.18.0/debian/changelog --- gpgme1.0-1.18.0/debian/changelog 2022-09-29 02:31:10.0 +0200 +++ gpgme1.0-1.18.0/debian/changelog 2022-10-26 06:56:43.0 +0200 @@ -1,3 +1,16 @@ +gpgme1.0 (1.18.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add 0010-build-python-Don-t-use-gpg-error-config-gpgme-config.patch +and 0013-python-Fix-configure-generating-setup.py.patch from upstream +GIT master to fix FTBFS after removal of gpg-error-config. +Closes: #1022348 + * Without gpg-error-config gpgme-config is not installed by the upstream +build system anymore. Adapt libgpgme-dev.install, drop related lintian +override and Debian specific manpage. + + -- Andreas Metzler Wed, 26 Oct 2022 06:56:43 +0200 + gpgme1.0 (1.18.0-1) unstable; urgency=medium * new upstream version diff -Nru gpgme1.0-1.18.0/debian/gpgme-config.1 gpgme1.0-1.18.0/debian/gpgme-config.1 --- gpgme1.0-1.18.0/debian/gpgme-config.1 2022-09-06 20:52:33.0 +0200 +++ gpgme1.0-1.18.0/debian/gpgme-config.1 1970-01-01 01:00:00.0 +0100 @@ -1,94 +0,0 @@ -.TH "GPGME" "1" "08 July 2012" "gpgme" "User commands" - -.SH NAME -gpgme\-config \- script to get information about the installed version of GPGME - -.SH SYNOPSIS -.B gpgme\-config -.RB [ \-\-api\-version ] -.RB [ \-\-cflags ] -.RB [ \-\-exec\-prefix ] -.RB [ \-\-get\-gpg ] -.RB [ \-\-get\-gpgsm ] -.RB [ \-\-host ] -.RB [ \-\-libs ] -.RB [ \-\-prefix ] -.RB [ \-\-thread=pthread ] -.RB [ \-\-version ] - -.SH DESCRIPTION -.PP -\fBgpgme\-config\fP is a tool that is used to configure to determine -the compiler and linker flags that should be used to compile -and link programs that use \fIGPGME\fP. It is also used internally -to the .m4 macros for GNU autoconf that are included with \fIGPGME\fP. - -.SH OPTIONS -.PP -\fBgpgme\-config\fP accepts the following options: -.TP -.B \-\-api\-version -Print the currently installed API version of \fIGPGME\fP to standard output. -.TP -.B \-\-cflags -Print the compiler flags that are necessary to compile a \fIGPGME\fP program. -.TP -.B \-\-exec\-prefix -Print the exec prefix that was used to configure the \fIGPGME\fP build. -.TP -.B \-\-get\-gpg -Print the path to the -.BR gpg (1) -binary used to configure the \fIGPGME\fP build. -.TP -.B \-\-get\-gpgsm -Print the path to the -.BR gpgsm (1) -binary used to configure the \fIGPGME\fP build. -.TP -.B \-\-host -Print host information. -.TP -.B \-\-libs -Print the linker flags that are necessary to link a \fIGPGME\fP program. -.TP -.B \-\-prefix -Print the prefix that was used to configure the \fIGPGME\fP build. -.TP -.B \-\-thread=pthread -Switch for the -.B \-\-cflags -and -.B \-\-libs -options for the thread-enabled \fIGPGME\fP version. -.TP -.B \-\-version -Print the currently installed version of \fIGPGME\fP to standard output. - -.SH AUTHORS -.PP -.PP -The -.I GPGME -library is written by many contributors, including Werner Koch, Marcus -Brinkmann, Andre Heinecke, Justus Winter, and Karl-Heinz Zimmer. -.PP -This manual page page was written by \fBJose Carlos Garcia Sogo\fR -\&<\@debian.org\&> and \fBDaniel Leidert\fR <\@wgdd.de\&> -for the Debian distribution (but may be used by others). - -.SH BUGS -.PP -Please report bugs to <https://bugs.gnupg.org>. - -.SH COPYRIGHT -\fBgpgme\-tool\fP is Copyright \(co 2015-2016 g10 Code GmbH License -GPLv2+: GNU GPL version 2 or later <https://www.gnu.org/licenses/> -.PP -This is free software: you are free to change and redistribute it. -There is NO WARRANTY, to the extent permitted by law. - -.SH "SEE ALSO" -.BR gpgme\-tool (1), -.BR /usr/include/gpgme.h , -.B info gpgme diff -Nru gpgme1.0-1.18.0/debian/libgpgme-dev.install gpgme1.0-1.18.0/debian/libgpgme-dev.install --- gpgme1.0-1.18.0/debian/libgpgme-dev.install 2022-09-06 20:52:33.0 +0200 +++ gpgme1.0-1.18.0/debian/libgpgme-dev.install 2022-1
Bug#1022348: gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.
Control: forwarded -1 https://dev.gnupg.org/T6204 On 2022-10-23 Lucas Nussbaum wrote: > Source: gpgme1.0 > Version: 1.18.0-1 [...] > > Could not find gpg-error-config. Please install the libgpg-error > > development package. > > make[4]: *** [Makefile:760: all-local] Error 1 [...] There is a patch in upstream GIT ae9258fbf3b9d434495ef11fc184a91fe7c4ca57 but it breaks when @GPG_ERROR_CFLAGS@ expands to nothing which happens on Debian. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1022289: libassuan: FTBFS: configure: error: libgpg-error was not found
On 2022-10-23 Lucas Nussbaum wrote: > Source: libassuan > Version: 2.5.5-4 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221023 ftbfs-bookworm > Hi, > During a rebuild of all packages in sid, your package failed to build > on amd64. > Relevant part (hopefully): > > ../configure: line 15745: /usr/i686-w64-mingw32/bin/gpg-error-config: No > > such file or directory [...] Hello, Caused by new gpg-error dropping gpg-error-config, this works for me: --- libassuan-2.5.5/debian/rules2022-04-30 17:47:12.0 +0200 +++ patched/libassuan-2.5.5.patched/debian/rules2022-10-23 18:23:40.505849321 +0200 @@ -27,7 +27,6 @@ for cpu in i686 x86_64; do \ mkdir -p build-$$cpu-w64-mingw32 && \ cd build-$$cpu-w64-mingw32 && $(WIN_FLAGS) ../configure \ - --with-libgpg-error-prefix=/usr/$$cpu-w64-mingw32 \ --prefix=/usr/$$cpu-w64-mingw32 \ --enable-static \ --host $$cpu-w64-mingw32 && \ and a successful build with gpg-error 1.46 and a patched build with 1.47 look almost identical except for configure messages changing: -checking for gpg-error-config... /usr/x86_64-w64-mingw32/bin/gpg-error-config +checking for gpg-error-config... no checking for gpgrt-config... /usr/bin/gpgrt-config configure: Use gpgrt-config with /usr/x86_64-w64-mingw32/lib as gpg-error-config -checking for GPG Error - version >= 1.17... yes (1.45) +checking for GPG Error - version >= 1.17... yes (1.46) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1021773: libconfig-model-dpkg-perl: tweak example in docs for fix.(scanned.)copyright does not work
On 2022-10-22 Dominique Dumont wrote: > On Saturday, 22 October 2022 12:09:30 CEST you wrote: > > Thank you. This does not throw an error, but does not work as expected > > either: > > (sid)ametzler@argenau:/tmp/GUILE-GNUTLS/guile-gnutls-3.7.9$ cat > > debian/fix.scanned.copyright ! Files:"*" Copyright=~"s/, Free Software$/, > > Free Software Foundation, Inc./" > > (sid)ametzler@argenau:/tmp/GUILE-GNUTLS/guile-gnutls-3.7.9$ > > > debian/copyright && cme update dpkg-copyright > /dev/null 2>&1 > > (sid)ametzler@argenau:/tmp/GUILE-GNUTLS/guile-gnutls-3.7.9$ grep ', Free > > Software$' debian/copyright Copyright: 2007-2012, 2014-2016, 2019, 2021, > > 2022, Free Software > > Copyright: 2004, 2005, 2007-2009, 2011-2015, Free Software > Hmm, Looking at guile-gnutls copyright file [1], I see that this entry is > correct: > Files: * > Copyright: 1985, 1986, 1988, 1990-2021, Free Software Foundation, Inc. > License: GPL-3+ > whereas the following entry is not: > Files: guile/modules/gnutls.in > Copyright: 2007-2012, 2014-2016, 2019, 2021, 2022, Free Software > License: LGPL-2.1+ > So, I assume you want to apply the instruction specified in > fix.scanned.copyright to change all copyright entries. > Which is not the case because > "! Files:"*"Copyright=~"s/, Free Software$/, Free Software Foundation, Inc./" > applies *only* on: > Files: * [ Way to do it snipped] I see. :-) Thank you very much for the handholding. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1021773: libconfig-model-dpkg-perl: tweak example in docs for fix.(scanned.)copyright does not work
On 2022-10-19 Dominique Dumont wrote: [...] > The following should work with current and future version of > Config::Model::Loader > ! Files:"*" Copyright=~"s/, Free Software$/, Free Software Foundation, Inc./" Thank you. This does not throw an error, but does not work as expected either: (sid)ametzler@argenau:/tmp/GUILE-GNUTLS/guile-gnutls-3.7.9$ cat debian/fix.scanned.copyright ! Files:"*" Copyright=~"s/, Free Software$/, Free Software Foundation, Inc./" (sid)ametzler@argenau:/tmp/GUILE-GNUTLS/guile-gnutls-3.7.9$ > debian/copyright && cme update dpkg-copyright > /dev/null 2>&1 (sid)ametzler@argenau:/tmp/GUILE-GNUTLS/guile-gnutls-3.7.9$ grep ', Free Software$' debian/copyright Copyright: 2007-2012, 2014-2016, 2019, 2021, 2022, Free Software Copyright: 2004, 2005, 2007-2009, 2011-2015, Free Software cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1022087: jellyfish: FTBFS with pkgconf
Control: reassign -1 pkgconf Control: found -1 1.8.0-6 Control: close -1 1.8.0-9 On 2022-10-22 Andreas Metzler wrote: > On 2022-10-21 Andreas Metzler wrote: > [...] > > Indeed applying the upstream patch fixes the testcase Nilesh provided. > > I have not tried rebuilding jellyfish with patched pkgconf. > Strangely the fix does not work in the installed version: Nevermind. User-error, still had old libpkgconf3. jellyfish builds successfully with the new pkgconf upload in experimental. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1022087: jellyfish: FTBFS with pkgconf
X-Debbugs-Cc: pkgc...@packages.debian.org On 2022-10-21 Andreas Metzler wrote: [...] > Indeed applying the upstream patch fixes the testcase Nilesh provided. > I have not tried rebuilding jellyfish with patched pkgconf. Strangely the fix does not work in the installed version: (sid)ametzler@argenau:/dev/shm/JEL/pkgconf-1.8.0$ ln -s pkgconf pkg-config (sid)ametzler@argenau:/dev/shm/JEL/pkgconf-1.8.0$ PKG_CONFIG_PATH=/tmp/ PKG_CONFIG_SYSROOT_DIR=debian/tmp/ ./pkg-config --cflags jellyfish-2.0 -Idebian/tmp//usr/include/jellyfish-2.3.0 (sid)ametzler@argenau:/dev/shm/JEL/pkgconf-1.8.0$ PKG_CONFIG_PATH=/tmp/ PKG_CONFIG_SYSROOT_DIR=debian/tmp/ pkg-config --cflags jellyfish-2.0 -I/usr/include/jellyfish-2.3.0 (sid)ametzler@argenau:/dev/shm/JEL/pkgconf-1.8.0$ pkg-config --version 1.8.0 (sid)ametzler@argenau:/dev/shm/JEL/pkgconf-1.8.0$ ./pkg-config --version 1.8.0 (sid)ametzler@argenau:/dev/shm/JEL/pkgconf-1.8.0$ dpkg -s pkgconf | grep ^Versio n Version: 1.8.0-9 cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1022087: jellyfish: FTBFS with pkgconf
On 2022-10-21 Andreas Metzler wrote: > On 2022-10-20 Nilesh Patra wrote: >> On Wed, 19 Oct 2022 21:11:12 +0100 Andrej Shadura >> wrote: >> > Source: jellyfish > [] >> I took a look at this one, and this seems to FTBFS with pkgconf >> because pkgconf does not seem to honor atleast PKG_CONFIG_SYSROOT_DIR >> which is set in d/rules for this package[1] > [...] >> with old pkg-config: >> $ PKG_CONFIG_PATH=. PKG_CONFIG_SYSROOT_DIR=debian/tmp/ pkg-config --cflags >> jellyfish-2.0 >> -Idebian/tmp//usr/include/jellyfish-2.3.0 >> with pkgconf: >> $ PKG_CONFIG_PATH=. PKG_CONFIG_SYSROOT_DIR=debian/tmp/ pkg-config --cflags >> jellyfish-2.0 >> -I/usr/include/jellyfish-2.3.0 > [...] > Hello, > Looks like this could be https://github.com/pkgconf/pkgconf/issues/267 > which was fixed in June > https://github.com/pkgconf/pkgconf/commit/a61193c7236f5b240585c4f8eef6f452f1d9a7ee > but has not hit a release yet. Indeed applying the upstream patch fixes the testcase Nilesh provided. I have not tried rebuilding jellyfish with patched pkgconf. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1022087: jellyfish: FTBFS with pkgconf
On 2022-10-20 Nilesh Patra wrote: > On Wed, 19 Oct 2022 21:11:12 +0100 Andrej Shadura wrote: > > Source: jellyfish [] > I took a look at this one, and this seems to FTBFS with pkgconf > because pkgconf does not seem to honor atleast PKG_CONFIG_SYSROOT_DIR > which is set in d/rules for this package[1] [...] > with old pkg-config: > $ PKG_CONFIG_PATH=. PKG_CONFIG_SYSROOT_DIR=debian/tmp/ pkg-config --cflags > jellyfish-2.0 > -Idebian/tmp//usr/include/jellyfish-2.3.0 > with pkgconf: > $ PKG_CONFIG_PATH=. PKG_CONFIG_SYSROOT_DIR=debian/tmp/ pkg-config --cflags > jellyfish-2.0 > -I/usr/include/jellyfish-2.3.0 [...] Hello, Looks like this could be https://github.com/pkgconf/pkgconf/issues/267 which was fixed in June https://github.com/pkgconf/pkgconf/commit/a61193c7236f5b240585c4f8eef6f452f1d9a7ee but has not hit a release yet. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1021714: lists.debian.org: Request for new mailing list: collab-maint (was: Evolving away from source package realms)
On 2022-10-13 Santiago Ruano Rincón wrote: > Package: lists.debian.org > Severity: wishlist > Dear list masters and fellow Debian peers, > I hereby would like to propose to create a mailing list for > collaborative maintenance. > Name: debian-collab-maint > Rationale: > El 13/10/22 a las 07:02, Tobias Frost escribió: [...] > Other than the salsa Debian group, I think it would be useful to have a > mailing list to share the responsibility of packages, and at the same > time, reduce the personal "ownership" of them. Packages with Maintainer: [...] Hello, I am not sure this is the right way. * It is already possible to avoid personal e-mail adresses as maintainer using team+...@tracker.debian.org * Scalability: If this was used for many packages the mailing would just be too noisy. Take a look at e.g. debian-qa-packages@ldo, which is imho unreadable. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1021773: libconfig-model-dpkg-perl: tweak example in docs for fix.(scanned.)copyright does not work
On 2022-10-15 Dominique Dumont wrote: > On Friday, 14 October 2022 15:07:56 CEST you wrote: >> Note: loading debian/fix.scanned.copyright fixes from copyright fix files >> Configuration item 'Dpkg::Copyright' has a user error: >> Error while applying fix.scanned.copyright file: >> Configuration item 'Files:"'*'" Copyright' has a wrong value: >> Undefined mandatory value. > This can happen if the s/\s*".*// results in a blank copyright. > What is the content of the copyright file before running "cme update" ? Hello, I actually tried to do something else, got an error (the same one) and then feel back to the example provided to find whether there was some fundamental breakage. I do not think the diagnosis is correct though, I have no »"« in the Copyright lines, so the pattern simply is a noop and should not throw an error, shouldn't it? ametzler@argenau:~$ grep ^Copy GIT/writing/guile-gnutls/debian/copyright | grep \" ametzler@argenau:~$ Anyway what I really tried to do was working around #1021757 and transform Copyright: 2007-2012, 2014-2016, 2019, 2021, 2022, Free Software to Copyright: 2007-2012, 2014-2016, 2019, 2021, 2022, Free Software, Inc. with ! Files:'*' Copyright=~s/, Free Software$/, Free Software Foundation, Inc./ (This is https://salsa.debian.org/gnutls-team/guile-gnutls/ ) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1021773: libconfig-model-dpkg-perl: tweak example in docs for fix.(scanned.)copyright does not work
Package: libconfig-model-dpkg-perl Version: 2.164 Severity: normal The docs for Config::Model::Dpkg::Copyright list dthis example for tweaking: ! Files:'*' Copyright=~s/\s*".*// Pasting this example into debian/fix.scanned.copyright makes cme update dpkg-copyright fail with: Note: loading debian/fix.scanned.copyright fixes from copyright fix files Configuration item 'Dpkg::Copyright' has a user error: Error while applying fix.scanned.copyright file: Configuration item 'Files:"'*'" Copyright' has a wrong value: Undefined mandatory value. cu Andreas
Bug#1021772: libconfig-model-dpkg-perl: docs refer to debian/fix.copyright but fix.scanned.copyright is used
Package: libconfig-model-dpkg-perl Version: 2.164 Severity: normal Hello, the docs refer to "debian/fix.copyright" while the filemname used is fix.scanned.copyright. cu Andreas
Bug#1021757: licensecheck: Handle wrapped copyright statements
Package: licensecheck Version: 3.3.0-1 Severity: normal Hello, licensecheck does seem to handle wrapped copyright statements: (sid)ametzler@argenau:/tmp/GUILE-GNUTLS/guile-gnutls-3.7.8$ head -n4 m4/ltoptions.m4 m4/lib-prefix.m4 ==> m4/ltoptions.m4 <== # Helper functions for option handling.-*- Autoconf -*- # # Copyright (C) 2004-2005, 2007-2009, 2011-2015 Free Software # Foundation, Inc. ==> m4/lib-prefix.m4 <== # lib-prefix.m4 serial 20 dnl Copyright (C) 2001-2005, 2008-2022 Free Software Foundation, Inc. dnl This file is free software; the Free Software Foundation dnl gives unlimited permission to copy and/or distribute it, (sid)ametzler@argenau:/tmp/GUILE-GNUTLS/guile-gnutls-3.7.8$ licensecheck -r m4 --copyright | grep -A1 -E 'm4/ltoptions.m4|m4/lib-prefix.m4' m4/lib-prefix.m4: FSF Unlimited License (with License Retention) [Copyright: 2001-2005, 2008-2022 Free Software Foundation, Inc.] -- m4/ltoptions.m4: FSF Unlimited License (with License Retention) [Copyright: 2004-2005, 2007-2009, 2011-2015 Free Software] cu Andreas
Bug#1020640: libglew2.2: Glew built without, wxwidgets with EGL support
On 2022-10-03 Alastair McKinstry wrote: > Hi, > As maintainer would be open to changing Glew to EGL support, but need to > understand better the consequences. > I have a test build of glew with egl (for Linux, not hurd or freebsd yet) > and it builds fine. > Any pointers to docs on EGL/non-EGL builds, or opinions and evidence would > be welcome. [...] With hugin opening hugin and klicking on the [GL] icon yields ERROR: 13:32:20.593540 (./src/hugin1/hugin/GLViewer.cpp:133) SetUpContext(): Error initialising GLEW: Unknown error. Klicking once more seems to succeed. I have tried rebuilding glew with --- a/debian/rules +++ b/debian/rules @@ -34,7 +34,7 @@ override_dh_auto_build: GLUT_LDFLAGS=-lglut \ LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH) \ 'LD=$$(CC)' \ - SYSTEM=$(firstword $(subst -, ,$(DEB_HOST_GNU_SYSTEM))) \ + SYSTEM=$(firstword $(subst -, ,$(DEB_HOST_GNU_SYSTEM)))-egl \ But I am not sure that actually works, since the symbol list is unchanged. The hugin behavior also does not change with this glew rebuild. I suspect glew upstream just is not ready yet: Afaict fedora does build with EGL suppport and OpenSuse has dropped it again: | * Sat Aug 21 2021 Atri Bhattacharya | - Revert building with EGL support, as it breaks mutliple apps | (boo#1189524). There is known breakage on the glew side: https://github.com/nigels-com/glew/issues/321 https://github.com/nigels-com/glew/issues/315 Archlinux builds with EGL but does some patching https://archlinuxarm.org/packages/armv7h/glew/files (Applying the patch to the Debian package yielded a FTBFS) cu Andreas
Bug#1021348: exim4-base: race in system boot causes exim4 to fail starting automatically
On 2022-10-06 Giacomo Mulas wrote: > Package: exim4-base > Version: 4.96-4 > Severity: normal > Dear Maintainer, > Since several months now I noticed that exim4.service fails to start > at boot when I am at work. > If I run > systemctl status exim4 > I get: [...] > ott 06 12:43:29 capitanata exim4[4169]: 2022-10-06 12:43:29 Exim > configuration error in line 508 of /var/lib/exim4/config.autogenerated.tmp: > ott 06 12:43:29 capitanata exim4[4169]: Unexpected end of configuration > file: .endif missing > ott 06 12:43:29 capitanata exim4[4245]: Invalid new configfile > /var/lib/exim4/config.autogenerated.tmp, not installing [...] > Exim4 invariably starts without a hitch if I manually issue a > systemctl start exim4 > after boot. [...] Hello, this is pretty strange since /usr/sbin/update-exim4 does not rely on dynamic data. Is your configuration data valid? /usr/sbin/update-exim4.conf -v --output /tmp/testme /usr/sbin/exim4 -bV -C /tmp/testme cu Andreas
