-
-
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
armbian-desktop
package is severely inconsistent across arch/appgroups/config_base
#5439
Comments
Jira ticket: AR-1796 |
For completeness:
|
Yes. "armbian-desktop-$DE-$ARCH" should be either with all groups or with no groups, so something that is fixed. Idea is that this package, when installed from minimal image, provides desktop. Also regarding configs, if we don't use them, perhaps removing them? |
Yes, we could remove appgroups and configs, but still, ARCH differences would still occur... I'm testing making this package ARCH-specific, since nothing practical would change (package name is the same), and would allow us to "get by" as long as the targets.yaml used for repo-publishing does not have different appgroups/configs across all targets. |
AFAIK configs are always the same - at least for our internal needs. If someone else uses this, can't tell. Lets discuss this problem later on meeting. |
Yes. Configs are always the same. ( Unfortunately, the
So if we have a "fixed"/common armbian-desktop package (same for all appgroups) we'd be in trouble, we'd miss at least those:
So we'd need to move those to image creation or something. Similarly, the
|
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see #5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
…on variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted) - this has been tested with complete/default targets and works
…ggregation variant, where arch/config/appgroups are ignored; see armbian#5439 (re-submitted)" This reverts commit 70c5a5c.
What happened?
Ok so here's an old impasse. Hold on to your hat.
config/optional/architectures/amd64/_config/desktop/_all_distributions/appgroups/browsers/packages
This adds
google-chrome-stable
(with an extra apt-source) toAGGREGATED_PACKAGES_DESKTOP_COMMA
.But only if:
So it is not included for any arm64, ever, nor if APPGROUPS does not include "browsers".
All good.
Unfortunately, the
armbian-desktop
deb is then inconsistent:armbian-jammy-desktop-gnome
Architecture: all
AGGREGATED_PACKAGES_DESKTOP_COMMA
(only for the amd64+browsers case, that includesgoogle-chrome-stable
)So it's actually impossible to conciliate desktop aggregation (release+arch+appgroups+config_base+...) with a "single package", arch-independent, "armbian-desktop" package that is only per-
RELEASE
+DESKTOP_ENVIROMENT
.It gets worse if we consider
AGGREGATED_DESKTOP_POSTINST
andAGGREGATED_DESKTOP_CREATE_DESKTOP_PACKAGE
which are also included in that package.Some possibilities:
AGGREGATED_PACKAGES_DESKTOP_SANS_APPGROUPS_SANS_CONFIG_BASE_COMMA
and use that in the package Recommends.How to reproduce?
"Simple" way to reproduce:
./compile.sh 'BETA=yes' 'BOARD=uefi-arm64' 'BRANCH=current' 'BUILD_DESKTOP=yes' 'BUILD_MINIMAL=no' 'DESKTOP_APPGROUPS_SELECTED=browsers' 'DESKTOP_ENVIRONMENT=gnome' 'DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base' 'RELEASE=jammy' ARTIFACT_IGNORE_CACHE=yes
./compile.sh 'BETA=yes' 'BOARD=uefi-x86' 'BRANCH=current' 'BUILD_DESKTOP=yes' 'BUILD_MINIMAL=no' 'DESKTOP_APPGROUPS_SELECTED=browsers' 'DESKTOP_ENVIRONMENT=gnome' 'DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base' 'RELEASE=jammy' ARTIFACT_IGNORE_CACHE=yes
./compile.sh 'BETA=yes' 'BOARD=uefi-x86' 'BRANCH=current' 'BUILD_DESKTOP=yes' 'BUILD_MINIMAL=no' 'DESKTOP_APPGROUPS_SELECTED=none' 'DESKTOP_ENVIRONMENT=gnome' 'DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base' 'RELEASE=jammy' ARTIFACT_IGNORE_CACHE=yes
Each of these 3 builds produces a different
armbian-jammy-desktop-gnome
.Branch
main (main development branch)
On which host OS are you observing this problem?
Jammy
Relevant log URL
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: