Re: December 2020 (old) bugs squashing!

[Maxim Cournoyer]

Hi Simon,

zimoun  writes:

> Hi,
>
> Let’s have an Advent calendar effort!  Everybody out there who is not
> familiar with this tradition of an « Advent calendar » and to avoid any
> ambiguity, I am appropriating myself the concept*: all of us try to
> close one or more bug per day from 1rst to 31th December, then 2021 will
> start on new balls as in tennis match. :-)
>
> In priority let pick bugs older than #3 (~Jan. 2018).
>
> 
>
> From Debbugs, I count 151 bugs or forgotten patches, almost 3 years!
> Time to close them or investigate more.
>
>
> If you do not know how to proceed:
>
>  1. pick an old bug and read the thread
>  2. if the last message is ending with an unanswered question, then mark
> it as moreinfo: send an email to cont...@debbugs.gnu.org using the
> bug number (e.g., 23456) with:
>
>   tags 23456 moreinfo
>   thanks
>
> Please give a look at:
>  
> 
>  3. if you do not know what to do, then reply by asking if the bug is
> still relevant for the author.  Please provide one line to remember
> the topic and the link which points to the bug:
>
>   
>
>   4. if it is a patch, then check if it is not superseded by something
>  already merged, else try to apply it and report success, rebase or
>  failure.
>
> Last, good candidates are bugs with only one or two messages.
>
>
> I hereby offer some ’(define drink)’ for the one who will close as many
> issues as possible in those 31 days.  Well, with the hope to meet those
> bug fighters once real time meeting will be possible again, otherwise
> you will win my gratitude. :-)
>
> For now, Tobias and Maxim have good score but hey we are only the 1th
> day. ;-)

Eh, 2020 is behind us and I don't think I managed to close much bugs in
last December; it's a priority I'll try to keep up with in 2021.  Let's
bring the number of issues down to something we can fit in our head more
easily!

Thanks for the initiative :-).

Maxim

Re: Make guix-publish's URL identical to cache file name

[Peng Mei Yu]

Hi,

Ludovic Courtès writes:

> Peng Mei Yu  skribis:
>
>> Ludovic Courtès writes:
>>
>>> Ricardo Wurmus  skribis:
>>>
 We need to make sure that *all* the files produced by “guix publish”
 have correct permissions; IIRC some of the files are not readable at all
 by users other than the owner of the files.
>>>
>>> Oops, I had forgotten, my bad.  I’ll push the attached patch later
>>> today.
>>>
>>> Next we’ll need to update the ‘guix’ package, restart ‘guix publish’ on
>>> berlin, and chmod a+r -R /var/cache/guix/publish.
>
> These two issues are now fixed.
>
>> Ping.  What's the status of rsync?
>
> It’s not running yet.  Ricardo, do you have a diff against berlin.scm to
> run it?

Ping again.


--
Peng Mei Yu

Re: Add Microsoft Cascadia Code font?

[Mark H Weaver]

Hi,

Leo Prikler  writes:

> Am Sonntag, den 10.01.2021, 07:28 -0500 schrieb Julien Lepiller:
>> I might be wrong, but I thought fonts were considered non-functional
>> data. If that's the case, isn't cc-by-nc-nd acceptable?
>
> Not according to the FSDG:
>> [Non-functional data] can be included in a free system distribution
>> as long as its license gives you permission to copy and redistribute,
>> both for commercial and non-commercial purposes.
> IIUC CC BY-ND would be covered if we indeed consider fonts to be non-
> functional data, but not CC BY-NC and certainly not CC BY-NC-ND.

Also, fonts are specifically listed as an example of functional data
according to the FSDG:

>>> License Rules
>>>
>>> “Information for practical use” includes software, documentation, fonts,
>>> and other data that has direct functional applications.  It does not
>>> include artistic works that have an aesthetic (rather than functional)
>>> purpose, or statements of opinion or judgment.
>>>
>>> All information for practical use in a free distribution must be
>>> available in source form.  (“Source” means the form of the information
>>> that is preferred for making changes to it.)
>>>
>>> The information, and the source, must be provided under an
>>> appropriate free license.  [...]



 Regards,
   Mark

Re: Cuirass logo - artwork.

[Development of GNU Guix and the GNU System distribution.]

