On 09/02/2012, Brett <brett.ma...@gmx.com> wrote: >> > Somehow patch-apps_unix_ximage_c has gotten in there, even though >> > (according to >> > http://www.openbsd.org/cgi-bin/cvsweb/ports/textproc/mupdf/patches/Attic/ >> > ) it was moved to the attic over 2 years ago. >> >> $ cvs status patch-apps_unix_ximage_c >> >> see if there is sticky tag there. If so, then do: >> >> $ cvs up -dPA >> >> --patrick >> > > # cvs -d/usr/cvsync status > /usr/ports/textproc/mupdf/patches/patch-apps_unix_ximage_c > =================================================================== > File: patch-apps_unix_ximage_c Status: Up-to-date > > Working revision: 1.1 Fri Feb 10 00:17:20 2012 > Repository revision: 1.1 > /usr/cvsync/ports/textproc/mupdf/patches/patch-apps_unix_ximage_c,v > Sticky Tag: (none) > Sticky Date: (none) > Sticky Options: (none) > > I ran the $ cvs up -dPA command anyway but patch-apps_unix_ximage_c did not > return to the attic. > > The hostname in my cvsync config file is cvsync.allbsd.org if that would > make any difference. > > Brett.
Looks like cvsync.allbsd.org is in trouble -- patch-apps_unix_ximage_c is present both outside Attic at rev1.1, and within Attic at rev1.2. http://cvsweb.allbsd.org/cvsweb.cgi/ports/textproc/mupdf/patches/?cvsroot=openbsd http://www.openbsd.org/cgi-bin/cvsweb/ports/textproc/mupdf/patches/ Perhaps Hiroki can clarify how this could have happened. C.
