| The Following 2 Users Say Thank You to wolke For This Useful Post: | ||
|
|
2019-11-12
, 18:03
|
|
Posts: 804 |
Thanked: 1,586 times |
Joined on Aug 2014
|
#183
|
[/QUOTE| The Following User Says Thank You to aspergerguy For This Useful Post: | ||
|
|
2019-11-12
, 18:14
|
|
Posts: 7 |
Thanked: 23 times |
Joined on Aug 2018
|
#184
|
| The Following 3 Users Say Thank You to eugenio For This Useful Post: | ||
|
|
2019-11-15
, 09:48
|
|
Posts: 127 |
Thanked: 203 times |
Joined on Sep 2010
@ Switzerland
|
#185
|
| The Following User Says Thank You to maximilian1st For This Useful Post: | ||
|
|
2019-11-15
, 10:40
|
|
Posts: 127 |
Thanked: 203 times |
Joined on Sep 2010
@ Switzerland
|
#186
|
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:257:in `execute': Vagrant was unable to mount VirtualBox shared folders. This is usually (Vagrant::Errors::VirtualBoxMountFailed) because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was:
| The Following User Says Thank You to maximilian1st For This Useful Post: | ||
|
|
2019-11-15
, 10:56
|
|
Posts: 127 |
Thanked: 203 times |
Joined on Sep 2010
@ Switzerland
|
#187
|
$ vagrant ssh -c "/vagrant/patch.sh -a f5321 -i /vagrant/Sailfish*.zip"
W: You must be root to use this script! Trying with sudo...
I: Unzipping the Sailfish X archive
Archive: /vagrant/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15.zip
creating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/Jolla-3.2.0.12-f5121-armv7hl.urls
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/AdbWinUsbApi.dll
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/flash-on-windows.bat
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/fastboot.exe
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/flash.sh
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/md5.lst
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/hw-release
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/fastboot.img
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/hybris-boot.img
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/hybris-recovery.img
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/flashing-README.txt
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/AdbWinApi.dll
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/fimage.img001
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/os-release
I: Converting the fimage sparse image to a raw image...
I: Copying the fimage contents
'/tmp/sailfish-image-patcher/tmp.BwT0WHatci/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/home.img.gz' -> 'patcher-tmp/work/fimage/home.img.gz'
'/tmp/sailfish-image-patcher/tmp.BwT0WHatci/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/root.img.gz' -> 'patcher-tmp/work/fimage/root.img.gz'
I: Uncompressing the contents
I: Copying the Sailfish root contents...
I: Preparing for the patch...
I: Patching the image...
DBus unavailable, falling back to libssu
DBus unavailable, falling back to libssu
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 154 100 154 0 0 490 0 --:--:-- --:--:-- --:--:-- 503
100 858k 100 858k 0 0 1291k 0 --:--:-- --:--:-- --:--:-- 6452k
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 154 100 154 0 0 511 0 --:--:-- --:--:-- --:--:-- 525
100 449k 100 449k 0 0 727k 0 --:--:-- --:--:-- --:--:-- 727k
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 154 100 154 0 0 508 0 --:--:-- --:--:-- --:--:-- 522
100 1121k 100 1121k 0 0 1581k 0 --:--:-- --:--:-- --:--:-- 1581k
warning: ./augeas-libs.rpm: Header V3 DSA/SHA1 Signature, key ID f2633ee0: NOKEY
Preparing... ################################# [100%]
Updating / installing...
1:augeas-libs-1.6.0+git1-1.2.8.joll################################# [ 50%]
2:zypper-1.14.6+git3-1.3.8.jolla ################################# [100%]
Retrieving repository 'tmp-compat-f5321' metadata ................................................................................................................................................[done]
Building repository 'tmp-compat-f5321' cache .....................................................................................................................................................[done]
Specified repositories have been refreshed.
Retrieving repository 'jolla' metadata ...........................................................................................................................................................[done]
Building repository 'jolla' cache ................................................................................................................................................................[done]
Specified repositories have been refreshed.
Error building the cache:
[adaptation0|plugin:/ssu?repo=adaptation0] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation0' because of the above error.
Error building the cache:
[adaptation1|plugin:/ssu?repo=adaptation1] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation1' because of the above error.
Error building the cache:
[aliendalvik|plugin:/ssu?repo=aliendalvik] Valid metadata not found at specified URL
Warning: Skipping repository 'aliendalvik' because of the above error.
Building repository 'apps' cache .................................................................................................................................................................[done]
Building repository 'customer-jolla' cache .......................................................................................................................................................[done]
Building repository 'hotfixes' cache .............................................................................................................................................................[done]
Building repository 'jolla' cache ................................................................................................................................................................[done]
Error building the cache:
[sailfish-eas|plugin:/ssu?repo=sailfish-eas] Valid metadata not found at specified URL
Warning: Skipping repository 'sailfish-eas' because of the above error.
Building repository 'tmp-compat-f5321' cache .....................................................................................................................................................[done]
Error building the cache:
[xt9|plugin:/ssu?repo=xt9] Valid metadata not found at specified URL
Warning: Skipping repository 'xt9' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 18 NEW packages are going to be installed:
droid-compat-f5321-droid-config droid-compat-f5321-droid-config-flashing droid-compat-f5321-droid-config-sailfish droid-compat-f5321-droid-hal droid-compat-f5321-droid-system
droid-compat-f5321-feature droid-compat-f5321-hybris-libsensorfw-qt5 droid-devicetree-f5321 libpython3_7m1_0 python3-base rpm-divert sailfish-content-graphics-closed-z1.25
sailfish-content-graphics-default-z1.25-base sailfish-device-encryption-unlock-ui-resources-z1.25 sailfish-minui-resources-z1.25 sailfish-upgrade-ui-resources-logo-z1.25
sailfish-upgrade-ui-resources-z1.25 yabit
The following NEW pattern is going to be installed:
droid-compat-f5321
18 new packages to install.
| The Following User Says Thank You to maximilian1st For This Useful Post: | ||
|
|
2019-11-15
, 14:12
|
|
Posts: 986 |
Thanked: 1,526 times |
Joined on Jul 2010
|
#188
|
| The Following 3 Users Say Thank You to wolke For This Useful Post: | ||
|
|
2019-11-15
, 14:20
|
|
Posts: 986 |
Thanked: 1,526 times |
Joined on Jul 2010
|
#189
|
| The Following 3 Users Say Thank You to wolke For This Useful Post: | ||
|
|
2019-11-17
, 11:56
|
|
Posts: 127 |
Thanked: 203 times |
Joined on Sep 2010
@ Switzerland
|
#190
|
EDIT: i never did figure this one out. it was suddenly completely broken on freshly built 3.1 installs (despite working on 3.1 before), and stayed broken after updating to 3.2 with ssu. flashing 3 different times with slightly different procedures didnt fix it. also, once logged into jolla account in 3.1, it offered me the official upgrade to 3.2 (which it never did before....), and then THAT didnt fix it.
installing zip of 3.2 fixed it, no problem.
~ teleshoes ~