Комментарии (0)
Нет комментариев. Ваш будет первым!
Problem: nothing provides kf5bluezqt-bluez4 needed by droid-config-device-bluez4-1-1.armv7hl Solution 1: Following actions will be done: deinstallation of bluez-configs-mer-4.101+git73-1.31.1.armv7hl deinstallation of bluez-4.101+git73-1.31.1.armv7hl deinstallation of connman-1.30+git20-1.31.1.armv7hl deinstallation of connman-configs-mer-1.30+git20-1.31.1.armv7hl deinstallation of connman-qt5-1.0.98-1.32.1.armv7hl deinstallation of ssu-network-proxy-plugin-0.42.0-1.35.2.armv7hl deinstallation of ssu-0.42.0-1.35.2.armv7hl deinstallation of sdk-register-0.5-10.1.11.jolla.armv7hl deinstallation of qt5-qtsysteminfo-5.2.0+git8-1.7.1.armv7hl deinstallation of qt5-qtdeclarative-systeminfo-5.2.0+git8-1.7.1.armv7hl deinstallation of ssu-vendor-data-jolla-0.95-10.32.2.jolla.noarch Solution 2: keep obsolete bluez-configs-mer-4.101+git73-1.31.1.armv7hl Solution 3: break droid-config-device-bluez4-1-1.armv7hl by ignoring some of its dependencies
sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper ar http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfish_latest_armv7hl/ sfl sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper up
sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper re mesa-llvmpipe sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper rm mesa-llvmpipe
Нет комментариев. Ваш будет первым!