Hey, Tobias,

‐‐‐ Original Message ‐‐‐
On Sunday, January 10, 2021 6:15 PM, Tobias Geerinckx-Rice  
wrote:

[...]

> Like the others I prefer the orange/black colour scheme. It integrates better 
> with other Guix sites & the other one has less positive connotiations.

Oh, really?! I know people associate these colors to political parties and 
sports teams depending on the region they live... Is there anything else 
considered negative about the blue-red scheme?


> Row B's ‘S’ just looks off; I prefer C's. Is this a stock typeface?

No, they are just rectangles.


> I see ‘integration’ in the logo but not in ‘//’.

OK, so it just looks like a link between the top and bottom parts of the S. But 
since the text-based logo has no votes for now, I'll just ignore it :)

By the way, I forgot to mention that the S in B and C variants also were 
supposed to symbolize the continuous part of CI. They were supposed to look 
close to the infinity symbol (drawn vertically).


> The logo comes frustratingly close to ‘CI’ whilst (to my eye) trying very 
> hard not to :-) A bit like the name ‘Cuirass’. Where did that come from, 
> Mathieu?

Pierre asked this same question earlier:

Pierre: Why is it called "Cuirass"? :p
Othacehe: No idea, you would have to ask Mathieu Lirzin about it!

About the integration of this logo with the Guix look, I thought that this logo 
was for Cuirass itself, not necessarily for the instance available in 
https://ci.guix.gnu.org/.

If Cuirass Web UI supports theming, the Guix instance could easily change the 
branding so that it is uniform with the style that has been used so far to name 
and brand other components. So Guix components like GuixHPC, GuixData, GuixCI, 
GuixDays, and so on, could use the same graphic style.

(Maybe Guix could use a Guile library defining an SXHTML/CSS theme to make it 
easier to style the websites of the different Guix components)

Re: Cuirass logo - artwork.

[Tobias Geerinckx-Rice]

Luis, Mathieu,

Luis Felipe via Development of GNU Guix and the GNU System 
distribution. 写道：

Here is my proposal:

https://luis-felipe.gitlab.io/media/2021/01/cuirass-logo-proposal-2021-01-09.png


Like the others I prefer the orange/black colour scheme.  It 
integrates better with other Guix sites & the other one has less 
positive connotiations.


Row B's ‘S’ just looks off; I prefer C's.  Is this a stock 
typeface?


I see ‘integration’ in the logo but not in ‘//’.

The logo comes frustratingly close to ‘CI’ whilst (to my eye) 
trying very hard not to :-)  A bit like the name ‘Cuirass’.  Where 
did that come from, Mathieu?


Thanks for drawing these up so swiftly!

T G-R


signature.asc
Description: PGP signature

Re: Cuirass logo - artwork.

[Mathieu Othacehe]

Hello Luis,

> Variants A, B, and C only differ in the shape of the S characters.
>
> What do you think?

Woo, that was fast! All your proposals seem terrific to me but I have a
small preference for the design 2B with the blue background.

What do other people think :)?

Many thanks for your help,

Mathieu

Re: Add Microsoft Cascadia Code font?

[Julien Lepiller]

Le 10 janvier 2021 08:09:03 GMT-05:00, Leo Prikler 
 a écrit :
>Hi Julien,
>
>Am Sonntag, den 10.01.2021, 07:28 -0500 schrieb Julien Lepiller:
>> I might be wrong, but I thought fonts were considered non-functional
>> data. If that's the case, isn't cc-by-nc-nd acceptable?
>
>Not according to the FSDG:
>> [Non-functional data] can be included in a free system distribution
>> as long as its license gives you permission to copy and redistribute,
>> both for commercial and non-commercial purposes.
>IIUC CC BY-ND would be covered if we indeed consider fonts to be non-
>functional data, but not CC BY-NC and certainly not CC BY-NC-ND.
>

I see, thanks for correcting me!

Re: Add Microsoft Cascadia Code font?

[Leo Prikler]

Hi Julien,

Am Sonntag, den 10.01.2021, 07:28 -0500 schrieb Julien Lepiller:
> I might be wrong, but I thought fonts were considered non-functional
> data. If that's the case, isn't cc-by-nc-nd acceptable?

