The libevent port has a security patch that was introduced by mistake, it causes malfunctions of programs using it, e.g. links unable to fork external programs. The patch has been reverted in the upstream[1], so I think it should be removed here too.

[1]https://github.com/libevent/libevent/commit/ddacaef59ab6808a0801007d0a681f2415af4871

Some ports have incomplete file list in .signature. This is the case for opt/mplayer that its main source signature is missing, what makes it bad is that it's also using the insecure http protocol (http://distfiles.serverop.de/mplayer-$version.tar.xz).

cd to /usr/pors/opt/mplayer, pkgmk -cs shows that the signature is ok.

I suggest patch pkgmk to print out errors in such case and re-check all ports, I believe there're more ports affected by this issue.

Currently the port installs -ise variant of en_GB dict files without changing their names, so hunspell couldn't recognise locale en_GB correctly, Many other locales symlink to en_GB are also broken.

The new url is:
https://download.qt.io/archive/qt/4.8/4.8.7/qt-everywhere-opensource-src-4.8.7.tar.gz

The download url is broken, the old url redirects to a github repo.

debian has shut down their ftp services, so the link is broken. I've changed the url to using http, and updated it to a newer version by the way. also I removed a line that changes mandir to /usr/man.

Hi,
python3-pip does not work if python3-setuptools is not installed. But it seems
it's impossible to successfully install python3-setuptools.

If I run 'prt-get depinst python3-setuptools',
it first installs python3-appdirs, no problem,
next python3-pyparsing, here it always throw an exception:

Found existing installation: appdirs 1.4.0
Uninstalling appdirs-1.4.0:
Exception:
...

I've configured prt-get to run pkgmk as an unprevileged user with fakeroot.
The problematic line of script is python3-pyparsing/Pkgfile:19:

/usr/bin/python3/ $SRC/get-pip.py --root=$SRC/build

get-pip.py attempts to uninstall appdirs, which is impossible.

I fixed this bug by made a simple modification to get-pip.py:

sed -i 's/"--upgrade"/"--upgrade", "--upgrade-strategy", "only-if-needed"/' $SRC/get-pip.py

By adding that option to pip inside get-pip.py, it will not try uninstalling existing dependencies if possible.
It still does not work if one has an outdated dependency, but uninstalling it should sovle the problem.

See here for the reference:
https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption--upgrade-strategy

=======> ERROR: Footprint mismatch found:
MISSING -rwxr-xr-x root/root usr/lib/python3.6/lib-dynload/_decimal.cpython-36m-x86_64-linux-gnu.so

There are many files installs to /usr/lib/clang/$version, and the footprint hasn't been updated.

The problem:
pkgmk exports PKG and SRC before calling 'build', which may interfere with
building scripts executed inside the build function (for example, the configure
script).
This problem may not be obvious for most packages, it affects packages that
references environment variables PKG or SRC while building.

A example of this bug is in my port swi-prolog:

build() {
cd swipl-$version/src
./configure --prefix=/usr
make
make DESTDIR=$PKG install

cd ../packages
./configure --prefix=/usr # here
make
make DESTDIR=$PKG install

find $PKG -type f -name 'README*' -delete
}

Here the second configure script does not work as intended. By default if PKG is
empty, the second configure script will build a default set of packages, but as
pkgmk has exported PKG, which makes no sense to swi-prolog, the configure script
silently ignored the error, and choose to build nothing.

The fix:
The export can be omitted for PKG and SRC in pkgmk, the basic execution of pkgmk
is as follows:

. Pkgfile
export PKG=...
export SRC=...
(set -e -x; build)

Since Pkgfile is sourced, which means the build funciton runs in the same
context/process as pkgmk, it's not necessary to export PKG and SRC. I've tested,
by simply removing the keyword export from the variable assignment of PKG and
SRC, all my ports builds fine, of course it also solved the bug above. So this
fix should not influence existing ports.

See attachment for the proposed fix.

Related mailing list discussions:
https://lists.crux.nu/pipermail/crux/2017-January/005373.html
https://lists.crux.nu/pipermail/crux/2017-January/005376.html

flash does not ship with chrome any more, here is the fix:

contrib/mldonkey doesn't build with opt/ocaml. mldonkey can build it's own ocaml during ./configure, and the ocaml version is hardcoded. Here is the fix, and I've updated mldonkey to 3.1.5 by the way.

The downlaod link of amule is borken, and a newer version of amule is available.

The newest vim has an issue that it prints many error messages when running as vi, the issue also presents when running git commit. After digging for a while, I found the problem of it, that's because of packadd matchit in /usr/share/vim/vimrc, and that line of code is not compatible with vi, the fix is rather simple, just,
sed -i 's/packadd matchit/if 1 | packadd matchit | endif/'/usr/share/vim/vimrc
The if statement would be ommitted by vi, thus avoid the issue.

According to https://www.kernel.org/doc/Documentation/kbuild/modules.txt, the default location for external modules is /lib/modules/$(KERNELRELEASE)/extra/, whereas ports/contrib/virtualbox installs its modules to /lib/modules/$(KERNELRELEASE)/kernel/drivers/misc.
A side-effect of this is that the virtualbox moduels get wiped out when doing a 'make modules_install' after rebuilding the linux kernel.

It seems that geeqie has been migrated to github, the source is not available on sourceforge anymore. And the most recent version is 1.2.3, we have version 1.0 in the crux ports.
This is the Pkgfile that compiles fine with the newest version:

# Description: Gtk+ based image viewer
# URL: http://geeqie.sourceforge.net/
# Maintainer: Juergen Daubert, juergen dot daubert at t-onlione dot de
# Depends on: gtk intltool

name=geeqie
version=1.2.3
release=1
source=(http://geeqie.org/$name-$version.tar.xz)

build() {
cd $name-$version
./autogen.sh
export CFLAGS="$CFLAGS `pkg-config --cflags gtk+-2.0`"
export LDFLAGS="$LDFLAGS `pkg-config --libs gtk+-2.0`"
./configure --prefix=/usr --disable-gtk3
make
make DESTDIR=$PKG install
sed -ri '/\[.+\]=/d' $PKG/usr/share/{geeqie/,}applications/*.desktop
rm -r $PKG/usr/share/{doc,locale}
}

I updated the nvidia proprietary driver for my crux machine, and I noticed that nvidia.ko got installed to /lib/modules/`uname -r`/kernel/drivers/video/nvidia.ko, if I remember correctly, it was in /lib/modules/`uname -r`/extra/. I noticed the problem when I rebuild my linux kernel, and reinstall the linux kernel modules with 'make modules_install', that newly updated nvidia driver module got removed unexpectedly. so I consider this a bug, or I might do it wrong with the kernel rebuild?