Felix Lechner writes:
Hi Ian,
On Mon, Jul 01 2024, Ian Eure wrote:
if you have strong feelings about -next vs. -latest
How about nss-rapid? It provides the clue about what was
packaged to
someone who knows libnss.
I like it. I’ll update the package descriptions to make
Hi Maxim,
Maxim Cournoyer writes:
Hi Ian,
Ian Eure writes:
[...]
Concretely:
The current nss package should stay how it is. When the next
ESR
happens, it should update to that (ungrafting nss at the same
time),
and track ESR releases only from that point forward. I don’t
think
Hi Felix,
Felix Lechner writes:
Hi Ian,
On Thu, Jun 27 2024, Ian Eure wrote:
The nss package updates frequently, around once a month. [...]
I'm
considering options to balance update frequency vs. huge
rebuilds.
Your plan sounds reasonable but my opinion is inconsequential.
Instead
Hi Ludo,
Ludovic Courtès writes:
Ian Eure skribis:
Guix sends archive requests to SWH. SWH gives that source code
to
HuggingFace. HuggingFace demonstrably violates the licenses.
Which licenses? As has been said previously, and you can verify
for
yourself, it does not ingest code
The nss package updates frequently, around once a month. It's
also very low in the package graph, so a ton of stuff depends on
it. The most recent update was a graft for security fixes, so we
didn't have to rebuild everything, but the new Librewolf version
once again requires an nss update.
Efraim Flashner writes:
[[PGP Signed Part:Undecided]]
On Wed, Jun 26, 2024 at 10:46:56AM +0300, Efraim Flashner wrote:
On Tue, Jun 25, 2024 at 08:48:12AM -0700, Ian Eure wrote:
> Hi Efraim,
>
> Efraim Flashner writes:
>
> > [[PGP Signed Part:Undecided]]
> > On Th
Hi Efraim,
Efraim Flashner writes:
[[PGP Signed Part:Undecided]]
On Thu, Jun 20, 2024 at 05:10:11PM -0700, Ian Eure wrote:
Hi Guixers,
I want to update the Librewolf package, but it now depends on
Rust
>= 1.76, which is newer than what's in master. I see the
>rust-team
bran
Hi Guixers,
I want to update the Librewolf package, but it now depends on Rust >= 1.76,
which is newer than what's in master. I see the rust-team branch has versions
up to 1.77 — is there a timeline for merging that, or a TODO list of things
that need to be done to merge it? I'm not sure if
Guix sends archive requests to SWH. SWH gives that source code to
HuggingFace. HuggingFace demonstrably violates the licenses.
Guix could stop sending archive requests to SWH. This wouldn’t
*stop* the bad things from happening, but it would *stop
condoning* them. The same as how Guix not
Hi Greg,
Please read my earlier reply in this thread[1].
HuggingFace is demonstrably violating the licenses of the Free
Software used to train its StarCoder2 LLM.
Software Heritage is continuing to partner with HuggingFace in
spite of these violations.
Guix is continuing to partner with
Hi MSavoritias,
Thank you for the email.
I’m going to lay out this situation as clearly as I can, in the
hope that others will better understand, and hopefully treat it
with the seriousness it deserves.
1. Guix requests SWH to archive some source code. This is fine.
2. SWH archives the
There’s a steady number of bug reports generated by the "You found
a bug" message which happens during `guix pull's. The
overwhelming majority of these reports are caused by networking
problems or the Guix infrastructure being unreliable or
overloaded. Many of these were submitted during the
I’m not sure of the precise mechanism employed, but I believe that
that in the past, if I ran `git format-patch' and `git
send-email', it would send an email to the right place. This is
implied by the manual, which doesn’t mention a patch submission
email address, except for an issue number
this, or a committment to build this within a reasonable
timeframe, would allay my concerns.
Ian Eure writes:
Hello,
I’m following up on this since discussion since it’s been a
month and
I haven’t heard any updates.
Summarizing the situation:
- SHF has an opaque, difficult, and undocumented
Ian Eure writes:
Clément Lassieur writes:
On Fri, Apr 12 2024, Andrew Tropin via Guix-patches via wrote:
On 2024-04-06 08:04, Ian Eure wrote:
Moves nss update to nss-3.98 / nss-certs-3.98 to avoid
rebuilding
thousands of packages.
Rebases.
Ian Eure (3):
gnu: Add nss-3.98.
gnu
Clément Lassieur writes:
On Fri, Apr 12 2024, Andrew Tropin via Guix-patches via wrote:
On 2024-04-06 08:04, Ian Eure wrote:
Moves nss update to nss-3.98 / nss-certs-3.98 to avoid
rebuilding thousands of packages.
Rebases.
Ian Eure (3):
gnu: Add nss-3.98.
gnu: Add nss-certs-3.98
No, this is not a bug. specification->package always returns the latest
version of a package and has no way of knowing what variable(s) that package
object is bound to.
On April 21, 2024 8:02:50 AM PDT, Felix Lechner
wrote:
>Hi,
>
>On Sat, Apr 20 2024, Ian Eure wrote:
>
>
The change is mentioned in the channel news, but it says nothing about needing
to remove that part of the config.
On April 21, 2024 1:32:38 AM PDT, "pelzflorian (Florian Pelz)"
wrote:
>Hello Ian. My understanding of the nss-certs etc/news.scm item had been
>that we should remove
ftware-Heritage-2024-Vision-Milestones-Newsletter.pdf
Ian Eure writes:
Hi Guixy people,
I’d never heard of SWH before I started hacking on Guix last
fall, and
it struck me as rather a good idea. However, I’ve seen some
things
lately which have soured me on them.
They appear to be using the a
Some recent nss-certs changes have a negative side effects which
needs to be fixed.
A patch of mine was pushed recently (commit
0920693381d9f6b7923e69fe00be5de8621ddb6f), which adds nss-certs
3.98 to (gnu packages certs), under the nss-certs-3.98 variable.
Then, commit
Simon Tournier writes:
Hi,
On lun., 18 mars 2024 at 12:38, Ian Eure
wrote:
They appear to be violating free software licenses on large
scale.
They are in violation of SWH’s own positions.
[...]
[1]: https://arxiv.org/html/2402.19173v1
[2]:
https://huggingface.co/spaces
Simon Tournier writes:
Hi,
On sam., 16 mars 2024 at 08:52, Ian Eure
wrote:
They appear to be using the archive to build LLMs:
https://www.softwareheritage.org/2024/02/28/responsible-ai-with-starcoder2/
About LLM, Software Heritage made a clear statement:
https
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
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
Christopher Baines writes:
[[PGP Signed Part:Undecided]]
Ian Eure writes:
Hi Guixy people,
I’d never heard of SWH before I started hacking on Guix last
fall, and
it struck me as rather a good idea. However, I’ve seen some
things
lately which have soured me on them.
They appear
Hi Guixy people,
I’d never heard of SWH before I started hacking on Guix last fall,
and it struck me as rather a good idea. However, I’ve seen some
things lately which have soured me on them.
They appear to be using the archive to build LLMs:
Hello,
I’ve been following along with this discussion, as well as a
discussion on Clojureverse, and thought it might be helpful to
pull together some threads and design decisions around Clojure’s
behavior.
Clojure is designed to ship libraries as source artifacts, not
bytecode ("pretty
Csepp writes:
Ian Eure writes:
Hello,
On Debian, you can create a preseed file containing answers to
all the questions
you’re prompted for during installation, and build a new
install image which
includes it. When booted, this installer skips any steps
which have been
preconfigured, which
Christopher Baines writes:
[[PGP Signed Part:Undecided]]
Hey!
After substitute availability taking a bit of a dive recently,
the
bordeaux build farm has finally caught back up and QA is back
submitting
builds for packages changed by patches.
QA also has a feature to allow easily tagging
mentioned which
can be explained.
On Mon, Jan 15 2024, Ian Eure wrote:
Some examples of where I think Guix could do better. This is
an
illustrative list, not an exhaustive one.
Inconsistent organization
=
Most package-related commands are under `guix package',
Greetings,
As I’ve been learning Guix, one of the things I’ve found somewhat
unpleasant is the lack of consistency within the guix CLI tool.
It feels a bit Git-like, with not much consistency, commands that
non-obvioulsy perform more than operation, related commands in
different places in
Hello,
I wanted to package Fractal, which is a native GNOME client for
Matrix chat. It requires newer versions of glib and gtk than are
currently in Guix. I believe I’ve seen in IRC that some folks are
working on getting GNOME 43/44 packages done, which probably needs
the glib/gtk updates
32 matches
Mail list logo
