-
Notifications
You must be signed in to change notification settings - Fork 116
/
UPDATING
3619 lines (2686 loc) · 126 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.
20241004:
AFFECTS: users of www/c-icap
AUTHOR: [email protected]
The c-icap server version is moving from branch 5.X to 6.X.
An in-place upgrade may require some changes in your current
configuration.
For installation instructions please refer :
https://sourceforge.net/p/c-icap/wiki/configcicap
https://sourceforge.net/p/c-icap/wiki
20240930:
AFFECTS: users of sysutils/nq
AUTHOR: [email protected]
The nq upstream renamed the fq utility to nqtail
and the tq utility to nqterm.
20240927:
AFFECTS: users of databases/mongodb50
AUTHOR: [email protected]
MongoDB version 5.0 is End of Life starting October 2024.
Please make sure you are running MongoDB version 6.0 or higher.
In-place upgrades are supported from version 5.0 to 6.0.
For an in-place upgrade it is important that the
'featureCompatibilityVersion' is set to 5.0.
See: https://www.mongodb.com/docs/v6.0/release-notes/6.0-upgrade-standalone/#feature-compatibility-version
TL;DR, run these commands in mongodb50 before upgrading:
$ mongo --port <portnr>
> db.adminCommand( { setFeatureCompatibilityVersion: "5.0" } )
> exit
20240912:
AFFECTS: security/clamav, security/clamav-lts
AUTHOR: netchildFreeBSD.org
The start scripts of clamav have been renamed to clamav_clamd,
clamav_freshclam and clamav_milter for improved compatibility with
other parts of the system. The automatic start at boot (rc.conf
variable settings) is not affected, but if you have some other
automatism you may want to change
".../etc/rc.d/clamav-clamd" to ".../etc/rc.d/clamav_clamd"
".../etc/rc.d/clamav-freshclam" to ".../etc/rc.d/clamav_freshclam"
".../etc/rc.d/clamav-milter" to ".../etc/rc.d/clamav_milter"
or
"service clamav-clamd ..." to "service clamav_clamd ..."
"service clamav-freshclam" to "service clamav_freshclam ..."
"service clamav-milter ..." to "service clamav_milter ..."
20240907:
AFFECTS: www/tt-rss
AUTHOR: [email protected]
The ttrssd_local_db rc var has been removed in favor of using daemon's
restart option -r to retry the ttrssd php scripts if database is not up
before ttrssd starts.
20240829:
AFFECTS: devel/binutils
AUTHOR: [email protected]
Historically devel/binutils would implicitly use devel/elfutils when
it discovers it previously installed. This resulted in it depending on,
though not explicitly if previously found, elfutils when built manually.
This behavior has now changed. binutils will now disable any
auto-dependency on elfutils. Users who build binutils manually and wish
to have it depend on elfutls must now explicitly set the option when
building binutils.
There is no change to packages built by poudriere.
20240824:
AFFECTS: dns/acme-dns
AUTHOR: [email protected]
The start script of acme-dns has been renamed to acme_dns for improved
compatibility with other parts of the system. The automatic start at
boot (rc.conf variable settings) is not affected, but if you have some
other automatism you may want to change
".../etc/rc.d/acme-dns" to ".../etc/rc.d/acme_dns"
20240816:
AFFECTS: users of databases/redis
AUTHOR: [email protected]
The databases/redis port has been updated to 7.4. Users wanting to
stay on 7.2 can replace databases/redis with databases/redis72 with
one of the following commands.
If you use pkg with binary packages:
# pkg set -o databases/redis:databases/redis72
# pkg upgrade
If you use portmaster:
# portmaster -o databases/redis72 databases/redis
If you use portupgrade:
# portupgrade -o databases/redis72 databases/redis
Keep in mind license term has changed with Redis 7.4. Now it is
distributed under dual license of Redis Source Available License v2
(RSALv2) and Server Side Public License v1 (SSPLv1). If you don't
want to accept either of them, then Valkey (databases/valkey) may be
alternative for you. It is fork of Redis 7.2 and distributed under
3-clause BSD license that is same as Redis 7.2 and before.
20240815:
AFFECTS: users of devel/subversion-lts and devel/subversion
AUTHOR: [email protected]
The port option STATIC has been broken since 2022-01 because textproc/utf8proc
does not provide an archive with CMake. Therefore, it has been removed.
20240809:
AFFECTS: sysutils/amavisd-new
AUTHOR: netchildFreeBSD.org
The start scripts of amavisd have been renamed to amavisd_snmp and
amavis_p0fanalyzer for improved compatibility with other parts of the
system. The automatic start at boot (rc.conf variable settings) is
not affected, but if you have some other automatism you may want to
change
".../etc/rc.d/amavisd-snmp" to ".../etc/rc.d/amavisd_snmp"
".../etc/rc.d/amavis-p0fanalyzer" to ".../etc/rc.d/amavis-p0fanalyzer"
or
"service amavisd-snmp ..." to "service amavisd_snmp ..."
"service amavis-p0fanalyzer ..." to "service amavis_p0fanalyzer ..."
20240727:
AFFECTS: lang/php8[123]
AUTHOR: netchildFreeBSD.org
The start scripts of php-fpm have been renamed to php_fpm for improved
compatibility with other parts of the system. The automatic start at boot
(rc.conf variable settings) is not affected, but if you have some other
automatism you may want to change
".../etc/rc.d/php-fpm" to ".../etc/rc.d/php_fpm"
or
"service php-fpm ..." to "service php_fpm ..."
If you have custom start scripts which depend upon php-fpm, you need to
change the REQUIRE lines in them from "php-fpm" to "php_fpm".
20240726:
AFFECTS: users of archivers/py-borgbackup
AUTHOR: [email protected]
Borgbackup has been upgraded to version 1.4.0.
The FreeBSD port as of 2024-07-26 reinstates FreeBSD 13 compatibility.
For users who wish to continue using version 1.2,
use either of these commands for upgrading:
With binary packages through pkg:
pkg set -o archivers/py-borgbackup:archivers/py-borgbackup12
pkg upgrade
With portmaster or portupgrade (replace the command accordingly):
portmaster -o archivers/py-borgbackup12 archivers/py-borgbackup
20240723:
AFFECTS: users of databases/postgresql* and other software using PostgreSQL to run
AUTHOR: [email protected]
The default version of PostgreSQL has been switched from 15 to 16.
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 15, your
files are named according to this.
# service postgresql stop
# pkg create postgresql15-server postgresql15-contrib
# mkdir /tmp/pg-upgrade
# tar xf postgresql15-server-15.7.pkg -C /tmp/pg-upgrade
# tar xf postgresql15-contrib-15.7.pkg -C /tmp/pg-upgrade
# pkg delete -f databases/postgresql15-server databases/postgresql15-contrib databases/postgresql15-client
Now update PostgreSQL:
pkg user:
# pkg install databases/postgresql16-server databases/postgresql16-contrib
# pkg upgrade
Portmaster users:
# portmaster databases/postgresql16-server databases/postgresql16-contrib
# portmaster -a
Portupgrade users:
# portinstall databases/postgresql16-server databases/postgresql16-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/data16 -U postgres"
# su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data15/ -B /usr/local/bin/ -D /var/db/postgres/data16/ -U postgres "
Now the migration is finished. You can start PostgreSQL again with:
# service postgresql start
ATTENTION:
1) If you use non-default initdb options, you have to adjust the initdb-command accordingly
20240715:
AFFECTS: net-mgmt/netbox
AUTHOR: [email protected]
The NetBox 4.0 release contains major changes, so at least the following
items must be checked before proceeding with the upgrade:
1. NetBox v4.0 requires Python 3.10 or later.
2. Please also check the pkg-message and the changelogs for further info.
20240705:
AFFECTS: sysutils/bacula*-{client,server}
AUTHOR: netchildFreeBSD.org
The start scripts of bacula have been renamed to bacula_fd, bacula_dir and
bacula_sd for improved compatibility with other parts of the
system. The automatic start at boot (rc.conf variable settings) is
not affected, but if you have some other automatism you may want to
change
".../etc/rc.d/bacula-fd" to ".../etc/rc.d/bacula_fd"
".../etc/rc.d/bacula-dir" to ".../etc/rc.d/bacula_dir"
".../etc/rc.d/bacula-sd" to ".../etc/rc.d/bacula_sd"
or
"service bacula-fd ..." to "service bacula_fd ..."
"service bacula-dir ..." to "service bacula_dir ..."
"service bacula-sd ..." to "service bacula_sd ..."
20240704:
AFFECTS: net/xrdp and x11-drivers/xorgxrdp
AUTHOR: [email protected]
xrdp has been updated to the releases of the latest stable branch v0.10.
This version significantly improves performance improvement especially if the
client is Windows 11. There are to things to be careful about when updating.
1) Make sure to update both net/xrdp and x11-drivers/xorgxrdp ports
simultaneously.
2) Config files require manual migration (follow the steps below).
Review and backup changes you made to xrdp.ini and sesman.ini before updating
xrdp. The following example only mentions xrdp.ini however make sure to do the
same review, backup and migration for sesman.ini as well.
Before updating xrdp, review and backup your changes.
# cd /usr/local/etc/xrdp
# diff -u xrdp.ini.sample xrdp.ini > xrdp.ini.diff
After updating xrdp, migrate your changes to new configuration files.
xrdp.ini.sample is replaced with new version at this point. See diff and
manually apply changes.
# cp xrdp.ini.sample xrdp.ini
# vi xrdp.ini
20240620:
AFFECTS: net-mgmt/net-snmp
AUTHOR: [email protected]
The snmpd and snmptrapd daemons now drop privileges by default when started
using the rc scripts provided in the package. Make sure that snmpd
configuration in /usr/local/share/snmp is readable by the "snmpd" user. If
you have defined extension scripts in snmpd.conf, make sure that they can be
executed by an unprivileged user. To revert to the old behavior of always
running as root, set snmpd_sugid="NO" or snmptrapd_sugid="NO" in /etc/rc.conf.
See the snmpd rc script for a hint on how to debug any permission problems
that might arise as a result of this change.
20240615:
AFFECTS: mail/cyrus-imapd25
AUTHOR: [email protected]
The BDB option is disabled by default.
If you are using the berkeley cyrusdb backend, we strongly recommend
that you switch to something other than the berkeley cyrusdb
backend. If you want to continue using the berkeley cyrusdb
backend, build the cyrus-imapd25 port yourself with the BDB option
enabled.
20240613:
AFFECTS: multimedia/audacious and multimedia/audacious-plugins
AUTHOR: [email protected]
Upstream project made qt6 the new default, so the port flavors have
been updated to follow this change.
If you are using the qt6 flavor, you should uninstall it and install
the unflavored package. If you want to keep using the qt5 version it
will be updated automatically to the qt6 version. If you should
uninstall the unflavored package and instal the qt5 version.
20240606:
AFFECTS: users of net-mgmt/unifi8
AUTHOR: [email protected]
The default MongoDB version dependency has been switched from 5.0 to 6.0.
Although MongoDB 5.0 -> MongoDB 6.0 datafiles in-place upgrade seem to
work, users are strongly recommended to take full backup of unifi
database prior to upgrade and start with clean installation afterwards.
For an in-place upgrade it is important that the MongoDB
'featureCompatibilityVersion' is set to 5.0.
See: https://www.mongodb.com/docs/v6.0/release-notes/6.0-upgrade-standalone/#feature-compatibility-version
Run these commands in mongodb50 before upgrading (e.g. while unifi is running):
$ mongo --port 27117
> db.adminCommand( { setFeatureCompatibilityVersion: "5.0" } )
> exit
See updating entry 20230310 for a backup/restore upgrade.
20240604:
AFFECTS: net-mgmt/net-snmp
AUTHOR: [email protected]
The net-snmp port's newsyslog(8) configuration has been updated such
that the snmpd log file will be owned by the snmpd user following log
rotation. This is done to make it easier to run snmpd as the snmpd
user rather than as root, using the snmpd_sugid rc.conf option.
For now snmpd still runs as root by default. This is expected to change
in the future.
20240529:
AFFECTS: users of TeX*
AUTHOR: [email protected]
TeX system has been updated to 2024 from 2023. Normal pkg upgrade or
portmaster -a should handle all the upgrade properly. In case not please
create a ticket or send a mail to [email protected]
Previously users have reported to delete texlive-texmf prior to
starting update, or pkg-static will indicate there is a conflict
during the upgrade of texlive-base :
# pkg remove texlive-texmf
20240529:
AFFECTS: users of python
AUTHOR: [email protected]
The default version of python3 and python was switched to 3.11.
For ports users wanting to keep version 3.9 as default,
add DEFAULT_VERSIONS+= python=3.9 python3=3.9 to make.conf
Following procedures may ease the upgrade:
For users of pre-build packages:
# sh
# for i in $(pkg query -g %n 'py39-*'); do pkg set -yn ${i}:py311-${i#py39-}; done
# pkg upgrade
For portmaster users:
# sh
# portmaster -o lang/python311 python39
# REINSTALL="$(pkg info -oq '*py39*')"
# pkg delete -f "*py39*"
# portmaster $REINSTALL
# REBUILD=$(pkg query -g "%n:%dn" '*' | grep py3 | grep -v py311 | cut -d : -f 1 | sort -u)
# portmaster $REBUILD
# REBUILD2=$(pkg list | grep python-39 | xargs pkg which | awk '{print $6}' | sort -u)
# portmaster $REBUILD2
Final steps (for pre-built packages & portmaster):
If no longer required, Python 3.9 can be removed via
"pkg remove python39" and the directory /usr/local/lib/python3.9 can
then be deleted afterwards, if not empty.
20240522:
AFFECTS: net-p2p/transmission-daemon
The web interface has been separated from the daemon port into its own port.
This allows users of transmission-gtk and transmission-qt to install the web
interface.
20240521:
AFFECTS: www/gitlab
AUTHOR: [email protected]
Make sure you upgrade first to 16.11.x before you upgrade to the today
released version 17.0.0.
For more details see:
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.11-17.0-freebsd.md
20240517:
AFFECTS: comms/tio
AUTHOR: [email protected]
As of 3.1 upstream have reworked configuration file layout and syntax
so older configurations will not work.
For more details, see
https://github.com/tio/tio/releases/tag/v3.1
20240513:
AFFECTS: users of security/libressl
AUTHOR: [email protected]
The port has been updated to the latest stable version 3.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.
20240509:
AFFECTS: databases/timescaledb
AUTHOR: [email protected]
The Foreign Key storage in hypertables has changed in an incompatible way,
after runing ALTER EXTENSION, you must run the SQL script here:
https://github.com/timescale/timescaledb-extras/blob/master/utils/2.15.X-fix_hypertable_foreign_keys.sql
For more details, see
https://github.com/timescale/timescaledb/pull/6797
20240508:
AFFECTS: www/oauth2-proxy
AUTHOR: [email protected]
The start script is converted to be instance aware. To use it:
- cp /usr/local/etc/oauth2-proxy.cfg.sample /usr/local/etc/oauth2-proxy-myapp.cfg
- vi /usr/local/etc/oauth2-proxy-myapp.cfg
- ln -s oauth2_proxy /usr/local/etc/rc.d/oauth2_proxy_myapp
- sysctl oauth2_proxy_myapp_enable=YES
- service oauth2_proxy_myapp start
This allows to easily start multiple instances on the same system.
As part of this, the start script was renamed to oauth2_proxy. This only
affects manual restarts, no change in rc.conf is needed.
20240430:
AFFECTS: audio/py-pyradio
AUTHOR: [email protected]
The new version of Pyradio moves some data files to new locations.
To see what it really does, run pyradio from a terminal the first time.
Besides that, the recordings are moved/saved into ~/pyradio-recordings.
You can change that directory in the config file.
For more details, see
https://github.com/coderholic/pyradio/releases/tag/0.9.3
20240423:
AFFECTS: textproc/vale
AUTHOR: [email protected]
When upgrading to v3.0.0, the vocabularies need to be moved from
$StylesPath/Vocab to $StylesPath/config/vocabularies.
20240421:
AFFECTS: www/gitlab-ce
AUTHOR: [email protected]
With the upgrade to version 16.11 the default path for gitlab-ce changed:
/usr/local/www/gitlab-ce -> /usr/local/www/gitlab
Make sure you follow the upgrade manual very carefully:
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.10-16.11-freebsd.md
The gitlab port also got a new flavor gitlab@ee to make the Gitlab
Enterprise Edition available (you will need a license for it).
Please note, that the ee flavor is a draft, but any feedback is welcome.
See also the installation and upgrade manual for more details.
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/install/16.11-freebsd.md
20240408:
AFFECTS: users of databases/p5-DBD-mysql
AUTHOR: [email protected]
Upstream removed support for MariaDB from the 5.0 branch. So if you use
MariaDB you need to use databases/p5-DBD-mysql4 from now on.
Portmaster users:
portmaster -o databases/p5-DBD-mysql4 databases/p5-DBD-mysql
portmaster -a
Portupgrade users:
portupgrade -o databases/p5-DBD-mysql4 -f databases/p5-DBD-mysql
portupgrade -a
20240330:
AFFECTS: users of mail/spamassassin
AUTHOR: [email protected]
sa-update must be run following update and prior to restarting sa-spamd
else it will fail to start due to a syntax error.
20240326:
AFFECTS: users of net/bird2
AUTHOR: [email protected]
The net/bird2 default flavor has ben switched to netlink on FreeBSD >= 14.0
There is not change for FreeBSD < 14.0 (default flavor is still rtsock)
20240319:
AFFECTS: users of net/rdist6
AUTHOR: [email protected]
As of 52032b3d50c0 net/rdist6 will install its binary named rdist instead
of rdist6. Base FreeBSD no longer has its own rdist binary. Therefore
there is no need to rename the rdist6 binary to rdist6 to avoid confusion.
The historical and default name of the rdist binary is "rdist".
20240318:
AFFECTS: users of net-mgmt/unifi8
AUTHOR: [email protected]
The default MongoDB version dependency has been switched from 4.4 to 5.0.
Although MongoDB 4.4 -> MongoDB 5.0 datafiles in-place upgrade seem to
work, users are strongly recommended to take full backup of unifi
database prior to upgrade and start with clean installation afterwards.
See updating entry 20230310 for details.
20240316:
AFFECTS: users of net/rabbitmq
AUTHOR: [email protected]
In preparation for upgrading to future RabbitMQ releases, users *must*
enable all feature flags before upgrading stepwise to v3.12.13, to be
able to migrate later to v3.13.0 when it is released in 2024Q2.
See https://www.rabbitmq.com/docs/upgrade for details.
20240228:
AFFECTS: users of www/redmine50
AUTHOR: [email protected]
The default version of ruby has been switched from 3.1 to 3.2.
However www/redmine50 does not support ruby 3.2. Users should add the
following in their relevant make.conf file:
DEFAULT_VERSIONS+=ruby=3.1
Although redmine 5.1.X supports ruby 3.2 and later but so far there is
no redmine51 ports in the tree.
20240222:
AFFECTS: users of databases/xtrabackup8
AUTHOR: [email protected]
The port databases/xtrabackup8 upgraded to version 8.0.35-30
and renamed to databases/xtrabackup80 in preparation for upcoming
incompatible branch databases/xtrabackup81, to avoid confusion.
20231229:
AFFECTS: users of databases/tarantool
AUTHOR: [email protected]
A new major version of the tarantool has been released.
databases/tarantool renamed to databases/tarantool2.
2.11 is an LTS version and will be supported for a while.
20231125:
AFFECTS: users of lang/php81
AUTHOR: [email protected]
The default version of PHP has been switched from 8.1 to 8.2.
If you use binary packages you should make a list of php packages
before running 'pkg upgrade':
# pkg info \*php81\* > ~/installed-php-ports-list
After the upgrade, check with such list if all your php extensions
are still installed, and reinstall them if needed.
If you use mod_php81 you need to deinstall it and install mod_php82.
20231104:
AFFECTS: users of security/libressl
AUTHOR: [email protected]
The port has been updated to the latest stable version 3.8 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.
20231031:
AFFECTS: users of devel/subversion-lts
AUTHOR: [email protected]
devel/subversion-lts has been updated from 1.10.x to the latest LTS version,
1.14.x. Some changes between these releases may require attention from
administrators or users.
Refer to https://subversion.apache.org/docs/release-notes/1.14.html#compat-misc for details.
20231028:
AFFECTS: users of net-mgmt/nfdump
nfdump-1.7.x is compatible to nfdump-1.6.18, which means it can
read files created with nfdump-1.6.18 or newer. Flow files created
with earlier nfdump versions may not contain all flow elements.
If you have older files, it is recommended to use nfdump-1.6.17
to update the records.
nfdump 1.7.x provides the same set of programs as 1.6.x and can
be used almost as a drop-in replacement. This may change in future
and older legacy programs may be removed. You can convert any old
files from nfdump-1.6 to nfdump-1.7 format by reading/writing
files: ./nfdump -r old-flowfile -y -w new-flowfile
Please note, that only nfdump may read older flow files. All other
programs relay on the new file format.
20231027:
AFFECTS: users of net-mgmt/librenms
AUTHOR: [email protected]
When updating to >= 23.10.0, a broken crontab is fixed. This breakage
caused the validation error: Scheduler is not running
After updating, If that error does not clear for you, run:
sudo lnms config:cache
20231027:
AFFECTS: users of print/ghostscript9*
AUTHOR: [email protected]
The default ghostscript version has been updated from 9 to 10.
If you compile your own ports you may keep 9 as the default version by
adding the following lines to your /etc/make.conf file:
#
# Keep ghostscript 9 as default version
#
DEFAULT_VERSIONS+=ghostscript=9
Please note that print/ghostcript9* will be removed in the future since it is
not supported by upstream anymore.
20231026:
AFFECTS: users of lang/chicken
AUTHOR: [email protected]
The chicken binaries csc and csi, together with their manual pages, have been
renamed to chicken-csc and chicken-csi, to avoid conflicts with lang/mono.
This is in line with what several Linux distros do. See PR 274736.
20231023:
AFFECTS: users of mail/mailman3
AUTHOR: [email protected]
logging.http section has now been split into two parts, logging.http is for
the Mailman internal code and logging.gunicorn is for Gunicorn specifically
since they have different logging formats. This should fix spurious errors
with KeyError: t that was often confusing for users.
Python 3.9 is now the minimum supported version of Python.
20231017:
AFFECTS: users of lang/perl5*
AUTHOR: [email protected]
The default Perl version has been switched to Perl 5.36. 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.34 to 5.36, do:
First, add to /etc/make.conf:
DEFAULT_VERSIONS+= perl5=5.36
Portupgrade users:
portupgrade -o lang/perl5.36 -f lang/perl5.34
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.34`
If, for some reason, this command fails at one point, it is safe to
run it again, it will not rebuild what it already rebuilt, as the
ports that have been rebuilt no longer depend on libperl.so.5.34 but
on libperl.so.5.36.
Portmaster users:
portmaster -o lang/perl5.36 lang/perl5.34
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:
portmaster -f `pkg shlib -qR libperl.so.5.34`
If, for some reason, this command fails at one point, it is safe to
run it again, it will not rebuild what it already rebuilt, as the
ports that have been rebuilt no longer depend on libperl.so.5.34 but
on libperl.so.5.36.
20231014:
AFFECTS: users of security/openssl and security/openssl30
AUTHOR: [email protected]
The openssl port was renamed to openssl111 and subsequently the
openssl30 port was renamed to openssl.
The shared library version of OpenSSL has been bumped.
Users of DEFAULT_VERSIONS= ssl=openssl30 must update this to
ssl=openssl.
Users of DEFAULT_VERSIONS= ssl=openssl should not change this unless
they use ports that require the deprecated OpenSSL 1.1.1 version.
You must rebuild all ports that depend on OpenSSL if you use OpenSSL
from ports.
20231011:
AFFECTS: users of www/caddy
AUTHOR: [email protected]
The default admin endpoint has changed from localhost:2019 to
/var/run/caddy/caddy.sock. Using a Unix socket is more secure,
allowing it to be secured by filesystem permissions rather than
requiring a firewall.
If you only control caddy from the rc(8) script (service caddy ...),
you don't need to do anything. If you access the API yourself, you
will want to update your scripts to use the new socket.
To use the old endpoint, add the following to /etc/rc.conf:
caddy_admin="localhost:2019"
20231009:
AFFECTS: users of net/ntpd-rs
AUTHOR: [email protected]
In 1.0.0 the configuration has been completely reworked, please check the
documentation for details. Configuration will not automatically migrate.
20231004:
AFFECTS: www/gitlab-ce
AUTHOR: [email protected]
Before you upgrade to version 16.4.x or higher, make sure you did the
upgrade to 16.3.x!
The database migration for 16.4.1 can fail due to unexpected name of a foreign key.
So it is recommended to have a database backup available in case the solution
described in the update manual does not work for you.
The upgrade manual can be found as usual here:
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.3-16.4-freebsd.md
20230930:
AFFECTS: users of Transmission (net-p2p/transmission@*)
AUTHOR: [email protected]
Fixes Bug 274065 by reorganizing the port as a metaport
(net-p2p/transmission) and components port (net-p2p/transmission-components).
Each component may be installed through the flavors of
transmission-componenents (@cli, @daemon, @docs, @gtk, @qt, @utils).
Alternatively, one or more component may be installed by running make config
on the metaport net-p2p/transmission.
AFFECTS: users of devel/php-composer2
AUTHOR: [email protected]
The composer2 ports has been moved over the old devel/php-composer
port, which was still providing the old EOLed version 1 of the
software.
Please use `pkg install php81-composer` (substitute 81 with the
PHP version you're using) to properly upgrade.
20230924:
AFFECTS: users of XFCE desktop (x11-wm/xfce4)
AUTHOR: [email protected]
XFCE 4.18 is incompatible with the latest version of the adwaita
icon theme (version 42.0 and newer), which was used as the default one.
Due to this the default icon theme has been changed to
x11-themes/xfce-icons-elementary.
Users that have XFCE already installed and are using the adwaita
icon theme will notice missing icons. To fix this you can install
any other icon theme (like x11-themes/xfce-icons-elementary) and
configure XFCE to use that via the "appearance" settings application,
under the "icons" tab.
20230919:
AFFECTS: users of net-p2p/transmission
AUTHOR: [email protected]
The 4.0 port haphazardly consolidated prior slave ports into flavors of a single port.
The flavors have now been revised to better match releases prior to 4.0.
The -full flavor included in the 4.0 port has been replaced with -default, which
restores the compile-time options of prior release's metaport. Other flavors allow
for more piecemeal installs. The prior -web slave port can be installed through the
-default flavor or the -daemon flavor.
See Bug 273841 for more details.
20230915:
AFFECTS: users of print/ghostscript10
AUTHOR: [email protected]
The port flavors have been replaced with a default port option of X11.
The flavors approach creates conflicting dependencies with other ports which
cannot be solved this time with the ports framework.
See PRs 270989 and 272541 for details.
20230910:
AFFECTS: users of dns/powerdns
AUTHOR: [email protected]
In Authoritative Server 4.8, the LMDB backend gains a new Lightning
Stream-compatible schema, which requires a data migration (this is
automatic, and there is no migration back to the old schema). LMDB
backend users should pay extra attention to the Upgrade Notes
(https://doc.powerdns.com/authoritative/upgrading.html).
20230910:
AFFECTS: users of net-mgmt/netbox
AUTHOR: [email protected]
1. Please make sure that the PostgreSQL server for the NetBox instance is
running version 12 or higher. This is because Django 4.2 requires
PostgreSQL 12 as a minimum.
2. Please also check the pkg-message and the changelogs for further info.
20230908:
AFFECTS: users of databases/postgresql* and other software using PostgreSQL to run
AUTHOR: [email protected]
The default version of PostgreSQL has been switched from 13 to 15.
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 13, your
files are named according to this.
# service postgresql stop
# pkg create postgresql13-server postgresql13-contrib
# mkdir /tmp/pg-upgrade
# tar xf postgresql13-server-13.12.pkg -C /tmp/pg-upgrade
# tar xf postgresql13-contrib-13.12.pkg -C /tmp/pg-upgrade
# pkg delete -f databases/postgresql13-server databases/postgresql13-contrib databases/postgresql13-client
Now update PostgreSQL:
pkg user:
# pkg install databases/postgresql15-server databases/postgresql15-contrib
# pkg upgrade
Portmaster users:
# portmaster databases/postgresql15-server databases/postgresql15-contrib
# portmaster -a
Portupgrade users:
# portinstall databases/postgresql15-server databases/postgresql15-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/data15 -U postgres"
# su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data13/ -B /usr/local/bin/ -D /var/db/postgres/data15/ -U postgres "
Now the migration is finished. You can start PostgreSQL again with:
# service postgresql start
ATTENTION:
1) The default user changed from "pgsql" to "postgres" in 11. The migration steps above now assume
the "postgres" database user and FreeBSD user.
2) See the updating entry 20190829 if you are updating from a release prior to 11.
3) If you use non-default initdb options, you have to adjust the initdb-command accordingly
20230906:
AUTHOR: [email protected]
AFFECTS: users of sysutils/devcpu-data*
The CPU microcode ports have been reorganized. The new ports are:
sysutils/cpu-microcode, sysutils/cpu-microcode-amd,
sysutils/cpu-microcode-intel, and cpu-microcode-rc.
To install all CPU microcode packages:
pkg install cpu-microcode
To install only packages for a specific CPU vendor:
pkg install cpu-microcode-amd
or
pkg install cpu-microcode-intel
To give users time to adjust to these changes, sysutils/devcpu-data will
remain in the tree until the end of 2023. The port has been converted to a
metaport and now provides the same functionality as sysutils/cpu-microcode.
Refer to the commit log in bc7829212d153aeff69b439d08e2e3001ef88ba3 for an
explanation as to why these changes were made.
20230904:
AUTHOR: [email protected]
AFFECTS: users of misc/openhab
The rc.d script of 4.0.2 had an error which didn't take the user to
run openhab into account. After installing the update and stopping
openhab run (for the default settings)
chown -R openhab:openhab /var/db/openhab/userdata /var/log/openhab
If you use other directories for the userdata and logs, you need to
adapt accordingly.
20230822:
AUTHOR: [email protected]
AFFECTS: users of sysutils/polkit together with sysutils/consolekit2
ConsoleKit2 has grown some logind1 compatibility which resulted in breaking
changes in its API. One of its consumers, Polkit, is patched to handle it,
so make sure to update both ports simultaneously.
20230822:
AUTHOR: [email protected]
AFFECTS: users of security/zeek
Zeek has been upgraded to 6.0.0 and the NETMAP option was removed;
it was too difficult to build it without zeek being installed in
%%PREFIX%%.
The consensus was that this was a rarely used feature, please
reach out to me if need this (I've done some work on a new
security/zeek-netmap port that is probably the right way forward).
When I upgraded zeek on my systems I found some cruft left over
from previous versions. The way I recommend upgrading from 5.0.9 to
6.0.0 is:
service zeek stop
pkg delete -fy zeek py311-zkg
[clean up leftover files in /usr/local/lib/zeek]
pkg install -y zeek
service zeek deploy