On Wed, 24 May 2017 20:10:00 +0200, "O. Hartmann"
wrote:
> Am Wed, 24 May 2017 13:04:30 -0500
> Larry Rosenman schrieb:
>
> > On 5/24/17, 1:01 PM, "O. Hartmann" wrote:
> >
> > Am Wed, 24 May 2017 19:40:46 +0200
> > "O. Hartmann" schrieb:
> >
> > > Am Wed, 24 May 2017 12:2
...@freebsd.org"
>> Message-ID: <1c1ab22c-60bf-4707-f635-8069aa1e0...@freebsd.org>
>> Subject: Re: svn commit: r318757 - head
>> References: <201705232025.v4nkpnrh001...@repo.freebsd.org>
>>
>>
>> <145539de-59b4-4f21-
rotected-headers="v1"
> From: Bryan Drewery
> To: Larry Rosenman , Ed Maste ,
> src-committ...@freebsd.org, svn-src-...@freebsd.org,
> svn-src-head@freebsd.org,
> "freebsd-curr...@freebsd.org"
> Message-ID: <1c1ab22c-60bf-4707-f635-8069aa1e0..
Am Wed, 24 May 2017 12:11:06 -0700
"Ngie Cooper (yaneurabeya)" schrieb:
> > On May 24, 2017, at 11:10, O. Hartmann wrote:
> >
> > Am Wed, 24 May 2017 13:04:30 -0500
> > Larry Rosenman schrieb:
>
> …
>
> > I use the traditional "make" way (via portmaster)
>
> There were some report
> On May 24, 2017, at 11:10, O. Hartmann wrote:
>
> Am Wed, 24 May 2017 13:04:30 -0500
> Larry Rosenman schrieb:
…
> I use the traditional "make" way (via portmaster)
There were some reports about needing to do “make clean” before “make
install”. Memory serves me correctly there are
Am Wed, 24 May 2017 13:04:30 -0500
Larry Rosenman schrieb:
> On 5/24/17, 1:01 PM, "O. Hartmann" wrote:
>
> Am Wed, 24 May 2017 19:40:46 +0200
> "O. Hartmann" schrieb:
>
> > Am Wed, 24 May 2017 12:28:51 -0500
> > Larry Rosenman schrieb:
> >
> > > I fixed my issu
On 5/24/17, 1:01 PM, "O. Hartmann" wrote:
Am Wed, 24 May 2017 19:40:46 +0200
"O. Hartmann" schrieb:
> Am Wed, 24 May 2017 12:28:51 -0500
> Larry Rosenman schrieb:
>
> > I fixed my issues by force-rebuilding perl and all installed p5-*
ports.
> >
> >
Am Wed, 24 May 2017 19:40:46 +0200
"O. Hartmann" schrieb:
> Am Wed, 24 May 2017 12:28:51 -0500
> Larry Rosenman schrieb:
>
> > I fixed my issues by force-rebuilding perl and all installed p5-* ports.
> >
> >
>
>
> This isn't possible in my case :-(
>
> lang/perl rebuilds all right, but
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281
On 5/24/17, 12:40 PM, "O. Hartmann" wrote:
Am Wed, 24 May 2017 12:28:51 -0500
Larry Rosenman schrie
Am Wed, 24 May 2017 12:28:51 -0500
Larry Rosenman schrieb:
> I fixed my issues by force-rebuilding perl and all installed p5-* ports.
>
>
This isn't possible in my case :-(
lang/perl rebuilds all right, but every p5-* ports fails with
[...]
Checking if your kit is complete...
ListUtil.c: l
I fixed my issues by force-rebuilding perl and all installed p5-* ports.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281
_
Am Wed, 24 May 2017 08:06:34 -0500
Larry Rosenman schrieb:
> The initial failure:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=peripatus&dt=2017-05-23%2019%3A17%3A42
>
> I then recompiled perl, and got:
> borg.lerctr.org /home/pgbuildfarm $ cd /home/pgbuildfarm/bin/latest
> && ./run
The initial failure was NOT, except that the PostgreSQL build builds a PL/Perl
interpreter that MIGHT
Be considered that.
It was unexpected.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 17716 Limpia Crk
On Wed, May 24, 2017 at 08:06:34AM -0500, Larry Rosenman wrote:
> The initial failure:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=peripatus&dt=2017-05-23%2019%3A17%3A42
>
> I then recompiled perl, and got:
> borg.lerctr.org /home/pgbuildfarm $ cd /home/pgbuildfarm/bin/latest &&
> .
The initial failure:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=peripatus&dt=2017-05-23%2019%3A17%3A42
I then recompiled perl, and got:
borg.lerctr.org /home/pgbuildfarm $ cd /home/pgbuildfarm/bin/latest &&
./run_branches.pl --run-all --config=/home/pgbuildfarm/conf/build-farm.conf
S
On Tue, May 23, 2017 at 04:46:14PM -0500, Larry Rosenman wrote:
> My PostgreSQL buildfarm animal BROKE with this change until I force rebuilt
> lang/perl5.24
> and all my p5-* ports.
So what was the symptoms and the error, exactly ?
A lot of efforts were spent to ensure that _consistent_ set of o
On Tue, May 23, 2017 at 05:39:50PM -0400, Allan Jude wrote:
> The project also includes fixing a number of other long-standing-
> because-of-ABI changes, like the max length of a mountpoint is now
> 1024 instead of some small value (60 or 80 or something it was before)
It was around 80. I hit tha
On 5/23/2017 4:29 PM, Bryan Drewery wrote:
> On 5/23/2017 4:24 PM, Larry Rosenman wrote:
>> borg.lerctr.org /home/ler $ sudo poudriere jail -l
>> JAILNAME VERSION ARCH METHOD TIMESTAMP
>> PATH
>> p103amd64 10.3-RELEASE-p18 amd64 http 2017-04-23
On 5/23/2017 4:24 PM, Larry Rosenman wrote:
> borg.lerctr.org /home/ler $ sudo poudriere jail -l
> JAILNAME VERSION ARCH METHOD TIMESTAMP
> PATH
> p103amd64 10.3-RELEASE-p18 amd64 http 2017-04-23 08:39:24
> /usr/local/poudriere/jails/p103amd64
borg.lerctr.org /home/ler $ sudo poudriere jail -l
JAILNAME VERSION ARCH METHOD TIMESTAMP PATH
p103amd64 10.3-RELEASE-p18 amd64 http 2017-04-23 08:39:24
/usr/local/poudriere/jails/p103amd64
p103i386 10.3-RELEASE-p18 i386 http
On 5/23/2017 2:46 PM, Larry Rosenman wrote:
> My PostgreSQL buildfarm animal BROKE with this change until I force rebuilt
> lang/perl5.24
> and all my p5-* ports.
>
> emulators/qemu-user-static also won’t compile (sbruno@ is on this one).
>
> Poudriere did *NOT* force a fuill rebuild even though
On 05/23/17 14:39, Allan Jude wrote:
> On 2017-05-23 17:33, Alexey Dokuchaev wrote:
>> On Tue, May 23, 2017 at 08:25:49PM +, Ed Maste wrote:
>>> New Revision: 318757
>>> URL: https://svnweb.freebsd.org/changeset/base/318757
>>>
>>> Log:
>>> Add note to UPDATING for ino64 to follow the standar
On 05/23/17 23:33, Alexey Dokuchaev wrote:
On Tue, May 23, 2017 at 08:25:49PM +, Ed Maste wrote:
New Revision: 318757
URL: https://svnweb.freebsd.org/changeset/base/318757
Log:
Add note to UPDATING for ino64 to follow the standard upgrade process
...
+20170523:
+ The "ino64" 64-bit
My PostgreSQL buildfarm animal BROKE with this change until I force rebuilt
lang/perl5.24
and all my p5-* ports.
emulators/qemu-user-static also won’t compile (sbruno@ is on this one).
Poudriere did *NOT* force a fuill rebuild even though freebsd-version *WAS*
bumped.
Is there a hazard for ot
On 2017-05-23 17:33, Alexey Dokuchaev wrote:
> On Tue, May 23, 2017 at 08:25:49PM +, Ed Maste wrote:
>> New Revision: 318757
>> URL: https://svnweb.freebsd.org/changeset/base/318757
>>
>> Log:
>> Add note to UPDATING for ino64 to follow the standard upgrade process
>> ...
>> +20170523:
>> +
> On May 23, 2017, at 14:33, Alexey Dokuchaev wrote:
>
> On Tue, May 23, 2017 at 08:25:49PM +, Ed Maste wrote:
>> New Revision: 318757
>> URL: https://svnweb.freebsd.org/changeset/base/318757
>>
>> Log:
>> Add note to UPDATING for ino64 to follow the standard upgrade process
>> ...
>> +201
On Tue, May 23, 2017 at 08:25:49PM +, Ed Maste wrote:
> New Revision: 318757
> URL: https://svnweb.freebsd.org/changeset/base/318757
>
> Log:
> Add note to UPDATING for ino64 to follow the standard upgrade process
> ...
> +20170523:
> + The "ino64" 64-bit inode project has been committed
Author: emaste
Date: Tue May 23 20:25:49 2017
New Revision: 318757
URL: https://svnweb.freebsd.org/changeset/base/318757
Log:
Add note to UPDATING for ino64 to follow the standard upgrade process
The existing upgrade process documented in UPDATING is both necessary
and sufficient for upgr
28 matches
Mail list logo