On 06/02/2012 01:19 PM, Raymond Wooninck wrote:

Since the update of Factory to GCC 4.7, the YaST software management system has not been working anymore. I have seen numerous bug reports on this, but it seems as if the YaST maintainers are pointing to the Zypp Team.

So instead of working together and providing a solution for this, we as users are still stuck with a non working Software Management system. Despite that we have already reached the 12.2 Beta 1 milestone.

Are we really expecting from our users that they will fall-back to a command line tool with reduced functionality ?? I think this is the biggest Show- Stopper that openSUSE 12.2 has at the moment and I really hope that the YaST and Zypper teams getting their acts together and providing a working solution before 12.2 is released. It would be really strange to see a release without the possibility to update the system properly.

I apologize for the tone of the message, but I am really getting pissed off with the current situation around YaST and if this is not resolved soon, then my system for one will never see the official release of 12.2.

What bug reports have you filed? Did you supply proper debugging information? For me, both YaST and zypper mostly work, thus it is important that tose people with problems file good reports. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sat, Jun 2, 2012 at 3:19 PM, Raymond Wooninck wrote:

Are we really expecting from our users that they will fall-back to a command line tool with reduced functionality ??   I think this is the biggest Show- Stopper that openSUSE 12.2 has at the moment and I really hope that the YaST and Zypper teams getting their acts together and providing a working solution before 12.2 is released. It would be really strange to see a release without the possibility to update the system properly.

