[Pkg-giraffe-discuss] z-push: some signed tags missing on the repository

[Roel van Meer]

Carsten Schoenert writes:

> I thought upstream has already changed those files to upstream versions
> while I've read the release announcement for version 2.3.6 [1], thats
> why I originally have written my previous email. But if it's impossible
> to use existing Debian packages that's also fine.
>
> But I would write then some sentences with some further explanations
> into README.Debian. This not only us help to keep track of such changes.

Thanks, I did so: https://github.com/roelvanmeer/z-push-packaging/commit/3c1f39a688ad62d715dfafa683c85f5601f365a2

> >> Roel, care to check this? If the packages are possible to use the
> >> respective binary package needs a depends and a extra line in the
> >> *.links sequencer file. I can give a advice then if needed. An example
> >> for such a linking can be seen in the package libvmime1-doc.
> >
> > Well, it is really required to get Z-push into experimental then we should
> > discuss what should be done, but unfortunately it's not as easy as just
> > replacing the files with dependencies to other modules.
>
> No, it's not a requirement to use the upstream versions of those files
> and the usage of modified files isn't a blocker for getting z-push into
> Debian.

Great!

> In the near future on the Kopano Conference there will be time to talk
> with upstream what can be done and what should be done.

I'll be there too, mosty likely.

Carsten, Mark asked if the current state of Z-push packaging was ready to be  
uploaded to the alioth repo. Since you reviewed it, what's your opinion? Are  
there things I should do before we can do that?

Thanks,

Roel