Log message:
x11/xlockmore-lite: Update to 5.77

See base package x11/xlockmore for changelog.

Log message:
x11/xlockmore-lite: Update to 5.68

See base package x11/xlockmore for changelog.

Log message:
xlockmore{,-lite}: restore CONFLICTS.

Log message:
Update of xlockmore and xlockmore-lite to the latest version.

Upstream changelog:

xlockmore-5.46 as of 10 March 2015, the maintained version of xlock

5.46
  xmb fonts messing up password screen since ascent was not being set
    correctly.  Also fixed xjack mode.
  Updated language use in xlock.c, now removed to .h files.  If I made some
    bad assumption about the language... let me know.
  BSD install fixes (DESTDIR, FreeType2, fortune) and switching to xz.
  Cygwin install fixes (cygport, xlockrc).

5.45
  A bad value of fnt for pyro2 could cause to give an X error.  Fixed to
    not free memory we are using and have a better default.

5.44
  Fix for make_one_sided_pentomino was using 18 as basis for 2 sided
    pentominoes in loop.  Found out about it by gcc 4.8.1 warning: iteration
    12u invokes undefined behavior [-Waggressive-loop-optimizations].
  dilemma, voters, wator size fix for neighbors = 6.
  Proper crediting of Nathan Thompson for discovering High Life part of
    life mode.
  A few new gliders and patterns for life and life3d.
  Updated win32 to use updated cygwin.  Currently links are only satisfied
    using cygwin using 32-bit installation.  For me, cross compiling using
    64-bit gave undefined references in visgl.c and xlock.c.
  magick.c update for version 7, thanks to Jouk Jansen.

5.43
  life3d: added new rule B58S58, which has a replicator.
  -e added to shell in Makefile.in, told it should now stop on build errors,
    rather than trying to continue which could be confusing.  Thanks to
    Glyn Kennington <glyn AT potatojunkie.co.uk>.
  If crypt fails (which is possible with glibc2.17) it could cause xlock to
    get a signal 11.  There is now protection around the strcmp() to prevent
    NULL poiter dereferences thanks to Mancha <mancha1 AT hush.com>.

5.42
  USE_MB now defined by default. If this is not defined it can only
    correctly display ASCII.  There could be font issues which may
    lead one to want only ASCII (if so use configure --disable_mb).
    Also looked into Xutf8 but did not see any benefit this had over Xmb.
    Password window and the following modes: bomb,dclock,image,marquee,nose
    are affected.  Fixed a few problems with marquee for width, height, and
    if a character needs more than 2 bytes.
  In Cygwin a seemingly unrelated fix where USE_MB gets defined in xlock.h.
    An #undef was added in xlock.h, if USE_MB gets defined in an internal
    include file.
  -lcrypt added to modes/Makefile.in.  This is needed on my Linux Ubuntu
    and seems ok on Cygwin where it was not needed.  (If this causes a
    problem remove from modes/Makefile).  Also tested on FreeBSD.
  cppcheck fixes
    passwd.c: passcpy could be freed twice
    iostuff.c: could have left file open
    ras.c: leak if mem fails
    resource.c: check if malloc succeeded was in wrong spot
    sound.c: ESound, a redundant check
    memcheck.c: continuing after memory failure
    dclock: problem with parens in ifdefs
    rain: leak fix ( :) )
    t3d: uninitialized time1 (unlikely but fixed anyway)
    molecule: leak if mem fails
    text3d: leak if nothing to draw

Log message:
Fix a bug in the last commit, where the resource file was read out of the
examples directory.

Log message:
Treat the app-defaults/XLock as a configuration file, thus enabling
administrators of multi-user machines to have a site-specific default
configuration and not lose it on updates of the package.

Log message:
5.41 - includes the dclock patch.

Log message:
A missed case of last problem.... dclock -veg and dclock -lab.

Log message:
xlock -mode dclock would segfault on OSes with sizeof(time_t)>sizeof(long);
this includes NetBSD-6 on 32bit systems.

As a result, xlock -mode random (the default) would eventually unlock
the screen, without the user being aware of this (as she/he's can be
presumed to have left the monitor).

The reason was that some variables in dclock.c were declared long, but
contain essentially time_t values. In on case, a pointer to such a
variable was casted to (struct time_t *) and passed to localtime(),
and the resulting pointer is not checked for error before being used.

The variables have been changed to time_t and the typecast has been
removed.

Log message:
Whitespace. (as whined about by pkglint)