Hi,
Following the most recent update of PHP5 (5.2.6_2) and subsequent
portaudit warnings for 5.2.6, I've been upgrading lang/php5 and
lang/php5-extensions-1.1 on a number of machines.
My question is, what is the best way to do this. Some options come to mind:
1) portupgrade -fpb php5-5.2.6
Hi,
Following the most recent update of PHP5 (5.2.6_2) and subsequent
portaudit warnings for 5.2.6, I've been upgrading lang/php5 and
lang/php5-extensions-1.1 on a number of machines.
My question is, what is the best way to do this. Some options come to mind:
1) portupgrade -fpb php5-5.2.6 p
Pine Digital Security Support wrote:
Hi,
Following the most recent update of PHP5 (5.2.6_2) and subsequent
portaudit warnings for 5.2.6, I've been upgrading lang/php5 and
lang/php5-extensions-1.1 on a number of machines.
My question is, what is the best way to do this. Some options come to
Frederique Rijsdijk wrote:
Hi,
Following the most recent update of PHP5 (5.2.6_2) and subsequent
portaudit warnings for 5.2.6, I've been upgrading lang/php5 and
lang/php5-extensions-1.1 on a number of machines.
My question is, what is the best way to do this. Some options come to mind:
1) p
> Pine Digital Security Support wrote:
>>
>> Hi,
>>
>> Following the most recent update of PHP5 (5.2.6_2) and subsequent
>> portaudit warnings for 5.2.6, I've been upgrading lang/php5 and
>> lang/php5-extensions-1.1 on a number of machines.
>>
>> My question is, what is the best way to do this. So
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
* Alexey Shuvaev ([EMAIL PROTECTED]) wrote:
> While the ports are in freeze just want to point to the problem I have
> encountered. Not sure if this is a critical bug, just a bug or not
> a bug at all (so, no PR yet).
This is definitely a bug, so better send-pr for this issue not to be
lost while
On Tue, Sep 09, 2008 at 05:20:06PM +0400, Dmitry Marakasov wrote:
> * Alexey Shuvaev ([EMAIL PROTECTED]) wrote:
>
> > While the ports are in freeze just want to point to the problem I have
> > encountered. Not sure if this is a critical bug, just a bug or not
> > a bug at all (so, no PR yet).
> Th
* Peter Pentchev ([EMAIL PROTECTED]) wrote:
> > This is definitely a bug, so better send-pr for this issue not to be
> > lost while we're in freeze.
> What I mean is the following scenario:
> - libfoo uses libtool for its build
> - libfoo depends on libbar which depends on GNU sed
> - during libfo
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Here's the fix, btw.
Portrevision bump is to make users with gsed-tainted libtool to
rebuild it with correct sed.
--- libtool.patch begins here ---
Index: Makefile
===
RCS file: /home/pcvs/ports/devel/libtool15/Makefile,v
retrieving
Hello,
while playing with fastcgi stuff, i have updated my tool to explore the
FreeBSD ports tree. It is now a fastcgi responder which can answer
questions behind a web server such as apache or lighttpd. It can be
found here:
http://www.lpthe.jussieu.fr/~talon/show_index.fcgi
The needed configura
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear portmgr team,
I would like to ask you to approve the following fix:
devel/p5-Data-Dump-Streamer
[http://www.gahr.ch/FreeBSD/patches/p5-Data-Dump-Streamer.diff]
Background:
Update to 0.06 of devel/p5-B-Utils has changed the installation path
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
On Tue, Sep 09, 2008 at 06:11:44PM +0400, Dmitry Marakasov wrote:
> * Peter Pentchev ([EMAIL PROTECTED]) wrote:
>
> > > This is definitely a bug, so better send-pr for this issue not to be
> > > lost while we're in freeze.
> > What I mean is the following scenario:
> > - libfoo uses libtool for it
---> Backing up the old version
---> Uninstalling the old version
---> Deinstalling 'dovecot-1.1.2_1'
Dovecot is still running. Shall I stop it? [y]?
If you do not intend to reinstall Dovecot, you should manually remove
the user 'dovecot' (uid='143') and the group 'dovecot' (gid='143').
Clean
On Wed, Sep 10, 2008 at 01:23:01AM +0400, Alex Keda wrote:
---> Backing up the old version
---> Uninstalling the old version
---> Deinstalling 'dovecot-1.1.2_1'
Dovecot is still running. Shall I stop it? [y]?
...
---> Restoring the old version
Dovecot has reserved the groupname 'do
20 matches
Mail list logo
