Let's then request the SRU verification team to drop the package for trusty-proposed.
If SASL is not supported in the Trusty pkg, there is no point to complete the SRU for Trusty.
Additionally, since Trusty is near to its EOL, I don't see good reason/justification to justify the effort/work to enable SASL on the package.
Also enabling SASL, IMHO, won't be consider a "bug fix", but a "new feature".
For all the reasons above, let's simply drop the pkg from trusty-proposed.
Ionna,
Let's then request the SRU verification team to drop the package for trusty-proposed.
If SASL is not supported in the Trusty pkg, there is no point to complete the SRU for Trusty.
Additionally, since Trusty is near to its EOL, I don't see good reason/ justification to justify the effort/work to enable SASL on the package.
Also enabling SASL, IMHO, won't be consider a "bug fix", but a "new feature".
For all the reasons above, let's simply drop the pkg from trusty-proposed.
- Eric