The list of upstream changes is huge, so I'm not pasting it here in the
commit message, but here is the upstream URL:
https://dev.gajim.org/gajim/gajim/blob/gajim-1.1.2/ChangeLog
One of the most visible updates are the design changes for various
dialogs and the Emoji overhauls.
On our end, we now need three more dependencies, namely cssutils,
precis-i18n and keyring, which I added accordingly.
In addition, the test runner is now integrated into setup.py, which we
now use.
I also cleaned up the package expression a bit, eg. it's no longer
wrapped in a big "with lib;", so that "nix-instantiate --parse" is able
to detect attribute errors (which is very useful if you have editor
integration).
Signed-off-by: aszlig <aszlig@nix.build>
This package is required since Gajim version 1.1.0 and I intentionally
didn't set meta.maintainers because I'm not going to be able to maintain
this package, except if Gajim requires a newer version.
Signed-off-by: aszlig <aszlig@nix.build>
Just a small bugfix release, but required for Gajim 1.1.2.
Upstream fixes:
* Always bind after SM failed
* Dont try and guess system language
Signed-off-by: aszlig <aszlig@nix.build>
Closes: https://github.com/NixOS/nixpkgs/pull/54081
This PR is committed using the new version.
The never version requires JRE 10, actually the changelog mentions
downgrading from JDK11 to 10 because of a bug related to https
but this seams to be fixed by now
https://bugs.openjdk.java.net/browse/JDK-8210005
Also I did not find a `jre` output in jdk11, so the closure size
might increase due to it.
This should make the composability of kernel configurations more straigthforward.
- now distinguish freeform options from tristate ones
- will look for a structured config in kernelPatches too
one can now access the structuredConfig from a kernel via linux_test.configfile.structuredConfig
in order to reinject it into another kernel, no need to rewrite the config from scratch
The following merge strategies are used in case of conflict:
-- freeform items must be equal or they conflict (mergeEqualOption)
-- for tristate (y/m/n) entries, I use the mergeAnswer strategy which takes the best available value, "best" being defined by the user (by default "y" > "m" > "n", e.g. if one entry is both marked "y" and "n", "y" wins)
-- if one item is both marked optional/mandatory, mandatory wins (mergeFalseByDefault)
This behavior ended up breaking the handleEvalIssue functionality by hiding those packages. So something like this:
$ nix-env -iA nixpkgs.zoom-us
would silently fail, without telling the user how to fix it! Regardless, this "bug" should be handled in Nix - not Nixpkgs.
Fixes #38952.
