forked from opnsense/ports
-
Notifications
You must be signed in to change notification settings - Fork 0
/
UPDATING
17822 lines (13155 loc) · 597 KB
/
UPDATING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
This file documents some of the problems you may encounter when upgrading
your ports. We try our best to minimize these disruptions, but sometimes
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.
20200204:
AFFECTS: users of editors/vim
AUTHOR: [email protected]
The PYTHON2 and PYTHON3 options have been turned into a single PYTHON
option that uses whichever python you've set as default. However,
this means that you cannot have both python2 and python3 support at
the same time.
20200126:
AFFECTS: users of multimedia/gstreamer1-plugins[-bad]
AUTHOR: [email protected]
In GStreamer 1.16 some files moved from the gstreamer1-plugins-bad package
to the gstreamer1-plugins package.
If your using a tool like portmaster or portupgrade delete the old -bad
port and then follow the normal upgrade method.
# pkg delete -f gstreamer1-plugins-bad
20200126:
AFFECTS: users of sysutils/helm
AUTHOR: [email protected]
The Helm project have deprecated the Tiller utility in Helm 3. If you are using
Helm 2 you will need to migrate the configuration to be compatible with Helm 3.
Please, refer to the following documentation for more information about the
migration process:
https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
Note that the 2to3 plugin binary is not available for FreeBSD and you will need
to compile it yourself.
20200113:
AFFECTS: users of python and net/samba410, devel/talloc, devel/tevent, databases/tdb, databases/ldb*
AUTHOR: [email protected]
In the entry 20191216 for the Python update the filtering constrains
are too limiting and omit the Samba supplimentary libraries, which do
have Python bindings to the default Python 3.x version. With the update
of the default Python3 version you also need to rebuild all the
supplimentary Samba libraries and samba410 itself.
For portmaster users it would be enough to run:
# portmaster devel/talloc devel/tevent databases/tdb databases/ldb15 net/samba410
20200109:
AFFECTS: www/firefox
AUTHOR: [email protected]
Firefox requires Capsicum since r522464 for IPC and in future will
require Capsicum for process sandboxing. If you use a custom kernel
make sure to copy the following lines from GENERIC kernel:
options CAPABILITY_MODE # Capsicum capability mode
options CAPABILITIES # Capsicum capabilities
20200107:
AFFECTS: Users of *-emacs27-* packages
AUTHOR: [email protected]
There is a major version bump in 28.0.50, therefore to upgrade all the
packages dependent on editors/emacs-devel, please use the following commands:
# sh
# for i in $(pkg query -g %n '*-emacs27*'); do \
nn=$(echo "$i" | sed -e 's/emacs27/emacs28/'); \
pkg set -yn "$i":"$nn"; done;
# pkg upgrade
20200106:
AFFECTS: users of net/gnatsd
AUTHOR: [email protected]
net/gnatsd has been replaced by net/nats-server to reflect the
new naming upstream.
All options in rc.conf should be renamed by replacing 'gnats'
with 'nats' (nats_enable, nats_user, nats_options).
20200101:
AFFECTS: users of security/openssl and security/openssl111
AUTHOR: [email protected]
The openssl port was removed on 2019-12-31, subsequently the openssl111
port was renamed to openssl on 2020-01-01.
The shared library version of OpenSSL has been bumped.
Users of DEFAULT_VERSIONS= ssl=openssl111 must update this to
ssl=openssl.
You must rebuild all ports that depend on OpenSSL if you use OpenSSL
from ports.
20191226:
AFFECTS: users of sysutils/dsbmd
AUTHOR: [email protected]
With version 1.10 dsbmd now uses sysutils/fusefs-jmtpfs for mounting
MTP devices. Please adjust your dsbmd.conf or recreate it from the new
dsbmd.conf.sample.
20191225:
AFFECTS: multimedia/libva-intel-media-driver
AUTHOR: [email protected]
As of libva 2.6.0 iHD driver is automatically enabled, so you no
longer need to adjust LIBVA_DRIVER_NAME in ~/.profile or ~/.login.
20191221:
AFFECTS: users of misc/openhab2
AUTHOR: [email protected]
If you upgrade from a pevious version, make a backup of
/var/db/openhab2
read about the breaking changes in the release notes at
https://github.com/openhab/openhab-distro/releases/tag/2.5.0
and run
%%PREFIX%%/libexec/openhab2/runtime/bin/update.freebsd
which takes care about changes for:
- Textual Configuration
- Next Generation Rule Engine
20191216:
AFFECTS: users of python
AUTHOR: [email protected]
Default version of python3 and python was switched to 3.7.
For ports users wanting to keep version 3.6 as default,
add DEFAULT_VERSIONS+= python=3.6 python3=3.6 to make.conf
This may ease the upgrade for users of pre-build packages:
# sh
# for i in $(pkg query -g %n 'py36-*'); do pkg set -yn ${i}:py37-${i#py36-}; done
# pkg upgrade
For portmaster users:
# portmaster -o lang/python37 python36
# REINSTALL="$(pkg info -o py36-\* | awk '{printf "%s ", $2}')"
# pkg delete -f py36-\*
# portmaster $REINSTALL
# REBUILD=$(pkg query -g "%n:%dn" '*' | grep py3 | grep -v py37 | cut -d : -f 1 | sort -u)
# portmaster $REBUILD
# REBUILD2=$(pkg list | grep python-36 | xargs pkg which | awk '{print $6}' | sort -u)
# portmaster $REBUILD2
20191204
AFFECTS: users of mail/nextcloud-mail
AUTHOR: [email protected]
Version 0.20.0 removed the default mail configuration via config.php.
All users will be prompted to enter account and SMTP- and IMAP-server
details for sending and reading email.
20191126:
AFFECTS: consumers of net/py-urllib3
AUTHOR: [email protected]
Since version 1.25 HTTPS connections are now verified by default which is
done via "cert_reqs = 'CERT_REQUIRED'". While certificate verification
can be disabled via "cert_reqs = 'CERT_NONE'", it's highly recommended to
leave it on.
Various consumers of net/py-urllib3 already have implemented routines that
either explicitly enable or disable HTTPS certificate verification (e.g.
via configuration settings, CLI arguments, etc.).
Yet it may happen that there are still some consumers which don't
explicitly enable/disable certificate verification for HTTPS connections
which could then lead to errors (as is often the case with self-signed
certificates).
In case of an error one should try first to temporarily disable
certificate verification of the problematic urllib3 consumer to see if
this approach will remedy the issue.
20191125:
AFFECTS: users of emulators/qemu
AUTHOR: [email protected]
emulators/qemu31 has been updated to 4.1.1. Previous 3.1.X branch has
been repocopied to emulators/qemu31. If someone wants to stick with 3.1.X
branch please use one of the following command:
# pkg install emulators/qemu31
or
# portmaster -o emulators/qemu31 emulators/qemu
or
# portupgrade -o emulators/qemu31 emulators/qemu
20191124:
AFFECTS: users of irc/eggdrop
AUTHOR: [email protected]
The irc/eggdrop port has been updated to 1.8.4 and its config is not
backward compatible with 1.6.21. A new port was created to keep 1.6.21
version available at irc/eggdrop16 and it will be available for 3 months
until users have time to upgrade their configuration.
More information at:
https://raw.githubusercontent.com/eggheads/eggdrop/v1.8.4/NEWS
If you would like to keep using 1.6.21, please run the following command
to update pkg database:
pkg set -n eggdrop:eggdrop16
pkg set -o irc/eggdrop:irc/eggdrop16
20191108:
AFFECTS: users of databases/redis[-devel]
AUTHOR: [email protected]
The databases/redis port has been updated to the recent stable release.
Users wanting to stay on v4.x can replace databases/redis with
databases/redis4 with one of the following commands:
# pkg install databases/redis4
or
# portmaster -o databases/redis4 databases/redis
or
# portupgrade -o databases/redis4 databases/redis
20191103:
AFFECTS: users of www/node
AUTHOR: [email protected]
The www/node port has been updated to Node.js v13.0.0, the latest
upstream release. A new port, www/node12, has been created for the
v12.x LTS branch. Users wanting to stay on v12.x can replace www/node
with www/node12 with one of the following commands:
# pkg install www/node12
or
# portmaster -o www/node12 www/node
or
# portupgrade -o www/node12 www/node
20191029:
AFFECTS: users of emulators/open-vm-tools[-nox11]
AUTHOR: [email protected]
open-vm-tools 11.0.1 has removed the vmxnet driver. This driver has been
in tree for quite some time and hopefully everyone is using the in tree
version, however if you had removed device vmx from your kernel, or are
running an unsupported version of FreeBSD which didn't have the driver
included in the base system, updating your open-vm-tools version will
leave you without networking.
20191026:
AFFECTS: users of www/qt5-webengine
AUTHOR: [email protected]
Users that upgrade www/qt5-webengine without using pkg/poudriere might
experience failures due to conflicts with the installed version of 5.12.2.
In that case, pkg delete -f the qt5-webengine package before building
the updated version.
20191025:
AFFECTS: users of x11/nvidia-driver (and slave ports)
AUTHOR: [email protected]
x11/nvidia-driver* ports no longer install Linux programs and libraries,
which had been moved to their own ports (x11/linux-nvidia-libs*). When
updating the driver package next time, remember to install them manually
if you need to run Linux OpenGL programs.
20191016:
AFFECTS: users of KDE Plasma Desktop (x11/plasma5*)
AUTHOR: [email protected]
With Plasma 5.17 the startup script has been renamed. People who use the
.xinitrc method to start Plasma have to call the new binary.
Previously:
exec ck-launch-session startkde
Change to:
exec ck-launch-session startplasma-x11
20191014:
AFFECTS: users of mail/rspamd, mail/rspamd-devel
AUTHOR: [email protected]
Sample configuration files has been removed as default configuration files
are NOT intended for modification by users and SHOULD be overwritten on
port upgrade.
Make sure the default configuration files are unmodified and migrate all
configuration changes to the proper places, before you continue.
20191002:
AFFECTS: users of textproc/groff
AUTHOR: [email protected]
with groff 1.2.4_3, groff does not depend anymore on ghostscript and
netpbm. In order to be able to properly use the html backend the user
can install ghostscript and netpbm from ports without the need of
reinstalling the package.
Also note that the X11 option has been removed.
20190930:
AFFECTS: users of net-mgmt/netbox
AUTHOR: [email protected]
Since the 2.6 release a running Redis server instance is required for
caching objects to run. Also the following settings like below need to be
added (or modified) in the existing configuration.py:
REDIS = {
'HOST': 'localhost',
'PORT': 6397,
'PASSWORD': ''
'DATABASE': 0,
'CACHE_DATABASE': 1,
'DEFAULT_TIMEOUT': 300,
'SSL': False,
}
Note that if you were using these settings in a prior release with
webhooks, the DATABASE setting remains the same but an additional
CACHE_DATABASE settings has been added with a default value of 1 to
support the caching backend.
The DATABASE setting will be renamed in a future release of NetBox to
better relay the meaning of the setting. It is highly recommended to keep
the webhook and cache databases separate. Using the same database number
for both may result in webhook processing data being lost during cache
flushing events.
Please also check the pkg-message and the changelogs for further info.
20190927:
AFFECTS: users of emulators/qemu-devel
AUTHOR: [email protected]
qemu-devel has been updated to 4.1.0 and 4.0.0 has been merged into a new port
emulators/qemu40. If you want to stick with 4.0.X branch, simply use:
# portmaster -o emulators/qemu-devel emulators/qemu40
20190927:
AFFECTS: users of XFCE desktop (x11-wm/xfce4)
AUTHOR: [email protected]
Due to changes in the XFCE 4.14 metaport, systems could end up with
both xscreensaver and xfce4-screensaver installed and enabled
simultaneously.
This can cause conflicts and problems unlocking the screen.
To avoid problems, please make sure to have only one enabled by
going to the Application Autostart tab of the Session and Startup
settings applet and enable only one Screensaver there.
Some further information can be found in the xfce4-session
pkg-message displayed on installation and upgrade.
20190920:
AFFECTS: users of net-mgmt/pushgateway
AUTHOR: [email protected]
The persistent storage format used by pushgateway in the latest version
is not backwards compatible. See the pushgateway changelogs for details.
20190911:
AFFECTS: users of security/bastillion
AUTHOR: [email protected]
The datastore of bastillion needs to be updated:
java -jar $PREFIX/jetty_bastillion/upgrade/bastillion-upgrade-3.08.00.jar \
$PREFIX/jetty_bastillion/bastillion/WEB-INF/classes/BastillionConfig.properties
20190909:
AFFECTS: users of lang/ruby25
AUTHOR: [email protected]
The default ruby version has been updated from 2.5 to 2.6.
If you compile your own ports you may keep 2.5 as the default version by
adding the following lines to your /etc/make.conf file:
#
# Keep ruby 2.5 as default version
#
DEFAULT_VERSIONS+=ruby=2.5
If you wish to update to the new default version, you need to first stop any
software that uses ruby. Then, you will need to follow these steps, depending
upon how you manage your system.
If you use pkgng, simply upgrade:
# pkg upgrade
If you do not use pkg, please check entry 20190420.
The description there should also work for this version.
20190906:
AFFECTS: users of devel/py-fabric
AUTHOR: [email protected]
Fabric (devel/py-fabric) was upgraded to 2.5.0, Fabric (2+) represents
a near-total reimplementation and reorganization of the software.
Fabric 2 is not at 100% feature parity with 1.x! Some features have been
explicitly dropped, but others simply have not been ported over yet,
either due to time constraints or because said features need to be
re-examined in a modern context.
More information at:
https://www.fabfile.org/upgrading.html#upgrading
https://www.fabfile.org/upgrading.html#upgrade-specifics
If you would like to keep using 1.x, please run the following command to
update pkg database:
pkg set -n py27-fabric:py27-fabric1
pkg set -o devel/py-fabric:devel/py-fabric1
20190830:
AFFECTS: users of www/gitlab-ce
AUTHOR: [email protected]
Make sure you upgrade your PostgreSQL to version 11 as described in 20190829,
before you upgrade your gitlab-ce version.
Gitlab-ce 12.1 needs at least PostgreSQL version 9.6.
After this you can follow the usual upgrade guide:
https://gitlab.fechner.net/mfechner/Gitlab-docu/blob/master/update/12.0-12.1-freebsd.md
20190829:
AFFECTS: users of database/postgresql* and other software using PostgreSQL to run
AUTHOR: [email protected]
The default version of PostgreSQL has been switched from 9.5 to 11.
The upgrade procedure can use up twice the space the databases
currently needs. If you have a big amount of stored data take a
closer look at the manpage of pg_upgrade for avoidance and/or
speedup of the upgrade.
The upgrade instructions consider a basic usage and do not match
complex scenarios like replication, sharding, or similar.
Upgrade instructions:
First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
If you have another Version of PostgreSQL installed, for example 9.5.19, your
files are named according to this.
# service postgresql stop
# pkg create postgresql95-server postgresql95-contrib
# mkdir /tmp/pg-upgrade
# tar xf postgresql95-server-9.5.19.txz -C /tmp/pg-upgrade
# tar xf postgresql95-contrib-9.5.19.txz -C /tmp/pg-upgrade
# pkg delete -f databases/postgresql95-server databases/postgresql95-contrib databases/postgresql95-client
Now update PostgreSQL:
pkg user:
# pkg install databases/postgresql11-server databases/postgresql11-contrib
# pkg upgrade
Portmaster users:
# portmaster databases/postgresql11-server databases/postgresql11-contrib
# portmaster -a
Portupgrade users:
# portinstall databases/postgresql11-server databases/postgresql11-contrib
# portupgrade -a
After installing the new PostgreSQL version you need to convert
all your databases to new version:
# su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data11 -U pgsql"
# chown -R postgres /usr/local/pgsql/data/
# su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /usr/local/pgsql/data/ -B /usr/local/bin/ -D /var/db/postgres/data11/ -U pgsql "
Now the migration is finished. You can start PostgreSQL again with:
# service postgresql start
ATTENTION:
1) The default user changed from "pgsql" to "postgres". The migration steps above preserve
the "pgsql" database user while the database daemon is now executed as the "postgres" FreeBSD user.
2) The default data dir changed from "/usr/local/pgsql/data/" to "/var/db/postgres/data11/"
3) If you use non-default initdb options, you have to adjust the initdb-command accordingly
20190816:
AFFECTS: users of net-im/ejabberd
AUTHOR: [email protected]
Riak support has been removed by upstream. For update instructions from
19.05, please refer to:
https://docs.ejabberd.im/admin/upgrade/from_19.05_to_19.08/
20190812:
AFFECTS: users of lang/perl5*
AUTHOR: [email protected]
The default Perl version has been switched to Perl 5.30. If you are using
binary packages to upgrade your system, you do not have anything to do, pkg
upgrade will do the right thing. For the other people, follow the
instructions in entry 20161103, it should still be the same.
20190801:
AFFECTS: users of www/ot-recorder
AUTHOR: [email protected]
The data directory has moved from /var/spool/owntracks to
/var/db/owntracks
Be sure to stop otrecorder, move the directory, and start otrecorder.
service ot-recorder stop
cd /var/spool
mv owntracks /var/db
service ot-recorder start
20190728:
AFFECTS: users of net-im/py-matrix-synapse
AUTHOR: [email protected]
The support for Python 2.7 has been dropped with the 1.1.0 release of
net/py-matrix-synapse.
Users that still use the Python 2.7 version of net-im/py-matrix-synapse
should switch to a newer Python version, e.g. 3.6, which is the default
Python version since April 2019.
20190717:
AFFECTS: users of net-p2p/zetacoin and net-p2p/zetacoin-nox11
AUTHOR: [email protected]
Zetacoin will default to using modern versions of BDB (5.x or 6.x) when
the WALLET option is selected. See pkg-help for explanation.
The zetacoin-nox11 slave port was renamed to zetacoin-daemon to align
with the net-p2p/bitcoin format.
The zetacoin-cli and zetacoin-tx utilities have been re-packaged into
a separate port. If you require these programs, or use the zetacoin-cli
program to access the daemon or the GUI, install net-p2p/zetacoin-utils
to reinstall them.
20190717:
AFFECTS: users of sysutils/py-borgmatic
AUTHOR: [email protected]
The default location for borgmatic's configurations changed. We moved it
from '/etc/borgmatic' to '/usr/local/etc/borgmatic' in order to follow
recommended standards used on FreeBSD.
20190710:
AFFECTS: users with DEFAULT_VERSIONS+=linux=c6 or c6_64 in /etc/make.conf
AUTHOR: [email protected]
On amd64 adding DEFAULT_VERSIONS+=linux=c6 to /etc/make.conf made Linux
infrastructure ports (linux_base-c6 and linux-c6*) install i386 CentOS 6
packages. Using c6_64 instead of c6 made them install mixed amd64/i386
CentOS 6 packages and allowed Linux application ports to install amd64
binaries when available. The i386-only configuration was only useful for
users of x11/nvidia-driver* which didn't provide Linux amd64 emulation
until recently.
With x11/nvidia-driver* now supporting Linux amd64 there's no longer a
need for i386-only Linux on amd64 so DEFAULT_VERSIONS+=linux=c6 has been
changed to make Linux infrastructure ports install mixed amd64/i386
CentOS 6 packages, like c6_64 before, and support for c6_64 has been
removed.
Users with DEFAULT_VERSIONS+=linux=c6 should reinstall linux_base-c6 and
all packages that depend on it. A list of dependent packages can be
obtained with the following command:
pkg info -r linux_base-c6
Users with DEFAULT_VERSIONS+=linux=c6_64 only need to replace c6_64 with
c6 in /etc/make.conf.
Users of x11/nvidia-driver* should upgrade to FreeBSD 11.3 or 12.0 if
they want to run Linux amd64 OpenGL programs. If you are running an
older version you may want to postpone installing or updating Linux
application ports until you find the time to upgrade because application
ports may install amd64 binaries now. Infrastructure ports are safe to
reinstall, and so is x11/nvidia-driver*.
On i386 nothing has changed.
20190707:
AFFECTS: users of www/gitlab-ce
AUTHOR: [email protected]
You must at first upgrade to version 11.11.5 before you can upgrade
to version 12.
Support for MySQL will be dropped with next version.
Make sure you use at least PostgreSQL version 9.6.
Follow the normal upgrade manual that can be found here:
https://gitlab.fechner.net/mfechner/Gitlab-docu/blob/master/update/11.11-12.0-freebsd.md
20190705:
AFFECTS: users of net/serviio which bought a license for the non-free features
AUTHOR: [email protected]
Version 2 of serviio needs a new license file. Updating without a new license
file will disable the non-free features.
20190701:
AFFECTS: users of databases/mysql56-(server|client)
AUTHOR: [email protected]
The default MySQL version has been updated from 5.6 to 5.7.
If you compile your own ports you may keep 5.6 as the default version by
adding the following lines to your /etc/make.conf file:
#
# Keep MySQL 5.6 as default version
#
DEFAULT_VERSIONS+=mysql=5.6
If you wish to update to the new default version, you need to first stop any
running server instance. Then, you will need to follow these steps, depending
on installed packages.
# pkg set -o databases/mysql56-client:databases/mysql57-client
# pkg set -o databases/mysql56-server:databases/mysql57-server
# pkg upgrade
20190630:
AFFECTS: users of net/samba410
AUTHOR: [email protected]
If you used Samba in AD/DC mode with the previous versions of the port on UFS2
backed storage you have to add usage of vfs_freebsd VFS module for at least
SYSVOL share and configure it to use 'legacy' mode(see manpage).
The reason behind this is that previous versions Samba port used a hack to
workaround broken mapping of Linux security and trusted extended attributes
into FreeBSD namespace. In particular, essential security.NTACL attribute
was replaced with the user.NTACL and placed in a insecure USER namespace.
This port dropped this hack in favor of vfs_freebsd module, which should
provide more controlled way of such a mapping.
To maintain the compatibility with the previous installations on UFS2 storage
(as ZFS uses it's own way of mapping SYSVOL, thanks to the iXsystems patches)
the vfs_freebsd module provides 'legacy' mode that implements old functionality.
For the fresh installations it is recommended to use 'secure' mode of operations
for this module and use it as a global vfs objects.
Caution: The given module is still considered EXPERIMENTAL.
20190630:
AFFECTS: users of net/samba410, net/samba4[6-8] and devel/talloc?, devel/tevent?, databases/tdb?, databases/ldb*
AUTHOR: [email protected]
The port of the new version of Samba 4.10 is introduced. Due necessarily
to keep backwards compatibility for the legacy samba4[6-8] ports the
upgrade procedure is a bit convoluted.
You are safe to perform fresh new install of samba410 port. In case you
are upgrading from the previous versions of Samba, please use the
following procedure:
0. Take backups of all the relevant files, in particular PREFIX/etc/smb4.conf
and /var/db/samba4/ subdirectory. Keep in mind that files there (may)
have extended attributes, so use appropriate tools to preserve them.
1a. If you haven't updated Samba between 20190619 and 20190630 then next
step should be as simple as:
portmaster -o net/samba410 net/samba48
1b. If you have been affected by the archiving legacy versions of
Samba-related libraries for legacy versions of Samba, which happened
in the given time frame, then you need to reverse operation from the
20190619 entry:
for users of portmaster:
portmaster -o devel/talloc devel/talloc1
portmaster -o devel/tevent devel/tevent1
portmaster -o databases/tdb databases/tdb1
portmaster -o net/samba410 net/samba48
for users of portupgrade:
portupgrade -o devel/talloc devel/talloc1
portupgrade -o devel/tevent devel/tevent1
portupgrade -o databases/tdb databases/tdb1
portupgrade -o net/samba410 net/samba48
20190619:
AFFECTS: users of samba4[6-8] and devel/talloc, devel/tevent, databases/tdb, databases/ldb*
AUTHOR: [email protected]
To introduce samba410(we deliberately skip samba49 due the complexity of handling)
and to drop dependency on deprecated Python 2.7, Samba supplementary libraries
talloc, tevent and tdb were split into current Python 3 compatible versions
and legacy ones, with the suffix "1".
Old versions of Samba were changed to depend on the legacy supplementary libraries,
so if you need to install samba46, samba47 or samba48 over previous Samba
installations you need to downgrade supplementary libs with the following commands:
for users of portmaster:
portmaster -o devel/talloc1 devel/talloc
portmaster -o devel/tevent1 devel/tevent
portmaster -o databases/tdb1 databases/tdb
portmaster -r talloc1
for users of portupgrade:
portupgrade -o devel/talloc1 devel/talloc
portupgrade -o devel/tevent1 devel/tevent
portupgrade -o databases/tdb1 databases/tdb
portupgrade -fr devel/talloc1
20190613:
AFFECTS: users of www/qt5-webengine
AUTHOR: [email protected]
Users that upgrade www/qt5-webengine without using pkg/poudriere might
experience failures due to conflicts with the installed version of 5.12.2.
In that case, pkg delete -f the qt5-webengine package before building
the updated version.
20190611:
AFFECTS: users of net/routinator
AUTHOR: [email protected]
Release 0.4.0 fundamentally changes the command line options for
running the server and introduces a new way to initialize the local RPKI
repository used by Routinator.
If you have been using previous releases, you will likely have to adjust
your tooling. We apologize for this, but we also feel that the new commands
are more intuitive and logical.
20190604:
AFFECTS: users of net/samba47
AUTHOR: [email protected]
The default version of samba has been switched from 4.7 to 4.8.
Upgrade instructions:
For package users having samba47 installed indirectly (as a dependency):
# pkg upgrade
For package users having samba47 installed directly (leaf port):
# pkg upgrade
# pkg install samba48
For ports users:
If you want to keep samba47, add DEFAULT_VERSIONS+= samba=4.7 to make.conf
If you want to upgrade to samba48, remove samba47:
# pkg delete -f samba47
Portmaster users:
# portmaster net/samba48
# portmaster -a
Portupgrade users:
# portinstall net/samba48
# portupgrade -a
20180601:
AFFECTS: www/tt-rss
AUTHOR: [email protected]
tt-rss now uses php intl for extension; a web server reload
will be required if intl extension isn't already loaded.
20190522:
AFFECTS: users of sysutils/graylog
AUTHOR: [email protected]
The port has been updated to the latest stable version 3.0.2, which
includes more plugins by default, but also requires manual changes to
graylog's configuration files, possibly port and URL changes, such as
X-Graylog-Server-URL settings, and elasticsearch must be >= 5.
The location of configuration files has been amended to align with the
official distribution files and locations.
After upgrading, manually review and merge changes from your
/usr/local/etc/graylog/server/server.conf into
/usr/local/etc/graylog/graylog.conf
Consult https://www.graylog.org/post/announcing-graylog-v3-0-ga for
further details.
20190506:
AFFECTS: users of www/gitea
AUTHOR: [email protected]
Gitea requires the addition of another secret to the config file in order
to start up. Either manually add JWT_SECRET to the
${PREFIX}/etc/gitea/conf/app.ini config file (see app.ini.sample), or allow
Gitea to make the change for you by making the config file writable to the
git user.
20190424:
AFFECTS: users of www/node
AUTHOR: [email protected]
The www/node port has been updated to Node.js v12.0.0, the latest
upstream release. This is a major release, including many significant
changes. Users are encouraged to read the release announcements before
upgrading:
https://nodejs.org/en/blog/release/v12.0.0/
20190423:
AFFECTS: users of www/gitlab-ce
AUTHOR: [email protected]
The directory where all repositories and ssh permissions are stored
was changed from /usr/home/git back to /usr/local/git, to match again the
recommended standards on FreeBSD.
This will cause now some other git management packages to collide with
gitlab. Make sure you migrate all you git repositories to gitlab first,
before you continue.
Make sure /usr/local/git/repositories and /usr/local/git/.ssh are not
existing!
Otherwise the next commands can break your installation for managing
git repositories within gitlab and with your other gitlab management
software!
You must move the old files to the new location with:
# service gitlab stop
# mv /usr/home/git /usr/local/
# pkg upg
Make sure you update your config files, diff shows you what you maybe
must change:
# cd /usr/local/www/gitlab-ce
# git diff config/gitlab.yml.sample config/gitlab.yml
# cd /usr/local/share/gitlab-shell/
# git diff config.yml.sample config.yml
# cd /usr/local/share/gitaly
# git diff config.toml.sample config.toml
# Change home directory of user git back to /usr/local/git
# vipw
The line should now looks like:
git:*:211:211::0:0:gitosis user:/usr/local/git:/bin/sh
If you do an upgrade of gitlab follow the upgrade guide.
If not, just start gitlab again with:
# service gitlab start
20190422:
AFFECTS: users of security/libressl
AUTHOR: [email protected]
The port has been updated to the latest stable version 2.9 of LibreSSL.
The shared library versions of the libraries have been bumped.
After upgrading, manually update all packages that depend on any of the
libraries provided by LibreSSL (libssl, libcrypto and libtls) since the
versions of these libraries have changed. Normally, you can obtain the
list of dependent software by running the following command:
# pkg info -r libressl
Then you should rebuild all ports depending on libressl to avoid dangling
shared library dependencies. Poudriere and pkg handle this correctly,
portmaster and portupgrade users can use the following to rebuild all
dependent ports.
Portmaster users:
portmaster -r libressl
Portupgrade users:
portupgrade -fr security/libressl
20190421:
AFFECTS: users of databases/cego
AUTHOR: [email protected]
To upgrade from cego 2.39.16 to 2.44.1, you need to export to xml before
the upgrade and import from xml after the upgrade, because the internal
storage has changed for some types.
Use these steps:
- export your database while it runs, see
http://www.lemke-it.com/litexec?request=pubcegodoc&user=&lang=en§ion=cgdoc_database_running.html#tsimpexp_mode
for details.
- stop the database
service cego stop
- upgrade the port/package
- re-create the database
cego --mode=create --tableset=<database> --dbxml=<database>.xml
- import the database
cego --mode=xmlimport --tableset=<database> \
--dbxml=<database>.xml --impfile=export.xml --doLogging
- modify /etc/rc.conf by adding
cego_<database>_cpdump="YES"
cego_<database>_cleanup="YES"
- start the database
service cego start
20190420:
AFFECTS: users of lang/ruby24
AUTHOR: [email protected]
The default ruby version has been updated from 2.4 to 2.5.
If you compile your own ports you may keep 2.4 as the default version by
adding the following lines to your /etc/make.conf file:
#
# Keep ruby 2.4 as default version
#
DEFAULT_VERSIONS+=ruby=2.4
If you wish to update to the new default version, you need to first stop any
software that uses ruby. Then, you will need to follow these steps, depending
upon how you manage your system.
If you use pkgng, simply upgrade:
# pkg upgrade
If you use portmaster, install new ruby, then rebuild all ports that depend
on ruby:
# portmaster -o lang/ruby25 lang/ruby24
# portmaster -R -r ruby-2.5
If you use portupgrade, install new ruby, then rebuild all ports that depend
on ruby:
# pkg delete -f ruby portupgrade
# make -C /usr/ports/ports-mgmt/portupgrade install clean
# pkg set -o lang/ruby24:lang/ruby25
# portupgrade -x ruby-2.5.\* -fr lang/ruby25
20190419:
AFFECTS: users of emulators/qemu
AUTHOR: [email protected]
qemu 2.X version has been moved to qemu2. If you would like to use
2.X you should use qemu2. Otherwise you can use the new stable
upstream branch of 3.0.X.
Portmaster users will need to run this command:
portmaster -o emulators/qemu2 emulators/qemu
20190410:
AFFECTS: users of python
AUTHOR: [email protected]
Default version of python was switched to 3.6.
For ports users wanting to keep version 2.7 as default,
add DEFAULT_VERSIONS+= python=2.7 to make.conf
20190328:
AFFECTS: www/firefox-i18n, www/firefox-esr-i18n, mail/thunderbird-i18n, www/seamonkey-i18n
AUTHOR: [email protected]
Separate packages for localization packs are no longer supported.
Firefox 65+ has in-browser menu while Firefox ESR60, Thunderbird 60
or SeaMonkey 2.49 should download preferred .xpi manually. Refer to
the following article (including previous revisions) how to do this.
https://support.mozilla.org/kb/use-firefox-another-language
20190328:
AFFECTS: users of www/qt5-webengine
AUTHOR: [email protected]
Users that upgrade www/qt5-webengine without using pkg/poudriere might
experience failures due to conflicts with the installed version of 5.9.5.
In that case, pkg delete -f the qt5-webengine package before building
the updated version.
20190314:
AFFECTS: users of mail/rspamd, mail/rspamd-devel
AUTHOR: [email protected]
User and group that rspamd run as are changed from nobody:nobody to
rspamd:rspamd. Unless it is clean install you need to execute following
command.
# chown -R rspamd:rspamd /var/db/rspamd /var/log/rspamd /var/run/rspamd