Not according to the FSDG:
> [Non-functional data] can be included in a free system distribution
> as long as its license gives you permission to copy and redistribute,
> both for commercial and non-commercial purposes.
IIUC CC BY-ND would be covered if we indeed consider fonts to be non-
functional data, but not CC BY-NC and certainly not CC BY-NC-ND.

It goes on to list a hypothetical example of a game map, which is
somewhat ironic, considering that games more often disqualify
themselves for the FSDG through the use of entirely non-free assets or
assets rather than being GPL-incompatible through the use of assets,
that don't allow derivative work.  Of course, the former is a subset of
the latter, but the point I'm trying to make here, is that the latter
is sadly not even a concern for many (aspiring) game devs out there. 
It also reminds me, that I have yet to code up a fully GPL/FSDG-
compatible game myself – I'll get there some day, I promise.

TL;DR: Non-functional data is fine if it is commercially verbatim-
copyable.

Regards,
Leo

Re: Add Microsoft Cascadia Code font?

[yasu]

Well, let me know if that's the case!  After all, my submission is
almost identical as the existing packages such as font-ibm-plex and
font-inconsolata?
I would prefer not to "fork" as another repository if I can avoid it!
-Yasu
On Sun, 2021-01-10 at 07:28 -0500, Julien Lepiller wrote:
> I might be wrong, but I thought fonts were considered non-functional
> data. If that's the case, isn't cc-by-nc-nd acceptable?
> 
> Le 10 janvier 2021 05:38:16 GMT-05:00, Leo Prikler <
> leo.prik...@student.tugraz.at> a écrit :
> > Hi Yasu,
> > 
> > I don't think it'll be so simple.  It appears, that nerd-fonts
> > already
> > includes – or at least has the potential to include – some non-free
> > glyphs, which would in turn then be part of Cascadia.  An instance
> > would be pomicons [1], which are licensed as CC BY-NC-ND.  A
> > reviewer
> > would first have to verify, that Cascadia is indeed wholly covered
> > under the OFL or at least under a set of free licenses.
> > 
> > Yes, it sucks having to put that much effort into packaging a font,
> > but
> > if you just want to have a workable font for programming, there are
> > probably better solutions than Cascadia, some of which are already
> > packaged in Guix – e.g. font-fira-code.
> > 
> > Regards,
> > Leo
> > 
> > [1] https://github.com/gabrielelana/pomicons
> > 
> > Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo:
> > > Thank you for your comments!
> > > 
> > > Because I don't have a lot of time, is it ok to just re-format
> > > the
> > > original submission, get it committed with the comment that the
> > > package needs to be compiled rather than copied, when someone (or
> > > I)
> > > wants to so properly?
> > > 
> > > Cheers,
> > > Yasu
> > > 
> > > 
> > > > On Jan 10, 2021, at 18:16, Leo Prikler <
> > > > leo.prik...@student.tugraz.at> wrote:
> > > > 
> > > > Hello Vincent,
> > > > 
> > > > there is no .tar of the fonts however, that's a source tarball
> > > > generated by github.  To be fair, one should probably build
> > > > this
> > > > font
> > > > (and other fonts) from source instead.  In particular, we might
> > > > want to
> > > > package nerd-fonts[1] first, since Cascadia appears to be an
> > > > iteration
> > > > of it.
> > > > 
> > > > Regards,
> > > > Leo
> > > > 
> > > > [1] https://github.com/ryanoasis/nerd-fonts
> > > > 
> > > > 

Re: Add Microsoft Cascadia Code font?

[Julien Lepiller]

I might be wrong, but I thought fonts were considered non-functional data. If 
that's the case, isn't cc-by-nc-nd acceptable?

Le 10 janvier 2021 05:38:16 GMT-05:00, Leo Prikler 
 a écrit :
