FreeBSD Monitor - Feeds::ports_updating http://www.fbsdmon.org/feed/ports_updating 2014-10-19T23:59:59Z FreeBSD Monitor ports_updating http://www.fbsdmon.org/feed/ports_updating/8704b99c36b731746e9a 2014-10-19T23:59:59Z AFFECTS: users of x11/kde4-runtime<br />AUTHOR: kde@FreeBSD.org<br />KDE SC ports have been updated to 4.14.1. Several files have been<br />moved between packages, therefore the following action is required<br />before running any pkg/port upgrade utility:<br /><br /># pkg delete -f kde-runtime-4\* ports_updating http://www.fbsdmon.org/feed/ports_updating/a7baa3c566e3ff8f5335 2014-10-08T23:59:59Z AFFECTS: users of lang/ruby19<br />AUTHOR: swills@FreeBSD.org<br /><br />The default ruby version has been updated from 1.9 to 2.0. <br /><br />If you compile your own ports you may keep 1.9 as the default version by<br />adding the following lines to your /etc/make.conf file:<br /><br />#<br /># Keep ruby 1.9 as default version<br />#<br />DEFAULT_VERSIONS+=ruby=1.9<br /><br />If you wish to update to the new default version, you need to first stop any<br />software that uses ruby. Then, you will need to follow these steps, depending<br />upon how you manage your system.<br /><br />If you use pkgng, simply upgrade:<br /># pkg upgrade<br /><br />If you use portmaster, install new ruby, then rebuild all ports that depend<br />on ruby:<br /># portmaster -o lang/ruby20 lang/ruby19<br /># portmaster -R -r ruby-2.0<br /><br />If you use portupgrade, install new ruby, then rebuild all ports that depend<br />on ruby:<br /><br /># pkg delete -f ruby ruby-iconv portupgrade<br /># make -C /usr/ports/ports-mgmt/portupgrade install clean<br /># portupgrade -x ruby-2.0.\* -fr lang/ruby20 ports_updating http://www.fbsdmon.org/feed/ports_updating/5d42e1cde87166c1cedb 2014-10-08T23:59:59Z AFFECTS: users of lang/ruby19<br />AUTHOR: swills@FreeBSD.org<br /><br />The default ruby version has been updated from 1.9 to 2.0. <br /><br />If you compile your own ports you may keep 1.9 as the default version by<br />adding the following lines to your /etc/make.conf file:<br /><br />#<br /># Keep ruby 1.9 as default version<br />#<br />DEFAULT_VERSIONS+=ruby=1.9<br /><br />If you wish to update to the new default version, you need to first stop any<br />software that uses ruby. Then, you will need to follow these steps, depending<br />upon how you manage your system.<br /><br />If you use pkgng, simply upgrade:<br /># pkg upgrade<br /><br />If you use portmaster, install new ruby, then rebuild all ports that depend<br />on ruby:<br /># portmaster -o lang/ruby20 lang/ruby19<br /># portmaster -R -r ruby-2.0<br /><br />If you use portupgrade, install new ruby, then rebuild all ports that depend<br />on ruby:<br /><br /># pkg delete -f ruby ruby-iconv portupgrade<br /># make -C /usr/ports/ports-mgmt/portupgrade install clean<br /># pkg set -o lang/ruby19:lang/ruby20<br /># portupgrade -x ruby-2.0.\* -fr lang/ruby20 ports_updating http://www.fbsdmon.org/feed/ports_updating/dacc7b1eaea0c53001d8 2014-10-08T23:59:59Z AFFECTS: users of lang/ruby19<br />AUTHOR: swills@FreeBSD.org<br /><br />The default ruby version has been updated from 1.9 to 2.0. <br /><br />If you compile your own ports you may keep 1.9 as the default version by<br />adding the following lines to your /etc/make.conf file:<br /><br />#<br /># Keep ruby 1.9 as default version<br />#<br />DEFAULT_VERSIONS+=ruby=1.9<br /><br />If you wish to update to the new default version, you need to first stop any<br />software that uses ruby. Then, you will need to follow these steps, depending<br />upon how you manage your system.<br /><br />If you use pkgng, simply upgrade:<br /># pkg upgrade<br /><br />If you use portmaster, install new ruby, then rebuild all ports that depend<br />on ruby:<br /># portmaster -o lang/ruby20 lang/ruby19<br /># portmaster -R -r ruby-2.0<br /><br />If you use portupgrade, install new ruby, then rebuild all ports that depend<br />on ruby:<br /><br /># pkg delete -f ruby portupgrade<br /># make -C /usr/ports/ports-mgmt/portupgrade install clean<br /># portupgrade -x ruby-2.0.\* -fr lang/ruby20 ports_updating http://www.fbsdmon.org/feed/ports_updating/8ffee2b58a2893515a81 2014-10-03T23:59:59Z AFFECTS: xorg users<br />AUTHOR: bapt@FreeBSD.org<br /><br />The WITH_NEW_XORG setting has been activated by default on all versions<br />of FreeBSD, which allows us to have packages for xorg 1.12 and kde4.<br /><br />Please be aware that on systems that only support syscons<br />switching virtual terminals or exiting X<br />results in a black screen or the last image of their desktop<br />(like a screenshot) being presented. Commands can still be typed blindly.<br /><br />Most, if not all, systems should be using vt(4) and this can be enabled<br />by setting kern.vty=vt in /boot/loader.conf and reboot to activate. ports_updating http://www.fbsdmon.org/feed/ports_updating/012499258903ee2b5874 2014-10-01T23:59:59Z AFFECTS: xorg users<br />AUTHOR: bapt@FreeBSD.org<br /><br />The WITH_NEW_XORG setting has been activated by default on FreeBSD 10.0<br />and above, which allows us to have packages for xorg 1.12 and kde4.<br /><br />Please be aware that on systems that only support syscons<br />switching virtual terminals or exiting X<br />results in a black screen or the last image of their desktop<br />(like a screenshot) being presented. Commands can still be typed blindly.<br /><br />Most, if not all, systems should be using vt(4) and this can be enabled<br />by setting kern.vty=vt in /boot/loader.conf and reboot to activate. ports_updating http://www.fbsdmon.org/feed/ports_updating/92dcff967281ff2509e8 2014-09-30T23:59:59Z AFFECTS: users of mail/maildrop<br />AUTHOR: madpilot@FreeBSD.org<br /><br />Due to the way pkg works please note that the configuration<br />variables MAILDROP_SUID and MAILDROP_SGID, despite keeping their<br />old names, are now required to contain a valid username and<br />groupname existing on the system in which the package will be<br />installed, while in the past numeric uids and gids worked fine.<br /><br />Wrong values will cause pkg to skip installing the setuid binaries<br />on the system.<br /><br />Please check your configuration. ports_updating http://www.fbsdmon.org/feed/ports_updating/bc26f1e0f3c5aae1602a 2014-09-30T23:59:59Z AFFECTS: users of finance/gnucash<br />AUTHOR: madpilot@FreeBSD.org<br /><br />The new version of gnucsh requires guile 2.0. If the update fails<br />because the old guile 1.8 library is still present you will need<br />to manally remove gnucash, guile and, if installed, boehm-gc:<br /><br /># pkg delete gnucash guile boehm-gc<br /><br />and then install gnucash again the usual way. ports_updating http://www.fbsdmon.org/feed/ports_updating/5eb8b66e2d569efe3f3e 2014-09-29T23:59:59Z AFFECTS: users of comms/usbmuxd<br />AUTHOR: avilla@FreeBSD.org<br /><br />libusbmuxd.so was split from comms/usbmuxd into comms/libusbmuxd.<br />Remove usbmuxd before upgrading to avoid conflicts:<br /><br /># pkg delete -f usbmuxd<br /><br />If you need the daemon usbmuxd(1), you can reinstall the package<br />after the upgrade. ports_updating http://www.fbsdmon.org/feed/ports_updating/1bb4676ddb2cc7e71513 2014-09-28T23:59:59Z AFFECTS: users of deskutils/calibre<br />AUTHOR: madpilot@FreeBSD.org<br /><br />The dependency on graphics/py-imaging in calibre has been changed<br />to using the graphics/py-pillow port.<br /><br />Due to this change automatic updating of the port will not work<br />correctly.<br /><br />It is suggested to remove calibre and py-imaging from the system<br />and then reinstall calibre again using binary packages or ports. ports_updating http://www.fbsdmon.org/feed/ports_updating/80e502a2cb26de1af2d0 2014-09-27T23:59:59Z AFFECTS: users of net/foreman-proxy<br />AUTHOR: mm@FreeBSD.org<br /><br />In version 1.6 Foreman Smart Proxy splits its configuration into multiple<br />ruby files located in PREFIX/etc/foreman-proxy/settings.d.<br />The configuration of each service (dhcp, dhs, bmc, etc.) has been moved<br />into a dedicated file. <br /><br />You can use a bundled script to convert your old settings to new settings:<br />PREFIX/share/foreman/extra/migrate_settings.rb ports_updating http://www.fbsdmon.org/feed/ports_updating/6827f3a869e7953c6acd 2014-09-26T23:59:59Z AFFECTS: users of shells/bash<br />AUTHOR: bdrewery@FreeBSD.org<br /><br />Bash supports a feature of exporting functions in the environment with<br />export -f. Running bash with exported functions in the environment will<br />then import those functions into the environment of the script being ran.<br />This resulted in security issues CVE-2014-6271 and CVE-2014-7169, commonly<br />known as "shellshock". It also can result in poorly written scripts being<br />tricked into running arbitrary commands. <br /><br />To fully mitigate against this sort of attack we have applied a non-upstream<br />patch to disable this functionality by default. You can execute bash<br />with --import-functions to allow it to import functions from the<br />environment. The default can also be changed in the port by selecting the<br />IMPORTFUNCTIONS option. ports_updating http://www.fbsdmon.org/feed/ports_updating/3c3166bfe732d713f92a 2014-09-26T23:59:59Z AFFECTS: users of shells/bash<br />AUTHOR: bdrewery@FreeBSD.org<br /><br />Bash supports a feature of exporting functions in the environment with<br />export -f. Running bash with exported functioned in the environment will<br />then import those functions into the environment. This resulted in<br />security issues CVE-2014-6271 and CVE-2014-7169, commonly known as<br />"shellshock".<br /><br />To fully mitigate against this sort of attack we have applied a non-upstream<br />patch to disable this functionality by default. You can execute bash<br />with --import-functions to allow it to import functions from the<br />environment. The default can also be changed in the port by selecting the<br />IMPORTFUNCTIONS option. ports_updating http://www.fbsdmon.org/feed/ports_updating/8dea9aa19696cb6b8c85 2014-09-26T23:59:59Z AFFECTS: users of net/asterisk and net/asterisk11<br />AUTHOR: madpilot@FreeBSD.org<br /><br />The asterisk ports have been modified to have the LUA option<br />turned on by default to make such functionality available to users<br />of binary packages.<br /><br />Some care should be taken before upgrading by people not using lua<br />to avoid the sample extensions.lua file from being loaded on reload<br />after updating the asterisk port/pkg.<br /><br />Users compiling from ports not interested in LUA support are advised<br />to disable the option before updating.<br /><br />People using binary packages(or not wanting to disable the LUA<br />option in the port) not using the lua functionality should add:<br /><br />noload =&gt; pbx_lua.so <br /><br />to the PREFIX/etc/asterisk/modules.conf file, if using the<br />autoload=yes option in that same file. People not autoloading<br />modules don't need to perform any special action.<br /><br />If asterisk is rebooted and the pbx_lua module gets loaded on a<br />system were it should not, it will load the example extensions.lua<br />configuration file adding unexpected logic to your dialplan. In<br />such a case following the above steps and reloading asterisk will<br />fix the problem. ports_updating http://www.fbsdmon.org/feed/ports_updating/f5fb3d1bf88f18137093 2014-09-22T23:59:59Z AFFECTS: users of emulators/linux_base-f10 and emulators/linux_base-c6<br />AUTHOR: xmj@FreeBSD.org<br /><br />The complete drop-in replacement linux-c6 port infrastructure is in<br />ports and will shortly replace the current linux-f10- ports as default.<br /><br />To switch to the linux-c6 infrastructure:<br /><br />0. Back up all your vital information!<br />1. Remove the current linux base port and all linux-f10- ports:<br /> # pkg delete -f linux_base-f10 linux-f10-\*<br />2. Add these lines to /etc/make.conf:<br /> OVERRIDE_LINUX_BASE_PORT=c6<br /> OVERRIDE_LINUX_NONBASE_PORTS=c6<br />3. Make sure no Linux application is running.<br />4. Update the Linux kernel version in /etc/sysctl.conf:<br /> compat.linux.osrelease=2.6.18<br /> Make it take effect immediately:<br /> # sysctl compat.linux.osrelease=2.6.18<br />5. Install emulators/linux-c6.<br /><br />These steps are usually sufficient. If there are difficulties, expand<br />step 1 to:<br /><br />1a. Remove all ports which depend on the linux base port.<br />1b. Remove the linux base port.<br />1c. Clean the /compat/linux/ directory.<br /><br />If there are any other difficulties not fixed by these extended steps,<br />please submit an issue report in Bugzilla and send an email to<br />FreeBSD's emulation@ mailing list. ports_updating http://www.fbsdmon.org/feed/ports_updating/6719405ec17a729733ea 2014-09-22T23:59:59Z AFFECTS: users of emulators/linux_base-f10 and emulators/linux_base-c6<br />AUTHOR: xmj@FreeBSD.org<br /><br />The complete drop-in replacement linux-c6 port infrastructure is in ports <br />and will shortly replace the current linux-f10- ports as default.<br /><br />To switch to the linux-c6 infrastructure you should:<br /><br />0. Backup all your vital information!<br />1. Remove the current linux base port and all linux-f10- ports.<br />2. Add the following lines to /etc/make.conf:<br /> OVERRIDE_LINUX_BASE_PORT=c6<br /> OVERRIDE_LINUX_NONBASE_PORTS=c6<br />3. Make sure no linux application is running.<br />4. Set appropriate sysctl (compat.linux.osrelease=2.6.18).<br />5. Install emulators/linux-c6.<br /><br />That should be enough in most circumstances. If you experience difficulties,<br />please be sure to expand step 1 to:<br /><br />1a. Remove all ports which depend on linux base port.<br />1b. Remove linux base port.<br />1c. Clean /compat/linux/ directory.<br /><br />Should you encounter any other difficulties not fixed by these extended<br />steps, please submit an issue report in Bugzilla and send an email to FreeBSD's<br />emulation@ mailing list. ports_updating http://www.fbsdmon.org/feed/ports_updating/ba53d2e3a41cc4a0d3dd 2014-09-22T23:59:59Z AFFECTS: users of emulators/linux_base-f10 and emulators/linux_base-c6<br />AUTHOR: xmj@FreeBSD.org<br /><br />The complete drop-in replacement linux-c6 port infrastructure is in ports <br />and will shortly replace the current linux-f10- ports as default.<br /><br />To switch to the linux-c6 infrastructure you should:<br /><br />0. Backup all your vital information!<br />1. Remove the current linux base port and all linux-f10- ports.<br />2. Add the following lines to /etc/make.conf:<br /> OVERRIDE_LINUX_BASE_PORT=c6<br /> OVERRIDE_LINUX_NONBASE_PORTS=c6<br />3. Make sure no linux application is running.<br />4. Set appropriate sysctl (compat.linux.osrelease=2.6.18).<br />5. Install emulation/linux-c6.<br /><br />That should be enough in most circumstances. If you experience difficulties,<br />please be sure to expand step 1 to:<br /><br />1a. Remove all ports which depend on linux base port.<br />1b. Remove linux base port.<br />1c. Clean /compat/linux/ directory.<br /><br />Should you encounter any other difficulties not fixed by these extended<br />steps, please submit an issue report in Bugzilla and send an email to FreeBSD's<br />emulation@ mailing list. ports_updating http://www.fbsdmon.org/feed/ports_updating/9756bf2b52e5c56a8354 2014-09-09T23:59:59Z AFFECTS: users seeing build errors about missing *.la files<br />AUTHOR: tijl@FreeBSD.org<br /><br />We are in the process of adjusting or, if possible, removing libtool archives<br />(*.la files) from all ports because they can otherwise cause overlinking<br />between packages. This is the problem where in the dependency chain A-&gt;B-&gt;C<br />an extra link is added from A to C even if A does not use C directly. This<br />makes some updates to port C expensive because then both A and B have to be<br />rebuilt instead of just B.<br /><br />This is mostly behind the scenes work that you won't notice. In fact most<br />ports have already been converted. You may however run into build errors<br />about missing *.la files if a port update in the past went wrong and left<br />behind *.la files with references to other *.la files that are no longer<br />there. In this case, please run the following command:<br /><br />find /usr/local/lib -name '*.la' | xargs grep -l 'libfoo\.la' | xargs pkg which<br />(Replace libfoo\.la with the *.la file that is missing.)<br /><br />This command will print a list of *.la files that refer to the missing *.la<br />file and what package they belong to. First, where it says "not found in the<br />datatbase", remove the *.la file. After removing all such files, where it<br />says "installed by package X", rebuild X. Eventually the list printed by<br />that command will be empty and the build error should be gone. ports_updating http://www.fbsdmon.org/feed/ports_updating/e5c1e9daea41a20d51d4 2014-08-26T23:59:59Z AFFECTS: users of ports-mgmt/pkg, ports-mgmt/pkg-devel<br />AUTHOR: bdrewery@FreeBSD.org<br /><br />Pkg has been updated to 1.3.7. This fixes registration and tracking of<br />shared libraries. All earlier versions of Pkg incorrectly marked some<br />shared libraries and used the wrong name for some.<br /><br />Please note announcement for special instructions at:<br /> http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-August/000086.html<br /><br />- Users need to run 'pkg update -f' and 'pkg check -Ba' after upgrading to<br /> pkg-1.3.7 and before updating any other packages. This avoids needing to<br /> reinstall anything not needed due to changed shlibs.<br /> For binary package users:<br /> # pkg install ports-mgmt/pkg<br /> # pkg update -f<br /> # pkg check -Ba<br /> # pkg upgrade<br /> For port users:<br /> # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean<br /> # pkg check -Ba<br />- People building packages for serving to other systems need to rebuild<br /> all packages with 1.3.7. ports_updating http://www.fbsdmon.org/feed/ports_updating/05b5de625f2d1b11a48f 2014-08-23T23:59:59Z AFFECTS: users of graphics/libjpeg-turbo<br />AUTHOR: adamw@FreeBSD.org<br /><br />libjpeg-turbo installs its own unique library (libturbojpeg.so) and<br />a drop-in replacement for libjpeg.so. The drop-in replacement has been<br />split off into graphics/jpeg-turbo; libjpeg-turbo now installs only<br />libturbojpeg.so.<br /><br />If you were using the libjpeg.so from graphics/libjpeg-turbo, you<br />should install graphics/jpeg-turbo AFTER upgrading the libjpeg-turbo<br />port.