[Debichem-devel] Bug#866417: bkchem is marked for autoremoval from testing

Daniel Leidert daniel.leidert at wgdd.de
Tue Jan 9 14:40:15 UTC 2018


You wrote:
> On Tue, Jan 09, 2018 at 01:33:39PM +0100, Daniel Leidert wrote:

>> So if the goal of your effort is, to simply move all the packages over
>> to
>> Git just for the sake of it,
> I think that's a wrong interpretation:  I do nothing

This was addressed to Stuart, who asked permission to move over all
packages to Git. And it is reasonable to ask for his intentions and discuss
possible compromises, solutions and consequences.

> just for the sake
> of it but since somebody else created a reality I either need to adapt
> or I will suffer from the consequences.  I decided to adapt and you to
> suffer - everybody draws a personal decision.

I don't think it is up to you to make that judgement. I also wonder, what
hell you think will break lose?

To me it seems, you misjudge reality: The goal was to get rid of
Fusionforge (IIRC). It was not the goal to get rid of non-Git version
control systems. Now the situation is, that the chosen software for
salsa.d.o won't support these systems. But the situation also is,
that AFAIK fusionforge can be removed and non-Git systems can kept
running at least for developers. I don't know of any technical reason
that would make a prompt shutdown of version control systems necessary.

>> [1] IMHO there is really something wrong, when a project pushes all its
>> members to use one VCS but does not fix the build tools to use it first.
>> git-buildpackage has >100 open bug reports?!
>> IMO we should put effort in
>> fixing the toolset first
> You are talking about an ideal world right?

No. I'm talking about making reasonable decisions and taking
responsibility. Something that should be pretty normal.

I'll write a mail do d-devel the next days.

Regards, Daniel

More information about the Debichem-devel mailing list