Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Jul 2014 03:30:09 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 192283] New: irc/epic4 fails to fetch (tries to look in distinfo for tarball, not distfiles)
Message-ID:  <bug-192283-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192283

            Bug ID: 192283
           Summary: irc/epic4 fails to fetch (tries to look in distinfo
                    for tarball, not distfiles)
           Product: Ports Tree
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: jdc@koitsu.org

I'm not sure what is going on here.  This is very uncomfortable -- look very
closely at the error message (how it's attempting to look for the tarball
within the actual port distinfo file (?!?!), rather than /usr/ports/distfiles
(a directory):

root@icarus:/usr/ports/irc/epic4 # make clean
===>  Cleaning for epic4-2.10.5

root@icarus:/usr/ports/irc/epic4 # make fetch
===>  License BSD3CLAUSE accepted by the user
===>  Found saved configuration for epic4-2.10.5
===>   epic4-2.10.5 depends on file: /usr/local/sbin/pkg - found
=> epic4-2.10.5.tar.gz is not in /usr/ports/irc/epic4/distinfo.
=> Either /usr/ports/irc/epic4/distinfo is out of date, or
=> epic4-2.10.5.tar.gz is spelled incorrectly.
*** [do-fetch] Error code 1

Stop in /usr/ports/irc/epic4.

I haven't figured out exactly what's wrong here (nothing in the Makefile stands
out) and this is the only port which does this.  But it's 100% reproducible on
two separate RELENG_9 boxes with completely different hardawre, both with ports
SVN r363529 (latest as of this PR).

I should note at some point in the semi-recent past this port did work
correctly, so my gut feeling is that someone broke something within the Mk/
framework.

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192283-13>