I remember reading on the list that if the problems weren't resolved by release time, they'd switch to the older gcc for zypper/yast, essentially solving the problem by default. So as long as good bug reports show the failings, the final release should be OK (though I guess a beta2/rc would be nice to have, built with an older gcc, to make sure it's indeed fixed). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2 June 2012 19:59, Raymond Wooninck wrote:

Larry, There are a number of bug reports with regards to this issue. I do not believe that creating another one would resolve the situation.

Then list them, please.

If I run zypper, then the system refuses to update a number of packages without giving me a reason why. I do not even get a choice what to do in

You mean the "The following package updates will NOT be installed:" list that has been in zypper for a few releases already? That's not a bug. It's just the difference between "zypper lu" and "zypper lu -a".

certain cases. YaST software management indicated that (with a Update All packages if newer exist), that it wants to update 194 packages. Something that zypper doesn't even indicate. YaST starts then to work and shortly after it

"Update All packages if newer exist" is "zypper lu -a". Really, bug reports and good descriptions (copy & paste of commands) is the only way to go. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sat, 2 Jun 2012 20:29:11 +0100 Alin Marin Elena wrote:

https://bugzilla.novell.com/show_bug.cgi?id=759433

And here's another. Came across the same problem today. https://bugzilla.novell.com/show_bug.cgi?id=763779 -- Graham Davis, Bracknell, Berks. openSUSE 12.1 (64-bit); KDE 4.8.3; AMD Phenom II X2 550 Processor; Video: nVidia GeForce 210 (using nVidia driver); Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 02/06/12 14:59, Raymond Wooninck escribió:

If I run zypper, then the system refuses to update a number of packages without giving me a reason why.

That has been already fixed, it was a bug in libsolv. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Saturday, June 02, 2012, Cristian Rodríguez wrote:

El 02/06/12 15:26, Alin Marin Elena escribió:

...

now with the switch to gcc 4.7 turns out zypper and yast sw are not very portable... Personally I think this looks bad on sles/sled too... professional written software not portable to the latest standard of c++.

Software has bugs, and does not have to be portable, zypp is a *linux* package manager.

Compilers also have bugs.

We will all agree with the fact that Software has bugs. This goes hand in hand. Software without bugs is non-existent. However YaST has been the piece of software that made openSUSE to be openSUSE. The Package manager is one of the core components of a linux system and has the function to keep the system up to date with newer versions or to provide an interface to the user to install new software. And exactly this has currently a big portability bug due to the GCC 4.7 upgrade. And this is what Alin tried to indicate. Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Saturday, June 02, 2012, Alin Marin Elena wrote:

...

...

If I run zypper, then the system refuses to update a number of packages without giving me a reason why.

That has been already fixed, it was a bug in libsolv.

With the current versions in Factory, zypper still silently refuses updates to install. I have the Mozilla Firefox Beta repository active and when I run zypper up, I see MozillaFirefox as a possible update but it is listed in the category "The following packages updates will not be installed". I don't get any reasoning why until I run zypper up MozillaFirefox and then I get the options. Those options I am also expecting to see when I just run a zypper up (as I did in YaST with update all where newer). Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 02.06.2012 20:19, schrieb Raymond Wooninck:

Since the update of Factory to GCC 4.7, the YaST software management system has not been working anymore. I have seen numerous bug reports on this, but it seems as if the YaST maintainers are pointing to the Zypp Team.

...and they are probably right, as zypper also did not work reliably.

So instead of working together and providing a solution for this, we as users are still stuck with a non working Software Management system. Despite that we have already reached the 12.2 Beta 1 milestone.

instead of polemic mails, how about providing useful bugreports? https://bugzilla.novell.com/show_bug.cgi?id=761873 looks like it might have helped.

I apologize for the tone of the message, but I am really getting pissed off with the current situation around YaST and if this is not resolved soon,

Guess what? I was annoyed too. But instead of wasting everybody's time with emails, I installed debuginfo and tried to help fix the problem. Did you provide a coredump of your failing yast in a bugreport? Everyone can do that. It's not magic. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am Samstag, 2. Juni 2012, 23:28:21 schrieb Stefan Seyfried:

instead of polemic mails, how about providing useful bugreports?

Fass Dir an die eigene Nase!

Guess what? I was annoyed too. But instead of wasting everybody's time with emails, I installed debuginfo and tried to help fix the problem.

Did you provide a coredump of your failing yast in a bugreport? Everyone can do that. It's not magic.

If you'd know Raymond and considered his contribution you would have kept your comments to yourself. Further, getting that defensive just shows that he hit the right spot. It's a shame that just because some trolls used this list for polemics justified criticism is answered with defensive polemics rather than acknowledging that things might not work the way they should. Sven -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sat, 2012-06-02 at 20:05 -0400, Ken Schneider - openSUSE wrote:

Try:

zypper up <name of package it says will not be updated>

for further info on why.

I already know the answer to that, its because updates are in a lower-priority repository. And I can understand why that happens, though I think it could be done in a better way. My point in my question wasn't why. It was questioning the functionality of lu -a. The OP said running lu -a would update all newer packages, and that didn't make sense to me given the definition of "lu". But I was rather curious because I've seen others say to use lu -a as well, yet when I tried it (out of curiosity), it didn't work for me that way. :-) Bryen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 03.06.2012 10:38, schrieb Graham P Davis:

On Sun, 03 Jun 2012 03:15:40 +0530 "phanisvara das" wrote:

...

On Sun, 03 Jun 2012 00:59:11 +0530, Alin Marin Elena wrote:

...

https://bugzilla.novell.com/show_bug.cgi?id=759433

It's marked "resolved" *because* it has been marked as a duplicate. If

Well, now it is "reopened" and this means nobody will find the bug which is really worked at...

you check the bug of which it has been marked as a duplicate, I think you'll find it still active.

The one it was dup'ed to actually was "resolved fixed" but got reopened by me after I could still find a (different actually) crash and supply information that will hopefully be useful to track the cause (coredump, valgrind logs). https://bugzilla.novell.com/761873 -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sun, 03 Jun 2012 14:08:56 +0530, Graham P Davis wrote:

It's marked "resolved" *because* it has been marked as a duplicate. If you check the bug of which it has been marked as a duplicate, I think you'll find it still active.

the duplicate one used to be closed, but has been reopened, too. i only experience these crashes with yast, not with zypper, so i'm not reporting to that other one; quite possibly it's the same though. -- phani. -- Using Opera's revolutionary email client: http://www.opera.com/mail/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org