On 3/16/24 21:45, Tomas Volf wrote:
On 2024-03-16 20:24:50 +0200, MSavoritias wrote:
I was also distressed to see how poorly they treated a developer who
wished to update their name:
https://cohost.org/arborelia/post/4968198-the-software-heritag
https://cohost.org/arborelia/post/5052044-the-so
Hello,
I just found out that Guix QA returns a plain Guile error message when I
try to open an issue that was merged:
https://qa.guix.gnu.org/issue/69654
The error looks like this:
--8<---cut here---start->8---
An error occurred
Sorry about that!
wrong-type-
Hey,
> I have heard folks in the Guix maintenance sphere claim that we never rewrite
> git history in Guix, as a matter of policy. I believe we should revisit that
> policy (is it actually written anywhere?) with an eye towards possible
> exceptions, and develop a mechanism for securely maintai
On 3/17/24 11:39, Lars-Dominik Braun wrote:
Hey,
I have heard folks in the Guix maintenance sphere claim that we never rewrite
git history in Guix, as a matter of policy. I believe we should revisit that
policy (is it actually written anywhere?) with an eye towards possible
exceptions, and
Hi Ada,
On 2024-03-17 07:18, Ada Stevenson wrote:
Hi Guix,
I have this gripe with usability regarding using substitutes.
Sometimes, usually when I'm on an enterprise network like my
university's of library's wifi, the `guix substitute` process dies with
a "TLS error in procedure 'write_to_se
Hi all ,
thank you MSavoritias for bringing up points that many of us share. It's
clearly a tradeoff what to do about the past. For the future, as
Christpher already stated, we need a serious solution that we can uphold
as a free software project that does not alienate users or contributors.
On 3/17/24 13:53, paul wrote:
Hi all ,
thank you MSavoritias for bringing up points that many of us share.
It's clearly a tradeoff what to do about the past. For the future, as
Christpher already stated, we need a serious solution that we can
uphold as a free software project that does not
"Artyom V. Poptsov" writes:
> Hello,
>
> I just found out that Guix QA returns a plain Guile error message when I
> try to open an issue that was merged:
> https://qa.guix.gnu.org/issue/69654
>
> The error looks like this:
>
> An error occurred
>
> Sorry about that!
> wrong-type-arg
>
> #fWron
On 2024-03-17 12:53:54 +0100, paul wrote:
> only a 35 yrs old white cis boy
Could you stop labeling people like this? It makes me feel uncomfortable and
not welcomed...
T.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature
On Sat, 16 Mar 2024, Ian Eure wrote:
[...]
> GPL’d software I’ve created has been packaged for Guix, which I assume
> means it’s been included in SWH. While I’m dealing with their (IMO:
> unethical) opt-out process, I likely also need to stop new copies from
> being uploaded again in the future
MSavoritias writes:
On 3/17/24 11:39, Lars-Dominik Braun wrote:
Hey,
I have heard folks in the Guix maintenance sphere claim that
we
never rewrite git history in Guix, as a matter of policy. I
believe
we should revisit that policy (is it actually written
anywhere?)
with an eye towards po
MSavoritias writes:
On 3/17/24 13:53, paul wrote:
Hi all ,
thank you MSavoritias for bringing up points that many of us
share. It's clearly a tradeoff what to do about the past. For
the
future, as Christpher already stated, we need a serious
solution
that we can uphold as a free software
On 3/17/24 18:20, Ian Eure wrote:
MSavoritias writes:
On 3/17/24 11:39, Lars-Dominik Braun wrote:
Hey,
I have heard folks in the Guix maintenance sphere claim that we
never rewrite git history in Guix, as a matter of policy. I believe
we should revisit that policy (is it actually written
Simon Tournier writes:
>> Does your built images contains several layers?
>
> This had recently been introduced.
>
> 0cf75c9b2f23869201144917cea7f6ad49683d3d
> AuthorDate: Tue Dec 26 03:54:12 2023 +0300
> CommitDate: Mon Jan 8 21:04:44 2024 +0300
Thanks.
>> nix2container
Hi!
Gábor Boskovits skribis:
> 1. It is rare that guix home import does the right thing (it is usually
> removing some startup file customizations, does not seem to arrange to pick
> up profiles, not even its own). Either we should improve it, or document
> that it only gives a skeleton configur
Hi,
Z572 <873216...@qq.com> skribis:
> see
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=21ca59b365c0
>
> linux 6.7 support use binfmt_misc to add new binary formats within
> unprivileged namespaces,
> I think this improves guix reproducibility and also avoids le
Simon Tournier writes:
>> Well, I have not followed on which strategy Guix relies. What is the
>> one of nix2container? The one described here:
>>
>> https://grahamc.com/blog/nix-and-layered-docker-images/
>
> To answer to my question, the way to build the container image is
> different, he
Hi,
"pelzflorian (Florian Pelz)" skribis:
> Otherwise LGTM. Could you send another diff? Would a commit message
> like this be okay:
>
> doc: Simplify installation instructions.
>
> * doc/guix.texi (Installation): Direct readers towards the installation
> script. Remove superfluous commentary
Hi,
Hartmut Goebel skribis:
>> I will submit a patchset shortly for review and if accepted we can
>> look to combine all the cmake patches for the large rebuild.
>
> Yes, of course we should combine them. May I ask you to take care of
> it and include mine, which I just posted:
>
> https://issue
On Sunday, March 17th, 2024 at 12:24 PM, Ludovic Courtès wrote:
> I personally try to lower the barrier for Home services, but I think few
> people (if any) beyond me review Home services.
>
> We should expand the ‘home’ team; who’s in?
I would like to contribute to Guix home, but haven't been
On Sunday, March 17th, 2024 at 12:24 PM, Ludovic Courtès wrote:
> ‘guix home import’ does exactly that: generate a first configuration
> that you may find necessary to tweak. Perhaps the manual should clarify
> that?
Maybe we should call it "guix home init" then? Describing it as "import"
impli
Hi,
Ian Eure skribis:
> They appear to be using the archive to build LLMs:
> https://www.softwareheritage.org/2024/02/28/responsible-ai-with-starcoder2/
To me, if the end result is that copyleft licenses are ignored, as is
the case with Microsoft’s CoPilot, then we have a problem.
That’s no ex
Hello,
>Correctly handling the ABI concerns — which Guix currently does
>not do — would result in a combinatorial explosion of Clojure
>packages should multiple versions of Clojure ever be available in
>Guix at the same time.
I think this is partly true and also a problem of other languages in
Gu
Regarding Guix development, if the decision is made to not change
existing policy or implement another authorship mechanism, I think some
text could be added to the manual explaining such.
Contributing to Guix is an intentional thing, unlike SWH. Updating the
manual means contributors will, at lea
Hello!
Ryan Prior skribis:
> 1. I haven't been able to use Guix Home to migrate my home config across
> machines. I've done this 3 times since I started using Guix on what I would
> consider advanced-level (writing Guile, defining my own packages & manifests,
> contributing patches.) Each tim
Ryan Prior skribis:
> On Sunday, March 17th, 2024 at 12:24 PM, Ludovic Courtès wrote:
>
>> ‘guix home import’ does exactly that: generate a first configuration
>> that you may find necessary to tweak. Perhaps the manual should clarify
>> that?
>
> Maybe we should call it "guix home init" then? D
> only a 35 yrs old white cis boy
you're judging a group of individuals, namely those who were handed the cis
white male mix at the genetic lottery, as a uniform blob. and maybe even
somewhat deplorable, if i'm reading your right.
does it make sense to judge an individual based on some coincide
> I was also distressed to see how poorly they treated a developer
> who wished to update their name:
> https://cohost.org/arborelia/post/4968198-the-software-heritag
> https://cohost.org/arborelia/post/5052044-the-software-heritag
let's put aside the trans aspect of this question for a moment, b
28 matches
Mail list logo
