Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/telepathy-gabble/versions.
These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 0.18.4 with grep in /nix/store/pg936ixgiw96xqsrdzbwc1civylmy1q5-telepathy-gabble-0.18.4
- found 0.18.4 in filename of file in /nix/store/pg936ixgiw96xqsrdzbwc1civylmy1q5-telepathy-gabble-0.18.4
- directory tree listing: https://gist.github.com/92190024cdfe17a3e79730f988d904f6
This is for systems that are not using a full desktop environment, so
Gajim can fall back to the default icon theme of Gnome 3.
Among just fixing aesthetics this also fixes a few exceptions that were
triggered by Gajim not finding the icons. One example of this is when
you enter the plugins dialog, the window is empty if the icons can't be
found.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @abbradar, @Mic92, @7c6f434c
Just because the tests need GTK+, I think it's not a good idea to simply
disable them when we're still able to use an X virtual framebuffer to
run them anyway.
As with the package we had prior to version 1.0 I've disabled the
resolver test, because this one requires networking.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @abbradar, @Mic92, @7c6f434c
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 1.23.2 with grep in /nix/store/r7pl30mgdnrdig95aq6qy3d4dbvy8vji-pidgin-sipe-1.23.2
- directory tree listing: https://gist.github.com/c400423782c0ab85deea92ca910a179b
Semi-automatic update. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 0.5.8 with grep in /nix/store/v1xv4aj5wq1mw5mdml2hwh4qd5bfdcim-baresip-0.5.8
- found 0.5.8 in filename of file in /nix/store/v1xv4aj5wq1mw5mdml2hwh4qd5bfdcim-baresip-0.5.8
Semi-automatic update. These checks were performed:
- built on NixOS
- found 1.2.235 with grep in /nix/store/9z3lbwjmcvgxpicxnkqsqyn2bmkyqvsw-psi-plus-1.2.235
cc "@orivej"
Semi-automatic update. These checks were performed:
- built on NixOS
- found 0.8 with grep in /nix/store/di49z3ic9sk7mrg6rhf0c67qk8pda3kg-pidgin-xmpp-receipts-0.8
- found 0.8 in filename of file in /nix/store/di49z3ic9sk7mrg6rhf0c67qk8pda3kg-pidgin-xmpp-receipts-0.8
cc "@orivej"
The patches do no longer apply on-top of the pjsip version we provice.
One of the maintainers (@Radvendii @olynch) should have a look what can
be done about this.
The build has been failing since 2017-07-31…
Upstream changes:
* Improve Zeroconf behavior
* Fix showing normal message event
* remove usage of OpenSSL.rand
* a few minor bugfixes
The really important part here is the third point about OpenSSL.rand,
because the rand attribute no longer exists in pyopenssl and thus Gajim
doesn't even start.
Also the fix-tests.patch has been fixed upstream as well, so we don't
need it anymore.
Another change in 0.16.9 that's not included in the changelog is that
there is a test_nogui target, which is also run by the CI upstream is
using, so let's use that and remove xvfb_run.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @7c6f434c, @Mic92
Telegram was crashing when executed within a pure environment
(nix-shell -p tdesktop --pure).
Setting the environment variables QT_PLUGIN_PATH and XDG_RUNTIME_DIR
should resolve this issue. Fix#33729.
Few things:
* Discord binary has RUNPATH not RPATH set
* patchelf uses RUNPATH if it already exits, so deps end up in RUNPATH
* RUNPATH isn't searched for plugins or transitive deps
* ..badness results
Despite this, it currently seems to work-- with the caveat
that it has a little bar on top complaining about how
"it looks like your installation is corrupt".
This fixes that warning and does some minor cleanup.
SASL is required to connect to Freenode on high-abuse networks, e.g. highly
NATed networks or Tor. However, Pidgin only supports PLAIN authorization type,
and Freenode specifically prohibits using anything other than EXTERNAL or
ECDSA-NIST256P-CHALLENGE over Tor. It still allows PLAIN for potentially
problematic clearnet networks, though.
Signal is a bit like google-chrome, wherein the beta version
is independent from the release builds and uses different data
locations and binary names.
