This patch series implements upgrades in raw disks images. You can test it by adding the follow lines to the upgrade_image method
fo = open(os.path.join(temp_root, "etc", "hostname"), "w")
and then run "morph deploy" on an existent raw image, convert the raw image to a virtual disk image and verify on a new VM that the hostname had changed.
Tiago Gomes (2):
Allow installing extlinux to other system versions.
Implement raw disk upgrades.
morphlib/exts/rawdisk.write | 52 +++++++++++++++++++++++++++++++++++++++----
morphlib/writeexts.py | 8 +++----
2 files changed, 52 insertions(+), 8 deletions(-)
I think this is probably useful for Baserock's automated testing.
-------- Original Message --------
Subject: Announce: Wayland Functional Integration Test Suite
Date: 2013-05-22 14:56
From: "Eoff, Ullysses A" <ullysses.a.eoff(a)intel.com>
Copy: "gtk-devel-list(a)gnome.org" <gtk-devel-list(a)gnome.org>,
"Enlightenment developer list
I wanted to announce that a new open source project called
"wayland-fits" is now available on 01.org <https://01.org/wayland>.
The Wayland Functional Integration Test Suite (wayland-fits) is a fully
automated test suite. Its purpose is to validate the functionality and
integration between Wayland client software and Wayland server
software. It provides a test framework and test suites for multiple
Wayland-enabled toolkits and the Wayland core. The test framework
allows tests to emit input events from the bottom of the software
That is, [input system]->server->client->toolkit->test-app. This
enables full input pipeline validation. It also includes its own
test protocol that enables tests to cross-validate client and server
Currently there are tests for Wayland Core and Wayland EFL. And just
recently, I have started adding tests for Wayland Gtk+ (I'm already
finding several trivial bugs). There are plans to start adding tests
Wayland Clutter and Wayland Qt, too. Also, a server-side
implementation of the wayland-fits protocol is essential for every test
to execute. Right now, there is only an implementation for Weston
included that supports drm, x11, and headless backends (caution: the
headless backend will only run the software/shm based tests). It's
absolutely plausible, however, that there will be implementations for
other Wayland compositors that have a plugin architecture, too.
I am currently the maintainer of this project with contributions
coming in from one or two other people on occasion. I would be
oh-so-grateful to have more contributors from the enthusiastic Wayland
community. So start sending your patches! I only develop and
test on Intel hardware and Fedora... so if there are issues on other
hardware/OS flavors, feel free to submit fixes; tested, of course ;-).
There is still a lot of Wayland functionality that is not tested by
and design decisions that could be made...and I could use as much help
as I can get. If nothing else, I hope it's a useful test suite for
that use it. It has already detected many regressions and bugs.
The source repository is on github at:
There is more information in the README about contributing, building,
running, etc... Also, we can start using the wiki in the github
share more info (and such) as needed.
If you have any questions, feel free to drop me a line. I generally
in the #wayland and #wayland-efl IRC channels on freenode as some of
you already know (nick: uartie). I am travelling this week so expect a
Oh, and P.S. the project is written in C++ ;-)
U. Artie Eoff
Intel Open Source Technology Center
gtk-devel-list mailing list
I have tested this as a basic program, but have not tried it in
an actual deployment.
Jonathan Maw (1):
Write install-files configuration extension
install-files.configure | 109 +++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 109 insertions(+)
create mode 100755 install-files.configure
An accompanying branch exists in baserock:baserock/morphs.
This should be merged with other build essential changes
to reduce full-rebuilds.
Richard Maw (1):
Add fortran to the list of languages built
gcc.morph | 5 +++--
gcc.morph.yaml | 7 ++++++-
2 files changed, 9 insertions(+), 3 deletions(-)
Upgrades are handled by the developer specifying a name for
that version. The extension will push copy the files under
that extension and update the symlinks to point to the new
Jonathan Maw (2):
Can define version by the environment variable 'VERSION'
nfsboot deployment creates local state dirs
morphlib/exts/nfsboot.write | 23 ++++++++++++++++++++++-
1 file changed, 22 insertions(+), 1 deletion(-)
Bash builds successfully whether readline is
present or not, and seems to use a version of
readline that is included with the source code if
no readline is present.
Jonathan Maw (1):
core.morph | 12 +-----------
1 file changed, 1 insertion(+), 11 deletions(-)