I plan to submit this. Feel free to provide feedback before I do it.
Title: Almost two years of YaST News
Subtitle: Recent changes and future plans at YaSTland
Abstract:
YaST, the flagship installer and configuration tool of openSUSE is in
constant development. Just as its unattended companion AutoYaST.
Although the YaST Team at SUSE tries to communicate progress as often as
possible in the YaST Blog, it has been almost two years since we
presented the "Top 25 New Features in (Auto)YaST" at openSUSE Conference
2020. So it's time for another live update!
We will recap the main changes and new features that are already
integrated into openSUSE Tumbleweed and that will be included at
openSUSE Leap 15.4, to be released just a couple of days after the talk.
We will also take a look to some ideas for future development... and we
really need the feedback of the whole openSUSE community for that. So
please join us and speak up!
--
Ancor González Sosa
YaST Team at SUSE Software Solutions
Hello Team,
In SLES 15 SP3, how are the patterns and package descriptions translated?
Until SLES 12 SP5, we were modifying the package package-translations by merging the po files for a translated language and creating the package-translations-$lang.mo files
In SLES 15 SP3, I tried to do the same, merging all po files for a translated language and creating the package-translations-$lang.mo files.
Now in SLES 15 SP3 during installation, if I change the language I am not getting the translated description for the patterns.
I would really appreciate it if you could help us understand how to localize our patterns and package descriptions.
Regards,
Gaurav.
In the YaST Team we are not longer numbering the development sprints,
but that does not stop us from reporting progress at D-Installer
development (including a screenshot and some pre-announcements) as well
as news about the following YaST areas:
- Improvements in the network for S/390 and for iBFT.
- Small usability improvements.
- Extended documentation for ERB in AutoYaST.
- Some development tips & tricks.
Check the whole report at
https://yast.opensuse.org/blog/2022-03-22/yast-report-2022-2
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
Hello!
For some time we used a template for pull requests in the yast-storage-ng repository,
it turned out to be useful so we decided to use it for all YaST repositories
as a reminder to write good descriptions in the pull requests.
The template is now shared for all repositories under the "yast" GitHub organization
and is defined in the ".github" repository [1].
This is the default file but if you for whatever reason need a different template
for a specific repository then just define it there, the local file will override the
global one.
See more details in the GitHub documentation [2].
If you want to improve the template then feel free to open a pull request
for it. :-)
[1] https://github.com/yast/.github/blob/master/PULL_REQUEST_TEMPLATE.md
[2]
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-…
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
Hi,
because of my problems with ISP yesterday I got a bit angry at them because it was not first time when they messed configuration on their AP I'm connecting to. So, as the first I searched what can be used for monitoring my network and then gave a try to vnstat I haven't use before (ok that is not that new thing, but I simply haven't used that up to now because of ntop, netstat, ... so many tools in the area ;-) What vnstat does is that is collects traffic information for you via a service reading /sys. You can then export some statistics for various periods.
* https://www.geeksforgeeks.org/vnstat-command-in-linux-with-examples/
* I also learned about "ip -o -t monitor" which is way easier to use than checking logs and/or tcpdump when having connection issues
and then I was searching for some information about testing, monitoring, maintaining networks. I came across archive of NANOG talks.
I really don't know if it is interesting for any of yast developers and I didn't make to go through everything I wanted yet but this caught my eyes so far
* using open source tools to validate network configuration (https://www.youtube.com/watch?v=D9hZiW66jw4)
* a practical guide to (Correctly) troubleshooting with traceroute (https://archive.nanog.org/meetings/nanog45/presentations/Sunday/RAS_tracero…)
btw for my next study & learn period I planned to find out what's new in network emulation area. I'll probably take this https://www.networkstraining.com/network-simulation-software-tools/ as a start point.
Michal
Forwarding this here since this certainly have an effect on how people
install software in their openSUSE systems.
It may also imply the usage of OneClick Installer would decay.
Can we be part of any kind of alternative solution? Maybe a
generalization of this:
https://yast.opensuse.org/blog/2020-02-07/sprint-93#the-online-search-featu…
Cheers.
-------- Forwarded Message --------
Subject: Planning decomission of software.opensuse.org (Community meeting)
Date: Thu, 17 Mar 2022 21:05:14 +0000
From: Lubos Kocman <lubos.kocman(a)suse.com>
Reply-To: Lubos Kocman <lubos.kocman(a)suse.com>
To: factory(a)lists.opensuse.org <factory(a)lists.opensuse.org>
CC: karatekhd(a)opensuse.org <karatekhd(a)opensuse.org>
Hello openSUSE!
One of the outcomes of today's *community meeting was that we need to
decomission the current *software.opensuse.org code-base, as we can't
find volunteers to maintain it nor develop it any further. The current
code-base and its deployment is tied to ruby25 which makes
appliacations of security fixes for currently used rubygems almost
inpossible.
Our social platforms (forums-o-o, discord, etc) show many cases where
incorrect usage of the service leads to Leap systems being partially
migrated to Tumbleweed, or you end up with Tumbleweed which has enabled
a lot of invalid repos. The situation is not going likely to improve
without care any time soon.
At the meeting we agreed that decomission of the service is needed, and
that there is still a need to provide functionality that allows people
to search for and install software which is not part of their install,
and/or to search for version numbering or the status of the NEXT/devel
project(s).
There was already a *brainstorm about the services' future, but there
was not much progress in that direction.
I really hope that this can ignite some constructive discussions that
could help us to develop a replacement for the current service. As
suggesed in the meeting minutes there are upcoming opportunities that
we could make use such as gsoc, outreachy, hackweek. We should not try
to make this a ruby vs python vs node fight, but instead try to find a
sustainable solution to keep the service running for the next decade.
[0] https://github.com/openSUSE/software-o-o
[1] https://etherpad.opensuse.org/p/weeklymeeting20220317
[2] https://etherpad.opensuse.org/p/softwareworkshop
Thank you very much in advance
ps. There is no particular date for decomission yet, but it's coming.