From: Girar Builder awaiter robot <girar-builder@altlinux.org>
To: Igor Vlasenko <viy@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org
Subject: [#199373] FAILED srpm=fonts-type1-ctan-kerkis-2.0-alt2_33.src.rpm
Date: Sun, 4 Feb 2018 02:51:06 +0000
Message-ID: <20180204025106.GA30063@gyle.altlinux.org> (raw)
http://git.altlinux.org/tasks/199373/logs/events.1.1.log
2018-Feb-04 02:50:39 :: task #199373 for sisyphus started by viy:
#100 build fonts-type1-ctan-kerkis-2.0-alt2_33.src.rpm
2018-Feb-04 02:50:39 :: [i586] #100 fonts-type1-ctan-kerkis-2.0-alt2_33.src.rpm: build start
2018-Feb-04 02:50:39 :: [x86_64] #100 fonts-type1-ctan-kerkis-2.0-alt2_33.src.rpm: build start
+ ln -sf /usr/share/fonts/type1/ctan-kerkis/Kerkis-Bold.pfb '/usr/src/tmp/fonts-type1-ctan-kerkis-buildroot%{texfonts}/type1/%{texfontpath}/Kerkis-Bold.pfb'
ln: failed to create symbolic link '/usr/src/tmp/fonts-type1-ctan-kerkis-buildroot%{texfonts}/type1/%{texfontpath}/Kerkis-Bold.pfb': No such file or directory
error: Bad exit status from /usr/src/tmp/rpm-tmp.67456 (%install)
2018-Feb-04 02:51:04 :: [x86_64] fonts-type1-ctan-kerkis-2.0-alt2_33.src.rpm: remote: build failed
2018-Feb-04 02:51:04 :: [x86_64] #100 fonts-type1-ctan-kerkis-2.0-alt2_33.src.rpm: build FAILED
+ ln -sf /usr/share/fonts/type1/ctan-kerkis/Kerkis-Bold.pfb '/usr/src/tmp/fonts-type1-ctan-kerkis-buildroot%{texfonts}/type1/%{texfontpath}/Kerkis-Bold.pfb'
ln: failed to create symbolic link '/usr/src/tmp/fonts-type1-ctan-kerkis-buildroot%{texfonts}/type1/%{texfontpath}/Kerkis-Bold.pfb': No such file or directory
error: Bad exit status from /usr/src/tmp/rpm-tmp.76972 (%install)
2018-Feb-04 02:51:06 :: [i586] fonts-type1-ctan-kerkis-2.0-alt2_33.src.rpm: remote: build failed
2018-Feb-04 02:51:06 :: [i586] #100 fonts-type1-ctan-kerkis-2.0-alt2_33.src.rpm: build FAILED
2018-Feb-04 02:51:04 :: [x86_64] build FAILED
2018-Feb-04 02:51:06 :: [i586] build FAILED
2018-Feb-04 02:51:06 :: task #199373 for sisyphus FAILED
reply other threads:[~2018-02-04 2:51 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=20180204025106.GA30063@gyle.altlinux.org \
--to=girar-builder@altlinux.org \
--cc=sisyphus-incominger@lists.altlinux.org \
--cc=viy@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