We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I fetched repo for rel-v2022.2. When I run MACHINE=zc706-zynq7 bitbake petalinux-image-minimal, bitbake cannot fetch xsct binary tarball:
MACHINE=zc706-zynq7 bitbake petalinux-image-minimal
NOTE: Fetching xsct binary tarball from http://petalinux.xilinx.com/sswreleases/rel-v2022/xsct-trim/xsct-2022-2.tar.xz;sha256sum=8a3272036ca61f017f357bf6ad9dfbdec6aebb39f43c3ca0cee7ec86ea4c066f;downloadfilename=xsct_2022.2.tar.xz
Build stucks on the command above, The link itself returns 404.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I fetched repo for rel-v2022.2. When I run
MACHINE=zc706-zynq7 bitbake petalinux-image-minimal
, bitbake cannot fetch xsct binary tarball:Build stucks on the command above, The link itself returns 404.
![image](https://private-user-images.githubusercontent.com/55915826/237913672-f151b2a0-c6cf-4767-8c6e-c813c43e0970.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUwNjQwNDMsIm5iZiI6MTcyNTA2Mzc0MywicGF0aCI6Ii81NTkxNTgyNi8yMzc5MTM2NzItZjE1MWIyYTAtYzZjZi00NzY3LThjNmUtYzgxM2M0M2UwOTcwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MzElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODMxVDAwMjIyM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM0ZjI4ZDdiMTE5MzBhZDk4OGM4NTBlOTVmNDEzYzRlZWNkYzM4NzU1NTgyOWQwODU0MjBhYWU1OGIyN2I2NzAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.8UgjK-BpCyR0HUD7cs9TSiR6Dj87-btfzbFXYERDHtA)
The text was updated successfully, but these errors were encountered: