Forwarding my message to xubuntu-devel as it's still waiting for
moderation there, and it is relevant to this report.


---------- Forwarded message ----------
From: Andrew SB <email address hidden>
Date: Fri, Sep 11, 2009 at 12:18 AM
Subject: Plans for Exaile 0.3.x in Karmic?
To: <email address hidden>


Hi all,

I'm looking for some clarification on Exaile's status for Karmic.
(see: https://bugs.edge.launchpad.net/ubuntu/+source/exaile/+bug/420019)
Does the Xubuntu team still plan on getting the 0.3.x series into
Karmic? As a sometimes Exaile user and uploader to Ubuntu, I'm willing
to help. I just want to make sure that I'm not duplicating efforts and
that it just isn't simply too late as we have past Feature Freeze and
UI Freeze.

Are you on track for this goal? Has it been defered? Are you confident
that a freeze exception will be granted (any comment Cory as the
Xubuntu motu-release delegate)?

Has there been any contact with the Debian Maintainers about this? I
know upstream has had issues with them in the past, but if our
packaging diverges too much we'll likely run into issues in the
future.

Here's a quick review of the packaging found at
lp:~exaile-packagers/exaile/ubuntu. It's mostly trivial issues.

1) debian/changelog has diverged from the package in Ubuntu.

2) Lintian tells us:
  W: exaile source: debhelper-but-no-misc-depends exaile
  W: exaile source: debhelper-but-no-misc-depends exaile-plugin-moodbar
  W: exaile source: debhelper-but-no-misc-depends exaile-plugin-ipod
  W: exaile source: debhelper-but-no-misc-depends exaile-plugin-contextinfo
  N:
  N:    The source package uses debhelper but it does not use
${misc:Depends} in
  N:    the given binary package's debian/control entry. This is
required so the
  N:    dependencies are set correctly in case the result of a call to any of
  N:    the dh_ commands cause the package to depend on another package.
  N:
  N:    Refer to the debhelper(7) manual page for details.
  N:
  N:    Severity: normal, Certainty: certain

3) Vcs-Bzr field has an improper format.

  It currently is: Vcs-Bzr:
bzr+ssh://bazaar.launchpad.net/~exaile-devel/exaile/0.3.0.x

  It should be: Vcs-Bzr:
https://code.launchpad.net/~exaile-devel/exaile/0.3.0.x

  Although, both the Vcs-Bzr and Vcs-Browser currently point to the
upstream bzr branch.  lp:~exaile-packagers/exaile/ubuntu might be more
appropriate? What is the location of the packaging branch that will be
uploaded to Ubuntu?

4) There is no debian/watch file.

5) debian/control: Standards-Version should be 3.8.3

6) There is a patch using quilt, but there is no build-depends on
quilt. Quilt also isn't included in debian/rules. Is this patch even
needed/used?

7) debian/control: Unnessesary Uploaders field with "Uploaders: NAME <EMAIL>"

8) debian/copyright points to the versionless symlink at
usr/share/common-licenses/GPL when it should use the exact version.

9) debian/menu uses /usr/share/pixmaps/exaile.png This doesn't effect
Ubuntu, but icons in the Debian menu system should be in XPM format.

As this is essentially a complete repackaging, has there been any
testing of the dist-upgrade from the Jaunty version?

I'd be happy to work on this / provide a patch / sponsor an upload /
upload myself. Please let me know your current plan, and how I can
help.

Thanks!

 - Andrew Starr-Bochicchio
  Ubuntu MOTU Developer

P.S. Please CC me in replies as I'm not subscribed to this list.