On Thu, Jun 30, 2011 at 08:19:05AM +, b. f. wrote:
> Is there a new link for the new results? Or did you use the link above?
same link.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubsc
On Mon, Jun 20, 2011 at 06:21:26PM -0500, Mark Linimon wrote:
> A permanent URL to this run is:
>
>
> http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110616185105/
>
> That will stick around even if we use amd64-9-exp for something else.
I have up
On Sun, Jun 26, 2011 at 03:54:28AM +, b. f. wrote:
> Please don't hardcode the compilers
+1.
One of the Next Big Tasks is to be able to use a compiler other than
the system default, for ports. Please don't make this work more painful
than it will already be :-)
mcl
_
On Mon, Jun 20, 2011 at 05:37:53PM +0200, Roman Divacky wrote:
> Flz@ just ran an exp-build with CC=clang and CXX=clang++. The results can be
> seen here:
>
> http://pointyhat.freebsd.org/errorlogs/amd64-9-exp-latest/
A permanent URL to this run is:
http://pointyhat.freebsd.org/errorlogs/
On Wed, Jun 01, 2011 at 09:10:06AM +0200, Carsten Jensen wrote:
> While doing the revision, would it be too much trouble to add a section
> for web apps ?
Sorry, I don't know enough about them to add that section ...
mcl
___
freebsd-ports@freebsd.org ma
When going through the "Using" sections, I always get irritated by
having to figure out where the makevars that they are talking about
are defined. This patch adds some crossrefs to the CVSWeb pages
for them. (In a few cases, the filenames were mentioned, but they
weren't CVSWeb references.)
Doe
On Tue, May 24, 2011 at 02:37:42AM -0500, Brooks Davis wrote:
> Does it work for you on any other platforms?
For the record, the canonical answer can be found at:
http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=ganglia-monitor-core&wildcard=
However, it has been a while si
On Mon, May 02, 2011 at 10:01:48PM +0100, Anton Shterenlikht wrote:
> I'd like to take maintainership of
>
> astro/xearth
> textproc/urlview
done.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On Thu, Apr 28, 2011 at 03:55:35PM -0400, Jerry wrote:
> Would you please rewrite it in basic English using proper sentence
> structure.
Please note: although the primary language of the project is English,
probably less than half of FreeBSD committers are native Enligsh speakers.
See ports/xearth
On Wed, Apr 27, 2011 at 10:23:23AM +0200, Kurt Jaeger wrote:
> Maybe, if maintainer can "somehow easily" become ports committer,
> this hurdle might be lower ?
This has been discussed before. The barrier to entry is currently set
at the "seems to be willing to work on FreeBSD over a period of man
Let's play "let's pretend".
Let's pretend I'n on the ports management team (true).
Let's pretend I have enough influence to talk the rest of the ports
management team into agreeing with me (very debatable, based on past
performance.)
Then, let's pretend that portmgr promotes a new policy, "all P
I need to migrate portsmon to another server so that we can start up
these periodic emails again.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsub
On Tue, Apr 12, 2011 at 01:03:58AM -0500, Brandon Gooch wrote:
> What port is it? Sorry, I can't determine from the previous message...
ports/lang/io, Small prototype-based programming language
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists
done, thanks.
mcl
___
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"
On Thu, Mar 31, 2011 at 12:52:16PM +0200, Franco Marchesini wrote:
> can you upgrade the libcii port to version 2?
"po...@freebsd.org" is a placeholder that assigns maintainership to the
general mailing list.
For best results, you should submit a PR with a patch to update the port.
Otherwise, it
On Sat, Mar 19, 2011 at 04:34:17PM +0800, wen heping wrote:
> devel category is the largest one, how about divide it into :
>
> devel
> devel-perl
> devel-python
My own view is that naming the categories by language (e.g. "java")
is not a good idea. I'd rather divide things up by what they do,
r
On Thu, Mar 17, 2011 at 11:36:38AM +0100, Pietro Cerutti wrote:
> > all these efforts to rescue the ports are all good, but: do we actually
> > _need_ the ports? Just having one more port isn't a value in itself.
>
> It's a potential value. Having one port less is a potential loss.
Potential va
For those that want to see the state of all this, you can check out
the following URL:
http://portsmon.freebsd.org/portsconcordancefordeprecated.py
In particular, the "interesting" entries for you may be the unmaintained
ports (e.g. maintainer = "po...@freebsd.org".) In some of the other
case
On Wed, Mar 16, 2011 at 06:15:11AM +, b. f. wrote:
> But it's not clear to me why, for example, some usable fonts were
> deprecated -- fonts often don't have homepages.
The deprecations are (currently) advisory-only.
If people are using these ports, and want to keep them, then they need
to st
On Wed, Mar 16, 2011 at 11:45:25AM +0100, Matthias Andree wrote:
> However, we should be sure to find maintainers before ports are
> undeprecated, else we run into a cycle of deprecation, reviving the
> port, deprecating it again, and so on.
That's the purpose of a long deprecation period + the pe
On Sat, Mar 12, 2011 at 02:00:33PM -0800, Doug Barton wrote:
> 1. Fix all ports to compile with both gcc 4.2 (for RELENG_[78]) and clang.
I do not believe we have enough time before 9.0R to accomplish this;
especially as I understand that there is pressure within the src committer
community to sim
On Mon, Mar 14, 2011 at 08:27:27AM +1100, Peter Jeremy wrote:
> On several occasion, Doug has asked for the results of the gmake 3.82
> exp run. This request (which seems perfectly reasonable to me) has
> been consistently ignored.
Provided in email in this thread two days ago; annotated, at a hi
On Sun, Mar 13, 2011 at 11:39:26AM +0100, Ulrich Spörlein wrote:
> Augmented with a crude estimate of ports affected by these breakages
> (via grepping INDEX, basically).
With a little detective work, you can get that from pointyhat. e.g.
the "Aff." ("Affects") column in
http://pointyhat-west.
On Sat, Mar 12, 2011 at 06:00:40PM -0600, Ade Lovett wrote:
> Throwing out a PR with "exp-run probably desirable" is not particularly
> useful, and shows a certain naivety when it comes to such wide-ranging
> changes.
This seems a little harsh to me. OTOH, I think it's become much clearer
to me d
replying to myself.
On Sat, Mar 12, 2011 at 05:51:44PM -0600, Mark Linimon wrote:
> Up until recently, I haven't been doing any -exps myself, other than to
> test the setup on pointyhat-west (on which I continue to find bugs in the
> newer, generalized, codebase).
Slightly untrue
Actually, not "at random", it was "the latest one that came across
the threshhold." Sorry.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...
On Sat, Mar 12, 2011 at 05:14:14PM -0800, Rob Farmer wrote:
> Also, you suddenly getting involved probably didn't help, because it
> just gave the appearance that you guys were trying to double-team
> Doug.
As I've stated elsewhere in this thread, I had an empty slot for an -exp
and just grabbed o
A greatly expanded version of my original message is now at:
http://wiki.freebsd.org/GmakeTODO
Note: the second run is currently paused while we are working on hardware.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/
I'm sorry that I did not have a chance to run the gmake -exp sooner.
Up until recently, I haven't been doing any -exps myself, other than to
test the setup on pointyhat-west (on which I continue to find bugs in the
newer, generalized, codebase). I put the gmake -exp on there primarily as
a way to
On Sat, Mar 12, 2011 at 02:35:23PM -0800, Charlie Kester wrote:
> Is the underlying sourcecode available somewhere?
The code is really gross :-(
Right now I don't have the cycles to 'productize' it, sorry. Feel
free to abuse that server in the meantime.
mcl
_
On Sat, Mar 12, 2011 at 02:12:34PM -0800, Charlie Kester wrote:
> I'm not aware of any tool that will display a similar dependency tree
> for a port *before* it is installed.
http://portsmon.freebsd.org/portdependencytree.py
Note: it's running a live set of queries on the tree, so it's slow.
mcl
On Thu, Mar 10, 2011 at 10:28:40AM +0100, Hans Ottevanger wrote:
> If anybody is interested I could consolidate my results and post a few
> patches.
I would like to see them.
This is the kind of really-dull-but-necessary work that we need to have
people work on to fight the creeping dependencies
On Sat, Mar 12, 2011 at 01:34:58PM -0800, Doug Barton wrote:
> >Would you please offer examples of decisions that you feel that way about?
>
> Clearly it would be inappropriate for me to comment publicly on
> things that were discussed in private, so no, I'm not going to do
> that.
You just discu
On Fri, Mar 11, 2011 at 09:14:50PM -0800, Doug Barton wrote:
> There are way too many things happening "in private" around here and
> the only way to solve that problem is to open the doors.
Would you please offer examples of decisions that you feel that way about?
mcl
___
On Sat, Mar 12, 2011 at 06:38:12PM +, Christian Weisgerber wrote:
> FWIW, I expect a number of these will be trivial fixes where the
> commands for a Makefile target are indented with spaces instead of
> tabs.
Yeah, it kind of looked that way on first glance.
mcl
_
On Fri, Mar 11, 2011 at 10:59:02AM +, Klaus T. Aehlig wrote:
> Can anyone shed more light on why this port is marked BROKEN?
In general you have to do a little bit of detective work.
First stop: portsmon, to see where it is currently not building:
http://portsmon.freebsd.org/portoverview.p
I answered this question last night on IRC, aDe answered it in email:
> What is the urgency in upgrading gmake that prevents "fix the broken
> ports first" as an option to at least explore?
Now that gmake is out, if the past is any indication, some project
will quickly upgrade to it. We can wait
#x27;gmake' error classification has been added to the results;
OTOH, many regressions will be classified as 'makefile'. It depends on how,
exactly, the build failure occurred.
mcl
- Forwarded message from Mark Linimon -
Date: Sat, 5 Mar 2011 20:49:28 -0600
From: Mark Linimon
On Mar 10, 2011, at 14:21 , Doug Barton wrote:
> I admire your optimism, however experience tells us that once these
> types of accomodations get into the tree, they stay there for a long
> time.
Here's what I have on my system:
devel/autoconf
devel/autoconf213
devel/automake
devel/automa
On Thu, Mar 10, 2011 at 02:05:50PM -0600, Ade Lovett wrote:
> Preliminary runs show ~50 ports that break with 3.82, some of them
> unfortunately being dependencies for a reasonable number of others.
For values of "reasonable" in the ~1100 range.
mcl
___
Synopsis: add caution messages to some adobe products
Responsible-Changed-From-To: freebsd-ports->hrs
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Feb 15 16:26:26 UTC 2011
Responsible-Changed-Why:
Over to maintainer of print/acroread8 to add a vuxml entry.
h
Synopsis: [UPDATE] devel/bzr-git
State-Changed-From-To: feedback->open
State-Changed-By: linimon
State-Changed-When: Mon Feb 14 20:51:14 UTC 2011
State-Changed-Why:
Fix up damage from bogus submittal address.
Class-Changed-From-To: change-request->maintainer-update
Class-Changed-By: l
On Sun, Feb 13, 2011 at 10:12:05AM +0300, Odhiambo Washington wrote:
> What is it that this Debian GNU/kFreeBSD ships in those 7 DVDs?
Please ask that on one of their mailing lists; it's out of scope for
the two mailing lists you posted to.
mcl
___
free
On Fri, Feb 04, 2011 at 07:07:40PM +, Helmut Schneider wrote:
> The repocopy is complete but the port is not available yet. A few
> poeple already emailed me so I just would like to know why it is not
> available yet. Due to the upcoming release of 8.2?
No, adding new ports is allowed during m
$ cd audio/teamspeak_server
$ make maintainer
po...@freebsd.org
The ports are unmaintained as of this commit:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/audio/teamspeak_server/Makefile?rev=1.14
If you are interested in working on them, see:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/port
Synopsis: [bsd.port.mk] Pass CPPFLAGS to MAKE_ENV and CONFIGURE_ENV
Responsible-Changed-From-To: ports->freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Fri Jan 28 21:20:14 UTC 2011
Responsible-Changed-Why:
canonicalize assignment.
http://www.freebsd.org/cgi/qu
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, inclu
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, inclu
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 th
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 th
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 probl
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 probl
On Mon, Jan 17, 2011 at 08:12:40PM +0100, Julian H. Stacey wrote:
> rene@ has ignored request to roll back. If rene@ resigns,
> MAINTAINER would revert to po...@freebsd.org so others could fix
> FreeBSD's current ports/www/chromium
Because of the legal questions surrounding chromium, portmgr will
On Mon, Jan 17, 2011 at 11:38:22AM -, fgheor...@dracmail.net wrote:
>I am the author of dracMail Webamil ( mail/dracmail ) and I would
>like to take ownership of the port. I couldn't find in the Handbook
>how ports are being assigned.
It's currently unmaintained, so all you would
Synopsis: bsd.gnat.mk - improved Ada support for the ports system
State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Sun Jan 16 15:54:49 UTC 2011
State-Changed-Why:
Closed at request of John Marino: apparently, original submitter has
abandoned this idea.
h
On Fri, Jan 07, 2011 at 10:29:42PM +0100, olli hauer wrote:
> Ups, I thought freefall runs the gnats4 port.
Nope. Never got updated. The problem is that we have people that have
local copies of the repo, and we would need to get them to move all at
the same time.
(portsmon has a shim to do this
On Fri, Jan 07, 2011 at 04:18:49PM +0100, Olli Hauer wrote:
> I wonder about the old gants port.
> Do we use parts of this port somewhere (OS/freefall...)?
freefall, yep. It's our main GNATS installation.
mcl
___
freebsd-ports@freebsd.org mailing list
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 th
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, inclu
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 th
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 probl
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 probl
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, inclu
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 th
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 th
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 probl
On Mon, Dec 13, 2010 at 05:06:28PM +0100, Alexander Leidinger wrote:
> What's wrong with having it build on the pointyhat cluster for those
> which build a package and to make it an option for those which build
> the port?
Surely we want the pointyhat package to be the same as the default
package
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, inclu
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 probl
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 th
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 th
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 probl
Synopsis: Request for new port: projectM
State-Changed-From-To: open->suspended
State-Changed-By: linimon
State-Changed-When: Mon Dec 6 17:45:08 UTC 2010
State-Changed-Why:
mark suspended awaiting patches.
Responsible-Changed-From-To: freebsd-ports->freebsd-ports-bugs
Responsible-Chan
ok, but I'm trying to fix something before I have time to do an -exp
run ...
mcl
___
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"
Patch incorporating these suggestions, along with some other edge
cases I found, uploaded:
http://people.freebsd.org/~linimon/patches/diff.out.srcbase
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
On Tue, Nov 30, 2010 at 03:33:27AM -0600, Ade Lovett wrote:
> Seems like there's an awful lot of duplication of:
>
> SRC_BASE?= /usr/src
>
> in those port Makefiles.
>
> What's wrong with adding the above, with a bit of documentation, to
> bsd.port.mk ?
Nothing at all, but this is a fix I'd lik
pointyhat, which has multiple src trees) this should
fix edge conditions with 'make describe'.
I would appreciate feedback on the following patch:
http://people.freebsd.org/~linimon/patches/diff.out.srcbase
Thanks.
mcl
___
freebsd-ports@f
On Tue, Nov 30, 2010 at 12:40:33AM +0100, Matthias Andree wrote:
> Yes, would be nice. I doubt it will happen soon.
It's actually being looked at.
As part of the extensive rework of the pointyhat scripts I did this
summer, I attempted to factor out all the magic constants, including
the definiti
On Tue, Nov 23, 2010 at 12:00:08PM -0800, Jason Helfman wrote:
> Here is a patch to take care of removing of "updating".
I've committed a version of your two patches, plus some of my own changes,
to try to remove the ambiguities in the text about "new ports" vs. "updating
an existing port". Sever
On Sun, Nov 21, 2010 at 09:26:49PM -0800, Charlie Kester wrote:
> E.g., why not send an email requesting resubmission in the proper
> format?
A lot of committers do try to do just that. There is no automated
process, however.
> Many of the of oldest unassigned but still-open PR's show no evidenc
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, inclu
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 th
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 th
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 probl
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 probl
Synopsis: wrong message when trying to checkout using old repository path
Responsible-Changed-From-To: freebsd-ports->freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Sat Nov 20 13:41:58 UTC 2010
Responsible-Changed-Why:
Canonicalize assignment.
h
On Sat, Nov 13, 2010 at 09:35:29PM +0200, Andriy Gapon wrote:
> Not sure if we've had any problems like that when upgrading between minor
> versions of a single module, even such as xorg server.
I don't remember, either.
> That is, I am sure there will be a lot of testers if the port update is
>
On Mon, Nov 08, 2010 at 05:11:41PM +0200, Andriy Gapon wrote:
> Oh, forgot a need to simply bump port revisions of all xorg driver ports.
> That's perhaps a little bit laborious, but doesn't require any special skills.
> Or did you have something else in mind?
There's this whole "testing" thing :-
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, inclu
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, inclu
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 th
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 th
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 probl
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 probl
Synopsis: request to enable emulators/wine on amd64
Responsible-Changed-From-To: ports->freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Oct 28 19:13:54 UTC 2010
Responsible-Changed-Why:
Canonicalize assignment.
http://www.freebsd.org/cgi/query-pr.cgi?pr=151
> On Mon, 2010-10-18 at 16:34:11 +0200, Carsten Jensen wrote:
> I know that it can take some time, but seeing on the list that some
> new ports are still waiting to be added (goes back to 2007;
> ports/117299), I'm just trying for mine not to be "forgotten".
117299 is suspended awating a response
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, inclu
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, inclu
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 th
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 th
601 - 700 of 1353 matches
Mail list logo
