Re: update: vim7

2006-05-11 Thread steven mestdagh
Chris Kuethe [2006-05-10, 21:10:34]:
 Try 2... I forgot to check the no_x11 flavor.

seems to be okay on sparc64.  looks like you forgot to remove a 'p0' here
===  Building package for vim-lang-7.0.0p0-gtk2

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm



UPDATE: leafpad-0.8.9

2006-05-11 Thread Antoine Jacoutot
Hi.

Here's a diff to:

- update leafpad to the latest stable version (0.8.9)
- force dependency on gnomeprintui so that printing is enabled (before, if you
built the port without gnomeprintui, there was no registered dependency,
however if libgnomeprint was already installed, the configure script would pick
it up); thanks to Can Erkin Acar canacar at eee.metu.edu.tr for catching this

Please test and commit.

-- 
Antoine

leafpad.diff
Description: Binary data


distfiles gone?

2006-05-11 Thread Toni Mueller

Hello,

I wanted to fix a problem I have, but stumbled over this:

 
MASTER_SITE_OVERRIDE=ftp://ftp.openbsd.org/pub/OpenBSD/distfiles/${cipher}/${value}/;

(in bsd.port.mk)

The problem is that this directory
ftp://ftp.openbsd.org/pub/OpenBSD/distfiles/ does not exist. Since
upstream managed to put up a tarball that is different from what's
required in the OpenBSD ports mechanism, but under the same name, I am
now unsure as to how to proceed.

In theory, as far as I understood, the directory named above should be
there and hold all upstream distfiles as a last resort, for all
supported releases (ie, 3.8 and 3.9).

The culprit is db-4.2 which I need for 3.8/i386, but can't easily get
at atm. So far, I hope to get at the file to avoid re-constructing the
port...


Best,
--Toni++



Re: distfiles gone?

2006-05-11 Thread steven mestdagh
Toni Mueller [2006-05-11, 11:06:31]:
 
 Hello,
 
 I wanted to fix a problem I have, but stumbled over this:
 
  
 MASTER_SITE_OVERRIDE=ftp://ftp.openbsd.org/pub/OpenBSD/distfiles/${cipher}/${value}/;
 
 (in bsd.port.mk)
 
 The problem is that this directory
 ftp://ftp.openbsd.org/pub/OpenBSD/distfiles/ does not exist. Since
 upstream managed to put up a tarball that is different from what's
 required in the OpenBSD ports mechanism, but under the same name, I am
 now unsure as to how to proceed.
 
 In theory, as far as I understood, the directory named above should be
 there and hold all upstream distfiles as a last resort, for all
 supported releases (ie, 3.8 and 3.9).
 
 The culprit is db-4.2 which I need for 3.8/i386, but can't easily get
 at atm. So far, I hope to get at the file to avoid re-constructing the
 port...

Yes, the distfiles directory seems to be gone temporarily.
I remember fixing the distinfo because they changed it. However, we don't
propagate this kind of fixes to the -stable branches. Normally you can
copy over the distinfo file from the 3.9 or current ports tree.

steven

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm



Re: update: vim7

