Date: Wed, 18 Apr 2018 03:24:44 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 227600] porter's handbook: use of distinfo Message-ID: <bug-227600-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227600 Bug ID: 227600 Summary: porter's handbook: use of distinfo Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: freebsd@dreamchaser.org If you have a distinfo file that does not match the tarball you are attempt= ing to fetch, the ports mechanism fails fetching the tarball with the following misleading message: =3D> nufraw-0.41.tar.gz is not in /hd2/home/garya/Computing/ports/graphics/nufraw/distinfo. =3D> Either /hd2/home/garya/Computing/ports/graphics/nufraw/distinfo is out= of date, or =3D> nufraw-0.41.tar.gz is spelled incorrectly. In the general description of the fetch phase, it should mention that if a distinfo file is present, it *must* match the tarball being fetched. I had= the impression distinfo was only used after the tarball was fetched, during the extract phase. When upgrading a port it's easy to forget there is already a distinfo lying around. --=20 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-227600-7788>