Comment # 15 on bug 1061208 from Michael Andres

Patrick: Thanks. Your issue is different than the one reported here, but it's
something that worries us most ATM. It's seems to be a duplicate of
bug#1146027, but for now I'd like to continue here.


Let's stay with your server:

(In reply to Patrick Finie from comment #13)
> Now to a different and third machine,  My server.
> 
> instead of doing a update before changing over the repositories i did this
> method.  
> # cp -Rv /etc/zypp/repos.d /etc/zypp/repos.d.Old  ># sed -i 's/15.0/15.1/g'
> /etc/zypp/repos.d/* >  # zypper --gpg-auto-import-keys ref > zypper dup
> 
> dealt with all the package that needed to be changed over and rebooted.
> 
> went to use zypper and segfault.

I'm most interested in the 'zypper dup' before you rebooted: 

- 'zypper dup' creates a resolver testcase at
/var/log/updateTestcase-YYYY-MM-DD-hh_mm_ss (the date the dup command was
executed). Please pack the output directory and attach it to THIS bugreport.

(In case the testcase exceeds the 10MB limit for bugzilla uploads, you can use
'split' to divide the file into smaller pieces)

- If the zypper.log showing the refresh command and the dup are still available
(maybe backuped) please attach them as well.