Sorry, I am quite late with this, but I would like to share my insight
about this topic. I have put some words down here [1] as a comment in
the gist. What do you think about it? Anyway, after talking with Ancor,
the most efficient way to go is to release current version in TW and
then open the
What are my eyes seeing [1] ! Obviously, it worths trying, we have to
get rid of all that zombies that makes the code too difficult. But
first, I would try to add unit tests for each file we want to fix. We
should be ensure that we are only killing zombies and not simply ugly
people :)
[1]
h
On 1/2/19 9:17 AM, Lukas Ocilka wrote:
Dne 21. 12. 18 v 15:41 Lukas Ocilka napsal(a):
C. If it's a "sigh" one, then ... ?
With the happy new year 2019 I realized that it must have been this one
:) All languages are weird. Including all spoken languages too.
So, what can we actually learn f
On 1/9/19 2:55 PM, Ladislav Slezak wrote:
Hi all,
the GitHub Services are deprecated and are replaced by GitHub web hooks.
Basically the Services provided an additional logic to process the hooks.
For example the email service sends email notifications to the specified
address,
while the w
So, due to the tools are available for all architectures, I guess we
should not limit Bcache to x86. Of course, we would receive bugs because
bcache tools does not behave correctly, but we could simply forward such
bugs to bcache. Another option would be to restrict bcache actions only
to x86.
I see very useful that template proposed by Ladislav. It could help
quite a lot for reviewers and everyone interested in the PR (e.g.,
release managers or QA people). I am starting with something similar,
see [1] and [2]. Definitely, I think this is better than a simple link
to internal Trello
On 2/15/19 8:42 AM, Ladislav Slezak wrote:
Hi,
we usually mark the not ready pull requests with [WIP] or some similar tag.
GitHub now provides an integrated support for draft pull requests,
see https://github.blog/2019-02-14-introducing-draft-pull-requests/ and
https://help.github.com/arti
On 2/18/19 8:40 AM, Ladislav Slezak wrote:
Hi,
I was debugging a random build failure of the yast2 package in OBS [1] and I'd
like
to share my findings.
You can use `ls *.foo` in shell or `Dir.glob("*.foo")` in Ruby to get the files
matching the glob pattern. However, there is a tiny bu
I agree with your solution and explanations. I had would go with the
option that duplicates and freezes the given string (just as I18n does),
because having different behaviors when calling to _() looks a little
bit surprising to me. But of course, if that supposes to kill our
memory, it clearl
On 6/10/19 10:06 AM, Josef Reidinger wrote:
V Mon, 10 Jun 2019 09:55:53 +0200
Ancor Gonzalez Sosa napsáno:
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
Althoug
Thanks Martin for the info.
I think is a good idea to have our own ".editorconfig" at some place.
Maybe we could add it to yast-devtools and deploy the file in the user home?
Regarding the rules, I would add both: trim_trailing_whitespace and
insert_final_newline. I see none case where they c
On 6/26/19 7:42 AM, Josef Reidinger wrote:
V Tue, 25 Jun 2019 17:05:31 +0200
Stasiek Michalski napsáno:
On wto, cze 25, 2019 at 5:02 PM, Josef Reidinger
wrote:
Hi,
Any other idea that can help?
I would be curious about how quick meson/ninja would as a replacement
for configure/make al
Hi guys,
I see we have several temporary branches in many YaST repos, for example
in yast-storage-ng:
SLE-12-SP2 tracked
SLE-12-SP3 tracked
SLE-15-GAtracked
SLE-1
On 7/10/19 2:46 PM, Josef Reidinger wrote:
V Wed, 10 Jul 2019 12:13:52 +0100
José Iván López González napsáno:
Hi guys,
I see we have several temporary branches in many YaST repos, for example
in yast-storage-ng:
SLE-12-SP2 tracked
SLE-12
On 8/27/19 12:50 PM, Ladislav Slezak wrote:
Hi all,
I just noticed that GitHub has a new option (well, new for me, I do not
know how long actually it is there...) in the repository settings in the
"Merge Button" section with description "After pull requests are merged,
you can have head b
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.
Maybe installation process is not that important for regular user?
Iván
On 11/11/19 9:15 AM, Arvin Schnell wrote:
Hi,
the
More feedback [1]. Still we can find people thinking that YaST is great!!
[1] https://www.youtube.com/watch?v=BKidnt7WC3s
On 11/12/19 12:38 PM, Ladislav Slezak wrote:
Dne 11. 11. 19 v 14:19 Stasiek Michalski napsal(a):
Keep in mind, in the running system, YaST is labeled as YaST. In the
instal
d0d520550e1fe#gistcomment-3092823
[4]
https://gist.github.com/dgdavid/323e5aa879490e24ea2d0d520550e1fe#gistcomment-3092825
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
em.
For older code, I would follow the Josef's suggestion: to use the scope
resolution operator to always start from the global scope (e.g.,
::FileUtils).
[1] https://gist.github.com/imobachgs/d90940315bd0471ee00b2a68ba22fbe5
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC:
rrences
and IMHO it deserves a trello card ;)
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
org/github/yast/yast-bootloader
Kind regards
And for c++, maybe coverxygen [1] could help (if doxygen was used for
documenting the code).
[1] https://github.com/psycofdj/coverxygen
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-de
So, please no one-shot fix just because someone screemed.
Well, I agree we need to re-think the UI of the Expert Partitioner, but
I guess that would be an Epic for SLE-16. Meanwhile, we can do small
improvements at the same time we start supporting new features for SLE-15.
--
José Iván López Gon
types of widgets.
And much more, as it will show in this talk.
TODO: Do you have some interesting feature that will be in Leap 15.1 or 15.2
that deserve mentioning in talk?
Josef
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel
report. But
that approach is risky if the bug is not detected by openQA but a final
user.
I have described a possible solution here
https://gist.github.com/joseivanlopez/bcf7185904922afae7d93f7518192864.
Feedback is welcome.
CU
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC
t; projects
created from that template. We can use every "sample" to teach about
something specific (e.g., how to create UI interaction, how to define a
YaST CLI, etc).
Thanks David for your collaboration!
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To u
will need to
repeat some
steps again, just be prepared for that.
HTH
Thanks for sharing this info!
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
would
make the proposal code much more straightforward.
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
On 6/8/20 6:40 PM, Arvin Schnell wrote:
On Mon, Jun 08, 2020 at 04:31:35PM +0100, José Iván López González wrote:
As I see it, several wizards could be unified. For example, for RAID, LVM,
Btrfs and even for Bcache we would have a wizard asking for:
* Technology (RAID, LVM, Btrfs, Bcache, Auto
On 6/9/20 8:06 AM, Arvin Schnell wrote:
On Tue, Jun 09, 2020 at 07:33:10AM +0100, José Iván López González wrote:
On 6/8/20 6:40 PM, Arvin Schnell wrote:
Is the end result of the wizard a file system, whether on RAID,
LVM or plain partition? In that case it basically matches the
abstraction I
On 6/9/20 8:43 AM, Arvin Schnell wrote:
On Tue, Jun 09, 2020 at 08:18:44AM +0100, José Iván López González wrote:
Later, the user could use the partition dialog to fine tuning the result,
for example to configure the filesystem options.
That is one thing I do not like about the expert
?
Thanks!
[1] https://bugzilla.suse.com/show_bug.cgi?id=1172874
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
?
Thanks!
[1] https://bugzilla.suse.com/show_bug.cgi?id=1172874
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
oid the failure in
YaST side.
Regards,
Iván
[1] https://bugzilla.suse.com/show_bug.cgi?id=1172898
[2] https://apidock.com/ruby/Kernel/require
[3] https://bugzilla.opensuse.org/show_bug.cgi?id=1172898#c20
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
symlink_require_test.rb
Description: application/ruby
mit:
commit bc4a9329ccd9e9d6f1bb86b63df4bd981d227985 (tag: Leap_15.2-GM, tag:
Leap_15.1-GM)
Author: Jenkins
Date: Sat May 11 02:30:17 2019 +
New POT for text domain 'storage'.
Is this ok?
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@
On 7/7/20 3:01 PM, Ladislav Slezak wrote:
Dne 22. 06. 20 v 17:29 José Iván López González napsal(a):
Hi all,
Recently, a bug report [1] was filed because translation updates are
taken quite long to reach the product. It seems that it took almost 1
year and 4 months to get an updated yast2
orage-ng/tree/master/package
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
is currently perceived by many YaST Team members as the most
limiting factor to any UI-related discussion, beyond the UI framework
itself.
Cheers.
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
-up dialogs is a price we cannot pay?
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
y a small set of actions.
Here, I clearly vote for 3. IMHO, having too many buttons does not help
at all. It makes the UI more complex. The real challenge is to find the
good buttons to keep.
Regards,
Iván
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsub
g
interesting to propose.
Regards,
Iván
--
José Iván López González
YaST Team at SUSE LINUX GmbH
IRC: jilopez
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
On 02/27/2017 07:51 AM, Ancor Gonzalez Sosa wrote:
Since the original thread is already ruined with discussions about
concrete API design details that were not the main topic of my question,
I will try once again from scratch.
Do we need a layer between libstorage-ng and (the rest) of YaST?
I
On 02/28/2017 11:23 PM, Ancor Gonzalez Sosa wrote:
I'm aware of several YaST-related projects during this Hack Week 15. So
I though it would be good to collect them all in a thread with a
sentence about the outcome/status, just to ensure they are not
forgotten. We could also use the thread to me
Hi,
Our openQA tests for storage-ng are all red since two days ago. There
are two different errors. One of then [1] appears in the upgrade process
and the problem is that yast-update is requiring enum_mappings.rb file,
but that file was removed from storage-ng package due to it is not
necessa
On 09/11/2017 10:33 AM, Josef Reidinger wrote:
Hi,
just quick observations from my installation with leanos 15 with new
storage. I am not sure if all issues are known, so if you mention which
one is not known, I can try to report it with proper logs.
1. clean 20 GiB disk. Proposal is something
At this moment I would simply raise the threshold. When time will allow
it, we can think about it, but for now I would increase it a little bit
(25-30 ?).
I would avoid to disable it completely. We need somebody/something who
remembers us we can do it better :)
On 11/29/2017 03:24 PM, Ancor
On 03/13/2018 03:11 PM, Ancor Gonzalez Sosa wrote:
I don't know which YaST-related tasks are planned for the openSUSE
Conference 2018 in May. Are we sharing the ideas somewhere?
I assume Josef will make his annual presentation about what's new in
YaST and I know that Imo and Schubi have an Aut
Thanks, great improvement!
On 09/12/2018 11:23 AM, Ladislav Slezak wrote:
Hi,
I have improved the Jenkins integration in our submission workflow,
since now the both Jenkins (internal and external) should report the build
result
status and the OBS submit request (if created) directly to the Gi
48 matches
Mail list logo