>Hi Yasu,
>
>I don't think it'll be so simple.  It appears, that nerd-fonts already
>includes – or at least has the potential to include – some non-free
>glyphs, which would in turn then be part of Cascadia.  An instance
>would be pomicons [1], which are licensed as CC BY-NC-ND.  A reviewer
>would first have to verify, that Cascadia is indeed wholly covered
>under the OFL or at least under a set of free licenses.
>
>Yes, it sucks having to put that much effort into packaging a font, but
>if you just want to have a workable font for programming, there are
>probably better solutions than Cascadia, some of which are already
>packaged in Guix – e.g. font-fira-code.
>
>Regards,
>Leo
>
>[1] https://github.com/gabrielelana/pomicons
>
>Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo:
>> Thank you for your comments!
>> 
>> Because I don't have a lot of time, is it ok to just re-format the
>> original submission, get it committed with the comment that the
>> package needs to be compiled rather than copied, when someone (or I)
>> wants to so properly?
>> 
>> Cheers,
>> Yasu
>> 
>> 
>> > On Jan 10, 2021, at 18:16, Leo Prikler <
>> > leo.prik...@student.tugraz.at> wrote:
>> > 
>> > Hello Vincent,
>> > 
>> > there is no .tar of the fonts however, that's a source tarball
>> > generated by github.  To be fair, one should probably build this
>> > font
>> > (and other fonts) from source instead.  In particular, we might
>> > want to
>> > package nerd-fonts[1] first, since Cascadia appears to be an
>> > iteration
>> > of it.
>> > 
>> > Regards,
>> > Leo
>> > 
>> > [1] https://github.com/ryanoasis/nerd-fonts
>> > 
>> > 

Re: Add Microsoft Cascadia Code font?

[yasu]

I created a 'low-standard-guix' repository and moved the submitted
package there, for now :-)

https://github.com/yugawara/low-standard-guix/blob/master/README.md

Again, when I get time, let me see if I can properly package Cascadia
Code fonts!

Cheers,
Yasu



On Sun, 2021-01-10 at 19:56 +0900, Yasuaki Kudo wrote:
> Hi Leo,
> 
> Understood, and this level of scrutiny is actually an encouraging
> sign that Guix has standards! 
> 
> I am happy enough to have it this way for my personal use for
> now.  Later, when I have more time, let me revisit.   
> 
> I have not experimented with this yet but I also understand I can
> create a separate repository as well.   Maybe that will also do
> 
> Regards,
> Yasu
> 
> > On Jan 10, 2021, at 19:38, Leo Prikler <
> > leo.prik...@student.tugraz.at> wrote:
> > 
> > Hi Yasu,
> > 
> > I don't think it'll be so simple.  It appears, that nerd-fonts
> > already
> > includes – or at least has the potential to include – some non-free
> > glyphs, which would in turn then be part of Cascadia.  An instance
> > would be pomicons [1], which are licensed as CC BY-NC-ND.  A
> > reviewer
> > would first have to verify, that Cascadia is indeed wholly covered
> > under the OFL or at least under a set of free licenses.
> > 
> > Yes, it sucks having to put that much effort into packaging a font,
> > but
> > if you just want to have a workable font for programming, there are
> > probably better solutions than Cascadia, some of which are already
> > packaged in Guix – e.g. font-fira-code.
> > 
> > Regards,
> > Leo
> > 
> > [1] https://github.com/gabrielelana/pomicons
> > 
> > Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo:
> > > Thank you for your comments!
> > > 
> > > Because I don't have a lot of time, is it ok to just re-format
> > > the
> > > original submission, get it committed with the comment that the
> > > package needs to be compiled rather than copied, when someone (or
> > > I)
> > > wants to so properly?
> > > 
> > > Cheers,
> > > Yasu
> > > 
> > > 
> > > > On Jan 10, 2021, at 18:16, Leo Prikler <
> > > > leo.prik...@student.tugraz.at> wrote:
> > > > 
> > > > Hello Vincent,
> > > > 
> > > > there is no .tar of the fonts however, that's a source tarball
> > > > generated by github.  To be fair, one should probably build
> > > > this
> > > > font
> > > > (and other fonts) from source instead.  In particular, we might
> > > > want to
> > > > package nerd-fonts[1] first, since Cascadia appears to be an
> > > > iteration
> > > > of it.
> > > > 
> > > > Regards,
> > > > Leo
> > > > 
> > > > [1] https://github.com/ryanoasis/nerd-fonts
> > > > 
> > > > 

Re: Add Microsoft Cascadia Code font?

[Yasuaki Kudo]

Hi Leo,

Understood, and this level of scrutiny is actually an encouraging sign that 
Guix has standards! 

I am happy enough to have it this way for my personal use for now.  Later, when 
I have more time, let me revisit.   

