git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "MichaelTiloDressel@t-online.de" <MichaelTiloDressel@t-online.de>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.4-rc4
Date: Mon, 21 Jan 2008 03:33:37 -0800	[thread overview]
Message-ID: <7vy7ajxvji.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1JGuDL-2AugiG0@fwd26.aul.t-online.de> (MichaelTiloDressel@t-online.de's message of "Mon, 21 Jan 2008 11:49:15 +0100")

"MichaelTiloDressel@t-online.de"
<MichaelTiloDressel@t-online.de> writes:

> Concerning RPM specs.
>
> I created rpm packages on a x86_64 SuSE 10.3 system.
>
> There were two complains about unmatched dependencies for expat-devel
> and perl(Error)
> I could not get rid off.

Thanks.

perl-error and expat-devel are both packaged outside git.
Aren't they listed in dependencies?  At least I think
expat-devel is on the build dependency.

Our Makefile tries to install our own copy of perl::Error if the
build platform does not have one, which we do not want to do
when building a binary package.  Perhaps perl-error needs to be
on the build dependency to deal with this issue?  I dunno, as I
am not an RPM person.

  reply	other threads:[~2008-01-21 11:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 10:49 [ANNOUNCE] GIT 1.5.4-rc4 MichaelTiloDressel
2008-01-21 11:33 ` Junio C Hamano [this message]
2008-01-21 13:16   ` MichaelTiloDressel
  -- strict thread matches above, loose matches on Subject: below --
2008-01-12  7:11 [ANNOUNCE] GIT 1.5.4-rc3 Junio C Hamano
2008-01-21  2:37 ` [ANNOUNCE] GIT 1.5.4-rc4 Junio C Hamano
     [not found]   ` <7vsl0r3nvc.fsf-jO8aZxhGsIagbBziECNbOZn29agUkmeCHZ5vskTnxNA@public.gmane.org>
2008-01-21 22:22     ` Steffen Prohaska
     [not found]       ` <BB330DC7-9F38-4D41-85A2-D475701B6083-wjoc1KHpMeg@public.gmane.org>
2008-01-22  1:21         ` Johannes Schindelin
     [not found]           ` <alpine.LSU.1.00.0801220121300.5731-OGWIkrnhIhzN0uC3ymp8PA@public.gmane.org>
2008-01-22  5:50             ` Steffen Prohaska

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vy7ajxvji.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=MichaelTiloDressel@t-online.de \
    --cc=git@vger.kernel.org \
    /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.
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 NNTP newsgroup(s).