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

Know engines to download for Void Linux #20434

Closed
danielgaban opened this issue Jul 28, 2023 · 5 comments
Closed

Know engines to download for Void Linux #20434

danielgaban opened this issue Jul 28, 2023 · 5 comments
Labels
Milestone

Comments

@danielgaban
Copy link

Problem

from terminal when pnpm prisma init

prisma:warn Prisma doesn't know which engines to download for the Linux distro "void". Falling back to Prisma engines built "debian".

Suggested solution

Add which engine will be downloaded when user is using Void LInux.

Alternatives

Remove warning and stay with the falling back engine "debian".

@janpio janpio added kind/feature A request for a new feature. topic: engine download team/client Issue for team Client. labels Jul 28, 2023
@Jolg42
Copy link
Member

Jolg42 commented Aug 1, 2023

I didn't know about this distribution yet, link: https://voidlinux.org/

@danielgaban If you run cat /etc/os-release, I guess it looks like this?

% cat /etc/os-release 
NAME="Void"
ID="void"
PRETTY_NAME="Void Linux"
HOME_URL="https://voidlinux.org/"
DOCUMENTATION_URL="https://docs.voidlinux.org/"
LOGO="void-logo"
ANSI_COLOR="0;38;2;71;128;97"

DISTRIB_ID="void"

#17545 (comment)

Also, could you tell me which version of Prisma you are using here?

@danielgaban
Copy link
Author

@Jolg42 Yes it looks exactly. Prisma versions used:

@prisma/client 4.16.2
prisma 4.16.2

@cy1der
Copy link

cy1der commented Aug 20, 2023

+1 on this, got this warning when setting up RedwoodJS.

@linde12
Copy link

linde12 commented Aug 22, 2023

Same, on void 👍

@Jolg42
Copy link
Member

Jolg42 commented Mar 6, 2024

I'll close this, as the fallback/default engine should work as expected, so only a report would be needed if there is an issue, let us know if that's the case.

Note that we changed the message, to make it informational only in #23243
The updated message will be part of the next release 5.11.0, next week.

@Jolg42 Jolg42 closed this as completed Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants