[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#717000: RFS: libpar2/0.3.1-1



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libpar2"

* Package name    : libpar2
  Version         : 0.3.1-1
  Upstream Author : Peter Brian Clements, Francois Lesueur, Andreas Moog
* URL             : launchpad.net/libpar2
* License         : GPL-2+
  Section         : libs

It builds those binary packages:

libpar2-0  - Library for performing common tasks related to PAR
recovery sets
libpar2-0-dbg - Debugging symbols for the libpar2-0 library
libpar2-0-dev - Headers for the libpar2-0 library

The package is NOT lintian clean:

I: libpar2-0: no-symbols-control-file
usr/lib/x86_64-linux-gnu/libpar2.so.0.0.1

I chose to ignore that because in this case, maintaining a symbols
file for the different architectures is much effort for very little gains.

To access further information about this package, please visit the
following URL:

http://mentors.debian.net/package/libpar2

Alternatively, one can download the package with dget using this command:

dget -x
http://mentors.debian.net/debian/pool/main/libp/libpar2/libpar2_0.3.1-1.dsc

Changes since the last upload:

libpar2 (0.3.1-1) unstable; urgency=low

  * New Upstream Release:
    - Adds cancel support (Closes: #701904)
  * debian/combat: Use dh combat level 9
  * debian/control:
    - Standards version is 3.9.4
    - Use correct Vcs-* fields
  * debian/copyright: Update format field and copyright information
  * debian/*.install, debian/control: Convert library to multi-arch
  * debian/watch: Fix watchfile

- -- Andreas Moog <amoog@ubuntu.com>  Sun, 14 Jul 2013 13:11:20 +0200

Regards,
   Andreas Moog
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJR5F/xAAoJEGHzRCZ03mYkzY4QAJawlFat+gic/GoltNjx+wFi
W9dc2ZBQWuuC7nkT5+dIz+6JCL3Dyb/kKcLLfUQHBHfwf6uIfSZVYPRP/+hJBo7F
paeFcYLDWp2HIj6/JMqSxbsx4azDIZ0GcOokx8/dDk65DRhHkjW1Wd6I5eApbnL8
HOG1pYqbw7OY0LCXJB/JEUH4Ip4nZXCraHHdC0scKViLV6xBjy39Ovc0vxA/TLtQ
c5gVoQiptyqYO2ayTGn9n3+8alzh0AVuNCjKO/NFhGyvff+gK6pvwVIp132b/2Ex
kLjONFsDqPW2PXzbouGCoAmNXEdWSjhYhQA9x5eZUtMirOYa8KeDzepcEYeizU1q
HBJTiCMzyStJU6dN0ewd8ZY9hdz1/hprU/xMCVkFIQeGaoPa02wXGtKkLulKdvoB
/xPp42Qa6w/5XR5BxxY9pj6tg1k9SdPUHuozMLxO++uHcV7OvwhEUGH6GTEcetyy
TP4oE2QMOCOyZydfammj2xzFDtf4WcK9VMFsZoQHu3DcapV6ii3CuO2EvWXe6cGt
PA8sja3rYc8H/OkxmJv4FzZLaGydb7chhUy1huux1wDrzv/Q8mCZakyikjdiSNpk
xyNqLRemVdh0WuBQSNOnAQkT1+Y+dh0wOBYF/pjKICiVf26FrvQ1R25FLs2lvn5Z
MsYK6LYkZEWaWlOfuBjm
=RrMb
-----END PGP SIGNATURE-----


Reply to: