Just to make it official, the ports slush is over.
Ports committers are now able to perform regular updates, business as usual,
no need for portmgr@ approvals.
Keep in mind that -exp runs are always a good idea if you think there is a
significant change to the ports tree.
It is anticipated that
Just to make it official, the ports slush is over.
Ports committers are now able to perform regular updates, business as usual,
no need for portmgr@ approvals.
Keep in mind that -exp runs are always a good idea if you think there is a
significant change to the ports tree.
It is anticipated that
Chris Rees utis...@gmail.com wrote:
On 21 Apr 2013 02:13, Perry Hutchison per...@pluto.rain.com wrote:
...
The question is, what (if anything) else -- besides /usr/ports,
/usr/local, /var/db/ports, and /var/db/pkg -- needs to be checkpointed?
Are you installing any drivers? You may need
Peter Pentchev r...@ringlet.net wrote:
Some ports might store run state in /var/db/portname or a similarly
named directory. The thing is, the decision whether to save this and
restore it or to keep it across runs actually depends on the port: for
database management systems such as MySQL,
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
I'd like to maintain following unmaintained (former @skv) ports:
databases/pgbouncer
www/otrs
--
Mikhail
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Just to make it official, the ports slush is over.
Ports committers are now able to perform regular updates, business as usual,
no need for portmgr@ approvals.
Keep in mind that -exp runs are always a good idea if you think there is a
significant change to the ports tree.
It is anticipated that
Just to make it official, the ports slush is over.
Ports committers are now able to perform regular updates, business as usual,
no need for portmgr@ approvals.
Keep in mind that -exp runs are always a good idea if you think there is a
significant change to the ports tree.
It is anticipated that
On Sun, 21 Apr 2013, Juergen Lock wrote:
On Sun, Apr 21, 2013 at 12:25:37PM +0200, Kurt Jaeger wrote:
Hi!
http://people.freebsd.org/~nox/tmp/google-earth-6.0.3.2197-crashfixp-001.patch
Works on 9.1-amd64.
Ok as it seems to work for everyone that tested it I just committed
the
On Sun, 21 Apr 2013, Juergen Lock wrote:
On Sun, Apr 21, 2013 at 12:25:37PM +0200, Kurt Jaeger wrote:
Hi!
http://people.freebsd.org/~nox/tmp/google-earth-6.0.3.2197-crashfixp-001.patch
Works on 9.1-amd64.
Ok as it seems to work for everyone that tested it I just committed
the
On Mon, Apr 22, 2013 at 12:46:35PM -0400, Frank Seltzer wrote:
On Sun, 21 Apr 2013, Juergen Lock wrote:
On Sun, Apr 21, 2013 at 12:25:37PM +0200, Kurt Jaeger wrote:
Hi!
http://people.freebsd.org/~nox/tmp/google-earth-6.0.3.2197-crashfixp-001.patch
Works on 9.1-amd64.
Ok
On 2013-04-22 15:34, Mikhail Tsatsenko wrote:
I'd like to maintain following unmaintained (former @skv) ports:
databases/pgbouncer
www/otrs
Hi Mikhail,
I just assigned you as maintainer for the requested ports.
Would you please review the following PR's
PR 176640 : databases/pgbouncer:
22.04.2013, 22:33, Olli Hauer oha...@freebsd.org:
On 2013-04-22 15:34, Mikhail Tsatsenko wrote:
I'd like to maintain following unmaintained (former @skv) ports:
databases/pgbouncer
www/otrs
Hi Mikhail,
I just assigned you as maintainer for the requested ports.
Would you please review
Trying to update port graphics/jasper on our FreeBSD 10.0-CURRENT boxes
(all r249720 or higher) fails on all(!) Core2Duo based systems (Intel
E8400 or Q6600) (CLANG 3.3) with the below shown error.
Interestingly, the port does compile on all boxes running the very same
FreeBSD 10.0-CURRENT with
On Apr 22, 2013, at 20:47, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
Trying to update port graphics/jasper on our FreeBSD 10.0-CURRENT boxes
(all r249720 or higher) fails on all(!) Core2Duo based systems (Intel
E8400 or Q6600) (CLANG 3.3) with the below shown error.
...
Interestingly, the
On Mon, 2013-04-22 at 21:40 +0200, Dimitry Andric wrote:
On Apr 22, 2013, at 20:47, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
Trying to update port graphics/jasper on our FreeBSD 10.0-CURRENT boxes
(all r249720 or higher) fails on all(!) Core2Duo based systems (Intel
E8400 or Q6600)
official mirrors for ports repository on github hasn't been updated for
a few days.
Does FreeBSD project quit to provide mirrors on github? or suspended
temporarily?
--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
freebsd-ports@freebsd.org
On Fri, 2013-03-22 at 11:54:14 +0200, Pavel Bychykhin wrote:
In config dialog i check OPENLDAP, LDAP_SASL and SASL2.
The make process ignores an option LDAP_SASL.
As a result i see unsupported parameter value: bind = SASL in output of
postmap command.
As a solution, i added -DUSE_LDAP_SASL
On Tue, 23 Apr 2013 10:49:00 +0900
Koichiro IWAO m...@vmeta.jp wrote:
official mirrors for ports repository on github hasn't been updated
for a few days.
Does FreeBSD project quit to provide mirrors on github? or suspended
temporarily?
possible I missed something, but.. Is a mirror on
20 matches
Mail list logo
