Stephan Kulow wrote:

You really shouldn't use the repo for real life systems. You would need to recompile all your yast modules. It's mainly meant for zypper users.

To recompile all yast modules use y2compile script from yast2-devtools (/usr/share/YaST2/data/devtools/bin/y2compile). The script iteratively recompiles all yast modules. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@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@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Martin Vidner napsal(a):

On Tue, Feb 19, 2008 at 08:43:03AM +0100, Ladislav Slezak wrote:

...

Stephan Kulow wrote:

...

You really shouldn't use the repo for real life systems. You would need to recompile all your yast modules. It's mainly meant for zypper users.

You hit an unlucky time window of instability following the Hack Week. Please have a look at a page with recovery tips: http://en.opensuse.org/YaST/Crashes (and tell us how we can improve it, or edit it yourself, it is a wiki)

I suggest that you stop using the zypp:svn repo. It is even less stable than Factory, which is less stable than Alpha 2 of 11.0, which is less stable than 10.3. Try reverting to one of these. If you cannot, wait until fixed RPMs appear.

...

To recompile all yast modules use y2compile script from yast2-devtools (/usr/share/YaST2/data/devtools/bin/y2compile). The script iteratively recompiles all yast modules.

Recompiling is a rather large gun. Try the above RPM repos first.

Thank all of you for answer... It is getting clear to me now... Ok, so what yast and zypper version / repo should i use if i want bleeding edge y2 with most features (next-gen package solver, new layouts etc)? When i use the 0.9series of zypper, i cannot find a yast package which can work with it... I also have to recompile all modules? (or at least the wrong ones). Best regards and thanks again Gryffus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

On Wed, Feb 20, 2008 at 03:36:12AM +0100, Gryffus wrote: 3am... oh, you are _not_ from Hong Kong :-)

...

Thank all of you for answer... It is getting clear to me now...

Ok, so what yast and zypper version / repo should i use if i want bleeding edge y2 with most features (next-gen package solver, new layouts etc)? When i use the 0.9series of zypper, i cannot find a yast package which can work with it... I also have to recompile all modules? (or at least the wrong ones).

For the bleeding edge, use the current trunk of yast+zypp SVN or whatever is the most bleeding experimental branch (recently they have been merged to trunk, so trunk will give you all blood there is). But be sure to follow yast-devel and zypp-devel.

...

Best regards and thanks again Gryffus

Ok, so i tried to compile YaST from SVN and i got an error compiling trunk/core.... The error is:

Making all in ycp-ui make[4]: Entering directory `/home/gryffus/yast-svn/trunk/core/libyui/src/ycp-ui' make all-am make[5]: Entering directory `/home/gryffus/yast-svn/trunk/core/libyui/src/ycp-ui' CXXLD libpy2UI.la /usr/lib/gcc/i586-suse-linux/4.3/../../../../i586-suse-linux/bin/ld: cannot find -lycp

Argh, that is a bug in SVN head, it is looking for a library that has been just built and is not installed yet. I have committed a fix. Obviously we could use CruiseControl for yast too... -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Gryffus napsal(a):

Martin Vidner napsal(a):

...

On Wed, Feb 20, 2008 at 03:36:12AM +0100, Gryffus wrote:

3am... oh, you are _not_ from Hong Kong :-)

Yeah, i'm not :-) I'm from Czech Republic... Just like you and many people a have seen here :P. But my day ends same as a day in Red Dragon (rd2.cz) which is in 04:00 am :P

...

...

...

Thank all of you for answer... It is getting clear to me now...

Ok, so what yast and zypper version / repo should i use if i want bleeding edge y2 with most features (next-gen package solver, new layouts etc)? When i use the 0.9series of zypper, i cannot find a yast package which can work with it... I also have to recompile all modules? (or at least the wrong ones).

For the bleeding edge, use the current trunk of yast+zypp SVN or whatever is the most bleeding experimental branch (recently they have been merged to trunk, so trunk will give you all blood there is). But be sure to follow yast-devel and zypp-devel.

...

...

Best regards and thanks again Gryffus

Ok, so i tried to compile YaST from SVN and i got an error compiling trunk/core.... The error is:

Making all in ycp-ui make[4]: Entering directory `/home/gryffus/yast-svn/trunk/core/libyui/src/ycp-ui' make all-am make[5]: Entering directory `/home/gryffus/yast-svn/trunk/core/libyui/src/ycp-ui' CXXLD libpy2UI.la /usr/lib/gcc/i586-suse-linux/4.3/../../../../i586-suse-linux/bin/ld: cannot find -lycp

