Hi,
Someone commits a patch i tested and validated for nextcloud 9.0.52, can
someone commit ?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211007
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211007)
Thanks in advance!
Loïc Blot
___
freebsd
On 07/13/16 11:50, Kubilay Kocak wrote:
For GitHub there is ports infrastructure, using USE_GITHUB=yes and GH_*
variables. For usage, see our Porters Handbook:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#makefile-master_sites-github-description
Hello and thanks
Hi,
I saw in /usr/ports/UPDATING that special consideration needed to be
given to screen in order to update it from 4.0.4 to 4.4.0. So I made
sure I had no screens running, refreshed the ports tree (r418696),
checked the version I was going to upgrade (4.0.4) and ran portupgrade
-a. To my surprise
On 18/07/2016 10:52 PM, Andrea Venturoli wrote:
> On 07/13/16 11:50, Kubilay Kocak wrote:
>
>> For GitHub there is ports infrastructure, using USE_GITHUB=yes and GH_*
>> variables. For usage, see our Porters Handbook:
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#
Why do you think there is a problem? 4.04.00 == 4.4.0 (and not 4.0.4),
everything is fine, just ignore the leading zeros. ;)
On 19/07/2016 00:58, tech-lists wrote:
> Hi,
>
> I saw in /usr/ports/UPDATING that special consideration needed to be
> given to screen in order to update it from 4.0.4 to
On 18/07/2016 14:27, Pierre Guinoiseau wrote:
> Why do you think there is a problem? 4.04.00 == 4.4.0 (and not 4.0.4),
> everything is fine, just ignore the leading zeros. ;)
That makes no sense and is inconsistent WRT other numbering and
versioning. $4.04 is not $4.4 - applying leading zeros inco
Yup everything is good it's just the way screen does versions sometimes.
On Jul 18, 2016 8:28 AM, "Pierre Guinoiseau" wrote:
> Why do you think there is a problem? 4.04.00 == 4.4.0 (and not 4.0.4),
> everything is fine, just ignore the leading zeros. ;)
>
> On 19/07/2016 00:58, tech-lists wrote:
Walter,
17.07.2016, 22:54, "Walter Schwarzenfeld" :
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210723
>
> The patch is working for me.
Can confirm that it is working for me as well, thanks!
--
Brendan
___
freebsd-ports@freebsd.org mailing list
Hi!
> Someone commits a patch i tested and validated for nextcloud
> 9.0.52, can someone commit ?
Done. Please note that 9.0.53 is out due to
https://httpoxy.org/
http://cert.at/warnings/all/20160718.html
Can you provide a patch ?
--
p...@op
Hi!
> Done. Please note that 9.0.53 is out due to
>
> https://httpoxy.org/
> http://cert.at/warnings/all/20160718.html
>
> Can you provide a patch ?
I've put one up at:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211206
Please check and approve.
--
p...@opse
On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein wrote:
> Hello,
>
> On 7/15/16 11:41 PM, Euan Thoms wrote:
> >
> > Yes. I've used ssl=openssl and ssl=libressl in make.conf, no luck with
> > either. The bottom line is ftp/curl with default port options does not want
> > to build against
On Mon, Jul 18, 2016 at 12:45 PM, Euan Thoms wrote:
>
> On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein wrote:
>
> > Hello,
> >
> > On 7/15/16 11:41 PM, Euan Thoms wrote:
> > >
> > > Yes. I've used ssl=openssl and ssl=libressl in make.conf, no luck with
> either. The bottom line is ftp/curl w
On Tuesday, July 19, 2016 04:03 SGT, Kevin Oberman wrote:
> On Mon, Jul 18, 2016 at 12:45 PM, Euan Thoms wrote:
>
> >
> > On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein wrote:
> >
> > OK, I understand. And I'm glad we're heading somewhere where we will have
> > more consistency. I jus
Hello,
> On Jul 18, 2016, at 4:37 PM, Euan Thoms wrote:
>
>
>> On Tuesday, July 19, 2016 04:03 SGT, Kevin Oberman
>> wrote:
>>
>>> On Mon, Jul 18, 2016 at 12:45 PM, Euan Thoms wrote:
>>>
>>>
>>> On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein wrote:
>
>>>
>>> OK, I understand. And
It's a set of integers separated by dots, not a floating-point number
(even less when there are 2 dots), so he 4.04 != 4.4 comparison doesn't
apply here, it is (4, 04, 0) == (4, 4, 0).
Anyway the issue here - if there is one - is with GNU Screen, not the port.
On 2016-07-18 15:28:02, tech-lists w
On Tuesday, July 19, 2016 05:11 SGT, Jim Ohlstein wrote:
> Hello,
>
> > On Jul 18, 2016, at 4:37 PM, Euan Thoms wrote:
> >
> > OK, I'm clear about the make.conf options and what they mean. But I still
> > have a problem in that even if I use DEFAULT_VERSIONS+=ssl=openssl,
> > ftp/curl w
Hello,
> On Jul 18, 2016, at 6:44 PM, Euan Thoms wrote:
>
>
>> On Tuesday, July 19, 2016 05:11 SGT, Jim Ohlstein wrote:
>>
>> Hello,
>>
>>> On Jul 18, 2016, at 4:37 PM, Euan Thoms wrote:
>
>
>>> OK, I'm clear about the make.conf options and what they mean. But I still
>>> have a problem
On Tue, Jul 19, 2016 at 06:44:49AM +0800 I heard the voice of
Euan Thoms, and lo! it spake thus:
>
> Aha, I got ftp/curl to build using WITH_OPENSSL_PORT=yes. Don't know
> why I didn't try it before, perhaps since it is deprecated.
>
> So, I think we need to address some shortcoming in the new m
On Tuesday, July 19, 2016 07:32 SGT, "Matthew D. Fuller"
wrote:
> On Tue, Jul 19, 2016 at 06:44:49AM +0800 I heard the voice of
> Euan Thoms, and lo! it spake thus:
> >
> > Aha, I got ftp/curl to build using WITH_OPENSSL_PORT=yes. Don't know
> > why I didn't try it before, perhaps since it
19 matches
Mail list logo
