chdir can be fixed by creating a directory "/usr/share/doc/samba-3.0.22/swat" the other problem leaves me asking... Portage 2.1 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r3, 2.6.16-gentoo-r9gi2 i686) ================================================================= System uname: 2.6.16-gentoo-r9gi2 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.14 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r2 sys-devel/gcc-config: 1.3.13-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo" CXXFLAGS="-O2 -march=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LINGUAS="de" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 7zip apache apache2 apm avi berkdb bitmap-fonts bzip2 capabilities cli crypt curl dri eds emboss encode examples fam foomaticdb fortran gd-external gdbm gif gnutls gpm gstreamer gzip idn imlib ipv6 isdnlog ithreads jpeg ldap libg++ libwww logrotate mad mikmod mmx motif mp3 mpeg mysql ncurses nls nptl ogg openssl pam pcre pdflib perl png pppd python quicktime readline reflection ruby session spell spl sse sse2 ssl tcpd threads truetype truetype-fonts type1-fonts udev unicode utf8 vhosts vorbis xml xmms xorg zlib elibc_glibc kernel_linux linguas_de userland_GNU" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
I also have this chdir problem with 3.0.22-r3, but creating that directory does not solve the problem for me.
duh, I need /usr/share/doc/samba-3.0.22-r3/swat but of course, still have all the missing html and images
A stainy workaround is #--------------------- cd /tmp tar xzvf /usr/portage/distfiles/ samba-3.0.22/swat cp -a samba-3.0.22swat /usr/share/doc/samba-3.0.22 #--------------------- that at least worked for me, the stain is obviously the fact that i have to do it myself. but maybe - you'll never know - there will be a friendly maintainer of this package, who puts this into the ebuild ;)
Maybe I don't understand. Per upstream devs design, docs and swat are tightly matched. So, if you don't use the 'doc' use flag, you miss something of swat also. Could you please try with 'USE="doc swat" emerge -av samba'? If the result is good for you, put the line 'net-fs/samba doc swat' in /etc/portage/package.use. Else, tell me what I didn't understand... :-)
thanks for answering. I didn't do it, but i tell you that it'll probably work from what i read from the ebuild file. i don't want doc but swat nevertheless and there is the before mentioned folder on which swat depends, it includes some of the files an if it fails to do so there is an ugly page plus error messages telling me at first that it can't cd to such and such relative dir. after strace'ing i found out that that the dir in question is /usr/share/doc/samba-3.0.22-r3/swat/ first i just created it, but after that it couldn't find the files needed so i looked for these files in the distfile and copied them. ...and voila it worked. this now only has to be done in the ebuild. in my opinion line 266 of samba-3.0.22-r3.ebuild shouldn't be depending on USE="doc" but only on USE="swat"
I don't use swat myself, so I need someone to provide me a minimal list of file/dirs that are required. From the sources, it is not clear how to separate docs and swat. In the ebuild the behaviour of the use flags is: doc: swat is included (in the sense that doc==swat+something) -doc +swat: only swat is (should be?) retained -doc -swat: what you've already experimented More infos and/or patches to the ebuilds are welcome. :-)
oh my god, i just found that i truly embarrassed myself: equery uses told me that use ist indeed "-doc -swat". i looked at the ebuild and couldn't find anything wrong with it. sh> USE="swat" emerge samba and whatever you want should just work fine the before-last line is for giggles who apparently made a similar mistake
It's not the swat USE flag. I already have +swat, but -doc. I imagine it is the -doc that is the problem. Everything in the source tarball under swat/ needs to be copied to /usr/share/doc/samba-<version>
It's not the swat USE flag. I already have +swat, but -doc. I imagine it is the -doc that is the problem. Everything in the source tarball under swat/ needs to be copied to /usr/share/doc/samba-<version>. I think these files should be installed always with +swat, irregardles of the doc flag. While the files get stored under /usr/share/doc, they are the html files and images that swat uses to actually run, and cannot function without. They are not optional for swat.It seems to me having +swat should imply that swat can actually run.
oh maybe _i'm_ confused. i installed samba a few times on that system (for i ran into that problem), i fixed it manually in the end and it is in production now so i can't really contribute, anymore. until i have to build something similar.
OK nevermind I don't know what the problem is. I just emerged 3.0.23 with +swat and +doc and the files /still/ do not get installed under /usr/share/doc/samba-3.0.23/
@giggles1: if you look at the ebuild, you see that "-doc +swat" removes non critical parts of swat (./help/{guide,howto,devel} and ./using_samba only): see lines from 260 in samba-3.0.23.ebuild. Patches (or indication of what is exactly needed by swat) welcome.
I personally use "+doc -swat", and all the files you mentioned are in place. (but the -swat doesn't change anything in this case)
OK, something is removing them after they are installed, but I do not know what. Here is what I did: (1) Change ebuild, comment out the following: #if ! use doc; then # if ! use swat; then # rm -rf ${D}/usr/share/doc/${PF}/swat # else # rm -rf ${D}/usr/share/doc/${PF}/swat/help/{guide,howto,devel} # rm -rf ${D}/usr/share/doc/${PF}/swat/using_samba # fi #fi (2) emerge with +swat and +doc: # USE="doc" emerge samba -pv These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-fs/samba-3.0.23 USE="cups doc mysql pam postgres python readline swat xml -acl -async -automount -examples -kerberos -ldap -ldapsam -libclamav -oav -quotas -syslog -winbind" 0 kB (3) I can see the build installs the html, image files, etc (4) but then it STILL removes them, even tho +doc is set and the above parts of the ebuild are commented out: >>> Merging net-fs/samba-3.0.23 to / * Removing /usr/share/info * Removing /usr/share/doc The result that there is nothing under the doc directory. With +doc and the modified ebuild I dont see why doc is getting cleaned out.
Ok: I need more info. Could you attach the file resulting from: "# emerge -v samba | tee <file_to_attach.log>" ?
I believe this is the same problem that i was having, that i have managed to resolve. In more detail, if SWAT is set up as in the manpage, trying to connect to it (http://localhost:901) results in a 500 error with text saying that the server is malconfigured - chdir failed (or something like that). I resolved this issue by re-emerging samba with the swat USE flag enabled. This installed the necessary swat support files. The swat binary ( /usr/sbin/swat ) & xinitd definition ( /etc/xinitd.d/swat ) appears to be installed by default, but not the swat support files ( /usr/share/doc/samba-3.0.22-r3/swat ). This results in swat appearing to be available, but not actually being fully installed. I have updated a Gentoo HOW-TO guide to make explicit mention of the swat USE flag. I recommend that without the swat use flag, neither the swat binary nor the swat xinitd should be installed. This is my first post to this forum - if there is a better place to make this recommendation, could somebody please tell me where ( polite suggestions only, please... ;).
Sorry, i didn't notice the earlier entries...
I had doc and swat in my use flags and it was still removing the docs. Removing nodoc from features in make.conf fixed it.
if you have USE=-swat, then samba-3.0.23d will remove the swat binary and xinetd config file
