Bug#909000: Thunderbird 60 cannot be at stretch normal repository

2018-10-10 Thread Daniel Kahn Gillmor
On Wed 2018-10-10 17:30:33 +0200, Narcis Garcia wrote:
> The good solution for this is to move Thunderbird 60 to
> stretch-backports instead of being at normal repository.
>
> Normal users will keep current Enigmail 2:1.9 , current Thunderbird 1:52
> and current GnuPG 2.1 and not unstable repositories.
>
> Other users will be allowed to use stretch-backports to upgrade to
> Thunderbird 1:60 , Enigmail 2:2.2 and GnuPG 2.2 when all available.
>
> No packages break, no Enigmail loss for unexperienced users.

i haven't heard anyone from debian say that they're up for
maintaining/supporting thunderbird 52 in stretch.  do you know anyone
who is volunteering for that task?

if there isn't anyone, then moving to TB 60 in stretch is probably
pretty important, while it also requires all the rest of the maintenance
work described upthread.

Software maintenance within the context of an active network and complex
upstreams is hard :(

--dkg



Bug#909000: Thunderbird 60 cannot be at stretch normal repository

2018-10-10 Thread Narcis Garcia
The good solution for this is to move Thunderbird 60 to
stretch-backports instead of being at normal repository.

Normal users will keep current Enigmail 2:1.9 , current Thunderbird 1:52
and current GnuPG 2.1 and not unstable repositories.

Other users will be allowed to use stretch-backports to upgrade to
Thunderbird 1:60 , Enigmail 2:2.2 and GnuPG 2.2 when all available.

No packages break, no Enigmail loss for unexperienced users.

-- 


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.