Framework: partially sync with upstream
Taken from: FreeBSD
This commit is contained in:
Franco Fichtner
parent
a3c763c44c
commit
f3230d03ec
2
GIDs
2
GIDs
|
|
@ -516,7 +516,7 @@ polkitd:*:565:
|
|||
# free: 572
|
||||
# free: 573
|
||||
# free: 574
|
||||
# free: 575
|
||||
nexus:*:575:
|
||||
# free: 576
|
||||
# free: 577
|
||||
# free: 578
|
||||
|
|
|
|||
4
MOVED
4
MOVED
|
|
@ -8801,3 +8801,7 @@ ftp/curl-hiphop||2016-11-08|Has expired: useful only for removed hiphop-php
|
|||
textproc/rubygem-string-scrub||2016-11-08|Has expired: needed only for EOL versions of Ruby
|
||||
cad/py-gdsii|cad/python-gdsii|2016-11-10|Renamed
|
||||
textproc/erlang-p1xml|textproc/erlang-fast_xml|2016-11-08|Project was renamed
|
||||
devel/py-pydasm|devel/py-capstone|2016-11-11|Has expired: No more upstream and known bugs, use devel/py-capstone instead
|
||||
devel/libdasm|devel/capstone3|2016-11-11|Has expired: No more upstream and known bugs, use devel/capstone3 instead
|
||||
security/erlang-p1tls|security/erlang-fast_tls|2016-11-11|Project was renamed
|
||||
mail/trojita-qt4|mail/trojita|2016-11-13|Qt4 support was dropped, use mail/trojita instead
|
||||
|
|
|
|||
|
|
@ -176,8 +176,8 @@ CHOSEN_COMPILER_TYPE= clang
|
|||
.if (defined(FAVORITE_COMPILER) && ${FAVORITE_COMPILER} == gcc) || (${ARCH} != amd64 && ${ARCH} != i386) # clang not always supported on Tier-2
|
||||
USE_GCC= yes
|
||||
CHOSEN_COMPILER_TYPE= gcc
|
||||
.elif (${COMPILER_TYPE} == clang && ${COMPILER_VERSION} < 34) || ${COMPILER_TYPE} == gcc
|
||||
.if ${ALT_COMPILER_TYPE} == clang && ${ALT_COMPILER_VERSION} >= 34
|
||||
.elif ${COMPILER_TYPE} == gcc
|
||||
.if ${ALT_COMPILER_TYPE} == clang
|
||||
CPP= clang-cpp
|
||||
CC= clang
|
||||
CXX= clang++
|
||||
|
|
@ -198,8 +198,8 @@ CHOSEN_COMPILER_TYPE= clang
|
|||
.if (defined(FAVORITE_COMPILER) && ${FAVORITE_COMPILER} == gcc) || (${ARCH} != amd64 && ${ARCH} != i386) # clang not always supported on Tier-2
|
||||
USE_GCC= yes
|
||||
CHOSEN_COMPILER_TYPE= gcc
|
||||
.elif (${COMPILER_TYPE} == clang && ${COMPILER_VERSION} < 34) || ${COMPILER_TYPE} == gcc
|
||||
.if ${ALT_COMPILER_TYPE} == clang && ${ALT_COMPILER_VERSION} >= 34
|
||||
.elif ${COMPILER_TYPE} == gcc
|
||||
.if ${ALT_COMPILER_TYPE} == clang
|
||||
CPP= clang-cpp
|
||||
CC= clang
|
||||
CXX= clang++
|
||||
|
|
@ -220,8 +220,8 @@ CXX= ${LOCALBASE}/bin/clang++34
|
|||
.if (defined(FAVORITE_COMPILER) && ${FAVORITE_COMPILER} == gcc) || (${ARCH} != amd64 && ${ARCH} != i386) # clang not always supported on Tier-2
|
||||
USE_GCC= yes
|
||||
CHOSEN_COMPILER_TYPE= gcc
|
||||
.elif (${COMPILER_TYPE} == clang && ${COMPILER_VERSION} < 34) || ${COMPILER_TYPE} == gcc
|
||||
.if ${ALT_COMPILER_TYPE} == clang && ${ALT_COMPILER_VERSION} >= 34
|
||||
.elif ${COMPILER_TYPE} == gcc
|
||||
.if ${ALT_COMPILER_TYPE} == clang
|
||||
CPP= clang-cpp
|
||||
CC= clang
|
||||
CXX= clang++
|
||||
|
|
|
|||
|
|
@ -48,8 +48,8 @@ ALT_COMPILER_TYPE= gcc
|
|||
.endif
|
||||
|
||||
# We do always need clang
|
||||
.if (${COMPILER_TYPE} == clang && ${COMPILER_VERSION} < 34) || ${COMPILER_TYPE} != clang
|
||||
.if ${ALT_COMPILER_TYPE} == clang && ${ALT_COMPILER_VERSION} >= 34
|
||||
.if ${COMPILER_TYPE} != clang
|
||||
.if ${ALT_COMPILER_TYPE} == clang
|
||||
CC= /usr/bin/clang
|
||||
CPP= /usr/bin/clang-cpp
|
||||
CXX= /usr/bin/clang++
|
||||
|
|
|
|||
2
UIDs
2
UIDs
|
|
@ -521,7 +521,7 @@ polkitd:*:565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin
|
|||
# free: 572
|
||||
# free: 573
|
||||
# free: 574
|
||||
# free: 575
|
||||
nexus:*:575:575::0:0:Nexus Repository Manager OSS:/nonexistent:/usr/sbin/nologin
|
||||
# free: 576
|
||||
# free: 577
|
||||
# free: 578
|
||||
|
|
|
|||
89
UPDATING
89
UPDATING
|
|
@ -5,6 +5,95 @@ they are unavoidable.
|
|||
You should get into the habit of checking this file for changes each time
|
||||
you update your ports collection, before attempting any port upgrades.
|
||||
|
||||
20161113:
|
||||
AFFECTS: users of editors/libreoffice
|
||||
AUTHOR: bapt@FreeBSD.org
|
||||
|
||||
Building libreoffice with devel/mdds0 installed is known to fail.
|
||||
Users of portmaster/portupgrade and the one building in place should
|
||||
first remove devel/mdds0:
|
||||
|
||||
# pkg delete mdds0
|
||||
|
||||
20161113:
|
||||
AFFECTS: users of devel/libosinfo
|
||||
AUTHOR: novel@FreeBSD.org
|
||||
|
||||
The libosinfo port was separated into three different ports
|
||||
to follow the upstream split:
|
||||
|
||||
- sysutils/osinfo-db-tools: contains the CLI tools
|
||||
- misc/osinfo-db: contains database with OS data
|
||||
- devel/libosinfo: the library
|
||||
|
||||
As osinfo-db-tools now ships binaries that previously were
|
||||
part of libosinfo, it's required to delete the old libosinfo
|
||||
package to prevent conflict because of same files installation:
|
||||
|
||||
# pkg delete libosinfo
|
||||
|
||||
And then install the new version.
|
||||
|
||||
20161112:
|
||||
AFFECTS: users of security/heimdal
|
||||
AUTHOR: hrs@FreeBSD.org
|
||||
|
||||
Heimdal in the base system and security/heimdal <= 1.5.3_6 use
|
||||
Berkeley DB to store principals into /var/heimdal/heimdal.db and
|
||||
the database format is version 3 by default. On the other hand,
|
||||
security/heimdal 1.5.3_7 or newer use the newer version of
|
||||
Berkeley DB and the database format is version 9.
|
||||
These two versions are not compatible with each other. If there is
|
||||
a mismatch between Heimdal utilities and its database format,
|
||||
you will get an error like the following:
|
||||
|
||||
# /usr/local/sbin/kadmin -l dump
|
||||
BDB0641 __db_meta_setup: /var/heimdal/heimdal.db: unexpected file type or format
|
||||
kadmin: hdb_open: opening /var/heimdal/heimdal: Invalid argument
|
||||
|
||||
This mismatch can occur in the following three cases:
|
||||
|
||||
1. You used Heimdal in the base system and switch to use security/heimdal
|
||||
after creating /var/db/heimdal.db.
|
||||
|
||||
2. You used security/heimdal >= 1.5.3_7 and switch to use one in the
|
||||
base system.
|
||||
|
||||
3. You used security/heimdal < 1.5.3_7 and upgrade it to 1.5.3_7 or later.
|
||||
|
||||
To fix this mismatch, you need to dump contents of heimdal.db and
|
||||
rebuild the database by using kadmin(8) utility.
|
||||
|
||||
If you use Heimdal in the base system or older versions of
|
||||
security/heimdal, and plan to switch to use
|
||||
security/heimdal >= 1.5.3_7, execute the following command
|
||||
*after* creating a backup copy of /var/heimdal and installing
|
||||
security/heimdal:
|
||||
|
||||
# /usr/bin/kadmin -l dump /var/heimdal/heimdal.db.dump
|
||||
# rm /var/heimdal/heimdal.db
|
||||
# /usr/local/sbin/kadmin -l load /var/heimdal/heimdal.db.dump
|
||||
# rm /var/heimdal/heimdal.db.dump
|
||||
|
||||
The above example assumes security/heimdal is installed into
|
||||
/usr/local. If your base system is compiled with WITHOUT_KERBEROS
|
||||
use the following instead:
|
||||
|
||||
# db_dump185-5 /var/heimdal/heimdal.db | db_load-5 /var/heimdal/heimdal.db.new
|
||||
# chown 0600 /var/heimdal/heimdal.db.new
|
||||
# mv /var/heimdal/heimdal.db.new /var/heimdal/heimdal.db
|
||||
|
||||
db_dump and db_load utilitites are installed by database/db5 as
|
||||
dependency of security/heimdal.
|
||||
|
||||
If you want to switch from security/heimdal to Heimdal in the base
|
||||
system, use the following:
|
||||
|
||||
# /usr/local/sbin/kadmin -l dump /var/heimdal/heimdal.db.dump
|
||||
# rm /var/heimdal/heimdal.db
|
||||
# /usr/bin/kadmin -l load /var/heimdal/heimdal.db.dump
|
||||
# rm /var/heimdal/heimdal.db.dump
|
||||
|
||||
20161105:
|
||||
AFFECTS: users of security/heimdal
|
||||
AUTHOR: hrs@FreeBSD.org
|
||||
|
|
|
|||
Loading…
Reference in New Issue