Skip to content
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

Drop i386 support #321

Open
zeha opened this issue Feb 10, 2025 · 4 comments · May be fixed by #324
Open

Drop i386 support #321

zeha opened this issue Feb 10, 2025 · 4 comments · May be fixed by #324
Assignees

Comments

@zeha
Copy link
Member

zeha commented Feb 10, 2025

It won't be possible to install a bootable trixie i386. At least for that combo (+ testing + unstable) we should fail early.

Big q: should we drop all code paths for i386?

@zeha
Copy link
Member Author

zeha commented Feb 10, 2025

@mika assigning you for a decision

@mika
Copy link
Member

mika commented Feb 11, 2025

Yeah good point, thanks for raising this.

Neither any of my customers nor myself use any actual i386 system any longer.

I don't think that we strictly need i386 support for our vision (like #311), like for VM images or alike?

@jkirk jkirk pinned this issue Feb 11, 2025
@jkirk jkirk unpinned this issue Feb 11, 2025
@jkirk
Copy link
Contributor

jkirk commented Feb 11, 2025

@zeha
Copy link
Member Author

zeha commented Feb 24, 2025

Decision from meeting: drop it all.

zeha added a commit that referenced this issue Feb 25, 2025
Debian stops supporting the "i386" port with trixie, and we have not
been testing it for a very long time. Also simplifies some code here.

Closes: #321
@zeha zeha linked a pull request Feb 25, 2025 that will close this issue
zeha added a commit that referenced this issue Feb 27, 2025
Debian stops supporting the "i386" port with trixie, and we have not
been testing it for a very long time. Also simplifies some code here.

Closes: #321
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants