Not making much sense because partial upgrading is not supported in the
first place. Also note that this specifier did not prevent libuuid from
being upgraded, leaving its reverse dependencies behind.
%ci:no-build
Put libmount library in subpackage libmount, mount utilities in
subpackage mount-utils, libfdisk in subpackage libfdisk, and fdisk
utilities in subpackage fdisk.
On my aarch64 device, /system/bin/mount is unable to handle logical
volumes (tries to access the non-existing /etc/fstab and errors), so
lets add our own libmount package.
Enabling libmount also enables the lsblk utility, which we put in
blk-utils.
Put libmount library in subpackage libmount, mount utilities in
subpackage mount-utils, libfdisk in subpackage libfdisk, and fdisk
utilities in subpackage fdisk.
On my aarch64 device, /system/bin/mount is unable to handle logical
volumes (tries to access the non-existing /etc/fstab and errors), so
lets add our own libmount package.
Enabling libmount also enables the lsblk utility, which we put in
blk-utils.
* fix ccache building failed due to sse
* gogs require go-bindata to be built
* mariadb's cmake need to change END to ENDIF
* fix neovim building due to gitsubmodule usage
* php-redis: add blacklist from php dep
* rlwrap update to new version
* stfl disable perl and ruby
* util-linux comment out shm & sem support
* weechat disable ruby
* tor building need glob
In issue https://github.com/termux/termux-packages/issues/6160 I have found
that community repo "its-pointless.github.io" specifies us as maintainer
for its packages. This is NOT TRUE and potentially misleads people using
these packages.
Now TERMUX_PKG_MAINTAINER will contain a default value which is neutral
and not specify maintainer. So all packages now have to override it to
the correct value.
[skip ci]
%ci:no-build
parted: update from 3.2 to 3.3
rhash: update from 1.3.9 to 1.4.0
seafile-client: update from 7.0.8 to 7.0.9
sensible-utils: update from 0.0.12 to 0.0.13
util-linux: update from 2.35.2 to 2.36