-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add Debian riscv64 builds #10502
Merged
Merged
Add Debian riscv64 builds #10502
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tianon
added a commit
that referenced
this pull request
Jul 8, 2021
The most relevant bit to note here is that `riscv64` is still a "Debian Ports" architecture, so unfortunately only Debian Unstable ("Sid") is supported. However, it is in extremely good shape (especially right now while everything is deeply frozen for the imminent Bullseye release), and is impressively well-supported in spite of that. However, this will unfortunately be a limiting factor on the downstream effect of adding this support (in other words, not many other official images are likely to gain the architecture), since Debian Unstable is *not* a great (stable) base for running other software on top of over time (especially after that imminent Bullseye release and Unstable gets to freely earn its name once again). See https://www.debian.org/ports/ and https://ports.debian.org/ for more information about the Debian Ports project in general, and the following for information about ports becoming officially supported "release architectures" (lots of room for contribution here!): - https://ftp-master.debian.org/archive-criteria.html - https://dsa.debian.org/ports/hardware-requirements/ - https://release.debian.org/testing/arch_policy.html - https://wiki.debian.org/PortsDocs/New I personally also think https://buildd.debian.org/stats/ is extremely interesting -- all the release architectures are above 97% of the archive, and `riscv64` is not far behind (appears closer to 95% ATM). Major kudos to everyone who's been involved in getting this port to where it is today!
This was referenced Jul 8, 2021
make all the official images support the riscv64 architecture. (if upstream supports riscv64 )
#8794
Closed
Diff for 54f8e79:diff --git a/_bashbrew-cat b/_bashbrew-cat
index bfcaadb..3420ba1 100644
--- a/_bashbrew-cat
+++ b/_bashbrew-cat
@@ -1,6 +1,6 @@
Maintainers: Tianon Gravi <tianon@debian.org> (@tianon), Paul Tagliamonte <paultag@debian.org> (@paultag)
GitRepo: https://github.com/debuerreotype/docker-debian-artifacts.git
-GitCommit: 90a83b6b730031399d45a49809364b07df0d0087
+GitCommit: 9c1a3db18852520a8b72a4795c7b197bcc93e8a0
amd64-GitCommit: a4f413e5917d5917fb2343c0c37ea0728114c084
amd64-GitFetch: refs/heads/dist-amd64
arm32v5-GitCommit: f0fe8506f93540fae3d6f483f6ff207f412afd1b
@@ -15,6 +15,8 @@ mips64le-GitCommit: d114a529a4a7df3ddb4909dc8891edb9031350eb
mips64le-GitFetch: refs/heads/dist-mips64le
ppc64le-GitCommit: 476679fee8da3b4e947246d5580978380175cd8c
ppc64le-GitFetch: refs/heads/dist-ppc64le
+riscv64-GitCommit: 8c328b0330ae017cd49f86d7b089d12f1b28bd98
+riscv64-GitFetch: refs/heads/dist-riscv64
s390x-GitCommit: 296659d8855ee79e91507b85cade40d99ab893f2
s390x-GitFetch: refs/heads/dist-s390x
@@ -55,11 +57,11 @@ Architectures: amd64, arm32v5, arm32v7, arm64v8, i386
Directory: oldstable/slim
Tags: sid, sid-20210621
-Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, s390x
+Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, riscv64, s390x
Directory: sid
Tags: sid-slim, sid-20210621-slim
-Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, s390x
+Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, riscv64, s390x
Directory: sid/slim
Tags: stable, stable-20210621
@@ -99,15 +101,15 @@ Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, s390x
Directory: testing/slim
Tags: unstable, unstable-20210621
-Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, s390x
+Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, riscv64, s390x
Directory: unstable
Tags: unstable-slim, unstable-20210621-slim
-Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, s390x
+Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, riscv64, s390x
Directory: unstable/slim
Tags: experimental, experimental-20210621
-Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, s390x
+Architectures: amd64, arm32v5, arm32v7, arm64v8, i386, mips64le, ppc64le, riscv64, s390x
Directory: experimental
Tags: rc-buggy, rc-buggy-20210621
|
tianon
added a commit
to docker-library/faq
that referenced
this pull request
Jul 8, 2021
This was referenced Jul 8, 2021
Merged
tianon
added a commit
to docker-library/oi-janky-groovy
that referenced
this pull request
Jul 8, 2021
yosifkit
approved these changes
Jul 8, 2021
Anyone looking for more places to contribute to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The most relevant bit to note here is that
riscv64
is still a "Debian Ports" architecture, so unfortunately only Debian Unstable ("Sid") is supported. However, it is in extremely good shape (especially right now while everything is deeply frozen for the imminent Bullseye release), and is impressively well-supported in spite of that.However, this will unfortunately be a limiting factor on the downstream effect of adding this support (in other words, not many other official images are likely to gain the architecture), since Debian Unstable is not a great (stable) base for running other software on top of over time (especially after that imminent Bullseye release and Unstable gets to freely earn its name once again).
See https://www.debian.org/ports/ and https://ports.debian.org/ for more information about the Debian Ports project in general, and the following for information about ports becoming officially supported "release architectures" (lots of room for contribution here!):
I personally also think https://buildd.debian.org/stats/ is extremely interesting -- all the release architectures are above 97% of the archive, and
riscv64
is not far behind (appears closer to 95% ATM). Major kudos to everyone who's been involved in getting this port to where it is today!