Age | Commit message (Collapse) | Author | Files | Lines |
|
The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
bitlbee.pc requires glib, so all packages that depend on bitlbee will
also depend on glib.
|
|
|
|
Fixes: #73747
|
|
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/bitlbee/versions
|
|
He prefers to contribute to his own nixpkgs fork triton.
Since he is still marked as maintainer in many packages
this leaves the wrong impression he still maintains those.
|
|
|
|
Code coverage reports is not useful at all for users.
This is a feature for developer.
|
|
|
|
|
|
"platforms.gnu" has been linux-only since at least 17.03:
$ nix eval -f channel:nixos-17.03 lib.platforms.gnu
[ "i686-linux" "x86_64-linux" "armv5tel-linux" "armv6l-linux" "armv7l-linux" "aarch64-linux" "mips64el-linux" ]
Unlike platforms.linux, platforms.gnu indicates "must use glibc"
which for the most part is not intended.
Replacing platforms.gnu with platforms.linux would be the same "today"
but let's err on preserving existing behavior and be optimistic
about platforms these packages work on.
|
|
Homepage link "http://.../" is a permanent redirect to "https://.../" and should be updated
https://repology.org/repository/nix_stable/problems
|
|
|
|
Fixes:
* CVE-2016-10188
* CVE-2016-10189
* CVE-2017-5668
|
|
|
|
|
|
Previously it was written to /var/lib/bitlbee.pid but on
NixOS the user bitlbee has no write access to /var/lib/.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(My OCD kicked in today...)
Remove repeated package names, capitalize first word, remove trailing
periods and move overlong descriptions to longDescription.
I also simplified some descriptions as well, when they were particularly
long or technical, often based on Arch Linux' package descriptions.
I've tried to stay away from generated expressions (and I think I
succeeded).
Some specifics worth mentioning:
* cron, has "Vixie Cron" in its description. The "Vixie" part is not
mentioned anywhere else. I kept it in a parenthesis at the end of the
description.
* ctags description started with "Exuberant Ctags ...", and the
"exuberant" part is not mentioned elsewhere. Kept it in a parenthesis
at the end of description.
* nix has the description "The Nix Deployment System". Since that
doesn't really say much what it is/does (especially after removing
the package name!), I changed that to "Powerful package manager that
makes package management reliable and reproducible" (borrowed from
nixos.org).
* Tons of "GNU Foo, Foo is a [the important bits]" descriptions
is changed to just [the important bits]. If the package name doesn't
contain GNU I don't think it's needed to say it in the description
either.
|
|
|
|
|
|
svn path=/nixpkgs/trunk/; revision=27985
|
|
svn path=/nixpkgs/trunk/; revision=25419
|
|
svn path=/nixpkgs/trunk/; revision=24128
|
|
svn path=/nixpkgs/trunk/; revision=19162
|
|
svn path=/nixpkgs/trunk/; revision=14030
|
|
svn path=/nixpkgs/trunk/; revision=12258
|
|
svn path=/nixpkgs/trunk/; revision=11283
|
|
svn path=/nixpkgs/trunk/; revision=10715
|