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.
xfsprogs started using icu in bff5d1a4e8df8a23957e5739850754991ad2b9c8, part of v4.16.0
xfsprogs-4.15.0-docdir.patch is needed to avoid cyclic references in the outputs.
./glibc-2.27.patch is no longer necessary as it was included in xfsprogs 8041435de7ed028a27ecca64302945ad455c69a6
Introduce an extent-layer (as opposed to the existing file-level) deduplication
system for btrfs. This provides a means of finding similarities within
non-identical files, when they contain identical, aligned blocks.
This has been not touched in 6 years. Let's remove it to cause less
problems when adding new cross-compiling infrastructure.
This also simplify gcc significantly.
Fixes compilation on non-glibc at minor cost since these are only
used to guard the use of pragmas selectively disabling warnings
based on the GCC version used.
Since years I'm not maintaining anything of the list below other
than some updates when I needed them for some reason. Other people
is doing that maintenance on my behalf so I better take me out but
for very few packages. Finally!
This makes the command ‘nix-env -qa -f. --arg config '{skipAliases =
true;}'’ work in Nixpkgs.
Misc...
- qtikz: use libsForQt5.callPackage
This ensures we get the right poppler.
- rewrites:
docbook5_xsl -> docbook_xsl_ns
docbook_xml_xslt -> docbook_xsl
diffpdf: fixup
Bold marked applicable changelog entries:
- Support extended attributes (xattr) in forward mode<Paste>
- Add -fsck function
- Fix several symlink race attacks
- Use memory pools for buffer handling
- Parallelize file content encryption
- Use HKDF to derive separate keys for GCM and EME
* treewide: http -> https sources
This updates the source urls of all top-level packages from http to
https where possible.
* buildtorrent: fix url and tab -> spaces
This swaps the fetchgit call to be more consistent with the majority of other
NixPkgs fetchgit calls. Moreover, almost every network will be able to do HTTPS,
while some enterprise networks may limit external SSH access.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/e2fsprogs/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/chattr had a zero exit code or showed the expected version
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/lsattr passed the binary check.
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/compile_et had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/mk_cmds had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/badblocks had a zero exit code or showed the expected version
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/debugfs passed the binary check.
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/dumpe2fs passed the binary check.
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/e2freefrag had a zero exit code or showed the expected version
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/e2fsck passed the binary check.
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/e2image had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/e2label had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/e2undo had a zero exit code or showed the expected version
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/e4crypt passed the binary check.
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/e4defrag had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/filefrag had a zero exit code or showed the expected version
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/fsck.ext2 passed the binary check.
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/fsck.ext3 passed the binary check.
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/fsck.ext4 passed the binary check.
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/logsave had a zero exit code or showed the expected version
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/mke2fs passed the binary check.
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/mkfs.ext2 passed the binary check.
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/mkfs.ext3 passed the binary check.
- /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/mkfs.ext4 passed the binary check.
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/mklost+found had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/resize2fs had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin/bin/tune2fs had a zero exit code or showed the expected version
- 12 of 26 passed binary check by having a zero exit code.
- 0 of 26 passed binary check by having the new version present in output.
- found 1.44.2 with grep in /nix/store/3c5r4b2a5cb6cpwr73ahrr03v965hhbg-e2fsprogs-1.44.2-bin
- directory tree listing: https://gist.github.com/78b13b077d5f9da29fc2b256af44e638
- du listing: https://gist.github.com/356acc8c1a54a78ab93172cac717d3d5
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/duperemove/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/mcgis270lv4waah1f68insh0n8j7ja52-duperemove-0.11/bin/btrfs-extent-same had a zero exit code or showed the expected version
- /nix/store/mcgis270lv4waah1f68insh0n8j7ja52-duperemove-0.11/bin/duperemove passed the binary check.
- /nix/store/mcgis270lv4waah1f68insh0n8j7ja52-duperemove-0.11/bin/hashstats passed the binary check.
- /nix/store/mcgis270lv4waah1f68insh0n8j7ja52-duperemove-0.11/bin/show-shared-extents passed the binary check.
- 2 of 4 passed binary check by having a zero exit code.
- 2 of 4 passed binary check by having the new version present in output.
- found 0.11 with grep in /nix/store/mcgis270lv4waah1f68insh0n8j7ja52-duperemove-0.11
- directory tree listing: https://gist.github.com/0df1e551a8c77ca4dd4bb8f2783f75c4
- du listing: https://gist.github.com/4dc88fc1b6adba1caf3a67e67383c3c9
Without these patches, the output of mksquashfs is not reproducible.
The patches are taken from https://github.com/squashfskit/squashfskit,
a fork of squashfs-tools, licensed under the GPL2 or later like
squashfs-tools itself.
This reverts commit 6c182dd14d.
No reason to drop working code, for which there is no other alternative
(in this case, formatting/checking HFS+ filesystems).
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/encfs/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/hyf73217fw2hx4kwkl7g2bg92rkabxlw-encfs-1.9.5/bin/encfs --version’ and found version 1.9.5
- ran ‘/nix/store/hyf73217fw2hx4kwkl7g2bg92rkabxlw-encfs-1.9.5/bin/encfsctl --version’ and found version 1.9.5
- found 1.9.5 with grep in /nix/store/hyf73217fw2hx4kwkl7g2bg92rkabxlw-encfs-1.9.5
- directory tree listing: https://gist.github.com/43f0591cfbd83d8f0ed7349f3b2cbec2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/archivemount/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/7dc19v4ibkd9a958mxrhbn8hi4dj6flw-archivemount-0.8.12/bin/archivemount -V` and found version 0.8.12
- ran `/nix/store/7dc19v4ibkd9a958mxrhbn8hi4dj6flw-archivemount-0.8.12/bin/archivemount --version` and found version 0.8.12
- found 0.8.12 with grep in /nix/store/7dc19v4ibkd9a958mxrhbn8hi4dj6flw-archivemount-0.8.12
- directory tree listing: https://gist.github.com/9f95a5aa5b6c354b2dd5db0351c8fb72
Uses the HTTPS url for cases where the existing URL has a permanent
redirect. For each domain, at least one fixed derivation URL was
downloaded to test the domain is properly serving downloads.
Also fixes jbake source URL, which was broken.
The ceph-mgr daemon needs to know the location of cephs own-made python modules for some of the modules
that you can enable for it.
With wrapProgram, a wrapper is added that sets the proper pythonpath environment variable for the ceph-mgr
daemon so its modules can find the ceph python modules
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/sn92kb7bgpg6arj6jfgg7yv78ap2fkll-archivemount-0.8.9/bin/archivemount -V` and found version 0.8.9
- ran `/nix/store/sn92kb7bgpg6arj6jfgg7yv78ap2fkll-archivemount-0.8.9/bin/archivemount --version` and found version 0.8.9
- found 0.8.9 with grep in /nix/store/sn92kb7bgpg6arj6jfgg7yv78ap2fkll-archivemount-0.8.9
Resolved the following conflicts (by carefully applying patches from the both
branches since the fork point):
pkgs/development/libraries/epoxy/default.nix
pkgs/development/libraries/gtk+/3.x.nix
pkgs/development/python-modules/asgiref/default.nix
pkgs/development/python-modules/daphne/default.nix
pkgs/os-specific/linux/systemd/default.nix
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/debugfs.reiser4 -h` got 0 exit code
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/debugfs.reiser4 --help` got 0 exit code
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/debugfs.reiser4 -V` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/debugfs.reiser4 -v` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/debugfs.reiser4 --version` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/debugfs.reiser4 -h` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/debugfs.reiser4 --help` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/make_reiser4 -h` got 0 exit code
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/make_reiser4 --help` got 0 exit code
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/make_reiser4 -V` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/make_reiser4 -v` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/make_reiser4 --version` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/make_reiser4 -h` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/make_reiser4 --help` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/measurefs.reiser4 -h` got 0 exit code
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/measurefs.reiser4 --help` got 0 exit code
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/measurefs.reiser4 -V` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/measurefs.reiser4 -v` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/measurefs.reiser4 --version` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/measurefs.reiser4 -h` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/measurefs.reiser4 --help` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/mkfs.reiser4 -h` got 0 exit code
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/mkfs.reiser4 --help` got 0 exit code
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/mkfs.reiser4 -V` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/mkfs.reiser4 -v` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/mkfs.reiser4 --version` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/mkfs.reiser4 -h` and found version 1.2.1
- ran `/nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1/bin/mkfs.reiser4 --help` and found version 1.2.1
- found 1.2.1 with grep in /nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1
- found 1.2.1 in filename of file in /nix/store/frv798x9wv35ia6733bpwvq94w2mp9hm-reiser4progs-1.2.1
Semi-automatic update. These checks were performed:
- built on NixOS
- found 1.1.1 in filename of file in /nix/store/izfdcr9hld3rmcwcmvwfv9mc2pd414x3-zerofree-1.1.1
cc "@theuni"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/r1icgafqy02cz35kjkxr86hxj8mj1nyv-securefs-0.8.1/bin/securefs version` and found version 0.8.1
- found 0.8.1 with grep in /nix/store/r1icgafqy02cz35kjkxr86hxj8mj1nyv-securefs-0.8.1
- found 0.8.1 in filename of file in /nix/store/r1icgafqy02cz35kjkxr86hxj8mj1nyv-securefs-0.8.1
Semi-automatic update. These checks were performed:
- built on NixOS
- found 3.0.1 in filename of file in /nix/store/lwcvnbi1i9w8y84zi6b2g3ayqzzyxd0p-hubicfuse-3.0.1
cc "@jpierre03"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/cfhzvmll3rjhgrhl4ypv40ap726dlgh2-encfs-1.9.4/bin/encfs --version` and found version 1.9.4
- ran `/nix/store/cfhzvmll3rjhgrhl4ypv40ap726dlgh2-encfs-1.9.4/bin/encfsctl --version` and found version 1.9.4
- found 1.9.4 with grep in /nix/store/cfhzvmll3rjhgrhl4ypv40ap726dlgh2-encfs-1.9.4
- found 1.9.4 in filename of file in /nix/store/cfhzvmll3rjhgrhl4ypv40ap726dlgh2-encfs-1.9.4
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/btrfs --help` got 0 exit code
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/btrfs help` got 0 exit code
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/btrfs --version` and found version 4.15.1
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/btrfs version` and found version 4.15.1
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/mkfs.btrfs --help` got 0 exit code
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/mkfs.btrfs -V` and found version 4.15.1
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/mkfs.btrfs --version` and found version 4.15.1
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/btrfs-debug-tree help` got 0 exit code
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/btrfs-image --help` got 0 exit code
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/btrfs-find-root --help` got 0 exit code
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/btrfstune --help` got 0 exit code
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/btrfs-convert --help` got 0 exit code
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/fsck.btrfs -h` got 0 exit code
- ran `/nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1/bin/fsck.btrfs --help` got 0 exit code
- found 4.15.1 with grep in /nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1
- found 4.15.1 in filename of file in /nix/store/23glaba4yda3cyjixsxni52i2grvi799-btrfs-progs-4.15.1
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/56lvl3w77zgwsk1v618bklq10aq7fp17-bindfs-1.13.9/bin/bindfs -h` got 0 exit code
- ran `/nix/store/56lvl3w77zgwsk1v618bklq10aq7fp17-bindfs-1.13.9/bin/bindfs --help` got 0 exit code
- ran `/nix/store/56lvl3w77zgwsk1v618bklq10aq7fp17-bindfs-1.13.9/bin/bindfs -V` and found version 1.13.9
- ran `/nix/store/56lvl3w77zgwsk1v618bklq10aq7fp17-bindfs-1.13.9/bin/bindfs --version` and found version 1.13.9
- found 1.13.9 with grep in /nix/store/56lvl3w77zgwsk1v618bklq10aq7fp17-bindfs-1.13.9
With adding a patch that makes 2 absolute paths into 2 relative paths, ensuring the third-party libraries are available
in the python environment used and wrapping the python tools with wrapPrograms does so that the fixed ceph pkg can
compile and run as intended on NixOS.
- Update Ceph to last version
- Solve vulernatibility problem in the old version
- Patch rocksdb ceph rocksdb API
- Simplify a lot ceph build by switching to CMake
This Pull request require #34662 and #34661 to be effective
This continues #23374, which always kept around both attributes, by
always including both propagated files: `propgated-native-build-inputs`
and `propagated-build-inputs`. `nativePkgs` and `crossPkgs` are still
defined as before, however, so this change should only barely
observable.
This is an incremental step to fully keeping the dependencies separate
in all cases.
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.
Netatalk 3.1.11 is the latest stable release. There is also a nasty bug
with netatalk < 3.1.11 (https://sourceforge.net/p/netatalk/bugs/636/)
that prevents using netatalk shares for time machine backups.
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>
This requires some small changes in the stdenv, then working around the
weird choice LLVM made to hardcode @rpath in its install name, and then
lets us remove a ton of annoying workaround hacks in many of our Go
packages. With any luck this will mean less hackery going forward.
Changes:
* The patch `glusterfs-fix-unsubstituted-autoconf-macros` was deleted
because the issue was fixed upstream:
https://bugzilla.redhat.com/show_bug.cgi?id=1450588
* The `glusterd-ganesha.c` part of `glusterfs-use-PATH-instead-of-hardcodes`
was detleted because `glusterd-ganesha.c` was removed upstream
without replacement that has the relevant hardcoded paths.
Closes https://github.com/NixOS/nixpkgs/pull/29062
This fixes:
Traceback (most recent call last):
File "/nix/store/7f9arl3f9xyj8sm05mkanh2mlp217192-glusterfs-3.10.2/libexec/glusterfs/glusterfind/changelog.py", line 22, in <module>
import libgfchangelog
File "/nix/store/7f9arl3f9xyj8sm05mkanh2mlp217192-glusterfs-3.10.2/libexec/glusterfs/glusterfind/libgfchangelog.py", line 21, in <module>
libgfc = CDLL("libgfchangelog.so", use_errno=True, mode=RTLD_GLOBAL)
File "/nix/store/nlyr5ankhi7yvva8zndi718zj37js270-python-2.7.13-env/lib/python2.7/ctypes/__init__.py", line 362, in __init__
self._handle = _dlopen(self._name, mode)
OSError: libgfchangelog.so: cannot open shared object file: No such file or directory
Connection to 10.0.0.2 closed.
when running `glusterfind pre`.
Done by setting PYTHONPATH/LD_LIBRARY_PATH as for the other
Python scripts.
Fixes error
File "/nix/store/lxpsl84km87xpk59nai6a33ihgpfs7qr-glusterfs-3.10.2/libexec/glusterfs/glusterfind/changelog.py", line 105, in populate_pgfid_and_inodegfid
file_xattrs = xattr.list(p)
AttributeError: 'module' object has no attribute 'list'
when using `glusterfind pre`.
* 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
It was being parsed incorrectly, as noted on
https://github.com/NixOS/nix/issues/1440
nix-repl> builtins.parseDrvName ntfs3g.name
{ name = "ntfs"; version = "3g-2017.3.23"; }
Or else `services.udev.packages = [ bcache-tools ]` cannot be used.
To not break bcache in the initrd I'm modifying this in stage-1.nix:
- --replace /bin/sh ${extraUtils}/bin/sh
+ --replace ${bash}/bin/sh ${extraUtils}/bin/sh
Reasoning behind that change:
* If not modifying the /bin/sh pattern in any way, it will also match
${bash}/bin/sh, creating a broken path like
/nix/store/HASH-bash/nix/store/HASH-bash/bin/sh in the udev rule file.
* The addition of /bin/sh was done in 775f381a9e
("stage-1: add bcache support"). It seems somewhat plausible that
no new users have appeared since then and we can take this opportunity
to back out of this change without much fear of regressions.
If there _are_ regressions, they should be in the form of build time
errors, not runtime (boot), due to how the udev rule output is checked
for invalid path references. So low risk, IMHO.
* An alternative approach could be to copy the /bin/sh substitute rule
over to the non-initrd udev rules implementation in NixOS, but I think
this way is better:
- The rules file comes with a working path out of the box.
- We can use more precise pattern matching when modifying the udev
rules for the initrd.
Done by setting PATH and PYTHONPATH appropriately.
Adds the following patches:
* One that removes hardcodes to /sbin, /usr/bin, etc.
from gluster, so that programs like `lvm` and `xfs_info` can be
called at runtime; see https://bugzilla.redhat.com/show_bug.cgi?id=1450546.
* One that fixes unsubstituted autoconf macros in paths (a problem
in the 3.10 release); see https://bugzilla.redhat.com/show_bug.cgi?id=1450588.
* One that removes uses of the `find_library()` Python function that does
not behave as expected in Python < 3.6 (and would not behave correctly
even on 3.6 in nixpkgs due to #25763);
see https://bugzilla.redhat.com/show_bug.cgi?id=1450593.
I think that all of these patches should be upstreamed.
Also adds tests to check that none of the Python based utilities
throw import errors, calling `--help` or equivalent on them.
This is because the source tarball available on
https://download.gluster.org/pub/gluster/glusterfs/3.10/3.10.1/glusterfs-3.10.1.tar.gz
has different contents than the v3.10.1 tag;
for example, it lacks the file `xlators/features/ganesha/src/Makefile.am`,
which the tag has.
This is because GluserFS's release process removes some unused files.
This made impossible to apply patches written by or for upstream, as those
are written against what's in upstream's git.
As a nice side effect, we no longer have to hardcode the "3.10" in the
`3.10/${version}` part of the URL.
This reverts commit c0cef0425e.
The output of the command-line tool has changed somewhat and at least
nixos-generate-config.pl needs modifications to match. I'm leaving that
to someone who knows a bit more about btrfs.
Issue #24810.
util-linux cowardly refuses to install on all platforms. Therefore we
cannot rely on it for external dependancies, in particular luuid.
e2fsprogs won't configure without the luuid dependancy being satisfied.
From the Debian advisory:
Jann Horn of Google Project Zero discovered that NTFS-3G, a read-write
NTFS driver for FUSE, does not scrub the environment before executing
modprobe with elevated privileges. A local user can take advantage of
this flaw for local root privilege escalation.
This reverts commit e82c325bff.
This package update breaks the `update-grub.pl` script:
updating GRUB 2 menu...
Btrfs did not return a path for the subvolume at /
error: unable to activate new configuration
This backwards-incompatible change is the culprit:
$ /nix/store/np25r3yzv2r41ji7v73j110inpj8lhn2-btrfs-progs-4.8.2/bin/btrfs subvol show /
/ is toplevel subvolume
vs.
$ /nix/store/h53vs13nqvjwahpl26a4s7ygqk9xw1mw-btrfs-progs-4.8.3/bin/btrfs subvol show /
/
Name: <FS_TREE>
UUID: -
Parent UUID: -
Received UUID: -
Creation time: -
Subvolume ID: 5
Generation: 6004631
Gen at creation: 0
Parent ID: 0
Top level ID: 0
Flags: -
Snapshot(s):
Packaging changes
- Uses cmake
- Removes depends on rlog and boost, uses tinyxml to parse xml
Note that the encfssh utility is disabled, it requires patching to
work (and didn't work in previous versions of the package, either).
Better to leave it unusable until fixed.
This moves libsystemd.so and libudev.so into systemd.lib, and gets rid
of libudev (which just contained a copy of libudev.so and the udev
headers). It thus reduces the closure size of all packages that
(indirectly) depend on libsystemd, of which there are quite a few (for
instance, PulseAudio and dbus). For example, it reduces the closure of
Blender from 430.8 to 400.8 MiB.
After #16017 there were a lot
of comments saying that `nix` would be better than `JSON`
for Go packages dependency sets.
As said in https://github.com/NixOS/nixpkgs/pull/16017#issuecomment-229624046
> Because of the content-addressable store, if two programs have the
> same dependency it will already result in the same derivation in
> the
> store. Git also has compression in the pack files so it won't make
> much difference to duplicate the dependencies on disk. And finally
> most users will just use the binary builds so it won't make any
> differences to them.
This PR removes `libs.json` file and puts all package dependencies in
theirs `deps.json`.
In line with the Nixpkgs manual.
A mechanical change, done with this command:
find pkgs -name "*.nix" | \
while read f; do \
sed -e 's/description\s*=\s*"\([a-z]\)/description = "\u\1/' -i "$f"; \
done
I manually skipped some:
* Descriptions starting with an abbreviation, a user name or package name
* Frequently generated expressions (haskell-packages.nix)
Building against anything other than the headers used to build libc
doesn't really make any sense.
Also: this package is Linux specific, so mark it as such.
Create these symlinks, since NixOS (and other users) can still be using
the old names:
dosfsck -> fsck.fat
dosfslabel -> fatlabel
fsck.msdos -> fsck.fat
fsck.vfat -> fsck.fat
mkdosfs -> mkfs.fat
mkfs.msdos -> mkfs.fat
mkfs.vfat -> mkfs.fat
While at it, kill the makeFlags which seems unnecessary as it seems
to use a standard Autotools build (maybe this is a new thing).
When mount is used with mount-type "fuse.bindfs", it cannot find the
mount helper.
If mount can't find `mount.fuse.bindfs`, it executes the `mount.fuse`
mount helper and passes `fuse.bindfs` as argument. Then `mount.fuse`
tries to execute `bindfs` on its own, but it is not found in the PATH.
By creating a `mount.fuse.bindfs` link to the `bindfs` executable, this
problem is avoided because `mount` will just execute the
`mount.fuse.bindfs` mount helper without `mount.fuse` in the middle.
The following parameters are now available:
* hardeningDisable
To disable specific hardening flags
* hardeningEnable
To enable specific hardening flags
Only the cc-wrapper supports this right now, but these may be reused by
other wrappers, builders or setup hooks.
cc-wrapper supports the following flags:
* fortify
* stackprotector
* pie (disabled by default)
* pic
* strictoverflow
* format
* relro
* bindnow
This will probably be mandatory soon, and is a step in the right
direction. Removes the deprecated meta.version, and move some meta
sections to the end of the file where I should have put them in
the first place.
This adds a backport of rhinstaller/blivet#39 to the pinned blivet
version 0.17, it's addressing the following upstream bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1196397
It has been reported at aszlig/nixpart#7 and tested by @manveru (the
issue reporter), thanks a lot.
Thanks also to @domenkozar for finding the upstream issue.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Reported-by: Michael Fellinger <m.fellinger@gmail.com>
Fixes: aszlig/nixpart#7
Bugfixes:
- chunk recovery: fix floating point exception
- chunk recovery: endianity bugfix during rebuild
- mkfs with 64K pages and nodesize reported superblock checksum mismatch
- check: properly reset nlink of multi-linked file
Too many changes to list here. See:
https://btrfs.wiki.kernel.org/index.php/Changelog#By_version_.28btrfs-progs.29
