[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVSup S1G bug
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: CVSup S1G bug
- From: Han <han_(_at_)_mijncomputer_(_dot_)_nl>
- Date: Tue, 11 Sep 2001 17:24:20 +0200
- Mail-followup-to: misc_(_at_)_openbsd_(_dot_)_org
Christian Weisgerber (naddy_(_at_)_openbsd_(_dot_)_org) wrote:
> I have updated the net/cvsup current port to version 16.1d, which
> fixes this bug. Both net/cvsup and the lang/pm3 port it depends
> can be built without modifications on 2.9/i386. (However, since
> those ports were only introduced after the release, they aren't in
> I urge all users of cvsup to update.
It would be nice if the pkg was updated on the mirrors. I mean a pkg
with bug is now distributed... And pm3 is a resource eater.
Besides how will I update the ports tree if cvs does not work?
Gets weirder now: I just updated cvsup with:
cvsup -g -L 2 -i ports/net/cvsup /etc/cvs-supfile
[/usr/ports/net]# ls --full-time cvsup
-rw-rw-r-- 1 root wheel 1219 Tue Sep 11 17:18:27 2001 Makefile
drwxr-xr-x 2 root wheel 512 Tue Sep 11 17:18:30 2001 files/
drwxr-xr-x 2 root wheel 512 Tue Sep 11 17:18:30 2001 patches/
drwxr-xr-x 2 root wheel 512 Mon Jul 09 10:09:54 2001 pkg/
[~]$ pkg_info cvsup
Information for cvsup-bin-16.1-no_x11:
Were is that bug?