Your message dated Mon, 2 Jun 2008 13:21:58 +0100
with message-id <[EMAIL PROTECTED]>
and subject line estraier has been removed from Debian, closing #399138
has caused the Debian Bug report #399138,
regarding hyperestraier: FTBFS: upstream build rules look in $(HOME) for
includes
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.)
--
399138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399138
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: hyperestraier
Version: 1.0.6-1
Severity: serious
Justification: FTBFS
Tags: patch
Hi Fumitoshi,
Just as for qdbm as described in bug #398196, hyperestraier is failing to
build on alpha and mips:
[...]
# Add here commands to configure the package.
CFLAGS="-Wall -g -O2" JAVAC="gcj-wrapper" JAR="fastjar" ./configure
--host=alpha-linux-gnu --build=alpha-linux-gnu --prefix=/usr
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
--includedir=\${prefix}/include/estraier --libexecdir=\${prefix}/lib/estraier \
--enable-regex
#================================================================
# Configuring Hyper Estraier version 1.4.8.
#================================================================
checking for alpha-linux-gnu-gcc... alpha-linux-gnu-gcc
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
See `config.log' for more details.
[...]
You can find a full build log at
<http://buildd.debian.org/fetch.cgi?pkg=hyperestraier&arch=alpha&ver=1.4.8-1&stamp=1162623864>.
Please see bug #398196 for the full explanation of why this is a bug in this
package.
I have confirmed that the attached patch fixes the problem for hyperestraier
as well, by explicitly setting $HOME to a local directory inside the build
tree when building.
This bug affects both the testing and unstable versions of hyperestraier,
and together with bug #398196 it also currently prevents the fix for bug
#367374 in hyperestraier from reaching testing, so I will plan to NMU this
package as well if it is unfixed after two days.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
diff -u hyperestraier-1.4.8/debian/changelog
hyperestraier-1.4.8/debian/changelog
--- hyperestraier-1.4.8/debian/changelog
+++ hyperestraier-1.4.8/debian/changelog
@@ -1,3 +1,14 @@
+hyperestraier (1.4.8-1.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * High-urgency upload for RC bugfix.
+ * Set HOME=$(CURDIR)/junkhome when building, otherwise the package build
+ will incorrectly look for headers there -- and fail when the directory
+ exists and is unreadable, as happens sometimes on sudo-using
+ autobuilders!
+
+ -- Steve Langasek <[EMAIL PROTECTED]> Sun, 12 Nov 2006 04:52:18 -0800
+
hyperestraier (1.4.8-1) unstable; urgency=low
* New upstream release
diff -u hyperestraier-1.4.8/debian/rules hyperestraier-1.4.8/debian/rules
--- hyperestraier-1.4.8/debian/rules
+++ hyperestraier-1.4.8/debian/rules
@@ -16,6 +16,10 @@
# This has to be exported to make some magic below work.
export DH_OPTIONS
+# work-around for upstream build that thinks $(HOME) belongs in the
+# include path for all builds!
+export HOME=$(CURDIR)/junkhome
+
# These are used for cross-compiling and for saving the configure script
# from having to guess our platform (since we know it already)
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
--- End Message ---
--- Begin Message ---
Version: 1.2.29-3+rm
The estraier package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/423242 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
http://Marco.Tondela.org
--- End Message ---
