package can be reinstalled without deleting first

I built a vixie-cron pkgsrc but I can "make install" it again and again
without the "is already installed" message and "pkg_delete" suggestion.

(I know it should fail, because other pkgsrc entries won't install if
already installed. Just tested.)

# ls -l /home/jeremy/netbsd/var/db/pkg/vixie-cron_4.0_b1/+BUILD_*
-rw-r--r--    1 root     jeremy        890 Oct 31 18:46
/home/jeremy/netbsd/var/db/pkg/vixie-cron_4.0_b1/+BUILD_INFO
-rw-r--r--    1 root     jeremy        162 Oct 31 18:46
/home/jeremy/netbsd/var/db/pkg/vixie-cron_4.0_b1/+BUILD_VERSION

# ls -l /home/jeremy/netbsd/usr/pkg/*bin/cron*
---s--x--x    1 root     root        31732 Oct 31 20:43
/home/jeremy/netbsd/usr/pkg/bin/crontab
---x--x--x    1 root     root        36552 Oct 31 20:43
/home/jeremy/netbsd/usr/pkg/sbin/cron

# pkg_info -e vixie-cron_4.0_b1
vixie-cron_4.0_b1

The following should fail:

# bmake install
===> Installing for vixie-cron_4.0_b1
install -c -m  111 -o root -s cron    /home/jeremy/netbsd/usr/pkg/sbin/
install -c -m 4111 -o root -s crontab /home/jeremy/netbsd/usr/pkg/bin/
sh putman.sh crontab.1 /home/jeremy/netbsd/usr/pkg/man
+ cp crontab.1 /home/jeremy/netbsd/usr/pkg/man/man1/crontab.1
+ set +x

Re: package can be reinstalled without deleting first

On Thu, Oct 31, 2002 at 09:04:47PM -0800, Jeremy C. Reed wrote:
> I built a vixie-cron pkgsrc but I can "make install" it again and again
> without the "is already installed" message and "pkg_delete" suggestion.
> 
[snip]
>
> # pkg_info -e vixie-cron_4.0_b1
> vixie-cron_4.0_b1

I think it's because of the package name -- pkg_info (I think) assumes that
package names are of the form "pkgbase-NNN" where "NNN" is the version
number of the package.  In this case, it doesn't find a version number and
probably causes mysterious breakage.  Try changing the package name to
"vixie-cron-4.0b1", or if this is the beta version leading up to a 4.0
release, then maybe "vixie-cron-3.99b1" might be better.

	Cheers,

	-- Johnny Lam <jlam <at> netbsd.org>

RFC: pvm patch for console output alignment

Hi,

for a long time, pvm console "conf" output wasn't aligned because many
NETBSD$FOO architecture names were wider than assumed in the code.

With the appended patch, the output is nice again. 

