http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c yang xiaoyu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |jsrain@novell.com |ovo.novell.com | -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c2 Larry Finger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|Larry.Finger@lwfinger.net | --- Comment #2 from Larry Finger 2010-03-10 14:36:00 UTC --- Created an attachment (id=347618) --> (http://bugzilla.novell.com/attachment.cgi?id=347618) YaST log This log includes part of the time period of the problem. The update was started on March 7, and appeared to hang at 23:00 local time. I allowed it to try all night, then stopped it at 10:00 on March 8. After repairing the GRUB script as described in the initial bug report, I was able to boot the system. At roughly 11:30 on March 8, I again booted the NET install CD and again attempted an upgrade. At this time, it only needed to upgrade a single package, and then was able to finish and reboot into the 11.3M3 system. The hang/infinite loop happened when it was updating the bootloader. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c4 --- Comment #4 from Larry Finger 2010-03-17 15:52:22 UTC --- Unfortunately, no. I have tried several times since and it completed every time. That partition is only used for testing, thus I will do an 11.2 installation there and retry the upgrade to 11.3M3. As that involves taking my main computer off line, it will be a while until that happens. In the meantime, I will try the same with a VirtualBox VM. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c6 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Larry.Finger@lwfinger.net --- Comment #6 from Jiri Srain 2010-03-18 15:58:54 UTC --- grabbing the logs meant to tar-up the whole /var/log/YaST2 and /mnt/var/log/YaST2 directories, taring them and attaching to bzilla. This way I get logs from installation system (which did not get copied to hard disk because of the freeze). -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c8 --- Comment #8 from Larry Finger 2010-03-18 17:15:33 UTC --- Created an attachment (id=349273) --> (http://bugzilla.novell.com/attachment.cgi?id=349273) Tar archive of /mnt/var/log/YaST2 -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c10 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Larry.Finger@lwfinger.net --- Comment #10 from Jiri Srain 2010-03-19 06:52:24 UTC --- Which 'bootloader' process? The last item in the log is checking existence and executing /boot/perl-BL_delayed_exec, is this the process you are mean? -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@novell.com |jreidinger@novell.com -- 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.

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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c15 --- Comment #15 from Michael Andres 2010-03-22 15:53:10 UTC --- (In reply to comment #14)

Then depend on type of bootloader I choose to use summary or shortname (limitations of some bootloaders). So single command which return string is not sufficient for me.

We could offer

Parsing of /etc/products.d/basesystem sounds easy for perl as it doesn't depend on any tool which can break bootloader update process (but can have problems when you change these informations). Question is if it breaks also SLE11SP1 as same solution is also implemented there - see bug 583034 for reasons

-- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c17 --- Comment #17 from Michael Andres 2010-03-22 15:59:38 UTC --- .. offer 2 lines with key/value pairs. But direct parsing is probably ok too, as the format of the product metadata is nothing we deliberately change in an incompatible way. And yes, SLE11SP1 may be affected the same way. You should fix it. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c21 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@novell.com AssignedTo|jreidinger@novell.com |jkupec@novell.com --- Comment #21 from Josef Reidinger 2010-03-23 09:41:19 UTC --- Fix for SP1 sent to ibs. Jano please add suggested call to zypper and then return bug to me and I change parsing zypper output. It should not need lock and should return both summary (normal and short) and I decide which one to use. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c23 --- Comment #23 from Michael Andres 2010-03-23 12:34:43 UTC ---

But it does not load repos, and does not need the global lock, which is the most important thing here, right?

Important is that it does not launch the repos, nor loads the target resolvables. If 'God' in your example is ZYpp, then your code crates a lock and initializes the target (rpm database and gpg keys). Target also contains static versions for all baseproduct related methods. They don't init anything, just parse the baseproduct file. Target::targetDistribution( const Pathname & root_r )

Bootloader needs the values returned by Product::shortName() and Product::summary().

I could offer a std::pairstd::string,std::string Target::distributionLabel( root_r ); This would fit to distributionVersion and distributionFlavor which already exist. The std::pair would return Zypper could then write them as two lines, or as key/value pairs. The later is probably easier to understand in case one of the strings is empty. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c25 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ma@novell.com | --- Comment #25 from Michael Andres 2010-03-23 14:46:41 UTC --- @Josef: Do you actually need both values , or would it be sufficient to return just the shortName, and fall back to the label if shortName, is empty? -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c26 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jreidinger@novell.com | --- Comment #26 from Josef Reidinger 2010-03-23 14:56:52 UTC --- (In reply to comment #25)

@Josef: Do you actually need both values , or would it be sufficient to return just the shortName, and fall back to the label if shortName, is empty?

No I need both, as grub allows long names and it is preffered to have there long names, but elilo, plilo, zipl or lilo doesn't allow so long names with spaces. So I look which one user currently use and create name. If anything is empty and I handle it in some fallback, so it is not problem, if you return empty value for some value. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c28 --- Comment #28 from Ján Kupec 2010-03-23 16:47:13 UTC --- What about $ zypper tos --label long=Beautiful Name short=BN The same for the DistributionLabel struct and <<. Summary and shortName do not fit in 'label'. Label does not have summary or name, but it can have short and long version. What do you think? -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c30 --- Comment #30 from Josef Reidinger 2010-03-24 07:20:18 UTC --- (In reply to comment #29)

Or even better (in the spirit of normal output, --xmlout, and --terse):

$ zypper tos --label Distribution label: Beautiful Name Short Version: BN (for humans, translated)

$ zypper --terse tos --label long=Beautiful Name short=BN (for machines)

$ zypper --xmlout tos --label <distribution id="beautifulDistro-3-x86_64" label="Beautiful Name" short_label="BN"/> (for xml-loving machines)

sounds good for me. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c32 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jkupec@novell.com |jreidinger@novell.com --- Comment #32 from Ján Kupec 2010-03-26 12:00:00 UTC --- $ zypper tos -l Distribution Label: openSUSE Short Label: $ zypper -t tos -l labelLong openSUSE labelShort (it's \t between labelLong and openSUSE). Unfortunately i can't change simple 'zypper tos' to show "Distribution ID: openSUSE-11.2-x86_64" and the --terse version just "openSUSE-11.2-x86_64" for the sake of backward compatibility. But any new features should follow the normal/terse/xml output approach. Done in zypper 1.4.1, will submit the package later today. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c34 --- Comment #34 from Josef Reidinger 2010-03-26 16:56:14 UTC --- Larry - thanks for retest Jano - thanks, I wait when it gets to factory and switch for opensuse to zypper output. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=586303 http://bugzilla.novell.com/show_bug.cgi?id=586303#c35 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #35 from Josef Reidinger 2010-04-09 14:42:35 UTC --- new zypper just submitted to factory use zypper --terse tos -l -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=586303 https://bugzilla.novell.com/show_bug.cgi?id=586303#c37 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:11.2:32913 |maint:released:11.2:32913 | |maint:running:37855:importa | |nt --- Comment #37 from Swamp Workflow Management 2010-12-17 11:59:24 UTC --- The SWAMPID for this issue is 37855. This issue was rated as important. Please submit fixed packages until 2010-12-24. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/37855 -- 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.