[prev in list] [next in list] [prev in thread] [next in thread] 

List:       meego-dev
Subject:    Re: [MeeGo-dev] missing dist-upgrade path on major releases
From:       Stefan Kost <ensonic () hora-obscura ! de>
Date:       2011-07-19 9:54:56
Message-ID: 4E255470.5010700 () hora-obscura ! de
[Download RAW message or body]

Hi,

On 07/18/11 17:58, Kok, Auke-jan H wrote:
> On Mon, Jul 18, 2011 at 6:38 AM, Stefan Kost <ensonic@hora-obscura.de> wrote:
>> hi,
>>
>> there is a long standing bug
>> https://bugs.meego.com/show_bug.cgi?id=9205
>> regarding a missing upgrade path for new major releases. Why does MeeGo
>> want to be special here (technical/legal/other issue)? I'd really like
>> to know, the current status is quite embarrassing.
>>
>> Is there a practical intermediate solution available? Like installing
>> all updates and then updating the repositories to change the 1.1. to 1.2
>> in the repo url and running a dist-upgrade?. Has anyone tried that?
> We're working on bringing solutions in the long term.
>
> The focus for 1.3 will be on utilizing the btrfs features we can
> easily enable: Device reset (factory reset) will be possible, and the
> shell installer will be able to install into a new btrfs subvolume on
> an existing installation - effectively saving all your data (and
> potentially even your OLD os install as well as a bonus).
>
> Doing a in-place OS upgrade is probably something we'll not work on,
> as there are too many risks involved. "zypper dup" works good, but,
> the nature of rpm updates outside the tested update path is almost
> always guaranteed to give problems.
>
> Auke
What are the problems in particular you see here. I am running an (rpm
based) opensuse installation on my home computer, which I upgraded since
version 6.2. I know that it can cause issues, but in that case one could
still reinstall. So far I have been always able to resolve the conflicts.

Stefan
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
[prev in list] [next in list] [prev in thread] [next in thread]