Hi,

As explained at <http://bugs.debian.org/693537>, xzless depended on
the format of the first line of "less -V" output and the modern
version string "less 456 (GNU regular expressions)" confuses it.

That's entirely my fault and pretty broken behavior by xzless, but
it's possible xzless is not the only affected package.  I wonder:

 * is this effect of revealing bugs in scripts that parsed the version
   line intentional, and is it worth it?

 * would it make sense to add a

	Breaks: xz-utils (<< 5.1.1alpha+20120614-2+)

   to smooth the upgrade path?

 * any idea how one would go about finding other affected packages
   if they exist?

BTW, thanks for the pleasant and up-to-date "less" package that makes
it possible to notice this pretty early.

Sincerely,
Jonathan

I'm not sure about that.
can test less 456-2.

sudo dpkg -i less_456-2_amd64.deb
dpkg: regarding less_456-2_amd64.deb containing less:
 less breaks xz-utils (<< 5.1.1alpha+20120614-2+)
  xz-utils (version 5.1.1alpha+20120614-2) is present and installed.

dpkg: error processing less_456-2_amd64.deb (--install):
 installing less would break xz-utils, and
 deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
 less_456-2_amd64.deb

I have no idea.

Thank you. :)

I'm not sure about that.
can test less 456-2.

sudo dpkg -i less_456-2_amd64.deb
dpkg: regarding less_456-2_amd64.deb containing less:
 less breaks xz-utils (<< 5.1.1alpha+20120614-2+)
  xz-utils (version 5.1.1alpha+20120614-2) is present and installed.

dpkg: error processing less_456-2_amd64.deb (--install):
 installing less would break xz-utils, and
 deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
 less_456-2_amd64.deb

I have no idea.

Thank you. :)