about summary refs log tree commit diff
path: root/pkgs/applications/networking
AgeCommit message (Collapse)AuthorFilesLines
2024-05-03Merge pull request #307836 from jopejoe1/openasar/split-outArtturin2-53/+1
openasar: unstable-2023-10-24 -> 0-unstable-2024-01-13, move out of discord, adpot, update script
2024-05-03Merge #306080: staging-next 2024-04-22Vladimír Čunát77-312/+388
2024-05-03Merge pull request #308605 from r-ryantm/auto-update/yorNick Cao1-2/+2
yor: 0.1.192 -> 0.1.193
2024-05-03Merge pull request #308670 from r-ryantm/auto-update/kubeoneNick Cao1-3/+3
kubeone: 1.7.3 -> 1.7.4
2024-05-03Merge pull request #308694 from r-ryantm/auto-update/trayscaleNick Cao1-3/+3
trayscale: 0.11.2 -> 0.12.0
2024-05-03Merge pull request #308626 from r-ryantm/auto-update/kubesharkNick Cao1-2/+2
kubeshark: 52.2.39 -> 52.3.0
2024-05-03Merge pull request #308633 from r-ryantm/auto-update/atmosNick Cao1-3/+3
atmos: 1.70.0 -> 1.71.0
2024-05-03Merge pull request #308383 from emilylange/split-chromium-google-chromeJon Seager1-34/+14
google-chrome: move independently of `chromium`, add jnsgruk as maintainer, remove leftover `google-chrome-{beta,dev}` code paths
2024-05-03Merge master into staging-nextgithub-actions[bot]2-4/+4
2024-05-03Merge pull request #308591 from r-ryantm/auto-update/discordPol Dellaiera1-2/+2
discord: 0.0.51 -> 0.0.52
2024-05-03Merge pull request #308685 from r-ryantm/auto-update/kubecolorWeijia Wang1-2/+2
kubecolor: 0.3.1 -> 0.3.2
2024-05-03Merge master into staging-nextgithub-actions[bot]1-2/+2
2024-05-03trayscale: 0.11.2 -> 0.12.0R. Ryantm1-3/+3
2024-05-03kubecolor: 0.3.1 -> 0.3.2R. Ryantm1-2/+2
2024-05-03kubeone: 1.7.3 -> 1.7.4R. Ryantm1-3/+3
2024-05-02Merge pull request #308532 from NickCao/telegram-desktopNick Cao1-2/+2
telegram-desktop: 4.16.8 -> 5.0.0
2024-05-03Merge master into staging-nextgithub-actions[bot]2-86/+3
2024-05-02atmos: 1.70.0 -> 1.71.0R. Ryantm1-3/+3
2024-05-02kubeshark: 52.2.39 -> 52.3.0R. Ryantm1-2/+2
2024-05-02yor: 0.1.192 -> 0.1.193R. Ryantm1-2/+2
2024-05-02Merge pull request #308544 from r-ryantm/auto-update/sternWeijia Wang1-3/+3
stern: 1.28.0 -> 1.29.0
2024-05-02discord: 0.0.51 -> 0.0.52R. Ryantm1-2/+2
2024-05-02Merge pull request #308587 from toastal/meli-xxxMatthias Beyer1-83/+0
meli: add mirrors fetching tarballs
2024-05-03meli: mv to by-nametoastal1-83/+0
2024-05-02Merge master into staging-nextgithub-actions[bot]1-4/+4
2024-05-02stern: 1.28.0 -> 1.29.0R. Ryantm1-3/+3
2024-05-02telegram-desktop: 4.16.8 -> 5.0.0Nick Cao1-2/+2
Diff: https://github.com/telegramdesktop/tdesktop/compare/v4.16.8...v5.0.0 Changelog: https://github.com/telegramdesktop/tdesktop/releases/tag/v5.0.0
2024-05-02Merge pull request #295941 from NickCao/opentofuNick Cao1-4/+4
opentofu: 1.6.2 -> 1.7.0
2024-05-02Merge master into staging-nextgithub-actions[bot]2-2/+36
2024-05-02Merge pull request #301933 from aos/aos/helm-mapkubeapisSandro2-2/+36
2024-05-02Merge branch 'master' into staging-nextVladimír Čunát6-11/+11
2024-05-02Merge pull request #307645 from r-ryantm/auto-update/dropbox-cliéclairevoyant1-2/+2
dropbox-cli: 2023.09.06 -> 2024.04.17
2024-05-02Merge pull request #308358 from emilylange/chromiumEmily2-5/+5
chromium: 124.0.6367.91 -> 124.0.6367.118, lower version range of `--ozone-platform-hint` patch
2024-05-02chromium: lower version range of `--ozone-platform-hint` patchemilylange1-2/+2
Ref: fb10ea41b2a080cb4ecac34aa12cf056d8d3f90e We had to apply this patch from M125 to M124 because at the time, chromium hasn't backported this to M124 yet. Until now! Or at least somewhat. 124.0.6367.118 shipped and has an equivalent patch now, which means that this patch is no longer needed. (Ignoring the fact that it no longer applies because of this anyway) At least on chromium. The thing is, ungoogled-chromium hasn't caught up with chromium yet, meaning it is still on < .118 and thus still needs that patch.
2024-05-02Merge pull request #308277 from bobby285271/upd/homepageBobby Rong2-2/+2
treewide: Move away from wiki.gnome.org (part 2)
2024-05-01kubernetes-helm-mapkubeapis: init at 0.4.1Aos Dabbagh2-2/+36
Was looking for this plugin, but couldn't find it. I found this open PR: NixOS#217530 but it seems to have gone stale (no activity in over a year). I posted in it but figured everyone is too busy so I just decided to resubmit, addressing comments :-)
2024-05-02google-chrome: add jnsgruk as maintaineremilylange1-1/+1
They signaled interest in issue 306010.
2024-05-01google-chrome: move independently of `chromium`emilylange1-15/+9
Historically, `google-chrome` used the version info and debian package FOD provided by `chromium`. This was very efficient, because `chromium` uses parts of the debian tarball for Widevine (opt-in, via `.override`). Meaning `chromium` has to track that debian tarball with each update anyway. And they always release in sync. So why keep seperate `google-chrome` from `chromium` now? - The current `chromium` maintainers are already at capacity maintaining `chromium` and have no time for `google-chrome`. - `chromium` bumps become sometimes a bottleneck for `google-chrome`. This is because `chromium` is built from source and a lot more time consuming and significantly more complex. - Lately, `chromium` and `google-chrome` both had an upstream issue under wayland with `--ozone-platform-hint`, rendering it unusable. For `chromium` we were able to patch it, since unlike `google-chrome` it's built from source. The `chromium` maintainers simply forgot that `google-chrome` might have the same issue, continued to merge the PR, rendering `google-chrome` broken. This PR also removes primeos from `meta.maintainers` since they only added themself to `google-chrome` because it inherited `chromium`'s version, stating they don't actually use `google-chrome`. Furthermore, primeos no longer maintains `chromium`. Ref 477e7d6b60e817661632ff3a8aaf2e39c4cceadc
2024-05-01google-chrome: remove leftover `google-chrome-{beta,dev}` code pathsemilylange1-19/+5
Those are leftovers from when `google-chrome-{beta,dev}` were removed due to lack of maintenance in 59719f787e94f39e64e9086d08eaedd8a9e61b22.
2024-05-01chromium: 124.0.6367.91 -> 124.0.6367.118emilylange1-3/+3
https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_30.html This update includes 2 security fixes. CVEs: CVE-2024-4331 CVE-2024-4368
2024-05-01Merge pull request #307976 from michaeladler/updates/freerdpPol Dellaiera1-2/+2
freerdp: 2.11.5 -> 2.11.7
2024-05-01Merge master into staging-nextgithub-actions[bot]5-24/+24
2024-05-01Merge pull request #308274 from r-ryantm/auto-update/signal-desktop-betaJörg Thalheim1-2/+2
signal-desktop-beta: 7.6.0-beta.3 -> 7.7.0-beta.1
2024-05-01Merge pull request #308209 from r-ryantm/auto-update/temporalNick Cao1-3/+3
temporal: 1.23.0 -> 1.23.1
2024-05-01Merge pull request #307697 from r-ryantm/auto-update/knOTABI Tomoya1-2/+2
kn: 1.13.0 -> 1.14.0
2024-05-01signal-desktop-beta: 7.6.0-beta.3 -> 7.7.0-beta.1R. Ryantm1-2/+2
2024-05-01Merge pull request #307188 from JohnRTitor/anydeskAleksana2-17/+17
treewide: migrate some packages to finalAttrs, also reference lib explicitly in meta
2024-05-01Merge master into staging-nextgithub-actions[bot]3-8/+7
2024-05-01Merge pull request #307705 from eclairevoyant/hamsket-fixAtemu1-2/+1
hamsket: remove unneeded symlink
2024-05-01Merge pull request #307832 from felschr/tor-browser-fontconfig-fixéclairevoyant2-6/+6
{tor,mullvad}-browser: fix font config patch
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-02 18:43:14 +0000