YaST Development June 2012

yast-devel@lists.opensuse.org

12 participants
9 discussions

by Bryen M Yunashko

With my vision continuing to get worse, I notice with each new installation, I have more difficulty reading the installation screens. This is an accessibility issue. It would be nice if we could provide high-contrast option as well as font size change in the Video Mode list. Is there anything we can do to work on this in the near future? I'd like to be able to continue to use openSUSE for the long term. :-) Text mode is available but again, limited ability to see well without good high contrast. Bryen -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

9 years, 11 months

[yast-devel] Be aware of mixture code compiled with c++1x and c++98

by Josef Reidinger

Hi YaST hackers, maybe some of you already see lot of failures in factory YaST. One of goodly hidden problem is mixture of code compiled with c++1x and c++98. This is exactly what cause segfault in gtk sw_single. for explanation see comment from michael matz - https://bugzilla.novell.com/show_bug.cgi?id=767666#c11 Core is compiled with c++1x ( due to libzypp I expect ). So other parts that use core should be also compiled with this flag. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

9 years, 11 months

[yast-devel] 12.2 branches for libyui

by Thomas Goettlicher

Hey, As libyui refactoring in master takes a little bit longer, I created 12.2 branches for affected the repos. Please use these branches if you fix bugs for 12.2. Don't forget to cherry pick your fixes to master then. Many thanks, Thomas -- Thomas Goettlicher SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

9 years, 11 months

[yast-devel] patch for yast2-devtools

by Arvin Schnell

Hi, please review atteched patch for yast2-devtools. The reason for the patch is as following: A few days ago I changed yast2-core and increased the version numbers of liby2util and libycpvalues. But the plugin in yast2-xml does not link against those libraries so the buildservice does not rebuild yast2-xml thus the users following factory update yast2-core but not yast2-xml and the system gets broken (reported by customer). So the plugins have to be linked against those libraries which the patch does. Regards, Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany

9 years, 11 months

[yast-devel] Fixing yast git repos ; dont push until 10:00 UTC

