From: Upravdom Team Robot <upravdom@altlinux.org>
To: "Vitaly Lipatov" <lav@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org
Subject: E: incoming x86_64 reject: audacious-plugins-1.4.1-alt1
Date: Wed, 28 Nov 2007 13:38:14 +0300 (MSK)
Message-ID: <20071128103814.D0A1628232@hint1.office.altlinux.org> (raw)
Dear Vitaly Lipatov!
The audacious-plugins-1.4.1-alt1 package has been rejected from incoming
for x86_64 architecture.
Possible reason follows:
checking for rm... /bin/rm
checking for mv... /bin/mv
checking for cp... /bin/cp
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for a BSD-compatible install... /bin/install -c
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for pkg-config... /usr/bin/pkg-config
checking for audacious >= 1.4.1... no
configure: error: Cannot find Audacious 1.4.1 or later, have you installed audacious yet?
error: Bad exit status from /usr/src/tmp/rpm-tmp.20530 (%build)
RPM build errors:
Bad exit status from /usr/src/tmp/rpm-tmp.20530 (%build)
Command exited with non-zero status 1
1.87user 0.88system 0:03.29elapsed 83%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+276000minor)pagefaults 0swaps
hsh-rebuild: rebuild of `audacious-plugins-1.4.1-alt1.src.rpm' failed.
--
Rgrds, your upravdom
reply other threads:[~2007-11-28 10:38 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=20071128103814.D0A1628232@hint1.office.altlinux.org \
--to=upravdom@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=lav@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