Hi Tanguy,
Tanguy Le Carrour writes:
> Dear Timothy, dear Guix
>
> Sorry it took me soo long to answer!
No problem! Thanks for following up.
> Le 05/13, Tanguy Le Carrour a écrit :
>> Le 05/12, Timothy Sample a écrit :
>> > Tanguy Le Carrour writes:
>> > > I get the following error
On 2019-05-31, Tobias Geerinckx-Rice wrote:
> Vagrant,
>
> guix-comm...@gnu.org wrote:
>> gnu: diffoscope: Update to version 115-1.7f3416f.
>
> I wondered why this was updated to a git revision instead of the
> 115 release tag, and found:
Realized I should have included a comment explaining why
Vagrant,
guix-comm...@gnu.org wrote:
gnu: diffoscope: Update to version 115-1.7f3416f.
I wondered why this was updated to a git revision instead of the
115 release tag, and found:
Commit 7f3416ff
Committed by Vagrant Cascadian 6 days ago
Add support for known external tools on
Hi John,
> Another question: do we tend to try to use guix packages whenever a
package
> ships bundled with some third party source?
Yes. The preference is to use Guix packages where possible.
Best regards,
Paul.
Hi Mark,
> Hmm, I don't understand. What do the 4.14.x headers have to do with
> 4.15, which is the version I'm suggesting to delete?
Oh, my mistake.
Indeed, we have linux-libre@4.14.122 which should match the linux-libre-headers
we have, even after deleting 4.15.
pgpqZwmvUcOmY.pgp
Hi Danny,
Danny Milosavljevic writes:
>> I think we should not add linux-libre-4.15, because that version of
>> Linux-libre is no longer supported upstream, and therefore will have
>> well-known security flaws.
>
> OK with me to remove.
>
> The headers were from 4.14.67 (and still are), though.
Thanks Paul!
I’m looking forward to it. Another question: do we tend to try to use guix
packages whenever a package ships bundled with some third party source?
- John
> On May 30, 2019, at 9:23 AM, Paul Garlick
> wrote:
>
> Hi John,
>
> It is good to hear that you have made such good
Hi John,
It is good to hear that you have made such good progress on packaging
FreeCAD.
> we would need to also package opencascade-occt
I can help with this part. I am planning to introduce the opencascade-
occt package in order to upgrade gmsh, which also depends on
OpenCASCADE.
All
Hi All,
> Kudos Laura & Paul!
> I am cc'ing Paul :)
It is good to hear that the end result is being well received :)
I am thinking of adding a CREDITS file to the repository, primarily to
acknowledge the help given by the sound engineer. The use of the
studio equipment and the editing work
Hello Guix!
In a typical desktop setup, either home or workplace, it is common to use
printers. So can "cups-service-type" be added to "%desktop-services"?
Regards,
RG.
Ricardo Wurmus writes:
>> I started looking at what it would take to upgrade glibc to 2.29 on
>> ‘core-updates’. Bad news: it depends on Python.
>
> I had to check the date. This is for real?
It's for real:
--8<---cut here---start->8---
Changes to build
> I started looking at what it would take to upgrade glibc to 2.29 on
> ‘core-updates’. Bad news: it depends on Python.
I had to check the date. This is for real?
> Also, it would be nice to use ‘python-on-guile’ here, but it doesn’t
> provide a ‘python’ executable and I don’t know if it
Hello!
I started looking at what it would take to upgrade glibc to 2.29 on
‘core-updates’. Bad news: it depends on Python.
I came up with the WIP patch below, but Python eventually fails to build
with:
--8<---cut here---start->8---
In file included from
Hi Mark,
> I think we should not add linux-libre-4.15, because that version of
> Linux-libre is no longer supported upstream, and therefore will have
> well-known security flaws.
OK with me to remove.
The headers were from 4.14.67 (and still are), though. So we'll have
headers which we don't
I've sent a patch to #36000.
Nicolas Goaziou writes:
> Pierre Neidhardt writes:
>
>> Could work, I'll see what I can do.
>
> Great! Thank you.
Sorry, don't have the time this week. Feel free to update the patch if
you do. Worse case, this can always be improved later.
Cheers!
--
Pierre
15 matches
Mail list logo
