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
I am updating gentoo ebuild for gsa. Now on gentoo we are using gsa v. 23.0.0.
I have "built" both gsa v. 23.2.0 and gsa v. 23.1.1 and on both versions the menu bar is not rendered as expected (see pictures below).
The gsa gentoo's ebuild uses the gsa-node-modules tar archive.
I have tested both gsa newer versions with gsad v. 22.9.1, 22.10.0 and 22.11.0 but the problem seems to be unrelated to gsad.
On gsa 23.0.0 the menu bar shows as expected:
gsa-23.0.0
gsa-23.1.1 gsa-23.2.0
Operating system: Linux 6.6.38-gentoo DISTRIB_ID="Gentoo"
Installation method / source: source
Edited: I noticed there is no static/ dir in the build directory after building gsa, but there is no static/ dir even in the packaged dist files.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am updating gentoo ebuild for gsa. Now on gentoo we are using gsa v. 23.0.0.
I have "built" both gsa v. 23.2.0 and gsa v. 23.1.1 and on both versions the menu bar is not rendered as expected (see pictures below).
The gsa gentoo's ebuild uses the gsa-node-modules tar archive.
I have tested both gsa newer versions with gsad v. 22.9.1, 22.10.0 and 22.11.0 but the problem seems to be unrelated to gsad.
On gsa 23.0.0 the menu bar shows as expected:
Expected behavior
gsa-23.0.0
Actual behavior
gsa-23.1.1
gsa-23.2.0
Environment
Operating system:
Linux 6.6.38-gentoo
DISTRIB_ID="Gentoo"
Installation method / source:
source
Edited:
I noticed there is no static/ dir in the build directory after building gsa, but there is no static/ dir even in the packaged dist files.
The text was updated successfully, but these errors were encountered: