## Leslie Jensen (les...@eskk.nu):
> checking for dbopen in -ldb4... no
> checking for __db185_open in -ldb4... no
> configure: error: db not installed or functional
Looks as if you need to install one of databases/db[45]*.
At a quick glance through configure, I guess one of db41, db5, db48 or
d
wen heping wrote on 06.09.2011 03:35:
2011/9/5 Ruslan Mahmatkhanov:
Good day.
I want to grab maintainership of this ports:
devel/py-zopetesting
devel/py-zopeevent
net/py-zopeproxy
Now these 3 ports is yours.
Would you send a PR of repocopy to rename these ports?
Thanks.
wen
Thanks. Done
Hi,
On 9/6/11 4:02 AM, Kostik Belousov wrote:
On Mon, Sep 05, 2011 at 06:32:00PM +0100, Chris Rees wrote:
On 5 Sep 2011 18:15, "Mikhail T." wrote:
On -10.01.-28163 14:59, Chris Rees wrote:
I've had to deprecate sysutils/cfs -- there's a confirmed issue with
failing locks [1] which has been
2011/9/6 Mark Linimon :
> On Mon, Sep 05, 2011 at 05:38:06PM -0700, Doug Barton wrote:
>> My understanding is that we don't do port names with . in them. Can
>> someone who knows more than I confirm one way or the other?
>
> The porter's handbook is ambiguous:
>
> The first letter of the name part
On 09/05/2011 22:48, per...@pluto.rain.com wrote:
> Doug Barton wrote:
>> On 09/05/2011 02:33, Julian H. Stacey wrote:
> It is not responsible to threaten to remove ports without
> warning between releases for non urgent reasons.
>>
>> We understand that this is your perspective, however t
On Mon, Sep 05, 2011 at 05:38:06PM -0700, Doug Barton wrote:
> My understanding is that we don't do port names with . in them. Can
> someone who knows more than I confirm one way or the other?
The porter's handbook is ambiguous:
The first letter of the name part should be lowercase. (The rest o
On 09/05/2011 16:35, wen heping wrote:
> Would you send a PR of repocopy to rename these ports?
My understanding is that we don't do port names with . in them. Can
someone who knows more than I confirm one way or the other?
--
Nothin' ever doesn't change, but nothin' changes much.
2011/9/5 Ruslan Mahmatkhanov :
> Good day.
>
> I want to grab maintainership of this ports:
>
> devel/py-zopetesting
> devel/py-zopeevent
> net/py-zopeproxy
Now these 3 ports is yours.
Would you send a PR of repocopy to rename these ports?
Thanks.
wen
>
> But i want them to be renamed to py-
> AFAIK there are maybe half a dozen or so developers who have
> recently put themselves on record as supporting the current,
> agressive deprecation campaign. The number who have posted in
> opposition may well be smaller, so you are probably right if "the
> community" is defined as consisting on
Doug Barton wrote:
> On 09/05/2011 02:33, Julian H. Stacey wrote:
> >>> It is not responsible to threaten to remove ports without
> >>> warning between releases for non urgent reasons.
>
> We understand that this is your perspective, however the community
> in general has a different idea.
I supp
Matthias Andree wrote:
> So either Kostik, or you, or someone else steps up to maintain the port
> at least to the extent that the known security bugs and reported bugs
> get fixed, or to hell the port goes.
Recent un-professional threats to throw out ports at un-necessarily
short notice, with h
On -10.01.-28163 14:59, Doug Barton wrote:
It is not responsible to threaten to remove ports without warning
between releases for non urgent reasons.
We understand that this is your perspective, however the community in
general has a different idea.
Well, several committers are on (recent) rec
per...@pluto.rain.com wrote:
> Matthias Andree wrote:
> > > I agree, but I can think of another valid exception. System with
> > > Hamming correction on the memory, gets a single bit (correctable)
> > > error. Need to rewrite the memory contents to reset all the parity
> > > bits!
> > That's
Am 05.09.2011 20:29, schrieb Mikhail T.:
> On 05.09.2011 13:32, Chris Rees wrote:
>> If it's not that hard to fix then do it.
> Before doing it, I wanted to confirm, that there are no other, more
> serious vulnerabilities.
>
> Things, for which no fixes have been posted -- unlike for this
> partic
On 05.09.2011 13:32, Chris Rees wrote:
If it's not that hard to fix then do it.
Before doing it, I wanted to confirm, that there are no other, more
serious vulnerabilities.
Things, for which no fixes have been posted -- unlike for this
particular one, which Debian fixed several years ago (bef
On Mon, Sep 05, 2011 at 06:32:00PM +0100, Chris Rees wrote:
> On 5 Sep 2011 18:15, "Mikhail T." wrote:
> >
> > On -10.01.-28163 14:59, Chris Rees wrote:
> >>>
> >>> I've had to deprecate sysutils/cfs -- there's a confirmed issue with
> >>> failing locks [1] which has been open for two years with n
On 5 Sep 2011 18:15, "Mikhail T." wrote:
>
> On -10.01.-28163 14:59, Chris Rees wrote:
>>>
>>> I've had to deprecate sysutils/cfs -- there's a confirmed issue with
>>> failing locks [1] which has been open for two years with no fix.
>>>
>>
>> Whoops, also missed a CVE -- buffer overflows can cause
On -10.01.-28163 14:59, Chris Rees wrote:
I've had to deprecate sysutils/cfs -- there's a confirmed issue with
failing locks [1] which has been open for two years with no fix.
Whoops, also missed a CVE -- buffer overflows can cause a DoS.
Expiration date altered to 1 month accordingly.
Is thi
On Sun, 28 Aug 2011 21:05:11 -0500
"Conrad J. Sabatier" wrote:
> I'm wondering how other ports maintainers are dealing with their
> definitions of MASTER_SITES=, DISTFILES=, DISTNAME=, etc. with regards
> to Sourceforge.
>
> In browsing a number of projects recently on Sourceforge, I've noticed
On Mon, Sep 05, 2011 at 06:11:33PM +0200, Christoph Moench-Tegeder wrote:
> ## Baptiste Daroussin (b...@freebsd.org):
>
> > > Looks like it may be related to this commit:
> > >
> > > http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/libreoffice/files/patch-bin__distro-install-desktop-integratio
Am 05.09.2011 11:09, schrieb per...@pluto.rain.com:
> Matthias Andree wrote:
>>> I agree, but I can think of another valid exception. System with
>>> Hamming correction on the memory, gets a single bit (correctable)
>>> error. Need to rewrite the memory contents to reset all the parity
>>> bits!
>
## Baptiste Daroussin (b...@freebsd.org):
> > Looks like it may be related to this commit:
> >
> > http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/libreoffice/files/patch-bin__distro-install-desktop-integration
> >
> > Bapt, please would you investigate?
> >
> > Chris
> >
>
> I just fixed
Hi,
Doug Barton wrote:
> On 09/05/2011 02:33, Julian H. Stacey wrote:
> > Chris Rees wrote:
> >> On 4 September 2011 21:32, Julian H. Stacey wrote:
>
> Whoops, also missed a CVE -- buffer overflows can cause a DoS.
> Expiration date altered to 1 month accordingly.
> >>>
> >>> It is
On Mon, Sep 05, 2011 at 03:52:35PM +0100, Chris Rees wrote:
> On 5 September 2011 15:16, Leslie Jensen wrote:
> > 2011-09-05 15:51, Chris Rees skrev:
> >>
> >> On 5 Sep 2011 14:45, "Leslie Jensen" wrote:
> >>> ===> libreoffice-3.4.3 depends on file: /usr/local/bin/perl5.14.1 -
> >>
> >> found
On 5 September 2011 15:16, Leslie Jensen wrote:
> 2011-09-05 15:51, Chris Rees skrev:
>>
>> On 5 Sep 2011 14:45, "Leslie Jensen" wrote:
>>> ===> libreoffice-3.4.3 depends on file: /usr/local/bin/perl5.14.1 -
>>
>> found
>>>
>>> ===> Applying FreeBSD patches for libreoffice-3.4.3
>>> 1 out of
2011-09-05 15:51, Chris Rees skrev:
On 5 Sep 2011 14:45, "Leslie Jensen" wrote:
===>libreoffice-3.4.3 depends on file: /usr/local/bin/perl5.14.1 -
found
===> Applying FreeBSD patches for libreoffice-3.4.3
1 out of 4 hunks failed--saving rejects to
bin/distro-install-desktop-integrat
On 5 Sep 2011 14:45, "Leslie Jensen" wrote:
>
>
>
> ===> libreoffice-3.4.3 depends on file: /usr/local/bin/perl5.14.1 -
found
> ===> Applying FreeBSD patches for libreoffice-3.4.3
> 1 out of 4 hunks failed--saving rejects to
bin/distro-install-desktop-integration.rej
> => Patch patch-bin__distr
===> libreoffice-3.4.3 depends on file: /usr/local/bin/perl5.14.1 - found
===> Applying FreeBSD patches for libreoffice-3.4.3
1 out of 4 hunks failed--saving rejects to
bin/distro-install-desktop-integration.rej
=> Patch patch-bin__distro-install-desktop-integration failed to apply
cleanly.
Hi,Ruslan:
Do you have the plan to import Zope-2.13 into portstree?
I could run zope-2.13 on FreeBSD correctly with python-2.7, but
many new ports should be created if we import zope-2.13.
If you have the plan, give me a message and I am intersting of it.
wen
2011/9/5 Ruslan Mahmatkha
Hi,
so, all the consumers of devel/py-[c]elementtree ports are now handled.
After all of this patches will be committed, it's safe to remove this
py-[c]elementtree ports from the tree.
devel/boost-pyste - http://bugs.freebsd.org/159869 [x]
news/py-pynzb - http://bugs.freebsd.org/159867 [x
On 09/05/2011 02:33, Julian H. Stacey wrote:
> Chris Rees wrote:
>> On 4 September 2011 21:32, Julian H. Stacey wrote:
Whoops, also missed a CVE -- buffer overflows can cause a DoS.
Expiration date altered to 1 month accordingly.
>>>
>>> It is not responsible to threaten to remove p
Good day.
I want to grab maintainership of this ports:
devel/py-zopetesting
devel/py-zopeevent
net/py-zopeproxy
But i want them to be renamed to py-zope.testing, py-zope.event and
py-zope.proxy respectively to match upstream projectnames and to
consistency with other current and upcoming zope
Michel Talon wrote on 04.09.2011 11:29:
Ruslan wrote:
Hi, i maintain port (sysutils/rdup) that is failing with clang:
I have looked at the problem, it is indeed in rdup source. If you look
at rdup git history for rdup-tr.c you will see
remove rdup_entry_c from the code, totally unnee
Ivan Klymenko wrote on 04.09.2011 11:12:
В Sun, 04 Sep 2011 10:42:07 +0400
Ruslan Mahmatkhanov пишет:
Roman Divacky wrote on 25.07.2011 19:59:
Hi!
Flz@ just run another exp-build with CC=clang and CXX=clang++. The
results can be seen here:
http://pointyhat.freebsd.org/errorlogs/amd64-erro
per...@pluto.rain.com wrote:
> Chris Rees wrote:
> > Whoops, also missed a CVE -- buffer overflows can cause a DoS.
>
> Er, am I the only one who does not recognize what "CVE" stands for?
"CVE" == Common Vulnerabilities and Exposures
To put it simply, it's a database of security threats
mai
On 5 Sep 2011 11:06, "Julian H. Stacey" wrote:
>
> Mark Linimon wrote:
> > On Sun, Sep 04, 2011 at 10:32:30PM +0200, Julian H. Stacey wrote:
> > > It is not responsible to threaten to remove ports without warning
> > > between releases for non urgent reasons.
> >
> > portmgr has no such policy.
>
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
No matches t
(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 obsol
On 09/05/2011 02:53, Simon L. B. Nielsen wrote:
> Hey,
>
> Just FYI, I accidentally stopped the jail which built the portaudit database
> a few days ago and didn't notice since I had forgotten the portaudit database
> was actually built there. It has been fixed now.
Thank you! :)
--
Mark Linimon wrote:
> On Sun, Sep 04, 2011 at 10:32:30PM +0200, Julian H. Stacey wrote:
> > It is not responsible to threaten to remove ports without warning
> > between releases for non urgent reasons.
>
> portmgr has no such policy.
>
> Ports get deleted all the time due to various issues. I p
Hey,
Just FYI, I accidentally stopped the jail which built the portaudit database a
few days ago and didn't notice since I had forgotten the portaudit database was
actually built there. It has been fixed now.
--
Simon L. B. Nielsen
signature.asc
Description: Message signed with OpenPGP usin
Chris Rees wrote:
> On 4 September 2011 21:32, Julian H. Stacey wrote:
> >>
> >> Whoops, also missed a CVE -- buffer overflows can cause a DoS.
> >> Expiration date altered to 1 month accordingly.
> >
> > It is not responsible to threaten to remove ports without warning
> > between releases for no
42 matches
Mail list logo