From: zimoun <zimon.toutoune@gmail.com>
To: Jesse Gibbons <jgibbons@byui.edu>
Cc: 42979@debbugs.gnu.org
Subject: bug#42979: Some kde games are outdated
Date: Mon, 05 Jul 2021 11:28:56 +0200 [thread overview]
Message-ID: <87mtr1kt2f.fsf@gmail.com> (raw)
In-Reply-To: <a37c94b8-4af5-7bc3-17d4-2b1fbcbe6ac8@byui.edu> (Jesse Gibbons's message of "Fri, 21 Aug 2020 15:33:28 -0600")
Hi,
On Fri, 21 Aug 2020 at 15:33, Jesse Gibbons <jgibbons@byui.edu> wrote:
> The following KDE games fail to build:
>
> kblocks
> kdiamond
> kigo
> klines
> kollision
> lskat
>
> The upstream git repositories all have tags for version 20.8.0, but there are
> no source tarballs in the mirrors.
Using Guix 3694c0d, the version is now 20.12.0 and
https://bordeaux.guix.gnu.org provides all the substitutes. Note that
“guix build --check” works fine too.
BTW, this
$ guix gc -D $(guix build <pkg> -S)
$ guix build <pkg> -S --no-substitutes
also works fine. In my case, downloading from
<http://download.kde.org/stable/release-service/>.
Indeed the sources of 20.8.0 does not seem available upstream.
However, this version was not in Guix, AFAIK. For instance,
git log --grep=kigo
does not display a commit updating from 19.08.3 to 20.8.0. The only
update is from 19.08.3 (d685f86054..f114a689e7) to 20.12.0
(908e48f7dd..3cd53b4500). The version 19.08.3 seems removed from
upstream but we cannot do more; this source is still on ci.guix.gnu.org
and should be transparently available via Disarchive.
Well, I am in favor to close this bug. WDYT?
All the best,
simon
next prev parent reply other threads:[~2021-07-05 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 21:33 bug#42979: Some kde games are outdated Jesse Gibbons via Bug reports for GNU Guix
2021-07-05 9:28 ` zimoun [this message]
2021-07-05 14:20 ` Jesse via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtr1kt2f.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=42979@debbugs.gnu.org \
--cc=jgibbons@byui.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).