zim: 0.74.2 -> 0.74.3

[DeeUnderscore]

Description of changes

Changelog: https://github.com/zim-desktop-wiki/zim-desktop-wiki/blob/0.74.3/CHANGELOG.md#0743---tue-07-dec-2021

This also fixes problems with the build failing due to missing gobject-interospection. See #56943 (comment) for issue and other packages affected by this. Resolves #186451.

Also, stop double-wrapping bin/zim.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.11 Release Notes (or backporting 22.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[vojta001]

Result of nixpkgs-review pr 186657 run on x86_64-linux 1

1 package built:

• zim

[layus]

This seems to fail for me with an

Traceback (most recent call last):
  [...]
    assert Gtk
AssertionError

Gtk is not found.

Fixed by disabling dontWrapGApps. Might submit a PR at some point.

It seems that makeWrapperArgs+=("''${gappsWrapperArgs[@]}") is not completely equivalent to wrapGAppsHook effect.

[layus]

What I do not get is what changed in the meantime. Because the version that this PR pushed works too. So some dependency must have changed somewhere. Sorry for the fuss here. This deserves a new issue.