Hello!
Josselin Poiret skribis:
> While using a bit of LaTeX recently, I've noticed some packages don't
> work "out-of-the-box", at least on LuaLaTeX, and need some additional
> propagated inputs. Examples would be babel-french needing scalefnt,
> fontspec needing luaotfload, or hyperref needin
Hi,
Nicolas Graves via "Development of GNU Guix and the GNU System
distribution." skribis:
> I met a packaging error two times when hacking guile or maven packages,
> where after using the #:modules flag in arguments, I found myself with
> gnu build-system packaging phases instead of guile or ma
Hi!
Maxim Cournoyer skribis:
> Congrats, and yay! It's a hell of a release! :-) Let's try to make more
> punctual ones from now on, and also try to lower the amount of manual
> labor producing one incurs (by streamlining the process), as speaking
> for me, this was one of the reasons I kept put
On 2023-01-03 at 10:05+01:00, Ludovic Courtès wrote:
> But how difficult would it be to identify what needs to be propagated?
Is there any practical reasons to not propagate all TeX packages?
For other language I suppose we need to avoid version clashing,
but in my experience TeX packages usually
Hi Hartmut,
> Am 02.01.23 um 20:17 schrieb Ricardo Wurmus:
>
> Thanks for providing the patch. For me this looks huge and hard to
> maintain.
>
> “Hard to maintain”? How so?
>
> For me this double structure is hard to understand and thus to maintain. YMMV.
Okay. Here’s something simpler using
Hello!
Ricardo Wurmus skribis:
> Okay. Here’s something simpler using “partition”:
>
> commit 96fb123832b262a3453fe1b7646758da235a343e
> Author: Ricardo Wurmus
> Date: Tue Jan 3 10:14:52 2023 +0100
>
> WIP
>
> diff --git a/guix/scripts/refresh.scm b/guix/scripts/refresh.scm
> index e0b94
Hi,
On Sat, 24 Dec 2022 at 03:49, "jgart" wrote:
> Users could then decide what channels they'd like to subscribe to/opt
> in to by adding any of the following channels as they please:
>
> python-channel
> rust-channel
[...]
> etc...
>
> The above channels would still be maintained under the au
Hi Ludo,
Ludovic Courtès writes:
> Hi!
>
> Maxim Cournoyer skribis:
>
>> Congrats, and yay! It's a hell of a release! :-) Let's try to make more
>> punctual ones from now on, and also try to lower the amount of manual
>> labor producing one incurs (by streamlining the process), as speaking
>>
On 03-01-2023 10:08, Ludovic Courtès wrote:
Hi!
Maxim Cournoyer skribis:
Congrats, and yay! It's a hell of a release! :-) Let's try to make
more
punctual ones from now on, and also try to lower the amount of manual
labor producing one incurs (by streamlining the process), as speaking
for me
According to the web interface, ci.guix.gnu.org stopped building things
on December 31, with evaluation 79343.
Is this true? What's wrong?
Am 03.01.23 um 10:49 schrieb Ludovic Courtès:
I tried something different and perhaps simpler: making sure
‘options->update-specs’ always returns a list of , as the
name implies, and does the right thing with manifests, -r, and -e.
(Part of the patch moves the definition before its first
use.)
indieterminacy writes:
> On 03-01-2023 10:08, Ludovic Courtès wrote:
>> Hi!
>> Maxim Cournoyer skribis:
>>
>>> Congrats, and yay! It's a hell of a release! :-) Let's try to make more
>>> punctual ones from now on, and also try to lower the amount of manual
>>> labor producing one incurs (by st
Hey Guix,
I follow bug-h...@gnu.org pretty religiously (it's super entertaining),
and there has been work on a new cross-hurd branch, which are some
scripts for cross-compiling and creating an up-to-date Hurd system:
https://github.com/flavioc/cross-hurd
Anyone who is interested in updating Gu
However, there's no real reason that git-fetch *needs* to be
fixed-output in terms of having a hash pre-defined, at least for local
development and other purposes. So is there a way around this?
• write (package (source (git-checkout …)) …)
This works well. Now I'm curious how to know what
On 03-01-2023 19:42, Joshua Branson wrote:
indieterminacy writes:
On 03-01-2023 10:08, Ludovic Courtès wrote:
Hi!
Maxim Cournoyer skribis:
Congrats, and yay! It's a hell of a release! :-) Let's try to make
more
punctual ones from now on, and also try to lower the amount of
manual
labor p
Hi!
Hartmut Goebel skribis:
> Am 03.01.23 um 10:49 schrieb Ludovic Courtès:
>> I tried something different and perhaps simpler: making sure
>> ‘options->update-specs’ always returns a list of , as the
>> name implies, and does the right thing with manifests, -r, and -e.
>> (Part of the patch mov
Hello,
Pjotr Prins skribis:
> Just a heads up: we are excited to have Guix days and the FOSDEM
> devroom in Brussels Feb 2-5!!
>
> If you want to attend Guix days, please add to this list (the login is
> a bit hidden). We can only have limited people and catering. If we run
> over the max room n
Nguyễn Gia Phong skribis:
> On 2023-01-03 at 10:05+01:00, Ludovic Courtès wrote:
>> But how difficult would it be to identify what needs to be propagated?
>
> Is there any practical reasons to not propagate all TeX packages?
> For other language I suppose we need to avoid version clashing,
> but
Hi!
Stephen Paul Weber skribis:
>>> However, there's no real reason that git-fetch *needs* to be
>>> fixed-output in terms of having a hash pre-defined, at least for local
>>> development and other purposes. So is there a way around this?
>>
>> • write (package (source (git-checkout …)) …)
>
>
Hi there!
Ludovic Courtès skribis:
> • Containers, Dec. 10th
>
> https://discuss.linuxcontainers.org/t/fosdem-2023-containers-devroom-call-for-papers/15597
>
> • CI/CD, Dec. 12th
> https://lists.fosdem.org/pipermail/fosdem/2022q4/003457.html
>
> • Declarative & minimalist computin
Hello Guix!
The manual recommends this (info "(guix) Teams"):
git send-email --to issue_num...@debbugs.gnu.org $(./etc/teams.scm cc
mentors) *.patch
where:
--8<---cut here---start->8---
λ ./etc/teams.scm cc mentors
--add-header="X-Debbugs-Cc: r...@raghavgu
On 03-01-2023 19:42, Joshua Branson wrote:
What areas does guix need more documentation? To answer that question
for myself, I might say more gexp examples. Though unmatched-paren is
working on a series of blog posts to dive really deep into that topic.
Guix should use more em dashes in the
Just adding this here as a note to self:
oriansj
jgart: the answer to your qutebrowser problem is a known defect with an easy
work around: --qt-arg disable-seccomp-filter-sandbox true
mroh
ah, that explains why I have no fonts in kiwix-desktop. thx!
jgart
oriansj: [THANKS 💯]: Yay.
Hi Guixers,
How would you approach writing a script that installs every Guix package
exhaustively for your current revision?
I'm thinking of something similar to `all-packages` on PyPi but for every Guix
package (the whole wide 🌎️).
https://pypi.org/project/all-packages/
On 2023-01-04 at 02:33+00:00, jgart wrote:
> How would you approach writing a script that installs
> every Guix package exhaustively for your current revision?
I don't want to know why you'd like to do that,
but you can start from here:
repo=https://data.guix.gnu.org/repository/1/branch/master
pa
On 1/3/23 21:33, jgart wrote:
Hi Guixers,
How would you approach writing a script that installs every Guix package
exhaustively for your current revision?
I'm thinking of something similar to `all-packages` on PyPi but for every Guix
package (the whole wide 🌎️).
https://pypi.org/project/all-
I filed a couple patches related to teams recently, which pointed out a
few things about the teams process to me...
First off, I wonder if there is (or it is worth creating) a way to make
the scope of a team more fine-grained... e.g. I think the Embedded team
would want to be notified of changes
Good question, maybe we should just do that. Thoughts?
What about size? Does this not bloat up profile sizes?
--
Reza Housseini
This message is signed with my GnuPG key:
C0F3 0812 9AF2 80F4 0830 C2C1 C375 C6AF 0512 5C52
OpenPGP_0xC375C6AF05125C52.asc
Description: OpenPGP public key
On 2023-01-04 at 08:11+01:00, Reza Housseini wrote:
> What about size? Does [propagating all build inputs]
> not bloat up profile sizes?
I'm new to Guix, but aren't both build inputs
and propagated build inputs required at run time?
IIUC the only difference is that the propagated ones' env
is, ehm
29 matches
Mail list logo
