Jump to content
funtoo forums
  • 0
ottembomb

samba installation fails, due to manpage?

Question

Good evening!

 

After a bit of a rocky transition to kits, I'm running into a problem while upgrading samba

[2619/2724] Generating manpages/smb.conf.5
20:46:10 runner  XML_CATALOG_FILES="file:///etc/xml/catalog file:///usr/local/share/xml/catalog file:///mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/work/samba-4.7.0-abi_x86_64.amd64/bin/default/docs-xml/build/catalog.xml"                                     export XML_CATALOG_FILES                                     /usr/bin/xsltproc --xinclude --stringparam noreference 0 -o default/docs-xml/manpages/smb.conf.5.xml --nonet /mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/work/samba-4.7.0-abi_x86_64.amd64/docs-xml/xslt/expand-sambadoc.xsl /mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/work/samba-4.7.0-abi_x86_64.amd64/docs-xml/manpages/smb.conf.5.xml                                     /usr/bin/xsltproc --nonet -o default/docs-xml/manpages/smb.conf.5 /mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/work/samba-4.7.0-abi_x86_64.amd64/docs-xml/xslt/man.xsl default/docs-xml/manpages/smb.conf.5.xml
runtime error: file file:///usr/share/sgml/docbook/xsl-stylesheets/lib/lib.xsl line 58 element choose
xsltApplySequenceConstructor: A potential infinite template recursion was detected.
You can adjust xsltMaxDepth (--maxdepth) in order to raise the maximum number of nested template calls and variables/params (currently set to 3000).
Templates:
#0 name string.subst
#1 name string.subst
#2 name string.subst
#3 name string.subst
#4 name string.subst
#5 name string.subst
#6 name string.subst
#7 name string.subst
#8 name string.subst
#9 name string.subst
#10 name string.subst
#11 name string.subst
#12 name string.subst
#13 name string.subst
#14 name string.subst
Variables:
#0
replacement
target
string
#1
target
string
#2
string
#3
replacement
target
string
#4
target
string
#5
string
#6
replacement
target
string
#7
target
string
#8
string
#9
replacement
target
string
#10
target
string
#11
string
#12
replacement
target
string
#13
target
string
#14
string
error: file default/docs-xml/manpages/smb.conf.5.xml
xsltRunStylesheet : run failed
Waf: Leaving directory `/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/work/samba-4.7.0-abi_x86_64.amd64/bin'
Build failed:  -> task failed (err #11):
        {task: manpages/smb.conf.5 smb.conf.5.xml,parameters.all.xml -> smb.conf.5}
 * ERROR: net-fs/samba-4.7.0-r1::net-kit failed (compile phase):
 *   build failed
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_compile
 *   environment, line 4585:  Called multilib-minimal_src_compile
 *   environment, line 2885:  Called multilib_foreach_abi 'multilib-minimal_abi_src_compile'
 *   environment, line 3116:  Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
 *   environment, line 2751:  Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
 *   environment, line 2749:  Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile'
 *   environment, line  503:  Called multilib-minimal_abi_src_compile
 *   environment, line 2879:  Called multilib_src_compile
 *   environment, line 3328:  Called waf-utils_src_compile
 *   environment, line 5569:  Called die
 * The specific snippet of code:
 *       "${WAF_BINARY}" ${_mywafconfig} ${jobs} || die "build failed"
 *
 * If you need support, post the output of `emerge --info '=net-fs/samba-4.7.0-r1::net-kit'`,
 * the complete build log and the output of `emerge -pqv '=net-fs/samba-4.7.0-r1::net-kit'`.
 * The complete build log is located at '/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/temp/build.log'.
 * The ebuild environment file is located at '/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/temp/environment'.
 * Working directory: '/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/work/samba-4.7.0-abi_x86_64.amd64'
 * S: '/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/work/samba-4.7.0'

>>> Failed to emerge net-fs/samba-4.7.0-r1, Log file:

>>>  '/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/temp/build.log'

 * Messages for package net-fs/samba-4.7.0-r1:

 * ERROR: net-fs/samba-4.7.0-r1::net-kit failed (compile phase):
 *   build failed
 *
 * Call stack:
 *     ebuild.sh, line  115:  Called src_compile
 *   environment, line 4585:  Called multilib-minimal_src_compile
 *   environment, line 2885:  Called multilib_foreach_abi 'multilib-minimal_abi_src_compile'
 *   environment, line 3116:  Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
 *   environment, line 2751:  Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
 *   environment, line 2749:  Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile'
 *   environment, line  503:  Called multilib-minimal_abi_src_compile
 *   environment, line 2879:  Called multilib_src_compile
 *   environment, line 3328:  Called waf-utils_src_compile
 *   environment, line 5569:  Called die
 * The specific snippet of code:
 *       "${WAF_BINARY}" ${_mywafconfig} ${jobs} || die "build failed"
 *
 * If you need support, post the output of `emerge --info '=net-fs/samba-4.7.0-r1::net-kit'`,
 * the complete build log and the output of `emerge -pqv '=net-fs/samba-4.7.0-r1::net-kit'`.
 * The complete build log is located at '/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/temp/build.log'.
 * The ebuild environment file is located at '/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/temp/environment'.
 * Working directory: '/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/work/samba-4.7.0-abi_x86_64.amd64'
 * S: '/mnt/rwstorage/var/tmp/portage/net-fs/samba-4.7.0-r1/work/samba-4.7.0'

after a bit of searching, i came across this bug link:

 

https://bugzilla.redhat.com/show_bug.cgi?id=1491307

 

Should I file a bug about this, or will the fix come from upstream?

 

 

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

Patched and fixed in gentoo docbook-xsl-stylesheets-1.79.1-r2.ebuild
 
Local patch fix for current funtoo docbook-xsl-stylesheets-1.79.1-r1
Install localpatches foobashrc: http://www.funtoo.org/Applying_Local_Patches_to_Ebuilds
Download nonrecursive-string-subst.patch

# mkdir -p /etc/portage/localpatches/app-text/docbook-xsl-stylesheets
# cp nonrecursive-string-subst.patch /etc/portage/localpatches/app-text/docbook-xsl-stylesheets
# emerge -1 docbook-xsl-stylesheets

Verify patch was applied :

>>> Unpacking source...
>>> Unpacking docbook-xsl-1.79.1.tar.bz2 to /var/tmp/portage/app-text/docbook-xsl-stylesheets-1.79.1-r1/work
>>> Source unpacked in /var/tmp/portage/app-text/docbook-xsl-stylesheets-1.79.1-r1/work
>>> Applying local patches ...
 [32;01m*[0m Applying nonrecursive-string-subst.patch [localpatch] ...

Samba will now complete build/install:

emerge -av samba

Reference:
https://bugs.gentoo.org/488168
https://bugzilla.samba.org/show_bug.cgi?id=9515

Share this post


Link to post
Share on other sites
  • 0
On 10/8/2017 at 12:16 AM, Oleg Vinichenko said:

this is fixed 2 days ago

Hey Oleg!

Thanks for this important bit. I was just struggling with exactly this problem, although I had synchronized my kits earlier today. However, I had to add the ~amd64 so that emerge finally picked it up. Perhaps the samba target should be updated to refer to >docbook-xsl-stylesheets-1.79.1-r1 in their dependencies?

I'm so glad it unblocked the upgrade... I took a loonnnng time to finally converge to a full working build on kits. Looking forward to reaping the benefits!

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...