HEADS UP: change default Perl version to 5.10
Hi. Default Perl version is changed to 5.10. This change does not affect systems with already installed Perl (5.8 or 5.10). Only for systems without installed Perl new 5.10 port will be used. If you have already installed lang/perl5.8 and want switch to lang/perl5.10 please follow instructions: Portupgrade users: 0) Fix pkgdb.db (for safety): pkgdb -Ff 1) Reinstall perl with new 5.10: portupgrade -o lang/perl5.10 -f perl-5.8.\* 2) Reinstall everything that depends on Perl: portupgrade -fr perl Portmaster users: portmaster -o lang/perl5.10 lang/perl5.8 portmaster -r perl- Note: If the "perl-" glob matches more than one port you will need to specify the name of the perl directory in /var/db/pkg explicitly. -- Sergey Skvortsov mailto: s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_version notification and perl
On 15.07.2010 15:05, Naram Qashat wrote: > On 07/15/10 06:41, Jerry wrote: >> I just ran 'portsnap' to update my port tree, followed >> by "/usr/sbin/pkg_version -vIL=" which produced this output: >> >> These ports need updating: >> perl-5.10.1_1>succeeds index (index has 5.10.1) >> startup-notification-0.10<needs updating (index has 0.10_1) >> >> You will notice the discrepancy with perl. This never occurred before. >> Is there something wrong on my system or does the problem exist >> elsewhere? > > There is a typo in the Makefile for perl5.10, PORTREVISION is missing an > I, it says PORTREVISON instead. Fixed :( -- Sergey Skvortsov mailto: s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/perl5.12 segfault (amd64 - 8-STABLE)
On 17.07.2010 8:18, Mario Sergio Fujikawa Ferreira wrote: > Hi, > > I am running 8-STABLE as of July 1st 2010. > > FreeBSD exxodus.fedaykin.here 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #14: Thu > Jul 1 12:50:38 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 > > With latest ports as of July 14th 2010. > > I've been trying to build perl5.12 since its addition to > the ports tree without success. The ports tree is up to date as of > today. > > The build always produces segmentation faults. The relevant > part of the build log follows: Fixed. Problem was with -lpth linking (THREADS option). Please update ports tree and install port again. Sorry for the inconvenience. -- Sergey Skvortsov mailto: s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: new perl / perl-after-upgrade
On 16.09.2010 10:20, Christer Solskogen wrote: > After upgrading perl to 5.12.2_1 running perl-after-upgrade showed > that no files will be moved. And that is a little wierd when there are > a lot of files left in /usr/local/lib/perl5/5.12.1. Is that script > working as expected? Fixed, thanks for garga@ Please update Ports tree and reinstall lang/perl5.12. Or, manually patch "perl-after-upgrade" from here: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150622 and rerun. -- Sergey Skvortsov mailto: s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: otrs-2.4.9
On 30.11.2010 21:01, Piotr Byliński wrote: > Hello, > > Is it possible to know when will otrs-3 > be available in freebsd ports ? Committed. -- Sergey Skvortsov mailto: s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: p5-DBD-mysql-4.018
On 19.05.2011 0:38, Joseph Mingrone wrote: > Hello, > > I see the following error during the build: > > dbdimp.c: In function 'mysql_db_FETCH_attrib': > dbdimp.c:2447: error: 'sv_undef' undeclared (first use in this function) > > % uname -a > FreeBSD awarnach.mathstat.dal.ca 8.0-RELEASE-p4 FreeBSD 8.0-RELEASE-p4 > #0: Mon Jul 12 20:55:11 UTC 2010 > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > If any other information is helpful or if you would like me to create > a PR, just let me know. Please update port, this issue is fixed in 4.019 (just committed). -- Sergey Skvortsov mailto: s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: bugzilla-3.6.4_1
On 04.06.2011 3:03, Wilson, Bruce wrote: > Hi, > > I’m gearing up to move my older Bugzilla install to a new server, and > was hoping to install Bugzilla 4 via port. Is this update on your > radar? At a guess, will it be available in weeks, months, or next year? Committed. -- Sergey Skvortsov mailto: s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: UID/GID dynamic allocation in net/isc-dhcp3-server: why?
On 11.11.2006 23:37, Simon L. Nielsen wrote:
>
>> I don't like the current behaviour of the net/isc-dhcp3-server port
>> of creating 'dhcpd' user and group using dynamic allocation instead of
>> having static one (as specified in /usr/ports/{U,G}IDs). I like the idea
>> of [ug]id ranges, and dynamic allocation doesn't keep within this idea
>> (ids of users and daemons get mixed). Is there specific reason why there
>> is no static [ug]id for net/isc-dhcp3-server?
>
> Personally I have it precisely the other way around - I find the
> static allocations rather annoying since they are bound to collide
> with existing UID's at some point.
I disagree because static allocation is _very_ useful when you install
many similar applications into several jails on the same host machine.
Otherwise, if you'll use dynamic *ID allocation even simple "top" on
host machine may show very strange and inadequate results if identical
services are running with different UIDs.
Static allocation is simple and robust way to force synchronized *ID
allocation on jails, all other ways seem to be too complicated.
Users should manage their *IDs via "pw" to avoid conflicts.
Moreover I think we need to extend "pw" functionality: check
${PORTSDIR}/[UG]IDs file while creating new account for possible
conflicts - at least show relevant warning message if (user|group)name
mismatch canonical (U|D)ID.
--
Sergey Skvortsov
mailto: [EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
