September 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] buttons buttons buttons
by Martin Schmidkunz 24 Oct '08

24 Oct '08

Hi, when testing openSUSE 11.1/SLES 11 I came across a rather curious situation: many modules have already switched their label from Abort/OK(Accept, Finish...) to the style guide compliant Cancel/OK label. However in every case there is a third, inactive "Back" button included. This doesn't make sense as there is nothing to go back and the dialog is just an overview. I suppose this is due to many of you using wizard.ycp as base template for creating your module. What do you think about using the button box (http://lizards.opensuse.org/2008/08/28/button-order-in-yast-trying-to-make-…) instead of the buttons of wizard.ycp? In my opinion this would have the following advantages: * consistent button order in pop ups and in the module * user would not need to deal with an inactive button * button order in YaST would be consistent with the desktop used by the user What do you think about that issue? Cu, Martin -- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 6

[yast-devel] yast2-qt Title Bar Enhancements
by Thomas Goettlicher 01 Oct '08

01 Oct '08

I've added some enhancements to the title bar shown by the window manager in yast2-qt. Until now yast2-qt windows had names like YaST, YaST <2>, YaST <3>... That made it difficult to keep an overview of the open YaST modules. Most modules with wizards have there own desktop file with an icon and a list of localized names. The icon has been displayed in the title bar for a long time. The localized name can be used for the window title by now (libyui 2.17.12, qt 2.17.12, yast2 2.17.34). The command to make this happen is pretty simple. Similar to SetDesktopIcon you can use SetDesktopTitle to set the window title of a wizard. Example: Wizard::SetDesktopTitle("lan"); SetDesktopTitle searches for the desktop file in the directory /usr/share/applications/YaST2 and retrieves the localized name. This string is shown in the window title with a prepended "YaST2". If we want to benefit from this enhancement I'd like to ask the maintainers who use wizards to add this single line. Please let me know if you have any objections, suggestions or questions. Thanks Thomas -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 8

[yast-devel] Beware: libzypp-5.13.0 - WhatProvides::empty retruns invers result.
by Michael Andres 29 Sep '08

29 Sep '08

Hi! In libzypp-5.13.0 zypp::sat::WhatProvides::empty retruns the inverse result. That's the reason why e.g zypper in -C 'capability' fails. Just WhatProvides::empty is affected, size and iterator behave as expected. libzypp-5.13.0 is on beta2, so remember this in case of strange error reports. Fixed in 5.13.1 -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] RC1: Prague YaST team meeting 2008-09-23
by josef reidinger 29 Sep '08

29 Sep '08

