Hi!
Kyle Meyer writes:
> Hi Maxim,
>
> Maxim Cournoyer writes:
>
>> Another easy option is to retrieve the Message-ID of any message in the
>> series (via the source HTML of the mail archives, or directly from the
>> mail headers if you have the mail locally), and then use B4, Linux
>> style
Hi Maxim,
Maxim Cournoyer writes:
> Another easy option is to retrieve the Message-ID of any message in the
> series (via the source HTML of the mail archives, or directly from the
> mail headers if you have the mail locally), and then use B4, Linux
> style [0]. Example: suppose I wanted to
On 17/01/2024 15:47, Simon Tournier wrote:
(..)
On Tue, 16 Jan 2024 at 15:35, Steve George wrote:
We're planning to put up a blog post about Guix (and Guix-related) talks
at FOSDEM [0]. I've collected all the talks that that are about Guix (or
connected areas). If I've missed any Guix related
Hi,
On Tue, 16 Jan 2024 at 15:35, Steve George wrote:
> We're planning to put up a blog post about Guix (and Guix-related) talks
> at FOSDEM [0]. I've collected all the talks that that are about Guix (or
> connected areas). If I've missed any Guix related talks please tell me
> so I can add
Hi,
On Tue, 16 Jan 2024 at 00:19, Troy Figiel wrote:
> Although not fully PEP 517-compliant according the documentation, the
> pyproject-build-system does seem to fall back to setuptools.build_meta
> if the pyproject.toml is missing. Contrary to what the name implies to
> me, it can therefore
Hi,
On Thu, 11 Jan 2024 at 16:10, Ludovic Courtès wrote:
> Long story short: I’d like us to freeze and merge the branch ASAP,
> notably because the glibc graft on ‘master’ leads to a bad user
> experience. I’m happy with the current state of the branch and wouldn’t
> mind postponing remaining
Hi,
On Tue, 09 Jan 2024 at 21:32, Maxim Cournoyer wrote:
> What do you think? Should we go ahead and effect the following simple
> change for the Berlin build farm?
>
> --8<---cut here---start->8---
> modified hydra/modules/sysadmin/services.scm
> @@
Hi,
CC:
$ ./etc/teams.scm list-members go
Katherine Cox-Buday
Sharlatan Hellseher
On Sun, 14 Jan 2024 at 22:12, Troy Figiel wrote:
> --8<---cut here---start->8---
> (define* (check #:key tests? import-path #:allow-other-keys)
> "Run the
Hi Oleg,
On Thu, 11 Jan 2024 at 19:56, Sharlatan Hellseher wrote:
> I am happy to have been granted commit access
Cool! Welcome.
> If anyone has a good patch review workflow using Emacs, Gnus, and Magit,
> I would appreciate it ;-)
Well, nothing more than what had been already suggested.
Hi Tomas,
Tomas Volf <~@wolfsden.cz> writes:
> On 2024-01-14 22:12:38 +0100, Troy Figiel wrote:
>> Hi everyone,
>>
>> When looking into the Go build system, I noticed the default check phase
>> runs (invoke "go" "test" import-path), which only runs the tests in the
>> root directory of the
Hi,
Troy Figiel writes:
> Hi Guix/Python team,
>
> My fix for python-requests-kerberos was pushed today (thanks Oleg!) and
> I thought it would be an appropriate moment to ask about the
> pyproject-build-system. In short, is the pyproject-build-system a
> preferable default over the
Hi Attila,
Attila Lendvai writes:
>> 1. People find the [data] service provides value (can someone restate what
>> that
>> value is exactly? Is it needed e.g. to power
>
>
> if you allow hijacking the above into the wiki discussion:
>
> this is a good example where a wiki page (central, easily
Hello,
I use the Emacs compilation mode (M-x compile).
For example, the following "M-x compile RET guix build does-not-exist
RET" would result to the following:
--8<---cut here---start->8---
-*- mode: compilation; default-directory: "~/" -*-
Compilation
On Wed, Jan 17 2024, Greg Hogan wrote:
> Is it appropriate to make the recommended changes and submit an
> updated patch?
Yes, absolutely!
Kind regards
Felix
On Wed, Jan 17, 2024 at 12:17:26PM -0500, Greg Hogan wrote:
> What is the preferred process for when a patch review is provided
> (often by a committer) but no response is received from the submitter
> (for many weeks or months)?
>
> Is it appropriate to make the recommended changes and submit an
What is the preferred process for when a patch review is provided
(often by a committer) but no response is received from the submitter
(for many weeks or months)?
Is it appropriate to make the recommended changes and submit an updated patch?
Examples include #62262 and #67294, but there surely
Carlo Zancanaro writes:
> On Mon, Jan 15 2024, Richard Sent wrote:
>> At present this can be worked around by commenting out entries on the
>> list, but this requires
>> a) Already knowing what machine is offline
>> b) Remembering to uncomment it later when the machine goes back online
>> c)
Hi,
Efraim Flashner writes:
> On Fri, Jan 12, 2024 at 05:21:51PM +0100, Clément Lassieur wrote:
>> On Thu, Jan 11 2024, Sharlatan Hellseher wrote:
>>
>> > Hi Guix!
>> >
>> > I am happy to have been granted commit access and I am ready to help
>> > review pending issues and prepare queued
Hi Ludovic,
Ludovic Courtès writes:
> Hello Guix!
>
> Several of us have been fiddling with the ‘core-updates’ branch for a
> while. I think there’s now consensus that the branch is really
> dedicated to core packages and (guix build …) modules, as embodied in
> the new ‘core-packages’ team¹.
On 2024-01-17 16:21:05 +0800, Adam Faiz wrote:
> Hello,
>
> > Hello:
> >
> > How to always keep build tree when run guix build, at the moment, I
> > use --keep-failed, but it will remove build tree when build success, the
> > problem is that build success alway not right build success :-), I
On Mon, Jan 15 2024, Richard Sent wrote:
> At present this can be worked around by commenting out entries on the
> list, but this requires
> a) Already knowing what machine is offline
> b) Remembering to uncomment it later when the machine goes back online
> c) Generally feels "ugly" in a way that
Adam Faiz writes:
> Hello,
>
>> Hello:
>>
>> How to always keep build tree when run guix build, at the moment, I
>> use --keep-failed, but it will remove build tree when build success, the
>> problem is that build success alway not right build success :-), I need
>> go to build tree to check
On Wed, Jan 17, 2024 at 04:21:05PM +0800, Adam Faiz wrote:
> Hello,
>
> > Hello:
> >
> > How to always keep build tree when run guix build, at the moment, I
> > use --keep-failed, but it will remove build tree when build success, the
> > problem is that build success alway not right build
Hello,
> Hello:
>
> How to always keep build tree when run guix build, at the moment, I
> use --keep-failed, but it will remove build tree when build success, the
> problem is that build success alway not right build success :-), I need
> go to build tree to check some thing.
>
> Thanks!
>
24 matches
Mail list logo
