all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Adam Faiz <adam.faiz@disroot.org>
Cc: iyzsong@envs.net, Sharlatan Hellseher <sharlatanus@gmail.com>,
	maxim.cournoyer@gmail.com, 72589@debbugs.gnu.org,
	Eric Bavier <bavier@posteo.net>
Subject: [bug#72589] [PATCH] gnu: Add firebird-emu.
Date: Sun, 22 Sep 2024 10:50:29 +0200	[thread overview]
Message-ID: <Zu_aVRunZVbBIJri@jurong> (raw)
In-Reply-To: <856900d9-5995-cd04-bf8f-d08d8d64f461@disroot.org>

Hello,

(adding the Qt team in CC)

I have tried to build the package, but get a hash mismatch:
  expected hash: 0q8j2prs7713drwdgxwi1dhzk4gp9d908bx6p15fh5x2ffb676v6
  actual hash:   1ws8y38gmcg63zmq67sx1px21d0ssncgy6bmkn26471fl1854adw
hash mismatch for store item '/gnu/store/q6k9hx61c940akz8arwbh4v84jl3slpc-firebird-emu-1.6-checkout'
build of /gnu/store/x8mb0b752vrjqc68hwp80rfjnw8nkn0v-firebird-emu-1.6-checkout.drv failed

The description says that the package does not ship a ROM image, but
I suppose it can be used without one?

It is a bit unfortunate to introduce a package relying on Qt5 while I think
we are slowly moving towards Qt6.

Is it necessary to propagate qtdeclarative-5 and qtquickcontrols-5,
or could this be handled differently?

Finally I am not sure whether the license is gpl3 or gpl3+.
I did not find license headers in the source code, but this statement in
README.md:
"This work (except the icons from the KDE project) is licensed under the GPLv3."
So I think it might to safer to interpret this as GPLv3 only.

Andreas





      parent reply	other threads:[~2024-09-22  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12  7:13 [bug#72589] [PATCH] gnu: Add firebird-emu Adam Faiz via Guix-patches via
2024-08-15 22:44 ` Nicolas Graves via Guix-patches via
2024-09-22  8:50 ` Andreas Enge [this message]

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=Zu_aVRunZVbBIJri@jurong \
    --to=andreas@enge.fr \
    --cc=72589@debbugs.gnu.org \
    --cc=adam.faiz@disroot.org \
    --cc=bavier@posteo.net \
    --cc=iyzsong@envs.net \
    --cc=maxim.cournoyer@gmail.com \
    --cc=sharlatanus@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.