This adds a best-effort hack to run AppImages, which currently don't
work out-of-the-box on NixOS. This is not preferable to using packaged
applications, but may help users if the application they want to run
is not in nixpkgs.
It uses the package list from the Steam chroot, but without Steam
packages.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pacman/versions.
These checks were done:
- built on NixOS
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/repo-add passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/makepkg passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman-db-upgrade passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman-key passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pkgdelta passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/repo-elephant passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/repo-remove passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/vercmp passed the binary check.
- Warning: no invocation of /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/testpkg had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/cleanupdelta had a zero exit code or showed the expected version
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman-conf passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/makepkg-template passed the binary check.
- 11 of 13 passed binary check by having a zero exit code.
- 0 of 13 passed binary check by having the new version present in output.
- found 5.1.0 with grep in /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0
- directory tree listing: https://gist.github.com/61f365ecd9146adf48fc68403568904d
- du listing: https://gist.github.com/391d88c911aeda73c0cd89f80ced8ce2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/packagekit/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkcon -h’ got 0 exit code
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkcon --help’ got 0 exit code
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkmon -h’ got 0 exit code
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkmon --help’ got 0 exit code
- found 1.1.10 with grep in /nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10
- directory tree listing: https://gist.github.com/1d641323594032d2e935bd1e088bf409
The isSeccomputable flag treated Linux without seccomp as just a
normal variant, when it really should be treated as a special case
incurring complexity debt to support.
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt -h` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt --help` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt help` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt version` and found version 1.3.0
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newtmgr -h` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newtmgr --help` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newtmgr help` got 0 exit code
- found 1.3.0 with grep in /nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin
- found 1.3.0 in filename of file in /nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin
cc "@pjones @ehmry @lethalman"
This reverts commit 695027f61c.
We really can't have "nix-env -i nix" *not* upgrade nixUnstable to a
newer nixStable. For instance, it would cause "nix upgrade-nix" to
produce a user environment with collisions.
as discussed in bed3695848
Different names make it easier for the users to notice updates to Nix stable,
and to have Nix stable and unstable simultaneously.
This reverts commit bed3695848.
This commit effectively makes it impossible to upgrade to nixUnstable
with nix-env without mucking about with priorities, as you can't
uninstall the old nix transactionally with the new nix and if you
uninstall the old one first you no longer have nix at your disposal to
install the new one.
This reverts commit 9711aac642.
One should depend on
- `stdenv.cc.bintools`: for executables at build time
- `libbfd` or `libiberty`: for those libraries
- `targetPackages.cc.bintools`: for exectuables at *run* time
- `binutils`: only for specifically GNU Binutils's executables, regardless of
the host platform, at run time.
Main change: glibc: 2.25-x -> 2.26-y, containing security fixes,
and various features and deprecations. Unfortunately, some of the
latter still cause (transitively) a couple hundred newly failing jobs.
I'm not delaying anymore, so that we have the security fix on master.
I mainly patched gcc, llvm and icu, but I can't fix everything...
The biggest benefit is that we no longer have to update the registry
package. This means that just about any cargo package can be built by
nix. No longer does `cargo update` need to be feared because it will
update to packages newer then what is available in nixpkgs.
Instead of fetching the cargo registry this bundles all the source code
into a "vendor/" folder.
This also uses the new --frozen and --locked flags which is nice.
Currently cargo-vendor only provides binaries for Linux and
macOS 64-bit. This can be solved by building it for the other
architectures and uploading it somewhere (like the NixOS cache).
This also has the downside that it requires a change to everyone's deps
hash. And if the old one is used because it was cached it will fail to
build as it will attempt to use the old version. For this reason the
attribute has been renamed to `cargoSha256`.
Authors:
* Kevin Cox <kevincox@kevincox.ca>
* Jörg Thalheim <Mic92@users.noreply.github.com>
* zimbatm <zimbatm@zimbatm.com>
* pgadmin: use https homepage
* msn-pecan: move homepage to github
google code is now unavailable
* pidgin-latex: use https for homepage
* pidgin-opensteamworks: use github for homepage
google code is unavailable
* putty: use https for homepage
* ponylang: use https for homepage
* picolisp: use https for homepage
* phonon: use https for homepage
* pugixml: use https for homepage
* pioneer: use https for homepage
* packer: use https for homepage
* pokerth: usee https for homepage
* procps-ng: use https for homepage
* pycaml: use https for homepage
* proot: move homepage to .github.io
* pius: use https for homepage
* pdfread: use https for homepage
* postgresql: use https for homepage
* ponysay: move homepage to new site
* prometheus: use https for homepage
* powerdns: use https for homepage
* pm-utils: use https for homepage
* patchelf: move homepage to https
* tesseract: move homepage to github
* quodlibet: move homepage from google code
* jbrout: move homepage from google code
* eiskaltdcpp: move homepage to github
* nodejs: use https to homepage
* nix: use https for homepage
* pdf2djvu: move homepage from google code
* game-music-emu: move homepage from google code
* vacuum: move homepae from google code
* pkgs: refactor needless quoting of homepage meta attribute
A lot of packages are needlessly quoting the homepage meta attribute
(about 1400, 22%), this commit refactors all of those instances.
* pkgs: Fixing some links that were wrongfully unquoted in the previous
commit
* Fixed some instances
The configure script calls nix-instantiate, which fails if /nix/var
doesn't exist (e.g. in a sandbox). This caused a bogus Nix::Config
module to be generated, causing issues in Hydra.
The key distinction I'm drawing is that there's a component that deals
with the store of the machine being built, and another component for
the store building it. The inner part of it assumes nothing from the
builder (doesn't need chroot or root powers) so it can run comfortably
inside a Nix build, as well as nixos-rebuild. I have some upcoming work
that will use that to significantly speed up and streamline image builds
for NixOS, especially on virtualized hosts like EC2, but it's also a
reasonable speedup on native hosts.
This script is not needed anymore since "nix-prefetch-url --unpack
<url>" and "nix-prefetch-url -A foo.src" (where "foo.src" is a
fetchzip / fetchFromGitHub call) work fine.
