| Branch | Commit message | Author | Age |
|---|
| origin/staging-next | nixos/pam: enable lastlog2 import service if any pam service uses lastlog (#4... | K900 | 5 months |
| origin/master | blink-qt: init at 6.0.4 (#431321) | Ivan Mincik | 5 months |
| origin/backport-432323-to-release-25.05 | capnproto: fix fibers on static builds | Jade Lovelace | 5 months |
| origin/backport-424505-to-release-25.05 | julia_111: 1.11.5 -> 1.11.6 | Weijia Wang | 5 months |
| origin/staging | Merge staging-next into staging | nixpkgs-ci[bot] | 5 months |
| origin/nixos-unstable-small | nakama: 3.29.0 -> 3.30.0 (#432605) | nixpkgs-merge-bot[bot] | 5 months |
| origin/haskell-updates | Merge b1b0d690fbb0e4a2fa029ab625a3b1646487fee1 into haskell-updates | nixpkgs-ci[bot] | 5 months |
| origin/staging-25.05 | Merge staging-next-25.05 into staging-25.05 | nixpkgs-ci[bot] | 5 months |
| origin/staging-next-25.05 | Merge release-25.05 into staging-next-25.05 | nixpkgs-ci[bot] | 5 months |
| origin/backport-432577-to-release-25.05 | sydbox: 3.37.2 -> 3.37.6 | R. Ryantm | 5 months |
| [...] |
| |
| Tag | Download | Author | Age |
|---|
| 25.05 | nixpkgs-25.05.tar.gz | Leona Maroni | 8 months |
| 25.11-pre | nixpkgs-25.11-pre.tar.gz | Leona Maroni | 8 months |
| 25.05-beta | nixpkgs-25.05-beta.tar.gz | Leona Maroni | 8 months |
| 24.11 | nixpkgs-24.11.tar.gz | Martin Weinelt | 10 months |
| branch-off-24.11 | nixpkgs-branch-off-24.11.tar.gz | Tristan Ross | 14 months |
| 24.11-beta | nixpkgs-24.11-beta.tar.gz | Tristan Ross | 14 months |
| 24.05 | nixpkgs-24.05.tar.gz | Weijia Wang | 20 months |
| 24.11-pre | nixpkgs-24.11-pre.tar.gz | Weijia Wang | 20 months |
| 24.05-beta | nixpkgs-24.05-beta.tar.gz | Weijia Wang | 20 months |
| 23.11 | nixpkgs-23.11.tar.gz | figsoda | 2 years |
| [...] |
| |
| Age | Commit message | Author | Files | Lines |
|---|
| 2024-01-05 | ungoogled-chromium: 120.0.6099.129-1 -> 120.0.6099.199-1•••https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop.html
This update includes 6 security fixes.
CVEs:
CVE-2024-0222 CVE-2024-0223 CVE-2024-0224 CVE-2024-0225
(cherry picked from commit d163ea4133312f04ebf8eb4875ea4b61400b4b5e)
origin/backport-278603-to-release-23.11 | networkException | 1 | -5/+5 |
| 2024-01-05 | chromium: 120.0.6099.129 -> 120.0.6099.199•••https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop.html
This update includes 6 security fixes.
CVEs:
CVE-2024-0222 CVE-2024-0223 CVE-2024-0224 CVE-2024-0225
(cherry picked from commit 5c77fff6097b20c6d11d3dda15d51d25d3144b96)
| emilylange | 1 | -3/+3 |
| 2024-01-05 | chromium: improve and move `recompressTarball`•••Recap: We need that (arguably stupid) helper function/drv because the
chromium tarball is big -- and is likely to increase even more in the
future. So big, that we eventually exceeded hydra.nixos.org's
max-output-limit (3G). Instead of raising global hydra's limit, it was
decided that we recompress the tarball after deleting unused vendored
files from it.
I spent a lot of time on a version/prototype that does everything
(downloading, decompression, tar extraction, deleting unused files,
reproducible tar recreation and finally recompression) via stdin but
eventually had to scratch that.
GNU tar does not allow to create a tarball just from stdin, nixpkgs'
stdenv isn't built with stdin/stdout/pipes in mind, and things a lot of
other things I probably already forgot.
Nonetheless, this version improves multiple things:
- No more `mv` (used to be multiple, not just ours, since fetchzip had
some as well)
- No more `rm` to get rid of the extracted files before recompressing.
Instead, we simply don't extract them in the first place (thanks to
tar's --exlude).
- No more "no space left" that happened due to `downloadToTemp = true;`.
- Multithreaded xz decompression, since that commit is still in
staging-next.
We cannot use stdenv's unpackFile() because that does not allow us to
specify the needed --exclude (and --strip-components=1 if we don't want
to rely on glob matching).
The hash changed because we now have a static base directory ("source")
in the tarball, instead of whatever upstream provided us with (e.g.
"chromium-120.0.6099.129").
(cherry picked from commit e15783154fb13819d8a149e5df0a0d3412e73f97)
| emilylange | 5 | -40/+51 |
| 2024-01-05 | Merge pull request #278743 from NixOS/backport-278656-to-release-23.11•••[Backport release-23.11] jujutsu: 0.12.0 -> 0.13.0 | Nick Cao | 1 | -3/+3 |
| 2024-01-05 | Merge pull request #278764 from NixOS/backport-278422-to-release-23.11•••[Backport release-23.11] dataexplorer: 3.8.0 -> 3.8.3 | Nick Cao | 1 | -2/+2 |
| 2024-01-05 | Merge pull request #278716 from NixOS/backport-278686-to-release-23.11•••[Backport release-23.11] fastnetmon-advanced: 2.0.356 -> 2.0.357 | Nick Cao | 1 | -2/+2 |
| 2024-01-05 | Merge pull request #278942 from NixOS/backport-275459-to-release-23.11•••[Backport release-23.11] chromium: drop inactive maintainers, CODEOWNERS: init chromium | Emily | 3 | -17/+11 |
| 2024-01-05 | chromium: remove maintainer handles from README.md, mention electron•••Specifically the maintainers section is quite outdated and prone to get
out of sync with whatever primary data we have (mostly meta.maintainers)
in each derivation.
In an attempt to lower the risk of ending up out of sync again, we
simply remove the maintainer handles.
Also adds a mention for the newly from source built electron variant, as
almost everything except `upstream-info.nix` bumps will trigger electron
rebuilds as well.
And lastly, removes mentions of `chromium{Beta,Dev}` and the
accompanying `google-chrome-{beta,dev}, that have been removed a few
months ago.
I might look into reworking bigger parts of the README.md in the future,
but this honestly isn't that high of a priority for me for now.
(cherry picked from commit cdf5db87d48a1264b9ce68cb1755fe696a9e6713)
| emilylange | 1 | -15/+7 |
| 2024-01-05 | CODEOWNERS: init chromium•••(cherry picked from commit ff1380cb3a936bc84d04059ca842af957f3ab513)
| emilylange | 1 | -0/+2 |
| 2024-01-05 | chromium: drop inactive maintainers•••Our ./maintainers/README.md has a section titled "How to lose maintainer
status", which describes an "inactivity measure":
Maintainers how haven't reacted to "package-related notifications" for
more than 3 months can be removed.
All those 4 maintainers that are getting dropped as part of this commit
haven't responded to any such notifications (mostly review pings) for at
least 3 months.
(cherry picked from commit 477e7d6b60e817661632ff3a8aaf2e39c4cceadc)
| emilylange | 1 | -2/+2 |
| [...] |
| |
| Clone |
|---|
| https://cgit.wugi.info/git/nixos/nixpkgs |