I have not experimented with this yet but I also understand I can create a 
separate repository as well.   Maybe that will also do

Regards,
Yasu

> On Jan 10, 2021, at 19:38, Leo Prikler  wrote:
> 
> Hi Yasu,
> 
> I don't think it'll be so simple.  It appears, that nerd-fonts already
> includes – or at least has the potential to include – some non-free
> glyphs, which would in turn then be part of Cascadia.  An instance
> would be pomicons [1], which are licensed as CC BY-NC-ND.  A reviewer
> would first have to verify, that Cascadia is indeed wholly covered
> under the OFL or at least under a set of free licenses.
> 
> Yes, it sucks having to put that much effort into packaging a font, but
> if you just want to have a workable font for programming, there are
> probably better solutions than Cascadia, some of which are already
> packaged in Guix – e.g. font-fira-code.
> 
> Regards,
> Leo
> 
> [1] https://github.com/gabrielelana/pomicons
> 
> Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo:
>> Thank you for your comments!
>> 
>> Because I don't have a lot of time, is it ok to just re-format the
>> original submission, get it committed with the comment that the
>> package needs to be compiled rather than copied, when someone (or I)
>> wants to so properly?
>> 
>> Cheers,
>> Yasu
>> 
>> 
>>> On Jan 10, 2021, at 18:16, Leo Prikler <
>>> leo.prik...@student.tugraz.at> wrote:
>>> 
>>> Hello Vincent,
>>> 
>>> there is no .tar of the fonts however, that's a source tarball
>>> generated by github.  To be fair, one should probably build this
>>> font
>>> (and other fonts) from source instead.  In particular, we might
>>> want to
>>> package nerd-fonts[1] first, since Cascadia appears to be an
>>> iteration
>>> of it.
>>> 
>>> Regards,
>>> Leo
>>> 
>>> [1] https://github.com/ryanoasis/nerd-fonts
>>> 
>>> 
> 

Re: Add Microsoft Cascadia Code font?

[Leo Prikler]

Hi Yasu,

I don't think it'll be so simple.  It appears, that nerd-fonts already
includes – or at least has the potential to include – some non-free
glyphs, which would in turn then be part of Cascadia.  An instance
would be pomicons [1], which are licensed as CC BY-NC-ND.  A reviewer
would first have to verify, that Cascadia is indeed wholly covered
under the OFL or at least under a set of free licenses.

Yes, it sucks having to put that much effort into packaging a font, but
if you just want to have a workable font for programming, there are
probably better solutions than Cascadia, some of which are already
packaged in Guix – e.g. font-fira-code.

Regards,
Leo

[1] https://github.com/gabrielelana/pomicons

Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo:
> Thank you for your comments!
> 
> Because I don't have a lot of time, is it ok to just re-format the
> original submission, get it committed with the comment that the
> package needs to be compiled rather than copied, when someone (or I)
> wants to so properly?
> 
> Cheers,
> Yasu
> 
> 
> > On Jan 10, 2021, at 18:16, Leo Prikler <
> > leo.prik...@student.tugraz.at> wrote:
> > 
> > Hello Vincent,
> > 
> > there is no .tar of the fonts however, that's a source tarball
> > generated by github.  To be fair, one should probably build this
> > font
> > (and other fonts) from source instead.  In particular, we might
> > want to
> > package nerd-fonts[1] first, since Cascadia appears to be an
> > iteration
> > of it.
> > 
> > Regards,
> > Leo
> > 
> > [1] https://github.com/ryanoasis/nerd-fonts
> > 
> > 

Re: Add Microsoft Cascadia Code font?

[Yasuaki Kudo]

Thank you for your comments!

Because I don't have a lot of time, is it ok to just re-format the original 
submission, get it committed with the comment that the package needs to be 
compiled rather than copied, when someone (or I) wants to so properly?

Cheers,
Yasu


> On Jan 10, 2021, at 18:16, Leo Prikler  wrote:
> 
> Hello Vincent,
> 
> there is no .tar of the fonts however, that's a source tarball
> generated by github.  To be fair, one should probably build this font
> (and other fonts) from source instead.  In particular, we might want to
> package nerd-fonts[1] first, since Cascadia appears to be an iteration
> of it.
> 
> Regards,
> Leo
> 
> [1] https://github.com/ryanoasis/nerd-fonts
> 
> 

