Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Pike 8.0 rel 2 this weekend
by Peter Bortas ＠ Pike developers forum 28 Feb '16

28 Feb '16

As earlier announced I will build an RC for the second release of Pike 8.0 this weekend, and if all goes well release it on Tuesday. If you are sitting on some low risk fix patch now is the time to check it in. -- Peter Bortas

2 1

IA64
by Peter Bortas ＠ Pike developers forum 15 Feb '16

15 Feb '16

Removing silencing of warnings is fine, but I don't want IA64 specific runtime-support to be removed if there is any.

1 0

Change of release method
by Peter Bortas 09 Feb '16

09 Feb '16

Hi all, I'm going to change the release method a bit. First change being that there are releases again. Just posted 8.0 release to the user list. The second change is that I will make a stable release _attempt_ per month on the first Tuesday of the month. So the next potential packaging of a release will be on March 1st. Regards, -- Peter Bortas

1 0

Pike 8.0.162 release candidate
by Peter Bortas 08 Feb '16

08 Feb '16

This will be the full release unless it kills kittens. You have until Tuesday to pull the breaks. Pike 8.0.162 release candidate for your testing pleasures: https://pike.lysator.liu.se/pub/pike/beta/8.0.162/Pike-v8.0.162.tar.gz Windows build: https://pike.lysator.liu.se/pub/pike/beta/8.0.162/Pike-v8.0.162-win32-oldli bs.msi I did some work on building newer support libs for Windows, but that ended up being 6 hours of mostly frustration. So Nettle, GMP, GTK and Freetype are all still versions from 2008 or so. That build will probably not be promoted to a real release. Use it at your own risk. I'll have another go at that in the coming weeks. Changes in this mail are not added to CHANGES.TXT. Some of them probably should be. Changes since 8.0.146 (New Year release) -------------------------------------------------------------- * Fixed internal compiler error with implicit lambdas. * Allow disabling of wrapping of describe_backtrace output. The wrapping can add lots of spaces to the end of lines to pad them, resulting in enormous backtrace files in some circumstances. * Make the Pike SSL code work with APNS push server which uses client certificates. * Added the Markdown module and the standalone pike_to_html.pike from 8.1. * Web.Api/OAuth: Added the posibility to define the HTTP request timeout in async queries. * Protocols.HTTP: do_async_method() no longer resets the timeouts. Setting the query timeouts to something else than the default (120 seconds) should now work again. * Documentation [HTTPAccept]: Fix all references to HTTPLoop. HTTPLoop installs itself as HTTPAccept, so fix the documentation to reflect this. * Build: make precompile dependencies optional Fix builing of external modules * Updated to tzdata2016a. Regards, -- Peter Bortas

7 7

Pike 8.0.164 release candidate
by Peter Bortas 08 Feb '16

08 Feb '16

New build with Parser.Markdown removed. Still plan to release tomorrow Pike 8.0.164 release candidate for your testing: https://pike.lysator.liu.se/pub/pike/beta/8.0.164/Pike-v8.0.164.tar.gz Windows build: https://pike.lysator.liu.se/pub/pike/beta/8.0.164/Pike-v8.0.164-win32-oldli… Changes since 8.0.162 (yesterday) -------------------------------------------------------------- * Reverted inclusion of Parser.Markdown * Ratelimiting (of sorts) of error messages from Filesystem.Monitor Regards, -- Peter Bortas, NSC

1 0

Pike 8 release candidate today
by Peter Bortas ＠ Pike developers forum 07 Feb '16

07 Feb '16

A release candidate for 8.0 will be tagged within 30min to test-feed to primarily the Windows build machinery. If there are any other fixes you want in let me know before 18:00 and I will do another pull before doing final builds. -- Peter Bortas

1 1

Re: Protocols.IRC unmaintained - want me to give it some TLC?
by Chris Angelico 07 Feb '16

07 Feb '16

On Sun, Feb 7, 2016 at 11:20 AM, Peter Bortas @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Please do. > > I have (after a bit of head-scratching) figured out how the key > management works. I think. Try it. Thank you, seems to be working! Much appreciated. Ran into a problem with the githelper hook using the 7.8/8.0 way of calling up Charset, so I stuck in a #if to support the 8.0/8.1 way as well. ChrisA

1 0

Protocols.IRC unmaintained - want me to give it some TLC?
by Chris Angelico 07 Feb '16

07 Feb '16

The Protocols.IRC module basically hasn't been touched in years. I'm looking at making some use of it (building a Twitch.tv chatbot); want me to do up the module a bit while I'm at it (add docs and stuff, mainly)? I'm waiting on Grubba (or someone) to register my public key with the server, but other than that, happy to do a bit of documenting. ChrisA

2 1

Pike 8 release next weekend
by Peter Bortas 06 Feb '16

06 Feb '16

I'm aiming for a release of Pike 8 next weekend on Sunday the 7th. This is my current list of "blockers", please speak up if you have any others or if you have input on any of the existing: ** random() might now be really random (incompatible change) Will not be backed out. We should provide a pseudo-random() that is seedable, and preferably does not have a name that includes "random". I don't want to hold the release for that unless someone has a real application that needs it or have a finished implementation with a well thought out API by next Saturday. ** OpenBSD compile failures (regression) I will not hold the release for this unless someone with a OpenBSD machine tells me that they are actively working on it. ** Windows support libraries are old (not a regression, just regrettable) Will make an effort to build new versions of GMP och Nettle, and see if we can bundle a newer GTK release. Since this is not a regression I will not hold back a release for it though. Cheers, -- Peter Bortas, NSC

2 3

Change of public key
by Chris Angelico 28 Jan '16

28 Jan '16

I've just suffered a major hard drive meltdown, which wiped out one of my private keys. This is not a compromise, so there's no panic; but it means I've lost access to anything that it granted. Attached is my new public key, and a GPG signature so you know it's mine. Sorry for the hassle... welcome to security, where stuff sometimes goes wrong :) ChrisA

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel