Bug#736885: RFS: gdal/1.10.1+dfsg-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/28/2014 12:01 AM, Sebastian Ramacher wrote:
> On 2014-01-27 23:34:25, Bas Couwenberg wrote:
>> Package: sponsorship-requests Severity: normal
>>
>> Dear mentors,
>>
>> I am looking for a sponsor for my package "gdal"
>>
>> [...]
>>
>> Changes since the last upload:
>>
>> * Rebuild for libepsilon1.
>
> gdal is currently involved in the ongoing poppler transition. To
> not entangle the poppler and libepsilon transition, please talk to
> the Release Team and wait for their OK. (I don't know how many
> packages are involved in the libepsilon transition, but you might
> want to read [1] on how to coordinate transitions with the Release
> Team.)
GDAL is already marked 'good' in the poppler transition, that doesn't
seem to be a problem. The openjpeg transition in which it's include
via poppler may be.
Since only gdal and librasterlite need to be rebuild for the new
libepsilon skipping the release team was not protested. See:
https://lists.debian.org/debian-gis/2014/01/msg00054.html
> But anyway, this upload is not required. Once the new libepsilon
> got built and installed everywhere, it is enough to request
> binNMUs. reportbug release.debian.org has a template for that.
Andreas, should we go this route instead?
Kind Regards,
Bas
- --
GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCgAGBQJS5unHAAoJEGdQ8QrojUrxixoP/AqoV2br/jAhbYYnUAOzwiYw
lgelFntsNGWQZ0o+xCgOwdk8enTiMNWB00je+PCqZ+v+KhXJOHZo1juR9+5GCNqb
XDGvbbqPXVdR1O79mTcaH27JlVprGM6sjN2Uy0LDf73PrtfBFHgqoCIA/poe9UPb
0CWPz+eH+Vu/hPf5nC6zbGU1tyuEnOBXoD94HTKWs8tRg1EP0pymPtu5DRIRisMP
YuHSg4ASPQKKcMbNzUgI1cLyd/LVyDBhNamAMz1j7MqxdQSWSpg9M1LfPAn2lZEn
9dSOKPllBPL51bBKtGp5kih4/MGWWveBzfEZ4eCujUHWV1M3856FHXs0x5LK2LLh
YsuQuyZo6JEVETxVHsSwvu1Ecib2cLU9mJ9AspePRD/S+8PnYQmgR8tyFuOQXsR+
JlyEq8vFM61Ovs/p/OE1OH5Iggtj/uAGn+9P1Qd/UIgjRxCnT4ZojIzqKrgibSsu
itGb7Pj5s/B/XkjkH6jMB8eSLeGFc/kb6y75rQzvqjUeOGBYJLuTIQlMV2rQMnyi
+WWQrx4coGqCBPkEkgc6zg2VQAtxNo6WCXyQlzFD86n/RMlQTuOg0QqPqtG/9LzW
9Q7PWnQLhsw98u4hbbmIPglzo2kpNZYSNn5Nhe1i/NINGIkARhxm+pbv2IPGmmCY
fkGYwq9Ja8te2maytzLD
=HbSZ
-----END PGP SIGNATURE-----
Reply to: