forked from pfsense/FreeBSD-ports
-
Notifications
You must be signed in to change notification settings - Fork 0
/
UPDATING
14722 lines (10843 loc) · 490 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.
20170628:
AFFECTS: users of www/node
AUTHOR: [email protected]
The www/node port has been updated to Node.js v8.1.2, 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/v8.0.0/
https://nodejs.org/en/blog/release/v8.1.0/
20170626:
AFFECTS: users of net-mgmt/zabbix24*
AUTHOR: [email protected]
Zabbix 2.4 has reached end of life and net-mgmt/zabbix24* ports have been
removed. Users that have not yet moved to a newer version, should use now
net-mgmt/zabbix3-* (LTS release) or net-mgmt/zabbix32-* (Standard release).
See more info about Zabbix releases here:
http://www.zabbix.com/life_cycle_and_release_policy
20170624:
AFFECTS: users of mail/dcc-dccd
AUTHOR: [email protected]
The ALT_HOME option was removed in 1.3.159_1. If this option is being
used, please be sure to move the old home directory, /var/dcc to
${PREFIX}/dcc.
20170624:
AFFECTS: users of net/rabbitmq
AUTHOR: [email protected]
The rabbitmq-3.6.10_1 port has been changed to use version 19 of
the Erlang runtime, because RabbitMQ is not yet compatible with
version 20.
Upgrades to the previous rabbitmq-3.6.10 must be avoided as
they can lead to data corruption due to changes in Erlang 20.
20170622:
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.3 to 9.5.
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 scenarious 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.3.12, your
files are named accourding to this.
# service postgresql stop
# pkg create postgresql93-server postgresql93-contrib
# mkdir /tmp/pg-upgrade
# tar xf postgresql93-server-9.3.17.txz -C /tmp/pg-upgrade
# tar xf postgresql93-contrib-9.3.17.txz -C /tmp/pg-upgrade
# mv /usr/local/pgsql/data /usr/local/pgsql/data93
# pkg delete -f databases/postgresql93-server databases/postgresql93-contrib databases/postgresql93-client
Now update PostgreSQL:
pkg user:
# pkg install databases/postgresql95-server databases/postgresql95-contrib
# pkg upgrade
Portmaster users:
# portmaster databases/postgresql95-server databases/postgresql95-contrib
# portmaster -a
Portupgrade users:
# portinstall databases/postgresql95-server databases/postgresql95-contrib
# portupgrade -a
After installing the new PostgreSQL version you need to convert
all your databases to new version:
# service postgresql initdb
# su -l pgsql -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /usr/local/pgsql/data93/ -B /usr/local/bin/ -D /usr/local/pgsql/data/"
Now the migration is finished. You can start PostgreSQL again with:
# service postgresql start
20170614:
AFFECTS: users of editors/calligra
AUTHOR: [email protected]
Calligra has been updated to 3.0.1, which is a KDE Frameworks 5 (KF5)
based application. Calligra now uses Qt5 and KF5. The translations have
been merged (upstream) into the application, so separate language /
translation ports are no longer provided. Krita has been split out
(upstream) into a separate application, which is packaged as
graphics/krita. Kexi, the visual database applications creator,
is packaged separately as databases/kexi.
Users of Calligra are encouraged to install Krita and Kexi separately,
and to report issues with the upgrade to kde@.
20170613:
AFFECTS: users of net-im/ejabberd
AUTHOR: [email protected]
After update to 17.04, there is an issue[1] expected with S2S connections,
which can be resolved by adding 'mod_s2s_dialback: {}' to 'modules' section
of configuration file.
[1] - https://github.com/processone/ejabberd/issues/1700
20170603:
AFFECTS: users of www/kanboard
AUTHOR: [email protected]
After update to 1.0.44, there are following breaking changes:
* Move calendar to external plugin: https://github.com/kanboard/plugin-calendar
* Move Gantt charts to external plugin: https://github.com/kanboard/plugin-gantt
* Move Gravatar to external plugin: https://github.com/kanboard/plugin-gravatar
20170602:
AFFECTS: users of Qt 5 in presence of binutils
AUTHOR: [email protected]
gold linker from binutils 2.28 may produce duplicate library
symbols, which makes shared libraries created with it not usable
with conventional ld linker.
This affects Qt, as qt5-qmake will detect gold and use it to build
Qt libraries. Broken libQt5Core will be produced and ports which
depend on it will then fail to link with the following errors:
...lib/libQt5Core.so:(.dynamic+0x27ac8): multiple definition of `__bss_start at Qt_5'
...lib/libQt5Core.so:(.dynamic+0x27ac8): first defined here
...lib/libQt5Core.so:(.dynamic+0x27ac8): multiple definition of `_edata at Qt_5'
...lib/libQt5Core.so:(.dynamic+0x27ac8): first defined here
...lib/libQt5Core.so:(.dynamic+0x2b2d0): multiple definition of `_end at Qt_5'
Qt5 was fixed to ignore gold. If you see these errors, you
need to rebuild qt5-qmake, then all qt5-* ports.
20170529:
AFFECTS: users of sysutils/dsbmd
AUTHOR: [email protected]
Due to new configuration variables and semantic changes, users of dsbmd
version 0.2 and earlier should consider recreating their dsbmd.conf from
the new dsbmd.conf.sample.
20170518:
AFFECTS: users of www/yarn
AUTHOR: [email protected]
The default node backend for yarn has switched to www/node. Binary
package users should expect the node backend to be switched during
the upgrade. To keep the node6 (LTS) backend, rebuild www/yarn with
the NODE6 backend option enabled.
20170517:
AFFECTS: users of security/pecl-ssh2
AUTHOR: [email protected]
The security/pecl-ssh2 has been upgraded to version 1.0, and the new
version is not compatible with PHP5. If you need PHP5 support, you can
find version 0.13 in security/pecl-ssh2-0.
20170412:
AFFECTS: users of sysutils/ansible
AUTHOR: [email protected]
The default value for ansible_python_interpreter has been changed
to match the upstream /usr/bin/python. If managing FreeBSD systems,
adjust the hosts database to explicitly set a valid python interpreter:
[freebsd]
host1
[freebsd_vars]
ansible_python_interpreter=/usr/local/bin/python2.7
20170411:
AFFECTS: users of security/libressl
AUTHOR: [email protected]
The port has been updated to the latest stable version 2.5 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
20170411:
AFFECTS: www/firefox
AUTHOR: [email protected]
Firefox 53 or later may fail to build if sem(4) is present (see below)
because sysconf(3) still consults the old limits. If you don't plan to
run FreeBSD 8.x or older binaries make sure sem(4) isn't loaded during
boot or built statically into the kernel.
Creating config.status
Traceback (most recent call last):
File "configure.py", line 124, in <module>
sys.exit(main(sys.argv))
File "configure.py", line 34, in main
return config_status(config)
File "configure.py", line 119, in config_status
return config_status(args=[], **encode(sanitized_config, encoding))
File "python/mozbuild/mozbuild/config_status.py", line 136, in config_status
reader = BuildReader(env)
File "python/mozbuild/mozbuild/frontend/reader.py", line 886, in __init__
self._gyp_worker_pool = ProcessPoolExecutor(max_workers=max_workers)
File "python/futures/concurrent/futures/process.py", line 274, in __init__
_check_system_limits()
File "python/futures/concurrent/futures/process.py", line 263, in _check_system_limits
raise NotImplementedError(_system_limited)
NotImplementedError: system provides too few semaphores (30 available, 256 necessary)
20170410:
AFFECTS: users of x11-wm/awesome
AUTHOR: [email protected]
Awesome Window Manager (x11-wm/awesome) was upgraded to 4.1 and its config
is not backward compatible with 3.5. A new port was created to keep 3.5
version available at x11-wm/awesome3 and it will be available for 6 months
until users have time to upgrade configuration.
There are references about what has changed in 4.0 at:
https://awesomewm.org/apidoc/documentation/89-NEWS.md.html#v4
And configuration porting tips at:
https://awesomewm.org/apidoc/documentation/17-porting-tips.md.html#v4
If you would like to keep using 3.x, please run the collowing command to
update pkg database:
# pkg set -n awesome:awesome3
# pkg set -o x11-wm/awesome:x11-wm/awesome3
20170404:
AFFECTS: users of Xapian 1.2.x and www/ikiwiki
AUTHOR: [email protected]
Xapian has been updated to 1.4.3. The 1.2.x series has been renamed with
suffix "12". The Perl binding for Xapian 1.4.x is databases/p5-Xapian.
Since www/ikiwiki depends on Search::Xapian, it stays with Xapian 1.2.
If you would like to keep using 1.2, please run the following commands
to update pkg database:
xapian-core:
# pkg set -n xapian-core:xapian-core12
# pkg set -o databases/xapian-core:databases/xapian-core12
p5-Search-Xapian:
# pkg set -n p5-Search-Xapian:p5-Search-Xapian12
# pkg set -o databases/p5-Search-Xapian:databases/p5-Search-Xapian12
xapian-bindings:
# pkg set -n xapian-bindings:xapian-bindings12
# pkg set -o databases/xapian-bindings:databases/xapian-bindings12
xapian-omega:
# pkg set -n xapian-omega:xapian-omega12
# pkg set -o databases/xapian-omega:databases/xapian-omega12
20170401:
AFFECTS: net/samba44, net/samba45, net/samba46 and devel/p5-Parse-Pidl*
AUTHOR: [email protected]
It turned out that arbitary versions of p5-Parse-Pidl may lead to the
hard to explain crashes of the Samba server and utilities(in particular
we suspect it was responsible for the troubles with the DC provisioning).
So, from now on net/samba* ports use bundled version of Pidl. You need to
remove external package from the system:
pkg delete -f p5-Parse-Pidl p5-Parse-Pidl44
20170331:
AFFECTS: users of security/openssh-portable
AUTHOR: [email protected]
The format of several log messages emitted by the packet code has
changed to include additional information about the user and
their authentication state. Software that monitors ssh/sshd logs
may need to account for these changes. For example:
Connection closed by user x 1.1.1.1 port 1234 [preauth]
Connection closed by authenticating user x 10.1.1.1 port 1234 [preauth]
Connection closed by invalid user x 1.1.1.1 port 1234 [preauth]
Affected messages include connection closure, timeout, remote
disconnection, negotiation failure and some other fatal messages
generated by the packet code.
20170326:
AFFECTS: users of samba43
AUTHOR: [email protected]
The default version of samba has been switched from 4.3 to 4.4.
Upgrade instructions:
For package users having samba43 installed indirectly (as a dependency):
# pkg upgrade
For package users having samba43 installed directly (leaf port):
# pkg upgrade
# pkg install samba44
For ports users:
If you want to keep samba43, add DEFAULT_VERSIONS+= samba=4.3 to make.conf
If you want to upgrade to samba44, remove samba43 and obsolete packages:
# pkg delete -f samba36-libsmbclient samba36-nmblookup samba36-smbclient samba36 samba43 p5-Parse-Pidl
Portmaster users:
# portmaster net/samba44
# portmaster -a
Portupgrade users:
# portinstall net/samba44
# portupgrade -a
20170325:
AFFECTS: net/samba46 and devel/p5-Parse-Pidl
AUTHOR: [email protected]
New version of Samba port from 4.6 branch is added. Before upgrading please read upgrade notes:
https://www.samba.org/samba/history/samba-4.6.0.html
For the vfs_fruit users:
Users on *BSD must rename the metadata xattr used by vfs_fruit when
using the default setting "fruit:metadata = netatalk".
Due to a glitch in the Samba xattr API compatibility layer for FreeBSD and a
mistake in vfs_fruit, vfs_fruit ended up using the wrong xattr name when
configured with "fruit:metadata = netatalk" (default). Instead of the correct
org.netatalk.Metadata
it used
netatalk.Metadata
Starting with Samba 4.6 vfs_fruit will use the correct "org.netatalk.Metadata"
which means existing installations must rename this xattrs. For this purpose
Samba now includes a new tool `mvxattr`.
20170325:
AFFECTS: net/samba45, net/samba46 and devel/p5-Parse-Pidl
AUTHOR: [email protected]
While new Uses/samba.mk dosen't work well with slave ports to compile devel/p5-Parse-Pidl
for net/samba45 or net/samba46 you need explicitly set in the /etc/make.conf:
SAMBA4_PORT=net/samba46
explicitly. In the future that shouldn't be necessary.
20170321:
AFFECTS: users of samba36-libsmbclient, samba36-nmblookup samba36-smbclient and samba36
AUTHOR: [email protected]
The obsolete samba36-libsmbclient, samba36-nmblookup, samba36-smbclient and samba36 packages/ports were removed
and USES=samba was introduced.
Upgrade instructions:
For package users having those ports installed indirectly (as dependencies):
# pkg upgrade
For package users having those ports installed directly (leaf ports):
# pkg upgrade
# pkg install samba43
For ports users:
Choose you samba version, for instance add DEFAULT_VERSIONS+= samba=4.3 to make.conf
Remove obsolete packages:
# pkg delete -f samba36-libsmbclient samba36-nmblookup samba36-smbclient samba36
Portmaster users:
# portmaster net/samba43
# portmaster -a
Portupgrade users:
# portinstall net/samba43
# portupgrade -a
20170319:
AFFECTS: users of mail/pecl-mailparse
AUTHOR: [email protected]
The mail/pecl-mailparse has been upgraded to version 3.0.2, and the new
version is not compatible with PHP5. If you need PHP5 support, you can
find version 2.1.6 in mail/pecl-mailparse2.
20170319:
AFFECTS: users of textproc/pecl-yaml
AUTHOR: [email protected]
The pecl-yaml has been upgraded to version 2.0.0, and the new version is
not compatible with PHP5. If you need PHP5 support, you can find version
1.3.0 in textproc/pecl-yaml1.
20170316:
AFFECTS: users of python setuptools
AUTHOR: [email protected]
The python setuptools ports have been renamed to better match other python ports.
Ports users need to rename them so that portupgrade and portmaster do not
get confused. For example:
pkg set -n py27-setuptools27:py27-setuptools
pkg set -o devel/py-setuptools27:devel/py27-setuptools
or
pkg set -n py35-setuptools35:py35-setuptools
pkg set -o devel/py-setuptools35:devel/py35-setuptools
20170312:
AFFECTS: users of textproc/ack
AUTHOR: [email protected]
ack has been renamed back to p5-ack to match our perl naming. You could
run the following to update pkg database:
# pkg set -n ack:p5-ack
# pkg set -o textproc/ack:textproc/p5-ack
20170311:
AFFECTS: users of games/tome4 with paid DLCs
AUTHOR: [email protected]
The Ashes of Urh'Rok and Embers of Rage DLCs have been updated to be
compatible with changes introduced in ToME 1.5.0. Users of these DLCs
will need to redownload nd place these in $HOME/.t-engine/4.0/addons.
20170302:
AFFECTS: users of mail/thunderbird with Lightning
AUTHOR: [email protected]
After changes in the packaging of the Lightning extension, profiles
using this extension have to be re-created.
20170223:
AFFECTS: users of devel/mtbl
AUTHOR: [email protected]
There is a libmtbl shared library version bump in mtbl version 1.0.0.
The affected dependent ports have had PORTREVISION bumps, but you will
need to rebuild any applications that link to libmtbl.
20170220:
AFFECTS: sysutils/filebeat sysutils/metricbeat sysutils/packetbeat
AUTHOR: [email protected]
The three elasticsearch beats ports have merged into one single port
systuils/beats that installs all of the above and some more. The reason is to
make the port more maintainable and also that the new heartbeat beat would
conflict with sysutils/heartbeat.
20170220:
AFFECTS: devel/libevent2
AUTHOR: [email protected]
libevent2 has been renamed back to libevent as the default version.
If you manage out of tree ports make sure to run the following:
# pkg set -n libevent2:libevent
# pkg set -o devel/libevent2:devel/libevent
20170218:
AFFECTS: users of Qt 4 and Qt 5
AUTHOR: [email protected]
Following what is already done in Qt 5, the Qt 4 ports no longer install
their binaries into ${LOCALBASE}/bin (which is "/usr/local/bin" in most
cases). Additionally, the "-qt4" suffix has been dropped from the file names
of the binaries that had it, such as "qmake-qt4".
The new misc/qtchooser port is now used to choose whether a Qt 4 or Qt 5
version of a binary such as "moc", "qmake" or "designer" will be used. By
default, the Qt 5 versions are preferred, but that can be changed by setting
the QT_SELECT environment variable to "qt4".
qtchooser also allows one to seamlessly use other Qt installations for those
binaries, which is particularly beneficial to people working on Qt itself or
who need their own checkouts.
See qtchooser(1) for more information on how to configure qtchooser.
20170213:
AFFECTS: users of www/node*
AUTHOR: [email protected]
The BUNDLED_SSL option is now enabled by default on FreeBSD 10, since
Node.js requires OpenSSL 1.0.2, and FreeBSD 10 is shipped with 1.0.1.
20170213:
AFFECTS: users of graphics/libGL, graphics/libEGL, graphics/libglesv2
AUTHOR: [email protected]
The workaround for handling conflicting libraries between the
nvidia-driver, libGL, libEGL and libglesv2 ports was removed. If the
nvidia-driver port is updated before the other ports, it will remove
the libraries of said ports. This is a side effect of how the workaround
worked. If this happens reinstalling the affected port is enough.
pkg users can run: pkg install -f libGL libEGL libglesv2
20170211:
AFFECTS: users of x11-server/xorg-server
AUTHOR: [email protected]
Xorg server has been updated to 1.18.4 and autodetection has changed.
The order in which drivers are now attempted is:
1) vendor/model specific driver according to PCI IDs
2) generic modesetting driver which requires a drm driver with KMS
3) scfb, the generic framebuffer driver
4) vesa (only if arch is x86)
This should minimize the need for xorg.conf files. It is recommended to
load the correct KMS driver (i915kms.ko or radeonkms.ko) via rc.conf,
i.e. kld_list="i915kms.ko", to ensure correct functionality. Although
the vendor drivers may attempt to load the correct drm driver, which
does not always work, the modesetting driver assumes the required KMS
driver is already loaded and will fail if there is none. The modesetting
driver is now recommended as an alternative to the Intel driver; the
performance is comparable and stability is better with modesetting. The
ATI driver continues to offer better performance than modesetting.
20170203:
AFFECTS: users of security/libressl-devel
AUTHOR: [email protected]
The version 2.5.1 bumps the libcrypto, libssl and libtls shared library
versions. You will have to rebuild all packages that depend on
libressl-devel. Check the 20160811 libressl entry for more detailed
guidance on rebuilding.
20170202:
AFFECTS: users of www/uwsgi
AUTHOR: [email protected]
The previous disruptive changes to uwsgi for security have been remediated
through creation of a dedicated uwsgi user/group and utilizing the
uwsgi feature to set socket ownership. The uwsgi daemon by default now
has the following properties:
* Process runs as uwsgi user and group (UID/GID 165)
* Socket mode is 660, still protecting unauthorized access from "other"
* Socket ownership is www:www, restoring compatibility
20170130:
AFFECTS: users of devel/ice, devel/py-ice, devel/php5-ice
AUTHOR: [email protected]
Since __WORDSIZE as defined by <stdint.h> always reports 32 when using
C++98/03 (unless __STDC_LIMIT_MACROS is set explictly), Ice 3.6.3 used
"long long" for Int64 instead of "long" on 64-bit platforms by mistake.
A workaround has been added in version 3.6.3_2 of these three ports,
requiring to upgrade all of them at the same time and to rebuild all
custom code that links against them.
20170129:
AFFECTS: users of multimedia/motion
AUTHOR: [email protected]
Version 3.x expected the configuration files to reside in:
${LOCALBASE}/etc
Version 4.x expects the configuration files to reside in:
${LOCALBASE}/etc/motion
This was unfortunately overlooked when the port was updated to 4.x, but it
has now been fixed to install the default configuration file in the new
location. The rc script now checks for motion.conf in the new location.
While you may be able to simply copy your old motion.conf to the new location,
it is recommended to review ${LOCALBASE}/etc/motion/motion.conf and make
changes to it based on your old ${LOCALBASE}/etc/motion.conf as some options
have been added and removed.
Further, if you use motion with multiple cameras and have
${LOCALBASE}/etc/thread[0-9].conf files, they should be moved to
${LOCALBASE}/etc/motion as well. These files are deprecated and should be
renamed to camera[0-9].conf and in motion.conf, lines like:
thread /usr/local/etc/thread1.conf
Should be converted to:
camera /usr/local/etc/motion/camera1.conf
20170127:
AFFECTS: users of www/uwsgi
AUTHOR: [email protected]
The default socket mode for uwsgi as 777 is a severe security concern.
This has been remediated by changing the rc script to default to 600.
The mode is configurable with rc.conf values: uwsgi_socket_mode="600"
or for a profile named "www", uwsgi_www_socket_mode="600".
20170121:
AFFECTS: users of security/tinc
AUTHOR: [email protected]
this version of tinc requires all nodes in the VPN to be linked with a
version of OpenSSL or LibreSSL that supports the AES256 and SHA256
algorithms.
20170120:
AFFECTS: users of databases/mysql56-server
AUTHOR: [email protected]
databases/mysql56-server was updated to 5.6.35 which included backported
rc script changes from the mysql57-server port. This broke mysql_optfile in
rc.conf and also forced a sample my.cnf if none existed. MySQL has
some parameters which cannot be changed after a database has been
created, so this caused MySQL to fail to start.
This change was reverted in mysql56-server-5.6.35_1
An additional change was made in mysql56-server-5.6.35_2 to prevent
automatic loading of a sample my.cnf which was causing issues for
users who were running without a my.cnf.
20170117:
AFFECTS: users of EoL'ed FreeBSD versions (<10.3, 11 prior to 11.0)
AUTHOR: [email protected]
The ports system will now refuse to build anything if it's run on
outdated system version. This protects users from unexpected build
failures after code to support EoL'ed systems is removed from the
tree. You may define ALLOW_UNSUPPORTED_SYSTEM to override this and
allow builds, but no support will be provided in case of failures.
20170116:
AFFECTS: users of java/wildfly10
AUTHOR: [email protected]
The java/wildfly10 port has been updated to 10.1.0. To complete the
migration you must copy your existing configuration (directories
"appclient", "standalone", and "domain") from /usr/local/wildfly-10.0.0
to /usr/local/wildfly10.
20170115:
AFFECTS: users of net-mgmt/librenms
AUTHOR: [email protected]
The following is recommended for /var/db/mysql/my.cnf
NOTE: these are global settings. Please read this first:
http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html
[mysqld]
innodb_file_per_table=1
sql-mode=""
20170109:
AFFECTS: users of lang/ruby22
AUTHOR: [email protected]
The default ruby version has been updated from 2.2 to 2.3.
If you compile your own ports you may keep 2.2 as the default version by
adding the following lines to your /etc/make.conf file:
#
# Keep ruby 2.2 as default version
#
DEFAULT_VERSIONS+=ruby=2.2
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/ruby23 lang/ruby22
# portmaster -R -r ruby-2.3
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/ruby22:lang/ruby23
# portupgrade -x ruby-2.3.\* -fr lang/ruby23
20170102:
AFFECTS: multimedia/ffmpeg
AUTHOR: [email protected]
OPTIMIZED_CFLAGS switched to only use vendor optimizations which
means -ffast-math -fno-finite-math-only are no longer applied. If
you did like the former behavior consider adding
# multimedia/ffmpeg/Makefile.local
OPTIMIZED_CFLAGS_CFLAGS += -ffast-math -fno-finite-math-only
or
# /etc/make.conf
.if ${.CURDIR:M*/multimedia/ffmpeg}
CFLAGS += -ffast-math -fno-finite-math-only
.endif
20161230:
AFFECTS: users of x11/xfce4-terminal
AUTHOR: [email protected]
The port has been updated to the latest stable version 0.8.2.
Please, don't active the hidden 'MiscSlimTabs' option in
~/.config/xfce4/terminal/terminalrc, it requires Gtk+ > 3.20.
20161228:
AFFECTS: users of multimedia/mlt
AUTHOR: [email protected]
MLT Qt plugins have been moved to their own ports, mlt-qt4 and
mlt-qt5. Please, uninstall multimedia/mlt before you update:
# pkg delete mlt
20161227:
AFFECTS: users of security/openvpn, security/openvpn-polarssl
AUTHOR: Matthias Andree <[email protected]>
The OpenVPN ports have been updated to the new upstream release v2.4,
and their predecessors preserved as openvpn23 and openvpn23-polarssl,
respectively. Note that for the new v2.4 release, the
openvpn-polarssl port has been renamed to openvpn-mbedtls to match the
upstream library's new name.
20161218:
AFFECTS: users of www/nghttp2
AUTHOR: [email protected]
nghttp2 has been split into 2 ports: www/libnghttp2 for core library and
www/nghttp2 for the rest. Please uninstall nghttp2 before you update
this port.
20161216:
AFFECTS: mail/thunderbird, www/seamonkey
AUTHOR: [email protected]
ENIGMAIL is no longer provided as part of the ports after upstream
dropped binary components in 1.9. Go to Tools -> Add-ons Manager
then type "enigmail" in the search box to install.
20161213:
AFFECTS: users of devel/skalibs, lang/execline, sysutils/s6
AUTHOR: Colin Booth <[email protected]>
skalibs has undergone a major version bump and compatibility is not
guaranteed for software with a runtime dependency on
libskarnet.so.2.3.9.0. This will not affect lang/execline or
sysutils/s6 as those are statically linked against libskarnet.a.
execline has undergone a major version bump and compatibility is not
guaranteed for software with a runtime dependency on
libexecline.so.2.1.4.5. This will not affect sysutils/s6 as all s6
programs are statically linked against libexecline.a.
s6 has undergone a major version bump and compatibility is not
guaranteed for software with a runtime dependency on
libs6.so.2.2.4.3. Additionally, s6-applyuidgid and s6-setuidgid
have moved from $PREFIX/sbin to $PREFIX/bin. Any scripts calling
those utilities that are not relying on $PATH resolution to find
them will need to be rewritten.
20161207:
AFFECTS: users of www/node
AUTHOR: [email protected]
The www/node port has been updated to node.js v7.2.0, the latest
upstream release. A new port, www/node6, has been created for the
v6.x LTS branch. Users wanting to stay on v6.x can replace www/node
with www/node6 with one of the following commands:
# pkg set -o www/node:www/node6
or
# portmaster -o www/node6 www/node
or
# portupgrade -o www/node6 www/node
20161202:
AFFECTS: Users of textproc/p5-Search-Elasticsearch
AUTHOR: [email protected]
As of the 5.01 release of ths package, the client libraries for older
versions of Elasticsearch have started to be shipped seperately. If you are
using this library to access a none 5.X server you will need to install one of
the textproc/p5-Search-Elasticsearch-Client-* ports.
20161126:
AFFECTS: Users of security/gpgme-*
AUTHOR: [email protected]
Gpgme has been updated to 1.8.0.
With it comes the removal of libgpgme-pthread.so in favor of using
libgpgme.so itself as the thread-safe library. Ports that may have
linked to -lgpgme-pthread will now just link to -lgpgme. PORTREVISION
has been bumped on all ports with a dependency on security/gpgme.
The Python module provided by security/py-gpgme has been renamed
from pyme3 to gpg, as well.
Portmaster users:
portmaster -r gpgme
Portupgrade users:
portupgrade -fr security/gpgme
20161121:
AFFECTS: Users of graphics/tiff
AUTHOR: [email protected]
The tiff port was updated to 4.0.7.
The following tools are removed from this release: bmp2tiff, gif2tiff, ras2tiff, rgb2ycbcr and thumbnail.
20161116:
AFFECTS: Users of sysutils/bareos-*
AUTHOR: [email protected]
Bareos v1.6.x changed the configuration scheme, from one configuration
file per Bareos component (file daemon, storage daemon, and director)
to several configuration files, in several directories, for each
component. See http://doc.bareos.org/master/html/bareos-manual-main-reference.html
The new scheme will use all files named *.conf in the directory
hierarchies for each component:
/usr/local/etc/bareos/bareos-dir.d/
/usr/local/etc/bareos/bareos-fd.d/
/usr/local/etc/bareos/bareos-sd.d/
To retain the old configuration scheme of one file per component add
appropriate lines such as these to your /etc/rc.conf:
bareos_dir_config="/usr/local/etc/bareos/bareos-dir.conf"
bareos_fd_config="/usr/local/etc/bareos/bareos-fd.conf"
bareos_sd_config="/usr/local/etc/bareos/bareos-sd.conf"
20161113:
AFFECTS: users of devel/libosinfo
AUTHOR: [email protected]
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: [email protected]
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: [email protected]
kadmin(8) in heimdal-1.5.3_5 and prior did not create a database
in /var/heimdal in Berkeley DB format which kdc(8) required. This
problem has been fixed in heimdal-1.5.3_6.
20161104:
AFFECTS: users of mail/mu4e and mail/mu4e-maildirs
AUTHOR: [email protected]
The package name of mail/mu4e* have been changed from mu4e* to
mu4e*-emacsNN. When upgrading the older versions, this change can
cause the following error which prevents it from upgrading:
pkg-static: mu4e-emacs25-0.9.16 conflicts with mu4e-0.9.16 (installs files into the same place).
If this error occurs, please remove the old packages by using
"pkg delete" manually:
# pkg delete mu4e-0.9.16 mu4e-maildirs-0.8.20160126_1
20161103:
AFFECTS: users of lang/perl5*
AUTHOR: [email protected]
The default Perl version has been switched to Perl 5.24. 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, assuming you are
migrating from 5.20 to 5.24, do:
First, add to /etc/make.conf:
DEFAULT_VERSIONS+= perl5=5.24
Portupgrade users:
portupgrade -o lang/perl5.24 -f lang/perl5.20
You can now remove the DEFAULT_VERSIONS line added earlier
from /etc/make.conf
Then you will need to rebuild everything that uses libperl.so, you
can do so with:
portupgrade -f `pkg shlib -qR libperl.so.5.20`