--- Begin Message ---
Source: allegro4.4
Version: 2:4.4.3.1-4
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: [email protected]
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
allegro4.4 as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for allegro4.4
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru allegro4.4-4.4.3.1/debian/changelog
allegro4.4-4.4.3.1/debian/changelog
--- allegro4.4-4.4.3.1/debian/changelog 2023-08-28 13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/changelog 2024-01-30 16:25:24.000000000 +0000
@@ -1,3 +1,10 @@
+allegro4.4 (2:4.4.3.1-4.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <[email protected]> Tue, 30 Jan 2024 16:25:24 +0000
+
allegro4.4 (2:4.4.3.1-4) unstable; urgency=medium
* Add a clean dh target to remove CHANGES - fixes building after a
diff -Nru allegro4.4-4.4.3.1/debian/control allegro4.4-4.4.3.1/debian/control
--- allegro4.4-4.4.3.1/debian/control 2023-08-28 13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/control 2024-01-30 16:25:24.000000000 +0000
@@ -26,15 +26,16 @@
Vcs-Browser: https://salsa.debian.org/games-team/allegro4.4
Vcs-Git: https://salsa.debian.org/games-team/allegro4.4.git
-Package: liballegro4.4
+Package: liballegro4.4t64
+Provides: ${t64:Provides}
Section: libs
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends},
${shlibs:Depends}
-Breaks: liballegro4.4-plugin-alsa (<= 2:4.4.2-4)
-Replaces: liballegro4.4-plugin-alsa (<= 2:4.4.2-4)
+Breaks: liballegro4.4 (<< ${source:Version}), liballegro4.4-plugin-alsa (<=
2:4.4.2-4)
+Replaces: liballegro4.4, liballegro4.4-plugin-alsa (<= 2:4.4.2-4)
Description: portable library for cross-platform game and multimedia
development
Allegro is a cross-platform library mainly aimed at video game and multimedia
programming. It handles common, low-level tasks such as creating windows,
@@ -46,7 +47,7 @@
Architecture: any
Depends: ${misc:Depends},
${shlibs:Depends},
- liballegro4.4 (= ${binary:Version}),
+ liballegro4.4t64 (= ${binary:Version}),
libxext-dev,
libx11-dev,
libxpm-dev,
@@ -81,14 +82,17 @@
accepting user input, loading data, drawing images, playing sounds, etc. and
generally abstracting away the underlying platform.
-Package: liballeggl4.4
+Package: liballeggl4.4t64
+Provides: ${t64:Provides}
+Replaces: liballeggl4.4
+Breaks: liballeggl4.4 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends},
${shlibs:Depends},
- liballegro4.4 (= ${binary:Version})
+ liballegro4.4t64 (= ${binary:Version})
Description: library to mix OpenGL graphics with Allegro routines
AllegroGL is an Allegro add-on that allows you to use OpenGL alongside
Allegro -- you use OpenGL for your rendering to the screen, and Allegro for
@@ -109,7 +113,7 @@
Section: libdevel
Architecture: any
Depends: ${misc:Depends},
- liballeggl4.4 (= ${binary:Version}),
+ liballeggl4.4t64 (= ${binary:Version}),
liballegro4-dev
Replaces: liballegro4.2-dev (<< 2:4.4.2-3)
Breaks: liballegro4.2-dev (<< 2:4.4.2-3)
@@ -132,7 +136,10 @@
accepting user input, loading data, drawing images, playing sounds, etc. and
generally abstracting away the underlying platform.
-Package: libjpgalleg4.4
+Package: libjpgalleg4.4t64
+Provides: ${t64:Provides}
+Replaces: libjpgalleg4.4
+Breaks: libjpgalleg4.4 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -152,7 +159,7 @@
Section: libdevel
Architecture: any
Depends: ${misc:Depends},
- libjpgalleg4.4 (= ${binary:Version}),
+ libjpgalleg4.4t64 (= ${binary:Version}),
liballegro4-dev
Multi-Arch: same
Description: development files for the JPG loading addon for Allegro 4
@@ -166,7 +173,10 @@
accepting user input, loading data, drawing images, playing sounds, etc. and
generally abstracting away the underlying platform.
-Package: libloadpng4.4
+Package: libloadpng4.4t64
+Provides: ${t64:Provides}
+Replaces: libloadpng4.4
+Breaks: libloadpng4.4 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -186,7 +196,7 @@
Section: libdevel
Architecture: any
Depends: ${misc:Depends},
- libloadpng4.4 (= ${binary:Version}),
+ libloadpng4.4t64 (= ${binary:Version}),
liballegro4-dev
Multi-Arch: same
Description: development files for the PNG loading addon for Allegro 4
@@ -200,7 +210,10 @@
accepting user input, loading data, drawing images, playing sounds, etc. and
generally abstracting away the underlying platform.
-Package: liblogg4.4
+Package: liblogg4.4t64
+Provides: ${t64:Provides}
+Replaces: liblogg4.4
+Breaks: liblogg4.4 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -221,7 +234,7 @@
Section: libdevel
Architecture: any
Depends: ${misc:Depends},
- liblogg4.4 (= ${binary:Version}),
+ liblogg4.4t64 (= ${binary:Version}),
liballegro4-dev,
libvorbis-dev
Replaces: liballegro4.2-dev (<< 2:4.4.2-3)
diff -Nru allegro4.4-4.4.3.1/debian/liballeggl4.4.install
allegro4.4-4.4.3.1/debian/liballeggl4.4.install
--- allegro4.4-4.4.3.1/debian/liballeggl4.4.install 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballeggl4.4.install 1970-01-01
00:00:00.000000000 +0000
@@ -1,3 +0,0 @@
-usr/lib/*/liballeggl.so.4.4
-usr/lib/*/liballeggl.so.4.4.3
-
diff -Nru allegro4.4-4.4.3.1/debian/liballeggl4.4.lintian-overrides
allegro4.4-4.4.3.1/debian/liballeggl4.4.lintian-overrides
--- allegro4.4-4.4.3.1/debian/liballeggl4.4.lintian-overrides 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballeggl4.4.lintian-overrides 1970-01-01
00:00:00.000000000 +0000
@@ -1,14 +0,0 @@
-# We don't include symbols files, because on the one hand
-# private symbols are exported and not easily distinguishable
-# from public ones. They have a leading underscore, but there
-# are also public ones with a leading underscore.
-# On the other hand, symbols files are not needed, because
-# the API is frozen anyway. Quote from Peter Wang:
-# "Anyway, 4.4 is on life support.
-# The API is essentially frozen forever."
-# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
-liballeggl4.4 binary: no-symbols-control-file
-
-# False positive, there are no functions to protect.
-# There are only strncpy, memset and memcpy.
-liballeggl4.4 binary: hardening-no-fortify-functions
diff -Nru allegro4.4-4.4.3.1/debian/liballeggl4.4t64.install
allegro4.4-4.4.3.1/debian/liballeggl4.4t64.install
--- allegro4.4-4.4.3.1/debian/liballeggl4.4t64.install 1970-01-01
00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballeggl4.4t64.install 2023-08-28
13:02:32.000000000 +0000
@@ -0,0 +1,3 @@
+usr/lib/*/liballeggl.so.4.4
+usr/lib/*/liballeggl.so.4.4.3
+
diff -Nru allegro4.4-4.4.3.1/debian/liballeggl4.4t64.lintian-overrides
allegro4.4-4.4.3.1/debian/liballeggl4.4t64.lintian-overrides
--- allegro4.4-4.4.3.1/debian/liballeggl4.4t64.lintian-overrides
1970-01-01 00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballeggl4.4t64.lintian-overrides
2024-01-30 16:25:24.000000000 +0000
@@ -0,0 +1,15 @@
+# We don't include symbols files, because on the one hand
+# private symbols are exported and not easily distinguishable
+# from public ones. They have a leading underscore, but there
+# are also public ones with a leading underscore.
+# On the other hand, symbols files are not needed, because
+# the API is frozen anyway. Quote from Peter Wang:
+# "Anyway, 4.4 is on life support.
+# The API is essentially frozen forever."
+# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
+liballeggl4.4t64 binary: no-symbols-control-file
+
+# False positive, there are no functions to protect.
+# There are only strncpy, memset and memcpy.
+liballeggl4.4t64 binary: hardening-no-fortify-functions
+liballeggl4.4t64: package-name-doesnt-match-sonames liballeggl4.4
diff -Nru allegro4.4-4.4.3.1/debian/liballegro4.4.examples
allegro4.4-4.4.3.1/debian/liballegro4.4.examples
--- allegro4.4-4.4.3.1/debian/liballegro4.4.examples 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballegro4.4.examples 1970-01-01
00:00:00.000000000 +0000
@@ -1 +0,0 @@
-allegro.cfg
diff -Nru allegro4.4-4.4.3.1/debian/liballegro4.4.install
allegro4.4-4.4.3.1/debian/liballegro4.4.install
--- allegro4.4-4.4.3.1/debian/liballegro4.4.install 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballegro4.4.install 1970-01-01
00:00:00.000000000 +0000
@@ -1,4 +0,0 @@
-usr/lib/*/allegro/4.4.3/*
-usr/lib/*/liballeg.so.4.4.3
-usr/lib/*/liballeg.so.4.4
-
diff -Nru allegro4.4-4.4.3.1/debian/liballegro4.4.lintian-overrides
allegro4.4-4.4.3.1/debian/liballegro4.4.lintian-overrides
--- allegro4.4-4.4.3.1/debian/liballegro4.4.lintian-overrides 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballegro4.4.lintian-overrides 1970-01-01
00:00:00.000000000 +0000
@@ -1,13 +0,0 @@
-# We don't include symbols files, because on the one hand
-# private symbols are exported and not easily distinguishable
-# from public ones. They have a leading underscore, but there
-# are also public ones with a leading underscore.
-# On the other hand, symbols files are not needed, because
-# the API is frozen anyway. Quote from Peter Wang:
-# "Anyway, 4.4 is on life support.
-# The API is essentially frozen forever."
-# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
-liballegro4.4 binary: no-symbols-control-file
-
-# We keep the package name to be consistent with past Allegro packages.
-liballegro4.4 binary: package-name-doesnt-match-sonames
diff -Nru allegro4.4-4.4.3.1/debian/liballegro4.4t64.examples
allegro4.4-4.4.3.1/debian/liballegro4.4t64.examples
--- allegro4.4-4.4.3.1/debian/liballegro4.4t64.examples 1970-01-01
00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballegro4.4t64.examples 2023-08-28
13:02:32.000000000 +0000
@@ -0,0 +1 @@
+allegro.cfg
diff -Nru allegro4.4-4.4.3.1/debian/liballegro4.4t64.install
allegro4.4-4.4.3.1/debian/liballegro4.4t64.install
--- allegro4.4-4.4.3.1/debian/liballegro4.4t64.install 1970-01-01
00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballegro4.4t64.install 2023-08-28
13:02:32.000000000 +0000
@@ -0,0 +1,4 @@
+usr/lib/*/allegro/4.4.3/*
+usr/lib/*/liballeg.so.4.4.3
+usr/lib/*/liballeg.so.4.4
+
diff -Nru allegro4.4-4.4.3.1/debian/liballegro4.4t64.lintian-overrides
allegro4.4-4.4.3.1/debian/liballegro4.4t64.lintian-overrides
--- allegro4.4-4.4.3.1/debian/liballegro4.4t64.lintian-overrides
1970-01-01 00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liballegro4.4t64.lintian-overrides
2024-01-30 16:25:24.000000000 +0000
@@ -0,0 +1,14 @@
+# We don't include symbols files, because on the one hand
+# private symbols are exported and not easily distinguishable
+# from public ones. They have a leading underscore, but there
+# are also public ones with a leading underscore.
+# On the other hand, symbols files are not needed, because
+# the API is frozen anyway. Quote from Peter Wang:
+# "Anyway, 4.4 is on life support.
+# The API is essentially frozen forever."
+# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
+liballegro4.4t64 binary: no-symbols-control-file
+
+# We keep the package name to be consistent with past Allegro packages.
+liballegro4.4t64 binary: package-name-doesnt-match-sonames
+liballegro4.4t64: package-name-doesnt-match-sonames liballegro4.4
diff -Nru allegro4.4-4.4.3.1/debian/libjpgalleg4.4.install
allegro4.4-4.4.3.1/debian/libjpgalleg4.4.install
--- allegro4.4-4.4.3.1/debian/libjpgalleg4.4.install 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/libjpgalleg4.4.install 1970-01-01
00:00:00.000000000 +0000
@@ -1,3 +0,0 @@
-usr/lib/*/libjpgalleg.so.4.4.3
-usr/lib/*/libjpgalleg.so.4.4
-
diff -Nru allegro4.4-4.4.3.1/debian/libjpgalleg4.4.lintian-overrides
allegro4.4-4.4.3.1/debian/libjpgalleg4.4.lintian-overrides
--- allegro4.4-4.4.3.1/debian/libjpgalleg4.4.lintian-overrides 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/libjpgalleg4.4.lintian-overrides 1970-01-01
00:00:00.000000000 +0000
@@ -1,10 +0,0 @@
-# We don't include symbols files, because on the one hand
-# private symbols are exported and not easily distinguishable
-# from public ones. They have a leading underscore, but there
-# are also public ones with a leading underscore.
-# On the other hand, symbols files are not needed, because
-# the API is frozen anyway. Quote from Peter Wang:
-# "Anyway, 4.4 is on life support.
-# The API is essentially frozen forever."
-# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
-libjpgalleg4.4 binary: no-symbols-control-file
diff -Nru allegro4.4-4.4.3.1/debian/libjpgalleg4.4t64.install
allegro4.4-4.4.3.1/debian/libjpgalleg4.4t64.install
--- allegro4.4-4.4.3.1/debian/libjpgalleg4.4t64.install 1970-01-01
00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/libjpgalleg4.4t64.install 2023-08-28
13:02:32.000000000 +0000
@@ -0,0 +1,3 @@
+usr/lib/*/libjpgalleg.so.4.4.3
+usr/lib/*/libjpgalleg.so.4.4
+
diff -Nru allegro4.4-4.4.3.1/debian/libjpgalleg4.4t64.lintian-overrides
allegro4.4-4.4.3.1/debian/libjpgalleg4.4t64.lintian-overrides
--- allegro4.4-4.4.3.1/debian/libjpgalleg4.4t64.lintian-overrides
1970-01-01 00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/libjpgalleg4.4t64.lintian-overrides
2024-01-30 16:25:24.000000000 +0000
@@ -0,0 +1,11 @@
+# We don't include symbols files, because on the one hand
+# private symbols are exported and not easily distinguishable
+# from public ones. They have a leading underscore, but there
+# are also public ones with a leading underscore.
+# On the other hand, symbols files are not needed, because
+# the API is frozen anyway. Quote from Peter Wang:
+# "Anyway, 4.4 is on life support.
+# The API is essentially frozen forever."
+# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
+libjpgalleg4.4t64 binary: no-symbols-control-file
+libjpgalleg4.4t64: package-name-doesnt-match-sonames libjpgalleg4.4
diff -Nru allegro4.4-4.4.3.1/debian/libloadpng4.4.install
allegro4.4-4.4.3.1/debian/libloadpng4.4.install
--- allegro4.4-4.4.3.1/debian/libloadpng4.4.install 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/libloadpng4.4.install 1970-01-01
00:00:00.000000000 +0000
@@ -1,3 +0,0 @@
-usr/lib/*/libloadpng.so.4.4.3
-usr/lib/*/libloadpng.so.4.4
-
diff -Nru allegro4.4-4.4.3.1/debian/libloadpng4.4.lintian-overrides
allegro4.4-4.4.3.1/debian/libloadpng4.4.lintian-overrides
--- allegro4.4-4.4.3.1/debian/libloadpng4.4.lintian-overrides 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/libloadpng4.4.lintian-overrides 1970-01-01
00:00:00.000000000 +0000
@@ -1,10 +0,0 @@
-# We don't include symbols files, because on the one hand
-# private symbols are exported and not easily distinguishable
-# from public ones. They have a leading underscore, but there
-# are also public ones with a leading underscore.
-# On the other hand, symbols files are not needed, because
-# the API is frozen anyway. Quote from Peter Wang:
-# "Anyway, 4.4 is on life support.
-# The API is essentially frozen forever."
-# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
-libloadpng4.4 binary: no-symbols-control-file
diff -Nru allegro4.4-4.4.3.1/debian/libloadpng4.4t64.install
allegro4.4-4.4.3.1/debian/libloadpng4.4t64.install
--- allegro4.4-4.4.3.1/debian/libloadpng4.4t64.install 1970-01-01
00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/libloadpng4.4t64.install 2023-08-28
13:02:32.000000000 +0000
@@ -0,0 +1,3 @@
+usr/lib/*/libloadpng.so.4.4.3
+usr/lib/*/libloadpng.so.4.4
+
diff -Nru allegro4.4-4.4.3.1/debian/libloadpng4.4t64.lintian-overrides
allegro4.4-4.4.3.1/debian/libloadpng4.4t64.lintian-overrides
--- allegro4.4-4.4.3.1/debian/libloadpng4.4t64.lintian-overrides
1970-01-01 00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/libloadpng4.4t64.lintian-overrides
2024-01-30 16:25:24.000000000 +0000
@@ -0,0 +1,11 @@
+# We don't include symbols files, because on the one hand
+# private symbols are exported and not easily distinguishable
+# from public ones. They have a leading underscore, but there
+# are also public ones with a leading underscore.
+# On the other hand, symbols files are not needed, because
+# the API is frozen anyway. Quote from Peter Wang:
+# "Anyway, 4.4 is on life support.
+# The API is essentially frozen forever."
+# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
+libloadpng4.4t64 binary: no-symbols-control-file
+libloadpng4.4t64: package-name-doesnt-match-sonames libloadpng4.4
diff -Nru allegro4.4-4.4.3.1/debian/liblogg4.4.install
allegro4.4-4.4.3.1/debian/liblogg4.4.install
--- allegro4.4-4.4.3.1/debian/liblogg4.4.install 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liblogg4.4.install 1970-01-01
00:00:00.000000000 +0000
@@ -1,3 +0,0 @@
-usr/lib/*/liblogg.so.4.4.3
-usr/lib/*/liblogg.so.4.4
-
diff -Nru allegro4.4-4.4.3.1/debian/liblogg4.4.lintian-overrides
allegro4.4-4.4.3.1/debian/liblogg4.4.lintian-overrides
--- allegro4.4-4.4.3.1/debian/liblogg4.4.lintian-overrides 2023-08-28
13:02:32.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liblogg4.4.lintian-overrides 1970-01-01
00:00:00.000000000 +0000
@@ -1,14 +0,0 @@
-# We don't include symbols files, because on the one hand
-# private symbols are exported and not easily distinguishable
-# from public ones. They have a leading underscore, but there
-# are also public ones with a leading underscore.
-# On the other hand, symbols files are not needed, because
-# the API is frozen anyway. Quote from Peter Wang:
-# "Anyway, 4.4 is on life support.
-# The API is essentially frozen forever."
-# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
-liblogg4.4 binary: no-symbols-control-file
-
-# False positive, there are no functions to protect.
-# There are only strncpy, memset, memcpy and fread.
-liblogg4.4 binary: hardening-no-fortify-functions
diff -Nru allegro4.4-4.4.3.1/debian/liblogg4.4t64.install
allegro4.4-4.4.3.1/debian/liblogg4.4t64.install
--- allegro4.4-4.4.3.1/debian/liblogg4.4t64.install 1970-01-01
00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liblogg4.4t64.install 2023-08-28
13:02:32.000000000 +0000
@@ -0,0 +1,3 @@
+usr/lib/*/liblogg.so.4.4.3
+usr/lib/*/liblogg.so.4.4
+
diff -Nru allegro4.4-4.4.3.1/debian/liblogg4.4t64.lintian-overrides
allegro4.4-4.4.3.1/debian/liblogg4.4t64.lintian-overrides
--- allegro4.4-4.4.3.1/debian/liblogg4.4t64.lintian-overrides 1970-01-01
00:00:00.000000000 +0000
+++ allegro4.4-4.4.3.1/debian/liblogg4.4t64.lintian-overrides 2024-01-30
16:25:24.000000000 +0000
@@ -0,0 +1,15 @@
+# We don't include symbols files, because on the one hand
+# private symbols are exported and not easily distinguishable
+# from public ones. They have a leading underscore, but there
+# are also public ones with a leading underscore.
+# On the other hand, symbols files are not needed, because
+# the API is frozen anyway. Quote from Peter Wang:
+# "Anyway, 4.4 is on life support.
+# The API is essentially frozen forever."
+# (http://sourceforge.net/mailarchive/message.php?msg_id=29119754)
+liblogg4.4t64 binary: no-symbols-control-file
+
+# False positive, there are no functions to protect.
+# There are only strncpy, memset, memcpy and fread.
+liblogg4.4t64 binary: hardening-no-fortify-functions
+liblogg4.4t64: package-name-doesnt-match-sonames liblogg4.4
--- End Message ---
pgpklsaT9oUTk.pgp
