** Changed in: qps (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899616
Title:
Upgrading from focal to groovy, qps cannot be updated
To manage notific
Upgrades actually tend to be kind of an after thought for a lot of testing, but
in Lubuntu we've made it a requirement of testing. Our checklist is pretty
extensive and covers several different types of upgrades:
https://phab.lubuntu.me/w/release-team/testing-checklist/
Yeah it does sound like y
Right. OK. Sorry. Personally I think upgrades (using do-release-upgrade)
should be something that is of interest to be checked during beta, but
you're the boss.
Looking more into the issue and comparing with a fresh Groovy from
docker, I identified the issue as the fact that I have libqt5core5a
v
Beta's still not Final, for what it's worth. And upgrading to Groovy
post-Beta/pre-Final will not get you Beta, but it will get you Beta+,
which, again, could lead to broken situations.
That said, as of the 8th, both GUI and TUI upgrades from Focal to Groovy
have been tested in Lubuntu (the only f
Groovy was announced as "beta" quality in the beginning of the month. I
am reporting a bug in a beta release so it might get fixed before the
official release. I was not complaining, demanding attention or being a
bad actor in any way that I can detect - and no one said anything about
using Groovy
Since Groovy is a development release, I'm not surprised to see this
sort of behavior in general. I would strongly suggest against using
development releases in production.
Anyways, you might want to start with `sudo apt install --fix-broken` to
see if you can fix the broken packages.
** Changed
