On 10/29/20 1:17 PM, Arvin Schnell wrote:
> On Wed, Oct 28, 2020 at 09:52:07AM +, Arvin Schnell wrote:
>
>> So to avoid such problems with libstorage-ng and YaST I propose
>> to 1) disallow creating level 0 qgroups without an corresponding
>> subvolume and 2) ignore level 0 qgroups without a
On 10/28/20 10:52 AM, Arvin Schnell wrote:
>
> Hi,
>
> users can do funny things with btrfs qgroups leading to problems:
Indeed. That's why the YaST plan is to allow very limited management of
quotas, not even exposing the concept of qgroups to the user.
> When a subvolume is created a
The latest YaST Team report comes more varied than usual, including news
about Cockpit and about the openSUSE + LibreOffice Virtual Conference.
But, of course, the bulk of the post is still the new features in the
installer and its ecosystem:
- Unit tests for the installation-images Perl
For those of you who may have overlooked it, starting tomorrow the
openSUSE + LibreOffice Virtual Conference will take place online.
https://events.opensuse.org/conferences/oSLO
Some talks may be interesting for YaST enthusiasts in general or for the
YaST Team at SUSE in particular, so check the
As part of the current effort to improve how we display Btrfs subvolumes
in the Partitioner I was checking how we mount them.
We always create a fstab entry for each subvolume like /home, /var...
That makes a lot of sense when the system has support for snapshots,
because the default subvolume is
On 10/12/20 10:52 AM, Arvin Schnell wrote:
>
> Hi,
>
> bug #1065588 is still open. It deals with the installation of
> NTFS packages if an NTFS file system is found on the system. Even
> though the file system is not mounted YaST wants to install the
> NTFS tools. Some users do not like that
The YaST Team continues focusing on improving both AutoYaST and the
management of storage devices. Let's take a quick glance at some of the
results.
- New YaST test client to check AutoYaST dynamic profiles.
- Improved detection of which YaST package is needed to process each
section of the
On 9/21/20 10:03 AM, David Díaz wrote:
>
> On 21/9/20 7:35, josef Reidinger wrote:
>> On Sun, 20 Sep 2020 23:36:11 +0200
>> Ancor Gonzalez Sosa wrote:
>>
>>> [...]
>>> Good news in this regard. Iván came with an idea for a small change that
>>>
The YaST Team keeps working in mid-term goals in several areas,
specially AutoYaST and storage management. Let's take a look to the
progress.
- Several enhancements in the new MenuBar widget.
- More steps to add a menu bar to the Partitioner.
- New helpers to use Embedded Ruby in AutoYaST
On 9/10/20 2:47 PM, Ancor Gonzalez Sosa wrote:
> [...]
>
> First question: what approach should we follow for the menu bar?
>
> After some discussions, we have three proposals. I created three
> branches in the yast-storage-ng repository so you can play with them.
> For the
On 9/10/20 3:59 PM, Kenneth Wimer wrote:
> Here's my two cents:
>
> #1 is interesting as it finally explains why the buttons are below the table
> __ The menu has the context of the app only. Buttons have the context of the
> selection within a table
>
> Users are more used to #2. It would
On 9/10/20 2:47 PM, Ancor Gonzalez Sosa wrote:
> [...]
>
> First question: what approach should we follow for the menu bar?
>
> [...]
>
> Menu proposal 1
> https://github.com/ancorgs/yast-storage-ng/blob/menu_minimal/README.md
>
> Menu proposal 2
> https://g
Some time ago, we decided to make several changes in the Partitioner UI.
Check this section (or the full document if you are interested enough)
for more details:
https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md#agreed-plan-so-far
We are currently working on adding a new
With some delay from the actual end of the sprint, let's take a look to
what the YaST team was doing at the end of August.
- More flexible AutoYaST profiles by means of Embedded Ruby (ERB).
- Unify the format used to reference a certain element of an AutoYaST
profile, both when reporting errors
On 8/24/20 2:59 PM, Stasiek Michalski wrote:
> On Mon, Aug 24, 2020 at 14:56, Ancor Gonzalez Sosa wrote:
>> As you all know, we recently got to the conclusion of adding a menu bar
>> to the YaST Partitioner and getting rid of several entries we have in
>> the left-hand
On 8/24/20 2:56 PM, Ancor Gonzalez Sosa wrote:
>
> [...]
>
> Which option do you think would be better?
Option 2 is more similar to what we have now. So it's a less disruptive
change (and also less work to be implemented). But I prefer option 1
because I think it's a more standard
As you all know, we recently got to the conclusion of adding a menu bar
to the YaST Partitioner and getting rid of several entries we have in
the left-hand tree. Check
https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md#agreed-plan-so-far
We are in the process of
On 8/10/20 3:03 PM, Stefan Hundhammer wrote:
> On 2020-07-24 14:55, Ancor Gonzalez Sosa wrote:
>> We also discussed the idea of offering a WUI:
>>
>> - We see real use-cases for it, like:
>> * configuration via a web browser is kind of common/expected for
>>
During the latest two weeks the YaST Team has fixed quite some bugs in
(Auto)YaST, but we also has done more interesting stuff you can find in
our usual report, including:
- Documenting the current handling of the AutoYaST profile.
- Removing an undocumented AutoYaST feature for creating images.
As mentioned several times in IRC or daily calls, I think the YaST team
should have some representation in the "openSUSE + LibreOffice Virtual
Conference" taking place on October 15 - 17, 2020.
So I submitted the 30min. talk you can see below. If you have more ideas
for YaST-related content,
On 7/22/20 4:53 PM, Ancor Gonzalez Sosa wrote:
> The YaST team wants to take some time to think in the long term and try
> to envision the future of our UI design/programming... which may be
> anything from just an improved libYUI to something completely different
> and unrelated.
&g
The YaST team wants to take some time to think in the long term and try
to envision the future of our UI design/programming... which may be
anything from just an improved libYUI to something completely different
and unrelated.
It likely makes sense to start discussing what are the requisites
Our latest summary includes our usual overview of two weeks of work and
also the results of the survey about our blog. Regarding the first part,
you will find information about all this:
- Research about the differences in the look of the installer and
YaST Firstboot
- Several fixes related to
These are the results of the survey about the YaST blog post.
Total answers: 31
Q1.How often do you read the YaST Team reports?
This is my first time: 4 (12.90%)
When I find something interesting in the summary: 5 (16.13%)
Regularly: 22 (70.97%)
Q2.How do you value de new format compared to
The YaST Team is back with another development digest... but this time
we need your help! Please, visit our blog post and give us feedback
using the poll embedded there. It's just three questions and it would
help us a lot to define the future of our development reports.
On 6/15/20 6:10 PM, Ancor Gonzalez Sosa wrote:
> I have documented the outcome of our recent meeting to come up with a
> new concept for the UI of the Partitioner. See the result here:
>
> https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md#agreed-plan-so
I have documented the outcome of our recent meeting to come up with a
new concept for the UI of the Partitioner. See the result here:
https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md#agreed-plan-so-far
We will use that as a base for upcoming tasks in our development
As explained in our previous blog post, or latest YaST development
report is basically a collection of links to (rather descriptive)
Github’s pull requests.
You can find the report, which includes the links and a couple of extra
details here:
https://yast.opensuse.org/blog/2020-06-09/sprint-101
We agreed to have a meeting to discuss the ideas collected here and
decide how to move forward:
https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md
It will take place tomorrow Wednesday June 10th "after lunch", which I
guess can be translated to 2pm CEST (so nobody has to
One hundred development sprints, that’s a nice rounded number… to write
the last YaST development report.
This post will be the last one following our traditional format (read
the post if you want to know what the future will bring instead) and it
covers several topics like:
- A better editor
On 4/28/20 4:56 PM, Ancor Gonzalez Sosa wrote:
> The interface of the YaST Partitioner has reached a point in which is
> really hard to deal with it. We need to find a way to move forward.
>
> As a first step, we have created this document that explains the problem
> and we hope
On 5/22/20 10:41 PM, josef Reidinger wrote:
> Hi,
> I use this friday to see some rest in published talks from conferences. This
> time I check some videos from RubyConf 2019. I see three of them and let me
> share my personal impressions.
Thanks for sharing.
>
> [...]
>
> - we can prepare
On 4/29/20 10:14 AM, Steffen Winterfeldt wrote:
> On Tue, 28 Apr 2020, josef Reidinger wrote:
>
>> On Tue, 28 Apr 2020 17:47:48 +0200 (CEST)
>> Steffen Winterfeldt wrote:
>
>> seeing your pictures, it maybe even make sense to use checkbox frame
>> which can fit ever nicer there.
>> For example
On 5/12/20 7:21 PM, josef Reidinger wrote:
> On Tue, 12 May 2020 17:57:17 +0200
>
> Well, if you throwing around crazy ideas, then for me in qt ideal way to do
> partitioning is visual one.
For "domestic" systems (let's say two disks with one LVM), you are
likely right and some visual approach
On 5/13/20 3:16 PM, Stefan Hundhammer wrote:
> On 2020-05-12 17:57, Ancor Gonzalez Sosa wrote:
>> Crazy idea 1
>>
>>
>> Sections like "hard disk", "LVM", "RAID", etc. would not longer be the
>> main way to interact wit
On 4/28/20 4:56 PM, Ancor Gonzalez Sosa wrote:
> The interface of the YaST Partitioner has reached a point in which is
> really hard to deal with it. We need to find a way to move forward.
>
> As a first step, we have created this document that explains the problem
> and we hope
It's time for another report from the YaST trenches. This time with
links to other interesting reads and with several calls to action.
Today topics include:
* Some considerations about the usage of YaST
* A sneak peek at the future of AutoYaST, including a separate
full blog post
* Some
The interface of the YaST Partitioner has reached a point in which is
really hard to deal with it. We need to find a way to move forward.
As a first step, we have created this document that explains the problem
and we hope it can be used as a base to discuss the future of the
Partitioner
As usual, I was asked to help with the Features Page and with the
Release Announcement of openSUSE Leap 15.2, from the YaST point of view.
If you are curious about what we will say to the world or you want to
improve it, take a look to the "Snapper", "YaST" and "AutoYaST" sections
of
On 2020-04-17 15:42, josef Reidinger wrote:
> On Fri, 17 Apr 2020 15:05:04 +0200
> Bernd Ritter wrote:
>>
>> I will dig deeper into the documentation and get back to you if there is
>> something unclear to me. Would be happy to help improve documentation there.
>
> That would be great.
On 2020-04-17 14:21, Martin Vidner wrote:
> On Thu, Apr 16, 2020 at 10:25:55AM +0200, josef Reidinger wrote:
>> Hi,
>> I would like to arrange meeting about future of XML parser as we discuss on
>> review and planning meeting.
>> I propose to have it next Tuesday after daily call if everyone
>>
On 2020-04-08 13:33, josef Reidinger wrote:
> On Wed, 8 Apr 2020 10:46:17 +0200
> Martin Vidner wrote:
>
>> On Fri, Apr 03, 2020 at 05:21:21PM +0200, josef Reidinger wrote:
>>> On Fri, 3 Apr 2020 16:05:04 +0200
>>> Martin Vidner wrote:
2) It uses a namespace,
On 2020-04-06 21:38, Arvin Schnell wrote:
> On Mon, Apr 06, 2020 at 05:15:46PM +0200, josef Reidinger wrote:
>
>> as you can read in previous mails, I am playing with xml parser used in
>> YaST. Nokogiri looks like the best option due to its relax ng support and
>> its availability in SLE (used
While many activities around the world slow down, we are proud to say
the YaST development keeps going at full speed. Check it in the latest
report of the YaST Team activity, including:
* More news about the new Online Search functionality
* Improvements in the user interface to configure NTP
On 2020-03-30 22:07, josef Reidinger wrote:
> Hi,
>
> Or do we have some functionality that we would like to have on top of
> standard parsers?
I think it makes sense to offer our own parser. Otherwise, we could end
up with different parts of YaST using different approaches (rexml vs
nokogiri
On 3/11/20 10:47 PM, Lukas Ocilka wrote:
> Hi guys,
>
> Me and Ancor have been maintaining a long list of big topics, such as
> features, refactoring, wishes, future needs etc., but this list reflects
> the current situation trying to address all the needs from various
> sources at the time.
>
>
As Lukas mentioned in another thread, it's time to start looking to the
next big topic(s). And, while there are still some bugs to fix before
the release of SLE-15-SP2 / Leap 15.2, we should be very conservative
about what we modify there.
So, in my opinion, it's time to create the SLE-15-SP2
After a month of silent work, the YaST Team is back with some news about
the latest development sprint. Those news include:
- Enabling YaST on the Windows Subsystem for Linux
- Usability improvements for the Online Search, the Partitioner and
the Kdump module
- Better control of overridden
On 3/4/20 7:54 PM, Christian Boltz wrote:
> Hello,
>
> Am Mittwoch, 4. März 2020, 18:19:26 CET schrieb José Iván López
> González:
>> I have described a possible solution here
>> https://gist.github.com/joseivanlopez/bcf7185904922afae7d93f7518192864
>> . Feedback is welcome.
>
> Let me make a
On 3/3/20 5:04 PM, Ancor Gonzalez Sosa wrote:
> Sending this to both Ken (SUSE's UX expert) and the yast-devel ML (for
> public scrutiny).
>
> We have recently implemented a new feature in YaST about installing
> packages that are needed to inspect the storage setup of a s
Sending this to both Ken (SUSE's UX expert) and the yast-devel ML (for
public scrutiny).
We have recently implemented a new feature in YaST about installing
packages that are needed to inspect the storage setup of a system. But
we are not satisfied with the usability, so we wanted to have some
During this Hack Week I wanted to experiment with Crystal doing
something concrete. See more details at [1] and [2]. Josef Reidinger
joined the project as well.
So first, the TLDR;
1) We migrated quite some non-trivial code from Ruby to Crystal. Porting
Ruby+RSpec code to Crystal+Spectator was
On 2020-02-07 09:41, Josef Reidinger wrote:
> As deadline for papers are really close I would like to present the final
> proposal for two talks. If you can please do proof read and ideally also some
> PR buzzwords enhancements as it is not my strong page.
>
> ## Presentation 1
I like the
On 1/29/20 10:59 AM, Ancor Gonzalez Sosa wrote:
> [...]
>
> I would co-mentor any of those (or any other idea you can come with).
So what? Anyone wanting to co-mentor any project (from my list or any
other thing)?
Any reader of this list willing to participate as student?
Cheers
This started as a discussion in
https://bugzilla.suse.com/show_bug.cgi?id=1161460 which leads me to
realize we have the same "hack" repeated in dozens of YaST modules.
The point is that there is a function called `Popup::ReallyAbort` that
all YaST modules call when asked to quit. The only
On 2020-01-29 10:17, Stasiek Michalski wrote:
>
> On Wed, Jan 29, 2020 at 09:36, Ancor Gonzalez Sosa wrote:
>> On 2020-01-28 17:46, José Iván López González wrote:
>>> [...]
>>> Well, I agree we need to re-think the UI of the Expert Partitioner,
>>
>
On 2020-01-27 10:28, Ancor Gonzalez Sosa wrote:
> openSUSE is considering to apply for Google Summer of Code this year.
>
> We offered some projects in the past, some of them were indeed
> executed([1],[2]).
>
> [1] Alternatives YaST Module
> https://github.com/openSUS
openSUSE is considering to apply for Google Summer of Code this year.
We offered some projects in the past, some of them were indeed
executed([1],[2]).
[1] Alternatives YaST Module
https://github.com/openSUSE/mentoring/issues/13
[2] Rewrite Keyboard Management - Done out of GSoC
First of all, I'm moving this discussion to the yast-devel mailing list.
This is not internal team stuff.
On 1/23/20 3:36 PM, David Díaz wrote:
> Hi folks!
>
> As part of my current PBI[1], I must raise a discussion about the
> default behavior of pages with tabs in the Partitioner :)
>
> The
On 1/6/20 8:54 AM, Josef Reidinger wrote:
> V Sun, 5 Jan 2020 11:51:29 +0100
> Ancor Gonzalez Sosa napsáno:
>
>> On 1/3/20 12:24 PM, Ancor Gonzalez Sosa wrote:
>>> On 1/3/20 11:31 AM, Josef Reidinger wrote:
>>>> V Fri, 3 Jan 2020 11:14:15 +0100
>
On 1/6/20 2:55 PM, Martin Vidner wrote:
> On Fri, Jan 03, 2020 at 11:31:48AM +0100, Josef Reidinger wrote:
>> V Fri, 3 Jan 2020 11:14:15 +0100
>> Ancor Gonzalez Sosa napsáno:
>>> See more details at https://github.com/ancorgs/y3storage
>>
>> Hi, this is quite
On 1/3/20 12:24 PM, Ancor Gonzalez Sosa wrote:
> On 1/3/20 11:31 AM, Josef Reidinger wrote:
>> V Fri, 3 Jan 2020 11:14:15 +0100
>>
>> Hi, this is quite interesting. Especially similarities in testing looks
>> nice. I have few questions:
>
> I have to say tha
On 1/3/20 12:24 PM, Ancor Gonzalez Sosa wrote:
> On 1/3/20 11:31 AM, Josef Reidinger wrote:
>>
>>
>> Hi, this is quite interesting. Especially similarities in testing looks
>> nice. I have few questions:
>
> I have to say that my feeling is that similari
On 1/3/20 11:31 AM, Josef Reidinger wrote:
> V Fri, 3 Jan 2020 11:14:15 +0100
> Ancor Gonzalez Sosa napsáno:
>
>> Ok, and now that I got your attention, let's rephrase the subject into
>> something more realistic: "I'm starting to port to Crystal a very small
>
Ok, and now that I got your attention, let's rephrase the subject into
something more realistic: "I'm starting to port to Crystal a very small
and limited subset of yast-storage-ng".
See more details at https://github.com/ancorgs/y3storage
Is something I wanted to do in the past Hack Week... and
On 12/20/19 1:11 PM, Josef Reidinger wrote:
> V Fri, 20 Dec 2019 11:03:32 +0100
> Ancor Gonzalez Sosa napsáno:
>
>> I've gone through the full list of bugs assigned to the YaST Team or
>> some of its members with the intention of closing obsolete stuff that
>>
I've gone through the full list of bugs assigned to the YaST Team or
some of its members with the intention of closing obsolete stuff that
are not real issues anymore.
In the process I found out there are some YaST modules or areas that
have quite some open bugs. Some of them are modules that
The YaST Team is about to enter hibernation mode for a couple of weeks.
But before that, let’s take a look to the most important features and
bugfixes we implemented in the last sprint of 2019. That includes:
- bringing back to life some sections of the Software Manager,
- implementing system
Douglas DeMaio asked if me or any other YaST developer was planning to
give a talk at openSUSE Summit Dublin[1]. I have to admit that was out
of my radar. That summit is a small event that takes place right after
SUSECON[2] in the same location, reusing part of its infrastructure. So
it sounds
On 11/11/19 1:47 PM, José Iván López González wrote:
> Thanks Arvin, very interesting.
>
> It seems people mainly see YaST as a tool for configuring a running
> system. Nobody comments about YaST as installer. That surprises me.
Yes, that's the difference between bugzilla/jira driven feedback vs
It’s time for another YaST team report! Let’s see what’s on the menu.
- News and improvements in the storage area, specially encryption.
- Some polishing of the behavior of YaST Network.
- New widgets in libYUI.
- A look into systemd timers and how we are using them to replace cron.
- A new cool
In the latest sprint reports of the YaST Team we have mentioned several
times that we are working in expanding the capabilities of the
Partitioner regarding disk encryption.
With a little bit of delay, we have finally published a separate blog
post explaining the new features in more detail.
On our latest report, the YaST Team...
- confesses an uncomfortable truth about how we manage the UI,
- shows you how we keep our administrative mess under control,
- gives you a sneak peak on some upcoming features and improvements
Go check
On 6/25/19 11:52 AM, Ancor Gonzalez Sosa wrote:
> three development sprints, namely the 77th, 78th and 79th.
Which are the correct sprint numbers. The subject of the original email
is wrong (the perils of copy).
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe
May and June have been, so far, interesting months for the YaST Team.
Many things happening... which had the drawback of keeping us too busy
to publish our usual sprint reports.
But we are back with a looong report trying to summarize the latest
three development sprints, namely the 77th, 78th
We are behind schedule with our sprint reports. Don't worry, we plan to
fix it.
Meanwhile, we have published a summary of a long awaited YaST feature.
Enjoy the post "Getting further with Btrfs in YaST"
https://lizards.opensuse.org/?p=13814
Cheers
--
Ancor González Sosa
YaST Team at SUSE Linux
On 6/13/19 4:13 PM, Ladislav Slezak wrote:
>
> The master is automatically submitted to TW by Jenkins just after merging the
> change
If the package version for the merged change is bigger than the version
in TW. If you don't increase the version number as part of your changes,
then the package
On 6/13/19 2:40 PM, William Brown wrote:
> Hi there,
>
> I recently made some changes to https://github.com/yast/yast-auth-server
>
> I'd like to check what version of yast these changes appear in: How can I
> check where/how my changes are in tumbleweed/leap/sle? Thanks!
I guess you are
Last Friday we organized a rather big launch party for Leap 15.1 at a
professional school in Gran Canaria (Spain).
See pictures at
https://photos.app.goo.gl/YSpmFBE3oKqf7M1z5
Although it was targeted mainly to teachers and students of the Computer
Administration and Software Development courses,
On 4/10/19 1:38 PM, Stasiek Michalski wrote:
> Hi,
>
> On śro, Apr 10, 2019 at 1:27 PM, Ancor Gonzalez Sosa wrote:
>> Have you ever wondered how to develop a software that works flawlessly
>> in all languages, including right-to-left ones like Arabic? We wonder it
>>
Have you ever wondered how to develop a software that works flawlessly
in all languages, including right-to-left ones like Arabic? We wonder it
too!
Those and other interesting topics (both user-centric and developer
oriented) in the latest development report from the YaST Team at SUSE.
Profit!
On 3/28/19 1:06 PM, Ancor Gonzalez Sosa wrote:
> On 1/21/19 6:30 PM, Ancor Gonzalez Sosa wrote:
>>
>> I plan to expand those bullet points to be something bigger than a
>> sentence (in the cases in which that makes sense), but first a wondered
>> whether I was overlo
On 1/21/19 6:30 PM, Ancor Gonzalez Sosa wrote:
>
> I plan to expand those bullet points to be something bigger than a
> sentence (in the cases in which that makes sense), but first a wondered
> whether I was overlooking something interesting for the majority of
> final Leap 15.1
Another forward from a different mailing list about a topic we could
need to discuss.
In the YaST team we used to get the SUSE feature requests via Fate and
now we get them via Jira.
But on the openSUSE side, the old mechanism used for that (the public
Fate instance at features.opensuse.org) was
Just a reminder about the new blog posts, that are actually extending
some of the bullet-points in this original mail.
On 1/21/19 6:30 PM, Ancor Gonzalez Sosa wrote:
> [...]
>
> - Better support for Salt formulas in yast2-configuration-management.
https://lizards.opensuse.org/2019/02/2
Those who don't follow the YaST development sprint reports may overlook
some extra blog posts the YaST Team has published to present a couple of
features we have been working on lately.
Let's fix that by providing direct access to the links here.
Recapping the Bcache support in the YaST
What is better than a blog post explaining the novelties in YaST?
Three blog posts!
Check our usual sprint report covering the following topics.
- Improvements in the Bcache support in the Partitioner
- Users home as Btrfs subvolumes
- Better visualization of Salt formulas
- Automatic
On 2/20/19 11:03 PM, Stefan Koch wrote:
> Hi,
>
> please add the new YaST package yast2-usbauth from
> https://github.com/kochstefan/yast-usbauth or
> https://build.opensuse.org/package/show/YaST:Head/yast2-usbauth to
> openSUSE Factory/Tumbleweed/Leap.
> Request:
On 5/26/18 5:41 PM, Stefan Koch wrote:
> Hi @all,
>
> are there any news about this topic?
Resurrecting this thread. Sorry for the huuuge delay.
I just submitted (and accepted) your package to the YaST Devel project.
You are the maintainer and the bugowner.
Now getting that accepted into
t, that's a more
complex question.
Cheers.
>
>
> On 2/1/19 4:48 PM, Ancor Gonzalez Sosa wrote:
>> For those involved in the bcache support in storage-ng, this is Coly's
>> answer to the question about the current status in all archs.
>>
>> Forwarded M
:56 下午, Ancor Gonzalez Sosa wrote:
>
> By the way, Coly, I have a question about that. Assuming bcache is not
> production-ready in all architectures (which may be true or not,
> that's still an open question) - Are the bcache-tools available in all
> architectures, including
The time for the release announcement of Leap 15.1 is approaching. I was
asked to provide some list of highlights related to YaST. Some obvious
things that come to mind are:
Look
=
- The sidebar with the steps of the installation process is back.
- New icons everywhere.
- Better HiDPI
On 1/9/19 3:55 PM, Ladislav Slezak wrote:
>
> Hi all,
>
> [...]
>
> Travis and Jenkins
> --
>
> [...]
>
> This means the public Jenkins should work just as expected. Of course, if you
> see
> any issues there then just ping me.
Thanks a lot!
> yast-com...@opensuse.org
>
On 1/8/19 1:30 PM, Ladislav Slezak wrote:
>
> Hi,
>
> some time ago I fixed a typo in an yast2-packager shell script. After fixing
> it [1] I
> remembered that I had looked at the ShellCheck tool in the past. It is a
> similar tool
> to Rubocop but designed for shell scripts. There is even an
On 12/18/18 10:30 AM, Josef Reidinger wrote:
> V Tue, 18 Dec 2018 08:51:48 +
> Arvin Schnell napsáno:
>
>> Hi,
>>
>> I see again and again regressions due to simple mistakes,
>> e.g. bsc #1119678 or bsc #1119699. Apparently code reviews, unit
>> tests nor rubocop did help in these cases
On 12/12/18 5:40 PM, Stefan Hundhammer wrote:
> [...]
>
> Tricky programming is s cool.
> Readable and maintainable code is sooo overrated.
Just to get you even on worse mood. ;-)
https://www.destroyallsoftware.com/talks/wat
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To
um 18:04 schrieb Brüns, Stefan:
>>> On Dienstag, 20. November 2018 17:36:10 CET Ancor Gonzalez Sosa wrote:
>>>> YaST development keeps rolling. Check the latest report at
>>>> https://lizards.opensuse.org/2018/11/20/yast-sprint-67/
>>>
>>>> with
YaST development keeps rolling. Check the latest report at
https://lizards.opensuse.org/2018/11/20/yast-sprint-67/
with a lot of information about new features in the installer, like:
- More options to configure Kubic during installation.
- Several improvements in the storage proposal.
- Easing
On 11/08/2018 10:30 AM, Rodion Iafarov wrote:
>
> On 11/8/18 9:52 AM, Ladislav Slezak wrote:
>> Dne 07. 11. 18 v 16:39 Christopher Hofmann napsal(a):
>>> Hi YaSTees!
>>>
>>> I had a deeper look into Ladislav's REST API and I found it very
>>> flexible and easy to use - and furthermore very
On 10/17/2018 09:13 AM, Josef Reidinger wrote:
> V Tue, 16 Oct 2018 19:49:12 +0200
> Christian Boltz napsáno:
>
>> Hello,
>>
>> some days ago, I did a Tumbleweed installation. One noticable change
>> (since my last fresh install ~2 years ago) was that the installation
>> summary screen (the
1 - 100 of 345 matches
Mail list logo
