Please backport ansible 1.4.3+dfsg-1 (universe) from trusty

Bug #1247541 reported by anatoly techtonik
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Precise Backports
Fix Released
Undecided
Unassigned
Quantal Backports
Fix Released
Undecided
Unassigned
raring-backports
Fix Released
Undecided
Unassigned
saucy-backports
Fix Released
Undecided
Unassigned

Bug Description

Please backport ansible 1.4.3+dfsg-1 (universe) from trusty to saucy.

Reason for the backport:
========================
More convenient to work with, and:
 + speed
 + support for role dependencies and defaults
 + local facts
 + errors about mistyped variables

http://blog.ansibleworks.com/2013/09/13/ansible-1-3-and-awx-1-3-hit-the-streets/

Testing:
========
Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing.

You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:<lp username>/<ppa name> -s trusty -d saucy ansible

* saucy:
[x] Package builds without modification
[x] ansible-node-fireball installs cleanly and runs
[x] ansible installs cleanly and runs
[x] ansible-fireball installs cleanly and runs
[x] ansible-doc installs cleanly and runs

I tested raring,quantal,precise in a pbuilder-dist environent:

* raring:
[x] Package builds without modification
[x] ansible-node-fireball installs cleanly and runs
[x] ansible installs cleanly and runs
[x] ansible-fireball installs cleanly and runs
[x] ansible-doc installs cleanly and runs

* quantal:
[x] Package builds without modification
[x] ansible-node-fireball installs cleanly and runs
[x] ansible installs cleanly and runs
[x] ansible-fireball installs cleanly and runs
[x] ansible-doc installs cleanly and runs

* precise:
[x] Package builds without modification
[x] ansible-node-fireball installs cleanly and runs
[x] ansible installs cleanly and runs
[x] ansible-fireball installs cleanly and runs
[x] ansible-doc installs cleanly and runs

No reverse dependencies

Michael Vogt (mvo)
summary: - Please backport ansible 1.3.4+dfsg-1 (universe) from trusty
+ Please backport ansible 1.4.0+dfsg-1 (universe) from trusty
Revision history for this message
Michael Vogt (mvo) wrote : Re: Please backport ansible 1.4.0+dfsg-1 (universe) from trusty

Trusty has 1.4.0 now.

We should backport it al lthe way to precise as the current version in backports has some security issues, notably:

- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4259
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4260
- https://access.redhat.com/security/cve/CVE-2013-2233

I build and tested 1.4.0 and it works fine for me. I will update the description of the bugreport to reflect this.

description: updated
Revision history for this message
Felix Geyer (debfx) wrote :

I can push 1.4 into saucy-backports (and eventually the other releases) but the security fix should really end up in saucy-security too.

Revision history for this message
anatoly techtonik (techtonik) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

@Felix: Thanks, it would be nice get 1.4 into backports.

As for the security issue, I opened a bug some days ago:
  https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1256068
once I find the diff I will work on a debdiff for this too.

We should also backport to the other ubuntu versions. I am happy to do the testing there too.

Revision history for this message
Michael Vogt (mvo) wrote :

Hello - is there anything I can do to help this backport along?

It would be really great if a more recent version of ansible could be made available via backports.

summary: - Please backport ansible 1.4.0+dfsg-1 (universe) from trusty
+ Please backport ansible 1.4.3+dfsg-1 (universe) from trusty
description: updated
Revision history for this message
Iain Lane (laney) wrote :

Oops sorry, will look in a minute.

Revision history for this message
Iain Lane (laney) wrote :

Yep, looks good - accepted. Thanks.

Changed in saucy-backports:
status: New → Fix Released
Revision history for this message
anatoly techtonik (techtonik) wrote :

Iain, is there a service to check package version against upstream and request backport for minor versions from web interface?

Revision history for this message
Iain Lane (laney) wrote : Re: [Bug 1247541] Re: Please backport ansible 1.4.3+dfsg-1 (universe) from trusty

On Tue, Jan 07, 2014 at 10:25:09AM -0000, anatoly techtonik wrote:
> Iain, is there a service to check package version against upstream and
> request backport for minor versions from web interface?

No. You can check package versions at

  http://launchpad.net/ubuntu/+source/<packagename>

And request backports using the `requestbackport' tool.

  https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

Revision history for this message
anatoly techtonik (techtonik) wrote :

Thanks. Now I am sure that I've not missed anything.

I found the site I was thinking about - https://merges.ubuntu.com/ - thought that it also monitors upstream changes. I remember there was something like this somewhere..

Revision history for this message
Michael Vogt (mvo) wrote :

I also tested the current trusty version against:

* raring:
[x] Package builds without modification
[x] ansible-node-fireball installs cleanly and runs
[x] ansible installs cleanly and runs
[x] ansible-fireball installs cleanly and runs
[x] ansible-doc installs cleanly and runs

* quantal:
[x] Package builds without modification
[x] ansible-node-fireball installs cleanly and runs
[x] ansible installs cleanly and runs
[x] ansible-fireball installs cleanly and runs
[x] ansible-doc installs cleanly and runs

* precise:
[x] Package builds without modification
[x] ansible-node-fireball installs cleanly and runs
[x] ansible installs cleanly and runs
[x] ansible-fireball installs cleanly and runs
[x] ansible-doc installs cleanly and runs

Would be great to get the backports here as well as 1.1 has two CVEs attached to it that are fixed in 1.2.3+
(and therefore in the 1.4.3 version that I would like to see backported :)

description: updated
Revision history for this message
Felix Geyer (debfx) wrote :

The diff between 1.4.3 and 1.4.4 looks fairly small. I guess we should just backport that instead?

Revision history for this message
Michael Vogt (mvo) wrote :

@felix: yes indeed, that is preferable, the changes are very isolated to the "pip" extension module in ansible so super low risk if we pick 1.4.4 instead of 1.4.3.

Revision history for this message
Michael Vogt (mvo) wrote :

@Felix: ... and thanks a lot of your review :) !

Revision history for this message
Felix Geyer (debfx) wrote :

Great, I've pushed 1.4.4 to all 4 series.

Changed in precise-backports:
status: New → Fix Released
Changed in quantal-backports:
status: New → Fix Released
Changed in raring-backports:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.