On Tue, 18 Jun 2013 13:51:01 +0200 Alberto Planas Dominguez wrote: Hi Alberto, Thanks for your offer, but we actually already talked with Bernhard and already have image in openqa test image - http://openqa.opensuse.org/results/?sort=-mtime&hours=96&match=ruby&ob= We use it to provide useful image for testing ( We don't want to waste testers time, so start with automatic tests is good initial validation ). But it looks like it hit issue with slow ncurses start, so some tests fail. Now we look for more broad testing that is better done by hand as some issues can be quite hard to notice. Josef

Hi Ladislav,

I am Alberto from openSUSE. As you may know, you have big fans here for your work.

We just finished an iteration touching some components of Bernhard Wiedemann's openQA project. We found that his tool is very useful for us to test Factory, and we make some changes to make more robust tests.

We are going to download this ISO image and adapt some of the tests to use this new image. One of the good things about openQA is that have a broad set of different installation configurations. We have extended this initial set with USBOOT and UEFI/SB combinations, among new others.

These tests can't replace some manual tests, but I think that this can be a good initial coverage for this stage of the project.

Thanks for your effort, Alberto Planas.

Quoting Ladislav Slezak :

...

Hi all,

Long story short: Alternative Milestone 2 installation images with Ruby YaST created by the YCP Killer project are available here:

http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openSU... (~3.8GB)

http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openSU... (~860MB, only package subset, select "Minimal X" or "Textmode" software selection)

And here is the full story:

Introduction ------------

You might already know the YCP Killer project [1] by which we want to replace our specific YCP language used in YaST by Ruby.

The transition to Ruby is automated, we created a translator from YCP to Ruby and improved the core YaST so it can run Ruby modules.

Our goal is to switch all our YaST modules from YCP to Ruby in openSUSE-13.1.

The most critical part of YaST is the installer which cannot be easily updated on already released media. Therefore we need broader testing before this switch to avoid installation failures on large scale.

That's why we created alternative ISO images for installing openSUSE 13.1 Milestone 2 with YaST converted to Ruby.

Downloads ---------

We have two installation images with converted YaST installer, "fullDVD" which is basically the Milestone 2 DVD ISO and "miniDVD" which contains just a subset of packages needed for "Minimal X" installation (or "Minimal Text Mode", the other software selections will fail because of missing packages).

"fullDVD" is recommened, but if your download speed is slow or you have a download limit then you can try the "miniDVD".

(Note: we built the ISOs _after_ the official M2 images so there might be some small changes in package versions, the images are not 100% compatible with M2, but they are very close. So rather use the official M2 release for testing and reporting non-YaST issues.)

The ISOs are available here:

http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openSU... (~3.8GB)

http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openSU... (~860MB)

(We built only x86_64 images to save OBS resources, sorry, no other architectures.)

Installation ------------

You need to manually add "insecure=1" boot option because the ISOs are not signed by the official openSUSE GPG key. You will also need to accept the OBS YaST:Head:ruby GPG key when adding the installation repository during installation.

Alternatively to full installation you can switch to YaST Ruby later after installing the official Milestone 2. As root run this:

# add YaST:Head:ruby zypper ar -f http://download.opensuse.org/repositories/YaST:/Head:/ruby/openSUSE_Factory/ YaST:Head:ruby # replace all YaST packages, use distribution upgrade to allow vendor change zypper dup --from YaST:Head:ruby

Then you can test Ruby YaST in installed system, use it the same way as the classic YCP YaST.

Testing -------

We already did some minimal testing to ensure the image installs, but we need more intensive testing. So use the images as usual openSUSE installation images, try configuring various system properties, try different hardware/software setups...

We only changed the YaST implementation language, so the look&feel of YaST is (or actually must be) the same as in the classic YCP YaST.

The automatic translation to Ruby also means that a bug in YCP YaST will be also present in Ruby YaST (bug compatibility).

Known bugs -----------

- There is a segfault printed at the console at the end of the first installation stage just before reboot, but it happens at the very end when YaST is exiting and should be harmless.

- When using non-English language some texts are not translated (button labels, messages...).

- Installation from images is not supported (not available on the medium), the installation proposal will just inform about this.

- The ncurses control center in installed system starts for very long time (~2 minutes)

For other bugs see the GitHub link in the next section.

Bug/Success Reporting ----------------------

We are focused on bugs in YCP to Ruby translation, if you find a bug which is also present in YCP YaST in the official M2 then use the usual bug reporting via bugzilla.

If you are unsure you can try the same in the official M2 or you can report it anyway, we will check it. (Of course, it would be nice if you could do that so we are focused on real bug fixing.)

Also report slowdowns or other different behavior not observed in original YCP YaST.

For reporting bugs use GitHub issues (GitHub account needed):

https://github.com/yast/ycp-killer/issues

It would be also great to get some positive feedback to know how many people tested our installer and know what has been already tested and works.

Just send a short summary what did you test (which module(s), what did you configure...).

Feedback --------

If you have any questions or you want to report a success just reply here, write to yast-devel@opensuse.org or connect to #yast freenode IRC channel.

