Note that we still ask our committers to avoid sweepting commits until
after the release is officially out the door ... just in case.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, s
Hi,
are there any plans to update x11-toolkits/py-wxPython28* to a version
which support cairo (2.8.9.0 or higher?)
I could send in a patch myself...
Regards,
Rene
--
http://www.rene-ladan.nl/
GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6
(subkeys.pgp.net)
Hello everyone.
I'm getting kernel panics everytime I try to write a file to samba share
which is a fuse mount.
I tried samba 3.0.37, 3.3.13, 3.4.8, no difference.
Tried on 8.0-RELEASE, on today's 8.1-PRERELEASE.
How to reproduce:
1. Install /usr/ports/net/samba34, /usr/ports/sysutils/fusefs-u
Hello Ollivier,
Could you update devel/mercurial to version 1.6 (released 2010-07-01)?
Thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...
On Thursday, July 08, 2010 6:12:39 pm Doug Barton wrote:
> On Thu, 8 Jul 2010, John Baldwin wrote:
>
> > This is a port for yet-another-/etc-merging tool that I wrote recently.
It
> > passes portlint -N with one bogus warning because /etc is in the comment.
>
> I didn't try installing/deinstall
--On Thursday, July 08, 2010 15:39:09 -0500 Paul Schmehl
wrote:
Building CXX object agents/ontologies/CMakeFiles/niefast.dir/nmo.o
Linking CXX static library ../../lib/libniefast.a
[ 40%] Built target niefast
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/deskutils/kdepim4-runti
Currently the PR load is obviously too high for the committer team
to deal with. From a maintainer perspective this is rather painful,
I have currently stopped updating all my ports, because I want
pending updates committed first and also want to avoid running into
PR dependencies (ioquake3, openar
I think the people you describe as 'experienced' maintainers tend to be made
committers anyway, or that's as far as I know. There's little to be gained
by putting another rank of responsibility in, especially when a commit to
any port can cause huge wreckage; INDEX building, circular dependencies e
I think the people you describe as 'experienced' maintainers tend to be made
committers anyway, or that's as far as I know. There's little to be gained
by putting another rank of responsibility in, especially when a commit to
any port can cause huge wreckage; INDEX building, circular dependencies e
On Fri, 09 Jul 2010 18:15:58 +0200
Dominic Fandrey wrote:
> Currently the PR load is obviously too high for the committer team
> to deal with. From a maintainer perspective this is rather painful,
> I have currently stopped updating all my ports, because I want
> pending updates committed first a
On 09/07/2010 18:50, Gary Jennejohn wrote:
> On Fri, 09 Jul 2010 18:15:58 +0200
> Dominic Fandrey wrote:
>
>> Currently the PR load is obviously too high for the committer team
>> to deal with. From a maintainer perspective this is rather painful,
>> I have currently stopped updating all my ports
On 09/07/2010 18:26, Chris Rees wrote:
> I think the people you describe as 'experienced' maintainers tend to be made
> committers anyway, or that's as far as I know.
What gives you that impression? ~180 committers that have been
active within the last 12 months (as in at least one commit), are
cu
On Fri, Jul 09, 2010 at 06:15:58PM +0200, Dominic Fandrey wrote:
>
> To solve this problem with the current organization, my guess is
> that between 15 and 30 new active committers are required.
> Because I don't think this is easily achieved I want to suggest
> a different approach. And I expect
On 09/07/2010 19:25, Shaun Amott wrote:
> On Fri, Jul 09, 2010 at 06:15:58PM +0200, Dominic Fandrey wrote:
>>
>> To solve this problem with the current organization, my guess is
>> that between 15 and 30 new active committers are required.
>> Because I don't think this is easily achieved I want to
On 07/09/10 05:27, John Baldwin wrote:
> On Thursday, July 08, 2010 6:12:39 pm Doug Barton wrote:
>> On Thu, 8 Jul 2010, John Baldwin wrote:
>>
>>> This is a port for yet-another-/etc-merging tool that I wrote recently.
> It
>>> passes portlint -N with one bogus warning because /etc is in the com
On 07/09/10 05:27, John Baldwin wrote:
> (I used etcmerge as a template.)
BTW, I forgot to take this opportunity to insert my traditional rant
about "this is why I'm so pedantic when it comes to removing bad code
from existing ports." :) They get used as examples, and in this case
John made a pe
hello .. i can't build kde4 on my tinderbox because
'graphics/djvulibre-nox11' port .. here is my PR .. hope some FBSDD
can solve this .. thanks
http://www.freebsd.org/cgi/query-pr.cgi?pr=147650
___
freebsd-ports@freebsd.org mailing list
http://lists.fr
hello .. i can't build kde4 on my tinderbox because
'graphics/djvulibre-nox11' port .. here is my PR .. hope some FBSDD
can solve this .. thanks
http://www.freebsd.org/cgi/query-pr.cgi?pr=147650
___
freebsd-ports@freebsd.org mailing list
http://lists.fr
On Fri, Jul 09, 2010 at 07:37:11PM +0200, Dominic Fandrey wrote:
>
> On 09/07/2010 19:25, Shaun Amott wrote:
> > On Fri, Jul 09, 2010 at 06:15:58PM +0200, Dominic Fandrey wrote:
> >>
> >> To solve this problem with the current organization, my guess is
> >> that between 15 and 30 new active commit
> I went to http://soprano.sourceforge.net and founf the following:
>
> Soprano 2.4.4 released
> Wed, 06/30/2010 - 20:20 - trueg
> Soprano 2.4.4 is a bugfix release - probably the last one before the release
> of Soprano 2.5. It features the following changes:
>
> Fix to FindIODBC.cmake which en
On 09/07/2010 22:00, Shaun Amott wrote:
> On Fri, Jul 09, 2010 at 07:37:11PM +0200, Dominic Fandrey wrote:
>>
>> On 09/07/2010 19:25, Shaun Amott wrote:
>>> On Fri, Jul 09, 2010 at 06:15:58PM +0200, Dominic Fandrey wrote:
To solve this problem with the current organization, my guess is
>>
On Fri, Jul 09, 2010 at 10:51:01PM +0200, Dominic Fandrey wrote:
> > Ok - but how do we define "experienced"? Someone who has submitted 100
> > PORTVERSION++ PRs? I'm not convinced we have enough contributors who are
> > experienced enough to be given commit rights, but not contributing
> > enough
devel/icu4 was recently updated and now installs shlibs with ABI version
44. Unfortunately this hasn't been propagated to those ports with a
LIB_DEPENDS on devel/icu4 (all three of them):
worm:/usr/ports:% grep -r 'icu.*\.43:' .
./databases/postgresql90-server/Makefile:LIB_DEPENDS+=
icudata.43:$
On Fri, 9 Jul 2010, Shaun Amott wrote:
Indeed, part of the problem is burn-out. We recruit committers, and then
their activity tapers off (I'm guilty of this myself). Part of this, I
believe, is down to the effort involved in maintaining a useful
(up-to-date) testing environment -- hence my advo
On Fri, Jul 9, 2010 at 5:27 PM, Matthew Seaman
wrote:
> However naively incrementing the shlib version in the
> databases/postgresql84-server Makefile doesn't work:
>
> ===> Configuring for postgresql-server-8.4.4_2
> checking build system type... amd64-portbld-freebsd8.1
> checking host system t
25 matches
Mail list logo
