One noob, 3 orphan source packages, 14 .deb, looking for a sponsor

["Thomas Schmitt" <scdbackup@gmx.net>]

Hi,

assumed i can build Debian package files of three existing
orphaned Debian packages with current upstream release on
Debian 8.1 - where to ask the following questions:

- What more do i have to set up for making them ready
  for submission to a sponsor ? Sid ?

- Is an experienced packager around who could do a
  (one-time) review of my .debian.tar.xz before i bother
  busy people with upload permission ?

- How do i express that libisoburn source is licensed GPL-2
  or later but the xorriso binary becomes licensed GPL-3
  or later by linking it with libreadline ?

----------------------------------------------------------
What i did so far (with more curves than needed, i guess):

After reading
  https://debian-handbook.info/browse/stable/debian-packaging.html

i fetched the Debian source and ran dch

  apt-get source libburn4
  cd libburn-1.3.2
  dch

to prepend to debian/changelog:

  libburn (1.4.0-1) unstable; urgency=low

    * Non-maintainer upload.
    * New upstream release
      ...
    * Removed dependency on doxygen

   -- Thomas Schmitt <scdbackup@gmx.net>  Tue, 18 Aug 2015 11:25:43 +0200

This earned me

  dch warning: your current directory has been renamed to:
  ../libburn-1.4.0
  dch warning: no orig tarball found for the new version.

So i renamed libburn-1.4.0, unpacked upstream libburn-1.4.0.tar.gz,
moved ./debian from the renamed Debian source tree to it, and put
a copy of the upstream tarball as

  ../libburn_1.4.0.orig.tar.gz

above this self-made libburn-1.4.0 directory.

Then i went through the files in libburn-1.4.0/debian trying
to understand and to adapt them to the new release.
Since doxygen is a potential source of trouble, i removed
it from debian/control and debian/rules.

Then i ran

  dpkg-buildpackage -us -uc

Now i have

  -rw-r--r-- 1 * *    1332 Aug 18 14:01 libburn_1.4.0-1.dsc
  -rw-r--r-- 1 * *    5620 Aug 18 14:01 libburn_1.4.0-1.debian.tar.xz
  -rw-r--r-- 1 * *  970395 Aug 18 14:01 libburn_1.4.0.orig.tar.gz

  -rw-r--r-- 1 * *    3582 Aug 18 14:02 libburn_1.4.0-1_amd64.changes

  -rw-r--r-- 1 * *  140244 Aug 18 14:02 libburn-doc_1.4.0-1_all.deb
  -rw-r--r-- 1 * *  204788 Aug 18 14:02 libburn-dev_1.4.0-1_amd64.deb
  -rw-r--r-- 1 * *  251520 Aug 18 14:02 libburn-dbg_1.4.0-1_amd64.deb
  -rw-r--r-- 1 * *  117598 Aug 18 14:02 cdrskin_1.4.0-1_amd64.deb
  -rw-r--r-- 1 * *  149800 Aug 18 14:02 libburn4_1.4.0-1_amd64.deb

Other than the downloaded .dsc, my new one is not PGP signed.
(Who signs ? Sponsor or sponsee ?)

As superuser i ran

  dpkg -i libburn4_1.4.0-1_amd64.deb
  dpkg -i cdrskin_1.4.0-1_amd64.deb

A run of cdrskin -version says it is 1.4.0 on libburn-1.4.0.
A run of cdrskin --devices shows my drives.

Similar i did with libisofs_1.3.2-1.1 and libisoburn_1.3.2-1.1.
Installation:

  dpkg -i libisofs6_1.4.0-1_amd64.deb

A run of xorriso-1.3.2 -version shows that it uses libisofs-1.4.0
and libburn-1.4.0.

The precondition to build the libisoburn packages was

  apt-get install libreadline-dev
  dpkg -i libburn-dev_1.4.0-1_amd64.deb
  dpkg -i libisofs-dev_1.4.0-1_amd64.deb

After dpkg-buildpackage -us -uc in libisoburn-1.4.0 :

  dpkg -i libisoburn1_1.4.0-1_amd64.deb

Yields interesting version mix in xorriso. main believes it
is 1.3.2, the whole implementation knows it is 1.4.0.
I let main be 1.4.0, too, by:

  dpkg -i xorriso_1.4.0-1_amd64.deb

xorriso -version and xorriso -devices work as expected.
xfburn-0.5.2 starts up, at least.

Ultimate trust test: My own early evening backup script ...
my work backs up itself. Today it's 100 MB more than usual.

----------------------------------------------------------


Have a nice day :)

Thomas