From: QA Team Upravdom Robot <upravdom@altlinux.org>
To: "Michael Shigorin (ALT Linux Team)" <mike@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org
Subject: E: incoming x86_64 reject: btrcv-0.2beta2-alt1
Date: Tue, 23 Dec 2008 20:14:06 +0300 (MSK)
Message-ID: <20081223171406.75220151C05B@granary.armor.altlinux.org> (raw)
Dear Michael Shigorin (ALT Linux Team)!
The btrcv-0.2beta2-alt1 package has been rejected from Sisyphus incoming
for x86_64 architecture.
Possible reason follows:
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for a Python interpreter with version >= 2.4... python
checking for python... /usr/bin/python
checking for python version... 2.5
checking for python platform... linux2
checking for python script directory... ${prefix}/lib64/python2.5/site-packages
checking for python extension module directory... ${exec_prefix}/lib64/python2.5/site-packages
checking for noarch-alt-linux-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for PYGTK... configure: error: Package requirements (pygtk-2.0) were not met.
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively you may set the PYGTK_CFLAGS and PYGTK_LIBS environment variables
to avoid the need to call pkg-config. See the pkg-config man page for
more details.
RPM build errors:
error: Bad exit status from /usr/src/tmp/rpm-tmp.6627 (%build)
Bad exit status from /usr/src/tmp/rpm-tmp.6627 (%build)
Command exited with non-zero status 1
0.26user 0.32system 0:01.69elapsed 35%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+82455minor)pagefaults 0swaps
hsh-rebuild: rebuild of `btrcv-0.2beta2-alt1.src.rpm' failed.
--
Rgrds, your upravdom
reply other threads:[~2008-12-23 17:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081223171406.75220151C05B@granary.armor.altlinux.org \
--to=upravdom@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=mike@altlinux.org \
--cc=sisyphus-incominger@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 Girar Builder robot reports
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus-incominger/0 sisyphus-incominger/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 sisyphus-incominger sisyphus-incominger/ http://lore.altlinux.org/sisyphus-incominger \
sisyphus-incominger@lists.altlinux.org sisyphus-incominger@lists.altlinux.ru sisyphus-incominger@lists.altlinux.com
public-inbox-index sisyphus-incominger
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus-incominger
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git