[Bug 777403] New: Document what openSUSE needs from repo-md format and expand it for 12.3
https://bugzilla.novell.com/show_bug.cgi?id=777403 https://bugzilla.novell.com/show_bug.cgi?id=777403#c0 Summary: Document what openSUSE needs from repo-md format and expand it for 12.3 Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: christian.morales.vega@gmail.com QAContact: lrupp@suse.com Found By: --- Blocker: --- openSUSE needs some information from the repo metadata that can't be included in repo-md. All the requisites should be documented and then the changes proposed upstream. To start with: - It needs an unique id. I don't know what 1-Click currently does to detect duplicates (just the name?). But it's frequent to find users in the forums with duplicated repositories configured. If the repo metadata had an unique id this could be avoided. There is still the problem of YaST vs repo-md here. But whatever feature only available in the YaST format should be added to repo-md and then stop using the YaST format for good. - It needs to reference the distro version We need some identifier to see if a repo is for the current running distro. It should not be hardly enforced. But zypper could should a warning if the user tries to add a repo for a different distribution. Probably the OBS will need an "attribute" so packagers can set it in complicated cases where it's not obvious and a possible autodetection fails. But that's the minor of the problems. Too many users get confused for things like "http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_12.2..." where the URL contains both "Factory" and "12.2". - It needs high level metadata PackageKit wants to know if it's a source/debug/development repository. Getting this information from the repository configured name is ugly and prone to break when the user decides to rename it (PackageKit's yum backend does exactly the same) Again, an attribute should be added to the OBS. Something else? What is missing that is available in YaST format? -- 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=777403 https://bugzilla.novell.com/show_bug.cgi?id=777403#c1 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@suse.com, mls@suse.com Component|Infrastructure |build process AssignedTo|zypp-maintainers@forge.prov |mls@suse.com |o.novell.com | Product|openSUSE.org |openSUSE Build Service QAContact|lrupp@suse.com |adrian@suse.com --- Comment #1 from Michael Andres <ma@suse.com> 2012-08-28 15:38:03 CEST --- (In reply to comment #0)
openSUSE needs some information from the repo metadata that can't be included in repo-md. All the requisites should be documented and then the changes proposed upstream.
I think this was implemented a few years ago. The repomd.xml <tags> section can provide such info and libsolv would parse it an put it into the .solv file. You can access them via libzypp. AFAIK the story ends here, as the build service does not provide any data (except <repo>). <tags> <repo>obsrepository://build.opensuse.org/openSUSE:12.2:Update/standard</repo> <distro cpeid="cpe://o:opensuse...">openSUSE 12.2</distro> <updates cpeid="cpe://o:opensuse...">openSUSE 12.2</updates> <content>updates</content> <content>stable</content> <content>morekeywords</content> </tags> See also http://lists.baseurl.org/pipermail/yum-devel/2008-October/005430.html and http://old-en.opensuse.org/Standards/RPM_metadata#Vendor_support_level_for_a... AFAIK the <updates> tag is not available upstream, but Michael (mls) might know better.
To start with:
- It needs an unique id.
This would be the <repo> tag.
- It needs to reference the distro version We need some identifier to see if a repo is for the current running distro.
Actually we'd need to check if a repo requires/supports a specific installed product or product family: via <distro> tag Question would be how to match <distro> tag and /etc/products.d entry.
- It needs high level metadata PackageKit wants to know if it's a source/debug/development repository.
<content> keywords -- 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=777403 https://bugzilla.novell.com/show_bug.cgi?id=777403#c Michael Schröder <mls@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mls@suse.com |coolo@suse.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=777403 https://bugzilla.novell.com/show_bug.cgi?id=777403#c2 --- Comment #2 from Cristian Morales Vega <christian.morales.vega@gmail.com> 2012-09-27 22:41:10 UTC ---
Question would be how to match <distro> tag and /etc/products.d entry.
I don't know the details about CPE. But I guess it would be just a matter of adding it to the product information and adding a method to zypp::Product to retrieve it? -- 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=777403 https://bugzilla.novell.com/show_bug.cgi?id=777403#c3 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #3 from Stephan Kulow <coolo@suse.com> 2013-02-06 11:26:30 CET --- As the build service guys obviously don't care, I don't care either. openSUSE uses susetags -- 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.
participants (1)
-
bugzilla_noreply＠novell.com