On Tue, Sep 06, 2011 at 09:15:01PM -0700, Doug Barton wrote:
> On 09/07/2011 00:07, per...@pluto.rain.com wrote:
> >
> > How is it impractical to, as a rule, set an expiration date based on
> > an anticipated future release date rather than only a month or two
> > out from when the decision is mad
On Thu, 01 Sep 2011 15:33:02 +0200
"Julian H. Stacey" mentioned:
> Hi,
> Suggestion: pkgdb is too cryptic even with -v,
> it needs more explanation what it is up to &
> particularly what decisions it asks from user
>
Hi, Julian!
Thanks for the great suggestions, I will try to improve the
mess
Hi,
I want to maintain this ports:
mail/milter-greylist-devel
dns/py-adns
dns/checkdns
Thanks!
--
Mikhail
m.tsatse...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send an
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
Warning: Duplicate INDEX entry: xforms-1.0.93.s1,1
Committers on the hook:
az bapt beat culot dougb gahr sbz stas tobez
Most recent CVS update was:
U audio/rubyripper/Makefile
U comms/echolinux/Makefile
U comms/echolinux/fi
On Wed, 07 Sep 2011 01:04:38 +0200
Matthias Andree articulated:
> Greetings,
>
> apparently the new /etc/ssl/cert.pem file installed by
> security/ca_root_nss trips up the OpenSSL 0.9.8e in the 7.3-RELEASE
> base system. I haven't tested 7.4, 8.1 or 8.2, 8-STABLE is unaffected
> by the problem.
>
Doug Barton wrote:
> On 09/07/2011 00:07, per...@pluto.rain.com wrote:
> > Doug Barton wrote:
> >>> Better to deprecate such non urgent ports, & wait a while
> >>> after next release is rolled, to give release users a warning
> >>> & some time to volunteer ...
>
> That's an
Hi!
> One thing I've seen come up that I definitely think would be a good idea,
> though, is more accessible documentation of the CVS "attic", though.
http://www.freebsd.org/cgi/cvsweb.cgi/ports/?hideattic=0#dirlist
For example, net/ztelnet is no longer in the ports, but:
http://www.freebsd.org
On 2011-Sep-06 23:30:04 -0700, Stanislav Sedov wrote:
>What about requiring that the ports deprecated should be either broken
>or have known published vulnerabilties for a long period of
>time (say 6 months) for the start?
This might be reasonable for broken ports but ports with known
vulnerabili
On Wed, Sep 07, 2011 at 09:37:07PM +1000, Peter Jeremy wrote:
> On 2011-Sep-06 23:30:04 -0700, Stanislav Sedov wrote:
> >What about requiring that the ports deprecated should be either broken
> >or have known published vulnerabilties for a long period of
> >time (say 6 months) for the start?
>
>
___
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"
Erik Trulsson wrote:
> On Wed, Sep 07, 2011 at 09:37:07PM +1000, Peter Jeremy wrote:
> > On 2011-Sep-06 23:30:04 -0700, Stanislav Sedov wrote:
> > > What about requiring that the ports deprecated should be either broken
> > > or have known published vulnerabilties for a long period of
> > > t
On Wed, Sep 07, 2011 at 12:53:31PM +0200, Kurt Jaeger wrote:
> >
> > One thing I've seen come up that I definitely think would be a good idea,
> > though, is more accessible documentation of the CVS "attic", though.
>
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/?hideattic=0#dirlist
>
> For exam
On Wed, Sep 07, 2011 at 09:37:07PM +1000, Peter Jeremy wrote:
> On 2011-Sep-07 01:35:54 -0600, Chad Perrin wrote:
> >
> > One thing I've seen come up that I definitely think would be a good
> > idea, though, is more accessible documentation of the CVS "attic",
> > though. I had no idea such a thi
On Wed, Sep 07, 2011 at 09:25:15AM -0600, Chad Perrin wrote:
> On Wed, Sep 07, 2011 at 09:37:07PM +1000, Peter Jeremy wrote:
> > On 2011-Sep-07 01:35:54 -0600, Chad Perrin wrote:
> > >
> > > One thing I've seen come up that I definitely think would be a good
> > > idea, though, is more accessible
On 7 Sep 2011 16:53, "Mikhail T." wrote:
>
> On -10.01.-28163 14:59, Chris Rees wrote:
>>
>> I don't actually think they've been divisive -- it's been policy for
years.
>
>
> The policy -- up until fairly recently -- was to remove ports, that *fail
to build* for a while. This made sense -- if the
On 07.09.2011 12:04, Chris Rees wrote:
However... I find it deeply troubling that you consider buildability more
important than security fixes. Are you actually serious?
Yes, I'm, of course, serious. As you formulated above, the question is a no
brainer: software, that does not build is ul
On -10.01.-28163 14:59, Chris Rees wrote:
I don't actually think they've been divisive -- it's been policy for years.
The policy -- up until fairly recently -- was to remove ports, that *fail to
build* for a while. This made sense -- if the port remains unbuildable long
enough, then, certainl
On Wed, Sep 07, 2011 at 05:57:17PM +0200, Erik Trulsson wrote:
> On Wed, Sep 07, 2011 at 09:25:15AM -0600, Chad Perrin wrote:
> >
> > My understanding is that you are saying "attic" is just the standard
> > term for CVS history. Is that the case, or do I misunderstand your
> > point?
>
> Almost
Hi,
I need the port x11/xvattr.
But now it is expired :(
See his PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=149851
I need the port zu use vlc AND mplayer - thise players toggle this:
,
| "XV_AUTOPAINT_COLORKEY" (range 0 to 1)
| client settable attribute
| client gettable attribute
2011/9/7 Mikhail Tsatsenko :
> Hi,
> I want to maintain this ports:
> mail/milter-greylist-devel
> dns/py-adns
> dns/checkdns
>
Done. Thanks for volunteering.
I know it seems overkill, but for future reference a PR is less likely
to get lost in the mailing list.
Chris
___
On Fri, 2 Sep 2011 11:39:14 +0200
Michel Talon mentioned:
>
> Your answer is very interesting and allows me to go further in the
> reasoning. Indeed the UPDATING file is here to solve edge cases. My
> point is that there shouldn't be any edge cases, if there are some it is
> because something so
On Wed, Sep 7, 2011 at 8:57 PM, Heino Tiedemann
wrote:
> Hi,
>
> I need the port x11/xvattr.
>
> But now it is expired :(
>
>
> See his PR:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=149851
It seems from that PR that VLC should be fixed - you could always ask
the developers there if they are
On Wed, Sep 7, 2011 at 2:57 PM, Heino Tiedemann
wrote:
> Hi,
>
> I need the port x11/xvattr.
>
...
> What can I do?
Submit a working port in a PR and assume maintainership. Make sure to
fix the reason it was expired in the first place (which may be
becoming the upstream maintainer as well).
>
Hello, FreeBSD.
I've prepared port for subversion-1.7.0-rc2 for testing. It is
attached.
svn_hacks-1.7.patch is included, in case it will not be available
on ${MASTERSITE_LOCAL}
Notes:
(1) RC2 doesn't contain 'contrib' directory, so ASVN and
mdo_dontdothat is turend off
(2) FreeBSD hacks
On Wed, 07 Sep 2011 20:57:40 +0200
Heino Tiedemann mentioned:
> Hi,
>
> I need the port x11/xvattr.
>
> But now it is expired :(
>
Hi!
I just reverted that commit and brought it back.
Sorry for the inconveniences!
--
Stanislav Sedov
ST4096-RIPE
() ascii ribbon campaign - against html e-m
On 07.09.2011 23:35, Chris Rees wrote:
2011/9/7 Mikhail Tsatsenko:
Hi,
I want to maintain this ports:
mail/milter-greylist-devel
dns/py-adns
dns/checkdns
Done. Thanks for volunteering.
I know it seems overkill, but for future reference a PR is less likely
to get lost in the mailing list.
T
On Wed, 7 Sep 2011, Heino Tiedemann wrote:
Hi,
I need the port x11/xvattr.
But now it is expired :(
See his PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=149851
I need the port zu use vlc AND mplayer - thise players toggle this:
,
| "XV_AUTOPAINT_COLORKEY" (range 0 to 1)
| client s
Peter Jeremy wrote:
> On 2011-Sep-07 10:02:42 -0700, per...@pluto.rain.com wrote:
> >Reread the first paragraph. Provided the port is still in the
> >tree, when they try to build it the ports mechanism reports the
> >FORBIDDEN/BROKEN/whatever which describes the problem, and the
> >expiration da
On 9/7/2011 10:02 AM, per...@pluto.rain.com wrote:
> Doug Barton wrote:
>> On 09/07/2011 00:07, per...@pluto.rain.com wrote:
>>> Doug Barton wrote:
> Better to deprecate such non urgent ports, & wait a while
> after next release is rolled, to give release users a warning
>
On -10.01.-28163 14:59, Doug Barton wrote:
Non sequitur. The large number of ports that we support IS a feature. However,
it's also a pretty big maintenance burden. Especially when you consider the
number of those ports that are either actually or effectively unmaintained.
Support? What suppor
Hi Gecko team,
The update from Thunderbird 6.0 to 6.0.1 has stopped the Lightning
1.0b5pre plugin from working - it claims to be incompatible with the new
version of Thunderbird and can't be enabled. Lightning 1.0b5 seems to
work fine with Thunderbird 6.0.1 on my wife's windows PC, so I'm
gue
Hi,
Reference:
> From: Doug Barton
> Date: Wed, 07 Sep 2011 15:45:51 -0700
> Message-id: <4e67f41f.70...@freebsd.org>
Doug Barton wrote:
> On 9/7/2011 10:02 AM, per...@pluto.rain.com wrote:
> > Doug Barton wrote:
> >> On 09/07/2011 00:07, per...@pluto.rain.com wrote:
> >>> D
On 9/7/11 9:28 PM, Julian H. Stacey wrote:
>> And what we have been trying to explain to you is that this has never
>> been a supported mode of operation. We don't tie the ports tree to
>> specific releases,
>
> FreeBSD doese "tie the ports tree to specific releases". We have ports
> freezes befo
Hi all, please don't take this posting too serious. I was just curious ...
Just the other day, I bought a kill-a-watt. Among other things, I measured the
"cost of a source based package system", i.e. I was comparing the energy cost
of installing ports from source vs binary packages (setup, see b
On Thu, Sep 8, 2011 at 12:53 AM, Stefan Schaeckeler wrote:
> Hi all, please don't take this posting too serious. I was just curious ...
Thanks for the disclaimer.
> . Among other things, I measured the "cost of a source based package system",
> i.e. I was comparing the energy cost of installing
On 8 Sep 2011 02:29, "Julian H. Stacey" wrote:
>
> Hi,
> Reference:
> > From: Doug Barton
> > Date: Wed, 07 Sep 2011 15:45:51 -0700
> > Message-id: <4e67f41f.70...@freebsd.org>
>
> Doug Barton wrote:
> > On 9/7/2011 10:02 AM, per...@pluto.rain.com wrote:
> > > Doug Barton wrote
36 matches
Mail list logo
