Thanks for your feedback but unfortunately the result is the same even if I
provide the prototype for printf in the source file.
Frederic
Frederic Culot frede...@culot.org wrote:
Following the links on the ports tasks wiki page I found
'obskurator' to be a wanted port ... so I gave it a
I wanted to switch to the new k3b-kde4. I ran through a couple
of problems, most of them ports not accepting spaces in CC, but
there's a soprano issue I don't get through to:
Linking CXX executable sopranod
cd
I would prefer this approach:
amd.conf has the option preferred_amq_port to specify the listening
port. Don't know about ypbind.
It is not just rsyncd that can get disturbed. Grabbing arbitrary port
without consulting /etc/services and the startup scripts is a bad idea
for any service.
(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
I'll see if it's within my capabilities.
Chris
Sorry for top-posting, Android won't let me quote, but K-9 can't yet do
threading.
On 16 Aug 2010 02:22, Mark Linimon lini...@lonesome.com wrote:
On Sun, Aug 15, 2010 at 04:11:09PM +, John Sherman wrote:
If Wvdial is returned to
On 8/13/2010 11:51 AM, Freddie Cash wrote:
On Fri, Aug 13, 2010 at 8:47 AM, Mike Jakubik
mike.jaku...@intertainservices.com wrote:
Thanks for the info. Do you think this may be a usefull feature for other
users coming from portupgrade though? If there is an option to always
rebuild, one
On 12/08/2010 20:11, Anonymous wrote:
Dominic Fandrey kamik...@bsdforen.de writes:
On 07/08/2010 02:46, Adam Vande More wrote:
On Fri, Aug 6, 2010 at 5:11 PM, Doug Barton do...@freebsd.org wrote:
On 08/06/2010 15:03, Adam Vande More wrote:
for pkg in /var/db/pkg/* ; do
pkg_create
Hello.
Can you tell me when planed adding asterisk 1.6.2 in ports Freebsd?.
I try write to maintainer: sobo...@freebsd.org, but received error:
550 sender or recipient address is wrong
Thank you!
___
freebsd-ports@freebsd.org mailing list
On 8/15/2010 10:49 PM, David Wolfskill wrote:
The most straightforward way to make this a non-issue (it seems to me)
would be to start rsyncd(8) before other services that grab arbitrary
ports; however, the start-up script for rsyncd s[ecifies:
# PROVIDE: rsyncd
# REQUIRE: LOGIN
# BEFORE:
On Mon, Aug 16, 2010 at 6:37 PM, Dominic Fandrey kamik...@bsdforen.de wrote:
I wasn't aware that pkg_create can create several packages at once,
thanks for that!
I'm not quite sure how pkg_create creates a package, but it if does
use make package-noinstall be aware that it have a bug that
On 8/13/2010 11:25 AM, Paul Schmehl wrote:
I want to DEPRECATE security/barnyard. It's a master port. The slave
is security/barnyard-sguil. Is it sufficient to DEPRECATE and EXPIRE
the master? Or do I need to do that to the slave as well?
The simplest and best way to answer this question is
On 16/08/2010 22:09, Christer Solskogen wrote:
On Mon, Aug 16, 2010 at 6:37 PM, Dominic Fandrey kamik...@bsdforen.de wrote:
I wasn't aware that pkg_create can create several packages at once,
thanks for that!
I'm not quite sure how pkg_create creates a package, but it if does
use make
2010/8/6 Sandra Kachelmann s.kachelm...@googlemail.com:
I've been using ports-mgmt/portupgrade pretty much ever since it
started to exist. Unfortunately portupgrade seems to be pretty much
abandonware so I've been told to move on to portmaster. Despite the
very long manpage I can't seem to be
Am I the only one who finds it hard to navigate in portmaster(8)?
- options are neither sorted alphabetically nor grouped in blocks[1]
- too little space between an option and its description
- inconsistent in using terms (flags vs. options)
- being too verbose about port-related terms[2]
-
--On Monday, August 16, 2010 14:09:29 -0700 Doug Barton do...@freebsd.org
wrote:
On 8/13/2010 11:25 AM, Paul Schmehl wrote:
I want to DEPRECATE security/barnyard. It's a master port. The slave
is security/barnyard-sguil. Is it sufficient to DEPRECATE and EXPIRE
the master? Or do I need to
On Sun, Aug 15, 2010 at 09:58:12AM +0200, Frederic Culot wrote:
As a conclusion I would say that 'obskurator' should be removed from the
wanted
port page at http://wiki.freebsd.org/AndrewPantyukhin/Ports as it does not
manage to generate compilable obfuscated code as it claims to do.
On Sun, Aug 15, 2010 at 10:49:32PM -0700, David Wolfskill wrote:
[... rsyncd(8) port -- 873/tcp -- grabbed by either ypbind or amd before
rsynd started, so rsyncd isn't functional -- and doesn't whine about
it or terminate]
Thanks for the suggestions so far. Unfortunately, I'm finding
On 8/16/2010 3:04 PM, Olivier Smedts wrote:
I'm quite late, and won't speak for batch,
With portmaster 3.0 it should no longer be necessary. The option to stop
displaying config menus is now 100% effective.
but here is what I use
with portmaster. I switched recently from portupgrade to
On 08/16/2010 01:49, David Wolfskill wrote:
My build machine is noisy generates heat, so I leave it powered off
when it's not actively in use.
As a consequence, it gets rebooted rather often.
It is configured to run rsyncd(8) so I can update my laptop's local mirror
of the FreeBSD SVN
It's customary to cc the maintainer of a port when you're commenting on
it. Even more so when the maintainer is also the software author. I
usually keep up on the lists, but there are times when it falls lower on
the priority list so copying me on the message will ensure I can see it
in a
On 08/16/2010 17:20, jhell wrote:
The problem that I came across was that /usr/local/etc/rc.d is parsed
long after /etc/rc.d contents
This hasn't been true for a very long time. I first added the code to
incorporate the local scripts into the base rcorder almost 5 years ago.
so adding the
On Mon, 16 Aug 2010 20:20:31 -0400
jhell jh...@dataix.net wrote:
The problem that I came across was that /usr/local/etc/rc.d is parsed
long after /etc/rc.d contents so adding the BEFORE to the rsync start
script would not help or didn't at that time.
That only matters if you need to sort
Synopsis: Update port: sysutils/p5-Sys-Filesystem
Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Aug 17 02:01:19 UTC 2010
Responsible-Changed-Why:
Canonicalize assignment.
A while back I aborted a recursive update (bad idea, I know now) and
must have messed up something in whatever info portmaster uses to decide
whether to re-install a port. Now, whenever I use portmaster -a, it
re-installs py26-imaging, py26-reportlab and py26-xml.
Every time.
And it's a
On Mon 16 Aug 2010 at 19:48:23 PDT Charlie Kester wrote:
A while back I aborted a recursive update (bad idea, I know now) and
must have messed up something in whatever info portmaster uses to decide
whether to re-install a port. Now, whenever I use portmaster -a, it
re-installs py26-imaging,
A while back I aborted a recursive update (bad idea, I know now) and
must have messed up something in whatever info portmaster uses to decide
whether to re-install a port. Now, whenever I use portmaster -a, it
re-installs py26-imaging, py26-reportlab and py26-xml.
From portmaster(8):
Doug Barton do...@freebsd.org writes:
- inconsistent in using terms (flags vs. options)
Again, snarky; but I will take a look at making this usage more
consistent. Personally I have always used these terms interchangeably,
but I could have been wrong about it all this time. :)
The average
On 08/16/2010 20:07, Charlie Kester wrote:
On Mon 16 Aug 2010 at 19:48:23 PDT Charlie Kester wrote:
A while back I aborted a recursive update (bad idea, I know now)
Well not always, but apparently it was this time. :)
and
must have messed up something in whatever info portmaster uses to
On 08/16/2010 20:42, Anonymous wrote:
Doug Bartondo...@freebsd.org writes:
- inconsistent in using terms (flags vs. options)
Again, snarky; but I will take a look at making this usage more
consistent. Personally I have always used these terms interchangeably,
but I could have been wrong
29 matches
Mail list logo
