ACK from Backports team for original backport plan:
Backport the Karmic version to jaunty-backports, and then backport
Lucid's version to Karmic.
** Changed in: jaunty-backports
Status: New = Confirmed
** Changed in: jaunty-backports
Status: Confirmed = In Progress
** Changed in:
Let's handle the two together:
Doing a quick build test:
Karmic's version backports cleanly to Jaunty and appears to work in my
initial testing.
Lucid's version backports cleanly to Karmic.
Lucid's version does not backport to Jaunty because of pbuilder-
satisfydepends-dummy: Depends: quilt
Hey, thanks for the quick response!
If you can give me a few basic commands to run or look into I can play
with it on some VM's today. pbuilder something something and some wiki
pages is what I have so far. I know debian alright but not ubuntu as
specific.
I don't see why there would be a quilt
I took a quick look at the package... Undoing that is going to require
editng the upstream source. Which I think isn't necessary for this
backport.
I'll work with the upstream maintainer to get his two nitpicky unfiled
bugs fixed further upstream, and in two months we could kick jaunty up
to 1.4.
Right; the Debian maintainer added a quilt dependency.
https://wiki.ubuntu.com/Prevu
The Prevu tool is my perferred tool for quickly testing backports.
After doing prevu-init's for Karmic and Jaunty, run prevu
memcached/lucid to backport Lucid's version to the currently running
distribution, or
