Oops, I did it again!
Thousand times sorry, right when I pressed "push" I realize that I forgot
to include the arguments change in the commit message of the 'nyxt'
package update.
This time 2 argument phases have changed. Let me know if you want me to
update staging.
Too much work these days...
Pierre Neidhardt writes:
>> I had not realized sbcl-static-dispatch failed to build even on 'master'
>> initially, did you commit it by mistake? If I'd known I would not have
>> let it hold up the merge.
>
> Weird, it works for me on be0ebf33aa19dcfd36c7a8d22a53344dc3b4a533
It did not work for
Marius Bakke writes:
> I can confirm the above commit works.
Cool, thanks!
> I had not realized sbcl-static-dispatch failed to build even on 'master'
> initially, did you commit it by mistake? If I'd known I would not have
> let it hold up the merge.
Weird, it works for me on be0ebf33aa19dcfd
Pierre Neidhardt writes:
> Marius Bakke writes:
>
>> Speaking of the Common Lisp build system on 'staging', the newly-added
>> 'sbcl-static-dispatch' fails to build when merged or cherry-picked.
>>
>> Can you look into it?
>
> I haven't tested but this could be fixed by the commit I've just push
Looks like static-dispatch works on staging, but there is an issue with
the new build system for the next package I want to add, generic-cl.
I need to ping Guillaume on that and preferably before merging staging.
I'll open an issue just now.
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.
Marius Bakke writes:
> Pierre Neidhardt writes:
>
>> Can't wait for staging to merge, the Common Lisp build-system is vastly
>> improved!
>
> I've just fixed a 'totem' test failure. Unless other regressions show
> up it should be ready for merge within a few days. Testers wanted!
Speaking of
Pierre Neidhardt writes:
> I've just pushed a fix in 98a15c796afcc91894b7400b1d548cd50604db0c, so
> Nyxt should be back to its pristine defintion.
Oh my, thanks for catching that.
I did have the lparallel removal in my notes and distinctly remember
adjusting for it, but obviously messed up at s
Hi Pierre,
On Sun, 08 Nov 2020 at 16:16, Marius Bakke wrote:
>> Out of curiosity: how do commit messages help you here?
>
> It can be difficult to tell from the diff alone which inputs are native,
> regular, or propagated.
I had similar difficulties when looking at #31108. It is easier to find
Pierre Neidhardt writes:
> Hi Marius!
>
> Sorry about this! :(
>
>> If you happen to be around right now, can you confirm that there were no
>> changes to nyxt inputs in 573489fbcd68e3a89cc5c9c66693d3689b1b88bf?
>
> I don't have a Guix checkout at hand now so I can only tell you tomorrow.
> Did y
Hi Marius!
Sorry about this! :(
> If you happen to be around right now, can you confirm that there were no
> changes to nyxt inputs in 573489fbcd68e3a89cc5c9c66693d3689b1b88bf?
I don't have a Guix checkout at hand now so I can only tell you tomorrow.
Did you manage to fix the merge conflict?
Oth
Marius Bakke writes:
> This is a friendly reminder to please list all changes to inputs,
> arguments etc in the commit message. It makes resolving merge conflicts
> *much* easier.
>
> Due to SBCL changes on the 'staging' branch, there have been a few
> changes to the 'nyxt' inputs; and because t
Hello Pierre,
guix-comm...@gnu.org writes:
> commit 21e79225352a5e78aa329b6cd213eb553862c363
> Author: Pierre Neidhardt
> AuthorDate: Tue Oct 20 15:06:59 2020 +0200
>
> gnu: nyxt: Update to 2-pre-release-3.
>
> * gnu/packages/web-browsers.scm (nyxt): Update to 2-pre-release-3.
> ---
12 matches
Mail list logo
