http://bugzilla.novell.com/show_bug.cgi?id=586303
http://bugzilla.novell.com/show_bug.cgi?id=586303#c13
Michael Andres changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
CC| |jkupec@novell.com,
| |ma@novell.com
InfoProvider|ma@novell.com |
--- Comment #13 from Michael Andres 2010-03-22 15:03:40 UTC ---
I think this has nothing todo with the "error: cannot open Packages data...'.
You basically call 'zypper --no-refresh ...' and then parse the zypper output
to figure out some label, right?
1) --no-refresh does not imply that no download will happen. If some enabled
repo has no metadata at all (e.g because it is newly created), the initial
download will take place. Maybe this is what hung. We'd need the zypper logs to
check this, OTOH the system is not yet completely updated, so you probably
should not do this at all.
2) Even if all matadata were fine; you let zypper load all repos, print the
product information, then grep for the baseproduct line and parse the summary
from the line. That's much ado.
- If you need to parse anyway, then you can also directly parse
/etc/products.d/baseproduct, completely avoiding the zypper overhead.
sed -n 's/.*<summary>\(.*\)<\/summary>.*/\1/p' /etc/products.d/baseproduct
- Libzypp already provides some methods to retrieve certain baseproduct values
without explicitly initializing the target. zypper uses them e.g. for 'zypper
tos'.
We can offer something similar for the bootloader, if you ask for it. Could be
called 'zypper bootlabel' or so.
Just ask Jano to implement the CLI and tell me which value(s) from the product
are needed. Then your code does not need to know anything about the products.d
entries, and you probably get the ready to use string out of zypper.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.