| « webapp.eclass documentation | FSF Conference on GPLv3 » |
web-apps overlay
12/18/05 00:44 , Categories: Gentoo I finally finished going through the bugs assigned to webapps-request, an alias that has been accumulating ebuild request from users. Having closed what feels like ~30-40 bugs, I got it down to just 13 . Most of the remaining bugs are packages with weird build systems that I'm not interested in.
What did I do with all those ebuilds, you ask? What I didn't do was stick them in the tree. The web-apps herd is very much understaffed at the moment, so I've put a hold on adding random packages. Instead, I moved them to our brand new overlay. The purpose of the overlay is to make it easier for end users to install web-apps without adding work for our devs. So go check it out and let us know what you think!
Noteworthy package of the week: webgui from PlainBlack.
Update: I've gone through the maintainer-needed alias and picked up a few more relevant bugs. We are now back to 43 :|
6 comments
I've emerged all dependencies and it found a tar of webgui, http://ufpr.dl.sourceforge.net/sourceforge/pbwebgui/webgui-6.8.2-beta.tar.gz.
But when emerging it it stalls after unpacking the source.
At least that's what I am experiencing.
It looks like this:
# emerge -av www-apps/webgui
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] www-apps/webgui-6.8.2_beta +vhosts 0 kB [1]
Total size of downloads: 0 kB
Portage overlays:
[1] /usr/local/gentoo-webapps-overlay/experimental
[2] /usr/local/gentoo-webapps-overlay/production-ready
Do you want me to merge these packages? [Yes/No] yes
>>> emerge (1 of 1) www-apps/webgui-6.8.2_beta to /
>>> md5 files ;-) webgui-6.8.2_beta.ebuild
>>> md5 files ;-) files/postinstall-en.txt
>>> md5 files ;-) files/digest-webgui-6.8.2_beta
>>> md5 files ;-) files/reconfig
>>> md5 src_uri ;-) webgui-6.8.2-beta.tar.gz
>>> Unpacking source...
>>> Unpacking webgui-6.8.2-beta.tar.gz to /var/tmp/portage/webgui-6.8.2_beta/work
>>> Source unpacked.
After that, absolutely nothing happens.
hmm, just didd a 'ps ux'. It does show something is going on:
root 27814 0.4 0.8 13216 9212 pts/3 S+ 07:48 0:01 /usr/bin/python -O /usr/bin/emerge -av www-apps/webgui
root 27896 0.0 0.0 1500 424 pts/3 S+ 07:48 0:00 [webgui-6.8.2_beta] sandbox /usr/lib/portage/bin/ebuild.sh compile
root 27897 0.0 0.2 5620 3056 pts/3 S+ 07:48 0:00 /bin/bash /usr/lib/portage/bin/ebuild.sh compile
root 27916 0.1 0.9 12720 9836 pts/3 S+ 07:48 0:00 /usr/bin/perl testEnvironment.pl
How long is that supposed to take?
I see no disk activity and neither process shows up in 'top', so they can't be taxing the system very much.
I'm guessing something isn't going quite as expected.
These are still active, but they're using 0% cpu.
root 27814 0.0 0.8 13216 9212 pts/3 S+ 07:48 0:01 /usr/bin/python -O /usr/bin/emerge -av www-apps/webgui
root 27896 0.0 0.0 1500 424 pts/3 S+ 07:48 0:00 [webgui-6.8.2_beta] sandbox /usr/lib/portage/bin/ebuild.sh compile
root 27897 0.0 0.2 5620 3056 pts/3 S+ 07:48 0:00 /bin/bash /usr/lib/portage/bin/ebuild.sh compile
root 27916 0.0 0.9 12720 9836 pts/3 S+ 07:48 0:00 /usr/bin/perl testEnvironment.pl
Any clues what could be going wrong?
cd YOUR_OVERLAY_DIR/webgui
ebuild webgui-6.8.2_beta.ebuild digest unpack
cd /var/tmp/portage/webgui-6.8.2_beta/work/WebGUI/sbin
perl testEnvironment.pl
and see what it says.
Also, let's move this discussion to the trac - please file a new ticket with that info
Thanks
Will test your suggestion in a minute.
Comment feed for this postLeave a comment
