Comment 3 for bug 1537461

On Mon, 02 Oct 2017 11:44:41 -0400
"Maik Wagner" <email address hidden> wrote:

> I am very glad that somebody is looking at maintaining this package.
> Are you looking to primarily support Ubuntu or Debian.

   I'm primaraly a packager for Debian but keep in mind that is traditionally via Debian that applications and updates to those applications are done. OTOH; if I were not interested in the status of SQL-Ledger in Ubuntu, I would not have been reviewing the bugs present for it there.

> As upstream (DWS Systems) doesn't have its own github.com or other
> source code repository

   There not being a public repository for upstream is definitely an issue.

> would it be possible to unpack the upstream
> tarball in launchpad.net and apply the missing files there?

   There is the Debian packaging repository, currently at:
https://anonscm.debian.org/gitweb/?p=collab-maint/sql-ledger.git.

   That will be changing at some point, possibly, due to infrastructure changes at Debian.
   There is also this packaging repository at GitHub, mirrored from the Debian one, where there is
   a branch for packaging v3.2.5:
https://github.com/rocasa/pkg-sql-ledger

   And regarding the missing sourse files issue itself; other applications use something like that same file, so need to see how they handle it.

> If you are interested I completed some language packs for this
> application as well and I quite enjoy using SQL Ledger.

   Shouldn't something like that be sent to upstream?

> Would you mind sharing how to reproduce these bugs?

   You mean, those lintian errors? A minimal command line for that is as follows (where my system
is set to automatically run Lintian after the build and also includes an apropriate '-e" option): debuild -rfakeroot -us -uc
   That, of course, is on an extracted sql-ledger archive with an apropriate debian/ directory.