Known issues with xorg upgrades from HWE stacks?

[Timo Aaltonen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19.11.2013 21:18, Robie Basak wrote:
> On Tue, Nov 19, 2013 at 09:04:59PM +0200, Timo Aaltonen wrote:
>> AIUI LTS releases don't offer upgrades to interim releases (by 
>> default), only when the new LTS is available?
> 
> Right.
> 
> But imagine the situation without HWE.
> 
> I'm on Precise. Quantal is released, and I want to upgrade to it.
> It doesn't appear by default, and the standard answer is to
> specifically request through the GUI that all release upgrades are
> displayed rather than only LTS release upgrades. Then a release
> upgrade to Quantal appears, and I select it. AIUI, this is the
> supported way of doing it.
> 
> Now consider the same upgrade situation with HWE (which you say is
> not supported). In my ignorance, I do exactly the same thing. I
> request it to show me all available upgrades, not just LTS ones.
> The release upgrade to Quantal appears. I select it. My system
> breaks.
> 
> So I don't think that saying that you have to explictly select it
> is a reasonable excuse. This is the recommended way of upgrading up
> from an LTS to a standard release for non-HWE installations. I do
> not necessarily know that an HWE upgrade to a standard release is
> not supported. I may not even know that I have an HWE stack
> installed. The GUI behaves exactly the same, provides no warning
> with the identical process, and causes my system to break.
> 
> Save for any other explanation, this sounds like a Critical bug in 
> update-manager to me, since it causes the system to become
> unusable through a process that the user would otherwise expect to
> work, but is actually not supported in a particular configuration
> that the user ends up in by default.
> 
> Does this make sense? Does you disagree, or should I go ahead and
> file this bug?

Makes perfect sense, don't disagree at all. This was one of the points
of the discussion around "pockets vs renames", that upgrades to 12.10
were a big no-no. Apparently the upgrader wasn't updated to know about
that fact. Not pointing any fingers.. a bug report even this late
certainly won't hurt.


- -- 
t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIbBAEBAgAGBQJSi7sMAAoJEMtwMWWoiYTcNOAP+Lnvhc8pqWsSck2AFeN1U4V8
lh6DK49hbrJwn6sAy90JoRPlZK53chvYj2K7ruMXPFVKiZF2kJJ/oEmesVG3CrbA
3HILAETPHj1OYAzlCwG339uwS9fPF1bFWpWnmkBkMAhiXlApw1NFivps/y6Dsf0e
pTfZUpHtdj9anQFRYkzxSn952vx3gMP8TrCKg1cTjoEAb3UWLLZJj7t/yGp4+5G0
mn10Pnds5xBsF6CEgoWPPoqir95aAHR+VnwuSVg54LbXAbR58/stm/FDBXJssLpX
JXIOzSI2Ae2ZMuEByx/fAQQtlFVu1I6zsG/X2aU9mqP6Bt+SuhUqIrZksVMUgAKx
pDedUrRVQKb1XpvKFA0lqDRI0QeJOe0idTA9UHHsWoT54KomY44vCQtMFFq2SJ2z
plYbdmVM7g39jyJKMKpsKGBjHu9vm/SqMW7/6rsCnVaC7cw55ItgPe4mxwdqHCi1
dhN5OSBGy88WQa9UvNXG5Pesj0mEI7D4eLRPtO4tlG/KJGCr8/irudVbExDu1dlh
yuh5x3nCJOQFG5I3GYHUporAuWd2jPkhjWqwv2GdMQ/KhmMw/NeY2bgv8hicpShD
4hcInIhKLpmpP+EFi6WT6uKU3smqwRm/SUGdrje0OOifm06IDFaF0ru8oXI74fu9
Q0upsCVuX9KJZMd3wHQ=
=WamD
-----END PGP SIGNATURE-----