danblack: I took a look at the differences between the dh_strip in stretch (version 0.031-1) and the version currently in jessie-backports (version 0.031-1~bpo8+1) and yes, there is one difference:
error("--dbgsym-migration and --no-automatic-dbgsym are mutually exclusive");
}
+# UNCONDITIONALLY disable this as we need a new version of dpkg-dev
+# for this to work
+$dh{ENABLE_DBGSYM} = 0;
+
# This variable can be used to turn off stripping (see Policy).
if (get_buildoption('nostrip')) {
exit;
Daniel Bartholomew
added a comment - danblack : I took a look at the differences between the dh_strip in stretch (version 0.031-1) and the version currently in jessie-backports (version 0.031-1~bpo8+1) and yes, there is one difference:
--- dh_strip-stretch 2017-03-17 12:27:10.339611257 -0400
+++ dh_strip-jessie-0.031-1~bpo8+1 2017-03-17 12:57:01.018522537 -0400
@@ -166,6 +166,10 @@
error("--dbgsym-migration and --no-automatic-dbgsym are mutually exclusive");
}
+# UNCONDITIONALLY disable this as we need a new version of dpkg-dev
+# for this to work
+$dh{ENABLE_DBGSYM} = 0;
+
# This variable can be used to turn off stripping (see Policy).
if (get_buildoption('nostrip')) {
exit;
So have you all the information needed for debug packages on Debian and Ubuntu?
Although you observed compat 9 wasn't required for operation did you see added compression of the debug package as a result of it (https://www.mankier.com/7/debhelper#Compatibility_Levels)? Where filenames in the debug packages different?
Daniel Black
added a comment - dbart , yes that would be the difference I mentioned in (3.) here https://jira.mariadb.org/browse/MDEV-658?focusedCommentId=92965&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-92965 . I couldn't see how the dpkg-dev versioning had an effect on this.
So have you all the information needed for debug packages on Debian and Ubuntu?
Although you observed compat 9 wasn't required for operation did you see added compression of the debug package as a result of it ( https://www.mankier.com/7/debhelper#Compatibility_Levels)? Where filenames in the debug packages different?
So 5.5 has no debug syms.
(Debian): 10.0 has a 10.0.30 debug package for x86_64/i386 but not for ppc64le or 10.0.31 10.1 has 10.1.22 and 10.1.23 (x86_64 only) but not 10.1.24 10.2 has recent debug symbols packages for recent releases of x86_64/i386 but not ppc64le.
Daniel Black
added a comment - - edited So 5.5 has no debug syms.
(Debian):
10.0 has a 10.0.30 debug package for x86_64/i386 but not for ppc64le or 10.0.31
10.1 has 10.1.22 and 10.1.23 (x86_64 only) but not 10.1.24
10.2 has recent debug symbols packages for recent releases of x86_64/i386 but not ppc64le.
Bug
Major
danblack: I took a look at the differences between the dh_strip in stretch (version 0.031-1) and the version currently in jessie-backports (version 0.031-1~bpo8+1) and yes, there is one difference:
--- dh_strip-stretch 2017-03-17 12:27:10.339611257 -0400+++ dh_strip-jessie-0.031-1~bpo8+1 2017-03-17 12:57:01.018522537 -0400@@ -166,6 +166,10 @@error("--dbgsym-migration and --no-automatic-dbgsym are mutually exclusive");}+# UNCONDITIONALLY disable this as we need a new version of dpkg-dev+# for this to work+$dh{ENABLE_DBGSYM} = 0;+# This variable can be used to turn off stripping (see Policy).if (get_buildoption('nostrip')) {exit;