2006-05-11 Thread Pedro Martelletto
This one works for me (no_x11 flavour) on macppc and i386. However, it's
leaving behind an empty share/vim/vim70/lang directory upon deletion
(whereas the previous version didn't), is that intentional?

-p.



Re: update: vim7

2006-05-11 Thread Tan Dang

On 5/10/06, Chris Kuethe [EMAIL PROTECTED] wrote:

rumor has it the attachment got eaten...



Ok here on sparc64, but it leaves share/vim/vim70/lang behind on deinstall.






--
GDB has a 'break' feature; why doesn't it have 'fix' too?







Re: OpenBSD 3.9 MySQL 5.0.18 ports compile issues

2006-05-11 Thread Kevin

On 5/2/06, Jolan Luff [EMAIL PROTECTED] wrote:

On Tue, May 02, 2006 at 03:17:15PM -0700, Kevin wrote:
 Hello all,

 Just reloaded two of our Alpha servers to upgrade them to 3.9, and I'm
 having issues with MySQL not compiling from ports.

 Before I go filing bug reports and such I did the requisite searching
 to no avail. Am I the only one seeing the following behavior?

 as root:
 # cd  /usr/ports/databases/mysql
 # make install

 It chugs along for a bit like normal then bails with an apparent gmake
 error.

Actually, it's an ICE:

sql_table.cc:2507: Internal compiler error in `gen_reload_inhi', at 
insn-emit.c:5550

gcc2 on alpha is known to have problems.  You can try building with
different optimization levels like so:

env CFLAGS=-Os make install

and then try -O1, -O0, etc.  If that doesn't work then someone will have
to make the mysql port use gcc3 from ports on alpha and see if that
fixes it.



Hi Jolan et al,

Thanks for the reply--sorry for the delay. I was out of town for a few
days and wanted to give this its due effort.

So I've tried a variety of the above combinations to no avail. :-(

Same story.

FWIW: I  just glanced at the ftp mirrors, and there are only two
pre-compiled php5 packages for Alpha on 3.9 (core and pear), so this
seems to be affecting more than just mysql (i.e. no php5-pgsql,
php5-curl, etc...)

If it's of any use, I can make one of my alpha machines available
remotely to any OBSD dev.


Anyone have any other thoughts?


Thanks much,
Kevin








--
http://www.ebiinc.com :
Background Screening, Drug Testing  More
Leaders in background checks, worldwide.



mysql update error

2006-05-11 Thread Tomasz Pajor
I'm trying to upgrade my MySQL install and I'm getting this error:

bash-3.1# env SUBPACKAGE=-server make update
=== Updating for mysql-server-5.0.21
Upgrading from mysql-server-5.0.19
New package mysql-server-5.0.21 contains potentially unsafe operations
+INSTALL script
Can't safely update to mysql-server-5.0.21 (use -F update to force it)
/usr/sbin/pkg_add:
/usr/ports/packages/i386/all/mysql-server-5.0.21.tgz:Fatal error
*** Error code 1

Stop in /usr/ports/databases/mysql (line 2045 of
/usr/ports/infrastructure/mk/bsd.port.mk).

Can anyone help, thanks.

-- 
Tomasz Pajor
WebSolutions





new ports: colrdx, hamlib, tlf

2006-05-11 Thread Jason Wright
I've got a bunch (ok, 7 so far) hamradio apps I've ported. The
tar file at the link below contains the start of what I'd like
to get into the tree (under the directory hamradio).  My port-fu
is no good, so I'd appreciate review and feedback.

http://www.thought.net/jason/ham.tgz

--Jason L. Wright



Re: mysql update error

2006-05-11 Thread Alexandre Anriot
 I'm trying to upgrade my MySQL install and I'm getting this error:
 
 bash-3.1# env SUBPACKAGE=-server make update
 === Updating for mysql-server-5.0.21
 Upgrading from mysql-server-5.0.19
 New package mysql-server-5.0.21 contains potentially unsafe operations
 +INSTALL script
 Can't safely update to mysql-server-5.0.21 (use -F update to force it)
 /usr/sbin/pkg_add:
 /usr/ports/packages/i386/all/mysql-server-5.0.21.tgz:Fatal error
 *** Error code 1
 
 Stop in /usr/ports/databases/mysql (line 2045 of
 /usr/ports/infrastructure/mk/bsd.port.mk).

Use make package instead, and

pkg_add -F update mysql-server-5.0.21

then, as suggested by the error message.



Re: mysql update error

2006-05-11 Thread Brad
On Thu, May 11, 2006 at 09:56:29PM +0200, Tomasz Pajor wrote:
 I'm trying to upgrade my MySQL install and I'm getting this error:
 
 bash-3.1# env SUBPACKAGE=-server make update
 === Updating for mysql-server-5.0.21
 Upgrading from mysql-server-5.0.19
 New package mysql-server-5.0.21 contains potentially unsafe operations
 +INSTALL script
 Can't safely update to mysql-server-5.0.21 (use -F update to force it)
 /usr/sbin/pkg_add:
 /usr/ports/packages/i386/all/mysql-server-5.0.21.tgz:Fatal error
 *** Error code 1
 
 Stop in /usr/ports/databases/mysql (line 2045 of
 /usr/ports/infrastructure/mk/bsd.port.mk).
 
 Can anyone help, thanks.
 
 -- 
 Tomasz Pajor
 WebSolutions

As it says... use the -F update option for pkg_add. This is necessary
for any package which has an INSTALL script no matter what the script
does. I believe in most cases the INSTALL scripts are fine, but we play
it on the safe side for now.



Re: OpenBSD 3.9 MySQL 5.0.18 ports compile issues

2006-05-11 Thread Brad
On Thu, May 11, 2006 at 09:34:09AM -0700, Kevin wrote:
 On 5/2/06, Jolan Luff [EMAIL PROTECTED] wrote:
 On Tue, May 02, 2006 at 03:17:15PM -0700, Kevin wrote:
  Hello all,
 
  Just reloaded two of our Alpha servers to upgrade them to 3.9, and I'm
  having issues with MySQL not compiling from ports.
 
  Before I go filing bug reports and such I did the requisite searching
  to no avail. Am I the only one seeing the following behavior?
 
  as root:
  # cd  /usr/ports/databases/mysql
  # make install
 
  It chugs along for a bit like normal then bails with an apparent gmake
  error.
 
 Actually, it's an ICE:
 
 sql_table.cc:2507: Internal compiler error in `gen_reload_inhi', at 
 insn-emit.c:5550
 
 gcc2 on alpha is known to have problems.  You can try building with
 different optimization levels like so:
 
 env CFLAGS=-Os make install
 
 and then try -O1, -O0, etc.  If that doesn't work then someone will have
 to make the mysql port use gcc3 from ports on alpha and see if that
 fixes it.
 
 
 Hi Jolan et al,
 
 Thanks for the reply--sorry for the delay. I was out of town for a few
 days and wanted to give this its due effort.
 
 So I've tried a variety of the above combinations to no avail. :-(
 
 Same story.
 
 FWIW: I  just glanced at the ftp mirrors, and there are only two
 pre-compiled php5 packages for Alpha on 3.9 (core and pear), so this
 seems to be affecting more than just mysql (i.e. no php5-pgsql,
 php5-curl, etc...)
 
 If it's of any use, I can make one of my alpha machines available
 remotely to any OBSD dev.
 
 
 Anyone have any other thoughts?
 
 
 Thanks much,
 Kevin

I have a somewhat decent alpha now, so I'll take a look into this
issue.



Re: mysql update error

2006-05-11 Thread Tomasz Pajor
bash-3.1# pkg_add mysql-server-5.0.21.tgz
Can't install mysql-server-5.0.21 because of conflicts
(partial-mysql-server-5.0.19)
/usr/sbin/pkg_add: mysql-server-5.0.21.tgz:Fatal error
bash-3.1# pkg_add -F update mysql-server-5.0.21.tgz
Can't install mysql-server-5.0.21 because of conflicts
(partial-mysql-server-5.0.19)
/usr/sbin/pkg_add: mysql-server-5.0.21.tgz:Fatal error

I still have problems.
-- 
Tomasz Pajor
WebSolutions

 I'm trying to upgrade my MySQL install and I'm getting this error:

 bash-3.1# env SUBPACKAGE=-server make update
 === Updating for mysql-server-5.0.21
 Upgrading from mysql-server-5.0.19
 New package mysql-server-5.0.21 contains potentially unsafe operations
 +INSTALL script
 Can't safely update to mysql-server-5.0.21 (use -F update to force it)
 /usr/sbin/pkg_add:
 /usr/ports/packages/i386/all/mysql-server-5.0.21.tgz:Fatal error
 *** Error code 1

 Stop in /usr/ports/databases/mysql (line 2045 of
 /usr/ports/infrastructure/mk/bsd.port.mk).

 Use make package instead, and

 pkg_add -F update mysql-server-5.0.21

 then, as suggested by the error message.






Re: mysql update error

2006-05-11 Thread viq
On Thursday 11 May 2006 22:31, Tomasz Pajor wrote:
 bash-3.1# pkg_add mysql-server-5.0.21.tgz
 Can't install mysql-server-5.0.21 because of conflicts
 (partial-mysql-server-5.0.19)
 /usr/sbin/pkg_add: mysql-server-5.0.21.tgz:Fatal error
 bash-3.1# pkg_add -F update mysql-server-5.0.21.tgz
 Can't install mysql-server-5.0.21 because of conflicts
 (partial-mysql-server-5.0.19)
 /usr/sbin/pkg_add: mysql-server-5.0.21.tgz:Fatal error

 I still have problems.

you want to add -r to that

-- 
viq



Re: mysql update error

2006-05-11 Thread Tomasz Pajor
It worked thank you very much.

-- 
Tomasz Pajor
WebSolutions

 On Thursday 11 May 2006 22:31, Tomasz Pajor wrote:
 bash-3.1# pkg_add mysql-server-5.0.21.tgz
 Can't install mysql-server-5.0.21 because of conflicts
 (partial-mysql-server-5.0.19)
 /usr/sbin/pkg_add: mysql-server-5.0.21.tgz:Fatal error
 bash-3.1# pkg_add -F update mysql-server-5.0.21.tgz
 Can't install mysql-server-5.0.21 because of conflicts
 (partial-mysql-server-5.0.19)
 /usr/sbin/pkg_add: mysql-server-5.0.21.tgz:Fatal error

 I still have problems.

 you want to add -r to that

 --
 viq






Fix for /usr/ports/devel/startup-notification/patches/patch-libsn_sn-util_c

2006-05-11 Thread Michael Mitton

I found a problem with a patch in startup-notification.  The strncpy
statements were not copying the correct amount of data due to using
sizeof() instead of strlen() values.  Old patch and fixed patch below.

-Michael


Old Patch

$OpenBSD: patch-libsn_sn-util_c,v 1.1 2005/05/25 23:53:37 marcm Exp $
--- libsn/sn-util.c.orig   Wed May 25 16:35:54 2005
+++ libsn/sn-util.c  Wed May 25 16:37:28 2005
@@ -257,7 +257,7 @@ sn_internal_strdup (const char *str)
  char *s;

  s = sn_malloc (strlen (str) + 1);
-  strcpy (s, str);
+  strncpy (s, str, sizeof(s));

  return s;
}
@@ -376,6 +376,6 @@ sn_internal_append_to_string (char
  *append_to = sn_realloc (*append_to, *current_len + len + 1);

  end = *append_to + *current_len;
-  strcpy (end, append);
+  strncpy (end, append, sizeof(end));
  *current_len = *current_len + len;
}


