Re: uname -a output without svn revision number
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's a final decision, but for the current release building approach it seems likely this will be added to the list of settings that are changed in the branch for release (i.e., WITH_REPRODUCIBLE_BUILD by default on the branch). ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
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. Annoying. > > Please read the UPDATING entry and the src.conf description for > 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 ? Cheers, Julian -- Julian Stacey, Computer Consultant Sys.Eng. BSD Linux Unix, Munich Aachen Kent First referendum stole 700,000 votes from Brits in EU; 3,700,000 globaly. Lies criminal funded; jobs pound & markets down. 1.9M new voters 1.3M dead. Email MP: "A new referendum will buy UK & EU more time (Art 50.3), to avoid a hard crash, & consider all options." http://berklix.org/brexit/#mp ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
> 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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
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 absence of the > > revision number. > > Yes, newvers.sh relies on the metadata in .svn to determine the > revision number so this is as expected. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
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. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
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 case soon. No, nothing. > > If that's not the case, please run (from the src toplevel dir) > > sh -x sys/conf/newvers.sh >newvers.log 2>&1 I looked into the script sys/conf/newvers.sh and I think I understand now the problem. I compiled /usr/src on some other faster server and moved /usr/src and /usr/obj to my netbook as tar-archive to update kernel and userland there. To save space on the netbook I excluded /usr/src/.svn which is causing now the absence of the revision number. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. signature.asc Description: PGP signature
Re: uname -a output without svn revision number
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 want to add it to /etc/src.conf. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
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 explain why now the SVN revision number went away. 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 case soon. If that's not the case, please run (from the src toplevel dir) sh -x sys/conf/newvers.sh >newvers.log 2>&1 and make the output available (email to me is fine). ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
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/.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 waiting my time to > > trace & fix). Yet another annoying half baked commit, wasting time. > > > > Strange. I just made a HEAD kernel from an up-to-date /usr/src and > vers.c shows: > > #define VERSTR "FreeBSD 13.0-CURRENT #1 r342759M: Fri Jan 4 15:17:07 > CET 2019\nga...@ernst.home:/usr/obj/usr/src/amd64.amd64/sys/ernst\n" > > The 'M' appears because I use a modified /sys/conf/files to prevent > including the for me useless iflib stuff. > Run ``sh -x /usr/src/sys/conf/newvers.sh'' and you'll see the correct output. -- Gary Jennejohn ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
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 now its been excised ? > > Good you reported it. (I'd assumed it was local breakage waiting my time to > trace & fix). Yet another annoying half baked commit, wasting time. > Strange. I just made a HEAD kernel from an up-to-date /usr/src and vers.c shows: #define VERSTR "FreeBSD 13.0-CURRENT #1 r342759M: Fri Jan 4 15:17:07 CET 2019\nga...@ernst.home:/usr/obj/usr/src/amd64.amd64/sys/ernst\n" The 'M' appears because I use a modified /sys/conf/files to prevent including the for me useless iflib stuff. -- Gary Jennejohn ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
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 waiting my time to trace & fix). Yet another annoying half baked commit, wasting time. Cheers, Julian -- Julian Stacey, Computer Consultant Sys.Eng. BSD Linux Unix, Munich Aachen Kent First referendum stole 700,000 votes from Brits in EU; 3,700,000 globaly. Lies criminal funded; jobs pound & markets down. 1.9M new voters 1.3M dead. Email MP: "A new referendum will buy UK & EU more time (Art 50.3), to avoid a hard crash, & consider all options." http://berklix.org/brexit/#mp ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uname -a output without svn revision number
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 > > 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 c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC amd64 > > > > Why is this? I've read in UPDATING that: > > > > ... > > > > But this does not explain why now the SVN revision number went away. > > For me, it doesn't go away, but shows an "M" suffix, instead. In > /usr/obj/usr/src/sys/GENERIC/vers.c it shows: > > #define VERSTR "FreeBSD 13.0-CURRENT r342593M \n" > > What is the output of sh /usr/src/sys/conf/newvers.sh for you? $ ls -l /usr/obj/usr/src/amd64.amd64/sys/GENERIC/vers.c -rw-r--r-- 1 root wheel 1919 3 ene. 11:59 /usr/obj/usr/src/amd64.amd64/sys/GENERIC/vers.c $ tail -12 /usr/obj/usr/src/amd64.amd64/sys/GENERIC/vers.c #define SCCSSTR "@(#)FreeBSD 13.0-CURRENT GENERIC" #define VERSTR "FreeBSD 13.0-CURRENT GENERIC\n" #define RELSTR "13.0-CURRENT" char sccs[sizeof(SCCSSTR) > 128 ? sizeof(SCCSSTR) : 128] = SCCSSTR; char version[sizeof(VERSTR) > 256 ? sizeof(VERSTR) : 256] = VERSTR; char compiler_version[] = "FreeBSD clang version 7.0.1 (tags/RELEASE_701/final 349250) (based on LLVM 7.0.1)"; char ostype[] = "FreeBSD"; char osrelease[sizeof(RELSTR) > 32 ? sizeof(RELSTR) : 32] = RELSTR; int osreldate = 135; char kern_ident[] = "GENERIC"; $ sh /usr/src/sys/conf/newvers.sh I did around 11:50 am (i.e. the mod time of vers.c matches) a 'make buildkernel NO_CLEAN=yes' matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. signature.asc Description: PGP signature
Re: uname -a output without svn revision number
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 number went away from the output; it now says: > > FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC amd64 > > 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, >host, and time from the kernel (and uname), unless the working tree >corresponds to a modified checkout from a version control system. >The previous behavior can be obtained by setting the /etc/src.conf >knob WITHOUT_REPRODUCIBLE_BUILD. > ... > > But this does not explain why now the SVN revision number went away. For me, it doesn't go away, but shows an "M" suffix, instead. In /usr/obj/usr/src/sys/GENERIC/vers.c it shows: #define VERSTR "FreeBSD 13.0-CURRENT r342593M \n" What is the output of sh /usr/src/sys/conf/newvers.sh for you? -Dimitry signature.asc Description: Message signed with OpenPGP
uname -a output without svn revision number
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 c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC amd64 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, host, and time from the kernel (and uname), unless the working tree corresponds to a modified checkout from a version control system. The previous behavior can be obtained by setting the /etc/src.conf knob WITHOUT_REPRODUCIBLE_BUILD. ... But this does not explain why now the SVN revision number went away. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. signature.asc Description: PGP signature
