Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)

[Sebastiaan Couwenberg]

On 8/26/18 10:17 AM, Stuart Prescott wrote:
>>>> No one in the Debian GIS team is willing to maintain this EOL package
>>>> any longer, qmapshack is were we invest our effort.
>>>
>>> Please file a WNPP bug that orphans qlandkarte. That signals to others
>>> that
>>> they can (and should) take over maintenance of the package.
>>>
>>> §5.9.4 of the Developers Reference covers the case where the existing
>>> maintainers are unwilling to maintain a package any longer:
>>>
>>> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#orpha
>>> ning
>> No, EOL software should be removed. The QA team is not the place for EOL
>> and broken packages.
>>
>> The removal of qlandkartegt was a long time coming, since it's been
>> superseded by qmapshack in Debian and upstream, this issue was just the
>> trigger.
> 
> If you really believe that, the correct course of action is an RM bug. wontfix 
> on an RC bug still isn't right.

If you really cared, you would have checked and seen that one already
exists.

> More generally, though, there is plenty of software that is Debian without an 
> active upstream but with active maintainers keeping it alive. Dead upstream's 
> aren't a problem for Debian; it's dead upstreams coupled with inactive 
> maintainers. It's fine for you to decide that you don't want to be that 
> maintainer, but it's not your call to stand in the way of others who do want 
> to do this work.

I am the only active maintainer of this package, it *is* my call to tell
others that I will not fix this issue because the software is EOL.

People that want to fix this package know what to do, get involved in
upstream development and take over maintenance of the package.

I care more about the quality of Debian than to keep broken packages
that have no future in Debian.

So far no one has stepped up to revive QLandkarteGT upstream
development, it just a lot of empty talk and no action.

Stop talking out of your ass, and get off it to revive upstream
development if you really care about the future of this package.

Kind Regards,

Bas