From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] FTBFS: rkt
Date: Sat, 06 Feb 2021 22:04:24 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28554@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
New issue by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/28554
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* package:
*rkt-1.30.0``
### Expected behavior
It to compile
### Actual behavior
https://void.johnnynator.dev/logs/openssl/x86_64/bad/rkt.txt
```
=> rkt-1.30.0_2: running do_build ...
stage1/rootfs.mk:20: stage1/usr_from_coreoskvmhostsrcfly/usr_from_coreoskvmhostsrcfly.mk: No such file or directory
make: *** No rule to make target 'stage1/usr_from_coreoskvmhostsrcfly/usr_from_coreoskvmhostsrcfly.mk'. Stop.
make: *** Waiting for unfinished jobs....
=> ERROR: rkt-1.30.0_2: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 2
=> ERROR: in do_build() at common/build-style/gnu-configure.sh:13
```
@thypon Do you have any needs for this package or plans to fix it?
The project is considered ended upstream and I would propose to just remove it from the Void repo.
next reply other threads:[~2021-02-06 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 21:04 Johnnynator [this message]
2021-02-14 22:34 ` thypon
2021-02-14 22:36 ` [ISSUE] [CLOSED] " Johnnynator
2021-02-18 21:26 ` ericonr
2021-02-19 13:54 ` thypon
2021-02-19 15:13 ` [ISSUE] [CLOSED] " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28554@inbox.vuxu.org \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).