Argh, that is a bug in SVN head, it is looking for a library that has been just built and is not installed yet. I have committed a fix.

Obviously we could use CruiseControl for yast too...

Oh gj. Thanx very much i will check if it builds now.

Regards Gryffus So, core has built, but now i have a problem with gtk - it cannot find an "ycp-ui/Y2CCUI.h"

make[2]: Entering directory `/home/gryffus/yast-svn/trunk/gtk/src' CXX Y2CCGtk.lo In file included from /usr/include/c++/4.3/ext/hash_map:64, from /usr/include/YaST2/ycp/YCode.h:228, from /usr/include/YaST2/ycp/YStatement.h:28, from /usr/include/YaST2/ycp/ExecutionEnvironment.h:22, from /usr/include/YaST2/ycp/y2log.h:16, from Y2CCGtk.cc:7: /usr/include/c++/4.3/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header which may be removed without further notice at a future date. Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file backward_warning.h. To disable this warning use -Wno-deprecated. Y2CCGtk.cc:8:27: error: ycp-ui/Y2CCUI.h: No such file or directory Y2CCGtk.cc:29: error: expected class-name before '{' token Y2CCGtk.cc: In constructor 'Y2CCGtk::Y2CCGtk()': Y2CCGtk.cc:31: error: class 'Y2CCGtk' does not have any field named 'Y2CCUI' make[2]: *** [Y2CCGtk.lo] Error 1 make[2]: Leaving directory `/home/gryffus/yast-svn/trunk/gtk/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/gryffus/yast-svn/trunk/gtk' make: *** [all] Error 2 What next? :-(( -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Dňa Tuesday 19 February 2008 09:04:50 Dominique Leuenberger ste napísal:

...

...

...

On 2/19/2008 at 09:29, Stephan Kulow wrote:

You really shouldn't use the repo for real life systems. You would need to recompile all your yast modules. It's mainly meant for zypper users.

Stephan, and all other hackers.

This brings me to an idea: how can we create a text (sort of license text, mandatory to be displayed at installation, like for java or acrobat), that could warn about such issues?

like a 'last minute read this or fix it yourself' infor message? then we could have some texts like 'If you install this package, please be aware that your system might not work anymore afterwards... those packages are for tests only'

I believe we used to have this functionality in the old packagemanager. We can misuse license if really needed. Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

...

...

This brings me to an idea: how can we create a text (sort of license text, mandatory to be displayed at installation, like for java or acrobat), that could warn about such issues?

...

I believe we used to have this functionality in the old packagemanager. We can misuse license if really needed.

We still have this functionality in our package manager (sort of, not sure if we're talking about the same). It's called install notify message and it is a property of a package. Package manager displays it in a small pop-up window if user selects the package for installation. For example, if you choose to install kernel-default, you will see:

"Install this kernel only if you know exactly what you are doing. YaST installs the correct kernel for your system automatically."

There are, of course, some limitations. These messages pop up only if you select package manually, so if a) solver selects it for your or b) you're updating the package, you'll see nothing (well, as for b) it used to work that way in ncurses, but I changed it for the sake of consistency, see: https://bugzilla.novell.com/show_bug.cgi?id=308410)

I think the fix was in the wrong direction. especially in this example (zypper) it might be by installing the test version fromzypp:svn that a warning would be appropriate even for an update. or maybe even earlier, already when adding a repo? Do we have such functionality at this point? Dominique -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

...

...

On 2/19/2008 at 13:35, Duncan Mac-Vicar Prett wrote: Dominique Leuenberger wrote: I think the fix was in the wrong direction. especially in this example (zypper) it might be by installing the test version fromzypp:svn that a warning would be appropriate even for an update.

or maybe even earlier, already when adding a repo? Do we have such functionality at this point?

Dominique Ths repo was meant for developers or testers. We don't intended to provide a unstable-supported-warned repository.

If during the intragration of zypp-svn into factory (for which we used the build service) we would have needed to waste time creating warnings for users and special packaging, then I would prefer the ability to hide build service projects so we communicate the url only to testers ;-)

Duncan

Duncan... sboslutely! This might also be a weak point of the search interface: just everything can be found... I'm not sure if the 'rating' system will help much in this case... the typical windows user coming over anyhow just 'clicks.. and let's see what happens'... greater version number must be better... so the ability to hide (or better, having first hidden and then publish) repositories would be really great ;) Dominique -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org