Package Details: jicofo-bin 1.0+1066-1

Git Clone URL: (read-only, click to copy)
Package Base: jicofo-bin
Description: JItsi meet COnference FOcus binary
Upstream URL:
Licenses: Apache
Conflicts: jicofo
Provides: jicofo
Submitter: quartic
Maintainer: celogeek
Last Packager: celogeek
Votes: 8
Popularity: 0.000036
First Submitted: 2020-03-14 16:02 (UTC)
Last Updated: 2024-02-13 10:00 (UTC)

Dependencies (5)

Required by (2)

Sources (6)

Latest Comments

1 2 Next › Last »

celogeek commented on 2020-08-08 18:19 (UTC)

Interesting. Do you have any warning when you try to reinstall the package?

Jicofo tries to change the permissions on his config files. JVB try not.

Both contain passwords.

I set the right so jicofo can read but cannot change anything of the config you provide. The warning is just a warning that indicates he cannot do what he wants with the configuration.

If you want to allow jicofo to change your files, I guess an override should work. Maybe you will have a warning when you upgrade.

danieltetraquark commented on 2020-08-07 18:58 (UTC) (edited on 2020-08-07 19:00 (UTC) by danieltetraquark)

I had to add


to the systemd service. , otherwise jicofo would complain about missing write permissions.

celogeek commented on 2020-07-30 17:12 (UTC)


We make the nightly and the stable look alike. The config path now for jicofo is /etc/jicofo (more like arch path)

danieltetraquark commented on 2020-07-29 20:07 (UTC)

@C0rn3j, would you mind updating? Version 1.0-612 is available.

danieltetraquark commented on 2020-06-24 19:34 (UTC)

Version 1.0-589 is available.

celogeek commented on 2020-05-27 01:01 (UTC)

I understand the point. The checksum part is important.

All these steps can be done easily with a shell script that updates the PKGBUILD based on official stable tags. And then the maintainer can try the update then push it back.

danieltetraquark commented on 2020-05-21 12:07 (UTC) (edited on 2020-05-21 12:10 (UTC) by danieltetraquark)

@celogeek I understand what you want to do. The issue is, it is against how PKGBUILDs are intented to be used.

  1. Downloading stuff in build()

    (I'm citing from PKGBUILDs man page)

    The optional ''build()'' function is use to compile and/or adjust the source files in preparation to be installed by the package() function.

    So ''build'' should never download sources, especially if it is the main source. The checksum can't be checked, because it isn't in the ''PKGBUILD''. This could lead to malicious software beeing installed (because of network spoofing or whatever).

  2. A maintainer for a AUR package should at least check, when updating the ''PKGBUILD'', that everything still compiles.

    The maintainer can just do a makepkg and if anything changes in the PKGBUILD, just commit and push for anyone to get a new version.

    Using your PKGBUILD, everyone always gets the latest version (when installing initially) (because makepkg runs pkgver, and AUR helpers run makepkg).

  3. Autoupdating should only be done by -git packages, as AUR helpers recognize them and handle them properly.

  4. For the AUR maintainer, @quartic, all they have to do is: adjust pkgver and _debver, update the checksums (there is a command for that, updpksums), update the .SRCINFO file (use alias updtsrcinfo='makepkg --printsrcinfo > .SRCINFO' if you want).

To conclude: Don't do autoupdates in packages which arent -git, don't fetch sources in build (since it checksum isnt checked; if the build programm itself does it, this is something else).

EDIT: hopefully fix markdown syntax

celogeek commented on 2020-05-21 11:45 (UTC)

The goal is to be able to do an automatic updates. We can't do that by putting the debian package in the source with a static version.

If anyone takes this package and installs it, it will update automatically to the latest version. It can do that regularly if needed.

The maintainer can just do a makepkg and if anything changes in the PKGBUILD, just commit and push for anyone to get a new version.

The goal is to stay up to date, without any complication of looking for debian install and see what is installs.

debian version is late compared to the latest stable tag on jitsi-meet and his deps.

danieltetraquark commented on 2020-05-20 10:51 (UTC) (edited on 2020-05-20 10:54 (UTC) by danieltetraquark)

@celogeek the issue is, this will break the checksums with future releases. Also, most AUR helpers won't update it, since it doesn't end with -git (correct me if I'm wrong here). Also the deb file should be in the "source", so that makepkg can download it and not in the "build" part.

celogeek commented on 2020-05-20 10:36 (UTC)

I have update the PKGBUILD in order to automatically fetch the latest release version and update the pkgver accordingly.


pkgdesc="JItsi Meet COnference FOcus"


pkgver() {
  curl --silent "$_pkgname/releases/latest" | jq -r .name | tr '-' '+'

build() {
  curl -L "${_pkgname}_${pkgver//+/-}-${pkgrel}_all.deb" -o jicofo.deb

package() {
  cd "${srcdir}"
  ar p "jicofo.deb" data.tar.xz | tar xJv -C "${pkgdir}"

  rm -r "${pkgdir}/etc/init.d"
  rm -r "${pkgdir}/etc/logrotate.d"
  rm -r "${pkgdir}/usr/share/doc"
  chmod 0750 "${pkgdir}/etc/jitsi/jicofo"

  sed -i 's/-Xmx[^ ]*//' "${pkgdir}/usr/share/jicofo/"

  install -Dm644 "${_pkgname}.service" "${pkgdir}/usr/lib/systemd/system/${_pkgname}.service"
  install -Dm644 'sysusers.conf' "${pkgdir}/usr/lib/sysusers.d/${_pkgname}.conf"
  install -Dm644 'tmpfiles.conf' "${pkgdir}/usr/lib/tmpfiles.d/${_pkgname}.conf"
  install -Dm644 'config' "${pkgdir}/etc/jitsi/jicofo/config"
  install -Dm644 '' "${pkgdir}/etc/jitsi/jicofo/"

# vim: set ts=2 sw=2 et: