Apache OpenOffice (AOO) Bugzilla – Issue 121469
error in "determine_new_packagename (packagepool)"
Last modified: 2014-02-24 14:02:50 UTC
Created attachment 80022 [details] log info I try to build aoo-3.4.1 in Ubuntu12.04.1 x86_64, I meet the following error : ************************************************** ERROR: ERROR: More than one new package in directory /home/panquanyi/Downloads/aoo-3.4.1/main/instsetoo_native/unxlngx6.pro/OpenOffice/deb/install/en-US_inprogress/DEBS ( /home/panquanyi/Downloads/aoo-3.4.1/main/instsetoo_native/unxlngx6.pro/OpenOffice/deb/install/en-US_inprogress/DEBS/ooobasis3.4-en-us-draw-3.4.1-1-linux-3.2-x86_64.deb /home/panquanyi/Downloads/aoo-3.4.1/main/instsetoo_native/unxlngx6.pro/OpenOffice/deb/install/en-US_inprogress/DEBS/ooobasis3.4-en-us-draw-3.4.1-1-linux-3.2-x86_64) in function: determine_new_packagename (packagepool) I find the function "determine_new_packagename (packagepool) in file: solenv/bin/modules/installer/packagepool.pm crashed ,but do not know why. it is in the process of instsetoo_native build. the following is what I do : sudo apt-get install g++ ant sudo apt-get install autoconf dmake epm gperf bison orbit2 flex \ libx11-dev libxaw7-dev libfontconfig1-dev libxrandr-dev libcups2-dev \ libgconf2-dev libgnomevfs2-dev libpam-dev libgtk2.0-dev liborbit2-dev \ libssl-dev \ libwww-perl libarchive-zip-perl autoconf ./configure --disable-mozilla --without-junit --disable-odk ./bootstrap source LinuxX86-64Env.Set.sh cd instsetoo_native && build --all
(In reply to comment #0) > Created attachment 80022 [details] > log info > > I try to build aoo-3.4.1 in Ubuntu12.04.1 x86_64, > I meet the following error : > ************************************************** > ERROR: ERROR: More than one new package in directory it looks like you are not using the patched EPM. ./configure --with-epm-url=<URL> Specify the location of downloadable epm 3.7 source code. For example: http://ftp.easysw.com/pub/epm/3.7/epm-3.7-source.tar.gz
But my epm version is v4.2, must i used this special patched version 3.7, emp v4.2 donot fix the problem which fixed in the special patched version 3.7 ??? if true, I suggess epm should be removed and other package alternative should be used. @ubuntu:~$ epm --version ESP Package Manager v4.2
(In reply to comment #2) > But my epm version is v4.2, must i used this special patched version 3.7, > emp v4.2 donot fix the problem which fixed in the special patched version > 3.7 ??? You must use this version because it is *patched*; yes, it's suboptimal, but the build environment only works with this very special version with the patch applied. > if true, I suggess epm should be removed and other package alternative > should be used. ideally rpm-build and dpkg should be used directly, but... someone has to sit down, and modify the build environment (not an easy task).
thanks . I used this very special version 3.7, it's works! the compile process finished successfully.
I just found out the link provided by Ariel Constenla-Haile is not working and I found another link which contain a few mirror of this file: http://www.filewatcher.com/m/epm-3.7-source.tar.gz.463264-0.html When I do this: ./configure --with-epm-url=<URL> and then this: build --all:instsetoo_native My problem still persist. May I know what else have I miss?
I take notes in a blog: http://panquanyi.blog.163.com/blog/static/293250082013042853212/ I also meet some other problem and finally fix it, please have a try.
@panquanyi The solution that you provided is not working. Anyhow, here is the temporary workaround step I have been done: 1. download the EPM source from http://www.filewatcher.com/m/epm-3.7-source.tar.gz.463264-0.html 2. extract the source. 3. build the source. (the guideline is included in the source) 4. ./configure --with-epm= <the binary build in step 3) 5. ./boostrap 6. `build --all:instsetoo_native` if you choose to continue the build. @Dear all, This defect has not been resolve, hope there is a fix for this issue in near future.
There has been another bug raise for this problem and it was fixed now. For details fixes, check out the following link. https://issues.apache.org/ooo/show_bug.cgi?id=124301