Who turned out the light - GNOME Classic - DesktopNames

[poma]

On 22.07.2014 21:34, poma wrote:
> On 22.07.2014 21:25, poma wrote:
>> On 22.07.2014 20:32, poma wrote:
>>> On 22.07.2014 15:26, Matthias Clasen wrote:
>>>> On Sat, 2014-07-19 at 09:17 +0200, poma wrote:
>>>>
>>>>>> For Fedora purposes we treat GNOME Shell and GNOME Classic as two
>>>>>> separate desktops; Classic has approximately the same status as Xfce or
>>>>>> LXDE, we ship it and some people use it, but we don't guarantee testing
>>>>>> or require it to meet specific standards to ship.
>>>>>>
>>>>>
>>>>> I was referring to the technical aspect of it.
>>>>> If anything it's good to know.
>>>>>
>>>>
>>>> GNOME Classic gets the same automatic smoketesting upstream as GNOME,
>>>> and seems to be working just fine:
>>>>
>>>> http://build.gnome.org/continuous/buildmaster/builds/2014/07/22/28/smoketest-classic/work-gnome-continuous-x86_64-runtime/screenshot-final.png
>>>>
>>>
>>> Unable to complete install: 'invalid argument: Backing file '/srv/ostree/ostbuild/work/images/current/gnome-continuous-x86_64-runtime.qcow2' of image '/pool/testoverlay-gnome-continuous-x86_64-runtime.qcow2' is missing.'
>>>
>>> Traceback (most recent call last):
>>>       File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper
>>>         callback(asyncjob, *args, **kwargs)
>>>       File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install
>>>         guest.start_install(meter=meter)
>>>       File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install
>>>         noboot)
>>>       File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest
>>>         dom = self.conn.createLinux(start_xml or final_xml, 0)
>>>       File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux
>>>         if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
>>> libvirtError: invalid argument: Backing file '/srv/ostree/ostbuild/work/images/current/gnome-continuous-x86_64-runtime.qcow2' of image '/pool/testoverlay-gnome-continuous-x86_64-runtime.qcow2' is missing.
>>>
>>> How do I test this?
>>>
>>
>> # file testoverlay-gnome-continuous-x86_64-runtime.qcow2
>> testoverlay-gnome-continuous-x86_64-runtime.qcow2: QEMU QCOW Image (v2), has backing file (path /srv/ostree/ostbuild/work/images/current/gnome-continuous-x86_6), 8589934592 bytes
>>
>> # qemu-kvm testoverlay-gnome-continuous-x86_64-runtime.qcow2
>> qemu-system-x86_64: -machine accel=kvm: could not open disk image testoverlay-gnome-continuous-x86_64-runtime.qcow2: No such file or directory
>>
>> # qemu-kvm -monitor stdio -vnc :0 -vga std -drive file=testoverlay-gnome-continuous-x86_64-runtime.qcow2,if=virtio -m 768M -usb
>> qemu-system-x86_64: -drive file=testoverlay-gnome-continuous-x86_64-runtime.qcow2,if=virtio: could not open disk image testoverlay-gnome-continuous-x86_64-runtime.qcow2: No such file or directory
>>
>
> $ gnome-boxes
>
> (gnome-boxes:23034): Boxes-CRITICAL **: boxes_spice_display_construct: assertion '(_tmp0_ != 0) || (_tmp1_ != 0)' failed
>
> (gnome-boxes:23034): Boxes-CRITICAL **: boxes_spice_display_construct: assertion '(_tmp0_ != 0) || (_tmp1_ != 0)' failed
>
> (gnome-boxes:23034): Boxes-CRITICAL **: boxes_spice_display_construct: assertion '(_tmp0_ != 0) || (_tmp1_ != 0)' failed
>
> (gnome-boxes:23034): Boxes-CRITICAL **: boxes_spice_display_construct: assertion '(_tmp0_ != 0) || (_tmp1_ != 0)' failed
>
> (gnome-boxes:23034): Boxes-WARNING **: vm-importer.vala:47: Failed to import box 'GNOME 3.10' from file '/pool/testoverlay-gnome-continuous-x86_64-runtime.qcow2': Failed to execute: qemu-img convert -O qcow2 /pool/testoverlay-gnome-continuous-x86_64-runtime.qcow2 /home/virtio/.local/share/gnome-boxes/images/gnome-continuous-3.10
>

OK, I tested with the "real" image
# file gnome-continuous-x86_64-runtime-20140722.30.qcow2
gnome-continuous-x86_64-runtime-20140722.30.qcow2: QEMU QCOW Image (v2), 8589934592 bytes

https://wiki.gnome.org/Projects/GnomeContinuous
http://build.gnome.org/ostree/buildmaster/images/z/current/
http://build.gnome.org/continuous/buildmaster/images/z/current/

However what's the point now, after more than two months and how it can help us here?


poma