Bug#923184: [pre-approval] unblock: qgis/3.4.5+dfsg-1
On 2/24/19 9:23 PM, Bas Couwenberg wrote:
> Because the 2.18 LTR is EOL with the release of QGIS 3.4.5 having the
> latter in buster is probably better than leaving the qgis package at the
> last 2.18.x release (2.18.28).
>
> QGIS 3.4 is the new LTR and switches to Qt5 and Python 3, as such
> the changes since the version in testing are quite large and cannot be
> considered "small, targeted fixes".
>
> While users of the qgis package are unlikely to use the version of the
> package available in stable, and more likely using the latest LTR from
> backports, I think having 3.4.5 in buster is better for users upgrading
> from stretch than leaving them with the EOL 2.18.28 release until the
> package is updated in buster-backports.
>
> Would you approve of moving QGIS 3.4.5 from experimental to unstable and
> allowing it to migrate to tesing for inclusion in buster?
>
> Or should we keep it experimental until after the release, and make the
> newer LTRs available in buster-backports when it hits testing?
As reported by Lucas Nussbaum in #924833, qgis (2.18.28-2) FTBFS in
unstable due to sip4 (4.19.14+dfsg-1) which was uploaded a couple of
weeks after qgis.
With 2.18.x being EOL upstream, we cannot rely on upstream to provide a
fix, and I lack the skills for it.
I'm going to move QGIS 3.4 to unstable so that we at least have a
version of QGIS in unstable that supports SIP 4.19.14.
If the changes in QGIS 3.4 are deemed to invasive for an unblock, we'll
have to release buster without qgis and deal with lots of unhappy users.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Reply to: