ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Alexey Rusakov <ktirf@altlinux.ru>
To: devel@lists.altlinux.org
Subject: Re: [devel] anjuta2-2.2.2-alt1: i586 rebuild failed
Date: Tue, 20 Nov 2007 00:57:11 +0300
Message-ID: <20071120005711.37ede718@mission> (raw)
In-Reply-To: <20071119195644.BD62C28232@hint1.office.altlinux.org>

On Mon, 19 Nov 2007 22:56:44 +0300 (MSK)
QA Team Robot wrote:

> find-requires: running scripts (files,lib,pam,perl,pkgconfig,pkgconfiglib,python,shebang,shell,static,symlinks)
> /usr/src/tmp/anjuta2-buildroot/usr/share/anjuta/tools/find-fixmes.pl syntax OK
> /usr/src/tmp/anjuta2-buildroot/usr/share/anjuta/tools/prepare-changelog.pl syntax OK
> /usr/src/tmp/anjuta2-buildroot/usr/share/anjuta/tools/translation-status.pl syntax OK
> python.req: ERROR: /usr/src/tmp/anjuta2-buildroot/usr/share/anjuta/project/python/src/main.py: invalid syntax (line 1)
> Traceback (most recent call last):
>   File "/usr/lib/rpm/python.req.py", line 173, in ?
>     lis = parser.suite('\n'.join(lines)+'\n').tolist(line_info=1)
>   File "<string>", line 1
>     [+ autogen5 template +]
>                        ^
> SyntaxError: invalid syntax
> error: /bin/sh failed
> error: Failed to find Requires
> 
> RPM build errors:
>     /bin/sh failed
>     Failed to find Requires
> Command exited with non-zero status 1
> 333.98user 96.01system 7:49.76elapsed 91%CPU (0avgtext+0avgdata 0maxresident)k
> 0inputs+0outputs (47major+32305040minor)pagefaults 0swaps
> hsh-rebuild: rebuild of `anjuta2-2.2.2-alt1.src.rpm' failed.
> Command exited with non-zero status 1
Эххх, не настоящий это скрипт на Питоне, а только шаблон для него. Что
сделать, чтобы файлы в %buildroot%_datadir/anjuta/project/python
игнорировались python.req'ом?

-- 
  Alexey "Ktirf" Rusakov
  ALT Linux, project manager


       reply	other threads:[~2007-11-19 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 21:57 ` Alexey Rusakov [this message]
2007-11-20  2:02   ` Alexey Tourbin

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=20071120005711.37ede718@mission \
    --to=ktirf@altlinux.ru \
    --cc=devel@lists.altlinux.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

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