-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
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
[3.1.107-SDK] Build fails during core-setup #1716
Comments
What version of Debian is this? I would have expected the version to be between the |
It's bullseye. My /etc/os-release is as follows:
|
Hmm, yeah, that's "missing" some version variables vs. 9/stretch which we build on routinely in PR validation / CI, and 10/buster: PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/" (They're optional in the I think that #297 probably tracks fixing this requirement--in general it tracks broadening how well we support distros that are unknown in similar ways. @cerebrate do you know if Debian bullseye will get |
Aha! Well, that's easy enough to fix for now. And I would presume bullseye would get those fields once it formally ships as Debian 11 and becomes the new stable, as that's what's seemed to happen in the past, but I don't have any inside insight on that. It's a little inconvenient from a packaging point of view, though, because new packages are supposed to be built against testing or unstable, which lack those fields. |
I'm trying to build the 3.1.107-SDK release of source-build on Debian under WSL, looking towards packaging it for Debian, and am running into trouble during compilation; specifically, 11 errors show up during core-setup building, ending with:
I have attached core-setup.log here, which contains a number of errors of the form:
I can confirm that
corehost
does not exist under/home/avatar/src/source-build-3.1.107-SDK/artifacts/src/core-setup.fcfdef8d6ba770e4d7ba9efefe2591d8c33a1fc6/artifacts/bin/debian-x64.Release
; however, it does exist under a parallel directory nameddebian.-x64.Release
, which seems odd.Thoughts?
The text was updated successfully, but these errors were encountered: