On Mon, 05 Sep 2011 12:05:35 +0200
Julian H. Stacey j...@berklix.com mentioned:
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
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as broken in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as forbidden in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port,
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as forbidden in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port,
On Sep 7, 2011, at 8:30 AM, Stanislav Sedov wrote:
On Mon, 05 Sep 2011 12:05:35 +0200
Julian H. Stacey j...@berklix.com mentioned:
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
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 made?
On Thu, 01 Sep 2011 15:33:02 +0200
Julian H. Stacey j...@berklix.com 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
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
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
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.
The
Doug Barton do...@freebsd.org wrote:
On 09/07/2011 00:07, per...@pluto.rain.com wrote:
Doug Barton do...@freebsd.org 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:
On 2011-Sep-06 23:30:04 -0700, Stanislav Sedov s...@freebsd.org 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
On Wed, Sep 07, 2011 at 09:37:07PM +1000, Peter Jeremy wrote:
On 2011-Sep-06 23:30:04 -0700, Stanislav Sedov s...@freebsd.org 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
___
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 s...@freebsd.org wrote:
What about requiring that the ports deprecated should be either broken
or have known published vulnerabilties for a long period of
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 example,
On Wed, Sep 07, 2011 at 09:37:07PM +1000, Peter Jeremy wrote:
On 2011-Sep-07 01:35:54 -0600, Chad Perrin c...@apotheon.net 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
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 c...@apotheon.net wrote:
One thing I've seen come up that I definitely think would be a good
idea, though, is more
On 7 Sep 2011 16:53, Mikhail T. mi+t...@aldan.algebra.com 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
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
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,
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 correct.
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 m.tsatse...@gmail.com:
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 Wed, Sep 7, 2011 at 8:57 PM, Heino Tiedemann
rotkaps_spam_t...@gmx.de 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
On Wed, Sep 7, 2011 at 2:57 PM, Heino Tiedemann
rotkaps_spam_t...@gmx.de 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
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 rotkaps_spam_t...@gmx.de 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
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
Peter Jeremy peterjer...@acm.org 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
On 9/7/2011 10:02 AM, per...@pluto.rain.com wrote:
Doug Barton do...@freebsd.org wrote:
On 09/07/2011 00:07, per...@pluto.rain.com wrote:
Doug Barton do...@freebsd.org 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
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
Hi,
Reference:
From: Doug Barton do...@freebsd.org
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 do...@freebsd.org wrote:
On 09/07/2011 00:07,
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 before each
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
On Thu, Sep 8, 2011 at 12:53 AM, Stefan Schaeckeler schae...@gmx.net 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
39 matches
Mail list logo