Prague YaST team meeting 2008-09-16 =================================== Present: jkupec, jreidinger, jsrain, juhliarik, jsuchome, kmachalkova, locilka, mzugec Absent: mvidner, lslezak Minutes: jreidinger Next minutes: jsrain libzypp/zypper (jkupec) ----------------------- Keyring callbacks now take KeyContext object to provide some context (repository) information in which the GPG-related issue appeared. Zypper and YaST have been adapted to show this info (bnc #370223). new zypper command: 'licenses' - provides information about licenses of installed packages Continues to work on commit history. Discussion about separate folder /var/log/zypp versus saving logs to /var/log/YaST2/. Documented at http://en.opensuse.org/Libzypp/Package_History jsuchome --------- more modules support dynamic load rpm in inst-sys. kmachalkova ----------- All AA modules now have the very basic commandline support (print "This module does not support commandline" instead of opening UI in CLI mode) (bnc #269891) Default portmapper is rpcbind instead of portmap (which is still supported). Neither portmap nor rpcbind were in inst-sys, making mounting nfs directories and installation onto nfsroot impossible. Rpcbind has now been added and libstorage adjusted to use it. (Bnc #427428) On diskless machine (where automatic partitioning proposal is not possible and user has to modify partitioning by himself), expert partitioner is now started instead of trying to have user select one of (non-existent ;-) ) hard disks to partition. This enables him to mount nfs root or launch iSCSI client. Bnc (#421541) locilka ------- (During upgrade) libzypp doesn't provide any information about old products installed (bnc #429177) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Restarting YaST
by Lukas Ocilka 29 Sep '08

29 Sep '08

Hi, I've just added a new possibility to restart any YaST module/client while running it from /sbin/yast(2). So far only 'online_update' and 'menu' could have been restarted. The new feature is in yast2-2.17.33. Restarting is easy: * Create /var/lib/YaST2/restart_yast file * Exit the module/client * --> YaST is restarted * Check whether the file exists (which means got 'restarted') * Remove that file Note: 'online_update' and 'menu' behave the same as before. Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

1 0

[yast-devel] [PATCH] yast2 exit codes
by Stanislav Visnovsky 26 Sep '08

26 Sep '08

Hi! This is a long standing issue: the YCP clients cannot set the exit code for the yast2 process. This makes a big piece of command line functionality unusable. Attached patch implements the following behavior: Exit codes: 0 - everything fine 1 - too few arguments 5 - error in arguments 16 - generic client error 16 + x - client returned 'x' as exit code This is not exactly nice, but it keeps backward compatibility with the already returning exit codes. Basically, if error code is >0 and < 16, this is parameter handling error. if >= 16, you get the exit code by subtracting 16. 0 means no errors. Clients can return only 2 types of exit codes: boolean: true - exit code 0 false - exit code 16 integer: 16 + value Examples: return nil; => exit code 0 return; => exit code 0 return true; => exit code 0 return false; => exit code 16 return "true"; => exit code 0 (it's string!) return 2; => exit code 18 return -15; => exit code 1 return -100; => exit code 172 (process exit code is unsigned) If there are no objections, I will commit the patch + documenting the behavior in man page and in the generated docs. Stano

4 9

[yast-devel] IP netmask broadcast address calculator
by Johannes Meixner 26 Sep '08

26 Sep '08

Hello, I am looking for a "IP address calculator" in YCP. For example when I have IP address and netmask I like to get the resulting broadcast address (not only for 8 16 24 bit netmasks). Or when I have only a IP host or network address, I like to get the usual netmask for it depending on the address block, e.g. 127.x.x.x -> 255.0.0.0 10.x.x.x -> 255.0.0.0 192.168.x.x -> 255.255.255.0 (or 255.255.0.0 ?) In particular it would be nice if it accepts the various ways to specify the netmask, e.g. nnn.nnn.nnn.nnn/mm versus nnn.nnn.nnn.nnn/mmm.mmm.mmm.mmm I guess there is already code in whatever YCP module but where is it? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] Nuernberg YaST team - meeting 2008-09-23
by Duncan Mac-Vicar Prett 25 Sep '08

25 Sep '08

Nuernberg YaST team - meeting 2008-09-23 present: aorlovskyy, aschnell, dmacvicar, gs, jdsn, ma, schubi, sh, shaas, snwint, tgoettlicher, mantel minutes: shaas Topics ------ - Installation theming problems bnc#427632 - Wizard with steps doesn't update step status icons bnc#429070 - Richtext unreadable because of patterned background - Boost library is not ready (the maintainer Philipp Thomas is on vacation) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] YCP tricks
by Stanislav Visnovsky 25 Sep '08

25 Sep '08

Hi! I've created a new wiki page for YCP/YaST development tricks and code snippets. http://en.opensuse.org/YaST/Development/Tricks Feel free to update the page! Stano P.S. I hope this does not duplicate any other page. If yes, let me know. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] SSH key changes between stage 1 and stage 2
by Arthur Rodrigo Sawazachi Valadares 24 Sep '08

24 Sep '08

Hi, I noticed that after you're done with stage 1 and the systems reboot, on stage 2 the SSH host key is different, which fires a warning for the client who already recorded the key in it's know_hosts. I think it would be interesting to avoid this issue by copying the keys from the RAM in stage 1 to the disk after partitioning it and before installing the system in it. I wanted to hear any comments or suggestions from this list and check if there's anything this behavior might affect for the worse. Thank you, -- Arthur V. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

[yast-devel] ZYpp History Log
by Jan Kupec 24 Sep '08

24 Sep '08

Hi! I'm about to commit the first version of new history logging for libzypp, which will be described at http://en.opensuse.org/Libzypp/Package_History This will replace the old /var/log/YaST/y2logRPM; the new log will be written to /var/log/zypp/history by default, configurable in zypp.conf. As per discussion with a few people, there should not be much to do to adapt to this change (it seems that libzypp was the only one writing to this file). You should just be prepared to request the file from bug reporters, if needed, because you won't get the file in the /var/log/YaST dir tarball. Also bug reporting wiki howtos can be adapted. We also can consider making a backup of the old log and leaving a note with the new location (yast2-core package could do this perhaps?). -- cheers, jano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Fwd: Info about yast2 web-wt
by Stefan Hundhammer 24 Sep '08

24 Sep '08

Anybody who can give this guy some more information than me? All I could tell him is "it's as good as dead". ---------- Forwarded Message ---------- Betreff: Info about yast2 web-wt Datum: Mittwoch, 24. September 2008 Von: Lamarque Vieira Souza <lamarque(a)syst.com.br> An: Stefan Hundhammer <sh(a)suse.de> Hi, I am a developer from Brazil and I am developing a project that needs web interface for Yast2 in OpenSuse 11. Searching the Internet I have found web-wt. I would like to know if the project is still alive, the last modifications seems to be made in november 2007, is that correct? I have started porting the code to OpenSuse 11, but there are several compiling errors. I would like to know in which environment you compile it? I am using OpenSuse 11, yast2-ycp-ui-bindings-devel-2.16.47-5.1, yast2-core-devel-2.16.51-6.1, yast2-libyui-devel-2.16.48-3.1, wt-library-devel-2.2.0-0.1, asio-devel-1.0.0-2.1, Xerces-c-devel-2.7.0-6.2, FastCGI-devel-2.4.0-111.1, apache2-mod_fastcgi-2.4.2-39.25, apache2-devel-2.2.8-28.1. I would appreciate if you could help with these information. Thank you. -- Lamarque Vieira Souza, MSc Senior Architect and Developer http://www.metasys.com.br Tel.: +55 31 3503-9040 ------------------------------------------------------- -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 2

[yast-devel] Re: [yast-commit] r51351 - in /trunk/network: VERSION package/yast2-network.changes src/modules/Modem.ycp
by Lukas Ocilka 22 Sep '08

22 Sep '08

mzugec(a)svn.opensuse.org wrote: > Author: mzugec > Date: Mon Sep 22 11:21:23 2008 > New Revision: 51351 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=51351&view=rev > Log: > Modem: check return value of installation (bnc#387716) > > Modified: trunk/network/src/modules/Modem.ycp > ============================================================================== > --- trunk/network/src/modules/Modem.ycp (original) > +++ trunk/network/src/modules/Modem.ycp Mon Sep 22 11:21:23 2008 > @@ -22,6 +22,7 @@ > import "Routing"; > import "Service"; > import "Summary"; > +import "Message"; > import "SuSEFirewall4Network"; > > include "network/complex.ycp"; > @@ -239,7 +240,8 @@ > > /* Setup SL modem */ > if(contains(Requires, "smartlink-softmodem")) { > - PackageSystem::CheckAndInstallPackages(Requires); > + if(!PackageSystem::CheckAndInstallPackages(Requires)) > + Popup::Error(sformat("%1 : smartlink-softmodem",Message::CannotContinueWithoutPackagesInstalled())); > y2milestone("Setting up smartlink-softmodem ..."); > > Service::Stop("slmodemd"); Hi, How is this supposed to work? Does it really exit from the function (and modem configuration) if packages are not installed? I'd say it only reports and error and continues but maybe I'm wrong... But the error message says something different: CannotContinueWithoutPackagesInstalled, isn't it a bit confusing? Or does network check the Requires anywhere else again? Bye Lukas

1 0

[yast-devel] Warning for opening YaST components from non-standard path
by Stanislav Visnovsky 22 Sep '08

22 Sep '08

Hi! I've implemented a new functionality to emit warning into the log file if YaST is loading e.g. namespace from non-standard location (/usr/share/YaST2/ prefix). This should avoid problems with forgotten files in /y2update or ~/.yast2. If you want to silence the warning, set Y2SILENTSEARCH environment variable. It's available in yast2-core > 2.17.12 (not in factory yet). Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

[yast-devel] Prague YaST team meeting 2008-09-16
by Jan Kupec 18 Sep '08

18 Sep '08

Prague YaST team meeting 2008-09-16 =================================== Present: jkupec, jreidinger, jsrain, juhliarik, jsuchome, kmachalkova, locilka, lslezak, mzugec Absent: mvidner Minutes: jkupec Next minutes: jreidinger locilka ------- - Coly's *yast2-multipath* has been moved to YaST SVN (since CODE11) - 1st ever *Python SCR agent* .multipath - dependencies on perl-XML-Bare removed from yast modules (only perl-XML-Simple is used now) - *Desktop Selection* dialog in installation can selection screen can now be completely configured in the control file. - Patches from IBM to include reIPL in installation/bootloader adapted to require reIPL on s390 only (FATE #304960) libzypp/zypper -------------- - support for NU services mostly done (fate #302376, #303563, #304915) - new zypper command 'modifyservices' - draft of a generalized NU-like protocol available at http://en.opensuse.org/Standards/Repository_Index_Service Implementation Recommendation will be added soon, based on current libzypp's implementation. Details to be discussed on MLs. misc ---- - jreidinger & juhliarik working on *TrustedGrub* support in bootloader - jsuchome working on *SMB* module feature #300967: Mount Server Home Directory Automatically with Authentication - kmachalkova wrote a *CLI for the router module*. - the *sound* module will support enabling/disabling of *PulseAudio* (fate #304936) (lslezak) - when the *network* module detects virtual environment and proposes bridged proposal, there is hyperlink to switch between this proposal and "standard non-bridged" proposal (mzugec) - lslezak works on integration of *services* to the existing *repositories* module. Some UI issues need to be solved. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

Re: [zypp-devel] [yast-devel] patch disk usage (was: repodata.c - clarification)
by Roberto Mannai 18 Sep '08

18 Sep '08

Hi all any news about the patch? Ciao Roberto On Tue, Aug 26, 2008 at 9:16 AM, Stanislav Visnovsky <visnov(a)suse.cz> wrote: > > Hi Roberto! > > Thanks a lot for the patch! Unfortunatelly, our maintainer for the package > selector is on vacation. > > Maybe someone else from the team can review the patch? > > Stano > > Dňa Friday 22 August 2008 23:32:51 Roberto Mannai ste napísal: > > Hi Stano > > > > > I believe zypp-devel is the proper mailing list for this. > > > > Yes, thank you, they clared the question. > > > > I append the patch, trying to resolve the enhancement in: > > https://bugzilla.novell.com/show_bug.cgi?id=399239 - "YaST's software > > installation modules should show disk space modification". > > > > It adds the string " - Installing x MB" or " - Removing x MB" to the > > tooltip on the "Free space" column (in the disk usage widget) . > > > > The disk usage variation will work for the same packages that change > > the disk usage bar; the zypp-devel mailing list pointed out that the > > repositories with disk usage attribute are those soddisfying the > > command: > > dumpsolv /var/cache/zypp/solv/MYREPO/solv | grep diskusage > > > > > > Here the patch, feel free to change (or throw away :)): > > > > > > Index: qt/src/QY2DiskUsageList.cc > > =================================================================== > > --- qt/src/QY2DiskUsageList.cc (revision 50308) > > +++ qt/src/QY2DiskUsageList.cc (working copy) > > @@ -229,9 +229,20 @@ > > if ( nameCol() >= 0 ) setText( nameCol(), name() ); > > if ( deviceNameCol() >= 0 ) setText( deviceNameCol(), deviceName() ); > > } > > + > > > > - if ( usedSizeCol() < 0 ) > > - setToolTip( freeSizeCol(), _( "Used %1" ).arg( > > usedSize().form( 0, 1, true ).c_str() ) ); > > + if ( usedSizeCol() < 0 ) { > > + QString message = _( "Used %1" ).arg( usedSize().form( 0, 1, > > true ).c_str()); > > + > > + if(deltaSize() > 0){ > > + message = message + _( " - Installing %1" ).arg( > > deltaSize().form( 0, 1, true ).c_str() ); > > + > > + } else if(deltaSize() < 0){ > > + message = message + _( " - Removing %1" ).arg( > > deltaSize().form( 0, 1, true ).c_str() ); > > + > > + } > > + setToolTip( freeSizeCol(), message); > > + } > > } > > > > > > Index: qt/src/QY2DiskUsageList.h > > =================================================================== > > --- qt/src/QY2DiskUsageList.h (revision 50308) > > +++ qt/src/QY2DiskUsageList.h (working copy) > > @@ -132,6 +132,13 @@ > > * is the default implementation. > > **/ > > virtual FSize freeSize() const; > > + > > + /** > > + * The delta partition space, after installation / removal. > > + * Derived classes may choose to reimplement this method. > > + * Default implementation returns 0. > > + **/ > > + virtual FSize deltaSize() const { return 0; } > > > > /** > > * The currently used percentage ( 0..100 ) of this partition. > > Index: qt-pkg/src/YQPkgDiskUsageList.cc > > =================================================================== > > --- qt-pkg/src/YQPkgDiskUsageList.cc (revision 50323) > > +++ qt-pkg/src/YQPkgDiskUsageList.cc (working copy) > > @@ -114,9 +114,16 @@ > > const ZyppPartitionDu & partitionDu = *it; > > YQPkgDiskUsageListItem * item = _items[ > > QString::fromUtf8(partitionDu.dir.c_str()) ]; > > > > - if ( item ) > > - item->updateDuData( partitionDu ); > > - else > > + if ( item ) { > > + int usedBefore = item->usedSize(); > > + item->updateDuData( partitionDu ); > > + int usedAfter = item->usedSize(); > > + int usedDelta= usedAfter - usedBefore; > > + if (usedDelta != 0){ > > + item->setDeltaSize(usedDelta); > > + } > > + > > + } else > > yuiError() << "No entry for mount point " << partitionDu.dir << endl; > > } > > > > @@ -258,6 +265,7 @@ > > , _partitionDu( partitionDu ) > > , _pkgDiskUsageList( parent ) > > { > > + _deltaSize = 0; > > yuiDebug() << "disk usage list entry for " << partitionDu.dir << endl; > > } > > > > @@ -268,8 +276,20 @@ > > return FSize( _partitionDu.pkg_size, FSize::K ); > > } > > > > +void > > +YQPkgDiskUsageListItem::setDeltaSize(FSize aDelta) > > +{ > > + _deltaSize += aDelta; > > +} > > > > FSize > > +YQPkgDiskUsageListItem::deltaSize() const > > +{ > > + return _deltaSize; > > +} > > + > > + > > +FSize > > YQPkgDiskUsageListItem::totalSize() const > > { > > return FSize( _partitionDu.total_size, FSize::K ); > > Index: qt-pkg/src/YQPkgDiskUsageList.h > > =================================================================== > > --- qt-pkg/src/YQPkgDiskUsageList.h (revision 50323) > > +++ qt-pkg/src/YQPkgDiskUsageList.h (working copy) > > @@ -234,6 +234,19 @@ > > * Reimplemented from QY2DiskUsageListItem. > > **/ > > virtual FSize totalSize() const; > > + > > + /** > > + * The delta partition space, after installation / removal. > > + * > > + * Reimplemented from QY2DiskUsageListItem. > > + **/ > > + virtual FSize deltaSize() const; > > + > > + /** > > + * Set delta partition space, after marking packages for > > installation / removal. > > + * > > + **/ > > + virtual void setDeltaSize(FSize aSize) ; > > > > /** > > * The name to display for this partition ( the mount point ). > > @@ -263,6 +276,7 @@ > > > > ZyppPartitionDu _partitionDu; > > YQPkgDiskUsageList * _pkgDiskUsageList; > > + FSize _deltaSize; > > }; > > > > > > > > Best regards > > Roberto Mannai > >

5 6

[yast-devel] libyui-python/ncurses crashes ...
by Jan-Simon Möller 18 Sep '08

18 Sep '08

I can reproduce 2 crashed here ... #1: Take wigets.py from svn, unset Display and select the "Frame" example. (this happenz only in ncurses) #2: If I try to use a simple Table, e.g. yTableHeader = yui.YTableHeader() yTableHeader.addColumn("Selected") yTableHeader.addColumn("Name") yTableHeader.addColumn("Version") yTableHeader.addColumn("Description") myTableMinSize = factory.createMinSize(VBox, 50, 12) myTable = factory.createTable(myTableMinSize, yTableHeader) # note YItemCollection seems unavailable ! myItem = yui.YTableItem("X", "foo", "1.2.1", "qwertz") myTable.addItem(myItem) myItem2 = yui.YTableItem("", "bar", "1.3.1", "asdasdasd") myTable.addItem(myItem2) Table shows, but on first click it segfaults. Best regards Jan-Simon -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 1

[yast-devel] yast qt4 ui polishing
by Nick Shaforostoff 17 Sep '08

17 Sep '08

hi. I'm KDE developer and know Qt4 well. Yast would benefit from a bit of polishing: e.g. it is easy to relayout it to always fit subnotebook's 1024x600 screens (e.g. move label for lineedit from top to left side so that they take 1 row instead of two). Hitting Esc should trigger cancel in confirmation dialogs, some places need scrollview, other - improved keyboard navigation. So: do you accept patches? is there any instructions to build Yast from trunk? pleace CC me on reply -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] [PATCH]Save and restore Stderr
by Wenji Huang 16 Sep '08

16 Sep '08

Hi, We had ported yast to RHEL4/OEL4 those could make widen users to experience the integrated administration tool. And Oracle Enterprise Manager could remotely operate on hosts through yast EM interface that will covert complex instructions to yast command line. The result of command will be transfered back to Oracle EM to give corresponding response. There is one important module in yast EM interface written by Bert Barbe. Some yast modules will re-directed Stderr to other place so that there is no information/results outputted after yast command is executed. SaveStderr.pm can save/restore Stderr to avoid this. A simple example for reference: import "SaveStderr"; import "xxx" //the module will re-directed Stderr to other SaveStderr::RestoreStderr(); CommandLine::Print Beside Oracle EM, it may be helpful to debug yast in command. We hope it can be merged into upstream yast so as not to keep separated one when porting yast to later RHEL. Regards, Wenji #!/usr/bin/perl -w package SaveStderr ; open OLDERR, ">&STDERR"; use strict; import YaPI; our %TYPEINFO; # return state of $use_gui BEGIN { $TYPEINFO{RestoreStderr} = ["function", "void"];} sub RestoreStderr { open STDERR, ">&OLDERR" ; } 1

1 0

[yast-devel] Re: [yast-announce] YDialogSpy Can Now Show Widget Properties
by Ricardo Cruz 15 Sep '08

15 Sep '08

Sex, 2008-09-12 às 20:36 +0200, Stefan Hundhammer escreveu: > http://lizards.opensuse.org/2008/09/12/ydialogspy-can-now-show-widget-prope… > http://files.opensuse.org/opensuse/en/b/bf/DialogSpy-02-prop.png Excellent. If you add the edit functionality you mentioned, you would be one small step of making a builder out of it. ;) Can you just move the memory address to the properties part or something (or move it to its own column). Makes the widget tree unnecessarily clutter and hard to read. Cheers, Ricardo -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Re: [yast-announce] YDialogSpy: An Interactive YaST Dialog Debugger
by Ricardo Cruz 15 Sep '08

15 Sep '08

Qui, 2008-09-11 às 17:29 +0200, Stefan Hundhammer escreveu: > http://lizards.opensuse.org/2008/09/11/ydialogspy-an-interactive-yast-dialo… > > Short version: Hit Ctrl-Shift-Alt-Y, and you'll get a window with the > widget > tree of the current dialog. You can highlight parts of the dialog (Buttons, > HBoxes/VBoxes with their content) to see the layout engine in action. > Very cool. Added support for the GTK UI. Cheers, Ricardo -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] [11.0] Change ipv6 setting via commandline?
by Lars Behrens 11 Sep '08

11 Sep '08

Hi there, which yast module do I have to use in order to switch off the ipv6 option? And btw. is there a browsable list of all options which can be configured via yast on the commandline? TIA! Cheerz, Lars -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 6

[yast-devel] Re: [zypp-devel] repository 'path'
by Jan Kupec 11 Sep '08

11 Sep '08

Michael Andres wrote: > On Thu, Sep 11, Jan Kupec wrote: > >> Hi Hackers, >> >> the support for *path* in repositories (the piece appended to baseurl) is >> still not perfect in libzypp. I am about to fix it, but first i've got a >> few questions. >> >> - DO WE NEED THIS AT ALL? :O) >> >> AFAICT, we needed this for multi-product media (like patch-CDs >> probably). I'm not sure why, though, can't we just go about it with >> two different URLs? If some 'conent' file references the other >> repo with a relative path, it should be no problem for libzypp to >> just use the baseurl+this_path, no need to treat them separately(?). > > > To handle a media set we need to to know 2 urls. > > > 1) the media root > > - This is the location of media.<n>/media. We need it to check e.g whether > the correct media is inserted. > > There are also other files like the gpg-keys, releasenotes,.. kept in the > media root directory and not per repository. > > - In case you copy a media set to your disk (to offer it via http, > nfs,...) > > /somewhere/DVD1 > /DVD2 > ... > /DVD<N> > > this is the place where you have to change DVD1 to DVD2 when changing > from media 1 to 2. > > > 2) the repositories root on the media > > This is the path to acces the repository on the media. If the media has > just one repo at /, you don't need the path. > > > > Libzypp could live without 'path'. We could simply guess the media root > when changing or verifying media. For CD/DVD it's obvious. And for disc > copies we could probe for a ending in digits, or for a media.<n> > directory. > > But you also have to adapt YaST (and maybe other tools), which currently > expect the url pointing to the media root. They download e.g > > repo.url()/control.xml OK, so this is what escaped my attention, some metadata only in the media root, and multiple-media repos (mutliple CDs/DVDs). Thanx! > Or we have to change the media layout an keep certain files per repo and > not per media. This might even be reasonable, but... We would still have problem with changing media http://foo/DVD1/ http://foo/DVD2/ http://foo/DVD1/repo2 http://foo/DVD2/repo2 currently we expect the media number at the end of the URL. We use this regexp: "^(.*)(cd|dvd)[0-9]+(/)?$". But you're right, this is not hard to solve. > It's not a zypp local change. If we want to go for this, we have to > convince some people. But it could be worth trying to do this. I agree. At this point i can't asses whether keeping and fixing the path in libzypp is more tricky than getting rid of it, i would need info from affected people. But i guess some people will say it is too late for 11.1. But another thing is, we never dealt with this kind of media layout since libzypp's refactoring after 10.2. So we really need to do something about it one way or the other. A side question: would we add such multi-product repository as two zypp repos? -- cheers, jano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] [Fwd: Re: [zypp-devel] repository 'path']
by Jan Kupec 11 Sep '08

11 Sep '08

forwarding Michael's reply (i posted the original to wrong mailing list) -------- Original Message -------- Subject: Re: [zypp-devel] repository 'path' Date: Thu, 11 Sep 2008 12:51:44 +0200 From: Michael Andres <ma(a)suse.de> Organization: SUSE LINUX Products GmbH, D-90409 Nuernberg, Germany To: Jan Kupec <jkupec(a)suse.cz> CC: ZYpp-Devel <zypp-devel(a)opensuse.org>, yast(a)suse.cz References: <48C8E7D3.3040800(a)suse.cz> On Thu, Sep 11, Jan Kupec wrote: > Hi Hackers, > > the support for *path* in repositories (the piece appended to baseurl) is > still not perfect in libzypp. I am about to fix it, but first i've got a > few questions. > > - DO WE NEED THIS AT ALL? :O) > > AFAICT, we needed this for multi-product media (like patch-CDs > probably). I'm not sure why, though, can't we just go about it with > two different URLs? If some 'conent' file references the other > repo with a relative path, it should be no problem for libzypp to > just use the baseurl+this_path, no need to treat them separately(?). To handle a media set we need to to know 2 urls. 1) the media root - This is the location of media.<n>/media. We need it to check e.g whether the correct media is inserted. There are also other files like the gpg-keys, releasenotes,.. kept in the media root directory and not per repository. - In case you copy a media set to your disk (to offer it via http, nfs,...) /somewhere/DVD1 /DVD2 ... /DVD<N> this is the place where you have to change DVD1 to DVD2 when changing from media 1 to 2. 2) the repositories root on the media This is the path to acces the repository on the media. If the media has just one repo at /, you don't need the path. Libzypp could live without 'path'. We could simply guess the media root when changing or verifying media. For CD/DVD it's obvious. And for disc copies we could probe for a ending in digits, or for a media.<n> directory. But you also have to adapt YaST (and maybe other tools), which currently expect the url pointing to the media root. They download e.g repo.url()/control.xml Or we have to change the media layout an keep certain files per repo and not per media. This might even be reasonable, but... It's not a zypp local change. If we want to go for this, we have to convince some people. But it could be worth trying to do this. > Is the 'path' part of YUM's definition? AFAIK not. It's not needed if you don't deal with media sets the way we do it. 'path' is actually part of the media handling, not of the repo. > - our repository definition allows multiple baseurls to be defined, as > well as mirrors (these are ignored currently IIRC). What to do with > this: > > [foorepo] > baseurl = http://url1.org/repos > baseurl = http://url2.org/whatever > path = foorepo/openSUSE/11.1 > > not to mention mirrors. Should we just use the path for all of the > baseurls? We have to. We must assume all urls point to locations with the same layout (not just same content). And in most cases you dont need the path as it's /. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- cheers, jano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] [YaST] Czech YaST2 team (Prague) meeting 2008-09-09
by Michal Zugec 11 Sep '08

