New Phosh image - first impressions

[Seferi]

---

sudo apk add telegram-desktop
[sudo] password for demo:
ERROR: unsatisfiable constraints:
 icu-libs-65.1-r0:
   conflicts: icu-libs-66.1-r0
   satisfies: world[icu-libs] world[so:libicudata.so.65]
              world[so:libicui18n.so.65] world[so:libicuio.so.65]
              world[so:libicutest.so.65] world[so:libicutu.so.65]
              world[so:libicuuc.so.65] firefox-74.0-r0[so:libicui18n.so.65]
              firefox-74.0-r0[so:libicuuc.so.65]
              mozjs68-68.6.0-r0[so:libicui18n.so.65]
              mozjs68-68.6.0-r0[so:libicuuc.so.65]
              evolution-data-server-3.36.0-r1[so:libicui18n.so.65]
              evolution-data-server-3.36.0-r1[so:libicuuc.so.65]
              mozjs60-60.9.0-r2[so:libicui18n.so.65]
              mozjs60-60.9.0-r2[so:libicuuc.so.65]
              libical-3.0.8-r0[so:libicui18n.so.65]
              libical-3.0.8-r0[so:libicuuc.so.65]
              webkit2gtk-2.28.0-r0[so:libicui18n.so.65]
              webkit2gtk-2.28.0-r0[so:libicuuc.so.65]
              nuspell-3.0.0-r3[so:libicuuc.so.65]
              harfbuzz-icu-2.6.4-r1[so:libicuuc.so.65]
              enchant2-2.2.8-r0[so:libicuuc.so.65]
              vte3-0.60.0-r0[so:libicuuc.so.65]
 icu-libs-66.1-r0:
   conflicts: icu-libs-65.1-r0
   satisfies: world[icu-libs] qt5-qtbase-9999-r0[so:libicui18n.so.66]
              qt5-qtbase-9999-r0[so:libicuuc.so.66]
pine64-pinephone:~$

Seems like qt5-qtbase is built against a newer version of libicu then the other packages in that list, causing conflicts. That is strange, since the packages depending on the older versions come from Alpine directly and were rebuilt against the newer libicu before our Qt5 package.

I guess run an "apk update && apk upgrade -a" and try again.

So the March 16 release can be just 'updated'  and be 'current'  ?

Yes. The images you use are just snapshots of a specific time of the edge branch. You can always just update to the newest packages rather than reflashing.

Very strange that I'm the only one with the problem. I flashed the latest image (March 16) with jumpdrive again just to make sure. Still getting the same error...