Skip to content

Conversation

@Kreyren
Copy link

@Kreyren Kreyren commented Feb 6, 2019

Signed-off-by: Jacob Hrbek [email protected]

Jacob Hrbek added 2 commits February 6, 2019 17:07
- Added stub for wine-4.0-staging which depends on winepak/winepak-sdk#37
- Added stub for adobeair which depends on tps://github.com/winepak/winepak-sdk/pull/38
- Fixed typo on line 105 and 196

Signed-off-by: Jacob Hrbek <[email protected]>
@Kreyren
Copy link
Author

Kreyren commented Feb 6, 2019

TESTING

Results in

kreyren@dreamon:~/GIT/applications/com.leagueoflegends.Client$ flatpak-builder --user --arch=x86_64 --force-clean --install builds com.leagueoflegends.Client.yml
Can't parse 'com.leagueoflegends.Client.yml': 111:20: did not find expected '-' indicator
kreyren@dreamon:~/GIT/applications/com.leagueoflegends.Client$ flatpak-builder --user --arch=x86_64 --force-clean --install builds com.leagueoflegends.Client.yml
Can't parse 'com.leagueoflegends.Client.yml': 202:20: did not find expected '-' indicator
kreyren@dreamon:~/GIT/applications/com.leagueoflegends.Client$ flatpak-builder --user --arch=x86_64 --force-clean --install builds com.leagueoflegends.Client.yml

(flatpak-builder:22847): flatpak-builder-WARNING **: 17:17:43.564: 5:18: '3.0' will be parsed as a number by many YAML parsers

(flatpak-builder:22847): flatpak-builder-WARNING **: 17:17:43.564: 18:14: '3.0' will be parsed as a number by many YAML parsers

(flatpak-builder:22847): flatpak-builder-WARNING **: 17:17:43.564: 38:14: '3.0' will be parsed as a number by many YAML parsers
error: org.winepak.Sdk/x86_64/3.0 not installed
Failed to init: Unable to find sdk org.winepak.Sdk version 3.0

Removed problematic comment -> Fixes Can't parse ...


kreyren@dreamon:~/GIT/applications/com.leagueoflegends.Client$ flatpak-builder --user --arch=x86_64 --force-clean --install builds com.leagueoflegends.Client.yml

(flatpak-builder:22970): flatpak-builder-WARNING **: 17:21:09.466: 5:18: '3.0' will be parsed as a number by many YAML parsers

(flatpak-builder:22970): flatpak-builder-WARNING **: 17:21:09.466: 18:14: '3.0' will be parsed as a number by many YAML parsers

(flatpak-builder:22970): flatpak-builder-WARNING **: 17:21:09.466: 38:14: '3.0' will be parsed as a number by many YAML parsers
error: org.winepak.Sdk/x86_64/3.0 not installed
Failed to init: Unable to find sdk org.winepak.Sdk version 3.0

Conslusion: I need org.winepak.Sdk/x86_64/3.0 which depends on org.freedesktop.Sdk/i386/1.6

Current roadblock:
image

removed /var/libs/flatpak/*

Fixed solution by reconfiguring primary processing unit based on variables that ware parsed corrupted.


flatpak-builder --arch=x86_64 --force-clean builds --repo=winepak com.leagueoflegends.Client.yml -> Command 'flatpak-builder' not found, but can be installed...

apti flatpak-builder

flatpak-builder --arch=x86_64 --force-clean builds --repo=winepak com.leagueoflegends.Client.yml -> error: org.winepak.Sdk/x86_64/3.0 not installed

flatpak --user install winepak org.winepak.Sdk/x86_64/3.0 Looking for matches… error: Unable to load summary from remote winepak: Remote listing for winepak not available; server has no summary file. Check the URL passed to remote-add was valid.

flatpak remote-add --if-not-exists winepak https://dl.winepak.org/repo/winepak.flatpakrepo

same issue

Conclusion flatpak remote-add --if-not-exists winepak https://dl.winepak.org/repo/winepak.flatpakrepo results in error: Unable to load summary from remote winepak: Remote listing for winepak not available; server has no summary file. Check the URL passed to remote-add was valid.

flatpak --user remote-add --no-gpg-verify --if-not-exists winepak winepak-repo from https://github.com/winepak/winepak-sdk-images#new-repo seems to work. (results in no output)

flatpak --user install winepak org.winepak.Sdk/x86_64/3.0 ->
error: Unable to load summary from remote winepak: Remote listing for winepak not available; server has no summary file. Check the URL passed to remote-add was valid.

I gave up

@Kreyren
Copy link
Author

Kreyren commented Feb 6, 2019

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 this pull request may close these issues.

1 participant