Have a lot of fun!

Ladislav

[1] https://github.com/yast/ycp-killer

--

Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Ladislav Slezak wrote:

Hi all,

Long story short: Alternative Milestone 2 installation images with Ruby YaST created by the YCP Killer project are available here:

http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openSU...

(~3.8GB)

http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openSU...

(~860MB, only package subset, select "Minimal X" or "Textmode" software selection)

Hi Ladislav what should I use as the repo for a network installation? thanks Per -- Per Jessen, Zürich (32.6°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi, I am currently planing a new module for YaST, which would be the preferred language? The low level side will read/write some config files and do some DBus calls. Regards, Stefan --  Stefan Brüns  /  Bergstraße 21  /  52062 Aachen phone: +49 241 53809034     mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, Jun 18, 2013 at 03:05:52PM +0100, Alin M Elena wrote:

...

Ladislav Slezak wrote:

...

Hi all,

Long story short: Alternative Milestone 2 installation images with

...

Ruby YaST created by the YCP Killer project are available here: http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openSU SE-Factory-RUBY-YAST-fullDVD-x86_64-Milestone2-Build0001-Media.iso (~3.8GB)

http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openSU SE-Factory-RUBY-YAST-miniDVD-x86_64-Milestone2-Build0001-Media.iso

...

(~860MB, only package subset, select "Minimal X" or "Textmode" software selection)

Hi Ladislav,

I have tried the full dvd version in a virtual machine... unfortunately it seems the iso you have is affected by some silly bug related to /etc/fstab having partitions mounted by id so I could not finish a full testing...

It has been the default of YaST for years to create /dev/disk/by-id entries in fstab. Does your system install with the normal Milestone 2? Regards, Arvin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dne 18.6.2013 15:53, Per Jessen napsal(a):

Hi Ladislav

what should I use as the repo for a network installation?

Hi, This should work: http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/repo/openS... But linuxrc printed "No repository found" error when I tried this. No idea why it does not work... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dne 18.6.2013 16:12, "Stefan Brüns" napsal(a):

Hi,

I am currently planing a new module for YaST, which would be the preferred language?

The low level side will read/write some config files and do some DBus calls.

Thanks, nice to hear that someone is interested in writing a YaST module! The answer is actually not easy, it depends when you want to start writing it. Currently we are focused on transforming YCP into Ruby and we do not have any module written in Ruby from scratch. Lukas started some module recently, http://lists.opensuse.org/yast-devel/2013-06/msg00013.html, but it is not finished and it is the first attempt for writing a pure Ruby module. Also the documentation is missing, we have not decided which testing framwork we will use, which documentation tool etc... And our Ruby infrastructure is not finished yet, we can still change some implementation details if needed (now we can simply run the YCP->Ruby translator again and get updated modules automatically, we do not have maintain the stable API yet). So the summary is: - if you want to start writing the module right now then you probably should start with YCP and then convert it into Ruby with our tool - if you want to use Ruby now then be prepared for possible incompatible changes, you'll need to keep your module in sync with our changes - if you can wait then later we will have stable infrastructure, some pure Ruby examples (not converted from YCP), more documentation etc... (If you have more questions then ask at yast-devel@ as this is little bit off topic here...) -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Ladislav Slezak wrote:

Bug/Success Reporting ----------------------

We are focused on bugs in YCP to Ruby translation, if you find a bug which is also present in YCP YaST in the official M2 then use the usual bug reporting via bugzilla.

If you are unsure you can try the same in the official M2 or you can report it anyway, we will check it. (Of course, it would be nice if you could do that so we are focused on real bug fixing.)

Also report slowdowns or other different behavior not observed in original YCP YaST.

For reporting bugs use GitHub issues (GitHub account needed): https://github.com/yast/ycp-killer/issues

I've already reported it, but though I'd mention it here too - in ncurses, I can't access anything apart from the main menu. When I try to access a module/menu item, I keep getting returned to the main menu. -- Per Jessen, Zürich (24.6°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dne 18.6.2013 16:47, Arvin Schnell napsal(a):

On Tue, Jun 18, 2013 at 03:05:52PM +0100, Alin M Elena wrote:

...

I have tried the full dvd version in a virtual machine... unfortunately it seems the iso you have is affected by some silly bug related to /etc/fstab having partitions mounted by id so I could not finish a full testing...

Thank you for testing! Could you please add more details? What was the problem exactly? The system did not boot at all or there was an error displayed at boot? Did you use some special partitioning (RAID, LVM, encryption...)? How can I reproduce it? I'm using VirtualBox for testing installations and I haven't any problem related to mount-by-id so far...

It has been the default of YaST for years to create /dev/disk/by-id entries in fstab.

Does your system install with the normal Milestone 2?

Could you please verify it with the official M2 to rule out some possible problems in Factory? Thank you! -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Per Jessen wrote:

/sbin/yast lan

Running that by itself (I don't know if that is valid): bin/yast: line 431: 11736 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS -- Per Jessen, Zürich (25.8°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Ladislav Slezak wrote:

Dne 19.6.2013 10:40, Per Jessen napsal(a):

...

Per Jessen wrote:

...

/sbin/yast lan

Running that by itself (I don't know if that is valid):

bin/yast: line 431: 11736 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

For me it works in both cases ("yast" and "yast lan"), installed from fullDVD. Did you install the fullDVD ISO or just packages from YaST:Head:ruby?

I upgraded a 13.1M2 system from YaST:Head:ruby. -- Per Jessen, Zürich (26.0°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Ladislav Slezak wrote:

Dne 19.6.2013 10:48, Per Jessen napsal(a):

...

I upgraded a 13.1M2 system from YaST:Head:ruby.

Oh, please upgrade all packages from YaST:Head:ruby again, there was an incompatible change in yast2-core yesterday and some packages were not rebuilt against it.

I forgot to mention that the packages from the repository are continuously rebuilt, there are always the latest packages. There might more or less bugs than in the released ISO (depends in which moment you install... ;-) )

Upgrading all packages should fix it, it works for me (I have 12.3 system with packages from Y:H:r).

I ran the 'zypper dup --from YHr' only about an hour ago. -- Per Jessen, Zürich (26.4°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dne 19.6.2013 12:20, Alin M Elena napsal(a):

On Wednesday 19 Jun 2013 11:02:13 Ladislav Slezak wrote:

...

Dne 19.6.2013 10:48, Per Jessen napsal(a):

...

I upgraded a 13.1M2 system from YaST:Head:ruby.

The same issues as Per. I have updated less than 1h ago. apparently I cannot start software management even from kde...

I have reproduced it, looks like a problem in UI bindings. Please, switch back to the Milestone 2 versions (use the ISO or http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/repo/openS... repository for downgrading via zypper dup )

ncurses one takes forever (few minutes) to start yast.

Will be fixed in the next version (https://github.com/yast/ycp-killer/issues/467)

on the other issue with the iso.. by default the partitioner when new partitions are created puts them in fstab by id

/dev/disk/by-id/ata-ST3500418AS_9VM66M4C-part3 swap swap defaults 0 0 /dev/disk/by-id/ata-ST3500418AS_9VM66M4C-part6 / ext4 acl,user_xattr 1 1 /dev/disk/by-id/ata-ST3500418AS_9VM66M4C-part7 /home ext4 defaults 1 2

However if let like this the computer will not mount the partitions. if one changes to uuid everything is fine... However this is not a yast bug just one which prevented me to test the yast ruby installer.

OK, just check if it is also present in the official M2 or it is in our build only. -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

This is also present in the standard factory builds and is caused by an update of systemd and especially the new rule 61-msft.rules. This one seems to make it impossible to mount partitions based on their disk-by-id and the only way around it is either to use /dev/sd... or to use the UUID of the disk. The change was created by Robert Milasan based on a inaccessible bug report.

and to add too injury I have tested today... and it seems that if one selects at install time to create entries in fstab by uuid they are still created by id... so probably this would be a serious bug for m3. if someone else confirms this.. I will open a bug. regards, Alin -- Without Questions there are no Answers! _______________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin http://alin.elenaworld.net/ _______________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 19/06/13 12:50, Raymond Wooninck escribió:

This is also present in the standard factory builds and is caused by an update of systemd and especially the new rule 61-msft.rules. This one seems to make it impossible to mount partitions based on their disk-by-id and the only way around it is either to use /dev/sd... or to use the UUID of the disk. The change was created by Robert Milasan based on a inaccessible bug report.

So my suspicions as been confirmed.. :-| The main issue at hand here is simple, either 1) this patch or addition does not belong to udev but to a different package that has to get installed whenever this special devices are found on the system 2) Or the addition has to be submitted to upstream for review I go with 1 in particular because udev should not require sg3_utils unless it is required by all systems out there. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2013-06-19 18:50 (GMT+0200) Raymond Wooninck composed:

...

...

on the other issue with the iso.. by default the partitioner when new partitions are created puts them in fstab by id

...

...

/dev/disk/by-id/ata-ST3500418AS_9VM66M4C-part3 swap swap defaults 0 0 /dev/disk/by-id/ata-ST3500418AS_9VM66M4C-part6 / ext4 acl,user_xattr 1 1 /dev/disk/by-id/ata-ST3500418AS_9VM66M4C-part7 /home ext4 defaults 1 2

...

...

However if let like this the computer will not mount the partitions. if one changes to uuid everything is fine... However this is not a yast bug just one which prevented me to test the yast ruby installer.

...

OK, just check if it is also present in the official M2 or it is in our build only.

This is also present in the standard factory builds and is caused by an update of systemd and especially the new rule 61-msft.rules. This one seems to make it impossible to mount partitions based on their disk-by-id and the only way around it is either to use /dev/sd... or to use the UUID of the disk. The change was created by Robert Milasan based on a inaccessible bug report.

Those are not the only workarounds. With: kernel-desktop-3.10.rc4-1.1 systemd-204-3.1 udev-204-3.1 the LABEL= syntax I use in all my fstabs and Grub configs is still working as expected. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org