These have been submitted upstream,
but seconds before writing this message
so naturally no upstream response "yet" :).
Regardless of response, fetch patches
from the corresponding PR's for context
and of course hopefully they'll
be included in next version.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/xonsh/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/yp41kipqmmsjl0ldi4b16z2590shv9dp-xonsh-0.6.8/bin/xon.sh had a zero exit code or showed the expected version
- /nix/store/yp41kipqmmsjl0ldi4b16z2590shv9dp-xonsh-0.6.8/bin/.xonsh-wrapped passed the binary check.
- /nix/store/yp41kipqmmsjl0ldi4b16z2590shv9dp-xonsh-0.6.8/bin/xonsh passed the binary check.
- 2 of 3 passed binary check by having a zero exit code.
- 2 of 3 passed binary check by having the new version present in output.
- found 0.6.8 with grep in /nix/store/yp41kipqmmsjl0ldi4b16z2590shv9dp-xonsh-0.6.8
- directory tree listing: https://gist.github.com/e53ad25422aa303572f4452029cb65b3
- du listing: https://gist.github.com/0c29b7c27c01e8d34986163ba00f1615
The `.service` file defining the `systemd` unit for `autorandr.service`
which is bundled with the package itself uses `--default default` in the
`ExecStart` section. This can be an issue when having multiple layouts
(e.g. `default` as workstation layout I mostly work on and `mobile` when
I go somewhere else).
When the service gets restarted and `--default` can't be applied,
however the current layout can't be detected (e.g. when working with an
unknown beamer) the service silently fails with a message like this:
```
Jun 22 18:44:46 hauptshuhle autorandr[3168]: /nix/store/h83b72ffm68nm8fyjnppljchp456a94r-xrandr-1.5.0/bin/xrandr: ca>
Jun 22 18:44:46 hauptshuhle autorandr[3168]: Failed to apply profile 'default' (line 718):
Jun 22 18:44:46 hauptshuhle autorandr[3168]: Command failed: /nix/store/h83b72ffm68nm8fyjnppljchp456a94r-xrandr-1.>
```
As discussed in the IRC (see https://botbot.me/freenode/nixos/2018-07-05/?msg=101791455&page=6)
it's a bad long-term solution in terms of maintenance to manually patch
the service file bundled with the derivation, instead the service shall
be configured declaratively. Additionally this makes possible overrides
from the user-space way easier.
The `udev` rule (in `$out/etc/udev/rules.d`) won't' be affected, it
simply runs `systemctl start autorandr.service` when e.g. a new display
is added, so now `udev` communicates with the NixOS systemd unit.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/conan/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/c92p18la19jbr7ya0ml77gn6z9c9zagn-conan-1.5.1/bin/.conan_server-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/c92p18la19jbr7ya0ml77gn6z9c9zagn-conan-1.5.1/bin/conan_server had a zero exit code or showed the expected version
- /nix/store/c92p18la19jbr7ya0ml77gn6z9c9zagn-conan-1.5.1/bin/.conan_build_info-wrapped passed the binary check.
- /nix/store/c92p18la19jbr7ya0ml77gn6z9c9zagn-conan-1.5.1/bin/conan_build_info passed the binary check.
- Warning: no invocation of /nix/store/c92p18la19jbr7ya0ml77gn6z9c9zagn-conan-1.5.1/bin/.conan-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/c92p18la19jbr7ya0ml77gn6z9c9zagn-conan-1.5.1/bin/conan had a zero exit code or showed the expected version
- 2 of 6 passed binary check by having a zero exit code.
- 0 of 6 passed binary check by having the new version present in output.
- found 1.5.1 with grep in /nix/store/c92p18la19jbr7ya0ml77gn6z9c9zagn-conan-1.5.1
- directory tree listing: https://gist.github.com/097b90f575be6117eceec5c70235c405
- du listing: https://gist.github.com/54f8f4a3882e828289ab5b96dd0fa338
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/graphicsmagick/versions.
These checks were done:
- built on NixOS
- /nix/store/kws698xdnjfrl70gi5gvp4f90i00w35p-graphicsmagick-1.3.30/bin/gm passed the binary check.
- /nix/store/kws698xdnjfrl70gi5gvp4f90i00w35p-graphicsmagick-1.3.30/bin/GraphicsMagick++-config passed the binary check.
- /nix/store/kws698xdnjfrl70gi5gvp4f90i00w35p-graphicsmagick-1.3.30/bin/GraphicsMagick-config passed the binary check.
- /nix/store/kws698xdnjfrl70gi5gvp4f90i00w35p-graphicsmagick-1.3.30/bin/GraphicsMagickWand-config passed the binary check.
- 4 of 4 passed binary check by having a zero exit code.
- 3 of 4 passed binary check by having the new version present in output.
- found 1.3.30 with grep in /nix/store/kws698xdnjfrl70gi5gvp4f90i00w35p-graphicsmagick-1.3.30
- directory tree listing: https://gist.github.com/e51d94d9d1da3d8ccfb7359a7d6e7655
- du listing: https://gist.github.com/e1a40fb5a980660ff689d25e98d20d18
