Please remove libmpc from the sync blacklist

[Hans Joachim Desserud]

I came across this package, wondering why Debian has a newer version which didn't seem to automatically sync in Artful. After some digging, I discovered that the package had been blacklisted [1] and thus prevented from syncing. Originally done because the binary packages provided were also offered by a different package libmpcdec (bug 540019).

However, I did some more digging and found that libmpcdec had been removed shortly after [2]. With this other package gone, I wonder if there is still reasons to keep libmpc in the blacklist or whether it could be synced to the latest version available in Debian?

[1] http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt
[2] https://launchpad.net/ubuntu/+source/libmpcdec/+publishinghistory

Please sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main)

Changelog entries since current artful version 2:0.1~r459-4.1build1:

libmpc (2:0.1~r495-1) unstable; urgency=medium

  * Team upload.
  * New upstream release. (Closes: #837096)
  * debian/rules: Add get-orig-source target to fetch newer upstream
    snapshots.
  * debian/patches:
    - 02_link-libm.patch, 1001_missing_extern_kw.patch: Removed, included
      upstream.
    - 03_mpcchap.patch: Refreshed and fixed use of cue_parse_file.

 -- Sebastian Ramacher <email address hidden> Mon, 12 Sep 2016 20:34:33 +0200

libmpc (2:0.1~r475-2) unstable; urgency=medium

  * Team upload.
  * Drop all DEB_AUTO_UPDATE_* stuff and use dh-autoreconf exclusively to fix
    FTBFS. (Closes: #816529)
  * Update Vcs fields.
  * Bump standards to 3.9.8.

 -- James Cowgill <email address hidden> Wed, 31 Aug 2016 21:16:41 +0100

libmpc (2:0.1~r475-1) unstable; urgency=medium

  * New upstream release:
    - Contains a minor API change of removing some enum values that
      are not used anywhere in Debian.
  * debian/patches/05_visibility.patch:
    - Minor build system fix to declare HAVE_VISIBILITY.

 -- Sebastian Dröge <email address hidden> Sat, 19 Sep 2015 20:59:38 +0200

[Mattia Rizzolo (mapreri)]

You need to get this unblacklisted from syncing, otherwise we'd be at the same situation as before right after the next debian upload.
Besides this package is not diverged from debian, so after unblacklisting no actions should be needed.

~ubuntu-archive is subscribed, but IME it works better if somebody go nags in #ubuntu-release (note: I haven't reviewed this case at all myself).

[Adam Conrad (adconrad)]

Unblacklisted and synced back to a current version.