summaryrefslogtreecommitdiffstats
path: root/pkgs/data/misc
AgeCommit message (Collapse)Author
2021-01-30osinfo-db: 20201119 -> 20201218R. RyanTM
2021-01-29all-cabal-hashes: update to Hackage at 2021-01-29T18:57:29ZPeter Simons
2021-01-25treewide: remove stdenv where not neededPavol Rusnak
2021-01-22all-cabal-hashes: update to Hackage at 2021-01-22T18:56:49ZPeter Simons
2021-01-17pkgs/data, pkgs/games: [sS]tdenv.*lib -> libBen Siraphob
2021-01-16pkgs/data: pkgconfig -> pkg-configBen Siraphob
2021-01-15Revert "Merge pull request #105709 from CajuM/symbiflow"Austin Seipp
This reverts commit 02828f91f15668ce6a757b6ef1d2d8430a403194, reversing changes made to f0a7fce6ee72e574c2406bf1cfd1741c8d2cd07e.
2021-01-15pkgs/data: stdenv.lib -> libBen Siraphob
2021-01-11Merge pull request #105709 from CajuM/symbiflowDmitry Kalinkin
Add Symbiflow + prjxray for OSS Xilinx FPGA development
2021-01-11treewide: with stdenv.lib; in meta -> with lib;Profpatsch
Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2021-01-10symbiflow-arch-defs: init at 20200914-111752-g05d68df0Câju Mihai-Drosi
2021-01-10prjxray-db: init at 0.0-0232-g303a61dCâju Mihai-Drosi
2021-01-09Merge master into staging-nextgithub-actions[bot]
2021-01-08all-cabal-hashes: update to Hackage at 2021-01-07T20:56:37ZPeter Simons
2021-01-01treewide: cmake buildInputs to nativeBuildInputs, minor cleanupsBen Siraphob
2020-12-29tzdata: 2020c -> 2020fajs124
2020-12-25all-cabal-hashes: update to Hackage at 2020-12-24T01:16:25ZPeter Simons
2020-12-19Merge master into staging-nextgithub-actions[bot]
2020-12-18all-cabal-hashes: update to Hackage at 2020-12-18T01:03:03ZPeter Simons
2020-12-17cacert: 3.57 -> 3.60ajs124
2020-12-13Merge pull request #106476 from r-ryantm/auto-update/osinfo-dbMario Rodas
osinfo-db: 20201015 -> 20201119
2020-12-09osinfo-db: 20201015 -> 20201119R. RyanTM
2020-12-08Merge staging-next into staginggithub-actions[bot]
2020-12-07fedora-backgrounds: use stdenvNoCC (#106149)Daniël de Kok
No need for a C build environment when copying some backgrounds.
2020-12-05Merge staging-next into staginggithub-actions[bot]
2020-12-05Merge master into staging-nextgithub-actions[bot]
2020-12-04all-cabal-hashes: update to Hackage at 2020-12-04T10:00:55ZPeter Simons
2020-12-01Merge pull request #105568 from lukegb/nixpkgs-cacert-blacklistAndreas Rammhold
cacert: fix certificate denylist
2020-12-01cacert: add lukegb as maintainerLuke Granger-Brown
2020-12-01cacert: add myself as maintainerAndreas Rammhold
2020-12-01cacert: remove broken includeEmail optionLuke Granger-Brown
This doesn't do anything. Building with includeEmail = true produces the same set as includeEmail = false, and the substitute rule removes a random dictionary index operation.
2020-12-01cacert: fix blacklistLuke Granger-Brown
It's broken under Python 3, ironically due to the patch we're carrying. Fix it, and add a test to check it works. Fixes #93230.
2020-12-01Merge staging-next into stagingFrederik Rietdijk
2020-12-01spdx-license-list-data: 3.10 -> 3.11R. RyanTM
2020-11-28Merge pull request #102638 from r-ryantm/auto-update/osinfo-dbMario Rodas
osinfo-db: 20200804 -> 20201015
2020-11-19Merge pull request #104083 from timokau/sage-maintainers-teamTimo Kaufmann
maintainers: create sage team
2020-11-19fedora-backgrounds.f33: init at 33.0.7Daniël de Kok
2020-11-18maintainers: create sage teamTimo Kaufmann
Maintaining all the packages whose updates might break some aspect of sage. For reference: https://github.com/NixOS/nixpkgs/pull/103810#issuecomment-727536510
2020-11-18cacert: decouple from NSS to reduce rebuild amountAndreas Rammhold
In [#100765] @vcunat pointed out that we could decouple cacert from the NSS package to make it more rebuild friendly. Just rebuilding packages that depend on NSS seems to be about ~100. Rebuilding all the packages that depend on cacert is >9k as of this writing. This makes it much more feasible to upgrade high-profile packages that are (rightfully) pedantic on their NSS version like firefox and thunderbird. [#100765]: https://github.com/NixOS/nixpkgs/pull/100765
2020-11-09Merge staging-next into stagingFrederik Rietdijk
2020-11-09Merge master into staging-nextFrederik Rietdijk
2020-11-06all-cabal-hashes: update to Hackage at 2020-11-06T01:07:40ZPeter Simons
2020-11-06tzdata: Revert to the "fat" "bloated" formatRobert Hensing
The timezone dumps have switched to a "slim" format since 2020b. This has broken various packages, including - go 1.4 (used for bootstrapping) - haskellPackages.tz - libical The "fat" format can still be generated, as this commit shows. It seems to create files that are *mostly* the slim versions with some more data attached.
2020-11-04poppler_data: 0.4.9 -> 0.4.10R. RyanTM
2020-11-03osinfo-db: 20200804 -> 20201015R. RyanTM
2020-10-26Recover the complicated situation after my bad mergeVladimír Čunát
I made a mistake merge. Reverting it in c778945806b undid the state on master, but now I realize it crippled the git merge mechanism. As the merge contained a mix of commits from `master..staging-next` and other commits from `staging-next..staging`, it got the `staging-next` branch into a state that was difficult to recover. I reconstructed the "desired" state of staging-next tree by: - checking out the last commit of the problematic range: 4effe769e2b - `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken merge commit and its revert from that range (while keeping reapplication from 4effe769e2) - merging the last unaffected staging-next commit (803ca85c209) - fortunately no other commits have been pushed to staging-next yet - applying a diff on staging-next to get it into that state
2020-10-26Re-Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"Vladimír Čunát
This reverts commit c778945806b44d46ec16bc4302e7e7163e6bab97. I believe this is exactly what brings the staging branch into the right shape after the last merge from master (through staging-next); otherwise part of staging changes would be lost (due to being already reachable from master but reverted).
2020-10-25Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"Vladimír Čunát
I'm sorry; I didn't notice it contained staging commits. This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
2020-10-25Merge #101508: libraw: 0.20.0 -> 0.20.2Vladimír Čunát
2020-10-23all-cabal-hashes: update to Hackage at 2020-10-22T01:32:08ZPeter Simons
generated by cgit v1.2.3 (git 2.25.1) at 2024-08-14 22:47:36 +0000