New Patch

$OpenBSD: patch-libsn_sn-util_c,v 1.1 2005/05/25 23:53:37 marcm Exp $
--- libsn/sn-util.c.orig   Wed May 25 16:35:54 2005
+++ libsn/sn-util.c  Wed May 25 16:37:28 2005
@@ -257,7 +257,7 @@ sn_internal_strdup (const char *str)
  char *s;

  s = sn_malloc (strlen (str) + 1);
-  strcpy (s, str);
+  strncpy (s, str, strlen (str) + 1);

  return s;
}
@@ -376,6 +376,6 @@ sn_internal_append_to_string (char
  *append_to = sn_realloc (*append_to, *current_len + len + 1);

  end = *append_to + *current_len;
-  strcpy (end, append);
+  strncpy (end, append, len + 1);
  *current_len = *current_len + len;
}



Re: Fix for /usr/ports/devel/startup-notification/patches/patch-libsn_sn-util_c

2006-05-11 Thread Theo de Raadt
-  strcpy (s, str);

Yes, the old code is totally wrong for using strcpy.

+  strncpy (s, str, sizeof(s));

And whoever tried to fix it, made it even worse.  Now it only copies
either 4 bytes, 8 bytes, or the size of the destination buffer if it
is not a pointer (and it is a pointer, isn't it).  Heck, they might as
well have put a value 1 in there, for all that diff is worth.

+  strncpy (s, str, strlen (str) + 1);

Ah, but this diff is 100% the same as the original strcpy().  Think
about it.

If that is the best anyone can do, amateurish buffer overflow fixing
which makes it worse or doesn't fix it, then they should not change
the code.  There is an alternative.

Some people should instead try the alternative:

Don't try to fix it, but yell at the authors about the
problem repeatedly.

That's something even amateurs can do.  If you can spot it, you can
always get it fixed correctly that way.  But don't rely on even OpenBSD
developers (or ports contributers) to get this this right all the time.
The responsibility always lies with the official maintainer...