git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Missing RPM spec file in tarball

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 9, 2016, 16:42 UTC
Message-ID
<xmqq37l9dnyd.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<4c42a1f4-4f03-0fdf-8bd2-8a7f1f978073@accelya.com>
Sergio Martín Turiel <sergio.martin@accelya.com> writes:
Show 7 quoted lines
>  I am trying to build RPM packages from tarball (release 2.9.3 and
> 2.10.0), and i do not find git.spec file, in previous releases i can
> found it (e.g. 2.8.3).
>
> O.S.: CentOS 7.2
> Command: rpmbuild -ta git-2.9.3.tar.gz
> Response: error: Failed to read spec file from git-2.9.3.tar.gz

Since ab214331 ("Makefile: stop pretending to support rpmbuild", 2016-04-04) that is used in Git 2.9 and later, i.e.

    Makefile: stop pretending to support rpmbuild
    
    Nobody in the active development community seems to watch breakages
    in the rpmbuild target.  As most major RPM based distros use their
    own specfile when packaging us, they aren't looking after us as
    their pristine upstream tree, either.  At this point, it is turning
    to be a disservice to the users to pretend that our tree natively
    supports "make rpmbuild" target when we do not properly maintain it.
    
    Signed-off-by: Junio C Hamano <gitster@pobox.com>

we no longer ship an outdated git.spec and git.spec.in files. This was done after finding out that nobody noticed that git.spec has been left broken since around Git 2.8.0 (i.e. we stopped shipping README without adjusting the reference to it from the git.spec file).

Previous: Sergio Martín TurielNext: Stefan Beller
Message 2 of 5 in “Missing RPM spec file in tarball”
  1. Sergio Martín TurielSep 9, 2016
  2. Junio C HamanoSep 9, 2016
  3. Stefan BellerSep 9, 2016
  4. Johannes SchindelinSep 10, 2016
  5. Stefan BellerSep 11, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.