-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 15.08.2011 21:06, schrieb Larry Finger:

The purpose of this OBD is to test the open bugs reported for oS 11.4 to see which of them are still affecting 12.1.

I just had a look at http://en.opensuse.org/openSUSE:Open-Bugs-Day and all three of the steps under part 2 of "How" seem to be wrong in the context of retesting 11.4 bugs 2.1 would loose the information, that the bug is still in 11.4. Bugzilla can not have one bug for multiple versions - this is a known shortcoming of bugzilla. Either we could create a clone of the bug or we accept it, as nobody fixed it til now, so chances might be low that it would be fixed for 11.4. 2.2 is similar as 2.1 but cloning is not good here. Maybe best would be to just add the text "This has been fixed in 12.1." while leaving the status for 11.4 (unless it was also fixed there) 2.3 is worst as it suggests that 11.4 was out of support which is completely wrong. If it is hard to reproduce, maybe setting the bug to NEEDINFO from reporter, asking if he can still reproduce it on current 12.1 would be best. Opinions? Please discuss... Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk5MI/AACgkQSTYLOx37oWSxQQCeNe2+OxCy5VUB0lNFUtXzRV/W zcYAnjTIgw2gJDyHYq5Zg59fQAUO1X4y =BAXJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

On 08/17/2011 08:46 AM, Bernhard M. Wiedemann wrote:

Hi,

...

From yesterday's Factory Build0211 I have created two VM images that are 1GB compressed and 3.8GB uncompressed:

http://www5.zq1.de/img/obd3-gnome32.vmdk.xz http://www5.zq1.de/img/obd3-kde64.vmdk.xz Root PW is "linux" The gnome32 image uses LVM I adapted fstab, initrd and grub/menu.lst to not require virtio and tested both images with KVM and VirtualBox.

After downloading you can do img=obd3-gnome32.vmdk xz -cd $img.xz> $img

qemu-kvm -net user -net nic,model=virtio,macaddr=52:54:00:56:34:12 \ -drive file=$img,if=virtio,boot=on -m 1000 -usb -usbdevice tablet \ -monitor stdio -redir tcp:2222::22 -soundhw ac97

I did not try if VMware works.

I also snapshotted the Factory Build0211 repo to http://mirror.zq1.de/opensuse/factory/repo/oss/

but chances are that the fix for https://bugzilla.novell.com/show_bug.cgi?id=711760 goes into Factory this week which could allow for a new factory-tested snapshot.

I tested obd3-gnome32.vmdk. The load using qemu-kvm fails with no specific error being listed, but I was able to load it with VirtualBox using the following: Launch the VirtualBox GUI, and create a new machine with 1024 MB os RAM. When the GUI reaches the "Virtual Hard Disk" screen, select "Use existing hard disk", browse to the vmdk file, select it, and finish the VM setup. You can then boot the virtual machine. I plan on sending udated info to news@o.o and post a couple of places in the forums. Are we ready to publicize the URLs for the test material? My guess is not yet. Larry -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

On 08/17/2011 05:10 PM, Patrick Shanahan wrote:

* Bernhard M. Wiedemann [08-17-11 09:47]:

...

...

From yesterday's Factory Build0211 I have created two VM images that are 1GB compressed and 3.8GB uncompressed:

http://www5.zq1.de/img/obd3-gnome32.vmdk.xz http://www5.zq1.de/img/obd3-kde64.vmdk.xz Root PW is "linux" The gnome32 image uses LVM I adapted fstab, initrd and grub/menu.lst to not require virtio and tested both images with KVM and VirtualBox.

After downloading you can do img=obd3-gnome32.vmdk xz -cd $img.xz> $img

qemu-kvm -net user -net nic,model=virtio,macaddr=52:54:00:56:34:12 \ -drive file=$img,if=virtio,boot=on -m 1000 -usb -usbdevice tablet \ -monitor stdio -redir tcp:2222::22 -soundhw ac97

I dl'ed and expanded the disk image, created a vbox using the disk image as the drive. Booted ok but 800x600 display is not good and is the only option I can find.

What did I do wrong?

Do you have the VBox extension pack installed? With that installed, I set the GRUB options to 0x317 and got 1024x768. Larry -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 18.08.2011 03:42, schrieb Patrick Shanahan:

Yes, extension pack is installed. I set grub option to 0x345/0x31a/0x31b and get 1280x1024. Tks

But the VBox option to "Auto-resuze Guest Display" is checked and grayed-out. Other installs I can stretch the display and the vbox desktop matches. I can live with it but do not understand. ???

I think, this needs virtualbox-guest-x11 installed within the guest. Try zypper in virtualbox-guest-x11 virtualbox-guest-tools Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk5MqcYACgkQSTYLOx37oWQvJgCeKiLK+sCc8vqhxHa29Qytlb4w VrMAn19tHg0rLh044Y+W6IUS07SJggDM =0bPr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

* Bernhard M. Wiedemann [08-18-11 02:00]:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Am 18.08.2011 03:42, schrieb Patrick Shanahan:

...

Yes, extension pack is installed. I set grub option to 0x345/0x31a/0x31b and get 1280x1024. Tks

But the VBox option to "Auto-resuze Guest Display" is checked and grayed-out. Other installs I can stretch the display and the vbox desktop matches. I can live with it but do not understand. ???

I think, this needs virtualbox-guest-x11 installed within the guest. Try zypper in virtualbox-guest-x11 virtualbox-guest-tools

Unfortunately, both are already installed and the latest versions... tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org

Am Mittwoch, 17. August 2011, 22:26:24 schrieb Bernhard M. Wiedemann:

Am 15.08.2011 21:06, schrieb Larry Finger:

...

The purpose of this OBD is to test the open bugs reported for oS 11.4 to see which of them are still affecting 12.1.

I just had a look at http://en.opensuse.org/openSUSE:Open-Bugs-Day

and all three of the steps under part 2 of "How" seem to be wrong in the context of retesting 11.4 bugs

2.1 would loose the information, that the bug is still in 11.4. Bugzilla can not have one bug for multiple versions - this is a known shortcoming of bugzilla. Either we could create a clone of the bug or we accept it, as nobody fixed it til now, so chances might be low that it would be fixed for 11.4.

2.2 is similar as 2.1 but cloning is not good here. Maybe best would be to just add the text "This has been fixed in 12.1." while leaving the status for 11.4 (unless it was also fixed there)

2.3 is worst as it suggests that 11.4 was out of support which is completely wrong. If it is hard to reproduce, maybe setting the bug to NEEDINFO from reporter, asking if he can still reproduce it on current 12.1 would be best.

Opinions? Please discuss... Ciao Bernhard M.

2.1 cloning was what we agreed on. 2.2 maybe it is a good idea to retest the fix rather than adding blindly some comment. Do we switch the state for those than, if yes which? 2.3 NEEDINFO is the only state I can think of for those bugs Jürgen -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org