From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: The unshared changes give a problem with build after doing git pull on next Date: Fri, 26 Jul 2024 09:17:58 +0100 Message-ID: <4B595FF5-9FD8-4000-B5AF-DD40D0607F47@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4993844909294685335==" List-Id: --===============4993844909294685335== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, Hmm, this might be a slight transitioning problem=E2=80=A6 If you are now in next and build the distribution, it will likely build in bu= ild_x86_64/ and logs will be stored in logs_x86_64/. If you run ./make.sh cle= an, those directories will be removed. If you however change back to master, it will assume that your build is in bu= ild/ and your logs are in logs/. If you then run clean, it will try to remove= those directories and since they don=E2=80=99t exist, ./make.sh clean will r= eturn really quickly. Is this maybe what happens? You can fix this by either removing the directories by hand or changing to ne= xt, run ./make.sh clean, then change to master and run it again. That should = give you a clean tree. Best, -Michael > On 26 Jul 2024, at 08:57, Adolf Belka wrote: >=20 > Hi Michael, >=20 > I ran git pull origin next on my local repo and then went to try a package = update build. >=20 > The gettoolchain and downloadsrc worked fine. However the ./make.sh clean j= ust came straight back to the cursor without removing any of the directories = in my repo. >=20 > I am now using my master repo version for doing the package update but some= thing has gone wrong with the unshared migration because the clean command wo= rked fine when it was in your own repo. >=20 > Regards, >=20 > Adolf. >=20 --===============4993844909294685335==--