Anton Aylward <opensuse@antonaylward.com> wrote:
Greg Freemyer said the following on 10/02/2013 05:10 PM:
On Wed, Oct 2, 2013 at 2:14 PM, Anton Aylward <opensuse@antonaylward.com> wrote:
So why didn't it happen to me? Perhaps because I have this huge single BtrFS partition.
I think ImageMagick for 13.1 is different from the one for 12.3. Only the one for 13.1 fails to install due to the BtrFS lack of functionality.
That doesn't make sense. If 13.1 has a late model btrFS with the workaround patch, then it shouldn't fail, and according to that logic its a problem with imagemagick being changed and necessitating that BtrFS doesn't have the fix.
There's something there that doesn't make sense.
The zipper duplicate upgrade process runs under 12.3. 13.1 doesn't show up until reboot.
Here's a brand new thread from factory today:
http://markmail.org/message/vbfiw6sximwukofc
As of that 3 hour old thread, there is not even a recommended upgrade path for people running 12.3 with btrfs as their system drive and having ImageMagick installed.
As of that thread they are running 3.11.0-rc4-7.g327e5fc-default Which gets back to my question about which kernel will be in 13.1
The answer is still 3.11.
if, as in the past, the .1 (or previously the .0) release is rally a late model beta - call it a delta or a gamma, and the real release is the .2, then yes, sure, its all stuff that we don't expect to work properly anyway... user driven testing.
For the kernel that numbering scheme hasn't been used since 2.6.0 a decade or so ago.
You want a laugh? run
find /usr -links +20 -print0 | xargs -0 ls -l | more
When you see some link numbers above 200 go past stop and wonder what package they are from. Ask yourself if the installer will install THAT
package.
If the problem is what you claim then ImageMagick is the least of you worries. If you can install the basic system with that hugely linked file then perhaps the problem is something else.
I'm not claiming anything, just passing on info from the factory list.
That means you are exactly the person that will see this zypper dup upgrade failure unless you happened to have already setup the new feature.
I very much doubt I will face that problem for a variety of reasons which should be apparent to most people reading this thread.
Hint: its a show-stopper so will be fixed
Easier said than done in this case. It's a chicken and egg problem. With time they could have zipper duplicate upgrade the kernel first then reboot. I doubt they can transparently fix it. The easy option is to not support zipper duplicate for people that have their system files on btrfs. Just require people with that setup to download the dvd and upgrade that way.
Notice the that 12.3 kernel can't setup the feature with the filesystem mounted, so at least as of this very second the only choice is to boot a rescue CD/DVD and make the filesystem change, then boot back.
I very much doubt that the 12.3 release will have the 3.11 kernel
Thus as of this minute,
Thank you for the qualifier :-)
the only option for this use case is to download the 13.1 boot CD / DVD and use it to do the upgrade.
I assume this will be resolved in the next few weeks, but 13.1 is rapidly approaching release, so they don't have a lot of time left to address it.
Deadlines can be a great incentive for productivity.
After some thought I bet they don't support zypper dup updates for users like you. There is time to put a check in zypper to error out cleanly and the user base affected is likely small. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org