[Pkg-privacy-maintainers] Bug#910493: Handle transition from MAT to MAT2

[Jonas Meurer]

Hi intrigeri,

Am 07.10.2018 um 10:31 schrieb intrigeri:
> let's discuss how we'll be handling the transition from MAT to MAT2
> in Buster. My goal here is to avoid users keeping using the
> deprecated, unmaintained MAT v1, and to nicely transition them to the
> new MAT2 implementation.

Full ack. Thanks for bringing this up.

> As I wrote on the ITP (trimming down ideas that don't make sense
> anymore):
> 
> intrigeri:
>> What matters to me is the users' perspective. I think we should
>> provide a clear, unambiguous transition path and avoid leaking
>> technical details to users. So once MAT2 reaches feature parity with
>> MAT (I think the only real blocker is the lack of a Nautilus
>> extension; MAT v1's seems to be broken on sid currently but it has
>> a GUI which mitigates that problem) I think we should:
> 
>>  - Have mat2 conflicts+replaces mat, remove mat from testing+sid,
>>    and ship a transitional package called mat that pulls mat2 in.
> 
> IMO we should do that as soon as mat2 installs the Nautilus extension
> (#910491).
> 
> Does this make sense to you? Is there a better way to handle this?

The main advantage of mat over mat2 I know of is the GUI. But since mat
is broken and should no longer be used for security reasons, my
suggestion would be to ignore this advantage and go ahead with the
transition exactly the way you described it.

Cheers
 jonas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181007/f463e199/attachment-0001.sig>