Source: imediff2
Version: 1.1.2-3
Severity: minor

As I read carefully this source to fix #799865, I saw several
irregularities.

If you try to update manpage by editing imediff2-docbook.xml, the
generated imediff2.1 by the "make" invocation does not yield properly
formatted manpage:

| $ make imediff2.1
| xsltproc --novalid 
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl 
imediff2-docbook.xml
| Note: meta source : no *info/productname or alternative            imediff2
| Note: meta source : see http://docbook.sf.net/el/productname       imediff2
| Note: meta source : no refentry/refmeta/refmiscinfo@class=source   imediff2
| Note: meta source : see http://docbook.sf.net/el/refmiscinfo       imediff2
| Note: meta version: no *info/productnumber or alternative          imediff2
| Note: meta version: see http://docbook.sf.net/el/productnumber     imediff2
| Note: meta version: no refentry/refmeta/refmiscinfo@class=version  imediff2
| Note: meta version: see http://docbook.sf.net/el/refmiscinfo       imediff2
| Warn: meta source : no fallback for source, so inserted a fixme    imediff2
| Note: meta manual : no titled ancestor of refentry                 imediff2
| Note: meta manual : no refentry/refmeta/refmiscinfo@class=manual   imediff2
| Note: meta manual : see http://docbook.sf.net/el/refmiscinfo       imediff2
| Warn: meta manual : no fallback for manual, so inserted a fixme    imediff2
| Warn: AUTHOR sect.: no personblurb|contrib for Jarno Elonen        imediff2
| Note: AUTHOR sect.: see http://docbook.sf.net/el/contrib           imediff2
| Note: AUTHOR sect.: see http://docbook.sf.net/el/personblurb       imediff2
| Note: Writing imediff2.1

Of course manual edit of imediff2.1 is one way for the work around, this
is not a nice situation.

Also, this source has "VERSION = '1.1.1'" in the imediff2 command
causing "imediff2 --version" while the upstream version of package is
imediff2 1.1.2 (2007-08-18 00:48)

This package list python-setuptools as Build-Depends, but I see no
setup.py in the upstream source?  Why?

I see 2 upstream BTS patch proposals, but no responses can be seen.
https://alioth.debian.org/tracker/index.php?func=detail&aid=302985&group_id=30544&atid=411376
https://alioth.debian.org/tracker/index.php?func=detail&aid=305136&group_id=30544&atid=411376

The SVN repo seems not used at all.  The last commit is before the last
tarball release

https://anonscm.debian.org/viewvc/imediff2/debian/changelog?sortby=date&sortdir=down&view=log
Revision 22 - (view) (download) (annotate) - [select for diffs] 
Modified Sat Dec 23 14:19:05 2006 UTC (10 years, 3 months ago) by elonen

I wonder if it may be beneficial to start alioth collab-maint git
repository (or github if you like that) so fixing these issues as
upstream fix becomes more natural.

Who exactly is the upstream now? Jarno Elonen? Kevin Coyner?

Is there any better program out there which made the upstream loosing
interest?

I have been using this but wondering the situation... for how to contact
the upstream.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (98, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.10.0-rc6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Reply via email to