From: Junio C Hamano <gitster@pobox.com>
To: "Sergio Martín Turiel" <sergio.martin@accelya.com>
Cc: git@vger.kernel.org
Subject: Re: Missing RPM spec file in tarball
Date: Fri, 09 Sep 2016 09:42:34 -0700 [thread overview]
Message-ID: <xmqq37l9dnyd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <4c42a1f4-4f03-0fdf-8bd2-8a7f1f978073@accelya.com> ("Sergio Martín Turiel"'s message of "Fri, 9 Sep 2016 18:19:38 +0200")
Sergio Martín Turiel <sergio.martin@accelya.com> writes:
> 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).
next prev parent reply other threads:[~2016-09-09 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 16:19 Missing RPM spec file in tarball Sergio Martín Turiel
2016-09-09 16:42 ` Junio C Hamano [this message]
2016-09-09 16:42 ` Stefan Beller
2016-09-10 8:15 ` Johannes Schindelin
2016-09-11 16:05 ` Stefan Beller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq37l9dnyd.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sergio.martin@accelya.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).