Sounds interesting.
Just thought I'd let you know that your man page
(http://recvmail.org/recvmail.8.html) is 404 ;-)
--patrick
Mark Heily <[EMAIL PROTECTED]> wrote:
recvmail-0.9 - recieve electronic mail
Recvmail is a simple and secure mail server for recieving incoming mail.
It
On Mon, Nov 28, 2005 at 12:34:05PM +1100, the unit calling itself Ian McWilliam
wrote:
>
> On 28 Nov 2005, at 8:18 AM, J Moore wrote:
>
> >Ian,
> >
> >Hope you'll excuse my persistence, but I'm still struggling with
> >akpop3d. I may be confused, but here's how I see my choices:
> >
> >1. chgrp
On Tue, Nov 29, 2005 at 01:08:42AM +0100, Bernd Ahlers wrote:
> Aleksander Piotrowski [Mon, Nov 28, 2005 at 09:29:51PM +0100] wrote:
> >Jacob Meuser <[EMAIL PROTECTED]> wrote:
> >
> >> to make pkg-config look for xft instead of freetype2, and add
> >> ${X11BASE}/lib/pkgconfig to PKG_CONFIG_PATH in
On Tue, Nov 29, 2005 at 12:15:09AM +0900, Peter O'Gorman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ralf Wildenhues wrote:
>
> | The way I see it, there are two possible ways out:
> |
> | 1) Move all paths to uninstalled libraries (in the correct order) before
the patch does pu
recvmail-0.9 - recieve electronic mail
Recvmail is a simple and secure mail server for recieving incoming mail.
It is best used in combination with Sendmail.
Features:
* Runs in a completely unprivileged chroot(1) jail
* System calls are restricted by systrace(1)
* Stealth mode
Aleksander Piotrowski [Mon, Nov 28, 2005 at 09:29:51PM +0100] wrote:
>Jacob Meuser <[EMAIL PROTECTED]> wrote:
>
>> to make pkg-config look for xft instead of freetype2, and add
>> ${X11BASE}/lib/pkgconfig to PKG_CONFIG_PATH in CONFIGURE_ENV.
>
>I'm almost sure that pkg-configs searches ${X11BASE}/l
*duh*, yeah I guess that would help.. Looks to have gotten past the
current roadblock. I'll know in about a day if the compile was
successful ;p I guess if I had RTFM'd the upgrade FAQ in the 1st place I
could have saved time and resources.
Thanks for the help!
-Original Message-
From: K
On Monday 28 November 2005 06:00 pm, Price, Joe wrote:
> I did upgrade, and forgot that step.. I removed that directory,
> unfortunately, I get the following now ;)
>
> Any ideas?
Extract the new contents of /usr/include/g++ from the
install sets.
-Kurt
I did upgrade, and forgot that step.. I removed that directory,
unfortunately, I get the following now ;)
Any ideas?
# make clean && make
[..]
writing dependencies file
cd ../generated; cp includeDBincludeDB.current
cd ../generated; cp
/usr/ports/devel/jdk/1.5/w-jdk-1.5.0p1
Did not not get my reply to this question when you sent it to
me directly?
Was this box upgraded from 3.6 or before and
rm -rf /usr/include/g++
not done durring the upgrade?
(see http://www.openbsd.org/faq/upgrade37.html)
It looks like your c++ headers are screwed.
Does building something lik
On Mon, 28 Nov 2005 21:36:47 +0100
Aleksander Piotrowski <[EMAIL PROTECTED]> wrote:
> Jasper Lievisse Adriaanse <[EMAIL PROTECTED]> wrote:
>
> > here's a diff to bring devel/p5-Term-Screen up to date (to version 1.03).
>
> So, this time you don't want to maintain port that you are updating?
Stev
Ian McWilliam wrote:
Not really the port needs fixing some what. Try the attached tar ball.
The port now creates a group _akpop3d and the lock files writable by
the _akpop3d group.
You will need to make /var/mail group writable, leave the permissons on
/var/mail as root:wheel (the default).
On 11/28/05, Aleksander Piotrowski <[EMAIL PROTECTED]> wrote:
> Eric Faurot <[EMAIL PROTECTED]> wrote:
>
> > In this patch:
> >
> > - 1.1.5 -> 1.1.5p0
> > - add header files needed by modules using the Imaging C API
>
> I would love to review port that needs those header files.
In my particular ca
Eric Faurot <[EMAIL PROTECTED]> wrote:
> In this patch:
>
> - 1.1.5 -> 1.1.5p0
> - add header files needed by modules using the Imaging C API
I would love to review port that needs those header files.
Alek
--
- Młodzi Rzymianie czytają? - Maya zachęciła ją do zwierzeń [...] .
- To okropne, to
Jasper Lievisse Adriaanse <[EMAIL PROTECTED]> wrote:
> here's a diff to bring devel/p5-Term-Screen up to date (to version 1.03).
So, this time you don't want to maintain port that you are updating?
Alek
--
Prawdziwych przyjaciół tej nocy nie znalazł, w Monterey natomiast nie
brakowało przyjaci
Jacob Meuser <[EMAIL PROTECTED]> wrote:
> to make pkg-config look for xft instead of freetype2, and add
> ${X11BASE}/lib/pkgconfig to PKG_CONFIG_PATH in CONFIGURE_ENV.
I'm almost sure that pkg-configs searches ${X11BASE}/lib/pkgconfig for
configuration files by default.
Alek
--
- Co to są liter
Hello,
here's an update for devel/p5-Object-Realize to 0.15. It works on i386.
Index: Makefile
===
RCS file: /cvs/ports/devel/p5-Object-Realize/Makefile,v
retrieving revision 1.6
diff -u -r1.6 Makefile
--- Makefile7 Feb 2005 19:0
Hello,
here's a diff to bring devel/p5-Term-Screen up to date (to version 1.03).
Index: Makefile
===
RCS file: /cvs/ports/devel/p5-Term-Screen/Makefile,v
retrieving revision 1.3
diff -u -r1.3 Makefile
--- Makefile21 Jun 2005 12:
ports@ denizens,
I've run across a strange issue with the dsniff port, specifically
urlsnarf on 3.8-stable.
Box is a pretty standard configuration, running CARP and pfsync. I'm
running urlsnarf on the physical interface itself, (running it on the CARP
interface has proven to be a bad idea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues wrote:
| The way I see it, there are two possible ways out:
|
| 1) Move all paths to uninstalled libraries (in the correct order) before
| all other path specs. This is pretty much in the spirit of the patch
| you posted in the other
Hi,
In this patch:
- 1.1.5 -> 1.1.5p0
- add header files needed by modules using the Imaging C API
Eric.
py-Imaging.diff
Description: Binary data
On Mon, 28 Nov 2005 10:36:12 +0100, frantisek holop wrote:
> /var/www and /var/www/htdocs might have different owners sometimes
Sure. So as of now I take it that my earlier suspicion of 'elegance' kicks
in. I never doubted the way it is done, and from your answer I take it
that putting the files
Hi Jacob,
* Jacob Meuser wrote on Mon, Nov 28, 2005 at 01:03:56AM CET:
> On Sun, Nov 27, 2005 at 09:06:09AM +0100, Ralf Wildenhues wrote:
> >
> > Libtool knows that the library is uninstalled, because this information
> > is encoded in libbar.la
>
> yes, it winds up in $notinst_path. I disconve
hmm, on Mon, Nov 28, 2005 at 04:08:59PM +0800, Uwe Dippel said that
> All clear. Only my original question was pointing into another
> corner: Why link / alias instead of just putting the files there ?
> Is there any *security* improvement through moving the files out of
> /htdocs/ respectively /us
On Mon, 28 Nov 2005 08:00:33 +, Antoine Jacoutot wrote:
> You don't _have_ to link files.
> You can use the Alias directive in your httpd.conf.
>
> Alias /phpmyadmin/ /var/www/phpmyadmin/
All clear. Only my original question was pointing into another
corner: Why link / alias instead of just
Selon Uwe Dippel <[EMAIL PROTECTED]>:
> probably a stupid one, but that's me, then:
> some applications (wordpress, phpmyadmin) put their files into
> /var/www/foo and symlink to these dir from /var/www/htdocs/ to ../foo.
You don't _have_ to link files.
You can use the Alias directive in your htt
26 matches
Mail list logo