Re: Add Microsoft Cascadia Code font?

[Vincent Legoll]

Hello,

On Sun, Jan 10, 2021 at 10:16 AM Leo Prikler
 wrote:
> there is no .tar of the fonts however, that's a source tarball
> generated by github.  To be fair, one should probably build this font
> (and other fonts) from source instead.  In particular, we might want to
> package nerd-fonts[1] first, since Cascadia appears to be an iteration
> of it.

Yes you're right, I did not look at the submitted scm hard enough to
see it.

Sorry for the noise.

-- 
Vincent Legoll

Re: Add Microsoft Cascadia Code font?

[Leo Prikler]

Hello Vincent,

there is no .tar of the fonts however, that's a source tarball
generated by github.  To be fair, one should probably build this font
(and other fonts) from source instead.  In particular, we might want to
package nerd-fonts[1] first, since Cascadia appears to be an iteration
of it.

Regards,
Leo

[1] https://github.com/ryanoasis/nerd-fonts

Re: Add Microsoft Cascadia Code font?

[Vincent Legoll]

On Sun, Jan 10, 2021 at 9:46 AM Vincent Legoll 
wrote:

> * I've not checked the difference size (nor that it matters) between zip
> and tar.gz, you may want to use the smallest one to minimize download.
>

I just did, and the tgz wins: 3.1 MB vs 5.7 MB

-- 
Vincent Legoll

Re: Add Microsoft Cascadia Code font?

[Vincent Legoll]

Hello,

On Sun, Jan 10, 2021 at 9:04 AM yasu  wrote:

> Attached is my Guix package submission of Microsoft Cascadia Code
> fonts.
>
> This is my very first attempt to make a Guix package contribution and I
> did this in less than 30 minutes, copying the package descriptions of
> IBM Plex fonts and modifying a few things.   I dont' know what
> protocols I may have missed 
>
> Would you please let me know how to proceed from here?
>

LGTM

small nitpicks:

* 80 columns (you can auto-format the code with etc/indent-code.el, this
is documented here:
https://guix.gnu.org/manual/en/html_node/Formatting-Code.html)

* I've not checked the difference size (nor that it matters) between zip
and tar.gz, you may want to use the smallest one to minimize download.

Thanks

-- 
Vincent Legoll

Add Microsoft Cascadia Code font?

[yasu]

Hello Guix Development,

Attached is my Guix package submission of Microsoft Cascadia Code
fonts.

This is my very first attempt to make a Guix package contribution and I
did this in less than 30 minutes, copying the package descriptions of
IBM Plex fonts and modifying a few things.   I dont' know what
protocols I may have missed  

Would you please let me know how to proceed from here?

Regards,
Yasu
From a86683caa6ee17e881c91cc103d30f844d6a6b34 Mon Sep 17 00:00:00 2001
From: Yasuaki Kudo 
Date: Sun, 10 Jan 2021 16:11:26 +0900
Subject: [PATCH] i

---
 gnu/packages/fonts.scm | 17 +
 1 file changed, 17 insertions(+)

diff --git a/gnu/packages/fonts.scm b/gnu/packages/fonts.scm
index 11a8e6261b..d080eb5567 100644
--- a/gnu/packages/fonts.scm
+++ b/gnu/packages/fonts.scm
@@ -78,6 +78,23 @@
   #:use-module (gnu packages python-xyz)
   #:use-module (gnu packages xorg))
 
+(define-public font-cascadia-code
+  (package
+(name "font-cascadia-code")
+(version "2009.22")
+(source (origin
+  (method url-fetch)
+  (uri (string-append "https://github.com/microsoft/cascadia-code/releases/download/;
+  "v" version "/CascadiaCode-" version ".zip"))
+  (sha256
+(base32
+  "0ilqvy7hzw35w5mig6zp2lny30fm8kmpzh69fg2npr4snyacq6w0"
+(build-system font-build-system)
+(home-page "https://github.com/microsoft/cascadia-code/;)
+(synopsis "Microsoft Cascadia Code")
+(description "This package provides Microsoft Cascadia Code fonts.")
+(license license:silofl1.1)))
+
 (define-public font-ibm-plex
   (package
 (name "font-ibm-plex")
-- 
2.30.0