Hi,
Leo Famulari writes:
> On Fri, Feb 14, 2025 at 04:10:22PM +, Morgan Arnold wrote:
>> Maxime's concern seems to me to be more about the fact that this
>> change facilitates (and arguably encourages) the accidental commission
>> of copyright violations. This issue is not necessarily specif
Hi David,
David Pirotte writes:
> Hello Maxim,
>
>> I think our naming rules are reasonable. Interpreted language
>> *libraries* are typically prefixed by the interpreter name ...
>
> Yes, but in this particular case, I am merely asking guix to accept to
> make an exception, as expressed in my
On 2025-02-15, Liliana Marie Prikler wrote:
> title: Rename "main" branch
> id: 003
> status: draft
> discussion: https://issues.guix.gnu.org/
> authors: Liliana Marie Prikler
> sponsors:
> date:
> SPDX-License-Identifier: CC-BY-SA-4.0 OR GFDL-1.3-no-invariants-only
Happy to sponsor, though seems
Hi David,
David Pirotte writes:
Hello Ricardo,
Is this such a problem, for guix, to make an exception? As you
all
understood by now, this is a bit of a sensitive subject for me.
Ultimately, this kind of decision is a judgement call on the part
of the committers reviewing the patches. In
On 2025-02-11, Efraim Flashner wrote:
> We discussed the next release during Guix Days and I volunteered to lead
> the effort.
Thanks for working on it!
> The short version:
>
> * We need a tagged release so we can update the version in Debian and
> other distros, in CI systems, etc.
Unless th
Hello Maxim,
> I think our naming rules are reasonable. Interpreted language
> *libraries* are typically prefixed by the interpreter name ...
Yes, but in this particular case, I am merely asking guix to accept to
make an exception, as expressed in my answer to Ricardo.
Thanks,
David
pgptdezIB
Hello Ricardo,
> Frankly, this is absurd.
What is absurd here, Ricardo, is the situation, that is, the guix
reaction to my kindly expressed request that it would use the upstream
name as its g-golf package name, post-fixed as required:
g-golf-x.y.z[-guile-x.y]
[ with additional p
Andreas Enge writes:
> Hello,
>
> Am Sat, Feb 15, 2025 at 06:51:26PM + schrieb Christopher Baines:
>> I think more fundamentally there's a lack of interest/buy-in
>
> I think there is a lot of interest, everybody seemed to be quite happy
> when QA worked, and patches with the green button wer
Hello,
Am Sat, Feb 15, 2025 at 06:51:26PM + schrieb Christopher Baines:
> I think more fundamentally there's a lack of interest/buy-in
I think there is a lot of interest, everybody seemed to be quite happy
when QA worked, and patches with the green button were merged rather
quickly.
In my op
Ian Eure writes:
> A while back, I proposed splitting the nss package into two, one for
> the ESR, and one for the rapid release. Because LibreWolf tracks the
> Firefox Rapid Release channel, it needs a newer nss than what Guix has
> fairly frequently, around 2-3 times a year. However, the nss p
Hi,
So I've noticed that my backups haven't been run for several weeks
because vorta didn't start up because wayland. (I should make an
automated check for that...)
Therefore, I made a script to find all similarly broken packages, which
are:
Packages that use qt but (don't use qtwayland o
Hi Liliana,
Thank you for putting this together. I sponsor.
-- Ian
> Because the backtrace actually doesn't even point in the right place, it's
> quite useless in my opinion.
the worst part of it is that it is able to tell you the right file and line,
but it doesn't tell you the name of the function.
> Am I doing anything wrong? I use guile 3.0.1.
no (altho
Hi Guixers,
A while back, I proposed splitting the nss package into two, one
for the ESR, and one for the rapid release. Because LibreWolf
tracks the Firefox Rapid Release channel, it needs a newer nss
than what Guix has fairly frequently, around 2-3 times a year.
However, the nss package is
Hi David,
David Pirotte writes:
[...]
>> As a first rule, the upstream name g-golf should be kept as is.
>
> There should be no other rule.
I think our naming rules are reasonable. Interpreted language
*libraries* are typically prefixed by the interpreter name,
e.g. 'python-markdown', althoug
Simon Tournier writes:
> Hi,
>
> Some of us are not always happy with the Guix/Guile error reporting. As
> discussed at the Guix Days, maybe the best strategy to improve the
> situation is to report small examples that we can work on. Therefore,
> here one that I have just hit today when workin
David Pirotte writes:
>> it is not up to every author/committer to name things as they wish.
>
> Quite the opposite: it should not be up to the distro to rename
> upstream projects as they wish. At the very least, the distro should
> ask for an authorization.
Frankly, this is absurd.
The upstre
Am Samstag, dem 15.02.2025 um 10:26 +0100 schrieb Simon Tournier:
> Hi Liliana, all,
>
> On Sat, 15 Feb 2025 at 09:42, Liliana Marie Prikler
> wrote:
>
> > title: Rename "main" branch
>
> Just to notice that I’m lagging behind and the GCD Git repository is
> not yet ready.
>
> However, it alre
Hi Liliana, all,
On Sat, 15 Feb 2025 at 09:42, Liliana Marie Prikler
wrote:
> title: Rename "main" branch
Just to notice that I’m lagging behind and the GCD Git repository is not
yet ready.
However, it already supports ’main’ as the default branch. ;-)
https://git.savannah.gnu.org/cgit/guix/
title: Rename "main" branch
id: 003
status: draft
discussion: https://issues.guix.gnu.org/
authors: Liliana Marie Prikler
sponsors:
date:
SPDX-License-Identifier: CC-BY-SA-4.0 OR GFDL-1.3-no-invariants-only
---
# Summary
Currently, much of Guix's development takes place on the âmasterâ branc
20 matches
Mail list logo
