Please backport liberasurecode-1.1.0, python-pyeclib-1.1.1 to precise, trusty, vivid

Bug #1515710 reported by Tushar Gohad on 2015-11-12
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Precise Backports
Undecided
Unassigned
trusty-backports
Undecided
Unassigned
vivid-backports
Undecided
Unassigned

Bug Description

Please help with a relatively simple backport of:

http://packages.ubuntu.com/xenial/liberasurecode1 (1.1.0-2)
http://packages.ubuntu.com/xenial/liberasurecode-dev (1.1.0-2)

from Xenial.

Also, please sync python-pyeclib to Xenial:

https://packages.debian.org/sid/python-pyeclib (1.1.1-1)

and backport to Trusty.

Tushar Gohad (tsg-) on 2015-11-12
summary: - [FFE] Backport liberasurecode-1.1.0, python-pyeclib-1.1.1 to Ubuntu
- 14.04 LTS
+ Backport liberasurecode-1.1.0, python-pyeclib-1.1.1 to Ubuntu 14.04 LTS
Tushar Gohad (tsg-) on 2015-11-12
no longer affects: liberasurecode (Ubuntu)
description: updated
summary: - Backport liberasurecode-1.1.0, python-pyeclib-1.1.1 to Ubuntu 14.04 LTS
+ Please backport liberasurecode-1.1.0, python-pyeclib-1.1.1 to trusty

Verified that the xenial liberasurecode1 and liberasurecode-dev packages work well on trusty:

http://packages.ubuntu.com/xenial/liberasurecode1 (1.1.0-2)
http://packages.ubuntu.com/xenial/liberasurecode-dev (1.1.0-2)

description: updated
Tushar Gohad (tsg-) on 2015-11-18
no longer affects: swift
summary: - Please backport liberasurecode-1.1.0, python-pyeclib-1.1.1 to trusty
+ Please backport liberasurecode-1.1.0, python-pyeclib-1.1.1 to precise,
+ trusty, vivid
Micah Gersten (micahg) wrote :

Please open a request for each source using requestbackport in ubuntu-dev-tools. If they have to be accepted in a certain order, please note that and cross-reference the descriptions (descriptions can be edited after the request is submitted). If you need a newer version from Debian, please use the requestsync script, also in ubuntu-dev-tools. Once it's in the Ubuntu archive, you can then open a backport request with requestbackport.

Changed in precise-backports:
status: New → Invalid
Changed in trusty-backports:
status: New → Invalid
Changed in vivid-backports:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers