Bug#841294: Overrule maitainer of "global" to package a new upstream version
On Dec 05 2016, Ron <ron@debian.org> wrote:
> Hi Sam,
>
> On Wed, Nov 30, 2016 at 11:39:08AM -0500, Sam Hartman wrote:
>> >>>>> "Ron" == Ron <ron@debian.org> writes:
>>
>> Ron> Hi OdyX,
>>
>> Ron> On Wed, Nov 16, 2016 at 03:23:47PM +0100, Didier 'OdyX' Raboud wrote:
>> >> Hi there,
>> >>
>> >> I've been mostly VAC, and only now found enough time to properly
>> >> read through this bug log. In the interest of transparency and to
>> >> help the TC reach a consensus (also through understanding what
>> >> the other members' understanding, ideas and positions are), here
>> >> comes my current understanding of the problem at hand.
>> >>
>> >> As preamble, I will upfront state that I have _not_ looked in the
>> >> precise details of the so-called 'htags' functionality, as, the
>> >> rest will show, my current viewpoint on the problem is that it
>> >> doesn't matter.
>>
>> Ron> If we run with your proposal, what are you actually suggesting
>> Ron> we tell the people who'd be upset by the loss of htags without
>> Ron> notice in Stretch? Because I don't really see how you've
>> Ron> addressed that here.
>>
>> Ron, thanks for working with the process.
>
> Thanks for engaging with the question :)
>
> I was a little disappointed that all OdyX had to say about it was:
>
> <OdyX> I've sent a long mail with my opinion, and Ron's answer hasn't
> altered my conviction yet.
>
> Because "lalala, I'm not listening" isn't really an answer to a simple
> direct question. And definitely not something that I can wrap with
> "Sorry, but a group of Debian Developers considered this all in careful
> detail, and this is what we have decided", when breaking the news to
> affected people.
...whose existence has only been postulated so far though.
In any case, it seems there are plenty of people who'd be willing to
relieve you of that burden and take over maintenance of global -
including dealing with any fallout from updating to an up-to-date
version.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
Reply to: