On Fri, Sep 09, 2011 at 03:15:01PM +0200, Dash Shendy wrote:
I have noticed that you are responsible the FreeBSD port, and have
include the current version (0.5.10).
The actual maintainer of that port is fumif...@abacustech.jp .
po...@freebsd.org is a place-holder maintainer to indicate no one
On Mon, Sep 12, 2011 at 11:32:01PM +0200, Julian H. Stacey wrote:
Please consider resigning.
plonk.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On Sun, Sep 18, 2011 at 06:45:21AM +, Janne Snabb wrote:
I noticed that someone has removed sysutils/ltrace for some reason.
If we pull up the page on CVSWeb:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/ltrace/Attic/Makefile
We find:
2011-08-08 sysutils/ltrace: Has expired:
Bitrot on the original portsmon, due to be replaced by a new instance.
Feel free to ignore.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
portsmon is being migrated to a new host; the old one has been
decommissioned.
Right now I'm waiting for a DNS update to point to the new machine,
but in the meantime, you can reach portsmon as portsmonj.freebsd.org
(note the 'j' for 'jailed').
mcl
___
Why don't we take out Gnome and KDE then? I don't use it.
It's this kind of comment that is souring me on the FreeBSD community.
Can't we just disagree politely anymore?
mcl
___
freebsd-ports@freebsd.org mailing list
On Fri, Nov 11, 2011 at 12:40:12PM -0800, Stanislav Sedov wrote:
Because portmgr@ is using it? There're numerous cases when unmaintained,
buggy,
vulnerable and plainly dangerous stuff stays in tree because someone in
portmgr
gang likes it when other applications not used by them being
On Fri, Nov 11, 2011 at 01:04:41PM +0100, Benny Goemans wrote:
Is it possible to bring back the port so I can submit that change so that at
least some people can use it again?
I've just added a section to our Committer's Guide, since it seems
something that many people don't understand how to
A few people are getting creative again on ways to express this common
need. AFAIK the following is the best way to do it. What do people think?
mcl
Index: book.sgml
===
RCS file:
good point.
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
I would like to hold off on any more disruptive changes to the tree
until we can get this release out the door. If that means devel/clang
needs to stay at its current value (and only clang-devel updated), then
that's fine.
mcl
___
On Thu, Dec 08, 2011 at 11:40:07AM -0800, Daniel Duerr wrote:
I have a small request for whoever maintains the audio/squeezeboxserver
port...
That's bro...@freebsd.org:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/audio/squeezeboxserver/Makefile
The usual way to make requests is to go ahead
On Fri, Dec 16, 2011 at 06:09:08PM -0800, Xin LI wrote:
Actually you can add a dot (.) to these matches, e.g. freebsd[123]* -
freebsd[123].*, etc... Have you contacted the maintainer
(ger...@freebsd.org) by the way?
My guess? We should rip out the [123] and [23] strings entirely. If
anyone
I have recently been able to get the new build cluster on pointyhat-west
set up to run full builds of ports with clang on amd64-9. I have documented
the latest results on the wiki:
http://wiki.freebsd.org/PortsAndClang
If you are interested in working on ports being built via clang, this
is
In the last week I've been working on updating some of the ports
documentation on the wiki that had become stale. If you're looking
for something new to work on, these may be of interest.
http://wiki.freebsd.org/Trybroken
We have the ability to tell the build cluster go ahead and try to
build
According to http://www.freshports.org/ we have crossed the 23,000 port
barrier (currently 23,031). If I read this correctly the commit that
put us over the top was the addition of devel/py-Products.CMFActionIcons.
I appreciate all the hard work folks put into the Ports Collection. Now
I'll go
The problem with portsmon not updating its ports tree has now been
solved.
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 Sat, Dec 24, 2011 at 04:33:58PM +, Alexey Dokuchaev wrote:
On Sat, Dec 24, 2011 at 04:44:04PM +0800, Denise H. G. wrote:
290.10 has some issues on text redrawing as far I experience. I have
also been running 290.10 for quite a while. Some apps, especially emacs
and gnome-terminal
As of early December, I have been able to get FreeBSD's secondary ports
cluster (pointyhat-west.isc.FreeBSD.org) to the point where it is able
to more quickly build the entire ports tree with clang as the default
compiler. You can see the current state here:
On Mon, Jan 09, 2012 at 05:39:03PM -0500, Michael Scheidell wrote:
so, I am a ports committer, how about I hack bsd.port.*.mk files :-)
Commits to bsd.port.mk need to be approved by portmgr, preferably after
regression-testing on the cluster.
mcl
___
On Wed, Jan 18, 2012 at 09:09:10PM +, Chris Rees wrote:
I worry about the ethics of 'stealing' Fedora's bandwidth with other
people's ports; we should only be using their mirrors if it's explicitly
developed by Fedora.
Correct. dougb has pointed this out before and no one has taken the
On Thu, Jan 19, 2012 at 10:41:21AM -0800, per...@pluto.rain.com wrote:
Isn't this concern orthogonal to the original one about maintaining
a (set of) correct MASTER_SITE setting(s), for use by such ports as
can legitimately use Fedora/Debian/NetBSD/whatever sites?
Yes, IMHO.
mcl
On Tue, Jan 17, 2012 at 10:35:12AM -0500, Michael Scheidell wrote:
the solution would be for the submitter to work with the maintainer
on a solution, or am I supposed to fix this without reversing this?
In general each of us, as committers, is responsible for whatever side-
effects of the
You've probably reimplemented part of ports tinderbox (and, separately,
portsmon and FreshPorts) :)
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On Fri, Jan 20, 2012 at 10:44:23AM +, Matthew Seaman wrote:
HAS_SSE!= ${SYSCTL} -i -n hw.instruction_sse 2/dev/null
It's only a warning though, so INDEX generation should still work.
Yes, but the warning makes portmgrs sad. It leaves 'junk' in the
output of the file that's used to
On Fri, Jan 20, 2012 at 02:48:24PM -0500, Eitan Adler wrote:
You mean like this ?
http://www.freebsd.org/doc/en/books/porters-handbook/dads-sysctl.html
Yeah, but that's missing the 2 /dev/null corollary.
mcl
___
freebsd-ports@freebsd.org mailing list
On Thu, Jan 19, 2012 at 08:58:04AM +, Matthew Seaman wrote:
By my calculations there are 28 ports that set 'BROKEN' because of
architecture incompatibility on my amd64 system
IMHO these Makefiles are broken and should be fixed.
mcl
___
On Fri, Jan 20, 2012 at 10:20:05AM +, Matthew Seaman wrote:
Actually I take your point, that it should be possible to distinguish
between ports that permanently won't work on some architectures by
design, and ports that temporarily don't work because of mistakes or
broken dependencies or
On Fri, Jan 20, 2012 at 12:53:23PM +, Chris Rees wrote:
Occasionally someone runs an exp- for sparc64 (lol) etc.
You're conflating two different ideas. The arch is orthogonal to
TRYBROKEN.
They use TRYBROKEN to test packages marked BROKEN, but ONLY_FOR_ARCHS
sets IGNORE.
This part is
On Fri, Jan 20, 2012 at 05:16:08AM -0800, Doug Barton wrote:
On 01/20/2012 04:53, Chris Rees wrote:
Occasionally someone runs an exp- for sparc64 (lol) etc.
... which given the overwhelming lack of users for this platform is
almost certainly a waste of resources.
When we switch to
On Fri, Jan 20, 2012 at 10:20:05AM +, Matthew Seaman wrote:
Actually I take your point, that it should be possible to distinguish
between ports that permanently won't work on some architectures by
design, and ports that temporarily don't work because of mistakes or
broken dependencies or
On Tue, Jan 31, 2012 at 08:39:30AM +0100, n j wrote:
This question is probably not related to this announcement, but I
wonder if this change (pkg_* -- pkgng) will result in increased
number of available binary packages in the repositories
Absolute number, no. Speed of availability, possibly.
On Wed, Feb 01, 2012 at 11:16:38AM -0500, Michael Scheidell wrote:
The ChangeLog mentioned some sparc64 fixes, so it's worth giving it a
try again, but the port depends on boost-libs now which is marked as
broken on sparc64, so it cannot actually be tested.
So, how do you want me to handle
On Thu, Feb 02, 2012 at 08:38:38AM +, Chris Rees wrote:
We don't build sparc packages, so no Pavmail.
Gee, I sure *thought* I was building sparc64 packages:
$ showrunning | grep sparc64
sparc64-9 20120123043600 harlow.cse.buffalo.edu math/labplot
sparc64-9 20120123043600
On Tue, Feb 07, 2012 at 09:07:03PM -0500, Michael Scheidell wrote:
ok, but if I open a pr for subversion16, I am going to need to hack
GNATS and add a 'blocks' or 'depends on' so I get notified when its
committed :-)
for the blocked PR:
state=suspended
and give a reason why.
for the
On Sun, Feb 12, 2012 at 06:52:47PM +0400, Ruslan Mahmatkhanov wrote:
Just want to discuss some changes to this port that worth doing imho.
The main thesises are:
- We should remove DEPRECATED for now to keep consistency with lang/php4
- We should apply BACKPORTS patch unconditionally
Here
On Wed, Feb 15, 2012 at 05:12:09PM +, Chris Rees wrote:
The ports tree is never in a full freeze.
It is during the CVS tag operation.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On Sun, Feb 12, 2012 at 08:35:05PM +, Michael Scheidell wrote:
Public flogging seems to be more enjoyable than a private email to the
developer, the maintainer, and a committer.
I know we are all a little frustrated with some of the local commits, but
remember:
praise in public,
On Sun, Feb 12, 2012 at 03:22:38PM -0600, Stephen Montgomery-Smith wrote:
Also, if everyone starts using [redports], isn't the backlog going to
become huge?
We're working on getting more hardware.
Having something become too successful is a problem we should be happy
to have :)
mcl
Normally duplicate INDEX entries in the default config annoy one of us
portmgrs and we go try to figure them out.
On my own system I usually see this as a result of previously installed
dependencies e.g. cvsup_without_gui IIRC.
mcl
___
On Sat, Feb 18, 2012 at 03:59:37PM -0800, Doug Barton wrote:
Where I think reasonable minds can differ are (appropriate) responses of
the form, This was not done properly, here is how it can/should be done
(better). IMO those should *always* be public in order to help others
who are paying
On Tue, Feb 28, 2012 at 07:40:37AM -0500, Michael Scheidell wrote:
(FreeBSD never needed to set up a 'bounty' system for people wanting
to help pay for a port, have they?
If you check the archives, you'll see that there have been many discussions
over the years about the need/desire/whatever to
On Sat, Mar 03, 2012 at 03:36:02PM -0500, Super Bisquit wrote:
Have the packages for PowerPC32 been built yet?
http://pointyhat.freebsd.org/errorlogs/powerpc-9-latest/ is the run in
progress. With only two machines, progress is quite slow. The previous
results were
On Wed, Mar 07, 2012 at 06:19:51PM +0200, Andriy Gapon wrote:
BTW, our traditional taxonomy seems to be: USE_XXX is for stuff that ports
really require, WITH_XXX is for user preferences.
This isn't a taxonomy suggestion, it's a documented requirement:
On Wed, Mar 07, 2012 at 12:11:52PM +, b. f. wrote:
The custom gcc article that you are attempting to use was written at
a time when some of the related port Makefiles had some shortcomings
that no longer exist, and is not the recommended way to use lang/gcc*
for ports.
Would you be
On Sun, Mar 11, 2012 at 11:37:42PM -0700, Stanislav Sedov wrote:
The application itself was never supported by ports people and mostly is a
work of two outstanding individuals, Akinori MUSHA and Sergey Matveychuk.
I'm trying to keep it in a working shape as much as I could.
And all of this
portmgr's policy is to honor removal requests, no matter the circumstances.
If someone wants to fork the last free release and host it somewhere, I
would be less concerned in that case.
mcl
___
freebsd-ports@freebsd.org mailing list
On 9 April 2012 17:49, Julian H. Stacey j...@berklix.com wrote:
portmgr's policy is to honor removal requests, no matter the circumstances.
Irresponsible. Real 'Managers' shoulder responsibility. So ...
Real
On Tue, Apr 10, 2012 at 11:16:19AM +0200, Erwin Lansing wrote:
BROKEN is for less permanent or unknown breakage, like errors on pointyhat
where the one analyzing the logs doesn't have detailed knownledge of each
port and its breakage, and is used as a warning to users, so they don't try
to
On Tue, Apr 10, 2012 at 01:45:38PM +0200, Frederic Culot wrote:
To conciliate such a necessary action without hurting the feelings of those
maintainers who despite their work could not update the state of their port
in a
timely manner, maybe it would be good to be more verbose in the log of
On Tue, Apr 10, 2012 at 02:21:42PM +0200, Pietro Cerutti wrote:
The maintainer might be waiting for something to happen either upstream
or in our infrastructure, which could release the port from brokenness.
Putting a comment about that in the Makefile might go a long way to
minimizing
On Tue, Apr 10, 2012 at 09:32:47AM -0300, Marcelo Araujo wrote:
There is nothing more frustrating than try to install a port and it
doesn't fetch or doesn't build.
That's been my main point of worry all along (more personally than as
portmgr), and why I think the deprecation campaigns do more
On Mon, Apr 09, 2012 at 08:50:08PM -0700, Cy Schubert wrote:
On a tangential issue, php52 should probably be kept around, at least
for now. [...] I think these ports should be deprecated, giving
users ample time to migrate to newer ports
AFAIK all the php52 ports are indeed already marked
a) the best place is freebsd-ports@
b) we do periodic builds of ports with clang as default but in general
clang is not ready to be the default compiler yet. Please see
http://wiki.freebsd.org/PortsAndClang .
mcl
___
freebsd-ports@freebsd.org
The best thing to do with patches is submit them as PRs, either via
send-pr(1) or via the web interface. That way, the port maintainer
(if any) gets automaticially notified. (Well, automatic if the Synopsis
contains the category/portname explicitly)
mcl
On Mon, May 14, 2012 at 09:51:17AM +, Max Brazhnikov wrote:
But I'm going to commit the update soon anyway.
Please go ahead at this point. IWBNI you marked the other ports
BROKEN in the same commit.
If you don't have the cycles, I can go ahead and do it tomorrow. It's
past time just to
On Fri, May 11, 2012 at 12:10:25AM +0300, Andriy Gapon wrote:
P.S.
Perhaps this information should also be somewhere in the Porter's Handbook.
It is scattered around in it:
WITH/WITHOUT:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-options.html#AEN2542
USE:
Thanks for doing this work. A quick review looks to me to be TRT.
I would suggest some minor fixes but only for style: for me, it makes
it a bit clearer what's going on if the pre.mk include isn't among
the various WITH_* definitions, e.g. net/skystar2. Or maybe just
having a blank line before
Unfortunately certain things need to be defined before bsd.port.pre.mk
is included. So, pointy hat to me for giving bad advice.
These show up immediately as bad distinfo problems:
It would be nice to get the new version installed prior to the release
of FreeBSD-7.3, IMHO.
a) it's not sufficiently tested.
b) an upgrade to xorg is in the wings. That's certainly going to affect
even more ports.
Waiting for both of those to be finished would mean delaying 7.3 even
On Sun, Feb 28, 2010 at 08:02:40AM -0600, Programmer In Training wrote:
What about a list (by PORTS) of ports with problems with maintainers?
You may also find http://portsmon.freebsd.org helpful.
mcl
___
freebsd-ports@freebsd.org mailing list
On Sun, Mar 07, 2010 at 07:40:32AM -0600, ajtiM wrote:
Is the port gimp-app without maintainer, please.
$ pwd
/home/pcvs/ports/graphics/gimp-gap
$ make maintainer
a...@freebsd.org
ahze@ hasn't been as active recently, however.
The best way to proceed is to submit a PR with the suggested
Here's one more thank-you to Erwin for doing a thankless job for
the last few years.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
It probably bears repeating that the tree will be unstable for the next
few days while a number of large commits hit the tree. These were held
off during the release process to make life easier in case portmgr had
to do tag-slips.
Image processing libraries, xorg, kde, and gnome are scheduled to
On Thu, Mar 25, 2010 at 03:44:20PM +0100, Gary Jennejohn wrote:
It's only been a week since it was assigned to the maintainer (girgen@)
to look at.
It's too soon for a maintainer timeout, although I suppose if this is
considered to be an enormous security risk it could be committed without
On Sun, Apr 11, 2010 at 01:07:42AM +0400, Sergei Vyshenski wrote:
Do you think if it is possible to return openssl-0.9.8x to the ports,
just to make people with FreeBSD-6 happy.
fwiw, 6.4 EOL is on 11/30/2010, so you're going to be looking at
upgrading some time this year anyways.
This
not to be a troll but ...
... for those that want the ease-of-use of PBIs, why not just use PC-BSD
in the first place? They seem to have their own QA process in place in
terms of keeping the various large applications at a sane level.
Kernel development could (just like it is on the Macs) be
On Sun, May 02, 2010 at 02:59:40PM -0500, Tim A wrote:
4) I don't understand the suprematism attitude of the maintainers in
charge, who don't give a penny on the programs they are suppose to
maintain. They are only interested in the statistics generated by their
unprofessional ports, but not
On Fri, May 07, 2010 at 03:27:50AM +0300, Mihai Militaru wrote:
Most questions I investigated since I'm on this system have been
answered already here and there on the internet by some maintainers,
things like: go read the Bible, it is a problem with your hardware,
you've done something wrong.
[*] Did anyone have any good suggestions for a replacement for Gnats
yet? I know there is a desire to replace it with something better.
The project to come up with a prototype for its replacement has stalled.
I hope to restart it after completing some urgent upcoming package build
work.
mcl
fixed.
___
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 Sat, Jun 12, 2010 at 05:32:10PM +, Terry Poulin wrote:
Just noticed that they moved to github
http://github.com/zdia/gorilla and the current version is 1.5.3,
rather than the 1.4.4 version in the ports tree. I don't use the
program, but thought it best to make a note of it here;
On Fri, Jun 18, 2010 at 01:37:43PM +0200, Troels Kofoed Jacobsen wrote:
I submitted a PR for an update in January but nothing ever happened,
although a committer did take it.
http://www.freebsd.org/cgi/query-pr.cgi?pr=143209
It was marked closed via feedback timeout. However, there is no
On Mon, Jun 21, 2010 at 04:07:35PM +0200, Kurt Jaeger wrote:
There is a newer of dbvis version available (7.1).
Should I update my patch or how is this supposed to be handled ?
That's the preferred way, yes.
And for your other question, there are currently 1211 PRs in the queue,
of which 98
On Mon, Jun 28, 2010 at 09:19:05PM +0200, Andrea Venturoli wrote:
Any news on updating this port?
They're unmaintained, so it's probably up to you to do it :-)
mcl
___
freebsd-ports@freebsd.org mailing list
done.
___
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
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,
On Sat, Jul 10, 2010 at 06:46:36AM -0700, Jesse Smith wrote:
I would be happy to take over maintaining those to ease the load.
OK, we always welcome help :-) If you need help submitting PRs, let
us know.
Veteran maintainers might not like the idea of new blood having commit
access, which is
The intention of bsd.perl.mk was to eventually allow a bunch of code
to be pulled out of bsd.port.mk, and to have bsd.perl.mk only included
conditionally, on the theory that it will speed up INDEX building
somewhat. (I have not tested for speedup).
The problem is that there are N ports that
On Wed, Jul 21, 2010 at 10:21:11PM +0200, Kurt Jaeger wrote:
And is this ok to have two ports with the same name.
No, it's bad and should be avoided. I'm pretty sure some
portupgrade tool will break.
No, they actually handle it ok. It _is_ confusing to the users, however
(and, if you go
On Thu, Jul 22, 2010 at 02:18:36AM +0400, Anonymous wrote:
Ah, it uses NO_LATEST_LINK. So the answer is `none'. Sorry.
Yeah, but I had to look it up myself.
Do you know of any other examples that are missing either CONFLICTS or
NO_LATEST_LINK?
mcl
These are the results that I get on my home machine:
$ make index
Generating INDEX-7 - please wait..make_index: thunderbird-3.0.5_1: no entry for
:/home/pcvs/ports/lang
make_index: thunderbird-3.0.5_1: no entry for :/home/pcvs/ports/lang
make_index: thunderbird-3.0.5_1: no entry for
On Wed, Jul 28, 2010 at 11:47:11PM -0700, Doug Barton wrote:
When I asked you what was necessary to test this, you said all that was
necessary was to define _PERL_REFACTORING_COMPLETE.
And my memory slipped.
The explanation, however, was correct: the problem is that if you
unconditionally
On Tue, Aug 10, 2010 at 10:56:44AM +, Helmut Schneider wrote:
in the past I created a few PRs with patches for important security
updates for typo3. Unfortunately they all timed out.
What is the time GNATS is waiting for feedback of the maintainer?
It's 14 days for a normal update or
On Tue, Aug 10, 2010 at 05:14:04PM +, Helmut Schneider wrote:
b) I will email the maintainer and ask if he is willing to transfer
maintainership to you.
Me?! Huh! What does that mean? :) I mean, what if I run into problems?
Ask for help on ports@, the forums, the IRC channels, ... :-)
On Sun, Aug 15, 2010 at 04:11:09PM +, John Sherman wrote:
If Wvdial is returned to FreeBSD 8.0 will it be noted in the Forum
From a quick check, I can't see where it was ever in FreeBSD in the first
place?
In any case, the best way to find out about new ports is to subscribe to
FreshPorts (
On Tue, Aug 17, 2010 at 07:04:13PM -0400, Alex Goncharov wrote:
Please remove -- I am releasing my maintainership.
done
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On Sun, Aug 22, 2010 at 02:22:11AM -0500, Ade Lovett wrote:
Given that the port has apparently been broken since early June, and
that we have someone willing to take over , I'd say that this is a cast-
iron case for a maintainer-timeout commit of the patch along with
reassignment of the port.
After yet more inactivity, I am reassigning asterisk16 to f...@kasimir.com
with portmgr hat. Thank you both for your patience.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send
Please see ports/150493 for someone who seems to be looking at it.
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 Sat, Oct 16, 2010 at 02:04:20PM -0700, Charlie Kester wrote:
BTW, does anyone know what's going on with miwi?
Job change involving relocation halfway around the planet.
mcl
___
freebsd-ports@freebsd.org mailing list
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 from
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 :-)
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 Wed, May 06, 2009 at 10:21:39AM -0700, Charlie Kester wrote:
Does the portsmon statement simply mean that it hasn't been packaged
yet, or is there some other issue that needs to be addressed?
The latter (a bug in portsmon :-) )
There is some leakage of things that come and go in MOVED.
On Sun, May 17, 2009 at 01:25:39PM +0600, Dmitry N. Kolesnikov wrote:
I need the databases/clip port updated to current (v. 1.2.0), can you please
do it?
The po...@freebsd.org maintainer is the place-holder maintainer;
that means no one is maintaining it. The best thing for you to do
is to
It was just a repocopy. I'm working on it, just enotime now.
Then mark the port BROKEN, or some such. User confusion is a bad thing. :)
s/BROKEN/IGNORE/
mcl
___
freebsd-ports@freebsd.org mailing list
On Sat, May 30, 2009 at 04:48:15PM +0200, Mel Flynn wrote:
but what is the general policy on such ports?
They can come back if they're not vulnerable and someone volunteers
to maintain them. (deleted ports may have had ports@ as the maintainer,
but we don't allow that for port (re)additions.)
On Sat, May 30, 2009 at 11:01:38AM -0400, Diane Bruce wrote:
By the time FreeBSD-9 is released clang support will be solid and all
ports will compile with clang as well as gcc.
ooh, can I have unicorns, too? :-)
Seriously, I'd like to see the potential to throw the switch, with
the caveat that
On Thu, Jul 09, 2009 at 10:25:50PM +0200, Ulrich Spörlein wrote:
I am always confused about what portsmon is doing vs. pointyhat.
portsmon tracks all the errorlog data from pointyhat, with the caveat
that only the last 2 runs (somewhat erroneously termed full and
latest) of each buildenv are
1 - 100 of 545 matches
Mail list logo
