Ludovic Courtès writes:
> Release progress: week 1.
>
> Ludovic Courtès skribis:
>
>> Here’s a list of things to do to get there:
>>
>> • Merge ‘staging’ (?). What’s the status of that one, it seemed ready
>> a couple of weeks ago, but then I lost track of it. Marius?
>
> Marius, any
Ludovic Courtès writes:
> We need to plan and coordinate. Releases have to be a group effort;
> some of the most important work won’t be coding but coordination.
> Coordination is key. I don’t think I should be spearheading that
> effort, but I’m happy to be part of it.
>
> Who’s ready to
Tanguy LE CARROUR writes:
>> - Minimise the burden for submitters
>> - Lengthy guidance for submitting patches
>
> Actually, the `16.4 Packaging Guidelines` and `16.6 Submitting Patches`
> are everything that I've ever looked for.
I think the point here is that the Submitting Patches
Ludovic Courtès writes:
> Hi,
>
> Christopher Baines skribis:
>
>> Ludovic Courtès writes:
>>
>>> I wonder if it’s due to recent changes since I last looked, but I’m a
>>> bit confused by the numbers in this example:
>>>
>>> ht
Ludovic Courtès writes:
> I wonder if it’s due to recent changes since I last looked, but I’m a
> bit confused by the numbers in this example:
>
> https://qa.guix.gnu.org/issue/58186
>
> The numbers before/after patches don’t match and the lint warnings (nice
> addition!) appear to unrelated
Christopher Baines writes:
> Since it's easier to iterate once there's something visible, I've just
> stuck what I've got so far on the internet, it's available at:
>
> https://qa.guix.gnu.org/
>
> The code is here [3] and I've put a list of ideas in the README.
>
> 3:
Here are some notes I took during the discussion on patch review/quality
assurance at the 10 Years of Guix event.
Discussion:
- Find out how others review patches
- Julian
- Subscribe to guix-patches
- Look at subjects
- If not OCaml/Java/Maven, ignore email
- If obvious issues
Hey!
I think I sent the last message to guix-devel on this topic back in
February [1].
1: https://lists.gnu.org/archive/html/guix-devel/2022-02/msg00102.html
I haven't had a lot of time or motivation this year, but I've still been
trying to chip away at this.
The recent new thing is that I've
Hey,
The last update was sent out in May [1], so this update roughly covers
the last 3 months.
1: https://lists.gnu.org/archive/html/guix-devel/2022-05/msg00202.html
This hasn't been my primary focus, so some of the changes that somewhat
involve bordeaux.guix.gnu.org relate to using it for
Zelphir Kaltstahl writes:
> I am messing around again with updating a package and according to my
> own guide from previous adventures, I have to run the following
> command to generate the `pre-inst-env` script, in the root directory
> of the guix sources:
>
>
> guix environment guix --
zimoun writes:
> Hi,
>
> On mer., 06 juil. 2022 at 12:41, Christopher Baines wrote:
>
>>> What am I doing wrong?
>>
>> guix weather doesn't check substitute trust, so you've probably not got
>> the bordeaux.guix.gnu.org key in your ACL.
>
> Indeed.
zimoun writes:
> That’s said, I do not understand the result of “guix weather” and “guix
> build”. Let pick an example. Using Guix 06493e7, the package
> julia-staticarrays is unavailable on Berlin (ci.guix) and available on
> Bordeaux (bordeaux.guix). So far, so good!
>
> $ guix weather
Ludovic Courtès writes:
>>> IWBN to share as much code as possible with ‘guix publish’, which has
>>> great test suite coverage and is being hammered every day. Clearly the
>>> bit about extracting nars is specific to the nar-herder though, so that
>>> may prove difficult.
>>
>> I'm going to
Ludovic Courtès writes:
>> The code isn't great, there's some difficulty in extracting the single
>> file from the nar, but the biggest problem is a limitation in the guile
>> fibers web server. Currently, responses have to be read in to memory,
>> which is fine for we pages, but not great if
Hey!
The nar-herder helps with managing a collection of nars. There's some
overlap with the functionality of guix publish in that both tools can
serve narinfo files which is a key part of providing substitutes.
One thing that guix publish does aside from serving narinfo files is
providing access
Christopher Baines writes:
> So, one thing that I'd be interested in, is hearing from anyone who
> thinks they get worse download performance from bordeaux.guix.gnu.org or
> ci.guix.gnu.org than they get when downloading other
> things. Importantly, it would be good to know r
Ludovic Courtès writes:
> Hopefully we’ll get a clearer picture in the coming days…
There is starting to be some information in the QA data service instance:
Hey!
So the nar-herder came in to existence at the end of last year (2021)
and while the main use at the time was addressing the lack of storage on
bayfront, I also hoped to improve the situation regarding mirrors for
substitutes.
I'm not in a great situation to test this though, as my usual
Hi!
The last update was sent out in February [1], so this update covers
roughly the last 3 months.
1: https://lists.gnu.org/archive/html/guix-devel/2022-02/msg00099.html
### Summary
bordeaux.guix.gnu.org is one of the default sources of substitutes, the
other one being ci.guix.gnu.org.
I
guix-comm...@gnu.org writes:
> apteryx pushed a commit to branch master
> in repository guix.
>
> commit 223a3d7f7fdb6af9c4c090785cab15d38680e887
> Author: Maxim Cournoyer
> AuthorDate: Mon Apr 4 00:06:48 2022 -0400
>
> gnu: git: Update to 2.35.1.
>
> * gnu/packages/version-control.scm
Ricardo Wurmus writes:
> Ricardo Wurmus writes:
>
>> Hi Guix,
>>
>> I had to manually run the build of llvm 11 on aarch64, because it would
>> keep timing out:
>>
>> time guix build
>> /gnu/store/0hc7inxqcczb8mq2wcwrcw0vd3i2agkv-llvm-11.0.0.drv --timeout=99
>>
From: Christopher Baines
Date: Fri, 18 Feb 2022 23:06:57 +
Subject: [PATCH] channels: Allow disabling grafts when computing derivations.
---
build-aux/build-self.scm | 23 +++
guix/channels.scm| 19 +++
2 files changed, 26 insertions(+), 16
Mathieu Othacehe writes:
>> I like Chris Baines’ idea of decoupling nar distribution from nar
>> building. If we want to keep nars long enough so that ‘time-machine’ is
>> usable, then storage requirements will keep growing.
>>
>> Perhaps that means we can regularly copy nars “elsewhere” for
Ludovic Courtès writes:
>> The only thing I can see that's required before merging though is the
>> exports. I'm now thinking about this kind of thing (getting data out of
>> the data service) in the context of patch/branch review.
>
> I think there’s a couple of issues that would be nice to
Hey!
I think the last thread I started on this topic was all the way back in
August [1].
1: https://lists.gnu.org/archive/html/guix-devel/2021-08/msg1.html
Building on the feedback there, I've got two threads of work in mind for
the start of this year.
Firstly, work on getting data from
Hey!
It's not quite been a year since bordeaux.guix.gnu.org started
operating, but I thought I'd send out an update email towards the start
of 2022 looking back in to 2021 and looking forward to the rest of this
year.
If you're missing some context, this blog post should be useful, and has
lots
Ludovic Courtès writes:
> With a few exceptions, these articles do not have a clear license, which
> we would like to fix. We propose to dual-license all the articles under
> CC-BY-SA 4.0 and GFDL version 1.3 or later, with no Invariant Sections,
> no Front-Cover Texts, and no Back-Cover
Jack Hill writes:
> On Mon, 20 Dec 2021, zimoun wrote:
>
>> Hi,
>>
>> On Mon, 20 Dec 2021 at 23:07, Ludovic Courtès wrote:
>>
>>> Regarding nar-herder, I think it’d be nice to have a solution to
>>> mirroring in Guix proper, developed similarly to other components,
>>> because it could be a
zimoun writes:
> On Mon, 20 Dec 2021 at 23:07, Ludovic Courtès wrote:
>
>> Regarding nar-herder, I think it’d be nice to have a solution to
>> mirroring in Guix proper, developed similarly to other components,
>> because it could be a fairly central tool.
>>
>> ‘guix publish’ is probably not
Hi!
I rushed the nar-herder [1] in to existence back in December, to address
the buildup of nars on bayfront by moving the nars to another machine
with more space to store them.
1: https://git.cbaines.net/guix/nar-herder/about/
This was something I was planning for a while though, I sent an
Ludovic Courtès writes:
> Hello Guix!
>
> Here’s a client module for the Guix Data Service, allowing you to access
> a subset of the Guix Data Service interfaces from the comfort of your
> REPL.
>
> I had it sitting in my source tree for a while and Chris sent me an
> impressive shell one-liner
Ludovic Courtès writes:
> Luis Felipe skribis:
>
>> But I wonder if it is possible now to make the packages part use any of the
>> Postgres databases that already exist and allow traditional search without
>> JavaScript...
>
> Former Outreachy intern Danjela Lura, together with Chris Baines,
Ludovic Courtès writes:
>> However, due to the time spent not building things, the backlog is
>> longer than usual, and the substitute availability (especially for
>> x86_64-linux and i686-linux) is lower than usual.
>
> Yeah, ‘guix weather coreutils’ finds nothing on bordeaux.guix right now.
Ludovic Courtès writes:
> We were unlucky enough that it happened days after the other build farm,
> bordeaux.guix.gnu.org, ran out of disk space and had its CI stopped,
> right before the big merge—so it doesn’t have substitutes for current
> master.
Builds effectively stopped on the 29th of
zimoun writes:
> Hi Chris,
>
> On Thu, 16 Dec 2021 at 00:20, Christopher Baines wrote:
>> zimoun writes:
>
>>> Do you think that Bordeaux could run
>>>
>>><https://git.savannah.gnu.org/cgit/guix.git/tree/etc/source-manifest.scm>
>>
zimoun writes:
> Hi Chris,
>
> Thanks for the update. And for the all work. :-)
>
>
> On Wed, 15 Dec 2021 at 16:48, Christopher Baines wrote:
>
>> In summary, the space issue I mentioned in the previous update has
>> effectively been addressed. All t
Hey!
I sent out the last update 3 weeks ago [1].
1: https://lists.gnu.org/archive/html/guix-devel/2021-11/msg00154.html
In summary, the space issue I mentioned in the previous update has
effectively been addressed. All the paused agents are now unpaused and
builds are happening again.
However,
Ricardo Wurmus writes:
> Ludovic Courtès writes:
>
>>> The disk space usage trend is pretty much
>>> linear, so if things continue without any change, I think it will
>>> be
>>> necessary to pause the agents within a month, to avoid filling up
>>> bayfront entirely.
>>
>> Ah, bummer. I hope
Ludovic Courtès writes:
> Christopher Baines skribis:
>
>> I've been doing some performance tuning, submitting builds is now more
>> parallelised, a source of slowness when fetching builds has been
>> addressed, and one of the long queries involved in allocating bu
Hey!
It's been 3 months since I sent the last update [1]. This email was
meant to go out on Friday, but it seems opensmtpd was broken on my
machine, so it got stuck.
1: https://lists.gnu.org/archive/html/guix-devel/2021-08/msg00075.html
First, some good things:
I've been doing some performance
Ludovic Courtès writes:
> Christopher Baines skribis:
>
>> guix-data-service: computing the derivation-file-name for mips64el-linux
>> Computing Guix derivation for 'mips64el-linux'...
>
> [...]
>
>> @ build-started
>> /gnu/store/l89jsjd4881jv5pgc
zimoun writes:
> I am confused because using Guix fb32a38, I get:
>
> $ guix weather obs
> computing 1 package derivations for x86_64-linux...
> looking for 1 store items on https://ci.guix.gnu.org...
> https://ci.guix.gnu.org
> 0.0% substitutes available (0 out of 1)
> unknown substitute
zimoun writes:
>> As for keeping build results, everything that's ever been built for
>> bordeaux.guix.gnu.org (that's only ~337739 things totalling ~1.4TiBs) is
>> still around. In some ways, this is because deleting things is a bit
>> more difficult, as the files aren't in the store, you
zimoun writes:
> Hi Chris,
>
> On Fri, 17 Sep 2021 at 18:42, Christopher Baines wrote:
>> Christopher Baines writes:
>>
>>> In summary: data.guix.gnu.org is going to be down while I attempt to
>>> restore a backup from earlier this week.
>>
>&g
Christopher Baines writes:
> In summary: data.guix.gnu.org is going to be down while I attempt to
> restore a backup from earlier this week.
The restore was actually quicker than I expected, only taking ~2 hours,
so data.guix.gnu.org is back now.
It's still going to take some time to ca
zimoun writes:
> Playing with the new 'etc/sources-manifest.scm', using fb32a38, I get:
>
> $ guix weather -m ~/src/guix/guix/etc/source-manifest.scm
> computing 16,831 package derivations for x86_64-linux...
> looking for 16,831 store items on https://ci.guix.gnu.org...
>
Vagrant Cascadian writes:
> On 2021-08-18, Christopher Baines wrote:
>> Around 2 months ago, bordeaux.guix.gnu.org came in to existence [1][2].
>>
>> 1:
>> https://guix.gnu.org/en/blog/2021/substitutes-now-also-available-from-bordeauxguixgnuorg/
>> 2: https:
Hey!
Around 2 months ago, bordeaux.guix.gnu.org came in to existence [1][2].
1:
https://guix.gnu.org/en/blog/2021/substitutes-now-also-available-from-bordeauxguixgnuorg/
2: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00044.html
This took work I'd done on providing substitutes back
br...@waegenei.re writes:
> Today I pushed 2 commits¹ related to the package to master, mainly to
> update it to 2.33.0. But since then https://data.guix.gnu.org/ went
> offline and Cuirass' evaluation #4930² has 556 failed build. Newly
> failed builds have unhelpful logs, ending with "cannot
Ludovic Courtès writes:
> Hi Chris,
>
> Christopher Baines skribis:
>
>> I was thinking of using Cuirass for building derivations when testing
>> patches, but I gave up on that approach back in 2019 after trying to use
>> it (I discussed trying to us
Mathieu Othacehe writes:
>> I think trying to change up how branches (staging/core-updates) are
>> tested is a good place to start. The concrete change I'm proposing is to
>> use an instance of the Guix Data Service plus an instance of the Guix
>> Build Coordinator to do the testing and builds,
Ludovic Courtès writes:
> Christopher Baines skribis:
>
>> So, I think I've recently switched to thinking about the problem as one
>> of testing changes, rather than just testing patches. Since both patch
>> series, and branches are used to propose changes, I t
Lars-Dominik Braun writes:
> Hi Christopher,
>
>> Anyway, I wouldn't like for this change to lower the standard though,
>> it's currently the only package in Guix with an invalid description (as
>> far as I'm aware), is there some reason why it doesn't have one?
> it simply fell through the
guix-comm...@gnu.org writes:
> lbraun pushed a commit to branch master
> in repository guix.
>
> commit 91ce17a53236578f8055a2588460047741983925
> Author: Lars-Dominik Braun
> AuthorDate: Fri Aug 6 08:29:12 2021 +0200
>
> gnu: Add rocminfo.
>
> * gnu/packages/rocm.scm (rocminfo): New
raid5atemyhomework writes:
> In any case, it looks to me that bordeaux is already in
> `%default-substitute-mirrors`, which this patch uses, so it should get
> included anyway as a fallback in case the SJTU mirror is not available
> or something. So maybe the patch is OK as-is?
I haven't
Hey,
This is sort of a followup to [1], at least I think that's the last main
email I sent out about testing changes (although I didn't use that
term). I did also send out some notes from the Guix Day event back in
February 2021 though [2].
1:
Julien Lepiller writes:
> One way to find the missing modules is to boot another distro (or
> maybe the installer has a lot more modules than the installed system)
> and look at dmesg. You might see something like:
>
> scsi host0: ahci-sunxi
> ata1: SATA max UDMA/133 mmio …
>
> sunxi-mmc
Vagrant Cascadian writes:
> On 2021-06-29, Christopher Baines wrote:
>> I've had a Honeycomb LX2 board for a few weeks now, but I've been
>> struggling to get Guix installed on it.
>>
>> The most success I've had is with an installer image written to either a
&g
Hey,
I've had a Honeycomb LX2 board for a few weeks now, but I've been
struggling to get Guix installed on it.
The most success I've had is with an installer image written to either a
USB drive or nVME drive. I changed the bootloader to the
grub-efi-bootloader, using the efi-raw image type, a
Ricardo Wurmus writes:
> Ludovic Courtès writes:
>
>> BTW, did I mention we have budget? :-) Is there affordable POWER9
>> hardware we could purchase?
>
> Aside from that: do we have rack space for a POWER9 machine?
>
> For a limited time I could probably host it at the MDC data centre,
>
Christopher Baines writes:
> Christopher Baines writes:
>
>> While I've been working on the software side of building things for
>> substitutes through the Guix Build Coordinator for over a year now [1],
>> I've only been personally pushing to bring the benefits to
Efraim Flashner writes:
> Last week my HiFive Umatched¹ board came and was quite the object of
> interest at the local computer store as I picked up a case, PSU and
> graphics card.
I also recently received a HiFive Umatched board which I ordered months
ago.
While I don't really have the time
Christopher Baines writes:
> While I've been working on the software side of building things for
> substitutes through the Guix Build Coordinator for over a year now [1],
> I've only been personally pushing to bring the benefits to Guix users by
> default for the last few week
Hey,
While I've been working on the software side of building things for
substitutes through the Guix Build Coordinator for over a year now [1],
I've only been personally pushing to bring the benefits to Guix users by
default for the last few weeks [2].
1:
Christopher Baines writes:
> Christopher Baines writes:
>
>> Is there still a path to bring some of these benefits to users, and if
>> so, what things need doing?
>
> It's been a few weeks now, so to summarise, I think only one path
> emerged, and that is to ge
Mathieu Othacehe writes:
> Hey Chris,
>
>> That sounds sensible. On the specific name, given this is just about
>> substitutes, and at least in my opinion has nothing to do with
>> continuous integration, maybe picking just another word would avoid
>> thinking too much, it could be bordeaux, or
Ludovic Courtès writes:
> Hello!
>
> Christopher Baines skribis:
>
>> Christopher Baines writes:
>>
>>> Is there still a path to bring some of these benefits to users, and if
>>> so, what things need doing?
>
> [...]
>
>> Obvious
Christopher Baines writes:
> Is there still a path to bring some of these benefits to users, and if
> so, what things need doing?
It's been a few weeks now, so to summarise, I think only one path
emerged, and that is to get substitutes from bayfront to users.
Bayfront was already r
Ludovic Courtès writes:
> Hi,
>
> Christopher Baines skribis:
>
>> If there's effort put in to getting substitutes served from bayfront,
>> why do you suggest not documenting how to get those substitutes in the
>> manual?
>
> Mostly because bayfront is not
guix-comm...@gnu.org writes:
> This is an automated email from the git hooks/post-receive script.
>
> ngz pushed a commit to branch master
> in repository guix.
>
> The following commit(s) were added to refs/heads/master by this push:
> new bb94429 gnu: Add emacs-wucuo.
> bb94429 is
Ludovic Courtès writes:
> That all sounds like a plan!
>
> Christopher Baines skribis:
>
>> There's a few intertangled things, but the main question is, if bayfront
>> can be a source of substitutes, what's the path to actually have that
>> benefit users?
>
Ludovic Courtès writes:
> Hi,
>
> Christopher Baines skribis:
>
>>> Now, the penalty it imposes is annoying. I’ve sometimes found myself
>>> working around it, too (because I knew the server was going to have the
>>> store item sooner than 1h).
>>
Christopher Baines writes:
> Andreas Enge writes:
>
>> Hello Chris,
>>
>> Am Sat, May 01, 2021 at 07:56:05PM +0100 schrieb Christopher Baines:
>>> I think there are some benefits for using the Guix Build Coordinator to
>>> build things for substit
Andreas Enge writes:
> Hello Chris,
>
> Am Sat, May 01, 2021 at 07:56:05PM +0100 schrieb Christopher Baines:
>> I think there are some benefits for using the Guix Build Coordinator to
>> build things for substitutes, and it would be good to work out how to
>> get thos
Ludovic Courtès writes:
> Christopher Baines skribis:
>
>> Ludovic Courtès writes:
>
>> As people are going to Cuirass to look at the build status for packages,
>> system tests and various branches, the problem is similar to that of
>> substitutes. It
Luciana Lima Brito writes:
> On Sun, 02 May 2021 10:20:56 +0100
> Christopher Baines wrote:
>
>> I think what things are happening when is relevant, but that's more
>> about understanding the hierarchy, rather than specific start and end
>> times.
>
>> Ba
Ludovic Courtès writes:
> Thanks for your message! It’s great to see a summary of what’s been
> cooking in the Coordinator and your vision around it.
>
> Christopher Baines skribis:
>
>> More specifically, while the architecture is similar to daemon
>> offloadin
Canan Talayhan writes:
>>From this I'm guessing the temp_package_metadata table has only one
>>row. My understanding is that this table would normally have as many
>>rows as packages in the revision of Guix being processed. It might not
>>be possible to reproduce the slowness of the query
Luciana Lima Brito writes:
> On Sat, 01 May 2021 20:07:56 +0100
> Christopher Baines wrote:
>
>> Luciana Lima Brito writes:
>>
>> > For that I propose to build 2 charts, one of the
>> > macro view, what we call "overview first", showing the
&g
Hey,
The Guix Build Coordinator has been around for a while, it's been
available in Guix for more than 6 months now. The setup I've been using
to test the Guix Build Coordinator for building things for substitutes
(guix.cbaines.net) has been running since mid 2020.
Anecdotally, the test setup
Luciana Lima Brito writes:
> On Sat, 01 May 2021 09:16:08 +0100
> Christopher Baines wrote:
>
>> Currently the timing of various sections of the process includes
>> timing smaller sections, and that may complicate reading the chart,
>> since it won't convey which t
Luciana Lima Brito writes:
> On Fri, 30 Apr 2021 18:05:15 +0100
> Christopher Baines wrote:
>
>> >
>> > Task 1: Add instrumentation to identify the slow parts of processing
>> > new revisions:
>> >
>> > - Implementing a chart over t
Luciana Lima Brito writes:
> Hi,
>
> On Thu, 29 Apr 2021 21:14:10 +0100
> Christopher Baines wrote:
>
>> Great, can you add more detail to this bit? Given the instrumentation
>> is a really important part, it would be good to have some working
>> ideas fo
lubr...@posteo.net writes:
> Hi,
>
> On Wed, 28 Apr 2021 21:00:44 +0100
> Christopher Baines wrote:
>
>
>> I think time is the main thing, since that alone will help to identify
>> which are the slow parts.
>
>> Indeed, simplicity is a good thing to keep
Ludovic Courtès writes:
> Hi!
>
> Here’s the installation ISO image (with built-in zlib compression):
>
> --8<---cut here---start->8---
> $ ./pre-inst-env guix system image -t iso9660 gnu/system/install.scm
>
Luciana Lima Brito writes:
> On Wed, 28 Apr 2021 19:17:51 +0100
> Christopher Baines wrote:
>
>> So, there's already some code for timing different parts of the data
>> loading process, if you look in the job output and search for ", took
>> &quo
Luciana Lima Brito writes:
> I was thinking about the timeline of tasks.
>
> The main tasks are:
>
> 1. Add instrumentation to identify the slow parts of processing
> new revisions
>
> 2. Improve the performance of these slow parts
>
> I'm writing some ideas I have to divide the tasks in
Luciana Lima Brito writes:
> Hi,
>
> On Tue, 27 Apr 2021 21:29:35 +0100
> Christopher Baines wrote:
>
>
>> Great :) I've tweaked the commit message a little and pushed.
>
> This is really great!!!
>
> I started to look after my final application and I need t
Luciana Lima Brito writes:
> On Tue, 27 Apr 2021 19:42:13 +0100
> Christopher Baines wrote:
>
>> I'd go with this approach, applying the comments I made about the
>> match-lambda bit above in the email I sent a few minutes ago.
>
> I applied all you instructed me.
Luciana Lima Brito writes:
> On Tue, 27 Apr 2021 13:10:01 +
> Luciana Lima Brito wrote:
>
>> > Maybe add another procedure that combines group-to-alist but
>> > generates an alist with vectors as the values?
>> > (group-to-alist/vector maybe).
>
> I did it! :)
> It was so much simpler. I
Canan Talayhan writes:
> I am writing to give you an update on the progress that I have made.
Great :)
> I've created a temporary table named temp_package_metadata[1] and
> insert a revision that already in my local database[2]. Then as you
> said I've run the slow query with EXPLAIN ANALYZE.
Luciana Lima Brito writes:
> On Mon, 26 Apr 2021 22:21:50 +0100
> Christopher Baines wrote:
>
>>
>> Rather than writing:
>>
>> (match-lambda
>> ((alist ...)
>>
>> I'd just use
>>
>> (lambda (alist)
>>
>> as I th
Luciana Lima Brito writes:
> On Mon, 26 Apr 2021 09:15:37 +0100
> Christopher Baines wrote:
>
>> So, one advantage of alists over lists is that the code is probably
>> less brittle when adding elements say, since code parsing the list
>> will probab
Luciana Lima Brito writes:
> Your advices helped me think more clearly.
Great :)
> There was no need to create or modify structures other than what I was
> already changing. I now return an alist instead of a list on the
> derivation-differences-* functions on comparison.scm (for outputs,
>
Canan Talayhan writes:
> Thanks for your quick response. It helps a lot to me. But still, I
> have some confusion about the reproduction steps. As I understand it,
> I can reproduce the slow query just using the pure SQL queries without
> touching the code for now, right?
>
> Please find my
Christopher Baines writes:
> The approach I'd recommend is, make yourself a realistic
> temp_package_metadata table by populating it with all the
> package_metadata entries for a single revision already in your local
> database. Then construct and try the slow query, and see how lon
Vincent Legoll writes:
> Hello,
>
> On Sat, Apr 24, 2021 at 8:28 AM Christopher Baines wrote:
>> With some prompting, there's now a blog post about the Guix Build
>> Coordinator
>
> Nice post that explains a lot, but I'm still not so sure about the
> relati
Hey,
This is probably something I haven't spoken enough about, but my test
site (guix.cbaines.net) for building and providing substitutes has now
got to a point where I've tested most things I set out to test.
In particular, it's building the following things:
- packages for:
- x86_64-linux
Hey,
With some prompting, there's now a blog post about the Guix Build
Coordinator:
https://guix.gnu.org/en/blog/2021/building-derivations-how-complicated-can-it-be/
Since it doesn't have a web interface like the Guix Data Service, and
doesn't directly meet a widespread need, I think it's
Luciana Lima Brito writes:
> Hi,
>
> On Thu, 22 Apr 2021 22:15:34 +0100
> Christopher Baines wrote:
>
> I'm stuck.
>
>> I'd suggest avoiding '() as the value for hash and hash-algorithm when
>> they're NULL in the database. One option here that I've used in so
201 - 300 of 766 matches
Mail list logo
