Hey Andrew,
Thanks for your effort to review our wonderful package. As you could see we
really aren't experts on Debian packaging (but the debian/rules do work
since the packages build ^_^). Just before I get into the details, feel free
to join #exaile or #xubuntu-devel anytime to discuss this with us (i'm SiDi
on freenode).

2009/9/12 Andrew Starr-Bochicchio <email address hidden>

> Forwarding my message to xubuntu-devel as it's still waiting for
> moderation there, and it is relevant to this report.
>
>
> 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.
>

It of course would have been much easier to justify the upcoming 0.3.0.2
release if I had managed to properly package 0.3.0 and 0.3.0.1 before the
Feature and UI Freezes :] There is no duplicate effort as the official
maintainer have vanished and noone is working on Exaile in debian / ubuntu.

>
> 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)?
>

I think Cory told me he would allow the FF exception for Exaile. Given the
shape of the Exaile 0.2 package and the longstanding bugs in it, I think it
is more than welcome.

>
> 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.
>

I have directly pinged him on Freenode and had no answer. Exaile 0.3.0 was
released a few weeks ago, and has been immediately packaged by our gentoo /
arch packagers who keep in touch with us on #exaile and who are subscribed
to our RSS release feed. We also advertised the release on Identi.ca and
mentioned a coming release in the Ubuntu planet.

>
> 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.


I indeed removed some names in the Maintainer line, since there is no
maintainer anymore. This may have been an error from me.

>


> 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
>

We really didn't know about that. :/ I didn't know debhelper either :)

>
> 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


This is a bad typo from me, sorry

>
>
>   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?
>

We used this branch to have the code somewhere, but if you intend to
maintain Exaile then we can invite you in the group and it can be used as
the official branch for the ubuntu package.

>
> 4) There is no debian/watch file.
>

I am not sure how to find a proper URL pattern for the tarballs with
launchpad, and the link on the exaile site just points to it and is manually
updated.

>
> 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?
>

I didn't notice that patch. As far as I know, the only patch is the one
fixing the makefile in 0.3.0 and it can be dropped for 0.3.0.1. What patch
is that ?

>
> 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.
>
>
I will ask the Exaile artwork designer for the XPM icon. Is there a
preferred size ?

> 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.
>

Exaile 0.3.0.1 is out, I plan to finish 0.3.0.2 this week-end, if you can
catch me on IRC we can fix the bits that are wrong in the code and packaging
branch. Thanks for your work on Exaile.

>
> Thanks!
>
>  - Andrew Starr-Bochicchio
>   Ubuntu MOTU Developer
>
> P.S. Please CC me in replies as I'm not subscribed to this list.
>
> --
> New upstream version: 0.3
> https://bugs.launchpad.net/bugs/420019
> You received this bug notification because you are a direct subscriber
> of the bug.
>



-- 
Steve Dodier
OpenPGP : 1B6B1670
IRC : SiDi on irc.freenode.net
Jabber : <email address hidden>
<email address hidden>
https://launchpad.net/~sidi