maemo.org Bugzilla – Bug 4852
Remove Scratchboxism in wpeditor packaging
Last modified: 2010-03-15 20:56:51 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
Building wpeditor outside Scratchbox (Debian/Ubuntu) in typical build
environment (build-essentials and dependancies installed), see
Ability to build wpeditor
Fails to build due to assumption that automake, autoconf and libtool is
installed in typical build environments, which Scratchbox has, but Debian,
Ubuntu and others do not - a scratchboxism (or sb-will-have-it-ism).
EXTRA SOFTWARE INSTALLED:
Fixing this is a matter of adding ', autoconf, automake, libtool' to
Build-Depends in wpeditor packaging. Adding this fix will make us be able to
remove the only delta to wpeditor in the packaging we have to maintain in Mer
and would allow us and others to directly use the wpeditor packaging outside of
Maemo without modification.
Use of libtool, autoconf and automake can be seen in 'autogen.sh' (autoreconf
calls it) and debian/rules rule and hence package should build-depend on them
as these tools are not part of a typical build environment.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124)
Gecko/2009060308 Ubuntu/9.04 (jaunty) Firefox/3.0.11
This has been fixed in package
which is part of the internal build version
(Note: 2009 is the year, and the number after is the week.)
A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
To answer popular followup questions:
* Nokia does not announce release dates of public updates in advance.
* There is currently no access to these internal, non-public build versions.
A Brainstorm proposal to change this exists at
(Fix not included in today's 2.2009.51-1 update => updating Version field)
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).