Your message dated Fri, 01 Mar 2019 18:19:47 +0000
with message-id <[email protected]>
and subject line Bug#910493: fixed in mat2 0.8.0-3
has caused the Debian Bug report #910493,
regarding Handle transition from MAT to MAT2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
910493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910493
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mat2
Version: 0.4.0-1
Severity: normal

Hi,

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.

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?

Cheers!
-- 
intrigeri

--- End Message ---
--- Begin Message ---
Source: mat2
Source-Version: 0.8.0-3

We believe that the bug you reported is fixed in the latest version of
mat2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Meurer <[email protected]> (supplier of updated mat2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 01 Mar 2019 18:57:47 +0100
Source: mat2
Architecture: source
Version: 0.8.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 
<[email protected]>
Changed-By: Jonas Meurer <[email protected]>
Closes: 910493
Changes:
 mat2 (0.8.0-3) unstable; urgency=medium
 .
   * Upload to unstable. This adds a new binary package 'mat' which handles
     the transition from mat to mat2. (Closes: #910493)
Checksums-Sha1:
 ddeb0055d1ab28520bc4ae10864b7c62f3891061 2433 mat2_0.8.0-3.dsc
 02d0fad945cafa18382fc0f0ab46beafc0999a33 10020 mat2_0.8.0-3.debian.tar.xz
 3e0c3295bc30df3e84acc0c56207e62cb973debc 11857 mat2_0.8.0-3_amd64.buildinfo
Checksums-Sha256:
 74bfcf44fc7b666e5cd06af54f635faf9c137b5b3e9fa02391caba5722036617 2433 
mat2_0.8.0-3.dsc
 31707226f5ad70c5f3bb517e09a9bb01793336198f2f86ad9bc3120204e251df 10020 
mat2_0.8.0-3.debian.tar.xz
 fb7371466d7ad65c10706654cda5e7a1e259f1b397b0577a3ef5b27b59c953bd 11857 
mat2_0.8.0-3_amd64.buildinfo
Files:
 50e2f57f8a336bafe6f9bf875c863c20 2433 utils optional mat2_0.8.0-3.dsc
 74b4bfce60e611f1ea3506ec41cfa652 10020 utils optional 
mat2_0.8.0-3.debian.tar.xz
 e69b7ecd83e96f551d546321c99aeee7 11857 utils optional 
mat2_0.8.0-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEELIzSg9Pv30M4kOeDUmLn/0kQSf4FAlx5dosACgkQUmLn/0kQ
Sf7RRw//SsNersbzxV8byVgs7NqnR4hg0rO9m2+NjT4LI0UZ0aAGbXj+AHs1sXzL
LOnBYBs8DV3rAUKv9PAHAEy/7Afpud96H8CDDCKnjalv0j0k+K2q6Gyq8hKjokxk
yPyjZdIxaLzphVo1J7C4Dm3NU5yg0cQv2e28wmLlInAAKzNkavITAWORWL+jdLzR
DlJPws/0VgGOG+vZs6BEm1jFw/gZqrJ5haAU/4tVTHb8fX45vIVapNXw1LpAB4lF
jku6H1ksGO+2DTxgd16Gkd1Bb8TLEG5qUMeGvXTdemHJKcuFEkcolPr7mWe5ee4E
CT2vlOm5GV8S57EW3FGVPg2kPkHzIfc7K/zNKkIpc4Y2VSDkN/xmQKqTKyIZRrVY
LA750uJKfYTlEDqazQPNbIsx9ttkYXFbW8eISYg+yMnSyZthJEjTjCELXGzJKZxE
gN3Jxdmb4RHs9MgyTBdTDXYtOJxPPxv1Kx14BzMwayccZyPgiwL+BMjU6kByMuU5
9K5I6CLZa36WQNEizKGkH2Qb9QU78y1QSgpy/k4L5+3nIu+5SCHnGLJvZzu7n2b4
b9ujfkHsa5cWibwIhiIPK36d2RGYxUK17xYvWMIJ/Mw8b7tTB9R9q/kU9sVJoC4k
UWk+AQ60pi2PLAA7piuvBPrtInLN9Q/eKN3wtciwIM4rFovm4fM=
=3DLS
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to