From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Leo Famulari <leo@famulari.name>
Cc: "45573@debbugs.gnu.org" <45573@debbugs.gnu.org>
Subject: [bug#45573] [PATCH] Correct freecad runtime errors
Date: Mon, 04 Jan 2021 12:01:54 +0000 [thread overview]
Message-ID: <Oe__3Ny5SaWMP4SWAS96Z2IDkouevOqHAQkRj9H5qFT7FSL-JoYJ3HYVtgvCFPMyjzU7jLdJoiRPKB3DeYNxnVnoAb1JBgKjl9kMJ2hu00s=@elenq.tech> (raw)
In-Reply-To: <X/JdsJDnCzQGYJGd@jasmine.lan>
Hi Leo,
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, January 4, 2021 1:13 AM, Leo Famulari <leo@famulari.name> wrote:
>
> > - ;; Delete references to packaging tool cpack
> >
> >
> > - (substitute* "CMakeLists.txt"
> >
> >
> > - ((".*cpack.d.*") ""))
> >
> >
> > - #t))))
> >
> >
>
> I still did not understand the reason for this substitution. I tried
> building without it and found that the build is broken, so I added this
> info to the comment.
>
> Can you report it upstream? It seems like something that all
> distributors would benefit from.
I think it's related with packaging. But I'm not sure neither.
Guys at Nix do the same and remove that line. I tried to leave it
and it doesn't work. I'll try to report upstream.
> > Subject: [PATCH 2/6] gnu: Add soqt.
> >
> > * gnu/packages/qt.scm (soqt): New variable.
> >
>
> I pushed these first two patches as
> a5f13705cb9261ab66bdf73d1fb4a832714feb31
>
> Comments on the others to follow...
Thanks!
next prev parent reply other threads:[~2021-01-04 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 18:47 [bug#45573] [PATCH] Correct freecad runtime errors Ekaitz Zarraga
2020-12-31 22:36 ` Leo Famulari
2020-12-31 23:23 ` Ekaitz Zarraga
2021-01-01 14:37 ` Ekaitz Zarraga
2021-01-04 0:13 ` Leo Famulari
2021-01-04 12:01 ` Ekaitz Zarraga [this message]
2021-01-04 0:18 ` Leo Famulari
2021-01-04 12:15 ` Ekaitz Zarraga
2021-01-04 20:12 ` bug#45573: " Leo Famulari
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='Oe__3Ny5SaWMP4SWAS96Z2IDkouevOqHAQkRj9H5qFT7FSL-JoYJ3HYVtgvCFPMyjzU7jLdJoiRPKB3DeYNxnVnoAb1JBgKjl9kMJ2hu00s=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=45573@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).