Hi all,
some time ago we discussed where and how we should share
"Tips&Tricks" for YaST users and developers.
IIRC there was no clear conclusion so I decided to start
a wiki [1] to collect all our tricks we know or use.
For now it's just a place for dumping your ideas, links, short
howtos, etc... When we collect enough data we can probably
split it to several categories or move it somewhere else.
We just need the data first.
I have added there some my tricks from my personal "knowledgebase"
file. If you have better tricks or find something wrong simply
change it, it's a wiki ;-)
Ladislav
[1] https://github.com/yast/yast.github.io/wiki/YaST-Tips-and-Tricks
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
I got a list of all the rejected maintenance requests for packages with
name "yast2*" in 2021. Then I manually filtered out those which IBS
projects are currently in sync with the repository branch (since I
assume there was a follow-up request that fixed the problem).
These ones still remain to be fixed. Note not all of them correspond to
the problem building in i586, there are also other kind of problems.
In fact, I'm not even sure if this list includes all the maintenance
updates blocked by the i586 problem.
Out of sync in SLE-15-GA
* yast2-pkg-bindings
Out of sync in SLE-15-SP1
* yast2-pkg-bindings
Out of sync in SLE-15-SP2
* autoyast2
* yast2-network
* yast2-packager
Out of sync in SLE-15-SP3
* autoyast2
* yast2-add-on
* yast2-country
* yast2-installation
* yast2-theme
* yast2-network
* yast2-packager
* yast2-schema
Branches are not matched to IBS projects as expected
* yast2-migration
- Looks like it was not correctly branched into SLE-15-SP3 back then
* yast2-rear
- Problems due to branches when submitting to SLE-12-SPX (yes, 12)
* yast2-python-bindings
- Branches are messy
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Software Solutions
Again, the YaST Team combines the information from the two latest
sprints into a single blog post, including:
- Rethinking some internals in several areas
- Heavy work (still in progress) on yast2-users
- Improvements in the way YaST handles libYUI plugins
- A visual fix in the packages manager
- More progress in the release tools
Check the full report at
https://yast.opensuse.org/blog/2021-09-28/sprints-131-132
Cheers
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet.
Pending requests in repository yast-devtools:
- Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (60 days)
https://github.com/yast/yast-devtools/pull/161
Pending requests in repository yast-journal:
- Use Yast::Builtins.strftime in 'Change Filter' dialog (26 days)
https://github.com/yast/yast-journal/pull/45
Hi all,
JFYI, it looks like coveralls.io is having serious issues with its
database. So if you get a "405 Not Allowed" error when trying to submit
a coverage report, like we do through GitHub Actions[1], it will be
most likely related to those problems.
Let's hope they can recover soon. You can check the progress at their
status page[2].
Regards,
Imo
[1]
https://github.com/yast/yast-autoinstallation/pull/793/checks?check_run_id=…
[2] https://status.coveralls.io/
--
Imobach González Sosa
YaST Team at SUSE LLC
https://imobachgs.github.io/
Hello,
today morning I did a somewhat older
openSUSE Tumbleweed Snapshot20210423
test installation on a KVM virtual machine.
Something went wrong during package installation
but I could not read the error message because
YaST exited and about one second later I was in
linuxrc with its ncurses Error/Exit screen.
Because what I actually wanted to do is
to "just try out something on Tumbleweed"
but that error exit interrupted my ongoing work
so I did not do a major mental task switch
to dig out the error message and YaST logs.
Instead I simply exited and retried with an
up to date openSUSE Tumbleweed Snapshot20210914
which worked.
I guess the error was so fatal that YaST could not do
anything else than to exit straight.
But the UX is poor in such cases because in practice
it is then basically impossible for the user
to make a meaningful issue report.
I wished there was an easy way how to get the error message
and YaST logs out of the installation system in such cases.
The installation system had Internet access
so if there was some YaST error exit dialog
where error message and YaST logs could be sent
e.g. to any email address or something similar
(which the user could enter/specify as he likes),
then it would be easy for the user to make later
(after he completed his current actual task)
a meaningful issue report.
Kind Regards
Johannes Meixner
--
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5 - 90409 Nuernberg - Germany
(HRB 36809, AG Nuernberg) GF: Felix Imendoerffer
This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet.
Pending requests in repository yast-devtools:
- Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (53 days)
https://github.com/yast/yast-devtools/pull/161
Pending requests in repository yast-journal:
- Use Yast::Builtins.strftime in 'Change Filter' dialog (19 days)
https://github.com/yast/yast-journal/pull/45
Hi Team,
How to add custom menu category in YaST Control Centre in SLES 15 SP3 and openSUSE Leap 15.3?
We need a custom Category in YaST Control Centre in SLES 15 SP3, so that we can place our custom application under that Category.
In SLES 12 SP5 we were able to achieve this by creating a custom.menu file having Menu Name, Directory, Category and placing that menu file under /etc/xdg/menus/YaST-gnome-merged
Since yast2-control-center-gnome has been deprecated in SLES15SP3 the above workaround is not working here.
Regards,
Gaurav
Hi there!
In the context of revamping yast2-users[1], I spent some days looking
for an alternative layout that could help to improve the current UI by
reducing the number of tabs and grouping form fields to make better use
of available space.
However, due to our resolution constraints (UI must fit well in an
80x24 terminal) and some UI library limitations[2], looks like there is
not too much room for big changes and our best bet is to keep the
layout almost as it is, just making some necessary adjustments[3].
Summarizing them a lot, those changes will consist of adding a top menu
bar for making easier the user navigation, moving all settings to the
same dialog, improving filters by using a popup, making small changes
in forms, and adding some summary views.
Of course, nothing is written in stone and it would be nice to know
your feedback and/or ideas too. So, please, keep reading the following
links if you are interested and tell us what do you think. Is there
anything we overlooked? Some other ideas we should evaluate?
Remember that you can reach us by email, on IRC, or even by directly
leaving a comment in those Github issues.
Thanks!
[1] "Revamping yast2-users" mailing list thread -
https://lists.opensuse.org/archives/list/yast-devel@lists.opensuse.org/thre…
[2] "UI library limitations"
https://github.com/yast/yast-users-ng/issues/8
[3] "Revamping yast2-users UI: an initial proposal"
https://github.com/yast/yast-users-ng/issues/6
--
David Díaz
YaST Team at SUSE LINUX GmbH
IRC: dgdavid