Re: revision not displayed in a2440348eed7
- Reply: Marek Zarychta : "Re: revision not displayed in a2440348eed7"
- In reply to: Cy Schubert : "Re: revision not displayed in a2440348eed7"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 26 Sep 2023 23:07:23 UTC
On Tue, 26 Sep 2023 15:19:46 -0700 Cy Schubert <Cy.Schubert@cschubert.com> wrote: > In message <20230926231431.20f42fec1075c3980446c50a@dec.sakura.ne.jp>, > Tomoaki > AOKI writes: > > On Tue, 26 Sep 2023 15:48:50 +0200 > > Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> wrote: > > > > > W dniu 26.09.2023 o 13:30, KIRIYAMA Kazuhiko pisze: > > > > At least up to 15.0-CURRENT, nothing has happend by > > > > WITHOUT_REPRODUCIBLE_BUILD=yes. Something has changed in > > > > 15.0-CURRENT at some time. I've rebuilded with 3fb80f1476c7, > > > > but revision not showed by `uname -a' ;-( > > > > > > > > What changed ???? > > > > > > Nothing changed. Perhaps your build system can't check git hash ? If > > > your sources are from git repository, you need at least git-lite > > > installed and full git repository available on build machine. If you > > > checked out the repository with gitup and have gitup installed, it > > > should also work. It won't work if your build machine has access to > > > only a part of the repository like worktree. > > > > > > Cheers > > > > > > -- > > > Marek Zarychta > > > > Just a possibility, but copying src tree to directory other than the > > directory where checked out from git repo and building there could > > lose track with git hash. > > > > Another possibility is that if you build src with any user other than > > the one owning local (pulled) git repo could also lose track with git > > hash. For example, if I `git log HEAD` with regular user and the local > > repo is pulled by root, it fails. No special configuration is done. > > > > % git log HEAD > > fatal: detected dubious ownership in repository at '/usr/src' > > To add an exception for this directory, call: > > > > git config --global --add safe.directory /usr/src > > > > > > This could be due to e6dc6a27230, which was committed this morning. There > is discussion on the src commits ML (dev-commits-src-all, > dev-commits-src-main) about reverting the change. > > > -- > Cheers, > Cy Schubert <Cy.Schubert@cschubert.com> > FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org > NTP: <cy@nwtime.org> Web: https://nwtime.org > > e^(i*pi)+1=0 Would be unrelated here, unfortunately. As the subject says, the commit the original reporter is bitten at (not bi-sected) is at a2440348eed7, which is before e6dc6a27230. -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>