emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#39976: closed (next browser fails to build)


From: GNU bug Tracking System
Subject: bug#39976: closed (next browser fails to build)
Date: Sat, 07 Mar 2020 16:43:03 +0000

Your message dated Sat, 7 Mar 2020 17:39:45 +0100
with message-id <20200307163945.GB1773@doom>
and subject line Re: next browser fails to build
has caused the debbugs.gnu.org bug report #39976,
regarding next browser fails to build
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
39976: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=39976
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: next browser fails to build Date: Sat, 7 Mar 2020 16:28:31 +0100 User-agent: Mutt/1.12.2 (2019-09-21)
Hi,

what is the status of next browser?

When I noticed there is such thing I was happy as it could be
replacement for Conkeror and even with better language to use....

I used to have crashes pretty often and usually blamed WebKit for that...

But for some time I'm not able even to build it.

It seems that I have the same issue as can be seen here:

 https://ci.guix.gnu.org/log/91snb4sd5c6xrp930s3v5a5yrxfr0n3h-next-1.5.0


Thanks in advance,

Tomáš Čech

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: next browser fails to build Date: Sat, 7 Mar 2020 17:39:45 +0100 User-agent: Mutt/1.12.2 (2019-09-21)
Hi!

On Sat, Mar 07, 2020 at 05:13:00PM +0100, Pierre Neidhardt wrote:
Hi!

Glad to see you are interested in Next! :)

Next 1.5.0 should work rather well on Guix.

However the SBCL 2.0.2 update broke it.  But no worries, I've just
pushed a fix so you should able to install Next after a `guix pull'.

I'm hard at work with Next 2.0 and it should fix some long standing
issues that are still in Next 1.5.0.

Thanks for swift response and reaction. I can confirm that new pull
fixes the issue for me.

Stay tuned!

I will, good luck with 2.0!

Best regards,

Tomáš Čech


PS: I used bug-tracker e-mail in initial e-mail but you got the e-mail
   without assigned bug. So your response probably opened new one -
   please, be so kind and close it.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]