From nobody Tue Jun 22 22:52:18 2021 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D4FB511D1D21 for ; Tue, 22 Jun 2021 22:52:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4G8hVV5Skvz4cBb for ; Tue, 22 Jun 2021 22:52:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A418B19770 for ; Tue, 22 Jun 2021 22:52:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 15MMqI8d060783 for ; Tue, 22 Jun 2021 22:52:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 15MMqIMP060782 for ports-bugs@FreeBSD.org; Tue, 22 Jun 2021 22:52:18 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 255683] math/maxima fails to install due to strange staging error Date: Tue, 22 Jun 2021 22:52:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: russo@bogodyn.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255683 --- Comment #23 from russo@bogodyn.org --- Bingo. I see where this is happening now. The configure script for maxima has this: ' if test x"${git_found}" =3D xtrue; then # Test to see if git describe works (discarding any output). If # it works, use it. Otherwise, keep existing value of VERSION. # (git describe fails if git is executed in a non-Git directory, e.g., # an unpacked tarball. Since the exit codes of git describe are undocumented , # we cannot distinguish that from a missing annotated tag. # Play it safe by refusing to change VERSION.) if git describe > /dev/null 2>&1; then VERSION=3D"`git describe --dirty`" # When building RPMs, hyphens in the version are not allowed, so # replace them with underscores. VERSION=3D`echo $VERSION | sed 's;-;_;g'` fi fi And guess what "git describe --dirty" outputs: 10-eol-90770-g4226927ef6b6 (this is, of course, a ports tree that has been updated since my last post = to this thread). And this little mess is coming from THIS cute little bit of configure.ac: dnl See if git exists. If it does, update VERSION to include a git tag AC_CHECK_PROG(git_found, git, true, false) if test x"${git_found}" =3D xtrue; then # Test to see if git describe works (discarding any output). If # it works, use it. Otherwise, keep existing value of VERSION. # (git describe fails if git is executed in a non-Git directory, e.g., # an unpacked tarball. Since the exit codes of git describe are undocumented, # we cannot distinguish that from a missing annotated tag. # Play it safe by refusing to change VERSION.) if git describe > /dev/null 2>&1; then VERSION=3D"`git describe --dirty`" # When building RPMs, hyphens in the version are not allowed, so # replace them with underscores. VERSION=3D`echo $VERSION | sed 's;-;_;g'` fi fi This is deliberately setting VERSION to a string that represents how many commits there have been since the last tag in the history, the name of that tag, and the git sha of the current commit. Somehow, this is not happening for you, but it is *definitely* happening for me.=20=20 If git were not found, or if "git describe" didn't work, this wouldn't be a problem, as it would not clobber VERSION at all. Now, why VERSION is being used to name staging directories and using git to= get the VERSION value is a question I can't answer. But perhaps a patch that took this bit out of configure.ac and configure, so that git is never used to get VERSION during package/port creation would be reasonable? --=20 You are receiving this mail because: You are the assignee for the bug.=