Hi Jan, Jan Müller wrote (27 May 2014 08:26:49 GMT) : > Would be great, if this bug could be fixed and closed.
Sure, it would be great. > It is in backupninja upstream since ~ 6 month -> FYI upstream (that is, currently primarily me, who also happens to be the main maintainer of the package in Debian) is swamped and did not manage to put a new release out yet. In this context, you'll understand that it is not my priority to cherry-pick individual upstream patches on top of current sid's package, which requires making sure these patches don't depend on other commits, don't break anything else, etc. If you want to see things move forward faster, you can help e.g. by: * testing the current upstream Git code: https://lists.riseup.net/www/arc/backupninja/2014-02/msg00003.html * triaging incoming bug reports and testing proposed patches: https://lists.riseup.net/www/arc/backupninja/2014-02/msg00004.html :) > https://git.sarava.org/?p=backupninja.git;a=commitdiff;h=b8b8b46fbaf9acbdc769d311a064ab89bb670ef7 Just for the record, this is a repository used by an individual contributor to backupninja, not the official upstream release. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