May I commit? (I'll certainly feed this back to PVM...)

Regards,
	-is

--- console/cmds.c.old	Wed Oct 30 12:47:26 2002
+++ console/cmds.c	Wed Oct 30 12:49:37 2002
 <at>  <at>  -1365,9 +1365,9  <at>  <at> 
 	if (!pvm_config(&nhosts, &narchs, &hostlist)) {
 		printf("%d host%s, %d data format%s\n",
 			nhosts, (nhosts > 1 ? "s" : ""), narchs, (narchs > 1 ? "s" : ""));
-		fputs("                    HOST     DTID     ARCH   SPEED       DSIG\n", stdout);
+		fputs("                    HOST     DTID         ARCH   SPEED       DSIG\n", stdout);
 		for (i = 0; i < nhosts; i++)
-			printf("%24s %8x %8s%8d 0x%08x\n",
+			printf("%24s %8x %12s%8d 0x%08x\n",
 					hostlist[i].hi_name,
 					hostlist[i].hi_tid,
 					hostlist[i].hi_arch,

Re: tar ignores filenames that contain `..'

On Thu, 31 Oct 2002, David Laight wrote:

: Since the actual problem is that following a symlink might take
: you outside the current directory hierarchy, why not make pax
: chroot to the current directory before reading the archive?

You have to do it as root.  You can't support -C properly.

And, last but not least, `suddenly' followed symlinks simply Should Not
Happen in a regular archive, regardless of where the link points.  Hence the
reason that my pax-mods proposals say nothing about whether the symlinks
contain "../" or start with "/".

Restricting pax from following extant symlinks by default, while providing
an option to allow it, should *not* affect any of its expected normal
behavior.

--

-- 
-- Todd Vierling <tv <at> pobox.com>

Opera printing

I have two printers configured, one of them plain text
and other postscript.
When I send a webpage to print, and I choose the
postscript filter, the file goes to plain text spool
instead of postscript.
Also, when I choose the printer program in the opera's
print dialog and type lpr -Pps, the same thing
happens.

Thanks a lot

César

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com

Re: Opera printing

On Fri, 1 Nov 2002, César Catrián wrote:
> I have two printers configured, one of them plain text
> and other postscript.
> When I send a webpage to print, and I choose the
> postscript filter, the file goes to plain text spool
> instead of postscript.
> Also, when I choose the printer program in the opera's
> print dialog and type lpr -Pps, the same thing
> happens.

Why do you think this is a problem with the NetBSD package?
Please remember that Opera is binary-only, and that we just use the Linux
binary too... (Let's blame the Opera-makers :)

 - Hubert

--

-- 
Want to get a clue on IPv6 but don't know where to start? Try this:
* Basics -> http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.html
* Setup  -> http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html
Of course with your #1 IPv6 ready operating system -> http://www.NetBSD.org/

Re: package can be reinstalled without deleting first

On Thu, 31 Oct 2002, Johnny C. Lam wrote:

> I think it's because of the package name -- pkg_info (I think) assumes that
> package names are of the form "pkgbase-NNN" where "NNN" is the version
> number of the package.  In this case, it doesn't find a version number and
> probably causes mysterious breakage.  Try changing the package name to
> "vixie-cron-4.0b1", or if this is the beta version leading up to a 4.0
> release, then maybe "vixie-cron-3.99b1" might be better.

Thanks!

I overlooked that. (That also explains why "pkg_info vixie-cron" without
version did not work either.)

I used vixie-cron-4.0.1. That is the version number the author told me in
February. The README says 4.0 was released over two years before this
version was dated.

(I have a few pkgsrc packages to submit via send-pr.)

   Jeremy C. Reed
   http://bsd.reedmedia.net/

Re: Opera printing

You are right, and I can print to file normally.
Thanks

César

 --- Hubert Feyrer
<hubert.feyrer <at> informatik.fh-regensburg.de> escribió:
> Why do you think this is a problem with the NetBSD
> package?
> Please remember that Opera is binary-only, and that
> we just use the Linux
> binary too... (Let's blame the Opera-makers :)
> 
> 
>  - Hubert
> 
> -- 
> Want to get a clue on IPv6 but don't know where to
> start? Try this:
> * Basics ->
>
http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.html
> * Setup  ->
>
http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html
> Of course with your #1 IPv6 ready operating system
> -> http://www.NetBSD.org/
> 

_________________________________________________________

bash2 and libintl check problem

pkgsrc/shells/bash2 won't build under Debian Linux.

configure:1325: gcc -o conftest
-I/home/jeremy/netbsd/usr/pkgsrc/shells/bash2/work/.gettext/include -O2
-I/home/jeremy/netbsd/usr/pkgsrc/shells/bash2/work/.gettext/include
-L/home/jeremy/netbsd/usr/pkgsrc/shells/bash2/work/.gettext/lib
-Wl,-R/usr/lib conftest.c
-L/home/jeremy/netbsd/usr/pkgsrc/shells/bash2/work/.gettext/lib
-Wl,-R/usr/lib -lintl 1>&5
/usr/bin/ld: cannot find -lintl

# ls -l /home/jeremy/netbsd/usr/pkgsrc/shells/bash2/work/.gettext/lib
total 0
lrwxrwxrwx    1 root     jeremy         18 Nov  1 13:15 libintl.* ->
/usr/lib/libintl.*

# ls -l /usr/lib/libintl.*
ls: /usr/lib/libintl.*: No such file or directory

But I also have:
/usr/include/libintl.h

The bash Makefile does:

.if exists(/usr/include/libintl.h)
GETTEXT_PREFIX=         /usr

Maybe that should check for libraries also.

I worked-around this by doing:

packages writing files out of LOCALBASE

I forgot that bash2 package writes to /etc/shells.

Should we consider (or is there) some variable that can be set to say
whether it is okay to write outside of LOCALBASE?

Comments?

   Jeremy C. Reed
   http://bsd.reedmedia.net/