This has been successfully tested on Maverick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/755169
Title:
Backport drush 4.4-1 from natty to lucid, maverick
To manage notifications about this bug
Great. In that case, ACK from backporters fro lucid and maverick.
** Changed in: drush (Ubuntu)
Status: In Progress = Invalid
** Changed in: lucid-backports
Status: Confirmed = In Progress
** Changed in: maverick-backports
Status: Incomplete = In Progress
--
You received
Ping! What's keeping this from being backported now?
4.5 is coming up next week, I hope this will not be an issue...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/755169
Title:
Backport drush
Like I mentioned earlier, testing backports on all releases we're
backporting to is a requirement of the backports process. We can
approve the backport once it's been tested on maverick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i have finally found time to test the backport in lucid, and I confirm
it works. unfortunately, I can't test in maverick, but I don't see why
it would fail there.
** Changed in: lucid-backports
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member
I agree this should be backported to maverick.
I have the test environment only for Lucid however, so I will do that
part.
I am the maintainer of aegir-provision in Debian, and it was removed
from unstable and squeeze, because that version is out of date, unstable
and unsupported upstream. It
I have opened a bug report to remove the leaf package from the archive:
https://bugs.launchpad.net/ubuntu-sponsoring/+bug/793567
I will test the backport in a few minutes...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If a package is already broken, it needn't block a backport (the only
consideration would be if it were to make it a lot more broken, which
doesn't seem likely in this case).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
