of providing precompiled binary packages, using patches by Peter Wemm and
Bjoern A. Zeeb. This gets up "good" cvsup for upcoming 6.0 release.
- Turn off X11 automatically on amd64 instead of erroring out
- Bjoern A. Zeeb agreed to take maintainership of this port for amd64 arch
(read: help endusers solving their problems)
Based on: bz's patches floating on mailing list
Approved by: jdp (maintainer)
that are in the Attic. This solves the problem people are having
where their INDEX* files are being deleted even though they have
them listed in the refuse file. Since the bug is in the server,
mirror sites will need to upgrade their CVSup installation in order
for users to benefit from this fix.
Note: I bumped PORTREVISION from 0 to 2, intentionally skipping 1.
The amd64 version of this port had already bumped it to 1, and I
didn't want to confuse matters by bumping the other architectures to
the same revision number.
Approved by: portmgr (krion)
at this time, even though it is not called a "release". Make the
necessary changes to the cvsup-devel port, which uses the cvsup port
as its MASTERDIR.
I intentionally left "PORTREVISION?=0" in cvsup/Makefile, as a reminder
that this setting needs to be overridable by the cvsup-devel port.
At this moment, the cvsup-devel port builds the same thing as the
cvsup port. That situation probably won't last very long, so I am
leaving the cvsup-devel port in place. It is mentioned in a lot
of documentation, so I don't want to remove it just because it is
temporarily the same as the cvsup port.
so that they match the PORTREVISION value. The PORTREVISION was
mistakenly incremented twice for the same change, because I forgot
it at first, then sobomax incremented it, then I remembered and
incremented it myself.
Except for the version number, there is no functional change in this
commit. Do not bump PORTREVISION for this.
came to the fore in checkout mode when a file "files,v" in the
repository was manually changed into a directory "files".
With this patch, CVSup will still complain that it cannot delete
"files" because the directory is not empty. However, it is now a
warning rather than a fatal error, and the update will run to
completion. The warning will happen only once. After emitting
the warning, CVSup will fix the damage in the checkouts file to
eliminate the problem. On subsequent updates everything will be
OK and no more warnings will occur.
I have bumped PORTREVISION to 1, and added "p1" to the end of the
version number printed by CVSup.
PR: misc/27495
this crash on the client:
***
*** runtime error:
*** ASSERT failed
*** file "/usr/ports/net/cvsup/work/cvsup-16.1/suplib/src/POSIX/FileAttrOS.m3", line 52
***
