On 2024-04-16, Julien Lepiller wrote:
> Currently, most java packages use the implicit jdk from the build
> system (ant- or maven-build-system), which is… icedtea@8. We still
> have quite a lot of old packages that don't build with openjdk9, so
> I'm not sure when we can update the default jdk…
When recently taking a look at diffoscope, I was reminded that there is
effectively no default openjdk version, you have to pick a specific
version for each package definition...
At some time in diffoscope's history, that was openjdk@12.
But there are quite a few versions to choose from:
guix
Control: severity 1066113 serious
On 2024-03-16, Vagrant Cascadian wrote:
> On 2024-03-15, Salvatore Bonaccorso wrote:
>> On Fri, Mar 15, 2024 at 11:22:52AM -0700, Vagrant Cascadian wrote:
>>> On 2024-03-13, Vagrant Cascadian wrote:
>>> > On 2024-03-12, Vagrant Casc
On 2024-03-11, John Kehayias wrote:
> On Sunday, March 10th, 2024 at 9:58 PM, Vagrant Cascadian
> wrote:
>> On 2024-03-10, Suhail Singh wrote:
>>
>> > Vagrant Cascadian vagr...@debian.org writes:
>> >
>> > > but "guix pull" does not u
On 2024-03-10, Suhail Singh wrote:
> Vagrant Cascadian writes:
>> but "guix pull" does not update the running guix-daemon;
>
> Just to be clear, however, if one were to do =sudo -i guix pull=
> instead, followed by =systemctl restart guix-daemon.service= it /woul
On 2024-03-10, m...@excalamus.com wrote:
> On Wed, 06 Mar 2024 22:29:23 +0100 Vagrant Cascadian wrote ---
>> As the one who packaged and maintains guix in Debian...
>
> Thank you for doing this work!
>
>> The guix-daemon should continue to work from the pa
On 2024-03-06, pelzflorian (Florian Pelz) wrote:
> I don’t feel qualified to judge, but is this the preference? Arch wiki
> advises against the Arch AUR package: “Therefore, after updating Guix
> once, the AUR advantage really turns into a disadvantage, as there will
> be many unnecessary files
I noticed Debian is switching to 7zip from p7zip... my guess is because
7zip is actively maintained, whereas p7zip does not appear to as
actively maintained?
I am not hugely opinionated on the matter, but figured it was worth
mentioning, if anyone wanted to take a stab at it!
live well,
On 2024-02-27, Andreas Enge wrote:
> Am Mon, Feb 26, 2024 at 07:26:57AM -0800 schrieb Felix Lechner:
>> How about a 48-hour period every month in which commits are permitted
>> even if they cause "world rebuilds"?
>> We could pause the substitute builders during that period. It would get
>> rid of
On 2024-02-22, Steve George wrote:
> We're going to run some online patch review sessions. The first one is on
> *Thursday, 7th March* and you can sign-up here:
>
> https://libreplanet.org/wiki/Group:Guix/PatchReviewSessions2024
Hoping to make it for some of these, thanks for doing it!
One
On 2024-02-07, Josselin Poiret wrote:
> The fact that you have to wait for Debbugs's response after the first
> mail to get the proper mail to reply to means that we can't automate
> sending whole patchsets, and have to resort to hacks like the CLI `mumi`
> tool uses. I can't just send a patchset
On 2024-02-02, Attila Lendvai wrote:
>> > for an average unix user a service is a process that is running in the
>> > backgroud, doing stuff mostly without any user interaction. you can
>> > try to argue this away, but i'm afraid that this is the state of
>> > things.
>>
>>
>> I don’t think it’s
On 2024-01-31, Josselin Poiret wrote:
> One conundrum we have for now: glibc 2.38 has a couple of new CVEs, and
> we have three options:
> 1) change glibc to track the 2.38 release branch → world rebuild.
> 2) graft glibc → bad user experience (and we're not supposed to graft
> outside of master).
So, I stumbled a bit with a fairly recently installed aarch64/arm64
system. The install went fine late December, but then I tried "guix
system reconfigure" a couple days ago, and even though it is a very
simple configuration (based on bare-bones.tmpl with grub-efi)... it
pretty much needed to
On 2024-01-03, Wojtek Kosior via wrote:
> Before getting back to the discussion, please let me ask 1 question.
> Assume I submit a patch series that adds some useful and needed code and
> includes a copyright notice with a promise, like this
>
> ;;; Copyright © 2023 Wojtek Kosior
> ;;; Wojtek
On 2023-12-03, Efraim Flashner wrote:
> On Fri, Dec 01, 2023 at 11:58:57AM -0800, Vagrant Cascadian wrote:
>> On 2023-11-18, Herman Rimm wrote:
>> > * gnu/local.mk: Register image.
>> > * gnu/system/images/orangepi-r1-plus-lts-rk3328.scm: New file.
>> > * gnu/
On 2023-11-18, Herman Rimm wrote:
> * gnu/local.mk: Register image.
> * gnu/system/images/orangepi-r1-plus-lts-rk3328.scm: New file.
> * gnu/system/install.scm (orangepi-r1-plus-lts-rk3328-installation-os):
> New variable.
I guess this opens in my mind a larger question of how many images do we
On 2023-11-08, Felix Lechner via wrote:
> On Wed, Nov 08 2023, Maxim Cournoyer wrote:
>> A source tree doesn't produce a derivation. A derivation is the
>> complete build recipe that captures the source and the package
>> definition, that when built by the daemon produces a store item.
>
> Okay,
On 2023-09-14, Giovanni Biscuolo wrote:
> Maxim Cournoyer writes:
>> I like the 'Closes: ' trailer idea; it's simple. However, it'd need to
>> be something added locally, either the user typing it out (unlikely for
>> most contributors) or via some mumi wizardry (it's unlikely that all
>> users
On 2023-09-15, Liliana Marie Prikler wrote:
> Am Donnerstag, dem 14.09.2023 um 15:51 -0700 schrieb Vagrant Cascadian:
>> On 2023-09-10, Liliana Marie Prikler wrote:
>> > Am Donnerstag, dem 07.09.2023 um 09:12 -0700 schrieb Vagrant
>> > Cascadian:
>> > > I a
On 2023-09-10, Liliana Marie Prikler wrote:
> Am Donnerstag, dem 07.09.2023 um 09:12 -0700 schrieb Vagrant Cascadian:
>> I am much more comfortable with the "Fixes" convention of:
>>
>> Fixes: https://issues.guix.gnu.org/NNN
> I like the idea, but we sho
On 2023-09-13, Maxim Cournoyer wrote:
> Vagrant Cascadian writes:
>> On 2023-09-09, Maxim Cournoyer wrote:
>>> The Change-Id stays the same unless you manually edit it out of your
>>> commit message when amending / rebasing, so the commit hash may change
>>>
On 2023-09-13, Christopher Baines wrote:
> I think this has been talked about for a while [1], but I want to make it
> happen. Currently the guix-daemon is still similar to the nix-daemon
> that it was forked from, and is implemented in C++. I think that a Guile
> implementation of the guix-daemon
On 2023-09-09, Maxim Cournoyer wrote:
> Vagrant Cascadian writes:
>>> Did you see my message about integrating a commit-hook similar to what
>>> Gerrit uses? It produces unique ID such as:
>>>
>>> --8<---cut here--
On 2023-09-11, Simon Tournier wrote:
> On Mon, 11 Sep 2023 at 16:23, Ludovic Courtès wrote:
>> Note that the patch series adds a hard dependency on Git.
>> This is because the existing ‘git-fetch’ code depends on Git,
>> which is itself motivated by the fact that Git supports
>> shallow clones
On 2023-09-06, Maxim Cournoyer wrote:
> Simon Tournier writes:
>> On Wed, 06 Sep 2023 at 16:55, Christopher Baines wrote:
>>
>>> Once we know what tags to use, I can have the QA frontpage do something
>>> similar to the "Mark as moreinfo" links, so it's easy to just click a
>>> button then send
On 2023-09-07, Giovanni Biscuolo wrote:
> Hi Maxim and Ludovic,
> Maxim Cournoyer writes:
>> Giovanni Biscuolo writes:
..
>>> When I asket I though the best way would be to scan for a string like
>>> "Close #" in the commit message (the committer should add
>>> such a string) but probably this
On 2023-09-07, Maxim Cournoyer wrote:
> Felix Lechner writes:
>> On Thu, Sep 7, 2023 at 4:08 AM Giovanni Biscuolo wrote:
>>>
>>> close the bugs that are listed in
>>> the commit message
...
> Did you see my message about integrating a commit-hook similar to what
> Gerrit uses? It produces
post-receive hook).
>
> Oh I see, thanks!
>
> This is a complex case (see below), at least not one that can be solved
> by automatically closing bug reports upon commits :-O
>
> Sorry for the confusion I added by pointing out the wrong example, a
> quick look at many bug r
On 2023-09-06, Liliana Marie Prikler wrote:
> Am Dienstag, dem 05.09.2023 um 19:41 -0400 schrieb brian
>> ‘* foo/bar.scm new-package (inputs): add input’
>>
>> stuff. I literally can never remember this format, no matter how many
>> times I do it. I'm reasonably sure square brackes go in there
On 2023-09-03, Ricardo Wurmus wrote:
> Maxim Cournoyer writes:
>
>> In the simplest case, it can be as simple as:
>>
>> $ ./pre-inst-env guix refresh -u some-package
>> [build it, try it, fix if needed]
>> $ ./etc/committer.scm
>> $ git send-email
>>
>> Since it's a single patch, there's no
On 2023-07-11, Timothy Sample wrote:
> Vagrant Cascadian writes:
>> My current best idea is the handful of food carts at pioneer courthouse
>> square
...
> This sounds great, but I just remembered that FOSSY provides lunch!
> Maybe we should roll with that – it would mak
On 2023-07-06, Timothy Sample wrote:
> Vagrant Cascadian writes:
>> On 2023-07-04, Timothy Sample wrote:
>>
>>> What about having a Guix lunch on Friday?
...
>> There are not a lot of things near the venue, but I will look for
>> options that are nearby and/
On 2023-07-04, zamfofex wrote:
>> On 07/03/2023 6:39 AM -03 Simon Tournier wrote:
>>
>> Well, I do not see any difference between pre-trained weights and icons
>> or sound or good fitted-parameters (e.g., the package
>> python-scikit-learn has a lot ;-)). As I said elsewhere, I do not see
>>
On 2023-07-04, Timothy Sample wrote:
> Vagrant Cascadian writes:
>> On 2023-06-29, Timothy Sample wrote:
>>> The first FOSSY (Free and Open Source [Software] Yearly) conference
>>> is coming up in two weeks! It’s being hosted in Portland, OR by the
>>> Softw
On 2023-06-29, Timothy Sample wrote:
> The first FOSSY (Free and Open Source Yearly) conference is coming up in
> two weeks! It’s being hosted in Portland, OR by the Software Freedom
> Conservancy.
>
> I was looking over the schedule and I spotted a few familiar names from
> the Guix community.
On 2023-06-24, Nicolas Graves via "Development of GNU Guix and the GNU System
distribution." wrote:
> On 2023-06-24 13:08, Csepp wrote:
>> Nicolas Graves via "Development of GNU Guix and the GNU System
>> distribution." writes:
>> IMHO LLMs for Guix are so damn not worth the effort. It will
On 2023-06-11, Maxim Cournoyer wrote:
> Maxime Devos writes:
>> Op 02-06-2023 om 20:02 schreef Nicolas Graves:
>>> A few months ago, Maxime Devos worked on a new rust-build-system to
>>> handle a few issues we were experiencing with cargo (see discussions on
>>> antioxidant in guix-devel).
>>> A
On 2023-05-25, Christopher Baines wrote:
> France:wget
> https://bordeaux.guix.gnu.org/nar/lzip/078vr3r8mn3yrwzwxw64hmcyshic9p3q-stellarium-0.21.0
> US:wget
> https://bordeaux-us-east-mirror.cbaines.net/nar/lzip/078vr3r8mn3yrwzwxw64hmcyshic9p3q-stellarium-0.21.0
> Singapore: wget
>
On 2023-05-24, Felix Lechner via "Development of GNU Guix and the GNU System
distribution." wrote:
> On Wed, May 24, 2023 at 2:01 PM Vagrant Cascadian wrote:
>>
>> Please revert ASAP.
>
> I am not affected, but if I understood Maxim's message from 5/18
> co
On 2023-05-19, Simon Tournier wrote:
> On ven., 19 mai 2023 at 11:34, Josselin Poiret wrote:
>> I'm curious Leo, in general (not Guix because we have a pre-push hook),
>> how do you make sure you always publish signed commits? I don't want to
>> put unsigned commits anywhere except locally, but
Philip McGrath recently pointed out that the /etc/profile.d/guix.sh
snippet had not been updating in the Guix packaging for Debian:
https://bugs.debian.org/1036304
(and as bonus complication, was also renamed to zzz-guix.sh)
The reason I never noticed before is because it is actually a manual
I've noticed there is some trailing whitespace in /etc/guix/acl ... some
of it comes from the keys in etc/substitutes/ci.guix.gnu.org.pub ... but
some of it comes from whatever code assembles /etc/guix/acl (or rather,
whatever the symlink points to in /gnu/store).
I noticed this by trying to add
On 2023-04-23, Guillaume Le Vaillant wrote:
> Here are a few leaf packages that don't build because of some
> failing dependencies:
> - blender is blocked by opencolorio
> - electrum is blocked by python-ledgerblue
Hrm this is kind of an aisde, but python-ledgerblue is a plugin for
electrum to
On 2023-04-19, Felix Lechner via wrote:
> Given the broad popularity of LUKS full-disk encryption among our
> fellow Guix users, I thought the community might appreciate reading
> about potentially weak key-derivation functions in older LUKS
> installations. [1]
>
> The article even offers fixes,
On 2023-04-17, Simon Tournier wrote:
> On lun., 17 avril 2023 at 15:32, Ludovic Courtès wrote:
>
>> My plan is to write a service that makes it easy to offload a build to a
>> VM that runs with a different time (“in the past”) or something along
>> these lines to mitigate the problem.
>
> Do you
On 2023-03-08, Maxim Cournoyer wrote:
> On a side note, it would also introduce some kind of hierarchy in the
> group, which I dislike. One of the things that make Guix special is
> that it's pretty flat -- everybody can participate at the same level, at
> least between committers). I'd rather
On 2023-02-27, Efraim Flashner wrote:
> I've been thinking some about how we create our disk images for aarch64
> devices and how we'll eventually create images for riscv64 devices.
> Currently we use u-boot to load extlinux to boot linux. I propose we use
> u-boot with its EFI interface to load
On 2023-02-21, Christopher Baines wrote:
> So probably in part due to the recent changes to the commit policy [1] I
> think there are more "simple" changes being sent to guix-patches by
> committers, which I think is good, but that's got me thinking about the
> process for these changes.
>
> 1:
>
On 2023-01-27, Simon Tournier wrote:
> On sam., 12 nov. 2022 at 17:54, Vagrant Cascadian wrote:
>> On 2022-11-05, Ludovic Courtès wrote:
>>> Vagrant Cascadian skribis:
>>>> From bfa13fdd3616839883e50efbbc05fb132610ce67 Mon Sep 17 00:00:00 2001
>>>> From
On 2023-01-09, Simon Tournier wrote:
> On ven., 06 janv. 2023 at 10:42, Vagrant Cascadian wrote:
>> More I wanted to look through the patch text rather than the package
>> descriptions. It would ideally catch things like "reproducible" or
>> "deterministic&qu
On 2023-01-06, Simon Tournier wrote:
> On Tue, 03 Jan 2023 at 22:11, Vagrant Cascadian wrote:
>
>> Perhaps a description would for the team(s) would help a bit here. I
>> see embedded as dealing with bootloaders or firmware commonly used on
>> embedded systems, and
stly, I use the name "Vagrant Cascadian" with my contributions to
guix, but I may use a different email address depending on the nature of
the contribution (e.g. reproducible builds). I am not sure what would
happen if I added "Vagrant Cascadian" twice, with two different email
a
me.
>
> * gnu/packages/bootloaders.scm (u-boot-am335x-evm-boneblack): Remove the
> NAME-SUFFIX keyword argument. Specify the full name via the name field.
> * gnu/bootloader/u-boot.scm (u-boot-beaglebone-black-bootloader): Adjust to
> the renamed package.
>
> Report
On 2022-12-26, Maxim Cournoyer wrote:
> Vagrant Cascadian writes:
>> On 2022-12-22, Maxim Cournoyer wrote:
>>> Vagrant Cascadian writes:
>> I will take a guess that it was commit
>> c2c1dfdf5760873f1db86d14873f725a105f7feb which removed the "name"
On 2022-12-24, jgart wrote:
> I wanted to ask you what are your thoughts on this idea. This is a
> thought experiment at this stage.
>
> Should GNU Guix be a small core of packages (and services?)?
>
> For example, GNU Guix would be a core channel containing the reduced
> binary seed bootstrap and
On 2022-12-22, Maxim Cournoyer wrote:
> Vagrant Cascadian writes:
>
>> Wondering what necessitated this change from the old variable name to a
>> new name...
>>
>> commit c04528d2a2597d79278833f3607c806278253446
>> Author: Maxim Cournoyer
>> Date: Tu
On 2022-12-21, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>
>> Well, that is what I did, pulled guix to the curren wip-guile-ssh-0.16
>> branch (which contains an update to guile-ssh 0.16 and updates guix to
>> use a commit containing that), and managed to gu
Wondering what necessitated this change from the old variable name to a
new name...
commit c04528d2a2597d79278833f3607c806278253446
Author: Maxim Cournoyer
Date: Tue Dec 20 21:25:27 2022 -0500
gnu: u-boot-am335x-evm-boneblack: Fix variable name.
* gnu/packages/bootloaders.scm
On 2022-12-20, Vagrant Cascadian wrote:
> On 2022-11-02, Ludovic Courtès wrote:
>> Vagrant Cascadian skribis:
>>> On 2022-10-28, Vagrant Cascadian wrote:
>>>> Updating guile-ssh to 0.16.0 actually went mostly smoothly, except
>>>> guix-jupytertest
On 2022-11-02, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>> On 2022-10-28, Vagrant Cascadian wrote:
>>> Updating guile-ssh to 0.16.0 actually went mostly smoothly, except
>>> guix-jupytertest suites fail.
...
>> For clarity, I used:
>>
>> .
On 2022-12-11, Ludovic Courtès wrote:
> The second release candidate of the upcoming 1.4.0 release is now
> available for testing, fixing issues that were reported for rc1:
Also available in .deb format on your favorite Debian mirrors:
https://tracker.debian.org/pkg/guix
Currently only in
On 2022-11-02, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>> On 2022-10-28, Vagrant Cascadian wrote:
>>> I've been poking at updating guile-ssh to 0.16.0 and libssh to 0.10.4 in
>>> guix, but hit a few blockers.
>>>
>>> Updating guile-ssh to
On 2022-12-07, jg...@dismail.de wrote:
> We have abjad packaged but we don't necessarily have all the
> dependencies needed to build everything that abjad provides such as a
> PDF document that it mentions in its project Makefile.
>
> Should we include the LaTeX dependencies in the abjad package?
On 2022-12-03, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>
>> In guix/packages.scm:
>> 1295:37 5 (_)
>> 1555:16 4 (package->bag _ _ _ #:graft? _)
>> 1652:22 3 (thunk)
>> In guix/gexp.scm:
>> 523:11 2 (l
On 2022-12-01, Ludovic Courtès wrote:
> I’m pleased to announce Guile-Gcrypt version 0.4.0:
>
> git clone https://notabug.org/cwebber/guile-gcrypt.git
> cd guile-gcrypt
> git checkout v0.4.0 # or 425554d4327eeeb60c39e3d4a1b7bc5e36b63953
> git tag -v v0.4.0
FWIW, I updated guile-gcrypt to
On 2022-12-02, Ludovic Courtès wrote:
> Release progress: week 8.
>
> Apologies for not sending this one on time this Thursday; instead we got
> RC1, which is nice. :-)
>
> https://lists.gnu.org/archive/html/guix-devel/2022-12/msg0.html
Yay, love not having to build the source tarball to
On 2022-11-28, Ludovic Courtès wrote:
> You might remember that I started long ago asking people who had
> contributed to the blog whether they would agree to licensing their work
> under CC-BY-SA 4.0 and GFDL version 1.3 or later, with no Invariant
> Sections, no Front-Cover Texts, and no
On 2022-11-26, Simon Josefsson via "Development of GNU Guix and the GNU System
distribution." wrote:
> I find use of the term 'advanced' wrt Guix confusing and even mildly
> excluding, even though it is wide-spread. What is advanced about Guix?
> Can I use it even if I'm not an advanced user?
I've been working on adding support for MNT/Reform to guix
https://mnt.re/media/reform_md/2020-05-08-the-much-more-personal-computer.html
Just pushed the wip-mnt-reform branch; all it has is a kernel that I
have sucessfully booted on Debian, so it should be theoretically
possible to build a
On 2022-11-05, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>> From bfa13fdd3616839883e50efbbc05fb132610ce67 Mon Sep 17 00:00:00 2001
>> From: Vagrant Cascadian
>> Date: Wed, 2 Nov 2022 19:56:12 -0700
>> Subject: [PATCH 01/12] guix: lint: Exclude some "@&
On 2022-11-03, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>>>> test-name: channel-news, no news
>>>> ...
>>>> actual-error:
>>>> + (git-error
>>>> + #< code: -1 message: "invalid version 0 on
>>>> g
On 2022-11-03, Vagrant Cascadian wrote:
> On 2022-11-03, Ludovic Courtès wrote:
>> Vagrant Cascadian skribis:
>>
>>> --- a/guix/lint.scm
>>> +++ b/guix/lint.scm
>>> @@ -313,7 +313,8 @@ (define (tests-explicitly-enabled?)
>>>'(
On 2022-11-03, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>
>> --- a/guix/lint.scm
>> +++ b/guix/lint.scm
>> @@ -313,7 +313,8 @@ (define (tests-explicitly-enabled?)
>>'()))
>>
>> (define (properly-starts-sentence? s)
>>
leaves a lot of room for improvement. :)
live well,
vagrant
From 209c97b91d02831d78fc0b032f3b83fd5e0b9cb1 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Wed, 2 Nov 2022 19:56:12 -0700
Subject: [PATCH] guix: lint: Exclude "@code{" from various checks.
The visual representation of the releve
On 2022-11-02, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>
>> On 2022-10-27, Ludovic Courtès wrote:
>>> Release progress: week 3.
>> ...
>>> • Architectures:
>>>
>>> - powerpc64le-linux builds are back behind ci.guix, than
On 2022-10-28, Vagrant Cascadian wrote:
> On 2022-10-28, Vagrant Cascadian wrote:
>> I've been poking at updating guile-ssh to 0.16.0 and libssh to 0.10.4 in
>> guix, but hit a few blockers.
>>
>> Updating guile-ssh to 0.16.0 actually went mostly smoothly, except
>
On 2022-10-28, Vagrant Cascadian wrote:
> I've been poking at updating guile-ssh to 0.16.0 and libssh to 0.10.4 in
> guix, but hit a few blockers.
>
> Updating guile-ssh to 0.16.0 actually went mostly smoothly, except
> guix-jupytertest suites fail.
>
> Looking at guix-jupy
From: Vagrant Cascadian
Date: Thu, 27 Oct 2022 13:13:28 -0700
Subject: [PATCH 1/2] gnu: guile-ssh: Update to 0.16.0.
* gnu/packages/ssh.scm (guile-ssh): Update to 0.16.0.
---
gnu/packages/ssh.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/ssh.scm b/gnu
On 2022-10-27, Ludovic Courtès wrote:
> Release progress: week 3.
...
> • Architectures:
>
> - powerpc64le-linux builds are back behind ci.guix, thanks to
>Tobias!
...
> - armhf-linux: No progress so far.
Not sure where this fits into the release process, but I uploaded a git
On 2022-10-24, Joshua Branson wrote:
> Kevin Vigouroux via "Development of GNU Guix and the GNU System
> distribution." writes:
>
>> I would like to install Guix (System) on the Banana Pi M5 [0]. The
>> board is “open source” but not the firmware released by Amlogic [1].
>>
>> The platform
On 2022-10-07, Efraim Flashner wrote:
> On Thu, Oct 06, 2022 at 04:50:22PM +0200, Ludovic Courtès wrote:
> Firstly, I'd like to mention that we, in general, have a minimum system
> requirement of 2GB of RAM, and IIRC there aren't a lot of armhf boards
> out there which have that much. We do have
On 2022-09-25, Andreas Enge wrote:
> I am not quite sure how one presents a distribution at a booth, since
> there is not really much to attract the eye, or is there?
I know Debian used to have an automated debian-installer running on a
screen looping through all the supported languages of the
On 2022-09-05, zimoun wrote:
> On mer., 24 août 2022 at 14:06, Vagrant Cascadian wrote:
>
>> Maybe something like:
>>
>> (define-public thispackages
>> (package
>>(name "thispackages"
>>...
>>(lint-overides
>>
On 2022-08-24, zimoun wrote:
> On Tue, 23 Aug 2022 at 15:22, Vagrant Cascadian wrote:
>
>> But, because there is no way to silence a particular inappropriate
>> suggestion from guix lint, it becomes noise, and each person evaluating
>> the results of the package in the f
On 2022-08-24, Liliana Marie Prikler wrote:
> Am Mittwoch, dem 24.08.2022 um 14:53 +0200 schrieb Nicolas Goaziou:
>> Liliana Marie Prikler writes:
>>
>> > The packages
>> > - drascula,
>> > - lure,
>> > - queen, and
>> > - sky
>> > all share issues that make me question whether they should be in
I love guix lint! The vast majority of the time I even use it!
But... sometimes a guix lint suggestion isn't appropriate, at which
point it becomes noise for future contributors of that package.
tt might not be possible, or at least not worth the effort, to improve
guix lint to catch that
On 2022-06-12, Vagrant Cascadian wrote:
> I've been working on Reproducible Builds in guix a fair amount this
> month.
I did another round of this...
I fixed a few packages recently, and noticed some other people fixing
packages too, yay!
As of this moment for x86_64, it looks like:
On 2022-08-13, Tobias Platen wrote:
> Today I began building the Guix System for my ROCKPro64.
> I installed Guix on top of Debian and tried to build uboot, it works:
>
> guix build u-boot-rockpro64-rk3399
> successfully built /gnu/store/g1d4kjgn9b46vqk9mwhd0kc2r6sfi7cz-u-boot-
>
On 2022-07-04, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>> --- a/gnu/packages/tex.scm
>> +++ b/gnu/packages/tex.scm
>> @@ -395,6 +395,12 @@ (define-public texlive-bin
>> (("srcdir/tests/pprecA-0.ind
On 2022-06-07, Nicolas Goaziou wrote:
> kias...@disroot.org writes:
>
>> I've been watching the Repology page for Guix and I've noticed that
>> we've dropped to 51% outdated packages
>> [https://repology.org/repository/gnuguix]. We used to be at 40%
>> outdated packages a few months ago.
>
>
On 2022-07-14, zimoun wrote:
> Well, dreaming about science fiction, it appears me more approachable to
> have Guix running on something as Debian/kfreeBSD – it could be an
> interesting project with the help of Debian folks. Other said, “just”
> replace the Linux kernel by a variant of the
On 2022-07-12, John Kehayias wrote:
> Apologies for the long email, so let me start with the punchline:
> attached is a diff which adds an '--fhs-container' (or -F) option to
> guix shell/environment to set up an FHS-like container. This includes
> the usual /lib directory and a glibc which loads
On 2022-07-11, Vagrant Cascadian wrote:
> I hear Efraim say better to have unique randomness and no substitutes,
> and I hear Tobias say more or less it's ok as long as upstream is right
> about it being ok to embed a specific prime as other random numbers get
> mixed in at runtime..
On 2022-06-28, Tobias Geerinckx-Rice wrote:
>>I am at a loss as to what to do then ... nothing and just have it be
>>unreproducible? embed a specific random number? come up with better
>>upstreamable patches?
>
> From upstream's response and my own biases and my reading of the room here,
> I'd
On 2022-07-03, Andreas Enge wrote:
> Am Sun, Jul 03, 2022 at 12:53:09PM +0300 schrieb Efraim Flashner:
>> I misread the source. I'd like glibc-utf8-locales built with glibc-final.
>
> Has glibc-utf8-locales not been removed some time ago? I always had it in
> my profile, then saw a message during
On 2022-06-23, Maxim Cournoyer wrote:
>>> Perhaps to show our stand here we could patch our copy of pdftex with
>>> 's/FORCE_SOURCE_DATE/SOURCE_DATE_EPOCH/', lest we end up with a grocery
>>> list of *SOURCE_DATE* variable variants.
>>
>> Sure, with some technical details fixed up, as I think they
On 2022-06-28, Gábor Boskovits wrote:
> Tobias Geerinckx-Rice ezt írta (időpont: 2022. jún. 28., K
> 18:07):
>> Vagrant said:
>> > It is expensive to generate the random prime on some hardware, so doing
>> > so at runtime might not be feasible in some cases...
>>
>> But in the same reply you're
On 2022-06-22, Vagrant Cascadian wrote:
> On 2022-06-08, Vagrant Cascadian wrote:
>> On 2022-06-08, Efraim Flashner wrote:
>>> On Tue, Jun 07, 2022 at 07:20:25AM +0200, Julien Lepiller wrote:
>>>> On June 7, 2022 5:24:22 AM GMT+02:00, Felix Lechner
>>>>
On 2022-06-08, Vagrant Cascadian wrote:
> On 2022-06-08, Efraim Flashner wrote:
>> On Tue, Jun 07, 2022 at 07:20:25AM +0200, Julien Lepiller wrote:
>>> On June 7, 2022 5:24:22 AM GMT+02:00, Felix Lechner
>>> wrote:
>>> >On Mon, Jun 6, 2022 a
1 - 100 of 269 matches
Mail list logo