11 Sep '08

Czech YaST2 team (Prague) meeting 2008-09-09 ============================================ Present: jsrain, jkupec, jreidinger, jsuchome, kmachalkova, locilka, lslezak, mzugec Absent: juhliarik, mvidner Minutes: mzugec Next Minutes: jsrain jsrain ------ - fixed some issues with uefi booting - work on yast2-support module jkupec ------ - support for services in libzypp (fate #302376, #303563, #304915) - username/password stored in separate file for repository authentication in libzypp - new zypper commands: targetos, versioncmp jreidinger ---------- - hackweek project: downloader for openSUSE ISO images http://idea.opensuse.org/content/ideas/standalone-download-program-for-open… - fixed bootloader problem (when replace kernel-default with kernel-pae, remember which item is default) (bnc#402789) jsuchome -------- - work on SCR agent for pam_mount.conf.xml (fate 300967) - yast2-users: load cracklib dictionary during installation only for the time needed - yast2-nis-*: use rpcbind as default instead of portmap (bnc#423026) kmachalkova ----------- - hackweek project: improved ayast_setup.ycp (CLI support) from autoyast2 package - netconfig support in yast2-network (DNS part - /etc/resolv.conf) - nfs-client integration with partitioner - works with nfs(v3) - nfs-client(v4) can write dmapd.conf now locilka ------- - WFM::ClientExists ( http://lists.opensuse.org/yast-devel/2008-09/msg00033.html ) - support for ButtonBoxes in yast2 - AutoYaST can use images now (like "normal" installation) (fate#301321) - different workflow can be used while upgrading an add-on comparing to workflow used for new installation (FATE#301997) lslezak ------- - hackweek project: exporting a yast namespace as a DBus service (the code is not much usable, too many problems, but at least I successfully installed a package via pkg-bindings namespace Pkg:: running on DBus) - PkgBindings uses Selectables instead of Pool - removed duplicate code, bug compatible with other tools - support for services in PkgBindings mzugec ------ - work on yast2-support - support for InfiniBand in yast2-network (fate#304870), (fate#304115) - special proposal for virtualization network (fate#303386) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Enforcing okButton and cancelButton
by Stefan Hundhammer 10 Sep '08

10 Sep '08

https://bugzilla.novell.com/show_bug.cgi?id=422612 This shows that there are cases where it is legitimate to have a pop-up dialog with a ButtonBox with more than one button, but only an okButton and no cancelButton: ...message... <Countdown> [Stop] [OK] We (mschmidkunz + tgoettlicher + sh) thought that this is the one exception from that rule; in general, all dialogs with more than one button should have an okButton (for the regular end) and a cancelButton (as a safe escape). Now locilka found one more exception: ...error... [OK] [Details...] Now I can't help that sinking feeling that there might be even more. If there is a significant number of cases where it makes sense to not enforce that sanity check (must have only one button or both okButton and cancelButton), we have to get rid of that check. But I still think that it's useful. Who has more examples where it might be legitimate to have more than one button, yet not both an okButton and a cancelButton? Opinions? Suggestions? CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

10 21

[yast-devel] Re: [yast-announce] YaST .pot-files back from proofreading
by Johannes Meixner 10 Sep '08

10 Sep '08

Hello, On Sep 8 12:20 Jiri Srain wrote (shortened): > YaST .pot-files are back from proofreading. They are available at > /suse/jsrain/Export/proofed-os11.1-2008-09-08 It seems the current printer.pot is for obsolete code: grep '^#:' /suse/jsrain/Export/proofed-os11.1-2008-09-08/printer.pot #: src/common/helps.ycp:272 #: src/modules/Spooler.ycp:532 ../devtools/yast2/ycp_puttext printer.pot.new . Warning: Can't find .ycp file src/common/helps.ycp Warning: Can't find .ycp file src/modules/Spooler.ycp There are no longer such source files in yast2-printer so that there is nothing to apply here at the moment. Therefore I simply moved the current printer.pot to /suse/jsrain/Export/proofed-os11.1-2008-09-08/DONE/ Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] use ALog::Item
by Martin Vidner 09 Sep '08

09 Sep '08

Dear hackers, you are all admins of your own workstations, I believe. Have you ever wondered what YaST did to your system? Or even what *you* did to your system a week or a month ago? Please have a look at your y2log now: sudo less /var/log/YaST2/y2log The information is (mostly) there, but it is buried in piles and heaps of debugging information. So yes, as if you did not have enough features to implement already, I am asking you for more. But the users will love it. Please take one (or all) of your modules and put in log messages using the API below. Presumably they are already there, using y2milestone. ALog stands for Admin's log, to remind you who the reader is. ALog::Item("/etc/ntp.conf: added 'server ntp.example.org'") ALog::Item("enabled /etd/init.d/ntp") ALog::Item("started /etd/init.d/ntp") ALog::CommitPopup() will lead to ALog::Note("set up ntp from local server") A prototype is in SVN already: http://svn.opensuse.org/svn/yast/trunk/yast2/library/log/src/ALog.ycp The interface is not set in stone (yet). Please comment and let's find a design that is useful and easy to use. Open questions: - actual log format References: - https://keeper.novell.com/sxkeeper/feature/303700?contenttype=text/html - https://keeper.novell.com/sxkeeper/feature/100386?contenttype=text/html - related log in zypp: http://lists.opensuse.org/zypp-devel/2008-07/msg00043.html -- 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(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

8 14

[yast-devel] Annoucement: New built-in functions WFM::ClientExists(...) && getenv(...)
by Lukas Ocilka 08 Sep '08

08 Sep '08

Hi, I've enabled the getenv() and implemented new WFM::ClientExists() functions recently. *getenv* (implemented by juhliarik) returns the current value if ENV variables which you can set using setenv [1]. *WFM::ClientExists* is similar to WFM::call [2] (without args) but instead of calling the client, it only returns whether client you want to call exists. This is very useful to prevent from runtime errors when running clients from another YaST modules, especially during installation. New documentation for these built-in functions will be available soon (next time we rebuild the documentation). [1] http://forgeftp.novell.com/yast/doc/SL11.1/tdg/setenv-choose.html [2] http://forgeftp.novell.com/yast/doc/SL11.1/tdg/call.html Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

1 0

[yast-devel] y2makeall --clean
by Stanislav Visnovsky 04 Sep '08

04 Sep '08

Hi! I've added a new option to y2makeall script to invoke 'make clean' before building. This is quite helpful if you did not recompile whole subversion for quite some time. Usage: 'y2tool y2makeall --clean' Patch for trunk yast2-devtools attached. Please, review and commit if useful. Stano

2 2

[yast-devel] Button Order
by Stefan Hundhammer 04 Sep '08

04 Sep '08

Fate #303446 covers a long-standing request: Support both GNOME and KDE button orders in YaST2. The UI now provides a new widget called ButtonBox that handles that in an abstract way. What we need to do now is to use that widget whereever appropriate. In many cases, this will be as simple as replacing `HBox( `PushButton(`id(`ok ), _( "&OK" ) ), `PushButton(`id(`cancel), _( "&Cancel" ) ) ) with `ButtonBox( `PushButton(`id(`ok ), _( "&OK" ) ), `PushButton(`id(`cancel), _( "&Cancel" ) ) ) More information at http://en.opensuse.org/YaST/Development/Misc/Button_Order [Any follow-up discussions please on yast-devel] CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 6

[yast-devel] Proposition: Input domain in static network configuration
by Arthur Rodrigo Sawazachi Valadares 03 Sep '08

03 Sep '08

Hi, I wanted to propose a patch for linuxrc (initially) to allow the user to set search domain on static network configuration (DHCP already pulls this info from server, but in the future we could also allow the user to input extra domains). This would allow the user to type simple hostnames instead of fully qualified hostnames for NFS, FTP, etc throughout the installation. Any comments and suggestions are welcome =) Thank you, Arthur V. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Hackweek: Unified Installation Progress
by Stanislav Visnovsky 02 Sep '08

