https://bugzilla.novell.com/show_bug.cgi?id=421735 Robert Vojcik changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |bnc-team-gnome@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=421735 User bluedzins@wp.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=421735#c3 Maciej Pilichowski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|bluedzins@wp.pl | --- Comment #3 from Maciej Pilichowski 2008-09-20 14:07:00 MDT --- I don't know where from because now I cannot simulate upgrade again -- I changed a lot of things in yast since then. I know that yast does not downgrade package -- I am saying it should not be blindly upgraded. The package should be kept even the "newer" version is available -- it was me, who downgraded packaged after such upgrade, so in result I get what I started with. "Newer" because yast algorithm is too naive -- it just checks package name too establish order, so some suffix (without dot or dash) can influence yast: https://bugzilla.novell.com/show_bug.cgi?id=421148 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=421735 User bluedzins@wp.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=421735#c5 Maciej Pilichowski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #5 from Maciej Pilichowski 2008-10-07 10:46:50 MDT --- Not, it is not covered. The problem is depending library -- it cannot be too old, it cannot be too new. Yast is not capable of figuring it out just from the air, and it won't be. It is task of writing good spec file. It is well known problem so I think it is time to solve it once for good, writing more specific, more exact spec file. This, and not yast, will solve the problem. After all, user does not have to use yast anyway, she/he can use directly rpm. Reopening of course. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=421735 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=421735#c7 --- Comment #7 from Tambet Ingo 2008-10-08 09:05:03 MDT --- Not an issue anymore, NM requires the latest libnl now, so I'll add 'libnl >= 1.1' requirement with the next submission. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=421735 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=421735#c9 --- Comment #9 from Tambet Ingo 2008-10-08 09:23:09 MDT --- "Libnl failed NM in the past, it failed now, so it is possible it will fail again." There's been exactly one occasion when this was happened. It is possible that it will happen again, but it's easier to change NM spec file then, rather than for every libnl release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=421735 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=421735#c11 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #11 from Tambet Ingo 2008-10-15 06:08:45 MDT --- I still feel it's not the right solution. Requiring exact libnl version will break NM with every libnl upgrade, while the current situation is that libnl upgrade sometimes breaks NM. I added more precise version check, hopefully the next time things break people use bugzilla instead of forums. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.