Bug 149933

Summary:	YaST2 metadata
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	First Name Last Name <sinderbox+novell>
Component:	YaST2	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Enhancement
Priority:	P5 - None	CC:	suse-beta
Version:	Beta 4
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description First Name Last Name 2006-02-10 12:58:01 UTC

It has always annoyed me to have full metadata for installed packages, but limited for non installed ones. More specifically package file lists.

It is very useful, for instance, when considering a new package for installation, tracing remains of badly deinstalled packages, or even for installing a package if one knows only a file name (how do I install /etc/DIR_COLORS or /etc/localtime? )

It would be a nice improvement for YaST repositories to provide file names natively as done by URPMI, APT-RPM, RPM-MetaData, and others.

More now when SuSE's apt-rpm is superceded by smart (with YaST2 respository support). That would make all the suse apt repositories obsolete/unneeded, push for a better use of resources, and unify suse users after only one repository type.  

The tools will need to be updated to support it (status should be RESOLVED LATER) but extending the repository format is trivial and nothing fancy...  just needs the file lists, with a good mapping between files and packages.

Comment 1 Michael Gross 2006-02-13 14:16:21 UTC

There is a tool called pin (Package INformation) which allows you to locate package names by single files also with non-installed packages.
At the moment, the packaging interface (and its underlaying system) is getting completely changed. I suggest you file this at a later point of time, let's say once 10.1 was released. In the meantime, pin should work for you ;)

Comment 2 First Name Last Name 2006-02-13 14:36:25 UTC

Michael, should I file this later or is automatically set for later checking?

Is it incorrect to fill now enhancements even if considered they will be better introduced later? As stated in my report this should go (if accepted) on 10.2
People might later forget or even not be around :) 

Thank you.

Comment 3 First Name Last Name 2006-02-14 20:39:23 UTC

Now that I learn that suse is planing to leave YaST2 repo in favor of YUM/repomd this is probably not an issue anymore.

Comment 4 Stephan Kulow 2008-06-25 09:35:35 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 5 Stephan Kulow 2008-06-25 09:37:43 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:42:12 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:53:37 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 ;(