September 2008 - YaST Development - openSUSE Mailing Lists

[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