Mark Evenson wrote:
make: don't know how to make misc-depends. Stop
A target removed from somewhere in /usr/ports/Mk?
Yep, the target was removed. Fighting with the last problem I forgot
about this one. Fixed right now. Thanks Mark for the patch.
--
Dixi.
Sem.
Have you updated portupgrade to the last one (2.2.2_3,2)? Do it please.
Laganakos Vassilis wrote:
Hi,
Done that too (pkgdb -fu) , but didn't work for me... :(
I use FreeBSD6-stable
Vassilis
On Thu, Feb 01, 2007 at 01:45:55AM +0100, Csaba Molnar wrote:
2007. February 1. 00.34 d?tummal
David Stanford wrote:
missing key: categories: Cannot read the portsdb!
Something broken in INDEX :(
--
Dixi.
Sem.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Matthew Seaman wrote:
makes no difference. All of which seems to me to indicate a problem in
bsd.wx.mk
You're right. The problem is in the last bsd.wx.mk commit. A default
_WX_VER was changer from 2.6 to 2.8 but both _WX_PORT_python_2.8 and
_WX_FILE_python_2.8 variables are not defined.
--
Vasil Dimov wrote:
Hi,
Currently I get this:
% portversion -v gnupg
gnupg-1.4.6_2 needs updating (port has 2.0.1)
gnupg-2.0.1 = up-to-date with port
%
You did not show origins here. It can be an answer. I think they both
were security/gnupg.
This is
Daniel Malaby wrote:
I get an error when building mysql-administrator. I checked both FBSD
and mysql lists and did not find any info on this particular error, so I
was hoping you might be able to point me to some info.
Any help would be much appreciated.
[skipped]
In file included from
Hi.
I think portupgrade-devel is quite stable now. I use it on all servers
where I update ports often without problems. But anyway I need more
testers who could confirm its stablity. After a week of testing I'll
update portupgrade port to this version and start a next developing stage.
How you
Chuck Swiger wrote:
Should pkgdb not change the origin until after the port it thinks is the
new dependency actually is installed?
Sorry, I don't understand the question.
--
Dixi.
Sem.
___
freebsd-ports@freebsd.org mailing list
Stanislav Sedov wrote:
On Sat, 30 Sep 2006 17:45:18 +0200
Guillermo MORENO-SOCIAS [EMAIL PROTECTED] mentioned:
/libexec/ld-elf.so.1:
/usr/local/lib/perl5/site_perl/5.8.8/mach/auto/SNMP/SNMP.so: Undefined
symbol perl_get_sv
Try to deinstall net-snmp package before the build. Also it
Akinori MUSHA wrote:
Hi,
Is there anyone who can reproduce this build error? I couldn't
reproduce it on 4-STABLE nor on 6-STABLE.
http://pointyhat.freebsd.org/errorlogs/i386-4-latest/ruby18-mysql-2.7.1.log
http://pointyhat.freebsd.org/errorlogs/i386-5-latest/ruby18-mysql-2.7.1.log
Vasil Dimov wrote:
On Thu, Sep 21, 2006 at 12:48:18AM +1000, Nick Withers wrote:
Hey guys!
Sorry if this has already been pointed out a million or so
times, but the latest update of the ports UPDATING file (re:
zabbix) is listed as having been made on the 20061010. Being
the 2006-09-21 at
Matthew Seaman wrote:
The dependency on libGorm.so cannot point to '/usr/ports/' as the port to
intall to fulfill itself. I guess that's meant to say
/usr/ports/devel/gorm This patch looks to my untutored eye as if it might
provide the necessary fix:
Kris Kennaway wrote:
On Wed, Sep 13, 2006 at 03:54:44PM +0400, Stanislav Sedov wrote:
Hi!
We are going to update all sdl ports to latest version.
This will require modifications to sdl-dependent ports,
and we are currently doing full build in tinderbox
to ensure that all goes right.
Sergey Matveychuk wrote:
Kris Kennaway wrote:
On Wed, Sep 13, 2006 at 03:54:44PM +0400, Stanislav Sedov wrote:
Hi!
We are going to update all sdl ports to latest version.
This will require modifications to sdl-dependent ports,
and we are currently doing full build in tinderbox
to ensure
Carlos Fernando Assis Paniago wrote:
Hi. I'm trying to compile ruby (my system is up to date stable 6.1). And
it fails saying:
panix# cd /usr/ports/lang/ruby18
panix# make
NOTE:
You can enable pthread support by defining WITH_PTHREADS variable,
but not recommended since this might break
Stanislav Sedov wrote:
They are merely two different implementations of FAM subsystem: one
from SGI, another from RedHat. I belive, that SGI's one is sligthly
faster currently. Also, it covers standard completely contradictory to
gamin.
Does any of them use kqueue(2)?
--
Dixi.
Sem.
Dmitry Marakasov wrote:
What I propose is:
- Change variable naming scheme.
All *BASE and *DIR vars should be reverted to their original meanings
(i.e. local paths). Instead, INSTALL_ vars should be introduced:
INSTALL_LOCALBASE=${DESTDIR}/${LOCALBASE}
INSTALL_X11BASE=${DESTDIR}/${X11BASE}
Gábor Kövesdán wrote:
Hi,
I am pleased to announce, that portmgr committed my patch for ports
infrastructure DESTDIR support today. Note that this support is only for
Thanks for your work. It's highly appreciated.
The feature was discussed for years but no real progress had been done.
But a
Edwin Groothuis wrote:
On Fri, Aug 04, 2006 at 06:08:09PM +0200, G?bor K?vesd?n wrote:
I am pleased to announce, that portmgr committed my patch for ports
infrastructure DESTDIR support today. Note that this support is only for
the infrastructure, ports may or may not respect the DESTDIR
Mariusz Kownacki wrote:
Hello,
Since few days i have problem with installing ruby from ports
(/usr/ports/lang/ruby18).
According to advices I attach additional information. I would be
grateful for any help.
OS version:
FreeBSD xxx 6.1-STABLE FreeBSD 6.1-STABLE
---
[EMAIL
Gianni wrote:
SpamAssassin 3.1.4 was released.
Why do I get the following error messages in /var/log/maillolg ? If I restart
spamassassin then I haven't them again. What's wrong with it?
Aug 3 07:42:14 bastian spamd[66915]: mkdir /nonexistent: Permission denied
at
Sergey Matveychuk wrote:
Good. There is three patches there.
I'll test if they fix the vulnerabilities.
FYI The fixes was committed.
--
Dixi.
Sem.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
[LoN]Kamikaze wrote:
When a port installs dependencies prior to building and the -j flag is set
for make, portupgrade somehow breaks installing dependencies. If I simply do
# cd /usr/ports/category/port
# make install -j 4
it works fine, but the command
# portinstall category/port -m
[LoN]Kamikaze wrote:
I've got a Makefile where I install man pages int PREFIX/man/man1 and the
ports system nicely compresses them, but it does not make them available for
whatis. Should I run makewhatis PREFIX/man manually or is there a way this is
supposed to be done? The Porter's
Jim Trigg wrote:
I'm setting up a new system with 6.1-RELEASE, and I forgot to install
portupgrade from a package during the OS install. ruby-bdb fails to
build, complaining that it doesn't know how to make 'all' (it doesn't
specify which directory it's in, but it's right after it runs
[LoN]Kamikaze wrote:
Brooks Davis wrote:
On Wed, Jul 19, 2006 at 11:52:26AM +0200, [LoN]Kamikaze wrote:
Sergey Matveychuk wrote:
[LoN]Kamikaze wrote:
I've got a Makefile where I install man pages int PREFIX/man/man1 and the
ports system nicely compresses them, but it does not make them
Arseny Nasokin wrote:
I had pressed ^C when portupgrade checks database. Portupgrade's db is locked
always after it.
I have tryed to remove db and lock, remove and install again portupgrade but
nothing happines.
What should I do in this case?
What portupgrade version do you use?
A
Matt Sealey wrote:
(that is to say I applied the patch from the bugtracker and it rebuilds
but it still does the same error.. what exactly am I meant to rebuild as
in dependencies and so to make it work?)
After the patch applied, make sure you set WITH_BDB_VER to version you
want and type
Robert Huff wrote:
David J Brooks writes:
Voila! Everything was working perfectly again (including portupgrade) :-)
That did the trick!
Adding an extra data point:
The rebuild everything back up the tool-chain did not work
after an update early Friday morning.
It
Sergey Matveychuk wrote:
Robert Huff wrote:
David J Brooks writes:
Voila! Everything was working perfectly again (including portupgrade) :-)
That did the trick!
Adding an extra data point:
The rebuild everything back up the tool-chain did not work
after an update early
Bert van de Grift wrote:
On Mon, Jul 03, 2006 at 09:48:39AM +0400, Sergey Matveychuk wrote:
Daniel Dvor(a'k wrote:
Fixing the pkgdb.db does not help me at all.
It's a known issue.
Just remove the file and /usr/ports/INDEX*.db and run portupgrade
again. Note, it's described on man
Stay d wrote:
You did it, okay, thank you, but late :(
I always before upgrading something, go to /usr/ports and watch the UPDATING
file, simple there was nothing about portupgrade, nothing at the bigging of
June nothing at the end of June or at the bigging of July.
I am sorry that I do
101 - 132 of 132 matches
Mail list logo