Whenever we create scripts that are installed to $out, we must use runtimeShell
in order to get the shell that can be executed on the machine we create the
package for. This is relevant for cross-compiling. The only use case for
stdenv.shell are scripts that are executed as part of the build system.
Usages in checkPhase are borderline however to decrease the likelyhood
of people copying the wrong examples, I decided to use runtimeShell as well.
The original issue can be reproduced when sending with an unpatched
`mutt` or `neomutt` an email with an attachement which as han `.asc`
extension. This will be interpreted as `application/pgp-encrypted` which
experiences special logic, in the end the attachement will contain
"Version: 1"[1][2][3]
Right now, there are the following issues in the {,neo}mutt packages:
* `mutt.override { smimeSupport = true }` fails to build since the
Debian patch results in a 404. Debian moved their packages to
`salsa.debian.org`.
However we can't use a versioned URL for this as Debian only tracks
the Mutt versions that are available in their releases. The patch
doesn't touch Mutt's core and is therefore simple to rebase, so
sticking to the 1.10.2 patch for now should be sufficient.
* The original issue was never fixed in NeoMutt, currently we use the
S/MIME database from `pkgs.mime-types` which contains the issue with
`application/pgp-encrypted` as well.
After some discussion[4] it seems to be the best decision to use the
`mailcap` database distributed by Fedora[5] which fixes the issue
rather than `mime-types` v9 from 2012.
[1] https://bugs.archlinux.org/task/43319
[2] https://bugs.gentoo.org/534658
[3] https://github.com/neomutt/neomutt/blob/neomutt-20180716/sendlib.c#L490-L496
[4] https://github.com/NixOS/nixpkgs/pull/50927#issuecomment-441383260
[5] https://pagure.io/mailcap
In a few cases it wasn't clear so I left them as-is.
While visiting these moved other things to nativeBuildInputs
when it was clear they were one of these cases:
* makeWrapper
* archive utilities (in order to unpack src)
* a few of these might no longer be needed but leaving for another day
Couple of things were updated to make this work.
1. webkitgtk24x-gtk3 that is marked unsafe has been replaced with
webkitgtk (2.20.*) as astroid has recently indicated that [>= 2.20
is
acceptable](48ce7e3010)
2. protobuf built input was added to satisfy requirements
3. astroid was not functional at all without proper icons so gnome3.defaultIconTheme
were added to buildInputs
4. By default, astroid will use `gvim` as a setting for the embedded
editor, however that didn't work well with nixpkgs. vim is now
bundled with astroid by default. This setting can be overridden
by the user in astroid's config file.
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
* 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
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/balsa/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/1hgx73336q1zhd8r95wv2kicf6a2jmby-balsa-2.5.6/bin/balsa had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/1hgx73336q1zhd8r95wv2kicf6a2jmby-balsa-2.5.6/bin/balsa-ab had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/1hgx73336q1zhd8r95wv2kicf6a2jmby-balsa-2.5.6/bin/.balsa-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/1hgx73336q1zhd8r95wv2kicf6a2jmby-balsa-2.5.6/bin/.balsa-ab-wrapped had a zero exit code or showed the expected version
- 0 of 4 passed binary check by having a zero exit code.
- 0 of 4 passed binary check by having the new version present in output.
- found 2.5.6 with grep in /nix/store/1hgx73336q1zhd8r95wv2kicf6a2jmby-balsa-2.5.6
- directory tree listing: https://gist.github.com/8c38ffd6950508c78fde54f6f3530673
- du listing: https://gist.github.com/2156c87e8b84b7a84f6d6f4c4a7b8ebb
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/notmuch/versions.
These checks were done:
- built on NixOS
- /nix/store/fc0y8jb20kfm3v4yy3zzc6ipidc1ks1c-notmuch-0.27/bin/notmuch passed the binary check.
- Warning: no invocation of /nix/store/fc0y8jb20kfm3v4yy3zzc6ipidc1ks1c-notmuch-0.27/bin/notmuch-emacs-mua had a zero exit code or showed the expected version
- 1 of 2 passed binary check by having a zero exit code.
- 1 of 2 passed binary check by having the new version present in output.
- found 0.27 with grep in /nix/store/fc0y8jb20kfm3v4yy3zzc6ipidc1ks1c-notmuch-0.27
- directory tree listing: https://gist.github.com/2a14e6349ea43a555857f9e30bf328ff
- du listing: https://gist.github.com/d08317825ff4ade027455942eb367fdb
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mutt/versions.
These checks were done:
- built on NixOS
- /nix/store/ydny2lhs0idsg1hxzkgi198n9jn17rcw-mutt-1.10.0/bin/mutt passed the binary check.
- /nix/store/ydny2lhs0idsg1hxzkgi198n9jn17rcw-mutt-1.10.0/bin/pgpring passed the binary check.
- Warning: no invocation of /nix/store/ydny2lhs0idsg1hxzkgi198n9jn17rcw-mutt-1.10.0/bin/pgpewrap had a zero exit code or showed the expected version
- /nix/store/ydny2lhs0idsg1hxzkgi198n9jn17rcw-mutt-1.10.0/bin/muttbug passed the binary check.
- /nix/store/ydny2lhs0idsg1hxzkgi198n9jn17rcw-mutt-1.10.0/bin/flea passed the binary check.
- Warning: no invocation of /nix/store/ydny2lhs0idsg1hxzkgi198n9jn17rcw-mutt-1.10.0/bin/smime_keys had a zero exit code or showed the expected version
- 4 of 6 passed binary check by having a zero exit code.
- 0 of 6 passed binary check by having the new version present in output.
- found 1.10.0 with grep in /nix/store/ydny2lhs0idsg1hxzkgi198n9jn17rcw-mutt-1.10.0
- directory tree listing: https://gist.github.com/2b53d5dc44b600872e77911ba7099e1c
- du listing: https://gist.github.com/4caca5d9043a5281a6b192ebaf30065f
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/neomutt/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/ww06xw1m1b0r4fy308kwa6vvj4cyy1yk-neomutt-20180512/bin/neomutt -h’ got 0 exit code
- ran ‘/nix/store/ww06xw1m1b0r4fy308kwa6vvj4cyy1yk-neomutt-20180512/bin/neomutt --help’ got 0 exit code
- ran ‘/nix/store/ww06xw1m1b0r4fy308kwa6vvj4cyy1yk-neomutt-20180512/bin/.neomutt-wrapped -h’ got 0 exit code
- ran ‘/nix/store/ww06xw1m1b0r4fy308kwa6vvj4cyy1yk-neomutt-20180512/bin/.neomutt-wrapped --help’ got 0 exit code
- found 20180512 with grep in /nix/store/ww06xw1m1b0r4fy308kwa6vvj4cyy1yk-neomutt-20180512
- directory tree listing: https://gist.github.com/8d13b2cd77148163ee7c664ce4cdba07
- du listing: https://gist.github.com/9755eddec256452bf53913477fd2bebb
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/notmuch/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/bin/notmuch --help’ got 0 exit code
- ran ‘/nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/bin/notmuch help’ got 0 exit code
- ran ‘/nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/bin/notmuch --version’ and found version 0.26.1
- found 0.26.1 with grep in /nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1
- directory tree listing: https://gist.github.com/adeae189f9ac416571a7c0e3beca712f
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/vfixsp2napk2fv4dkhzdfv0nx473vz1j-imapfilter-2.6.11/bin/imapfilter -h` got 0 exit code
- ran `/nix/store/vfixsp2napk2fv4dkhzdfv0nx473vz1j-imapfilter-2.6.11/bin/imapfilter --help` got 0 exit code
- ran `/nix/store/vfixsp2napk2fv4dkhzdfv0nx473vz1j-imapfilter-2.6.11/bin/imapfilter -V` and found version 2.6.11
- ran `/nix/store/vfixsp2napk2fv4dkhzdfv0nx473vz1j-imapfilter-2.6.11/bin/imapfilter --version` and found version 2.6.11
- ran `/nix/store/vfixsp2napk2fv4dkhzdfv0nx473vz1j-imapfilter-2.6.11/bin/imapfilter -h` and found version 2.6.11
- ran `/nix/store/vfixsp2napk2fv4dkhzdfv0nx473vz1j-imapfilter-2.6.11/bin/imapfilter --help` and found version 2.6.11
- found 2.6.11 with grep in /nix/store/vfixsp2napk2fv4dkhzdfv0nx473vz1j-imapfilter-2.6.11
- directory tree listing: https://gist.github.com/3899407e9730a32a5b25ade7c1238086
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 1.0.3 with grep in /nix/store/5n2jwjv8x9a1sic8ia32vncq5i5smd0f-inboxer-1.0.3
- found 1.0.3 in filename of file in /nix/store/5n2jwjv8x9a1sic8ia32vncq5i5smd0f-inboxer-1.0.3
This is necessary because the standard library which is distributed with
lumail (the lumail core configuration so to speak) is written for lua5.1
apparently.
The website states 5.1 or 5.2 or 5.3, but 5.2 fails because "loadstring"
was deprecated in lua 5.2.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Includes:
* Package gets a flag to use the debug build
* install phase installs all lua scripts from the package and makes
lumail find them
* global configuration which is shipped with the package can be
overridden, if desired
* parallel building enabled
Semi-automatic update. These checks were performed:
- built on NixOS
- found 1.0.2 with grep in /nix/store/r58bhh86hprpzb4fh5xk0snaqgbqa8vy-inboxer-1.0.2
- found 1.0.2 in filename of file in /nix/store/r58bhh86hprpzb4fh5xk0snaqgbqa8vy-inboxer-1.0.2
cc "@mgttlinger"
This version bump contains the following fixes:
v8:
- Avoid a segmentation fault when notmuch_message_get_header() returns NULL. (Patch by Víctor M. Jáquez <vjaquez@igalia.com>).
v9:
- Do not use the deprecated notmuch_query_count_messages_st function when using Notmuch 0.25. (Patch by Adam Ruzicka <a.ruzicka@outlook.com>.)
We already had this patch in our tree.
- Fix crash in when running queries and the program is build with Notmuch 0.25. (Patch by Joshua Krusell <joshua.krusell@v-dem.net>).
- Fix conditional compilation when using Notmuch 0.25. (Patch by David Bremner <bremner@debian.org>).
Adaptation of #23058 by @spinus to 1.0.0rc1. See #23058 and #28111 for discussion.
This patch keeps the warnings. But I think it is useful to have a sanely working
version in nixpkgs, even if it is still considered insecure, just to follow the
upstream development by actually running it instead of reading the log.
it's an application, not a python module
Also, remove name attribute.
Build with python 3 by default.
afew: make setuptools_scm a buildInput
afew: don't set SETUPTOOLS_SCM_PRETEND_VERSION anymore
we fetch from pypi, with version info properly set, so this shouldn't be
an issue.
afew: set license
afew: add notmuch binary to PATH
it seems afew calls "notmuch new" in MailMover.py
afew: don't set LD_LIBRARY_PATH
the library is already hardcoded pythonPackages.notmuch's globals.py
The mime.types file shipped with neomutt is pretty basic so we use the one put
together by Gentoo from a dedicated mime-types derivation as it vastly improves
the handling of attachments.
Neomutt will by default look for /etc/mime.types which isn't present in order to
map file extensions to mime types.
If this file isn't found, and a message has a png attached with
application/octet-stream mime type, neomutt will not know what to do with it.
- neomutt has changed the binary name so we enable "mutt" via a wrapper script
with a warning
- we don't have to manually run the prepare.sh script as autoreconfHook handles
everything for us
- doc generation was previously trying to fetch DTDs from the net
