On Wed, Jul 31, 2019 at 12:35:56PM +, Holger Levsen wrote:
> > > > > src:librsync is currently still to be removed from bullseye on August
> > > > > 9th, because #776246 was only fixed in experimental...
> > > > In experimental and unstable.
> > >
> > > not according to the bts which only
On Wed, Jul 31, 2019 at 04:41:29PM +0500, Andrey Rahmatullin wrote:
> On Wed, Jul 31, 2019 at 11:28:46AM +, Holger Levsen wrote:
> > > > src:librsync is currently still to be removed from bullseye on August
> > > > 9th, because #776246 was only fixed in experimental...
> > > In experimental
On Wed, Jul 31, 2019 at 10:34:17AM +0500, Andrey Rahmatullin wrote:
> On Wed, Jul 31, 2019 at 02:06:50AM +, Holger Levsen wrote:
> > > Turns out I had some extra time for this flying back from DebConf and it
> > > needed changes to only one file for this, so new rdiff-backup with
> > >
On Wed, Jul 31, 2019 at 11:28:46AM +, Holger Levsen wrote:
> > > src:librsync is currently still to be removed from bullseye on August
> > > 9th, because #776246 was only fixed in experimental...
> > In experimental and unstable.
>
> not according to the bts which only knows 1.0.0-1~exp1 as
On Wed, Jul 31, 2019 at 02:06:50AM +, Holger Levsen wrote:
> > Turns out I had some extra time for this flying back from DebConf and it
> > needed changes to only one file for this, so new rdiff-backup with
> > librsync2 was uploaded yesterday...
>
> src:librsync is currently still to be
On Tue, Jul 30, 2019 at 09:06:32AM +0300, Otto Kekäläinen wrote:
> Turns out I had some extra time for this flying back from DebConf and it
> needed changes to only one file for this, so new rdiff-backup with
> librsync2 was uploaded yesterday...
src:librsync is currently still to be removed from
Turns out I had some extra time for this flying back from DebConf and it
needed changes to only one file for this, so new rdiff-backup with
librsync2 was uploaded yesterday...
librsync2 is available in unstable, please binNMU burp, csync2 and
duplicity.
From https://lists.debian.org/debian-python/2019/07/msg00093.html I guess
Otto (Cced) is interested in keeping rdiff-backup? In that case, Otto,
please prepare an upload with a fix.
--
WBR, wRAR
signature.asc
ma 29. heinäk. 2019 klo 10.39 Andrey Rahmatullin (w...@debian.org) kirjoitti:
>
> On Mon, Jul 29, 2019 at 10:36:57AM +0200, Otto Kekäläinen wrote:
> > > librsync2 is available in unstable, please binNMU burp, csync2 and
> > > duplicity.
> > >
> > > From
ma 29. heinäk. 2019 klo 10.25 Andrey Rahmatullin (w...@debian.org) kirjoitti:
>
> librsync2 is available in unstable, please binNMU burp, csync2 and
> duplicity.
>
> From https://lists.debian.org/debian-python/2019/07/msg00093.html I guess
> Otto (Cced) is interested in keeping rdiff-backup? In
On Mon, Jul 29, 2019 at 10:36:57AM +0200, Otto Kekäläinen wrote:
> > librsync2 is available in unstable, please binNMU burp, csync2 and
> > duplicity.
> >
> > From https://lists.debian.org/debian-python/2019/07/msg00093.html I guess
> > Otto (Cced) is interested in keeping rdiff-backup? In that
Control: tag -1 confirmed
On Sun, Jul 21, 2019 at 03:04:40PM +0500, Andrey Rahmatullin wrote:
> The librsync library changed the ABI and also some parts of API, the API
> change
> impacts only rdiff-backup, for which #928885 is filed with no reaction so far.
Please go ahead in unstable.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
The librsync library changed the ABI and also some parts of API, the API change
impacts only rdiff-backup, for which #928885 is filed with no reaction so far.
I've tested all revdeps,
13 matches
Mail list logo
