Bug 169694 - YaST doesn't detect changed PPDs
Summary: YaST doesn't detect changed PPDs
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 2
Hardware: All SuSE Linux 10.1
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Michal Zugec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-26 11:54 UTC by Johannes Meixner
Modified: 2008-06-25 09:56 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Meixner 2006-04-26 11:54:07 UTC
See
https://bugzilla.novell.com/show_bug.cgi?id=164991#c7

I updated manufacturer-PPDs and hplip to have the fixed PPDs
installed and YaST shows the popup about re-build of its
printer database and theer was ineed a new model
"LaserJet 5Si MX" but nevertheless I still got a PostScript PPD
when I selected the "LaserJet 5Si".

After "rm /var/lib/YaST2/ppd_db.ycp" it worked (i.e. no
PostScript PPD for the "LaserJet 5Si").

Therefore I assume something is wrong with the
"model name -> PPD files" mapping when PPDs change.
I guess that obsolete relations "model name -> PPD file"
are not removed.
Comment 4 Michal Zugec 2006-07-28 12:43:28 UTC
later
Comment 5 Stephan Kulow 2008-06-25 09:38:24 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:39:40 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 7 Stephan Kulow 2008-06-25 09:43:01 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 8 Stephan Kulow 2008-06-25 09:56:03 UTC
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(