On 2013-03-20 07:34, Alexander Zangerl wrote:
On Tue, 19 Mar 2013 13:24:28 +0100, intrigeri writes:
this problem is solved in the version in unstable (0.6.20-3),
Any particular reason why #702563 is not marked as such, then?
sorry, i overlooked that; closed now.
Would debian/patches/02unicode.dpatch apply to the duplicity version
currently in Wheezy? If not, how hard would it be to extract the
minimal upstream changes needed by this workaround?
both 682837 and 702563 are not hard to retrofit - but isn't that
against the freeze policy?
the way i understand '3. fixes for severity: important bugs in
packages
of priority: optional or extra, only when this can be done via
unstable'
would mean that only what's in unstable can be considered at this
time...
but please correct me if i'm wrong!
So, I recommend you investigate how targeted fixes for the most
serious bugs could go into Wheezy through t-p-u.
i've just completed that and prepared a 0.6.18-7 for tpu; the
much much more manageable debdiff is attached. if nobody complains
loudly
about further problems i'll upload that in a day.
NACK. The diff you attached also includes three versions prior to that
numbered above; things like "include new [...] backend" and fixing
wishlist bugs are big no-nos at this stage of the freeze. Besides that
it's also huge.
I'd be more open to properly isolated fixes for #682837 and #702563,
which is what I assume you intended to do here.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
<directhex> i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
