On Mon, Jul 03, 2006 at 10:15:56AM +0400, Sergey Matveychuk wrote:
> 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 /u
Hi,
> On Mon, 03 Jul 2006 10:15:56 +0400
> Sergey Matveychuk <[EMAIL PROTECTED]> said:
sem> See my HANDS-UP message a couples days ago at the list.
sem> Old (<=2.1.1,2) portupgrade use wrong (may be a right word will -
sem> "unexpected") database format.
I don't think that old portupgrad
On Fri, Jun 30, 2006 at 11:07:49AM -0400, Rob Szarka wrote:
> Thanks for the tip about the version. I didn't realize the 5.1 tree
> was development.
That would probably be because it isn't.
--
Riemer PalstraAmsterdam, The Netherlands
[EMAIL PROTECTED]
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'
Hannes Hauswedell wrote:
> i have problems figuering out the problem, though (this is my first port). i
> followed the "porters handbook"'s directions and everything looked fine over
> here
Everybody sometimes does something for the first time. And it's very
good you started doing your fi
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 page - if you fo
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 page - if you found pkgdb.db seriously
broken, just remove it.
--
Dixi.
Sem.
On Sun, 2 Jul 2006, Kevin Oberman wrote:
I have been unable to update tcl8.4 on my laptop running -current. I
have one other system running -current, but it installed the upgrade
correctly. It compiles without error, but if fails in the tests.
All of the errors were socket connection failure an
I have been unable to update tcl8.4 on my laptop running -current. I
have one other system running -current, but it installed the upgrade
correctly. It compiles without error, but if fails in the tests.
All of the errors were socket connection failure and included http,
httpold, io, and socket. he
> Synopsis: New Port: sysutils/kports (error in the last one)
>
> State-Changed-From-To: open->feedback
> State-Changed-By: itetcu
> State-Changed-When: Sun Jul 2 18:53:05 UTC 2006
> State-Changed-Why:
> Build errors:
> http://sce-tindy.tecnik93.com/tb-exp/index.php?action=describe_port&id=961
>
>
Hi all,
I upgraded my portupgrade to version 2.1.3 12 days ago, it was broken, okay
after reading Makeconf changes a go back by portupgrading to 2.1.4, actualy
2.1.1,2.
I was glad to see the portupgrade is working again.
Today cron/portsnap update told me, there is new version of portupgrade,
Hello;
FYI science/elmer*-5.2 has been released!
Unfortunately my main development machine was stolen so I won't be able to work
on these ports anymore (at least not soon), but updating it should be very easy
and I'll be glad to answer questions from anyone wanting to be the new
maintainer. It wo
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 did after an
At Thu, 29 Jun 2006 18:46:26 -0700 (PDT),
Dan Reinholz wrote:
>
> Both of these ports are on version 1.3.0. However, an
> updated version 1.3.3 is available for both of them.
> Simply modifying the version number in the port
> (pointing the Makefile to the updated source) is
> sufficient to get th
On Sunday 02 July 2006 07:07, yattaran wrote:
> David J Brooks wrote:
> > After running 'portupgrade portupgrade' I am left with the following
> > error when I run portversion or portupgrade, or pretty much any program
> > that addresses the ports collection:
> >
> > /libexec/ld-elf.so.1:
> > /usr/
hi,
i am very happy to see today the libupnp1.4.0 in the ports :-) .
at home i am testing the mediatomb (mediatomb.sourceforge.net) upnp-server on
my freebsd 6.1 machine. i compiled the libupnp 1.4.0 by myself under freebsd
6.1, and i must make some changes. i will attach this patches. some are
David J Brooks wrote:
After running 'portupgrade portupgrade' I am left with the following error
when I run portversion or portupgrade, or pretty much any program that
addresses the ports collection:
/libexec/ld-elf.so.1: /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so:
Undefined symbo
On 6/30/06, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
On Fri, Jun 30, 2006 at 10:32:25PM +0200, Anders Troback wrote:
> Hi there!
>
> Just installed the denyhost port but when I fire it up it's complains
> about the missing config file:
>
> # /usr/local/etc/rc.d/denyhosts start
> Starting denyh
David J Brooks wrote:
> On Saturday 01 July 2006 11:46, Sergey Matveychuk wrote:
>> Well, I did send-pr a couple hours ago but it's still not in GNATS.
>> I'm afraid I can forget to track. So here is a patch.
>> IIRC attachment will cut in main list, so here is cut&paste. The patch
>> is two-lined,
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we are attempting to notify maintainers of
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exp
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we are attempting to notify maintainers of
ports that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
David J Brooks wrote:
> On Saturday 01 July 2006 09:48, Sergey Matveychuk wrote:
>> David J Brooks wrote:
>>> On Saturday 01 July 2006 08:57, Sergey Matveychuk wrote:
Sergey Matveychuk wrote:
> Kostik Belousov wrote:
>> On Sat, Jul 01, 2006 at 03:49:45PM +0400, Sergey Matveychuk wrote:
23 matches
Mail list logo
