On Wed, 2019-12-11 at 12:23 +0000, jenkins(a)suse.de wrote:
> See <https://ci.suse.de/job/yast-POT-updater/173/display/redirect>
Hi all,
I've fixed the yast-POT-updater job that has been failing for around
two weeks. Just to make it clear, translations were submitted correctly
but, because of an escaping problem, Jenkins was reporting that the job
was failing.
Please, check MR#64[1] to our infra repo if you are interested in the
fix.
Regards,
Imo
[1] https://gitlab.suse.de/yast/infra/merge_requests/64
--
Imobach González Sosa
YaST Team at SUSE LINUX GmbH
https://imobachgs.github.io/
Hi all,
I have added the openSUSE:Leap:15.1:Update target to the YaST:Head OBS project.
Libzypp has been recently updated in Leap 15.1 and the latest pkg-bindings built in
YaST:Head were not compatible with it. Which means you could not combine the latest
15.1 updates with the YaST:Head.
So for the 15.1 distro with updates use this YaST:Head URL:
https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Leap_15.1_Up…
If you already use the original 15.1 repository you can just add the "_Update"
suffix into the URL in the *.repo file in the /etc/zypp/repos.d directory.
Enjoy! :)
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi there!
Today, while I was working to fix an issue when executing "yast2
system_settings" without enough permissions[1][2], some questions arose
to my mind. Let me share them,
* If I run "/usr/sbin/yast2" it warns about the permissions and only
shows a few modules[3]. So,
* Can we manage [1] and [2] in a "centralized" way? I mean, do we have
a way to know in advance when the execution of a certain module will
require root permissions? If the answer is NO,
* Can we open a discussion/research/whatever to do something to this
regard? Do you think it worth it? Or do you already had such discussions
in the past? If so, what was the conclusion?
Apart from these questions, a little bit off-topic but also related to
the topic, I found weird that "yast2 storage" prompt a warning[4] saying
> The storage subsystem is locked by an unknown application.
> You must quit that application before you can continue.
>
> Would you like to abort or try again?
when it is executed as a normal user. Actually is a problem with
permissions, not an "unknown application locking the storage subsystem".
Waiting for your inputs, thanks in advance.
See you.
[1] https://github.com/yast/yast-tune/pull/40
[2] https://github.com/yast/yast-bootloader/pull/583
[3]
https://gist.github.com/dgdavid/323e5aa879490e24ea2d0d520550e1fe#gistcommen…
[4]
https://gist.github.com/dgdavid/323e5aa879490e24ea2d0d520550e1fe#gistcommen…
--
David Díaz González
YaST Team at SUSE Linux GmbH
Hi folks!
Yesterday, we got a bug report about a crash at the moment to save the
yast2-ftp-server configuration when "Allowing for anonymous upload"
...
Caller: /usr/share/YaST2/modules/FtpServer.rb:522:in 'WriteUpload'
Details: undefined method 'mkdir' for
#<Yast::FileUtilsClass:0x00001002ce2a2c0>
...
After realizing that, probably, the code was written with the FileUtils
Ruby module[1] in mind but the Yast::FileUtils module[2] is being called
instead, two questions came two my mind
- How much time has been this broken without nobody noticing/reporting it?
The change was introduced exactly a year ago[3], do it means that the
yast2-ftp-server is no longer relevant?
- Do we have this problem in more places? I.e. Yast::FileUtils taking
the place of Object::FileUtils.
I don't have the answer for any of them ;) but I have a proposal[4] for
the last one: to implement the `method_missing` in the Yast::FileUtils
and fallback to Object::FileUtils. That way, we could avoid similar crashes.
What do you think?
[1] https://ruby-doc.org/stdlib-2.6.5/libdoc/fileutils/rdoc/FileUtils.html
[2]
https://github.com/yast/yast-yast2/blob/master/library/general/src/modules/…
[3] https://github.com/yast/yast-ftp-server/pull/54
[4] https://github.com/yast/yast-yast2/pull/997
--
David Díaz González
YaST Team at SUSE Linux GmbH
Hi all,
The YaST team has published another sprint report.
As usual, during this sprint we have been working on a wide range of
topics. The release of the next (open)SUSE versions is approaching and
we need to pay attention to important changes like the new installation
media or the /usr/etc and /etc split.
Although we have been working on more stuff, we would like to highlight
these topics:
* Support for the new SLE installation media.
* Proper handling of shadow suite settings.
* Mount points handling improvements.
* Help others to keep the Live Installation working.
* Proper configuration of console fonts.
* Better calculation of minimum and maximum sizes while resizing
ext2/3/4 filesystems.
* Small fixes in the network module.
You can find the whole report at h
ttps://lizards.opensuse.org/2019/12/05/yast-sprint-90/
Regards,
Imo
--
Imobach González Sosa
YaST Team at SUSE LINUX GmbH
https://imobachgs.github.io/