On 10/22/18 7:03 PM, Debian Bug Tracking System wrote:
> Hi Thomas
> 
> As per the package salvation process I oppose to this. I'm actively
> working on an updated package and I invited everyone who mailed me about
> the package to help maintain it. Unfortunately nobody really started to
> help in the last months.

Every single time someone started working on it, you managed to drive
him away. I do not intend to attempt the same approach again. So if
we're to do team work, then please answer what's bellow, and let's get
the job done (together, hopefully).

> As you know from previous conversation on this, my work in progress

Yeah, it's been nearly a year it's "in progress". Unfortunately, that's
not enough to reach Buster in time. What's holding you from uploading,
except what you describe below?

> can be found here. I also sent this to everyone else asking.
> 
> https://salsa.debian.org/ceph-team/ceph/tree/luminous/wip-gaudenz

I read "luminous" there in the branch name. Is this really what you
propose? Can't we have Mimic for Buster? Mimic comes with loads of nice
features, like a fully working cephfs that came out of beta. It'd be
really disappointing for everyone if we only had Luminous. Though
Luminous, I guess, is better than no ceph at all, which is the current
state of things... :(

> As you can see there was steady progress. That package is finally mostly
> ready.

I don't even understand where's the package that you're talking about.
On that branch you're pointing at, the changelog shows no entry from you
since Feb 2017. Should I manually fix the changelog to build a certain
version? If so, why didn't you edit it, to match the new upstream
release number?

> If you want to help, I'd appreciate someone to build the package
> and test it.

Sure, if you point at something that remotely looks like what we expect.

> There are also still two Errors reported by lintian which
> need fixing. One is an RPATH issue on the Java JNI libraray which I
> could not solve yet and where help would be much appreciated.

Can you explain further where to search for a fix?

Cheers,

Thomas Goirand (zigo)

Reply via email to