I was successful at creating the manpage for the port i'm working on. My
problem is I'm not sure how to install it. The porter's Handbook wasn't much
help. The manpage is in files and I need to compress and install it in man8
like a normal manpage from workdir, I'm just not sure what to put in
I was successful at creating the manpage for the port i'm working on.
My problem is I'm not sure how to install it. The porter's Handbook
wasn't much help. The manpage is in files and I need to compress and
install it in man8 like a normal manpage from workdir, I'm just not
sure what to
Beech Rintoul wrote:
I was successful at creating the manpage for the port i'm working on. My
problem is I'm not sure how to install it. The porter's Handbook wasn't much
help. The manpage is in files and I need to compress and install it in man8
like a normal manpage from workdir, I'm just
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including experimental
development code and obsolete releases.
Bugs can be in one of several states:
o - open
A problem report has
On Sun, Dec 03, 2006 at 09:28:40PM +0800, Rong-En Fan wrote:
http://pointyhat.freebsd.org/errorlogs/i386-5-exp-latest/index-maintainer.html
We're now down to fewer than 110 ports that need to be corrected to
deal with a non-standard X11BASE location (the rest are more general
port
On Mon, Dec 11, 2006 at 10:29:37AM +0800, Chun-Tien Chang (?i?g??) wrote:
I found that LC_ALL is not working well in unrar with some charset like
(zh_TW.Big5, zh_CN.GBK, zh_CN.GB2312,zh_CN.eucCN)
Please contact Rar author on this issue. There may be some security
considerations in just
On Fri, Dec 08, 2006 at 08:24:25PM +0200, Peter Pentchev wrote:
On Fri, Dec 08, 2006 at 07:57:59PM +0200, Peter Pentchev wrote:
On Wed, Dec 06, 2006 at 02:56:57PM +0200, Peter Pentchev wrote:
Hi,
I'm writing to you all because you are listed as maintainers of ports
that depend
It seems that the change log on freshports for the databases/slony1
port shows that someone somewhere is confused as to who's the
maintainer of the port. The Makefile clearly shows it is still me.
On 23 Nov 2006, an update was issued to upgrade the 1.1.5 version to
1.2.0 which had known
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 11 Dec 2006 11:23:09 -0500
Vivek Khera [EMAIL PROTECTED] wrote:
It seems that the change log on freshports for the databases/slony1
port shows that someone somewhere is confused as to who's the
maintainer of the port. The Makefile
Jun Kuriyama wrote:
Hi,
I'm planning to upgrade security/gnupg to 2.0.1. This upgrade
includes portrevision bumps to indicate dependency changes.
I'm testing conditional plist, upgrading procedure by portupgrade.
But I think it's almost ready to commit.
If you have further
On Dec 11, 2006, at 12:47 PM, Martin Wilke wrote:
For this update of 1.2.0 gives a pr show here
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/105575 here is my
mistake thats commit is after 7 days not 14 days. This is my mistake
right. After this commit, I received a private email with a
On Mon, Dec 11, 2006 at 06:47:53PM +0100, Martin Wilke wrote:
If the committers are not going to follow the rules, then why should
anyone bother to be a maintainer?
I could say this is all my fault a concatenation of stupid mistakes :(
I hope you forgive me for this mistake.
Vivek,
Hello list,
After some more troubleshooting I've come a step further.
I have run the '/usr/local/bin/pfstat -q' command from a shell and found
some problems with my /usr/local/etc/pfstat.conf file. After solving
these problems I get the following message issueing the
'/usr/local/bin/pfstat -q'
On Mon, Dec 11, 2006 at 07:42:00PM +, Shaun Amott wrote:
In addition: I would guess that mail/imp, and maybe others, expect
bin/gpg to be present. If this is indeed the case, it would need
additional patching.
Sorry - ignore that last bit. I wasn't thinking. :-)
--
Shaun Amott //
El domingo 10 de diciembre a las 16:15:07 CET, GalaxyPC.Net escribió:
install-info --quiet /usr/local/info/gnupg1.info /usr/local/info/dir
install-info: menu item `gpg' already exists, for file `gpg'
http://lists.freebsd.org/pipermail/freebsd-questions/2006-February/114123.html
Check if
On Monday 11 December 2006 20:29, Lars Wittebrood wrote:
Hello list,
After some more troubleshooting I've come a step further.
I have run the '/usr/local/bin/pfstat -q' command from a shell and
found some problems with my /usr/local/etc/pfstat.conf file. After
solving these problems I get
On Mon, Dec 11, 2006 at 10:15:59AM -0800, Doug Barton wrote:
Jun Kuriyama wrote:
Hi,
I'm planning to upgrade security/gnupg to 2.0.1. This upgrade
includes portrevision bumps to indicate dependency changes.
I'm testing conditional plist, upgrading procedure by portupgrade.
But
Hi,
I'm quite busy and tired. Maybe I'll update it in a few week, before
the the end of the year. The 6.2.1 must be out then.
It's good to see that this port is usefull to someone.
___
freebsd-ports@freebsd.org mailing list
List doesn't like text/x-csrc it seems. Resend as text/plain.
On Monday 11 December 2006 21:10, Max Laier wrote:
On Monday 11 December 2006 20:29, Lars Wittebrood wrote:
Hello list,
After some more troubleshooting I've come a step further.
I have run the '/usr/local/bin/pfstat -q'
Good time of the day to you!
Had the following prob: analogous config (conf+ links + secret).
mpd4.0b4 works fine, but the latest b5 -- failed.
Server: FreeBSD from 6.1-RELEASE to 6.2-PRERELEASE.
client: m$ xp native
error on connection to b5: #778 that says it was not possible to verify
the
Petr,
GNAT/GPL and GNAT/GCC are two different products. I made
gnat-gcc* ports as an experimental alternative to the gnat
port (GNAT 2005/GPL). They are not meant to be complete or
supported neither they are expected to pass all the tests.
These are actually not the problems of the porting
On Mon, Dec 11, 2006 at 01:23:54PM -0500, Vivek Khera wrote:
Reading this PR more closely it seems I was not even notified, as
Oleg Gawriloff [EMAIL PROTECTED] is described as the maintainer
and is the one responding to maintainer queries, which he is not.
What isn't detected well is if
But you're right, this is not the way that it is supposed to work. Please
accept my apologies, and we'll look at the code.
Well, this looks to have been a combination of two human errors (on that
particular PR), which the code really doesn't know how to deal with. But
after looking at it, I'm
On Mon, Dec 11, 2006 at 05:13:27PM -0600, Mark Linimon wrote:
On Mon, Dec 11, 2006 at 01:23:54PM -0500, Vivek Khera wrote:
Reading this PR more closely it seems I was not even notified, as
Oleg Gawriloff [EMAIL PROTECTED] is described as the maintainer
and is the one responding to
At Mon, 11 Dec 2006 10:15:59 -0800,
Doug Barton wrote:
Thanks for letting us know what you're plans are. I think you know
what I'm going to say next. ;) As I suggested when I wrote to you in
private e-mail some time ago, I think it would be more in line with
the plans that the developers have
On 12/12/06, Jun Kuriyama [EMAIL PROTECTED] wrote:
I just think security/gnupg should be used as what
you should choose for GnuPG. If new ports user
wants to install GnuPG, I hope there is
security/gnupg as recommended stable version.
An unversioned directory is the maintainer-designated
Recently, I installed a FreeBSD/amd64 laptop. I found this port
uses apm (i386 only) interface to get battery information. The
patch below changes it to use sysctl(3). Thus, it is usable on
amd64.
http://people.freebsd.org/~rafan/xbattbar.diff
It works on my ThinkPad X60 (-CURRENT). If you are
Since as far as I can tell no one has said this to you yet, you may
want to have a look at the URL below and take a shot at updating this
yourself.
Good luck,
Doug
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html
--
This .signature sanitized for your
Thank you very much Max. The patch did the trick for me.
Regards,
Lars.
-Original Message-
From: Max Laier [mailto:[EMAIL PROTECTED]
Sent: Monday, December 11, 2006 9:10 PM
To: freebsd-ports@freebsd.org
Cc: Lars Wittebrood
Subject: Re: Pfstat trouble, no data in database file
On
Jun Kuriyama wrote:
At first, thank you for your helping to upgrade our gnupg world to
2.0.x. And sorry I cannot explain as you can feel reasonable.
I just want to make sure that the relevant issues are well thought
out, which it sounds like you have done.
I just think security/gnupg should
On 12/12/06, Rong-En Fan [EMAIL PROTECTED] wrote:
Recently, I installed a FreeBSD/amd64 laptop. I found this port
uses apm (i386 only) interface to get battery information. The
patch below changes it to use sysctl(3). Thus, it is usable on
amd64.
http://people.freebsd.org/~rafan/xbattbar.diff
31 matches
Mail list logo
