* format with nixpkgs-fmt
* reorder attributes
* inline version

It was crashing with:

    TypeError: gobject `__main__+ChromeGNOMEShell' doesn't support property `application_id'

– that is the constructor of parent class Gio.Application does not recognize the kwarg.

This is typically caused by missing pygobject overrides but I think ones for Gio are built-in into pygobject.

Even weirder, adding just `${gobject-introspection}/lib/girepository-1.0` seems to fix the issue so it might be missing the whole typelib.
But then why does not it fail when importing it?

	from gi.repository import GLib, Gio

For now, I am adding the Gio typelib which should been done from the start but more debugging should be done since weirdness like this can bring more bugs.

Fixes: NixOS/nixpkgs#87740

NoMachine removes each old release as soon as a new one is available,
resulting in failed downloads. Thankfully, the Internet Archive
provides backups of old downloads, so we can use it as a fallback.

There's no need to ship the pre-generated completions in the nixpkgs
tree anymore.

nomachine-client: Add archive.org to source urls

also switch away from dependency aliases and reorder the attributes a bit

https://ftp.gnome.org/pub/GNOME/sources/glade/3.36/glade-3.36.0.news

This partially reverts commit 3e0aa4a.

See the discussion in the PR.

firefox: 76.0 -> 76.0.1

gnome3.glade: 3.22.2 -> 3.36.0

This update was generated by hackage2nix v2.15.3-1-gb7c82db from Hackage revision
commercialhaskell/all-cabal-hashes@4c409c7.

…sion

Allow the darwin links code to overwrite libs that were already
copied, because C dependencies can occur multiple times.

Solves errors like

    ln: failed to create symbolic link '/nix/store/higpc9xavwcjjzdipz7m9ly03bh7iy2z-hercules-ci-agent-source-0.7.0/lib/links/libboost_context.dylib': File exists

ghcjs hasn't compiled for several weeks.

fly: 6.0.0 -> 6.1.0

Update Haskell package set to LTS 15.12 (plus other fixes)

This is a legacy version for OCaml 4.02

Based on some feedback in #87094 and discussion with @FRidh, this re-organizes
the onboarding tutorial in the Nixpkgs manual's python section, so that we start
with the simplest, most ad-hoc examples and work our way up. This progresses
from:

1. How to create an temporary python env at the cmdline, then
2. How to create a specific python env for a single script, then
3. How to create a specific python env for a project in a shell.nix, then
4. How to install a specific python env globally on the system or in a user profile.

Additionally, I've tried to standardize on some of the "best practice" ways of
doing things:

1. Instead of saying that this command style is "supported but strongly not
   discouraged", I've just deleted it to avoid confusion.

   Bad:  nix-shell -p python38Packages.numpy python38Packages.toolz
   Good: nix-shell -p 'python38.withPackages(ps: with ps; [ numpy toolz ])'

2. In the portion where we show how to add stuff to the user's
   `XDG_CONFIG_HOME`, use overlays instead of `config.nix`. The former can do
   everything the latter can do, but is also much more generic and powerful,
   because it can compose with other files, compose with other envs, compose
   with overlays that do things like swap whether tensorflow and pytorch are
   built openblas/mkl/cuda stacks, and so on. The user is eventually going to
   see the overlay, so to avoid confusion let's standardize on it.