On 24-06-24 17:35:07, Jeremie Courreges-Anglas wrote:
> On Sun, Jun 23, 2024 at 01:56:44AM +1000, Joel Sing wrote:
> > The openbsd/mips64 port is effectively unmaintainable. I've been
> > trying to upstream the direct syscall to libc conversion for two
> > years now:
>
The openbsd/mips64 port is effectively unmaintainable. I've been
trying to upstream the direct syscall to libc conversion for two
years now:
https://github.com/golang/go/issues/61546
Currently, I'm carrying a bunch of extra diffs in ports, I have
limited working hardware to build/test on and wh
On 24-06-07 15:34:38, Kirill A. Korinsky wrote:
> On Fri, 07 Jun 2024 12:11:44 +0100,
> Stuart Henderson wrote:
> >
> > On 2024/06/07 01:04, Kirill A. Korinsky wrote:
> > > I also included trivial patches to add missed syscall.EBADMSG on 386,
> > > amd64
> > > and arm which allows to remove doze
Hi Kirill,
On 24-06-07 01:04:29, Kirill A. Korinsky wrote:
> Here an update for lang/go to 1.22.4, changelog:
>
> go1.22.4 (released 2024-06-04) includes security fixes to the archive/zip
> and net/netip packages, as well as bug fixes to the compiler, the go
> command, the linker, the runti
On 23-10-13 20:05:35, Daniel Jakots wrote:
> Hey,
>
> > go1.21.2 (released 2023-10-05) includes one security fixes to the
> > cmd/go package, as well as bug fixes to the compiler, the go command,
> > the linker, the runtime, and the runtime/metrics package. See the Go
> > 1.21.2 milestone on our i
On 23-03-21 11:49:19, A Tammy wrote:
> On 3/21/23 11:28, Stuart Henderson wrote:
> > On 2023/03/21 15:53, David Vasek wrote:
> >> On 2023-03-21 15:32, A Tammy wrote:
> >>> On 3/21/23 08:26, David Vasek wrote:
> Hello,
>
> more apps start using QUIC with GnuTLS. Port net/ngtcp2 can su
On 23-02-02 10:08:54, Omar Polo wrote:
> On 2023/02/02 20:00:44 +1100, Joel Sing wrote:
> > On 23-02-02 09:35:32, Omar Polo wrote:
> > > These are a few ports that have no reverse deps (outside themselves)
> > > and that don't provide any binary, only the go co
On 23-02-02 09:35:32, Omar Polo wrote:
> These are a few ports that have no reverse deps (outside themselves)
> and that don't provide any binary, only the go code, and thus quite
> useless. nowadays a go port would just use the modules if depends on
> these.
>
> - devel/go-sys
> - security/go-
On 22-12-19 00:49:53, Joel Sing wrote:
> On 22-12-15 13:15:58, Stuart Henderson wrote:
> > golang.org/x/sys/unix/zerrors_openbsd_* and friends are seriously out
> > of date on some archs; zerrors for 386 must have been generated on
> > openbsd 5.7 or earlier; arm and amd64
On 22-12-15 13:15:58, Stuart Henderson wrote:
> golang.org/x/sys/unix/zerrors_openbsd_* and friends are seriously out
> of date on some archs; zerrors for 386 must have been generated on
> openbsd 5.7 or earlier; arm and amd64 somewhere between 5.8 and 6.0.
> (I bumped into this trying to build som
On 22-06-12 11:07:49, Daniel Jakots wrote:
> Hi,
>
> Now that visa's patch [1] is in, I'm sending this update as make test
> passes on amd64.
>
> > go1.18.3 (released 2022-06-01) includes security fixes to the
> > crypto/rand, crypto/tls, os/exec, and path/filepath packages, as well
> > as bug fi
On 22-05-16 07:21:12, Daniel Jakots wrote:
> Here's a patch for go-1.18.2
>
> > go1.18.2 (released 2022-05-10) includes security fixes to the syscall
> > package, as well as bug fixes to the compiler, runtime, the go
> > command, and the crypto/x509, go/types, net/http/httptest, reflect,
> > and s
On 22-04-25 20:33:44, Daniel Jakots wrote:
> Hi,
>
> go1.18.1 was tagged shortly after 1.18.
>
> > go1.18.1 (released 2022-04-12) includes security fixes to the
> > crypto/elliptic, crypto/x509, and encoding/pem packages, as well as
> > bug fixes to the compiler, linker, runtime, the go command,
On 22-03-24 16:43:28, Christian Weisgerber wrote:
> It's time to start slowing down for the upcoming 7.1 release.
>
> There are no restrictions on the types of ports commits yet, but I
> would like to ask everybody to keep the approaching release in mind
> and to slowly wind down large ports work.
On 21-08-25 23:13:37, Stuart Henderson wrote:
> On 2021/08/24 16:13, Aaron Bieber wrote:
> > On Wed, 25 Aug 2021 at 04:10:43 +1000, Joel Sing wrote:
> > > The below diff updates lang/go to Go 1.17.
> > >
> > > Tested on amd64 and arm64, still ne
On 21-06-05 09:01:15, Daniel Jakots wrote:
> Hi,
>
> > go1.16.5 (released 2021-06-03) includes security fixes to the
> > archive/zip, math/big, net, and net/http/httputil packages, as well
> > as bug fixes to the linker, the go command, and the net/http
> > packagckage.
>
> https://golang.org/doc
On 21-02-20 10:39:40, Stuart Henderson wrote:
> On 2021/02/20 17:53, Joel Sing wrote:
> > > -MAKE_ENV += GO386=387
> >
> > We'll presumably want to keep this with GO386=softfloat - otherwise the
> > go binary package will only be useable on i386 CP
On 21-02-19 17:22:09, Aaron Bieber wrote:
> Here is a fairly well tested update to Go. This version now uses libc[1]
> thanks
> to jsing@'s hard work!
Just to clarify, Go 1.16 uses libc-based syscalls for amd64 and
arm64. The remaining platforms (openbsd/386, openbsd/arm, openbsd/mips64)
are stil
On 20-08-20 15:36:23, Aaron Bieber wrote:
> Hi!
>
> Here is an update to bring us to 1.15.
>
> I have run this through a "mini bulk" - there was one failure, but the port
> that failed (net/minio/server) builds fine by hand. The log is here:
> https://deftly.net/server.log
>
> I have tested:
>
On 19-09-26 17:36:25, Theo Buehler wrote:
> On Fri, Sep 27, 2019 at 01:32:38AM +1000, Joel Sing wrote:
> > On 19-09-26 16:14:44, Theo Buehler wrote:
> > > On Thu, Sep 26, 2019 at 11:09:16PM +1000, Joel Sing wrote:
> > > > On 19-09-26 13:06:51, Stuart Henderson wrote:
On 19-09-26 16:14:44, Theo Buehler wrote:
> On Thu, Sep 26, 2019 at 11:09:16PM +1000, Joel Sing wrote:
> > On 19-09-26 13:06:51, Stuart Henderson wrote:
> > > On 2019/09/26 09:44, Theo Buehler wrote:
> > > > I noticed two problems with go's 'make test'
On 19-09-26 13:06:51, Stuart Henderson wrote:
> On 2019/09/26 09:44, Theo Buehler wrote:
> > I noticed two problems with go's 'make test' when PORTS_PRIVSEP=Yes:
> > both having to do with _pbuild's home being /nonexistent:
> >
> > failed to initialize build cache at /nonexistent/.cache/go-build:
The following enables Go on aarch64/arm64.
ok?
Index: infrastructure/mk/arch-defines.mk
===
RCS file: /cvs/ports/infrastructure/mk/arch-defines.mk,v
retrieving revision 1.67
diff -u -p -r1.67 arch-defines.mk
--- infrastructure/mk/arc
On 19-09-13 14:53:30, Stuart Henderson wrote:
> On 2019/09/13 23:32, Joel Sing wrote:
> > On 19-09-13 12:38:19, Stuart Henderson wrote:
> > > On 2019/09/10 04:20, Joel Sing wrote:
> > > > The following updates lang/go to Go 1.13 and also updates the main
> > >
On 19-09-13 12:38:19, Stuart Henderson wrote:
> On 2019/09/10 04:20, Joel Sing wrote:
> > The following updates lang/go to Go 1.13 and also updates the main
> > golang.org/x packages to around the Go 1.13 release. This does
> > not update devel/go-tools, as it introduces
On 19-09-13 12:38:19, Stuart Henderson wrote:
> On 2019/09/10 04:20, Joel Sing wrote:
> > The following updates lang/go to Go 1.13 and also updates the main
> > golang.org/x packages to around the Go 1.13 release. This does
> > not update devel/go-tools, as it introduces
On 19-09-11 15:37:39, Stuart Henderson wrote:
> On 2019/09/10 19:37, Aaron Bieber wrote:
> > On Tue, 10 Sep 2019 at 04:20:55 +1000, Joel Sing wrote:
> > > The following updates lang/go to Go 1.13 and also updates the main
> > > golang.org/x packages to around the
On 19-03-08 14:03:29, Stuart Henderson wrote:
> - sysutils/beats/packetbeat is also broken, not sure how to fix that,
> maybe some vendored thing is in need of an update
>
> cd
> /usr/obj/ports/packetbeat-6.4.3/go/src/github.com/elastic/beats/vendor/github.com/tsg/gopacket/pcap
> CGO_LDFLAGS='"-g
On 19-02-08 21:16:02, Stuart Henderson wrote:
> On 2019/02/08 19:12, Marc Espie wrote:
> > On Fri, Feb 08, 2019 at 12:10:02AM -0500, Ted Unangst wrote:
> > > Go tries to use NCPU cpus. Unfortunately, half of them are turned off
> > > because
> > > hw.smt=0 by default, and then go spends a lot of t
On Monday 26 November 2018 18:21:56 Daniel Jakots wrote:
> Hi,
>
> Here's the diff to update haproxy to the 1.8 branch.
> Most of the libressl stuff has been done by jsing (thanks!) but he did
> the update to 1.8.13 and 13->14 needed some more fiddling. I did them
> on my own so I guess a review w
On Monday 22 October 2018 19:30:02 Alexander Bluhm wrote:
> On Mon, Oct 22, 2018 at 11:10:49AM -0600, Theo de Raadt wrote:
> > I understand the difficulty pointed out by the first questions. What
> > bothers me is the last question. It indicates a desire to support many
> > generations of softwar
On Monday 22 October 2018 20:40:48 Alexander Bluhm wrote:
> On Tue, Oct 23, 2018 at 04:36:24AM +1100, Joel Sing wrote:
> > > #if (OPENSSL_VERSION_NUMBER >= 0x1010L &&
> > > !defined(LIBRESSL_VERSION_NUMBER)) || (LIBRESSL_VERSION_NUMBER >=
> > > 0
On Monday 22 October 2018 19:05:44 Alexander Bluhm wrote:
> On Tue, Oct 23, 2018 at 03:21:23AM +1100, Joel Sing wrote:
> > P.S. There is more functionality that could be enabled for LibreSSL, which
> > is currently being explicitly disabled...
>
> When a new Net::SSLeay i
Get the MAC secret size from the cipher, rather than reaching into libssl
internals. This effectively takes the OpenSSL 1.1 code path instead of the
OpenSSL 1.0 code path, and will allow for further libssl clean up. While
here use some additional OpenSSL 1.1 code paths and const related
changes.
o
Get the MAC secret size from the cipher, rather than reaching into libssl
internals. This effectively takes the OpenSSL 1.1 code path instead of the
OpenSSL 1.0 code path, and will allow for further libssl clean up. While
here use some additional OpenSSL 1.1 code paths and const related
changes.
o
Get the MAC secret size from the cipher, rather than reaching into libssl
internals. This effectively takes the OpenSSL 1.1 code path instead of the
OpenSSL 1.0 code path, and will allow for further libssl clean up.
ok?
P.S. There is more functionality that could be enabled for LibreSSL, which
is
x11/freerdp currently reaches deep into libssl internals, in order to send
TLS alerts. AFAIK OpenSSL 1.1 does not provide any way for TLS alerts to be
triggered outside the library and freerdp's approach is to simply disable
this code. Do the same thing for current LibreSSL, so that we can make
the
On Sunday 26 August 2018 12:52:52 Theo Buehler wrote:
> A simple one:
This doesn't look right - the entire OPENSSL_VERSION_NUMBER < 1.1.0 path (on
line 40 of include/libssl_compat.h) should no longer be taken (or
substantially reduced).
> Index: patches/patch-include_libssl_compat_h
>
On Saturday 10 March 2018 13:19:06 Stuart Henderson wrote:
> On 2018/03/09 20:08, Jasper Lievisse Adriaanse wrote:
> > On Sat, Mar 10, 2018 at 03:45:36AM +1100, Joel Sing wrote:
> > > - The -x flag was previously on by default, which makes builds
> > > incredibly
> &
The following updates lang/go to 1.10.
This also brings the golang.org/x packages up to around the time of the
Go 1.10 release:
devel/go-sys
devel/go-tools
net/go-net
security/go-crypto
textproc/go-text
Last but not least, there are some changes to go.port.mk:
- Go 1.10 has a test cac
On Tuesday 10 October 2017 09:53:43 Stuart Henderson wrote:
> On 2017/10/09 03:34, Joel Sing wrote:
> > Upstream is providing a tarball of the release-branch.go1.4 git branch,
> > which contains minor fixes to keep Go 1.4 building on current platforms.
> > Most of the patc
Upstream is providing a tarball of the release-branch.go1.4 git branch,
which contains minor fixes to keep Go 1.4 building on current platforms.
Most of the patches that we currently have for lang/go-bootstrap have
been committed upstream - one of these is already in the go1.4
release tarball that
This brings security/go-crypto, net/go-net, textproc/go-text and
devel/go-tools up to versions that match the time of the Go 1.9
release. This depends on the new devel/go-sys package.
It is worth noting that some of the SSH related regress tests fail,
however these also fail on the current version
Attached is a new port - devel/go-sys - which provides the golang.org/x/sys
package. This is needed by the next security/go-crypto update.
ok?
P.S. This currently fails to pass regress on i386, due to a mmap test failure
(this is a kernel/uvm issue, not an issue with the package) - this should
Update lang/go to Go 1.9.
This is mostly a bunch of minuses, with a PLIST update.
The various Go packages (go-crypto, go-net, go-text, etc) also need updates,
however the existing versions appear to build correctly with Go 1.9 so we
should be able to land this separately. The package updates are
The following updates lang/go to 1.7.4.
This addresses a security issue with net/http package's
Request.ParseMultipartForm method.
https://golang.org/doc/devel/release.html#go1.7.minor
Passes regress on amd64 and i386.
ok?
Index: Makefile
===
On Saturday 24 September 2016 14:15:35 Steve Mynott wrote:
> Update go from 1.7.0 to 1.7.1
>
> go1.7.1 (released 2016/09/07) includes fixes to the compiler, runtime,
> documentation, and the compress/flate, hash/crc32, io, net, net/http,
> path/filepath, reflect, and syscall packages.
>
> https:/
Update lang/go to 1.7.1.
Passes regress on i386 and amd64.
ok?
Index: Makefile
===
RCS file: /cvs/ports/lang/go/Makefile,v
retrieving revision 1.38
diff -u -p -r1.38 Makefile
--- Makefile21 Aug 2016 14:08:25 - 1.38
+++
On Friday 19 August 2016 01:19:22 Dmitrij D. Czarkoff wrote:
> Hi!
>
> Now with go 1.7 in ports it's time to update go libraries. The diff below
> changes lang/go port and module so that go libraries have runtime dependency
> on lang/go, so that they get rebuilt once lang/go is updated. Ports
>
The following updates lang/go to version 1.7.
Passes regress on i386 and amd64.
ok?
Index: Makefile
===
RCS file: /cvs/ports/lang/go/Makefile,v
retrieving revision 1.36
diff -u -p -u -p -r1.36 Makefile
--- Makefile20 Jul 2016 15
On 6 Jun 2016 7:16 PM, Ray Lai wrote:
>
> On Mon, 06 Jun 2016 10:43:28 -0400
> "Ted Unangst" wrote:
> > I think the first of each of these should be thrkill instead.
>
> Yup. But I don't know asm asm so I left it as kill(2) for now, which is
> arguably better than leaving it as a non-existent sys
On Thursday 02 June 2016 21:02:58 Ted Unangst wrote:
> Trying to build anything with go 1.6 results in an error.
>
> $ go build hello.go
> package main
> imports runtime: C source files not allowed when not using cgo or
> SWIG: atomic_amd64x.c defs.c float.c heapdump.c lfstack.c mall
On Sunday 15 May 2016 08:45:09 Aaron Bieber wrote:
> Hola,
>
> It seems there is a strange issue with go apps that use the go-sqlite3
> driver. When they try to open the database, they error out with "unable
> to open database file".
>
> I can reliably hit the error by running "go test" in a clon
Thanks, I'll have this fixed shortly.
On Friday 13 May 2016 11:56:32 Stuart Henderson wrote:
> Bootstrap is now ok, but lang/go fails. Full log below, but the
> core of it is here:
>
> # Building packages and commands for openbsd/386.
> runtime/internal/sys
> ./make.bash: line 166: 13151 Ille
On Tuesday 05 April 2016 23:43:30 Dmitrij D. Czarkoff wrote:
> Juan Francisco Cantero Hurtado said:
> > The files will not show up again in the future in the PLIST.
>
> Indeed. Also
>
> > - I would prefer to keep the old behavior in do-install. INSTALL_* will
> >
> > use the correct permissio
Update lang/go to 1.5.3.
Passes regress on amd64, will test i386 shortly.
This release addresses CVE-2015-8618.
ok?
Index: Makefile
===
RCS file: /cvs/ports/lang/go/Makefile,v
retrieving revision 1.27
diff -u -p -r1.27 Makefile
---
On Wednesday 23 December 2015 03:02:25 Joel Sing wrote:
> On Wednesday 09 December 2015 00:40:28 Joel Sing wrote:
> > I'll rework go.port.mk and the relevant packages using /usr/local/go-pkg.
>
> This reworks go.port.mk to install packages in /usr/local/go-pkg and builds
>
On Thursday 10 December 2015 17:50:20 Michael McConville wrote:
> Joel Sing wrote:
> > Thanks for clarlifying - we could still implement 'go get -d' as a way
> > of getting sources, but it would be more work than it is likely worth
> > (and there are also some issue
On Wednesday 09 December 2015 00:40:28 Joel Sing wrote:
> I'll rework go.port.mk and the relevant packages using /usr/local/go-pkg.
This reworks go.port.mk to install packages in /usr/local/go-pkg and builds
without -a, -work and without running things through sed and piping to shell.
On Monday 07 December 2015 23:31:34 Stuart Henderson wrote:
> On 2015/12/08 10:05, Joel Sing wrote:
> > On Monday 07 December 2015 14:18:52 Kent R. Spillner wrote:
> > > On Tue, Dec 08, 2015 at 02:29:03AM +1100, Joel Sing wrote:
> > > > This brings me to the
On Monday 07 December 2015 14:18:52 Kent R. Spillner wrote:
> On Tue, Dec 08, 2015 at 02:29:03AM +1100, Joel Sing wrote:
> > This brings me to the next issue/topic - installing additional packages
> > under /usr/local/go is probably a bad idea.
>
> My recollection is that
On Sunday 06 December 2015 16:44:33 Stuart Henderson wrote:
> Slight problem with the go update, it breaks build of some ports using
> the go module:
>
> textproc/go-xlsx
> net/go-websocket
> devel/go-check-v1
> devel/go-tools
I obviously did not get to look carefully at r1.2 of go.port.mk - ther
On Friday 04 December 2015 03:12:16 Joel Sing wrote:
> The following updates lang/go to 1.5.1 - this depends on the
> lang/go-bootstrap package just sent to ports@.
>
> One difference is that this now installs the go binary in
> /usr/local/go/bin/go, which allows the package
The following updates lang/go to 1.5.1 - this depends on the lang/go-bootstrap
package just sent to ports@.
One difference is that this now installs the go binary in /usr/local/go/bin/go,
which allows the package to be used as a bootstrap to build Go from source.
Symbolic links are installed for /
>From Go 1.5 onwards, an existing go compiler is needed to bootstrap the build
(the runtime is now written in Go, rather than C) - the current "promise" is
that the bootstrap will only use functionality from the Go 1.4 API.
So that we can continue to build natively, the attached is a lang/go-boo
On Monday 19 January 2015, Joel Sing wrote:
> The following updates lang/go to 1.4.1 - this is basically a handful of bug
> fixes and also allows us to remove the last of the patches that existed in
> ports:
>
> https://github.com/golang/go/issues?q=milestone%3AGo1.4.1
>
>
The following updates lang/go to 1.4.1 - this is basically a handful of bug
fixes and also allows us to remove the last of the patches that existed in
ports:
https://github.com/golang/go/issues?q=milestone%3AGo1.4.1
Passes regress on 386/amd64.
ok?
Index: Makefile
On Thu, 6 Nov 2014, Ted Unangst wrote:
> I see errors trying to download some https URLs using python, but the
> base ftp client isn't affected. 5.6 release and current. One example is
> https://www.duosecurity.com/feed.
>
> athens:/tmp> python2.7
> Python 2.7.8 (default, Oct 6 2014, 13:51:42)
> [
On Thu, 6 Nov 2014, Ted Unangst wrote:
> I see errors trying to download some https URLs using python, but the
> base ftp client isn't affected. 5.6 release and current. One example is
> https://www.duosecurity.com/feed.
>
> athens:/tmp> python2.7
> Python 2.7.8 (default, Oct 6 2014, 13:51:42)
> [
On Sun, 26 Oct 2014, Stuart Henderson wrote:
> On 2014/10/26 04:00, Joel Sing wrote:
> > Update lang/go to 1.3.3.
> >
> > Passes regress on amd64 and i386.
> >
> > ok?
>
> It didn't package for me,
>
> Error:
> /usr/obj/ports/go-1.3.3/fake-amd
Update lang/go to 1.3.3.
Passes regress on amd64 and i386.
ok?
Index: Makefile
===
RCS file: /cvs/ports/lang/go/Makefile,v
retrieving revision 1.20
diff -u -p -r1.20 Makefile
--- Makefile25 Jul 2014 14:39:41 - 1.20
+++
On Wed, 1 Oct 2014, Reyk Floeter wrote:
> Am 30.09.2014 um 15:39 schrieb Christian Weisgerber :
> > Joel Sing:
> >>>> ===> www/apache-httpd-openbsd
> >>>> ===> www/apache-httpd
> >>
> >> Is this the only ports fallout?
> >
On Tue, 30 Sep 2014, Stuart Henderson wrote:
> On 2014/09/30 11:20, Stuart Henderson wrote:
> > On 2014/09/29 14:06, Christian Weisgerber wrote:
> > > Apache doesn't like the addition of SSL_CTX_use_certificate_chain().
> > >
> > > ===> www/apache-httpd-openbsd
> > >
> > > ../../modules/ssl/ssl_uti
On Tue, 30 Sep 2014, Stuart Henderson wrote:
> On 2014/09/29 14:06, Christian Weisgerber wrote:
> > Apache doesn't like the addition of SSL_CTX_use_certificate_chain().
> >
> > ===> www/apache-httpd-openbsd
> >
> > ../../modules/ssl/ssl_util_ssl.h:119: error: conflicting types for
> > 'SSL_CTX_use_
The following update lang/go to 1.2.1.
Additionally, the OpenBSD related API changes are added to the exceptions list
(which has already been done upstream for 1.3) so that make regress passes.
Passes regress on OpenBSD/amd64 and OpenBSD/i386.
ok?
Index: Makefile
===
On Tue, 19 Nov 2013, Stuart Henderson wrote:
> On 2013/11/19 02:38, Brad Smith wrote:
> > - Original message -
> >
> > > On Sat, 2 Nov 2013, Joel Sing wrote:
> > > > The following diff updates go/lang go 1.2rc3 - this is going to be
> > > >
}
PKGNAME = go-${VERSION}
@@ -17,7 +17,7 @@ MAINTAINER = Joel Sing http://go.googlecode.com/files/
Index: distinfo
===
RCS file: /cvs/ports/lang/go/distinfo,v
retrieving revision 1.5
diff -u -p -r1.5 distinfo
The 1.0.3 release of lang/go makes use of the old __tfork syscall, which was
recently removed by guenther@. The attached diff makes lang/go use the newer
version of the __tfork syscall. Additionally, switch to __set_tcb instead of
using sysarch, which allows for the removal of systrace.filter (w
Thanks. I'd prefer to run with the following, which:
- Updates to go 1.0.3.
- Fixes a bug in the regress tests that may result in the tests being built/run
with the installed binaries rather than the new binaries.
- Fixes a bug related to 'go install' trying to rebuild non-writeable $GOROOT
p
The rfork syscall is now obsolete.
ok?
Index: systrace.filter
===
RCS file: /cvs/ports/infrastructure/db/systrace.filter,v
retrieving revision 1.34
diff -u -p -u -p -r1.34 systrace.filter
--- systrace.filter 30 Jan 2012 16:02:24
On Wednesday 04 July 2012, Juan Francisco Cantero Hurtado wrote:
> On Wed, Jul 04, 2012 at 10:37:50AM +1000, Joel Sing wrote:
> > On Wednesday 04 July 2012, Juan Francisco Cantero Hurtado wrote:
> > > On Wed, Jul 04, 2012 at 01:17:00AM +1000, Joel Sing wrote:
> > > &
On Wednesday 04 July 2012, Stuart Henderson wrote:
> On 2012/07/04 10:37, Joel Sing wrote:
> > On Wednesday 04 July 2012, Juan Francisco Cantero Hurtado wrote:
> > > On Wed, Jul 04, 2012 at 01:17:00AM +1000, Joel Sing wrote:
> > > > The following diff updates lan
On Wednesday 04 July 2012, Juan Francisco Cantero Hurtado wrote:
> On Wed, Jul 04, 2012 at 01:17:00AM +1000, Joel Sing wrote:
> > The following diff updates lang/go to Go 1.0.2 - the current stable
> > release. Regress passes on both amd64 and i386.
> >
> > ok?
>
&g
The following diff updates lang/go to Go 1.0.2 - the current stable release.
Regress passes on both amd64 and i386.
ok?
Index: Makefile
===
RCS file: /cvs/ports/lang/go/Makefile,v
retrieving revision 1.3
diff -u -p -r1.3 Makefile
---
On Saturday 05 May 2012, Tobias Sarnowski wrote:
> On 05/04/12 15:11, Joel Sing wrote:
> > The following diff update Go to version 1.0.1. This release pulls several
> > bug fixes up to the stable branch.
> >
> > ok?
>
> Basically works for me on openbsd-current/
The following diff update Go to version 1.0.1. This release pulls several
bug fixes up to the stable branch.
ok?
Index: Makefile
===
RCS file: /cvs/ports/lang/go/Makefile,v
retrieving revision 1.2
diff -u -p -r1.2 Makefile
--- Makefi
Since the rfork syscall has gone away, we need to switch lang/go to tfork,
as is done by the following diff. Passes 'make regress' on both amd64 and
i386.
ok?
Index: patches/patch-src_pkg_runtime_sys_openbsd_386_s
===
RCS file: /cvs/
On Friday 30 March 2012, Stuart Henderson wrote:
> On 2012/03/30 01:05, Joel Sing wrote:
> > Go 1 was released yesterday - the attached is an updated port.
> >
> > Any further comments? Any oks?
>
> The diff below rolls the files which are common between i386/amd
runtime/extern.go:139: cannot use theGoarch as type
> string in const initializer ~/tmp/go$
Ugh, looks like I messed up the PLIST. Try the attached version instead :)
> On 01:05 Fri 30 Mar , Joel Sing wrote:
> > Go 1 was released yesterday - the attached is an updated port.
> >
>
Go 1 was released yesterday - the attached is an updated port.
Any further comments? Any oks?
On Monday 26 March 2012, Joel Sing wrote:
> A new version - this updates the port to the 2012-03-22 weekly release
> (effectively Go v1 RC2) and fixes the issue with the regress path for
>
On Friday 23 March 2012, Juan Francisco Cantero Hurtado wrote:
> On Fri, Mar 23, 2012 at 01:08:48AM +1100, Joel Sing wrote:
> > Attached is an updated version of the port for Go:
> >
> > - Version numbering is now 1.0preMMDD as suggested by sthen.
> >
> > - F
A new version - this updates the port to the 2012-03-22 weekly release
(effectively Go v1 RC2) and fixes the issue with the regress path for
the "go" binary.
ok?
On Friday 23 March 2012, Joel Sing wrote:
> Attached is an updated version of the port for Go:
>
> - Versi
sysarch() syscall in order to setup TLS.
ok?
On Thursday 22 March 2012, Joel Sing wrote:
> The attached is an initial port for the Go programming language
> (www.golang.org). A little background - Go is approaching a "Go version1"
> release and at that point it will have a stable
On Thursday 22 March 2012, Stuart Henderson wrote:
> On 2012/03/22 02:09, Joel Sing wrote:
> > 1. Version numbering - in some ways once Go version 1 is release the
> > versioning will be somewhat like Python and in the future you may want to
> > install Go version 1 and Go
On Thursday 22 March 2012, Ted Unangst wrote:
> On Thu, Mar 22, 2012, Joel Sing wrote:
> > 1. Version numbering - in some ways once Go version 1 is release the
> > versioning will be somewhat like Python and in the future you may want to
> > install Go version 1 and Go
The attached is an initial port for the Go programming language
(www.golang.org). A little background - Go is approaching a "Go version1"
release and at that point it will have a stable API. Unfortunately, for
several reasons Go version 1 will not be officially supported on OpenBSD,
however the
On Friday 27 January 2012, Joel Sing wrote:
> I suspect that recent versions of KDE are leaking pipe descriptors - for
> example, from within konsole (note fd 3 and 4):
>
> $ fstat -p $$
> USER CMD PID FD MOUNTINUM MODE R/WSZ|DV
> joel ksh
I suspect that recent versions of KDE are leaking pipe descriptors - for
example, from within konsole (note fd 3 and 4):
$ fstat -p $$
USER CMD PID FD MOUNTINUM MODE R/WSZ|DV
joel ksh14524 text / 26028 -r-xr-xr-x r 429720
joel ksh
http://code.google.com/p/openvpn-auth-ldap/
An OpenVPN plugin that implements username/password authentication via
LDAP - rather useful for hybrid environments.
This requires openvpn-plugin.h - rather than reaching into the extracted
openvpn source, it would make more sense to install it as part
On Thursday 26 January 2012, Stuart Henderson wrote:
> On 2012/01/26 23:39, Joel Sing wrote:
> > Update gpioflicker to v0.3
> >
> > ok?
>
> Please remove the REVISION line rather than setting to 0.
> Here's another version which also stops using groff (it&#x
1 - 100 of 103 matches
Mail list logo