by Bernhard M. Wiedemann

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Hackers, Some weeks ago the YaST repos migrated from svn to git and are now on github.com. As you might have heard, some(*) YaST repos have a broken history. This was caused by a bug in svndumpfilter3 that we used in the conversion process. We (Martin Vidner, Daniel Schmidt and Bernhard Wiedemann) now found a way to fix the repos without the need for everyone to reclone his checkouts. Please dont push anything to github.com/yast/* while we push the fixed repos - should be finished by 10:00 UTC. * Preconditions 1. If you don't have forks or checkouts of those yast repos, all is fine already and you don't have to do anything. 2. If you have clones without any local changes, you can just delete the clones and re-create them from github. (*) To check if your repository's history was affected by the bug, look for it in http://www.zq1.de/~bernhard/yast-broken-list.txt * What is Expected You likely heard that you should not change the public history of a git repo. We had to do exactly this because the history was just wrong. So if you have a fork or local checkout with own commits that are not yet pushed to github.com/yast/ then you have to do =========================== git pull --rebase =========================== once per affected repo and branch. Your branch(es) should now point to the fixed history while the old history is preserved in the "remotes/origin/broken/$BRANCH". They should only be needed for recovery. * What is Unexpected If you did for some reason git pull it creates a bad merge commit or conflict # if you have a merge conflict you have to git reset --hard HEAD # reverts it # if you get a merge commit you have to git branch yourstuff ; git reset --hard origin/$BRANCH git cherry-pick $commit # what you want to keep from yourstuff branch * The Unexpected Unexpected If you encounter any other problems, please contact us. About libyui: We will have a look at the situation after fixing the yast repos. Stay tuned. regards Daniel, Martin and Bernhard - -- (o_ //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/YVDgACgkQSTYLOx37oWRyrwCfQa+4yZY8w9J4ilPCuZGhJqeh 70kAn1K3z3Q+n5uGcAdEzLNUv/w0koRq =8upa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

9 years, 11 months

[yast-devel] blocxx removed from yast2-core

by Arvin Schnell

Hi, as requested in fate #313242 I have removed blocxx usage from yast2-core. It was used for logging. If you have e.g. libraries or plugins used by YaST which used this logging mechanism use something else, e.g. like libzypp, libstorage and libsnapper do. ciao Arvin PS: You can likely remove the buildrequires for blocxx from your YaST packages. -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

9 years, 11 months

[yast-devel] led display Suppliers shared photos with you

by led display Suppliers

Dear Mr/Miss, Still be puzzling about looking for best led display supplier? Now it will be miles easier working with KEROSA! Here you can find competitive price and excellent quality with a best mix. We"ve been in led display career for many years. We know your market and your country well. Our business is flexible which something is more likely to be a friend chat. We never waste your time. Our conversation will be very efficient base on our good communication. Please reply as soon as possible .if you are working on some led display project. We are ready to make you a satisfied offer! Samuel Shezhen Krosa Techology Co.,Ltd. Address: Building 3,Park,Guanguang road,Bao"an District,Shenzhen,China. post 518000

9 years, 11 months

[yast-devel] relationship between libyui and yast2-{gtk,ncurses,qt}-pkg

by Björn Esser

Hello! I'm currently working on a CMake-based buildsystem for the liberated libyui and it's plugins. And I have a few questions about the relationship between libyui and yast2-{gtk,ncurses,qt}-pkg. So the pkg-things are build-depending on the corresponding libyui-plugin, afaik. libyui-{gtk,ncurses,qt} are loaded from libyui directly when init of the ui. Thomas Goettlicher and I agreed to have plugins, that belong to a certain program (e.g. YaST2), but are loaded through libyui, put inside a subfolder of /usr/lib/yui (e.g. /usr/lib/yui/YaST2 for YaST). The plugins which are loaded from yast-core should stay where they are (/usr/lib/YaST2/subfolder). But from where and how are those yast2-{gtk,ncurses,qt}-pkg loaded? yast-core or libyui? If they are loaded by libyui they should be covered from it's new buildsystem, too. Otherways they can be build by the yast-devtools. I had some mail-dialogue regarding this with Josef already, but he isn't sure about this special case. I hope someone is able to answer my question. A lot of thanks in advance. Best Regards, Björn -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

9 years, 11 months

[yast-devel] YaST svn migrated to git

by J. Daniel Schmidt

Hi YaST hackers, the YaST svn migrated to git - finally! After about 24 hours the conversion was completed. All 147 YasT modules are now uploaded to github.com. If you do not yet have a login on github.com, go and create one. The YaST modules are grouped in the yast organization: https://github.com/yast As the libYUI was extracted from the YaST code base we put them into its own organization to underline its independence: https://github.com/libyui We also got our first forks while I was still uploading the repos. This shows the collaborative strength of git hosted projects. To make your initial clones a little easier there is a small tool called 'y2m' in this repo. https://github.com/yast/yast-meta If just follow the installation instructions in the README this tool helps you to clone or checkout all (or just some) YaST modules. Please feel free to adapt and improve this tool (grep for TODO) or write a better one. I just wanted to give those guys who are used to svn a small tool to help them getting started. Just one module did not make it in the conversion: yast-qt-pkg I will reenable write access to it in svn. Thus it will be migrated later. Please note the 'Conventions' for naming branches and tags for released products: http://en.opensuse.org/openSUSE:YaST_SVN_to_GIT For any questions related this to this switch contact us on our mailing lists: http://en.opensuse.org/Portal:YaST or chat with us in the #yast channel on irc.freenode.org Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE LINUX Products GmbH Research & Development Maxfeldstr. 5 HRB 16746 (AG Nürnberg) D-90409 Nürnberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

9 years, 11 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development June 2012