From: Guillaume Le Vaillant <glv@posteo.net>
To: phodina <phodina@protonmail.com>
Cc: "53149@debbugs.gnu.org" <53149@debbugs.gnu.org>
Subject: [bug#53149] [PATCH v2 1/3] gnu: opencascade-occt: Update to 7.6.0.
Date: Fri, 28 Jan 2022 10:45:16 +0000 [thread overview]
Message-ID: <87y2302kp1.fsf@kitej> (raw)
In-Reply-To: <JbbsaV5axMU8dRjIqNgjFIkecqUJ9mBnzdxkwIjbbqwMIiCYZ5Z-oBCM4i4RPfBakNMzhBJ0LTS7jdCO_ostTMVYWxeBk0csSPOaVjx48Ao=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
phodina via Guix-patches via <guix-patches@gnu.org> skribis:
> From 64195144def5a3dfdd593494523dd44df39be6f0 Mon Sep 17 00:00:00 2001
> From: Petr Hodina <phodina@protonmail.com>
> Date: Sun, 9 Jan 2022 23:04:57 +0100
> Subject: [PATCH v2 2/3] gnu: kicad: Update to 6.0.1.
>
> * gnu/packages/engineering.scm (kicad): Update to 6.0.1.
> Applied guix style command.
> [native-inputs]: Remove kicad-i18n. Use new syntax.
> [inputs]: Add bash-minimal, gtk+ and use opencascade-occt instead of
> opencascade-oce. Use new syntax.
> [arguments]: Remove phase install-translations.
Hi,
If the kicad-i18n package is not used anymore, I guess its definition
can be removed.
Also, the kicad-doc, kicad-symbols, kicad-footprints, kicad-packages3d
and kicad-templates packages inherit their version number from the kicad
package. So when the version of the kicad package changes, their base32
hashes usually have to be updated, or they may fail to build.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-01-28 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 22:45 [bug#53149] Update Kicad to 6.0.0 phodina via Guix-patches via
2022-01-11 19:54 ` Leo Famulari
2022-01-28 10:11 ` [bug#53149] [PATCH v2 1/3] gnu: opencascade-occt: Update to 7.6.0 phodina via Guix-patches via
2022-01-28 10:45 ` Guillaume Le Vaillant [this message]
2022-02-09 11:12 ` [bug#53149] [PATCH v3 " phodina via Guix-patches via
2022-02-11 15:48 ` bug#53149: " Guillaume Le Vaillant
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=87y2302kp1.fsf@kitej \
--to=glv@posteo.net \
--cc=53149@debbugs.gnu.org \
--cc=phodina@protonmail.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.