Re: r347638 breaks mergemaster
On Thu, 16 May 2019 at 13:34, David Wolfskill wrote: > ... > But rr347638 moved master.passwd from src/etc to lib/libc/gen, so > mergemaster ... isn't happy: > > | *** Creating the temporary root environment in /var/tmp/temproot > | *** /var/tmp/temproot ready for use > | *** Creating and populating directory structure in /var/tmp/temproot > | > | cp: /usr/src/etc/master.passwd: No such file or directory > | > | *** FATAL ERROR: Cannot copy files to the temproot environment > > I don't know if etcupdate is similarly affected. > It is. I got the same error message from etcupdate. ___ 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: FreeBSD Core Team Response to Controversial Social Media Posts
On Sun, 12 May 2019 at 18:28, Igor Mozolevsky wrote: > On Friday, 10 May 2019, FreeBSD Core Team Secretary > wrote: > > > The FreeBSD Core Team is aware of recent controversial statements made > > on social media by a FreeBSD developer. We, along with the Code of > > Conduct review committee, are investigating the matter and will decide > > what action to take. > > > > > -- > > FreeBSD Core Team > > This seems to be a wanton violation of Article 19 of the Universal > Declaration of Human Rights [1]. > > 1. https://www.un.org/en/universal-declaration-human-rights/ More applicable if you think that UN declarations don't apply to you:- https://www.supremecourt.gov/opinions/16pdf/15-1293_1o13.pdf -- Igor M. ___ 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: r347638 breaks mergemaster
On Thu, May 16, 2019, at 7:34 AM, David Wolfskill wrote: > Today's daily update of head is from r347606 to r347682. > > src/UPDATING (still) cites: > > ... > To rebuild everything and install it on the current system. > --- > # Note: sometimes if you are running current you gotta do more than > # is listed here if you are upgrading from a really old current. > > > make buildworld > make buildkernel KERNCONF=YOUR_KERNEL_HERE > make installkernel KERNCONF=YOUR_KERNEL_HERE > [1] > [3] > mergemaster -Fp [5] > make installworld > mergemaster -Fi [4] > make delete-old [6] > > > > But rr347638 moved master.passwd from src/etc to lib/libc/gen, so > mergemaster ... isn't happy: > > | *** Creating the temporary root environment in /var/tmp/temproot > | *** /var/tmp/temproot ready for use > | *** Creating and populating directory structure in /var/tmp/temproot > | > | cp: /usr/src/etc/master.passwd: No such file or directory > | > | *** FATAL ERROR: Cannot copy files to the temproot environment > > I don't know if etcupdate is similarly affected. Looking at this. Thanks for reporting. Regards, Brad Davis ___ 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"
r347638 breaks mergemaster
Today's daily update of head is from r347606 to r347682. src/UPDATING (still) cites: ... To rebuild everything and install it on the current system. --- # Note: sometimes if you are running current you gotta do more than # is listed here if you are upgrading from a really old current. make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE [1] [3] mergemaster -Fp [5] make installworld mergemaster -Fi [4] make delete-old [6] But rr347638 moved master.passwd from src/etc to lib/libc/gen, so mergemaster ... isn't happy: | *** Creating the temporary root environment in /var/tmp/temproot | *** /var/tmp/temproot ready for use | *** Creating and populating directory structure in /var/tmp/temproot | | cp: /usr/src/etc/master.passwd: No such file or directory | | *** FATAL ERROR: Cannot copy files to the temproot environment I don't know if etcupdate is similarly affected. Peace, david -- David H. Wolfskill da...@catwhisker.org Since the Senate is controlled by Trump's lap-dogs, impeachment now is foolish. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: Inability to build FreeBSD-current amd64
On 2019-05-16 09:36, Thomas Mueller wrote: from Niclas Zeising: I run a build WITH_CLANG_EXTRAS, and that worked, on current, last weekend, if that's what you're asking about. This won't take away the need for llvm ports in certain ports builds, however, such as firefox and mesa. So now I wonder why I failed four times straight building current. One definition of insanity is doing the same thing repeatedly and expecting a different result. Maybe the build host, 11.1-STABLE from July 30, 2017, was too old? I wouldn't have thought it was too old. I could also try an old current host from August 2, 2017, or try to build 12-STABLE from my 11.1-STABLE host. Would I do better to build amd64 or i386 from amd64 host? I presently have no FreeBSD i386 installation, only amd64. That could be that the toolchain on 11.1 stable is too old to build current. If you've posted the error you're getting, I've missed it, however. Regards -- Niclas ___ 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: Inability to build FreeBSD-current amd64
from Niclas Zeising: > I run a build WITH_CLANG_EXTRAS, and that worked, on current, last weekend, if > that's what you're asking about. > This won't take away the need for llvm ports in certain ports builds, however, > such as firefox and mesa. So now I wonder why I failed four times straight building current. One definition of insanity is doing the same thing repeatedly and expecting a different result. Maybe the build host, 11.1-STABLE from July 30, 2017, was too old? I wouldn't have thought it was too old. I could also try an old current host from August 2, 2017, or try to build 12-STABLE from my 11.1-STABLE host. Would I do better to build amd64 or i386 from amd64 host? I presently have no FreeBSD i386 installation, only amd64. Tom ___ 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"
