ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which
maintainers need to be pinged.
e.g:
`builtins.unsafeGetAttrPos "version" drv`
When using a `.json` file containing the version via `lib.importJSON`,
this will always return `null` and thus leading to no pings at all.
This commit works around this, resulting in properly working pings
for any changes to the upstream-info file.
A similar thing has been done for element-{web,desktop} in the past.
Previously when useChrome was set to false the command would be something like
```
makeWrapper [...] \
--add-flags "-cp [...]" \
--add-flags \
--add-flags "org.openqa.grid.selenium.GridLauncherV3"
```
The problem was that only the arguments to `--add-flags` was optional while for this to be parsed correctly the flag and argument has to be optional.
* chromedriver: add dbus to libraries
It is apparently required since version 94.
Fixes issue #139547
* chromedriver: remove extraneous LD_LIBRARY_PATH in wrapProgram
wrapProgram already prepends passed value to the specified environment
variable; no need to specify it explicitly.
* chromedriver: add a package test checking the reported version
* Update pkgs/development/tools/selenium/chromedriver/default.nix
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
* treewide: http -> https sources
This updates the source urls of all top-level packages from http to
https where possible.
* buildtorrent: fix url and tab -> spaces
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/chromedriver/versions.
These checks were done:
- built on NixOS
- /nix/store/b62dsg9dibywkpx8yzfm08dbcdfh9i60-chromedriver-2.40/bin/chromedriver passed the binary check.
- Warning: no invocation of /nix/store/b62dsg9dibywkpx8yzfm08dbcdfh9i60-chromedriver-2.40/bin/.chromedriver-wrapped had a zero exit code or showed the expected version
- 1 of 2 passed binary check by having a zero exit code.
- 0 of 2 passed binary check by having the new version present in output.
- found 2.40 with grep in /nix/store/b62dsg9dibywkpx8yzfm08dbcdfh9i60-chromedriver-2.40
- directory tree listing: https://gist.github.com/2beed7dbaa434f54d37a742a2c0e2662
- du listing: https://gist.github.com/8b1a61054a03382c346ba383ac79c163
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/chromedriver/versions.
These checks were done:
- built on NixOS
- /nix/store/r7ai8p033gdhncxsfjjy3rb8qmcsvpqx-chromedriver-2.39/bin/chromedriver passed the binary check.
- Warning: no invocation of /nix/store/r7ai8p033gdhncxsfjjy3rb8qmcsvpqx-chromedriver-2.39/bin/.chromedriver-wrapped had a zero exit code or showed the expected version
- 1 of 2 passed binary check by having a zero exit code.
- 0 of 2 passed binary check by having the new version present in output.
- found 2.39 with grep in /nix/store/r7ai8p033gdhncxsfjjy3rb8qmcsvpqx-chromedriver-2.39
- directory tree listing: https://gist.github.com/ed47d14dfe1661b73d2d877b6e790579
- du listing: https://gist.github.com/63dc7bb82190375bce025de50ed2d6fa
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/chromedriver/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/bnjr4qgd68lh8fdz2hxz7qrc1zvvxkni-chromedriver-2.38/bin/chromedriver -h’ got 0 exit code
- ran ‘/nix/store/bnjr4qgd68lh8fdz2hxz7qrc1zvvxkni-chromedriver-2.38/bin/chromedriver --help’ got 0 exit code
- found 2.38 with grep in /nix/store/bnjr4qgd68lh8fdz2hxz7qrc1zvvxkni-chromedriver-2.38
- directory tree listing: https://gist.github.com/8ba491f60826e1ad2389e69f92fb6116
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/chromedriver/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/z1h08azp3xdik94is0g2m2y5pvdfy4fc-chromedriver-2.37/bin/chromedriver -h` got 0 exit code
- ran `/nix/store/z1h08azp3xdik94is0g2m2y5pvdfy4fc-chromedriver-2.37/bin/chromedriver --help` got 0 exit code
- ran `/nix/store/z1h08azp3xdik94is0g2m2y5pvdfy4fc-chromedriver-2.37/bin/chromedriver -v` and found version 2.37
- ran `/nix/store/z1h08azp3xdik94is0g2m2y5pvdfy4fc-chromedriver-2.37/bin/chromedriver --version` and found version 2.37
- ran `/nix/store/z1h08azp3xdik94is0g2m2y5pvdfy4fc-chromedriver-2.37/bin/chromedriver -h` and found version 2.37
- ran `/nix/store/z1h08azp3xdik94is0g2m2y5pvdfy4fc-chromedriver-2.37/bin/chromedriver --help` and found version 2.37
- found 2.37 with grep in /nix/store/z1h08azp3xdik94is0g2m2y5pvdfy4fc-chromedriver-2.37
- directory tree listing: https://gist.github.com/d24f8e2019df676c89bb32d16ee980ed
