Installing from a flatpakref does not handle --arch properly #406

Open
mattdangerw opened this Issue Nov 19, 2016 · 0 comments

Projects

None yet

1 participant

@mattdangerw
Contributor
mattdangerw commented Nov 19, 2016 edited

If you have an installation of a app or runtime for your default arch, and try to install for another arch with
flatpak install --user --arch archThatIsNotInstalled --from my.flatpakref
you will see.
error: App [appid], branch [branch] is already installed

Instead we should install the ref for the new arch.

@mattdangerw mattdangerw added a commit to endlessm/flatpak-bundler that referenced this issue Nov 19, 2016
@mattdangerw mattdangerw Fix auto-install for non default arch
We were only properly auto installing for the default flatpak
arch. This fixes up the logic here. Unfortunately this is somewhat
blocked on a bug in flatpak
flatpak/flatpak#406
54a157d
@mattdangerw mattdangerw added a commit to mattdangerw/atom that referenced this issue Nov 21, 2016
@mattdangerw mattdangerw 🐧 Add Flatpak support
This commit adds preliminary support for building an Atom Flatpak
application, which should runnable on any linux distribution with
Flatpak support. See http://flatpak.org/getting.html

The build script here will download an electron "base application"
which contains all the linux library dependencies (gtk, libnotify)
and combines them with the atom application binary and resources
to form the output flatpak.

The flatpak can be created by running
$ ./script/build --create-flatpak
and will create a single file flatpak bundle in the out directory

For gpg signing of the flatpak bundle, two environment variables
ATOM_LINUX_FLATPAK_GPG_KEY_ID and ATOM_LINUX_FLATPAK_GPG_HOME_DIR
can be set.

The script requires flatpak > 0.6.13 to be installed on the
system. Easy cross compiling will be a broken until
flatpak/flatpak#406
is resolved.

Issue for the feature: atom#11837
def055c
@mattdangerw mattdangerw added a commit to mattdangerw/atom that referenced this issue Nov 21, 2016
@mattdangerw mattdangerw 🐧 Add Flatpak support
This commit adds preliminary support for building an Atom Flatpak
application, which should runnable on any linux distribution with
Flatpak support. See http://flatpak.org/getting.html

The build script here will download an electron "base application"
which contains all the linux library dependencies (gtk, libnotify)
and combines them with the atom application binary and resources
to form the output flatpak.

The flatpak can be created by running
$ ./script/build --create-flatpak
and will create a single file flatpak bundle in the out directory

For gpg signing of the flatpak bundle, two environment variables
ATOM_LINUX_FLATPAK_GPG_KEY_ID and ATOM_LINUX_FLATPAK_GPG_HOME_DIR
can be set.

The script requires flatpak > 0.6.13 to be installed on the
system. Easy cross compiling will be a broken until
flatpak/flatpak#406
is resolved.

Issue for the feature: atom#11837
0c1ef9c
@mattdangerw mattdangerw added a commit to mattdangerw/atom that referenced this issue Nov 21, 2016
@mattdangerw mattdangerw 🐧 Add Flatpak support
This commit adds preliminary support for building an Atom Flatpak
application, which should runnable on any linux distribution with
Flatpak support. See http://flatpak.org/getting.html

The build script here will download an electron "base application"
which contains all the linux library dependencies (gtk, libnotify)
and combines them with the atom application binary and resources
to form the output flatpak.

The flatpak can be created by running
$ ./script/build --create-flatpak
and will create a single file flatpak bundle in the out directory

For gpg signing of the flatpak bundle, two environment variables
ATOM_LINUX_FLATPAK_GPG_KEY_ID and ATOM_LINUX_FLATPAK_GPG_HOME_DIR
can be set.

The script requires flatpak > 0.6.13 to be installed on the
system. Easy cross compiling will be a broken until
flatpak/flatpak#406
is resolved.

Issue for the feature: atom#11837
e54494f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment