[opensuse-security] What's the matter with the updates?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 YOU says it wants to update: bug-buddy java-1_5_0-sun java-1_6_0-sun updates-alternatives Knowing about last Friday problem, I'm suspicious - and yes, there are conflicts again: #### YaST2 conflicts list - generated 2007-11-20 01:20:48 #### Cannot install java-1_6_0-sun-plugin, because it is conflicting with java-1_5_0-sun-plugin A conflict over java-1.3.1-plugin (java-1.3.1-plugin) requires the removal of java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] which is scheduled for installation === java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] === java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] is needed by atom:java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (java-1_6_0-sun-plugin >= 1.6.0.u3-0.5) sed-4.1.5-64.i586 is needed by java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (sed == 4.1.5-64) findutils-4.2.31-24.i586 is needed by java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (/usr/bin/find) === java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] === java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] is needed by atom:java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] (java-1_5_0-sun-plugin >= 1.5.0_update13-0.5) (null) Conflict Resolution: ( ) do not install java-1_6_0-sun-plugin ( ) do not install java-1_5_0-sun-plugin (X) Ignore this conflict of java-1_6_0-sun-plugin atom:bug-buddy cannot be installed due to missing dependencies There are no installable providers of bug-buddy >= 2.20.1-1.1 for atom:bug-buddy-2.20.1-1.1.i586[gwdg-update] === atom:bug-buddy-2.20.1-1.1.i586[gwdg-update] === atom:bug-buddy-2.20.1-1.1.i586[gwdg-update] is needed by patch:bug-buddy-4686-0.noarch[gwdg-update] (bug-buddy == 2.20.1-1.1) bug-buddy-2.20.1-1.1.i586[gwdg-update] provides bug-buddy == 2.20.1-1.1, but it is uninstallable. Try installing it on its own for more details. (null) Conflict Resolution: (X) do not install bug-buddy ( ) Ignore this requirement just here #### YaST2 conflicts list END ### And I try again, and I get the same conflict with a different text, impossible to understand unless you are a Yast programmer :-( #### YaST2 conflicts list - generated 2007-11-20 01:23:12 #### Cannot install java-1_6_0-sun-plugin, because it is conflicting with java-1_5_0-sun-plugin A conflict over java-1.4.2-plugin (java-1.4.2-plugin) requires the removal of java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] which is scheduled for installation === java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] === java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] is needed by atom:java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (java-1_6_0-sun-plugin >= 1.6.0.u3-0.5) sed-4.1.5-64.i586 is needed by java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (sed == 4.1.5-64) findutils-4.2.31-24.i586 is needed by java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (/usr/bin/find) === java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] === java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] is needed by atom:java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] (java-1_5_0-sun-plugin >= 1.5.0_update13-0.5) (null) Conflict Resolution: ( ) do not install java-1_6_0-sun-plugin ( ) do not install java-1_5_0-sun-plugin (X) Ignore this conflict of java-1_6_0-sun-plugin patch:bug-buddy cannot be installed due to missing dependencies There are no installable providers of bug-buddy == 2.20.1-1.1 for patch:bug-buddy-4686-0.noarch[gwdg-update] === patch:bug-buddy-4686-0.noarch[gwdg-update] === patch:bug-buddy-4686-0.noarch[gwdg-update] will be installed by another application. (ApplLow/ApplHigh) atom:bug-buddy-2.20.1-1.1.x86_64[gwdg-update] is needed by patch:bug-buddy-4686-0.noarch[gwdg-update] (bug-buddy == 2.20.1-1.1) atom:bug-buddy-2.20.1-1.1.ppc[gwdg-update] is needed by patch:bug-buddy-4686-0.noarch[gwdg-update] (bug-buddy == 2.20.1-1.1) atom:bug-buddy-2.20.1-1.1.i586[gwdg-update] provides bug-buddy == 2.20.1-1.1, but it is locked. (null) Conflict Resolution: ( ) unlock bug-buddy ( ) unlock all resolvables (X) do not install bug-buddy ( ) Ignore this requirement just here #### YaST2 conflicts list END ### So I answer the same thing as before, and get a third conflict: #### YaST2 conflicts list - generated 2007-11-20 01:25:45 #### Cannot install java-1_6_0-sun-plugin, because it is conflicting with java-1_5_0-sun-plugin A conflict over java-1.4.1-plugin (java-1.4.1-plugin) requires the removal of java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] which is scheduled for installation === java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] === java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] is needed by atom:java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (java-1_6_0-sun-plugin >= 1.6.0.u3-0.5) sed-4.1.5-64.i586 is needed by java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (sed == 4.1.5-64) findutils-4.2.31-24.i586 is needed by java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (/usr/bin/find) === java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] === java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] is needed by atom:java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] (java-1_5_0-sun-plugin >= 1.5.0_update13-0.5) (null) Conflict Resolution: ( ) do not install java-1_6_0-sun-plugin ( ) do not install java-1_5_0-sun-plugin (X) Ignore this conflict of java-1_6_0-sun-plugin #### YaST2 conflicts list END ### I get the same, and I answer the same: #### YaST2 conflicts list - generated 2007-11-20 01:26:40 #### Cannot install java-1_6_0-sun-plugin, because it is conflicting with java-1_5_0-sun-plugin A conflict over java-1.4.0-plugin (java-1.4.0-plugin) requires the removal of java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] which is scheduled for installation === java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] === java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] is needed by atom:java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (java-1_6_0-sun-plugin >= 1.6.0.u3-0.5) sed-4.1.5-64.i586 is needed by java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (sed == 4.1.5-64) findutils-4.2.31-24.i586 is needed by java-1_6_0-sun-plugin-1.6.0.u3-0.5.i586[gwdg-update] (/usr/bin/find) === java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] === java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] is needed by atom:java-1_5_0-sun-plugin-1.5.0_update13-0.5.i586[gwdg-update] (java-1_5_0-sun-plugin >= 1.5.0_update13-0.5) (null) Conflict Resolution: ( ) do not install java-1_6_0-sun-plugin ( ) do not install java-1_5_0-sun-plugin ( ) Ignore this conflict of java-1_6_0-sun-plugin #### YaST2 conflicts list END ### So, a third time I say to ignore, and this time it shuts up. Why is this nonsense? I should install both 1_5 and 1_6 patches: cer@nimrodel:~/.ssh> rpm -q java-1_6_0-sun-plugin java-1_5_0-sun-plugin java-1_6_0-sun-plugin-1.6.0.u3-0.3 java-1_5_0-sun-plugin-1.5.0_update13-0.3 but yast complains about conflicts, even if the initial screen says there are patches for both that I should apply. What is this all about? Finally, it says it is going to install: java-1_5_0-sun java-1_5_0-sun-plugin java-1_6_0-sun java-1_6_0-sun-alsa java-1_6_0-sun-jdbc java-1_6_0-sun-plugin updates-alternatives - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHQiuttTMYHG2NR9URAmCAAJoDgnwczaRlojPnITiJwaQ1eTfZwQCfdDlH FjreVByN6egkwUjcjCI4hBE= =U8/O -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
On Tue, Nov 20, 2007 at 01:34:40AM +0100, Carlos E. R. wrote:
YOU says it wants to update:
bug-buddy java-1_5_0-sun java-1_6_0-sun updates-alternatives
Knowing about last Friday problem, I'm suspicious - and yes, there are conflicts again:
This has nothing to do with last fridays problem. bug-buddy is already known and we have a fix waiting. The java conflict is new to me and I have not seen it during my tests. It seems that you have both java-1_5_0-sun-plugin and java-1_6_0-sun-plugin installed, right? How did you install them? Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-11-20 at 08:15 +0100, Marcus Meissner wrote:
On Tue, Nov 20, 2007 at 01:34:40AM +0100, Carlos E. R. wrote:
YOU says it wants to update:
bug-buddy java-1_5_0-sun java-1_6_0-sun updates-alternatives
Knowing about last Friday problem, I'm suspicious - and yes, there are conflicts again:
This has nothing to do with last fridays problem.
I know, I mean they have me in red alert condition :-p
bug-buddy is already known and we have a fix waiting.
Ok.
The java conflict is new to me and I have not seen it during my tests.
It seems that you have both java-1_5_0-sun-plugin and java-1_6_0-sun-plugin installed, right? How did you install them?
No idea. I think it's a condition inherited from 10.2 where both were installed, 1_6 partially, because both were pulled in by dependencies from different packages. In 10.3 I think I had 1_5, it stoppped working last week, something missing (precissely what this patch was supposed to mend, I guess), so I told it to uninstall and install 1_6 instead. Perhaps it was not fully uninstalled and yesterday it wanted to complete both 1_5 and 1_6. I'll try to remove 1_5 fully in a moment. [...] Done, it didn't complain this time. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHQsHDtTMYHG2NR9URAsLkAJ4yni8excOBSIpnvaBydMmJ23xbRQCfahCA HTqOgV2xw7m0w3z/YXu7UHA= =AGoy -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
Hi, Recently I upgraded from Open Suse 10.2 to 10.3, hoping for faster updates than I had with ZMD. This became true, but I have to manually start the network interfaces (ifup eth0 etc) and then I have to start OpenSue updater by hand. The cause of the problem is that Suse does not start my networkinterfaces. As I have upgraded Suse since I started with Suse Professional 8.0 and never ever had such a weird problem, I was not expecting this at all. The only way to overcome this is to enable knetworkmanager. This starts my first networkinterface, but not the other two. When ifup (the traditional way) is specified in Yast, the network interfaces don't start, and hence SuseUpdater always tells me there are no updates available, even after enabling eth0 manually. On the same machine a fresh install of Suse 10.3 solves this problem, but then I miss all that I have installed over the years. Knetworkmanager is kind of a solution, but I hope someone has a better suggestion for me. Regards, Marc --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-11-25 at 16:12 +0100, m.van.munnen@hccnet.nl wrote:
On the same machine a fresh install of Suse 10.3 solves this problem, but then I miss all that I have installed over the years.
Compare the new install to the updated one, and move over the changes. Look under /etc/sysconfig/network.
Knetworkmanager is kind of a solution, but I hope someone has a better suggestion for me.
Insufficient data. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHSg+XtTMYHG2NR9URAovuAJ9DduJlhl5v/OelT15FFA6JQJ/q7wCeI9ot ooptEljz+Ti/Gg6zyTFC34o= =5qsB -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
I don't think this is a "security" related posting. But for what it's worth, I constantly have to keep restarting rcnetwork manually to get my nic's to wake up and grab ip's. it's been like that for ages, i am used to it. i always keep an console open for just that. On Nov 25, 2007 10:12 AM, <m.van.munnen@hccnet.nl> wrote:
Hi,
Recently I upgraded from Open Suse 10.2 to 10.3, hoping for faster updates than I had with ZMD. This became true, but I have to manually start the network interfaces (ifup eth0 etc) and then I have to start OpenSue updater by hand. The cause of the problem is that Suse does not start my networkinterfaces. As I have upgraded Suse since I started with Suse Professional 8.0 and never ever had such a weird problem, I was not expecting this at all.
The only way to overcome this is to enable knetworkmanager. This starts my first networkinterface, but not the other two.
When ifup (the traditional way) is specified in Yast, the network interfaces don't start, and hence SuseUpdater always tells me there are no updates available, even after enabling eth0 manually.
On the same machine a fresh install of Suse 10.3 solves this problem, but then I miss all that I have installed over the years.
Knetworkmanager is kind of a solution, but I hope someone has a better suggestion for me.
Regards, Marc
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
-- cheers, dg Darko Gavrilovic, CISSP http://www.linkedin.com/in/darkog --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
participants (4)
-
Carlos E. R. -
darko g -
m.van.munnen＠hccnet.nl -
Marcus Meissner