On 7/24/07, Norberto Meijome <[EMAIL PROTECTED]> wrote:
On Mon, 23 Jul 2007 22:52:58 +0200
Nikola Lecic <[EMAIL PROTECTED]> wrote:
> > However, I gave up on getting Java working in Linux-Firefox. The
> > plugins _do_ show in about:plugins, but the Java test page shows
> > 'applet testvm not init
Hi!
Eclipse.org seemingly do not provide source codes of 3.3/Europe. We may need
to extract necessary source code from CVS repository which is different from
3.1/3.2 era.
We may need to have different approach/strategy
___
freebsd-ports@fre
Sorry, please ignore my previous mail.
I found the source code
Sorry!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Following the recent upgrade I am getting errors with samba
:
[EMAIL PROTECTED] /usr]# smbclient //localhost/test -U sambap
Password:
Domain=[DNS1] OS=[Unix] Server=[Samba 3.0.25a]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
I have tried googlling but to no avail.
Can anyone point me in the r
On Wednesday 25 July 2007 08:34:47 David Southwell wrote:
> Following the recent upgrade I am getting errors with samba
>
> [EMAIL PROTECTED] /usr]# smbclient //localhost/test -U sambap
> Password:
> Domain=[DNS1] OS=[Unix] Server=[Samba 3.0.25a]
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
On Wed, 25 Jul 2007, Wilson Ribeiro wrote:
I only typed make in firefox directory in ports tree... i didn't do
modifications i tried compile seamonkey and same problem ocurred...
Wilson Ribeiro
2007/7/25, Garrett Cooper <[EMAIL PROTECTED]>:
Wilson Ribeiro wrote:
> hi,
>
> error message:
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
hi,
error message:
ClassInfo.cpp
{standard input}: Assembler messages:
{standard input}:22958: Warning: end of file not at end of a line; newline
inserted
c++: Internal error: Killed: 9 (program cc1plus)
{standard input}:23815: Error: unrecognized symbol type "obje"
other informations:
FreeBS
Greetings,
When I upgraded to x11/xterm-227, I noticed that "rows" and "columns" as
reported to the terminal device by xterm were set to 0:
system:/home/cwt/xterm-227> stty all
speed 38400 baud; 0 rows; 0 columns;
Terminal applications would not properly recognize the window
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a re
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a re
Wilson Ribeiro wrote:
hi,
error message:
ClassInfo.cpp
{standard input}: Assembler messages:
{standard input}:22958: Warning: end of file not at end of a line;
newline
inserted
c++: Internal error: Killed: 9 (program cc1plus)
{standard input}:23815: Error: unrecognized symbol type "obje"
ot
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
Is anyone else seeing broken modifier keys (specifically the Win key)
with the new xkeyboard-config in ports, or is it just me?
xmodmap shows mod4 as blank. The Windows key also now seems to be
mapped to Meta_L instead of Super_L. Even after doing xmodmap -e "add
mod4 = Meta_L", beryl still wasn
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a re
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
To Whom Slowness of Portupgrade Concerns a Lot:
As I got tired of long waiting of portupgrade trying to resolve dependencies, I
came up with yet another tool for upgrading FreeBSD ports system. Unlink other
tools, it tries to maximize existing resource to maximize its performance.
This progra
Norberto Meijome wrote:
On Tue, 24 Jul 2007 22:05:52 -0700
Predrag Punosevac <[EMAIL PROTECTED]> wrote:
Well, I hope that they are aware but it seems that nobody is acting on
these issues(or at least not fast enough).
Predrag,
as good as your intentions seem to be, the results would
On Tue, 24 Jul 2007 22:05:52 -0700
Predrag Punosevac <[EMAIL PROTECTED]> wrote:
> Well, I hope that they are aware but it seems that nobody is acting on
> these issues(or at least not fast enough).
Predrag,
as good as your intentions seem to be, the results would be better if you
provided he
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a re
I am the maintainer of www/validator and was getting ready to update the
port since the W3C Validator has been updated to 0.8.0 now. However,
because of the changes that the W3C has made to the Validator, it requires a
Perl module called SGML::Parser::OpenSP, which they say has not yet been
releas
I should reword the part about SGML::Parser::OpenSP being unreleased. It
turns out it has been released, but the version that the W3C needs for the
new version of the Validator to work requires a version that they have not
yet released. The current version on CPAN is 0.99 and the version of their
25 matches
Mail list logo
