Hello Ludo',
> Hi,
>
> raid5atemyhomework raid5atemyhomew...@protonmail.com skribis:
>
> > Now, let us combine this with the second feature (really a bug): GNU
> > shepherd is a simple, single-threaded Scheme program. That means that
> > if the single thread enters an infinite loop (because of a
Hi Luis,
Thanks for testings and reporting.
On Fri, 19 Mar 2021 at 22:26, Luis Felipe wrote:
> ‐‐‐ Original Message ‐‐‐
> On Thursday, March 18, 2021 2:28 PM, zimoun wrote:
>
> [...]
>
>> We are still missing a good story to monitor what is archived on
>> Software Heritage and
On Sat, Mar 20, 2021 at 11:56:57PM +0100, zimoun wrote:
> > From the wip-next-release branch, we should cherry-pick the tzdata
> > updates and Qt 4 removal.
> >
> > I'll rewrite the branch with those commits today, and then see about
> > getting it built on CI.
>
> Do you mean cherry-pick and
Hi Andreas,
On Fri, 19 Mar 2021 at 19:31, Andreas Enge wrote:
> Am Thu, Mar 18, 2021 at 03:28:38PM +0100 schrieb zimoun:
>> guix weather --display-missing
>
> I am giving it a try, but after about one hour at 100% CPU on one core it
> is still only half way through. Is this normal? I think I
Hi Leo,
On Sat, 20 Mar 2021 at 16:01, Leo Famulari wrote:
> I suggest we use debbugs to keep track of tasks for the release.
>
> We can create a new bug called "1.2.1 release checklist".
>
> This bug can be made to depend on other bugs using the "block" feature
> of debbugs:
>
>
Hi Leo,
On Sat, 20 Mar 2021 at 14:09, Leo Famulari wrote:
> On Fri, Mar 19, 2021 at 09:50:55AM +0100, zimoun wrote:
>> The release work happens on master. The branch wip-next-release
>> contains fixes, but AFAIK, it is not built by the CI, and these fixes
>> are ’core-updates’-like changes; I
Hi Leo,
> On Fri, Mar 19, 2021 at 08:14:03PM -0400, Mark H Weaver wrote:
>> The following dependency chain seems to be responsible for most of the
>> imagemagick-dependent packages:
>>
>> gtk+@3 -> at-spi2-atk -> at-spi2-core -> gtk-doc -> dblatex -> imagemagick
Leo Famulari writes:
> To
I suggest we use debbugs to keep track of tasks for the release.
We can create a new bug called "1.2.1 release checklist".
This bug can be made to depend on other bugs using the "block" feature
of debbugs:
https://debbugs.gnu.org/server-control.html
Concretely, this means we send email to
On 2021-03-20 13:13, pkill9 wrote:
I would like to be able to pipe files into guix commands.
Specifically the `guix system build` command, so I can build a system
configuration on a remote Guix system over SSH, i.e. `cat config.scm |
ssh guix system build -`, or perhaps using the
On Fri, Mar 19, 2021 at 08:14:03PM -0400, Mark H Weaver wrote:
> Leo Famulari writes:
>
> > On Thu, Mar 18, 2021 at 09:40:04AM -0400, Mark H Weaver wrote:
> >> I knew this couldn't be right, but I thought I remembered it having
> >> fewer dependencies. Oh well. Sorry for the noise.
> >
> >
On Fri, Mar 19, 2021 at 09:50:55AM +0100, zimoun wrote:
> The release work happens on master. The branch wip-next-release
> contains fixes, but AFAIK, it is not built by the CI, and these fixes
> are ’core-updates’-like changes; I do not know if it is doable to merge
> on time.
I agree. The
Hi,
ison skribis:
> Under "6.7 Declaring Channel Dependencies" the examples show names being
> quoted, such as (name 'some-collection) however this causes guix pull to
> fail. I don't remember the exact error but it was failing the "match"
> statement under "resolve-dependencies" in
Hi,
raid5atemyhomework skribis:
> Now, let us combine this with the second feature (really a bug): GNU
> shepherd is a simple, single-threaded Scheme program. That means that
> if the single thread enters an infinite loop (because of a Shepherd
> service description that entered an infinite
Hi!
Konrad Hinsen skribis:
>>> does “guix build -n” fit your use-case?
>>
>> Checking... yes! I hadn't even considered using "build" when building is
>> exactly what I do not want to happen. But yes, it works just fine.
>
> Not quite:
>
> $ guix build -n zziplib
> substitute:
>
I would like to be able to pipe files into guix commands.
Specifically the `guix system build` command, so I can build a system
configuration on a remote Guix system over SSH, i.e. `cat config.scm |
ssh guix system build -`, or perhaps using the
`--expression` flag which would make more sense,
Hi Léo,
Léo Le Bouter skribis:
> On Wed, 2021-03-17 at 17:56 +0100, zimoun wrote:
>> If the removal for security reasons had been discussed on IRC, it
>> could
>> be nice to point the discussion here. Otherwise, open a discussion
>> on
>> the topic on guix-devel or bug-guix. The full removal
Vagrant Cascadian skribis:
> On 2021-03-17, Léo Le Bouter wrote:
>> Just as a reminder siding with vagrantc here:
>>
>> We must ensure the Debian 'guix' package can still work and upgrade
>> from it's installed version, so ensure that removing gzip doesnt break
>> initial 'guix pull' with it.
>
Hi,
Léo Le Bouter skribis:
> It seems GNU Guix takes a generic approach to updates while Debian or
> Fedora seems to look at specialized rules for each package, I was
> thinking we could import those already existing rules (in Fedora's or
> Debian's) into GNU Guix, I find it a superior approach
Hi,
Mark H Weaver skribis:
> Ultimately, I gave up. In my opinion, Guix has never achieved usability
> as a desktop system on non-Intel systems. Therefore, the Guix community
> is unable to attract many developers who want a distro that supports
> non-Intel systems well. Our community has
Good rmoning Mark,
> Hi,
>
> raid5atemyhomework raid5atemyhomew...@protonmail.com writes:
>
> > GNU Shepherd is the `init` system used by GNU Guix. It features:
> >
> > - A rich full Scheme language to describe actions.
> > - A simple core that is easy to maintain.
> >
> > However, in this
20 matches
Mail list logo
