Arch Linux

antechdesigns

Member

From: UK

Registered: 2017-05-09

Posts: 20

Website

build.sh Bug?

Is this a bug in build.sh

cp "${work_dir}/x86_64/airootfs/usr/share/licenses/amd-ucode/LICENSE" \ 

(no such file)

However the file at:

"${work_dir}/x86_64/airootfs/usr/share/licenses/amd-ucode/LICENSE" \

is named :

LICENSE.amd-ucode

or is it intentional ?

Checking the Intel ucode file directory it is just named:

LICENSE" \

Seems like the dot extention has not been hidden ???

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,610

Re: build.sh Bug?

Name changed. See the bug tracker.

eznix

Member

Registered: 2020-06-29

Posts: 25

Re: build.sh Bug?

I just changed the line in build.sh from:

cp "${work_dir}/x86_64/airootfs/usr/share/licenses/amd-ucode/LICENSE" \

to:

cp "${work_dir}/x86_64/airootfs/usr/share/licenses/amd-ucode/LICENSE.amd-ucode" \

And it works for the moment. The entire build.sh is getting a major work over, so its going to change very soon anyway.

Last edited by eznix (2020-07-30 17:10:06)

antechdesigns

Member

From: UK

Registered: 2017-05-09

Posts: 20

Website

Re: build.sh Bug?

I already fixed it before I posted

Not a bug, but check the bug tracker, go figure.

Torxed

Member

Registered: 2013-01-10

Posts: 200

Re: build.sh Bug?

Most likely just an old version of archiso, and thus `packages.x86_64` contains old references.
Update the `archiso` package as well, re-copy the `releng` config and add your changes and build. Should do the trick : )

Last edited by Torxed (2020-07-30 22:38:22)

eznix

Member

Registered: 2020-06-29

Posts: 25

Re: build.sh Bug?

The amd-ucode package was just updated on 07.26.2020 and changed the name of the license file from LICENSE to LICENSE.amd-ucode, this through off build.sh from the 06.30.2020 release version 45.1 as it was expecting the license filename to be LICENSE. It was a simple matter of one package changing something needlessly and another package expecting a simple license filename to be somewhat predictable. The new build.sh does not use hard coded filenames for the intel-ucode and amd-ucode licenses any longer and just copies whatever is in the license directory. Hopefully this type of ridiculous change for the point of change alone will be better handled in the future?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,610

Re: build.sh Bug?

I already fixed it before I posted

Not a bug, but check the bug tracker, go figure.

Who said it's not a bug?