On Sat, 5 Jan 2019 at 04:44, Julian H. Stacey wrote:
>
> > WITHOUT_REPRODUCIBLE_BUILD. You probably want to add it to
> > /etc/src.conf.
>
> Thanks Ed, Added, Rebuilding.
>
> I suggest the default should be the opposite, or has that already
> been discussed & I missed it ?
I don't know that there
Hi, Reference:
> From: Ed Maste
> Date: Fri, 4 Jan 2019 09:10:20 -0500
Ed Maste wrote:
> On Fri, 4 Jan 2019 at 08:42, Julian H. Stacey wrote:
> >
> > Matthias Apitz wrote:
> > > $ sh /usr/src/sys/conf/newvers.sh
> >
> > Me too. Mine also returns nothing. Ditto uname. Ditto dmesg.
> On Jan 4, 2019, at 19:00, Yoshihiro Ota wrote:
>
> I've seen such failures with NFS without lockd.
>
> Svn fails as it cannot lock its files, too.
Yeah. lockd must be running in order for this to work. This hasn’t changed
in the last few years.
Cheers,
-Enji
I've seen such failures with NFS without lockd.
Svn fails as it cannot lock its files, too.
Hiro
On Fri, 4 Jan 2019 10:41:56 -0500
Ed Maste wrote:
> On Fri, 4 Jan 2019 at 10:36, Matthias Apitz wrote:
> >
> > To save space on the netbook
> > I excluded /usr/src/.svn which is causing now the ab
On Fri, 4 Jan 2019 at 10:36, Matthias Apitz wrote:
>
> To save space on the netbook
> I excluded /usr/src/.svn which is causing now the absence of the
> revision number.
Yes, newvers.sh relies on the metadata in .svn to determine the
revision number so this is as expected.
___
El día viernes, enero 04, 2019 a las 09:30:05a. m. -0500, Ed Maste escribió:
> It looks like some aspects of this have been broken since r308789. Do
> you happen to have a git or hg tree higher up in the directory
> hierarchy? For example, ~/.git, and ~/src/freebsd/...? I'll have a fix
> for that
On Fri, 4 Jan 2019 at 08:42, Julian H. Stacey wrote:
>
> Matthias Apitz wrote:
> > $ sh /usr/src/sys/conf/newvers.sh
>
> Me too. Mine also returns nothing. Ditto uname. Ditto dmesg. Annoying.
Please read the UPDATING entry and the src.conf description for
WITHOUT_REPRODUCIBLE_BUILD. You probably
On Fri, 4 Jan 2019 at 00:53, Matthias Apitz wrote:
>
> Why is this? I've read in UPDATING that:
>
> ...
> 20180913:
> Reproducible build mode is now on by default, in preparation for
> FreeBSD 12.0. This eliminates build metadata such as the user,
> ...
>
> But this does not expla
On Fri, 4 Jan 2019 15:24:42 +0100
Gary Jennejohn wrote:
> On Fri, 04 Jan 2019 14:41:43 +0100
> "Julian H. Stacey" wrote:
>
> > Matthias Apitz wrote:
> > > $ sh /usr/src/sys/conf/newvers.sh
> >
> > Me too. Mine also returns nothing. Ditto uname. Ditto dmesg. Annoying.
> >
> > /usr/src/.
On Fri, 04 Jan 2019 14:41:43 +0100
"Julian H. Stacey" wrote:
> Matthias Apitz wrote:
> > $ sh /usr/src/sys/conf/newvers.sh
>
> Me too. Mine also returns nothing. Ditto uname. Ditto dmesg. Annoying.
>
> /usr/src/.svn_revision 342578 probably what I used to install / from,
> but how to tell no
Matthias Apitz wrote:
> $ sh /usr/src/sys/conf/newvers.sh
Me too. Mine also returns nothing. Ditto uname. Ditto dmesg. Annoying.
/usr/src/.svn_revision 342578 probably what I used to install / from,
but how to tell now its been excised ?
Good you reported it. (I'd assumed it was local breakage
El día viernes, enero 04, 2019 a las 07:52:40a. m. +0100, Dimitry Andric
escribió:
> On 4 Jan 2019, at 06:52, Matthias Apitz wrote:
> >
> > I've compiled CURRENT from svn and this gave me as 'uname -a' output:
> >
> > FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT r342378 GENERIC
> >
On 4 Jan 2019, at 06:52, Matthias Apitz wrote:
>
> I've compiled CURRENT from svn and this gave me as 'uname -a' output:
>
> FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT r342378 GENERIC amd64
>
> Now I've had do modify a source file (to nail down some problem) and the
> revision numb
Hello,
I've compiled CURRENT from svn and this gave me as 'uname -a' output:
FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT r342378 GENERIC amd64
Now I've had do modify a source file (to nail down some problem) and the
revision number went away from the output; it now says:
FreeBSD c7
14 matches
Mail list logo
