Please merge exaile (0.2.11.1+debian-1) from Debian unstable

[Andrew Starr-Bochicchio]

Binary package hint: exaile

 exaile (0.2.11.1+debian-1) unstable; urgency=low

   * New upstream release (Closes: #451549):
     - New desktop file (Closes: #444438),
     - Cover art can now be disabled (Closes: #444227).
   * Drop "432164" patch, fixed upstream.
   * Drop 01_fix_makefile_for_pysupport patch, new workaround added.
   * Bump Standards-Version to 3.7.3.
   * Move homepage to new dpkg standard field.
   * Update debian/menu to new policy.
   * Drop dpatch bdep, not used anymore.

 -- Adam Cécile (Le_Vert) <email address hidden> Mon, 25 Feb 2008 22:52:14 +0100

[Wouter Stomp (wouterstomp-deactivatedaccount)]

Even better would be to have the newest verion, 0.2.13:

"Today, April 1 2008, Amazon discontinued their ECS version 3.0 in favor of 4.0. This caused album art to stop being collected correctly. Exaile 0.2.13 is an emergency release aimed to fix this problem."

[Andrew Starr-Bochicchio (andrewsomething)]

exaile (0.2.11.1+debian-1ubuntu1) intrepid; urgency=low

  * Merge from debian unstable, remaining changes:
   - debian/control
    + Build-Dep on dpatch needed for patches
    + Added a Recommends on gstreamer0.10-plugins-bad,
        needed by exaile's equaliser to work.
    + Added XS/XB-Python-Version
   - debian/patches:
    + 02_files-on-share-dir, added to adjust the Makefile to point
        to the right policy installation dir on /usr/share/pkg.
    + 03_fix_mmkeys.dpatch, added to get Multimedia Keys working
   - debian/rules:
    + Added a link between /usr/lib/exaile/exaile.py and
      /usr/share/exaile/exaile.py preventing an error while starting
      exaile up.
    + Make burn.py and cd_import.py executables
   - Removed:
    + debian/README.Debian-source (orig tarball not repackaged)
    + debian/pyversions
   - debian/docs: Removed README.Debian-source

 -- Andrew Starr-Bochicchio <email address hidden> Thu, 01 May 2008 03:23:03 +0100

[Andrew Starr-Bochicchio (andrewsomething)]

Close bug in changelog

[Andrew Starr-Bochicchio (andrewsomething)]

The new release should definitely get into Ubuntu, but we still need to merge the Debian package.

[Andrew Starr-Bochicchio (andrewsomething)]

putting back to in progress and unsubscribing U-U-S. dpatch 02_files-on-share-dir doesn't seem to apply correctly. I'm going to have to take a second look.

[Emilio Pozuelo Monfort (pochu)]

Unsubscribing u-u-s, please subscribe the team back when you're done with the new upstream release.

[Andrew Starr-Bochicchio (andrewsomething)]

Correct merge. Tweaked 02_files-on-share-dir.dpatch inorder to apply correctly.

[Andrew Starr-Bochicchio (andrewsomething)]

Deleted so there is no confusion.

Emilio,

What should be the work flow on the new release? Should I get the merge uploaded first and than do the new release or should I go ahead and put together a package that includes both the Debian merge and the upstream release?

[Andrew Starr-Bochicchio (andrewsomething)]

Er... That should read: Deleted old debdiffs so there is no confusion.

(Sorry for the bug spam)

[Andrew Starr-Bochicchio (andrewsomething)]

Here is a debdiff between the current Ubuntu version and 0.2.13 including the Debian merge.

[Emilio Pozuelo Monfort (pochu)]

Andrew, could you please attach your diff.gz? Thanks

[Emilio Pozuelo Monfort (pochu)]

Andrew:

Upstream ships a debian/ folder, which means we need to repackage the tarball, which is a shame. I've seen they are making packages in their PPA, https://launchpad.net/~exaile-devel/+archive, but they are doing the package as a native package. If we can convince them to switch to a non-native package, their debian/ folder would be in the diff.gz (as ours is) and we could use directly their tarball without repackaging.

Could you try to convince them to do that for the next releases? You could mail their mailing list (http://groups.google.com/group/exaile-devel) or use the bug tracker (launchpad.net/exaile).
Also, could you forward them the manpage from debian/exaile.1?

Thanks!

[Launchpad Janitor (janitor)]

This bug was fixed in the package exaile - 0.2.13-0ubuntu1

---------------
exaile (0.2.13-0ubuntu1) intrepid; urgency=low

  * New upstream release. LP: #209411
  * Removed: debian/docs
  * debian/patches
   - Dropped 03_fix_mmkeys.dpatch Fixed upstream.

  * Merge from debian unstable (LP: #227961), remaining changes:
   - debian/control
    + Build-Dep on dpatch needed for patches
    + Added a Recommends on gstreamer0.10-plugins-bad,
      needed by exaile's equaliser to work.
    + Added XS/XB-Python-Version
   - debian/patches:
    + 02_files-on-share-dir, added to adjust the Makefile to point
      to the right policy installation dir on /usr/share/pkg.
    + 03_fix_mmkeys.dpatch, added to get Multimedia Keys working
   - debian/rules:
    + Added a link between /usr/lib/exaile/exaile.py and
      /usr/share/exaile/exaile.py preventing an error while starting
      exaile up.
    + Make burn.py and cd_import.py executables
   - Removed:
    + debian/README.Debian-source (orig tarball not repackaged)
    + debian/pyversions
   - debian/docs: Removed README.Debian-source
  * debian/patches/02_files-on-share-dir
   - Tweaked inorder to apply cleanly.

 -- Andrew Starr-Bochicchio <email address hidden> Sat, 10 May 2008 16:07:16 -0400

[Emilio Pozuelo Monfort (pochu)]

Bah, in fact we don't need to repackage, I was confused. But it would still be nice if upstream didn't ship a debian/ dir.

[Andrew Starr-Bochicchio (andrewsomething)]

We got a problem here. It's FTBFS. python-gtk2-dev seems to be broken...

http://launchpadlibrarian.net/14460975/buildlog_ubuntu-intrepid-i386.exaile_0.2.13-0ubuntu1_FAILEDTOBUILD.txt.gz

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  python-gtk2-dev: Depends: python-gobject-dev (>= 2.14) but it is not going to be installed
                   Depends: python-gtk2 (>= 2.12.1-0ubuntu1) but it is not going to be installed
E: Broken packages
apt-get failed.
Package installation failed
Trying to reinstall removed packages:
Trying to uninstall newly installed packages:
Source-dependencies not satisfied; skipping exaile

[Emilio Pozuelo Monfort (pochu)]

Andrew Starr-Bochicchio wrote:
> We got a problem here. It's FTBFS. python-gtk2-dev seems to be
> broken...

Yes, it's currently uninstallable, I think it's due to a libffi problem but
haven't checked it yet. I'll request a retry when it's fixed, so don't worry.

[Emilio Pozuelo Monfort (pochu)]

Emilio Pozuelo Monfort wrote:
> Yes, it's currently uninstallable, I think it's due to a libffi problem but
> haven't checked it yet. I'll request a retry when it's fixed, so don't worry.

Retry requested, let me know if it fails to build again.

[Andrew Starr-Bochicchio (andrewsomething)]

Still fails....

The following packages have unmet dependencies:
  python-gtk2-dev: Depends: python-gobject-dev (>= 2.14) but it is not going to be installed
                   Depends: python-gtk2 (>= 2.12.1-0ubuntu1) but it is not going to be installed
E: Broken packages
apt-get failed.
Package installation failed
Trying to reinstall removed packages:
Trying to uninstall newly installed packages:
Source-dependencies not satisfied; skipping exaile
******************************************************************************
Finished at 20080515-1319

[Emilio Pozuelo Monfort (pochu)]

Andrew Starr-Bochicchio wrote:
> Still fails....

python-gobject fixed binaries weren't available yet so it failed. They are
available now, retries have been rescheduled and it's being built now!

Cheers