Port lang/ruby19 broken on 8-STABLE amd64 by r362982

Terry Kennedy TERRY at tmk.com
Tue Jul 29 08:20:59 UTC 2014


  The recent commit of r362982 breaks the lang/ruby19 port on (at least)
8-STABLE amd64. The port builds properly, but when portupgrade tries to
install the new version, it fails as follows:

--->  Installing the new version via the port
===>  Building package for ruby-1.9.3.547,1
Creating package /usr/ports/lang/ruby19/work/pkg/ruby-1.9.3.547,1.tbz
Registering depends: libexecinfo-1.1_3 libffi-3.0.13_1 readline-6.3.6_1 indexinfo-0.2 openssl-1.0.1_13 libyaml-0.1.6.
Creating bzip'd tar ball in '/usr/ports/lang/ruby19/work/pkg/ruby-1.9.3.547,1.tbz'
tar: /usr/local/share/ri/1.9/system/ACL/ACLEntry/cdesc-ACLEntry.ri: Cannot stat: No such file or directory
tar: /usr/local/share/ri/1.9/system/ACL/ACLEntry/dot_pat-i.ri: Cannot stat: No such file or directory
tar: /usr/local/share/ri/1.9/system/ACL/ACLEntry/dot_pat_str-i.ri: Cannot stat: No such file or directory
tar: /usr/local/share/ri/1.9/system/ACL/ACLEntry/match-i.ri: Cannot stat: No such file or directory

  and continues on that way for many, many lines. It then concludes with:

tar: /usr/local/share/ri/1.9/system/Zlib: Cannot stat: No such file or directory
tar: /usr/local/share/ri/1.9/system/fatal: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** Error code 1

Stop in /usr/ports/lang/ruby19.
*** Error code 1

Stop in /usr/ports/lang/ruby19.
*** Error code 1

Stop in /usr/ports/lang/ruby19.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20140729-42362-11tiaon env UPGRADE_TOOL=portupgrade UPGRADE_PORT=ruby-1.9.3.484_2,1 UPGRADE_PORT_VER=1.9.3.484_2,1 make reinstall
--->  Restoring the old version
tar: man/man1/erb19.1.gz: Cannot stat: No such file or directory
tar: man/man1/irb19.1.gz: Cannot stat: No such file or directory
tar: man/man1/ri19.1.gz: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.

  I waited a few days to report this, figuring someone else would, but it
appears not.

  This may be related to other ports I have installed; I can send you a
complete pkg_info list if that would be helpful.

        Terry Kennedy             http://www.tmk.com
        terry at tmk.com             New York, NY USA


More information about the freebsd-ruby mailing list