[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Backporting version not in testing

On Sat, Nov 08, 2014 at 09:46:46PM +0000, Holger Levsen wrote:
> Hi Andreas,
> On Samstag, 8. November 2014, Andreas Bombe wrote:
> > It works fine if you don't want the network sync feature. 
> ah, ok. sounds a lot less bad :) is there a bug report for this problem?

Well, it's a pretty popular feature, I think. You don't need it if you
use it on one machine only or you can copy the files manually, but
that's not as smoothly automated and does not include a merge function.

Bug reports for broken sync creep up pretty regularly when I don't
update the package for a time. Currently there's #768398 because I was
reluctant to update the package during freeze and well, upstream's
server broke the current version already.

For wheezy there's #720765. I want to take better care of the package
now so I want to backport at least to wheezy.

> > Alternatively I could keep the package out of the release/testing
> > altogether and distribute current versions straight from unstable into
> > backports.
> I think you should rather talk with the release team to find ways to (also) 
> resolve this issue within stable+testing. There are other packages like this 
> in the archive...

Okay, I was reluctant to do that because with all the work they have it
felt a bit frivolous to ask to have my package excepted. Especially
since it would have to be a complete freeze exemption allowing new
versions in indefinitely.

If that is actually the correct (and acceptable) thing to do, I will ask
the release team for jessie.


Reply to: