ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Michael Shigorin <mike@osdn.org.ua>
To: devel@altlinux.ru
Subject: [devel] Re: [Fwd: Re: vegastrike-data-0.4-alt1.src.rpm - cannot rebuild]
Date: Fri, 3 Oct 2003 12:56:10 +0300
Message-ID: <20031003095610.GR9068@osdn.org.ua> (raw)
In-Reply-To: <3F7B958E.6070307@sicex.ru>

On Thu, Oct 02, 2003 at 10:03:42AM +0700, Alexander Belov wrote:
> Помогите плз., что делать.

Read docs.altlinux.ru regarding package builds for Sisyphus.

;-]

> Понятно, что не понятно, причем тут я? На сколько я понимаю,
> rpm находит файлы питоновские и зачем-то пытается с ними
> чего-то сделать (откомпилить), а у вас видимо не стоит pyton

Heh.  Did you hear about hasher? (and build dependencies)

In short, you'd better add BuildRequires: python-devel at least,
or run "buildreq vegastrike.spec" starting with fresh Sisyphus
system to yield better result.

Regarding this exact situation, I'd suggest either sending fixed
spec to Stanislav or building nosrc.rpm not to re-upload the
whole body of unchanged data.

> У меня - все работает, а здесь, приведены какие-то действия rpm, о
> которых его в принципе то и не просили.

These are default on build servers and it's somewhat reasonable
to ask for proper build dependencies even without automated build
systems.

-- 
 ---- WBR, Michael Shigorin <mike@altlinux.ru>
  ------ Linux.Kiev http://www.linux.kiev.ua/


  parent reply	other threads:[~2003-10-03  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-02  3:03 [devel] " Alexander Belov
2003-10-02 10:49 ` Stanislav Ievlev
2003-10-03  9:56 ` Michael Shigorin [this message]
2003-10-03 10:55   ` [devel] " Alexander Belov
2003-10-03 11:13     ` Michael Shigorin
2003-10-03 17:14       ` Вячеслав Диконов
2003-10-04 13:40         ` Alexandre Prokoudine

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=20031003095610.GR9068@osdn.org.ua \
    --to=mike@osdn.org.ua \
    --cc=devel@altlinux.ru \
    /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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git