Hi Tobias!
> The bad things. All of them. In order.
Oh! How are you doing now? Let me know if you need anything. I can try
and help in any way plausible. :-)
> You did fine, only renaming ‘truetype’ -> ‘ttf’ should have been
> separate. If it had been, I don't think it would have been merged.
On 2020-05-10, Marius Bakke wrote:
> Guillaume Le Vaillant writes:
>
>> Guillaume Le Vaillant skribis:
>>
>>> Hi,
>>>
>>> After pulling guix with the merged core updates (guix at commit
>>> 95ffdfe86cb1b8a8e4fff1386a147718400b76e0), I found a few packages
>>> failing to build:
>>>
>>> - fbreader
Guillaume Le Vaillant writes:
> Guillaume Le Vaillant skribis:
>
>> Hi,
>>
>> After pulling guix with the merged core updates (guix at commit
>> 95ffdfe86cb1b8a8e4fff1386a147718400b76e0), I found a few packages
>> failing to build:
>>
>> - fbreader
>> - gnubg
>> - gnubik
>> - postgis
>> - p
Hello,
Did you have a look at Shengyu Zhang's work on xattr? That's about
summer 2016. Also see glibc/sysdeps/mach/hurd/setxattr.c which
translates gnu attributes into RPC calls, and then again in the
translators's diskfs_set_translator. See for instance in
hurd/ext2fs/inode.c's diskfs_set_transla
Hello,
As part of the effort of creating vm-images for the Hurd using Guix, it
would be nice to use extended file attributes to set passive
translators.
In particular, it would be helpful if we could use
setfattr --name=gnu.translator --value=/hurd/pfinet 1
That would allow us to boot right
This back and forth is what I've been having going on in my head. We might
be able to leverage repology.org for their work on mapping packages across
distros. Yesterday, civodul entered a bug to remove the Etag and
last-modified headers in the nginx config to fix a bug on our side so
repology wil
Raghav,
Raghav Gururajan 写道：
Nice! I was wondering what happend to you. ;-)
The bad things. All of them. In order.
No, my goal was to enable other types. I happened to update it
like that
and assumed I did it correctly when I came across this MIME
thing.
You did fine, only renaming ‘tru
Hey Tobias!
>> Hello Guix!
>
> o/
>
> I haz returned.
Nice! I was wondering what happend to you. ;-)
>> As of 2017, IANA (www.iana.org) has changed the standard template for
>> font media types.
>>
>
> Not so much changed, but that there was previously no standard. The W3C
> was displeased wi
Raghav,
Raghav Gururajan 写道：
Hello Guix!
o/
I haz returned.
As of 2017, IANA (www.iana.org) has changed the standard
template for
font media types.
Not so much changed, but that there was previously no standard.
The W3C was displeased with the proliferation of ad-hoc,
inconsistent fon
Hello Guix!
As of 2017, IANA (www.iana.org) has changed the standard template for
font media types.
SOURCE: https://www.iana.org/assignments/media-types/media-types.xhtml#font
So, font/freetype and font/opentype has to be updated to font/ttf and
font/otf, respectively.
Almost all font packages
Hi Julien,
On Sun, 10 May 2020 at 14:13, Julien Lepiller wrote:
> The proposal was about suggesting anotger nameqwhen no package was found, not
> to install something else.
Sorry I misinterpreted.
> >Well, do you have specific example in mind?
>
> $ guix install gcc
> guix install: error: gc
Hi Vincent,
On Sun, 10 May 2020 at 12:08, Vincent Legoll wrote:
> Used googl often being used to approximate it, crudely but effectively.
The big question is how to build such database.
Wikidata?
All the best,
simon
Le 10 mai 2020 05:57:22 GMT-04:00, zimoun a écrit :
>Dear,
>
>On Sat, 9 May 2020 at 22:19, Josh Marshall
> wrote:
>
>> [...] naming conventions between the source project, [...] , and guix
>itself have some drift.
>
>Some packages already track upstream name: see the field '(proprieties
>(upstream
On 09/05/2020 22:18, Josh Marshall wrote:
This appears that it could be low effort, not interfere with any
commands, not really change the interface, and make life easier.
Anybody have any thoughts as to whether this would be a good idea or not?
What about the following:
>8--
Dear,
On Sat, 9 May 2020 at 22:19, Josh Marshall
wrote:
> [...] naming conventions between the source project, [...] , and guix itself
> have some drift.
Some packages already track upstream name: see the field '(proprieties
(upstream-name . "foo"))', e.g., the package "r-flowsom",
> The appr
Hi,
I'm not sure if that's something guix needs to be aware of.
If the name differs very much and guix naming conventions differ plus it
can not be found through any of the fields, it makes sense. But you
probably don't want to track the different conventions used by various
package managers as it
Guillaume Le Vaillant skribis:
> Hi,
>
> After pulling guix with the merged core updates (guix at commit
> 95ffdfe86cb1b8a8e4fff1386a147718400b76e0), I found a few packages
> failing to build:
>
> - fbreader
> - gnubg
> - gnubik
> - postgis
> - python-cheetah
> - python-trezor
>
> I have n
17 matches
Mail list logo
