Your message dated Mon, 31 Dec 2018 04:15:22 +0000
with message-id <[email protected]>
and subject line Bug#914111: Removed package(s) from unstable
has caused the Debian Bug report #507195,
regarding liblunar: Shouldn't use in-tree libtool when trying to detect python
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
507195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507195
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: liblunar
Version: 1.0.0-1
Severity: normal
Tags: patch
User: [email protected]
Usertags: origin-ubuntu jaunty ubuntu-patch
Hi,
Newer libtools don't put the libtool script in tree on libtoolize, so
when your package runs libtoolize during the build it is removed. This
then causes the configure check for python to fail as it can't use
../libtool. This means that the python parts aren't built, and so the
package fails to build when can't be installed.
Attached is a patch to use the system libtool instead. Please consider
applying it.
Thanks,
James
diff -u liblunar-1.0.0/debian/changelog liblunar-1.0.0/debian/changelog
diff -u liblunar-1.0.0/debian/patches/00list
liblunar-1.0.0/debian/patches/00list
--- liblunar-1.0.0/debian/patches/00list
+++ liblunar-1.0.0/debian/patches/00list
@@ -1,0 +2 @@
+02_libtool_path
only in patch2:
unchanged:
--- liblunar-1.0.0.orig/debian/patches/02_libtool_path.dpatch
+++ liblunar-1.0.0/debian/patches/02_libtool_path.dpatch
@@ -0,0 +1,21 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 02_libtool_path.dpatch by <[email protected]>
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Correct the paths to the libtool script in configure.ac
+
+@DPATCH@
+diff -urNad liblunar~/configure.ac liblunar/configure.ac
+--- liblunar~/configure.ac 2008-11-28 23:38:12.000000000 +0000
++++ liblunar/configure.ac 2008-11-28 23:38:40.000000000 +0000
+@@ -112,8 +112,8 @@
+ }
+ EOF
+
+- if /bin/sh ../libtool --mode=compile ${CC} $PYTHON_CFLAGS -c
testpython.c >/dev/null 2>&1 && \
+- /bin/sh ../libtool --mode=link ${CC} -o testpython.la -rpath
`pwd` -module -avoid-version -no-undefined $PYTHON_LIB_LOC testpython.lo
$PYTHON_LIBS $PYTHON_EXTRA_LIBS >/dev/null 2>&1 && \
++ if libtool --mode=compile ${CC} $PYTHON_CFLAGS -c testpython.c
>/dev/null 2>&1 && \
++ libtool --mode=link ${CC} -o testpython.la -rpath `pwd` -module
-avoid-version -no-undefined $PYTHON_LIB_LOC testpython.lo $PYTHON_LIBS
$PYTHON_EXTRA_LIBS >/dev/null 2>&1 && \
+ grep 'dlname.*testpython' testpython.la >/dev/null 2>&1; then
+ result=yes
+ else
--- End Message ---
--- Begin Message ---
Version: 2.0.1-3+rm
Dear submitter,
as the package liblunar has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/914111
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
