jami-packaging issueshttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues2021-12-29T17:18:40Zhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/92Add raspbian (armhf/arm64) packages2021-12-29T17:18:40ZAmin BandaliAdd raspbian (armhf/arm64) packagesWe do not provide a raspbian package anymore due to complications with cross-building our Qt package (`libqt-jami`), now used for building both the client library (`lrc`) and the Qt client (`jami-qt`). Since `lrc` is also built using `l...We do not provide a raspbian package anymore due to complications with cross-building our Qt package (`libqt-jami`), now used for building both the client library (`lrc`) and the Qt client (`jami-qt`). Since `lrc` is also built using `libqt-jami`, we cannot continue providing a `jami-gnome` raspbian package either.Backloghttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/66Create Raspbian container2020-10-22T22:48:38ZFredy PulidoCreate Raspbian containerWe started building Raspbian from Debian ARM containers and all was working but now we got some dependencies broken:
```
The following packages have unmet dependencies:
jami : Depends: libwebkit2gtk-4.0-37 (>= 2.26.3-1~deb10u1) but 2.2...We started building Raspbian from Debian ARM containers and all was working but now we got some dependencies broken:
```
The following packages have unmet dependencies:
jami : Depends: libwebkit2gtk-4.0-37 (>= 2.26.3-1~deb10u1) but 2.26.2-1~deb10+1+rpi1 is to be installed
E: Unable to correct problems, you have held broken packages.
```
We did an investigation and we found this build dependency declaration:
```
libwebkit2gtk-4.0-dev | libwebkit2gtk-3.0-dev,
```
Until there all is OK but debian and raspbian versions aren't the same:
From debian machine
``` apt show libwebkit2gtk-4.0-dev| grep -i version
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Version: 2.26.3-1~deb10u1
This build comes from the GTK port of WebKit (API version 4.0).
```
From Raspberry machine:
```
pi@raspberrypi:~ $ apt show libwebkit2gtk-4.0-dev| grep -i version
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Version: 2.26.2-1~deb10+1+rpi1
This build comes from the GTK port of WebKit (API version 4.0).
```
We can fix it and avoid any future problem by creating a Raspbian image for Docker (there are not any official one and community images does not provide Dockerfiles then we can not reuse their work).
This links could be be useful:
* https://www.raspberrypi.org/forums/viewtopic.php?t=234715
* https://github.com/wokis/raspberrypi/blob/master/rpi-debootstrap.sh
* https://docs.docker.com/develop/develop-images/baseimages
* https://downloads.raspberrypi.org/raspbian/
This new Dockerile must replace the actual one for raspbianhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/62Do not bundle ffmpeg for raspbian2022-02-01T20:56:13ZFredy PulidoDo not bundle ffmpeg for raspbianBecause Raspbian's is customized for that Hardware.Because Raspbian's is customized for that Hardware.Fredy PulidoFredy Pulidohttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/53Remove dirty qemu-static hack2020-10-22T22:56:00ZFredy PulidoRemove dirty qemu-static hackAs soon as https://git.jami.net/savoirfairelinux/jami-packaging/issues/52 got resolved read the [ARM page](https://git.jami.net/savoirfairelinux/jami-packaging/wikis/ARM) and check if after the update we can run this command without prob...As soon as https://git.jami.net/savoirfairelinux/jami-packaging/issues/52 got resolved read the [ARM page](https://git.jami.net/savoirfairelinux/jami-packaging/wikis/ARM) and check if after the update we can run this command without problems:
```
docker run --rm -ti arm64v8/debian uname -a
```
If thes then remove the dirty qemu-static hack documented in the [ARM page](https://git.jami.net/savoirfairelinux/jami-packaging/wikis/ARM).