unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, 63435@debbugs.gnu.org
Cc: iyzsong@envs.net
Subject: [bug#63435] Add vcmi 1.2.1 to games.scm
Date: Mon, 15 May 2023 12:07:06 -0700	[thread overview]
Message-ID: <87353xmn1h.fsf@wireframe> (raw)
In-Reply-To: <16d133f8d31322aee3bb5cea5baff6fc03fc95ca.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

On 2023-05-15, Liliana Marie Prikler wrote:
> Am Sonntag, dem 14.05.2023 um 12:52 -0700 schrieb Vagrant Cascadian:
>> Also applied. Used "fuzzylite" for XXX...
> Is the failure due to fuzzylite?  Actually, XXX is a marker for
> incomplete code like TODO.

I would be fine with prefixing it with TODO or whatever else makes
sense!

... although to make any sense out of this, a little more background ...

I am fairly sure I successfully built with qtbase@6 and qttools@6 in
earlier iterations while developing the initial patch... but at the time
of the original patch submission, qtbase@6 itself was failing to build,
which is why i switched to qtbase@5 ... but whatever made qtbase@6 build
successfully now fails to build vcmi!

Whee.

So the original comment was arguably confusing and the need to even have
a comment at all has since entirely changed context (e.g. went from
qtbase@6 failing to build to vcmi failing to build with qtbase@6)!

I am not entirely sure that makes any more sense now, but I have some
small hope. :)


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2023-05-15 19:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  5:43 [bug#63435] Add vcmi 1.2.1 to games.scm Vagrant Cascadian
2023-05-11 17:17 ` Liliana Marie Prikler
2023-05-11 21:48   ` Vagrant Cascadian
2023-05-11 23:07     ` Vagrant Cascadian
2023-05-12  1:47       ` Liliana Marie Prikler
2023-05-12  6:17         ` Vagrant Cascadian
2023-05-12 20:53           ` Liliana Marie Prikler
2023-05-13  1:33             ` Vagrant Cascadian
2023-05-13  1:35               ` Vagrant Cascadian
2023-05-13  6:16                 ` Liliana Marie Prikler
2023-05-14 19:52                   ` Vagrant Cascadian
2023-05-15 18:31                     ` Liliana Marie Prikler
2023-05-15 19:07                       ` Vagrant Cascadian [this message]
2023-07-03  2:50                       ` Vagrant Cascadian
2023-07-09  5:36                         ` bug#63435: " Liliana Marie Prikler
2023-05-13  6:12               ` [bug#63435] " Liliana Marie Prikler
2023-05-14 19:50                 ` Vagrant Cascadian

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=87353xmn1h.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=63435@debbugs.gnu.org \
    --cc=iyzsong@envs.net \
    --cc=liliana.prikler@gmail.com \
    /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).