Bug 255642 - Update selection "never install" is forgotten
Summary: Update selection "never install" is forgotten
Status: RESOLVED DUPLICATE of bug 164445
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Jiří Suchomel
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-17 21:10 UTC by Volker Kuhlmann
Modified: 2007-03-21 18:15 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Yast2 logs (1.07 MB, application/x-bzip2)
2007-03-21 10:51 UTC, Volker Kuhlmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Volker Kuhlmann 2007-03-17 21:10:09 UTC
The recent agfa font package update contains no user-visible changes, therefore there is no need to install it. In yast, set the update-package to "never install". The red round stop sign icon shows next to the package. Other selected updates are installed during this invocation of YOU. With the next invocation of YOU, the "never install" setting for this package is forgotten. I have installed only the yast package management, none of the zmd-related packages.

With this font package it's not a real problem of course, but that's not the case with e.g. the last buggy kernel update.
Comment 1 Cyril Hrubis 2007-03-20 17:04:48 UTC
Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!
Comment 2 Volker Kuhlmann 2007-03-21 10:51:49 UTC
Created attachment 125660 [details]
Yast2 logs

YOU run 1: install OO updates, set agfa-fonts taboo.
YOU run 2: set fonts taboo again, click ok, nothing to install.

Older yast logs manually removed - one of them was over 400MB, and saving them ran over 10min on a fast computer. Please let me know if you need them afterall.
Comment 3 Jiří Suchomel 2007-03-21 18:15:35 UTC

*** This bug has been marked as a duplicate of bug 164445 ***