02 Sep '08

Hi Hackers! So, Hackweek III is over and here is the result of my work - a grand unified installation progress. Global progress =============== The basic idea is that the progress consists "stages" - during a new install, there are 3: disk preparation, image deployment and package installation. Before the first client using the unified progress, the stages need to be set up, e.g. : list< map<string,any> > stages = [ $[ "name" : "disk", "description": _("Preparing disks..."), "value" : Mode::update() ? 0 : 120, // 2 minutes, who needs more? ;-) "units" : `sec, ], $[ "name" : "images", "description": _("Deploying Images..."), "value" : ImageInstallation::TotalSize() / 1024, // kilobytes "units" : `kb, ], $[ "name" : "packages", "description": _("Installing Packages..."), // here, we do a hack, because until images are deployed, we cannot determine how many // packages will be really installed additionally "value" : (PackageSlideShow::total_size_to_install - ImageInstallation::TotalSize()) / 1024 , // kilobytes "units" : `kb, ], ]; SlideShow::Setup( stages ); The function will calculate the partitioning of the unified progress based on estimate of a needed time. A stage can provide the estimate of time or an amount of data to be transferred (the constants used are based on assumption of 15 min install time and that the data are downloaded and written to disk). The logic is no rocket science as the only goal for a progress bar is to have it move somewhat regularly. A client using the new unified progress will do basically 2 things: 1) calls SlideShow::MoveToStage( stage-id ) - this will move the global progress to a proper position for start of the stage and updates also the label ("description" entry in the map) 2) calls regularly SlideShow::StageProgress( new_percent, new_label ) - new_percent is the progress inside of the current stage, the library will recompute this to get a global progress percents. - if new_label is nil, label is not updated. More functionality ================== The SlideShow dialog contains the following functionality: - global progress (see above) - subprogress for the current action (e.g. download a package, format disk, ...) - installation log - slide show support - optional package table - release notes viewer See the SlideShow API how to handle those. Implementation Notes ==================== During the hacking, I've splitted the old SlideShow module into 3: - Slides.ycp - handling of slide loading from the installation medium - SlideShow.ycp - generic API for the unified installation progress - PackageSlideShow - code specific for handling package installation, e.g. CDs, summary table, .... Attached are the complete new modules as diffs do not make much sense. Next, there is updated control.xml with a new installation client inst_prepareprogress which sets up the stages for normal installation. The rest are diffs for adapting to new APIs. Influenced code is in yast2-installation, yast2-packager and yast2-storage I've tested the code on modified alpha2 - new installation, update and also on running system. Qt and ncurses. Stano

2 3

[yast-devel] yast style guide effective
by Martin Schmidkunz 02 Sep '08

02 Sep '08

Hi everybody, finally the YaST style guide is finished and effective immediately! See: http://en.opensuse.org/YaST/Style_Guide So please take a look at your modules and polish them :-) As far as I can see the main issues are: * table with buttons http://en.opensuse.org/YaST/Style_Guide#Table_with_Buttons * using check boxes to enable/disable things * to make ConfirmAbort look like http://en.opensuse.org/Image:Ysg_discarding_changes.png * replacing "Abort" label with "Cancel" in wizardycp Thanks a lot to everyone contributing to the style guide! Especially to Lukas and Bubli! Cu, Martin -- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 2

[yast-devel] Re: [zypp-devel] Enabled distupgrade of the SAT solver
by Stefan Schubert 02 Sep '08

02 Sep '08

Cristian Rodríguez schrieb: > Stefan Schubert escribió: > >> Hi, >> I have enabled the distupgrade of the SAT solver. In order to use the old >> distupgrade you can set the environment variable ZYPP_NO_SAT_UPDATE. >> But this should be used as fallback only :-) >> >> This variable will can be used until the old distupgrade mechanism will >> be removed from libzypp. >> I will send an EMAIL when this happens. >> > > Will be nice if you can also describe what are the practical differences > between both and how they may affect users. > Ähm, the differences and the affects to the user should be: NONE. It is "just another" algorithm. :-) Greetings Stefan > Cheers. > > > > -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Enabled distupgrade of the SAT solver
by Stefan Schubert 02 Sep '08

02 Sep '08

Hi, I have enabled the distupgrade of the SAT solver. In order to use the old distupgrade you can set the environment variable ZYPP_NO_SAT_UPDATE. But this should be used as fallback only :-) This variable will can be used until the old distupgrade mechanism will be removed from libzypp. I will send an EMAIL when this happens. Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0