Re: x11/x3270

2020-02-16 Thread Matthias Apitz
El día sábado, febrero 15, 2020 a las 02:55:21p. m. +0100, Kurt Jaeger escribió: > Hi! > > > Hey, there's an opportunity for you to step up and update that port! > > (And perhaps ping the maintainer if he's still around and interested > > in that port, not having done anything in about five years

Re: x11/x3270

2020-02-15 Thread Vidar Karlsen
On 2/15/20 2:55 PM, Kurt Jaeger wrote: Hi! Hey, there's an opportunity for you to step up and update that port! (And perhaps ping the maintainer if he's still around and interested in that port, not having done anything in about five years is an indicator of sorts. This port can be yours, at th

Re: x11/x3270

2020-02-15 Thread Kurt Jaeger
Hi! > Hey, there's an opportunity for you to step up and update that port! > (And perhaps ping the maintainer if he's still around and interested > in that port, not having done anything in about five years is an > indicator of sorts. This port can be yours, at the cost of a patch!) This can be y

Re: x11/x3270

2020-02-15 Thread Christoph Moench-Tegeder
## Matthias Apitz (g...@unixarea.de): > Trying build of x3270-3.3.15_3 even though it is marked BROKEN. Hm. x11/x3270$ svn log distinfo r376982 | madpilot | 2015-01-13 20:15:59 +0100 (Tue, 13 Jan 2015) | 9 lines Last updat

Re: x11/x3270

2020-02-15 Thread Kurt Jaeger
Hi! > Why is x11/x3270 marked as BROKEN? Because the distfile is only available from the distcache. It needs to be available from some other site, otherwise the port is considered broken. > [root@jet /usr/ports/x11/x3270]# make fetch > ===> x3270-3.3.15_3 is marked as broken: unfetchable. > **