Hey Maxim, I'm trying to build package for ubuntu by command: make -f extras/packaging/gnu-linux/Makefile ubuntu_22.04 But I receive following error: command -v guix > /dev/null 2>&1 || \ (echo 'guix' is required to build the 'has-guix-p' target && exit 1) output=$(guix pack -C xz -f deb -m /home/ubuntu/jami-client-qt/extras/packaging/gnu-linux/guix/guix-pack-manifest.scm -v3 -S /usr/bin/jami=bin/jami -S /usr/share/applications/jami.desktop=share/applications/jami.desktop -S /usr/share/icons/hicolor/scalable/apps/jami.svg=share/icons/hicolor/scalable/apps/jami.svg -S /usr/share/icons/hicolor/48x48/apps/jami.png=share/icons/hicolor/48x48/apps/jami.png -S /usr/share/metainfo/jami.appdata.xml=share/metainfo/jami.appdata.xml --postinst-file=/home/ubuntu/jami-client-qt/extras/packaging/gnu-linux/guix/guix-pack-deb.postinst --system=x86_64-linux ) && mkdir -p "$(dirname "extras/packaging/gnu-linux/packages/guix-deb-pack/jami-20230727.0-x86_64.deb")" && cp --reflink=auto "$output" "extras/packaging/gnu-linux/packages/guix-deb-pack/jami-20230727.0-x86_64.deb" && guix gc --delete "$output" guix pack: error: postinst-file=/home/ubuntu/jami-client-qt/extras/packaging/gnu-linux/guix/guix-pack-deb.postinst: unrecognized option make: *** [extras/packaging/gnu-linux/Makefile:273: extras/packaging/gnu-linux/packages/guix-deb-pack/jami-20230727.0-x86_64.deb] Error 1
Do you know any issues with that flag? The file exists so I think it might be something wrong with that flag. When I try to build package by command: make -f extras/packaging/gnu-linux/Makefile debian_12 I receive other error: /jami/work/daemon/contrib/src/gnutls/rules.mak:15: *** Trying to download https://www.gnupg.org/ftp/gcrypt/gnutls/v3.7/gnutls-3.7.6.tar.xz but DISABLE_CONTRIB_DOWNLOADS is TRUE, aborting.. Stop. make[2]: Leaving directory '/jami/work/daemon/contrib/native' make[1]: *** [debian/rules:63: override_dh_auto_build] Error 2 make[1]: Leaving directory '/jami/work' make: *** [debian/rules:56: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Do you have any idea how to move forward with those? I have already updated guix, but nothing changes. What is the command you use to build packages by docker? On Thu, Aug 10, 2023 at 4:37 PM Maxim Cournoyer < maxim.courno...@savoirfairelinux.com> wrote: > Hi, > > ----- Original Message ----- > > From: "Johnny Markiewicz" <joh...@sonicwebdev.com> > > To: "Maxim Cournoyer" <maxim.courno...@savoirfairelinux.com> > > Cc: "jami" <jami@gnu.org> > > Sent: Thursday, August 10, 2023 3:32:50 AM > > Subject: Re: jami client > > > Hey Maxim, > > Thank you for the quick answer, it helped a lot to move forward. > > Do you know is it possible to create a deb package from build? I want to > > run this build on another computer. > > This is something routinely done by the CI packaging pipeline, and > everything is available for review in the jami repository, more > specifically under the extras/packaging/gnu-linux directory. The packaging > can be accomplished via Docker or GNU Guix; when using Guix all the > external dependencies used are that of the currently installed Guix, which > makes it very efficient but has the downside of requiring these to be up to > date in Guix (otherwise you may have build failures, i.e. because the > current opendht package in Guix is slightly older than the one in the Jami > contribs. Other packaging targets build everything from the daemon contrib > system (bundled), which is much slower (it will build a full Qt > distribution, including qtwebengine -- better have 32 GiB of RAM) but > matches what most Jami developpers would test. > > Example, from the root of the jami project: > > ``` > make -f extras/packaging/gnu-linux/Makefile debian_12 > ``` > > Will leave you a bunch of .deb packages in the > 'extras/packaging/gnu-linux/packages' output directory. > > ``` > make -f extras/packaging/gnu-linux/Makefile deb-pack-x86-64 > ``` > > Would use 'guix pack -f deb' to produce a self-contained Jami Debian > package that includes the whole distribution (very disk-heavy but > portable). If you have Guix installed on your machines it'd be more > efficient to simply 'guix install jami'. We could setup a Guix channel to > distribute the latest Jami (to be done, but it should be relatively > straightforward by adding a directory and a file to the jami repository). > > I hope that helps, > > Maxim >
